[Bug]: Bad position of Go to top button

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Having "Go to top" button in the navbar makes no sense and is one of the bad UI examples. The purpose of this button is just to go the top of the page in one go, so there is no point of having it from the top page only.
I would like to fix this by removing the "Go to top" button from the navbar and keeping it at the bottom of the page towards the bottom right corner.
Add Screenshots

What browsers are you seeing the problem on?
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC contributor
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

@mansiruhil13 Can you assign me this task with hacktoberfest and gssoc-extd labels? Thank you!


adding edit parameter to enable builder in downloaded template

"Can I use the builder with the downloadable?
Yes, when the template is configured with an application ID, adding the URL parameter 'edit' will open the builder. You will be prompted for user authentication through the Identity Manager"
Can you explain exactly where and how to add the URL parameter 'edit' - I have tried and failed :(  Thank you!

sure, you should be accessing the application using an URL like
http://localhost/MyJournal/index.html to use the builder, you have to modify the URL to be http://localhost/MyJournal/index.html?edit
Note that except advanced customization or if you have increased the maximum number of sections, you can also just enter the builder through the item in ArcGIS Online. you will not have to know that trick and the changes will apply to both application.

Sweet…thx… I had been trying to append &edit (which works when app is hosted in AGOL) instead of ?edit to the url for app hosted on localhost….
From: glazou<EMAIL_ADDRESS>Sent: Wednesday, June 3, 2015 4:49 PM
To: Esri/map-journal-storytelling-template-js
Cc: Hoole, Meg FLNR:EX
Subject: Re: [map-journal-storytelling-template-js] adding edit parameter to enable builder in downloaded template (#36)
sure, you should be accessing the application using an URL like
http://localhost/MyJournal/index.html to use the builder, you have to modify the URL to be http://localhost/MyJournal/index.html?edit
Note that except advanced customization or if you have increased the maximum number of sections, you can also just enter the builder through the item in ArcGIS Online. you will not have to know that trick and the changes will apply to both application.
—
Reply to this email directly or view it on GitHubhttps://github.com/Esri/map-journal-storytelling-template-js/issues/36#issuecomment-108649046.


Change Point Dot color

How to, it's not in documents.

I need to change Point dot color too.I've seen on line 276 (https://github.com/jtblin/angular-chart.js/blob/master/dist/angular-chart.js):
function getColour (colour) {       return {         fillColor: rgba(colour, 0.2),         strokeColor: rgba(colour, 1),         pointColor: rgba(colour, 1),         pointStrokeColor: '#fff',         pointHighlightFill: '#fff',         pointHighlightStroke: rgba(colour, 0.8)       };     }
I need to change pointColor to always be white on some cases, not the same color of stroke.  Any advice here?

Going further on this, I've found that on chart.js v1, you can set a full 'data' object, with labels and datasets, and pass it when you create a new ChartJs. But angular-chart forces me to set separated configs in each canvas attribute (chart-labels, chart-data, chart-series, ....).
There is a way to pass the full data object directly using angular-chart? If not, do you think to allow this as an option (you can use both ways, not at the same time, of course)? Ty.


Automatically calculate which models have MinCPUModel's features

Automatically calculate which models have MinCPUModel's features and ignore models that don't.
Signed-off-by: bmordeha<EMAIL_ADDRESS>
What this PR does / why we need it:
Currently if a source node has a Feature that is in MinCpuModel's features and a target node doesn't a migration to this node will fail  and it will be very hard to understand why because the features in MinCpuModel don't appear in the node's labels.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/retest-required

/hold

/unhold


Small optimizaitons in h5 unpack_data.

Minimize group ID look-ups and avoid simple
function call overhead.

Current coverage is 100.00%

Merging #311 into master will not affect coverage as of 63d2a53

@@            master    #311   diff @@
======================================
  Files           41      41
  Stmts         1881    1879     -2
  Branches         0       0
  Methods
======================================
- Hit           1881    1879     -2
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of 63d2a53

Powered by Codecov. Updated on successful CI builds.

Is this OK?


Bump moment to moment-timezone.

Description
Attempting to send a post preview email in Ghost 3.15.3 results in the following error:
TypeError: momentDate.tz is not a function
    at Object.serialize (/var/www/hackers/versions/3.15.3/core/server/services/mega/post-email-serializer.js:102:36)
    at async getEmailData (/var/www/hackers/versions/3.15.3/core/server/services/mega/mega.js:13:39)
    at async Object.sendTestEmail (/var/www/hackers/versions/3.15.3/core/server/services/mega/mega.js:66:44)
    at async Object.query (/var/www/hackers/versions/3.15.3/core/server/api/canary/email-preview.js:70:30)

moment has supposedly been deprecated in favor for moment-timezone:
(node:20259) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated

Replace moment in post-email-serializer.js appears to resolve this issue: https://github.com/toddbirchard/Ghost/blob/097a72ffe88d55dac37aba99d42df03f1848c841/core/server/services/mega/post-email-serializer.js#L5

@toddbirchard I'm not able to reproduce this bug. How did you you install Ghost and which version of Node.js are you running?

I'm running a self-hosted Ghost instance with the following:
Ghost version: 3.15.3
Ghost-CLI version: 1.13.1
Node version: v12.16.3
NPM version: 6.14.5
Ubuntu version: 18.04.4
If this issue is unique to me, my best guess might be that building a third-party storage adapter in the /current directory may have caused some chained dependency conflict. In that case, this might just be a "me" issue as opposed to an actual issue ¯_(ツ)_/¯.
Thanks!

Hey @toddbirchard! :wave:
I just came across the same error when I was updating the moment dependency. I'm guessing you had the latest version of moment installed for some reason, and something inside moment changed such that our existing code didn't work.
Whatever the case, thanks for the PR because it made solving the problem much easier. I'm going to close this PR in favor of the one going in with the moment update but thanks again!


Updated js-guidelines

My updates.

This is all great stuff, which is why my comments are all quibbles and nitpicks.

This looks great to me :) Other then the small nits and s/aegir.js/aergir/g, is RTM :)
Thank you for reviewing this throughly, @RichardLitt :)


[BUG]: "drizzle-kit generate" generates unexpected migrations and then "push:pg" throws unexpected errors

What version of drizzle-orm are you using?
0.29.0
What version of drizzle-kit are you using?
0.20.6
Describe the Bug
Whenever I make small schema changes and generate migration, it generates different  SQL queries as well. For instance, I added new table with the following schema.
this is the newly added small table with only 2 columns but it doesn't matter how big or small change it is, it can be even a column name change, it still generates enormous SQL migration query and db push throws error.
export const relatedPhrases = pgTable("related_phrases", {
  wordId: integer("phrase_id")
    .notNull()
    .references(() => words.id, {
      onDelete: "cascade",
    }),
  relatedPhraseId: integer("related_phrase_id")
    .notNull()
    .references(() => words.id, {
      onDelete: "cascade",
    }),
});
export const relatedWordsToWordsRelations = relations(
  relatedPhrases,
  ({ one }) => ({
    word: one(words, {
      fields: [relatedPhrases.wordId],
      references: [words.id],
    }),
    relatedPhrase: one(words, {
      fields: [relatedPhrases.relatedPhraseId],
      references: [words.id],
    }),
  })
);

Generated SQL Query
// this is my expected change
CREATE TABLE IF NOT EXISTS "related_phrases" (
        "phrase_id" integer NOT NULL,
        "related_phrase_id" integer NOT NULL
);

// I do not expect the sql queries below
ALTER TABLE "words_attributes" ALTER COLUMN "word_id" DROP NOT NULL;
ALTER TABLE "words_attributes" ALTER COLUMN "attribute_id" DROP NOT NULL;
DO $$ BEGIN
 ALTER TABLE "accounts" ADD CONSTRAINT "accounts_userId_users_id_fk" FOREIGN KEY ("userId") REFERENCES "users"("id") ON DELETE cascade ON UPDATE no action;
EXCEPTION
 WHEN duplicate_object THEN null;
END $$;

DO $$ BEGIN
 ALTER TABLE "pronounciations" ADD CONSTRAINT "pronounciations_user_id_users_id_fk" FOREIGN KEY ("user_id") REFERENCES "users"("id") ON DELETE cascade ON UPDATE no action;
EXCEPTION
 WHEN duplicate_object THEN null;
END $$;

DO $$ BEGIN
 ALTER TABLE "requests" ADD CONSTRAINT "requests_user_id_users_id_fk" FOREIGN KEY ("user_id") REFERENCES "users"("id") ON DELETE no action ON UPDATE no action;
EXCEPTION
 WHEN duplicate_object THEN null;
END $$;

DO $$ BEGIN
 ALTER TABLE "saved_words" ADD CONSTRAINT "saved_words_user_id_users_id_fk" FOREIGN KEY ("user_id") REFERENCES "users"("id") ON DELETE cascade ON UPDATE no action;
EXCEPTION
 WHEN duplicate_object THEN null;
END $$;

ALTER TABLE "words" DROP COLUMN IF EXISTS "related_phrases";
DO $$ BEGIN
 ALTER TABLE "related_phrases" ADD CONSTRAINT "related_phrases_phrase_id_words_id_fk" FOREIGN KEY ("phrase_id") REFERENCES "words"("id") ON DELETE cascade ON UPDATE no action;
EXCEPTION
 WHEN duplicate_object THEN null;
END $$;

DO $$ BEGIN
 ALTER TABLE "related_phrases" ADD CONSTRAINT "related_phrases_related_phrase_id_words_id_fk" FOREIGN KEY ("related_phrase_id") REFERENCES "words"("id") ON DELETE cascade ON UPDATE no action;
EXCEPTION
 WHEN duplicate_object THEN null;
END $$;

ALTER TABLE "accounts" ADD CONSTRAINT "accounts_provider_providerAccountId_pk" PRIMARY KEY("provider","providerAccountId");

Error
error: column "word_id" is in a primary key
    at /home/furki4_4/development/Turkish-Dictionary/node_modules/drizzle-kit/bin.cjs:24545:21
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async PgPostgres.query (/home/furki4_4/development/Turkish-Dictionary/node_modules/drizzle-kit/bin.cjs:25506:21)
    at async Command.<anonymous> (/home/furki4_4/development/Turkish-Dictionary/node_modules/drizzle-kit/bin.cjs:63185:9) {
  length: 102,
  severity: 'ERROR',
  code: '42P16',
  detail: undefined,
  hint: undefined,
  position: undefined,
  internalPosition: undefined,
  internalQuery: undefined,
  where: undefined,
  schema: undefined,
  table: undefined,
  column: undefined,
  dataType: undefined,
  constraint: undefined,
  file: 'tablecmds.c',
  line: '7330',
  routine: 'ATExecDropNotNull'
}

