python312Packages.aliyun-python-sdk-kms: 2.16.4 -> 2.16.5, python312Packages.aliyun-python-sdk-config: 2.2.13 -> 2.2.14, python312Packages.aliyun-python-sdk-core: 2.15.1 -> 2.15.2

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 338451 run on x86_64-linux 1

40 packages built:

python311Packages.aiooss2
python311Packages.aiooss2.dist
python311Packages.aliyun-python-sdk-cdn
python311Packages.aliyun-python-sdk-cdn.dist
python311Packages.aliyun-python-sdk-config
python311Packages.aliyun-python-sdk-config.dist
python311Packages.aliyun-python-sdk-core
python311Packages.aliyun-python-sdk-core.dist
python311Packages.aliyun-python-sdk-dbfs
python311Packages.aliyun-python-sdk-dbfs.dist
python311Packages.aliyun-python-sdk-iot
python311Packages.aliyun-python-sdk-iot.dist
python311Packages.aliyun-python-sdk-kms
python311Packages.aliyun-python-sdk-kms.dist
python311Packages.aliyun-python-sdk-sts
python311Packages.aliyun-python-sdk-sts.dist
python311Packages.oss2
python311Packages.oss2.dist
python311Packages.ossfs
python311Packages.ossfs.dist
python312Packages.aiooss2
python312Packages.aiooss2.dist
python312Packages.aliyun-python-sdk-cdn
python312Packages.aliyun-python-sdk-cdn.dist
python312Packages.aliyun-python-sdk-config
python312Packages.aliyun-python-sdk-config.dist
python312Packages.aliyun-python-sdk-core
python312Packages.aliyun-python-sdk-core.dist
python312Packages.aliyun-python-sdk-dbfs
python312Packages.aliyun-python-sdk-dbfs.dist
python312Packages.aliyun-python-sdk-iot
python312Packages.aliyun-python-sdk-iot.dist
python312Packages.aliyun-python-sdk-kms
python312Packages.aliyun-python-sdk-kms.dist
python312Packages.aliyun-python-sdk-sts
python312Packages.aliyun-python-sdk-sts.dist
python312Packages.oss2
python312Packages.oss2.dist
python312Packages.ossfs
python312Packages.ossfs.dist


example algoritm problematic

the narrative for 13.5. Vector Single-Width Scaling Shift Instructions clearly defines the function, however the formula in the examples does not explicitly reference the sign/zero extension. Rounding that would carry into or our of the high order bit are problematic.
consider SEW=8:
value in the element X'FF' vssrl by 1 should be X'80' , formula yields X'00'
value in the element X'7F' vssra by 1 should be X'40' , formula yields X'C0'
I couldn't come up this an obviously good notation to express the required value extension but perhaps this will do:
For vxrm=rnu, round = 1 << (src2-1)
Scaling shift right logical
vssrl.vv vd, vs2, vs1, vm   # vd[i] = (zero_extend(vs2[i]) + round)>>vs1[i]
vssrl.vx vd, vs2, rs1, vm   # vd[i] = (zero_extend(vs2[i]) + round)>>x[rs1]
vssrl.vi vd, vs2, imm, vm   # vd[i] = (zero_extend(vs2[i]) + round)>>imm
Scaling shift right arithmetic
vssra.vv vd, vs2, vs1, vm   # vd[i] = (sign_extend(vs2[i]) + round)>>vs1[i]
vssra.vx vd, vs2, rs1, vm   # vd[i] = (sign_extend(vs2[i]) + round)>>x[rs1]
vssra.vi vd, vs2, imm, vm   # vd[i] = (sign_extend(vs2[i]) + round)>>imm

The text has been changed to use the roundoff function, but this issue persists.  We should perhaps define roundoff_unsigned and roundoff_signed functions.  I'll make a PR.

Looks good to me.
The roundoff text is much better than original.
And now comprehensive with the signed/unsigned .
Thanks.
On Fri, Nov 29, 2019, 16:41 Andrew Waterman<EMAIL_ADDRESS>wrote:

The text has been changed to use the roundoff function, but this issue
persists. We should perhaps define roundoff_unsigned and roundoff_signed
functions. I'll make a PR.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/riscv/riscv-v-spec/issues/109?email_source=notifications&email_token=AFAWIKOHI6EVNRNFGU2WKOLQWGD73A5CNFSM4G33AHYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFPSQSY#issuecomment-559884363,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFAWIKNDNU5NXFE3JPZMUPTQWGD73ANCNFSM4G33AHYA
.

Cool, thanks for the review.


Parse cost section on infobox from API

While the API currently doesn't return cost info, it's planned to be implemented so we should make sure ketch is ready to add the information to infoboxes

It's planned to come from the game API rather than Galaxy Info. For now you can just hardcode the values for basic material prices since they're static.

For now you can just hardcode the values for basic material prices since they're static.
So is the economy static now? If my memory serves right, ship materials would fluctuate based on the economy or other factors. That, and material prices would also fluctuate based on supply and demand from, say, megabase.

If the economy is still static, I'll definitely hardcode it in the meantime. But if things still move around, I'd prefer to not provide values that can turn out to be faulty.

Yeah the prices for ores at MB are static and haven't changed in months, with no current plans to change them.

Okay thanks!

okay. i'll try to give this a go. I still don't really know what the material values are, and since I don't play galaxy. i'm going to have a galaxypedia staff member fetch them for me. i'm going to self assign myself to this and probably create a new class ketchupbot-side to calculate the values.
@Wingysam from my knowledge, the galaxy info api doesn't seem to provide ship material info. is there a way to get this from the galaxy info api, for me to then hardcode the cost values?
this is the data for a ship returned from the galaxy info api's galaxypedia endpoint

Yeah the material amounts are calculated at runtime so there's no way for Galaxy Info to know them without duplicating the complicated algorithm.
Maybe I could refactor that to calculate the prices at build time?

That'd be useful.
Getting cost info to galaxypedia is pretty high priority for me, cause I've been nagged about it by users since the Galaxypedia's been conceived.

If you want this done today you could give me an API endpoint to hit with cost data and I'll make the game post to it every time ships get reloaded.

Hmm. If we wanted to move to game-contacting-ketchupbot, I'd prefer using a websocket solution, which is what @SeaswimmerTheFsh was supposed to be working on, but doesn't appear to be happening anytime sooner.
It'd probably be better if you did that galaxy info sided, then send the data in the same galaxypedia endpoint. I'll write some logic in ketchupbot to treat it differently and to not parse it.
To be clear, all I'd really need is the material quantities for ships, not necessarily the prices, unless you'd prefer to manage it instead of ketchupbot.

In that case I'd accept a PR for the endpoint. You could store it in the KeyValue table.

In that case I'd accept a PR for the endpoint. You could store it in the KeyValue table.

The issue is that I don't program in typescript anymore, and given I'm unfamiliar with the galaxy info codebase, I probably won't be able to get an endpoint out for you anytime sooner.
I plan on reading the galaxy info codebase and implementing some updates myself eventually, but that can be weeks if not months ahead. So either you can wait for me to eventually start working on galaxy info, or you can find another person you could offload the galaxy info sided work to.

I have other priorities than adding the data to Galaxy Info right now, so I'm not available to do it at the moment.


typescript: "parser" must be specified top-level

also set emcaVersion: 6
This should fix the build failure in https://github.com/hashgraph/hedera-sdk-js/pull/22

Fixed by re-applying the extends and fixing Vue a different way


File named 'index.html' is never found

As the title goes, URL pointing to a file named 'index.html' is always redirected to root (that shows directory listing), and returns 404 if directory listing is disabled. This behaviour is new, and I assume incorrect. If the file is 'index.htm', I'm able to point at it, but it's not used as default page.

@TomMarius Please set cleanUrls to false if you want to disable the default behavior of stripping this extension from file paths or making the index redirect.


add page break for PDF output

After TOC, added by JS tooling
After Intro (Intro and IPR should be on same page if we break the two apart), added by JS tooling
In the template so that new editors can fiddle with pages breaks as desired by committee

