getting errors "TypeError: container.init is not a function, TypeError: container.get is not a function" while loading remote module using dynamic federation

Hi @manfredsteyer. Please guide on below issue.
I am using nrwl-nx-monorepo and have upgraded to the latest of:
1). angular - 13.1.3
2). @angular-architects/module-federation - 14.0.1
3). webpack - 5.60.0
I followed your migration guide at below link:
https://github.com/angular-architects/module-federation-plugin/blob/main/migration-guide.md
But yet when I try to load remoteModule into my host using dynamic federation I am getting below issues in my console:

Let me know if any more information needed.

Hi,

Do you have target="es2020" in your global tsconfig.json?
Do you use type:'module' when calling loadRemoteModule and loadRemoteEntry?

Hi,

Do you have target="es2020" in your global tsconfig.json?
Do you use type:'module' when calling loadRemoteModule and loadRemoteEntry?

Hi @manfredsteyer ,
1). Yes I have target="es2020" in global tsconfig.json (tsconfig.base.json in nx monorepo)
2). Yes in my host app route file I have specified "type='module' ".
For reference I am providing below details:
1). Global tsconfig.base.json image.
2). Host app - routing file image, webpack.config.js image, main.ts image
3). Mfe app - webpack.config.js image
Global tsconfig.base.json

Host app
routing file

main.ts

webpack.config.json

Mfe app
webpack.config.json

Migration guide points which are now throwing error are:
1). scriptType="text/javascript" - not able to use it now. Gives error "Invalid property".
2). In host app "main.ts" file can not write the below code:
import { loadRemoteEntry } from '@angular-architects/module-federation';
loadRemoteEntry({ type: 'module', remoteEntry: 'http://localhost:5005/remoteEntry.js'})
.then(_ => import('./bootstrap').catch(err => console.error(err)))
It throw error.
I have a requirement where I have 5 microfrontends and have to load them conditionally inside the host app.
Please have a look at the above observations.

to make sure, the config is correct please try to add the Module Federation setup with ng add.
delete ".angular" folder after each config change to make sure no side-effects occur.
please provide more details on the errors for "scriptType" and "main.ts.

to make sure, the config is correct please try to add the Module Federation setup with ng add.
delete ".angular" folder after each config change to make sure no side-effects occur.
please provide more details on the errors for "scriptType" and "main.ts".

Hi @mikezks
Below are the observations:
Microfrontend successfully loading with [scriptType:"text/javascript"] setting
1). Now I am able to use [scriptType:"text/javascript"]. I had done a mistake shown in comment ['equal' sign i was using in place of 'colon']

with above configuration in both host and mfe webpack.config.js and below host routing I am able to load mfe in host app

But with ES6 module configuration in webpack.config.js it is not working and giving the same issue mentioned in my initial post
1).  I already used below command format to add module federation to the host and mfe projects

2). I tried deleting the .angular folder after changes in webpack.config.js but still issue getting.
3). main.ts --> Let me elaborate on this
In the migration guide its is said to have below code in host app main.ts

but on load in this case i get below error

-------------------on the other hand if I keep the default content in main.ts file as shown below i do not get issues

I tested w/<EMAIL_ADDRESS>and<EMAIL_ADDRESS>successfully. Only difference, I used a CLI app and not Nx.
Works with fully dynamic loading and main.ts based runtime loading.
Feel free to provide a demo repo that shows your issue.


Basic example doesn't work, dropping item does nothing.

I'm submitting a ...
[ ] bug report
[ ] feature request
[x] other

What is the current behavior?
Basic example from manual doesn't work for me. When I drop item nothing happens. May be its's not compatible with stackblitz.
Code is here.

The basic requirement is to have an onDrop handler on the droppable & set drag data on the draggable.
I modified your example to include both. Link: https://stackblitz.com/edit/angular-drag-drop-example-tw7dt3

Thanks, it's clear now )


Trying productive environment fail

Hi
I did all the steps to get up odoo v11 with copier and succecsfuly got my http://localhost:11069 environment running
Now I tried to make it run on a productive way, so i got stuck with this error:
WARNING: The SMTP_REAL_NON_CANONICAL_DEFAULT variable is not set. Defaulting to a blank string.
ERROR: Network "dmoemuebles2_default" needs to be recreated - option "encrypted" has changed
Steps:
I created my copier instance:
copier copy gh:Tecnativa/doodba-copier-template dmoemuebles2
I linked my tests domains to this server and so i give to copier this basic answers:
Changes here will be overwritten by Copier
_commit: v1.5.4
_src_path: gh:Tecnativa/doodba-copier-template
backup_deletion: true
backup_dst: null
backup_email_from: null
backup_email_to: null
backup_tz: UTC
cidr_whitelist: null
domain_prod: dmoemuebles2.realsystems.com.mx
domain_prod_alternatives: www.realsystems.com.mx
domain_test: dmoemuebles3.realsystems.com.mx
gitlab_url: null
odoo_dbfilter: .*
odoo_initial_lang: en_US
odoo_listdb: false
odoo_oci_image: null
odoo_proxy: traefik
odoo_version: 11.0
paths_without_crawlers:

/web
/website/info
postgres_dbname: prod
postgres_username: odoo
postgres_version: 11
project_author: RS
project_license: AGPL-3.0-or-later
project_name: dmoemuebles
smtp_canonical_default: null
smtp_canonical_domains: null
smtp_default_from: null
smtp_relay_host: null
smtp_relay_port: 587
smtp_relay_user: null

I creates on a separate directory my traefik global proxy:
inverseproxy.yaml
version: "2.1"
services:
proxy:
image: traefik:1.6-alpine
networks:
shared:
private:
public:
volumes:
- acme:/etc/traefik/acme:rw,Z
ports:
- "80:80"
- "443:443"
depends_on:
- dockersocket
restart: unless-stopped
privileged: true
tty: true
command:
- --ACME.ACMELogging
-<EMAIL_ADDRESS>- --ACME.EntryPoint=https
- --ACME.HTTPChallenge.entryPoint=http
- --ACME.OnHostRule
- --ACME.Storage=/etc/traefik/acme/acme.json
- --DefaultEntryPoints=http,https
- --EntryPoints=Name:http Address::80 Redirect.EntryPoint:https
- --EntryPoints=Name:https Address::443 TLS
- --LogLevel=INFO
- --Docker
- --Docker.EndPoint=http://dockersocket:2375
- --Docker.ExposedByDefault=false
- --Docker.Watch
dockersocket:
image: tecnativa/docker-socket-proxy
privileged: true
networks:
private:
volumes:
- /var/run/docker.sock:/var/run/docker.sock
environment:
CONTAINERS: 1
NETWORKS: 1
SERVICES: 1
SWARM: 1
TASKS: 1
restart: unless-stopped
networks:
shared:
internal: true
driver_opts:
encrypted: 1
private:
internal: true
driver_opts:
encrypted: 1
public:
volumes:
acme:
so i run:
docker-compose -p inverseproxy -f inverseproxy.yaml up -d
Now my web page says:

So I modified my .dockers files:
vi .docker/db-access.env
vi .docker/db-creation.env
vi .docker/odoo.env
vi .docker/smtp.env
And make it to match test environment values and:
docker-compose -f prod.yaml up -d
I got this error:
WARNING: The SMTP_REAL_NON_CANONICAL_DEFAULT variable is not set. Defaulting to a blank string.
ERROR: Network "dmoemuebles2_default" needs to be recreated - option "encrypted" has changed
Now I tried
docker-compose down
docker-compose -f prod.yaml up -d
docker-compose up
And got nothin different now Im stuck did you see some insight what do i missed?
Thanks

docker-compose build --pull
docker-compose down
docker-compose up -d

Excelent thank you very much Pedro
I hope you can give me some insight on this I think its not an issue from copier.

Probably you haven't deploy the general proxy in your server, but without more information is difficult to say.

Pedro I create on a separate directory my traefik global proxy:
inverseproxy.yaml
version: "2.1"
services:
proxy:
image: traefik:1.6-alpine
networks:
shared:
private:
public:
volumes:

acme:/etc/traefik/acme:rw,Z
ports:
"80:80"
"443:443"
depends_on:
dockersocket
restart: unless-stopped
privileged: true
tty: true
command:
--ACME.ACMELogging
<EMAIL_ADDRESS>--ACME.EntryPoint=https
--ACME.HTTPChallenge.entryPoint=http
--ACME.OnHostRule
--ACME.Storage=/etc/traefik/acme/acme.json
--DefaultEntryPoints=http,https
--EntryPoints=Name:http Address::80 Redirect.EntryPoint:https
--EntryPoints=Name:https Address::443 TLS
--LogLevel=INFO
--Docker
--Docker.EndPoint=http://dockersocket:2375
--Docker.ExposedByDefault=false
--Docker.Watch
dockersocket:
image: tecnativa/docker-socket-proxy
privileged: true
networks:
private:
volumes:
/var/run/docker.sock:/var/run/docker.sock
environment:
CONTAINERS: 1
NETWORKS: 1
SERVICES: 1
SWARM: 1
TASKS: 1
restart: unless-stopped
networks:
shared:
internal: true
driver_opts:
encrypted: 1
private:
internal: true
driver_opts:
encrypted: 1
public:
volumes:
acme:

so i run:
docker-compose -p inverseproxy -f inverseproxy.yaml up -d
Is this ok?

I can't say about that. Maybe @Yajo can answer.

Thank you Pedro
I know I still have to learn more to get this done

Indeed I have this configuration with traefik:

How can i put prod.yaml in tune with this to allow dmoemueble2.realsystems.com.mx to link to odoo container?
my prod.yaml file:
services:
odoo:
extends:
file: common.yaml
service: odoo
restart: unless-stopped
env_file:
- .docker/odoo.env
- .docker/db-access.env
environment:
DOODBA_ENVIRONMENT: "${DOODBA_ENVIRONMENT-prod}"
INITIAL_LANG: "$INITIAL_LANG"
depends_on:
- db
networks:
default:
inverseproxy_shared:
labels:
traefik.longpolling.frontend.rule: "Host:${DOMAIN_PROD};PathPrefix:/longpolling/"
traefik.www.frontend.rule: "Host:${DOMAIN_PROD}"
traefik.forbid-crawlers.frontend.rule: "Host:${DOMAIN_PROD};PathPrefix:/web,/web/{anything:.},/website/info,/website/info/{anything:.}"
# Main service
traefik.http.middlewares.dmoemueble2-11-0-prod-buffering.buffering.retryExpression:
IsNetworkError() && Attempts() < 5
traefik.http.middlewares.dmoemueble2-11-0-prod-compress.compress: "true"
traefik.http.routers.dmoemueble2-11-0-prod-main.entrypoints: "web-main"
traefik.http.routers.dmoemueble2-11-0-prod-main.middlewares:
dmoemueble2-11-0-prod-buffering,
dmoemueble2-11-0-prod-compress
traefik.http.routers.dmoemueble2-11-0-prod-main.rule: "host(${DOMAIN_PROD})"
traefik.http.routers.dmoemueble2-11-0-prod-main.service: "dmoemueble2-11-0-prod-main"
traefik.http.routers.dmoemueble2-11-0-prod-main.tls: "true"
traefik.http.routers.dmoemueble2-11-0-prod-main.tls.certresolver: "letsencrypt"
traefik.http.services.dmoemueble2-11-0-prod-main.loadbalancer.server.port: 8069
# Longpolling service
traefik.http.routers.dmoemueble2-11-0-prod-longpolling.entrypoints: "web-main"
traefik.http.routers.dmoemueble2-11-0-prod-longpolling.rule:
"host(${DOMAIN_PROD}) && pathprefix(/longpolling/)"
traefik.http.routers.dmoemueble2-11-0-prod-longpolling.service: "dmoemueble2-11-0-prod-longpolling"
traefik.http.services.dmoemueble2-11-0-prod-longpolling.loadbalancer.server.port: 8072
traefik.http.routers.dmoemueble2-11-0-prod-longpolling.tls: "true"
traefik.http.routers.dmoemueble2-11-0-prod-longpolling.tls.certresolver: "letsencrypt"
# Forbid crawlers
? traefik.http.middlewares.dmoemueble2-11-0-prod-forbid-crawlers.headers.customResponseHeaders.X-Robots-Tag
: "noindex, nofollow"
traefik.http.routers.dmoemueble2-11-0-prod-forbidden-crawlers.entrypoints: "web-main"
traefik.http.routers.dmoemueble2-11-0-prod-forbidden-crawlers.middlewares:
dmoemueble2-11-0-prod-buffering,
dmoemueble2-11-0-prod-compress,
dmoemueble2-11-0-prod-forbid-crawlers
traefik.http.routers.dmoemueble2-11-0-prod-forbidden-crawlers.rule:
Host(${DOMAIN_PROD}) && Path(/web, /web/{anything:.*}, /website/info, /website/info/{anything:.*})
traefik.http.routers.dmoemueble2-11-0-prod-forbidden-crawlers.service: "dmoemueble2-11-0-prod-main"
traefik.http.routers.dmoemueble2-11-0-prod-forbidden-crawlers.tls: "true"
traefik.http.routers.dmoemueble2-11-0-prod-forbidden-crawlers.tls.certresolver: "letsencrypt"
db:
extends:
file: common.yaml
service: db
env_file:
- .docker/db-creation.env
restart: unless-stopped
networks:
default:
driver_opts:
encrypted: 1
inverseproxy_shared:
external: true
volumes:
filestore:
db:

Hi there!
Thanks for taking the time to report the problem, but it seems like this is not exactly a bug in this project's code and/or scope. It is more likely a problem on your specific deployment, instance or configuration.
Doodba is a project that sews many others together, such as:

click-odoo-contrib
Copier
Docker Compose
Docker
Git Aggregator
Git
Gitlab
OCA
Odoo
Traefik

When you use Doodba, you are expected to know those tools. Although this project includes some documentation that is specific for some of those components, we don't aim to replace their own documentation or support channels, which might be documentation, a mailing list, a chat room, a help forum, commercial support, etc.

It seems your problem is more related to Traefik.
I hope you can get proper help there. If you find out that your problem was finally caused by Doodba itself or that some if our docs are missing, incomplete, outdated or confusing, please feel free to reopen this issue, open a new one, or even contribute a PR to improve the situation.
To keep the bug tracker clean and focused, This issue will stay closed. I hope you understand and don't take that personally. 😊
Have a nice day!

Thank you very much Yaho to take the time to answer me.
I know this is not the forum to learn other technologies =)
Your tips are very welcome and very usefull.
"To keep the bug tracker clean and focused, This issue will stay closed. I hope you understand and don't take that personally. ￼"
Never Yaho, this is an Open Source Project and I apreciate you and Pedro take the time to answer us as your possibilities.
I will try to contribute to this project on my possibilities with my discoveries in the way of a newbie.
Regards.


Include pgp key in admin settings and user settings

https://github.com/yzernik/squeakroad/pull/375


Change Split Rune Column to +

The split rune change column (from inventory/swap) is great for replacing runes without filling up inventory space.  However the slash is ambiguous with a ratio so 1/1 reads like (one of one runes are from inventory).  I recommend 1+1 instead which is more clear that there are two changes.

I tried some variants and settled on this being the most obvious:


Cannot detect server start after Palworld V<IP_ADDRESS>

The GUI always Indicaing starting after click start server and the server is actually already started.
Here is the log:
[05-04-2024 20:01:56] utils.go: Init() - Palword Dedicated Server GUI v1.0.6
[05-04-2024 20:01:58] <IP_ADDRESS>:1200 connected to the GUI server
[05-04-2024 20:02:00] Downloading dedicated server...
[05-04-2024 20:02:26] Server downloaded and updated successfully!
[05-04-2024 20:02:28] Starting dedicated server...

I'll take a look.

Releasing a fix now. Will leave this issue open to track other issues that this version might cause. Thanks for the heads up!

Everything looks good so far.
On a side note, this is my first private server (hosted for my private game group) and this program has been a godsend. Thank you for the efforts!


treewide: fix cargoSha256 (again)

Motivation for this change
Previously: https://github.com/NixOS/nixpkgs/pull/62047
This time the change in cargo vendor output was caused by https://github.com/NixOS/nixpkgs/commit/a4fc84de44c4edad7fcf303944bcb874180c1bf3.
I hope that some time soon we can ban buildRustPackage from Nixpkgs.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

Notify maintainers
cc @

carnix is worse at the moment due the large amounts of nix expressions it generates. There is no alternative atm.

Why did the rustc update cause cargo vendor output to change though? What's the root cause here?

I'm also curious why this change didn't affect all rust packages. For example, it doesn't look as though exa broke with the update.

Why did the rustc update cause cargo vendor output to change though?
What's the root cause here?

It looks like Cargo.lock files are no longer excluded.  So only the
packages with dependencies containing Cargo.lock would have changed.
At least, that's what's changed for the one I looked at (rsclock, whose
vendored autocfg now includes Cargo.lock).

Wow really? That seems really odd, because I thought Cargo.lock was intentionally and explicitly excluded from dependencies.

Wow really? That seems really odd, because I thought Cargo.lock was
intentionally and explicitly excluded from dependencies.

Yep.  You can confirm yourself by building rsClock.cargoDeps before that
commit was merged from staging-next, and after, and comparing with
diffoscope.
It might not be that Cargo.lock specifically is now included, though.
Maybe there was some other change to inclusion logic made that just
happened to manifest as Cargo.lock beginning to be included in this
case.


Use charset predefined StandardCharsets.UTF_8 code.

Codecov Report

Merging #189 (f37f78d) into master (2e39ef6) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #189      +/-   ##
============================================
+ Coverage     89.44%   89.46%   +0.02%
- Complexity     3602     3604       +2
============================================
  Files           183      183
  Lines          9992     9992
  Branches       1352     1352
============================================
+ Hits           8937     8939       +2
  Misses          769      769
+ Partials        286      284       -2

Impacted Files
Coverage Δ

...rg/apache/commons/configuration2/io/FileUtils.java
80.76% <100.00%> (ø)

...commons/configuration2/tree/InMemoryNodeModel.java
96.94% <0.00%> (+0.76%)
: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 2e39ef6...f37f78d. Read the comment docs.

Yep, I'm working on the RC but I haven't made the release branch yet so I'll pull this in.

Thanks @darkma773r !


The Concept list for BoreHole Pupose contains duplicate terms and doesn't link to the definitions

https://vocabs.gsq.digital/vocabulary/borehole-purpose/concept/

@lisa-woody the vocabulary file is properly formed and formatted.
I can see the same issue in vocPrez in all the vocabularies I have just checked. The standard display is fine but the endpoint shows duplicates. Something is going awry in the endpoint process for VocPrez @DavidCrosswellGSQ

Two issues here:

There is a known bug in VocPrez that has been fixed in Version 2 of VocPrez. We will upgrade to VocPrez2 post go-live August 3 (version 1 works) - apart from these types of visual issues.

The links for these don't work as this vocab is not published in linked.data.gov.au - Nick was meant to get all registered and approved, but there are a number of vocabs that aren't registered.


Hi,
There is currently no document about this issue
https://nextra.site/docs/guide/advanced/remote

src\pages\pokemon\[name].mdx

import { RemoteContent } from "nextra/data";
import { buildDynamicMDX, buildDynamicMeta } from "nextra/remote";
import { useFetch } from "@/hooks";

export async function getPokémons() {
  const { results: data } = await useFetch({
    url: process.env.NEXT_PUBLIC_API_POKEMON,
  });
  return { data };
}

export async function getStaticPaths() {
  const { data } = await getPokémons();
  return {
    paths: data.map(({ name }) => ({ params: { name } })),
    fallback: false,
  };
}

export async function getStaticProps({ params: { name: __name__ } }) {
  const { data } = await getPokémons();
  const { url } = data.find(({ name }) => name === __name__);
  const { name, ...rest } = await useFetch({ url });
  const content = `---
title: ${name}
---
# ${name}
\`\`\`
${JSON.stringify({ name, ...rest }, null, 2)}
\`\`\`
`;
  return {
    props: {
      ...(await buildDynamicMDX(content)),
      ...(await buildDynamicMeta()),
    },
  };
}

<RemoteContent />

everything works, but no sidebar

no breadcrumb

also can not search

I'm using similar implementation. Any luck to have search working with this?

@shenlong616 and @IlirEdis have you had a look at GraphQL Yoga website?
This section is generated with <RemoteContent> if you look at the code.

@shenlong616 do you think I can see your repository? I really interested as I need to do something similar

@shenlong616 got it working ... put this in your _meta.js
const { createCatchAllMeta } = require('nextra/catch-all')
import { usePokémonList } from "@/hooks";

module.exports = async () => {
  const { data } = await usePokémonList();
  // FIXME: This is horrible but does the job
  const pageList = data.map((item) => {return item.name + '.mdx'})
  return createCatchAllMeta(pageList)
};

Look the result

One thing I could not reproduce is the error you showed above - I am on a Mac and there's something Windows specific in it. Also, check the node version... I am using v18.16.1. If you wish, I can publish your code on a repo (I see it has nothing private) so it remains as a reference

@shenlong616 and @IlirEdis have you had a look at GraphQL Yoga website? This section is generated with <RemoteContent> if you look at the code.

@LunaticMuch yes i've seen this and as i noticed they are using Algolia as a third party service for the search functionality.
Is search working with your use case?

good point @IlirEdis
I have noticed it does not work, although it should. I try to review it tomorrow and create a fresh case.

I already asked a question here https://github.com/shuding/nextra/issues/1952#issuecomment-1627759509 but it seems it will not work with remote data, maybe until a future release. I will be forced to move away from Nextra because of this.