### Expected behavior

The migration SQL queries that contains only my schema changes which wouldn't cause any problem when I prompt push:pg. Last but not least, when I drop generated migrations, and generate a new migration from scratch, it doesn't throw any errors.

### Environment & setup

- WSL <IP_ADDRESS>
- Next.js 13.5.2
- postgres-3.4.3
- node 20.5.0

I have the same issue, if this can help:
New schema
export const rewardTypes = pgTable("reward_type", {
  id: serial("id").primaryKey(),
  name: varchar("name", { length: 64 }).notNull().unique(),
  description: text("description"),
  points: smallint("points").notNull().default(1),
  type: rewardableActionTypes("type").notNull(),
});

export const rewardTypesRelations = relations(rewardTypes, ({ many }) => ({
  users: many(usersToRewards),
  referral_link: many(referralLinks),
}));

export const usersToRewards = pgTable(
  "users_to_rewards",
  {
    user_id: text("user_id").references(() => users.id, {
      onDelete: "set null",
    }),
    reward_id: integer("reward_id").references(() => rewardTypes.id, {
      onDelete: "set null",
    }),
  },
  (table) => ({
    pk: primaryKey({
      columns: [table.reward_id, table.user_id],
    }),
  })
);

export const usersToRewardsRelations = relations(usersToRewards, ({ one }) => ({
  user: one(users, {
    fields: [usersToRewards.user_id],
    references: [users.id],
  }),
  reward: one(rewardTypes, {
    fields: [usersToRewards.reward_id],
    references: [rewardTypes.id],
  }),
}));

Migration file
DO $$ BEGIN
 CREATE TYPE "rewardableActionType" AS ENUM('POPULARITY', 'CONTRIBUTION', 'ACHIEVEMENT', 'TOXICITY');
EXCEPTION
 WHEN duplicate_object THEN null;
END $$;
--> statement-breakpoint
CREATE TABLE IF NOT EXISTS "reward_type" (
	"id" serial PRIMARY KEY NOT NULL,
	"name" varchar(64) NOT NULL,
	"description" text,
	"points" smallint DEFAULT 1 NOT NULL,
	"type" "rewardableActionType" NOT NULL,
	CONSTRAINT "reward_type_name_unique" UNIQUE("name")
);
--> statement-breakpoint
CREATE TABLE IF NOT EXISTS "users_to_rewards" (
	"user_id" text,
	"reward_id" integer,
	CONSTRAINT "users_to_rewards_reward_id_user_id_pk" PRIMARY KEY("reward_id","user_id")
);
--> statement-breakpoint
DO $$ BEGIN
 ALTER TABLE "users_to_rewards" ADD CONSTRAINT "users_to_rewards_user_id_user_id_fk" FOREIGN KEY ("user_id") REFERENCES "user"("id") ON DELETE set null ON UPDATE no action;
EXCEPTION
 WHEN duplicate_object THEN null;
END $$;
--> statement-breakpoint
DO $$ BEGIN
 ALTER TABLE "users_to_rewards" ADD CONSTRAINT "users_to_rewards_reward_id_reward_type_id_fk" FOREIGN KEY ("reward_id") REFERENCES "reward_type"("id") ON DELETE set null ON UPDATE no action;
EXCEPTION
 WHEN duplicate_object THEN null;
END $$;

Error
$ bun run drizzle-kit push:pg
drizzle-kit: v0.20.14
drizzle-orm: v0.30.6

No config path provided, using default path
Reading config file '/Users/v1s10n_4/code/perso/invaded-map/drizzle.config.ts'
error: column "user_id" is in a primary key
    at /Users/v1s10n_4/code/perso/invaded-map/node_modules/drizzle-kit/bin.cjs:24462:21
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async PgPostgres.query (/Users/v1s10n_4/code/perso/invaded-map/node_modules/drizzle-kit/bin.cjs:25423:21)
    at async Command.<anonymous> (/Users/v1s10n_4/code/perso/invaded-map/node_modules/drizzle-kit/bin.cjs:63261:9) {
  length: 102,
  severity: 'ERROR',
  code: '42P16',
  detail: undefined,
  hint: undefined,
  position: undefined,
  internalPosition: undefined,
  internalQuery: undefined,
  where: undefined,
  schema: undefined,
  table: undefined,
  column: undefined,
  dataType: undefined,
  constraint: undefined,
  file: 'tablecmds.c',
  line: '7331',
  routine: 'ATExecDropNotNull'
}

I finally found a way to make the migration work (after several drop-migrate-push and retry) by changing the following:
export const usersToRewards = pgTable(
  "users_to_rewards",
  {
-    user_id: text("user_id").references(() => users.id, {
-      onDelete: "set null",
-    }),
+    user_id: text("user_id")notNull().references(() => users.id),
-    reward_id: integer("reward_id").references(() => rewardTypes.id, {
-      onDelete: "set null",
-    }),
+    reward_id: text("reward_id").references(() => rewardTypes.id)
  },
  (table) => ({
    pk: primaryKey({
+     name: "users_to_rewards_pk",
      columns: [table.reward_id, table.user_id],
    }),
  })
);

I wanted to keep those fields nullable on delete but i guess its necessary as they're used for the composite primary key.
Anyway its a good workaround.

I finally found a way to make the migration work (after several drop-migrate-push and retry) by changing the following:
export const usersToRewards = pgTable(
  "users_to_rewards",
  {
-    user_id: text("user_id").references(() => users.id, {
-      onDelete: "set null",
-    }),
+    user_id: text("user_id")notNull().references(() => users.id),
-    reward_id: integer("reward_id").references(() => rewardTypes.id, {
-      onDelete: "set null",
-    }),
+    reward_id: text("reward_id").references(() => rewardTypes.id)
  },
  (table) => ({
    pk: primaryKey({
+     name: "users_to_rewards_pk",
      columns: [table.reward_id, table.user_id],
    }),
  })
);

I wanted to keep those fields nullable on delete but i guess its necessary as they're used for the composite primary key. Anyway its a good workaround.

thank you dude! I added notNull function like you did and it stopped giving me the error. My columns that caused the error are used in a composite key like yours.


Invalid selectors cause application to crash

Bug report
Describe the bug
My application was crashing with the following errors:
Firefox: DOMException: An invalid or illegal string was specified
Chrome: VM78 react_devtools_backend.js:2560 DOMException: Failed to execute 'insertRule' on 'CSSGroupingRule': the rule '@hoverNone{.c-imFVOV{white-space:nowrap;overflow-x:scroll;padding:var(--space-2) 0}}' is invalid and cannot be parsed
Safari: SyntaxError: The string did not match the expected pattern.
To Reproduce

Define a theme

export const { theme, css, styled, global, getCssString } = createCss({
  theme: {
    colors: {
      background: 'white',
      foreground: 'black',
    },
    space: {
      0: '0',
      1: '0.25rem',
    },
  },
  media: {
    bp1: '(min-width: 40em)',
    bp2: '(min-width: 52.5em)',
    noHover: '(hover: none)',
  },
});

Create a styled component, but use a non-existing media query name

In this example I use @hoverNone, but the right name should be @noHover.
const Subcategories = styled('div', {
  '@bp2': {
    whiteSpace: 'normal',
  },
  '@hoverNone': {
    whiteSpace: 'nowrap',
    overflowX: 'scroll',
    padding: '$2 0',
  }
});

It will crash
Change @hoverNone to @noHover and things are OK.

I found another instance in my application which crashed because we used $ > div instead of & > div in a nested selector.
Expected behavior
Catch the error before the application crashes, and log a warning to the console that some styles could not be applied because you wrote an invalid selector.
System information

OS: macOS
Browser: Firefox 89/Chrome 91/Safari 14.1
Version of Stitches: "@stitches/react": "^0.2.0-canary.4"
Version of Node.js: 14.x on Vercel

Thanks for that. Repro: https://codesandbox.io/s/zen-shadow-xpkce?file=/src/App.tsx

Also happening when adding breakpoints in css prop. Repro: https://codesandbox.io/s/kind-flower-mg04z?file=/src/App.tsx

Another repro: https://codesandbox.io/s/sparkling-http-69zg6?file=/src/components/Playground/index.tsx:342-355

Fixed, will be released in 0.2.1.
Demos:

https://codesandbox.io/s/626-pr-iw7rn
https://codesandbox.io/s/626-pr-norman-hzg40
https://codesandbox.io/s/626-pr-fixed-3p1uy

This is now available in the latest version
npm i @stitches/react@latest


Consider removing env() and config() or making them not load by default

Reason: Use twig to not strictly separate concerns. Like layout authors should not be able to read env or core configuration.

For 4.x they will be loaded by default, with a flag to turn them off. For 5.x that will be reversed. I'll implement this shortly

That's great!

@WyriHaximus Sounds good. Though perhaps in 5.x env should be changed to a function instead of a filter.


issue#111 Create PlantItemViewModel for using it as binding on every plant list item instead of plant and its click listener

The changes of this branch are about creating a view model for wrapping a plant and its click listener and use it as binding instead of having both the plant item and the click listener as bindings. Moreover, this changes let us to take out the logic of click action from adapter and use it only for delegating the user actions to collaborators (in this case the view model)

Would you mind to squash all commits into 99a2c439194bc9783f24919daf4a788b3a51880b which is the first commit of the whole story or second one which is the refinement of the first according to PR review, keep commits clean?

Would you mind to squash all commits into 99a2c43 which is the first commit of the whole story or second one which is the refinement of the first according to PR review, keep commits clean?

They are all squashed into e29828e. I don't know if it's valid to you.

@vjgarciag96 Actually and frankly I want to only keep commits clean and know how many main works are done, for example: feature done, and then refeinment .
Anyway, now the PR looks good and MVVM like. 👍

@XinyueZ ok, if you want I can cherrypick the commit e29828e to another branch to make it cleaner. However, if you want to merge the current branch is also good for me.

@vjgarciag96 I think everything is fine. Because I always rebase after works being down,  i.e run git rebase -i HEAD~7 to keep my commits cleaned, for your case like here 7 to squash all to first commit. Thatz only nice2have.

@XinyueZ ok, perfect then. I didn't understand you at first, but know I understand it and sounds good. Thank you!


Adding a label to the metrics, to allow running two instances in parallel

