It would be nice if the validation error messages referenced a schema by its title rather than its UUID

Currently when I get a validation error message, it ends with something like  in schema ecff90d3-5502-54ba-b62f-5969d00a49c8. But my schema does have a title — it would be nice if that was used instead of the UUID. It would make the error messages slightly more friendly and useful.
BTW, great lib. Thank you!

Great idea!

@aviflax, @jaybloke  Try giving your schema an id property. (http://spacetelescope.github.io/understanding-json-schema/structuring.html#the-id-property).
This gem uses the id as the schema's URI and doesn't generate an uuid.

@angelim But it creates a uuid as id for schemas that come without an id though (just for completeness, your answer perfectly solves the uuid issue).
However, for displaying it to users, the id is also not a really convenient caption.
Processing error outputs for end users is not something that json-schema currently supports well (which we already identified, there are also other issues about that topic).
I think it would be worth to discuss how errors should be structured and handeld and based on that design or rather sketch of design someone (or maybe I myself find some time to do it) can prepare a PR.
My first idea would be to bring OO to errors and define error classes which for themselves semantically define what is wrong in which place. These classes then could define serveral "to_s"-variants.
Any more input?
Problem is that this will likely break backwards-compatibility if we won't add another flag (I really don't want to do that) or have some hack - so this would be something vor v3.
@iainbeeston Your thoughts on this?

@RST-J I agree with you completely. My first answer was an attempt to solve that particular problem without changing any code. I think this gem would benefit from re-evaluating the way errors messages are handled. Maybe something along the lines of ActiveModel Validators. That would also give it more flexibility to allow internationalization and customization.

Yes, there could be some to_i18n-method which then returns something like %w(json_schema draft_04 NAME_ID properties name required).
But I see one issue, its about the NAME_ID-part in the array. This should be something that identifies the schema which was violated.
Intuitivly I see two solutions. Either we take the value of the schema's title property. Or we take the schema's id property and underscore the path ('http://example.com/some/schema_path/to_file' would then be inserted as (%some schema_path to_file)). Or we combine both with title being prioritized. But as I actually have never seen the use of the title property before this issue I'd propose we could just use the second approach alone.

In https://github.com/ruby-json-schema/json-schema/blob/master/lib/json-schema/errors/validation_error.rb I see some very useful information coming with each error. To be as flexible as possible validation could return an array of instances of mentioned ValidationError. Additionally to unify the basic presentation of errors, I think ActiveModel::Errors is a good example of how it might work.
Should we move the discussion on better errors to a new issue?


Update python to 3.11.1

Python 3.11.1 has been released - update to newest version

This should be doable via dependabot now and not required.


Fix the hooks in level_api.hpp to avoid the code divergence

This got reverted cause it apparently broke some mods, namely randomizer was skipping all SPAWN_TYPE.SYSTEMIC callbacks, which did work in a simpler test script.


cannot import from nuxt/app (Package import specifier "#build/app.config.mjs" is not defined)

Environment
Operating System: MacOS Ventura
Node Version: v16.13.0.
Nuxt Version: 3.0.0-rc.9
Nitro Version: 0.5.0
Package Manager<EMAIL_ADDRESS>Builder: webpack ( I think)
User Config:
Runtime Modules:
"dependencies": {
"@formkit/i18n": "^1.0.0-beta.10",
"@pinia/nuxt": "^0.4.1",
"axios": "^0.27.2",
"pinia": "^2.0.21",
"pinia-plugin-persistedstate": "^2.1.1",
"postmark": "^3.0.1",
"swiper": "^8.3.1",
"vue3-marquee": "^3.0.7"
}
Build Modules:
"devDependencies": {
"@aceforth/nuxt-netlify": "^1.1.0",
"@formkit/nuxt": "^1.0.0-beta.11-0dd967c",
"@iconify-json/heroicons-solid": "^1.1.1",
"@nuxtjs/tailwindcss": "^5.3.2",
"@tailwindcss/typography": "^0.5.7",
"@vueuse/core": "^9.1.1",
"@vueuse/nuxt": "^9.1.1",
"netlify-cli": "^11.5.1",
"nuxt": "3.0.0-rc.9",
"unplugin-icons": "^0.14.5"
}
Reproduction
I upgrade with yarn upgrade and with yarn upgrade nuxt, then yarn upgrade --force, and then yarn upgrade --latest.
I upgraded to RC.9 and a few packages that didn't work I upgraded manually to the edge repository like formkit that needed yarn add @formkit/nuxt@next --dev .
I'will try to make a minimal reproduction, but as the project has many pages and components Im not sure if I have to recreate the whole project.
Describe the bug
When I do yarn build -> the site is completely broken it doesn't load any page.
When I do yarn dev -> the site works ok
When I do yarn check -> There is 1 error
error "<EMAIL_ADDRESS>doesn't satisfy found match of<EMAIL_ADDRESS>error Found 1 errors.