Look into Typesense, an open-source Algolia alternative. They have a fork
of the Algolia DocSearch crawler you can use to create an index once the
site is live rather than on build.
On Sun, Jul 16, 2023, 4:25 PM Ilir Bajrami @.***> wrote:

I already asked a question here #1952 (comment)
https://github.com/shuding/nextra/issues/1952#issuecomment-1627759509
but it seems it will not work with remote data, maybe until a future
release. I will be forced to move away from Nextra because of this.
—
Reply to this email directly, view it on GitHub
https://github.com/shuding/nextra/issues/1980#issuecomment-1637193481,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHBIFX6EVVNI7VMX733K6G3XQRL3DANCNFSM6AAAAAAZLRKCYQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I already asked a question here #1952 (comment) but it seems it will not work with remote data, maybe until a future release. I will be forced to move away from Nextra because of this.

Accoring to your comment you also found what is not working correctly. This makes sense as I see indexed [name] as a file.

@IlirEdis take it with very low confidence, but it does not seem a massive problem to fix. The issue is that the metadata for search is generated only repeating the dynamic route name instead of the name the page is supposed to have.

@LunaticMuch maybe im exaggerating it but at the moment i dont have any clue how to fix it, lol. Here's a codesandbox to see my implementation.
If it opens the first default home Nextjs page, navigate to /docs/home to see the docs page.

@IlirEdis I am cautious in saying easy :) but what I understand is that the  just generate a wrong index file.

@IlirEdis I did some research. The index is populated as a webpack plugin. It backs file on disk, so dynamic routes do not really work.
A workaround, for the build, would be just to dump an additional index file and then to combine both json. I tried it, and it work.
As a strategy, some changes would be required. I have no real idea about the webpack plugin. I would have built the index file at runtime outside webpack, but I am sure there's a reason for that. I know some solutions with Next.JS actually build indexes on the API route and then back the API route for the search.

Hi @LunaticMuch could you please elaborate on "solutions" to build indexes at runtime? I'm trying to build a search feature using Orama and content from Notion.

@LunaticMuch maybe im exaggerating it but at the moment i dont have any clue how to fix it, lol. Here's a codesandbox to see my implementation.
Btw here in this sandbox i implemented this: https://docs.oramasearch.com/plugins/plugin-nextra but it behaves exactly the same as the default Nextra search which is implemented using this library: https://github.com/nextapps-de/flexsearch
If it opens the first default home Nextjs page, navigate to /docs/home to see the docs page.

@IlirEdis Any luck since then getting remote mdx working so it shows up in the sidebar?

https://the-guild.dev/blog/nextra-3#remote-docs-support

@LunaticMuch maybe im exaggerating it but at the moment i dont have any clue how to fix it, lol. Here's a codesandbox to see my implementation.
Btw here in this sandbox i implemented this: https://docs.oramasearch.com/plugins/plugin-nextra but it behaves exactly the same as the default Nextra search which is implemented using this library: https://github.com/nextapps-de/flexsearch
If it opens the first default home Nextjs page, navigate to /docs/home to see the docs page.

@IlirEdis Any luck since then getting remote mdx working so it shows up in the sidebar?

Hi @codinsonn. sorry, i abandoned this project long time ago. It seems links posted by @dimaMachina have a solution. Probably i will get back to this when i have time. It seems Nextra has an update.

https://the-guild.dev/blog/nextra-3#remote-docs-support
working example: https://github.com/shuding/nextra/tree/7a694a6e05d8744706ad4de31b7e1063f42c7d7a/examples/swr-site/pages/en/remote/graphql-eslint
latest preview: https://nextra-theme-docs-mxya8w9g1.vercel.sh/en/remote/graphql-eslint

Awesome, got a version working with these examples
Thx! 🙏


Update k8s versions in system-requirements.mdx

k8s versions should be aligned the Enterprise release that Cloud is currently based on. The current window is 1.24-1.26

Product Version(s):

Issue:

Link to docs preview:

SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:

Merge checklist:

[ ] Deploy preview inspected wherever changes were made
[ ] Build completed successfully
[ ] Test have passed

@sujeet-kr @bmckercher123 Can you take a look?

LGTM


Make EBS block size a variable in AWS nomad clients

:gear: Issue
It was mentioned that the AWS EBS root disk size was hard-coded in AWS, but a variable in GCP.
:white_check_mark: Fix
This eliminates the 100gb hardcoding and adds a variable with a default of 100gb.
:question: Tests

[] Passed reality check

We need to update Terraform apparently https://github.com/CircleCI-Public/server-terraform/blob/main/.circleci/config.yml#L29


Vite plugins (e.g. Babel) not executed for entrypoints

Describe the bug
Vite plugins aren't executed for entrypoints. Reason is probably because they are loaded via jiti. I like to use some babel plugins for my projects, so it would be great if entrypoints are processed regularly via Vite.
To Reproduce
// wxt.config.js

import { defineConfig } from 'wxt';
import babel from 'vite-plugin-babel'

export default defineConfig({
  vite: () => ({
    plugins: [babel()],
  }),
});

// entrypoints/background.js

import map from 'lodash/fp/map'

// use some babel plugin here
export default defineBackground(() => console.log([1, 2] |> map(x => x * 2))

Expected behavior
The code runs through.
Actual behavior
Builds exits with a parsing error.
Additional context
It works with vite-plugin-web-extension and Nuxt.

Yeah, for this to work we'd have to use vite to transpile the entrypoints. I will look into this after some of the other large issues are handled.
For now, you can use custom plugins in other files, just not the entrypoints.

I'm gonna close this issue, it will be fixed in #506, follow that one for updates.


Propose scheduler queries for synchronization primitives (?)

This is a suggestion from @dietmarkuehl. A strand scheduler might not want the algorithms to use locks and atomics for synchronization, for instance. Needs design work.

Sorry was passing by - looks like there was an older issue identical to this one https://github.com/NVIDIA/stdexec/issues/690

Indeed. Thanks, closing as a dupe.


Training log

Thanks for the great work! However, I encountered some difficulties during reproducing this paper based on other codebase, like mmdetection. Could you share the training log? So that I can check the problem. Many thanks.

loss_text.txt

Thanks for your help.


Passthrough labels and annotations for the service.

Purpose of the change
Being able to pass annotations or labels for the service that schema registry deploys is useful. Easier to manager and track it with other components deployed on a K8s cluster this way (based on putting some annotations on the service).
How to verify it
It is pretty minute code change.
You can test it out with various values files like this:
helm install schema charts/schema-registry --debug --dry-run -f values.yaml

@jdmaguire please create an accompanying issue and please use the template for the PR.

@jdmaguire the configured labels and annotations seem to get added to the deployment and not the service. But the description states that the intent is to add the annotations or labels to the service deployed by schema registry. Could u clarify that too?

When I do
helm install schema charts/schema-registry --debug --dry-run --set service.annotations.passedano=works

I see
NAME: schema
LAST DEPLOYED: Wed Nov 18 10:06:22 2020
NAMESPACE: default
STATUS: pending-install
REVISION: 1
TEST SUITE: None
USER-SUPPLIED VALUES:
service:
  annotations:
    passedano: works

COMPUTED VALUES:
authentication:
  authGroupResourceIdentifier: group
  authNamespaceResourceIdentifier: namespace
  authResourceDomain: prn
  disableBasicAuthentication: false
  enabled: false
  passwordAuthSecret: null
  userPasswordFile: null
client:
  loadDynamic: false
  method: ""
  token: ""
container: {}
controllerUri: tcp://localhost:9090
image:
  pullPolicy: IfNotPresent
  repository: pravega/schemaregistry
  tag: 0.1.0
ingress:
  annotations: {}
  enabled: false
  hosts:
  - schema-registry.pravega.com
  path: /
  tls: []
initContainer: {}
pravega:
  tlsTrustStore: null
  validateHostName: true
replicas: 2
service:
  annotations:
    bravo: echo
    passedano: works
  labels:
    mango: tango
  port: 9092
  type: LoadBalancer
serviceAccount:
  annotations: null
  create: true
  name: schema-registry
storeType: Pravega
tls:
  certFile: null
  enabled: false
  keyFile: null
  keyPasswordFile: null
  secret: null

HOOKS:
MANIFEST:
---
# Source: schema-registry/templates/service_account.yaml
# /**
#  * Copyright (c) Dell Inc., or its subsidiaries. All Rights Reserved.
#  *
#  * Licensed under the Apache License, Version 2.0 (the "License");
#  * you may not use this file except in compliance with the License.
#  * You may obtain a copy of the License at
#  *
#  *     http://www.apache.org/licenses/LICENSE-2.0
#  */
apiVersion: v1
kind: ServiceAccount
metadata:
  name: schema-registry
  namespace: default
  labels:
    app.kubernetes.io/name: schema-registry
    app.kubernetes.io/version: "0.1.0"
    app.kubernetes.io/managed-by: Helm
    helm.sh/chart: "schema-registry-0.1.0"
  annotations:
    null
---
# Source: schema-registry/templates/configmap.yaml
# /**
#  * Copyright (c) Dell Inc., or its subsidiaries. All Rights Reserved.
#  *
#  * Licensed under the Apache License, Version 2.0 (the "License");
#  * you may not use this file except in compliance with the License.
#  * You may obtain a copy of the License at
#  *
#  *     http://www.apache.org/licenses/LICENSE-2.0
#  */

apiVersion: v1
kind: ConfigMap
metadata:
  name: schema-schema-registry-configmap
  namespace: default
  labels:
    app.kubernetes.io/name: schema-registry
    app.kubernetes.io/version: "0.1.0"
    app.kubernetes.io/managed-by: Helm
    helm.sh/chart: "schema-registry-0.1.0"
data:
  "CONTROLLER_URL": "tcp://localhost:9090"
  "STORE_TYPE": "Pravega"
  "CONTROLLER_TLS_VALIDATE_HOSTNAME": "true"
  "AUTHORIZATION_ENABLED": "false"
  "TLS_ENABLED": "false"
  "pravega_client_auth_loadDynamic": "false"
  "pravega_client_auth_method": ""
  "pravega_client_auth_token": ""
  "PRE_START_CMD": ""
---
# Source: schema-registry/templates/service.yaml
# /**
#  * Copyright (c) Dell Inc., or its subsidiaries. All Rights Reserved.
#  *
#  * Licensed under the Apache License, Version 2.0 (the "License");
#  * you may not use this file except in compliance with the License.
#  * You may obtain a copy of the License at
#  *
#  *     http://www.apache.org/licenses/LICENSE-2.0
#  */

apiVersion: v1
kind: Service
metadata:
  name: schema-schema-registry
  namespace: default
  labels:
    app.kubernetes.io/name: schema-registry
    app.kubernetes.io/version: "0.1.0"
    app.kubernetes.io/managed-by: Helm
    helm.sh/chart: "schema-registry-0.1.0"
    mango: tango
  annotations:
    bravo: echo
    passedano: works
spec:
  type: LoadBalancer
  ports:
    - port: 9092
      targetPort: 9092
      protocol: TCP
      name: rest
  selector:
    app.kubernetes.io/name: schema-registry
---
# Source: schema-registry/templates/deployment.yaml
# /**
#  * Copyright (c) Dell Inc., or its subsidiaries. All Rights Reserved.
#  *
#  * Licensed under the Apache License, Version 2.0 (the "License");
#  * you may not use this file except in compliance with the License.
#  * You may obtain a copy of the License at
#  *
#  *     http://www.apache.org/licenses/LICENSE-2.0
#  */

apiVersion: apps/v1
kind: Deployment
metadata:
  name: schema-schema-registry
  namespace: default
  labels:
    app.kubernetes.io/name: schema-registry
    app.kubernetes.io/version: "0.1.0"
    app.kubernetes.io/managed-by: Helm
    helm.sh/chart: "schema-registry-0.1.0"
spec:
  replicas: 2
  selector:
    matchLabels:
      app.kubernetes.io/name: schema-registry
  template:
    metadata:
      labels:
        app.kubernetes.io/name: schema-registry
    spec:
      serviceAccountName: schema-registry
      containers:
        - name: schema-registry
          image: "pravega/schemaregistry:0.1.0"
          imagePullPolicy: IfNotPresent
          envFrom:
          - configMapRef:
              name: schema-schema-registry-configmap
          ports:
            - name: rest
              containerPort: 9092
              protocol: TCP
          livenessProbe:
            initialDelaySeconds: 2
            exec:
              command:
                - sh
                - -c
                - netstat -ltn 2> /dev/null | grep 9092 || ss -ltn 2> /dev/null | grep 9092
---
# Source: schema-registry/templates/ingress.yaml
# /**
#  * Copyright (c) Dell Inc., or its subsidiaries. All Rights Reserved.
#  *
#  * Licensed under the Apache License, Version 2.0 (the "License");
#  * you may not use this file except in compliance with the License.
#  * You may obtain a copy of the License at
#  *
#  *     http://www.apache.org/licenses/LICENSE-2.0
#  */

Only passed annotation to the service. Could you explain how you say the annotation applied to the deployment?

@jdmaguire please create an accompanying issue and please use the template for the PR.

Created https://github.com/pravega/schema-registry/issues/162


Cleanup

[ ] Common system (looking to extract later for other CSS libraries)
[ ] columnGap and rowGap

Superseded by #89


wget download the langchain docs failed

I tried your code "wget -r -A.html -P langchain-docs https://langchain.readthedocs.io/en/latest/" to download the langchain-docs, I always failed

changed the url to:
https://python.langchain.com/en/latest/index.html
and this should resolve it

@emarco177  A minor nit. Could you push the change in path for ingestion.py? Since the domain is changed, the folder also is different.
loader = ReadTheDocsLoader("langchain-docs/python.langchain.com/en/latest")

Done thanks!


Add OpenSplat to implementations

Adds another implementation.
By the way, thanks for the extensive list of resources collected in this repo! It definitely helped me navigate the current state of the research.

Thank you!


Create new versions of the link checker api reports tables

For: https://trello.com/c/aqGcNwFT/90-2-whitehall-link-checker-pegs-mysql-at-400-cpu-every-morning
The existing link_checker_api_reports table currently has ~900,000 rows
and no index on the link_reportable_id and link_reportable_type columns.
This makes joining on it expensive.  We'd like to add an index on those
columns, but doing so would take a long time and block the application
because we show link check information on edition show pages.  However,
this data is:

quite new - we only turned on this version of the link checking code
in the middle of january 2018.
quite transient - when we re-enable the overnight link checker we'll
quickly generate link check reports for all the editions.

So it doesn't actually feel that useful to keep it around and go through
the effort of using a tool like lhm or percona to peform
this change directly on the data.  We haven't removed the old version of
the table yet, because we want to apply the indexes to it so we can test
out if having those indexes on a table of that size would actually speed
things up.  We'll add those indexes manually in the console and do
some testing, and then follow up with a new migration that removes the
old tables.  We may decide to back port the existing data if we do decide
it's useful, which is why we've set the auto increment on the new versions
of the tables to start at the max id of the old versions (with a +1000 to
give us some wiggle room for any rows that get inserted after the table
rename, but before the auto increment change.

Intention is to run this on integration as a branch, and then on staging as a branch to let us do the manual testing.  If all good we'll merge and get on production, and then we can probably revert #3810.

Ran this on integration and the renaming part of the migration took a couple of seconds:
12:54:05 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal] -- rename_table(:link_checker_api_reports, :old_link_checker_api_reports)
12:54:05 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal]
12:54:06 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal] -> 1.4384s
12:54:06 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal]
12:54:06 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal] -- rename_table(:new_link_checker_api_reports, :link_checker_api_reports)
12:54:06 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal]
12:54:06 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal] -> 0.0499s
12:54:06 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal]
12:54:06 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal] -- execute("alter table link_checker_api_reports auto_increment = 842937")
12:54:07 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal] -> 0.0072s
12:54:07 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal]
12:54:07 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal] -- rename_table(:link_checker_api_report_links, :old_link_checker_api_report_links)
12:54:07 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal]
12:54:07 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal] -> 0.0075s
12:54:07 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal]
12:54:07 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal] -- rename_table(:new_link_checker_api_report_links, :link_checker_api_report_links)
12:54:07 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal]
12:54:07 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal] -> 0.0078s
12:54:07 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal] -- execute("alter table link_checker_api_report_links auto_increment = 3611775")
12:54:07 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal] -> 0.0072s
12:54:07 *** [err :: ip-10-1-6-139.eu-west-1.compute.internal]