I've setup two instances of this app on my Kubernetes cluster.  One I'm specifying my ISP's closest server, the other I'm letting the app choose, so that I can monitor within the ISPs network and external to my ISP.  In order for me to split the data in Prometheus I need to have the server ID added to the metric, which is what this PR provides.
Let me know if you'd like any changes to this.

I'll accept it, I think this is a good use for metric labels. Normally I would be concerned about the cardinality, but the number of speedtest servers shouldn't ever grow without bound.
One thing though, can you update the README in this PR as well?
1. https://github.com/jeanralphaviles/prometheus_speedtest#instrumenting-speedtests-with-curl

   * Add the `server_id` labels to these metrics in the example

2. https://github.com/jeanralphaviles/prometheus_speedtest#integrating-with-prometheus

   * Mention that these metrics are labeled with the Speedtest Server ID.

Also there's a typo :)

I'll fix all this, but I also would like to look into cardinality more.  I don't like that this causes multiple "data points" in the graph (breaks/changes in line color) when the server id changes.  It works great if you "hard code" the server ID like I do in one of my deployments.  The more standard method where you don't provide a server id in the command args (the standard usecase) isn't pretty in Grafana with this change.  I think that would be a regression to most folks.

I've something better in that I'll test and put up a PR for.  simpler change, and doesn't impact the normal use case.


[documentation] Document deployment on existing AWS EKS cluster

Related to #935.
To test and document how to deploy to an existing ("local") EKS cluster, I ran through the following steps:
Use (create) base EKS cluster
To get a functioning EKS cluster up and running quickly, I created a cluster and web app based on this tutorial. This cluster is running in it's own VPC with 3 subnets (each in it's own AZ) and there are no node groups. A scenario like seemed like a good place to start from the perspective of an incoming user.
Once this EKS cluster is up, there are still a handful of steps that seem to be required before QHub can be deployed to it:

Ensure that the subnets are allowed to "automatically assign public IP addresses to instances launched into it" otherwise node group can't be launched
Create general, user and worker node groups

Attach Node IAM Role with specific permissions (copied from existing role from previous qhub deployment):
Configure node group being mindful of instance size, attached block storage size and auto-scaling features.

I'm sure there are scenarios where there already exists node groups and they can be repurposed but more broadly it would be nice to make this process a lot more streamlined. Did I overcomplicate this, or are there other ways of handling the QHub deployment without having to add these node groups explicitly?
Deploy QHub to Existing EKS Cluster
Ensure that you are using the existing cluster's kubectl context.
Initialize in the usual manner:
python -m qhub init aws --project eaeexisting --domain eaeexisting.qhub.dev --ci-provider github-actions --auth-provider github --auth-auto-provision --repository github.com/iameskild/eaeaws

Then update the qhub-config.yaml file. The important keys to update are:

Replace provider: aws with provider: local
Replace amazon_web_services with local

And update the node_selector and kube_context appropriately

Once updated, deploy in the usual manner:
python -m qhub deploy --config qhub-config.yaml --disable-prompt --dns-provider cloudflare --dns-auto-provision

The deployment completes successfully and all the pods appear to be running (alongside the existing pods from the web app). The issue is that I can't access the cluster from the browser:
404 page not found

When examining the print statement from the deployment more, you can see that the cluster doesn't have an IP address:
[terraform]: ingress_jupyter = {
[terraform]:   "hostname" = "aea1abf087211438cbf9e44ef5fb64c3-197330438.us-east-2.elb.amazonaws.com"
[terraform]:   "ip" = ""
[terraform]:

qhub-config.yaml

project_name: eaeexisting
provider: local
domain: eaeexisting.qhub.dev
certificate:
  type: self-signed
security:
  authentication:
    type: GitHub
    config:
      client_id:
      client_secret:
      oauth_callback_url: https://eaeexisting.qhub.dev/hub/oauth_callback
  users:
    iameskild:
      uid: 1000
      primary_group: admin
      secondary_groups:
      - users
  groups:
    users:
      gid: 100
    admin:
      gid: 101
default_images:
  jupyterhub: quansight/qhub-jupyterhub:v0.3.13
  jupyterlab: quansight/qhub-jupyterlab:v0.3.13
  dask_worker: quansight/qhub-dask-worker:v0.3.13
  dask_gateway: quansight/qhub-dask-gateway:v0.3.13
  conda_store: quansight/qhub-conda-store:v0.3.13
storage:
  conda_store: 60Gi
  shared_filesystem: 100Gi
theme:
  jupyterhub:
    hub_title: QHub - eaeexisting
    hub_subtitle: Autoscaling Compute Environment on Amazon Web Services
    welcome: Welcome to eaeexisting.qhub.dev. It is maintained by Quansight
      staff. The hub's configuration is stored in a github repository based on
      https://github.com/Quansight/qhub/.
      To provide feedback and report any technical problems, please use the github
      issue tracker.
    logo: /hub/custom/images/jupyter_qhub_logo.svg
    primary_color: '#4f4173'
    secondary_color: '#957da6'
    accent_color: '#32C574'
    text_color: '#111111'
    h1_color: '#652e8e'
    h2_color: '#652e8e'
monitoring:
  enabled: true
cdsdashboards:
  enabled: true
  cds_hide_user_named_servers: true
  cds_hide_user_dashboard_servers: false
ci_cd:
  type: github-actions
  branch: main
terraform_state:
  type: remote
namespace: dev
local:
  kube_context: arn:aws:eks:us-east-2:892486800165:cluster/eaeeks
  node_selectors:
    general:
      key: eks.amazonaws.com/nodegroup
      value: general
    user:
      key: eks.amazonaws.com/nodegroup
      value: user
    worker:
      key: eks.amazonaws.com/nodegroup
      value: worker
profiles:
  jupyterlab:
  - display_name: Small Instance
    description: Stable environment with 1 cpu / 4 GB ram
    default: true
    kubespawner_override:
      cpu_limit: 1
      cpu_guarantee: 0.75
      mem_limit: 4G
      mem_guarantee: 2.5G
      image: quansight/qhub-jupyterlab:v0.3.13
  - display_name: Medium Instance
    description: Stable environment with 2 cpu / 8 GB ram
    kubespawner_override:
      cpu_limit: 2
      cpu_guarantee: 1.5
      mem_limit: 8G
      mem_guarantee: 5G
      image: quansight/qhub-jupyterlab:v0.3.13
  dask_worker:
    Small Worker:
      worker_cores_limit: 1
      worker_cores: 0.75
      worker_memory_limit: 4G
      worker_memory: 2.5G
      worker_threads: 1
      image: quansight/qhub-dask-worker:v0.3.13
    Medium Worker:
      worker_cores_limit: 2
      worker_cores: 1.5
      worker_memory_limit: 8G
      worker_memory: 5G
      worker_threads: 2
      image: quansight/qhub-dask-worker:v0.3.13
environments:
  environment-dask.yaml:
    name: dask
    channels:
    - conda-forge
    dependencies:
    - python
    - ipykernel
    - ipywidgets
    - qhub-dask ==0.3.13
    - python-graphviz
    - numpy
    - numba
    - pandas
  environment-dashboard.yaml:
    name: dashboard
    channels:
    - conda-forge
    dependencies:
    - python==3.9.7
    - ipykernel==6.4.1
    - ipywidgets==7.6.5
    - qhub-dask==0.3.13
    - param==1.11.1
    - python-graphviz==0.17
    - matplotlib==3.4.3
    - panel==0.12.4
    - voila==0.2.16
    - streamlit==1.0.0
    - dash==2.0.0
    - cdsdashboards-singleuser==0.5.7

@viniciusdc would you mind taking a look at this to see if is missed anything? And could you share any qhub-config.yaml that successfully deployed on an existing cluster? Thanks a lot :)

Now that I think of it, this is most likely caused by the fact that this existing web app already has an EXTERNAL-IP set. I will attempt this again with an existing cluster that doesn't already have a public facing IP/ingress.

@viniciusdc would you mind taking a look at this to see if I missed anything? And could you share any qhub-config.yaml that successfully deployed on an existing cluster? Thanks a lot :)

Hi @iameskild, the only qhub-config that I have is for a GCP deployment. The only difference from yours (besides the provider) it that we needed to set the load-balancer configuration to an internal one, but that's because some security policies

Hey @viniciusdc, how did you provision the DNS? From looking reading through the code base, it appears that when deploying to a local (existing) cluster, the update_record for CloudFlare is skipped altogether:
https://github.com/Quansight/qhub/blob/c0d08bbcc08816475bf26466e2d64f9daf03164e/qhub/deploy.py#L108-L119
And that what I see when I deploy:
INFO:qhub.deploy:Couldn't update the DNS record for cloud provider: local

This explains why I can't access the cluster.

I was able to get around this by updating the DNS record manually in the CloudFlare portal 👍

Hey @viniciusdc, how did you provision the DNS? From looking reading through the code base, it appears that when deploying to a local (existing) cluster, the update_record for CloudFlare is skipped altogether:
https://github.com/Quansight/qhub/blob/c0d08bbcc08816475bf26466e2d64f9daf03164e/qhub/deploy.py#L108-L119
And that what I see when I deploy:
INFO:qhub.deploy:Couldn't update the DNS record for cloud provider: local

This explains why I can't access the cluster.

You can work around that, providing the DNS records manually in the namespace right? by providing the certificate's secrets... (I am not sure)

I noticed that a few minutes after posting this 😆  Thanks Vini


CASSANDRA-19534 (5.0 patch): Unbounded queues in native transport requests lead to node instability

Committed as https://github.com/apache/cassandra/commit/617a75843c9bfaf241249514f9604466f6c8ccab


Add the option for an additional EBS volume

As a user of this module, having the option to create a EBS volume in addition to the root volume would be very helpful.
This could be done by adding the following resources:
resource "aws_ebs_volume" "bastion_secondary_ebs_volume" {
  count             = var.enable_secondary_ebs_volume ? 1 : 0
  availability_zone = local.vpc_azs[0]
  size              = 1
  encrypted         = true
  tags              = var.tags
}

resource "aws_volume_attachment" "ebs_attachment" {
  count  = var.enable_secondary_ebs_volume ? 1 : 0
  device_name = "/dev/sdb"
  volume_id   = aws_ebs_volume.bastion_secondary_ebs_volume[0].id
  instance_id = module.bastion.instance_id
}

variable "enable_secondary_ebs_volume" {
  description = "Enable the creation of a secondary EBS volume"
  type        = bool
  default     = true
}

Changes Merged in.


