Grunt-sass error

Hi all,
When I run the command "grunt watch" it was running properly before, but I installed slickJS npm then I started getting the error
Local Npm module "grunt-sass" not found. Is it installed?
Then I tried installing using the command : npm install grunt-sass

<EMAIL_ADDRESS>install C:\xampp\htdocs\feedprojects\docroot\sites\all\themes                                                                                \feed\born\node_modules\node-sass
node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v3.1                                                                                3.1/win32-x64-59_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v3.13.1/win                                                                                32-x64-59_binding.node":
HTTP error 404 Not Found
Hint: If github.com is not accessible in your location
try setting a proxy via HTTP_PROXY, e.g.
  export HTTP_PROXY=http://example.com:1234

or configure npm proxy via
  npm config set proxy http://example.com:8080

<EMAIL_ADDRESS>postinstall C:\xampp\htdocs\feedprojects\docroot\sites\all\th                                                                                emes\feed\born\node_modules\node-sass
node scripts/build.js

Building: C:\Program Files\nodejs\node.exe C:\xampp\htdocs\feedprojects\docroot\                                                                                sites\all\themes\feed\born\node_modules\node-gyp\bin\node-gyp.js rebuild --verbo                                                                                se --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [ 'C:\Program Files\nodejs\node.exe',
gyp verb cli   'C:\xampp\htdocs\feedprojects\docroot\sites\all\themes\fe                                                                                ed\born\node_modules\node-gyp\bin\node-gyp.js',
gyp verb cli   'rebuild',
gyp verb cli   '--verbose',
gyp verb cli   '--libsass_ext=',
gyp verb cli   '--libsass_cflags=',
gyp verb cli   '--libsass_ldflags=',
gyp verb cli   '--libsass_library=' ]
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| win32 | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb which failed Error: not found: python2
gyp verb which failed     at F (C:\xampp\htdocs\feedprojects\docroot\sites\all                                                                                \themes\feed\born\node_modules\which\which.js:40:28)
gyp verb which failed     at E (C:\xampp\htdocs\feedprojects\docroot\sites\all                                                                                \themes\feed\born\node_modules\which\which.js:43:29)
gyp verb which failed     at C:\xampp\htdocs\feedprojects\docroot\sites\all\th                                                                                emes\feed\born\node_modules\which\which.js:54:16
gyp verb which failed     at FSReqWrap.oncomplete (fs.js:166:21)
gyp verb which failed  python2 { Error: not found: python2
gyp verb which failed     at F (C:\xampp\htdocs\feedprojects\docroot\sites\all                                                                                \themes\feed\born\node_modules\which\which.js:40:28)
gyp verb which failed     at E (C:\xampp\htdocs\feedprojects\docroot\sites\all                                                                                \themes\feed\born\node_modules\which\which.js:43:29)
gyp verb which failed     at C:\xampp\htdocs\feedprojects\docroot\sites\all\th                                                                                emes\feed\born\node_modules\which\which.js:54:16
gyp verb which failed     at FSReqWrap.oncomplete (fs.js:166:21)
gyp verb which failed   stack: 'Error: not found: python2\n    at F (C:\xampp                                                                                \htdocs\feedprojects\docroot\sites\all\themes\feed\born\node_modules\w                                                                                hich\which.js:40:28)\n    at E (C:\xampp\htdocs\feedprojects\docroot\sites                                                                                \all\themes\feed\born\node_modules\which\which.js:43:29)\n    at C:\xamp                                                                                p\htdocs\feedprojects\docroot\sites\all\themes\feed\born\node_modules\                                                                                which\which.js:54:16\n    at FSReqWrap.oncomplete (fs.js:166:21)' }
gyp verb check python checking for Python executable "python" in the PATH
gyp verb which failed Error: not found: python
gyp verb which failed     at F (C:\xampp\htdocs\feedprojects\docroot\sites\all                                                                                \themes\feed\born\node_modules\which\which.js:40:28)
gyp verb which failed     at E (C:\xampp\htdocs\feedprojects\docroot\sites\all                                                                                \themes\feed\born\node_modules\which\which.js:43:29)
gyp verb which failed     at C:\xampp\htdocs\feedprojects\docroot\sites\all\th                                                                                emes\feed\born\node_modules\which\which.js:54:16
gyp verb which failed     at FSReqWrap.oncomplete (fs.js:166:21)
gyp verb which failed  python { Error: not found: python
gyp verb which failed     at F (C:\xampp\htdocs\feedprojects\docroot\sites\all                                                                                \themes\feed\born\node_modules\which\which.js:40:28)
gyp verb which failed     at E (C:\xampp\htdocs\feedprojects\docroot\sites\all                                                                                \themes\feed\born\node_modules\which\which.js:43:29)
gyp verb which failed     at C:\xampp\htdocs\feedprojects\docroot\sites\all\th                                                                                emes\feed\born\node_modules\which\which.js:54:16
gyp verb which failed     at FSReqWrap.oncomplete (fs.js:166:21)
gyp verb which failed   stack: 'Error: not found: python\n    at F (C:\xampp\                                                                                \htdocs\feedprojects\docroot\sites\all\themes\feed\born\node_modules\wh                                                                                ich\which.js:40:28)\n    at E (C:\xampp\htdocs\feedprojects\docroot\sites\                                                                                \all\themes\feed\born\node_modules\which\which.js:43:29)\n    at C:\xampp                                                                                \htdocs\feedprojects\docroot\sites\all\themes\feed\born\node_modules\w                                                                                hich\which.js:54:16\n    at FSReqWrap.oncomplete (fs.js:166:21)' }
gyp verb could not find "python". checking python launcher
gyp verb could not find "python". guessing location
gyp verb ensuring that file exists: C:\Python27\python.exe
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYT                                                                                HON env variable.
gyp ERR! stack     at PythonFinder.failNoPython (C:\xampp\htdocs\feedprojects\do                                                                                croot\sites\all\themes\feed\born\node_modules\node-gyp\lib\configure.js:483:19)
gyp ERR! stack     at PythonFinder. (C:\xampp\htdocs\feedprojects\doc                                                                                root\sites\all\themes\feed\born\node_modules\node-gyp\lib\configure.js:508:16)
gyp ERR! stack     at C:\xampp\htdocs\feedprojects\docroot\sites\all\themes\feed                                                                                \born\node_modules\node-gyp\node_modules\graceful-fs\polyfills.js:284:29
gyp ERR! stack     at FSReqWrap.oncomplete (fs.js:166:21)
gyp ERR! System Windows_NT 10.0.15063
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\xampp\htdocs\feedp                                                                                rojects\docroot\sites\all\themes\feed\born\node_modules\node-gyp\bin\n                                                                                ode-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsas                                                                                s_ldflags=" "--libsass_library="
gyp ERR! cwd C:\xampp\htdocs\feedprojects\docroot\sites\all\themes\feed\born\nod                                                                                e_modules\node-sass
gyp ERR! node -v v9.0.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
Build failed with error code: 1
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is inst                                                                                alled. You must install peer dependencies yourself.
npm WARN born No description
npm WARN born No repository field.
npm WARN born No license field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional log                                                                                ging output above.
npm ERR!      C:\Users\naveen.bhandari\AppData\Roaming\npm-cache_logs\2018-03-03                                                                                T08_59_20_829Z-debug.log
I see that the link from github is not working when I try to open in a new tab, looks like file is not available now. Please let me know how I can fix this error.

3.13.1 is very old and doesn't support Node 9, please upgrade your node-sass (by upgrading your grunt-sass version) or downgrade your node version to a supported version as indicated on the 3.13.1 release page


Get response for date question

Trello: https://trello.com/c/h5u7N1T9
Follows on from: PR #5315
What's changed?
Add a method to DateQuestionPresenter to get the current value of the date fields.
Changes in this PR

[x] Date question

Changes in other PRs

