[config] config file location

error to locate config file if the binary is called outside the main directory

Fixed by #2

Fixed by #2


httpclient4.5.5 exception

httpclient 4.5.5
apache skywalking 5.0-beta2
error.log

@peng-yongsheng Issue shouldn't be set in the closed milestone.


history with multiple Worker Classes raise runtime error

When running more than one worker class, sidekiq-history raises NoMethodError: undefined method symbolize_keys' for nil:NilClass` when recording statistics.
lib/sidekiq/history/middleware.rb:50
To reproduce:

Execute jobs with SendEmailWorker one or more times
Executes jobs with SendTwitterWorker once
See 'SendTwitterWorker' fail, with the 'retries' tab in sidekiq-web, showing the error message NoMethodError: undefined method symbolize_keys' for nil:NilClass
if you execute workers with (backtrace: true), then the error is at lib/sidekiq/history/middleware.rb:50

Fixed this in #33

thanks!


⚠ Redacted has degraded performance

In b28f06c, Redacted ($RED) experienced degraded performance:

HTTP code: 200
Response time: 1092 ms

Resolved: Redacted performance has improved in 0b11473.


Create cybersecurity_questions.md.

add-cybersecurity-questions

Your submission does not follow the question template guideline. Please rectify.


Unable to generate reports with empty enhanced table [Kibana 7.5.0 - ET 1.6.0-1.8.0]

Hi there,
I'd like to highlight a possible bug which can cause quite some problems in a production environment. As described by the title, I've experienced a fail in the report when the enhanced tables happen to be empty (No results found). It doesn't happen with default tables.
Also, I want to specify I'm in a air-gapped environment (in fact, due to a Kibana issue in such an environment when it comes to make report, I had to specify newsfeed.enabled: false in the kibana.yml).
Steps to reproduce:

download brand-new tars of elasticsearch and kibana version 7.5.0, unzip it and launch elasticsearch.
install enhanced table on the kibana instance and launch kibana.
go to Management>Elasticsearch>License Management and activate the trial license (to unlock reporting features).
put a template on a given testing-index (needed only to ingest a document with a recognized date) and then ingest a document. You can do both from the Dev Tools this way

PUT _template/testing_template
{
  "order": 2,
  "index_patterns": [
    "testing*"
  ],
  "settings": {
    "index": {
      "number_of_shards": "1",
      "number_of_replicas": "0"
    }
  },
  "mappings": {
    "properties": {
      "date": {
        "type": "date"
      }
    }
  },
  "aliases": {}
}

PUT testing_index/_doc/1
{
  "foo": "bar",
  "date": "2020-03-11T06:00:00.000Z"
}

Make a index-pattern testing_index*.
Go to the Dashboard section, create a new Dashboard (e.g. testing dashboard), click on Add to add a visualization and create a enhanced table one like the following:

Once the visualization is added to the dashboard, set a timerange in the dashboard to visualize something in the enhanced table (so include the date of the document in your timerange).

Save the dashboard storing the time with it.

Try making a report from inside the Dashboard (once it is saved) by clicking on Share>PDF Reports>Generate PDV. You should see in the bottom right corner of the screen a green pop-up like the following that indicates the report has been queued:

After few moments you should be able to download the report from the Management>Kibana>Reporting section.

Now, try to edit your Dashboard, setting a timerange which DOES NOT include your document. You should see something like this:

Save the Dashboard (storing time again) and try to make another report.

In my case, the report fails because it reaches the maximum number of retries.
As already said, it doesn't happen with default tables (you can try following the above steps but with a classic Table visualization and it'll work).
Hope this can be sorted out soon since the reporting feature is kinda useful and utilised in prod environments and it can happen there are no data for a specific timerange. It would prevent someone from using this super useful visualization.
Thanks.

Hi,
I managed to reproduce your issue, and so, I confirm that there is a bug.
That said, I'm annoyed because I have no precise error, no log that can help me to understand why this issue happens...

Yeah, I know. That annoys me too.
Might it be linked to any kind of timeout that causes the report to fail? Maybe because it tries to load something for an undefined time, breaking the report.
I don't know really, but it prevents anybody from using this visualization anywhere where a report is needed.

Well, I'm as annoyed as you.
I would like to fix the issue.
But I have no idea what is the cause of this issue.

Hi,
I just published Enhanced Table v1.11.0! And it includes a fix of this bug.
More info on release here:
https://github.com/fbaligand/kibana-enhanced-table/releases/tag/v1.11.0

Hi,
I just published Enhanced Table v1.11.0! And it includes a fix of this bug.
More info on release here:
https://github.com/fbaligand/kibana-enhanced-table/releases/tag/v1.11.0


Change the default contact in the user-agent

Currently, the default contact in the user-agent is listed as <@WebSciDL>. As a result, upstream servers often think the requests are coming from WSDL research group. We need to change the default to something else.

@ibnesayeed I presume a placeholder would work best here, correct? Maybe "@Administrator", "MEMGATOR_ADMIN", "CHANGE_ME", or something of the like?

I am thinking of changing it to <@WebSciDL (Default)>. It has been really helpful to keep @WebSciDL there as we were approached (and came to know about) when service providers faced some issues from MemGator instances that we don't control.
To make it more obvious, we can perhaps print a warning when MemGator is run in the server mode without custom contact or user agent (or spoof flag).

What might be better is to simply keep @WebSciDL sans (default), check the condition of that exact string and only then print a warning.

That would work too. So we basically only need to add that warning mechanism and that's all.


Data Import (sfimport) Failure

Describe the bug
Import SF Data failed.  Through the Amplify application, it appears this is happening due to too many concurrent executions.  When running the Import directly through Step Functions it is failing due to SQL Setup failure
{
"resourceType": "lambda",
"resource": "invoke",
"error": "Lambda.Unknown",
"cause": "The cause could not be determined because Lambda did not return an error type. Returned payload: {"errorMessage":"2023-05-12T00:48:46.092Z bff4ec05-f64d-40e0-b25a-1e4b73d10fe7 Task timed out after 60.02 seconds"}"
}
To Reproduce
Steps to reproduce the behavior:

Go to Application in AWS Amplify
Click on Domain and Manage Data Lake
Enter RootKey
Go down to Latest Data Export and note the error
Run the sfimport directly from step functions and notice same error

Expected behavior
Expected that the application would pull the data into RDS
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

I do see the SQLSetup having a default timeout of 60 seconds and it's likely this, I'm guessing, that is causing the failure.  Is that something I can change after the DataLake is set up?  and is this something that can be modifying in the build script to prevent such a low timeout interval from having to be modified later?

The timeout you mentioned is configured for the Lambda functions. You can go to the said Lambda function on AWS console and update the timeout parameter under the Configuration tab.


Make components that receive or emit events use EventProducer and EventConsumer

These recently introduced abstractions are not used by the components that pre-date it, we should make sure all components that can use it do so.

I think the only bit missing is to make GraphQLServer be an EventConsumer<SchemaEvent>, a simple refactoring.


Question about point feature

when i debug with you code, found that there is no pts_voxel_encoder, thus there is no pts_feat of the output.
I can only found you use point surpervise the sdf in "sparse_points_sdf_supervised"?
So how do you use lidar input like your paper?

Thanks for your interest! We currently only release the code for image modality, and the complete code (for point modality and multi-modality) will be released soon.


Import subclasses in shell_plus implemented.

Coverage decreased (-0.6%) to 51.818% when pulling b07028534f975db6885af7b24b9b8016b23bc309 on domandinho:domandinho_issue#1158 into 3862a187e6b0427e9443e07932fe8e5d42e92419 on django-extensions:master.

thanks !!


Version 1.01.00 release

Pretty substantial changes have been made between 1.00 and 1.01. We should do a code review to look for any erroneous code that may have been left behind.

All tests completed. expected 'static' dashboard data stayed the same before/after tests. Approving PR.


4.0.3 Bug: Call to undefined method CodeIgniter\HTTP\RedirectResponse::withCookies()

Bug Description
The following exception is thrown when user tries to login in a myth-auth integrated project:
Call to undefined method CodeIgniter\HTTP\RedirectResponse::withCookies()
When the following is executed
return redirect()->to($redirectURL)->withCookies()->with('message', lang('Auth.loginSuccess'));
from VENDORPATH/myth/auth/src/Controllers/AuthController.php at line 99
CodeIgniter 4 version
4.0.3 release (non-dev)
Affected module(s)
CodeIgniter\HTTP\
Expected behavior
Please stop making breaking changes, and maintain framework stability across all minor versions, as we want to be able to use and support CI4, and not seek stability elsewhere.
Context

PHP version 7.3.x

It is not a breaking change. It a new feature to the core of CI. Since Myth:Auth is in beta, there is no promise of stability there and this breaking issue is better targeted at Myth:Auth :)  The notes on Myth:Auth do state that the latest version requires the develop branch of CI4 to work due to this.
Luckily 4.0.4 is expected to drop tonight with that fix in it, with a new release of Myth:Auth right around the corner.


Fix the typo of BookKeeper, missing k/K

Motivation
There are several typo of BookKeeper, missing k/K
Documentation
Check the box below and label this PR (if you have committer privilege).
Need to update docs?

[x] doc
This PR contains doc typo change.

/pulsarbot run-failure-checks

Doc changes LGTM

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

merge the failure test from master

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks


[incubator/cloudwatch-agent] Add the helm chart for installing AWS CloudWatch Agent to Kubernetes cluster

Signed-off-by: Sergey Vasilyev<EMAIL_ADDRESS>Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
Setting Up Container Insights on Amazon EKS and Kubernetes
Description
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/ok-to-test

/retest

Hello @viglesiasce @unguiculus
Could you please review my PR?

@s2504s
Pinged in kubernetes slack channel #charts .

Thanks for creating this chart! I just pulled this in and started using it in our cluster. Only issue I'm seeing is that configurable parameters aren't injected into the cwagent-configmap.yaml as they should be.

Hi 👋 new charts are no longer accepted to stable or incubator. See Status of the Project and Deprecation Timeline for more info about that.
Good news is you can host a Helm chart yourself on GitHub, use the same tools as this repo does for automatic Chart testing and releasing, and list your Helm repo on https://helm.hub.sh. Follow this issue for info about existing guidelines and upcoming improvements: https://github.com/helm/charts/issues/7800

PS this chart looks nice 😄 Hope to see it on the Hub. Let us know in Slack if you need any help


Post score not correctly updated on flood of vote requests

For the seeder script in our Docker setup I have it create some entities automatically. One thing I've recently looked into is making some API requests in parallel. When doing this for the like/vote requests on a post, I noticed that the post score doesn't end up matching reality.
For example, I create 20 different +1 votes(from different users) on a single post. I do this by sending 20 API requests towards POST /api/v3/post/like at the same time.
I can then retrieve all 20 vote entities using the GET /api/v3/post/like/list route. But when I retrieve the post itself, either via GET /api/v3/post or GET /api/v3/post/list, its score will be less than 20. Usually in the range of 7-10.
I only see this issue when sending multiple requests all at once. It works fine if I make each vote request sequentially.