Ignore clang-format if not available

Not sure we should  update this as it is still not in the stable debian release (OK, 3.6 is not either...)

ok.


Protect against state mismatch in the Java View.

setViewport() was holding on to a reference of the client's Viewport
object, which could potentially be mutated after the call. This would
cause a mismatch between the values in getViewport() and the actual
values honored by the native layer.
Similar issues existed for our simple config structs like
DynamicResolutionOptions, but I fixed these by making them immutable
since clients are not likely to hold on to them.

Woops this was horribly wrong :)


Stable/copper

@cekees just creating this pr to compare files, no need to merge. We (me and @tridelat) have some issues in copper with messages regarding -fPIC option and relocation errors for scipy and grib_api

@cekees no changes there so I am going to close it


How does page speed collect LCP value when there is no timing-allow-origin?

If the image resource has no timing-allow-origin header, will the LCP value be the loadTime or does page speed have its way to get renderTime?

No we only have the loadTime, which can lead to some issues like https://github.com/GoogleChrome/web-vitals/issues/369#issuecomment-1636820858

Note that the Chrome User Experience Report (CrUX) does not have this constraint and so the CrUX data surfaced in tools like PageSpeed Insights will have the correct LCP time.
This is one difference between CrUX and RUM (including web-vital.js): https://web.dev/crux-and-rum-differences/#cross-origin-resources

Note that the Chrome User Experience Report (CrUX) does not have this constraint and so the CrUX data surfaced in tools like PageSpeed Insights will have the correct LCP time.
This is one difference between CrUX and RUM (including web-vital.js): https://web.dev/crux-and-rum-differences/#cross-origin-resources

Thanks! The page you provided is helpful.


can't start vscode x64 version in win7 x64, but x86 can.

Issue Type: Bug
just start vscode by double click the Code.exe.
VS Code version: Code 1.28.0 (431ef9da3cf88a7e164f9d33bf62695e07c6c2a9, 2018-10-04T16:47:36.731Z)
OS version: Windows_NT ia32 6.1.7601

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3 CPU       M 380  @ 2.53GHz (4 x 2527)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: unavailable_softwarevideo_decode: unavailable_softwarevideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
3.87GB (0.23GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (9)

Extension
Author (truncated)
Version

vscode-eclipse-keybindings
alp
0.9.8

vscode-eslint
dba
1.6.0

auto-close-tag
for
0.5.6

auto-rename-tag
for
0.0.15

svn-scm
joh
1.43.0

vscode-language-pack-zh-hans
MS-
1.28.2

debugger-for-chrome
msj
4.10.2

vscode-docker
Pet
0.3.1

LiveServer
rit
5.1.1

You're not meant to be able to start the 64 bit version on 32 bit Windows.

I mean that it can't start the 64 bit version of vscode on 64 bit Windows 7, but the 32 bit version of vscode can start on 64 bit Windows 7.

The version of x64 windows 7  is recognized as Windows_NT ia32 6.1.7601 but x64 windows 10 Windows_NT x64 10.0.17134, but I don't know why.

Try running code --verbose on the 64-bit version  and see what the output is.

I just ran code --verbose, but nothing happened.I think the code recognizes the windows as x86 arch, so nothing to start. And I noticed that sombody else also encounterd similar situations.

when I use the depends.exe to display the dependences of Code.exe, just show the error info below:


creating oprudkyi/laravel-bootstrap-adminlte-starter-kit

getting the following error
(HTTP code 404) unexpected - {"message":"manifest for oprudkyi/laravel-bootstrap-adminlte-starter-kit:latest not found"}

Go to https://hub.docker.com/r/oprudkyi/laravel-bootstrap-adminlte-starter-kit/tags/
Observe no latest tags were created for that image
Select a different tag in Kitematic
🎉  enjoy container running.

Ideally you open an issue with the repo owner to let them know how frustrating it is that they don't have a latest image tagged


Margriet updates

added lines as suggested in comments of issue #507

Closing this pull request as there are no code change


<EMAIL_ADDRESS>hash check failed

I believe that cmder has update but the has has not been updated in scoop bucket.

Transient error.  Closing.


exec user process caused: exec format error

kubectl apply -f https://raw.githubusercontent.com/zilliztech/milvus-operator/main/deploy/manifests/deployment.yaml
vecdb@pve-223-x86:~/milvus-install$ kubectl get pods -n milvus-operator
NAME                               READY   STATUS              RESTARTS   AGE
milvus-operator-68c6964984-vhn9w   0/1     ContainerCreating   0          5m14s
milvus-operator-checker-q2v87      0/1     CrashLoopBackOff    5          5m14s
vecdb@pve-223-x86:~/milvus-install$ kubectl logs milvus-operator-checker-q2v87 -n milvus-operator
standard_init_linux.go:228: exec user process caused: exec format error
vecdb@pve-223-x86:~/milvus-install$

milvusdb/milvus-operator not support arm64 ?

milvusdb/milvus-operator not support arm64 ?

https://milvus.io/docs/prerequisite-helm.md ?

milvusdb/milvus-operator not support arm64 ?

milvus.io/docs/prerequisite-helm.md

As far I am aware, the list of CPU instructions listed as requirements are all x86 exclusive:

SSE4.2
AVX
AVX2
AVX-512

This can be observed on the list of supported architectures in the Docker hub image tag page.

milvusdb/milvus-operator not support arm64 ?

milvus.io/docs/prerequisite-helm.md

As far I am aware, the list of CPU instructions listed as requirements are all x86 exclusive:

SSE4.2
AVX
AVX2
AVX-512

This can be further observed on the list of supported architectures in the Docker hub image tag page.

add nodeSelector

@lysShub Hi, Arm image is in beta, if you want to try out, search for "arm" in milvus' dockerhub repo to find beta images.


Fixes/1448

Seprated InvalidateMeasure out from InvalidateFormattedText.
In this way whoever needs both the feature, calls then explicitly.
Now TextPresenter's subscriber for SelectionStart/End doent invalidate measure,
since it should only focus on invalidate formatted text
Fixes #1448

Thanks @achal7!

In commit bc3d6ec8 still having problem with selected text for CenterAllignment and RightAllignment.
I have a fix which looks like crutch. In Avalonia.Skia.FormattedTextImpl, method Draw, after string "float x = TransformX(origin.X, 0, paint.TextAlign);" add this:
if (paint.TextAlign != SKTextAlign.Left)
{
    var measure = paint.MeasureText(Text);

    x -= paint.TextAlign == SKTextAlign.Center
        ? measure / 2
        : measure;

    paint.TextAlign = SKTextAlign.Left;
}

I think problem in canvas.DrawText, when using several brushes


build(deps): bump fastlane deps & sentry cli

This PR resolves []
Description
bumps fastlane deps & sentry cli

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

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

bump fastlane deps & sentry cli - gkartalis

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

This PR contains the following changes:

Dev changes (bump fastlane deps & sentry cli - gkartalis)

  Generated by :no_entry_sign: dangerJS against 925054969b3baeb8ec53a1abeb794075f3a56d8b


[Bug] Fix the bug about flink version don't be changed when flink home is changed

What problem does this PR solve?
Issue Number: close #1566
Problem Summary:
Flink version don't be changed when flink home is changed
What is changed and how it works?
Proposal: code
Feel free to ping committers for the review!
Contribution Checklist

Make sure that the pull request corresponds to a GITHUB issue.

Name the pull request in the form "[Feature] [component] Title of the pull request", where Feature can be replaced by Hotfix, Bug, etc.

Minor fixes should be named following this pattern: [hotfix] [docs] Fix typo in README.md doc.

Purpose of this pull request
Fix the bug about flink version don't be changed when flink home is changed

Thanks for you feedback, @1996fanrui
@wolfboys PTAL.

@lvshaokang @wolfboys Thanks for your review~


timeout settings

Timeout settings seems not so reliable.
Trying to generate a big document (close to 600 pages),
I have set a timeout of 30000000 like this:
export PUPPETEER_DEFAULT_TIMEOUT=30000000
export PUPPETEER_RENDERING_TIMEOUT=30000000
export PUPPETEER_NAVIGATION_TIMEOUT=30000000
But I get a timeout error after 2minutes, 38 seconds.

The preview mode shows the document with no error in the console.
Dividing the document into three result in no errors when generating each of the three documents.
I can't share the document to reproduce the case, sorry.

I believe it's the same issue as https://github.com/Mogztter/asciidoctor-web-pdf/issues/612.
Previously, the printToPDF function was using a default timeout of 30s. When https://github.com/Mogztter/asciidoctor-web-pdf/commit/643d5548bc9953e592957ccc356162b8523ab672 will be released, you will be able to set PUPPETEER_PRINT_TIMEOUT (or PUPPETEER_DEFAULT_TIMEOUT) to increase this value.

Fixed in the latest release: https://github.com/Mogztter/asciidoctor-web-pdf/releases/tag/v1.0.0-alpha.16


HLint Skip the Main Function Check

I knew that HLint is a tool for code improvement in Haskell. It would be great if HLint check the main function first then suggest a code improvement. Please take a look on this issue on coala HaskellLintBear.

The idea is that you run your code through the compiler first. HLint doesn't attempt to catch errors.

I see...
In the future, is it possible to implement this one on HLint?

Hlint can already dump errors to JSON. However, it can't do anything relating to GHC errors.

The idea is that you run your code through the compiler first. HLint doesn't attempt to catch errors.

If that's the case you should improve the message to suggest this imo. Otherwise I would think that hlint would do this itself as a linter at least to some degree (like it has some syntax error detection to avoid weird parsing errors).

The code you wrote isn't a syntax error, and with suitable libraries, you could even make it do what you are expecting. Only a compiler knows it isn't correct.

That's why I suggest to extend the message to something like this: :smile:

Check Haskell code for possible problems by running the Haskell compiler again.

Are you suggesting I extend the message when HLint has nothing to report to also say "beware, you might want to compile your code too"? I would have thought that was obvious given the intended audience... Maybe if that's suitable for users of HaskellLintBear then it should be adding that message? Or perhaps even actually compiling the code with GHC before running the linter (certainly Haskell IDE's do that).

It's all clear for me now, @ndmitchell. Thank you!
Are you still on this, @Makman2?

Are you suggesting I extend the message when HLint has nothing to report to also say "beware, you might want to compile your code too"?

Oh man sorry my bad... I've totally misunderstood the original issue (https://github.com/coala/coala-bears/issues/2011). The phrase Check Haskell code for possible problems is our documentation of HaskellLintBear.py, I thought this message was emitted by our bear running over some Haskell code with hlint.
Nvm then :+1:

Or perhaps even actually compiling the code with GHC before running the linter (certainly Haskell IDE's do that).

Yeah that's something we have to consider from coala-side :)


Improve assertion failure message for contain to print the JSX string…

… of the expected value

Thanks for your contribution, it's greatly appreciated

👍

lgtm

Merged, thanks for your contribution!


Finalize URI/IRI resource id (RID?) library

Adding oascomply.resourceid and its various URI/IRI-related classes dramatically simplified things.  Some ideas for finalizing this module in M2 (see also #34 for context):

oascomply.rid is probably the ideal module/subpackage name given that I kept doing import oascomply.resourcied as rid (there are too many URI/IRI classes across at least 4 dependent libraries involved in oascomply to have the class names unqualified)
although if this is to be split out, then probably uri_iri or something else a bit more obvious would be better than rid 🤔
The WithJsonPtr functionality should probably be handled with a mixin adding a ptr or jsonptr or ptrfrag or something property rather than with compounding multiple inheritance and overloading the fragment property
Is it worth trying to associate media types and fragments in some way?  To allow indicating the media type rather than selecting the fragment syntax directly?
Scheme-specific validation should also be a mixin if additional properties (e.g. URN q-component, r-component) are needed
Consider scheme-specific normalization handlers that can be registered; include file:/ vs file:/// in this; note that normalization is mostly outside of the scope of this project, and aside from file authorities, would be left for future contributions
Query format handlers (e.g. x-www-form-urlencoded) are probably also mixins, as they would add properties (consider also that urn: would need to apply this to both q- and r-components, I think ?)
It's worth considering if some mixin ideas could be handlers instead - otherwise, the subclasses are likely to proliferate to handle all sorts of combinations

Note that furl also looks promising, but it does automatic encoding (including of IRIs down to URIs).  It does, however, catch the double-port error unlike many libraries.  Might be worth considering.  It seems very full-featured and might do too much processing up front, though, given how heavily this will get used.

The furl authors also have an orderedmultidict package that looks worth using for x-www-form-urlencoded query strings whether furl is worth using for oascomply or not.

Further thoughts:

Constructors just parse using rfc3987.parse(), but don't do anything else (possibly unless passed specific parameters)
Have an rid.global_config() or similar function that determines what validations are performed and other features enabled when...
...Class.validate() is called, which returns a validated instance of Class (where Class is one of Iri, IriReference, Uri, UriReference)
It should probably be possible to perform validations manually after construction, but it might end up being better to just handle validations as constructor parameters - use case for incremental validation unclear

rfc3987.parse() already does the fundamental syntax validation.  rid.global_config() would enable things like scheme-specific validations; the cost of checking the global config can by bypassed by just calling the constructors directly
Also, unless the global config mandates some level of pre-parsing, additional parsing is not done unless/until properties are accessed.  So all classes might have a jsonptr property for JSON Pointer fragments, but it will only attempt to build a JsonPtr instance if accessed.  Likewise, q_component and r_component properties will raise errors unless the scheme is urn (it's an open question as to how many properties to add for various URI schemes, but the general philosophy is "make them all available and assume the caller will use them correctly")

rfc3987 cannot be used due to GPL.  For now, we will use jschon's URI class, which is backed by rfc3986, as it is adequate and will make things consistent.  jschon has agreed to adopt a better URI/IRI class if/when one is available, which is something I will work on separately from this project.  But will help this project when it is fixed upstream.

The rfc3987 library has been removed on the m2 branch


sqs: send_message_batch doesn't validate group ID for FIFO queues

Hello,
When putting a message into a FIFO queue, the MessageGroupId is mandatory. While moto checks it for messages sent one at a time, it looks like there is no check for batch sends.
The PR that introduced the check on send_message() doesn't seem to have done so for send_messages() too.
Failing unit test on fe7430b36:
diff --git a/tests/test_sqs/test_sqs.py b/tests/test_sqs/test_sqs.py
index 3fe2e025..977a3165 100644
--- a/tests/test_sqs/test_sqs.py
+++ b/tests/test_sqs/test_sqs.py
@@ -2569,6 +2569,20 @@ def test_send_messages_to_fifo_without_message_group_id():
     ex.response["Error"]["Message"].should.equal(
         "The request must contain the parameter MessageGroupId."
     )
+    with pytest.raises(Exception) as e:
+        queue.send_messages(
+            Entries=[
+                {
+                    "Id": "id_1",
+                    "MessageBody": "body_1",
+                },
+            ]
+        )
+    ex = e.value
+    ex.response["Error"]["Code"].should.equal("MissingParameter")
+    ex.response["Error"]["Message"].should.equal(
+        "The request must contain the parameter MessageGroupId."
+    )

 @mock_logs

Thanks for raising this and providing the test case @yveoch!


[theme] CSP implementation with new style system using @emotion

There is no way to provide CSP nonce to StylesProvider
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'self' 'nonce-h3zjTDbRfKct'". Either the 'unsafe-inline' keyword, a hash ('sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU='), or a nonce ('nonce-...') is required to enable inline execution.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
Material UI used(using) jss as styling solution which read meta[property="csp-nonce"]. Now it can be configured in @emotion/cache but cache is created in StylesProvider.
Expected Behavior 🤔
StylesProvider should accept nonce as a parameter or read from meta[property="csp-nonce"]
Steps to Reproduce 🕹
Code sample with no CSP nonce provided (check developer console not codesandbox)
Code sample with nonce and works
Context 🔦
Implement a new Material UI styling system with the existing system.

Any browser.

@povilass Each styling solution seems to do it differently:

sc look into what webpack provides and that's it. Programmatic support is https://github.com/styled-components/styled-components/issues/2363 but it's not very secure (webpack value doesn't change between two requests)
emotion has an option to provide to the cache, and that's it https://emotion.sh/docs/@emotion/cache#nonce
jss looks into a header: https://cssinjs.org/csp?v=v10.5.0 (<meta property="csp-nonce" content="{{ styleNonce }}">).

We should probably improve the documentation. As for making a change to the underlying implementation, I'm not sure we have much room for freedom.

I think problem is a lack of documentation how to do it. I am looking at @material-ui/core which exports StylesProvider with default implementation, but now I can not pass nonce to cache configuration and recreate same configuration all over again
function StylesProvider(props: any) {
    const { children } = props;
    // Cache with option to prepend emotion's style tag
    const cache = createCache({ key: 'css', prepend: true, nonce: getNonce()});
    return <CacheProvider value={cache}>{children}</CacheProvider>;
}

@povilass I've tried to add in the section for the CSS injection, that if you are using custom cache for emotion, you need to add the prepend option - https://next.material-ui.com/guides/interoperability/#css-injection-order

Maybe we should make this more visible and add it somewhere else?

The problem is not how to implement nonce itself but just your StylesProvider accepts injectFirst which adds emotion cache but I can't pass any other cache properties if this is enabled? @oliviertassinari

Regarding this, I'd say for more advanced usages, it is expected that clients will create their own cache (note that if you are not using emotion, none of these options would make sense at all).

@mnajdova ok gonna start from the beginning. Currently we using Typography migrated to emotion after this change I had to add StyleProvider with injectFirst otherwise all my styles are put in wrong order.
Not working codesandbox
Not working also codesandbox
working codesandbox but how to pass to style provider nonce ?

I don't want to create my emotion cache

@povilass Why not?

Maybe we should make this more visible and add it somewhere else?

@mnajdova Considering https://next.material-ui.com/guides/content-security-policy/ is broken in v5, we might want to start there.

Yes I know how to implement CSP all steps are fulfilled in v4 documentation, but I expected that CSP won't be broken in v5 with emotion because it is kinda breaking change for me also. @oliviertassinari

@povilass Ok, so your concern is about making the migration easier.
@mnajdova Considering developers migrating will have to use StylesProvider or StyledEngineProvider is we rename it. Maybe it's an opportunity to:

emotion:

Read the head to search for <meta property="csp-nonce" content="this-is-a-nonce-123" />
Read the window to search for __webpack_nonce__ , e.g.  getNonce.
If any of the two exists, provide it to emotion's cache

sc:

Do nothing as I doubt many developers will make the effort to switch

@oliviertassinari I think you do not need to implement nonce search, emotion already giving us how to do it. Problem is how to pass it to StyledEngineProvider with existing cache. If someone implements custom cache so they have to provide it themself.


DPO 🤝 FSDP2

The what and the why
We have started migrating our recipes onto FSDP2 APIs, as they offer better composability with torch compile, quantization APIs, frozen/unfrozen weights, and more. See the original PyTorch RFC for more details: https://github.com/pytorch/pytorch/issues/114299.
Thus far we migrated our full finetune recipe in #1287, and we already have a LoRA recipe on FSDP2 that just needs to be moved out of our dev/ folder.
This issue is to track migration of our DPO recipe onto FSDP2, which is the last remaining piece to get us fully onto FSDP2.  We can also clean up stuff like this, which screws with compile.
The how
This can be done by following the lora_finetune_fsdp2 recipe. The most important changes will be in the _setup_model method. As in that recipe, we need to:

instantiate the model on meta device (ref)
set trainable params and define the activation checkpointing strategy (ref)
iterate over submodules from lowest to highest, sharding as we go. #1287 introduced the shard_model utility, which is applied for full finetune here. The only difference for the DPO recipe is that we will need to add one extra condition to shard the LoRA A and B params (as done here in the LoRA FSDP2 recipe)
load LoRA weights if provided (ref)
perform custom initialization of any parameters that need it (RoPE buffers and optionally LoRA weights) (ref)
load the base model weights (ref)

Testing: This is one of our only recipes without CI 😢. We should run the recipe before and after the changes on a couple different models to ensure (a) it works, (b) loss curves are unchanged, and (c) memory and perf are comparable.

Are we/have we updated the QAT recipe or are we deprecating?

@SalmanMohammadi just merged #1330 so our QAT recipe is now in FSDP2


Small file uploads are not handled properly by Apex

As reported at https://groups.google.com/forum/#!topic/vertx/X_n6e8PIoEo Apex does not properly handle small files in multipart uploads - while large buffers (> 8000 bytes) seem to be handled properly, smaller ones just lead to a timeout or other failure.
This is demonstrated by the project at https://github.com/millross/apex-small-file-failure which basically rips out a test from BodyHandlerTest within the Apex repository, and modifies it so that two near-identical tests can be run, only differing in the file size uploaded. The one with the small buffer fails, the one with the larger buffer succeeds.
Please review the reproducer and provide feedback if the code is wrong, or look into the problem. If I diagnose the problem I'll attach details to this issue.

Just as an FYI, writing an equivalent test in vert.x raw http handling (rather than wrapped by Apex) behaves properly, so the problem lies within Apex somewhere.

This looks like a race condition to me. Did a little bit of debugging, and it's clear that with both a small and large file attachment, HttpServerRequestImpl::streamToFileSystem is called. This method pauses the request and then resumes it once the Pump to file has been set up.
For a small file, however, the resume call happens AFTER HttpServerFileUpload::complete() is called, meaning that at the point the latter method is called, the request is still paused. For a larger file, HttpServerFileUpload::complete() is called before the resume call within HttpServerRequestImpl::streamToFileSystem, so in effect a small file upload is identified as complete before the request is resumed. This then falls foul of the "paused" check in HttpServerFileUpload::complete() and the notifyEndHandler() call is not made, meaning that the request does not complete on the server. In short this actually appears to be a vert.x bug rather than an Apex bug.

Thanks for looking into this.
I'll take a look probably tomorrow, if you can create a reproducer only using Vert.x (not Apex) even better :)

Thanks Tim, I'll try and carve out some time today to create a vert.x only reproducer, can't promise it though as I'm a bit stuck for time till Thurs now.

This should be fixed now (bug in vertx-core). I've also added some more tests.


Kernel panic using live streamer on Mavericks

Hi,
I don't know if it happens only to me, but I often get kernel panics on a macbook pro 15 with Mavericks using live streamer.
I would say it happens once every 20 times I use it, and it happens only when live streamer is running.
Here's the stack trace that I get after rebooting.
http://pastebin.com/SHjqYh8v
Thanks for the excellent work!

The log doesn't tell me much, but I think this is more likely to be an issue caused by the actual video playback rather than Livestreamer itself.
Perhaps this is helpful: https://support.apple.com/kb/PH14063?locale=en_US

I don't know about that, I usually stream with VLC other network streams and I never had this happened to me.
I just reported in case there were others with this problem. Thanks.


Delegatable credentials CDD scheme

Signed-off-by: lovesh<EMAIL_ADDRESS>

@mikelodder7 @dhuseby The build terminates as there are some tests that can take minutes to complete (long chains of credentials). Can we increase this timeout?

@mikelodder7 @dhuseby The build terminates as there are some tests that can take minutes to complete (long chains of credentials). Can we increase this timeout to 15 minutes?

I'm not sure. We're using Travis-CI and Appveyor free services. There might be a way to do that. Let me look.

@mikelodder7 @dhuseby The build terminates as there are some tests that can take minutes to complete (long chains of credentials). Can we increase this timeout to 15 minutes?

I'm not sure. We're using Travis-CI and Appveyor free services. There might be a way to do that. Let me look.

@mikelodder7 @dhuseby The build completes successfully when I run the tests in release mode (cargo test --release). Are you opposed to always running the tests in release mode? The downside would be not getting a stacktrace that is as helpful as the debug mode's but one can debug the failing test on his local machine unless the failure is intermittent.

I think the reason for the recent failure of the build is the version mismatch. Going to fix it soon.


TOC links should be displayed in a way that makes it clear they are links.

Maybe we could make them bold?

Fixed


Request for phi 3 support

Hi, kindly add the support for phi 3 too.

https://huggingface.co/microsoft/Phi-3-mini-4k-instruct
Model link

Hi! Thanks for the suggestion! We are actually currently working on it as of now. Expect to see phi 3 support hopefully next week. 🙏

Sure thanks.


search function doesn't work in SQlite db connection

When using SQlite db, the search function doesn't work. SQlite doesn't support the concat() and I'm getting "SQLSTATE[HY000]: General error: 1 no such function: CONCAT (SQL: SELECT count(*) AS c FROM (select * from (select "users"."id", ..."

Ok thanks for opening this issue... I will try to fix this ASAP...

yes i have same problem with mysql.AJAX error and I fix it with replace line 202:
from : $this->filter_count = DB::select($sql_str, $sql_bindings_params)[0]->c;
to: $this->filter_count = DB::select($sql_str, [$query_search_value])[0]->c;

Latest release is now available:
https://packagist.org/packages/syamsoul/laravel-datatable-ssp#3.1.1
https://github.com/syamsoul/laravel-datatable-ssp/releases/tag/3.1.1


Best Practice Question

Question in regards to creating http.DefaultClient or http.DefaultTestNetClient instances to submit transaction in a microservice...If I'm using GoKit, should I create one client for the Service to use for all transactions (like in a struct), or should a new client be created for each transaction submission in a method on the Service?
My question pertains to concurrent requests for transactions coming in and if the client will block until each current transaction completes...I'd like to create a single client for the Service, but I know clients with Postgres has thread pools where a client can be grabbed from the pool. Does Stellar client work the same way or am I better off instantiating a new client for every transaction?
Looking at the code in client.go, I'm not seeing any Go routines or channels for handling concurrency, so my guess would be create a new client for every transaction, but just wanted to confirm.

I'll answer my own question: it actually doesn't matter whether you instantiate one or multiple clients, however submitting multiple transactions from an account whether via one or multiple clients will encounter horizon errors for being out of sequence. Basically, its not guaranteed the ordering of transactions that reach the horizon API, so if the sequence are out of sync, then Horizon will reject the majority of the transactions and allow only one transaction to pass through. In order to solve this issue, you need to use payment channels. Below is an example:
https://www.lumenauts.com/blog/boosting-tps-with-stellar-channels


Feature/refactor poetry

Refactor as a package so that it can be called by other python code/script easily.
(Also added support for poetry)

I did the changes for my convenience. If you prefer the current code structure, i'm also fine :)


Error when inserting user: Invalid FamilyName

The following code returns the error Invalid Given/Family Name: FamilyName:
var service = google.admin('directory_v1');
service.users.insert({
  auth: oauth2Client,
  name: {
    givenName: 'John',
    familyName: 'Doe',
  },
  password: 'testtest123',
  changePasswordAtNextLogin: true,
  primaryEmail<EMAIL_ADDRESS>
}, function(err, response) {
  if (err) {
    console.log(err);
  }
  console.log(response);
});

I looked deeper into the code and I logged the request being made and I see the parameters are being converted into a query string.
/admin/directory/v1/users?name%5BgivenName%5D=John&name%5BfamilyName%5D=Doe&password=testtest123&changePasswordAtNextLogin=true&primaryEmail=johndoe%40mydomain.com
I then changed the code locally so that the parameters were posted as JSON instead of a query string and the request was successful.
I think the possible fixes to this issue could be either:

Fix the Google Admin API to handle name[givenName] and name[familyName] correctly in the queryString.
Or post parameters as JSON instead of using a query string.

Change your code to the following to make it work:
service.users.insert({
  auth: oauth2Client,
  resource: {
    name: {
      givenName: 'John',
      familyName: 'Doe',
    },
    password: 'testtest123',
    changePasswordAtNextLogin: true,
    primaryEmail<EMAIL_ADDRESS>
  }
}, ...);

thanks @jmdobry, works perfectly now :)

@jmdobry I'm sorry but this error still happens to me. Using version 26.0.1
  var service = google.admin('directory_v1');
  service.users.insert({
    auth: auth,
    resource: {
      name: {
        givenName: 'John',
        familyName: 'Doe',
      },
      password: 'testtest123',
      changePasswordAtNextLogin: true,
      primaryEmail<EMAIL_ADDRESS>    },
    headers: {
      mimeType: 'application/json'
    }
  }, ...
)

The API returned an error: Error: Invalid Given/Family Name: FamilyName

When using API explorer this request works but I can clearly see it's being sent as JSON in the body.

Any solution to this error? I faced it too.
-Ville

@VilleKuhlman
This is the code I'm currently using (in a Zapier task, but that's irrelevant) and it works
const { auth } = require('google-auth-library');

const createUser = (z, bundle) => {
  const keys = require('keys.json');
  const jwtClient = auth.fromJSON(keys);
  jwtClient.scopes = ['https://www.googleapis.com/auth/admin.directory.user'];
  jwtClient.subject =<EMAIL_ADDRESS>  const newPassword = generatePassword(...);

  return jwtClient.authorize().then(function() {
    return new Promise(function(resolve, reject) {
      jwtClient.request({
        url: 'https://www.googleapis.com/admin/directory/v1/users',
        method: 'POST',
        headers: {
          // 'Mime-Type': 'application/json',
          'Content-Type': 'application/json'
        },
        data: JSON.stringify({
          name: {
            givenName: bundle.inputData.first_name,
            familyName: bundle.inputData.last_name,
          },
          password: newPassword,
          changePasswordAtNextLogin: true
          primaryEmail: bundle.inputData.email.toString().trim()
        })
      }, function(error, response) {
        if(error)
          reject(error.errors[0]);
        else
          resolve(response);
      });
    });
  }).then(function(response) {
    return {
      email: response.data.primaryEmail,
      password: newPassword
    };
  }).catch(function(error) {
    return {
      error: error.message
    };
  });
};

As you can see I'm using google-auth-library instead of this one as I couldn't find a single working example and the other one works pretty well.

Ok thank you - I shall give this a try,
I cant understand why they can't get their documentation updated..


Improve the overview with the examples dependencies

To better navigate through examples, we need one or more scalable visualizations.

Initial version showing the code as tooltip:


Multi path is not working for 11.4 beta 3 devices

In particular this issue was closed, but beta 3 specifically is not working all the other betas are, for 15F5061e devices the multi path is not patched on this particular beta.

#14


Driver: look for the runtime object in the SDK

The runtime object is for the host, and is part of the SDK.  If -sdk
is passed, look for the runtime support object relative to the SDK root.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test and merge

@swift-ci please test

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 945917ce4ca3011fa40505a93ffcf995687dcbb1

I think you mean "target", not "host".

…although in the future I don't know if we really want to assume "using a non-Darwin SDK" = "cross-compiling".

"target" is the wrong term, "host" is what the binary will run on.  "target" is only used when cross-compiling a non-cross-compiling compiler.  This is the de-facto terminology used across most Unices: https://www.gnu.org/software/automake/manual/html_node/Cross_002dCompilation.html
Your second point cannot be over-stressed.  This is purely intended as a temporary workaround.  The problem is that the change to look for the libraries in the SDK was reverted and I am just waiting on that to go back in as that would allow us to drop that invalid condition.  I didn't want to break the Darwin target, but I agree that it is incorrect.

CC: @brentdax - you may also care about this since you are doing something related to this on the Darwin side.  LMK if we can co-ordinate somehow on this.

"Target" is the right term because "target" is the compiler flag (and terminology), and since all three of "build", "host", and "target" are in play for a compiler.

target is the flag, though the value of the flag is host as that is what the generated builds run on.  Quoting from the reference:
--host=host
        The system where built programs and libraries will run.

--target=target
    When building compiler tools: the system for which the tools will create output.

Correct, when building compiler tools.  In fact, even when building the compiler, host/build are the correct term.  The "target" is there fore the case that you are cross-compiling a non-cross-compiling compiler.  That is, you are building clang on x86_64 for ARM64 which will only build binaries for ARMv7.  In such a case, the build is x86_64, the host is aarch64, and the target is armv7.  In general, when you are compiling any standard package, the terms are build/host.

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 945917ce4ca3011fa40505a93ffcf995687dcbb1

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 945917ce4ca3011fa40505a93ffcf995687dcbb1

Build failed
Swift Test Linux Platform
Git Sha - e96e7cc190388f316789911bb511881770c43214

@swift-ci please test Linux platform

Build failed
Swift Test Linux Platform
Git Sha - e96e7cc190388f316789911bb511881770c43214

Please test with following PRs:
apple/swift-lldb#1829
@swift-ci please test Linux platform

I'm going to merge this for now.  I really want to iterate on this a bit more, the !Darwin bit of that check really doesn't sit well with me.

Hello,
When making Cross Compilation for Android on macOS Host I have to provide -sdk flag (-sdk /usr/local/ndk/platforms/android-24/arch-arm).
Without -sdk flag there will be following compile error:
/usr/local/ndk/toolchains/llvm/prebuilt/darwin-x86_64/lib/gcc/arm-linux-androideabi/4.9.x/../../../../arm-linux-androideabi/bin/ld.gold: error: cannot open crtbegin_dynamic.o: No such file or directory
/usr/local/ndk/toolchains/llvm/prebuilt/darwin-x86_64/lib/gcc/arm-linux-androideabi/4.9.x/../../../../arm-linux-androideabi/bin/ld.gold: error: cannot open crtend_android.o: No such file or directory

But With -sdk flag (-sdk /usr/local/ndk/platforms/android-24/arch-arm) I am getting another error:
clang: error: no such file or directory: '/usr/local/ndk/platforms/android-24/arch-arm/usr/lib/swift/android/armv7/swiftrt.o'

In this case path to swiftrt.o incorrect: /usr/local/ndk/platforms/android-24/arch-arm/usr/lib/swift/android/armv7/swiftrt.o
Now I am thinking how to solve this error :)
Is -sdk flag can't point anywhere except Swift SDK (which include file swiftrt.o)?
Thank you!

@vgorloff there's a lot of discussion about what -sdk should mean and should do in the forums thread https://forums.swift.org/t/swift-linux-layout-considerations-aka-linux-is-difficult-lets-go-shopping/27400/2. IIRC, as things are right now, for Android, one might need to pass -sdk pointing to the Swift SDK, and some combination of -Xclang-linker -sysroot -Xclang-linker /foo/bar and -Xcc ... to point to the Android NDK. Look in #26366 for the changes needed for the test suite to run. It might give you a clue.

Thank you!
Usage of the flags -Xclang-linker and -Xcc helped to solve issue.


Reuse the destination narrow logic when uploading images

Fixes #3130
Extract the code in ComposeBox => handleSend() that determines
the destination narrow to getDestinationNarrow(). Use this function
to pass the narrow to ComposeMenu which then uses that value when
uploading an image.

Added a commit to remove getNarrowToSendTo and renamed the narrow prop in ComposeMenu to destinationNarrow.

Hmm, this isn't right, in that first commit:
compose menu: Cleanup unused `getNarrowToSendTo` selector

We are not currently using it, and the logic was always a bit flaky.

We definitely are -- in fact the selector's result is replacing the narrow prop that the parent passes in. And when the narrow that's passed in is a stream narrow, that's important.

You are right, I swapped the order of the two commits a bit too hastily.
Now reverted back.
After the Reuse the destination narrow logic when uploading images commit, the getNarrowToSendTo selector is now not needed.

Sounds good! I think you didn't push the new version, though :wink:

Ha, indeed. Pushed.

Thanks!
Hmm, the first commit does two or three things now, and one is it "renames" the narrow prop of ComposeMenu... but there's still a connect call passing narrow. That feels a bit off.
And in fact Flow gives an error at that commit:
Cannot create ComposeMenu element because ST [1] is not a React component.

     src/compose/ComposeBox.js
     303│         />
     304│         <View style={styles.composeBox} onLayout={this.handleLayoutChange}>
     305│           <View style={styles.alignBottom}>
     306│             <ComposeMenu
     307│               destinationNarrow={this.getDestinationNarrow()}
     308│               expanded={isMenuExpanded}
     309│               onExpandContract={this.handleComposeMenuToggle}
     310│             />
     311│           </View>
     312│           <View style={styles.composeText}>
     313│             {this.getCanSelectTopic() && (

     flow-typed/npm/react-redux_v5.x.x.js
 [1] 119│     ST: {[_: $Keys<Com>]: any}

Which sounds familiar -- we have a couple of fixmes for those, which we added at the last RN version upgrade because they were baffling to figure out. So now that's a clue about what was causing those errors!
$ rg 'is not a React component'
src/main/MainScreenWithTabs.js
21:        {/* $FlowFixMe-56 Cannot create ZulipStatusBar element because ST is not a React component. */}

src/common/Screen.js
104:        {/* $FlowFixMe-56 Cannot create ZulipStatusBar element because ST is not a React component. */}

This is an example of why I always want fixmes to have an explanatory comment. :-) I'm going to go see about fixing those two, now that we have this clue to what the error means.

Back to this branch: as always I want every commit to leave things non-broken. I think this is also an example where the change is harder to understand for reasons that overlap with why the intermediate code is broken, and making things non-broken will make it easier to understand.
Maybe first rename; then factor out and use that instead of connect; then delete the selector definition itself?

The rename is a separate commit now.
Makes more sense. 👍

Looks great -- thanks for the revisions! Merged.


Update sites.json

Added Intelligence X, Warner Bros. Games and duplicated CODM from Activision

Why did you close it @ukrbugreporter ? I was going to merge it.

Why did you close it @ukrbugreporter ? I was going to merge it.

I deleted the repo by mistake, I'll make another pull request after I fix errors


Linux Function does not have MSI_ENDPOINT or MSI_SECRET after adding application as a MSI

After adding the application (a linux python function) as a managed service identity, then restarting the function, the application settings are not populated with the MSI_ENDPOINT or MSI_SECRET. I have tried disabling and enabling multiple times, as well as restarting the application, but they do not populate.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f57d3177-ce9e-ebfa-03a7-45beb8ca3212
Version Independent ID: a59df23d-f3ac-9809-61d3-5741e31f020a
Content: Managed identities overview - Azure App Service
Content Source: articles/app-service/overview-managed-identity.md
Service: app-service
GitHub Login: @mattchenderson
Microsoft Alias: mahender

@tlagore Managed Identity is in public preview for App service on Linux and apps for containers.
There is a bug currently where the values aren't set in the kudu container, but they are set in the site's main container so if you check kudu or bash it won't show up, but if you ssh you'll be able to check the environment to confirm.
Please let me know if this helps.

Thanks for the quick response. You are correct, the environment variables do actually exist. However, both of the variables are empty.
APPSETTING_WEBSITE_AUTH_ENABLED=False
...
MSI_ENDPOINT=
...
MSI_SECRET=
...
ScmType=None
KUDU_SYNC_CMD=kudusync
FRAMEWORK_VERSION=microsoft/azure-functions-python3.6:2.0
WEBSITE_NODE_DEFAULT_VERSION=8.11.1
SCM_BIN_PATH=/opt/Kudu/bin
PHP_VERSION=7.2

@tlagore This is a bug currently where the values aren't set in the kudu container however if you ssh you'll be able to check the environment to confirm.

Sorry, can you please let me know how to ssh?
documentation shows https://.scm.azurewebsites.net/webssh/host
but this produces SSH CONNECTION CLOSE - Error: connect ECONNREFUSED <IP_ADDRESS>:2222Error: connect ECONNREFUSED <IP_ADDRESS>:2222
I am owner of the subscription. Do I need to enable ssh on container? Do you have documentation for this?
Thank you

Here is the document - https://docs.microsoft.com/en-us/azure/app-service/containers/app-service-linux-ssh-support
Do you have custom docker image?

Hello Dashleen, thanks for the response. It would seem the ssh documentation there is for web apps. I am dealing with an azure function. Is the documentation the same? All of the documented methods fail for the function.

I am closing this issue, because tests have shown I do indeed have access to these environment variables, even though I can't see them through portal or portal cli.

Thanks for the update! Please let us know if you need any further help on this.


Access and Discussion of Google mobility data feature

I was very interested to read your latest report using Mobility data from Google to arrive at a better and more reactive estimate of Rt, as we were exploring similar ideas and were in the process of correlating simulation results with changes of mobility to gain an initial idea of what to expect.
Are you planning to release the code which uses the mobility data for public use?
Questions/discussion on data periodicity
As we were also thinking of using this data we had a few thoughts about what different features of the data represented, notably the weekly periodicity. I'd be very interested in getting your thoughts and viewpoint on the following comments:
It is my impression that the strong weekly periodicity of the mobility data is due at least in part to the periodicity of the baseline data, which is a daily baseline. My hunch is that this periodicity does not accurately reflect behaviours and cannot be used to inform the Rt. The mobility data could probably be averaged over a 7 day window to get a more realistic estimate of transmission patterns.
If we consider the google mobility data for work place frequentation in Italy and France, there is a clear relative increase in workplace attendance (compared to other days in the week) on Saturdays and Sundays. In countries where most things are usually closed the interpretation of people sneaking to work on Sundays during a pandemic is a little far-fetched. It is much more likely that the periodicity is mostly in the baseline data, on a day where 90% of people are normally not at work, the essential workers still at work represent a larger proportion therefore appearing as an uptick in work place frequentation.
My suggestion is that the strong weekly periodicity does not reflect the real world transmission pattern as the google data are normalised per day rather than against a weekly average.
Extract from Google's About this data

Changes for each day are compared to a baseline value for that day of the week:

The baseline is the median value, for the corresponding day of the week, during the 5-week period Jan 3–Feb 6, 2020.
The datasets show trends over several months with the most recent data representing approximately 2-3 days ago—this is how long it takes to produce the datasets.

Hi @payoto, bit busy with few releases but the short answer for availability is yes code should be up by tomorrow noon (cleaning up uncecessary bits).
I will answer your other concerns in sometime as I get more time to write a detailed reply.

Thanks a lot for the hard work!

Hi @payoto , please find the release here de6f3e5
I will reply for other part tomorrow, just busy and do not want to not engage when I can't concentrate. Hope that is fine

Thanks @s-mishra for such hard work and openness !

Hi @s-mishra , just a friendly reminder if you have time to address the points I made about the weekly temporality of the data.


[Bug]: Update manager shows Unknown instead of Up to Date

What happened and in what context?
Update manager shows Unknown instead of Up to Date
see screenshot

If needed, paste the relevant bot log contents here.
No response
If needed, paste the relevant bot journal contents here.
No response
What branch does this occur on?
master
Reports only on latest master or development branches!

[X] I have updated to latest development/master version before submitting the bug

Same for me, happened after the update.

Update Manager is a moonraker feature.
I'm leaving this open for now, but this is not on our side. If it's bothering you, run a reinstall.
Not sure what happened here.

updated telegram today again . still your product is only one having trouble showing version .

Try it now, should be fine again. It's the version number which mainsail did not like, I have corrected it.

All good .


Avoiding substring index out of range exception

Action

Add a brief description of what was made

Issues: #issue-number #issue-number ...
Commits: #commit-hash ...

...

PR for https://github.com/LeonardoCardoso/SwiftLinkPreview/issues/11


swagger-validator middleware needs to handle charset in consumes validation

The current code that checks the Content-Type of a request against the consumes of an operation does not handle the charset that can be included in the Content-Type.  (See rfc2616#sec3.7)  We need to address this.
Reported by @grahamj

When the consume charset is set to [ "application/json; charset=utf-8" ] in the operation, this method doesn't work and throw Invalid content type :
Error: Invalid content type (application/json).  These are valid: application/json; charset=utf-8

We'll discuss this further in #295.


With triton ensemble model, how to make DALI internal output in GPU?

I have an ensemble model DALI+detect model, and I found the internal output of DALI is fixed to TRITONSERVER_MEMORY_CPU_PINNED in server log,
I0206 08:36:48.496881 1 infer_response.cc:165] add response output: output: DALI_OUTPUT_0, type: FP32, shape: [64,3,512,320]
I0206 08:36:48.496914 1 pinned_memory_manager.cc:131] pinned memory allocation: size 125829120, addr 0x7f085e000090
I0206 08:36:48.496918 1 ensemble_scheduler.cc:509] Internal response allocation: DALI_OUTPUT_0, size 125829120, addr 0x7f085e000090, memory type 1, type id<PHONE_NUMBER>55264
I0206 08:36:48.496923 1 infer_response.cc:165] add response output: output: DALI_OUTPUT_1, type: INT64, shape: [64,3]
I0206 08:36:48.496926 1 pinned_memory_manager.cc:131] pinned memory allocation: size 1536, addr 0x7f08658000a0
I0206 08:36:48.496928 1 ensemble_scheduler.cc:509] Internal response allocation: DALI_OUTPUT_1, size 1536, addr 0x7f08658000a0, memory type 1, type id<PHONE_NUMBER>52464