Additional context
No response
Logs
[nuxt] [request error] [unhandled] [500] Package import specifier "#build/app.config.mjs" is not defined in package /Users/david/WebstormProjects/mixverde/.output/server/node_modules/nuxt/package.json imported from /Users/david/WebstormProjects/mixverde/.output/server/node_modules/nuxt/dist/app/config.mjs
  at new NodeError (node:internal/errors:371:5)
  at throwImportNotDefined (node:internal/modules/esm/resolve:429:9)
  at packageImportsResolve (node:internal/modules/esm/resolve:778:3)
  at moduleResolve (node:internal/modules/esm/resolve:924:21)
  at defaultResolve (node:internal/modules/esm/resolve:1044:11)
  at ESMLoader.resolve (node:internal/modules/esm/loader:422:30)
  at ESMLoader.getModuleJob (node:internal/modules/esm/loader:222:40)
  at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:40)
  at link (node:internal/modules/esm/module_job:75:36)```

@ChurikiTenna Would you open a new issue with a reproduction?

I have a similar issue and have created an issue with reproduction over here: https://github.com/histoire-dev/histoire/issues/430

That isn't a Nuxt issue but to do with the way histoire is loading nuxt composables outside the Nuxt environment.

We also experienced this issue with histoire (v 0.12.4) and useCookie. Upgrading to v 0.15 fixed the issue, but caused some other problems, so we had to find another solution. Managed to solve it using a dynamic import from "#app":
  const app = await import('#app');
  const myCookie = app.useCookie('myCookie', { maxAge: MAX_COOKIE_AGE });

Posting this since it might help others.
Note that importing from ("#imports") lead to an error message.


[PostgreSQL] Query aborting waits end of execution

System information:

Windows 7 Pro x64
DBeaver <IP_ADDRESS>002011957, <IP_ADDRESS>002081854 (EA)
No additional extensions

Connection specification:

PostgreSQL 9.3
PostgreSQL default driver (9.4.1212.jre7)
No tunnels or proxies

Describe the problem you're observing:
Query aborting waits end of execution
Steps to reproduce, if exist:
Execute SELECT pg_sleep(20) and try to cancel it. It will be canceled after 20 sec, not immediately (after end of query execution)

thanks for the bug report

Fixed

verified

Dear all, please consider reopening this issue - I have encountered exactly the same behaviour for Oracle DB. Sometimes the only resolution is to kill DBeaver process. Tested on DBeaver 7.0.4, Linux Mint 19.3

Could you please give a query example?

Can reproduce in Oracle DB with
BEGIN
DBMS_LOCK.sleep(20);
END;

@kseniiaguzeeva In my case it was enough to leave program in an idle state for a few minutes (half hour maybe). Then an attempt of a statement execution runs infinitely.

it happens for me too with multiple Oracle database connections through VPN, if I leave dbeaver in an idle state for like 30-40 minutes then try to execute a query in any of the databases and it just runs infinitely and cancel button does nothing but generaring more and more tasks trying to abort the query.
DBeaver has to be killed and reopened in order to run queries normally


Update thquan's tasks

Update thquan's tasks
1. Description
Finished thquan's tasks
2. List of issues fixed:
None
Details:

Renamed templates folder from accounts to main
Updated group's member list in README
Added these frontend templates:

Sign up (register) / sign in (login)
Customer profile (detail) page
Create Report page

Added test routes, some of them can be reused later.

3. Other things to notice:
These are just templates, which require further work to operate correctly.
Tag the staff here: (name of staff).

OK


track alternative treatment in stratification

We weren't capturing the alternative treatment category.

Yes, that's exactly why. I need to re-run model 4 with this.


Improve about app feature

Is your feature request related to a problem? Please describe.
Currently about app feature looks displays very limited set of information.

Describe the solution you'd like
I'd like to have a full AboutAppPage with a lot of information about AnitaB, the awesome contributors and how one can start contributing :)
Describe alternatives you've considered
no alternatives

I would like to work on this issue.

Can i self assign this? would like to work on it.
cc @isabelcosta

go go @Techno-Disaster :)

@bartekpacia are the current licenses just place holders? also @isabelcosta can i remove the licences? we don't need them atm not before release ofc and they aren't even the proper licensees required ig

@Techno-Disaster  Will leave that decision up to y'all, I never heard of this feature. For me you can take it out, if this needs more thought

@Techno-Disaster Will leave that decision up to y'all, I never heard of this feature. For me you can take it out, if this needs more thought

cools, i just wanted to know if we need to have some licenses in the app officially, like from AnitaB or something.

I don't know as of now, but its nice to bring that up on Zulip

Current UI

The about page is almost done. Please help me with the content we have to add in it by editing this doc

Looks great @Techno-Disaster.
Regarding the licenses, they are real according to the docs. I'd leave them.

thanks Bartek.
also what data do i add to the page? current data is just some placeholder. I have asked several times to edit the doc, but no one's added anything. Should i keep the data like this for now? as its not really important. We can change it while releasing if required.
cc : @isabelcosta

@Techno-Disaster I meant that the "general scaffold" looks great. We can merge this as a base to serve for future improvements. Contributors will have an easier time adding new stuff there when the basics are already done :)

@Techno-Disaster I meant that the "general scaffold" looks great. We can merge this as a base to serve for future improvements. Contributors will have an easier time adding new stuff there when the basics are already done :)

cools. will send a PR asap


Module not found: Can't resolve 'styled-components'

I'm working with the Pro version of the template. I just downloaded it, initialized a repo and tried deploying it to Vercel, but the deployment fails with the following error:
<EMAIL_ADDRESS>Module not found: Can't resolve 'styled-components'

Here are the complete logs:
[16:24:14.268] Running build in Washington, D.C., USA (East) – iad1
[16:24:14.379] Cloning github.com/Ricardomol/my_private_repo (Branch: main, Commit: e8ea4f9)
[16:24:14.738] Previous build cache not available
[16:24:14.823] Cloning completed: 443.925ms
[16:24:15.106] Running "vercel build"
[16:24:15.551] Vercel CLI 37.1.2
[16:24:15.899] Installing dependencies...
[16:24:16.191] yarn install v1.22.19
[16:24:16.261] [1/4] Resolving packages...
[16:24:17.664] [2/4] Fetching packages...
[16:24:50.775] warning<EMAIL_ADDRESS>The engine "libvips" appears to be invalid.
[16:24:50.778] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[16:24:50.780] warning<EMAIL_ADDRESS>The engine "glibc" appears to be invalid.
[16:24:50.781] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[16:24:50.782] warning<EMAIL_ADDRESS>The engine "macos" appears to be invalid.
[16:24:50.782] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[16:24:50.782] warning<EMAIL_ADDRESS>The engine "glibc" appears to be invalid.
[16:24:50.782] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[16:24:50.782] warning<EMAIL_ADDRESS>The engine "musl" appears to be invalid.
[16:24:50.782] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[16:24:50.783] warning<EMAIL_ADDRESS>The engine "glibc" appears to be invalid.
[16:24:50.783] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[16:24:50.783] warning<EMAIL_ADDRESS>The engine "glibc" appears to be invalid.
[16:24:50.783] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[16:24:50.783] warning<EMAIL_ADDRESS>The engine "glibc" appears to be invalid.
[16:24:50.783] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[16:24:50.783] warning<EMAIL_ADDRESS>The engine "macos" appears to be invalid.
[16:24:50.783] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[16:24:50.783] warning<EMAIL_ADDRESS>The engine "glibc" appears to be invalid.
[16:24:50.784] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[16:24:50.784] warning<EMAIL_ADDRESS>The engine "glibc" appears to be invalid.
[16:24:50.784] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[16:24:50.784] warning<EMAIL_ADDRESS>The engine "musl" appears to be invalid.
[16:24:50.784] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[16:24:50.784] warning<EMAIL_ADDRESS>The engine "glibc" appears to be invalid.
[16:24:50.784] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[16:24:50.784] warning<EMAIL_ADDRESS>The engine "glibc" appears to be invalid.
[16:24:50.784] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[16:24:50.784] warning<EMAIL_ADDRESS>The engine "glibc" appears to be invalid.
[16:24:50.784] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[16:24:50.785] warning<EMAIL_ADDRESS>The engine "musl" appears to be invalid.
[16:24:50.785] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[16:24:50.785] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[16:24:50.785] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[16:24:50.785] warning<EMAIL_ADDRESS>The engine "musl" appears to be invalid.
[16:24:50.785] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[16:24:50.793] [3/4] Linking dependencies...
[16:24:50.797] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[16:24:50.797] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[16:24:50.797] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>[16:24:50.797] warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>|| ^2.0.0-beta || ^2.0".
[16:24:50.797] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^6.0".
[16:24:50.797] warning "react-hot-toast ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[16:24:50.798] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^6".
[16:24:50.799] warning "sanity ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^6".
[16:24:50.799] warning "sanity ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^6".
[16:24:50.826] warning Workspaces can only be enabled in private projects.
[16:24:50.834] warning Workspaces can only be enabled in private projects.
[16:24:50.840] warning Workspaces can only be enabled in private projects.
[16:24:50.841] warning Workspaces can only be enabled in private projects.
[16:24:50.841] warning Workspaces can only be enabled in private projects.
[16:24:50.841] warning Workspaces can only be enabled in private projects.
[16:25:01.305] [4/4] Building fresh packages...
[16:25:03.899] success Saved lockfile.
[16:25:03.904] Done in 47.72s.
[16:25:03.940] Detected Next.js version: 14.1.0
[16:25:03.941] Running "yarn run build"
[16:25:04.135] yarn run v1.22.19
[16:25:04.163] $ prisma generate && next build
[16:25:04.798] Prisma schema loaded from prisma/schema.prisma
[16:25:05.241]
[16:25:05.241] ✔ Generated Prisma Client (v5.9.1) to ./node_modules/@prisma/client in 61ms
[16:25:05.241]
[16:25:05.241] Start using Prisma Client in Node.js (See: https://pris.ly/d/client)
[16:25:05.241] ```
[16:25:05.241] import { PrismaClient } from '@prisma/client'
[16:25:05.241] const prisma = new PrismaClient()
[16:25:05.242] ```
[16:25:05.242] or start using Prisma Client at the edge (See: https://pris.ly/d/accelerate)
[16:25:05.242] ```
[16:25:05.242] import { PrismaClient } from '@prisma/client/edge'
[16:25:05.242] const prisma = new PrismaClient()
[16:25:05.242] ```
[16:25:05.242]
[16:25:05.242] See other ways of importing Prisma Client: http://pris.ly/d/importing-client
[16:25:05.242]
[16:25:05.242] ┌─────────────────────────────────────────────────────────────┐
[16:25:05.242] │  Deploying your app to serverless or edge functions?        │
[16:25:05.242] │  Try Prisma Accelerate for connection pooling and caching.  │
[16:25:05.242] │  https://pris.ly/cli/accelerate                             │
[16:25:05.242] └─────────────────────────────────────────────────────────────┘
[16:25:05.242]
[16:25:05.865] Attention: Next.js now collects completely anonymous telemetry regarding usage.
[16:25:05.866] This information is used to shape Next.js' roadmap and prioritize features.
[16:25:05.866] You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
[16:25:05.866] https://nextjs.org/telemetry
[16:25:05.866]
[16:25:05.963]    ▲ Next.js 14.1.0
[16:25:05.964]
[16:25:06.044]    Creating an optimized production build ...
[16:25:33.216] Failed to compile.
[16:25:33.216]
[16:25:33.216]<EMAIL_ADDRESS>[16:25:33.216] Module not found: Can't resolve 'styled-components'
[16:25:33.216]
[16:25:33.216] https://nextjs.org/docs/messages/module-not-found
[16:25:33.216]
[16:25:33.217] Import trace for requested module:
[16:25:33.217] ./node_modules/sanity/lib/index.esm.js
[16:25:33.217] ./sanity.config.ts
[16:25:33.217] ./src/app/(studio)/admin/[[...index]]/page.tsx
[16:25:33.217]
[16:25:33.217]<EMAIL_ADDRESS>[16:25:33.217] Module not found: Can't resolve 'styled-components'
[16:25:33.217]
[16:25:33.217] https://nextjs.org/docs/messages/module-not-found
[16:25:33.217]
[16:25:33.217] Import trace for requested module:
[16:25:33.217] ./node_modules/sanity/lib/desk.esm.js
[16:25:33.217] ./sanity.config.ts
[16:25:33.217] ./src/app/(studio)/admin/[[...index]]/page.tsx
[16:25:33.217]
[16:25:33.217] ./node_modules/sanity/lib/_chunks/TooltipDelayGroupProvider-e1ApGn-p.js
[16:25:33.217] Module not found: Can't resolve 'styled-components'
[16:25:33.217]
[16:25:33.217] https://nextjs.org/docs/messages/module-not-found
[16:25:33.217]
[16:25:33.217] Import trace for requested module:
[16:25:33.217] ./node_modules/sanity/lib/desk.esm.js
[16:25:33.217] ./sanity.config.ts
[16:25:33.217] ./src/app/(studio)/admin/[[...index]]/page.tsx
[16:25:33.217]
[16:25:33.217] ./node_modules/sanity/lib/_chunks/_internalBrowser-g8TrRAj2.js
[16:25:33.217] Module not found: Can't resolve 'styled-components'
[16:25:33.217]
[16:25:33.217] https://nextjs.org/docs/messages/module-not-found
[16:25:33.217]
[16:25:33.217] Import trace for requested module:
[16:25:33.217] ./node_modules/sanity/lib/index.esm.js
[16:25:33.217] ./sanity.config.ts
[16:25:33.217] ./src/app/(studio)/admin/[[...index]]/page.tsx
[16:25:33.218]
[16:25:33.218] ./node_modules/sanity/lib/_chunks/index-c8Mnhnf1.js
[16:25:33.218] Module not found: Can't resolve 'styled-components'
[16:25:33.218]
[16:25:33.218] https://nextjs.org/docs/messages/module-not-found
[16:25:33.218]
[16:25:33.218] Import trace for requested module:
[16:25:33.218] ./node_modules/sanity/lib/_chunks/structure-pNyMk_sD.js
[16:25:33.218] ./node_modules/sanity/lib/desk.esm.js
[16:25:33.218] ./sanity.config.ts
[16:25:33.218] ./src/app/(studio)/admin/[[...index]]/page.tsx
[16:25:33.218]
[16:25:33.229]
[16:25:33.229] > Build failed because of webpack errors
[16:25:33.248] error Command failed with exit code 1.
[16:25:33.248] info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
[16:25:33.270] Error: Command "yarn run build" exited with 1
[16:25:33.967]

Any help with this error please?

Download
https://www.mediafire.com/file/xs3e15yonljh4bk/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://bit.ly/3MjP129
password: changeme
In the installer menu, select "gcc."


sendResponse should has encoding parameters

I think it will be much more convenient if you add some lines to the AppBaseController->sendResponse method allowing seeing encoded json properly:
public function sendResponse($result, $message)
{
    $headers = ['Content-type'=> 'application/json; charset=utf-8'];

    return Response::json($this->makeResponse($result, $message), 200, $headers, JSON_UNESCAPED_UNICODE);
}

I’d like to be able to easily read the output instead of "...\u043a\u0440\u044b\u043b\u0430\u0442\u044b\u0445 \u0444\u0440\u0430\u0437..."

@zhekaus why you are getting output like,
"...\u043a\u0440\u044b\u043b\u0430\u0442\u044b\u0445 \u0444\u0440\u0430\u0437..." ?

Because it isn’t English but Cyrillic (Russian) in utf8 encoding.
If I add headers parameter and JSON_UNESCAPED_UNICODE option, I’ll see Russian text.

Actually, we are already using Response::json to send a response and it's not a general requirement. so can not add it as of now.
But it you want to do so, then you can do it by following steps:

Create your own AppBaseController
Publish Templates
Modify /resources/api-generator-templates/api/Controller.stub & /resources/api-generator-templates/scaffold/Controller.stub to use your AppBaseController instead of package one.


Move notCompatibleWithConfigurationCache config to KmpPlugin from KmpKtorfitPlugin

I think we can use withPlugin or something to do it.
https://github.com/DroidKaigi/conference-app-2024/pull/744/files

🙋♂

Thanks! Assigned 👍


Change all comment docs from /* -> /**

Parser will only look for comment blocks that begin with /**

This will be done in the rewrite.


New Deliverable UI should indicate required fields

There is no programmatic way to solve this issue, without directly modifying the HTML directly.

Placed on hold for now; this is substitutable with sufficient documentation (for now).


Update currency names for different languages

I still feel like Intl can save the day here

Fixed as part of #128


Bump Triton version to 21.11

Bump Triton image version to the latest.

CI MESSAGE: [3558414]: BUILD STARTED

CI MESSAGE: [3558414]: BUILD PASSED


$template in Vue 3

What problem does this feature solve?
I tried petite-vue and found it had this nice $template feature where I could specify the id of a template element and it would render that.
What does the proposed API look like?
Same $template in Vue 3 as exists already petite-vue.
https://github.com/vuejs/petite-vue#components-with-template

see https://vuejs.org/api/options-rendering.html#template

Oh, so this already works. This is really nice, I wasn't aware of that. It is a bit confusing though that it is called template in Vue but $template in vue-petite.


Fix bug with several endpoints not including app_id

The OneSignal API requires passing app_id in device update calls. Edit device calls without app_id are deprecated and will stop working in the future.
At your earliest convenience, please publish a patch release with this change.

I just pushed a commit with a few additional fixes. The app_id should be included with all of the device API POST requests.


try to install the library

Discussed in https://github.com/mkdocstrings/mkdocstrings/discussions/682

Originally posted by rraulf August  2, 2024
I try to install the library (as in #680 @matanox) and get an error:
ERROR: Could not find a version that satisfies the requirement mkdocstring (from versions: none)
ERROR: No matching distribution found for mkdocstring
What is the solution?
Thanks!

mkdocstring

You're missing the last "s": mkdocstrings :slightly_smiling_face:


Added Simple-FizzBuzz.py

Thank you for your PR, unfortunately this solution has already been submitted :/
Don't worry, your PR will still count!


Ursa Overpower Particle displacement

Reported by  MouJiaoZi:
https://cdn.discordapp.com/attachments/317271861966929921/318635014059327488/unknown.png

Fixed
09804ae3f1f6e65a0af4b22f70a1cc12041058fb


does this support UDP ?

does this support UDP ? or tcp only

https://github.com/armon/go-socks5/blob/master/request.go#L248
It seems the answer is not support UDP.


[BUG] Annotations not being applied to ingress

Describe the bug
We set a annotation on the ingress, but it never was applied to the ingress.
To Reproduce
Steps to reproduce the behavior:

Deploy chart using annotation on ingress.
View ingress that was created, no annotations were created as you added.

Expected behavior
Ingress gets deployed with applied annotations.
Environment

Longhorn version: 1.2.4
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): Rancher Catalog App
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: RKE2

Number of management node in the cluster: 3
Number of worker node in the cluster: 2

Additional context
ingress:
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt
  enabled: true
  host: longhorn.ourdomain.tld
  ingressClassName: nginx-lb
  secrets: null
  tls: true
  tlsSecret: longhorn.local-tls

Thanks @johnwc for reporting
I am able to reproduce this issue using Longhorn chart on the Rancher market place.
The problem doesn't happen when install using pure Helm.
Need to do more investigation

I am scratching my head not understanding why setting the helm value here  doesn’t take effect.
I am asking for help from Rancher team

Rancher UI ticket is filled at https://github.com/rancher/dashboard/issues/6038

For what it's worth I see the same issue with kustomize here, using:
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

namespace: longhorn-system

helmCharts:
- name: longhorn
  repo: https://charts.longhorn.io
  version: 1.6.1 # https://artifacthub.io/packages/helm/longhorn/longhorn
  releaseName: longhorn
  namespace: longhorn-system
  includeCRDs: true
  valuesInline:
    ingress:
      enabled: true
      annotations:
        cert-manager.io/cluster-issuer: XXXX
        external-dns.alpha.kubernetes.io/hostname: XXXX
      ingressClassName: nginx
      host: XXXXX
      tls: true
      tlsSecret: longhorn-ingress-tls

I wonder if rancher also uses kustomize underneath...


STM32f407

is it this library for stm32f407??

Hi @charisfs ,
It is a generic C library. One can compile it for an stm32f407.

Hi,
I am trying to add bno055 support to the linux kernelv3.10. Is there any patch available or available driver?
Thanks


Add Identity intializer

We are missing some initializers to fully support the export of models from Keras. One of them is the Identity initializer.
Add an initializer class, write documentation for it, write a test for it, try, if possible, create a small trainable network with it (in your own GitHub) and attach a link.
Also, support for export and import of initializer in JSON format should be added (see ModelLoader.kt  and ModelSaver.kt)
A detailed description of the initializer can be found here

Hi there 👋🏻
I'm new to the party and would love to help.
Created a first draft of this in #73
I will hopefully complete this in the next couple of days.


Block woff fonts and css

These resources do not affect the page rendering.

I think if you remove CSS, Google will consider it as cloaking. Not sure about fonts though.

If you pre-render pages, make sure that the content served to Googlebot matches the user's experience, both how it looks and how it interacts. Serving Googlebot different content than a normal user would see is considered cloaking, and would be against our Webmaster Guidelines.
Source

Css is not able to change markup. Links to css files are still on the same
place. With this PR css and woff fonts are not loaded during the js->html
render operation only
15 окт. 2015 г. 9:09 AM пользователь "Breno Calazans" <
<EMAIL_ADDRESS>написал:

I think if you remove CSS, Google will consider it as cloaking. Not sure
about fonts though.
If you pre-render pages, make sure that the content served to Googlebot
matches the user's experience, both how it looks and how it interacts.
Serving Googlebot different content than a normal user would see is
considered cloaking, and would be against our Webmaster Guidelines.
Source
http://googlewebmastercentral.blogspot.com.br/2015/10/deprecating-our-ajax-crawling-scheme.html
—
Reply to this email directly or view it on GitHub
https://github.com/prerender/prerender/pull/193#issuecomment-148269878.

Oh, I see, that's great, it should be more performant, right?

Yes. Less requests - faster render
15 окт. 2015 г. 9:19 AM пользователь "Breno Calazans" <
<EMAIL_ADDRESS>написал:

Oh, I see, that's great, it should be more performant, right?
—
Reply to this email directly or view it on GitHub
https://github.com/prerender/prerender/pull/193#issuecomment-148270751.

I'd still worry about not loading css. css can cause layout changes and javascript might be used to detect layout changes. Unless there are some benchmarks showing that css causes pages to load much slower, I think it's just a hypothetical gain.
We've had some issues with us not loading images in phantomjs due to some websites waiting for layout changes due to images or onload functions.

Ok. I've updated PR to block .woff fonts only.

Adding this small tweak reduced my load time by ~5s. Highly recommended for anyone reading this thread.

Awesome, sorry I haven't merged yet!


Communication & server statistics

Features

Added request handlers on the server for sparsely sending & receiving very basic data statistics
Added a logs feature on the server that keeps track of all successful requests sent by clients
Received TFJS model are periodically saved under a JSON format server-side
The server now uses HTTP's status codes to make it easier for the client to handle responses
The server's default port is now 8081 to avoid conflict when running the main app as well
Wrote a test.js file to quickly test the server's request handlers

Refactoring specific to FeAI

The helpers/communication/peer.js file is no longer needed, as only server communication occurs on FeAI
The helpers/communication/helper.js has fewer functions, a lot of them were DeAI-specific
The Communication Manager's code is now more explicit

Minor changes that may or may not be kept

The concat function can take multiple strings as argument, this is fixed
Renamed helpers subfolders (helpers/*) without the _script part
The task attribute taskId is used over trainingInformation.modelId when the code isn't model/training/IndexedDB-related for clarity (typically, task routes and task IDs in components)
Client messages should refer to taks by their their title to make it human readable

once merged, can you also propagate the relevant changes to DeAI? (to keep the code as similar as possible, while as small as possible also :))

I followed your code suggestions and made the naming of functions and data structures more explicit and wrote comprehensive documentation about them.
Considering the specific dict structure required for keeping track of the number of data samples held per client, I decided not to regroup it within a more general metadata dict. The distinction between weights and metadata (only #samples/client atm) should now be more clear nonetheless.


[Programmatic Access - MakeCode - Grow your business with Microsoft 365]: Luminosity ratio of "Read how small……chat for work" link with respect to its background colour is less than 4.5:1.

User Experience:
Low vision users will get impacted as they will not be able to see the controls present on the page properly & will face difficulties while reading the content on the page if the luminosity ratio of the any controls: link, text etc does not meet the minimum requirement of 4.5:1 ratio.
Note: User credentials should NOT be included in the bug.
Repro Steps:

Open #URL: https://www.microsoft.com/en-us/microsoft-365/business
and sign in with valid credentials
"Grow your business with Microsoft 365" page appears.
Navigate to "Read how small……chat for work" link.
Run the AI tool.
Observe and weather Luminosity ratio of "Read how small……chat for work" link with respect to its background colour is greater than 4.5:1 or not.

Actual Result:
Luminosity ratio of "Read how small……chat for work" link with respect to its background colour is 2.7:1 which is less than minimum contrast ratio: 4.5:1.
Expected Result:
Luminosity ratio of "Read how small……chat for work" link with respect to its background colour should be greater than or equal to 4.5:1.
Note: The same issue exists with the 'Help me choose' link present on the same page. https://webcompliance.trafficmanager.net/ScanResultsApi/GetAccessibilityScanConsolidatedReport?siteId=b64f9055-1724-4c63-6fcb-08dbb915c549
Issue:
Ensures the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds (color-contrast - https://accessibilityinsights.io/info-examples/web/color-contrast)
Target application:
Microsoft 365 for Business | Small Business | Microsoft 365 - https://www.microsoft.com/en-us/microsoft-365/business
Element path:
.text-primary-alt
Snippet:
<a
data-bi-cn="Read how to safeguard your business with Microsoft 365"
data-bi-ecn="Read how small and medium-sized businesses can benefit from
AI-powered chat for work" data-bi-ct="cta"
data-bi-pa="body" data-bi-bhvr="231"
data-bi-tags="{"BiLinkName":"Read how to
safeguard your business with Microsoft 365"}" class="cta
text-primary-alt font-weight-semibold "
data-target="https://go.microsoft.com/fwlink/?linkid=2240366&clcid=0x409&culture=en-us&country=us"
aria-label="Read how small and medium-sized businesses can benefit from
AI-powered chat for work" target="_blank"
data-regenerate-fwlink="true"
href="https://go.microsoft.com/fwlink/?linkid=2240366&clcid=0x409&culture=en-us&country=us">

How to fix:
Fix any of the following:
Element has insufficient color contrast of 2.67 (foreground color: #229af6, background color: #f2f2f2, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
Environment:
Microsoft Edge version <IP_ADDRESS>
====
This accessibility issue was found using Accessibility Insights for Web 2.41.0 (axe-core 4.7.2), a tool that helps find and fix accessibility issues. Get more information & download this tool at http://aka.ms/AccessibilityInsights.
MAS Reference:
MAS 1.4.3 – Contrast (Minimum)
ARIA Authoring Ref Link/Fluent Patterns Guidance /HITS Guidance: NA
UIA/DOM details available: Yes
Reference Links:

Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.
External Bug Process: If this bug belongs to the external team, mark it as resolved/done and assign it back to the tester with notes on where to file/route the bug. For more information, please use this link. “HCL Staff should not log any third-party external bugs. Should be routed to edad team”.
Please reach out to the C&AI Teams channel for any process-related queries.

Test Environment:
OS Version: Windows 11 23H2 (OS Build: 22631.2715)
Browser Version: Edge dev Version 118.0.2088.9 (Official build) dev (64-bit)
URL: https://www.microsoft.com/en-us/microsoft-365/business
Tool: AI for Web, Color Contrast Analyzer (CCA)
Test Metrix: Edge + Narrator
Attachment:

#A11yAuto,#A11yMAS,#A11ySev2,#Accessibility,#HCL,#K4W,#Win11-Edge (Chromium),#WCP,#HCL-MakeCodeArcade-Sep21

We don't own microsoft.com site. This has nothing to do with makecode.


Installation guide for Expo

Documentation mentions nothing about Expo. Was previously using pusher-js perfectly fine, but cannot anymore.

You need to follow the build instructions provided by Expo at https://docs.expo.dev/workflow/customizing/#adding-custom-native-code-with-development-builds. See https://github.com/pusher/pusher-websocket-react-native/issues/108 for more info on this.


Destructure RGB into json obj: Color: {r: 123, g:243, b: 24}

Or what have you

Is this fixed yet?!

How about now?

Here's a sampy request that works right now:
POST http://localhost:8080/api/composites
`    {
"name": "Blake",
"client": "Mac",
  "members": [
    {"id":0, "size": 25, "type":"tri","color": {"R": 216, "G": 103, "B":95 },"degrees":-44,"e":215.34359999999998,"f":465.0185},
    {"id":1,"size": 25,"type":"tri","color": {"R": 216, "G": 103, "B":95 },"degrees":-44,"e":232.34320000000002,"f":337.01840000000004},
    {"id":2,"size": 25,"type":"tri","color": {"R": 216, "G": 103, "B":95 },"degrees":-47,"e":637.6078,"f":211.94670000000002},
    {"id":3,"size": 25,"type":"tri","color": {"R": 216, "G": 103, "B":95 },"degrees":-51,"e":336.255,"f":275.4788},
    {"id":4,"size": 25,"type":"tri","color": {"R": 216, "G": 103, "B":95 },"degrees":-47,"e":681.5476,"f":388.5723},
    {"id":5,"size": 25,"type":"sq","color": {"R": 216, "G": 103, "B":95 },"degrees":0,"e":743,"f":27},
    {"id":6,"size": 25,"type":"pg","color": {"R": 216, "G": 103, "B":95 },"degrees":-27,"e":444.0483,"f":126.90119999999999}
  ]
}`


Lifetime requirements backwards incompatibility

extern crate tar;

use std::fs;
use tar::Archive;

fn main() {
    let tnames = vec!["a", "b", "c"];

    let ars: Vec<Archive<fs::File>> = tnames.iter().map(|tname| {
        let file = fs::File::open(tname).unwrap();
        Archive::new(file)
    }).collect();
    let mut arfiless: Vec<Vec<tar::File<fs::File>>> = ars.iter().zip(tnames).map(|(ar, tname)| {
        let arfiles: Vec<_> = ar.files().unwrap().map(|res| res.unwrap()).collect();
        arfiles
    }).collect();

    let mut arheadmaps: Vec<_> =
        arfiless.iter_mut().map(|arfiles| xx(arfiles)).collect();
}

fn xx<'a, 'b: 'a>(arfiles: &'a mut Vec<tar::File<'a, fs::File>>) {

}

This breaks after https://github.com/alexcrichton/tar-rs/commit/71b60399f0ce5d20765e81441b1f3d79255e1a48
Easily fixable by adding changing 'a, fs::File to 'b, fs::File on xx, but it worked before.

$ cargo build
    Updating registry `https://github.com/rust-lang/crates.io-index`
   Compiling tar v0.3.2 (file:///space/ahobsons/rust/tar-rs)
   Compiling dayer v0.1.1 (file:///space/ahobsons/rust/dayer)
src/main.rs:19:9: 19:17 error: `arfiless` does not live long enough
src/main.rs:19         arfiless.iter_mut().map(|arfiles| xx(arfiles)).collect();
                       ^~~~~~~~
src/main.rs:12:18: 20:2 note: reference must be valid for the block suffix following statement 1 at 12:17...
src/main.rs:12     }).collect();
src/main.rs:13     let mut arfiless: Vec<Vec<tar::File<fs::File>>> = ars.iter().zip(tnames).map(|(ar, tname)| {
src/main.rs:14         let arfiles: Vec<_> = ar.files().unwrap().map(|res| res.unwrap()).collect();
src/main.rs:15         arfiles
src/main.rs:16     }).collect();
src/main.rs:17
               ...