Specifically renaming the old reports table out of the way and then renaming the new one into it's place took ~1.5s.  The individual rename operations are atomic, but it would mean there's a brief blip when we do it where there is no link_checker_api_reports table (because the old one has been moved, but the new one hasn't yet).

Running it on staging took roughly the same amount of time:
15:06:28 *** [err :: whitehall-backend-1.backend.staging.publishing.service.gov.uk] -- rename_table(:link_checker_api_reports, :old_link_checker_api_reports)
15:06:28 *** [err :: whitehall-backend-1.backend.staging.publishing.service.gov.uk]
15:06:29 *** [err :: whitehall-backend-1.backend.staging.publishing.service.gov.uk] -> 1.3208s
15:06:29 *** [err :: whitehall-backend-1.backend.staging.publishing.service.gov.uk]
15:06:29 *** [err :: whitehall-backend-1.backend.staging.publishing.service.gov.uk] -- rename_table(:new_link_checker_api_reports, :link_checker_api_reports)
15:06:29 *** [err :: whitehall-backend-1.backend.staging.publishing.service.gov.uk]
15:06:29 *** [err :: whitehall-backend-1.backend.staging.publishing.service.gov.uk] -> 0.0288s
15:06:29 *** [err :: whitehall-backend-1.backend.staging.publishing.service.gov.uk]
15:06:29 *** [err :: whitehall-backend-1.backend.staging.publishing.service.gov.uk] -- execute("alter table link_checker_api_reports auto_increment = 877147")
15:06:29 *** [err :: whitehall-backend-1.backend.staging.publishing.service.gov.uk]
15:06:29 *** [err :: whitehall-backend-1.backend.staging.publishing.service.gov.uk] -> 0.0938s
15:06:29 *** [err :: whitehall-backend-1.backend.staging.publishing.service.gov.uk] -- rename_table(:link_checker_api_report_links, :old_link_checker_api_report_links)
15:06:29 *** [err :: whitehall-backend-1.backend.staging.publishing.service.gov.uk] -> 0.0062s
15:06:29 *** [err :: whitehall-backend-1.backend.staging.publishing.service.gov.uk] -- rename_table(:new_link_checker_api_report_links, :link_checker_api_report_links)
15:06:29 *** [err :: whitehall-backend-1.backend.staging.publishing.service.gov.uk] -> 0.0050s
15:06:29 *** [err :: whitehall-backend-1.backend.staging.publishing.service.gov.uk] -- execute("alter table link_checker_api_report_links auto_increment = 3361214")
15:06:29 *** [err :: whitehall-backend-1.backend.staging.publishing.service.gov.uk] -> 0.0177s
15:06:29 *** [err :: whitehall-backend-1.backend.staging.publishing.service.gov.uk] ==<PHONE_NUMBER>1807 CreateNewLinkCheckerApiReportsTables: migrated (1.5057s) ====

Closing as we realised just adding the index didn't take too long, so we did that instead (in #3832).


give todo comments a different color than standard comments

The default (darcula) color scheme has this:

ayu-dark-jetbrains does not:

It's useful: todo comments are typically more important and rarer than regular ones.
The parsing and identifying of todo comments is by something else in the IDE, and  the user can toggle it on/off outside of color scheme settings, so ayu-dark-jetbrains does not need to worry about this.

Thank you for creating the issue! The improvement will be shipped with v1.1.0.


Determine migration window with nmfs-openscapes community for prod

- [ ] Determine the community representative for nmfs-openscapes
- [ ] Reach out and coordinate a mutually beneficial migration window

Definition of Done

[ ] A mutually beneficial time window for prod hub unavailability has been agreed upon

@yuvipanda DM'd me with the following:

I was thinking start of your day on Friday? There are no workshops until later this month, and the amount of data is small enough this should be doable. Plus I'm around to provide cover / takeover if you run into issues by the end of your day. And doing it earlier allows us to do much less data transfer.


Submitting Navigraph.NavigraphHub

[/ ] Have you signed the Contributor License Agreement?
[ /] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ /] This PR only modifies one (1) manifest
[ /] Have you validated your manifest locally with winget validate --manifest <path>?
[ /] Have you tested your manifest locally with winget install --manifest <path>?
[ /] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Review required
Added  Navigraph.NavigraphHub
Thanks

This package errored when installed in a Windows 11 VM:

2023-05-15 13:01:16.188 [CLI ] ShellExecute installer failed:<PHONE_NUMBER>

Don't want to say, it working on my end.
Could be you don't have program that it interacts with.

Don't want to say, it working on my end. Could be you don't have program that it interacts with, but is working in Window Sandbox for me - were that program is not present.

Oh - this program interacts with another program? What's the name of that program?

Sorry I didn't put that very well.
The software doesn't depend on another piece of software in order to run but it's a installer that will install to a set location for MSFS. This Application doesn't need to be installed for the software to work.
I've haven't been able to re-produce your issue, could you give me some details on your testing method - I've just followed the steps here: https://learn.microsoft.com/en-us/windows/package-manager/package/repository
I've have tested this on Windows 10 22H2 and Windows 11 22H2 both working as expected.

Closed as new pull request made, with update release of software.


Agent registration defaults to private ip even when public is available