after I change the memtype to TRITONSERVER_MEMORY_GPU,
https://github.com/triton-inference-server/dali_backend/blob/076e98841c976e0f6c55fc360431cfb5bfd7f485/src/dali_backend.h#L175-L180
DALI output img shape became GPU but image data is is still TRITONSERVER_MEMORY_CPU_PINNED :
I0207 07:39:24.490871 1 infer_response.cc:165] add response output: output: DALI_OUTPUT_0, type: FP32, shape: [64,3,512,320]
I0207 07:39:24.490905 1 pinned_memory_manager.cc:131] pinned memory allocation: size 125829120, addr 0x7f47fc000090
I0207 07:39:24.490909 1 ensemble_scheduler.cc:509] Internal response allocation: DALI_OUTPUT_0, size 125829120, addr 0x7f47fc000090, memory type 1, type id 0
I0207 07:39:24.490913 1 infer_response.cc:165] add response output: output: DALI_OUTPUT_1, type: INT64, shape: [64,3]
I0207 07:39:24.490917 1 ensemble_scheduler.cc:509] Internal response allocation: DALI_OUTPUT_1, size 1536, addr 0x7f47f8000000, memory type 2, type id 0
I0207 07:39:24.490986 1 ensemble_scheduler.cc:524] Internal response release: size 125829120, addr 0x7f47fc000090

