text:
feat: Adding standard transformer keep alive & kafka configurations

Motivation
Recent change on standard transformer, introducing enable gRPC client keep alive and also publish prediction log. This PR adding the required helm chart changes to enable configuration change
Modification
Adding several environment variables
transformer.feast.grpc.keepAliveEnabled
transformer.feast.grpc.keepAliveTime
transformer.feast.grpc.keepAliveTimeout
transformer.model.grpc.keepAliveEnabled
transformer.model.grpc.keepAliveTime
transformer.model.grpc.keepAliveTimeout
transformer.kafka.brokers
transformer.kafka.maxMessageSize
pyfuncGRPCOptions

Checklist

[ ] Chart version bumped
[ ] README.md updated

@tiopramayudi You'll need to use helm-docs to generate README.md.

LGTM, can you rebase @tiopramayudi

authors: pradithya tiopramayudi

repo: caraml-dev/helm-charts


text:
fix: Set grpc as the container name when raw deployment mode is used

Description

UPI models (using gRPC) were unable to deploy using Raw deployment mode. It is related to this issue: https://github.com/kserve/kserve/issues/2728
The fix is to set the container name as "grpc" rather than "h2c" as the latter is only applicable for Serverless deployments ("h2c" also works for Serverless deployments using HPA based autoscaling metrics).
Modifications

api/cluster/resource/templater.go - Make createContainerPorts take the deployment mode into account

Tests

[ ] Deploying new PyFunc models using UPI + Raw Deployment

Checklist

[x] Added PR label
[x] Added unit test, integration, and/or e2e tests
[ ] Tested locally
[ ] Updated documentation
[ ] Update Swagger spec if the PR introduce API changes
[ ] Regenerated Golang and Python client if the PR introduces API changes

Release Notes

Fix UPI models unable to deploy using raw deployment mode

LGTM, Thanks @krithika369

source: gharchive/pull-request

repo: caraml-dev/merlin

license_type: permissive

license_source: github-api


text:
Grid documentation for as

It would be nice if there was a better explanation of how to use as prop of Grid component: https://carbon-components-svelte.onrender.com/components/Grid#props
I want to pass some actions to the underlying div or perhaps render the underlying div as a section instead.