This is a issue with the delay created by:

The post/list endpoint returns aggregated data, and this is aggregated through events
The ORM isnt saving it immediatly to the db, it only "merges" it to the cache ( BUT this should be reflecting directly to the aggregated data )


Set max incoming connections

I think that backlog != maxconnection, can you write a simple unit test to check it ? But I may be wrong.

@NicolasDorier how about this?
I wasn't sure how FindOrConnect should handle the max limit though.

@dangershony I am not sure FindOrConnect make sense at all.
Find without connection would.
I think you can close the connection even before processing any message, in the socket Accept loop.

Yeah its odd as that would create an outbound connection and the list should only have inbound,
I will change it no problem.
I was thinking on closing the connection earlier that means I'll have to call the method Utils.SafeCloseSocket(Socket) rather then the standard Node functionality

it seems FindOrConnect is used for testing so I will ignore it for now, unless it has a production purpose.

Can you also bump the nuget build?

do when going back home tomorrow

Thanks I will update the fullnode


Fix validation

Try the branch of ci-feedstock-setup

@conda-forge-admin rerender

@conda-forge-admin rerender


Add documentation about re-exporting modules as a namespace

We hit this when trying to compile code for a webpage that had packages loaded into global variables. It took us days to find out the solution and it caused tons and tons of stress. The docs really need to be clearer about this.
-Emily

@microsoft-github-policy-service agree

wtf? after making this PR I just randomly got an email in Chinese from some random website claiming to be MurphySec (but they were not murphysec.com). I guess I got picked up by some spambots

Thank you for your recent pull request for documentation! We appreciate your time and effort in submitting your work for review.
This seems to be a workaround for a bug in the typings of an external dependency, and has its own caveats that would need to be spelled out, but may be too niche of a topic for these reference pages. We would always encourage users who encounter buggy dependency typings to file an issue or PR with the library / DefinitelyTyped typings rather than implement a workaround like this.

This seems to be a workaround for a bug in the typings of an external dependency

It's... not? There's nothing wrong with the library's typings. It's just the the typings are ES6 modules and this is being used in the browser through a global variable. This isn't a workaround for anything, this is literally just declaring the existence of a global variable that contains a library. It could be any library and any variable name, and it's not the library's job to declare itself a global variable if it's not normally used in a browser.

We would always encourage users who encounter buggy dependency typings to file an issue or PR with the library / DefinitelyTyped typings rather than implement a workaround like this.

The dependency typings are perfectly fine and this is not a workaround for anything. Again this is just declaring a global variable that contains a library. This is a useful feature for compiling TypeScript for environments that already have global modules, and the fact that it's not easily discoverable by developers is a big problem.


Fix broken link

Related issues (optional)
Closes #7937 .

Deploy preview for docsdocker ready!
Built with commit 8a04e93d0d7ff5f575864a9c8dce282206a664a0
https://deploy-preview-7943--docsdocker.netlify.com


chore(deps-dev): bump tsd from 0.11.0 to 0.14.0

I made the PR fail on purpose: it turns out you need to remove ts-expect-error in tsd tests with more recent versions of tsd. It makes sense: tsd uses TS diagnostics to know if there is an error or not. As older tsd versions used a TS version that did not understand ts-expect-error there was no issue. Now that tsd does use a TS version supporting this comment, the tests started to fail. The following commit fixes the tests.

I made the PR fail on purpose: it turns out you need to remove ts-expect-error in tsd tests with more recent versions of tsd. It makes sense: tsd uses TS diagnostics to know if there is an error or not. As older tsd versions used a TS version that did not understand ts-expect-error there was no issue. Now that tsd does use a TS version supporting this comment, the tests started to fail. The following commit fixes the tests.


Access token cookie is not replaced!

Hello,
I have a problem:
const cookies = new Cookies();

I set initial cookie like this: cookies.set("accessToken", initialAccessToken, { secure: true, });
After generating a new access token I use the same: cookies.set("accessToken", newAccessToken, { secure: true, });

The problem is: it duplicates. I can see 2 cookies "accessToken". What do I do wrong? Thank you in advance.

iam facing the same problem when i refresh the page for some reason the cookies duplicates, and when try to using remove('cookie') the target cookie not removed from the browser. but when i refresh the browser the target cookie that intent to remove, duplicates.
i am using vue 3

Seems to have to do with the path option when a cookie is set. When you call setCookie(), the cookie will be set with the current path. If you try to set the same cookie at a different path, it will create a duplicate.
I solved this for myself by setting the path option in setCookie to be /.
e.g.
setCookie('team', teamId, { path: '/' });

It would be nice to have an option on the cookie provider to set a default path instead of taking the current path.

@AllenWilliamson I agree it would be nice. A default set options will be added in v6.


Adjust OpenBMC PowerOff and global SniffTest

In early OpenBMC targets, we were told to issue both immediate (chassis)
as well as soft (host) poweroff in our sys_power_off() path. This is no
longer the recommendation, so adjust to be consistent with IPMI and LPAR
methods that issue an immediate power off.
Additionally, we're also been told that 30 seconds might not be enough
even for an immediate PowerOff in some (upcoming?) systems, so adjust
the SniffTest logic so we wait_for_standby() before issuing a PowerOn.
This should fix some CI scenarios where the BMC was executing a soft
power off (even if we're issuing both immediate and soft) and the 30
second delay was not sufficient before we could issue a poweron -
intermintently failing the test.
Signed-off-by: Klaus Heinrich Kiwi<EMAIL_ADDRESS>

retest this please


fix(helm): Add ClusterOriginIssuers to approver ClusterRole

cert-manager was unable to process the Approval action of a certificate when using ClusterOriginIssuer, the pod was showing:
 1 conditions.go:263] Setting lastTransitionTime for CertificateRequest "test-tls-1" condition "Approved" to 2024-07-10 08:57:28.083240782 +0000 UTC m=+600872.378883246
E0710 08:57:28.093648       1 controller.go:162] "re-queuing item due to error processing" err="admission webhook \"webhook.cert-manager.io\" denied the request: status.conditions: Forbidden: user \"system:serviceaccount:cert-manager:cert-manager\" does not have permissions to set approved/denied conditions for issuer {cf-cluster-origin-issuer ClusterOriginIssuer cert-manager.k8s.cloudflare.com}" logger="cert-manager.controller" key="my-site/test-tls-1"

Turns out the ClusterRole manifest in the helm chart was missing the clusteroriginissuers.cert-manager.k8s.cloudflare.com/* resourceName, adding it fixed the issue.

You'll need to bump the chart version too.

good call, done!

dankjewel!


websitesvoorgratis.nlofficieleskype not contactable on skype

smh, the brandweer (de echte) needs to contact websitesvoorgratis.nl

SKYPE STILL EXISTS?!?!?!??!?!?!??!?!?!?
i picked an absurdly long username with a dot (which from what i could tell is an illegal character) so it wont be claimed by anyone else if skype was still up (didnt wanna make the same mistake as VPRO hahaha)

It does!! :D

SKYPE STILL EXISTS?!?!?!??!?!?!??!?!?!?
i picked an absurdly long username with a dot (which from what i could tell is an illegal character) so it wont be claimed by anyone else if skype was still up (didnt wanna make the same mistake as VPRO hahaha)

A dot has never been an illegal character on Skype


Added second ICA and ica-label functionality

Closes #5 !
I amended the default YAML config file, and run_ica to allow for differences in ica_kwargs between run1 and run2.
By default, ica1 will use fastica for efficiency, since the purpose of ica1 is only to flag outlying ic timecourses.
By default, ica2 will use extended infomax, as this is the default that mne-icalabel recommends.
I also added ica-label funcionality, ic_labels are now stored in self.ic_labels.
I request a review from @christian-oreilly !

I added one more commit here because it relates to the ICA: 61d9d6f
The pipeline will now save the fitted ICA instances (as .fif files), and the IC labels (into a .tsv sidecar file).

Thus, the EEG visualizer will be able to load in the saved ICA and labels and plot them - So this is a timely addition since we are almost ready to start working on those plots.
I am going save a lossless derivative into the eeg-visualizer repo so that we can access the raw, ICA, IC labels for the dash development.


[DX] Resolvers chains working by default

Is your feature request related to a problem? Please describe.
The way this plugin generates codes naturally makes users do resolvers chaining. This is a standard GraphQL practice documented by Apollo Docs > Server > Resolvers > Resolver Chains.
When using this plugin for the first time, it was unexpected to me that this wasn't supported by default. I spent few hours trying to look for a solution.
Describe the solution you'd like
Enable support for resolver chaining by making this config default. We can also just update readme of this plugin and this guide: https://the-guild.dev/graphql/codegen/docs/guides/graphql-server-apollo-yoga-with-server-preset
const config: CodegenConfig = {
  schema: '**/schema.graphql',
  generates: {
    'src/schema': defineConfig({
      typesPluginsConfig: {
        /* This is required for resolvers chaining */
        useIndexSignature: true,
        defaultMapper: 'Partial<{T}>',
      }
    })
  }
}

Additional context

https://github.com/dotansimha/graphql-code-generator/issues/3828
https://the-guild.dev/graphql/codegen/plugins/typescript/typescript-resolvers#integration-with-apollo-server

if you are using resolver chains then you will need nested partials using utility-types https://the-guild.dev/graphql/codegen/plugins/typescript/typescript-resolvers#allow-deep-partial-with-utility-types
const config: CodegenConfig = {
 schema: "**/schema.graphql",
 generates: {
  "src/schema": defineConfig({
   add: {
    "./types.generated.ts": {
     content: "import type { DeepPartial } from 'utility-types';",
    },
   },
   typesPluginsConfig: {
    defaultMapper: "DeepPartial<{T}>",
   },
  }),
 },
};

Hello 👋  Thanks for creating this issue. I think there's definitely something we can work out to make the usage clearer. 🙂
For context, this plugin is created to have first-class support the mappers way enabling resolver chaining for the following benefits:
1. Predictability and runtime safety when using a mapper - or not
By default, codegen matches resolver's TS types with GraphQL field output type. This eliminates the chance where someone forgets to return null into a non-nullable GraphQL field - which is possible with Partial or DeepPartial - and cause a runtime error. On the other hand:

By using mappers, we explicitly tell codegen which value we don't want to return in a resolver, shifting the responsibilities to the following resolvers.
And by using this plugin, it automatically creates chaining resolvers at the leaf node if there could be runtime error e.g. nullable value being returned into a non-nullable GraphQL field, mismatched types, etc.

2. Consistent baseline object when multiple resolvers return the same type
Consider the following schema:
type Cat {
  owner: Person!
}

type Dog {
  owner: Person!
}

type Person {
  id: ID!
  name: String!
}