[x] When a user click back on a URL based Smart Answer then the previous questions show, with the previous answer pre-filled (#5315)
[x] When a user click back on a session based Smart Answer then the previous questions show, with the previous answer pre-filled (#5315)
[x] Country-select question (#5315)
[x] Money question (#5315)
[x] Postcode question (#5315)
[x] Value question (#5315)
[x] Checkbox question (#5316)
[x] Radio button question
[x] Salary question (#5320)

Why?
There is currently a bug in session-based smart-answers, where answers to previous date questions are not being populated even though the answers exist in the session.
⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠

@kevindew Thanks for the re-review, I've made the suggested change and fixed up.


Adding new school

http://www.colonialschooldistrict.org/williampenn/

@Badvillain01 Pull request merged. Thank you!


[DOC-6738] enforce supported restore version

Addresses DOC-6738, DOC-7227:

As of 23.1, we do not support restoring backups outside of the versioning policy window. Restoring backups older than the minimum supported binary version is blocked. Only version N and N+1 can be restored.

Preview:

Restoring Backups Across Versions

I tested it out and this is our current error message:
ERROR: backup from version 22.1 is older than the minimum restoreable version 22.2 HINT: refer to our documentation about restoring across versions: https://www.cockroachlabs.com/docs/v22.2/restoring-backups-across-versions.html
It's currently linking out to v22.2 so it would need to be updated to 23.1.

Hi @adityamaru, could you take a look at this whenever you get the chance? Thanks!


Running on a data without test labels

Hello there
Suppose I have trained my model on a dataset having the images as well as masks in the training as well as test set (Cityscape dataset). Is it possible that after training it on the (cityscape) dataset, I run it for creating masks of MSMT17_V2 image dataset? If yes what all changes should I do? Thank you well in advance for the reply :-)

Hi, @absagargupta
You can ake prediction on any images/any dataset (make sure to preprocess them same as in training stage), but model will produce label it have been trained on.

Thank you so much for the prompt reply. In case I need just the labels of people and the background what changes should I take care of?

Suppose you have trained you model for C=10 classes, where value 3 is people class.
Output of network will be a tensor output with shape (N, H, W, 10).
To get mask of people class:
mask = (np.argmax(output, axis=-1) == 3)

Thank you. :-)


Set radius for each window's corner

Describe your PR, what does it fix/add?
This PR opens a possibility to define a radius for each window's corner separately. This can come as a new way for ricing Hyprland in combination of modified hyprwm/hyprland-plugins/hyprbars (please don't judge color scheming, I set them to have a high contrast).

As you can see window has rounded corners only at the bottom and hyprbars only at the top. They become more unified and it actually seems like hyprbars is part of the window.
Rounding has additional definition:
decoration {
    rounding = 15 # old way
    rounding = 0,0,15,15 # new way: topLeft, topRight, bottomRight, bottomLeft
}

Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
However it is not done yet and there are still some issues. For example: window border isn't part of the bar (in picture set to size 7) as it still renders around the original window and not around hyprbars.

On top of that as you can see (in highlighted red rectangle) the border is rounded even though radius is set to 0. To keep it consistent there shouldn't be any rounding.
When merged it will break hyprwm/hyprland-plugins/hyprbars and hyprwm/hyprland-plugins/borders-plus-plus as they rely on CWindow::rounding() and not the changed CWindow::getCornerRadii().
Also I'm not sure if substraction box for renderdata.damage has correct values. I've left a TODO comment there.
Is it ready for merging, or does it need work?
PR is not ready for merging. I just wanted to see if it's a valid feature to add into Hyprland and if there's any interest for it.
If it will be decided to merge this, I'll make another PR into hyprwm/hyprland-plugins to fix compatibility and rounding.

Probably not supported by the API but can one add multiple ways of defining variables, vaxry?
In this example it would be perfect:
decoration {
    rounding = 15 # old way => would become the same as rounding = 15,15,15,15
    rounding = 0,0,15,15 # new way => when needed users can use this syntax
}

Probably not supported by the API but can one add multiple ways of defining variables, vaxry? In this example it would be perfect:
decoration {
    rounding = 15 # old way => would become the same as rounding = 15,15,15,15
    rounding = 0,0,15,15 # new way => when needed users can use this syntax
}

Yes. I kept the old way of defining rounding with one integer and added a new way with four separated by comma.
This
rounding = 15

then gets mapped as:
rounding = 15,15,15,15

@Eclextic already possible.

This would be a nice addition at least for people who use hyprbars as plugin.

I was looking to see if it was possible to set corner-radius on a per-corner basis and I found this merge request. I'm in favor of this feature. Giving more customization options for users, when it doesn't add unnecessary complexity, is always a good thing.

I was looking to see if it was possible to set corner-radius on a per-corner basis and I found this merge request. I'm in favor of this feature. Giving more customization options for users, when it doesn't add unnecessary complexity, is always a good thing.

I appreciate the support but instead of commenting it's better to give thumbs up to the PR (first comment) so that it's easier to see which PRs are wanted by people.
Currently there's big migration away from wlroots. That includes some changes in rendering. When that's done and polished I'll take a second look on this and will try to finish it.


python312Packages.terminaltables3: init at 4.0.0

Add the python package terminaltables3 since it's a requirement for python3Packages.keep

Things done

Built on platform(s)

[x] 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

[x] Fits CONTRIBUTING.md.

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

I can't add tests since upstream doesn't have any, but I will add an import check

I guess you could if you use fetchFromGitHub instead ?

It seems I confused the git repo of terminaltables and terminaltables3, there are indeed tests, so I'll add the hook

Looks like there's a merge conflict.

It seems the package was added in ca49d19831ac9. I'll close this pr then


Issue printing numbers starting with 0s

Hi! I'm having an issue when I'm trying to pass a value starting with 0 to the excel, for example if I pass the value '0000234', when I download the excel it appears as '234'. I'm guessing that the Excel is treating the value as a number instead of a string, and I tried using a callback with the .toString() method with no luck.
Any help with this? would be deeply appreciated.
Thanks!

Hi
I just face the same issue and can get it resolved by workaround to put zero-width whitespace in front of value using callback.
you can copy zero white space character from below link
https://beautifuldingbats.com/punctuation/whitespace/
then put it in your field call back

"telephone": {field: "user.telephone", callback: value =>  ${value}}

with the extra white space in between and $ of${value}
but the down side if user use VLOOKUP function in excel it will consider the white space as well.

Thanks for the solution! what I finally did is passing the value as
="value".
this shows the value correctly in the spreadsheet, but then if you look for
it in the "formula" field you will see it with the =""
Ill try this one anyway!
El vie., 5 jul. 2019 5:59, innozent<EMAIL_ADDRESS>escribió:

Hi
I just face the same issue and can get it resolved by workaround to put
zero-width whitespace in front of value using callback.
you can copy zero white space character from below link
https://beautifuldingbats.com/punctuation/whitespace/
then put it in your field call back
"telephone": {field: "user.telephone", callback: value => ${value}}
with the extra white space in between and $ of${value}
but the down side if user use VLOOKUP function in excel it will consider
the white space as well.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jecovier/vue-json-excel/issues/107?email_source=notifications&email_token=AENRYP2TFGXQ3EYS34CBPX3P53BIVA5CNFSM4H4P3HOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZIPFPY#issuecomment-508621503,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AENRYP7BORVY4Y2YRXAJCBLP53BIVANCNFSM4H4P3HOA
.

我遇到了同样的问题，我的值为 "01234"字符串，导出后变成了  “1234” 。


convert to hdbview

Hi Thomas,
I can see there is massconvert for converting hdbdd entities to hdbtable format. But it does not convert views to hdbview format.
Do you have plan to support this request.
currently i am migrating from Neo to CF. There are 100 of views to converted to hdbview files.
Still i used the inspectview option to convert view to hdbview for the below view
context MD_SPC {
view TEMP as select from c {
MO, MATERIALNR, UOM, CURRENCY, MAX(CALMONTH) CALMONTH
}
where ID_DATASET = 1
GROUP BY MO, MATERIALNR, UOM, CURRENCY;
view VIEW as select from c join TEMP as z on c.MO=z.MO and c.UOM = z.UOM and c.CURRENCY = z.CURRENCY and c.MATERIALNR = z.MATERIALNR and c.CALMONTH = z.CALMONTH {
	c.MO,
	c.CURRENCY,
	c.MATERIALNR,
	max(c.COSTPERUOM) COSTPERUOM
	//c.COSTPERPIECE
}//where c.UOM = 'ST'
GROUP BY c.MO, c.MATERIALNR, c.CURRENCY;

};
hana-cli inspectView HFP_INTERNAL HFP_PMT.VIEW::MD_SPC.VIEW -o hdbview -a
Using Connection Configuration loaded via default-env-admin.json
CDS compilation failed
.cds:1:21-22: Error: Extraneous ‘:’, expecting ‹Identifier›
.cds:1:22-33: Error: No artifact has been found with name “MD_SPC_VIEW” (in entity:“HFP_PMT_VIEW”)
Is there any way i can convert to hdbview format or similar? please let me know can you please suggest if there is any option exists.
Regards,
Karthick
Regards,
Karthick

There are no current plans to add views to the Mass Convert. That would be an enhancement request.
As far as the inspectView - are you using the name of the object within the database?  You can't use the CDS name but the SQL View name.  We lookup by the SQLView name.  If that is your SQLView name then you likely need the --useQuoted true parameter on the command.

I have added Views to massConvert with the latest release this afternoon.


Update config.py

After creating your pull request, tick these boxes if they are applicable to you.

[ ] I have tested my changes against the review branch (the latest developmental version), and this pull request is targeting that branch as a base
[ ] I have tested my changes on Python 3.5.3 or higher

Description
Related issues (if applicable)

You leaked your bot token. Please reset your bot's token in the discord's dashboard.
Also, this is how to correctly configure your bot: https://just-some-bots.github.io/MusicBot/using/configuration/


Free up disk space in CI + generate utilization report

Frees up disk space in CI by deleting unnecessary files, and prints useful utilization info

This change is


Build failure: kstars

Steps To Reproduce
There is a hash mismatch for kstars in nixpkgs-unstable
Steps to reproduce the behavior:

nix build nixpkgs#kstars

Build log
$ nix build nixpkgs#kstars
error: hash mismatch in fixed-output derivation '/nix/store/0ps64p08rn47dwp7bvn5fvnlcd6qya3h-source.drv':
         specified: sha256-28RRW+ncMiQcBb/lybEKTeV08ZkF3IqLkeTHNW5nhls=
            got:    sha256-enID8edG6JS0uOeHFnPjswHXSp2v444JKf/388/2DzI=
error: 1 dependencies of derivation '/nix/store/ds1ipaxn309705gwibzxcvrp4dgqr5w0-kstars-3.6.9.drv' failed to build

Additional context
Add any other context about the problem here.
Notify maintainers
@timput
@hjones2199
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.23, NixOS, 24.05 (Uakari), 24.05.20240329.d8fe5e6`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - nixpkgs: `/nix/store/cb1gs888vfqxawvc65q1dk6jzbayh3wz-source`

Add a :+1: reaction to issues you find important.

Last updated by @bzizou

As was spotted during the PR review https://github.com/NixOS/nixpkgs/pull/281099#discussion_r1486018642, the ref stable-3.6.9 is a branch not a tag.

The source of the problem is (also mentionned in a #281099 comment) a typo in the name of the latest version of kstars
files (https://bugs.kde.org/show_bug.cgi?id=480853).
There's now a 3.7.0 version out. So I'll suggest a new PR with this version, using the official source


Custom App Client does not seem to work

Thanks for this sample, what I found during the testing is that custom app client ${var.aos_domain_name}-opensearch does not seem to be used by Opensearch, Opensearch still relies on the the auto-created client app.
This is because in oath flow a server needs to store client ID and client secret to use these in redirect queries, and that what happens behind the scenes when Opensearch creates the Client APP. It takes the generated Client ID and Secret and stores them in the cluster somewhere, I have no clue where actually.
Simple test is to remove the auto-created app client, then the whole authentication is broken, and the domain as well cause there is no way to set ClientID and Secret through console or API.
I've elaborated a bit in this comment https://github.com/hashicorp/terraform-provider-aws/issues/5557#issuecomment-1193120014

Hi @vavdoshka ,
As you have correctly noticed, this behaviour is related to the issue in the Terraform AWS provider. That is noted in the comment left in the code.
Once the issue is solved, it will be possible to remove the workaround.
If I understood correctly, everything works until you delete the auto-created app client?

I've elaborated on the issue here
there is actually no way to automate the full flow because OpenSearch relies on Application Client ID and Secret, which it gets from the application client it creates itself.

I've elaborated on the issue here
there is actually no way to automate the full flow because OpenSearch relies on Application Client ID and Secret, which it gets from the application client it creates itself.

If you follow the instructions in the README you will have the deployment done in an automated way, without a manual intervention.

This is precisely what I did, and that was very helpful.
But as soon as one removes the autogenerated application client, the authentication does not work anymore,
which makes the point that the custom application client:
https://github.com/aws-samples/opensearch-in-vpc/blob/849d9aebd6f56aaae4f8c1865e53f613633abc59/opensearch-in-vpc-module/opensearch.tf#L72-L87
is just useless; nothing is using it. When one removes it, nothing basically will change; the app authentication will work intact.

Am trying this but am getting this error any clue? thanks in advance!
module.opensearch_example.aws_elasticsearch_domain.aos (local-exec): Error parsing parameter '--callback-urls': Unable to retrieve https://XXXXXXXX.REGION.XX.amazonaws.com/_plugin/kibana/app/kibana: received non 200 status code of 302


Can't load comment for the last 12 hours

Right now every post in the last 12 hours (or even more) doesn't have any comments and have "Loading Failed" instead.

Hi @SimonHalvdansson,
I came here to post this exact issue. I am also unable to load recent hn posts  comments. Tried deleting data, reinstalling app, nothing seems to work.
Regards,
Sourabh

This is due to the HN Algolia API being down. Long term I want to enable an alternate API backend but for now I've set a nice error message when this happens in https://github.com/SimonHalvdansson/Harmonic-HN/commit/f373225216eb28ea8bfacbecd8f300098d9baa43. As a user, there is nothing that can be done right now but these things usually pass in not too long.

Ah so it's algolia. I forgot what HN API was and only found firebase when I google it so I thought it's not an API problem. I hope it'll not last too long.


Error Relating to JEI Type Mods

Me and my friend Vinixatoki have created our own modpack and used this mod as an addition.
After playing for a bit, we encountered an error with the gems.
The gems collected from chests, IE generated structure, when put directly in inventory would be normal.  However, upon throwing the gem out of your inventory and picking it up again, the item comes back as an "Errored" gem, which has no use.  Gems that drop from mobs also fit this category.
Under strenuous testing, the error appears to happen to JustEnoughItems, or mods that show recipes and others, but also appears to be inconsistent as further testing brings successful results with no changes.  (I LOVE CODING YEAAAHHHH!)
If anything, I am not a coder and have no skill in this, and I would like to bring this up (As I saw someone else brought it up,) I did more searching and found what could be the cause.
Latest Mod Version 7.3.5
Game Version 1.20.1

This sounds like something is causing data loss on items, though I suspect that would propagate to more items than just Gems

duplicate of #1242


Add support for TLS

Since version 1.5.13, Memcached supports TLS.
Motivation
At OpenStack, we are considering a switch from python-memcached to pymemcache in our oslo.cache Memcache backend driver. In the next step, we will need to enable TLS in Memcached as data must be encrypted in the wire for our scenario.
I looked over the documentation and couldn't find anything related to TLS support. If there is a way to achieve that, please let us know.
I would like to help with the implementation of this if needed.

I don't believe anyone is working on TLS support so we'd gladly accept a contribution that implements it.

Hi @jparise,
Thanks for reaching out!
We actually have backend drivers for multiple python memcached clients. We'll try to synchronize patches across all clients we use and try to merge the feedback reviews we get in all of them.
Here is our memcached python clients mapping so far:
Oslo Cache Memcached Backends
oslo_cache.memcache_pool

Underlying library: python-memcached
Feature request: https://github.com/linsomniac/python-memcached/issues/171
Possible future underlying library: pymemcache
Change: https://review.opendev.org/#/c/634457
Feature request: https://github.com/pinterest/pymemcache/issues/258

dogpile.cache.memcached

Underlying library: python-memcached
Feature request: https://github.com/linsomniac/python-memcached/issues/171

dogpile.cache.pylibmc

Underlying library: pylibmc
Feature request: https://github.com/lericson/pylibmc/issues/255

dogpile.cache.bmemcached

Underlying library: python-binary-memcached
Feature request: https://github.com/jaysonsantos/python-binary-memcached/issues/207

Closed by #276

Thanks for the reviews @jparise o/


Option to allow ALL repeatable scripts to run (even if unchanged).

What version of Flyway are you using?
4.0.3
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin, SBT plugin, ANT tasks)
Command line
What database are you using (type & version)?
MySQL 5.6
What operating system are you using?
Windows 7
What did you do?
(Please include the content causing the issue, any relevant configuration settings, and the command you ran)
flyway migrate
What did you expect to see?
Feature Request:
Needs a config, command line and API option to allow ALL repeatable scripts to run (even if unchanged) after the versioned scripts run.
Use Case: I want to recompile ALL executable code against new schema changes to ensure that the required fields and types are still valid for all existing code.  I've used this invaluable feature in other migration tools.  Very useful as a config setting on your CI server.
What did you see instead?
Missing feature.

Currently there is also a very real risk that you accidentally script the same object twice in two different R__ scripts.  You update one script, run flyway migrate and only one of these scripts runs (looks good & your app works ok on you dev machine so you commit the change). Now someone later performs a migration that runs both scripts. The later one happens to overwrite your recent change. Nasty mystery bug!  Safer to rerun all R__ script to avoid this.

To add to the feature request: Could java / jdbc migrations be configured to run regardless of whether the checksum changed?
What I have done as a workaround for my repeatable java / jdbc migrations, I have implemented MigrationChecksumProvider and am returning a random Integer every time it runs.
Does anyone have a better workaround for this? I need to make sure that the migration is running every time.

+1 we would also like to see this feature. We run a hierarchical set of database migrations targeting the same schema all managed by flyway. We use repeatable migrations to provide defaults for code tables and the like. Clients may override certain values with their own Flyway migration. If we now change something in the root we would like all repeatable migrations to run, including the non-changed client overrides.

+1 we would like this feature too for testing that repeatable migrations are idempotent.

+1 We would also like this feature to be able to separate our tables, grants, default inserts and indices in different migration files especially during development.

+1 Would be great to have this feature for development databases!

+1 would be highly useful during developing phases

This would be very handy.
My current solution is to have a comment at the top of every repeatable migration with the version of the latest migration. When the repeatable migrations need to be rerun, I just find replace on the whole project for that comment to update it to the new version.

Rather than a binary option, how would everyone feel about extending the migration naming convention:
R__repeatableMigration.sql runs as now, only when the file is changed,
A__alwaysRunMigration.sql runs on every migration?
(This also starts to work towards the Flyway Test story, as A__ migrations would be an ideal place to include integrity checks)

I just kinda realized that this can already be somewhat accomplished using Flyway's callbacks: https://flywaydb.org/documentation/callbacks

Another option could be to add some metadata to the top of the repeatable script:
-- flyway run: always

I just kinda realized that this can already be somewhat accomplished using Flyway's callbacks: https://flywaydb.org/documentation/callbacks

This is exactly how we do it. We have an afterMigrate.sql script that compiles all our packages which are defined as separate repeatable migrations and this works very well.
The call back option could provide more flexibility around the implementation as some repeatable migrations you may only wish to execute when necessary (ie only target all the package bodies excluding materilized views). The callback could do this and allows for the one off custom script to executed.

We have an afterMigrate.sql script that compiles all our packages which are defined as separate repeatable migrations and this works very well.

@cdavid15 could you please expound on this? How are you compiling stuff from within a SQL file? Sounds interesting.

Flyway is running against an oracle database so it’s custom plsql block that executes against the USER_OBJECTS view to determine the correct objects (packages, package bodies etc) then we loop through the results and execute the statement to compile.
When I’m back in at work on Monday I’ll update this with a sample script. I’m sure the exact use case we used it for was when packages were invalid then we would recompile them. May not meet every use case being described above but may be useful to some.

Another use case:
Conditional Compilation in PL/SQL
We are using conditional compilation for making some private methods accessible for utPLSQL unit tests in our test environments.
The conditional code is included (or not) only at compile time. You can't change the code afterwards by changing the compile flag and compiling the existing code again.
If we could set the compile flag and "force" flyway to repeat the repeatables that would help a lot!

We're not convinced adding this new option is the best approach.
As we understand it, this feature is desired to test all the scripts work when run from scratch. We think this sort of 'start from scratch' test scenario is the responsibility of a CI environment. In CI you can provision a new DB, migrate all Flyway scripts, and see if it works.
For instance, @tohagan says:

Safer to test rerunning all R__ script to avoid this as this reflects the true database state after a clean & full migrate...you want an option to perform this for your CI testing environment

In this scenario, for instance, we think you should just introduce a CI step that provisions an empty DB and migrates. No new functionality is needed from Flyway in order to do this.
So we think more robust CI is the solution here. However we're open to more discussion if this isn't a desirable option for people.

We wrote a blog post on how to do this with the new timestamp placeholder released in Flyway 6.3.0. https://flywaydb.org/blog/flyway-timestampsAndRepeatables
I will close this issue. If this solution does not work for you please open a new issue with the reasons why.

We wrote a blog post on how to do this with the new timestamp placeholder released in Flyway 6.3.0. https://flywaydb.org/blog/flyway-timestampsAndRepeatables
I will close this issue. If this solution does not work for you please open a new issue with the reasons why.

Updated link for future reference
https://www.red-gate.com/blog/timestamps-and-repeatable-migrations


Resolving hostnames takes too long

I'm in a network that has about 100-200 people in it, and resolving the hostnames takes too long. I don't really need the names so would there be an option to skip it (or a timeout perhaps?)

You Are Right it will be good change to add option to skip host name scan

Good point. I will have a look at your pull request when I have time.
Thanks!


docs: mention ARGILLA_AUTH_SECRET_KEY in docker-compose deployment

Description
I'm proposing to add a mention to the var ARGILLA_AUTH_SECRET_KEY introduced in https://github.com/argilla-io/argilla/pull/4539 to the docker-compose-related documentation in docs/_source/getting_started/installation/deployments/docker_compose.md
As far as I am aware, that env var needs to be set in order to run the service in docker-compose.
It's a small edit, I didn't create (yet) an issue for this.

[x] Documentation update

How Has This Been Tested

[ ] sphinx-autobuild

I didn't run sphinx! I had troubles w/ cloning, will update this as soon as I can
Checklist

[x] I added relevant documentation
[ ] I followed the style guidelines of this project
[ ] I did a self-review of my code
[ ] I made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I filled out the contributor form (see text above)
[ ] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)

@davidefiocco thanks for the PR. I updated the phrasing a bit and will merge it now :)


[POC] Data Interfaces v38 candidate

Closing until @juditnovak is back.

Sure.
I In fact, the candidate v38 used here was not yet final, so updates were needed here anyway :-)


bumping version to 1.3.1

Coverage remained the same at 98.757% when pulling 6cfb3c8190fad68de2f0b0831ed857352dc5b5a6 on crubin/release-1.3.1 into 5ae5058720c033059dbc67b944acb8045ed1de29 on master.


[docs] Default theme viewer bad font on linux

Duplicates

[X] I have searched the existing issues

Related page
https://mui.com/material-ui/customization/default-theme/
Kind of issue
Other
Issue description
It seems that font-family field was overriden for MuiTreeItems:
.css-1hogq46 .MuiTreeItem-content .MuiTreeItem-label {
    font-family: Menlo,Consolas;
    font-size: 0.825rem;
}

Menlo is MacOS font, and Consolas is a Windows font. I have neither, so for me it fallbacks to Liberation Sans, which is a Times New Roman-looking font:

This can be solved by inserting a generic default:
font-family: Menlo, Consolas, monospace;

It will then render in a monospace font at least.
Context 🔦
n/a

Generic monospace font is a good place to start for sure. Maybe @danilo-leal has ideas for something more specific?


Update Kuberntes Manifests

Since all the resources in the complete demo yaml are namespaced it
makes sense to also create the namespace itself.

Added namespace to complete-demo.yaml

Updated all manifests and Helm chart to use updated APIs.

Deployments updated to use apps/v1
Added selector to all Deployments
DaemonSets upadted to use apps/v1
Ingresses updated to use networking.k8s.io/v1beta1
NetworkPolicies updated to use networking.k8s.io/v1

Updated the Helm chart version since the resources were updated.

Bump Helm chart version to 0.3.0

This will work on k8s 1.14 and above, where the Ingress resource would
break in 1.13 and less, where it is still under extensions/v1beta1

Read the contribution guidelines
Include a reference to a related issue in this repository
A description of the changes proposed in the pull request

LGTM, this seems to be the most complete of all open PRs  regarding the api version issues


Allow for top-level Elasticsearch mapping to be defined

It would be nice to define an explicit Elasticsearch mapping (minus any _meta fields` at the top of the schema. Something akin to what is in the Elasticsearch documentation:
PUT /my-index-000001
{
  "mappings": {
    "properties": {
      "age":    { "type": "integer" },
      "email":  { "type": "keyword"  },
      "name":   { "type": "text"  }
    }
  }
}

I believe you can do this by setting any mapping you want inside transform.mapping: {} in the schema.json file. We use this to create abstract mappings that apply to some downstream transforms - working well so far.

@nowfred The problem is that we use custom plugins to shape the schema into a custom format before indexing. Our mappings don't necessarily align with PGSync's schema output.
We need a way to define a custom Elasticsearch mappings without referencing columns.

I have added support for this in the master branch. Please give it a try. Here is a schema example

@toluaina That's exciting! I will give it a shot 👍🏻

@toluaina Unfortunately, this does not seem to work for me. I added the following field:
[
  {
    ...
    "mappings": {
      "properties": {
        "name": {
          "type": "text",
          "fields": {
            "raw": {
              "type": "keyword",
              "ignore_above": 256
            }
          }
        }
      }
    }
  }
]

I receive the following error:
elasticsearch.BadRequestError: BadRequestError(400, 'mapper_parsing_exception', 'Root mapping definition has unsupported parameters:  [index : {properties={collection={type=text, fields={raw={ignore_above=256, type=keyword}}}}}]')


Is there a user dashboard?

Great work, love the design and the public spec; main immediate question: is there an endpoint for a logged-in user to get the API keys they've already signed up for?

Nope, but if you just request a new key you'll get your old key anyway.


CODEC-236: MurmurHash2 and MurmurHash3 implementations.

All MurmurHash implementations are public domain.
Credit was given in Javadoc where both implementations came from.

Coverage decreased (-1.06%) to 91.327% when pulling 6d2b19a7aa854aed46a30f1f3927cbdbc6110c0c on melloware:CODEC-236 into 45a195e0776e2dfb85022f034aec3af191cf7dca on apache:master.

Hm, XXHash32 and others implements java.util.zip.Checksum. Other classes in org.apache.commons.codec.digest do not implement Codec interfaces where some could, like UnixCrypt. Food for thought. But for the new code in this PR, the fit with the Codec interfaces might not be best.
The Travid build (https://travis-ci.org/apache/commons-codec/jobs/556975625) reveals that the Javadoc for the new code is incomplete:
[ERROR] /home/travis/build/apache/commons-codec/src/main/java/org/apache/commons/codec/digest/MurmurHash3.java:84: warning: no @param for l0
[ERROR] 	public static int hash32(long l0, int seed) {
[ERROR] 	                  ^
[ERROR] /home/travis/build/apache/commons-codec/src/main/java/org/apache/commons/codec/digest/MurmurHash3.java:84: warning: no @param for seed
[ERROR] 	public static int hash32(long l0, int seed) {
[ERROR] 	                  ^
[ERROR] /home/travis/build/apache/commons-codec/src/main/java/org/apache/commons/codec/digest/MurmurHash3.java:84: warning: no @return
[ERROR] 	public static int hash32(long l0, int seed) {
[ERROR] 	                  ^
[ERROR] /home/travis/build/apache/commons-codec/src/main/java/org/apache/commons/codec/digest/MurmurHash3.java:97: warning: no @param for l0
[ERROR] 	public static int hash32(long l0, long l1, int seed) {
[ERROR] 	                  ^
[ERROR] /home/travis/build/apache/commons-codec/src/main/java/org/apache/commons/codec/digest/MurmurHash3.java:97: warning: no @param for l1
[ERROR] 	public static int hash32(long l0, long l1, int seed) {
[ERROR] 	                  ^
[ERROR] /home/travis/build/apache/commons-codec/src/main/java/org/apache/commons/codec/digest/MurmurHash3.java:97: warning: no @param for seed
[ERROR] 	public static int hash32(long l0, long l1, int seed) {
[ERROR] 	                  ^
[ERROR] /home/travis/build/apache/commons-codec/src/main/java/org/apache/commons/codec/digest/MurmurHash3.java:97: warning: no @return
[ERROR] 	public static int hash32(long l0, long l1, int seed) {
[ERROR] 	                  ^
[ERROR] /home/travis/build/apache/commons-codec/src/main/java/org/apache/commons/codec/digest/MurmurHash3.java:275: warning: no @param for offset
[ERROR] 	public static long hash64(byte[] data, int offset, int length, int seed) {
[ERROR] 	                   ^

It would be best if you could address this as well as the decrease in code coverage.

@garydgregory Thanks for all your feedback.  I went back and Javadoc'ed every method and param.  I also was able to get Coveralls unit test coverage up 0.4%!   When I grabbed the unit tests from Hive it looks like it had incomplete tests for 128 hashing so I created those tests.

One more comment: Did you consider providing a MurmurHash1 implementation?

I did consider MurmurHash1 but from what i can tell it was more of a prototype that led to the creation of Murmur2.  From Wikipedia about Murmur1:

"The original MurmurHash was created as an attempt to make a faster function than Lookup3. Although successful, it hadn't been tested thoroughly and wasn't capable of providing 64-bit hashes as in Lookup3. It had a rather elegant design, that would be later built upon in MurmurHash2, combining a multiplicative hash (similar to Fowler–Noll–Vo hash function) with a Xorshift."


feat(xquery): default xquery-version=3.1

I's been always unclear which version of XQuery we can use in the compiled query.
Following #905, this pull request defines the default /x:description/@xquery-version = 3.1.
Further work
Update Wiki to require XQuery 3.1 processors.

Further work
Update Wiki to require XQuery 3.1 processors.

Done.


Demonstrate the best practice of performing registration

The changes in this PR demonstrate the best practice of how an application should perform registration in order to subscribe for incoming call push notifications.

Move PkPushRegistry instance initialization and PkPushRegistryDelegate methods to AppDelegate. This ensures that PushKit is set up each time the app is launched and push notifications can be received by the application.

Events of the PkPushRegistryDelegate protocol will be sent to the view-controller via the PushKitEventDelegate protocol. This could be implemented in the best place based on the app logic.

Upon receiving the didUpdatePushCredentials: callback, the app can use the cached device token that was saved in a previous successful registration and only call TwilioVoice.register() only when the device token has been updated.

Hi @bchen-twilio,
nice work with this PR.
I am updating the React-Native library to work with the Twilio Voice SDK 5.2.0 (https://github.com/hoxfon/react-native-twilio-programmable-voice/pull/144)
I was wondering if these changes would apply to a library where there is no AppDelegate.m and AppDelegate.h, given that they live in the app folder of the library user.
Thanks

Hi @fabriziomoscon
Thanks for the great questions.
The idea of this PR is basically to ensure that the PushKit instance is always initialized when the app is launched and the kept alive when necessary, typically the same lifecycle of the app unless session based logic is desired. I am not an expert of using the RN library but I would imagine there is a place to achieve this.
Cheers,
-bobie


How to get keypoints output .json file like original OpenPose ?

Sorry I don't understand the question

I meant the output of the original OpenPose is a json file with 2d keypoints which look something like this:
{   "version": 1.3,   "people": [     {       "person_id": [         -1       ],       "pose_keypoints_2d": [         535.734,         246.827,         0.855832,         ....       ],       "face_keypoints_2d": [         496.62,         230.471,         0.699601,         ...       ],       "hand_left_keypoints_2d": [         751.966,         512.104,         0.542437,         ...       ],       "hand_right_keypoints_2d": [         266.106,         510.039,         0.540713,         ....       ],       "pose_keypoints_3d": [],       "face_keypoints_3d": [],       "hand_left_keypoints_3d": [],       "hand_right_keypoints_3d": []     }   ] }
Can I get these values from controlnet_aux ?

This functionality is in the A1111 implementation, e.g. see https://github.com/Mikubill/sd-webui-controlnet/blob/main/annotator/openpose/init.py#L122

So if I pass the poses from https://github.com/patrickvonplaten/controlnet_aux/blob/master/src/controlnet_aux/open_pose/init.py#L220
to that function, I should be able to get the json right ?

There's a good chance that the openpose implementations have diverged.  I last updated all of them on 5/27 so it's worth a pass to review.

yeah latest openpose has 7 additinal joints. The pelvis + 2 toes and ankle for both feet. Anyways those didn't matter to me. I approximated the position of pelvis with hip joints and mapped the toes and ankle to feet.


Need to add an option in Settings to allow to use entire screen width for chat messages and message box

We need to add an option in Settings to allow to use entire screen width for chat messages and message box. By default the option should be off. Please find the design here (the link is available for DIAL dev team only): https://www.figma.com/file/lwL5jneveZczAj5RLcLFH2/DIAL-Chat?type=design&node-id=1479-6708&mode=design&t=bvYoJf5FCesvhuAZ-4

Comment from user (246 internal ticket): Please consider increase the conversation width, it currently only occupy less than 50% approx. of the visible area width. This drawback becomes quite outstanding when the conversation include table format content, when each column becomes very narrow, it's difficult to read.

Please take care of #143 #144
Can we fix them at the same time?

@denys-kolomiitsev return the feature:

The width of the conversation name container depends on the conversation name length. Now default renaming after the first message cuts name at 160th character.

If manualy rename conversation it will widen to full width.

TBD: should we increase characters number of the default conversation name.

Verified on staging successfully


Add NGL.Stage.loadData method

Currently you can only load data via .loadFile. It would be useful if you can load a data String using a method such as .loadData.

Wait, I just found you can pass a Blob to path in .loadFile. Perhaps it would be nice to have a more explicit method for that. Sorry.

Wait, I just found you can pass a Blob to path in .loadFile. Perhaps it would be nice to have a more explicit method for that.

Maybe, I don't want to clutter the API with so many methods. A Blob is very similar to a File I would say.

I agree that loadFile is sufficient. API should be simple and easy to remember.

my plan is to document how to load string data

added examples to new api docs 3c7ecad1522979458bf459495aa7ea6d2704c4ce


Autoplay + muted does not autoplay the video on chrome

I've got a warning message in the console:
plyr.js:619 Unmuting failed and the element was paused instead because the user didn't interact with the document before.

the regular version (hml5), works

js:
const player = new Plyr('#player', {
muted: true
});
here is the codepen:
https://codepen.io/romaingranai/pen/WNpRxEE
Everything seems to work just fine on firefox and safari! Any clue, are you able to redirect me on another issue if it has already posted and fixed?

Different browsers have different policies for muting. Chrome even has a scoring system to allow autoplay. The error message you're seeing is the browser telling you that the user hasn't interacted with the video so it's unwilling to change the state of it.

@JayGeorge  is there any workaround for this?

You can't unmute a video automatically. You should be able to mute + autoplay though. I recommend you test this in Chrome in a new private/incognito window every time otherwise you may see inconsistent results due to their scoring system mentioned above.
A separate issue is with Vimeo by the way, just in case you're running into that—for which there's a solution here

I've also been having issues with Autoplaying + muted.
Chrome's autoplay policy says "Muted autoplay is always allowed" and it works fine when I use the native video player instead of loading Plyr. So it seemed like Plyr was doing something that makes the video appear as unmuted and triggers the MEI evaluation.
When I outputted the values of my options immediately after loading, I found they do not all seem to be picked up:
const player = new Plyr('video', {
  autoplay: true,
  muted: true,
  volume: 0
});
console.log(player.autoplay); // true
console.log(player.muted);    // false
console.log(player.volume);   // 1

So I tried setting them after initialisation and explicitly calling play() and this works for me:
const player = new Plyr('video', {
  // whatever
});
player.muted = true;
player.volume = 0;
console.log(player.muted);    // true
console.log(player.volume);   // 0
player.play();                // the video starts playing


Fixed Incorrect Tuple Usage in unpackData

Fixed "IndexError: tuple index out of range"
value = tuple(float(value[i]) / divisor for i in value)
Was effectively attempting to access the value tuple using an element as an index.
value = tuple(float(i) / divisor for i in value)
Uses the elements from the tuple and modifies them.
Ex: (0,0,0,255) becomes: (0.0, 0.0, 0.0, 255.0)
Instead of throwing an error.

Description

Thanks for catching this!


Infrataster doesn't work with ports other than 80

Dockerspec Version
0.4.1
Ruby Version
ruby 2.4.0p0
Platform Details
Mac
Scenario
Testing a docker container exposing port 9000 with Infrataster.
Steps to Reproduce
    describe server(described_container) do

      describe http('/healthcheck') do
        it 'responds with works' do
          expect(response.body).to include 'WORKS'
        end
      end

    end

Expected Result
Serverspec on tag: "sha256:21afedc21ede0f4fb2e6416d83cf2f70b60e3fa3a6c275e1ec53a8f4f78e4e81"
    server '/sleepy_bose'
      http 'http://<IP_ADDRESS>:9000/healthcheck' with {:params=>{}, :method=>:get, :headers=>{}}

Actual Result
Serverspec on tag: "sha256:21afedc21ede0f4fb2e6416d83cf2f70b60e3fa3a6c275e1ec53a8f4f78e4e81"
    server '/sleepy_bose'
      http 'http:/healthcheck' with {:params=>{}, :method=>:get, :headers=>{}}

Hi @estahn,
Try passing the complete URL to the http resource:
    describe server(described_container) do

      describe http('http://localhost:9000/healthcheck') do
        it 'responds with works' do
          expect(response.body).to include 'WORKS'
        end
      end

    end

That should work in theory. Let me know if not.

It doesn't because the port is not mapped. dockerspec will need to look for
a random available port and map the exposed container port. Then specify it
in the server resource.
Also I'd like to avoid specifying the entire URL otherwise dockerspec
becomes useless in this case.
Note: I currently use Infrataster without dockerspec and it works. I'm
trying to integrate it in the context of dockerspec.
On Sat., 1 Apr. 2017, 7:26 am Xabier de Zuazo<EMAIL_ADDRESS>wrote:

Hi @estahn https://github.com/estahn,
Try passing the complete URL to the http resource:
describe server(described_container) do

  describe http('http://localhost:9000/healthcheck') do
    it 'responds with works' do
      expect(response.body).to include 'WORKS'
    end
  end

end

That should work in theory. Let me know if not.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zuazo/dockerspec/issues/5#issuecomment-290896675, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAWGvr_Pma3TqhDtghD10MiKSOTnZffeks5rreALgaJpZM4MwG1y
.

Sorry @estahn, I misunderstood the issue.
Please, could you give me an example of Dockerfile/docker-compose.yml to reproduce the problem?

@zuazo No worries. I don't use docker-compose, but i might start with it for my test cases.
The _spec files looks like this:
require 'dockerspec/infrataster'

describe 'thumbor' do
  before :all do
    image = Docker::Image.get(ENV['DOCKER_IMAGE'])

    set :os, family: :alpine
    set :backend, :docker
    set :docker_image, image.id
  end

  describe docker_run(tag: Docker::Image.get(ENV['DOCKER_IMAGE']).id) do
    describe server(described_container) do
      describe http("/healthcheck") do
        it 'responds with works' do
          expect(response.body).to include 'WORKS'
        end
      end

    end
  end

end

Call:
DOCKER_IMAGE=hipages/thumbor:6.3 bundle exec rspec

The docker image needs to be pulled before, but is currently not publicly available. You can use zanui/thumbor instead.
There is another issue which is kinda related to the port problem. It's not possible to access container via IP and port directly on Mac.
The current workaround i'm testing is from my old infrataster tests:
set :docker_container_create_options, {
  "AttachStdout" => true,
  "AttachStderr" => true,
  "PortBindings" => { "9000/tcp" => [{ "HostIp" => "<IP_ADDRESS>", "HostPort" => "9000" }]}
}

Basically exposing the port the host system like you suggested.
Any better idea would be appreciated.

I got it working with some ugly workaround.
require 'dockerspec/infrataster'

Infrataster::Server.define('app', '<IP_ADDRESS>')
set :docker_container_create_options, {
  "PortBindings" => { "9000/tcp" => [{ "HostIp" => "<IP_ADDRESS>", "HostPort" => "9000" }]}
}

describe 'thumbor' do
  before :all do
    image = Docker::Image.get(ENV['DOCKER_IMAGE'])

    set :os, family: :alpine
    set :backend, :docker
    set :docker_image, image.id
  end

  describe docker_run(tag: Docker::Image.get(ENV['DOCKER_IMAGE']).id, wait: 1) do
    describe server('app') do
      describe http("http://app:9000/healthcheck") do
        it "responds content including 'WORKING'" do
          expect(response.body).to include('WORKING')
        end
      end
    end
  end
end


fix: checkboxItem and radioItem closing on click

Isn't the expected behavior that they close on click? Even menus within VSCode or the browsers that are checkbox/radio close on click.
Maybe an option to disable it but I don't think disabling it altogether is a good idea.

Isn't the expected behavior that they close on click? Even menus within VSCode or the browsers that are checkbox/radio close on click.
Maybe an option to disable it but I don't think disabling it altogether is a good idea.

Yeah, maybe you're right. I was looking at a lib that had it like this and thought it was a good idea! But now I'm thinking otherwise...
With controlled usage from #234 , this probably won't be needed. Will close it

That was my thought as well - controlled would make this possible for specific use cases! I do see it being nice in certain situations, specifically, if it's like a filter menu for a table or something, I think it'd be annoying to close each time but then other times I would want it to close (selecting a color theme or something like that)!


libmdbx not found.

The repo https://github.com/erthink/libmdbx/tree/d5e4c198d8ab8319041d41ce7c6d44b8c7e7c876 is not found.

This is due to recent removal of libmdbx from Github.
We've updated the repository by #633
Please pull the repo again and retry your build.


Added SPS visibility helpers / bbox, frustum, toussa

Added :

SPS.refreshVisibleSize() : just refreshes the SPS underlying mesh bounding info
SPS.forceVisibility() : sets the SPS underlying mesh as always selectable as active

As the SPS may have a variable mesh size, its bounding box may not be updated when needed so the full SPS can disappear from screen because its BBox is no longer in the frustum.
These two helpers will allow the user to update the SPS BBox on demand.
This will be documented

Please don't merge now, I will change some little things tomorrow

changes done
documented

Can I merge ?

yes, you can !
Le 05/11/2015 16:21, Temechon a écrit :

Can I merge ?
—
Reply to this email directly or view it on GitHub
https://github.com/BabylonJS/Babylon.js/pull/805#issuecomment-154091527.

last important commit coming !
travis is sick again ...

you can really merge now ;-)


autocompletion is slow and stuck

autocompletion takes too much time on moba-xterm and stucks my cli
any tips on what to do in that case?
takes at least 5 seconds for each completion

Thanks for your interest in argcomplete. Based on the information you provided, this does not seem like an issue with argcomplete, so I'm going to close it for now.
You may want to read the documentation for this project about what to do in a situation that you encountered, or provide a complete reproduction test case.

Im sorry I didn't noticed it.
Thank you for the reply!


Add SPDR space

Created a space via ENS.

There is a conflict in your PR, can you resolve it?

There is a conflict in your PR, can you resolve it?

Resolved.

@gokaiorg Please check.


auth: add oauth2 provider module

Hey, I just made a Pull Request!
This migrates the oauth2 provider to be a separate module
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Hi @Rugvip, so this has pretty much everything from the current oauth2 provider, did run into some config that wasn't in the config.d.ts file so I made sure to include that in this version. Also, there's one outstanding item: the current provider has a disableRefresh option and I'm not sure how to implement that in this module. Here's the current code: https://github.com/backstage/backstage/blob/535f5fd6ce466baf29f2c3a3c2d06b9c9c80dca3/plugins/auth-backend/src/providers/oauth2/provider.ts#L139.
Finally, the current provider has a test that it actually triggers the auth and checks the result, should I try and replicate that?

Thanks @Rugvip 🚀


chore: bump importGraph

Update importGraph to use reservoir dependencies instead of git-dependencies.
See importGraph commit 7376ac0

According to bug report on Zulip.

Thanks :tada:
bors merge


topomerge can't deduplicate geometries

I expected topomerge to be able to deduplicate geometries but it didn't work:
topomerge -k 'd.id' < foo.json

Geometries come out like this:
{"type":"MultiPolygon","arcs":[[]],"id":"1"}
// etc.

As a workaround I used ndjson-reduce 'p[d.id] = d, p' '{}' | ndjson-split 'Object.values(d)' on the GeoJSON features first.

Right—that’s not how topojson.merge (topomerge) works. It expects the input to be topologically-consistent and non-overlapping. Could probably be documented better, though.

I might have been having a different issue, but it sounds similar it's quite nuanced describing the differences. I had two shapefiles which shared a border, but when I merged them into the same topojson file the borders didn't match up despite them being very similar. The fix was that I was doing the quantization after conversion to topojson, when you need to do at the point you load both files. I hope this is correct and helpful to other people.
geo2topo -q 1e5 -n nuts=raw/ndjson/nuts.ndjson


Next version API

Replace the t function usage with direct method calls.

Pull Request Test Coverage Report for Build 32

37 of 37 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 20:
0.0%

Covered Lines:
76

Relevant Lines:
76

💛  - Coveralls


Fix menu font color

Font in the menu is probably too low contrast to be accessible.

This is before the Australian update, so it was for everywhere. I would fire it up and have Jill look at it. She'll know what needs to be changed.


Whitespace Between CJK & Latin Not Working Before Line Break

Description
The feature was added in https://github.com/typst/typst/pull/2334. Normally, it works as intended:

// src
Typst是一个排版系统

However, when there is a line break (#linebreak() or \), any CJK text immediately before is not spaced. Lines ending with Latin letters are not affected by this glitch:

// src
我们能利用Typst做很多事情 \
如plot一些图表 #linebreak()
和管理citation #linebreak()
并produce许多精美的document \

Thanks for the attention.
Reproduction URL
No response
Operating system
Web app, macOS
Typst version

[ ] I am using the latest version of Typst

minimal reproduction:
plot一些图表 #linebreak()

The space is gone after line_break in L169

The glyph before linebreaking is reshaped in https://github.com/typst/typst/blob/c177a63c9b8b5e57a6ce10f454e809b5474a354b/crates/typst-library/src/layout/par.rs#L1152 and later assigned https://github.com/typst/typst/blob/c177a63c9b8b5e57a6ce10f454e809b5474a354b/crates/typst-library/src/layout/par.rs#L1182 .
When it is reshaped, the x_advance and x_offset is not preserved. So the spacing between latin and cjk is lost.
It enters this branch because start + shaped.text.len() > range.end == true

currently have no idea whether it is desired behavior or not. cc @peng1999 for help :pray:

Is the problem essentially this https://github.com/typst/typst/pull/2334#issuecomment-1754801378 even though it shouldn't happen according to this https://github.com/typst/typst/pull/2334#issuecomment-1755029885?

When it is reshaped, the x_advance and x_offset is not preserved.

The reshape does not make sense. I think find_safe_to_break needs to be fixed.
In this part of function:
https://github.com/typst/typst/blob/0f274f8edbbb93d65cb11713f4bdf912b3286800/crates/typst-library/src/text/shaping.rs#L482-L501
When the shaped text contains "字\n" (len = 5), and we want to slice the first character "字" (range 0..4), the function fails to handle this situation because

range.end != 5, and
\n produces no glyph, so there is no glyph that starts at index 4.


Process exits on Real-time signals

Hello! First, thanks for i3blocks-mpris, it is pretty cool!
I have come across a bug that I was unable to figure out. My volume blockets rely on real time signals to get "manually" notified on volume changes (via pkill -RTMIN+10 i3blocks). This is rather common in i3blocks and is explicitely supported.
The bug I came across is that sending any SIGRTMIN+N causes i3blocks-mpris to exit without any error message, the only trace in standard error is the message Real-time signal N, and the exit code is always of the form162+N, where N is the same as in SIGRTMIN+N.
I tried to debug as far as I could but my knowledge on dbus is close to zero.

Hello, is is an expected behavior:
SIGNAL(7)
...
The default action for an unhandled real-time signal is to terminate the receiving process.

pkill -RTMIN+10 i3blocks — this sends the signal to all processes whose process names contain i3blocks substring (icnluding i3blocks-mpis). What you really want is pkill -x -RTMIN+10 i3blocks-volume-block (given your volume blocket is named i3-blocks-volume-block):
PGREP(1)
...
       -x, --exact
              Only match processes whose names (or command lines if -f is specified) exactly match the pattern.

$ pgrep -l i3blocks
2234 i3blocks
2264 i3blocks-mpris

$ pgrep -l -x i3blocks
2234 i3blocks

See https://github.com/un-def/i3blocks-mpris/issues/5

You are right on point!
Thanks for the small lesson on linux's signal handling :+1:
Closing issue!


build(deps): bump embassy, esp-hal, rtt-target, bare-metal

Description

Bumping to current main branches.
Issues/PRs references

Open Questions

Change checklist

[x] I have cleaned up my commit history and squashed fixup commits.
[x] I have followed the Coding Conventions.
[x] I have performed a self-review of my own code.
[x] I have made corresponding changes to the documentation.

Seems like this breaks esp wifi, investigating ...

Wifi works with defmt debug output enabled :confused:

Offline discussiion: we'll merge this now despite my Wifi regression, I'll open an issue for that.


⚠ Guya.moe Proxied has degraded performance

In 2437ec2, Guya.moe Proxied (https://ice.guya.moe/) experienced degraded performance:

HTTP code: 200
Response time: 11951 ms

Resolved: Guya.moe Proxied performance has improved in 0943a00 after 10 minutes.


Each night the integration disconnect and ask for re-auth

My alexa based automations stopped working almost each night, sometimes even after a HA reboot. It asks for re auth.

Home-assistant (version): last one
alexa_media (version from const.py or HA startup): last one
alexapy (version from pip show alexapy or HA startup): last one
Amazon 2FA is enabled (y/n). <!---We will not debug login issues if unanswered--->: No

I have the same problem with 2FA.
When i try to configure again, it says "Invalid 2-factor key".

Had same problem, but followed directions here and no longer having issue.

No matter what I do, it's not longer working for me with 4.7.7

OMG. I enabled debugging and it said
[alexapy.alexalogin] Not logged in due to email mismatch to stored h************p@g*******m
[alexapy.alexalogin] Resetting Login for h************p@g*******m  - amazon.de
Recognize the two spaces in front of the dash! Doing copy & paste of the email it added a space after the email address.
After removing the space the logon started working again. PHEW.


can't auth to prod via local.headers: verdaccio.local to verdaccio.prod to npm

ISSUE
When I try to install a package that verdi.local can't find it when it asks verdi.prod . verdi.prod responds with:
0|wps-npm  |  http <-- 403, user: undefined($homeip), req: 'GET /base64', error: unregistered users are not allowed to access package base64

I thought having the headers, Authorization in my verdi.local would fix this?
.NPMRC CONFIG
<EMAIL_ADDRESS>always-auth=true
registry=http://localhost:4873/
//$prod/:_authToken="LX4oULtJAAQt4WaqZiXzO/gRMU68WbY5OBwoMqC2cQ="

VERDACCIO SETUP
verdi.local --> verdi.prod --> npm.official
I don't just use @scoped packages, I also use pre-releases of packages like prettier 1.6.0 (which comes with --config option, that 1.5.x doesn't)
My circleci server is configured to use verdi.prod
I especially love using verdi.local for offline development
verdi.local
uplinks:
  prod:
    url: http://$prod:4873/
    headers:
       Authorization: "Basic LX4oULtJAAQt4WaqZiXzO/gRMU68WbY5OBwoMqC2cQ="

I'm using the token from ~/.npmrc that is received from verdi.prod by doing
npm adduser --registry  http://$prod:4873
verdi.prod
storage: ./storage

listen: <IP_ADDRESS>:4873

auth:
  htpasswd:
    file: ./htpasswd
    max_users: -1

uplinks:
  npmjs:
    url: https://registry.npmjs.org/

packages:
  '@*/*':
    # scoped packages
    access: $authenticated
    publish: $authenticated
    proxy: npmjs

  '**':
    access: $authenticated
    publish: $authenticated
    proxy: npmjs

Follow up of https://gitter.im/verdaccio/questions?at=599dacb2a7b406262dbc6762

@Falieson according to my test your set up has an issue
uplinks:
  prod:
    url: http://<IP_ADDRESS>:4873/
    headers:
      authorization: Bearer 5WXoet5VYxOnUwv8aADlPA==

If you go deaper into npm/pacote they don't use Basic, they use Bearer as authorization prefix header. It works for me, try and let me know whether works or not.

THANK YOU! That fixed it!


ci: Updated source for conventional-pr-title-action

Description
This pull request changes the following:

Update source of conventional-pr-title-action to use step-security maintained version

Related Issues

Closes #863

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


Switching between change detection variables the UI not updating to current Model name.

Describe the bug
Switching between variables reveals the UI is not updating correctly.
Still displays "Fixed Threshold" when the Condition is now "Relative difference of means (1)"

To Reproduce
Create multiple change detection variables. each with different implementations.
switch between variables.
Version
What is the version of Horreum ?
If you are using a development branch; what is the commit id ?
0.13.0

@whitingjr is this a duplicate of: https://github.com/Hyperfoil/Horreum/issues/1123 ?

yes duplicate


publish<EMAIL_ADDRESS>

Requested by: @markstory
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Targets

[ ] pypi
[ ] github

I feel like that typing improvement may deserve a minor bump but we are sub 1.0 anyway so let's roll 🙂


Connection to services arriving OVN clusters don't work.

If the destination cluster is running OVN Kubernetes, and a service is being contacted, it fails.
What happened:

Packet arrives the gateway
Packet is forwarded to the submariner router on 169.254.x.7

The packet doesn't arrive to destination.
Load balancers are implemented as logical-switch load balancers on every host, where the pods are connected,
and not on the routers, so we need to figure out how to trigger them.
i.ex:
[majopela@bluehat subm-demo]$ ovn_nbctl ls-lb-list ip-10-0-151-109.us-east-2.compute.internal
UUID                                    LB                  PROTO      VIP                     IPs
d532d66d-0090-4b00-a4ec-73662f87192c                        udp        <IP_ADDRESS>:53          <IP_ADDRESS>:5353,<IP_ADDRESS>:5353,<IP_ADDRESS>:5353,<IP_ADDRESS>:5353,<IP_ADDRESS>:5353,<IP_ADDRESS>:5353
                                                            udp        <IP_ADDRESS>:53       <IP_ADDRESS>:53,<IP_ADDRESS>:53
fd498951-60ff-4b4f-a3c0-5550bbf49d14                        tcp        <IP_ADDRESS>:53          <IP_ADDRESS>:5353,<IP_ADDRESS>:5353,<IP_ADDRESS>:5353,<IP_ADDRESS>:5353,<IP_ADDRESS>:5353,<IP_ADDRESS>:5353
                                                            tcp        <IP_ADDRESS>:9154        <IP_ADDRESS>:9154,<IP_ADDRESS>:9154,<IP_ADDRESS>:9154,<IP_ADDRESS>:9154,<IP_ADDRESS>:9154,<IP_ADDRESS>:9154
                                                            tcp        <IP_ADDRESS>:443          <IP_ADDRESS>:6443,<IP_ADDRESS>:6443,<IP_ADDRESS>:6443
                                                            tcp        <IP_ADDRESS>:443      <IP_ADDRESS>:8443
                                                            tcp        <IP_ADDRESS>:443      <IP_ADDRESS>:6443,<IP_ADDRESS>:6443
                                                            tcp        <IP_ADDRESS>:443       <IP_ADDRESS>:6443,<IP_ADDRESS>:6443,<IP_ADDRESS>:6443
                                                            tcp        <IP_ADDRESS>:8443      <IP_ADDRESS>:8443,<IP_ADDRESS>:8443,<IP_ADDRESS>:8443
                                                            tcp        <IP_ADDRESS>:443        <IP_ADDRESS>:8443
                                                            tcp        <IP_ADDRESS>:8080     <IP_ADDRESS>:8080
                                                            tcp        <IP_ADDRESS>:443      <IP_ADDRESS>:6443,<IP_ADDRESS>:6443,<IP_ADDRESS>:6443
                                                            tcp        <IP_ADDRESS>:443        <IP_ADDRESS>:8443

What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Submariner version (use subctl version):
Kubernetes version (use kubectl version):
Cloud provider or hardware configuration:
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Network plugin and version (if this is a network-related bug):
Others:

This can be solved by attaching the ovn-kubernetes loadbalancers from the internal switches into the submariner_router too:
From a row in the Logical_Switch table, see "load_balancer":
_uuid               : 452e863c-f345-48df-9a84-5830bfede2b3
acls                : [4fe946c5-47a4-44f2-bd3a-6fe53be05ed2]
dns_records         : []
external_ids        : {}
forwarding_groups   : []
load_balancer       : [0620c995-8d4d-4956-aa31-4056340fc5d1, d532d66d-0090-4b00-a4ec-73662f87192c, fd498951-60ff-4b4f-a3c0-5550bbf49d14]
name                : ip-10-0-185-211.us-east-2.compute.internal
other_config        : {subnet="<IP_ADDRESS>/23"}

We should keep that entry in sync with the submariner_router:
 ovn-nbctl set Logical_Router d076dc7c-3d99-4ac5-9b3d-d6eb11615fdf 'load_balancer=[0620c995-8d4d-4956-aa31-4056340fc5d1, d532d66d-0090-4b00-a4ec-73662f87192c, fd498951-60ff-4b4f-a3c0-5550bbf49d14]'


Feat: Adjusting Sidebar Size for Improved Accessibility on Small Devices

Describe the feature
The feature involves adjusting the size or height of the sidebar on our website to ensure that all sections are adequately displayed, especially on small devices. Currently, the sidebar is too short to contain all options, leading to certain sections being inaccessible or hidden on smaller screens. By resizing the sidebar, we aim to improve accessibility and usability for users browsing the website on mobile devices or smaller screens.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Assigned!

Make sure to star the repo before working on it! Happy open-source contributing!


Skip auto-installing when the root package's extra.discovery is enough

Here is an idea that popped up in #236 and that builds on #232.
When the root package configures this:
    "extra": {
        "discovery": {
            "psr/http-factory-implementation": "My\\Psr17Factory"
        }
    }

then we shouldn't need auto-installing any extra packages for this virtual package.
Same when listing individual interfaces:
    "extra": {
        "discovery": {
            "Psr\\Http\\Client\\ClientInterface": "My\\Psr18Client"
        }
    }

In this case, we should verify that all the interfaces required to fulfill one of the supported *-implementation are listed.

thanks for the discussion in #236 . a workaround for now would be to do the composer config allow-plugins.php-http/discovery false from the readme, correct? and have the internal package provide the required *-implemenation information for composer.
I agree we can't check just for the *-implementation of installed packages because that still does not tell which classes to use. and scanning the code for implementing interfaces is too fragile (and a performance problem when no caching mechanism is available). while afaik java does support this sort of self-registration and autodiscovery mechanisms, i agree with not going that far.
the change suggested here would be that the existing configuration to chose which class to use for which psr factory also accepts unknown classes in addition to the well-known ones, right? that seems consistent with what we have and non-surprising.
(btw there is some doc that is only in the readme but missing from https://docs.php-http.org/en/latest/discovery.html, we should sync the 2 places when we do this change)

composer config allow-plugins.php-http/discovery false

correct!

the existing configuration to chose which class to use for which psr factory also accepts unknown classes in addition to the well-known ones

This works already!
The only thing missing is skipping the installation of well-know packages when all interfaces of the virtual package are listed.

oh even better. yeah then its not much left to be done :+1:
and i just realized that you just added the pinning recently. neat, thanks!


Release cognitiveservices language 2022 05 01 GA

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

This branch is not ready to merge yet - there are other changes coming. You also need to resolve the conflicts. Just copy any non-2022-05-01 files directly from main to make it easy. One easy way is to create a topic branch against your feature branch, checkout main's version of the 2022-03-01-preview files, commit, and submit a PR to the release branch here.
Once that branch is updated, this PR should be updated automatically.
# assumes Azure/azure-rest-api-specs is your upstream remote
git fetch upstream release-cognitiveservices-Language-2022-05-01-GA
git checkout -b update-2022-03-01-preview upstream/release-cognitiveservices-Language-2022-05-01-GA -- specification/cognitiveservices/data-plane/Language/preview/2022-03-01-preview
git commit -am'Update 2022-03-01-preview files'
# now submit a PR to release-cognitiveservices-Language-2022-05-01-GA

@nourhaanfarid can you resolve the merge conflicts so we're closer to merging this?

Closed in favor of https://github.com/Azure/azure-rest-api-specs/pull/19191 since I had to rebase and can't force push.


Support other increments of size

Currently the size is always doubled, but for exponential or factorial algorithms it would be better to increment size by 1. For most flexibility, the functions would allow to increment by a fixed amount and/or by a factor. Arguments could be:

start value/size
steps number of doublings or additions, must be ≥ 0
factor: a float ≥ 1, default 2
increment: an int ≥ 0, default 0

The function then measures run-times for start, start*factor+increment, etc. for as many steps as given. (steps = 0 means it does only for start)

[ ] update library (should check that factor > 1 or increment > 0, as otherwise size doesn't grow)
[ ] update code guide
[ ] update/add an example in an essay (maybe a student essay)
[ ] update template

I've made a start on this and pushed a 39-support-other-increments branch.
So far I have:
- modified the library including code, docstrings and assertions.
- modified the example and template essays by changing the double parameter to steps
I won't tick any of the boxes until I have had another look tomorrow and will continue working on it.


Add wiki

How do I train and test?

I'm working on a thorough walkthrough that should be ready in a few days.
You can view the draft here:
https://medium.com/p/c8c86419225e/edit


[cleanup][1/x] make hp_tensor_to_float8_dynamic only work with hp inputs

Summary:
hp_tensor_to_float8_dynamic should only work with high precision
inputs, logic which checks for the input being already in float8 up
to the callsites to make it more explicit and easier to follow.
Test Plan: CI
Reviewers:
Subscribers:
Tasks:
Tags:

Stack from ghstack (oldest at bottom):

-> #1458


Image resizer source code

Hello. The repo contains binary files for an image resizer tool. Is the source code for it available?

No, source code for this tool is unavailable.


remove once package

https://github.com/facebook/jest/pull/3594

Codecov Report

Merging #3867 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master    #3867   +/-   ##
=======================================
  Coverage   57.58%   57.58%
=======================================
  Files         195      195
  Lines        6792     6792
  Branches        6        6
=======================================
  Hits         3911     3911
  Misses       2878     2878
  Partials        3        3

Impacted Files
Coverage Δ

packages/jest-jasmine2/src/queueRunner.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Update RTD to Target Correct GH Release Branch

Signed-off-by: Brett Logan<EMAIL_ADDRESS>

fwiw (and I'm pretty sure you know this) - there are still links that use hard coded branch references in the release-2.2 doc.

@sykesm Once the community PR get's in I am going to go through master and catch any that we missed in addition to the ones being corrected in that PR and then I'll correct it through 2.2.


add auto labeling

Users can upload their model to the bucket (or if they stored the the training output to their bucket) The client will give the user an auto label button that will use the model to detect objects in the selected photo.
pressing the autolabel button should prompt the user with the new labels highlighted allowing them to confirm or reject the propositions.
Possibly have an option to autolabel the entire dataset at once with a specified confidence?
I'm thinking almost a find and replace UI. i.e.
keep tapping enter to confirm or skip labels in an image, then move onto the next image
or press the confirm all in image or confirm all in dataset button

+1
Can it be possible to prioritize this enhancement.
This is one of the most useful feature for everyone. And IBM Watson started with auto labelling but their labelling process is very very slow.

I can try my best, shouldn't be too hard 😬

Hi @bourdakos1 ,
Could you please mention expected time for this feature.

I wouldn’t expect it any sooner than the end of December. If you have any experience with react, I’m welcome to outside help

Originally I was going to load models from object storage, but after looking at the tensorflow.js docs I think we also have other options.
The user could upload models directly to the tool and be persisted to localstorage/indexeddb. The drawback would be that you would only be able to use the model on the browser that you uploaded the model to. The perk would be that you could easily use any model with any bucket

Here's mock ups of what auto label will most likely look like

Second option looks more prominent as user can outside model to auto-label.
I do not have experience in React but will try locally. If got any success will raise a pull request for your review.

loading the model seems to block the UI so I will load it after clicking auto label

✅Auto label UI is pretty much done
✅I'm able to load the model from the object storage
⏹Need to implement the actual labeling logic

@sachinshelke auto labeling is more/less complete.
I think the workflow could be ironed out a bit more to make things more efficient.
At the moment, to use the feature you need to upload a model_web folder to the root of your object storage bucket. Eventually you will be able to upload models directly to the tool or use a model stored directly from training.
TODO:
⏹ Label lots of images to find places to smooth out user experience
⏹ Add keyboard shortcuts
⏹ Upload model through the tool
⏹ Use model from any location in bucket

You can try out the feature at: https://stagingannotations.us-east.containers.appdomain.cloud/

@bourdakos1 Awesome. It work as it required.
I think it is good to be put in production.
One more item in TODO

Allow modifying / adjusting auto labelled box

I think I will release this by end of the day
Here's future update TODOs:
⏹ Allow modifying boxes
⏹ Allow drawing a new box
⏹ add a previous button
⏹ highlight all auto predicted boxes when hovering label all
⏹ add accept button to the box itself

Auto labeling is now live, I'll close this issue and open a new one requesting enhancements


Design an error message for the cover image of the infowindow

In the current version of the infowindows we have an error message that appear when the URL of a cover image couldn't be loaded. We'd need something similar for the new infowindow style.

There has been no activity on this issue for several months and that's why we are closing it (automatically). If you think this still needs to be addressed please reopen it. The good news is that we are now working on the next version of CARTO.js, stay tuned.


cargo2nix misses symlinks within workspace

I'm trying to build solana-frozen-abi-macro which has a build.rs that sets some cfg values depending on current toolchain (via rustc_version) in its build.rs https://github.com/solana-labs/solana/blob/master/frozen-abi/macro/Cargo.toml
The cause is that the build.rs is a symlink (to ../build.rs) and lack of the build.rs does not really confuse cargo at a lower level.
Looks like a bad case of NixOS/nix#1232 - can I do anything to help make a failure like this more apparent?

If the build.rs you want is present and just in the wrong place, you can likely use an override of the unpack or build phase to massage the sources into the correct place before nix misses them.  You can do this for a single dependency similar to here:
https://github.com/cargo2nix/cargo2nix/blob/master/overlay/overrides.nix#L132-L145

I believe the same issue will affect a crate that references workspace files or files above the workspace but still in the flake.  The proper solution may be to build each crate with the entire workspace source, but having patched out the higher up Cargo.toml's so that cargo doesn't attempt to build the crate with full workspace knowledge.
We could automatically patch some things, but it's likely fragile since paths can be generated through build.rs etc.
As far as how cargo2nix pulls apart dependencies and provides the build information via .link-flags and other intermediate files, they still have to be in consistent locations.
Really the change should amount to building workspace crates with a path offset, the full workspace source, and patching out Cargo.toml files in any parent directories.

https://github.com/cargo2nix/cargo2nix/issues/173

Think I'm going to add the entire workspace as a source instead of using subpaths as the source.  Performing the offset before running cargo is just another one liner.  Will require modifying the Cargo.nix and overlay.  That would fix the bulk of #173 and this issue.


[FontData] Fixes saving copy of the font source data, if it was created from built-in font.

Fixes #53253 (theme in the extension should be reimported to work).

Thanks!


Avoid using API KEY by specifing an app url #26

Hi,
If you use MFA for AuthN, awsprocesscreds still have some problem with handling MFA properly.
So here are the small modifications to handle app url without the need of using of an OKTA API KEY

adding the option to use an application url instead of using API KEY.
defaulting to appurl in configuration
remove the email constraint in login (not mandatory in Okta)
this change do not remove the existing options that are using OKTA API KEY (to remove in next step)

Please fix the failing tests and add documention on the appurl setting to the README. thanks!


JFR Native support

This is for Java Flight Recorder.
The extension can at build time then pre configure the ExtendedCamelContext.setStartupStepRecorder(new JavaInflight...)
And have the recorder use the configuration values from the supported values which we have in camel-main.
Its all the camel.main.startupRecorder options that can be used for configuration, such as duration, profile, dir etc.

Native support currently blocked by https://github.com/oracle/graal/issues/3608.


Directory walking

Description
I want use typst to compose type that "3 screenshots per page, landscape, images from a folder".
I want typest to behavior like css but the output is pdf. When I trying to achieve this, there are some missing
future:

walk through a folder by given path, return a iterator which yields all file path
render a length-unknown image path list

Use Case
Use typst as a universal type set tool.

#set page("a4", flipped: true)
#set text(10pt, style: "italic")

#let cell = rect.with(
  inset: 8pt,
)

#grid(
  columns: (auto, auto, auto),
  rows: (100%),
  gutter: 8pt,
  cell[#image("./images/1.png")],
  cell[#image("./images/2.png")],
  cell[#image("./images/3.png")],
)

Such code will compose a paper of 3 images in it, but I have a foldre of many screenshots.
Is there some tool could handle these scanery?

I recommend try with the preprocessing approach (using "typst-pyimage") first.

@laurmaedje do we want to implement a function for directory?
Maybe adding a interface named "list_dir" which takes a path and returns an array?

I'm not yet completely decided, but I'm open to discussing it. It should of course be restricted to the project/package directory like file loading. And there are further design decisions about what exactly it returns (what about folders for instance: is there a way to tell whether an array item is a file or folder). And then we need a good and efficient interface for the World trait.

How about a simple design like this (two new function)

list_dir(path: str): returns a list of strings under the given path, which includes files and sub-folders.
is_dir(path: str): returns whether a path is a directory.

I think this should be a minimum design; if a path is not a directory but a filename, then we should use functions such as "read" (we might also need to add some debug log and throw the error should we read a directory, instead of a file).

I saw within feat requests that walking a dir was requested. My question is until or if that feature gets added it there a way I could do a hacky rust implementation? My use case for moving from lualatex to typst requires me to automatic iterate a directory and sort the files based on content and then import in that order. (copypaste question from discord)
little more details:
my use case is for writing a penetration testing report in which I need to walk through a directory and import/include/sort findings based on cvss scores.

Not sure if this is still on the table, but I thought I'd just mention my use case on the off-chance it helps anyone.
I am designing a recipe book, each recipe is a Yaml file in a sub-dir of the project. My Typst book iterates through the recipes to produce the formatted output. It currently does this with a hard-coded set of paths, but it would be nice to be able to programmatically walk through all the files in that sub-dir that's effectively part of the "source" of the project.
I did think about making the recipes Typst files instead of Yaml, but that wouldn't change much as there does not seem to be any form of glob importing currently. If there is a neat way of doing this already, I don't know about it sorry.
Anyway just my two cents, I still think this issue is relevant!

Hi guys, I just made PR #4380 which provides a readdir function. This function returns the names of a directory's contents as an array of strings.
#readdir("test-folder")

renders something like below
("a.txt", "c", "b.json")

Thus we can do things like
#for file in files {
  if file.ends-with(".txt") {
    read("test-folder/" + file)
  }
}

I'd also like to have this ability for automatically including the contents of certain folders into an appendix; my current approach is:
= Appendix
#show: appendix
== Matlab Code
=== ber_curves.m
#let text = read("matlab/ber_curves.m")
#raw(text, lang: "matlab")
=== Exsample_aliasing.m
#let text = read("matlab/Exsample_aliasing.m")
#raw(text, lang: "matlab")
...

I would much rather be able to just point it at the matlab folder and have it add an entry for each file that is present there.