Authentication error :GET Request failed with status: 401 Unauthorized in Rust example

Getting error when running the rust example on both sandbox and testnet env

@SlavaSereb

Is there any change that has happened in the past week. Previously code which was working , is also giving 401 error. While postman api works correctly for the same api keys and body


merge change for issue #224

What kind of change does this PR introduce? (check one with "x")
[] Bugfix
[] Feature
[] Code style update (formatting, local variables)
[X] Refactoring (no functional changes, no api changes)
[] Other... Please describe:

Fixes: #224
What is the current behavior?
What is the new behavior?

Refer to #224 for description of the fixed issue.  The original pull request #225 was approved but closed before the fix was merged into master.  So I resubmit the same change to get it merged.


Bump etcd versions for 1.20 and 1.21

EKS-A tests failing during cluster upgrade v1.20 & v1.21. Issue appears to originate with https://github.com/etcd-io/etcd/pull/14441.
Upgrade v1.20 & v1.21 to use the patched version 3.4.21

Closed by #1348


AVL encodings (-1 and "don't change")

(1) Section 6.1 says AVL is unsigned, while a NOTE also says AVL of -1 is used to set vl to VLMAX. Should the -1 in the NOTE be changed to 2^XLEN-1 ?
(2) Using x0 as rs1 for AVL means "don't change VL". Will this cause a problem with some compilers? After constant propagation, it may determine that vl=0 is a valid value and attempt to use x0, but this will not have the normally intended effect. Hence, the compiler will have to have special-case code to detect this and move 0 into another register (something which isn't typically done).
Instead, maybe the vtype fields in rs2 could be expanded to include a flag (bit 7?) that has the effect of ignoring rs1 if set when executing vsetvl. For vlsetvi, an extra bit may be needed from the ISA encoding, which is less than ideal.

Agreed re: 1 (alternatively ~0)
Speaking as one of the GCC maintainers, (2) is no problem.  It's already an accepted pattern in RISC-V that rs1=x0 can have special meaning, as is the case for CSRRS/CSRRC and SFENCE.VMA.  GCC and LLVM already have to cope with some x-registers having special purpose, e.g., don't use x5 for tail calls to avoid messing up return-address stacks.

thanks for the clarification Andrew. I'll accept what you say as truth and don't need a reply ... but I just wanted to clarify my issue with (2) is not about generating a deliberate opcode (using x0) to achieve the intended special purpose.... it's about the accidental generation of what seems like it could be a plausible opcode. x0 is also a bit different than the special instructions and other registers (x0 == 0 has been ingrained in our mindset for a long time). still, i'll assume what you have said holds true and don't expect a response. (compiler-writers beware! here be dragons; pun intended).

Haha.  Yes, it certainly merits a warning and careful auditing.

if compiler knows vl=0, it should elide the code.  Also, don't tell compiler that there is a vl=immediate form of vsetvl in first place

It's not about immediate forms. Before register allocation (using virtual registers in SSA form) you might have something like
%virtreg:GPR = <constant>
vsetvl ..., %virtreg, ...

which would in general be lowered to materializing the constant into one of x1-x31 and assign %virtreg to that register. But when the constant is 0, it's preferred to just assign %virtreg to x0 and not need any materialization code.
We can't rely on high level optimizations such as eliding all following vector code for vl=0 to side-step the problem, especially since the constant might only become apparent very late in the compilation pipeline. But it's easy to avoid the problem by having a register class for "GPR but not x0" and using it for this operand of vsetvl (treating the version with x0 as a different instruction internally). As Andrew said, similar tricks are already necessary for other instructions such as CSR operations or some C instructions.

I'm closing this issue because I think there's rough agreement on the latter point.
I tried using 2^XLEN-1 instead of -1, but thought the spec became less clear as a result.

I think there is a way to get the -1 / VLMAX setting and the "keep VL" setting with slightly rearranged ISA encoding for setvl / setvli:
rd  rs1    AVL
0   0     vl     used to maintain current value
!0   0     ~0     used to get largest VLMAX
0  !0   x[rs1]   normal use, doesn't keep vl value in GPR
!0  !0   x[rs1]   normal use
The current spec merges rows 1 and 2 of this table, and only has the functionality of row 1.
The change separates the rd=x0 case from the rd !=x0 case. When VL is kept at the same value, there is probably no need to return it in rd, hence the use of x0 in row 1. If the current value of vl is needed, the CSR can be read. When VLMAX is requested, a VL must be returned, hence the use of any register but x0 in rd.

This seems like a simple enhancement so I added to draft spec.


[Question] How to implement SmoothStep Connection style on WPF?

Hello,@miroiu!  As described in the title, I would like to discuss how to implement the style of smooth step connection on WPF? Because in similar node editors, I seem to have only seen similar designs on the browser side. After practicing and researching, I found that implementing the smooth step style is extremely troublesome. I would like to know if I will learn how to implement smooth step connection in notify?

Hi @lyq-lin ! I implemented the feature in this PR: #149. Please let me know if that works for you.

It's amazing that I can always learn the "best practices" of WPF on notify. Thank you for your answer @miroiu


Compilation warnings

Reported by a customer -- when loading the bootstrap, there are three compiler warnings.
RsrServiceSnapshot >> decode: aStream using: aDecoder
WARNING: unused method temp 'templateClass'
RsrSnapshotAnalysisTest >> testNewServicesInDictionary
WARNING: unused method temp 'expected'
RsrSnapshotAnalysisTest >> testServiceReferencingAnotherService
WARNING: unused method temp 'expected'

Fixed with commit 0817bfc1

Fixed with commit 0817bfc1

I've got code in the Rowan load script that fails/reports compiler warnings during load ... sound like it's time to add this to the Sparkle/RSR scripts

I've got code in the Rowan load script that fails/reports compiler warnings during load ... sound like it's time to add this to the Sparkle/RSR scripts

I've added the compile warning check to the installation script ... in Rowan, I've found that the best place to put the compile warning check is in the batch job used to run tests ... I run Rowan tests in a fresh extent0.rowan.dbf and if compile warnings show up the test is failed ... I always run tests BEFORE merging code into the release branches ... it is always prudent to run tests before merging code into a branch that users will be using ...

I've added the compile warning check to the installation script ... in Rowan, I've found that the best place to put the compile warning check is in the batch job used to run tests ... I run Rowan tests in a fresh extent0.rowan.dbf and if compile warnings show up the test is failed ... I always run tests BEFORE merging code into the release branches ... it is always prudent to run tests before merging code into a branch that users will be using ...

Installing with this change to the script creates a zero-length topazerrors.log file. Is this expected? If so, should that go in a .gitignore so it doesn't get committed?

Installing with this change to the script creates a zero-length topazerrors.log file. Is this expected? If so, should that go in a .gitignore so it doesn't get committed?

that's the resultcheck in action ... while the topazerrors.log file is not unexpected, where the file is dropped depends upon where the script gets run, I usually run topaz in a directory outside of the repository itself .... if there is a standard directory that the script is run from then a .gitignore wouldn't hurt ... which directory is the standard location?

that's the resultcheck in action ... while the topazerrors.log file is not unexpected, where the file is dropped depends upon where the script gets run, I usually run topaz in a directory outside of the repository itself .... if there is a standard directory that the script is run from then a .gitignore wouldn't hurt ... which directory is the standard location?


Dynamic AppCall compilation

It's not possible to normally generate a dynamic APPCALL using our compiler at the moment. The option, if possible, would be to autogenerate it for dynamic (not known at compile time) scriptHash parameters, if that's not possible then we need a DynAppCall() interop probably.
CC: @AlexVanin.

One possible caveat is globally defined contract address: if it is not constant, we must use dynamic appcall, even though Go doesn't allow to []byte constants.
I prefer separate interops for static/dynamic calls perhaps with string argument in static case:

It helps readability.
Usage of dynamic appcalls is a special smart-contract permission, so we better be explicit.

Yeah, I've also thought about the second point and it has some value, so a separate call can make things more predictable.

Fixed in master-2.x, not relevant for master.


Fix Heatmaps for Android (Mobile)

Heat maps for Android don´t work.

This Issue has been created by mistake. Apologizes, Ismar.


Unable to retrieve child resources.  Details: ["Error:Unable to retrieve authentication token."]

Unable to retrieve child resources.
Details:
["Error:Unable to retrieve authentication token."]

@aureole82 can you go to Settings -> Services -> Disks, uncheck the checkbox and then restart? That should unblock you (assuming you don't need to work with disks).

Closing due to lack of response. If you are still having problems, please open a new issue. Thanks.


Update the samples to use the new nodejs10 runtime.

Resolved merge conflicts.

I'm coo with this, just please let @fhinkel sign off :)

Travis has passed; for some reason it's not reported back to GitHub.
Merging the PR now.


Disable anti-aliasing for mobile

Description
disabling anti-aliasing for mobile, because it still looks exactly the same and improves performance.
Tests
ran it on the phone and checked how it looked
Documentation
How is this documented (for example: release note, upgrade guide, feature page, in-code documentation)?
Did you remember a changelog entry?
Primary reviewers
If your change will take a long time to review, you can name at most two primary reviewers who are ultimately responsible for reviewing this request. @ mention them.

Is AA also disabled on the camera in the post processing layer?


Fix for issue #3853. AllOf ref is incorrect for FQ class names

Fix for ticket 3853

Thanks! replaced by #4146 which includes this PR's test. Went for explicit setting of full ref as a safer option

Indeed a better solution. Thanks for using the test.


chore: update text in otp verification page

Pull Request Test Coverage Report for Build<PHONE_NUMBER>1
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 9.329%

Totals

Change from base Build<PHONE_NUMBER>9:
0.0%

Covered Lines:
10115

Relevant Lines:
108420

💛  - Coveralls


test: added kurtosis ci workflow

What was wrong?
How was it fixed?
To-Do

[ ] Clean up commit history and use conventional commits.

closing for now, working on solidifying this functionality over in portal-package and then using it over here


Flow comment parsing

Flow supports this comment syntax. These are some pretty simple parser hacks.
Comment Includes
Input:
/*::
type Foo = {...};
*/

Parsed:

type Foo = {...};

/*:: is ignored and everything until the next */ is parsed as if the comment tokens weren't there.
Input:
ab/*::c*/de

Parsed:
abcde

Comment Annotations
Input
function foo(bar/*: number */)/*: string */ {...}

Parsed:
function foo(bar: number): string {...}

These are the same as includes, except /*: is parsed as a : token. The /* and `*/ are thrown out.

I think these would be pretty easy to add to Babylon to get an AST including the parts inside comments.
The only question I have is if this should be part of the Flow plugin or a separate plugin. I'm leaning towards separate plugin.
I can take this on unless someone else wants to. I'm happy to help anyone out if they want to take it on. Might be a good one for beginners

Note that comment annotations are not contextual at all, as long as the resulting syntax is parsable, it is valid:
Input:
const object = {
  foo/*: bar */
};

Parsed:
const object = {
  foo: bar
};

Interesting idea. I definitely hadn't considered trying to treat it like actual syntax instead of parsing the comments later. It does seem like that would address a lot of the current issues we have with the flow comment plugin.
I'd be open to it. I assume we'd want a similar flag for the code generator to output all this stuff?
My only comment is that your ab/*::c*/de to abde example seems off, since it would be treated as two separate identifiers in the parser normally, so it seems like it should still see the comment as a token separator.

current issues we have with the flow comment plugin

There's a Flow comment plugin already? Where/What?

since it would be treated as two separate identifiers in the parser normally

Oh I'm sorry, you're right the comment tokens aren't simply thrown out, they are replaced with whitespace ref

We've got https://github.com/babel/babel/tree/master/packages/babel-plugin-transform-flow-comments, but it's always been buggy because leadingComments and trailingComments aren't very accurate.
Generally whenever people submit bugs for it, we recommend they use .js.flow files instead, like https://github.com/babel/babel/issues/6142#issuecomment-323766148
You can see there are at least a few other obvious ones https://github.com/babel/babel/issues?utf8=✓&q=is%3Aissue is%3Aopen flow-comments

Ooooh, thought you meant a Babylon plugin

Yeah sorry, could have been clearer on that :)

@thejameskyle @loganfsmyth I can work on this.


ADDED: Learn Flutter - Beginners Course

Hey @richard937 !
Congrats on submitting your pull request.
You PR has been merged and the changes will be reflected on the website in a few minutes,.
Do leave a star, if you liked the repo ;)
Happy hacking ! 🎊