Rancher Version ---
Rancher v1.0.0
Cattle  v0.159.2
User Interface  v0.100.3
Rancher Compose v0.7.3
Docker Version: Docker version 1.10.3, build 20f81dd
OS: Ubuntu 14.04.2 LTS
Steps to Reproduce:
AWS cloud with two instances.
One instance within a private subnet with only access to NAT; only a private IP will be assigned to the machine.
One Instance within a public subnet with access to the internet gateway; private and public IPs will be assigned to the machine.
Both instances are able to communicate with each other within the internal network, using the private IP the two instances are able to communicate on all ports against each other.
The public facing instance has ports 80 and 22 open to the world.
First, the private instance will be used to install the rancher server. The UI can be accessed via ssh-tunneling.
Next, the public instance will grab the project id, token id, and the agent image using curl against the private ip /v1 endpoint of the private instance.
Using the above data, the public instance will run the rancher agent image and register it.
Results: The agent registers successfully against the rancher server, however, the agent registers with its own private ip.
Expected: The expected result was to have the agent register with the public ip as stated within the following doc, http://docs.rancher.com/rancher/rancher-ui/infrastructure/hosts/custom/. Specifically note the statement By default, the IP of a VM with a private IP and public IP will be set to the public IP
Also here is the output of the log using docker log from the rancher agent on the public instance.
INFO: Starting agent for CD18A5DC251692AF13D4
INFO: Access Key: CD18A5DC251692AF13D4
INFO: Config URL: http://rancher.PRIVATE-IP-INSTANCE.com/v1
INFO: Storage URL: http://rancher.PRIVATE-IP-INSTANCE.com/v1
INFO: API URL: http://rancher.PRIVATE-IP-INSTANCE.com/v1
INFO: IP: <IP_ADDRESS>
INFO: Port:
INFO: Required Image: rancher/agent:v0.11.0
INFO: Current Image: rancher/agent:v0.11.0
INFO: Using image rancher/agent:v0.11.0
INFO: Downloading agent http://rancher.PRIVATE-IP-INSTANCE.com/v1/configcontent/configscripts
INFO: Updating configscripts
INFO: Downloading http://rancher.PRIVATE-IP-INSTANCE.com/v1//configcontent//configscripts current=
INFO: Running /var/lib/cattle/download/configscripts/configscripts-1-f0f3fb2e1110b5ada7c441705981f93a480313a324294321cff467f0c3e12319/apply.sh
INFO: Sending configscripts applied 1-f0f3fb2e1110b5ada7c441705981f93a480313a324294321cff467f0c3e12319
INFO: Updating pyagent
INFO: Downloading http://rancher.PRIVATE-IP-INSTANCE.com/v1//configcontent//pyagent current=
INFO: Running /var/lib/cattle/download/pyagent/pyagent-1-9e3dcab12585149a65d818082279708965cd826df1937a55b24f48428f8f0c0673b9f37ae03c16234efdd22657d02b33/apply.sh
INFO: Updating host-api
INFO: Downloading http://rancher.PRIVATE-IP-INSTANCE.com/v1//configcontent//host-api current=
INFO: Running /var/lib/cattle/download/host-api/1-076f245550ef0d977e9dcfe411ef2faebde6b6277c93a3a02a17e69ef6c42c85/apply.sh
INFO: Sending host-api applied 1-076f245550ef0d977e9dcfe411ef2faebde6b6277c93a3a02a17e69ef6c42c85
INFO: Updating agent-binaries
INFO: Downloading http://rancher.PRIVATE-IP-INSTANCE.com/v1//configcontent//agent-binaries current=
INFO: Running /var/lib/cattle/download/agent-binaries/1-4200f9b686342da8e941359211b1d8c5f98877ae293d0ead231d43507f1c9eae/apply.sh
INFO: Sending agent-binaries applied 1-4200f9b686342da8e941359211b1d8c5f98877ae293d0ead231d43507f1c9eae
INFO: Updating python-agent
INFO: Downloading http://rancher.PRIVATE-IP-INSTANCE.com/v1//configcontent//python-agent current=
INFO: Running /var/lib/cattle/download/python-agent/1-a91ca3edd3ab1b58766de4c4206feefa9123274d9b7b999ab48766ca58609528/apply.sh
INFO: Sending python-agent applied 1-a91ca3edd3ab1b58766de4c4206feefa9123274d9b7b999ab48766ca58609528
INFO: Updating cadvisor
INFO: Downloading http://rancher.PRIVATE-IP-INSTANCE.com/v1//configcontent//cadvisor current=
INFO: Running /var/lib/cattle/download/cadvisor/1-21c3283c2bb12833be339f90a0c9a64d933464e475045636b8a43412ad630347/apply.sh
INFO: HOME -> ./
INFO: HOME -> ./bin/
INFO: HOME -> ./bin/cadvisor
INFO: HOME -> ./bin/cadvisor.sh
INFO: Sending cadvisor applied 1-21c3283c2bb12833be339f90a0c9a64d933464e475045636b8a43412ad630347
INFO: Sending pyagent applied 1-9e3dcab12585149a65d818082279708965cd826df1937a55b24f48428f8f0c0673b9f37ae03c16234efdd22657d02b33
INFO: Starting agent /var/lib/cattle/pyagent/apply.sh
INFO: Executing /var/lib/cattle/pyagent/main.py
INFO: Updating host-config
INFO: Downloading http://rancher.PRIVATE-IP-INSTANCE.com/v1//configcontent//host-config current=
INFO: Running /var/lib/cattle/download/host-config/host-config-1-91c08336cd39a5ec2f3dc3b617130380ff2b1a638ca38ad5b59f54fe2925d187/apply.sh
INFO: HOME -> ./
INFO: HOME -> ./etc/
INFO: HOME -> ./etc/cattle/
INFO: HOME -> ./etc/cattle/api.crt
INFO: Sending host-config applied 1-91c08336cd39a5ec2f3dc3b617130380ff2b1a638ca38ad5b59f54fe2925d187
time="2016-03-29T19:34:55Z" level="info" msg="Starting event router."
time="2016-03-29T19:34:55Z" level="info" msg="Watching state directory: /var/lib/rancher/state/containers"
Monitoring mount context of PID 961
time="2016-03-29T19:35:12Z" level="info" msg="Processing event: &docker.APIEvents{Status:\"start\", ID:\"9454ed14ec11d1454b1ee0061d4a1b687fcc05cfea7b7b0e8666dd1cb7cbfe68\", From:\"-simulated-\", Time:0}"
time="2016-03-29T19:35:12Z" level="info" msg="Processing event: &docker.APIEvents{Status:\"start\", ID:\"68049f66ecd2b772fffa991d7e9aa5720b3c68be0fcd6b3e1d13f76ce0ee1f45\", From:\"-simulated-\", Time:0}"
time="2016-03-29T19:35:12Z" level="info" msg="Connecting to proxy." url="ws://rancher.internal.fitzy.co/v1/connectbackend?token=eyJhbGciOiJSUzI1NiJ9.eyJleHAiOjE0NTkyODA0MTIsInN1YiI6ImNhdHRsZSIsImlzcyI6Imh0dHA6XC9cL2NhdHRsZS5pbyIsInJlcG9ydGVkVXVpZCI6Ijk1YjA2ZjAwLWQzNDktNGQ4NC04ZTJhLTEwODMzNjFhYWFmYyIsImlhdCI6MTQ1OTI4MDExMiwia2lkIjoiZGVmYXVsdCJ9.FDZ0SvnQ-RoZ0EYpEntk8pPPKwhsrQM_6BEPcLorXyWXVP49brxeoWlNJ2BzjGg2NGt1zd7k7JHqsFJJwuqzut_3_aoiueep8G_jU_fAzdN2AG5i-YIWbmCswRoTII-4EOOHOiYbsxo8nx-s4K7_3ZyutVx5bbSi79yYL7KDjoYKPRFwPUqQyPcCGwrhL3-qt72y66-7kdRVhZgbw5xJigmX2GVjSMivN4yI81YyoBRVTovcGN7PQbfsB64FjSg-TZCYN57gDpCp1UxCFhO5FD1ZVOL9ot8ahuOiNVFeDgQALFie1NQ0YJX9xzPLfToLleUYATiiwuHv43lcoaejOQ"
time="2016-03-29T19:35:14Z" level="info" msg="Processing event: &docker.APIEvents{Status:\"start\", ID:\"68049f66ecd2b772fffa991d7e9aa5720b3c68be0fcd6b3e1d13f76ce0ee1f45\", From:\"-simulated-\", Time:0}"
time="2016-03-29T19:36:54Z" level="info" msg="Processing event: &docker.APIEvents{Status:\"start\", ID:\"671ab21f6fe1045b460d0b0766d5015bc85f5ad3e843987496244cff7b56d255\", From:\"rancher/agent-instance:v0.8.1\", Time:1459280214}"
time="2016-03-29T19:36:54Z" level="info" msg="Assigning IP [<IP_ADDRESS>/16], ContainerId [671ab21f6fe1045b460d0b0766d5015bc85f5ad3e843987496244cff7b56d255], Pid [20465]"
time="2016-03-29T19:36:54Z" level="info" msg="Processing event: &docker.APIEvents{Status:\"start\", ID:\"671ab21f6fe1045b460d0b0766d5015bc85f5ad3e843987496244cff7b56d255\", From:\"-simulated-\", Time:0}"
time="2016-03-29T19:37:04Z" level="info" msg="Processing event: &docker.APIEvents{Status:\"start\", ID:\"bafde55c22f9484e230f493f7f6d9f0f339ce6e2ef6b680c7281bf3d3d170477\", From:\"rancher/external-dns:v0.3.0\", Time:1459280224}"
time="2016-03-29T19:37:05Z" level="info" msg="Assigning IP [<IP_ADDRESS>/16], ContainerId [bafde55c22f9484e230f493f7f6d9f0f339ce6e2ef6b680c7281bf3d3d170477], Pid [21487]"
time="2016-03-29T19:37:05Z" level="info" msg="Processing event: &docker.APIEvents{Status:\"start\", ID:\"bafde55c22f9484e230f493f7f6d9f0f339ce6e2ef6b680c7281bf3d3d170477\", From:\"-simulated-\", Time:0}"

If you want it to be the public IP, you can always set it by re-registering the agent and adding -e CATTLE_AGENT_IP=<public_ip> into the docker run command. Typically, we've seen in the case of both a public and private IP, it tends to pick the public but was this machine also hosting your rancher/server?
http://docs.rancher.com/rancher/faqs/agents/#how-does-the-host-determine-ip-address-and-how-can-i-change-it-what-do-i-do-if-the-ip-of-my-host-has-changed-due-to-reboot

The rancher/server image was only running on the private ip instance. The rancher/agent image was running on the second instance which had a private ip and a public ip.
A work around that I ended up using was to move the rancher/server image to an instance which had access to the internet gateway thus allowing the instance to have a public ip and private ip.
However, I would prefer to have my original case since it allows me to isolate rancher/server - giving me the peace of mind that the outside world would not be able to communicate with the rancher/server.