I want to know is it possible to make the internal output all in GPU and what's the right method to set this. I think it can improve the throughput of ensemble model.

@uefall ,
thank you for pointing that out! Could you tell, which version of dali_backend are you running? #16 fixed issues with choosing the device, this PR will be available in tritonserver-21.02. In case you'd like to use the main branch of dali_backend, please follow  docker build instructions.
If you are using main branch and you still observe CPU allocation of DALI output, could you run the server with --log_verbose=2 and check the instance groups in full DALI model configuration logged? Here's how it should look like:
I0208 23:00:49.566997 1 dali_backend.cc:71] Loading DALI pipeline from file /models/dali/1/model.dali
I0208 23:00:49.567063 1 dali_backend.cc:44] model configuration:
{
    "name": "dali",
    "platform": "",
    "backend": "dali",
[...]
   "instance_group": [
       {
           "name": "dali",
           "kind": "KIND_GPU",
           "count": 1,
            "gpus": [
                0
            ],
            "profile": []
        }
    ],
[...]
}

Anyway, your proposal to change the default requested memory type is good. It's available in #21

sorry for my late reply.
I use the version
commit 076e98841c976e0f6c55fc360431cfb5bfd7f485 (HEAD -> main, origin/r21.02)
Author: Michał<EMAIL_ADDRESS>Date:   Tue Jan 26 02:43:57 2021 +0100