Tinkers Construct Tool Materials Crash

Hi, I decided to report this issue I'm experiencing because I couldn't find anyone reported this issue.
If I look up the usage of a Tinkers Construct tool part (like Pickaxe Head) it shows me the information about that material. But if I click (on the usage page) on the pickaxe icon with the "Recipes" tag (shown below) I get this crash:
Crash Report
Mods used:
NotEnoughItems <IP_ADDRESS>
NotEnoughResources <IP_ADDRESS>
NEI Addons <IP_ADDRESS>
NEI Integration 1.0.11
Tinkers' Construct 1.8.5
TiC Tooltips 1.2.4
Tinkers' Mechworks <IP_ADDRESS>
AOBD 2.6.3
ExtraTiC 1.4.5
And I used lots of other mods, these are only the NEI and TiC related mods that I listed. You can find the other mods names in the Crash Report.
I actually don't know what mod causes this, I just guess it's NEI. If not, just tell me and I will report to another mod.

I am also having this issue, same setup


Remove model selection from outlier detection stage

A cleaner interface is to pass the model weights to the outlier detection code. Model selection could be a separate stage. For now we will simply use the latest model.

Model selection stage in progress.
TODO

[ ] Make JSON file API in DeepDriveMD_API.
[ ] Implement basic model selection which takes latest checkpoint file and writes the path to JSON.
[ ] Remove latest_ml_checkpoint_path() from PipelineManager


TypeScript Error: defineRouting expects 0 arguments but got 1 during npm run build