as
let
No
boolean
false
Set to true to render a custom HTML elementProps are destructured as props in the default slot (e.g., <header {...props}>...

<Row as let:props>
  <section
    {...props}
    on:dblclick={(e) => {
      console.log("dblclick", e);
    }}
  >
    ...
  </section>
</Row>

source: gharchive/issue


text:
Cupcake website page content creation - Help/FAQ page

As a Cupcake website content creator

I need to: know what frequently asked questions our adopters have

so that I can: consolidate them and present them on the FAQ page.

Additional information

Let's create the content for the current release based on the v19a, Carbon website FAQ page and input from Linda, Wonil, and Jeff.

Acceptance criteria

[ ] A list of the questions published with markdowns
[ ] Reviewed the list with Linda, Wonil, and Jeff.
[ ] Content and design accepted by Linda.

@JennySanchez
FAQ page is ready for review!
Live link: https://deploy-preview-111--carbon-for-ibm.netlify.com/help/faqs

Our next step is to review the content with Linda and get her input on finalizing the content.

My feedback below in red.docx

@ljcarot Thank you for reviewing and making edits to the FAQ page content. It makes sense to me and I will make updates to the page.

@ljcarot FAQ page update completed and can be viewed on the Cupcake website.

@wonilsuhibm @jeffchew Please take a look and let me know if we missed anything. Thank you.

authors: JennySanchez jacobottesen-dgc ljcarot


text:
chore(SidePanel)!: remove deprecated prop from side panel components

Contributes to #1385
I removed the deprecated prop pageContentSelector from both SidePanel and CreateSidePanel and made sure that all of the tests still pass.
What did you change?
packages/cloud-cognitive/src/components/CreateSidePanel/CreateSidePanel.js
packages/cloud-cognitive/src/components/CreateSidePanel/CreateSidePanel.stories.js
packages/cloud-cognitive/src/components/CreateSidePanel/CreateSidePanel.test.js
packages/cloud-cognitive/src/components/SidePanel/SidePanel.js
packages/cloud-cognitive/src/components/SidePanel/SidePanel.stories.js
packages/cloud-cognitive/src/components/SidePanel/SidePanel.test.js
How did you test and verify your work?
Storybook and ran tests for both CreateSidePanel and SidePanel

@matthewgallo I've also dropped out the deprecated onActionToolbarButtonClick field.

authors: dcwarwick matthewgallo


text:
Component level tokenization - Data table

User Story

As a [user role below]:
Carbon adopter

I need to:
theme various tokens for the Data table component

so that I can:
apply an overall theme in my application

Additional information

This is component-level tokenization work identified in the epic https://github.com/carbon-design-system/ibm-dotcom-library/issues/2503
Latest code can be found at _data-table-core.scss, _data-table-action.scss, _data-table-expandable.scss and _data-table-sort.scss changes in: https://github.com/carbon-design-system/carbon/compare/master...asudoh:alternate-type-space

Acceptance criteria

[ ] Component-level tokens applied in Carbon

Carbon rejected the pull request as they do not have the resources to take on the work.  Closing the epic (#2503) and all of the linked issues.
Copy of Jeff's email summarizing the next steps:
We have worked extensively with Akira Sudoh (former Carbon team member) and have recently created a comprehensive code contribution to Carbon to introduce API tokens that would enable the expressive theme. After review from the Carbon team, they have unfortunately rejected our code proposal, stating that it would be too much for their team to support at this time. They have taken considerable resource reductions and their team is much smaller than it was previously which most likely contributed to this decision on their end.
With this news, our team is essentially back to supporting a proxy on our end. However, we have had very valuable learnings when working with Akira, and plan to execute on this new contingency plan:

Identify key Carbon components we would like to support in the expressive theme ◦We can begin with a set of essential components we would like to support, then expand over time

We will make full use of our automated visual regression tool that we recently stood up. This will be extended to our standalone storybook instance with the Carbon components that have the expressive theme enabled. The work that needs to be done here: ◦Activate visual regression testing for Carbon expressive components
-Create additional e2e tests to cover all variants

Take all of Akira's work, and apply the tokenization to the IBM.com Library instead ◦Rather than a hardcoded way of applying the proxy, we are thinking of having the API tokens as an offering from our team instead. This can be ultimately used by other IBM.com Library adopters if the need arises, plus adds more flexibility and scalability on our end

Updates to documentation/design kits for our adopters ◦We will need to own and create all supporting documentation for the expressive theme, so there is some upfront and continuing work around this.

We have almost all of the carbon components with a hardcoded proxy already in place so it serves as a very good starting point. We will be applying the action items above in order to future proof it as a manageable solution going forward.

authors: RobertaJHahn jeffchew

repo: carbon-design-system/ibm-dotcom-library


text:
CBAPI-3539: Update SDK to use watchlist manager v3 instead of v2 APIs

Pull request checklist
Please check if your PR fulfills the following requirements:

[x] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[ ] Tests have been added that prove the fix is effective or that the feature works.
[x] New and existing tests pass locally with the changes.
[x] Code follows the style guidelines of this project (PEP8, clean code, linter).
[x] A self-review of the code has been done.

What is the ticket or issue number?

https://jira.carbonblack.local/browse/CBAPI-3539
Pull Request Description

Replaces the v2 Watchlist APIs with v3 APIs, which includes ensuring that the org key is properly formatted into the URIs whenever necessary.
Does this introduce a breaking change?

[ ] Yes
[x] No

How Has This Been Tested?

Unit tests have been adjusted to reflect the changes.  No net loss of coverage as a result.  Additionally, a UAT script has been added.

Added in most recent commit.

license: MIT


text:
https://js.adapools.org/groups.json is returning an empty array

Describe the bug
https://js.adapools.org/groups.json is returning an empty array (probably since their migration to cexplorer), creating more discrepancies with the adastat results. Maybe we shouldn't rely on this API anymore (at first glance, there is no correspondent endpoint on cexplorer).
To Reproduce
Steps to reproduce the behavior:

GET request on https://js.adapools.org/groups.json

It currently already gets skipped as a source, will be replaced by Koios as source soon

authors: andreAmorimF rdlrt


text:
🛑 mainnet - API is down

In 63c9236, mainnet - API (https://api.beta.explorer.cardano.org/api/v1/epochs) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mainnet - API is back up in dfaa74e after 1 minute.

repo: cardano-foundation/cf-explorer-status


text:
🛑 mainnet - API is down

In ef840ce, mainnet - API (https://api.beta.explorer.cardano.org/api/v1/epochs) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mainnet - API is back up in 00641e3 after 8 minutes.


text:
Add Maestro Dapp Platform builder tool

Checklist

[x] I have read the How to Contribute.
[x] I have read the Builder Tool Requirements
[x] I have run yarn build after adding my changes without getting any errors.

Builder Tool addition

Title: Maestro Dapp Platform
Description: Blockchain indexer, APIs and event management system for the Cardano blockchain.
Website:  https://www.gomaestro.org/dapp-platform
Get started: https://docs.gomaestro.org/
Tags:

http
hosted

From a quick look it might be better suited in the showcase section. (Similar to other services not a direct builder tool)

@rphair @katomm @fill-the-fill Can you please check my latest updates?

@katomm @fill-the-fill can you please approve?

@rphair When does this go into production?

@Vardominator generally editors can't even predict this.  Periodically, as you can imagine, staging gets merged into the production branch when everything seems to go well together.

authors: Vardominator katomm rphair

repo: cardano-foundation/developer-portal


text:
Add a button to add card if no cards in the stack

Ticket: CS-5464
https://github.com/cardstack/boxel/assets/12637010/58894458-fba5-4982-aa84-a83945257d3a

Make sure to include tests for this

authors: FadhlanR habdelra

repo: cardstack/boxel


text:
make rebuild fails because of missing directories

Hi Carla Team!
I am having some trouble with the command make rebuild. After following your guide on how to create sensors one is supposed to rebuild the project, but I get the following error:
x86_64-linux-gnu-gcc: error: /home/bake/carla/PythonAPI/carla/dependencies/lib/libxerces-c.a: No such file or directory
x86_64-linux-gnu-gcc: error: /home/bake/carla/PythonAPI/carla/dependencies/lib/libproj.a: No such file or directory
x86_64-linux-gnu-gcc: error: /home/bake/carla/PythonAPI/carla/dependencies/lib/libsqlite3.a: No such file or directory
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
make: *** [Util/BuildTools/Linux.mk:38: rebuild] Error 1

I don't know why this is the case since I installed all the dependencies and I also was able to build and launch Carla successfully. Do you have any input on this?
Thanks in advance.
CARLA version: 0.9.12
Platform/OS: Ubuntu 20.04

I have the same issue. The system is Ubuntu 20 as well.

I am facing the same issue. Also in Ubuntu 20.04. and Carla Version 0.9..12.
Did you find any solution?
Thank you in advance

Hey guys! No, I haven't I am first trying to integrate LibCarla in a different way and waiting for a response of the developers. If someone replies or I find I way I'll let you know

the solution is:
DO NOT make rebuild
just make clean and make PythonAPI and make launch

Same issue here! Have you found a solution?

@ucbmpc2021
I am just using make launch. If you really need to do a rebuild, you can manually copy the three libraries.
In this case:

copy the three libraries from CARLA_FOLDER/Build/proj-install/
make rebuild
Wait until the CARLA_FOLDER/PythonAPI/carla/dependencies/lib/ folder is created and paste the libraries inside.
Wait until the rebuild process is done.

It is just a workaround, but it worked for me.
OBS: In the same way, you will need to make launch to initiate the simulator

@MaikolDrechsler Thanks for your tips! Very helpful.

I'm trying to build the code inside Docker, so make launch isn't an option for me.
Can someone please fix the make rebuild command? :wink:

repo: carla-simulator/carla


text:
system gem dependency

Hello,
One of gems, which is required for some gems, requires the system gems i.e. rubygems verison >= 1.4.x. Can I point the requirements in the Gemfile? For example:
source :gemcutter
gem 'system', '1.6.2' #????
gem 'rubytree', '0.5.2'

Nope. That is handled by Rubygems.
On Oct 17, 2011, at 10:03 PM, Малъ Скрылевъ (Malo Skrylevo)reply@reply.github.com wrote:

Hello,
One of gems, which is required for some gems, requires the system gems i.e. rubygems verison >= 1.4.x. Can I point the requirements in the Gemfile? For example:
source :gemcutter
gem 'system', '1.6.2' #????
gem 'rubytree', '0.5.2'
--
Reply to this email directly or view it on GitHub:
https://github.com/carlhuda/bundler/issues/1485

Can you add the feature to the bundler? We can't rub budle procedure at heroku because of the dependency problem.

No, it is not possible.
Plus, even if we did, it still would not work on Heroku.

repo: carlhuda/bundler


text:
mio 0.3.6 doesn't compile

Lots of errors, of which the first is:
/home/vagrant/.cargo/registry/src/github.com-1ecc6299db9ec823/mio-0.3.6/src/net/mod.rs:22:27: 22:106 error: this function takes 2 parameters but 3 parameters were supplied [E0061]
/home/vagrant/.cargo/registry/src/github.com-1ecc6299db9ec823/mio-0.3.6/src/net/mod.rs:22         let linger = try!(nix::getsockopt(self.as_raw_fd(), nix::SockLevel::Socket, nix::sockopt::Linger)
                                                                                ^~~~~~~~~~~~~~

I guess the problem is that your Cargo.toml confidently goes and gets the latest nix from github:
[dependencies.nix]
git = "https://github.com/carllerche/nix-rust"

whereas I suppose it ought to get whatever version it actually relies on.

Thanks for the report. I fixed this on v0.3.x. I'll try to push a build shortly.

Was this resolved? What could I do to fix this issue locally?

Sorry for the delay. I pushed 0.3.7 to fix this: https://crates.io/crates/mio

authors: carllerche dimbleby mattcifelli

repo: carllerche/mio

license: mit

license_source: bigquery


text:
How can I parse input data as JSON that doesn't set the content type?

I have an endpoint that is /evaluate.json which does not guarantee that the request has a content type. This is triggering the assert:
https://github.com/carllerche/tower-web/blob/d35f6e4af0d36220dcee5e3f108f657645292096/src/extract/serde.rs#L98-L107
What kind of transformation do we need to make?

There should be a way to annotate the method or the request type. Maybe #[accept]?

If I understand, something like this would replicate today's behavior:
#[accept("application/json")]
fn compile(/* ... */) { /* ... */}

Would we allow multiple attributes?
#[accept("application/json")]
#[accept("text/json")]
fn compile(/* ... */) { /* ... */}

As well as no allow attribute?
Can we have two routes that differ only in accepts?
#[post("/user/:id")]
#[accept("text/xml")]
fn update_xml(/* ... */) { /* ... */}

#[post("/user/:id")]
#[accept("application/json")]
fn update_json(/* ... */) { /* ... */}

All of this would be good IMO.
To add, I think it should be possible to list multiple content types in one attribute:
#[accept("application/json", "text/plain")]

authors: carllerche shepmaster

repo: carllerche/tower-web


text:
Create templates for GitHub Issues

Scope
GitHub issue lack a standard for presenting the information
Proposed solution
Prepare a list of templates in GitHub (https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates) to simplify the creation of new Issues and provide a blueprint on which information are required
Type of Issues
There are multiple types of issues, but I would group them together as:

[ ] Bug Report
[ ] Feature Request
[ ] Documentation
[ ] Refactoring (more technical)
[ ] UI/UX Change Request

Reference link: https://github.com/stevemao/github-issue-templates/

This is also related to the #167 Accessibility Pass so I expect this will be bumped higher on my priority list. Currently setting conservative milestone of 3.2, but I expect it will be done sooner than that.
Top of mind tasks for myself:

[ ] Research varying Obsidian Plugin Repos and see how they have templates, if any. Also check some non-obsidian repos for differences.
[ ] Determine what is need to know information per information
[ ] Encourage screenshots and videos without clogging a ticket
[ ] Provide a space for superfluous information
[ ] Provide a space for proposed solutions, including examples from other GitHub repos/code

Tentative All-in-one Draft 1 for repo issues. Edit to look under the hood.

Scope

Current Actions

Example

Suggested Actions

Example

Possible Solutions or Implementations

Context or Use Case

Environmental Variables

Operating System:
Obsidian Version:
Obsidian Theme:
Obsidian RPG Manager Version:
Do you use custom css snippets?
Do you use a vault-syncing service like Obsidian Sync or Obsidian-Git?

I suspect that template is mostly adequate but we may need something different for pull requests as more goes into that.
How do you want to handle pulls? Do you have automated testing? Maybe read a Lovecraftian Alice in Wonderland for some ideas...

So... I tried to use the template for a few issues, and I think that it works. However, having one size to fit all creates a complex template that tries to solve all the problem in one go, creating more issues than it solves.
I will use the template and see if it overly complicated for some types of issues or if it can work
Thanks

I did use it a couple of times myself, and found it cumbersome to use on smaller screens if the example portion was left in.
I think those can honestly be left out, and replaced with a more realistic "how to write good tickets" pinned thread if we experience issues after this.

I am using it, but I find myself removing lots of data. I am also sure we can add the templates directly in GitHub, so we can associate them to a specific type of task

<As a>
<I want to>
<so that>

I like this portion.
The more I think about it.. you are correct, we will need more. Because a bug report involving the UI we'll need to know some things, like the questions I was asking about what theme they are using and what rpgm version they are using. In a feature request, we do not need that.

The portion you highlighted is standard user story requirement. It should never contain UI elements or details.
It can be further extended (for testing purposes) with acceptance criteria which follow this style:
<Given>
[<And>]
<When>
[<And>]
<Then>
[<And>]

Multiple acceptance criteria can fulfil one user story
<Given> I have added more than one image to a component
<When> I open the component
<Then> I see the carousel of images instead of a single image

<Given> I am in the component
<When> I want to add a new image to the component
<Then> I should see a link to allow me to upload a new image

<Given> I found and clicked the link to add an image to a component
<When> I am shown a new modal form
<Then> I can see two options: "select a local image" and "Add an online image"

<Given> I see the new image selection modal form
<When> I want to add an online image
<Then> I am shown a URL input text where to add the URL of the image

<Given> I am adding a new online image
<When> I add the url
<Then> the preview of the image is loaded
<And> the button to add the image is unlocked

...
...

@sigrunixia can we close this one?

Yep! Closing!

authors: carlonicora sigrunixia

repo: carlonicora/obsidian-rpg-manager


text:
Can you add the “give a like”  functionality for the reply below the forum post?

Like V2ex, can you add the "thank the replier ( or“give a like” to a floor)" functionality for the reply below the post? In V2ex,  clicks "thank the replier" to a reply below the post, it will refresh to see that this reply has a little red heart mark.
As shown in the figure.

Hi,@bnulhf.
I read the existing code. And I found that this feature has been implemented.
I think the reason you can’t see the thank you is because you haven’t logged in yet. Please log in and try again.
There is a Thank you with heart feature code: web/src/Reply.js
And I have already tested in the local environment.

It also works in online casbin-forum:

Hi,@bnulhf.
I read the existing code. And I found that this feature has been implemented.
I think the reason you can’t see the thank you is because you haven’t logged in yet. Please log in and try again.
There is a Thank you with heart feature code: web/src/Reply.js
And I have already tested in the local environment.

It also works in online casbin-forum:

Oh, that's true. I'm sorry I didn't notice. Thank you very much！

Oh, that's true. I'm sorry I didn't notice. Thank you very much！

authors: bnulhf oceanlvr

repo: casbin/casbin-forum


text:
[querstion] User load slowly in RoleEdit page

We have 2,000 users , user load slowly in RoleEdit page, the page is also very laggy.
How can I optimize this page?

<Row style={{marginTop: "20px"}} >
  <Col style={{marginTop: "5px"}} span={(Setting.isMobile()) ? 22 : 2}>
    {Setting.getLabel(i18next.t("role:Sub users"), i18next.t("role:Sub users - Tooltip"))} :
  </Col>
  <Col span={22} >
    <Select virtual={false} mode="multiple" style={{width: "100%"}} value={this.state.role.users}
      onChange={(value => {this.updateRoleField("users", value);})}
      options={this.state.users.map((user) => Setting.getOption(`${user.owner}/${user.name}`, `${user.owner}/${user.name}`))}
    />
  </Col>
</Row>

When I set virtual=true, it works well

@shiningstarts can you make a PR?

authors: hsluoyz shiningstarts

repo: casdoor/casdoor


text:
missing field wrap at line 1

Default example gives
missing field `wrap` at line 1 column 383
missing field `wrap` at line 1 column 383
missing field `wrap` at line 1 column 383
missing field `wrap` at line 1 column 383...

Developer console shows
8x degenerate.js:729 missing field `wrap` at line 1 column 320
8x degenerate.js:729 missing field `wrap` at line 1 column 383

Thanks for reporting this! Which example are you running, and what browser are you using? There's recently been a change to chrome that appears to be causing problems, so I'm wondering if that's related.

authors: casey hacker-DOM

repo: casey/degenerate


text:
Relax wallet limits

Allow wallets with more funds.

Done.

repo: casey/ord


text:
TODO: Determine Protocol Feasibility

"Decide whether or not I should do this at all. Fungible tokens are almost entirely meritless. However, alternative fungible token standards, like BRC-20, have a large on-chain footprint and have lead to a proliferation of UTXOs, and standards with no on-chain footprint have UX challenges and have been slow to see adoption."

There are two issues here as I see it:
One is personal motivation. I might decide that this is all just a horrible waste of time. However, it's all open source code, and whatever I do will likely have some value. Any motivated individuals can just pick things up from where I leave them.
The other is related to alternative protocols. I think that Taproot Assets and RGB are better than runes in many ways. Transactions can be kept confidential, and there is less on-chain footprint. However, there are a couple factors which make me worry that both protocols won't see significant adoption.
One of these factors is complexity. Taproot Assets and RGB are both fairly complex protocols to implement. This might limit the proliferation of compatible services which seem to have helped a lot with adoption of ordinals.
The other factor is UX complexity which comes from the fact that both protocols rely on off-chain data. This means that in order to perform transactions, users need to run their own server, rely on someone else's server, or use some kind of P2P network for the exchange of this off-chain data. I worry a bit that this might limit adoption, and and make it unappealing for end users.

We (Charlie and I + a lot of our friends in the industry) were having a public discussion about it and I am glad that my opinion about what this meant is VERY aligned with where you are at. Had to use disclaimers like, "I'm not Casey and don't speak for him" :smile:

Word :)

Maybe a "price check" on features like mint and transfer would be a good way to compare financial feasibilities? Price of mint, price of transfer, price of airdrop to 1-10-100 users.  I understand this will change as the size of transactions changes during development, but it might offer a baseline to compare with other protocols.

There are two issues here as I see it:
One is personal motivation. I might decide that this is all just a horrible waste of time. However, it's all open source code, and whatever I do will likely have some value. Any motivated individuals can just pick things up from where I leave them.
The other is related to alternative protocols. I think that Taproot Assets and RGB are better than runes in many ways. Transactions can be kept confidential, and there is less on-chain footprint. However, there are a couple factors which make me worry that both protocols won't see significant adoption.
One of these factors is complexity. Taproot Assets and RGB are both fairly complex protocols to implement. This might limit the proliferation of compatible services which seem to have helped a lot with adoption of ordinals.
The other factor is UX complexity which comes from the fact that both protocols rely on off-chain data. This means that in order to perform transactions, users need to run their own server, rely on someone else's server, or use some kind of P2P network for the exchange of this off-chain data. I worry a bit that this might limit adoption, and and make it unappealing for end users.

With regards to Taproot and RGB, id love to learn more, but googling only giving me blog posts which have no technical discussions. Where should I find more about this?

I'm having fun implementing, and I'm enjoying crafting the greatest shitcoin carnival the world has ever seen, so it's probably feasible.

Word

authors: BitTogether Psifour afeezaziz bluezdot casey summraznboi

repo: casey/runestone


text:
http metrics do not pre-aggregate

We pre-aggregated status codes to all, 4xx, 5xx etc. This caused
confusion for users when they tried to do aggregations on the metric
like sum(rate(http_request_latency_ms_count[1m])) because it ended up
tripling the rate.
This PR removes pre-aggregation, prefering to let the monitoring system
to do aggregation.

yay!

authors: mightyguava tirsen

repo: cashapp/misk


text:
Add JSON FeatureFlag

The LDFeatureFlag impl uses the guice registered Moshi instance to
deserialize the JSON into a POJO.
Most likely app developers will screw up the JSON values in LD,
resulting in Moshi deserialization Exceptions in their app.
However, it should be a rather quick change to update the value in LD.
I believe the usefulness of JSON flags for DynamicConfigs outweighs this chance
of human error.
I want to use this to dynamically configure jobqueue and event
consumers. Something like a JobqueueConsumerConfig:
{
"enabled": Boolean
"batch_size": Int
"schedule": TaskSchedule
}
TaskSchedule:
{
"more_work_ms": Int
"no_more_work_backoff: Backoff
"error_backoff": Backoff
}
This would be extremely difficult to manage with individual flattened
flags like "jobqueue_consumer_schedule_more_work_ms".

Nice!

Serialization exceptions are a good example of why in-code default values could be useful.
How controversial would it be to expand the Feature API to also include a safe get-or-default accessor that would bark loudly (e.g., with log.warn) and use the specified default. Maybe making it something you have to explicitly use would make it less controversial than making default value fallbacks a standard for all feature flag usage?
E.g.,
const val SOME_SAFE_DEFAULT = makeValidGsonThatWontExplode()
...
fun Feature.getOrDefault(..., defaultVal) {
  try {
    this.get(...)
  } catch (e: Exception) {
    log.warn("Flag not registered or value was invalid", e)
    SOME_SAFE_DEFAULT
  }
}
...
...
val definitelyValidParams = zachsJsonFeature.getOrDefault(flagInput, SOME_SAFE_DEFAULT)
doStuff(definitelyValidParams)

@zcross I still feel like that default value is a little bomb in the codebase. Lots of feature flags are created with a initial value, and then get turned on in production to a target value. But the default in the code will always be the initial value.

@zcross I still feel like that default value is a little bomb in the codebase. Lots of feature flags are created with a initial value, and then get turned on in production to a target value. But the default in the code will always be the initial value.

@zcross @swankjesse there is never going to be a golden answer to this problem, it is very use case specific. sometimes a default is totally sane, sometimes it could cause catastrophic consequences. additionally, failing a request that could use a sane default could also lead to catastrophic consequences.
The question is should we provide overloaded methods that accept an optional default. I think the concern there is it makes providing a default too easy, without forcing a developer to think through what happens if my code unexpectedly falls back to the default in the future. Is it really safe?
After initially being an advocate for defaults, and implementing my own default fallback logic in a library, I'm starting to realize defaults are hard to reason about. Ultimately it's much easier to think about the failure scenario of "failing to talk to LD and failing the request" vs "failing to talk to LD and running an old code path".
I think for now we force developers to implement their own try-catch-return default logic and reconsider adding it later.

Yeah, I think you got it exactly right. Running old code is a dangerous failure mode, whereas 503ing is a well-known failure mode.

authors: ryanhall07 swankjesse zcross


text:
Migrate to version catalogs and enable dependabot for them

Death to buildSrc/

Dependabot doesn't support version catalogs yet (https://github.com/dependabot/dependabot-core/issues/3121)

authors: JakeWharton veyndan

repo: cashapp/zipline


text:
Use ssl.external.enabled for UI alerts

This goes along with #161 and ssl.enabled being split into two properties in CDAP 4.0

LGTM

repo: caskdata/cdap-ambari-service


text:
Cask request: TeamCity

Cask details
Name - TeamCity
Homepage - https://www.jetbrains.com/teamcity/
License - Free
Download URL - https://www.jetbrains.com/teamcity/download/download-thanks.html?platform=mac
Description - Powerful Continuous Integration out of the box.

This appears to be a server application, not a GUI app. It's probably best suited for homebrew, see Homebrew/homebrew#46959

Agreed with @samshadwell. Closing.
On another note, it’s fine to ask for a few casks here and there, but when you ask for so many, we’d really prefer if you tried it, @codeapps. Next time, please try submitting a PR.

authors: codeapps samshadwell vitorgalvao

repo: caskroom/homebrew-cask


text:
makemkv fails to install (sha256 mismatch)

Hi,
actual sha256 checksum is:
76def66f7248267fb8774e1fc506d88199304237464474080391dea99d41c24d
(corresponds to v1.9.10 of makemkv)
Cheers.

https://github.com/caskroom/homebrew-cask/pull/20599

authors: moffat vitorgalvao


text:
Issue running edit and create commands.

Reported by humby in IRC
Running the create and edit commands isn't working as expected.
Create Output

$ brew cask create test
Error: No such file or directory - mate

  Most likely, this means you have an outdated version of homebrew-cask. Please run:

      brew update && brew upgrade brew-cask && brew cleanup && brew cask cleanup

  If this doesn’t fix the problem, please report this bug:

      https://github.com/caskroom/homebrew-cask/issues

/usr/local/Cellar/brew-cask/0.52.1/rubylib/hbc/utils.rb:138:in `exec'
/usr/local/Cellar/brew-cask/0.52.1/rubylib/hbc/utils.rb:138:in `exec_editor'
/usr/local/Cellar/brew-cask/0.52.1/rubylib/hbc/cli/create.rb:23:in `exec_editor'
/usr/local/Cellar/brew-cask/0.52.1/rubylib/hbc/cli/create.rb:17:in `run'
/usr/local/Cellar/brew-cask/0.52.1/rubylib/hbc/cli.rb:79:in `run_command'
/usr/local/Cellar/brew-cask/0.52.1/rubylib/hbc/cli.rb:119:in `process'
/usr/local/Cellar/brew-cask/0.52.1/rubylib/brew-cask-cmd.rb:18:in `<main>'

$ brew cask create test
Error: A Cask for test already exists. Run "brew cask cat test" to see it.

Edit Output

$ brew cask edit test
Error: No such file or directory - mate

  Most likely, this means you have an outdated version of homebrew-cask. Please run:

      brew update && brew upgrade brew-cask && brew cleanup && brew cask cleanup

  If this doesn’t fix the problem, please report this bug:

      https://github.com/caskroom/homebrew-cask/issues

/usr/local/Cellar/brew-cask/0.52.1/rubylib/hbc/utils.rb:138:in `exec'
/usr/local/Cellar/brew-cask/0.52.1/rubylib/hbc/utils.rb:138:in `exec_editor'
/usr/local/Cellar/brew-cask/0.52.1/rubylib/hbc/cli/edit.rb:18:in `exec_editor'
/usr/local/Cellar/brew-cask/0.52.1/rubylib/hbc/cli/edit.rb:12:in `run'
/usr/local/Cellar/brew-cask/0.52.1/rubylib/hbc/cli.rb:79:in `run_command'
/usr/local/Cellar/brew-cask/0.52.1/rubylib/hbc/cli.rb:119:in `process'
/usr/local/Cellar/brew-cask/0.52.1/rubylib/brew-cask-cmd.rb:18:in `<main>'

Doctor Output

$ brew cask doctor
==> OS X Release:
10.9
==> OS X Point Release:
10.9.5
==> Hardware Architecture:
intel-64
==> Ruby Version:
2.0.0-p481
==> Ruby Path:
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby
==> Homebrew Version:
0.9.5
==> Homebrew Executable Path:
/usr/local/bin/brew
==> Homebrew Cellar Path:
/usr/local/Cellar
==> Homebrew Repository Path:
/usr/local
==> Homebrew Origin:
https://github.com/Homebrew/homebrew
==> Homebrew-cask Version:
0.52.1
==> Homebrew-cask Install Location:
/usr/local/Cellar/brew-cask/0.52.1
==> Homebrew-cask Staging Location:
/opt/homebrew-cask/Caskroom
==> Homebrew-cask Cached Downloads:
/Library/Caches/Homebrew
/Library/Caches/Homebrew/Casks
0 files
0.00 megs
==> Homebrew-cask Default Tap Path:
/usr/local/Library/Taps/caskroom/homebrew-cask
==> Homebrew-cask Alternate Cask Taps:
<NONE>
==> Homebrew-cask Default Tap Cask Count:
2244
==> Contents of $LOAD_PATH:
/usr/local/Cellar/brew-cask/0.52.1/rubylib
/Library/Ruby/Site/2.0.0
/Library/Ruby/Site/2.0.0/x86_64-darwin13
/Library/Ruby/Site/2.0.0/universal-darwin13
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/x86_64-darwin13
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/universal-darwin13
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/x86_64-darwin13
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/universal-darwin13
==> Contents of $RUBYLIB Environment Variable:
<NONE>
==> Contents of $RUBYOPT Environment Variable:
<NONE>
==> Contents of $RUBYPATH Environment Variable:
<NONE>
==> Contents of $RBENV_VERSION Environment Variable:
<NONE>
==> Contents of $CHRUBY_VERSION Environment Variable:
<NONE>
==> Contents of $GEM_HOME Environment Variable:
<NONE>
==> Contents of $GEM_PATH Environment Variable:
<NONE>
==> Contents of $BUNDLE_PATH Environment Variable:
<NONE>
==> Contents of $PATH Environment Variable:
PATH="/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin:/usr/local/Library/Taps/telemachus/homebrew-desc/cmd:/usr/local/Library/ENV/scm"
==> Contents of $SHELL Environment Variable:
SHELL="/bin/bash"
==> Contents of Locale Environment Variables:
LANG="en_AU.UTF-8"
==> Running As Privileged User:
No

Previously reported as #8788. We have a fix in master; perhaps we should cut a bugfix release.
Refer to https://github.com/caskroom/homebrew-cask/issues/8919#issuecomment-70021838 for details.

authors: fanquake ndr-qef


text:
hapu: use secure url

Instructions

Look for and complete the section relevant to your submission. Delete the others, including these Instructions.
{{cask_file}} represents the cask file you’re submitting/editing (if applicable).
If there’s a checkbox you can’t complete for any reason, that’s OK. Just explain in detail why you weren’t able to do so.

Changes to a cask
Editing an existing cask

[x] Commit message includes cask’s name (and new version, if applicable).
[ ] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.

Checks fails every time because the appcast checkpoint returns a different value on each download. Not sure how to fix this. Though strangely the "appcast" seems like a human readable ChangeLog page, so maybe it should be used for homepage purposes instead.

As the appcast changes everytime it must be removed or another one needs to be found (I couldn't find one).
As the url has no version number (and no appcast is available) the version token needs to be set to :latest and the sha256 to :no_check (sha256 token reference).

Thank you, done.

authors: tsparber vszakats


text:
Remove starrealms.rb

Homepage shows only a Steam link for OSX on a much higher version than the cask version.

Recommend removal

If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so.
After making all changes to the cask:

[ ] brew cask audit --download {{cask_file}} is error-free.
[ ] brew cask style --fix {{cask_file}} reports no offenses.
[ ] The commit message includes the cask’s name and version.

Thank you for the contribution. It was merged directly as 6498b966fe380bc29d9c2343406d522af5139ed1 to keep commit history cleaner. Your contribution is still credited to you.

authors: colindunn vitorgalvao


text:
Update image2icon to 2.8

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if updating only the sha256:

[ ] I verified this change is legitimate How do I do that? and am providing confirmation below:

Thanks for the PR!

authors: commitay zach-adams


text:
Update usage guidelines for keys trash: and delete:

I couldn't find a commit in which this was done, but it seems like trash: does move files to Trash, and is no longer a synonym for delete:.

@commitay Maybe list of paths for zap and delete should be mention in documentation?

authors: nrlquaker tgdnt


text:
🛑 My Homepage is down

In e532d8c, My Homepage (https://casman.co.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: My Homepage is back up in e372577.


text:
Add detection for fileless executions to eBPF code

Each new process execution is now probed for filess execution, that might indicate something malicious going on.

@anjmao I've added another flag to indicate that a file was executed from a tmpfs.

repo: castai/kvisor


text:
LuceneIndexing errors on lateset repo?

I have tried to reproduce the doc2query related experiment.  I cloned the lastest master repo, but indexing parts failed with the following errors.
But I found out that it works on older branches.(say fastutil-removal)
It's little bit confusing, not sure what the real problem is.
(p.s. I run indexing on google colcab vm, and now it worked)

2020-05-10 07:52:42,088 ERROR [pool-2-thread-7] index.IndexCollection$LocalIndexerThread (IndexCollection.java:241) - pool-2-thread-7: Unexpected Exception:
java.lang.NoSuchMethodException: io.anserini.index.generator.LuceneDocumentGenerator.(io.anserini.index.IndexArgs)
at java.lang.Class.getConstructor0(Class.java:3349) ~[?:?]
at java.lang.Class.getDeclaredConstructor(Class.java:2553) ~[?:?]
at io.anserini.index.IndexCollection$LocalIndexerThread.run(IndexCollection.java:158) [anserini-0.9.1-SNAPSHOT.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
at java.lang.Thread.run(Thread.java:834) [?:?]

And the indexing results like this:(no indexing)

What instructions have you been following? Can you send link?
Should be DefaultLuceneDocumentGenerator instead of LuceneDocumentGenerator. Maybe we have outdated documentation that needs to be updated?

@lintool Big thanks! DefaultLuceneDocumentGenerator works;)
Yes, it seems that the dttttq & doc2query instructions need to be updated.

Can you please send PR with updates? That way we can acknowledge your contributions!

@lintool OKay, I have PR the updates!

authors: DylanJoo lintool

repo: castorini/anserini


text:
Test rebase

Just testing what a rebase would look like instead of squashing

yeah, can't deal with conflicts

repo: catalystneuro/neuroconv


text:
振听和途中流局还没有实现

振听判断的变量为 match::furiten

振听问题以及解决，途流待议。

repo: catcarbon/mjbot


text:
Should we provide a fallback for doctest_evalc?

The octave packages of Debian and Ubuntu do not come with mkoctfile and hence are not always installed. Not sure if we should provide the old fake_evalc as a fallback (+ buffering support...).

I'd say no. mkoctfile is included in the Windows build of Octave, mkoctfile can be easily installed with liboctave-dev in Debian and if it's missing, the user gets a good hint from Octave:
octave:1> pkg install -forge interval
pkg: please install the Debian package "liboctave-dev" to get the mkoctfile command

I'd also say no.
OTOH, If you want it around for bit for testing or whatever, I don't mind but definitely not with all the buffering stuff... (just let it interleave).

My motivation was that on my local server farm only the octave package (but not liboctave-dev) is installed. I nevertheless agree, and I think it's good to document these kind of decision and the rationale in the form of github issues. If there are sufficiently many other people suffering from the same problem we might reconsider providing a fallback.
(Note that we also have to use the octave/stable PPA for travis, which only provides octave but not liboctave-dev. For some magic reason, this seems to work with the distributions's liboctave-dev package...)


text:
Can add a new debug mode for the output executable SQL statement?

So the output SQL statement to the screen when debugging
Copy paste to the SQL manager, such as phpMyAdmin can be directly run to see the results are very convenient
Current.Log () debug () and last_query () methods are required to manually replace the field's double quotes as the number or delete to perform
Thanks!
PS:Your point of view impeccable!

The reason why you can not execute the generated query directly because Medoo is using the standard quote identifier from SQL-92 https://en.wikipedia.org/wiki/SQL-92 for all queries. You can see Medoo run SET SQL_MODE=ANSI_QUOTES for MySQL and SET QUOTED_IDENTIFIER ON for MSSQL from initialization to make them using this standard.
It's not the correct way to use Medoo that just copy and execute the Medoo generated query to another place alone, and that's not the usage Medoo recommended.
But we are considering to make the quote identifier be customizable from initialization, so that you can control what kind of quote should used.

authors: catfan iscraft

repo: catfan/Medoo


text:
fix(lichess): fixed a bit of unthemed stuff, aswell added prettier lichess support and more

🔧 What does this fix? 🔧
fixed unthemed feeds, buttons and colors on the homepage, aswell ingame
i also added support for prettier lichess
🗒 Checklist 🗒

[x] I have read and followed Catppuccin's contributing guidelines.
[x] I have updated the version appropriately in the ==UserStyle== header of the catppuccin.user.css file.

Please also see the linters complaints.

Please also see the linters complaints.

mkay

Please also see the linters complaints.

the linters work now

Please also see the linters complaints.

the linters work now

But the entire diff is 2 lines changed, with none of them being css changes.

Please also see the linters complaints.

the linters work now

But the entire diff is 2 lines changed, with none of them being css changes.

well u wanted them to work so here ya go

I'm not going to deal with this behaviour.

I'm not going to deal with this behaviour.

:/

authors: isabelroses kingofcube

repo: catppuccin/userstyles


text:
Support Dynamic member lookup

Be able to access properties of wrapped Input (or Output) like ordinary property access with KeyPath Dynamic Member Lookup feature.
struct Input: InputType {
    let searchText = PublishRelay<String?>()
    let buttonTap = PublishSubject<Void>()
}

let input = InputWrapper(Input())

input.searchText("query")  // accesses `func accept(_:)`
input.buttonTap.onNext(()) // accesses `AnyObserver`

struct Output: OutputType {
    let repositories: BehaviorRelay<[GitHub.Repository]>
    let isEnabled: BehaviorSubject<Bool>
    let error: Observable<Error>
}

let output = OutputWrapper(Output())

let o: Observable<[GitHub.Repository]> = output.repositories
let v: [GitHub.Repository] = output.repositories.value
let p: Property<[GitHub.Repository]> = output.repositories
let t: Bool = try? output.isEnabled.throwableValue()
let o2: Observable<Error> = output.error

In addition, PR introduces some breaking changes to improve interface with KeyPath.
To improve type inference.

[RENAME] Relay<Input> -> InputWrapper<Input>
[RENAME] Relay<Output> -> OutputWrapper<Output>

To avoid defining BehaviorRelay (or BehaviorSubject) like this: ReadOnly<BehaviorRelay<Bool>>

[RENAME] ReadOnly -> PrimitiveProperty
[DELETE] Dependency.readOnlyReference(from:for:)

Use OutputWrapper.property(for:) instead.

See also #8

repo: cats-oss/Unio


text:
Improvement: DO-1561 Allow calling create-dara-app programmatically

Motivation and Context

Allow passing project_name and package_name as an argument when creating an app.
Expose cookiecutter's no-input and overwrite-if-exists to give control back to the user.

Implementation Description

Any new dependencies Introduced
No
How Has This Been Tested?
Locally with all variations of arguments
PR Checklist:

[x] I have implemented all requirements? (see JIRA, project documentation).
[x] I am not affecting someone else's work, If I am, they are included as a reviewer.
[x] I have added relevant tests (unit, integration or regression).
[x] I have added comments to all the bits that are hard to follow.
[x] I have added/updated Documentation.
[x] I have updated the appropriate changelog with a line for my changes.

Screenshots (if appropriate):

@Roman-Kornev could we fix the tests here and then this can be merged? Thanks!

authors: Roman-Kornev tamara-causalens

repo: causalens/dara


text:
Incorrect datetime value for available_at column

I'm getting the error before when a try to queue a job. I'm using MySQL and I think it has to do with the way MySQL/PostgreSQL handles datetime.
[10:38:11.921] FATAL (adonis-background-job-demo/2916): "uncaughtException" detected
    Error: insert into `adonis_jobs` (`available_at`, `class_path`, `payload`) values ('2023-07-09 10:38:11.915 +01:00', 'app/Jobs/ExampleJob.ts', '{\"json\":{\"classPath\":\"app/Jobs/ExampleJob.ts\",\"data\":[{\"user\":{\"name\":\"John\",\"email\":\"john@test.com\",\"created_at\":\"2023-07-09T10:38:11.726+01:00\",\"updated_at\":\"2023-07-09T10:38:11.726+01:00\",\"id\":1},\"signedUrl\":\"/verification/john@test.com?signature=eyJtZXNzYWdlIjoiL3ZlcmlmaWNhdGlvbi9qb2huQHRlc3QuY29tIiwicHVycG9zZSI6ImVtYWlsIHZlcmlmaWNhdGlvbiJ9.-UyIPSjUUn1pWgBZiiEDVKjZ9gbxGsK1_BrkxCYs50g\"}],\"version\":\"v1\"}}') - Incorrect datetime value: '2023-07-09 10:38:11.915 +01:00' for column 'available_at' at row 1
        at Packet.asError (/Users/~/Workspace/adonis-background-job-demo/node_modules/mysql2/lib/packets/packet.js:728:17)
        at Query.execute (/Users/~/Workspace/adonis-background-job-demo/node_modules/mysql2/lib/commands/command.js:29:26)
        at Connection.handlePacket (/Users/~/Workspace/adonis-background-job-demo/node_modules/mysql2/lib/connection.js:497:34)
        at PacketParser.onPacket (/Users/~/Workspace/adonis-background-job-demo/node_modules/mysql2/lib/connection.js:97:12)
        at PacketParser.executeStart (/Users/~/Workspace/adonis-background-job-demo/node_modules/mysql2/lib/packet_parser.js:75:16)
        at Socket.<anonymous> (/Users/~/Workspace/adonis-background-job-demo/node_modules/mysql2/lib/connection.js:104:25)
        at Socket.emit (node:events:527:28)
        at addChunk (node:internal/streams/readable:315:12)
        at readableAddChunk (node:internal/streams/readable:289:9)
        at Socket.Readable.push (node:internal/streams/readable:228:10)
[10:38:11.954] WARN (adonis-background-job-demo/2916): pino.final with prettyPrint does not support flushing

/Users/~/Workspace/adonis-background-job-demo/node_modules/mysql2/lib/packets/packet.js:728
    const err = new Error(message);
                ^
Error: insert into `adonis_jobs` (`available_at`, `class_path`, `payload`) values ('2023-07-09 10:38:11.915 +01:00', 'app/Jobs/ExampleJob.ts', '{\"json\":{\"classPath\":\"app/Jobs/ExampleJob.ts\",\"data\":[{\"user\":{\"name\":\"John\",\"email\":\"john@test.com\",\"created_at\":\"2023-07-09T10:38:11.726+01:00\",\"updated_at\":\"2023-07-09T10:38:11.726+01:00\",\"id\":1},\"signedUrl\":\"/verification/john@test.com?signature=eyJtZXNzYWdlIjoiL3ZlcmlmaWNhdGlvbi9qb2huQHRlc3QuY29tIiwicHVycG9zZSI6ImVtYWlsIHZlcmlmaWNhdGlvbiJ9.-UyIPSjUUn1pWgBZiiEDVKjZ9gbxGsK1_BrkxCYs50g\"}],\"version\":\"v1\"}}') - Incorrect datetime value: '2023-07-09 10:38:11.915 +01:00' for column 'available_at' at row 1
    at Packet.asError (/Users/~/Workspace/adonis-background-job-demo/node_modules/mysql2/lib/packets/packet.js:728:17)
    at Query.execute (/Users/~/Workspace/adonis-background-job-demo/node_modules/mysql2/lib/commands/command.js:29:26)
    at Connection.handlePacket (/Users/~/Workspace/adonis-background-job-demo/node_modules/mysql2/lib/connection.js:497:34)
    at PacketParser.onPacket (/Users/~/Workspace/adonis-background-job-demo/node_modules/mysql2/lib/connection.js:97:12)
    at PacketParser.executeStart (/Users/~/Workspace/adonis-background-job-demo/node_modules/mysql2/lib/packet_parser.js:75:16)
    at Socket.<anonymous> (/Users/~/Workspace/adonis-background-job-demo/node_modules/mysql2/lib/connection.js:104:25)
    at Socket.emit (node:events:527:28)
    at addChunk (node:internal/streams/readable:315:12)
    at readableAddChunk (node:internal/streams/readable:289:9)
    at Socket.Readable.push (node:internal/streams/readable:228:10)
[ warn ]  Underlying HTTP server died with "1 code"

Referring to the segment: https://github.com/cavai-research/Adonis-Queue/blob/e9216df2cff3298888d2285248d06d5fabbd6175/src/Drivers/Database.ts#L15-L19
availableAt is directly assigned to the insert method without any further parsing.
If you are using Luxon DateTime, call toString() or toSQL() on the DateTime instance before assigning to availableAt.
If you are using native Date object, you can pass in the Date object directly or call toString() on the Date instance.
As an improve, I think the code can be improved so that availableAt expects a Luxon instance. cc @McSneaky

I think the available_at column is supposed to be set automatically at the point of calling dispatch().
From the look of things, availableAt is already a type of luxon https://github.com/cavai-research/Adonis-Queue/blob/e9216df2cff3298888d2285248d06d5fabbd6175/src/types.ts#L14

@ammezie this should be fixed in 2.0.4 https://github.com/cavai-research/Adonis-Queue/releases/tag/v2.0.4

authors: McSneaky ammezie ndianabasi

repo: cavai-research/Adonis-Queue


text:
🛑 Janax Soft is down

In c5c8303, Janax Soft (https://www.janaxsoftware.com.ar/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Janax Soft is back up in 7250e47.

repo: cavalicenti/upptime


text:
chore: bdd-nh-1585910218 to 0.0.1

chore: Promote bdd-nh-1585910218 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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


text:
use print-unreadable-object

I didnt know about this, looks useful. I can use it in all print-object definitions.
also read https://github.com/scymtym/utilities.print-items and see if it would be useful too.

Generalize the approach we used for stencil-params and see if that makes sense to use in more places

repo: cbaggers/cepl


text:
Not coloring when pLDDT is exactly on the borderline

Hi,
Thanks for this script! There is one issue that I found: when the value (rarely) is exactly 90, 70 or 50, the residue is not colored. Can you modify this by adding = -s to the right places?

That's a good catch, I noticed this too, it's unfortunate when this happens, as sometimes the pLDDT values match these exact numbers.
Instead of using the trick you mentioned (I'm not sure what = -s refers to), I have submitted a pull request with code modifications to address this issue. The updated script now includes these values and ensures they are colored appropriately.
Best

authors: NicoFrL gezmi

repo: cbalbin-bio/pymol-color-alphafold


text:
Make var and for loops compatible for Swift 3.0

Simple cleanup for the deprecation of var in function parameters and C-style for loops.

Looks like some good changes, I'll try it out this afternoon - thanks!

authors: cbpowell lucasderraugh

repo: cbpowell/MarqueeLabel-Swift


text:
增加计时器配置功能

现在计时器默认打开，无法设置，尤其是每次提交后还发消息通知，希望可以提供设置选项。

设置什么内容?

我其实只想要一个关闭的选项，至于其它设置我暂时没有想法。

设置什么内容?

我其实只想要一个关闭的选项，至于其它设置我暂时没有想法。

增加了 2.19.4

authors: WangDongYao ccagml

repo: ccagml/leetcode-extension


text:
Неверные тестовые данные account и secure

Использую тестовые данные account и secure.
Включаю $cdek->setTest(true);
Пытаюсь авторизоваться, получаю ошибку "Authentication is failed, please check your account and secure"
Начал дебажить, выяснилось, что sdk переписывает мои ключи на свои https://s.mail.ru/XZvy/hWYPggSa4

Соответственно авторизация не работает, так-как видимо эти ключи более не актуальны.
Если в файле, указанном на скриншоте, убрать этот код то авторизация начинает работать.
Может я что-то упустил или это бага?

Разобрался, нужно после setTest() установить свои ключи через setAccount() и setSecure(), тогда норм.


text:
Scope being overwritten

ID: 07bf0e3a-e2db-4887-b843-ef8b48b58934
Rule Id: CG0143
Prod Scope:
Scope:
  Classes:
    Include:
      - EVENTS
  Domains:
    Include:
      - DS

Generated Scope:
Scope:
  Classes:
    Include:
      - SPECIAL PURPOSE
  Domains:
    Include:
      - DM

Again, no properties should be overwritten. The merge should only do additions, not replaces. For this case, where the scopes don't match what is expected, this should appear in the merge log file for manual investigation.

This is what is in the rule definition:

CG0143
3.2
1
SPC
DM

CG0143
3.3
1
SPC
DM

CG0143
3.4
1
SPC
DM

Does this mean rule author can change the rule definition?

I have changed the code so that it will not overwritten if the scope is already created in the rule.

This is what is in the rule definition:
CG0143	3.2	1	SPC	DM
CG0143	3.3	1	SPC	DM
CG0143	3.4	1	SPC	DM
Does this mean rule author can change the rule definition?

Yes, the author can write the rule differently from what is in the spec verbatim and we want to see these cases in the logs.
In this example, the author correctly changed the scope because the rule condition is based on DS and references DM instead of the other way around.

authors: gerrycampion htu

repo: cdisc-org/crbuilder


text:
feat(deps): upgrade compiler dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-compiler-dependencies-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1429

Questions ?
Please refer to the Backport tool documentation


text:
chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2300

Questions ?
Please refer to the Backport tool documentation


text:
chore(deps): upgrade configuration

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-configuration-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2468

Questions ?
Please refer to the Backport tool documentation


text:
chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2487

Questions ?
Please refer to the Backport tool documentation


text:
feat(deps): upgrade compiler dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-compiler-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1425

Questions ?
Please refer to the Backport tool documentation


text:
chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-24-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1459

Questions ?
Please refer to the Backport tool documentation


text:
chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-23-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1593

Questions ?
Please refer to the Backport tool documentation


text:
metricFactory.createMetricSearch doesn't support empty dimension map

Feature scope
MetricFactory
Describe your suggested feature
Declaring CustomMetricGroup as following:
      {
        title: 'Test',
        metrics: [
          metricFactory.createMetricSearch(
            'query',
            { dummyDim: undefined as any as string },
            MetricStatistic.SUM,
          ) as MathExpression,
        ],
      },

Which generates a graph with following search query:
SEARCH('{test_namespace,dummyDim}  EligibleEvent', 'Sum', 60)

As far as I can tell, there is no way to omit the DimensionMap. When I emit the metric, I don't associate any dimension, so I need to associate a dummy dimension, which is a little hacky.
Nit: Also unrelated issue, createMetricSearch returns IMetric, which is incompatible with what the MonitoringFacade expects (Metric | MathExpression) resulting in me needing to cast the return into a MathExpression.
Related code snippet:
https://github.com/cdklabs/cdk-monitoring-constructs/blob/e7aa66bc3a051a46bc28d674f7e6bca6f4195a6a/lib/common/metric/MetricFactory.ts#L148-L185

Closing in favour of #599, which is more detailed.

authors: echeung-amzn jakeinater

repo: cdklabs/cdk-monitoring-constructs


text:
Add UI test/canary that exercises "typical flow"

Following discovery of the bug fixed in #630, it became clear we need automated UI testing around the whole user flow/journey, so that such issues don't go unnoticed in the future.

Interesting - so the bug in #630 wouldn't have been caught by an integration test (e.g. on PRs or as a check on our internal pipeline) because the change has to actually take affect in a newly generated package before it's noticed on the UI.
I wonder if something like a Cloudwatch Synthetics broken link checker canary would make sense here, since it could potentially catch any broken links on the website in the future (and could be a lot simpler to set up)?

So even with the above in mind, the Construct Hub should still run UI tests going through typical website user flows on a periodic basis. Running tests on pull requests or as deployment steps isn't enough since these tests can also fail due to changes in our backend data (like new packages, or backend reprocessing).
We should also try to reuse the tests we have already written with Cypress in construct-hub-webapp so that they can be used as a single source of truth. (Maybe we could add a  flag to enable or disable running the tests with fixture data)
Here's a couple of ways that I thought might achieve this:

Use Cypress Dashboard. This would make it easy to inspect test runs and inspect the tests, but I think it might provide a lot more features than we need for our use.
Use GitHub actions to run UI tests against constructs.dev on a routine basis (e.g. once an hour).
Create our own test canary that runs in AWS. It looks like this isn't practical with AWS Lambda at the moment (see https://github.com/cypress-io/cypress/issues/1232#issuecomment-885277518), but it is possible to do with AWS CodeBuild. This could be an interesting use case for a construct, perhaps?

Note: options 1 and 2 don't provide UI test canaries for private Construct Hub. But I think option 2 might be the easiest (at least as an interim solution).

Ah I just realized (2) probably is no good since the UI tests and our actual deployment of the website will be tied to different lifecycles. For example, we might update the integration tests along with a code change to the website, and then the tests will start failing until our actual website deployment change is live. We would also have less options for tracking and monitoring test metrics so... I guess (3) is the way to go.

What about CloudWatch Synthetics? This is supposedly what it's intended for...?

This issue requires some further discussion as we decide what features we want to provide for private Construct Hub, and how high priority this is, and how important it is to continue using our Cypress-based test suite.
If we want to have a UI canary running as a construct (within Construct Hub), then I believe the best path forward would be to have the Cypress test suite available at deployment time (so that the canary can run the tests corresponding to the deployed version of Construct Hub). This requires either taking construct-hub-webapp as a peer dependency, or separating the Cypress tests in construct-hub-webapp so they can be run in isolation and then bundled in the construct-hub NPM package. OR, this could be resolved by combining the repositories together so that construct-hub already includes all of the E2E testing code.
If this doesn't need to be a construct, we could consider how can we just run the E2E testing code in our internal pipeline. And if we don't want to use Cypress, then we would have to rewrite our tests with Puppeteer to work with CloudWatch Synthetics.
For now I've submitted https://github.com/cdklabs/construct-hub-webapp/pull/820 as a stop gap solution.

authors: Chriscbr RomainMuller

repo: cdklabs/construct-hub


text:
Patient-view and risks for inappropriate advice

Some key CDS-Hooks use cases include:

Show card based on FHIR data
Show multiple cards relate to the same FHIR/context data, possibly from different CDS-Services

This makes the following scenario's possible:

When the CDS-Client decides to update information a CDS Sever depends upon, an update to the resource(s) will be present in the scratch-patch of the CDS-Client/EMR.  Other cards are based on the old data and and no longer valid, they might even providing suggestions that can be potentially harm-full to the patient.
A Card is presented that provides a suggestion that solves an issue. The Suggestion is followed. Later, another change overrides that suggestion causing the original issue to re-appear. The current specification does not state the CDS-Service is recalled. It can also not access the information in the CDS-Client context. As a result, the practitioner cannot rely on the CDS-Service to provide guidance.

These scenario's both introduce significant and potentially dangerous situations. This raises the question of what use of the patient-view hook is justified that does not introduce these risks?
If none, we should not publish the hook.
If some, we should mention those, mention the risks and state that the patient-view SHALL not be used for such advice.
In practice this severely limits the use the patient-view.  Addressing these issues might very well requiring new testing. As a result, one could even wonder whether the required changes are compatible with a maturity-level of 4.....

Hey @bvdh,
At root - you're struggling to define how different CDS clients implement workflow and UI as it relates to the display of external CDS.
Should CDS Hooks really attempt to define this behavior? Our approach thus far has been to not prescribe cds client UI.
Would non-normative track recommendations for cds client behavior address your concerns?
Isaac

Bas,
Do note that we do try to call out a related risk already in the spec:

The risk that a CDS Service could return a decision based on outdated patient data, resulting in a safety risk to the patient.

https://cds-hooks.org/specification/1.0/#security-and-safety

Add documentation to note: For more information on patient safety issues see Security & Safety.

authors: brynrhodes bvdh isaacvetter

repo: cds-hooks/docs


text:
Exposure Status isn't persisted properly on iOS

What?
notificationSent: true supposes to be persisted after notification is sent for the first time. However, it isn't which causes notification is sent multiple times on iOS until user opens the app.

How to verify it?

See logs below on Sentry.
Navigate to newer / older log.
Scroll down to see additional data.

https://sentry.io/organizations/canadian-digital-service/issues/1782161356/events/b9283e991ea342ab8c063e9f5a4227f3/?project=5309250&query=cPK2&statsPeriod=14d
https://sentry.io/organizations/canadian-digital-service/issues/1782161356/events/985b9b12989643b0a552be045124b86f/?project=5309250&query=cPK2&statsPeriod=14d

^ Ignore my linked issue

I find that the app is crashing on this line:
https://github.com/cds-snc/covid-shield-mobile/blob/fabb21d772c3a3f633a12b625036ed4615046b30/src/services/ExposureNotificationService/ExposureNotificationService.ts#L155
With the following error:
Possible Unhandled Promise Rejection (id: 0):
Error: Observer: Error while trying propagating value [object Object], haven't finished propagation cycle for [object Object]
Error: Observer: Error while trying prpagating value [object Object], haven't finished propagation cycle for [object Object]
    at Subscriptions.propagate (http://192.168.0.164:8081/index.bundle?platform=ios&dev=true&minify=false:121555:17)
    at MapObservable.set (http://192.168.0.164:8081/index.bundle?platform=ios&dev=true&minify=false:121634:28)
    at MapObservable.append (http://192.168.0.164:8081/index.bundle?platform=ios&dev=true&minify=false:121660:14)
    at _callee2$ (http://192.168.0.164:8081/index.bundle?platform=ios&dev=true&minify=false:120416:51)
    at tryCatch (http://192.168.0.164:8081/index.bundle?platform=ios&dev=true&minify=false:30548:19)
    at Generator.invoke [as _invoke] (http://192.168.0.164:8081/index.bundle?platform=ios&dev=true&minify=false:30724:24)
    at Generator.prototype.<computed> [as next] (http://192.168.0.164:8081/index.bundle?platform=ios&dev=true&minify=false:30591:23)
    at tryCatch (http://192.168.0.164:8081/index.bundle?platform=ios&dev=true&minify=false:30548:19)
    at invoke (http://192.168.0.164:8081/index.bundle?platform=ios&dev=true&minify=false:30624:22)
    at http://192.168.0.164:8081/index.bundle?platform=ios&dev=true&minify=false:30654:13

authors: henrytao-me jeberhardt jeffmaher

repo: cds-snc/covid-shield-mobile


text:
Design changes: swap label for icons on the notice component

📇 User story
To maintain alignment with Canada.ca on a widely used and high impact component, the decision was made to switch from label only to using icons without labels for the notice type.
✅ Definition of Done / Outcomes
Notice component of all types are updated in Figma to use icons (from GCDS icons) instead of labels
📜 Acceptance criteria
Add here the list of assumed steps that will be needed to complete the task

[ ] Update EN Figma component and poster
[ ] Update FR Figma component and poster
[ ] Update component archive and decision record

📝 More info
https://docs.google.com/document/d/1V-cdbeSFPsyj7qj3fumj3RoK9MKIGJ6psd-KyRXfmYg/edit
. 🚫 Out of scope
Publishing of the Notice component will be done in tandem with the code PR

So work is done but we wont update the Figma poster until dev is done so we have consistency. Though the requirement doc with related decisions can be updated @realdylanzheng

@realdylanzheng Where can we see the updated design?

https://www.figma.com/design/Uq2iUvQPdgYwcQFh0xFzhH/Notice?node-id=23721-2461

authors: ClementineHahn SmartMouthWords adorayi

repo: cds-snc/design-gc-conception


text:
Revisit hierarchy styles

H4 is smaller than body text (see SOMCs)

In the interim, for soft launch, I'm hacking this by changing all the H4 in SOMC pages to H3.
However, we will need a more apt fix at some point soon.

Normal Body/Paragraph text is larger than H3, providing a skewed sense of structure/hierarchy.
For example:
Here "Example" is H3, and text is normal/body text

This appears to be resolved in staging.

repo: cds-snc/resources-ressources


text:
🛑 tanecni-divadlo.cz is down

In bf950c4, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 75560b5.

repo: cebreus/upptime


text:
🛑 tanecni-divadlo.cz is down

In 0e7961a, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 0aa7f0e.


text:
🛑 tanecni-divadlo.cz is down

In e1371f2, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 41c2825.


text:
🛑 tanecni-divadlo.cz is down

In cf3ad1c, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in b38583b.


text:
🛑 tanecni-divadlo.cz is down

In b9423e8, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in d6f1da1.


text:
🛑 tanecni-divadlo.cz is down

In 75f7750, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 522f2f2.


text:
🛑 tanecni-divadlo.cz is down

In bd3e1d6, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 0ab841e.


text:
🛑 tanecni-divadlo.cz is down

In 306a2eb, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 85303bc.


text:
🛑 tanecni-divadlo.cz is down

In 899833a, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 829653c.


text:
🛑 tanecni-divadlo.cz is down

In 2eccd07, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 22592fc.


text:
🛑 tanecni-divadlo.cz is down

In 2120ebd, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 96e5677.


text:
🛑 tanecni-divadlo.cz is down

In 8ff7931, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in df7ddc0.


text:
🛑 tanecni-divadlo.cz is down

In 0da8afb, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 910593a.


text:
🛑 tanecni-divadlo.cz is down

In f59db04, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in d0afe3b.


text:
🛑 CDN is down

In fc56d30, CDN (https://cdn.ceccun.com/cdynamic/captive) was down:

HTTP code: 522
Response time: 15423 ms

Resolved: CDN is back up in 976da61.

repo: ceccun/status


text:
🛑 CDN is down

In 96a92b1, CDN (https://cdn.ceccun.com/cdynamic/captive) was down:

HTTP code: 522
Response time: 15222 ms

Resolved: CDN is back up in d542b43.


text:
🛑 CDN is down

In 8f44bd3, CDN (https://cdn.ceccun.com/cdynamic/captive) was down:

HTTP code: 502
Response time: 481 ms

Resolved: CDN is back up in 39615fa.


text:
🛑 CDN is down

In eeb6acd, CDN (https://cdn.ceccun.com/cdynamic/captive) was down:

HTTP code: 525
Response time: 265 ms

Resolved: CDN is back up in 1f50512 after 55 minutes.


text:
CI does not run tests in CedarJavaFFI

Before opening, please confirm:

[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

Bug Category
Other
Describe the bug
CedarJavaFFI has its own tests, but the CI in this repo does not run them; as a result, they are broken on main as of this writing.  We should either modify the CI to run these tests, or remove the tests if we don't think they add value and prefer to have only the tests in CedarJava.
Expected behavior
main does not contain broken tests.
Reproduction steps

Checkout main
cd CedarJavaFFI
cargo test

Code Snippet
No response
Log output
No response
Additional configuration
No response
Operating  System
No response
Additional information and screenshots
No response

Somewhat related and probably could be addressed at the same time: CedarJava and/or CedarJavaFFI could use more tests for error paths, ensuring that various failure cases are properly reported across the FFI boundary (both sides agree on the structure of JSON for these error cases).

Closed by #128?

Yes

authors: cdisselkoen khieta

repo: cedar-policy/cedar-java


text:
Some optimizations to the validator proofs.

Issue #, if available: None, but related to #30
Description of changes: Some optimizations to the validator proofs. In combination with the overflow validation branch, these were needed to keep the proofs under the limit both at the command line and in VS Code on my system. But they are valid optimizations in their own right.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Note: partially addresses #35

authors: khieta mattmccutchen-amazon

repo: cedar-policy/cedar-spec


text:
ipv6?

In my testing I just tried ipv6, and I am unable to connect with either an ipv6 address (with or without[]) nor a hostname that resolves to ipv6 address only.

with wfreerdp I succeeded with [fe80::94b0:d277:5e17:9f2c] but not with an hostname (AAAA record).

https://github.com/FreeRDP/FreeRDP/issues/1949

Well, while reading this thread again, I just noticed something... you said your hostname resolves to ipv6 only; so, if there is an issue with ipv6, it's normal the connection doesn't work anyway.
But that doesn't explains why wfreerdp didn't worked either, so also check your DNS :p

I released the fix because, even if it doesn't address your issue, it fixes another. Please tell me if it's ok.

I now tried IP v6 with 2.1.2. I can now get it to run with [] notation, but not with a hostname that resolves to IPv6 only – as with wfreerdp. Any idea how to debug that? Is there a log or trace of freerdp communication?
Thanks, Joachim

Nice the ipv6 is working :)
Regarding the hostname, check your DNS configuration.  try running nslookup as explained in my previous post.
You can enable the myrtille logs into <myrtille>\bin\Myrtille.Services.exe.config (https://github.com/cedrozor/myrtille/blob/master/DOCUMENTATION.md#configuration--performance-tweaks--debug), RemoteSessionLog key; don't forget to restart the myrtille service.
Also look to the windows event logs (system and application), and search for anything related to DNS.

nslookup reports the expected ipv6 address.
I enabled logging, however the wfreerdp.*.log files are length 0 (except for the one where I tried [] notation). All other logs untouched. Nothing in the system and application event logs that I can attribute to that test.

myrtille server and hyper-v server are in the same domain, even the virtual machine is a clone of a domain member. (Btw, domain is not shown for VM Bus connections, nor security).
ping -6 with NetBIOS name does not work (not sure it should, https://msdn.microsoft.com/en-us/library/jj663161.aspx), neither does ping -6 with FQDN, whereas ping with the address returned by nslookup (which also succeeds) does.
With Myrtille I am using the exact same URLs except exchanging server=xx, and it works for everything except a name that resolves to ipv6 only. Thus I don´t think it is about security options or authentication.

Ah sorry, I thought you were connecting a standard rdp server (not an Hyper-V VM).
Yes, the domain is not shown for a VM bus connection because it applies to the user whose authentication is delegated to the VM. The security protocol is not shown either because it applies to a standard rdp connection.
I have to recheck the VM bus connection using a hostname for the (Hyper-V) server address. For my previouses tests, I entered the server IP or just left the field empty (equivalent to "localhost"), because both Myrtille and Hyper-V servers are on the same machine. And I don't think "localhost" even goes through the DNS lookup; as a loopback address, it must be translated directly to 127.0.0.1 or [::1].
The wfreerdp code to resolve the hostname for a VM bus connection may differ from the one used for a standard rdp connection (even if I doubt it because it relies on tcp in both cases, just with a different port).
Just for a try, could you enable remote desktop access on the VM then connect it with myrtille through a standard rdp connection with the VM hostname?

So I installed myrtille on another machine of the domain. The VM Bus connection, with the Hyper-V host as server, worked in all cases :

NETBIOS
NETBIOS.home
FQDN

There must be something with your config :/ what is the error message (dialog box) into the browser after the connection fails?

*.home does not resolve in my network, and I think it shouldn´t.
The message is the following:

I only need to change the server= part of the URL to use an ipv4 alias and it succeeds.
I´d be happy to figure out what´s wrong or different...

You said the hyperv server address resolves to ipv6 only and you use an ipv4 for the server param into the url? and why does it resolves to ipv6 only? did you disabled ipv4?
On the myrtille machine, you said the nslookup of your hyperv machine works (fe80::94b0:d277:5e17:9f2c) and you can ping that ip. Is it still working?
If the connection with [fe80::94b0:d277:5e17:9f2c] works (&server=%5Bfe80%3A%3A94b0%3Ad277%3A5e17%3A9f2c%5D into the url), it must be an DNS issue...
Sorry, I'm running out of ideas :/

My network is mostly ipv4 and at present only exposes ivp4 to the outside. Internally I have some aliases in my DNS that resolve to ipv6 only in order to test software explicitly with ipv6. In other words, the hyper-v server hast multiple ipv4 aliases and one ipv6 alias resolving to the exact ipv6 address I used for testing..
I do understand you are running out of ideas. Actually I think it is either a local issue or a freerdp issue (as I can reproduce it with that as well). If only diagnostics would be better.. likely I have to go the hard way and debug wfreerdp.

About diagnostics, there is something you could do. Open a console window and go into the myrtille bin folder. There enter the following command lines (obviously replacing path and values by yours):
SET WLOG_APPENDER=FILE
SET WLOG_FILEAPPENDER_OUTPUT_FILE_NAME=wfreerdp.log
SET WLOG_FILEAPPENDER_OUTPUT_FILE_PATH=absolute\path\to\wfreerdp.log
SET WLOG_LEVEL=TRACE

wfreerdp /u:user /p:password/ /v:hostname /cert-ignore /vmconnect:vmguid /log-level:TRACE

This will not only bypass myrtille, but also set logs to a more precise level.
Then check wfreerdp.log.

If you want to check it, this should guarantee at least something in the logs (not 0 sized) and probably the root of the problem...

finally had time to dig deeper...
https://stackoverflow.com/questions/10767107/getaddrinfo-cannot-resolve-ipv6-google-com-but-nslookup-can provided the right solution of Netsh interface teredo set state enterpriseclient.

Congratulations, it was deep digging! did the log helped or did you had to debug wfreerdp?

repo: cedrozor/myrtille


text:
chore: bump versions of app/sdk/core dependencies to latest

app  0.5.0
sdk 0.46
core 0.35.4

needed for successful testnet pairing with app
Resolves #733

Codecov Report

Merging #736 (69a82f9) into main (38a6a96) will increase coverage by 0.38%.
The diff coverage is 53.47%.

@@            Coverage Diff             @@
##             main     #736      +/-   ##
==========================================
+ Coverage   52.26%   52.65%   +0.38%
==========================================
  Files         103      114      +11
  Lines        6224     6526     +302
==========================================
+ Hits         3253     3436     +183
- Misses       2629     2731     +102
- Partials      342      359      +17

Impacted Files
Coverage Δ

core/client.go
100.00% <ø> (ø)

core/fetcher.go
51.78% <ø> (ø)

das/daser.go
73.20% <ø> (+2.61%)
:arrow_up:

fraud/bad_encoding.go
31.11% <ø> (ø)

fraud/proof.go
0.00% <ø> (ø)

header/dah.go
100.00% <ø> (ø)

header/header.go
46.03% <0.00%> (ø)

header/p2p/request.go
0.00% <0.00%> (ø)

header/p2p/serde.go
0.00% <0.00%> (ø)

header/serde.go
50.00% <ø> (ø)

... and 65 more

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 3dbc376...69a82f9. Read the comment docs.

Everything works now.

The only unit test failing in race is TestRemoteClient_StartBlockSubscription_And_GetBlock
This will be fixed on a separate PR to not overflow this one

The PR that fixes flakeness is prepared to be made after this one is merged

authors: Bidon15 Wondertan codecov-commenter

repo: celestiaorg/celestia-node


text:
Monitors hang at #close.

This seems to be in nio4r but I cannot see what changed, or trace it into that library completely. But this release of Celluloid::IO is dying intermittently, more often than surviving, within TCPSocket, in accept at wait_readable and in that, at the mailbox.reactor.wait_readable and finally in that, at monitor.close inside the ensure block ...
With MRI 2.2.1 this can be interrupted ( but failing obviously ) by SIGINT, but with rbx-2.5.8 this even prevents SIGINT and the rspec process needs SIGTERM to fully be killed. I think the thing that opens this a bit wider is that on jRuby 1.7.20 sending SIGINT does work, and reveals a suppressed STDERR message: Bad file descriptor ... this is in the case of failing at IO::SSLServer ...
But then it gets weirder... under jRuby the SSLServer test always passes, if run by itself. Under rbx-2.5.8 and MRI 2.2.1 it never passes, and dies inside the ensure block mentioned above.
In strace it hangs up at:

jRuby 1.7.20 ... futex(0x7fce8dbab9d0, FUTEX_WAIT, 18860, NULL)
rbx 2.5.8 ... futex(0x6a86a4, FUTEX_WAIT_PRIVATE, 25, NULL)
MRI 2.2.1 ... select(12, [11], NULL, NULL, NULL)

I can't figure out what changed yet. It's hard to bisect because changes out in Celluloid at earlier points break tests that succeeded in the past. Any ideas @tarcieri?

Correction: On MRI 2.2.1 it's actually hanging at Kernel.select([io]) hence the strace output.

I made some change to how TCPSocket works somewhere.

https://github.com/celluloid/celluloid-io/commit/3d3f10a467c7b900ab4fdec7dec11901fea6b4b4 but I think that actually fixes problems not creates them :/

Yeah, that's not it. I reverted that one line and it's still there. Plus, it was fine still as of a month after your change.

It really seems like the issue is outside Celluloid::IO

if you want heavy IO tests use celluloid-dns it does a crap load of IO in some of the tests.

I added a timeout to be able to see the already failing errors, and it's test clobbering each other's port. So I'm randomizing per-test. No idea how this "suddenly" started... you'd think it'd have been going on all along.

Yeah, I had some issues with tests running servers on the same port, I just gave each test it's own port.

I have it doing that now... and sometimes it will completely pass now. Sometimes. I wonder what changed, or if it's always been like this. The issue seems to be the ECONNREFUSED mystery error in ssl_socket_spec.rb

It's a miracle*
*Unlikely but inevitable
*An improbable given
GOT IT :shipit:

What was the bug

It was with the tests themselves, but it reveals an issue with SSL support that might come up. The server takes about 0.126 on CI to spin up. The method we were using didn't actually catch the spinup. There is a Thread.pass approach ( which I left there ) and it is noted in the test that it's probably responsible for ECONNREFUSED ... which it is. It caused this interplay between port assignment between tests, and inability to use the port once obtained, in the test that was failing. I changed the port assignment method to test if the port was actually available, then assign it... otherwise it picks another port ( up to N retries ) before it fails with EADDRINUSE but I inserted the number of retries into the error message. It was showing 45-70 retry attempts at times, and getting either EADDRINUSE or ECONNREFUSED ... that is, after I added a timeout wrapping all the tests in an around(:each) {} ...
The ultimate solution came down to inserting that sleep 0.222 right after an SSL server was instantiated in tests, just before the client tried to open a socket to it ( which is where the tests previously locked up ... because the test instance had both client and server on one process, and the thread was locking and if it wasn't locking, it was hitting a failure either for port assignment or connection refused because the server had not spun up ) ... it was only one issue, but it ended up taking a lot to find it.... even including strace

So the SSL socket has some kind of timeout/pause which is causing other tests to fail because the port isn't released?

It is both unreleased and then caused EADDRINUSE and unprepared, causing ECONNREFUSED ... without sleep 0.222 for now. I think we need to handle this in the ducktype itself, but for now I fixed the test. In general, SSL needs some attention.

I didn't change the ducktype because the test failure was not technically even using Celluloid::IO ... it was making sure it failed without Celluloid::IO

So its a bug in ruby itself? The SSL Server contractor returns before it's useable?

It seems so. In all Rubies tested. It is confusing as to how, because it is implemented differently in each Ruby, but ultimately the same result.

Or wait, Are the Server and Client in another thread? If so, you could use a condition variable or something to wait till you fire up the Client to connect to the Server.

Yeah, arbitrary values for sleep are a definite smell. I'd suggest doing what @Asmod4n and using actual thread synchronization.
I think I'd actually suggest something like a Queue with a timeout (so problems with tests don't indefinitely hang the test suite). The semantics of ConditionVariables are a bit tricky, as they're effectively level-triggered interrupts, and what you want here is edge-triggered, which is what a Queue provides. Unfortunately Ruby's built-in Queue does not have native timeout support, though ConditionVariable does.
I believe @mperham already wrote something like a QueueWithTimeout for Sidekiq tests. I think it'd be nice if Celluloid had something like that built-in.

https://github.com/mperham/connection_pool/blob/master/lib/connection_pool/timed_stack.rb#L29

I do think something like a native QueueWithTimeout in our test suite would be good. But I do also think using a Condition could be enough. The trouble in this case, is knowing when to signal the server is ready.

I'll check that out. Thanks @mperham

Where "connection" can be any ruby object, really.

authors: Asmod4n digitalextremist ioquatix mperham tarcieri

repo: celluloid/celluloid-io


text:
Celo:

Describe your issue here.
Environment

Elixir Version: 1.12.3

Erlang Version: 24

BlockScout Version: ce5c306361b0a24b2ad498857f8d763c666325aa

User Agent: Mozilla/5.0 (Linux; Android 11; SM-M315F) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.41 Mobile Safari/537.36

Steps to reproduce
Tell us how to reproduce this issue. If possible, push up a branch to your fork with a regression test we can run to reproduce locally.
Expected Behaviour
Tell us what should happen.
Actual Behaviour
Tell us what happens instead.

İyi günler ben tfbx çektim ama yanlışlıkla mexc erc20 adresi seçtim. Celo ağı seçmek lazım yardım ederseniz sevinirim

repo: celo-org/celo-monorepo


text:
Specify the encryption key in helm

Description
Specifies the encryption key as defined in https://github.com/celo-org/celo-blockchain/pull/365. For now we will actually just use the same key as consensus for simplicity.
Tested

[ ] Deployed on a testnet and saw that celo-blockchain correctly decrypted the message
[ ] Actually change the migration if we have a separate key

Related issues

Fixes https://github.com/celo-org/celo-blockchain/issues/321
Sister PR to https://github.com/celo-org/celo-blockchain/pull/365

Backwards compatibility

This change is not backwards compatible. When merging and deploying, the celo-blockchain docker image has to be updated, and the validator flag variable has to be adjusted

@nambrot - This is an old PR.  Is this still relevant and something we should take a look at, or can we close it?

authors: kevjue nambrot


text:
Patch #35

See https://github.com/cenkalti/rain/issues/35
I am not super sure if we need both mutex, because it is probably the same torrents that are stuffed in the 2 maps.

Pull Request Test Coverage Report for Build 1342988435

2 of 6 (33.33%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 45.309%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

torrent/session.go
0
2
0.0%

torrent/session_dht.go
0
2
0.0%

Totals

Change from base Build 1338450435:
0.03%

Covered Lines:
3303

Relevant Lines:
7290

💛  - Coveralls

I see that access to torrentsByInfoHash is already protected with mTorrents. I don't think putting another lock will make a difference.

It did get rid of the data race (that was triggered by a complex unit-test), so maybe there’s a place where mTorrents does not protect things.
I’ll try to get a better repro but I don’t know when I’ll get to this.

On Oct 30, 2021, at 4:04 PM, Cenk Altı @.***> wrote:
I see that access to torrentsByInfoHash is already protected with mTorrents. I don't think putting another lock will make a difference.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/cenkalti/rain/pull/36#issuecomment-955605635, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC2O6UOPZIWPYCDCJWEMQADUJR2YFANCNFSM5GAHIMTQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I don't see this bug anymore with latest master, closing.

authors: bsergean cenkalti coveralls

repo: cenkalti/rain