the log-verbose2 shows
I0220 02:03:17.687831 1 dali_backend.cc:71] Loading DALI pipeline from file /models/dali_ctdet/1/model.dali
I0220 02:03:17.687940 1 dali_backend.cc:44] model configuration:
{
    "name": "dali_ctdet",
    "platform": "",
    "backend": "dali",
    "version_policy": {
        "latest": {
            "num_versions": 1
        }
    },
    "max_batch_size": 128,
    "input": [
        {
            "name": "DALI_INPUT_0",
            "data_type": "TYPE_UINT8",
            "format": "FORMAT_NONE",
            "dims": [
                -1
            ],
            "is_shape_tensor": false,
            "allow_ragged_batch": false
        }
    ],
    "output": [
        {
            "name": "DALI_OUTPUT_0",
            "data_type": "TYPE_FP32",
            "dims": [
                3,
                512,
                320
            ],
            "label_filename": "",
            "is_shape_tensor": false
        },
        {
            "name": "DALI_OUTPUT_1",
            "data_type": "TYPE_INT64",
            "dims": [
                3
            ],
            "label_filename": "",
            "is_shape_tensor": false
        }
    ],
    "batch_input": [],
    "batch_output": [],
    "optimization": {
        "priority": "PRIORITY_DEFAULT",
        "input_pinned_memory": {
            "enable": true
        },
        "output_pinned_memory": {
            "enable": true
        }
    },
    "instance_group": [
        {
            "name": "dali_ctdet_0",
            "kind": "KIND_GPU",
            "count": 1,
            "gpus": [
                0
            ],
            "profile": []
        }
    ],
    "default_model_filename": "",
    "cc_model_filenames": {},
    "metric_tags": {},
    "parameters": {},
    "model_warmup": []
}
I0220 02:03:17.688125 1 dali_backend.cc:348] TRITONBACKEND_ModelInstanceInitialize: dali_ctdet_0 (GPU device 0)

and dali output is still memory type 1 and 2
I0220 02:08:46.983816 1 infer_response.cc:165] add response output: output: DALI_OUTPUT_0, type: FP32, shape: [64,3,512,320]
I0220 02:08:46.983851 1 pinned_memory_manager.cc:131] pinned memory allocation: size 125829120, addr 0x7feb2e000090
I0220 02:08:46.983855 1 ensemble_scheduler.cc:509] Internal response allocation: DALI_OUTPUT_0, size 125829120, addr 0x7feb2e000090, memory type 1, type id 0
I0220 02:08:46.983860 1 infer_response.cc:165] add response output: output: DALI_OUTPUT_1, type: INT64, shape: [64,3]
I0220 02:08:46.983864 1 ensemble_scheduler.cc:509] Internal response allocation: DALI_OUTPUT_1, size 1536, addr 0x7feb2a000000, memory type 2, type id 0
I0220 02:08:46.983931 1 ensemble_scheduler.cc:524] Internal response release: size 125829120, addr 0x7feb2e000090
I0220 02:08:46.983936 1 ensemble_scheduler.cc:524] Internal response release: size 1536, addr 0x7feb2a000000

I will update to the latest and try again, thank you.

I update the code and test again, got same result,
DALI_OUTPUT_0 is decoded image data DALI_OUTPUT_1 is image shape,
why it made DALI_OUTPUT_1 to GPU and DALI_OUTPUT_0 still remain CPU?
I remove the image shape output and left only image data output,  still memory type 1
I0220 06:30:07.825872 1 pinned_memory_manager.cc:131] pinned memory allocation: size 125829120, addr 0x7f664e000090
I0220 06:30:07.825877 1 ensemble_scheduler.cc:509] Internal response allocation: DALI_OUTPUT_0, size 125829120, addr 0x7f664e000090, memory type 1, type id 0
I0220 06:30:07.825922 1 ensemble_scheduler.cc:524] Internal response release: size 125829120, addr 0x7f664e000090

tested ok with the latest version, maybe I forgot to change the container last time.
I will close this issue.
@szalpal ,Thank you!

The problem is that I use a large batchsize to do perf test and the DALI_OUTPUT exceed the cuda memory limit
W0222 10:25:26.739351 1 memory.cc:135] Failed to allocate CUDA memory with byte size 251658240 on GPU 0: CNMEM_STATUS_OUT_OF_MEMORY, falling back to pinned system memory

this info shows only once and i missed it.


Codecov upload seems broken

          Codecov upload seems broken because:

Originally posted by @germa89 in https://github.com/ansys/pymapdl/issues/3501#issuecomment-2428527735

Closed in #3542