@VDuda I believe you found a bug in our documentation. :-) The docs are misleading as they assume the more typical scenario of the rancher-server being exposed on a public IP and thus the agent connecting to it by going out through its public interface instead of the private network.
rancher/server "guesses" the IP of a host based on the source IP of the agent making the request. So, if you are staying completely within your private network, we will only ever be able to guess the private IP.

@deniseschannon Maybe you could update the docs to be more clear. Here's what it currently states:

By default, the IP of a VM with a private IP and public IP will be set to the public IP. If you wanted to change the IP address to the private one, you’ll need to edit the command provided from the UI. In order for the rancher-agent container to be launched correctly, set the CATTLE_AGENT_IP environment variable to the private IP address. All the hosts within Rancher will need to be on the same network as Rancher server.

maybe it could be pudated to something like:

By default, the IP of a VM with a private IP and public IP will be set to match the IP specificied in the registration URL. For example, if a private IP is used in the regirstation URL, then the host's private IP will be used. If you wanted to change the host's IP address, you’ll need to edit the command provided from the UI. In order for the rancher-agent container to be launched correctly, set the CATTLE_AGENT_IP environment variable to the desired IP address. All the hosts within Rancher will need to be on the same network as Rancher server.

Thanks @cjellick. Updated docs with your recommendations.

@VDuda If you have further questions, please re-open. As @cjellick mentioned, it looked like our docs weren't clear enough, which have been corrected since.

yeah, I'm seeing a different behavior. Registration URL is set to public IP but it's using the private IP anyway. Using 1.6.2 (new install). This is on AWS.


add login and registration routes

This PR implements #6. Summary of the changes :

adds login, register routes
modifies home page to render index.html
adds the template directory which contains all the templates
updates the requirements

Testing
I started the flask app using the below command  and then browsed to http://<IP_ADDRESS>:5000/login and http://<IP_ADDRESS>:5000/register
docker-compose up -d --build

@Vai2021 a couple pull requests were approved and their branches merged into the main branch. This has caused merge conflicts that will prevent your branch from merging in until they are resolved. These merge conflicts are quite common. If you're not familiar with dealing with merge conflicts then we can get together soon and I'll walk you through it.

@Nunie123 I have made the requested changes. Can you please re review the PR ? Thanks.

@Nunie123 , Made the requested changes. Can you please review once again.


README wording tweaks

Thanks, but can you sign-off your commit? https://github.com/docker/datakit/blob/master/CONTRIBUTING.md#sign-your-work

LGTM (once sign-off is added).

@thaJeztah is it easy to set up the bot to check for this?

@samoht it's done through both https://github.com/docker/leeroy, and https://github.com/docker/docker/blob/master/hack/make/validate-dco
perhaps @icecrime knows how the bot (Leeroy) is set up

But I'd love to have a document describing how to set it all up :smile:

@icecrime, @thaJeztah: I'd love to have DCO checking for docker/hyperkit too...

I've signed the commit (e60f570).

Thanks!


update sync with k8s function - [closed]

In GitLab by @sokril on Dec 11, 2017, 06:12
Merges sync -> dev

In GitLab by @wknet123 on Nov 13, 2019, 10:17
the coverage is  % check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:17
the build is FAILED console log

In GitLab by @wknet123 on Nov 13, 2019, 10:17
the coverage is  % check console log

In GitLab by @wknet123 on Nov 13, 2019, 10:17
closed


Merge "rc" into "main"

Approval PR for a manual merge

Created with:
In repo dir
git checkout main
git pull
git checkout rc
git pull
gh pr create --head rc --base main -t 'Merge "rc" into "main"' -b "Approval PR for a manual merge"

After approval I will run:
git checkout main
git merge rc
git push

I have no idea why this is not up to date.

Created with:
In repo dir
git checkout main
git pull
git checkout rc
git pull
gh pr create --head rc --base main -t 'Merge "rc" into "main"' -b "Approval PR for a manual merge"

After approval I will run:
git checkout main
git merge rc
git push

I wonder who wrote that

Created with:
In repo dir
git checkout main
git pull
git checkout rc
git pull
gh pr create --head rc --base main -t 'Merge "rc" into "main"' -b "Approval PR for a manual merge"

After approval I will run:
git checkout main
git merge rc
git push

I wonder who wrote that

Jared did. Figured we should bring that along every PR that needs it.


It's redundant to ask for layer type when creating a layer

@AbelVM commented on Thu Jul 14 2016
It's compulsory to add type attrib as parameter when creating a layer, but the type is implicit in the function name:
createCartoDBLayer({...type:'CartoDB'...})
createTorqueLayer({ ...type: 'Torque', ...})
...

It would be way simpler if the type is defined only once as a parameter instead of having 6 different functions:
createLayer({...type:'CartoDB'...})
createLayer({ ...type: 'Torque', ...})
...

On this topic I recall @javisantana wrote this comment motivating why he thought it was better to have separate methods over a generic one.

There's this bug.  You will not need to set the type once this is fixed.

:+1:

Closing this issue then. I will fix https://github.com/CartoDB/cartodb.js/issues/1297 now and we won't need the layer types anymore.


de_DE

replacing all en_US messages with german translations.

Added in commit https://github.com/bloodmc/GriefDefender/commit/d22fdc01969736605ba0838dde13083d4bc9bfbc
Thanks!


make golint happy

The generated documentation was interpreted as package documentation. This was wrong. The generated documentation is supposed to inform about the code generation itself, not about the package it is generated into. This PR fixes this to make golint happy again.

LGTM


Update .ruby-version to 3.2.2

Upgrades Ruby to 3.2.2. See commits for more details.
This PR should be tested before merge, as per https://docs.publishing.service.gov.uk/manual/ruby.html#update-ruby-version-in-the-relevant-repos.
Trello card: https://trello.com/c/K1grjTiC/3373-upgrade-ruby-versions-to-322-2

Thanks @robinjam , I was just looking into this!


fixes #495 Added support for formatting notifications

Also noticed that locks with binary data were not properly formatted and fixed
that.

The diffs for FluoFormatter in this PR are much easier to look at when ignoring white space.


dart2js erroneous warning

new Set.from(someList == null ? [] :
    someList);