Fixed at a0ed971398cbe4931327dcdcec74c2d9cf1546fa

@dcbullock I split (3) as a separate issue


DBMS: SW Subclass for mongodb

One of my clients is working with mongo db and would like to use
this as a SW Subclass under DBMS.
I would appreciate if you could update the schema accordingly and
include that in the next release.
Please let me know when it can be incorporated.
Thanks in advance
Jan
https://de.wikipedia.org/wiki/MongoDB
https://www.mongodb.com/

will be added to schema version 5.3.5


Can't Install the node_modules

I am trying to run this application locally but I cannot get past the part of installing node_modules
My environment:
MacBook-Pro:react-material-dashboard sebastianalvarado$ node -v
v10.0.0

MacBook-Pro:react-material-dashboard sebastianalvarado$ npm -v
5.6.0

The error that I'm getting is the following:
error An unexpected error occurred<EMAIL_ADDRESS>Request failed \"404 Not Found\"".

Hi sebasalvarado,
Please remove yarn.lock and try again. This should fix your problem. For some reason the .gitignore file did not exclude this file from the commit. We will remove it in the next commit.
Thank you,
Devias Team

Thanks for your response, it did not fix it however.
This is the output of a yarn:
MacBook-Pro:react-material-dashboard sebastianalvarado$ yarn
yarn install v1.10.1
info No lockfile found.
[1/4] 🔍  Resolving packages...
warning @material-ui/core > recompose > fbjs ><EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2.
warning react-scripts > react-app-polyfill ><EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2.
warning react-scripts ><EMAIL_ADDRESS>Way too old
warning react-scripts > workbox-webpack-plugin > workbox-build ><EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
warning react-scripts > eslint > file-entry-cache > flat-cache ><EMAIL_ADDRESS>CircularJSON is in maintenance only, flatted is its successor.
warning react-scripts > jest > jest-cli > prompts ><EMAIL_ADDRESS>Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit <https://github.com/lukeed/kleur/releases/tag/v3.0.0\> for migration path(s).
warning react-scripts > postcss-preset-env > postcss-color-functional-notation > postcss-values-parser ><EMAIL_ADDRESS>I wrote this module a very long time ago; you should use something else.
warning react-scripts > workbox-webpack-plugin > workbox-build > joi ><EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
warning react-scripts > workbox-webpack-plugin > workbox-build > joi ><EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
warning react-scripts > workbox-webpack-plugin > workbox-build > joi > topo ><EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
warning react-scripts > jest > jest-cli > jest-environment-jsdom > jsdom ><EMAIL_ADDRESS>use String.prototype.padStart()
error Couldn't find package "<EMAIL_ADDRESS>required by "<EMAIL_ADDRESS>on the "npm" registry.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Error: Couldn't find package "<EMAIL_ADDRESS>required by "<EMAIL_ADDRESS>on the "npm" registry.
    at MessageError.ExtendableBuiltin (/usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:243:66)
    at new MessageError (/usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:272:123)
    at PackageRequest.<anonymous> (/usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:33701:17)
    at Generator.throw (<anonymous>)
    at step (/usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:98:30)
    at /usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:111:13
    at run (/usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:95053:22)
    at /usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:95070:30
    at flush (/usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:94576:9)
    at process._tickCallback (internal/process/next_tick.js:172:11)
Error: Couldn't find package "<EMAIL_ADDRESS>required by "<EMAIL_ADDRESS>on the "npm" registry.
    at MessageError.ExtendableBuiltin (/usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:243:66)
    at new MessageError (/usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:272:123)
    at PackageRequest.<anonymous> (/usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:33701:17)
    at Generator.throw (<anonymous>)
    at step (/usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:98:30)
    at /usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:111:13
    at run (/usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:95053:22)
    at /usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:95070:30
    at flush (/usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:94576:9)
    at process._tickCallback (internal/process/next_tick.js:172:11)