Description
I'm encountering a TypeScript error when running npm run build in my Next.js project that uses next-intl. Interestingly, the error does not occur when I run npm run dev; everything works as expected in the development environment.
Error Message:
./i18n/routing.ts:4:38
Type error: Expected 0 arguments, but got 1.

  2 | import { defineRouting } from "next-intl/routing";
  3 |
 >4 | export const routing = defineRouting({
    |                                      ^
  5 |   locales: ["en", "es"],
  6 |   defaultLocale: "en",
  7 |   pathnames: {

Verifications

[X] I've verified that the problem I'm experiencing isn't covered in the docs.
[X] I've searched for similar, existing issues on GitHub and Stack Overflow.
[X] I've compared my app to a working example to look for differences.

Mandatory reproduction URL
https://github.com/amannn/next-intl-bug-repro-app-router
Reproduction description
Steps to reproduce:

Set up a Next.js project with TypeScript and install next-intl.

Create an i18n/routing.ts file with the following content:

import { defineRouting } from "next-intl/routing";

export const routing = defineRouting({
  locales: ["en", "es"],
  defaultLocale: "en",
  pathnames: {
    // Custom route configurations
  },
});

Run npm run build to build the project for production.

Expected behaviour
The project should build successfully without any TypeScript errors, just as it does during development with npm run dev.
Actual Behavior:
The build process fails with the TypeScript error mentioned above, indicating that defineRouting expects 0 arguments but received 1.
Additional Information:
tsconfig.json:
{
  "compilerOptions": {
    "target": "es5",
    "lib": ["dom", "dom.iterable", "esnext"],
    "allowJs": true,
    "skipLibCheck": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "incremental": true,
    "plugins": [{ "name": "next" }],
    "types": ["@testing-library/jest-dom", "jest", "node"],
    "paths": { "@/*": ["./*"] },
    "typeRoots": ["./types", "./node_modules/@types"]
  },
  "include": [
    "next-env.d.ts",
    "**/*.ts",
    "**/*.tsx",
    ".next/types/**/*.ts",
    "global.d.ts",
    "jest.config.js"
  ],
  "exclude": ["node_modules"]
}

Hello, I can't include more about reproduction because it is very simple and it is al explained in the 1st post.
All that I can do is to share my project and you can try it yourself @amannn
https://github.com/NachoTamayo/VTTS/
Regards

If you can provide a minimal reproduction based on the provided template then I'm happy to have a look, but bug reports are not meant for general support requests—sorry.
I'll move this to a discussion.


Support "edge" mode for rotation padding

Hi, Thanks for the library!
When we do the rotation transformation, can we support 'edge' padding for the black areas? skimage supports different padding mode: http://scikit-image.org/docs/dev/api/skimage.transform.html#skimage.transform.rotate
Thank you!

Affine is a wrapper around skimage's warp function and supports the mode parameter, i.e. something like Affine(rotate=(-45, 45), mode="edge") should work.


if constexpr first try

Not sure my example will fit in a single slide. I guess/hope this PR will trigger some pdf generation somewhere.
I did not found how to have 'C++17' instead of 'C++11' in the slide title.
I also insert some few 'member function' here and there, can be removed if you dislike.

Sorry for the cryptic \frametitleii,it,gb and so on but leet speach is the only thing I found to go around the problem that latex commands do no accept numbers in their name...

Now that I've looked at it into more details, few things came to my mind :
* definitely 2 slides
* we may drop / simplify drastically the made up example for constexpr in favor of the one for if constexpr

Would be a pity. I love to see this idea of using units for numbers. (except for the presumed bug on case 'm'). On the other hand, it is perhaps both too short and too much, and divert the students from the current topic you want to talk about, 'constexpr'.

* we have an ordering problem : templates were not yet introduced at that moment of the course. Shall we move constexpr and if constexpr together to the end of the "Cor modern C++ section"

I would only move 'if constexpr'. It has been introduced later. I would not be ashamed if it is not adressed at the same time than basic constant expressions. And as you say, to be usefull, it requires templates, which is not the case with simple 'constexpr', which was on the contrary introduced to avoid templates and TMP, no ?

So, @sponce @bernhardmgruber, do we merge ?

I'll merge this as soon as my refactoring is merged. And I'll take care to rebasing and sorting it out

Thanks.

"Merged" through #75 that was a manual rebase of this. So closing it


Fix for scenario where version_label is empty

version_label can be empty if you only want to update the config of the env and not the version deployed. In this case the wait_for was for ever looping.
Pulled from @fvant, already merged upstream.

:+1:

Coolio
👍


Can we change the url to nr-fds-theme? Or is that crazy?

Can we change the url/repo name to nr-fds-theme? Or is that crazy at this point?
@DerekRoberts

@jackwingsam Ha, sure!  Whatever your team decides we do.  :D

Looks like while I was on vacation, we got approval to change from FSA to FDS

Welcome back @jackwingsam!  :)  ...Let's talk to @MCatherine1994 about making this change.

Hi Jack @jackwingsam, changing url is doable. Just wondering since we already published some packages that teams are sharing for the stylesheet. If we change the repo name, we might want to change the package name as well?

i really don't know how to answer the part about the packages.
the name change overall is not a high priority thing. but slightly higher priority now that Chantelle got the name change approved. what's a good timeline that fits your schedule?

@jackwingsam Let's leave that to @MCatherine1994.  I'm mostly here for support and/or to fill in any gaps.

yeah, sorry i didn't tag anyone. my last comment was meant to ask @MCatherine1994 to pick a timeline that best suits her pre-existing workload

sure, I'll bring this to our dev meetup this Thursday cause the package naming will impact the teams that are currently using it. And will target do the change next Monday. Thanks!

Morning @jackwingsam @DerekRoberts, I wonder do we need to include "fds" in our repo name? Or maybe we can call it "nr-common-theme", so we don't need to worry about the team name in the future?

@MCatherine1994 I like that idea!  Departments get renamed all the time in gov.  Plus common says a lot.  :)

I'm ok with a more generic name but maybe something more specific to forestry? We know there are other NR sector teams (like ENV and even with FOR/WLRS) also doing their own design systems. We tried to join forces but they didn't want to...

how about nr-forest-theme? or any other suggestion? @jackwingsam @DerekRoberts

Ideally we'd build components that all of NR can use.  Most of my tools are for general consumption, not just gov.

yeah, I agree. If other teams want a different theme, they can name their repo differently

I'll put this on hold for now until Andrea is back from the vacation and it's not that urgent, then we can discuss which name want to use.

Ideally we'd build components that all of NR can use. Most of my tools are for general consumption, not just gov. nr-theme!

i like to think that way too, building for all of gov, but we did shop what we're doing with other NR teams and they were not satisfied with it.
the other thing that makes me not that comfortable with a generic nr-theme repo name is that we made a lot of decisions that are not in line with the rest of BCGov/GCPE. for example the blue that we have for the buttons across all of our login pages and headers on the content pages is not a normal BC Gov blue. we made some decisions that were only focused on FSA/FDS apps.
i agree with @MCatherine1994, let's wait for Andrea

Just to provide an update for this issue. I checked the repos in bcgov organization, don't see any other repo named with "nr" or "theme", also chatted with Andrea, we should be good to use "nr-theme". If other teams also work on other design systems, they can call their repo a different name.

Thanks @MCatherine1994
@alkolot is the one who's going to have to interface with other nr design teams


Use authentication context whenever available

To access keychain items with the same authentication context
I noticed that kSecUseAuthenticationContext is not being used. But, it's useful for repeated access of keychain items. Especially, when it's being used with Touch ID.

@jessearmand Thank you for the PR! It has been merged with a tiny change. Sorry for the late response.


[FRONTEND]To use proper default num_warps and num_stages based on the device backend in JITFucntion

The default values used by JITFunction for num_warps and num_stages are coupled with Nvidia GPU architecture. We should use the proper default values based on the device backend for the kernel to be compiled to.

Add two functions to return the default num_warps and num_stages for the specific device backend.
JITFunction uses the proper default num_warps and num_stages based on the specific device backend.

    def test_compile_in_subproc() -> None:
        major, minor = torch.cuda.get_device_capability(0)
        cc = major * 10 + minor
        config = instance_descriptor(tuple(range(4)), (), (), ())

        multiprocessing.set_start_method('fork')
        proc = multiprocessing.Process(
            target=compile_fn,
            args=(config, cc))
        proc.start()
        proc.join()
>       assert proc.exitcode == 0
E       AssertionError: assert 1 == 0
E        +  where 1 = <Process name='Process-1' pid=4192087 parent=4191930 stopped exitcode=1>.exitcode

I am investigating this issue.
It is caused by this PR which invokes the CUDA runtime API in Pytorch to get the architecture information in compiling.
The Pytorch CUDA runtime lazy initialization has limitation in python multiprocessing by fork.
https://pytorch.org/docs/stable/notes/multiprocessing.html#cuda-in-multiprocessing
Maybe it is a little over-protected for this Triton test case that we just want to query the information of the device.

@ptillet
I can quick make a fix by skipping query the device runtime information in compiling if the CUDA CC has been set by the user.
But I think your suggestion is very important.
What do you think about to supporting the fork for CUDA in compiling? Does it has to be supported carefully?
There is some comments that
// We can't initialize CUDA before fork() so we need to spawn a new process
https://forums.developer.nvidia.com/t/cuda8-0-bug-child-process-forked-after-cuinit-get-cuda-error-not-initialized-on-cuinit/45764/2

After review the test case carefully, the compile should not to query the CUDA capability if the user explicitly set the cc.


Remove the "visible" field from DisplayWork

If something gets as far as being a DisplayWork, it surely must be visible!

👍

Mmm. So in fact we convert Work to DisplayWork inside the WorksService, after it's been retrieved from Elasticsearch, but before we decide to 410 it.
This feels icky to me – WorksService is a weird mixture of internal logic (interacting with Elasticsearch and Works) and display logic. It feels like WorkService should just return a Work, and it's up to the caller to decide how to use it.


Handle NaNs

1 Treat NaNs as error in RMSE accuracy measurements
Comparison with NaN always goes to false-case of if-statement, but tolerance errors are reported in true-case of if-statement. So, RMSE equals NAN was always hidden, and faulty tests might pass.
2 set_all_to_sawtooth method generates infinities in case length(dimx) == 2, this results in NaNs being the results of FFT.

@stmuxa
looks like a simple fix, but the PR shows 17 commits? can you rebase from clFFT properly and issue PR again with 1 commit. thanks

yes, somehow I mixed up my branch with these commits.
will fix on monday.

@bragadeesh
Done. Dropped commits added by mistake, squashed the rest into one commit.


Add use case images

#190  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @thisisgoldman and the rest of your teammates on  Graphite

Merge activity

Aug 29, 4:27 PM EDT: @thisisgoldman started a stack merge that includes this pull request via Graphite.


Rate limiting advanced plugin

Lots of questions/comments:

Right now we don't have support for multiple pages within a plugin directory, the pages conflict with each other:
 The following destination is shared by multiple files.
22:46:43 jekyll.1 |                     The written file may end up with unexpected contents.
22:46:43 jekyll.1 |                     /github-repos/developer.konghq.com/dist/plugins/rate-limiting-advanced/index.html
22:46:43 jekyll.1 |                      - /github-repos/developer.konghq.com/app/_kong_plugins/rate-limiting-advanced/index.md
22:46:43 jekyll.1 |                     - github-repos/developer.konghq.com/app/_kong_plugins/rate-limiting-advanced/reference.md

This is the same problem that Diana ran into here: https://github.com/Kong/developer.konghq.com/pull/20
I tried messing around with the jekyll config file and the collections but couldn't figure it out. Haven't worked with collections before so that is a bit of a mystery - can collections be modified to use pieces of content here and there? For example, right now the plugins index is pulling in two entries for the RLA plugin, its index page and its reference page, but the links are both to the landing page, and the content is from reference (all very confusing).

Rate Limiting Advanced landing page: so much content! This feels like too much detail to get into on a landing page, but at the same time, I don't want it to get lost. Should all of this live on different pages? If we're not nesting anything other than index, reference, and maybe API doc under each plugin, where would it all go?

Added metadata for tier: enterprise and konnect_compatible: true. Could also make it konnect: true. Since the pricing model is changing, we don't need to worry about Konnect Free/Plus/Enterprise tags here and can just have a true/false flag.

How do we want to portray multiple examples? Right now, on the reference page, they're listed out in a row. Should there be a dropdown to select an example, or is that too many dropdowns?

Non-plugin specific: should every single page have a description key with a short description? I'd say yes, for search metadata reasons.

Implemented what we talked about on Friday: split content, moved examples into metadata.
When splitting the content, went down a rabbit hole of need a bunch more plugin pages, so now we have stubs for all the Rate Limiting plugins - that seems reasonable.
Questions:

Should we display all plugins as cards on reference pages, tutorials, etc as well? For consistency? Or should they appear in related links?
Should we have a separate plugin_reference layout, or should we use plugin?
I turned the plugin's reference.md file into yaml. I can't think of why not - most of that content should be generated, so yaml seems to make sense.

@fabianrbz feel free to make changes here directly, if you're fixing anyway, and merge this whenever to get them in sooner.

Implemented what we talked about on Friday: split content, moved examples into metadata.

When splitting the content, went down a rabbit hole of need a bunch more plugin pages, so now we have stubs for all the Rate Limiting plugins - that seems reasonable.
That's great, thanks!

Questions:

Should we display all plugins as cards on reference pages, tutorials, etc as well? For consistency? Or should they appear in related links?

This is something we can discuss with the rest of the team. I don't think that cards are needed because it might give them too much visibility in reference pages and tutorials.

Should we have a separate plugin_reference layout, or should we use plugin?

I added a two, although the one for the reference doesn't have much, we'll see if we need it in the future.

I turned the plugin's reference.md file into yaml. I can't think of why not - most of that content should be generated, so yaml seems to make sense.

That makes sense.

@fabianrbz if it helps at all - feel free to make changes here directly, if you're fixing plugin collections/references anyway, and merge this whenever to get them in sooner.
I've made some changes, will merge this soon.


F2 f 133 framework fixes

Proposed changes

What changed
Refactor to use features of hmpo-form-wizard, including editing, backLinks, and config based routing.
Note: This should be backed up with browser tests covering all the scenarios required.

Why did it change

Issue tracking

F2F-XXXX

Checklists
Environment variables or secrets

[ ] Documented in the README
[ ] Added screenshots to show the implementation is working
[ ] Ran cfn-lint on any SAM templates

Other considerations

changes incorporated in other PRs


flutter create crashing with latest 1.5.4 upgrade

My setup is perfectly fine. It was working before I upgraded to latest flutter.
Steps to Reproduce
Run flutter create command
Logs
$ flutter --version
Flutter 1.5.4-hotfix.2 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 7a4c33425d (7 weeks ago) • 2019-04-29 11:05:24 -0700
Engine • revision 52c7a1e849
Tools • Dart 2.3.0 (build 2.3.0-dev.0.5 a1668566e5)
$ flutter create new_project
Creating project new_project...
  new_project/README.md (created)
  new_project/android/app/build.gradle (created)
  new_project/android/app/src/main/java/com/example/new_project/MainActivity.java (created)
  new_project/android/new_project_android.iml (created)
  new_project/android/build.gradle (created)
  new_project/new_project.iml (created)
  new_project/test/widget_test.dart (created)
  new_project/ios/Flutter/Release.xcconfig (created)
  new_project/ios/Flutter/AppFrameworkInfo.plist (created)
  new_project/ios/Flutter/Debug.xcconfig (created)
  new_project/ios/Runner/Base.lproj/Main.storyboard (created)
  new_project/ios/Runner/Base.lproj/LaunchScreen.storyboard (created)
<EMAIL_ADDRESS>(created)
<EMAIL_ADDRESS>(created)
  new_project/ios/Runner/Assets.xcassets/LaunchImage.imageset/LaunchImage.png (created)
  new_project/ios/Runner/Assets.xcassets/LaunchImage.imageset/README.md (created)
  new_project/ios/Runner/Assets.xcassets/LaunchImage.imageset/Contents.json (created)
<EMAIL_ADDRESS>(created)
<EMAIL_ADDRESS>(created)
<EMAIL_ADDRESS>(created)
<EMAIL_ADDRESS>(created)
<EMAIL_ADDRESS>(created)
<EMAIL_ADDRESS>(created)
<EMAIL_ADDRESS>(created)
<EMAIL_ADDRESS>(created)
<EMAIL_ADDRESS>(created)
<EMAIL_ADDRESS>(created)
<EMAIL_ADDRESS>(created)
<EMAIL_ADDRESS>(created)
<EMAIL_ADDRESS>(created)
<EMAIL_ADDRESS>(created)
  new_project/ios/Runner/Assets.xcassets/AppIcon.appiconset/Contents.json (created)
<EMAIL_ADDRESS>(created)
  new_project/ios/Runner/Info.plist (created)
  new_project/ios/Runner.xcodeproj/xcshareddata/xcschemes/Runner.xcscheme (created)
  new_project/ios/Runner.xcodeproj/project.xcworkspace/contents.xcworkspacedata (created)
  new_project/ios/Runner.xcworkspace/contents.xcworkspacedata (created)
  new_project/pubspec.yaml (created)
  new_project/.metadata (created)
  new_project/.gitignore (created)
  new_project/ios/Runner/AppDelegate.h (created)
  new_project/ios/Runner/main.m (created)
  new_project/ios/Runner/AppDelegate.m (created)
  new_project/ios/Runner.xcodeproj/project.pbxproj (created)
  new_project/web/index.html (created)
  new_project/.idea/workspace.xml (created)
  new_project/.idea/modules.xml (created)
  new_project/.idea/runConfigurations/main_dart.xml (created)
  new_project/.idea/libraries/KotlinJavaRuntime.xml (created)
  new_project/.idea/libraries/Dart_SDK.xml (created)
  new_project/.idea/libraries/Flutter_for_Android.xml (created)
  new_project/android/app/src/profile/AndroidManifest.xml (created)
  new_project/android/app/src/debug/AndroidManifest.xml (created)
  new_project/android/app/src/main/res/values/styles.xml (created)
  new_project/android/app/src/main/res/mipmap-mdpi/ic_launcher.png (created)
  new_project/android/app/src/main/res/mipmap-xxxhdpi/ic_launcher.png (created)
  new_project/android/app/src/main/res/mipmap-xxhdpi/ic_launcher.png (created)
  new_project/android/app/src/main/res/mipmap-xhdpi/ic_launcher.png (created)
  new_project/android/app/src/main/res/mipmap-hdpi/ic_launcher.png (created)
  new_project/android/app/src/main/res/drawable/launch_background.xml (created)
  new_project/android/app/src/main/AndroidManifest.xml (created)
  new_project/android/gradle.properties (created)

Oops; flutter has exited unexpectedly.
Sending crash report to Google.
Crash report sent (report ID: 761b0d58cb7960b0)

Crash report written to /home/kk/src/flutter/flutter_03.log;
please let us know at https://github.com/flutter/flutter/issues.

Flutter crash report; please file at https://github.com/flutter/flutter/issues.
command
flutter create new_project
exception
TemplateException: Value was missing for section tag: androidX. (3:1)
{{#androidX}}
^
#0      Renderer._renderSection (package:mustache/src/renderer.dart:136:9)
#1      Renderer.visitSection (package:mustache/src/renderer.dart:115:7)
#2      SectionNode.accept (package:mustache/src/node.dart:63:43)
#3      Renderer.render.<anonymous closure> (package:mustache/src/renderer.dart:58:30)
#4      List.forEach (dart:core-patch/growable_array.dart:278:8)
#5      Renderer.render (package:mustache/src/renderer.dart:58:13)
#6      Template.render (package:mustache/src/template.dart:40:14)
#7      Template.renderString (package:mustache/src/template.dart:33:5)
#8      Template.render.<anonymous closure> (package:flutter_tools/src/template.dart:157:77)
#9      __InternalLinkedHashMap&_HashVMBase&MapMixin&_LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:367:8)
#10     Template.render (package:flutter_tools/src/template.dart:109:24)
#11     CreateCommand._renderTemplate (package:flutter_tools/src/commands/create.dart:575:21)
#12     CreateCommand._generateApp (package:flutter_tools/src/commands/create.dart:502:23)
<asynchronous suspension>
#13     CreateCommand.runCommand (package:flutter_tools/src/commands/create.dart:353:37)
<asynchronous suspension>
#14     FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:559:18)
<asynchronous suspension>
#15     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:495:33)
<asynchronous suspension>
#16     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142:29)
<asynchronous suspension>
#17     _rootRun (dart:async/zone.dart:1124:13)
#18     _CustomZone.run (dart:async/zone.dart:1021:19)
#19     _runZoned (dart:async/zone.dart:1516:10)
#20     runZoned (dart:async/zone.dart:1463:12)
#21     AppContext.run (package:flutter_tools/src/base/context.dart:141:18)
<asynchronous suspension>
#22     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:486:20)
#23     CommandRunner.runCommand (package:args/command_runner.dart:196:27)
<asynchronous suspension>
#24     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:396:21)
<asynchronous suspension>
#25     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142:29)
<asynchronous suspension>
#26     _rootRun (dart:async/zone.dart:1124:13)
#27     _CustomZone.run (dart:async/zone.dart:1021:19)
#28     _runZoned (dart:async/zone.dart:1516:10)
#29     runZoned (dart:async/zone.dart:1463:12)
#30     AppContext.run (package:flutter_tools/src/base/context.dart:141:18)
<asynchronous suspension>
#31     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:356:19)
<asynchronous suspension>
#32     CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:111:29)
#33     new Future.sync (dart:async/future.dart:224:31)
#34     CommandRunner.run (package:args/command_runner.dart:111:11)
#35     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:242:18)
#36     run.<anonymous closure> (package:flutter_tools/runner.dart:60:20)
<asynchronous suspension>
#37     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142:29)
<asynchronous suspension>
#38     _rootRun (dart:async/zone.dart:1124:13)
#39     _CustomZone.run (dart:async/zone.dart:1021:19)
#40     _runZoned (dart:async/zone.dart:1516:10)
#41     runZoned (dart:async/zone.dart:1463:12)
#42     AppContext.run (package:flutter_tools/src/base/context.dart:141:18)
<asynchronous suspension>
#43     runInContext (package:flutter_tools/src/context_runner.dart:50:24)
<asynchronous suspension>
#44     run (package:flutter_tools/runner.dart:51:10)
#45     main (package:flutter_tools/executable.dart:60:9)
<asynchronous suspension>
#46     main (file:///b/s/w/ir/k/archive/flutter/packages/flutter_tools/bin/flutter_tools.dart:8:3)
#47     _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:298:32)
#48     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:171:12)

flutter doctor
[✓] Flutter (Channel stable, v1.5.4-hotfix.2, on Linux, locale en_US.utf8)
    • Flutter version 1.5.4-hotfix.2 at /opt/flutter
    • Framework revision 7a4c33425d (7 weeks ago), 2019-04-29 11:05:24 -0700
    • Engine revision 52c7a1e849
    • Dart version 2.3.0 (build 2.3.0-dev.0.5 a1668566e5)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /opt/android-sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = /opt/android-sdk
    • Java binary at: /usr/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-b03)
    • All Android licenses accepted.

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/setup/#android-setup for detailed instructions).

[!] Connected device
    ! No devices available

! Doctor found issues in 2 categories.

Also note that everything else works. Running my existing projects, launching the emulator .etc Just creating a new one doesn't.

I'm not able to reproduce on 1.5.4, did you make any modifications to flutter locally?

chmod -R 777 /opt/flutter/

Re-installed Flutter and it works. Sorry for the bother.


How do I get the key once it is generated?

I am not sure if this is included somewhere, but after creating an API key from the admin panel, how do I actually get the key so that I can put it in my headers? Its always hidden for me.

Hello @tahmidkhan once you click save (when creating a key) it will show up in the next page, above the "Success" message. If you missed it, you can still access it from the database or running the django shell command(import the library, select the model etc). I am attaching a screenshot - hope it helps!

@manosim Oh good stuff, now I got it. I missed the message popping up. Thanks a lot, this is really helpful.


update jck build xml to use platform info

jck test needs platform info for compilation and running
the platform info is auto-generated by TKG

fixed:#335
Signed-off-by: Tianyu Zuo<EMAIL_ADDRESS>

This PR is depending on https://github.com/eclipse/openj9/pull/1560
Reviewer: @llxia
Reviewer: @smlambert


separate tls_start hooks for client and server, fixes #4665, refs #4547

Description
Tests pass and I did a smoke test with one website.
I think this also made the internal code cleaner, there were multiple if/else blocks for these two cases.
There's one open question that only you can decide: does it make sense that TlsStartData is used for both hooks? Or is something about that superfluous?
Checklist

[x] I have updated tests where applicable.
[ ] ~I have added an entry to the CHANGELOG.~ Basically "New Proxy Core (@mhils)"

I'll accept :cake: or :broccoli:

You have self-identified yourself as a competent proxy core contributor now and have no more excuses

this was mostly shift+ctrl+f, ctrl+c and ctrl+v :smile:

You have self-identified yourself as a competent proxy core contributor now and have no more excuses

this was mostly shift+ctrl+f, ctrl+c and ctrl+v 😄

Yes, this is exactly how it works for me as well. 😛

Yes, this is exactly how it works for me as well. stuck_out_tongue


BPCJ-6 As a developer, I want to be able to use bytepushers-common-js-package module in a require js app so that I can verify the module is require js compliant.

[ ] We want to import the package using JSPM from the client project
[ ] We want to use the code in a client require js project
[ ] Use the code in a web page

Team updated code to support this feature.


Sideeffect when using the "version" package

There is a package named "version" on pub. Declaring it as a dependency in the pubspec.yaml looks like "version: ^3.0.2". This causes the versioncode-bump plugin to not only update the real version in the pubspec, but also this dependency. So:
version: 1.0.1+15
dependencies:
  version: ^3.0.2

becomes:
version: 1.0.1+16
dependencies:
  version: 1.0.1+16

Hey, great catch! Will look into it soon!

@czaefferer I have published a new release! Please update your Fastlane plugin to make use of the fix!


Remove requirement to extend base adapter

Makes it easier and dependency-free creation of configuration adapters

Coverage increased (+0.02%) to 98.969% when pulling b97e991f0ac58922982d5d8ce3f4dca30e2bf233 on WoLfulus:master into 04d7dbc9fc502234aef890cefa1e5457f8720828 on idwall:master.

Coverage increased (+0.02%) to 98.969% when pulling 9d0ce817fe8ad7d6063a7c9379cb47e3ec011a8c on WoLfulus:master into 04d7dbc9fc502234aef890cefa1e5457f8720828 on idwall:master.


Distinguishable highway=*_link

Description
It would be great if the ways tagged with highway=*_link were visually differentiated from the corresponding ways marked with highway=*.
This can be achieved by making the highway=*_link ways narrower than the corresponding highway=* ways.
Now, both highway=*_link and highway=* have the same line width and visually it is difficult to distinguish them from each other, you need to look at the properties of each of them to find out which line indicates which type of road.
Screenshots
Location on the screenshot - https://www.openstreetmap.org/edit#map=19/52.29335/4.71532

If I get it right the code is here
https://github.com/openstreetmap/iD/blob/1ee45ee1f03f0fe4d452012c65ac6ff7649e229f/modules/osm/way.js#L105-L115

Good idea. Was on the way to add a similar render request.


“Azure IoT Tools” extension not display in VSCode menu after install.

OS: windows10
Azure IoT tools :0.0.3-rc
step:
1.open VS Code , here only Azure Account  has already installed
1.install Azure IoT tools from VSIX
2.After installing successfully,  check “Azure IoT Tools”, “Azure IoT Toolkit”, “Azure IoT Device Workbench” and “Azure IoT Edge” are not display in VS Code
and there is no message to reminder user to reload VS Code

VS Code issue


Unusually High CPU While Fetching Mirrors

I'm noticing 80-100% CPU utilization during the fetching process for mirrors (Server 2016 Core Eval).
Is anyone else experiencing this?  Is there an inefficiency in the CUI download indicator, or is this a bug specific to the OS/VM technology that I am on?
It doesn't seem to cause any major problems in a development environment, but for a production system, this risks the chance of stealing the resources from elsewhere.  May be all or part of the cause for the Anti-Malware executable acting up mid-install (e.g. possibly related to #1388).

I noticed that downloads are significantly slower with scoop than with a browser. I have ~10% CPU (maybe 1 of 8 HT cores?) usage on the powershell process.
Seems more than it should be. Need to investigate

Yeah I have noticed this as well. With the work I was doing with the
progress bars I was working towards being able to switch out the downloader
for something else if needed. Perhaps this could be user configurable.
On Tue, Mar 21, 2017 at 8:13 AM Rémy<EMAIL_ADDRESS>wrote:

I noticed that downloads are significantly slower with scoop than with a
browser. I have ~10% CPU (maybe 1 of 8 HT cores?) usage on the powershell
process.
Seems more than it should be. Need to investigate
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lukesampson/scoop/issues/1389#issuecomment-287899698,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0QgjI6CsS2xmrDlBhszwcXlJmgqDeKks5rnuvcgaJpZM4MiCGF
.

I've found that commenting out the download cursor logic fixes the CPU spikes introduced with the download indicator.  There are still a few other spikes, but this helps.
The cursor draw routine must have an expensive call in it although I think it can be improved.
https://github.com/lukesampson/scoop/blob/master/lib/install.ps1#L215-L252
If I'm reading this correctly:

The download indicator is updated with the buffer; each 2,048 B
If my math is correct... 100 MB = 48,828 executions of the draw routine.
Assuming we're interested in 1-100% indicator, this means on average, each percent is drawn about 500 times.

I've never done CUI interface before, so I'm not prepared to write up a PR just yet, but I think drawing the indicator less often will help remedy this problem.  There are likely other indicators that could benefit from less frequent updates.

Since I wrote the progress logic I'll have a look at optimising it a bit.
On Tue, Mar 21, 2017 at 2:45 PM Tres Finocchiaro<EMAIL_ADDRESS>wrote:

I've found that commenting out the download cursor logic
https://github.com/lukesampson/scoop/blob/master/lib/install.ps1#L167
fixes the CPU spikes introduced with the download indicator. There are
still a few other spikes, but this helps.
The cursor draw routine must have an expensive call in it although I think
it can be improved.
https://github.com/lukesampson/scoop/blob/master/lib/install.ps1#L215-L252
If I'm reading this correctly:

The download indicator is updated with the buffer; each 2,048 B
If my math is correct... 100 MB = 48,828 executions of the draw
routine.
Assuming we're interested in 1-100% indicator, this means on
average, each percent is drawn about 500 times.

I've never done CUI interface before, so I'm not prepared to write up a PR
just yet, but I think drawing the indicator less often will help remedy
this problem. There are likely other indicators that could benefit from
less frequent updates.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/lukesampson/scoop/issues/1389#issuecomment-287968868,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0Qgn5UXAdtMFUjVDsab8X8E-hwE67Bks5rn0f0gaJpZM4MiCGF
.

There are still some serious performance problems with the download process.
Please see right-most edge...
With $last = dl_onProgress $totalRead $last

Without $last = dl_onProgress $totalRead $last

Can you try increasing the timeout to see if that helps?
On Thu, Mar 23, 2017 at 12:36 PM Tres Finocchiaro<EMAIL_ADDRESS>wrote:

There are still some serious performance problems with the download
process.
Please see right-most edge...
With $last = dl_onProgress $totalRead $last
[image: image]
https://cloud.githubusercontent.com/assets/6345473/24227939/47d93880-0f47-11e7-88be-b3a839fd0652.png
Without $last = dl_onProgress $totalRead $last
[image: image]
https://cloud.githubusercontent.com/assets/6345473/24227969/7b2511c8-0f47-11e7-8519-2e2e97251aea.png
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/lukesampson/scoop/issues/1389#issuecomment-288591407,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0QglYhtvuoRosG2NUhJuIxAH5k89bRks5rocyqgaJpZM4MiCGF
.

I changed it to 1 second (1000 ms) same problem.

Perhaps it has to do with the number of times the event is thrown, regardless of how often we draw to the screen.

I'm probably not the best person to test this, because my machine is a beast (i7-5820k /w 64GB RAM)

What if you do call $last = dl_onProgress $totalRead $last but you make the function just return?

Perhaps it has to do with the number of times the event is thrown, regardless of how often we draw to the screen.

I think it's a factor, but it's not a smoking gun.  Yes, this still exposes the performance problems, but so does moving the $delta directly into the while {...}.
I was able to eradicate it by using a KB counter (e.g. byte.length * 100), but on slow connections with very small packages (e.g. 'awk'), it doesn't really show enough progress (the timer is ideal).
Still trying things....

@deevus I've created a PR #1394 which seems to fix the problem.  It appears many things can spike the CPU of powershell.exe, namely 1. New date instantiations.  2. Frequent function calls 3. Frequent screen updates.
By using a stopwatch, it seems to fix the problem.
I blindly reverted your 01d9b95 but there is a formatting change that gets reverted.  Let me know if you need that back in.

For a visual...
Before #1394

After #1394

Oh this ticket is tree years old and I have exact two issues.
i installed it today, slow downloading and hight cpu usage.


Workspace classes

Workspace classes should be described in detail (why they exist and what parameters can be set).
The information should explain the maximum limits based on the hardware node availability in the cluster.
GPU availability should be highlighted.
Overprovisioning should be explained - how it works and the pros and cons of setting the overprovisioning factor.
https://www.gitpod.io/docs/configure/workspaces/workspace-classes

The overprovisioning factor allows a higher density of workspaces per hardware node in the cluster. This lowers the "request" values than the actual "limits." The provisioner will create more workspaces than would be possible, counting on the fact that now all of the workspaces will use all of the given resources.

The cons of setting the overprovisioning factor are that if the actual usage exceeds the node hardware resources, unexpected workspace issues may occur (like instant workspace eviction from the node).


icons!

what title says is what it is

If this doesn't need to be merged immediately, @NetOperatorWibby is currently working on a project to source assets like this from the same origin so that they're not littered repeatedly throughout our repos.
@eukreign would it be tricky to source these from https://github.com/lbryio/design? The two of you should discuss.

@kauffj , i believe @tzarebczan really wants this in the current release. we can change it later. (in fact, all of these icons are from this same repo, the folder was deleted before and I just brought it back).

:+1:


Tarballs are not delted after backup

Container backups should be deleted from /tmp dir after (un)sucessfull transfer to backup destination.

:tada: This issue has been resolved in version 0.10.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add tsconfig exclude validation

Changes are visible to end-users: no
Test plan

New test cases added

Resolves: https://github.com/aspect-build/rules_ts/issues/644
By adding a validation to the tsconfig file. If a out_dir parameter is set to the rule and the tsconfig file does not have the exclude key set the build will fail

After some discussions with @jbedard, I tested if the exclude is still needed at all for several parameters.
The tests made are as follows:
root_dir parameter testing (Latest rules_ts + default TS and node version)

root_dir
tsconfig rootDir
tsconfig exclude
Result

.
undefined
undefined
BUILD PASSED

./
undefined
undefined
BUILD PASSED

./src
undefined
undefined
BUILD FAILED - cannot find outputs

./src
undefined
[]
BUILD FAILED - cannot find outputs

./src
src
undefined
BUILD FAILED - cannot find outputs

./src
./src
undefined
BUILD FAILED - cannot find outputs

src
src
[]
BUILD PASSED

src
src
undefined
BUILD PASSED

src
./src
undefined
BUILD PASSED

src
undefined
undefined
BUILD PASSED

src
undefined
[]
BUILD PASSED

out_dir parameter testing (Latest rules_ts + default TS and node version)

out_dir
tsconfig outDir
tsconfig exclude
Result

out
Undefined
Undefined
BUILD PASSED

out
out
Undefined
BUILD PASSED

out
./out
Undefined
BUILD PASSED

Undefined
./out
Undefined
BUILD FAILED - cannot find outputs

Undefined
./out
[]
BUILD FAILED - cannot find outputs

Undefined
out
Undefined
BUILD FAILED - cannot find outputs

Undefined
out
[]
BUILD FAILED - cannot find outputs

.
Undefined
Undefined
BUILD PASSED

./
Undefined
Undefined
BUILD FAILED - ./ messes up outputs paths

./
Undefined
[]
BUILD FAILED - ./ messes up outputs paths

./out
Undefined
Undefined
BUILD FAILED - ./ messes up outputs paths

declaration_dir parameter testing declaration=True (Latest rules_ts + default TS and node version)

declaration_dir
tsconfig declarationDir
tsconfig exclude
Result

"dec"
"dec"
Undefined
BUILD PASSED

"dec"
Undefined
Undefined
BUILD FAILED - cannot find output declarations

Undefined
"dec"
Undefined
BUILD FAILED - cannot find output declarations

All tests were made before the changes in this branch. No tests show the need for exclude to be added at this point.
Is there a test case that still fails with the latest rules_ts?
And should we make these errors more friendly?
@jbedard


pydantic module version error

I have trying to install ML backend latest but unfortunately I am getting error:
`/home/marlo/.local/lib/python3.10/site-packages/pydantic/_internal/_config.py:341: UserWarning: Valid config keys have changed in V2:

'allow_population_by_field_name' has been renamed to 'populate_by_name'
warnings.warn(message, UserWarning)
/home/marlo/.local/lib/python3.10/site-packages/pydantic/_internal/fields.py:161: UserWarning: Field "model_version" has conflict with protected namespace "model".
You may be able to resolve this warning by setting model_config['protected_namespaces'] = ().
warnings.warn(
`

I tried to downgrade the pydantic module and run it again, but other problems occurred.
When I examined the ML backend codes, I saw that the response.py file uses this module. But I can't find a solution.

i have same issue too


Simple text component

Builds on top of #92
Required by https://github.com/bpmn-io/bpmn-properties-panel/pull/100

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: barmac:x: pinussilvestrusYou have signed the CLA already but the status is still pending? Let us recheck it.

I decoupled the branch from the nested lists so that it can be reviewed independently. Ready for review though.


define {algebra,canonical}_type traits

Change-Id: If010690f453c1968e5c9792ea402a0e79fd8f8d8

Codecov Report
Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 48.97%. Comparing base (0b13f8a) to head (9196eb8).

Files with missing lines
Patch %
Lines

rigid_geometric_algebra/blade_type_from.hpp
0.00%
1 Missing :warning:

Additional details and impacted files
@@                            Coverage Diff                             @@
##           Ib74377844e20fea3c7e5477bb23257c486928db3      #31   +/-   ##
==========================================================================
  Coverage                                      48.97%   48.97%
==========================================================================
  Files                                             17       17
  Lines                                            147      147
  Branches                                           2        2
==========================================================================
  Hits                                              72       72
  Misses                                            74       74
  Partials                                           1        1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


fixes "Kubernetes" typo in Readme.md

Changed "Kubernetess" to "Kubernetes".

My first pull request. Hope it's okay :)


fixed: not only TimeoutError will retry, ConnectionError will also

conn = StrictRedis(connect_timeout=3)

When raise ConnectionError, It took 6s!

Hi @lyncir -- just wanted to let you know that my org has recently forked aredis as it appears to have become unmaintained and we've merged in this pull request (and all other open PRs against the aredis repo); in case you find it useful, the fork is here and version 2.0.0 is on PyPI with your changes.


Legacy mode should not stretch by default if wrapping is enabled and columns are defined

In modern mode, grid cells will not stretch if a column count has been defined and wrapping is enabled.
In legacy mode however, grid cells will stretch if a column count has been defined and wrapping is enabled.
The decision to do this was to make the transition from version 3 to version 4 easier.
In hindsight I feel like this was the wrong call.
If you would like legacy mode to align with modern mode in terms of cell stretching, up vote this issue.
If there is enough interest then I will release a small version 5 patch that fixes this inconsistency.

I've decided to go ahead and do this

Fixed in version 5


RolePolicy Cannot set property 'owner' of undefined

error: TypeError: Cannot set property 'owner' of undefined
    at module.exports (/node_modules/sails-permissions/dist/api/policies/RolePolicy.js:43:34)

This doesn't seem to work
if (!_lodash2['default'].contains(['update', 'delete'], action) && req.options.modelDefinition.attributes.owner) {
    // Some parsing must happen on the query down the line,
    // as req.query has no impact on the results from PermissionService.findTargetObjects.
    // I had to look at the actionUtil parseCriteria method to see where to augment the criteria
    req.params.all().where = req.params.all().where || {};
    req.params.all().where.owner = req.user.id;
    req.query.owner = req.user.id;
    _lodash2['default'].isObject(req.body) && (req.body.owner = req.user.id);
  }

where as this does
if (!_lodash2['default'].contains(['update', 'delete'], action) && req.options.modelDefinition.attributes.owner) {
    // Some parsing must happen on the query down the line,
    // as req.query has no impact on the results from PermissionService.findTargetObjects.
    // I had to look at the actionUtil parseCriteria method to see where to augment the criteria
    var params = req.params.all();
    params.where = params.where || {};
    params.where.owner = req.user.id;
    req.query.owner = req.user.id;
    _lodash2['default'].isObject(req.body) && (req.body.owner = req.user.id);
  }

That seems to fix it. I wonder how/when this broke down.

Didn't work for me. It seems to happen because "where" is actually a string and "owner" property is being assigned to literal value.

If you have come here looking for a solution and you are lazy like me and don't want to fork and npm install etc., copy RolePolicy.js in your apps policies folder and apply the fix mentioned above there...

@dottodot The provided fix isn't fixing actually, but simply disabling owner policy. The previous code is actually bad practice as it expects req.params.all() to always return the same object. This expectation isn't backed by any specification (checked docs for expressjs as well as sailsjs on this). Therefore the code is hackish and error-prone.
Try this to prove my assumption:
console.log( req.params.all() === req.params.all() );

In my case this is logging false and so documenting that invoked method is actually providing copy of req.params data rather than any actual storage on parsed parameters. By calling it three times in falsy code all writes operate on different objects. However, this code tries to modify req.params for a reason here: to use it somewhere else. Your fix seems to be working but comes with different semantics. It is still working on a copy of req.params thus not modifying the original data. Try this after your fixing code to illustrate that:
console.log( req.params );

Guess it doesn't contain where unless some parameter named where was found in actually requested URL. So, your code isn't adjusting req.params either but qualifying some local-only variable which isn't used afterwards. Your fix is thus equivalent to simply removing the two changed lines completely.
Here comes the full proof:
    console.log( req.params.all() === req.params.all(), req.params, req.params.all() );
    var params = req.params.all();
    params.where = params.where || {};
    params.where.owner = req.user.id;
    console.log( req.params, req.params.all() );

So, how to fix this? Neither way is correct. Actually sails-permissions has to support such implicit provision of where parameter using some custom data injected into req. Other files relying on parameter req.params.where need to merge that parameter with custom data injected here.

I also stumbled upon this issue, it actually happens for me every time i try to call the /user/me route without being admin (so you are the owner of the resource). So quite a prominent use-case I think ...

++


Divide the project to apps - DO NOT MERGE

#33

We need to add the following lines to falcon/setting.py
INSTALLED_APPS = [
'Employees.apps.EmployeesConfig',
'Manager.apps.ManagerConfig',
'Task.apps.TaskConfig',
]

# Run database migrations pipenv run python manage.py migrate
This line should be added to the setup.sh to run the migrations when using vagrant up

@aradz1997 , @orzionpour Done

@mgold1234 @natifridman @nunnatsa can you please CR?

@AvivLiberman please edit the PR description. Please explain what this PR do, and why is it needed. Description like #33 won't help the reviewers, and more import, won't help you in the future when tou'll try to remember what was changed in this PR and why it was done, while trying to debug an issue on the customer site, in the middle of the night, on weekend.

@nunnatsa it wasn't my PR - I have opened it because @avraham1992 got a mess one

@AvivLiberman, but for someone that open this PR #33 is not clear

@mgold1234 you are right, I think that this PR include 2 tasks in it:

#25
#23

And I don't think the structure is good. I will open new one

@AvivLiberman , why do you think that the structure is not good?


404 /angular-2-local-storage not found and systemjs.config.js

Hi,
I had to add
map {
    ...,
    'angular-2-local-storage': 'npm:angular-2-local-storage/dist'
},

and
packages: {
    ...,
    'angular-2-local-storage': { main: './angular-2-local-storage.js', defaultExtension: 'js' }
}

to get angular-2-local-storage work as documented.
Otherwise I got 404 for /angular-2-local-storage requests.
Using v0.0.20 from via npm install.
I'm relatively new to all this npm and SystmJS stuff (been living in a cave for about five years now) so I just wanted to know if this is a "it's not a bug, it's a feature" case.

We're using WebPack now with the latest angular-cli. However when we were on the older version, we had to add similar config to what you have above for most of our 3rd party dependencies.
I've updated the documentation to reflect this. For reference, here is the original notes from README.md:

Add the following to your map and packages arrays in src/system-config.ts:
    const map: any = {
        'angular-2-local-storage': 'vendor/angular-2-local-storage'
    };
	const packages: any = {
        'angular-2-local-storage': { main: 'index.js', defaultExtension: 'js' }
    };

And then add the following to vendorNpmFiles in angular-cli-build.js:
    vendorNpmFiles: [
        'angular-2-local-storage/**/*.js'
    ]

For me with angular2 example project and systemjs works:
const map: any = {
'angular-2-local-storage': 'vendor/angular-2-local-storage/dist'
};

hello can you please describe me how to add this component in my module class. I have tried as mentioned in the https://www.npmjs.com/package/angular-2-local-storage but did not worked for me.
error:
(SystemJS) XHR error (404 Not Found) loading http://localhost/meServer/node_modules/angular-2-local-storage/dist/angular-2-local-storage.js


Use latex in noise documentation

Replace images in docs/noise.md
Fix docstrings omitting the $$ to activate latex parsing

Fixes https://github.com/quantumlib/Cirq/issues/1552

Examples of output:

Dave was using Latex, but with a few missteps like -> instead of \rightarrow.


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/client-writers
/assign knative-sandbox/client-writers
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/client 712e0e4...4470416:
  > 4470416 upgrade to latest dependencies (# 1411)
  > 5892b7c upgrade to latest dependencies (# 1405)
bumping knative.dev/eventing-kafka d5c68b7...604eeb3:
  > 604eeb3 upgrade to latest dependencies (# 785)
  > 1f62e23 upgrade to latest dependencies (# 784)
  > 8274025 Update community files (# 776)
  > dc7825a Add receiver/dispatcher labels to Pods as well as Deployments (# 783)
  > e2e9329 upgrade to latest dependencies (# 780)
  > d4fd0a1 [distributed KafkaChannel] Kafka AdminClient Error Handling (# 782)
bumping knative.dev/pkg 889b567...552bbc1:
  > 552bbc1 Support the webhook serving over non-TLS. (# 2204)
  > 64ab22b k8s-service-trailing-slash-fix (# 2178)
  > c367a9d Drop Client as it is only used in tests (# 2203)
  > bb4aaf0 Ignore special errors in codegen for events (# 2202)
  > 3826bb2 Add a new mechanism for requeuing a key. (# 2201)

/retest

The failed tests are caused by go 1.15. I'll bump it to align with client and rest of Knative world.

/retest


Interference when using with Mongoose

I'm using this library in conjunction with Cesanta's Mongoose library in order to serve html and connect to an MQTT broker at the same time. Both libraries work independently, but together they don't.
I'm getting this error:
I (61964) MQTT_CLIENT: Sending MQTT CONNECT message, type: 1, id: 0000
E (61965) MQTT_CLIENT: Writing failed, errno= 4
I (61966) MQTT_CLIENT: Error MQTT Connected
I (61972) MQTT_CLIENT: Reconnect after 10000 ms
I (61976) MQTT_SAMPLE: MQTT_EVENT_DISCONNECTED

In this case the HTTP server works, but after a while the MQTT client connects and the HTTP server stops working.
I've tried numerous things but nothing seems to work.
Stopping the mg_mgr_poll, which polls for HTTP request, works but then of course the HTTP server doesn't respond.
I think the 2 sockets are interfering.
Thanks in advance

@nathanprins Please try this fix:
https://github.com/tuanpmt/espmqtt/issues/48#issuecomment-393199625

That worked a treat! Thank you very much. Made my day!


Suits only show up for host

Suits seem to appear to show up just for the host, the suit rack is empty when everyone else looks at it. they can see the suits the host is wearing but cant select one

https://github.com/x753/Lethal-Company-More-Suits/issues/2#issuecomment-1817803279
Are you using More Company?

More Company will update soon, or you can find the file on his discord.

#2 (comment) Are you using More Company?

yeah i am, guessing the update will fix it?

#2 (comment) Are you using More Company?

yeah i am, guessing the update will fix it?

Yeah, you can wait for the new update or go to the discord.
https://discord.com/channels/1174563521384697869/1175776312305123328/1175885143697793094

This issue seems to continue to persist.
Is there a known work-around? If so, could we post it here?


Laravel 10 upgrade

Hello,
I've notice that dates casting used in the models Subscription, Order and OrderItem has been removed from laravel 10:
https://laravel.com/docs/10.x/upgrade#model-dates-property
Thanks for your work

@F-Andre as soon as we offer laravel v10 support we will move the $dates properties to $casts


Support for loading, unloading and listing Redis Modules

Pull Request check-list
Please make sure to review and check all of these items:

[x] Does $ tox pass with this change (including linting)?
[x] Does travis tests pass with this change (enable it first in your forked repo and wait for the travis build to finish)?
[ ] Is the new or changed code fully tested?
[ ] Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.
Description of change
This is a continuation of @vamc19 's PR: https://github.com/andymccurdy/redis-py/pull/808

Codecov Report

Merging #1360 into master will decrease coverage by 0.07%.
The diff coverage is 62.50%.

@@            Coverage Diff             @@
##           master    #1360      +/-   ##
==========================================
- Coverage   92.76%   92.69%   -0.08%
==========================================
  Files          20       20
  Lines        6581     6597      +16
==========================================
+ Hits         6105     6115      +10
- Misses        476      482       +6

Impacted Files
Coverage Δ

redis/client.py
85.83% <40.00%> (-0.26%)
:arrow_down:

redis/connection.py
81.84% <100.00%> (+0.09%)
:arrow_up:

redis/exceptions.py
100.00% <100.00%> (ø)

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 67c2fca...7b4c8f6. Read the comment docs.

tested manually with this script:
import urllib.request
import redis
import os
import stat

urllib.request.urlretrieve(
    "https://github.com/RedisJSON/RedisJSON/releases/download/v1.0.4/rejson.so",
    "rejson.so")
st = os.stat("/home/vagrant/redis-py/rejson.so")
os.chmod("/home/vagrant/redis-py/rejson.so", st.st_mode | stat.S_IEXEC)
r = redis.Redis()
r.module_load("/home/vagrant/redis-py/rejson.so")
print(r.module_list())
r.module_unload('ReJSON')

the unload action fails because rejson has commands, and you can't unload a module with commands.

This code is not fully tested, and this fails the codecov checks.
The test idea we've had requires compiling a Redis module, which will make the testing a bit too complex for what this is worth.
Perhaps after we move to docker test env we can revisit the test.
For now I'm merging as-is @andymccurdy


Floyd-Warshall Algorithm

Hello , I'm a SWOC contributor . I would like to create a new issue .
The Floyd-Warshall algorithm is also known as All pairs shortest path  algorithm is used to find all pair shortest path problem from a given weighted graph.
In the end  it will generate a matrix, which will represent the minimum distance from any node to all other nodes in the graph.
The time complexity for this algorithm is O(V*3) --> Here V represents the number of vertices in the given graph .
I will provide the    C program     (explicit) for the above algorithm . The output not only consists of the result but also the step by step solution  .
The infinity is represented as 999
Can I contribute

Sorry @Abhilash1781, Floyd Warshall algorithm has been implemented in all four languages


add definition 2.4.10, 2.5.8, 2.6.6, 2.7.1 and ruby 2.4 EOL

https://www.ruby-lang.org/en/news/2020/03/31/ruby-2-4-10-released/
https://www.ruby-lang.org/en/news/2020/03/31/ruby-2-5-8-released/
https://www.ruby-lang.org/en/news/2020/03/31/ruby-2-6-6-released/
https://www.ruby-lang.org/en/news/2020/03/31/ruby-2-7-1-released/
https://www.ruby-lang.org/en/downloads/branches/

Thank you!!

Hi, I dont get this new version when i try to upgrade it with homebrew, is it deployed ?

It first needs to be released here and then it can be bumped in homebrew. It's still only on master so far. I guess mislav will get around to that in a bit :)

@PatrickLerner 👍


Perplexity In theanoLM vs SRILM

Hi,
SRILM n-gram modelling toolkit, gives me two perplexities on my test set. The formula they use to calculate perplexity is given by:
 This gives us the geometric average of 1/probability of each token, i.e., perplexity. The exact expression is: 	ppl = 10^(-logprob / (words - OOVs + sentences))
This gives us the average perplexity per word excluding the </s> tokens. The exact expression is: 	ppl1 = 10^(-logprob / (words - OOVs))
I wanted to know, how to compare the perplexity that I get from theanoLM vs what I get from SRILM n-gram language model. One thing I can think of is to divide the ppl from SRILM by 10. What else? Just wanted to compare my LSTM LM built using theanoLM and n-gram model built using SRILM.
Thank you

First of all, make sure both models have exactly the same vocabulary. Otherwise the perplexities are not comparable. SRILM ignores OOV words when computing the perplexity. You get the same behaviour from TheanoLM, if you use --unk-penalty 0. If you have a high percentage of OOV words, I recommend using that during training also. Otherwise the training may be guided towards a network that just gives a high probability for the OOV token - the perplexity gets low but it won't be a good model.
TheanoLM includes sentence end tokens in the perplexity computation, so you should look at the "ppl" value from SRILM output.
Perplexity is not dependent on the base. SRILM uses base 10 logprobs, so that's why base 10 exponent is taken in the above formula. TheanoLM uses the natural logarithm, but you only need to care about it if you're comparing logprobs. Then you should use --log-base 10, e.g.
theanolm score model.h5 test.txt --output word-scores --log-base 10

Use --log-base 10 also if you're rescoring an n-best list generated using SRILM!

Thanks for the reply.
I did some calculation as you suggested by you.

SRILM: PPL calculation using a 4gram LM trained on 130M tokens. The command used to calculate perplexity.

ngram -debug 2 -order 4 -lm mgb.o4g.kn.gz -vocab /data/sls/qcri-scratch/sameer/language_modelling/theanoLM/data/rnnlm_data/input.vocab -limit-vocab -ppl /data/sls/qcri-scratch/sameer/language_modelling/theanoLM/test.txt
Vocab argument given here, is the vocab that I used to train the LSTM language model.
Perplexity is given by:
5002 sentences, 60169 words, 8754 OOVs
0 zeroprobs, logprob= -156679 ppl= 598.63 ppl1= 1115.17

TheanoLM: The command used to train the LSTM LM on 4M tokens is as given below:

theanolm train model.h5 validation-data.txt --training-set training-data.txt --vocabulary input.vocab --architecture lstm300
Perplexity calculation command:
theanolm score model.h5 test.txt --output word-scores --log-base 10
Perplexity is given by:
Number of sentences: 5002
Number of words: 70173
Number of predicted probabilities: 65171
Cross entropy (base e): 5.615544113890271
Cross entropy (base 10): 2.4387998215468305
Perplexity:<PHONE_NUMBER>816429
The question is:
Do you think this is the right way to compare the two models?
If it is, I am finding it hard to believe that a 4gram language model trained on 130M tokens is giving higher ppl than a LSTM model trained on just 4M tokens.

The difference in perplexity is so big that I agree with you, there has to be a mistake somewhere. Also, TheanoLM reports 70173 words and 70173 - 5002 = 65171 predicted probabilities (sentence starts excluded) and SRILM reports 60169 words.
You're using --limit-vocab with SRILM, meaning that <unk> is discarded from the language model.
You should use --unk-penalty 0 with TheanoLM, so that it too excludes <unk> from perplexity computation.
Both tools should compute the probability of the same words, so the number of predicted probabilities should match. To debug what's going on, I would start from a smaller test set (maybe just one sentence that also includes OOV words) and compute word scores with both tools (--output word-scores with TheanoLM and -ppl test.txt -debug 2 with SRILM). Then you can see if the numbers are in the same ballpark.

Thank you for the reply and sorry to bother you so much with this.
So, I calculated the score again with --unk-penalty 0 and now the ppl with LSTM is:
Number of sentences: 5002
Number of words: 70173
Number of predicted probabilities: 56304
Cross entropy (base e): 6.153225547136662
Cross entropy (base 10): 2.6723119010275695
Perplexity:<PHONE_NUMBER>3500837 (up from 270)
Looking at one sentence with an oov word.
SRILM outputs:
msAr Al<SlAH AlsyAsy fy Almgrb ElY mHk AlAntxAbAt AlmHlyp
p( msAr |  )         = [2gram] 8.29459e-05 [ -4.0812 ]
p( Al<SlAH | msAr ...)  = [2gram] 0.00205024 [ -2.6882 ]
p( AlsyAsy | Al<SlAH ...)       = [3gram] 0.166815 [ -0.777764 ]
p( fy | AlsyAsy ...)    = [3gram] 0.0872803 [ -1.05908 ]
p( Almgrb | fy ...)     = [3gram] 0.00236401 [ -2.62635 ]
p( ElY | Almgrb ...)    = [3gram] 0.0145742 [ -1.83641 ]
p(  | ElY ...)     = [OOV] 0 [ -inf ]
p( AlAntxAbAt |  ...)      = [1gram] 0.000176341 [ -3.75365 ]
p( AlmHlyp | AlAntxAbAt ...)    = [2gram] 0.00657387 [ -2.18218 ]
p(  | AlmHlyp ...)  = [3gram] 0.0397053 [ -1.40115 ]
1 sentences, 9 words, 1 OOVs
0 zeroprobs, logprob= -20.406 ppl= 185.068 ppl1= 355.426
TheanoLM outputs:
Sentence 5
log(p(mnETf | )) = -5.457753244181191
log(p(yjmE | mnETf, )) = -3.471448757439608
log(p(EAmp | yjmE, mnETf, )) = -4.334170511210176
log(p(AlmgArbp | EAmp, yjmE, mnETf, ...)) = -4.860515910641084
log(p(ElY | AlmgArbp, EAmp, yjmE, ...)) = -1.663495796750342
log(p(>hmyth | ElY, AlmgArbp, EAmp, ...)) = -4.4424301866621825
log(p( | >hmyth, ElY, AlmgArbp, ...)) = -1.5500514724751076
Sentence perplexity: 39.75906966574181
I must also say that I have been using the 4gram model for lattice rescoring which is trained on the full text that I have and I have been getting very good results with WER reduction, so I have little reason to doubt that something went wrong when I was building 4gram language model. So, my guess is something went wrong while I was building the LSTM language model.
Any suggestions or comments?

I spotted one bug: There was an unnecessary base conversion, when computing the sentence perplexity. I fixed it already, but I didn't have time to test it. So in the above "word-scores" output, 10.33876... is incorrect. If you update to the latest version in Git, you should get 216.72... That's a bit worse than 185.068 given by SRILM. But that bug shouldn't affect the overall perplexity computation.
The probabilities that you get from SRILM and TheanoLM are similar, so I'm confident that they're computed correctly. The only suspicious thing I still see is that the tools report different number of words:
TheanoLM: 70173 tokens - 5002 sentence starts - 8867 OOVs = 56304 tokens
SRILM: 60169 words, 8754 OOVs
Are you sure you gave both tools the same test data? If you can't find the cause of that mismatch, you can start from one sentence and grow the test data until you find a sentence for which TheanoLM and SRILM report different word or OOV counts.
One more thing: You have a relatively high percentage of OOVs and they have a large effect on the perplexity. I suggest either excluding OOVs during training (--unk-penalty 0) or giving a constant score (e.g. --unk-penalty -5). Otherwise the OOVs may skew the training process.

thanks. Yes, I gave them both the same test data. I will try to find the
cause of the mismatch.
I have now started training with ( --unk-penalty 0 )
Hope to see some good results.
On Mon, Jun 6, 2016 at 12:07 AM, Seppo Enarvi<EMAIL_ADDRESS>wrote:

I spotted one bug: There was an unnecessary base conversion, when
computing the sentence perplexity. I fixed it already, but I didn't have
time to test it. So in the above "word-scores" output, 10.33876... is
incorrect. If you update to the latest version in Git, you should get
216.72... That's a bit worse than 185.068 given by SRILM. But that bug
shouldn't affect the overall perplexity computation.
The probabilities that you get from SRILM and TheanoLM are similar, so I'm
confident that they're computed correctly. The only suspicious thing I
still see is that the tools report different number of words:
TheanoLM: 70173 tokens - 5002 sentence starts - 8867 OOVs = 56304 tokens
SRILM: 60169 words, 8754 OOVs
Are you sure you gave both tools the same test data? If you can't find the
cause of that mismatch, you can start from one sentence and grow the test
data until you find a sentence for which TheanoLM and SRILM report
different word or OOV counts.
One more thing: You have a relatively high percentage of OOVs and they
have a large effect on the perplexity. I suggest either excluding OOVs
during training (--unk-penalty 0) or giving a constant score (e.g. --unk-penalty
-5). Otherwise the OOVs may skew the training process.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/senarvi/theanolm/issues/13#issuecomment-223837710,
or mute the thread
https://github.com/notifications/unsubscribe/AHV3fZg9YcrAh6WDp60Tkmm1h0TZtpk9ks5qIzqXgaJpZM4ItXmx
.

--
conversation enriches understanding, but solitude is the school of genius.

Hi @sameerkhurana10 : quick question - you mentioned that the command you used to train on 4M tokens was:
theanolm train model.h5 validation-data.txt --training-set training-data.txt --vocabulary input.vocab --architecture lstm300.
Where did you generate "input.vocab" from?
I am trying to run a simple experiment as follows:
theanolm train model.h5 validation-data.txt --training-set training-data.txt
but always encountering this exception:
IncompatibleStateError: Vocabulary parameter 'words' is missing from neural network state.
Any thoughts @senarvi ?
Thanks!

@pranjaldaga: It sounds like the file model.h5 exists already, but is invalid. If the file exists, the program tries to continue training from the previous state. Try deleting it first.

back again.
i am still seeing the same behaviour. Here is a preliminary analysis.
trained an n-gram language model using SRILM, command:
ngram-count -text train.dat -order 3 -unk -map-unk "<UNK>" -kndiscount -interpolate -lm o3g.kn.gz
ppl command:
ngram -unk -lm o3g.kn.gz -ppl test.dat
ppl : 1063.3 , 00V: 1928
Trained two language models with theanoLM, one with --vocab and the other without.
without --vocab (the vocab is derived automatically by theanolm from the training data (I believe))
score command:
theanolm score model.h5 test-data.txt --output perplexity --exclude-unk
ppl : 2393.5 (believable compared to n-gram). model is trained using hsoftmax
with --vocab option. The model is word-blstm256-softmax. Vocab size is restricted to 40k most frequent words extracted from the training corpus.
score command:
theanolm score model.h5 test-data.txt --output perplexity --exclude-unk
ppl: 201 (hard to believe), oov: 5709
Any comments?

The vocabulary in your n-gram model is so large (all training words?) that there are only 1928 OOV test words, so the perplexity is higher. In the last case you have 5709 OOV test words, leaving all the low-probability words out of the perplexity computation. It's not hard to believe that perplexity is 201 with a small vocabulary. Do not compare perplexities unless you're using exactly the same vocabulary. Then you should get exactly same OOVs too.

okay, true.


HBASE-27257 Remove unnecessary usage of CachedBlocksByFile from RS UI

I kept around the old warning, but moved it to near the "View as Json" links, since that's where it makes sense now.
Here's how it looks on one of my prod regionservers:

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 32s
Docker mode activated.


Add LastPass 4.48.0

The old version (<IP_ADDRESS>) is remoted because the download URL doesn't change even if a new version has been released. Thus, the installers of the older versions won't pass the SHA256 checksum verification.
Microsoft Reviewers: Open in CodeFlow

The installer still asks for which browsers to install LastPass on - since user input is required here - validation-unattend-failed


Add course For python and add documentation in it

@arpit456jain  I want to add python course and its documentation under swoc'22 .

go ahead @khushi-purwar


Consider adding a symmetric version of commute in the definition of natural transformation

since we are in the mood of considering op of op being definitionally equal to the original definition, in the case of natural transformation, we might also need something like this:
https://github.com/agda/agda-categories/blob/9a9c4abda552657e973c600692cc2d3ffaa37520/Categories/NaturalTransformation/Core.agda#L37
in the opposite of a natural transformation, the commute proof is constructed by symming commute. the consequence is that, the op of op of a natural transformation is not definitionally equal to itself. to fix this, we shall add sym-commute in the same spirit as sym-assoc in the definition of Category.
in general, the rule of thumb is that, if an opposite can be defined by a definition, then it is a good idea to introduce redundancy to the original definition, so that op of op is the same as the original term. this is a good material in the paper.

indeed, this library has implemented this trick:
https://github.com/HoTT/HoTT/blob/35d9de1f587117cafebf7d7b1851bb177f173783/theories/Categories/NaturalTransformation/Core.v#L47-L48

Makes sense.   I wasn't expecting the same thing to make sense here too!

Since there are now a bunch of 'redundant' fields in many records, would it make sense to add 'smart constructors' for these records that fill in the defaults?
For example, for Category one could have a 'constructor' category that takes 8 arguments (for the non-redundant fields) and fills in the remaining two? Additionally, some of the arguments that Agda can infer from the others could be made implicit (e.g. Obj, or morphism equality).
WDYT?

I'm definitely in favour.

@sstucki
there has been such constructors, e.g. https://github.com/agda/agda-categories/blob/2d0a0cc0975e94a864ece5811308953f84e7f981/Categories/Category/Core.agda#L153-L154 , https://github.com/agda/agda-categories/blob/2d0a0cc0975e94a864ece5811308953f84e7f981/Categories/NaturalTransformation/Core.agda#L55-L56
If certain fields can be inferred, you can remove that field after pressing C-c C-r.

Oops, thanks @HuStmpHrrr, I had completely missed these. 😳
Yes, this is pretty much what I had in mind. And it's nice that one can use record syntax with these too.
The only thing I don't like are the names. xyzHelper seems a bit too generic. Maybe we can come up with a better naming convention? For example, for the record Category the auxiliary record could be named PlainCategory or BaseCategory? And the names of the 'wrappers' is probably even more important, as these will be more visible in actual code. We could even use a symbolic name to reduce the visual overhead. E.g. just category/nt/naturalTransformation or something generic, like 《_》?
I'm just brainstorming here, I'd love to hear other suggestions.

yeah helper might not be the best name. we can definitely change them.


Feature: Fork and make a Universal App that runs on Windows 10 and Phone

I can't find it on the store 😢

We are still working on it! Soon!
On Thu, Jul 13, 2017 at 7:51 AM, seriouz<EMAIL_ADDRESS>wrote:

I can't find it on the store 😢
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/shanselman/babysmash/issues/8#issuecomment-315101527,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAALTDDIRnrWWxOgedkXUppDKizHtUESks5sNi7jgaJpZM4EuKje
.

--
Scott Hanselman
Donate to fight diabetes: http://hnsl.mn/fightdiabetes


archive/zip: malformed archive may cause panic or memory exhaustion

Due to a pre-allocation optimization in zip.NewReader, a malformed archive which indicates it has a significant number of files can cause either a panic or memory exhaustion.
This was originally discoverd by OSS-Fuzz: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33912.
This is CVE-2021-33196.

Applying release-blocker and okay-after-beta1 labels based on my best understanding from #46241, please update if needed.

@gopherbot please consider this for backport to 1.15 and 1.16 as this is a security issue.


Date and time localization ignores locale on nuxt generate

Version
nuxt-i18n: 6.18.0
nuxt: 2.14.6
Nuxt configuration
mode:

[x] universal
[ ] spa

Nuxt-i18n configuration
  i18n: {
    lazy: false,
    locales: ['en','es','fr','it'],
    strategy: 'prefix',
    defaultLocale: 'it',
    vueI18n: {
      fallbackLocale: 'it',
      messages: {
        en: { hello: 'Hello' },
        es: { hello: 'Hola' },
        fr: { hello: 'Salut' },
        it: { hello: 'Ciao' }
      },
      dateTimeFormats: {
        en: { long: { year: 'numeric', month: 'long', day: 'numeric', weekday: 'long' } },
        es: { long: { year: 'numeric', month: 'long', day: 'numeric', weekday: 'long' } },
        fr: { long: { year: 'numeric', month: 'long', day: 'numeric', weekday: 'long' } },
        it: { long: { year: 'numeric', month: 'long', day: 'numeric', weekday: 'long' } }
      }
    }
  }

Reproduction Link
https://github.com/jollycic/test-nuxt-i18n-date-localization
Steps to reproduce

Clone the repo and ``npm install`;
Run nuxt generate and wait for the task to complete;
Check ~/dist/en/index.html, ~/dist/es/index.html, ~/dist/fr/index.html, and ~/dist/it/index.html

What is Expected?
Both the message and the date should be localized accordingly on each page.
What is actually happening?
Only the message appears to be localized with the correct locale, while the date is always localized in English, no matter what locale has been set as default or fallback.
This behavior is inconsistent with the client side, where both the message and the date are localized correctly. This can be noticed when running in dev mode`. Does this hint to a possible concurrency issue?
I don’t know if this is a known or expected behavior, or if I have done anything wrong with the module configuration, in which case I apologize.

vue-i18n implements $d using the Intl.DateTimeFormat Javascript API and that API only supports the EN locale in Node 12 and lower. So you'd need to use at least Node 13 (ideally 14) to have proper support for that API on the server-side.

vue-i18n implements $d using the Intl.DateTimeFormat Javascript API and that API only supports the EN locale in Node 12 and lower. So you'd need to use at least Node 13 (ideally 14) to have proper support for that API on the server-side.

Thank you very much, I wasn’t aware of this.

Thank you very much, I wasn’t aware of this.


Problem with rename the App name

I rename the App via
php artisan app:name Pollr
When I install via voyager:install something wrong with service call. I checked in directory
Vendor\tcg\voyager\src\controllers
most of them still called App as the prefix, why not adapt to the new App Name?
use {App}\Http\Requests;
use {App}\Http\Controllers\Controller;

I'm open for pull requests.

Did we have the method getNamespace?

Apologies. That was a typo that slipped past. It has since been resolved. If you run composer update, that should resolve it.

It works, 😃 😃 😃