outputs:
--- Dec 6, 2013 10:27:42 AM Running dart2js... ---
myexample.dart Warning: 'EfficientLength' is not assignable to 'Iterable<dynamic>'.
        new Set.from(someList.channelIds == null ? [] :
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
lib/core/set.dart:54:11: Info: This is the method declaration.
  factory Set.from(Iterable<E> other) = LinkedHashSet<E>.from;
          ^^^
This is not expected.

Whatever this was has been fixed. Try in Dart Pad:
void main() {
  var someList = ['a', 'b'];
  var l2 = new Set.from(someList == null ? [] : someList);
  print(l2);

  someList = null;
  var l3 = new Set.from(someList == null ? [] : someList);
  print(l3);
}

It prints:
{a, b}
{}


Update jwt-issuer-technical-profile.md

Added missing PartnerClaimType="tfp"
Relates to issue #116734

@kengaderdus
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@sebastiandemel Thanks for your contribution! #sign-off


Create separate wheel for CUDA

This is to package CUDA as a separate wheel rather than including it in the main one.

It's working for Linux, which is enough for this PR.  I'll work on the Windows packages in another PR.


Consider incorporating 'animalese' chat sounds

https://github.com/mattmarch/ACVoicebox
This may or may not clash with the cutesy noises we have going on in the puzzles. We want the characters to sound somewhat consistent.

To increase consistency, you could create your own set of sounds using the voice packs you're using in the game.

You also have some good sounds in the Cartoon Voices pack like "cartoon voices male talking bubble 1.wav" , although you do not have female versions of them.


English synthesis broken.

With cca9a06 it seems like the app can not synthesize english voice anymore.
This is with cca9a06:

Compared to aa7c3f6 with same model and settings:

Interestingly german synthesis still seems to work fine with cca9a06:

I tried to infestigate myself but could not really pin the issue down.
If this was still WIP feel free to close.

fixed with 051a1fb


The automated release is failing 🚨

:rotating_light: The automated release from the beta branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the beta branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Cannot push to the Git repository.
semantic-release cannot push the version tag to the branch beta on the remote Git repository with URL<EMAIL_ADDRESS>This can be caused by:

a misconfiguration of the repositoryUrl option
the repository being unavailable
or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the beta branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the beta branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Cannot push to the Git repository.
semantic-release cannot push the version tag to the branch beta on the remote Git repository with URL<EMAIL_ADDRESS>This can be caused by:

a misconfiguration of the repositoryUrl option
the repository being unavailable
or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨
Your semantic-release bot :package::rocket:

Last push cloud be failing due to presence of yarn.lock file, something to do with chalk, in this issue others have suggested some workarounds ,
"resolutions": {
    "npm/chalk": "^4.1.2"
},

@nodece what are your thoughts?

:rotating_light: The automated release from the beta branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the beta branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Cannot push to the Git repository.
semantic-release cannot push the version tag to the branch beta on the remote Git repository with URL<EMAIL_ADDRESS>This can be caused by:

a misconfiguration of the repositoryUrl option
the repository being unavailable
or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨
Your semantic-release bot :package::rocket:

Last push cloud be failing due to presence of yarn.lock file, something to do with chalk, in this issue others have suggested some workarounds ,
"resolutions": {
    "npm/chalk": "^4.1.2"
},

@nodece what are your thoughts?

I'm not sure what happened, this is my personal token.
fatal: unable to access 'https://github.com/casbin/casbin-core.git/': The requested URL returned error: 403.

Disable the semantic-release.


Add titano

Drafting this to check build before review

As I've reverted the branch of ci-arduino change, I thought there needs to be a merge of https://github.com/adafruit/ci-arduino/pull/177 however the build has completed regardless.

May not be ready for prime time, or at least I can't get my titano to boot correctly (red light of doom)

This will be included/superseded by #540


Electricity demand on high voltage net has a missing query

When I try to open the Electricity demand on high voltage net chart the model crashes:
- Gquery hv_industry_metals_load_curve does not exist

This is probably due to changes in the steel sector modelling.

Due to changes in the steel sector, no metal sector nodes now remain on the HV net. See this commit.
Therefore the HV metal series is removed from the chart.


Powershell Direct doesn't respect $PSSessionConfigurationName

Steps to reproduce
$PSSessionConfigurationName = "Powershell.7"
Enter-PSSession -VMName myvm -Credential (Get-Credential)

Expected behavior
[myvm]: PS c:\> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      7.3.0
PSEdition                      Core
GitCommitId                    7.3.0
OS                             Microsoft Windows 10.0.25217
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Actual behavior
[myvm]: PS c:\> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      5.1.25217.1000
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.25217.1000
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Error details
No response
Environment data
Name                           Value
----                           -----
PSVersion                      7.3.0
PSEdition                      Core
GitCommitId                    7.3.0
OS                             Microsoft Windows 10.0.22623
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

You need to add -ConfigurationName $PSSessionConfigurationName to your command otherwise it will default to the 5.1 session.

@kilasuit $PSSessionConfigurationName should still work, it's designed to be the default configuration name pwsh connects to if defined as per https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_preference_variables?view=powershell-7.3#pssessionconfigurationname.

Still the problem here is that AFAIK configuration names only apply to the WinRM/WSMan PSRemoting sessions as it's a specific part of that protocol. I'm unsure if the Hyper-V based ones (what -VMName selects) supports such a thing. IIRC it does but I'm unsure how it is actually plumbed in. If it does support it then it would make sense for it to also use $PSSessionConfigurationName.

Looks like it is in there https://github.com/PowerShell/PowerShell/blob/9c55e1e9ab7f77d8a16d28648db5a22978e087ba/src/System.Management.Automation/engine/remoting/common/RemoteSessionHyperVSocket.cs#L589
Would have to step through the code to see why $PSSessionConfigurationName isn't being applied there.

@jborean93 The client is Windows 11 and I tested Powershell Direct against the most recente Azure Stack HCI Preview (build 25217), against Windows Server 2022 build (20348), and against Windows 11 Insider Preview build 25236, so we can exclude a too old version of Windows, I think.

Why close this issue? It is not answered, the bug still there.

@leoniDEV it's was just an automated closure based on me adding the resolution-answered label. I've corrected this by reopening this issue & re-routing this to the right Working Group to investigate further. That was my bad & I apologise for the inconvenience caused


update the minio server

The current minio master is not very stable and the release version of minio doesn't have the fix for multi-part upload.So we cloned the minio repo and cherrypicked the commit.
This PR is to use the deis version of the minio server.
Update by mboersma
Closes deis/workflow#367.

This PR changes deis/minio to build from the "deis" branch of https://github.com/deis/minio-src, which is minio tag OFFICIAL.2016-02-08T00-12-28Z plus a multipart upload fix. I've tried the before/after tests several times and this does fix deploying example-ruby-sinatra. I've tested the other Deis example buildpack and Dockerfile apps with git push deis master too and had success.

:boom: !!
Sent from my iPhone

On Feb 25, 2016, at 17:44, Matt Boersma<EMAIL_ADDRESS>wrote:
This PR changes deis/minio to build from the "deis" branch of https://github.com/deis/minio-src, which is minio tag OFFICIAL.2016-02-08T00-12-28Z plus a multipart upload fix. I've tried the before/after tests several times and this does fix deploying example-ruby-sinatra. I've tested the other Deis example buildpack and Dockerfile apps with git push deis master too and had success.
—
Reply to this email directly or view it on GitHub.


Running multiple evaluations on the same task

Prior to the "Group agg rework" commit, I was able to run multiple evaluations on the same task in the same run, like this:
group: taskA
task:

  - task: taskA_fs0
    include: _taskA.yaml
    num_fewshot: 0

  - task: taskA_fs1
    include: _taskA.yaml
    num_fewshot: 1

  - task: taskA_fs3
    include: _taskA.yaml
    num_fewshot: 3

  - task: taskA_fs5
    include: _taskA.yaml
    num_fewshot: 5

Now, I am unable to run bencmarks in this way. Changing include: _taskA.yaml to something like task: _taskA throws Please call groups which overlap their constituent tasks in separate evaluation runs., as somewhat expected.
I tried using tag and tag_alias to no avail. How am I supposed to run tasks like above? It this still supported?

Could you share a more full repro of some kind that I can use to get this error and inspect what your group looks like a bit more?
From what I understand, in your current posted config file, because these tasks have different names, this should be the way we recommend usage like your case. So I'm not sure why this is erroring.
But yes, the reason we throw an error like this is because (for now) the different num_fewshot variants of the "same" task would compete to overwrite each other and create confusion in logged files' contents, etc.

Could you share a more full repro of some kind that I can use to get this error and inspect what your group looks like a bit more?
Sure. My fork is here [1]. My tasks are under tasks/romanian_bench. With the exception of ro_truthfulqa they are all in the same format as stated above. Note that in order to make "include" work in the last version, I had to change a line in yaml task loading (check last commit).

But yes, the reason we throw an error like this is because (for now) the different num_fewshot variants of the "same" task would compete to overwrite each other and create confusion in logged files' contents, etc.
This makes sense, but as you mentioned they have different names, and prior to the group rework, everything worked just fine.

[1] https://github.com/MihaiMasala/lm-evaluation-harness

Do you have any updates on this?


[STORM-609] Add storm-redis to storm external

@HeartSaVioR  and I have added abstract bolt  and trident state implementations, we also add some test cases, and modify the readme usage.
Anyone can help review?

@dashengju
Though there're some points to reduce round-trip to Redis, looks good to me. Great job!
Seems like we're ready to review our effort to Storm community and finally merge into Storm Project.

@HeartSaVioR , thanks for your careful review, I have changed all the notes.

@dashengju Great! Thanks for applying.

@harshach @revans2 @ptgoetz
I'd like to hear your thoughts about this.
Anything including code reviews, thought about Storm + Redis, and so on is very appreciated.
Thanks in advance!

My biggest comment is that there are some TODOs in the code that look like they have already been addressed and should be deleted.  I would like to see some unit tests at some point too, but the integration test/examples seem like a good start.  I am +1 for merging this in, although I would like others to take a look at the code as well.
The committer question for @dashengju and @HeartSaVioR would need to be discussed on the private list, but if it helps to get this in, I am willing to lend my name to support the code as well.

@revans2
About tests, integration tests are based on storm-hdfs.
I'm not familiar with Storm unit tests (don't know @dashengju is familiar with) so it takes some time for adding.
About sponsors, I'm ready to follow Storm Project rule. :)
I'll support storm-redis module whether I will be added to sponsor or not, cause both are my favorite things.

@dashengju
For your information, Jedis team is discussing about Jedis 3.0, and ShardedJedis could be replaced to JedisCluster for reducing code complexity.
https://groups.google.com/d/msg/jedis_redis/7ZJPFp_qTY0/ISHqEPZlAnwJ

@HeartSaVioR and @dashengju Thanks for the patch and I think overall the code looks good.
I am little confused about the core bolt. You have a trident state and query function but in the core implementation you just provide an abstract bolt. Any reason why the core functionality can not be extended to support the basic persist and lookup features out of the box? You already have a mapper interface for trident and instead of taking the tridentuple as input you could change the type to ITuple so it will be able to support both trident states and core bolt. It is ok to leave this implementation as is and file a jira to add the core persist and lookup bolts later or document why it is not a good idea to do so.
Also I think the README should be more detailed. you probably want to document that users trying to use core features needs to extend AbstractRedisBolt and how they should be using methods from the parent class. The trident section should cover the query functions and your probably want to remove ShardedRedis related classes from README as they don't exist.

@Parth-Brahmbhatt
Thanks for review!
First of all, let's start about abstract bolt.
https://github.com/apache/storm/pull/365#issuecomment-68332013
You can see the matrix I've commented.
Redis provides so many data types so we need to decide what data types we support or not.
I thought JedisCommands is easy and convenient enough to use so users would no problem to extend abstract bolt and make his/her own bolt.
But I'm also thinking it is really better for users to force making bolt, instead of providing some simple bolts. It could be already inconvenient to use in point of users' view.
@revans2 @dashengju How do you think about?
Btw, persist/lookup bolts for some datatypes can be added at any time.
Also, changing mapper to support normal bolt and trident seems great.
We can check it now, and provide some bolts based on it if it works smoothly.
Thanks for your help!
Then let's talk about README.md.
Describing usage of AbstractBolt to README.md is already done, please see AbstractRedisBolt usage.
I agree we should remove description related to SharededJedis. I'll take care of it.

@revans2 ,  I have added you to the committer. thanks.

@revans2 @dashengju
Just I'm confused about 'Committer Sponsor'. Is it explained from docs? I can't find it.
If it doesn't exist, could you explain it?
Maybe it's better to have description about 'Committer Sponsor' to BYLAWS.md.

@HeartSaVioR , It is explained in README.md

@dashengju
No, I mean that "What is Committer Sponsor and where can I find description?".
I think if it is "Committer" Sponsor then we cannot be included, but if it is Committer "Sponsor" then we can be included.

@dashengju
I don't think we ever explained it in the docs.  I believe it was more of a discussion on the mailing lists when the kafka integration code was brought in.  The main goal behind this is when we bring in a new significant piece of code, that we are sure there is enough support from the community that it will not become abandon-ware.  There was nothing formally adopted as far as I remember, or it would be in the bylaws.  I mainly wanted to add my support to help maintain it so there would be less doubt about bringing it in.  Both you and @HeartSaVioR have already done a lot of work on Storm so I don't think there would be much doubt anyways.

+1 the changes still look good
Are there any other committers that want to take a look at the code?  I would feel more comfortable with more people looking at the code, just because it is so large.  If no one wants to take a look I guess I'll just pull it in sometime next week.

I'll address follow-up issue, providing some persist / lookup bolts after merged to master.

I wish to hear additional opinions, and finally see it pulled in master. :)

@dashengju
According to #416, we should remove ourselves from "committer sponsors" to let storm-redis module can be merged into master.
Thanks for clarification, @ptgoetz.

@HeartSaVioR , @ptgoetz
I agree with "committer sponsors" only committers can join external's "committer sponsors".
I have changed the committer sponsors members in Readme, @ptgoetz , please help to review.

Since we changed committer sponsor, seems like we can pull this in.

+1, sorry it took so long to get in.


Skip lines that start with #

Add the ability to comment out lines in plugin.txt

can you add a test to https://github.com/jenkinsci/docker/blob/master/tests/install-plugins/pluginsfile/plugins.txt ?

ping @moatazelmasry2

Yes sorry about the delay. I'll get it done this week.

done in #622


universal2 wheels

Try if new compiling method works for some lucky reason.

OK, I've found the problem.
It's a cross-compilation to ARM on amd64 and it's trying to use the optimized version!

@henryiii OK, I think I've made it smart now. Care to have a quick look and tell me what you think?

Looks good. Is there an easy way for me to test on an M1? (Specifically, is there a good way to run the test suite on an existing wheel?)