Error: Couldn't find package "<EMAIL_ADDRESS>required by "<EMAIL_ADDRESS>on the "npm" registry.
    at MessageError.ExtendableBuiltin (/usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:243:66)
    at new MessageError (/usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:272:123)
    at PackageRequest.<anonymous> (/usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:33701:17)
    at Generator.throw (<anonymous>)
    at step (/usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:98:30)
    at /usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:111:13
    at run (/usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:95053:22)
    at /usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:95070:30
    at flush (/usr/local/Cellar/yarn/1.10.1/libexec/lib/cli.js:94576:9)
    at process._tickCallback (internal/process/next_tick.js:172:11)

Essentially the same error, can't find the package "<EMAIL_ADDRESS>. Looks like it's a WebAssembly dependancy. My yarn version is:
MacBook-Pro:react-material-dashboard sebastianalvarado$ yarn -v
1.10.1

Also, if I try npm install the error is more obscure.
MacBook-Pro:react-material-dashboard sebastianalvarado$ npm install
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2.
npm ERR! Maximum call stack size exceeded

npm ERR!      /Users/sebastianalvarado/.npm/_logs/2019-05-13T15_12_12_515Z-debug.log

Hi,
From the yarn log it seems that the error is generated by the IE11 polyfill, right? Could you please give me your repo url to see exactly why you're getting this error. Are you using Mac or Windows?
Also, in few minutes we are updating the project to a newer version using the latest material-ui package version.

This is my repo URL: https://github.com/sebasalvarado/react-material-dashboard
I just cloned your latest version and the error seems to be the same.
I am on a Mac OSX v10.14.3

Hi again,
I cloned your project, used the same Node version (v10.0.0), but I was unable to replicate your problem.
Later I ended up looking for people with the same issue and is seems that you have to remove a file (if it exists) from /Users/{your account}/.npmrc (replace with your account). Also try to clean your npm cache using npm cache clean --force.
Let me know if it works.

Awesome! Thanks so much, I think that removing .npmrc file made it, for anyone having the problem in the future you need to remove this file if you still have it.


Create an issue comment with GitHub Script

🎉 You've created this issue comment using GitHub Script!!!


Add Jonny-T87's file slide

I have: created a branch, created a file and made a commit, and opened a pull request for file slide

I also like it.

👍 Fantastic


Best way to auto generate swagger.yaml file for hug api.

There is a way using hug documentation api.http.documentation(). We can convert this to yaml file but is there any library or best practice around this.

Hi @dggs123 :
Have you find a good way to do that yet, in a way the yaml output is 100% following the spec?
Thanks

Checking in :)


Added a hook that gets called after the character initialized

Added a hook that gets called after the character initialized

Why would you call a hook called ‘OnPlayerCharacterInitialized’ inside a hook callback called ‘PlayerCharacterInitialized’? The hook already exists!
Also we don’t prefix hooks with ‘On’, and we call hooks with ‘cwPlugin:Call’ not with ‘hook.Call’ as that is just for regular GMod hooks.

No, PlayerCharacterInitialized sadly doesn't work how I wanted it to work. I require OnPlayerCharacterInitialized, because I need all the information
which class got assigned, because after it got initialized it will check for the rank and assign it a class, which when I just use PlayerCharacterInitialized can be achieved.

fixed the typo

Added a new hook called PlayerCanTakeKnockbackFromDamage


refactored the pageViewEvent so it actually works...

Description
Code cleanup
Re-added pageViewField to view events
pageView events now also send customMetadata
Comments
Linter
Modified the config structure to simplify it

@jdevost It looks really weird to do that in Go, its a good idea but with the different types it looks really fungo :(

@erocheleau 👎 for Go. I'll stick to js/nodejs :-)

It's the difference between typed and not typed :D


UI improvements

UI Improvements required
Meeting 9th October

Added in some minor css and formatting improvements

todo: some buttons are larger than necessary e.g. colour selector, widths selector save buttons could be a row of icons

main functionality implemented


Update README.rst

Hosting in StackForge was superseded by the OpenStack organization.

Hi thanks for your contribution, the official repository is on https://github.com/openstack/cloudbase-init, patches are reviewed via Gerritt