With Partial or DeepPartial, it's easy to accidentally return the inconsistent Person object in Cat.owner and Dog.owner resolvers, making it much easier to hit runtime errors, especially in bigger apps e.g.
const resolvers: Resolvers = {
  Cat: {
    owner: () => ({ id: "100" }) // 👈 object with only `id` can be return here, because `Person` is partial. This will result in runtime error.
  }
  Dog: {
    owner: () => ({ name: "Bart" }) // 👈 object with only `name` can be return here, because `Person` is partial. This will result in runtime error.
  }
}

On the other hand, Person resolvers wouldn't know what's being passed in, making it hard to code and may cause runtime errors:
const resolvers: Resolvers = {
  // Same Cat/Dog resolvers as before
  Person: {
    id: ({ id }) => id // 👈 This will trigger type error because `id` is nullable from using `Partial`
    // 👈 No `name` resolver... which means it'd error if clients query for `Cat.owner` because `Person.name` is non-nullable in the Graph, but we don't handle the nullable case
  }
}

For these reasons, Partial and DeepPartial mappers is supported via your mentioned config options, but not by default for this plugin. I'll add some notes to the guides to clarify the reasoning 🙂

For context, here's the file convention of using mappers when using this plugin: https://the-guild.dev/graphql/codegen/docs/guides/graphql-server-apollo-yoga-with-server-preset#adding-mappers

Hi @arjunyel , sure!
I've set up a small GraphQL server with some mocked data here: https://github.com/eddeee888/graphql-server-template
Let's look at the related part of the schema extracted from that repo:
# book/schema.graphql
type Book {
  id: ID!
  isbn: String!
}

# user/schema.graphql
extend type Query {
  user(id: ID!): User
}
type User {
  id: ID!
  fullName: String!
  booksRead: [Book!]!
}

In Query.user resolver, we don't want to implement with booksRead as we want to let User.booksRead handle that logic.

Here's how we can do with this preset:

Declare a User mapper in user/schema.mapper.ts. This mapper is the minimal shape that can be used to resolve any User fields:

// user/schema.mappers.ts

// Preset detects a mapper by the type name `User` (GraphQL type) + `Mapper` (The customisable suffix)
export type UserMapper = {
  id: string;
  firstName: string;
  lastName: string;
};

What this means is we can now pass this mapper object into any resolver that is supposed to return a GraphQL User node. Our Query.user may look something like this:
// user/resolvers/Query/user.ts
export const user: NonNullable<QueryResolvers["user"]> = async (
  _parent,
  { id },
  { data },
) => {
  // We must now return a consistent `UserMapper` into GraphQL `User` node
  // Without the UserMapper, we must return `{ id: string, fullName: string, booksRead: Book[] }`
  return {
    id: "1",
    firstName: "Bart",
    lastName: "Simpson"
  }
};

And we can resolve User.booksRead like this:
// user/resolvers/User.ts
export const User: UserResolvers = {
  booksRead: (parent, __, { data }) => { // `parent` is `UserMapper`
    /* Do booksRead resolver logic here*/
  },
  fullName: (parent) => {
    //👇 Server preset would generate `User.fullName` resolver and tell us _why_ we this is generated
    /* User.fullName resolver is required because User.fullName exists but UserMapper.fullName does not */
    return `${parent.firstName} ${parent.lastName}`;
  },
};

You can find the full example in the mentioned repo with these main files:

book schema
user schema
user mapper
Query.user returning a user mapper
User resolver chaining

Let me know if this doesn't answer your question @arjunyel ! Happy to chat more.
If we are happy with this discussion, I'll close this issue in 3 days and update the docs

@eddeee888 makes total sense, you are the biggest legend in history!


If your safe is full and you are prompted to safeguard a card, it goes into an infinite loop

https://boardgamearena.com/bug?id=92755

https://boardgamearena.com/bug?id=92906


castlabs electron version is missing the typescript .d.ts file

Run a standard electron-quick-start app, and npm install it.
Look inside node_modules/electron
notice the electron.d.ts file.
Removing this makes it significantly harder to "plug and play" the swap out of electron, as now my app will not compile into javascript.

Good catch, thanks for reporting it.
This is simply an oversight on our part. I'll make sure it gets fixed.

The release has been updated and now electron.d.ts is part of the install.


Preparing 1.1.4 release

Codecov Report

Merging #2347 into 1.1.x will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##            1.1.x    #2347   +/-   ##
=======================================
  Coverage   79.54%   79.54%
=======================================
  Files          85       85
  Lines        8897     8897
  Branches     1901     1901
=======================================
  Hits         7077     7077
  Misses       1558     1558
  Partials      262      262

Impacted Files
Coverage Δ

webapp/graphite/settings.py
77.38% <100%> (ø)
:arrow_up:

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 40dcdf2...ad66037. Read the comment docs.


Proper API reference

Does this thing have a proper API reference like this one:
https://github.com/kriskowal/q/wiki/API-Reference ?
I am looking at connection.rollback in the examples on the main page but don't know exactly when its callback argument is called.

The only documentation in the README. It would be awesome if you could contribute something you feel is a proper API reference or at least help us understand how we can improve the current docs such that you feel it is a proper API reference.

I'm going to close since I haven't heard back.