src/main.rs:16:18: 20:2 note: ...but borrowed value is only valid for the block suffix following statement 2 at 16:17
src/main.rs:16     }).collect();
src/main.rs:17
src/main.rs:18     let mut arheadmaps: Vec<_> =
src/main.rs:19         arfiless.iter_mut().map(|arfiles| xx(arfiles)).collect();
src/main.rs:20 }
error: aborting due to previous error
Could not compile `dayer`.

To learn more, run the command again with --verbose.

Simpler:
extern crate tar;

use std::fs;
use tar::Archive;

fn main() {
    let file = fs::File::open("a").unwrap();
    let ar = Archive::new(file);
    let arfiles: Vec<tar::File<fs::File>> = ar.files().unwrap().map(|res| res.unwrap()).collect();
    xx(&arfiles);
}

fn xx<'a>(arfiles: &'a Vec<tar::File<'a, fs::File>>) {}

In fact, the error "arfiles does not live long enough" is really not the error I would expect, given that the following definition of xx allows it to compile:
fn xx<'a, 'b: 'a>(arfiles: &'a Vec<tar::File<'b, fs::File>>) {}

Typically when rust is unable to satisfy function lifetime parameters it says (IIRC) something like "unable to satisfy lifetime bounds of X" and you now have a clue that you've done something wrong with function lifetime parameters.