I know of none. :( Still M1-less myself.
This code is on PyPI so a good way to test would be to run the test suite of current main of argon2-cffi

Guessing this is what I'm supposed to see?
% time tox -e py310
.package create: /Users/henryfs/git/software/argon2-cffi/.tox/.package
.package installdeps: flit_core >=3.4,<4
py39 create: /Users/henryfs/git/software/argon2-cffi/.tox/py39
py39 inst: /Users/henryfs/git/software/argon2-cffi/.tox/.tmp/package/1/argon2-cffi-21.2.0.dev0.tar.gz
py39 installed: argon2-cffi @ file:///Users/henryfs/git/software/argon2-cffi/.tox/.tmp/package/1/argon2-cffi-21.2.0.dev0.tar.gz,argon2-cffi-bindings==21.2.0,attrs==21.2.0,cffi==1.15.0,coverage==6.2,hypothesis==6.29.0,iniconfig==1.1.1,packaging==21.3,pluggy==1.0.0,py==1.11.0,pycparser==2.21,pyparsing==3.0.6,pytest==6.2.5,sortedcontainers==2.4.0,toml==0.10.2,tomli==1.2.2
py39 run-test-pre: PYTHONHASHSEED='996790143'
py39 run-test: commands[0] | python -m pytest
============================================= test session starts =============================================
platform darwin -- Python 3.9.9, pytest-6.2.5, py-1.11.0, pluggy-1.0.0
cachedir: .tox/py39/.pytest_cache
rootdir: /Users/henryfs/git/software/argon2-cffi, configfile: pyproject.toml, testpaths: tests
plugins: hypothesis-6.29.0
collected 67 items

tests/test_legacy.py ..................
tests/test_low_level.py ........................
tests/test_password_hasher.py .............
tests/test_utils.py ............

============================================= 67 passed in 2.08s ==============================================
py39 run-test: commands[1] | python -m argon2 -n 1 -t 1 -m 8 -p 1
Running Argon2id 1 times with:
hash_len: 16 bytes
memory_cost: 8 KiB
parallelism: 1 threads
time_cost: 1 iterations

Measuring...

0.0ms per password verification
___________________________________________________ summary ___________________________________________________
  py39: commands succeeded
  congratulations :)
tox -e py310  7.94s user 1.16s system 110% cpu 8.235 total

Takes 15 seconds on my Intel Mac, and 8 seconds on my M1.

I could have compiled it in the background…i guess the wheel test would be an pip install argon2-cffi-bindings and look what it does. 🤔

Does it take less than 8 seconds to compile?

Well I’m hearing the M1 are really fast. 😅 But unlikely, yeah.


When I try to run the game, it doesn't support Direct11 and I can't run it.

Configuration

UTM Version: 4.4.5 (94)
macOS Version: 14.2.1（23C71）
Mac Chip (Intel, M1, ...): M1 Max

Crash log
A D3D11-compatible GPU (Feature Level 11.0,Shader Model 5.0)is required
to run the engine.

Yes, this is a known issue --- I'm assuming you're either using Wine or using a Windows VM. ANGLE on mac
OS isn't full-featured to provide all of the needed features. Moving to Vulkan will probably help, but that is not a trivial endevour.


Test suite issue with pandas 1.5

Bug Description
Debian wants to upgrade pandas to version 1.5.  In connection with this pandas version the test suite of q2templates throws an error.  This is documented in a bug report.
Steps to reproduce the behavior
You can install the prerequisites (specifically pandas 1.5) as we used in the full build log.  This ends with the following error:
=================================== FAILURES ===================================
______________________ TestDataFrameToHTML.test_defaults _______________________

self = <q2templates.tests.test_util.TestDataFrameToHTML testMethod=test_defaults>

    def test_defaults(self):
        df = pd.DataFrame({'col1': ['foo', 'bar', 'baz'], 'col2': [1, 2, 4.2]})

        obs = df_to_html(df)

>       self.assertIn('border="0"', obs)
E       AssertionError: 'border="0"' not found in '
\n
\n
\n      	\n      col1	\n      col2	\n
\n
\n
\n
\n      0	\n      foo	\n      1.0	\n
\n
\n      1	\n        bar	\n      2.0	\n
\n
\n      2	\n      baz	\n      4.2	\n
\n
\n
'

q2templates/tests/test_util.py:33: AssertionError
=========================== short test summary info ============================
FAILED q2templates/tests/test_util.py::TestDataFrameToHTML::test_defaults - A...
========================= 1 failed, 2 passed in 0.33s ==========================

Expected behavior
Passing the test suite as with previous pandas version.
Computation Environment

OS: Debian (unstable + python3-pandas from experimental)
QIIME 2 Release: 2022.8.0

Kind regards, Andreas.

Hey @tillea,
I believe we fixed this in this PR: https://github.com/qiime2/q2templates/pull/49
You could either apply that patch, or wait for the 2022.11 release which should be out end of next week. It looks like our current version of pandas for the core distribution is 1.5.1.
As always, thanks for the report!

Hi,
Am Fri, Dec 09, 2022 at 10:12:31AM -0800 schrieb Evan Bolyen:

I believe we fixed this in this PR: https://github.com/qiime2/q2templates/pull/49
You could either apply that patch, or wait for the 2022.11 release which should be out end of next week. It looks like our current version of pandas for the core distribution is 1.5.1.
Thanks a lot.  I've applied the patch to the Debian package.  There is no need for an intermediate release.

As always, thanks for the report!
You are welcome, Andreas.


lint project using Ruff

Ruff is a rust based python linter that enforces beautiful code standard. Can I apply it to this package?
https://github.com/astral-sh/ruff#ruff

Hey @alon-david , thanks for the idea.
@rnowling-memphis any thoughts?

Thanks for the suggestion @alon-david .  We recently started using Pylint (older but serves a similar function).  Our code base is pretty small so run-time isn't much of an issue, but the team is still adjusting to using Pylint effectively in our work.  I'm hesitant to do a bait and switch on them until they are at least comfortable using Pylint as a tool rather than seeing it as a hinderance.  :)  E.g., I'd like to get to a point where the code base is clean enough that we aren't disabling any of the Pylint checks.

Hi @alon-david, thank you for this one absolutely amazing but I had to say that I agree with @rnowling-memphis


Added cgroup_sock_addr2 related files to deploy-ebpf and Product.wxs script

Description
In deploy-ebpf.ps1, cgroup_sock_addr2 test related files were added to deploy in the test VM.
In Product.wxs, cgroup_sock_addr2 related files were added. GUID was created using the VS tool.
Testing
There is no existing test coverage. deploy-ebpf script is for deploying the files.
Documentation
No

Closes #2174


Is .NET Framework target with ASP.NET Core supported for controller output?

I have a project which targets .Net Framework 4.7 instead of .Net Core (due to some libraries that won't work with .Net Core) but am using ASP.Net Core 2.2. I don't see an option for this in NSwag Studio when generating C# controllers? What is generated uses System.Web.* and this doesn't work with .NET Framework it seems ...

Controller generators do not support asp.net core output yet, but you can override templates, etc

Ah, ok. Is there any documentation on template overriding?

https://github.com/RSuter/NSwag/wiki/Templates
And i think there are some open issues with this topic

I'll have a look - if I have the ZIP distribution, how do I use a custom template with nswag.exe? Or do I need to edit the default template?
Do you know if XML comments should make it into the Swagger UI with ASP.Net Core too? The XML doc is being generated but nothing is showing up in the UI. Obviously, I'd rather generate the other way around, from the YAML spec but then I need to fix the template ...

You can copy the originals from github and point the nswag.exe to this dir

I am playing at customising controller templates for what I need but it seems that I can't reference, for example, parameter.Kind throws an error about, e.g. Path or Query not being a built in type or ILiquidizable. I can't see any other way to find out where the parameter came from?

The models can be found e.g. here: https://github.com/RSuter/NSwag/blob/master/src/NSwag.CodeGeneration.CSharp/Models/CSharpControllerTemplateModel.cs (and more in this directory). If a property is missing - please create a PR with it and we can discuss/add it.
I would be great if we could enhance the templates so that they also support ASP.NET Core (there are already some open issues for that).

Project with all open controller generator issues: https://github.com/RSuter/NSwag/projects/4


refactor(all): better interfaces, add router event export, more tests

This is now ready for review.

refactor to TS
ensure compat with latest release
add export RouterEvent for better typings/hooks
include fix #619

For comparison, typings is based on 1.5.0 release (same for 1.6) at https://github.com/aurelia/router/blob/2a8a16622dc162c9bd24028a76420692f2a0882a/dist/aurelia-router.d.ts

The latest commits https://github.com/aurelia/router/pull/632/files/26facc5f83fd7bb48da8e5015efb943e913c21f7..7d3ee63e77d585f7964ea6706163e1cd2dff7691 will export a few critical information related to router event enum and pipeline slot name enum, along with some comments for better understanding & usage

@bigopon Is this ready?

@EisenbergEffect yes it is ready. Everything has been reverted to internak refactoring instead of aiming for a 2.0 beta. Its a big refactoring so if needed, we can do a RC release

@bigopon What is the release process for this library now? Just build and release from master? After this next release, will we be able to use the develop branch and align this process with the other updated repos?


fix: update readme

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


[FEATURE] Independence between offline estimation and Battery Data Toolkit

Is your feature request related to a problem? Please describe.
Not really, but more of an inconvenience. Ideally, the offline estimation should be able to be run independent of how the data is stored. However, the base class moirae.estimators.offline.loss.BaseLoss requires keyword argument observations to be passed as a batdat.BatteryDataset, somewhat breaking modularity and mutual independence of the package.
Describe the solution you'd like
Preferably, the observations keyword could be passed as a dictionary of the form
observations: {'inputs': List[GeneralContainer], 'outputs': List[GeneralContainer]}
Additional context
In many cases, especially for testing, but also when working with collaborators, the data is not available in the `battery-data-toolkit' form. This makes it so we need to add an additional intermediate step in order to run an estimation.
Tagging @WardLT for discussion

Great point!


Prompt for device name before starting kex

In the existing kex2 device provisioning, the user does:

new device: login
new device: choose an existing device
new device: told a secret to input into existing device
existing device: device add
existing device: enter secret
new device: handle hello, enter a new device name
existing device: countersign
new device: post sigs

A problem that has been showing up in the logs is that in step 6, the user takes a while to enter a device name and the existing device either times out, or they stop the app.  So when 6 is finally complete, there is no device to countersign.
In this flow, kex starts on the new device at step 3.  It starts on the existing device at step 4.  There is a delay at step 6 while the user enters a device name.
In the CLI UX we added all these magenta banners to try to alert the user about this flow and keep them interacting on the correct device and not shutting down the existing device.
But, I think a better flow is:

new device: login
new device: choose an existing device
new device: enter a new device name
new device: told a secret to input into existing device
existing device: device add
existing device: enter secret
new device: handle hello
existing device: countersign
new device: post sigs

Kex starts running on the new device at step 4 in the new flow.  It starts running on the existing device after step 6.  After step 6, there is no user interaction needed, so the whole exchange should be very quick with less chance of failure.
An added benefit of this change is that the prompt for the device name at step 3 in the new flow now retries 10 times with helpful prompts on what is wrong with the name.  The current flow this replaces has no such check and relies on the server to reject bad/existing names.
cc: @chrisnojima @malgorithms

this sounds good to me

Seems like a much better move.