[#160582942] Enable dotnet-core buildpack

What
We didn't think we had the capability to support dotnet-core as a
buildpack, but for various reasons we don't think this decision is
valid anymore. The reasons include but are not limited to:

the team now has more dotnet experienced people
we can't stop people using custom buildpacks anyway
our users want it
it seems to be stable

How to review

Code review
See green pipeline
Log into api.towers.dev.cloudpipeline.digital and push an app

Who can review
Not me

LGTM


Asynchronously handle fragalysis upload?

Currently, uploading all the data to fragalysis takes something like an hour when protein snapshots are uploaded.
We should find a way to either avoid this or offload it to a separate thread/process.

Have we tried adding max_concurrent_requests in ~/.aws/config for the uploading user? Adding:
s3 =
    max_concurrent_requests = 100

would increase the number of concurrent requests aws s3 {cp,sync,mv,rm} can utilize from the default of 10 to 100.

Otherwise, if it's preferable for upload to be part of the CLI, then we can add an entry point such as upload_artifacts that uses boto3 internally to threadpool/processpool out these calls in Python. This may be the more integrative approach for an end-to-end workflow.

Great idea! I'll add this to the local ~/.aws/config for now, but it would be great to integrate this upload into the codebase long-term.

Understood, we'll pursue upload as part of the fah-xchem CLI. Thanks John!


Fix code scanning alert - Assignments to innerHTML/[o...

Tracking issue for:

[x] https://github.com/webrtc-org/samples/security/code-scanning/1

https://gist.github.com/gilbertalgordo


Improve test coverage

Coverage increased (+8.8%) to 73.76% when pulling 7424089f950b5d44ebcdb378201a428abd0265a9 on improve-test-coverage into c90849fcb29fbc498b3d59ff54e7893df8b65d91 on master.

Coverage increased (+9.8%) to 74.798% when pulling 9baff792ff5ed3f6f91787e6755eacd456caf8ed on improve-test-coverage into c90849fcb29fbc498b3d59ff54e7893df8b65d91 on master.

Coverage increased (+10.3%) to 75.288% when pulling ca7c6a6199061b0d9a091aa5685384df1376d50f on improve-test-coverage into c90849fcb29fbc498b3d59ff54e7893df8b65d91 on master.

Coverage increased (+14.9%) to 79.901% when pulling 8b133a79a16c4505edbf3e164ab4fdacb6adc518 on improve-test-coverage into c90849fcb29fbc498b3d59ff54e7893df8b65d91 on master.

Coverage increased (+16.4%) to 81.384% when pulling 91f493ef3ee1c7d327f306a581262aa205544e9a on improve-test-coverage into c90849fcb29fbc498b3d59ff54e7893df8b65d91 on master.

Coverage increased (+17.2%) to 82.208% when pulling dbcbe546d1614718ab7eb434a0e34f8fb146a1e5 on improve-test-coverage into c90849fcb29fbc498b3d59ff54e7893df8b65d91 on master.

Coverage increased (+17.4%) to 82.372% when pulling 46be8b48dc924526de9449e1c118c356034a5a24 on improve-test-coverage into c90849fcb29fbc498b3d59ff54e7893df8b65d91 on master.


Missing SYSTEM_TIME property in default_api_template.xml file

Description
We have enabled the default API by using the below confirmations.
[apim.global_handlers.properties]
skip_default_api_handler = true

Then we collected correlation logs after invoking a default API URL.
Example:

Version API URL: /newapi/v1/test
Default APO URL: /newapi/test

When we invoke the default API instead of the Version API, in the correlation logs we can see the HTTP log line as below.
2023-01-30 11:06:19,883|71c3e1b8-0bfb-41d7-b4fe-afa20f36153e|PassThroughMessageProcessor-13|**1675056979835**|HTTP|admin--testapi|GET|/testapi/*|testapi|Bearer eyJ4NXQiOiJNell4TW1Ga....

As you can see, instead of time in milliseconds it will print the timestamp. It was identified that this is happening due to a missing property in synapse configurations.
Steps to Reproduce

Add the below configuration and start the APIM server.

[apim.global_handlers.properties]
skip_default_api_handler = true

Create a versioned API.
Enable correlation logs.
Invoke the API and collect logs.

Affected Component
APIM
Version
3.2.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response

Closing since this issue is not reproducible in the master branch.


If harp is not installed, it does not raise any errors

It would be nice to raise an error or something, because I just skipped that part and didn't know why it was not working :)

Hey @gabrielpugliese-luizalabs ! By skipped, what do you mean exactly? You have used the Start.app or the manual installation process?
Thanks!

It's the manual process. I haven't noticed that there is an Start.app command (haven't found it yet - where is it located?)

What is your operating system, windows?
On Monday, August 10, 2015, gabrielpugliese-luizalabs <
<EMAIL_ADDRESS>wrote:

It's the manual process. I haven't noticed that there is an Start.app
command (haven't found it yet - where is it located?)
—
Reply to this email directly or view it on GitHub
https://github.com/hugeinc/styleguide/issues/32#issuecomment-129637835.

Ubuntu 14.04

Ok! Nice, can you just write your steps so I can reproduce?
Something like:

I installed this..
And then did this command..

Etc. And I will add a error message for missing dependencies when starting the server.

Ok

I've downloaded the bundle and unzipped
cd styleguide/structure/_node-files && npm install
node watch.js

The progress is 100% but nothing is being served because harpjs is not installed.

I would add a command before 2. in the steps like: npm install -g harp and also check if harp is installed on the startup of watch.js

Perfect, I'll do that and it will be release on version 2.0.5.
Thank you!

:rocket:

Closed on develop, soon to be merged.
https://github.com/hugeinc/styleguide/blob/develop/styleguide/structure/_node-files/watch.js


Rename support for tile entities in the storage scanner

https://goo.gl/1M9CCV
I would like to be able to rename these storage's for instance the item router at the bottom I use to put patterns into my refined storage crafter's so it would be nice to rename it for convenience sake.

that would be pretty nice. i have multiple modular storages with item filters. mostly filtered per mod. if i could rename them. e.g. one storage module for rftools, one for enderio,... to have a nice list in the storage scanner.


Move Any support out of ProtobufMessage

A minor nit, but the support for parsing/serializing Any (that is, google.protobuf.Any, not Swift Any) messages ought to be moved out of the core ProtobufMessage protocol and into a separate extension that contains that and other Any-related functionality.

@allevato - Should this get rolled in with #13? Does it need to happy by the 1.0 release?

This was originally just about code organization, but I'd need to take a closer look to see if moving Any support into an extension of ProtobufMessage would cause problems (the implementations become non-overridable, so if any of the specific message types customize them, that wouldn't work anymore).
It's probably fine to leave out of 1.0, given the priorities of everything else.

Oops, we had another bug for this also, but ti seems to be done now.


Request: an easy way to re-establish an Observatory connection to a running app

It's easy for an android app to get killed when the device runs out of memory, etc. When the app is brought back up (e.g. when the user taps the app launcher icon again), it creates a new observatory port. Unfortunately, it's difficult to re-establish the connection unless you know about adb logcat and adb forward. During profiling and debugging, it's all about Observatory and so when the Observatory connection dies, my profiling workflow dies.
I was doing a full flutter run --profile but that's a slow process to run if all I'm trying to do is bring back Observatory.
May I suggest we offer something like a flutter connect command that finds the running Flutter app on the device/emulator and does any port forwarding/mapping business.
That would be a YUGE time saver as we're profiling our Flutter apps.
Thanks!

cc @devoncarew thoughts?

In the meantime, here's what you can do:

restart your Flutter app
run adb logcat | grep Observatory
find the last "Observatory listening on ..."
copy the last port number (e.g. :44324)
Control-C
run adb forward tcp:44324 tcp:44324
Open your browser
go to <IP_ADDRESS>:44324

cc @johnmccutchan

@jason-simmons did some work to discover running apps on a device and forward their ports. That's exposed through the daemon protocol but not through the CLI.
That said, it sounds like the launching and re-launching apps w/ flutter run --profile was slow. Just making a null build for it fast would solve the use-case of the app closing while profiling.

launching and re-launching apps w/ flutter run --profile was slow.

This is true. Especially if nothing has changed.
If flutter run --profile was crazy fast when nothing has changed (essentially: start the app on my phone and forward ports) then yes, that would solve the use case.

Related: https://github.com/flutter/flutter/issues/5112

Closing as https://github.com/flutter/flutter/issues/23687 is more specific


Possible typo in feature macro

I've been reading the source code to get an insight on the engine's internals and noticed a unique typo in a feature macro. Running a global search on the repo, it appears consistently across all files it's used in so it's mostly harmless, but a possible source of bugs in the future if someone tries to fix it, or if an end-user wants to disable it for some reason.
It appears as: JERRY_PROPRETY_HASHMAP
It should be: JERRY_PROPERTY_HASHMAP
It appears in 14 files, mostly in /ecma/base. No files reference the correct spelling, so it won't have affected functionality up to this point.

Hi @ConsciousCode! Thanks for the report, indeed that's a typo. Feel free to open a PR with the renaming if you would like to contribute to the project.


Bus error in 30-test_evp.t (alignment issue on Solaris Sparc 32 Bit)

I get a bus erro when running 30-test_evp.t for OpenSSL 1.0.1e on Solaris Sparc 32 Bit.
gdb tells me:
Program terminated with signal 10, Bus error.
#0  CRYPTO_ocb128_aad (ctx=ctx@entry=0x3d238, aad=aad@entry=0x3d304 "", len=len@entry=16) at crypto/modes/ocb128.c:297
297             ocb_block16_xor(&ctx->offset_aad, aad_block, &tmp1);
and the stack is:
#0  CRYPTO_ocb128_aad (ctx=ctx@entry=0x3d238, aad=aad@entry=0x3d304 "", len=len@entry=16) at crypto/modes/ocb128.c:297
lookup =
aad_block = 0x3d304
i = 1
all_num_blocks = 1
num_blocks = 1
last_len =
tmp1 = {a = {289644378304612875,<PHONE_NUMBER>880525503}, c = "\004\005\006\a\b\t\n\vC▒\021I\214\005\202▒"}
tmp2 = {a = {11092886392772803782,<PHONE_NUMBER>3994026278}, c = "\231▒▒f▒▒Ƣ▒X▒\211\207=&"}
#1  0xff2a0c90 in aes_ocb_cipher (ctx=0x2cbe8, out=0x0, in=0x3ca30 "", len=0) at crypto/evp/e_aes.c:2599
remaining = 1
buf = 0x3d304 ""
buf_len = 0x3d318
written_len = 0
trailing_len =
octx = 0x3d040
...
Looking at aad_block, the address 0x3d304 is not aligned correctly for the 64 bit data type use in ocb_block16_xor().
This goes back to buf in crypto/evp/e_aes.c, which in turn shares alignment with &octx->aad_buf. It loks like the layout of EVP_AES_OCB_CTX does not make sure that its member aad_buf is 8 byte aligned.
A short check of master suggests the same problem will happen there as well.
Regards,
Rainer

Please double-check #2994.

#2994 is committed since I had opportunity to confirm the problem and fix myself. Closing this too. Thanks for great report!


[examples/karpenter] karpenter provisioner: use eks-vpc_name in subnetSelector to prevent subnet conflicts with other VPCs

What does this PR do?
This PR fixes subnetSelector in karpenter provisioner by using VPC name e.g. ${eks-vpc_name}-private* => aws001-preprod-dev-vpc-private*
Motivation
If we already have a non-default VPC in account then *private* subnet selecter will select private subnets from all available VPCs as shown in this image.

Karpenter will then discover all private subnets (from all VPCs) and will try to launch nodes in a different VPC and we will get this error.
Error log:
2022-05-14T12:58:21.515Z	ERROR	controller.provisioning	Could not launch node, launching instances, with fleet error(s), InvalidParameter: Security group sg-08772d703d36e84ab and subnet subnet-06ab25f078c0630e5 belong to different networks.; InvalidParameter: Security group sg-08772d703d36e84ab and subnet subnet-04adc26d50a7c8249 belong to different networks.; InvalidParameter: Security group sg-08772d703d36e84ab and subnet subnet-09ef75c0d1cf0d92e belong to different networks.; UnfulfillableCapacity: Unable to fulfill capacity due to your request configuration. Please adjust your request and try again.	{"commit": "7b5afee", "provisioner": "default"}

More

[X] Yes, I have tested the PR using my local account setup  (Provide any test evidence report under Additional Notes)
[ ] Yes, I have added a new example under examples to support my PR
[ ] Yes, I have created another PR for add-ons under add-ons repo (if applicable)
[ ] Yes, I have updated the docs for this feature
[ ] Yes, I ran pre-commit run -a with this PR

Note: Not all the PRs required examples and docs except a new pattern or add-on added.
For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes
terraform plan with my branch. I have also tested this using terraform apply with default_provisioner.yaml

you can also see that aws001-preprod-dev-vpc-private* filter only selects relevant subnets

Thanks for the addition @armujahid  - could you format your change please with pre-commit run -a

formating has been done but it's still stuck at terraform validate on my PC

ya, with the current module structure it takes quite some time - but the checks all passed for pre-commit so all good, thank you! https://github.com/aws-ia/terraform-aws-eks-blueprints/runs/6435063869?check_suite_focus=true


Feature request: Signup form from the post layout

name: Signup form
about: This a gerneral pull request to add a signup form to the newsletter in the post layout
title: 'Feature request: Signup form from the post layout'
labels: 'enhancement'
assignees: '@delisma'
What does this MR do?
This PR addresses the feature request in issue #34. The main solution would be an email input field directly at the bottom of the blog post.

General checklist

[x] Documentation created/updated
[x] Changelog entry added, if necessary
[ ] Tests added for this feature/bug
[ ] Conforms to the style guides

Related issues
#34

@LPipes4 - Thoughts?

en: https://deploy-preview-35--blog-tbs.netlify.app/2021/05/10/codesign-with-deciders
fr: https://deploy-preview-35--blogue-sct.netlify.app/2021/05/10/participation-approbateurs-conception


[Work In Progress] Update main.yml

closes #430

I have tested that the pull_request_target event works successfully in this test pr.  It has not been turned on yet for all GitHub customers and is only turned on for me.  I will open this PR for review once this feature is shipped.

closing this in favor of #452


Higher order components

I was trying to build a higher order component (i.e., a function Component -> Component) but got stuck when "forwarding" requests to the "inner" component. My approach is something like the following:
data Query f o a
  = SomeOuterAction a
  | Inner (forall b. Tuple (f b) (b -> a))
  | HandleInner o a

type Slot = Unit

type State = Unit

hoc
  :: forall f i o m
   . Functor f
  => H.Component HH.HTML f i o m
  -> i
  -> H.Component HH.HTML (Query f o) i o m
hoc innerComponent input =
  H.parentComponent
    { initialState: const unit
    , render
    , eval
    , receiver: const Nothing
    }

  where

  render :: Unit -> H.ParentHTML (Query f o) f Slot m
  render _ =
    HH.div_
      [ HH.text "I'm the wrapper"
      , HH.slot unit innerComponent input (HE.input HandleInner)
      ]

  eval :: Query f o ~> H.ParentDSL State (Query f o) f Slot o m
  eval (SomeOuterAction next) = pure next
  eval (Inner (Tuple fb return)) = do
    result <- H.query unit fb
    pure $ return $ unsafePartial $ fromJust result
  eval (HandleInner o next) = do
    H.raise oqueries
    pure next

The problem is that somewhere in the line with H.query the b type variable escapes its scope and I can't figure out how to fix that. Also I'm not happy about the unsafePartial.
Generally, I wonder whether this is even the right approach, if higher order components are even possible, and what other approaches for achieving similar things in Halogen might be.

I have an immediate suggestion that may help, Inner's argument is Coyoneda. That may fix the skolem escape as it uses Exists to deal with the existential b instead. We use the same thing to capture child queries in HalogenM as it happens: https://github.com/slamdata/purescript-halogen/blob/666dda47e0a41bdf8ecff71c86f70aeef130863a/src/Halogen/Query/HalogenM.purs#L39
The unsafePartial is unavoidable really - there's no way to prove that a query will succeed, since the component being queried might not exist in the HTML. Since the HTML is constant here it should be fine. Actually, another alternative would be to case on the result and use halt when the result is Nothing: it's just as partial, as the result is an exception, but perhaps it better expresses that it's a known invariant.
With both of the above you'd end up with something like this (which does compile without error :tada:):
import Prelude

import Data.Coyoneda (Coyoneda, unCoyoneda)
import Data.Maybe (Maybe(..))

import Halogen as H
import Halogen.HTML as HH
import Halogen.HTML.Events as HE
import Halogen.Query.HalogenM as HQ

data Query f o a
  = SomeOuterAction a
  | Inner (Coyoneda f a)
  | HandleInner o a

type Slot = Unit

type State = Unit

hoc
  :: forall f i o m
   . Functor f
  => H.Component HH.HTML f i o m
  -> i
  -> H.Component HH.HTML (Query f o) i o m
hoc innerComponent input =
  H.parentComponent
    { initialState: const unit
    , render
    , eval
    , receiver: const Nothing
    }

  where

  render :: Unit -> H.ParentHTML (Query f o) f Slot m
  render _ =
    HH.div_
      [ HH.text "I'm the wrapper"
      , HH.slot unit innerComponent input (HE.input HandleInner)
      ]

  eval :: Query f o ~> H.ParentDSL State (Query f o) f Slot o m
  eval (SomeOuterAction next) = pure next
  eval (Inner iq) = iq # unCoyoneda \k q -> do
    result <- H.query unit q
    case result of
      Nothing -> HQ.halt "HOC inner component query failed (this should be impossible)"
      Just a -> pure (k a)
  eval (HandleInner o next) = do
    H.raise o
    pure next

I think this looks good as an approach for this sort of thing - it's not something I've had time to play with yet, but I've had it in mind since we made stuff existential, since it seems like it should be possible now.

Exciting to discover Coyoneda this way. :) The whole thing turns out to work really well. For reference, here is how I use the higher order component (a variation on the "components" example):
module Component where

import Prelude
import Button as Button
import HOC as HOC
import Halogen as H
import Halogen.HTML as HH
import Halogen.HTML.Events as HE
import Data.Coyoneda (liftCoyoneda)
import Data.Maybe (Maybe(..), maybe)

data Query a
  = HandleButton Button.Message a
  | CheckButtonState a

type State =
  { toggleCount :: Int
  , buttonState :: Maybe Boolean
  }

data Slot = Button
derive instance eqTickSlot :: Eq Slot
derive instance ordTickSlot :: Ord Slot

type ChildQuery = HOC.Query Button.Query Button.Message

component :: forall m. H.Component HH.HTML Query Unit Void m
component =
  H.parentComponent
    { initialState: const initialState
    , render
    , eval
    , receiver: const Nothing
    }
  where

  initialState :: State
  initialState =
    { toggleCount: 0
    , buttonState: Nothing }

  render :: State -> H.ParentHTML Query ChildQuery Slot m
  render state =
    HH.div_
      [ HH.slot Button (HOC.hoc Button.myButton unit) unit (HE.input HandleButton)
      , HH.p_
          [ HH.text ("Button has been toggled " <> show state.toggleCount <> " time(s)") ]
      , HH.p_
          [ HH.text
              $ "Last time I checked, the button was: "
              <> (maybe "(not checked yet)" (if _ then "on" else "off") state.buttonState)
              <> ". "
          , HH.button
              [ HE.onClick (HE.input_ CheckButtonState) ]
              [ HH.text "Check now" ]
          ]
      ]

  eval :: Query ~> H.ParentDSL State Query ChildQuery Slot Void m
  eval = case _ of
    HandleButton (Button.Toggled _) next -> do
      H.modify (\st -> st { toggleCount = st.toggleCount + 1 })
      pure next
    CheckButtonState next -> do
      buttonState <- H.query Button $ HOC.Inner $ liftCoyoneda $ H.request Button.IsOn
      H.modify (_ { buttonState = buttonState })
      pure next

Maybe it also makes sense to add something like this to the examples? I could prepare a PR...

I forgot one thing. For some reason, I need to define a Functor instance for the query algebra of the inner component, in this case Button.Query. Is there a way to avoid this?

Nice!
Yeah, I was going to say if this proves to be useful technique it would be great to have as an example / eventually a chapter in the guide (got some way to go before I get to those kind of fun topics yet though :wink:).
Regarding the Functor constraint... I think it's unnecessary? I didn't notice that is was present in your original example so didn't remove it from my proposal, but if you just take the constraint off hoc it still seems to compile for me.

Uh, yes, you're right. That constraint was a relic of my previous struggles...

Why do we need Coyoneda and to hide algebra argument, if this simplest approach works as well:
data Query f i o a
  = InnerQuery (f a)
  -- ...

--  HOC eval
eval (InnerQuery query) = do
  id <- H.gets _.id
  H.query (ChildSlot id) query >>= case _ of
    Just next -> pure next
    Nothing   -> HQ.halt "impossible"

-- Container eval
eval (GetValue next) = do
  value <- H.query ChildSlot (WithDisable.liftQuery (H.request Counter.GetValue))
  pure next

Coyoneda is so that you don't incur a Functor constraint on f. Halogen in general does not require you to implement Functor for query algebras. Coyoneda is the free Functor.


fix: Adjust home screen placeholder for large rail

Description
Adjust home screen placeholder for large rail.
PR Checklist

[ ] I tested my changes on iOS / Android.
[ ] I added screenshots or videos to illustrate my changes.
[ ] I added Tests and Stories for my changes.
[ ] I added an app state migration.
[ ] I hid my changes behind a feature flag.
[ ] I have prefixed changes that need to be tested during a release QA with [NEEDS EXTERNAL QA] on the changelog.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

Thanks!


Add a package for Demeter CLI

This is a CLI tool used to manage Demeter
https://docs.demeter.run/cli

Moving to blinklabs-io/cardano-up-packages#5


Blame report.

****************** Blame Report 1.16.4-2.4.1 ******************

 Failed to load structure nbt file from : minecraft:empty
 The path represented by this is:  data/minecraft/structures/empty.nbt
 The calling Template Pool is: stoneholm:hallways/hallway_x
 Most common cause is that there is a typo in this path to the nbt file.
 Please let the mod author know about this so they can double check to make sure the path is correct.
 A common mistake is putting the structure nbt file in the asset folder when it needs to go in data/structures folder.

 Failed to load resource file: stoneholm:worldgen/processor_list/crypter.json

 Reason stated: Not a json array

 Possibly helpful hint (hopefully):
     This error typically means you need an certain kind of JSON array surrounding
     the current JSON. This is typically seen with worldgen JSON. If this is a worldgen JSON file, then
     check out slicedlime's example datapack for worldgen to find what's off: https://t.co/cm3pJcAHcy?amp=1

 Prettified form of the broken JSON:
{
  "processors": [
    {
      "rules": [
        {
          "output_state": {
            "Name": "minecraft:mossy_cobblestone"
          },
          "input_predicate": {
            "block": "minecraft:cobblestone",
            "probability": 0.01,
            "predicate_type": "minecraft:random_block_match"
          },
          "location_predicate": {
            "predicate_type": "minecraft:always_true"
          }
        },
        {
          "output_state": {
            "Name": "minecraft:cobblestone"
          },
          "input_predicate": {
            "block": "minecraft:barrel",
            "probability": 0.85,
            "predicate_type": "minecraft:random_block_match"
          },
          "location_predicate": {
            "predicate_type": "minecraft:always_true"
          }
        },
        {
          "output_state": {
            "Properties": {
              "rotation": "12"
            },
            "Name": "minecraft:wither_skeleton_skull"
          },
          "input_predicate": {
            "block": "minecraft:skeleton_skull",
            "probability": 0.005,
            "predicate_type": "minecraft:random_block_match"
          },
          "location_predicate": {
            "predicate_type": "minecraft:always_true"
          }
        },
        {
          "output_state": {
            "Name": "minecraft:air"
          },
          "input_predicate": {
            "block": "minecraft:skeleton_skull",
            "probability": 0.6,
            "predicate_type": "minecraft:random_block_match"
          },
          "location_predicate": {
            "predicate_type": "minecraft:always_true"
          }
        },
        {
          "output_state": {
            "Properties": {
              "facing": "north",
              "lit": "false",
              "signal_fire": "false",
              "waterlogged": "false"
            },
            "Name": "minecraft:campfire"
          },
          "input_predicate": {
            "block": "minecraft:campfire",
            "probability": 0.15,
            "predicate_type": "minecraft:random_block_match"
          },
          "location_predicate": {
            "predicate_type": "minecraft:always_true"
          }
        }
      ],
      "processor_type": "minecraft:rule"
    }
  ]
}

[11:37:28] [main/ERROR]:
****************** Blame Report 1.16.4-2.4.1 ******************

 Failed to load resource file: stoneholm:worldgen/processor_list/decayer.json

 Reason stated: Not a json array

 Possibly helpful hint (hopefully):
     This error typically means you need an certain kind of JSON array surrounding
     the current JSON. This is typically seen with worldgen JSON. If this is a worldgen JSON file, then
     check out slicedlime's example datapack for worldgen to find what's off: https://t.co/cm3pJcAHcy?amp=1

 Prettified form of the broken JSON:
{
  "processors": [
    {
      "rules": [
        {
          "output_state": {
            "Name": "minecraft:mossy_cobblestone"
          },
          "input_predicate": {
            "block": "minecraft:cobblestone",
            "probability": 0.01,
            "predicate_type": "minecraft:random_block_match"
          },
          "location_predicate": {
            "predicate_type": "minecraft:always_true"
          }
        },
        {
          "output_state": {
            "Name": "minecraft:cobblestone"
          },
          "input_predicate": {
            "block": "minecraft:barrel",
            "probability": 0.85,
            "predicate_type": "minecraft:random_block_match"
          },
          "location_predicate": {
            "predicate_type": "minecraft:always_true"
          }
        },
        {
          "output_state": {
            "Properties": {
              "rotation": "12"
            },
            "Name": "minecraft:wither_skeleton_skull"
          },
          "input_predicate": {
            "block": "minecraft:skeleton_skull",
            "probability": 0.005,
            "predicate_type": "minecraft:random_block_match"
          },
          "location_predicate": {
            "predicate_type": "minecraft:always_true"
          }
        },
        {
          "output_state": {
            "Name": "minecraft:air"
          },
          "input_predicate": {
            "block": "minecraft:skeleton_skull",
            "probability": 0.6,
            "predicate_type": "minecraft:random_block_match"
          },
          "location_predicate": {
            "predicate_type": "minecraft:always_true"
          }
        },
        {
          "output_state": {
            "Properties": {
              "facing": "north",
              "lit": "false",
              "signal_fire": "false",
              "waterlogged": "false"
            },
            "Name": "minecraft:campfire"
          },
          "input_predicate": {
            "block": "minecraft:campfire",
            "probability": 0.15,
            "predicate_type": "minecraft:random_block_match"
          },
          "location_predicate": {
            "predicate_type": "minecraft:always_true"
          }
        }
      ],
      "processor_type": "minecraft:rule"
    }
  ]
}

Failed to load structure nbt file from : minecraft:empty
That is interesting, that's a minecraft default one.

The rest should be an easy fix though I wonder when it cropped up.

Hi, it may be related to https://github.com/TelepathicGrunt/RepurposedStructures-Fabric/issues/112 (FAPI 0.34 and a bug in CCA) but I can't check this rn.

yep it is because of CCA not being updated for new version of fapi and thus, broke everyone. Using just Stoneholm alone with Blame yields only these two reports:
****************** Blame Report 1.16.4-2.4.1 ******************
Failed to load structure nbt file from : minecraft:empty
The path represented by this is:  data/minecraft/structures/empty.nbt
The calling Template Pool is: stoneholm:hallways/hallway_x
Most common cause is that there is a typo in this path to the nbt file.
Please let the mod author know about this so they can double check to make sure the path is correct.
A common mistake is putting the structure nbt file in the asset folder when it needs to go in data/structures folder.
[07:50:11] [Worker-Main-11/ERROR]:
****************** Blame Report 1.16.4-2.4.1 ******************
Failed to load structure nbt file from : stoneholm:abandoned_poi/inn
The path represented by this is:  data/stoneholm/structures/abandoned_poi/inn.nbt
The calling Template Pool is: stoneholm:abandoned_hallways/to_poi
Most common cause is that there is a typo in this path to the nbt file.
Please let the mod author know about this so they can double check to make sure the path is correct.
A common mistake is putting the structure nbt file in the asset folder when it needs to go in data/structures folder.
The first report seems to say that stoneholm:hallways/hallway_x piece is trying to load "minecraft:empty" nbt piece. Except minecraft:empty isn't an nbt piece but it is a template pool. The report may be off a little with its wording which I'll have to figure out how to fix later.
The second report is pointing to an inn piece that doesnt exist here: https://github.com/TheGrimsey/Stoneholm/tree/v1.2/src/main/resources/data/stoneholm/structures/abandoned_poi
Hopefully that helps

That is very interesting, thank you.
Yeah, I am a bit confused as to why it would complain about minecraft:empty being missing. stoneholm:hallways/hallway_x is a piece and shouldn't be referring to it anywhere. I will have to double check the structure blocks.
When it comes to stoneholm:abandoned_poi/inn that is just using the wrong path (should actually just be stoneholm:poi/inn for abandoned areas as well). Easy to fix.


Error parsing WHOIS server when godaddy throws bad domain info

This package is great. I've been finding lots of bad info inside WHOIS info from using this, and godaddy is not returning a valid host for a few domains:
$ whois the4ccoalition.org
...
Registrar WHOIS Server: whois.godaddy
...

$ whois pgsf.org
...
Registrar WHOIS Server: whois.godaddy
...

Hello @lapubell
Thanks for your PR, this is the mistake of Godaddy, they return a wrong whois server, I have try to contact them to fix it, but no response. I will merge your PR, but this is not a elegant fix.

If you think this repository is helpful, please share it with friends, thanks.


pypi / source distribution

@miyuchina I'm testing out a dependency-management tool for the nix language / package system and it fell on its face when it tried to find a source distribution for mistletoe on pypi.
Can you look into getting one uploaded? :)

I uploaded a source distribution to pypi for version 0.7.2. Let me know if that works for you!


router: include attempt count for response in virtual hosts

Following the same logic as https://github.com/istio/istio/pull/21198
Where https://github.com/istio/istio/pull/21198 included x-envoy-attempt-count for the upstream requests, this PR adds the same header to the respective downstream responses.

[ ] Ambient

[ ] Configuration Infrastructure

[ ] Docs

[ ] Installation

[x] Networking

[ ] Performance and Scalability

[ ] Policies and Telemetry

[ ] Security

[ ] Test and Release

[ ] User Experience

[ ] Developer Infrastructure

[X] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

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

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Can you give some more info about why this is needed?
Generally every header we have added has gotten complaints and there is some work to allow configuring these: https://github.com/istio/api/pull/2240

I would feel much more comfortable if we had https://github.com/istio/api/pull/2240 which would allow this to be opt in. Although its stalled a bit.. will see if I can revive it

Sure, I think the most common use case here is people enabling this for debugging purposes.
So having a control flag make sense.

@howardjohn just saw last week's work group meeting's recording. Thank you for reviving https://github.com/istio/api/pull/2240. I'll keep an eye out for the resolution there.

You can enable it in access log and it prints it IIRC

@ramaraochavali , yeah thats one of the possibilities for testing things but it gets trickier in production with services that have 100s of pods and if the retry issues only happen sporadically.
In our case, the clients usually keeps an eye out for the header and logs those requests separately to be debugged.

PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@howardjohn I see https://github.com/istio/api/pull/2240 is merged finally after all the discussions 😄
Any objections in re-opening (and possibly merging) this one ?


Documentation: how to start crono

Thanks fo the great gem!
The documentation only explains how to start crono from the command line. I'd like to have it autostarted with a Rails project instead of creating a Linux init script or something. Can it start automatically when Rails is started? Do we need to create an initializer? What are the consequences of running as a daemon vs. not running it as a daemon?
Again, thank you.

Hello @brunofacca
you can start it using foreman
With a Procfile like:
web: bundle exec puma -C config/puma.rb crono: bundle exec crono
then:
foreman start

Thank you @plashchynski


CH4 - Make sure Riki can not die before he should

Possible to get some lucky crits and stun to kill him I think right now

This is still an issue. Right now Riki only gets the takes no damage modifier durign wards section, but during outpost section he is still killable after dust for example.

Fixed so he's only killable at the end of outpost section

Fixed in https://github.com/ModDota/dota-tutorial/pull/412


Make sure nil values stay as nil: fixes issue with repeatable values

Fixes issue with repeatable values including '' after each value, this would cause wkhtmltopdf to fail

Fixes issue with repeatable values including '' after each value, this would cause wkhtmltopdf to fail

Which issue, is there a bug already filed for this or can you describe it here?

There wasn't a bug filed. It was an issue I was running into while using
it. I'll try to explain it here:
The problem appeared when I was trying to use run_script as an option. I
noticed if I use just one run_script option, then the option wouldn't
appear at all in the wkhtmltopdf command that was sent. With multiple
options put in an array like "run_script: [jqueryIncludeScript,
script]", the wkhtmltopdf command would crash. After debugging it
appears that the problem was that it would include an extra blank string
parameter after each key and value pair. E.g. --run-script <script 1> ''
--run-script <script 2> ''. So what the change I did fixed that, the
third value now stays nil, by not converting it to a string, and
therefore won't appear in the command options. So it now outputs as
--run-script <script 1> --run-script <script 2>
The commit "Fix bug with repeating keys with string values" fixed the
issue with inputting a single repeatable option but not inputting
multiple repeatable options.
On 6/3/15 3:17 PM, Ian Cordasco wrote:

Fixes issue with repeatable values including '' after each value,
this would cause wkhtmltopdf to fail

Which issue, is there a bug already filed for this or can you describe
it here?
—
Reply to this email directly or view it on GitHub
https://github.com/pdfkit/pdfkit/pull/309#issuecomment-108585604.

Would you mind adding tests to this so it doesn't regress?

Sure, I'll put up some tests by the end of the day

The tests I just added work with my changes, but fail at the previous commit. So that should be good to go.

LGTM. @pdfkit/rb thoughts?

(thumbsup) Thanks @tylerITP


"Use cases" field in SMIRFF xml?

Discussion: Chris Bayly suggested we include a "use_case" field in the ffxml files which would give a simple example SMILES for a fragment in which the specified parameter would be used, just to make it easier for people to be able to see what parameters are intended to cover. Thoughts?

If your goal is to annotate handwritten XML files, why not use XML comments?
You can certainly add additional attributes like this if you want, but they
will be ignored by the ForceField parser.
In summary: Do what makes you happy to the manually curated XML files! It
shouldn't break anything.

Yes, understood.
Having them as a tag might make sense from the standpoint of being able to make nice visualizations of what the parameters are supposed to be doing downstream; comments are less helpful for this since they aren't automatically parseable as easily.
This issue is mostly here to remind me to discuss it with Christopher when he gets back to see if he has a specific use case in mind.

The important question for me is this: if you want the sampling framework
to generate these, how would it do that, and does it offer added value over
just having a tool that finds matches in a set of molecules to display in
some useful way?

Exactly. I'll discuss that with him when he gets back (looks like about a week from today).

I'm closing this -- I think the functionality needed is just to query a set of molecules and see which match the specified string, which is trivial.


Error

https://gist.github.com/64ce4c90aafc34fc68b5
During /pex user  group set

Do you get the same error when using the correct command of /pex user Stormbow group set Potato?

Yeah the command was correct... I shortened it fpr this issue. I could NOT reproduce it, it was just happening when setting a group

That command isn't used to "set up" a group, but it's good you got it working.  :)


No explanation for what is "μ" in test outputs

Every now and then, the μ symbol (Greek letter mu) appears in my test outputs. However, I couldn't find this documented in the Tests chapter of the book.

The number after μ is the mean gas used across all fuzz runs, and the one after ~ is the median gas used across those same fuzz runs. I can probably get a PR in for this later today if you don't beat me to it 🙂
https://github.com/gakonst/foundry/blob/b8125de1d7eec22baca83b24fe141b1d262c1426/forge/src/runner.rs#L96

Not sure where this is supposed to fit - honestly, this should probably be in the Forge command reference (TBD)

Until that page is created, I think https://book.getfoundry.sh/forge/fuzz-testing.html seems like the appropriate spot by adding an "Interpreting Results" section or something similar

Thanks @mds1 for explaining this.


Fireteam chat leaks sometimes

Sometimes, chats from fireteam appear to others than clients in the fireteam the messages were sent at.

Still issue in 2.5.1


Motion sensor alerts

After days of testing this plugin, it appears that the motion alerts reported by the HomeKit are spotty and inconsistent while Ring motion notifications pop up on every occurrence. Am running all latest os on raspberry e b+

I have similar problem. After restart Homebridge the motion alerts are reported for a small time. For example 10 min. . After them I don’t get more motion alerts over HomeKit.

This plugin is now DEPRECATED... you will find a vastly superior plugin here!


Improve UX

Closes https://github.com/reform-org/reform/issues/269
Closes https://github.com/reform-org/reform/issues/171
Closes https://github.com/reform-org/reform/issues/314
Closes https://github.com/reform-org/reform/issues/275
Closes https://github.com/reform-org/reform/issues/264
Closes https://github.com/reform-org/reform/issues/315

Actions column should be way smaller on mobile
Dropdowns in table are getting cut off overflow y visible should help

Bugs that need to be addressed before merging:

[ ] Scrolling the table horizontally does not work
[ ] popper places the dropdown at the wrong offset (ca. 8px too high)
[ ] Dropdowns do not close on click outside, UI (especially mobile menu) is therefore not navigatable because other dropdowns overlay it.
[ ] td does not has max width but div inside, therefore some tds are too large on big screens

[ ] Multiselect closes once option has been selected
[ ] multiclose in table: popper misplaced until scroll


Fix Jumps Benchmarks

Continuation of https://github.com/SciML/SciMLBenchmarks.jl/pull/230
@isaacsas

What’s wrong with them currently?

I'll take a stab at updating them in a few minutes. There's a few old package things that need to be updated.

First things first, they gotta get updated to Catalyst.jl, so they are pretty far behind 😅 .
https://github.com/SciML/SciMLBenchmarks.jl/pull/275

Oh wow, that’s old. Sorry, I thought I’d updated that at some point…

I must have mixed it up with the problem library…

@Gregliest fixed two of them in https://github.com/SciML/SciMLBenchmarks.jl/pull/286 . Mendes and Diffusion are left.
Diffusion needs to be updated to use the new programmatic interface of https://catalyst.sciml.ai/dev/tutorials/generating_reactions_programmatically/ . The current version uses rn = @empty_reaction_network which has been entirely replaced by programmatically writing ReactionSystems, which is documented there.
I'm not sure what the other one boils down to right now.

FWIW, I think the diffusion one is very similar to what is in the problem library (which should be updated to Catalyst):
https://github.com/SciML/DiffEqProblemLibrary.jl/blob/29606924fadb5c0576e5bb87ca4c345cc1501a38/src/jump_premade_problems.jl#L237-L254


Undefined variable: b:syntastic_changedtick

Every time I save a file I have this message error:
Error detected while processing function <SNR>50_BufWritePostHook[4]..<SNR>50_UpdateErrors:
line   46:
E121: Undefined variable: b:syntastic_changedtick
E15: Invalid expression: [a:buf, b:syntastic_changedtick]

My vim version: stable 7.4.2152
Syntactic: commit a0f5b72f14fba99f91b07580d0a11c96900fb242

Please upgrade to the latest master HEAD and try again.

Please see #1862.  Not the same problem, but still not syntastic's problem, either.

If the problem is vim related the patch is only for 7.4.2299 and I'm in 7.4.2152, should I upgrade vim?

The problem is likely to be triggered by a third-party plugin, and it's also likely to be related to an autocmd.

I'm not a vim expert, how can I debug this?
This is the list of third-party plugins I have installed:
Plug 'tpope/vim-sensible'
Plug 'scrooloose/nerdtree'
Plug 'tpope/vim-fugitive'
Plug 'airblade/vim-gitgutter'
Plug 'scrooloose/syntastic'
Plug 'tpope/vim-surround'
Plug 'ctrlpvim/ctrlp.vim'
Plug 'bling/vim-airline'
Plug 'valloric/youcompleteme'
Plug 'sirver/ultisnips'
Plug 'honza/vim-snippets'
Plug 'roosta/srcery'
Plug 'xuyuanp/nerdtree-git-plugin'
Plug 'mileszs/ack.vim'
Plug 'terryma/vim-multiple-cursors'
Plug 'editorconfig/editorconfig-vim'
Plug 'xolox/vim-session'
Plug 'xolox/vim-misc'
Plug 'scrooloose/nerdcommenter'
" Loaded when specific file type is opened
Plug 'stephpy/vim-php-cs-fixer', { 'for': 'php' }
Plug 'rust-lang/rust.vim', {'for': 'rust'}

Disable the other plugins (i.e. comment out the Plug lines above) and check that syntastic works as expected.  Then enable them in turn, and see which one breaks syntastic.  Start with xuyuanp/nerdtree-git-plugin, IIRC it had problems with syntastic in the past and the problems were never fixed to this day.
It's a relatively short list, but if you want to optimise your work you can do binary search: comment out half of them, to find out if the offending one is in the first half or the second half etc.

@lcd047, you hit the spot, the problematic plugin is xuyuanp/nerdtree-git-plugin
I did a full plugin upgrade this morning, before this all work with any issue ...

This should be fixed in 557b52f.  Please upgrade to the current master HEAD and try again.

The problem was fixed.


Export to image on Ubuntu under Windows works only the first time

I am using Ubuntu running on Windows 10 using WSL1 (https://ubuntu.com/tutorials/ubuntu-on-windows#1-overview).
The first time I run kaleido write_image function to export a PNG figure it works fine.
The second and subsequent times write_image function hangs. When I interrupt with the keyboard I get the following on the terminal:
I have left it run overnight and didn't finish so it definitely hangs.

^CTraceback (most recent call last):
File "main.py", line 43, in
barChart.graphBarChart(cfg.emotionalGraphFilename, cfg.outputImagesFolder, xAxisLabels, yAxisValues)
File "/home/soltuin/devsource/doc-to-pdf/doc-to-pdf/barChart.py", line 81, in graphBarChart
fig.write_image(fileName, width=barWidth, height=barHeight, engine="kaleido", validate=False)
File "/home/soltuin/pythonenvironments/neocemod/lib/python3.8/site-packages/plotly/basedatatypes.py", line 3251, in write_image
return pio.write_image(self, *args, **kwargs)
File "/home/soltuin/pythonenvironments/neocemod/lib/python3.8/site-packages/plotly/io/_kaleido.py", line 244, in write_image
img_data = to_image(
File "/home/soltuin/pythonenvironments/neocemod/lib/python3.8/site-packages/plotly/io/_kaleido.py", line 130, in to_image
img_bytes = scope.transform(
File "/home/soltuin/pythonenvironments/neocemod/lib/python3.8/site-packages/kaleido/scopes/plotly.py", line 102, in transform
response = self._perform_transform(
File "/home/soltuin/pythonenvironments/neocemod/lib/python3.8/site-packages/kaleido/scopes/base.py", line 218, in _perform_transform
response = self._proc.stdout.readline()

I looked at the kaleido/scopes/base.py line 218 and it seems to be waiting for a response from kaleido process? (I don't know kaleido internals)
Is there anyway I can debug this issue? add verbose of some sort?

Adding data to the issue.
Running $ps just noticed that there are many kaleido processes running in the background.

The next thing you could try would be to call the kaleido native executable from the command line. There are some instructions for that in https://github.com/plotly/Kaleido/issues/26#issuecomment-664948907.  These were written for Windows, but the approach is the same for Linux.
Since you're export is working the first time, I expect everything will work up until the first time you enter {"data":{"layout":{}}}, so do this part multiple times.  It will probably hang the second time, but hopefully chromium will output some error info.  Please copy all of the terminal output that you see.
All that said, it looks like folks have had trouble with using Chromium-based projects under WSL 1. See https://github.com/microsoft/WSL/issues/648 and https://github.com/microsoft/WSL/issues/2760.  So it might not be possible to get this working reliably.  I expect things will work better on WSL 2 since this is based on a true Linux VM instead of a Linux-to-windows translation layer.

Thanks for your interest in Kaleido. We are currently working on an overhaul that might address your issue - we hope to have news in a few weeks and will post an update then. Thanks - @gvwilson


software_spec: fix cellar any handling.

cellar :any actually requires no references to the cellar, prefix or repository (not just cellar) so we can pour those bottles anywhere regardless of the cellar, prefix or repository.
Reported in https://github.com/Homebrew/brew/pull/9481#issuecomment-744974244

Review period skipped due to critical label.

Thanks for the fix, Mike!


EdgeHubConnectionString and IOTEDGE_IOTHUBHOSTNAME are not set / spark_home not set / exception in worker process

I came across the following spark worker node issue that might be related to the gunicorn gateway inference server running Spark?
(The last pandas not found incurred on this server? i noted pandas module not found error, and the gunicorn requires python 3.7 so would the score.py need somekind of reconfiguration to be validated?)https://docs.microsoft.com/en-us/azure/machine-learning/how-to-inference-server-http
2022-01-11T07:22:51,350423000+00:00 - rsyslog/run
2022-01-11T07:22:51,356648500+00:00 - gunicorn/run
2022-01-11T07:22:51,355747300+00:00 - iot-server/run
2022-01-11T07:22:51,381952900+00:00 - nginx/run
EdgeHubConnectionString and IOTEDGE_IOTHUBHOSTNAME are not set. Exiting...
2022-01-11T07:22:51,595759100+00:00 - iot-server/finish 1 0
2022-01-11T07:22:51,599248900+00:00 - Exit code 1 is normal. Not restarting iot-server.
Starting gunicorn 20.1.0 ****
Listening at: http://<IP_ADDRESS>:31311 (454)
Using worker: sync
worker timeout is set to 300
Booting worker with pid: 484
SPARK_HOME not set. Skipping PySpark Initialization. *****
Exception in worker process
Traceback (most recent call last):
File "/azureml-envs/azureml_b40613e65d875dd6f39858a7ef2209be/lib/python3.6/site-packages/gunicorn/arbiter.py", line 589, in spawn_worker
worker.init_process()
File "/azureml-envs/azureml_b40613e65d875dd6f39858a7ef2209be/lib/python3.6/site-packages/gunicorn/workers/base.py", line 134, in init_process
self.load_wsgi()
File "/azureml-envs/azureml_b40613e65d875dd6f39858a7ef2209be/lib/python3.6/site-packages/gunicorn/workers/base.py", line 146, in load_wsgi
self.wsgi = self.app.wsgi()
File "/azureml-envs/azureml_b40613e65d875dd6f39858a7ef2209be/lib/python3.6/site-packages/gunicorn/app/base.py", line 67, in wsgi
self.callable = self.load()
File "/azureml-envs/azureml_b40613e65d875dd6f39858a7ef2209be/lib/python3.6/site-packages/gunicorn/app/wsgiapp.py", line 58, in load
return self.load_wsgiapp()
File "/azureml-envs/azureml_b40613e65d875dd6f39858a7ef2209be/lib/python3.6/site-packages/gunicorn/app/wsgiapp.py", line 48, in load_wsgiapp
return util.import_app(self.app_uri)
File "/azureml-envs/azureml_b40613e65d875dd6f39858a7ef2209be/lib/python3.6/site-packages/gunicorn/util.py", line 359, in import_app
mod = importlib.import_module(module)
File "/azureml-envs/azureml_b40613e65d875dd6f39858a7ef2209be/lib/python3.6/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 994, in _gcd_import
File "", line 971, in _find_and_load
File "", line 955, in _find_and_load_unlocked
File "", line 665, in _load_unlocked
File "", line 678, in exec_module
File "", line 219, in _call_with_frames_removed
File "/var/azureml-server/wsgi.py", line 1, in
import create_app
File "/var/azureml-server/create_app.py", line 3, in
from app import main
File "/var/azureml-server/app.py", line 32, in
from aml_blueprint import AMLBlueprint
File "/var/azureml-server/aml_blueprint.py", line 23, in
main_module_spec.loader.exec_module(main)
File "/var/azureml-app/score.py", line 16, in
import pandas as pd
ModuleNotFoundError: No module named 'pandas' ******
Worker exiting (pid: 484)
Shutting down: Master
Reason: Worker failed to boot.

I also tried Python 3.8 with similar error:  (I may try to see if I can explicitly do Conda install pandas or pip install pandas (this is a pure azureml cloud notebook and deployment. My last run shows the failure is at line 16 of score.py: import pandas as pd.
Error:
{
"code": "AciDeploymentFailed",
"statusCode": 400,
"message": "Aci Deployment failed with exception: Error in entry script, ModuleNotFoundError: No module named 'pandas', please run print(service.get_logs()) to get details.",
"details": [
{
"code": "CrashLoopBackOff",
"message": "Error in entry script, ModuleNotFoundError: No module named 'pandas', please run print(service.get_logs()) to get details."
}
]
}

I can confirm that adding 'pandas' to pip section of myenv.yml file solve the problem. Perhaps it is worth to note  and see if using version version specification also solve the problem (no idea what conda install using that 'zureml-defaults' specified in the yml file):
The conda environment file specifies the dependencies for the service. It includes dependencies required by both the model and the entry script. Please note that you must indicate azureml-defaults with verion >= 1.0.45 as a pip dependency, because it contains the functionality needed to host the model as a web service
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/machine-learning/how-to-deploy-inferencing-gpus.md

@rhpoon Is this issue related to one of our samples? Which one?

@rhpoon No response, and not related to a code sample. Closing.


adding LightweightRNN

merging Lightweight RNN, which contains recurrent layers, back into head

I didn't want to merge this into master, but I created another branch and merged it into michael-rnn, see #10


Getting error during delete resource

Info     - Deleting resource user.user_favorite(Optional("89"), nil) using URL: http://cisfinder.com/api/user/user_favorite/89
Error    - Either 'data', 'errors', or 'meta' must be present in the top level.
my model is:
class Favorite: Resource{
var reference_id: String?

required init() {
    super.init()
}
required init(coder: NSCoder) {
    super.init(coder: coder)
}
override class var resourceType: ResourceType {
    return "user.user_favorite"
}

override class var fields: [Field] {
    return fieldsFromDictionary([
        "reference_id": Attribute(),
        ])
}

}

Can you post here the response from the server?

On 6 Dec 2016, at 13:07, jyoti jangir<EMAIL_ADDRESS>wrote:
Info - Deleting resource user.user_favorite(Optional("89"), nil) using URL: http://cisfinder.com/api/user/user_favorite/89
Error - Either 'data', 'errors', or 'meta' must be present in the top level.
my model is:
class Favorite: Resource{
var reference_id: String?
required init() {
super.init()
}
required init(coder: NSCoder) {
super.init(coder: coder)
}
override class var resourceType: ResourceType {
return "user.user_favorite"
}
override class var fields: [Field] {
return fieldsFromDictionary([
"reference_id": Attribute(),
])
}
}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

This is the desired response:
In case of success
{
"meta": {
"user": {
"id": 34,
"role_id": 4,
"organisator_id": 0,
"gender": "M",
"title": null,
"firstname": "John",
"lastname": "Dow",
"email_address"<EMAIL_ADDRESS>"dob": null,
"telephone": "",
"status": 1,
"locked": false,
"false_logins": 0,
"count_logins": 19,
"confirmed": true,
"token_expires": "2016-11-15T11:41:15+0100",
"user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.98 Safari/537.36",
"last_login": "2016-12-05T12:25:21+0100",
"created": "2016-11-14T11:41:15+0100",
"modified": "2016-12-05T12:25:21+0100",
"facebook_id": 0
}
}
}
In case of failure:
{
"success": false,
"data": {
"message": "Not Found",
"url": "/api/user/user_favourite/89",
"code": 404
}
}

Can you include the entire response for a successful and failed deletion? So including status code.
When the DELETE request returns a non-successful status code (< 200 and > 299 ), Spine tries to deserialise the response. It seems that that response does not contain a data, meta, or errors key. If it does, then this is a bug in Spine somewhere.

I have posted the entire response, getting this response when I make an API on the "POSTMAN".


fix: cypress flakiness due to focus cypress function

Description
Updating the focus cypress function to click function to avoid flakiness.
Fixes #Issue Number
or
Fixes Issue URL

[!WARNING]
If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation
/ok-to-test<EMAIL_ADDRESS>:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[ ] No

/ci-test-limit


Aggregating different sources

I want to aggregate metrics of a source group, but when use source groups for metrics, it puts data from different sources separately.
For example, consider I have source group glob:node* and I have two sources node-1 and node-2, and for each of them I have metric cpu.idle. What I want to show on graph is a cpu.idle metric which is aggregation (preferably average) of node-1.cpu-idle and node-2.cpu-idle. But when I use source groups for that, it shows node-1.cpu-idle and node-2.cpu-idle separately.
Does Facette support this? If not, do you have plans to support it?

Hi @gokarslan,
You can perform some operations on series when grouped or when source/metric groups are present.
You have to click on the “cog” icon to do so and select ”Sum” or ”Average” as operation:

Let me know if it answers your question.

Hi @vbatoufflet,
Thank you very much for your answer, it answers my question for single metric with source group.  Another thing I'm curious about is what if I have a metric group and source group and I want to sum metrics on metric group for per source and then take average of them.
For example, if I have a metric group M with metrics M1, M2 and source group S with sources S1 and S2, what I want to calculate is first M1+M2 for each source (S1, S2) then taking average of those sum. (i.e. if my resulting field is M_R; let M_S1 = M1+ M2 (source S1) and M_S2=M1+M2 (source S2) then M_R = (M_S1 + M_S2)/2)
Is this possible?

That's not possible given the way it works today. All you'll we have is a resulting ”big” average or sum of all matching source/metric couples.


Allow user to set node selector for system managed components, manager, UI, driver deployer

This feature allow user to deploy Longhorn only on a specific
set of nodes
Modification:

Remove the toleration and priority class settings from question.yaml.
User cannot set toleration for the user-deployed components  (manager, UI, Driver) from the question.yaml because Rancher chart doesn't allow question of type array. Therefore, user must choose to Edit as YAML in Rancher Ui when install Longhorn . On the other hand, if user wants set toleration and priority class for Longhorn, they must set them for both system managed components and user-deployed components. Therefore, to avoid the mistakes, we remove everything from the question.yaml and user can edit the yaml to specify value for both system managed components and user-deployed components.
Allow user to specify node selector for  system managed components and user-deployed components. Again, user must chose edit as YAML because the limitation of Rancher chart.

longhorn/longhorn#2199

@shuo-wu  How do you think about the removal of the toleration and priority class settings from question.yaml ?
Right now, the user experience is not great when user instal Longhorn using Rancher UI and want to set  toleration ,  node selector.  I have asked Rancher team at here. Waiting for their feedback

@PhanLe1010
Now tolerations, priorityclass, and node selector settings are applied to system deployed workloads only, right? Maybe we can directly convert the array/map to a string and applied them to the settings as well.
e.g., for the toleration setting, we can use the following:
taint-toleration: {{ .Values.longhornManager.tolerations | toJson }}

Then the rendered result is:
taint-toleration: [{"effect":"NoSchedule","key":"key","operator":"Equal","value":"value"}]

Here is the doc:
https://helm.sh/docs/chart_template_guide/function_list/#type-conversion-functions
Notice that the tolerations/priorityclass/nodeselector are set separately for longhornManager/longhornDriver.... Why cannot use a single setting for all workloads instead?

Notice that the tolerations/priorityclass/nodeselector are set separately for longhornManager/longhornDriver.... Why cannot use a single setting for all workloads instead?

This is a good point, I missed this part.
One more question: do we allow users to deploy longhorn workloads and longhorn managed workloads separated in different nodes? I don't think so, so probably we just need to make sure the node selector for longhorn both workloads managed via the default setting.

@shuo-wu

for the system managed components. User will specified a string value for taint-toleration, system-managed-components-node-selector, and priority-class in the default-setting section. The string values will have similar structure as seen in UI setting page. For taint-toleration, the value should look like key=value:NoExecute instead of [{"effect":"NoSchedule","key":"key","operator":"Equal","value":"value"}]
We don't want to use a single tolerations/priorityclass/nodeselector setting for all longhornManager/longhornDriver/UI because they doesn't always have to be the same. For example, it makes sense that users have high priority class for longhorn manager but low priority class for UI. Same goes for toleration and node selector, user may want to run Longhorn UI on a specific node that is different than where Longhorn manager is running. In general, I think we should let user customize the components that they controller (manager, driver, UI) however they want. We should only controller the system managed components

@innobead

so probably we just need to make sure the node selector for longhorn both workloads managed via the default setting.

This is our previous design and it create a headache for user who is using GitOps tools: Longhorn continuously modified the  user-deployed components and GitOps try to revert it back to the initial state. You can see more detailed in this user's feedback https://github.com/longhorn/longhorn/issues/2120#issuecomment-748473152

Thanks @PhanLe1010 explanation. Let's keep it for now and see user feedback.


opvn_getclients second variable not passing through

Hi, I am trying to run this one:
docker run -v $OVPN_PKI:/etc/openvpn --rm -it kylemanna/openvpn ovpn_getclient $DEVICE > "/volume2/folder name/$DEVICE.ovpn"
However I keep getting as an output in the folder the message that there are two parameters (three really), combined, combined-save or separate.
This script can produce the client configuration in two formats:     1. combined (default): All needed configuration and cryptographic material is in one file (Use "combined-save" to write the configuration file in the same path as the separated parameter does).     2. separated: Separated files. Please specify one of those options as second parameter.
So I append "combined" to the end of that line:
docker run -v $OVPN_PKI:/etc/openvpn --rm -it kylemanna/openvpn ovpn_getclient $DEVICE > "/volume2/folder name/$DEVICE.ovpn" combined
And I get the same thing happening. I've tried -combined, --combined, -combined-save, you name it. I tried assigning the path to variables and running it that way, but getting the same message, or other odd messages.  I've been trying to follow this faq however when I get to generating the OpenVPN client file, that's where it stalls so I can't move further.
Also, second issue, I decided that might be too much trouble and was trying to follow this katacoda scenario for docker-compose, and ran into this error:
bash-4.3# docker-compose run --rm openvpn \
>     ovpn_genconfig -u udp://example.com
Creating network "openvpn_default" with the default driver
Error response from daemon: Bind mount failed: '/volume2/docker/openVPN/openvpn-data/conf' does not exists

Any help would be great. Thanks.

if you use docker desktop in windows, you should do it like this:
docker run -v $OVPN_PKI:/etc/openvpn --rm -it kylemanna/openvpn ovpn_getclient $DEVICE > "c:\$DEVICE.ovpn"

if you use docker desktop in windows, you should do it like this:
docker run -v $OVPN_PKI:/etc/openvpn --rm -it kylemanna/openvpn ovpn_getclient $DEVICE > "c:\$DEVICE.ovpn"

I'm SSHing into my Synology NAS so it wouldn't be a drive letter type of deal.

try this:
docker run -v $OVPN_PKI:/etc/openvpn --rm -it kylemanna/openvpn ovpn_getclient $DEVICE combined
combined is already saving to file you do not need to redirect.
you put combined after > (redirect) and therefore it is not pass as  argument to script

try this:
docker run -v $OVPN_PKI:/etc/openvpn --rm -it kylemanna/openvpn ovpn_getclient $DEVICE combined
combined is already saving to file you do not need to redirect.
you put combined after > (redirect) and therefore it is not pass as  argument to script


Added error message to the terminal for more explicit debugging

This fixes issue #25 - Debugging

Thanks for the PR. No camera today.. so no picture of gratitude... Please accept this old style emoticon in its place...
8(