Hm OK, I tracked this down and it seems to be because the the "seek" operation in an Entry was changed from a fn(Foo) to a Box<Fn(Foo)> to handle some extra captured data, and that addition of a destructor ended up triggering what I can only presume are the dropck rules.
I'll see if I can't find a way to make that just a plain fn without unsafe code...

Hm ok, so after thinking a little more about this I think there's not much that can be done here. This is an unfortunate interaction with dropck but overall I think it's not too bad of a breaking change or too bad to fix in practice. For now I'm gonna close this but let me know if there's any difficulty in upgrading!
This is certainly surprising to me in terms of backwards compatibility, and I'll try to keep an eye out for things like this in the future!

Thanks for the clear explanation! It does makes sense to me that adding destructors could influence lifetimes (because, if I'm understanding correctly, you now have an extra lifetime that needs to be tracked because a fn without a box does not have any lifetime).
However, I'm still a little perplexed around the exact cause of the error. Reading https://github.com/rust-lang/rfcs/blob/master/text/0192-bounds-on-object-and-generic-types.md#lifetime-bounds-on-parameters (specifically "for any lifetime 'a, 'a outlives 'a"), it seems to me that the lifetimes accepted by:
fn xx<'a, 'b: 'a>(x: &'a Vec<T1<'b, T2>>) {}

are a superset of those accepted by
fn xx<'a>(x: &'a Vec<T1<'a, T2>>) {}

because 'a is a valid lifetime for 'b in 'b: 'a?

Sorry, I shouldn't write comments when tired! I was looking at it from the wrong direction!
The problem is to do with my current lifetime rules being too strict and having to relax them, not the other way around which is what I mistakenly wrote the comment above based on.
Is there any reading you can recommend on the dropck rules etc? Or is it just the normal case of hunting in the rfcs repo?

Ah yeah unfortunately I don't know of any better documents other than what's in the rfcs repo :(


[Summary] Flowtype / VSCode pain points and potential improvements

Flowtype VSCode pain points and potential improvements
A lot of engineers have started using VSCode for day to day development. A good portion of these engineers are coming from a background of TypeScript which has very good built in support within VSCode. This is the case for a few reasons:

VSCode comes with a TypeScript extension built into and bundled with the editor. Users do not have to configure or update this plugin. It “just works”.
TypeScript’s VSCode editor support is implemented with tsserver and the TypeScript built in extension instead of using the open Language Server Protocol developed by Microsoft. This means some features TypeScript supports today just aren’t possible without also updating the Language Server Protocol.

https://github.com/microsoft/vscode/issues/70239
https://github.com/microsoft/vscode-languageserver-node/issues/471

TypeScript’s API is more stable than Flow’s. Flow is still a minor version (0.x) and the project has historically not been shy about that fact.
Facebook (as far as I know) mostly only supports the Nuclide IDE internally through the Language Server Protocol. This may mean in some cases Flow + VSCode issues might not always be high priority or visible to the Flow team, especially if they're unique LSP + VSCode behavior.
It’s not always easy or straightforward to configure Flow in VSCode. For example, it may be that the local node_modules Flow server (flow-bin) isn’t found and the VSCode plugin falls back to using its own version of Flow. We've had one issue in the past for example were a project was not configured to point to the local flow-bin server. When the Flow-for-vscode plugin auto updated, the user started to get errors in VSCode they weren't seeing from the command line. This is easily fixed when you know the cause but otherwise, you loose confidence in the tooling.

Collecting ideas for IDE improvements (will continue to update this)

[ ] Auto import of dependencies. TypeScript currently supports “auto importing” dependencies but Flow does not.

https://github.com/facebook/flow/issues/7662

[ ] Work upstream with LSP team to add needed features to the spec to match TypeScripts support.

https://github.com/microsoft/vscode-languageserver-node/issues/471

- [] Add “codelens” support https://github.com/facebook/flow/issues/7890

Decided against this for now. The output ended up being too verbose to be helpful. Could consider adding this behind a config flag?

[ ] Support for WorkspaceSymbol in LSP https://github.com/facebook/flow/issues/7743

[ ] Support documentation tooltip in LSP https://github.com/facebook/flow/issues/7725

[ ] Explore ways to configure and Bundle vscode with Flow

[ ] Autocompletion/suggestions on imported or inherited types #7722

[ ] Hints / suggestions / autocomplete are missing #7723

A couple more improvements

Better syntax highlighting when using generics (currently using the Babel JavaScript "language")
Cmd + clicking on the import path, should jump to the file. Currently only cmd + click on the imported names works

Awesome, thanks for starting this list! This is an area that we're going to be investing in over the next couple of months, so the list of issues (please tag them with LSP!) and their relative priority will help me out a lot.
We don't use flow-for-vscode internally but vscode is still very important to us. You are correct that we've made Nuclide communicate with Flow solely over the LSP. All of our other editor integration is deprecated in favor of the LSP, and I hope we remove the legacy stuff ASAP so that we can focus (what were you saying about an unstable api? 😂).
Accurately implementing the LSP is our priority. In my experience so far, there aren't many LSP + vscode bugs as it's the reference LSP implementation. So it's a matter of us returning poor LSP responses, which so far have impacted Nuclide and VSCode equally -- e.g. returning bad ranges made them both filter out autocomplete results.

@mroch maybe also check autocomplete and type-at-pos labels

@mroch do you have any news about this?


how to parse / (no spaces)

Say I have a script like:

#!/usr/bin/python
"""
Usage:
    myscript <arg2>/<arg2>
"""

from docopt import docopt
args = docopt(__doc__, version='1.0.0')
print args

Running it gives an argument named "/" which isn't at all what I intended.  I've included the output below, but github insists on wiping out the key:

$ ./docopt2 arg1/arg2
{ '<arg2>/<arg2>': 'arg1/arg2'}

I'd like it to parse  and  separately.  Unfortunately, TokenStream's definition just does a simple split, giving the current behaviour.
I expect that this is not intended to work, but is there a reason why, apart from "it was easier to write"?
Is there an easy way to make this work?

afaict, this can be closed


feat(mdx): gemoji

Fix RM-9013

🧰 Changes
Adds MDX support for gemoji!
🧬 QA & Testing

Broken on production.
Working in this PR app.

emojis look great! although owlmojis don't render for me

I think this is okay. Jenn is still working on images, so the owlmoji's won't work till then.

This PR was released!
🚀 Changes included in v6.75.0-beta.28


[Bug][Jira] An error occurred during extracting changelog

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
When I try to run a blueprint, an error occurred during extracting the changelogs

What do you expect to happen
It should go smoothly and no errors like this.
The bug was caused by the issue commits collector being disabled by default.
How to reproduce

create a Jira blueprint
run the blueprint

Anything else
No response
Version
main
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@mindlesscloud Please check if it exists in v0.17, and cherrypick the PR if so.


ignore loadbalancer listener to prevent errors on ressource collector

Description of changes:
I had problems with loadbalancer listeners, as they produce errors in the ressource collector step. Hence I ignored them.
Error was:
Got the pagination token
Got the pagination token
Done fetching autoscaling groups
['abc']
['abc', 'xyz']
Done fetching cloudwatch namespaces
This resource is EC2 arn:aws:ec2:REGION:ACCOUNT_ID:instance/i-030c9b32154097763
Done fetching volumes
Instance i-030c9b32154097763 does not have CWAgent
This resource is EC2 arn:aws:ec2:REGION:ACCOUNT_ID:instance/i-013c766a7bdfdaf5d
Done fetching volumes
Instance i-013c766a7bdfdaf5d does not have CWAgent
This resource is ELBv2 arn:aws:elasticloadbalancing:REGION:ACCOUNT_ID:listener/app/lb-name/c0b0259937634568/aba573d50763852a
Traceback (most recent call last):
  File "/path/to/repo/tag-based-cloudwatch-dashboard/data/resource_collector.py", line 701, in <module>
    handler()
  File "/path/to/repo/tag-based-cloudwatch-dashboard/data/resource_collector.py", line 692, in handler
    decorated_resources.append(router(resource, config))
                               ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/path/to/repo/tag-based-cloudwatch-dashboard/data/resource_collector.py", line 159, in router
    resource = elb2_decorator(resource, config)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/path/to/repo/tag-based-cloudwatch-dashboard/data/resource_collector.py", line 484, in elb2_decorator
    response = elb.describe_load_balancers(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/botocore/client.py", line 553, in _api_call
    return self._make_api_call(operation_name, kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/botocore/client.py", line 1009, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (ValidationError) when calling the DescribeLoadBalancers operation: 'arn:aws:elasticloadbalancing:REGION:ACCOUNT_ID:listener/app/lb-name/c0b0259937634568/aba573d50763852a' is not a valid load balancer ARN

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closing this one because of different fix I applied. Thanks a bunch for bringing this to my attention.


Please ignore this. This is a bug bounty test... rphydw

Please ignore this. This is a bug bounty test... rphydw

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Implement cross-platform build scripts

With the addition of native addons to Etcher, its no longer possible to
package the application for all operating system in a single host.
Given we need to build on Windows, we're creating cross-platform bash
and batch scripts and deprecating the original Makefile.
Signed-off-by: Juan Cruz Viotti<EMAIL_ADDRESS>

We're lacking archiving back to .asar in Windows, but omitting the .dlls in the way.


[MOS-004] Entry Overview

As a
user
I want to
see a list of my entries on the app homescreen
so that
I can sroll through them and see them all.

[ ] Create the tables that will contain the rows
[ ] Add the menu bar 'My open secrete'
[ ] Create the right menu with the 'Tag', 'Filter' and 'New Entry' buttons
[ ] Scroll bar to see the list of journals

Estimated: 3 story points


Puppeteer occasionally doesn't start on windows

This seems to be a buffering issue: the stderr of the child_process is empty on windows unless the chromium is closed.

Thanks @aslushnikov and gang for rolling out Puppeteer! The issues looks like an early indication of synergies that can only happen when browser automation tool and browser dev team is one team :smile:


Welling/soft assay types start

Updates to rules classifier

@jpuerto-psc @gesinaphillips to be clear, when I merge this PR and redeploy the updated dev-integrate branch on DEV, I'll be building the ingest-api by pulling the latest commit from IVT phillips/multi-assay branch?

@yuanzhou - that is right. Please wait for @jswelling to confirm that this is ready to merge, seems like there are a few merge conflicts that need to be resolved.

@yuanzhou - should be good to merge here!

@gesinaphillips I'm afraid that you'll have to back out the commit https://github.com/hubmapconsortium/ingest-api/pull/435/commits/82df881404e55e3367ad841dc796d997d34f5e9e, our workflow is NEVER merge dev-integrate into your feature branch.

@gesinaphillips I'm afraid that you'll have to back out the commit 82df881, our workflow is NEVER merge dev-integrate into your feature branch.

I'm so sorry to do this again, I was being overly hasty. Reverting.

@gesinaphillips might be a good idea to delete that commit from the history and force push to your branch.

Ah. I thought that keeping the history might be preferred, so I went with the new commit @yuanzhou

@gesinaphillips for some reason the revert commit doesn't look good to me.
The old commit: https://github.com/hubmapconsortium/ingest-api/commit/82df881404e55e3367ad841dc796d997d34f5e9e had introduced several new changes being tested on DEV from other developers.
The revert commit https://github.com/hubmapconsortium/ingest-api/commit/8de3415f0ea0aa6108d5f51c25c4a809e3fbd53d only reverted a small part of the changes introduced by the above commit.
I'd suggest to delete the last two commits, one at a time with
# git reset --hard HEAD~1

Then verify again to make sure you are at https://github.com/hubmapconsortium/ingest-api/pull/435/commits/e4cdb9819dac0268d4f0265ef256a3330e2164e1.
Finally push to the feature branch
# git push origin HEAD --force

@yuanzhou Okay that should do it! Thank you very much for the instructions.


scale percentiles by time-unit too

Currently the min/max/mean/etc values sent to graphite are scaled
by the configured duration unit, so that one can choose what unit
the numbers sent to graphite represent, but the percentile values
are sent unscaled. This change applies the same scaling to them.

@dt Could you drop in some details about the why and how?

Added a commit desc, just saying that this applies the same scaling (division by du) to percentiles that is applied to the other timing numbers.

Thanks! :bowtie:


fix: fix noInteraction option in network chart QB-885

@PurwaShrivastava I have edited the commit message with the correct bug number


Error in console. spigot 1.15.2

https://pastebin.com/gbp5pgix

Make sure ProtocolSupport is up-to-date.


show which environment the email belongs to

It might be easier for staff to know which environment the mail is from ;ie DEV/TEST/DEMO/PROD etc..
Solutions
Can put the url so that its visible
color code the mail (leave nothing for prod)

Hey team! Please add your planning poker estimate with Zenhub @djnunez-aot @jadmsaadaot @saravanpa-aot @VineetBala-AOT

Verified all emails having text at bottom showing which environment the email is from.


Widget rebuild (useProvider) not triggered in profile or release build, but works in debug mode

Describe the bug
Bit of weird issue. If you take the example Todo app, do a debug build then no issue. But on profile/release the
final todo = useProvider(_currentTodo);

does not trigger a rebuild in the TodoItem widget when you check/uncheck an item (checkbox).
To Reproduce
Use the example Todo app and build to profile or release. Error occurred on an Android build (not tested on iOS). No changes made to the example. In the picture below, you can see one item is left, however, none of the items are checked. If you navigate to a different filter and back a build is forced and the items will then be checked.

I attempted to isolate the issue by creating a stripped down version of the example, but I couldn't reproduce the issue. Guessing it's something with ScopedProvider or overrideWithValue.
Expected behavior
Expect the TodoItem widget to rebuild when filteredTodos updates, forcing the checkbox to update its status.

What version are you using? This was fixed in 0.7.1

Sorry was on 0.7.0 😅. I should learn to read closed issues. Thanks for the quick response.


Question: helmfile lint - produces error on deprecated apiVersions

Question First off great product.
I'm using the helmfile lint command to do linting on the helm charts I use in my setup.
From what I can read the helmfile lint uses helm lint as sub-command to do the linting?
In helm the linting does not produce an error on deprecated fields like apiVersion, which mean my jenkins build, where I perform my linting, does not break. But when using helmfile lint command, the build break because helmfile produces an error instead of a warning. Have I overlooked a setting to make deprecation a warning instead of an error?
I hope my question make sense?
Thanks.

never mind.. found a way to skip checks for these here charts.


Upgrade jest to latest version

Fixes #2698
Add description here.

@vimal1083 Nice work, glad to have you back fixing these node related issues we are having!
Since you last worked on Hypha we have updated to using node v16.x that use lockfileVersion 2 for package-lock.json. I have fixed this PR but please upgrade your local hypha dev env.

Thanks @frjo .
Yes missed checking lockfileVersion. I will update my local env for hypha


Typescript support (WIP)

Add Typescript to main codebase
esbuild to build /dist/index.js (reduces backed size to 50Kb)
npm publish only publishes /dist/index.js
files renamed from *.js to *.ts
eslint has TS support added
This is based on https://github.com/markusahlstrand/cloudworker-proxy/pull/130 so we have an integration test checking the final artefact still works (it does). That PR should be merged first
outstanding issue: of course our JS is not good TS so linting fails. There needs to be a ton of work to fix it.

current failures are linting because of the new TS code. The actual unit and integration tests pass

This looks good but has a merge conflict on the S3 file. Any chance you could have a look @tomlarkworthy ?

Yeah will fix later

ok I think this merges now


url.Parse not working correctly for a non absolute URL with port.

What version of Go are you using (go version)?
go version go1.9.1 linux/amd64

Does this issue reproduce with the latest release?
Yes: https://play.golang.org/p/yoLxXnHE1J
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/rz/golang"
GORACE=""
GOROOT="/home/rz/.gimme/versions/go1.9.1.linux.amd64"
GOTOOLDIR="/home/rz/.gimme/versions/go1.9.1.linux.amd64/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build155424131=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"

What did you do?
url.Parse not working for relative url with port.
When parsing www.example.com:443, IsAbs returns true, and port is empty.
https://play.golang.org/p/yoLxXnHE1J
What did you expect to see?
IsAbs returns false.
What did you see instead?
IsAbs returns true.

Dup of #21415
That is not a valid URL. An absolute URL starts with a scheme (http://, etc) and a relative URL must never contain a colon in its first path element, per the specs.

@bradfitz Shouldn't Parse return an error in that case?

Just keep in mind that you're parsing either a full URL or just a path.


Guaranteed ARC Opts: Access instructions do not reduce refcounts.

Fixes rdar://problem/32560531 MatMul regression with dynamic
exclusivity checks due to retain/release.

@swift-ci smoke test and merge.


htk to numpy

Hi,
how do i convert an ark file or htk file to numpy array?
import kaldi
import numpy

f1="This_is_htk_file.lps"
f2="This_is_ark_file.ark"

The support for HTK feature files is fairly basic. You need to do things manually. Note that the code below is not tested, so it may or may not work out of the box.
from kaldi.matrix import Matrix
from kaldi.matrix.htk import HtkHeader, read_htk
from kaldi.util.io import xopen

with xopen("path/to/feats.htk") as f:
    feats, header = Matrix(), HtkHeader()
    read_htk(f.stream(), feats, header)
    feats_arr = feats.numpy()
    ...

The easiest way of reading Kaldi features is using a table reader.
from kaldi.util.table import SequentialMatrixReader

for key, feats in SequentialMatrixReader("ark:path/to/feats.ark"):
    feats_arr = feats.numpy()
    ...


Is there a plan for developing  hackmd api-client in different language?

Hello @Yukaii, thank you for maintaining this repository🙇🏻♂  This is helpful for me to make some automation stuff on HackMD.
I'm curious if there is a plan for developing api-client in different language besides nodejs? Since I will make some python scripts for automatically syncing all notes from HackMD to GitHub for PyConTW, we are prepared to build a similar api-client in Python so that we could make more unified codebase. Is there already an ongoing project? Or maybe I can make some contributions here.
Look forward to your reply, thank you!

I just found out that HackMD released their API doc with Postman. I'd like to know if the author can also expose the underlying OpenAPI spec (in json or yaml) as well so that we can convert it into an API library in any language using OpenAPI codegen tools (e.g. this one for python) on our own?


Gitea 1.6.2 failed to start after restart with error Invalid object name 'SYS.INDEXES'

Gitea version (or commit ref):gitea-1.6.2-windows-4.0-amd64
Git version: 2.21.0.windows.1
Operating system: Windows Server 2012 R2
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[x] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:
2019/02/27 19:59:03 [I] Log Mode: File(Info)
2019/02/27 19:59:03 [I] XORM Log Mode: File(Info)
2019/02/27 19:59:03 [I] Cache Service Enabled
2019/02/27 19:59:03 [I] Session Service Enabled
2019/02/27 19:59:03 [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: sync database struct error: mssql: Invalid object name 'SYS.INDEXES'.

Description
This happened after i restarted my server. If there is any other way that i can provide more info please let me know.
Screenshots

Hi @Noderino, first thing is you'll likely want to upgrade to the latest version as we've fixed some major security vulnerabilities, also the DB library has been updated which might solve the problem.
Are you able to connect directly to MSSQL to run queries manually against it?

Yes i can connect to MSSQL without a problem. I also tried to replace gitea.exe with newer versions and latest but i am still getting same error.

This is the log before first "Invalid object name" error.
2019/01/29 18:45:40 [...routers/repo/http.go:137 HTTP()] [E] invalid credentials
2019/01/29 18:45:40 [...routers/repo/http.go:137 HTTP()] [E] invalid credentials
2019/01/29 18:46:15 [...routers/repo/http.go:137 HTTP()] [E] invalid credentials
2019/01/29 18:46:15 [...routers/repo/http.go:137 HTTP()] [E] invalid credentials
2019/02/27 13:10:07 [I] Log Mode: File(Info)
2019/02/27 13:10:07 [I] XORM Log Mode: File(Info)
2019/02/27 13:10:07 [I] Cache Service Enabled
2019/02/27 13:10:07 [I] Session Service Enabled
2019/02/27 13:10:08 [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: Unable to open tcp connection with host '<IP_ADDRESS>:1433': dial tcp <IP_ADDRESS>:1433: connectex: No connection could be made because the target machine actively refused it.
2019/02/27 13:11:07 [I] Log Mode: File(Info)
2019/02/27 13:11:07 [I] XORM Log Mode: File(Info)
2019/02/27 13:11:07 [I] Cache Service Enabled
2019/02/27 13:11:07 [I] Session Service Enabled
2019/02/27 13:11:22 [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: sync database struct error: mssql: Invalid object name 'SYS.INDEXES'.

Which version of your database?

SQL Server 2014

@lunny Do you mean version number in dbo.version table? It is 74

@Noderino No. I means your SQL Server.


modify scope operand

Merged! Thanks for the PR

Another update https://github.com/sysdiglabs/sysdig-sdk-python/pull/158. My bad pushed pr without any local testing. Hopefully this will be final 😊


Fix test

Description
Proposition to fix test_max_time_lock.py.

test_deliberate_failure_and_protection.py works fine without any modification
test_max_lock_time.py initially failed every time so some fix are proposed:

for test_max_lock_time, the proposed solution works 8/10. The timing is very narrow as:

It take about 0.01s between the process start call and the execution of the 1st line in the process.
The wait can be between +/- 40% of its attributed value.
The lock removal as well as the lock creation can take between 0.1 to 0.2s.

for test_max_lock_time_crashed, the proposed solution taking into consideration the timing mentioned above into consideration, works 100% of the time.

Cheers,
Thomas
Closes # .

To DO:

A test should be add to accertain /eos/ or /afs/ can be accessed before trying the following test: test_afs.py , test_eos.py, test_fs.py, test_fs_api.py.
There is a recursion error from xaux/fs/fs.py and xaux/fs/eos.py when trying to test from eos/:

_test_helpers.py:50: in init_file
    with ProtectFile(fname, "w", wait=1) as pf:
../xaux/protectfile.py:194: in __init__
    arg['file'] = FsPath(arg['file']).resolve()
../xaux/fs/fs.py:42: in __new__
    return EosPath.__new__(EosPath, *args, _eos_checked=True)
../xaux/fs/eos.py:113: in __new__
    self._set_eos_path()
../xaux/fs/eos.py:123: in _set_eos_path
    parts = _non_strict_resolve(self.expanduser().parent, _as_posix=True).split('/')
/afs/cern.ch/work/t/thpugnat/private/python/miniforge/envs/mf-xtest/lib/python3.10/pathlib.py:873: in parent
    return self._from_parsed_parts(drv, root, parts[:-1])
../xaux/fs/fs.py:101: in _from_parsed_parts
    return FsPath(super(Path, cls)._from_parsed_parts(*args, **kwargs))
../xaux/fs/fs.py:42: in __new__
    return EosPath.__new__(EosPath, *args, _eos_checked=True)
../xaux/fs/eos.py:113: in __new__
    self._set_eos_path()
../xaux/fs/eos.py:123: in _set_eos_path
    parts = _non_strict_resolve(self.expanduser().parent, _as_posix=True).split('/')
/afs/cern.ch/work/t/thpugnat/private/python/miniforge/envs/mf-xtest/lib/python3.10/pathlib.py:873: in parent
    return self._from_parsed_parts(drv, root, parts[:-1])
../xaux/fs/fs.py:101: in _from_parsed_parts
    return FsPath(super(Path, cls)._from_parsed_parts(*args, **kwargs))
E   RecursionError: maximum recursion depth exceeded while calling a Python object
!!! Recursion detected (same locals & position)


Configuring single interpreter for jupyter server

Part of #8623
Created a classes to:

Select an interpreter for jupyter
Ensure jupyter and notebook is installed in jupyter
Allow user to select another interpreter
Added command to select interpreter
Keep track of whether an interpreter was ever set (part of spec for backwards compat)
Send telemetry (for command and selection result)

Note: Will create a separate PR to wire up these new classes and refactor how we startup jupyter
(wanted to minimize changes and make reviews easier, hence the splitting of PR)

Codecov Report

Merging #9565 into master will increase coverage by 0.13%.
The diff coverage is 93.93%.

@@            Coverage Diff             @@
##           master    #9565      +/-   ##
==========================================
+ Coverage   60.83%   60.97%   +0.13%
==========================================
  Files         530      535       +5
  Lines       28645    28786     +141
  Branches     4344     4355      +11
==========================================
+ Hits        17425    17551     +126
- Misses      10261    10273      +12
- Partials      959      962       +3

Impacted Files
Coverage Δ

src/client/telemetry/index.ts
86.48% <ø> (ø)
:arrow_up:

src/client/datascience/constants.ts
99.68% <100%> (ø)
:arrow_up:

src/client/datascience/jupyter/notebookStarter.ts
71.54% <100%> (ø)
:arrow_up:

src/client/common/utils/localize.ts
94.96% <100%> (+0.01%)
:arrow_up:

src/client/common/installer/productNames.ts
100% <100%> (ø)
:arrow_up:

src/client/datascience/jupyter/jupyterExecution.ts
48.31% <100%> (ø)
:arrow_up:

...lient/datascience/jupyter/kernels/kernelService.ts
54.92% <100%> (ø)
:arrow_up:

...cience/jupyter/interpreter/jupyterCommandFinder.ts
71.32% <100%> (ø)

.../jupyter/interpreter/jupyterInterpreterSelected.ts
100% <100%> (ø)

src/client/common/installer/productInstaller.ts
96.27% <100%> (+0.01%)
:arrow_up:

... and 16 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0b7e8de...28ba68e. Read the comment docs.


Possible missing JSDoc comments for class sap.m.DatePicker

There are couple for methods without JSDoc comments in the source code of sap.m.DatePicker, specifically:
,
,
,
,
.
As result, no type definitions are generated for those methods as well.
I don't know if this is intentional/those methods should be exposed in the type definitions, am I missing something?

Hello @dfenerski ,
The onBeforeRendering, invalidate and exit are inherited method and it shouldn't be documented in the context of the DatePicker. I created internal incident<PHONE_NUMBER> for getIconSrc and toggleOpen.
Regards,
Plamen Ivanov

Hello @dfenerski ,
The getIconSrc and toggleOpen are helper methods inherited from InputBase, to align to other inputs. They have no additional API value, that's why they are not documented in the context of the DatePicker.
Best Regards,
Tsanislav

Initially I came across this while migrating an app to TypeScript. There seem to be no type definitions generated for those methods, or am I missing something?

Let me jump in here. Thats correct type definitions are only generated for public methods. And as far as I know, these methods are not public, so it works as expected.


Bump to latest soc-testsocket-sifive.

This points to https://github.com/sifive/soc-testsocket-sifive/pull/8, which just helps us get this repo pointed to a much more recent version of the dependencies.
Once that PR merges in, I'll update this one to point to the merged commit rather than a branch.

I had to bump to wake 0.17.1, which caused me to have to make a new release of environment-blockci-sifive.git. This all seems to be working now, so I'm going to merge the soc-testsocket-sifive.git change, and repoint this to the merged commit.
Also, I've added a CHANGELOG.md, much like I did in https://github.com/sifive/environment-blockci-sifive/pull/6.

cc @sistillson
So, it looks like despite the fact that Travis CI is returning a green checkmark, if you actually look at the console output, it's failing to compile the software test program, and therefore failing to run the RTL simulation. Two questions:

Is it failing to compile because of https://github.com/sifive/api-generator-sifive/pull/16? Here is the error message:
block-pio-sifive/drivers/metal/sifive_pio.c: In function 'pio_odata_write':
block-pio-sifive/drivers/metal/sifive_pio.c:15:48: error: 'METAL_PIO_ODATA' undeclared (first use in this function); did you mean 'METAL_PIO_REGBW'?
     unsigned int byte_to_write = (bit >> 3) + (METAL_PIO_ODATA);
                                                ^~~~~~~~~~~~~~~
                                                METAL_PIO_REGBW

Can we fix the wake rules such that software compilation failures cause the wake process to exit with non-zero status?

Force-pushed a few more changes to this branch:

One to bump to the latest api-generator-sifive in order to have the Wake command actually fail if we fail a test
One to update the driver file to match the new generated header file #define names

I am expecting this branch to (correctly) fail now, but I need to implement an alternative fix to https://github.com/sifive/api-generator-sifive/pull/23 so that the build actually passes.

Previous push failed (as expected), and I am now pointing this branch at https://github.com/sifive/soc-testsocket-sifive/pull/9, which should hopefully pass.
Once we confirm everything is working, I'll merge in https://github.com/sifive/soc-testsocket-sifive/pull/9, and then I'll clean up this PR to point at the merge commit and get all the CHANGELOG stuff updated.

Simulation tests are now passing, but docs are now failing. Working on a fix for that now.

Bumped various wit pointers to commits that have been merged into master and/or tagged on their respective repos. Squashed down the commits, and I think this is now ready for a final (!) review.


Do not use cml.A.where(cml.A > 0, 0) to set values smaller zero to zero

Do not do this (as it is done once in the basic processing example notebook) to set negative values to 0:
cml['A'] = cml.trsl - cml.baseline
cml['A'] = cml.A.where(cml.A > 0, 0)

This will also set all the NaNs to 0 ❗
Hence, this can lead to severe underestimation of CMLs, e.g. in interpolated maps, where CMLs with NaNs, should be excluded.

Currently I would prefer
cml.A.values[cml.A.values < 0] = 0

because it is the easier to understand than the other two options. I am a bit worried about mutating the numpy.array which is stored somehow behind the scenes, though.


Automated Package Upgrade

:tada: This PR is included in version 2.2.137 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[feat] Add an API that can open a folder directly. Not the dialog.open()

Describe the problem
I can't find any related API in the document.
Describe the solution you'd like
I hope the API can open the folder directly based on a path parameter.
Alternatives considered
No response
Additional context
No response

When this function be called, it can open the OS's file explorer.

You can do this already with shell.open which will open the explorer if given a file path; or shell.Command which needs to be manually set up per OS, but can be expanded, for example if you want to preselect files, see #4062.
That said i'm closing this as a duplicate because #4062 should cover this too.


keeps style folder but deletes everything in it

Changes the tools/removDemo.js file so that the styles folder is not deleted but that everything in the styles folder is deleted

per https://github.com/coryhouse/react-slingshot/issues/545#issue-304096397

Coverage remained the same at 91.453% when pulling 4e239567c0058388d86b6f190dfa2112ede85df5 on nharrisanalyst:master into 4f03a7d271a49dc62fa28e036c60a11ebd0a3ef3 on coryhouse:master.


improve federation trace

At the moment federation trace works by dumping the seen headers in a given reply packet.
This is great to understand a working network but pointless to diagnose a failing network.  Seems the easiest approach to take though to make trace work - just dump the seen-by headers.
People expect it more like traceroute though where you see each hop.  This is possible if I make every connector emit a trace packet over to a destination, imagine:

Client sets up a listener on choria.trace.uuid and puts in the header to emit traces there
Every connector when the packet enters and leaves sends a message to choria.trace.uuid
Client displays the traces

This way we will have a traceroute like view of the network and be able to diagnose where failures happen - or rather the hop before where they fail.

tbh, I still cant think of a way this will work.  With federation the middleware is separate there is no way to bridge the trace packets other than through federation - which is exactly the thing people will want to debug

not realistically possible, closing


Issue with rhel8.0 not existing in the dictionary.

My hypervisor is ubuntu. I got the following task failed. It might not be an issue, but I would appreciate your input/advice.
TASK [../../roles/kubeinit_libvirt : Create VM definition for the service nodes] *********************************************************************************
failed: [hypervisor-01] (item=okd-service-01) => {"ansible_loop_var": "item", "changed": false, "cmd": "virt-install    --connect qemu:///system    --name=okd-service-01    --memory memory=12288    --cpuset=auto    --vcpus=8,maxvcpus=16    --os-type=linux    --os-variant=rhel8.0    --autostart                    --network network=kimgtnet0,mac=52:54:00:f2:46:a7,model=virtio                  --graphics none    --noautoconsole    --import    --disk /var/lib/libvirt/images/okd-service-01.qcow2,format=qcow2,bus=virtio\n", "delta": "0:00:00.791032", "end": "2020-09-29 13:45:49.480230", "item": "okd-service-01", "msg": "non-zero return code", "rc": 1, "start": "2020-09-29 13:45:48.689198", "stderr": "ERROR    Error validating install location: Distro 'rhel8.0' does not exist in our dictionary", "stderr_lines": ["ERROR    Error validating install location: Distro 'rhel8.0' does not exist in our dictionary"], "stdout": "", "stdout_lines": []}

@git4liluo weird issue, this is configured here
https://github.com/Kubeinit/kubeinit/blob/11d7332e7d420344ab16b8480dc24fbdf2631a54/kubeinit/roles/kubeinit_libvirt/tasks/10_deploy_service_nodes.yml#L127
Can you please run in you hypervisor:
osinfo-query os

And see if you have available rhel8.0? if not you should have rhl8.0  (note the 'e' is not present).
Just update the playbook1 with the distro and it should work.
Please feel free to ask any questions you have, and if you find any issue also feel free to raise issues in the project's repo (https://www.github.com/kubeinit/kubeinit). Also, it would be awesome if you can star the project to catch up with updates and new features.
Thanks!

Thnx. I will use rhl8.0.


add support for detach manage mode of flink EC

What is the purpose of the change
EngineConn-Core defines the the abstractions and interfaces of the EngineConn core functions.
The Engine Service in Linkis 0.x is refactored, EngineConn will handle the engine connection
and session management.
Related issues/PRs
Related issues:
#4721
#4722
#4723
Brief change log

Add method of 'askCEngineConn' in linkis-application-manager
Add detach manage mode of FlinkJarOnceExecutor
Add FlinkManagerConcurrentExecutor

Checklist

[x] I have read the Contributing Guidelines on pull requests.
[x] I have explained the need for this PR and the problem it solves
[x] I have explained the changes or the new features added to this PR
[ ] I have added tests corresponding to this change
[ ] I have updated the documentation to reflect this change
[ ] I have verified that this change is backward compatible (If not, please discuss on the Linkis mailing list first)
[ ] If this is a code change: I have written unit tests to fully verify the new behavior.

Please resolve the code conflicts.


Bundler takes one argument

Bundler takes one argument. Now watchify works correctly and can see changes in files.

There's already a PR for this: #48. Does that work for you?

Yes but i think we do't need to fire the bundle() method.
https://github.com/jwright/marionette-wires/commit/af412eecf304ae22434ca22c980a780e0337d2f0#diff-b9e12334e9eafd8341a6107dd98510c9R116

@thejameskyle No it's not. Look at this pr https://github.com/thejameskyle/marionette-wires/pull/51


fixed apiversion clusterrolebinding.yaml and clusterrole.yaml

this fixes issue 129 submitted by me.

LGTM

What does this mean? What needs to be done to get this merged in?

so what are we waiting on now? this is a blocker trying to get it fixed ASAP.

@gargath @JoelSpeed  Any chances of merging this? We would love to keep using this chart and we are currently blocked on this issue.

Have tested it and works with change on EKS 1.22 (where rbac.authorization.k8s.io must be v1)

So when will it be merged?

Unfortunately this repo seems to be unmaintained, there seems to be a similar project for anyone who also has found themselves without wave: https://github.com/stakater/Reloader

Thank you for the contribution. I will merge #112 instead of this, as it is the earlier contribution.


Fix RIDER-96095: decouple the plugin from IntelliLang

The plugin no longer has a strong dependency on IntelliLang. All the injection-dependent stuff has been moved to an optional v2 module.

@ForNeVeR Thanks!


Total number of staff members is incorrect

On the enrollment page, the "Total: " at the bottom should be the number of staff members, but it looks like it's the number of students.

Problem seems to be on line 66 of students.list.html. It should not be hardcoded to enrollments but rather use the roster variable defined in enrollment.html.


Retry the celery task on error

Celery docs: https://docs.celeryproject.org/en/stable/userguide/tasks.html#automatic-retry-for-known-exceptions
@dhodovsk

Related to #830 but more general approach. Both issues will help, the other one will retrigger only a GitHub API call without a need to rerun the whole task.


?sqi=true&rcn=10&smf=PREFIX... vs  ?fu=1&smf=PREFIX...

Hello,
I have been dealing with the ACME Semantic Descriptor support and now I am blocked on the way to get parent resources from a smf discovery.
I have created a AE with a descriptor with RDF...
When I execute a discover like this:    ...?sqi=true&rcn=10&smf=PREFIX... I get the right result:
{"m2m:qres": "{"results": {"bindings": [{"device": {"type": "uri", "value": "http://example.com/devices/1\"}}]}, "head": {"vars": ["device"]}}"}
but when I execute the same but now using:     ?fu=1&smf=PREFIX...  to get parent resources (e.g. AE) I get:
{"m2m:uril": []}
Do ACME supports the returning of parent resources when the smf query hits?
Thank you
Alex

For this little test I have just one AE, with one cont and a SD both suns of AE.
In the discovery operation I am passing path to the parent AE, e.g.
'http://<IP_ADDRESS>:8081/cse-mn/CSensorIndoorTemperature?fu=1&smf=PREFIX+
I also tried to pass 'http://<IP_ADDRESS>:8081/cse-mn?fu=1&smf=PREFIX+  but the return is the same:
{"m2m:uril": []}
Does ACME supports discover based on smf?

Yes, it does. The issue is that with fu=1 the CSE does first a oneM2M "discovery" operation, which means a list of URI's of the child resources of your target, here the AE. In the next step, the CSE applies the semantic filtering on that list.  In your example the list contains Uris to the cnt and smd of the AE. Semantic filtering is working on child (!) resources of the target resources that are SMD resources. But since there are none, the result is empty.
Roughly:
Resource tree:
AE
  + cnt
  + smd

step: discovery: list = [ AE/cnt, AE/smd]
step: semantic filter:

look for  AE/cnt/smd -> none
look for AE/smd/smd -> none

result: list = [ ]

I am following document TR-0045... That is why I created the SD inside AE
I have just created the same SD but now inside cont and discovery returns {"m2m:uril": []}

Ok.
But as you wrote the algorithm used to answer discover operations:
step: discovery: list = [ AE/cnt, AE/smd]
step: semantic filter:
    look for AE/cnt/smd -> none
    look for AE/smd/smd -> none
result: list = [ ]

I thought that if I created the SD inside the container that it would be returned by executing a successful SPARQL query, but it is not. Please could you present the ordered steps to create the oneM2M resources including SD to be possible to return the parent of a (successful processed) SD?
Thank you

In fact I have thought once to create a oneM2M implementation as you did and as you are doing, because the majority of open source implementations have serious dependencies problems and... etc. Except ACME of course. I am dealing with standardization and have chosen oneM2M and I have just adopted ACME which seems to be a good piece of software and well written. Congratulations! So it is expected that in future days I will post new questions here when things get "blur". :-)
Great link and very useful!
Thanks once again.
Alex

Thank you very much for your kind words!
You are saying you are dealing with standardization. Are your planning to attend the oneM2M standardization meetings? We, the oneM2M standardization group, are just meeting this week at ETSI in France.
Please keep the questions coming. Perhaps also consider to ask them on StackOverflow (if they are general oneM2M question). Then the discussion will help a broader audience.

I am very interested in interoperability and in oneM2M in particular.
Can anyone attend oneM2M meetings? Do you belong to the oneM2M board?
Is it possible to attend via online? (no possibility to go to France). If so I would like to attend.

Could you try contact me on the discord channel? I'd like to introduce you to the technical plenary chair to arrange things

When I try to access https://discord.com/invite/6ryMHQC2Uj I have been getting "Invite Invalid"...
You said that meeting is in this week but when? Friday, Saturday, Sunday? I am going to talk about this with my R. Coordinator and probably he is also interested (if available) to attend the meeting.
Here is a (secondary) email for exchanging details<EMAIL_ADDRESS>

When I try to access https://discord.com/invite/6ryMHQC2Uj I have been getting "Invite Invalid"...

For me the link works. It seems that sometimes discord has troubles with the verification :(


There's no way to refresh the list of projects in the cloud explorer

except closing and re-opening VS. In fact, there's not even a way to logout of an existing account so that I can log back in again and that would refresh things.

You can logout of an account by using the "Manage Accounts" dialog available from "Tools > Google Cloud Tools > Manage Accounts...". From the dialog you can delete accounts.
Dupe of #177 to add UI to refresh projects.


Was Banned for questioning Staff

Staff was unfair because while I was doing the Mewtwo quest I had Le_tree flying around me with fly while it wasn't active. How am I supposed to respond while I have mods doing the same quest I'm on using fly and command that are unavailable to me?
I have been nothing but fair but when a so called "mod" calls me out for calling out staff, I get banned?  If I get banned for that, then I get banned for what I did, But your Staff has acted in an unprofessional way. What I did was nothing more than say that some staff have been abusing their /fly. While this is available to all. This is not available while no one have redeemed /fly, yet mods continue to use it and I get called out and banned for stating so. I will not apologize for what I have said. Better Yet Maybe look into mod abuse. I have been a long time player and if this is how I end Oblique than So be it. But I have been Fair in my judgement, yet reticulated by staff. This will be my last sentence on the subject.

This is how some of your Smods have treated players. Go ahead and look up the time as well if fly has been active. This is mod abuse, Yet I get banned for talking about it.

Nothing but ignored unless I mention it later and get banned for disruption. How is this a fair server if this type of corruption happens without consequence?

Not testing, no anything, just doing a quest, that others where doing at the time with mod privilege's. This is not fair

You were temporarily banned for 3 days because you have continuously brought up this issue in public. And refuse to listen to reason when multiple mod staff, including myself have told you how and why the SMod in question was flying. And if I recall correctly, Le_Tree left the area soon as you started complaining. Im not sure how you can abuse /fly when its a command nearly every player can use when the booster is activated. Yes it gives Mods as well other staff roles such as Builders and Quest Designers an advantage but its completely for convenience and nothing else. And you weren't banned because we are trying to silence you, if we wanted to, this would've been a permanent ban.. We've had many players question why some staff roles have certain commands when the playerbase doesn't, but you are the only one who has taken it this far. I'm not unbanning you, take this time to cool down and stop this tirade. If you continue to bring up this issue as well as the issue you caused earlier today, then you'll be permanently banned since you continued to refuse to listen to us.


fix fix some test cases

What problem does this PR solve?
Problem Summary:

add some missing output blocks for test_audit_log_behavior.out
call flush_audit_log() does not support old planner, add check for it.

Check List (For Committer)

Test

[ ] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[x] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[x] No colde files have been changed.
[ ] Other reason

Behavior changed:

[x] No.
[ ] Yes.

Does this need documentation?

[x] No.
[ ] Yes.

Release note

None

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run buildall


Feature/18

Yes, I will have a look later. Some of my commits were not meant to be merged into dev but rather to ease development for @vidhya-metacell.
Specifically, I don't think we need the props renaming, nor the react-diagrams components exposing.
I will check with @ddelpiano and do the changes myself according to his reply.


Add boat form not visible on a tablet

Steps to reproduce: click on 'add boat' from the main screen
Expected behaviour: Clicking on add boat shows the first page of the add boat form
Actual behaviour: the "add a boat" form just presents me with a blue screen (I'm on a tablet) and it was not obvious I needed to scroll down to find the first field to fill in

Tested on all apple responsive design mode layouts using MacOs Safari and it's fine. Trying next with Android.


Improve flash step for zephyr RTOS

This pr contains some cleanups and minor behavior changes which should make using and evolving the flash step in zephyr easier. The behavior changes are:

The nucleo_h743zi platform should now work again, it seems there was a faulty indentation in the previous version.
All platforms now check if the used build artifact (zephyr.exe/zephyr.bin) exists before using it.
Console output should now be consistent between the platforms (obviously excluding the flash tool).
The olimex-stm32-e407 platform now runs the flashed firmware after resetting. This is consistent with what the west flash-based platforms and the nucleo_h743zi platform do.
The step now defaults to using west flash as opposed to special casing each and every supported platform. This seems reasonable to me, as this should be the correct way for most zephyr-based use cases.

As a side effect, this should allow the usage of any suitable zephyr-supported target by just adding its name to the supported_platforms file, as flash.sh will no longer complain about an unknown platform.
It would be nice if somebody could check that i didn't break anything for the openocd-based boards, as i don't have access to any of them (i could just check that the command actually tried doing something which seemed useful for them).

Thank you very much!


Attempting to "Run Query" after opening a .soql file in the new query builder results in "No AuthInfo" error

Summary
I've opened an existing account.soql file in the SOQL extension and pressed "Run Query". Doing so  results in the Salesforce CLI output:

NamedOrgNotFound: No AuthInfo found for name ActiveScratchOrgName

Steps To Reproduce:

Open existing account.soql file with the SOQL Builder extension
Press Run Query
No output is seen
Observer error in the Salesforce CLI Output:

NamedOrgNotFound: No AuthInfo found for name ActiveScratchOrgName

Confirm that SFDX: Open Default Org works as expected and there isn't an issue connecting to the org.
Confirm that SFDX: Execute SOQL Query works as expected with the same query

Expected result
The SOQL query should run
Actual result
Salesforce CLI output error:

NamedOrgNotFound: No AuthInfo found for name ActiveScratchOrgName

Additional information

VS Code Version:
1.51.0
SFDX CLI Version:
sfdx-cli/7.80.0-b979aae708 win32-x64 node-v12.18.3
OS and version:
OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.18362 N/A Build 18362

We believe this has been resolved.


Dev mode - corousel not shown

Hi,
I have trouble with this addon. It works fine when I deploy it for production (package -Pproduction), but when I use it in development mode with springboot, I do not see the carousel. Instead, I see all the slides together in a column.
Could you help me with this?
Thank you!

Hello @hr015, if you're using springboot make sure to add this value: com.flowingcode.vaadin.addons to the vaadin.whitelisted-packages property in your application.properties file. More information about whitelisted configuration here.


[📚] Cloud Storage doesn't have getStream

The docs at
https://firebase.google.com/docs/storage/flutter/download-files#download_files
say

Once you have a reference, you can download files from Cloud Storage by calling the getData() or getStream()

but there is no getStream function on the Reference class.
Is there a feature request for having the getStream feature? I couldn't find one.

Hi @nickmeinhold, thank you for bringing this to our attention. We'll make sure to update the documentation.


command with CRLF

Not sure if this is already reported.
Script doesn't seem to be running (using Windows) when my line endings are CRLF.
docker-compose.yml
web:
  image: node:4
  volumes:
    - ..:/usr/src/app
  working_dir: /usr/src/app
  command: sh ./init.sh

init.sh (line-ending as CRLF)
#!/bin/bash

# npm install some-packages

npm start

I had to convert the line endings to LF for the container to successfully execute the script.

If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
For more information about reporting issues, see CONTRIBUTING.md.
You don't have to include this information if this is a feature request
(This is an automated, informational response)

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

@vutran This just how the Linux kernel parses #! lines -- because CR is a valid filesystem character in Unix. Your editor probably has an option to output and display Unix-style line endings.

Yes, this is expected with crlf, not related to Docker.
Closing since this seems to be as expected.


Feature/extract specification from assembly

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

155 of 248 (62.5%)  changed or added relevant lines in 10 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-5.3%) to 84.39%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

csly-cli-extractor/ParserSpecificationExtractor.cs
10
13
76.92%

csly-cli-builder/LexerGenerator.cs
36
42
85.71%

csly-cli-decompiler/Decompiler.cs
13
19
68.42%

csly-cli-decompiler/LexerDecompiler.cs
32
67
47.76%

csly-cli-decompiler/ParserDecompiler.cs
42
85
49.41%

Totals

Change from base Build<PHONE_NUMBER>:
-5.3%

Covered Lines:
1267

Relevant Lines:
1466

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

155 of 248 (62.5%)  changed or added relevant lines in 10 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-5.3%) to 84.39%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

csly-cli-extractor/ParserSpecificationExtractor.cs
10
13
76.92%

csly-cli-builder/LexerGenerator.cs
36
42
85.71%

csly-cli-decompiler/Decompiler.cs
13
19
68.42%

csly-cli-decompiler/LexerDecompiler.cs
32
67
47.76%

csly-cli-decompiler/ParserDecompiler.cs
42
85
49.41%

Totals

Change from base Build<PHONE_NUMBER>:
-5.3%

Covered Lines:
1267

Relevant Lines:
1466

💛  - Coveralls


Google Login - Error 403 - Use secure browsers

When loging in to the Riot Account with my Google Account on my Pixel 7 I get the following error:
Error 403: disallowed_useragent
Request details: access_type=online response_type=code redirect_uri=https://authenticate.riotgames.com/redirects/google state=d764ceabd425d5a6fa93aecc505bf62ad35cd87f07878bc52ec25330a163 prompt=select_account client_id=187685766663-ct6bdnthcq6jlllecpg1guhthoc7i8vv.apps.googleusercontent.com scope=openid https://www.googleapis.com/auth/userinfo.profile https://www.googleapis.com/auth/userinfo.email

I was able to log in with google now, thank you for the fix