DJOSER settings dictionary

I believe the docs to be outdated:
https://djoser.readthedocs.io/en/latest/settings.html
DJOSER = {
    'PASSWORD_RESET_CONFIRM_URL': '#/password/reset/confirm/{uid}/{token}',
    'ACTIVATION_URL': '#/activate/{uid}/{token}',
    'SEND_ACTIVATION_EMAIL': True,
    'SERIALIZERS': {},
}

Unless what I am using is invalid (I'm using string formatting).
DJOSER = {
    'PASSWORD_RESET_CONFIRM_URL':   '{}/password/reset/confirm/{}/{}'.format(VUE_ROOT_DOMAIN, '{uid}', '{token}'),
}

I receive the following error:
AttributeError at /auth/v1/hug/password/reset/ 'Settings' object has no attribute 'PASSWORD_RESET_CONFIRM_URL':

Please post the full Trackback - click the "switch to copy-and-paste version" and use the result.

:thinking: I once answered similar question on StackOverflow. Plus, try using djoser-2 which is cleaned up - maybe this bug is already solved there. If not, please do provide the traceback.


Re-enable CRIU tests by not using overlayfs snapshotter

While the issue hasn't been fixed in the kernel yet, we can workaround
the issue by not using overlayfs snapshotter.
Fixes #3930.
Signed-off-by: Kazuyoshi Kato<EMAIL_ADDRESS>

Hmm, let me check the kernel version on the GitHub Actions' Ubuntu.

Ubuntu 14.04 uses Linux fv-az54-676 5.4.0-1031-azure #32~18.04.1-Ubuntu SMP Tue Oct 6 10:03:22 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux.

I don't think this will work based on ongoing commentary in https://github.com/checkpoint-restore/criu/issues/860 (see this comment). The upstream bug is confusing as it has been marked fixed at least once or twice, but is clearly still an issue.
The recommendation in https://github.com/checkpoint-restore/criu/issues/1239#issuecomment-713331969 might be worth considering--should we run just the checkpoint/restore tests to make sure our code is still working by running a quick test with a different graphdriver?

Thanks @estesp. How about running the tests with multiple different snapshotters? I'm bit concerned to move containerd's tests from overlay to let's say devmapper because of criu.

Yes, I think we can build a small action that only runs the criu tests with a native/devicemapper snapshotter and let the rest of the testsuite continue using overlay.

container_checkpoint_test.go:142: type with url : not found: unknown is coming from https://github.com/containerd/containerd/blob/f1a469a03578b061af0991228fdd3171a75fc2c8/runtime/v2/runc/container.go#L53.

@estesp Could you take a look? Seems like CRIU has been broken.

Sorry @kzys this needs a rebase due to the PR which moved *_test.go from the root being merged.
Also, thinking about the time cost of having yet another pass through make integration just to pick up the checkpoint tests:
What about renaming the last test in the checkpoint test file here to start with TestCheckpoint and then you could pass EXTRA_TESTFLAGS="-run TestCheckpoint" to your make integration and only have the handful of checkpoint tests run rather than adding 2-3 minutes to all of the runc+Linux integration combinations in CI?

@estesp Sounds good to me. Let me update the PR.

Rebased! Not so sure why "CGroupsV2 and SELinux Integration" is failing here.

Rebased! Not so sure why "CGroupsV2 and SELinux Integration" is failing here.

429 Too Many Requests. ... we're trying to work on this.. it's the new docker.io pull rate limits

@estesp Can you take a look?

/ok-to-test


Theme looks different (too much purple) on Ubuntu

The theme looks a bit too purple than the screenshot in README. Is this what its suppose to look like (see screenshot below)?

I love this theme because it's like One Dark but with a hint of purple but this is too much.
Using VSCode for Ubuntu (don't think this matters too much)

Spooky, the screenshot that I took looks perfect but its different than on my VSCode. I'm not sure how to show you what's wrong then.

@ketozhang this happens to me too! Most of the time, this is has more to do with monitor/screen you are using. I have my laptop and work monitor side-by-side most days, and there's a surprisingly big difference in how different the colors look.

@ketozhang thanks for reaching out! My bad, I'm just seeing this. Also, thanks @Jaballadares for the answer.
I think this is what you're experiencing, @ketozhang. Could you consider that and let me know what you find?
Cheers!


Update Comanhua URL

Checklist:

[X] Updated extVersionCode value in build.gradle for individual extensions
[ ] Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
[ ] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[ ] Added the isNsfw = true flag in build.gradle when appropriate
[ ] Have not changed source names
[ ] Have explicitly kept the id if a source's name or language were changed
[ ] Have tested the modifications by compiling and running the extension through Android Studio
[ ] Have removed web_hi_res_512.png when adding a new extension

Please review and approve it to merge.


Support multiple custom versions of hadoop by generate-tarball

Support multiple custom versions of hadoop when tarballing with the generate-tarball.sh
#12406 only support single hadoop version.

Can one of the admins verify this patch?

Codecov Report

Merging #12925 (df23094) into master (8994f55) will decrease coverage by 25.54%.
The diff coverage is n/a.

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

@apc999 do you want to glance over this before merging?

thanks @liupan664021

alluxio-bot, merge this please


[MEP] Enable Entitlements + Operator

This PR aims to address this scenario: when an experience column is authored to like desktop & cc-all-apps-any in MEP Manifest, right now, unless there's coincidently another column like cc-all-apps-any, the variant desktop & cc-all-apps-any will never get selected. Reason is that current logic in getPersonalizationVariant() for splitting variant name doesn't include &, so hasEntitlementTag will stay false, leading to no entitlement resolution. The code change tries to split by & when building out variantInfo.allNames. It is used to check if any entitlement tags are used. variantInfo[name] is used for variant mapping and thus unmodified.
This bug might again be trickier to reproduce, due to Milo by default doesn't do entitlements when logged out, and IMS only working on very specific branch links. So on the feature branch, the page is in a deadlock situation, with MEP waiting for entitlements that will never be resolved. (added a catch for IMS error so entitlements will still resolve). But you can create a MEP experience like https://gnav--milo--adobecom.hlx.page/drafts/jinglhua/desktop-entitlements and https://main--milo--adobecom.hlx.page/drafts/jinglhua/desktop-ent.json and then use logs or breakpoints around variantInfo and confirm that entitlements not getting resolved currently. To verify my fix, do the same, and you should see that at least it tries to resolve (will be resolved to an empty array due to IMS).
Resolves: https://jira.corp.adobe.com/browse/MWPW-155314
Test URLs:

Before: https://stage--milo--adobecom.hlx.page/drafts/jinglhua/desktop-entitlements
After: https://mep-entitlements-operator--milo--adobecom.hlx.page/drafts/jinglhua/desktop-entitlements

i'll be adding UT on Monday

Looking good so far to me as well. Will check back after "not" support and unit test updates are ready

Hello friends @chrischrischris  @vivgoodrich @vhargrave, all comments are taken care of and changed lines are 100% covered by unit tests. Let me know if you find anything else!

und variantInfo and confirm that entitlements not getting resolved currently. To verify my fix, do the same, and you should see that at le

done the rebase!

I think I'm missing something.
are you reversing the value if there is a "not"?
like if they are in "cc-all-app-any" then "not cc-all-app-any" should return false
and I can't tell if you're doing that

Discussed the issue with Jingle and am no longer concerned about the handling of the "not" operator.


Add Mount Item Name Icon into ActionEffectSet.

Hi, In order to make Action Effect easy to use. I add Name and Icon for general showing.
Besides, Mount and Item are added for some case using.

Thank you!


What build previous version run with driver 470 ?

Hello.
Thanks for reading my topic.
Trying use the current build version not have hardware acceleration.
Here Ubuntu Linux 20.04.6 using geforce 600 series driver 470.
Perhaps is being required use updated drivers.
What build previous version have compatibility with driver 470 ?
Have an nice week.

4.4, 5.0 and 5.1 are built with legacy ffnvcodec versions which support driver version 471.41 and higher.
master is always built against the latest codec headers, which currently need driver 522.25 or newer.

You are saying is possible tweak the build script to run ffmpeg 6 in driver 470 ?
Is an simple task ?
I am an Linux novice user.
The file below run in driver 470 ?
https://github.com/BtbN/FFmpeg-Builds/releases/download/latest/ffmpeg-n5.1-latest-linux64-gpl-5.1.tar.xz

You can build any version of ffmpeg with any version of the headers.
But obviously not multiple at a time, so a choice has to be made there.
Latest versions -> latest drivers
Old versions -> older drivers
If you want a different combination, you'll have to make a custom build yourself.
Nvidias documentation says 471.41 is the oldest supported driver for the 11.1 Video Codec headers, so you might have to update your driver a bit.

None of them are compatible with 470. 471 should work though, and is a supported legacy driver for your old card.
Any 5.1 or 4.4 build will work with driver 471 or newer.

The nvidia headers are in nvidia binary driver and distro driver PPA or in ffmpeg git source ?

Not sure what you're asking.
If you want to make a custom build that uses a specific version, you got to modify the ffnvcodec script in this very repo.


Question

Hey, I am studying http desync attacks and I ended up in your paper. I also saw a video of you talking about your research on the smuggling topic, very great job!
I have got one question: in the research you talked about the discrepancies among different entities that generally act as reverse proxy, cdn, waf, cache, web server etc... but in your graphes there are discrepancies assigned to pairs like reverse proxy <-> cache proxy. With this path, how you tested the request? I imagine it has to be also sent to a web server...
Can you please explain me how you handle such situation ?

Hi, Paolo.
It is very common for request paths to have two or more reverse proxies and origin server (i.e., a web server) at the end. If you can cause desync between any of two servers (e.g., two reverse proxies), you are already successful, you don't have to worry about the web server.

Okay I understand, thanks! Are you researching on the "future research" cited in the paper? Because I see this repo is maintained

We maintain this repo, mainly because of its versatility and various applications, not necessarily because I still research request smuggling.


how can I make the swag comment flexible in different environments?

how can I make the swag comment flexible in different environments?
for the local test I may use
// @Host <IP_ADDRESS>

for the server, I should use
// @Host <server public ip>

I don't want to manually change every time when deploying the project.

Some general API info can be set dynamically. you can follow like:
// programatically set swagger info
	docs.SwaggerInfo.Title = "Swagger Example API"
	docs.SwaggerInfo.Description = "This is a sample server Petstore server."
	docs.SwaggerInfo.Version = "1.0"
	docs.SwaggerInfo.Host = "petstore.swagger.io"
	docs.SwaggerInfo.BasePath = "/v2"


error in npm run generate:prerender

Hello
when i run npm run generate:prerender  i have this error :
ERROR { Error: Uncaught (in promise): TypeError: Cannot read property 'call' of undefined
TypeError: Cannot read property 'call' of undefined
at webpack_require (C:\Users\issam\Desktop\nest-nguniversal-demo\dist\prerender.js:145231:30)
at Function.requireEnsure [as e] (C:\Users\issam\Desktop\nest-nguniversal-demo\dist\prerender.js:145250:25)
at ɵ0 (C:\Users\issam\Desktop\nest-nguniversal-demo\dist\prerender.js:145445:38)
someone help me plz

Please, provide a minimal repository which reproduces your issue.

Hello,
same Issue on:

Windows 10
Node 10.17.0
NPM 6.12.0

I check out the code and run build:prerender.
Then i have an Error in generate:prerender step:
ERROR { Error: Uncaught (in promise): TypeError: Cannot read property 'call' of undefined TypeError: Cannot read property 'call' of undefined     at __webpack_require__ (c:\some_folder\dist\prerender.js:145231:30)     at Function.requireEnsure [as e] (c:\some_folder\dist\prerender.js:145250:25)     at ɵ0 (c:\some_folder\dist\prerender.js:145445:38)     at RouterConfigLoader.loadModuleFactory (c:\some_folder\dist\prerender.js:149622:39)     at RouterConfigLoader.load (c:\some_folder\dist\prerender.js:149607:35)     at MergeMapSubscriber.project (c:\some_folder\dist\prerender.js:148610:47)     at MergeMapSubscriber._tryNext (c:\some_folder\dist\prerender.js:88799:27)     at MergeMapSubscriber._next (c:\some_folder\dist\prerender.js:88789:18)     at MergeMapSubscriber.Subscriber.next (c:\some_folder\dist\prerender.js:85348:18)     at Observable._subscribe (c:\some_folder\dist\prerender.js:87360:24)     at resolvePromise (c:\some_folder\dist\prerender.js:2436:31)     at resolvePromise (c:\some_folder\dist\prerender.js:2393:17)     at c:\some_folder\dist\prerender.js:2497:17     at ZoneDelegate.invokeTask (c:\some_folder\dist\prerender.js:2007:31)     at Object.onInvokeTask (c:\some_folder\dist\prerender.js:80535:33)     at ZoneDelegate.invokeTask (c:\some_folder\dist\prerender.js:2006:60)     at Zone.runTask (c:\some_folder\dist\prerender.js:1779:47)     at drainMicroTaskQueue (c:\some_folder\dist\prerender.js:2185:35)     at process._tickCallback (internal/process/next_tick.js:68:7)     at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)   rejection:    TypeError: Cannot read property 'call' of undefined        at __webpack_require__ (c:\some_folder\dist\prerender.js:145231:30)        at Function.requireEnsure [as e] (c:\some_folder\dist\prerender.js:145250:25)        at ɵ0 (c:\some_folder\dist\prerender.js:145445:38)        at RouterConfigLoader.loadModuleFactory (c:\some_folder\dist\prerender.js:149622:39)        at RouterConfigLoader.load (c:\some_folder\dist\prerender.js:149607:35)        at MergeMapSubscriber.project (c:\some_folder\dist\prerender.js:148610:47)        at MergeMapSubscriber._tryNext (c:\some_folder\dist\prerender.js:88799:27)        at MergeMapSubscriber._next (c:\some_folder\dist\prerender.js:88789:18)        at MergeMapSubscriber.Subscriber.next (c:\some_folder\dist\prerender.js:85348:18)        at Observable._subscribe (c:\some_folder\dist\prerender.js:87360:24),   promise:    ZoneAwarePromise [Promise] {      __zone_symbol__state: 0,      __zone_symbol__value:       TypeError: Cannot read property 'call' of undefined           at __webpack_require__ (c:\some_folder\dist\prerender.js:145231:30)           at Function.requireEnsure [as e] (c:\some_folder\dist\prerender.js:145250:25)           at ɵ0 (c:\some_folder\dist\prerender.js:145445:38)           at RouterConfigLoader.loadModuleFactory (c:\some_folder\dist\prerender.js:149622:39)           at RouterConfigLoader.load (c:\some_folder\dist\prerender.js:149607:35)           at MergeMapSubscriber.project (c:\some_folder\dist\prerender.js:148610:47)           at MergeMapSubscriber._tryNext (c:\some_folder\dist\prerender.js:88799:27)           at MergeMapSubscriber._next (c:\some_folder\dist\prerender.js:88789:18)           at MergeMapSubscriber.Subscriber.next (c:\some_folder\dist\prerender.js:85348:18)           at Observable._subscribe (c:\some_folder\dist\prerender.js:87360:24) },   zone:    Zone {      _parent:       Zone {         _parent: null,         _name: '<root>',         _properties: {},         _zoneDelegate: [ZoneDelegate] },      _name: 'angular',      _properties: { isAngularZone: true },      _zoneDelegate:       ZoneDelegate {         _taskCounts: [Object],         zone: [Circular],         _parentDelegate: [ZoneDelegate],         _forkZS: null,         _forkDlgt: null,         _forkCurrZone: [Zone],         _interceptZS: null,         _interceptDlgt: null,         _interceptCurrZone: [Zone],         _invokeZS: [Object],         _invokeDlgt: [ZoneDelegate],         _invokeCurrZone: [Circular],         _handleErrorZS: [Object],         _handleErrorDlgt: [ZoneDelegate],         _handleErrorCurrZone: [Circular],         _scheduleTaskZS: [Object],         _scheduleTaskDlgt: [ZoneDelegate],         _scheduleTaskCurrZone: [Circular],         _invokeTaskZS: [Object],         _invokeTaskDlgt: [ZoneDelegate],         _invokeTaskCurrZone: [Circular],         _cancelTaskZS: [Object],         _cancelTaskDlgt: [ZoneDelegate],         _cancelTaskCurrZone: [Circular],         _hasTaskZS: [Object],         _hasTaskDlgt: [ZoneDelegate],         _hasTaskDlgtOwner: [Circular],         _hasTaskCurrZone: [Circular] } },   task:    ZoneTask {      _zone:       Zone {         _parent: [Zone],         _name: 'angular',         _properties: [Object],         _zoneDelegate: [ZoneDelegate] },      runCount: 0,      _zoneDelegates: null,      _state: 'notScheduled',      type: 'microTask',      source: 'Promise.then',      data:       ZoneAwarePromise [Promise] {         __zone_symbol__state: 0,         __zone_symbol__value:          TypeError: Cannot read property 'call' of undefined              at __webpack_require__ (c:\some_folder\dist\prerender.js:145231:30)              at Function.requireEnsure [as e] (c:\some_folder\dist\prerender.js:145250:25)              at ɵ0 (c:\some_folder\dist\prerender.js:145445:38)              at RouterConfigLoader.loadModuleFactory (c:\some_folder\dist\prerender.js:149622:39)              at RouterConfigLoader.load (c:\some_folder\dist\prerender.js:149607:35)              at MergeMapSubscriber.project (c:\some_folder\dist\prerender.js:148610:47)              at MergeMapSubscriber._tryNext (c:\some_folder\dist\prerender.js:88799:27)              at MergeMapSubscriber._next (c:\some_folder\dist\prerender.js:88789:18)              at MergeMapSubscriber.Subscriber.next (c:\some_folder\dist\prerender.js:85348:18)              at Observable._subscribe (c:\some_folder\dist\prerender.js:87360:24) },      scheduleFn: undefined,      cancelFn: undefined,      callback: [Function],      invoke: [Function] } }
Can someone help please.

@kamilmysliwiec
The minimal repository is this one. Pre-rendering does not work.

Prerendering is now shipped by Angular team as part of the official Universal package.   If you face any issue, please, report this in the official repository https://github.com/angular/universal


BitsandBytes Enablement on ROCm

Overview
This PR introduces bitsandbytes enablement on ROCm for AMD GPUs. It adds hipified versions of CUDA kernels and ops which allow the flow to route bitsandbytes API function calls to use optimized version of HIP kernels for AMD GPUs.
In the multi-backend-refactor branch, there is a proposal to separate various backends to support multiple GPUs/accelerators. The core of bitsandbytes is built on top of PyTorch and decides the API function call of individual GPUs/accelerators based on the device_type of the tensor as highlighted here. ROCm recognizes cuda  device type in PyTorch and runs seamlessly without the need to change anything in the application code. Hence, this PR updates cuda backend in bitsandbytes to enable its functionality on ROCm for AMD GPUs. This PR also adds support for ROCm in the  cmake build and enables key functionality of bitsandbytes  on AMD GPUs.
Summary of Changes

Updated CUDA backend to work seamlessly on ROCm

Integrated HIP environment into bitsandbytes through hipified versions of CUDA kernels and ops

Cmake build updates for ROCm

Enabled key features in bitsandbytes functional and autograd api

Impact
It enables to build and support bitsandbytes on ROCm for AMD GPUs . Bitsandbytes users can port applications smoothly onto AMD gpus as it requires minimal changes on their front. In addition to this, it also ensures that ROCm changes do not affect CUDA environment, thereby not affecting existing CUDA users.
CC: @Titus-von-Koeller @matthewdouglas @arlo-phoenix

Issue #149: can Intel Arc GPUs be supported in a similar manner?

Issue #149: can Intel Arc GPUs be supported in a similar manner?

@tpimh There's separate work in progress for Intel. So far there's been work on CPU with IPEX (#1178, #1206) and separately a SYCL port: #747.

Thanks! This looks promising.
I will try on both AMD and Intel Arc.

Dear @pnunna93,
thanks to you and your team for the amazing work. We're super excited about this and I'm very happy with what I'm seeing at an initial superficial review.
It would be great to have the AMD runner available relatively soon, otherwise it remains quite messy and work intensive to keep track of the correctness of the various backend implementations. Please let me know what I can do to help and I'll make sure to pull the right strings.
Regarding the review, as communicated in Slack, I have to first focus on wrapping up my deep dive in evaluating tensor-driven dispatch by integration with the PyTorch dispatcher via the torch.library APIs. I don't see any reason to not merge your PR, but I need to take another thorough look and I think it would be helpful for everyone to have clarity on the backend abstraction / dispatch mechanism asap and am therefore prioritizing that; so everyone can then refactor their code to account for that.
In that context, one important question came up:
Our paged optimizers use CUDA unified memory, as described in detail here.
Is that feature available on ROCm devices in one way or another? This would be quite important to understand for my analysis, as the handling of unified memory in relation to PyTorch is one of my last open questions. It's quite a special case, because it's a cornerstone of preventing OOMs in low resource environments -- a key feature for our user group -- and is not implemented/ accounted for in PyTorch and, therefore, we use that feature directly through CUDA related APIs: The underlying CUDA function is cudaMemPrefetchAsync AFAICT.
Thanks 🤗 and congrats on the great work in this PR, we're super excited about this ❤

Dear @pnunna93 et al,
Unfortunately we're (mostly me alone) quite resource constrained and humbled by the workload associated with the multi-backend-refactor. I just talked with my colleague @younesbelkada about the topic how to best handle the next steps.
We both took a look at this PR and the one from Intel and think that at first glance everything looks really good. At this time, both me and Younes are not in a position to give detailed feedback and I need to focus on concretizing the path forward on how to integrate with the PyTorch dispatcher (tensor driven dispatch, as requested) through the torch.library Python-level APIs. After extensive research and yesterday's consultation with 3 PyTorch devs at Meta that are experts on the topic I need to focus on making this new input concrete.
However, for the purpose of iterative progress (as agreed in our prior conversations), we've decided to already go ahead and merge both the open Intel and AMD branches into multi-backend-refactor, where interested parties can then compile from source and give the new functionality (we're so excited and grateful about this!) a thorough testing.
Once we've made some progress on the torch.library based refactor, I'll next focus on enabling the nightly releases for that branch as well. We're also looking forward to your feedback on the this torch.library / tensor-driven dispatch topic once the code is there on the basis of which to discuss (and refactor the backend specific code towards that new target, after we agreed with all of you that this is the right path).
Among other things, there's also been extensive ongoing work in the background on things like moving BNB to a new independent/non-profit Github org, but under the umbrella of Hugging Face and the support of their infra team for managing the complexities of the CI/CD backend and runners. Also, we're working to make Github runners for the different hardware platforms a reality (thanks for your help on that!).
Thanks again for the good work and active collaboration! ❤ 🚀

P.S. Also see this: README: asking for help from volunteer alpha testers
Let us know if you have further thoughts on this and how you think it's best to communicate about this.


Please add Throttle utility

Could you add throttle utility?

https://css-tricks.com/the-difference-between-throttling-and-debouncing/
https://lodash.com/docs/4.17.4#throttle
http://sampsonblog.com/749/simple-throttle-function
https://jsfiddle.net/jonathansampson/m7G64/

It would be very useful, once debounce is available throttle is a must-have.

can be very useful for certain use-case!

We've trimmed the core library to be much leaner, and we are unlikely to add more utility API such as this which is better distributed via general purpose utility libraries.
However we encourage developers to create class mixins (using standard ES6 class expressions) and/or simply implement the utility API they desire on a subclass of Polymer.Element and use that as the base class for elements developed in your organization.

@kevinpschaaf @sorvell @azakus Please create Throttle utility. We need throttle for resize and click events. Thank you.

https://stackoverflow.com/questions/27078285/simple-throttle-in-js/
https://github.com/Polymer/polymer/blob/master/lib/utils/debounce.html

Why don't you just use lodash? Polymer shouldn't even provide debounce method, IMHO.

@merlinnot We need throttle mixin for Polymer Elements from Polymer JS Experts... We need maintained mixins from Polymer Team.

lodash.min.js has 71KB... How to load only throttle function in Polymer element?

@JosefJezek it is extremely easy to write your own throttle function and put it in a behavior for reuse. If you've never done it before, I suggest is as a good exercise to understand behaviors. You can also write your own base class that extends Polymer.Element and includes all the helper functions you want.
However, I suggest staying away from asynchronous behaviors as much as possible.

You can use lodash-cli to create custom builds which can be damn small if you pick just the methods you need :)

Here is utility for Polymer https://github.com/StartPolymer/s-utils


calloc behavior on AIX platform

According to the documentation AIX returns NULL when requested size is 0 but also returns NULL if you provide 0 to count parameter.  In this example rule below, there is no strings definition in it, rule successfully compiles with given variable but afterwards when I try to create a scanner with the compiled rules, yr_scanner_create  function returns insufficient memory error. The reason is; new_scanner->matches is NULL because of the calloc behavior. To avoid this, #define _LINUX_SOURCE_COMPAT must be added to mem.c.
rule find_by_name
{
    meta:
        description = "Find files by name."

    condition:
        file_name == "Task.dat"
}

Interesting. The manpage for malloc and friends on my Debian system list this as nonportable behavior. IMHO, the correct response is to rewrite those allocations rather than telling the compiler to use glibc-compatible variants of those library functions.

Thank you for the fix, @hillu. The only concern with these changes is that, from now on, in addition to the NULL check on a calloc call, there must also be relevant count control, similar to your additional checks. However, due to the common behavior of calloc on Linux, it might be overlooked and become implicit knowledge, potentially leading to oversights. Adding the _LINUX_SOURCE_COMPAT macro with a conditional compilation directive can prevent future problems, what do you think?

I have similar concerns. It's very easy to re-introduce issues like this in the future.


Weird visual glitches appear while switching workspaces with treemacs opened

What did you expect to happen?
An update to Doom Emacs has triggered unexpected visual glitches. This should not happen.
What actually happened?
Since a few weeks ago some weird visual glitches started to appear while switching workspaces with treemacs opened.
Video showcasing the problem: https://imgur.com/a/xiZq8Yh
I am switching between workspace 1 and 2 using [w and ]w (equivalent of SPC tab [ / SPC tab ]), which triggers intermittent visual glitches in random places within Emacs.
Describe your attempts to resolve the issue
Have not yet tried something to resolve the issue.
Steps to reproduce
The problem happens on the latest origin/develop.
I did not yet pinpoint the exact commit where the issue started to appear.
The problem appears between 23f6f9051 and 2132d6006, from what I've tested so far.
A git checkout to commit 2132d6006 of develop resolves the issue (commit that was made ~2 weeks ago).

System Information
https://pastebin.com/gx8gehPu

Related: #5934

Try commenting out these lines and see if your issue goes away.

Thanks Henrik. These are the steps I took:

I commented out those lines you linked
Checked out newer commit git checkout af7c1d79b in  ~/.emacs.d
Removed packages again: rm -r ~/.emacs.d/.local/straight
Synced doom sync
Issue is still present in later commits

Will try pinpointing the issue once I find some more time.

The glitches have automagically resolved themselves after uncommenting your suggested lines and running a doom upgrade. However, sometimes it does randomly come back, but will re-open the issue by then.
Thanks for the assistance!


Allow port 9400 in NSG for Kafka REST proxy enabled clusters

Kafka REST proxy enabled cluster must allow inbound traffic on port 9400 to successfully create a cluster.

@jihwang0709 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

Publishing is suspended until Tuesday, May 19. Merging will resume 7:00 AM PT Tuesday.
This PR is ready for merge.


Added website

Changes proposed

[x] Added website link
Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[x] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Looks good!


Add wasmcloud-provider-macros crate

wasmcloud-provider-macros crate should be added in crates/provider/macros once #387 is done
cc @vados-cosmonic

Is wasmcloud-provider-macros supposed to be something different than provider-wit-bindgen?

no, this should have been closed by the PR


Update Supported Erlang versions guide to mention OTP 21

Note that I now list <IP_ADDRESS> as the minimum required. Even though nodes will still run on 19.3 we will ask any pre-<IP_ADDRESS> users to upgrade first since ERL-430 and ERL-448 are catastrophic and running into them on affected versions is a matter of time. So this is a strong recommendation stated as a requirement, not a breaking change.
References rabbitmq/rabbitmq-server#1616.
[#157964874]

Enforcing Erlang/OTP <IP_ADDRESS> as the minimum supported version is the right call. We've been reasonable and only kept mentioning it for 6 months, it was time to pull the trigger. This is good!


Implemented sealed traits according to Rust API Guidelines

They way the sealed trait Kind is implemented for BinaryHeap and SortedLinkedList prevents it from being used as bounds:
struct SomeStruct<T, K, const N: usize>
where K: Kind {
    binary_heap: BinaryHeap<T, K, N>
}

As suggested by the Rust API Guidelines, we can create a sealed trait by having an internal private trait that is required by the public trait. This way we can import the trait, but we can't implement it because of the private requirement.
This PR converts the sealed traits to this pattern. Because of a name conflict in sorted_linked_list.rs I renamed the generic type Kind to K throughout the module.

Thanks for finding this, could you have a look at fixing the failing tests?


Add the notion of using #dibs to indicate someone owns an issue

Signed-off-by: Doug Davis<EMAIL_ADDRESS>

I'm always in favor of being explicit. I'm not sure we're at the volume that people are unsure what other people are working on or can't immediately reach out and find that person to ask if they are still working on it. Having dibs would let non members attempt to call an issue, but they should also be told they need to reach out on sig chat, or reach out directly to the original assignee to take over.

@MHBauer added some text to try to address your comment.

I would really prefer not to make fields in the github UI meaningless.  It looks like for k8s, the plan is to use a dummy user as the assignee and make a comment.  Not sure if that closes the gap for you @duglin.

Not sure what you mean by github UI fields being meaningless - but if the upstream plan will allow for non-maintainers to grab issues then that's fine.

What issues have arisen that would require non-maintainer developers to claim an issue like this?

This came up because Richard wanted to grab an issue but he's not a maintainer.

I like the concept of dibs, but if we're hung up on that, a short blurb saying "contact someone, we're here to help you help us" should do it. We are open to having more people participate.

@duglin I'd like you to be responsible for implementing this proposal for the first few #dibs that come through, so we can see it in real life. Documentation like this doesn't, and can't, factor in the human element. After we see it in action, I'd like us to re-evaluate.
I'm LGTMing this

issue #346

Let's see how it works in practice! LGTM.


Jailbreakd Bug(Probably webkit related)

iPhone 6, iOS 11.3, Empty_List. Yesterday I had experienced a weird bug. It’s possible that this might be the same as another issue listed but here. When viewing content inside of YouTube for about an hour. The access to the internet was cut off completely and when I exited the application to test and see if it was just not the app itself. I tried opening Twitter and the app froze at it’s loading screen. I did read jailbreakd memory issues from what was listed and it sounds like it could be this one. Just sharing what I experienced.

Duplicate of #12 and #19

Definitely duplicate, please leave a comment on #12


Update instance to t3.micro

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/lgtm
/approve


[beta-1.70] backport add the Win32_System_Console feature

This is a beta backport of #12016 which is required to build the cargo library on Windows.
This also includes #12011 to get CI passing.

Thanks!
@bors r+

:pushpin: Commit 07e53ab7ad1ff5d54c71d6cb08462442116badc5 has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit 07e53ab7ad1ff5d54c71d6cb08462442116badc5 with merge ec8a8a0cabb0e0cadef58902470f6c7ee7868bdc...


Allow custom go-test-args

This PR allows passing in go-test-args from go-test.yml. This comes in handy when trying to reproducing NDFs. We could add variables for go-version and os but I figured that's overkill at this point, might as well add it when it's needed.

@n8maninger friendly reminder in case you missed the notification


Pluginbundle not actually working for some plugins

I am sure this is something I am doing wrong, but I'm at my wits end here.
I sometimes use sessions as a way to have settings for a given project.  For example for our salt repo at work my session is:
call pathogen#infect('/home/frew/code/vim-salt-plugins/{}')

source /home/frew/.vvar/sessions/_salt

And the latter is an Obsession built session.  It works perfectly fine.  Until I try to add a plugin that adds a file to the plugin subdirectory.  So for example syntax and and ftplugins work fine in the vim-salt-plugins directory, but if I add Eunuch to the bundle, the command (like :Remove) do not get added.
Here is the &rtp, to be clear:
/home/frew/code/vim-salt-plugins/eunuch,/home/frew/code/vim-salt-plugins/salt-vim,/home/frew/code/vim-salt-plugins/vim
-jinja,/home/frew/.vim,/home/frew/.vim/bundle-lua/neocomplete,/home/frew/.vim/bundle-python/editorconfig,/home/frew/.v
im/bundle-python/ultisnips,/home/frew/.vim/bundle/FastFold,/home/frew/.vim/bundle/IndentAnything,/home/frew/.vim/bundl
e/airline,/home/frew/.vim/bundle/better-whitespace,/home/frew/.vim/bundle/colors-solarized,/home/frew/.vim/bundle/comm
entary,/home/frew/.vim/bundle/csv,/home/frew/.vim/bundle/ctrlp,/home/frew/.vim/bundle/denite,/home/frew/.vim/bundle/ex
change,/home/frew/.vim/bundle/fugitive,/home/frew/.vim/bundle/fugitive-gitlab,/home/frew/.vim/bundle/gitgutter,/home/f
rew/.vim/bundle/go,/home/frew/.vim/bundle/goyo,/home/frew/.vim/bundle/inkpot,/home/frew/.vim/bundle/l9,/home/frew/.vim
/bundle/lastplace,/home/frew/.vim/bundle/lost,/home/frew/.vim/bundle/matchit,/home/frew/.vim/bundle/matchmaker,/home/f
rew/.vim/bundle/obsession,/home/frew/.vim/bundle/pathogen,/home/frew/.vim/bundle/perl,/home/frew/.vim/bundle/projectio
nist,/home/frew/.vim/bundle/python,/home/frew/.vim/bundle/quick-scope,/home/frew/.vim/bundle/repeat,/home/frew/.vim/bu
ndle/sleuth,/home/frew/.vim/bundle/splitjoin,/home/frew/.vim/bundle/surround,/home/frew/.vim/bundle/tabular,/home/frew
/.vim/bundle/terminus,/home/frew/.vim/bundle/textobj-between,/home/frew/.vim/bundle/textobj-entire,/home/frew/.vim/bun
dle/textobj-underscore,/home/frew/.vim/bundle/textobj-user,/home/frew/.vim/bundle/unimpaired,/home/frew/.vim/bundle/vi
negar,/home/frew/.vim/bundle/visual-star-search,/home/frew/.vim/bundle/wipeout,/var/lib/vim/addons,/usr/share/vim/vimf
iles,/usr/share/vim/vim80,/usr/share/vim/vimfiles/after,/var/lib/vim/addons/after,/home/frew/.vim/bundle/tabular/after
,/home/frew/.vim/bundle-python/ultisnips/after,/home/frew/.vim/after

I did put set sessionoptions-=options in my vimrc based on the README to pathogen and even looked through the actual session file in question to see if rtp/runtimepath was there, but it's not.
Any ideas?

Sessions load after plugins are already active, so changing 'runtimepath' in one will have no effect on what plugins are loaded.

Thanks.
--
Sent from a telephone. Pardon my brevity.
On May 20, 2017 9:25 AM, "Tim Pope"<EMAIL_ADDRESS>wrote:

Closed #187 https://github.com/tpope/vim-pathogen/issues/187.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tpope/vim-pathogen/issues/187#event-1090585267, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAf4_qi0Zc3RH_wEJDjJGc85qCFbIfsks5r7xQAgaJpZM4NhUDc
.


[Bug]: Unable to install traceAnalyticsDashboards in latest release

Describe the bug
Using the docker container I'm unable to install the traceAnalyticsDashboards following the instructions: https://opensearch.org/docs/1.2/dashboards/install/plugins/#install
To reproduce
Tyring omitting sudo (sudo isn't in the docker container)
$ bin/opensearch-dashboards-plugin install traceAnalyticsDashboards
Yields:
Attempting to transfer from traceAnalyticsDashboards
Attempting to transfer from https://ci.opensearch.org/ci/dbc/distribution-build-opensearch-dashboards/2.3.0/latest/linux/x64/tar/builds/opensearch-dashboards/plugins/traceAnalyticsDashboards-2.3.0.zip
Plugin installation was unsuccessful due to error "No valid url specified."

Running as root I initially get the error:
 > [2/2] RUN /usr/share/opensearch-dashboards/bin/opensearch-dashboards-plugin install traceAnalyticsDashboards:
opensearch-project/opensearch-build#5 1.659 OpenSearch Dashboards should not be run as root.  Use --allow-root to continue.

and adding the allow flag I'm back to the first error:
 => ERROR [2/2] RUN /usr/share/opensearch-dashboards/bin/opensearch-dashboards-plugin --allow-root install traceAnalyticsDashboards                                                                                3.3s
------
 > [2/2] RUN /usr/share/opensearch-dashboards/bin/opensearch-dashboards-plugin --allow-root install traceAnalyticsDashboards:
opensearch-project/opensearch-build#5 1.229 Attempting to transfer from traceAnalyticsDashboards
opensearch-project/opensearch-build#5 1.232 Attempting to transfer from https://ci.opensearch.org/ci/dbc/distribution-build-opensearch-dashboards/2.3.0/latest/linux/x64/tar/builds/opensearch-dashboards/plugins/traceAnalyticsDashboards-2.3.0.zip
opensearch-project/opensearch-build#5 3.189 Plugin installation was unsuccessful due to error "No valid url specified."

Checking the url above (https://ci.opensearch.org/ci/dbc/distribution-build-opensearch-dashboards/2.3.0/4103/linux/x64/tar/builds/opensearch-dashboards/plugins/traceAnalyticsDashboards-2.3.0.zip) in a browser I get:
<Error>
AccessDenied
<Message>Access Denied</Message>
<RequestId>Y765PWB52XN12WJF</RequestId>
<HostId>
wCqSWEqM7jDoi2gxHsRXjLVhRiqnWNkqN9KsAPpvQm7J1ehhdtqaq0Xyty8JDOpHseLQOzEEilI=
</HostId>
</Error>

Expected behavior
installation of the plugin
Screenshots
Host / Environment
kubernetes/docker
Additional context
the following Dockerfile can be used to reproduce:
FROM opensearchproject/opensearch-dashboards:2.3.0

USER root

RUN /usr/share/opensearch-dashboards/bin/opensearch-dashboards-plugin --allow-root install traceAnalyticsDashboards

Relevant log output
No response

@msillence Thanks for reporting the issue. Starting from OpenSearch 1.2 the trace analytics plugin has been merged with OpenSearch Observability plugin. This may be the cause of installation failure.
You may try the following steps to mitigate the issue:

Use the observability dashboards plugin name to install via plugin cli.

bin/opensearch-dashboards-plugin install  observabilityDashboards

OR Use the below URL to download the and manually install the plugin.

https://ci.opensearch.org/ci/dbc/distribution-build-opensearch-dashboards/2.3.0/latest/linux/x64/tar/builds/opensearch-dashboards/plugins/observabilityDashboards-2.3.0.zip


Update file explorer readme

Summary of the Pull Request
Updating the File Explorer module readme with updated module name, demo gif and step to enable Preview Pane in File Explorer.
Readme link in Fork repo branch: https://github.com/udit3333/PowerToys/blob/user/udit3333/Update-File-Explorer-Readme/src/modules/previewpane/README.md

PR Checklist

[x] Applies to #1763
[x] CLA signed. If not, go over here and sign the CLA

Shouldn't the bottom section about coding guidelines be inside of the contribution / coding areas?

Shouldn't the bottom section about coding guidelines be inside of the contribution / coding areas?

Yeah it can moved to a different location since it's applicable to other modules as well. Where do you think will be the right place for that section?

Shouldn't the bottom section about coding guidelines be inside of the contribution / coding areas?

Yeah it can moved to a different location since it's applicable to other modules as well. Where do you think will be the right place for that section?

if it lacks a good spot, make one :)

Moved the last section on Coding Guidance to a separate readme in devdocs folder.


DKPY2: Cannot connect outside of mavproxy

Hi, I'd be very interested having this for the project that I'm working on, and decided to see if I could get it working on my system (Ubuntu 14.04). However when I try to connect to sitl, by running "droneapi.connect("<IP_ADDRESS>:4444")" on the python command prompt, the command prints "Started.", but then never returns (this seems to be happening somewhere in the MPFakeState prepare function). Any idea what would cause this?
currently on tcr-nomp branch
sitl started with sim_vehicle.sh --map --out=<IP_ADDRESS>:4444
#299
@jlian

@tcr3dr I'm not even getting this far - when I try and import "connect" I get ImportError: No module named numpy

That's weird, numpy should come preinstalled,

That's weird, numpy should come preinstalled,

Not pre-installed on Windows, though of course that might depend on the distribution.
It is weird though, because I don't get the error when connecting from a script.

I'm closing this. The issue was fixed, and numpy is no longer a dependency.


[MusicBERT]: Could not load pretrained checkpoints

Please refer to https://github.com/microsoft/muzic/issues/51#issuecomment-1173043024_

Seems to be resolved in #51 now


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


test(sdk): Add the test integration for multiple custom scope

Signed-off-by: Talwinder kaur<EMAIL_ADDRESS>

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (f5616d7) 89.02% compared to head (b35d118) 89.07%.

:exclamation: Current head b35d118 differs from pull request most recent head 59672c8. Consider uploading reports for the commit 59672c8 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #686      +/-   ##
==========================================
+ Coverage   89.02%   89.07%   +0.04%
==========================================
  Files         103      103
  Lines        4218     4218
==========================================
+ Hits         3755     3757       +2
+ Misses        312      310       -2
  Partials      151      151

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


difference between repo and demo?

In your demo located here
the grid tiles are styled like this:
<md-grid-tile ng-repeat="gridTitle in homeCtrl.grid" md-rowspan="2" md-colspan="2" md-colspan-sm="1" ng-click="$state.go('posts.detail', { id: gridTitle.id })" class="ng-scope ng-isolate-scope" role="listitem" tabindex="0" style="left: calc(((25% - 6px) + 8px) * 0); width: calc(((25% - 6px) * 2) + 8px); padding-top: calc(((25% - 6px) * 2) + 8px); margin-top: calc(((25% - 6px) + 8px) * 0);">

    <md-grid-tile-footer class="ng-scope">

accusamus beatae ad

</md-grid-tile-footer>

</md-grid-tile>

I'm looking specifically at this code:
style="left: calc(((25% - 6px) + 8px) * 0); width: calc(((25% - 6px) * 2) + 8px); padding-top: calc(((25% - 6px) * 2) + 8px); margin-top: calc(((25% - 6px) + 8px) * 0);"
But in the code that's in the repo, the grid is then styled like this:
<md-grid-tile ng-repeat="gridTitle in homeCtrl.grid" md-rowspan="2" md-colspan="2" md-colspan-sm="2" ng-click="$state.go('posts.detail', { id: gridTitle.id })" class="ng-scope ng-isolate-scope" role="listitem" tabindex="0" style="left: calc(((12.5% - 7px) + 8px) * 0); width: calc(((12.5% - 7px) * 2) + 8px); padding-top: calc(((12.5% - 7px) * 2) + 8px); margin-top: calc(((12.5% - 7px) + 8px) * 0);">

    <md-grid-tile-footer class="ng-scope">

accusamus beatae ad

</md-grid-tile-footer>

</md-grid-tile>

And I'm looking specifically at this code:
style="left: calc(((12.5% - 7px) + 8px) * 0); width: calc(((12.5% - 7px) * 2) + 8px); padding-top: calc(((12.5% - 7px) * 2) + 8px); margin-top: calc(((12.5% - 7px) + 8px) * 0);
So in your demo, the styling uses 25% and the repo I'm coding with uses 12%. I know since these are inline they are being generated by JS - but for some reason, I can't for the life of me, find where these are being set.
If you can point me in the right direction, it would solve a lot of my styling issues in relation to the grid.
Thanks,
Pete

The demo was written in an earlier version of Angular Material. The Angular Material upgrade was quite big and a lot changed. I couldn't get the grid tiles demo fully working quickly, so I published it thinking that updating the dependencies and some other layout issues was more important than fixing my specific grid tile issue.

Okay, thanks for the update, I appreciate it.
Pete


tree shaking is enabled in development mode

Bug report
It is mentioned in the documentation that one of the conditions for tree shaking to be enabled is mode: production.
But I found that the development mode code disappeared. I never believed that it was caused by tree shaking, because the document was very sure that it would not be enabled, 😢 until I found this problem by debugging.
This is easy to reproduce, such as this warehouse xiaoxiaojx/webpack-issuer
What is the current behavior?
tree shaking is enabled in development mode
What is the expected behavior?
Modify the webpack documentation or fix the development mode bug
If it is confirmed to be a bug, I can contribute this pr

Other relevant information:
webpack version:  5.88.2

@TheLarkInn @alexander-akait Hello everyone, here I am again. Although turbopack, esbuild, and vite are very popular at present, my favorite is still webpack ❤

This change caused  https://github.com/webpack/webpack/commit/e1b5a78a241cc6037031a2dba121a604ebf0a6e0

bump

@xiaoxiaojx Yeah, side effects optimization is enabled in any mode to avoid big different between development and production, especial problems with side effects, because developers often make mistakes there, do you want to update our docs?


[BUG] NullPointerException due to IndexOutOfBoundException sporadically with SentenceDetector

Please provide as much details as possible, this will help us to deliver a fix as soon as possible.
Thank you!
Describe the bug
I am running the DocumentBySentenceSplitter on a large number of documents and noticing that it is throwing a NPE on a subset of document in production. The error has not been reproduced locally by splitting the document. I suspect it may be because of the load in production - I have 100 threads splitting documents using one splitter. I have attached an example document just to make sure it's not due to the document.
A_47_278&E_1992_77-EN.pdf
Log and Stack trace
Please provide a log and a stack trace (with exception), if applicable.
java.lang.NullPointerException
                                                     java.lang.Thread.run                        Thread.java:  840
                       java.util.concurrent.ThreadPoolExecutor$Worker.run            ThreadPoolExecutor.java:  635
                        java.util.concurrent.ThreadPoolExecutor.runWorker            ThreadPoolExecutor.java: 1136
                                                                      ...
                                        clojure.core.async/thread-call/fn                          async.clj:  487
                                        pinecone-sync.core/run/process/fn                           core.clj:   49
                                          pinecone-sync.core/process-file                           core.clj:   19
                                  pinecone-sync.embeddings/embed-document                     embeddings.clj:  144
                                           pinecone-sync.embeddings/split                     embeddings.clj:   75
                                                                      ...
                 jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke  DelegatingMethodAccessorImpl.java:   43
                   jdk.internal.reflect.GeneratedMethodAccessor538.invoke
dev.langchain4j.data.document.splitter.HierarchicalDocumentSplitter.split  HierarchicalDocumentSplitter.java:   67
  dev.langchain4j.data.document.splitter.DocumentBySentenceSplitter.split    DocumentBySentenceSplitter.java:   74
                   opennlp.tools.sentdetect.SentenceDetectorME.sentDetect            SentenceDetectorME.java:  130
                opennlp.tools.sentdetect.SentenceDetectorME.sentPosDetect            SentenceDetectorME.java:  260
                                                  java.util.ArrayList.get                     ArrayList.java:  427
                                             java.util.Objects.checkIndex                       Objects.java:  361
                               jdk.internal.util.Preconditions.checkIndex                 Preconditions.java:  266
                    jdk.internal.util.Preconditions.outOfBoundsCheckIndex                 Preconditions.java:   70
                              jdk.internal.util.Preconditions.outOfBounds                 Preconditions.java:   64
java.lang.IndexOutOfBoundsException: Index 23 out of bounds for length 23

This is one such stack trace. For different documents, the index/length numbers are different
To Reproduce
Please provide a relevant code snippets to reproduce this bug.
Runt he DocumentBySentenceSplitter with argument 400 and 20 on the attached document
Expected behavior
A clear and concise description of what you expected to happen.
The document should be split by sentence.
Please complete the following information:

LangChain4j version: e.g. 0.24.0
Java version: e.g. 17

@nsadeh thank you so much for reporting! Here is the fix: https://github.com/langchain4j/langchain4j/pull/481

Thank you!


feat : [IDP-1664] : Added the steps to add API docs

Harness Developer Pull Request
Added the steps and instructions to create yaml of kind api and register the same in IDP.
What Type of PR is This?

[ ] Issue
[x] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Reason a request was Closed on Advanced Search and Queue results

As an IAO analyst and ministry coordinator
I want the reason stated that a request was Closed in the 'Current State' column on Advanced Search and the Queue
so that I can quickly no why a request was Closed

Assumptions & Scope
What are the assumptions for this story?
Users have asked to quickly know the reason why a request was Closed on their Queue or Advanced Search
What is IN scope?
Add reason for why a request was Closed to the Current State column on Advanced Search and Request Queue
What is NOT in scope?
Closing and selecting a reason a request is Closed #469
Reason a request was Closed on Advanced Search and Queue results #4920
Acceptance Criteria
Scenario 1: Reason a request was Closed on Request Queue

GIVEN the IAO analyst or ministry in on a Request Queue (My Requests, My Team's Requests, Watching Requests)
WHEN there is a Closed request(s) listed in the 'Current State' column
THEN the reason (e.g., Abandoned, Access Denied, Application Fee - Abandoned, Full Disclosure, No Resp. Records Exist/Located, Outside Scope of Act, Partial Disclosure, Records in Another Min/Org, Refuse to Confirm or Deny, Routinely Releasable, Section 43, Transferred, Withdrawn) the request was Closed will appear: Closed - Abandoned

Scenario 1: Reason a request was Closed on Advanced Search

GIVEN the IAO analyst or ministry in on Advanced Search
WHEN there is a Closed request(s) listed in the 'Current State' column
THEN the reason (e.g., Abandoned, Access Denied, Application Fee - Abandoned, Full Disclosure, No Resp. Records Exist/Located, Outside Scope of Act, Partial Disclosure, Records in Another Min/Org, Refuse to Confirm or Deny, Routinely Releasable, Section 43, Transferred, Withdrawn) the request was Closed will appear: Closed - Abandoned

Scenario 3: xxxxxx
...
Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)
Validation Rules? (If yes, list here)
Design
@xxx - please link the Design here
Definition of Ready

[ ] Is there a well articulated User Story?
[ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
[ ] If there is a user interface, is there a design?
[ ] Does the user story need user research/validation?
[ ] Does this User Story needs stakeholder approval?
[ ] Design / Solution accepted by Product Owner
[ ] Is this user story small enough to be completed in a Sprint? Should it be split?
[ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
[ ] Has the story been estimated?

Definition of Done

[ ] Passes developer unit tests
[ ] Passes peer code review
[ ] If there's a user interface, passes UX assurance
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Confirm Test cases built and succeeding
[ ] No regression test failures
[ ] Test coverage acceptable by Product Owner
[ ] Ticket ready to be merged to master or story branch
[ ] Developer to list Config changes/ Update documents and designs
[ ] Can be demoed in Sprint Review
[ ] Tagged as part of a Release
[ ] Feature flagged if required
[ ] Change Management activities done?

@JHarrietha-AOT, please advise if this will create any spacing issues for the queue or advanced search?

We could maybe have it cut-off after a certain character limit and have a hover over option? I imagine most common ones will be easily perceived at a glance anyways.
Also - not sure if we need scenario 1, since closed requests don't show on the queue. Although OIPC requests may show, they will eventually move to a different state like records review or sign-off.

@lmullane - update scenarios if 'closed - reason for closing' exceeds certain character limit (where it doesn't show up all in advanced search, display full reason for closing on hover.

Internal Technical Refinement (4920):
Estimate: 5
Question (Dev Proposal for display):

Similar to the event Queue content column with tooltip for over X characters.
Update from Bus. Refinement:
The format will be "Closed - {Reason}. The character limit exceeds the breakable will be shown in tooltip.
Reference: Event Queue - Column (Content)


.fileupload (jQuery) doesn't works with audio+video player

I just spend whole day to install this package via npm first (w/o succes), then with bower... and the links from example was different with current directories. So, finally I solve it. I use to remake ur code to reproduce audio-player & upload to server obrained audio file. I did absolutely same with video player, I changed all like in example " audio + video", video is obtaining (console.log), it shows me size of obtained file, format, but returns me error 500 from the server. Note that I use absolute the same code at backend like with audio-only(it worked with audio).
I'm working with Laravel 5.4, console.log shows me following stepts :

started recording video stream.
RecordRTC.js:1012 Using recorderType: MediaStreamRecorder
RecordRTC.js:2016 Passing following config over MediaRecorder API. {type: "video", video: {…}, canvas: {…}, frameInterval: 10, disableLogs: false, …}
RecordRTC.js:693 Recorder state changed: recording
RecordRTC.js:93 Initialized recorderType: MediaStreamRecorder for output-type: video
(index):79 started recording!
RecordRTC.js:119 Stopped recording video stream.
RecordRTC.js:693 Recorder state changed: stopped
RecordRTC.js:160 video/webm -> 308 KB
(index):85 finished recording:  {video: Blob(308296)}
jquery.min.js:5 POST http://localhost:8000/test 500 (Internal Server Error)

My back-end code :
>
> >     /**
> >      * Store a newly created resource in storage.
> >      *
> >      * @param  \Illuminate\Http\Request  $request
> >      * @return \Illuminate\Http\Response
> >      */
> >     public function test(Request $request) // POST /cvs
> >     {
> >         print_r($_FILES);
> >         $path = '/video/'.uniqid();
> >
> >         Storage::disk('local')->putFileAs('public'.$path, $request->file('files'), "filename.webm");
> >                      return response()->json("x",200);
> >
> >     }

Response from /test route in my debugger :
Array () , so it means that obtained video doesn't hit the Request object.
My entire code of player and jQuery (worked for audio-only)
<head>
       <title> Project </title>
       <link href="/videojs-record/node_modules/video.js/dist/video-js.min.css" rel="stylesheet">
        <link href="/videojs-record/dist/css/videojs.record.css" rel="stylesheet">

        <script src="/videojs-record/node_modules/video.js/dist/video.min.js"></script>
        <script src="/videojs-record/node_modules/recordrtc/RecordRTC.js"></script>
        <script src="/videojs-record/node_modules/webrtc-adapter/out/adapter.js"></script>

        <script src="/videojs-record/dist/videojs.record.js"></script>

        <script src="//ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js"></script>
        <script src="/videojs-record/node_modules/blueimp-file-upload/js/vendor/jquery.ui.widget.js"></script>
        <script src="/videojs-record/node_modules/blueimp-file-upload/js/jquery.iframe-transport.js"></script>
        <script src="/videojs-record/node_modules/blueimp-file-upload/js/jquery.fileupload.js"></script>

        <style>
        /* change player background color */
        #myVideo {
            background-color: #ff6b6b;
        }
        /* hide file upload button */
        #fileupload {
            display:block;
        }
        </style>
</head>

<body>
        <video id="myVideo" class="video-js vjs-default-skin"></video>

          Select a video: <input id="fileupload" type="file" name="files">

<script>
        $(function () {
            $('#fileupload').fileupload({
                url: '/test',
                method: "POST",
                done: function (e, data) {
                    $.each(data.files, function (index, file) {
                        var message = 'Upload complete: ' + file.name + ' (' +
                            file.size + ' bytes)';
                        $('<p/>').text(message).appendTo(document.body);
                        console.log(message);
                    });
                }
            });
var player = videojs("myVideo", {
    controls: true,
    width: 320,
    height: 240,
    fluid: false,
    plugins: {
        record: {
            audio: true,
            video: true,
            maxLength: 60,
            debug: true
        }
    }
}, function(){
    // print version information at startup
    videojs.log('Using video.js', videojs.VERSION,
        'with videojs-record', videojs.getPluginVersion('record'));
});
// error handling
player.on('deviceError', function() {
    console.log('device error:', player.deviceErrorCode);
});
player.on('error', function(error) {
    console.log('error:', error);
});
// user clicked the record button and started recording
player.on('startRecord', function() {
    console.log('started recording!');
});
// user completed recording and stream is available
            player.on('finishRecord', function() {
                // the blob object contains the audio data
                var videoFile = player.recordedData;
                console.log('finished recording: ', videoFile);
                // upload data to server
                var filesList = [videoFile];
                $('#fileupload').fileupload('add', {files: filesList});
            });
        });
</script>

UPDATE :
I added
if (jQuery('#fileupload').val()) { console.log("YES"); } else { console.log("NO");}
after
            player.on('finishRecord', function() {
                // the blob object contains the audio data
                var videoFile = player.recordedData;
                console.log('finished recording: ', videoFile);
                // upload data to server
                var filesList = [videoFile];
                $('#fileupload').fileupload('add', {files: filesList});

and it outputed me "NO" at console.log
So, here is the problem :    $('#fileupload').fileupload('add', {files: filesList}); doesn't add obtained file to the input. Do you have idea - why?

So, that was because :

in Firefox we have to use player.recordedData
in Chrome(as I used), that object has one more object key - video. So, to access that object we have to use :  player.recordedData.video

To salve this cross-browser incompatibility with code :
 player.on('finishRecord', function() {
                if(player.recordedData.video == undefined) {
                    var videoFile = player.recordedData;
                } else {
                   var videoFile = player.recordedData.video;
                }
                console.log('finished recording: ', videoFile);
                // upload data to server
                var filesList = [videoFile];
                $('#fileupload').fileupload('add', {files: filesList});
            });

@priMo-ex3m thanks for that fix, can you make a pull request for that?

You're using audio+video, and the examples use audio-only, so I cannot update these examples, closing as is.


LuaLS/lua-language-server is not loading config.json

When I follow the readme.md the LuaLS/lua-language-server is not recognizing the config file.

Installed LuaLS/lua-language-server in VSCode
Added a new Profil with an empty settings.json in VSCode
Added     "Lua.workspace.userThirdParty": [      "C:\\workspace\\anomaly-definitions"  ] where the path is the root of this project cloned via git
Open D:\Anomaly-<IP_ADDRESS>-Modding\gamedata\scripts

Maybe I missed something, however I thought the LLS is now recognizing at least the .scripts files but it doesn't, which is obvious, since the LLS is not prompting me to use the config for "Stalker: Anomaly".
I got it somehow to work with with:
{
    "files.associations": {
        "*.script": "lua"
    },
    "Lua.workspace.userThirdParty": [
        "C:\\workspace\\anomaly-definitions"
    ],
    "Lua.workspace.library": [
      "C:\\workspace\\anomaly-definitions\\library",
      "D:\\Anomaly-<IP_ADDRESS>-Modding\\gamedata\\scripts"
    ],
    "Lua.workspace.ignoreSubmodules": false,
    "Lua.diagnostics.disable": [
      "lowercase-global"
    ],
    "Lua.runtime.plugin": "C:\\workspace\\anomaly-definitions\\plugin.lua",
    "Lua.runtime.version": "Lua 5.1",
}

As you can see I need to use VSCodes files.associations, to have a somehow working state, but this just enables the prompt: "Do You need to configure your work enviroment as 'luafilesystem'?" - which is not "Stalker: Anomaly" and ofcourse ignores your LLS-3rdlib-Config for "files".
This way I am going down from 30K+ errors to just 2K+ errors, but for example lua_help.script alone has 1003 errors.
Did I missed something?

Sorry for responding so late, meant to reply much earlier but got sidetracked.
As far as setup goes, I'm not sure why the automatic "Environment Emulation" doesn't work. It did work when I wrote the readme, though not right at this moment as I'm testing it for some reason.
The manual method is as you described, by plugging in the Lua.workspace.library and Lua.runtime.plugin, which seems to work at least. The .lua association with .script files is a good point that I overlooked, and I'll update the readme to include it.
As far as errors goes, lua_help.script is not a proper .lua file, as it serves more as auto-generated documentation for exported stuff from engine so no surprise there. Best off disabling diagnostics for that file at least.
Otherwise, it looks most of the other 'errors' are due to non-standard amounts and types of whitespace used to declare classes, for which I should be able to put out a fix soon.


add example to send customized message by using serializer

based on <IP_ADDRESS>. anyone can help?

This PR seems to accidentally try to merge trunk into 0.8.2 branch. Due to the hundreds of files this changes, its impossible to review.
Can you close this and open as PR to the correct branch?

@microwishing Can you please close this pull request as soon as possible?
Once you update your example to be against trunk, you can re-open and we will review. In the mean time this is slowing down others builds and reviews, as many Jenkins jobs are being trigger/backed up.

@microwishing, can you please close this PR? It's been generated incorrectly.

Closing PR as requested at https://issues.apache.org/jira/browse/INFRA-10795


Cookie options

This fixes #42
I also added the ability to change the path as part of cookie.
Should be merged after PR #46.

@sdogruyol all fixed

@neovintage thank you 👍


Intellisense for StyleSheet not working

#28470
#29180
#306
Are you still working on this problem? I can not get Intellisence when typing second line of StyleSheet with TSX/JS file 😫.

#306


fix(is-IS): translation updates

Updated automated translations for the is-IS locale

Cherry-picked to work around some conflicts - merged as 2af5170e91c3eefbee4e49aa828cb3ed5d27d0d8


Response codes

One small detail I noticed in the spec is that for creating, modifying and deleting pins a successful response has a 202 code (accepted), which is described as:

The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.

I guess it's assumed that the pinning/deleting will happen outside of the request in a queue?
In my initial implementation there is no queue (responses can take a few seconds) so 202 feels wrong here, there's no need for the client to come back and check because the status will be pinned or failed in the response itself, so it makes sense for it to be a 200.
Similarly with deleting, the delete happens during the request so a 204 seems like the right response code here as there's no response body expected.
I wonder if there's some wiggle room in the spec for different response status codes depending on implementation, clients could definitely use the hint of 202 if they are going to need to come back and check on the status, although a status of queued or pinning also confirms that.
Related but possibly not helpful: looking at the status codes for the IPFS HTTP API, IPFS itself uses 200 when processing:

200 - The request was processed or is being processed (streaming)

IPFS HTTP API,  IPFS itself uses 200 when processing:

The HTTP API under /api/v0/ is an RPC-style API over HTTP, not a REST API. Would not use it as inspiration.
It does not support asynchronous mode of operation at all (either returns final response of uses streaming, which is blocking too), and due to RPC nature is very opinionated about codes (eg. returns 500 when it "should" return 404 etc).

I guess it's assumed that the pinning/deleting will happen outside of the request in a queue?

@andrew correct, the idea behind HTTP 202 is to emphasize the asynchronous nature of pinning operation.
Example: user should be able to create Pin object for a CID that represents 650GB of data (eg. ipfs files stat /ipfs/QmXoypizjW3WknFiJnKLwHCnL72vedxjQkDDP1mXWo6uco) and POST /pins  should return immediately, with PinStatus.status set to queeued (no blocking)
For the simplicity, v0.0.5 of the spec assumes 202 is always returned, even if data was already on the pinning service. We could expand the spec and add support for returning  200 or even more correct 201  (created) for situation when pin was instantly created, without queuing, but it's already possible to indicate that by returning pinned in PinStatus.status, so its mostly cosmetic change, not sure if worth complicating HTTP client side.
Thoughts?

Yeah probably not worth complicating the spec over it at this point, plus I suspect that most http clients will just accept any old 2XX response and look at the status (which could possibly be a 2XX with failed) anyway, thanks for the thoughtful response 👍


Refer Friends Feature Flag - Scholarship Edition!

What's this PR do?
Updates all references to the refer-friends feature flag to the refer-friends-scholarship feature flag!
I figured it'd be neater to just replace for now, and if we ever wanted to do a side by side test or wtvr down the pike, we can just add it back in instead of both cluttering our codebase.
How should this be reviewed?

Toggle the DS_REFER_FRIENDS_SCHOLARSHIP_TEST to true in .env
Create a new user via web
Do they have the refer-friends-scholarship feature flag?
Did Customer.io get this field in the Payload?

Relevant Tickets
Pivotal card
Checklist

[ ] Documentation added for new or changed endpoints.
[x] Tests added for new features/bug fixes/API updates.
[ ] Post a message in #dev-northstar if this includes something that causes a rebuild!
[ ] If new attributes were added to users, there is a corresponding PR to surface these in Aurora.
[ ] If new attributes were added to users, then the data team already knows about these changes.
[x] This PR has been added to the relevant Pivotal card.

I have a silly question -- would this mean that people who had refer-friends be opted into this scholarship experience too and how would we distinguish between the two groups (refer-friends = gift card and these people are scholarship entries)?

I have a silly question -- would this mean that people who had refer-friends be opted into this scholarship experience too and how would we distinguish between the two groups (refer-friends = gift card and these people are scholarship entries)?

Fair question! Thankfully, this will only apply to new web registrants, so no existing users should be affected.

Though, this made me

I have a silly question -- would this mean that people who had refer-friends be opted into this scholarship experience too and how would we distinguish between the two groups (refer-friends = gift card and these people are scholarship entries)?

Fair question! Thankfully, this will only apply to new web registrants, so no existing users should be affected.

Though, this made me realize that if we remove the refer-friends from the C.io blink payload, that flag won't get send to c.io if we ever updated a user manually with that flag, or backfilled or something. I think I need to add that field back in @DFurnes ?

Ah, yeah, good point. I didn't think about opting people into that flag after the fact!

Ah, yeah, good point. I didn't think about opting people into that flag after the fact!

Like I soooort of doubt we would, but I guess it's a fair possibility so doesn't hurt? (Out of curiosity @DFurnes , if we ever update a user and their attributes are sent to c.io but missing a field that's already been set on c.io, would that field be deleted or is it just a merge they're doing, and the field would remain un-updated?)
Anyways, I'll add it back in, and merge!

Out of curiosity @DFurnes , if we ever update a user and their attributes are sent to c.io but missing a field that's already been set on c.io, would that field be deleted or is it just a merge they're doing, and the field would remain un-updated?

Unless we explicitly send null for that field, it just merges with the existing profile. 😌

Out of curiosity @DFurnes , if we ever update a user and their attributes are sent to c.io but missing a field that's already been set on c.io, would that field be deleted or is it just a merge they're doing, and the field would remain un-updated?

Unless we explicitly send null for that field, it just merges with the existing profile. 😌

Ah golden! Ok, so I guess worth it just for the manual opting-in... It can't hurt


iOS decryption using TSCellTokenEncryptedData is not working

Describe the bug
We have integrated themis on our backend and mobile app. so encrypted data using the themis secure cell token protected method is coming from the API to mobile. when ios App try to decrypt that  using the same masterkey that backend use and with give ciphertext and token library throwing the error
To Reproduce
Steps to reproduce the behavior:

Master key: b0gyNlM4LTFKRDI5anFIRGJ4SmQyLGE7PYA8KLQbT5K=

let hash = "abDoZIU="
let token = "AAEBQAwAAAAQAAAABQAAAJ52NkaXhYJFmmE5DB8muA6itiN2NecN1kfb2RA="

let cipherText =  Data(base64Encoded: hash, options: .ignoreUnknownCharacters)!
let cipherToken =  Data(base64Encoded: token, options: .ignoreUnknownCharacters)!
var encryptedMessage: TSCellTokenEncryptedData = TSCellTokenEncryptedData()
encryptedMessage.cipherText = NSMutableData(data:cipherText)
encryptedMessage.token = NSMutableData(data:cipherToken)

do {
    let decryptedMessage: Data = try cellToken.unwrapData(encryptedMessage, context: nil)
    let resultString: String = String(data: decryptedMessage, encoding: .utf8)!
    print("decryptedMessage = \(resultString)")
} catch let error as NSError {
    print(error.localizedDescription)
    print("Error occurred while decrypting \(error)", #function)
    return
}

See the following error:

ThemisDemo/Pods/themis/src/themis/sym_enc_message.c:345 - error: themis_auth_sym_plain_decrypt(hdr->alg, derived_key, derived_key_length, iv, hdr->iv_length, in_context, in_context_length, encrypted_message, hdr->message_length, message, message_length, auth_tag, hdr->auth_tag_length)

Error occurred while decrypting Error Domain=com.CossackLabs.Themis.ErrorDomain Code=11 "Secure Cell (Token Protect) decryption failed" UserInfo={NSLocalizedDescription=Secure Cell (Token Protect) decryption failed} decryptData()

Expected behavior
It should be decrypted if we send base 64 decoded data to TSCellTokenEncryptedData as we are able to decrpyt the same data on Android, Node.js and https://docs.cossacklabs.com/simulator/data-cell/
Environment (please complete the following information):

OS: [latest ios]
Hardware: [64-bit, or iPhone 11 Max SIMULATOR]
Themis version:  0.12.2
Installation way:

cocoapod

Additional context
Add any other relevant context for the problem here. Share an example project, if you can.

Hi @parthh!
Thanks for reporting an issue. The issue exists, but I believe it’s not with SwiftThemis but with our documentation for Themis Interactive Simulator.
Why the code does not work
In Swift code you have to decode the key into Data:
let masterKey = Data(base64Encoded: "b0gyNlM4LTFKRDI5anFIRGJ4SmQyLGE7PYA8KLQbT5K=",
                     options: .ignoreUnknownCharacters)!
let cellToken = TSCellToken(key: masterKey)!

because TSCellToken accepts only Data.
However, the interactive simulator does not decode the key as base64. Instead it interprets it as UTF-8 text. When you input the key like this into the simulator:

The actual key that is used for encryption is not
let masterKey = Data(base64Encoded: "b0gyNlM4LTFKRDI5anFIRGJ4SmQyLGE7PYA8KLQbT5K=",
                     options: .ignoreUnknownCharacters)!

but rather
let masterKey = "b0gyNlM4LTFKRDI5anFIRGJ4SmQyLGE7PYA8KLQbT5K=".data(using: .utf8)!

Effectively, the data was encrypted with a key different from the one used for decryption, which causes the decryption to fail.
What code works successfully
If you use the same key as the simulator, the incorrectly decoded key, then the data can be decrypted successfully:
let masterKey = "b0gyNlM4LTFKRDI5anFIRGJ4SmQyLGE7PYA8KLQbT5K="
let hash = "abDoZIU="
let token = "AAEBQAwAAAAQAAAABQAAAJ52NkaXhYJFmmE5DB8muA6itiN2NecN1kfb2RA="

let cipherText = Data(base64Encoded: hash, options: .ignoreUnknownCharacters)!
let cipherToken = Data(base64Encoded: token, options: .ignoreUnknownCharacters)!
let encryptedMessage = TSCellTokenEncryptedData()
encryptedMessage.cipherText = NSMutableData(data: cipherText)
encryptedMessage.token = NSMutableData(data: cipherToken)

let correctKey = Data(base64Encoded: masterKey, options: .ignoreUnknownCharacters)!
let cellTokenDoesNotWork = TSCellToken(key: correctKey)!
let decryptedMessageFail = try? cellTokenDoesNotWork.unwrapData(encryptedMessage, context: nil)

let nilMessage = "<nil>".data(using: .utf8)!
print("decryptedMessage = \(String(data: decryptedMessageFail ?? nilMessage, encoding: .utf8)!)")
// prints "decryptedMessage = <nil>"

let simulatorKey = masterKey.data(using: .utf8)!
let cellTokenThisWorks = TSCellToken(key: simulatorKey)!
let decryptedMessageOk = try? cellTokenThisWorks.unwrapData(encryptedMessage, context: nil)

print("decryptedMessage = \(String(data: decryptedMessageOk ?? nilMessage, encoding: .utf8)!)")
// prints "decryptedMessage = Hello"

What are the next steps
You cannot use base64-encoded encryption keys with the interactive simulator at the moment. The key used with the interactive simulator must be encoded in UTF-8 when testing the output against the application code.
Could you please verify that using UTF-8 works for you?

@ilammy you are good, it worked now


VSIX's resource loading error on not English environment.

Konnichiwa (Hello) Mark.
I tried to read the JSON file that contains conversion rules by the extension "Edit DB Context Rules" on Visual Studio.
And then, VS displayed error dialog with the message "Can't find resource toolwindows ruleeditordialog.xaml".
(Sorry I don't remember the message exactly.)
When VS showed the dialog, VS's language environment was Japanese.
After that, I changed VS's language from Japanese to English, VS showed the dialog successfully.
It seems vsix package doesn't include ruleeditordialog.xaml file for not English environment (or VS cannot find the resource on the other lang environment).
(I tried on Visual Studio 2022 community editon , Entity Framework Ruler 1.0.85)

It may take me a little time to test this in a non-English environment.  I'll keep you posted.

Fixed in latest VSIX update


"generate"

Use of the word generate (title, and README) is confusing.  When run the software sets up and executes a Reverse SSL capability? If yes, then generate is the wrong word to use to describe this. If no, then the documentation should state what further steps should be performed (after generation) in order to execute/launch it.

Indeed, my choice of words might be inadequate here. The script starts the listener locally and provides the user with an agent (a single command for Linux and a Powershell script for Windows) that, when executed on remote machine, will establish a reverse shell communication with it. As such, what do you think can be a good alternative for term "generate"?
Cheers and thank you for your input! :D

Generate is fine for step 1, if you details "step 2" :)


Merge to production

Issue

Link:
Summary:

How

Screenshots

References

Checklist

[ ] Tests added
[ ] Cleaned up commit history (rebase!)
[ ] Documentation added
[ ] Thought about variable and method names

Once tested by @ccrisan on Syncrobit 0x58


Change naming

As the package only contains the gqcnn solution it might be an idea to rename it to panda_gqcnn.

I will keep it named panda_autograsp but I will slightly update the documentation.


train_ssd300 throws errors

I convert the train_ssd300.ipnb into .py file, and execute it to train on PASCAL VOC 2007, 2012, some errors were thrown as below:
os environment:
ubuntu 16.04
tf: tensorflow-gpu 1.30
keras: 2.0
history = model.fit_generator(generator = train_generator,
steps_per_epoch = ceil(n_train_samples/batch_size),
epochs = epochs,
callbacks = [ModelCheckpoint('ssd300_weights_epoch-{epoch:02d}_loss-{loss:.4f}_val_loss-{val_loss:.4f}.h5',
monitor='val_loss',
verbose=1,
save_best_only=True,
save_weights_only=True,
mode='auto',
period=1),
LearningRateScheduler(lr_schedule),
EarlyStopping(monitor='val_loss',
min_delta=0.001,
patience=2)],
validation_data = val_generator,
validation_steps = ceil(n_val_samples/batch_size))
File "train_ssd300.py", line 275, in
validation_steps = ceil(n_val_samples/batch_size))
File "/home/junhao.li/anaconda2/envs/py35/lib/python3.5/site-packages/keras/legacy/interfaces.py", line 87, in wrapper
return func(*args, **kwargs)
File "/home/junhao.li/anaconda2/envs/py35/lib/python3.5/site-packages/keras/engine/training.py", line 2016, in fit_generator
self._make_train_function()
File "/home/junhao.li/anaconda2/envs/py35/lib/python3.5/site-packages/keras/engine/training.py", line 990, in _make_train_function
loss=self.total_loss)
File "/home/junhao.li/anaconda2/envs/py35/lib/python3.5/site-packages/keras/legacy/interfaces.py", line 87, in wrapper
return func(*args, **kwargs)
File "/home/junhao.li/anaconda2/envs/py35/lib/python3.5/site-packages/keras/optimizers.py", line 424, in get_updates
lr_t = lr * (K.sqrt(1. - K.pow(self.beta_2, t)) /
File "/home/junhao.li/anaconda2/envs/py35/lib/python3.5/site-packages/keras/backend/tensorflow_backend.py", line 1443, in sqrt
x = tf.clip_by_value(x, zero, inf)
File "/home/junhao.li/anaconda2/envs/py35/lib/python3.5/site-packages/tensorflow/python/ops/clip_ops.py", line 58, in clip_by_value
[t, clip_value_min, clip_value_max]) as name:
File "/home/junhao.li/anaconda2/envs/py35/lib/python3.5/contextlib.py", line 59, in enter
return next(self.gen)
File "/home/junhao.li/anaconda2/envs/py35/lib/python3.5/site-packages/tensorflow/python/framework/ops.py", line 4521, in name_scope
g = _get_graph_from_inputs(values)
File "/home/junhao.li/anaconda2/envs/py35/lib/python3.5/site-packages/tensorflow/python/framework/ops.py", line 4262, in _get_graph_from_inputs
_assert_same_graph(original_graph_element, graph_element)
File "/home/junhao.li/anaconda2/envs/py35/lib/python3.5/site-packages/tensorflow/python/framework/ops.py", line 4201, in _assert_same_graph
"%s must be from the same graph as %s." % (item, original_item))
ValueError: Tensor("training/Adam/Const:0", shape=(), dtype=float32) must be from the same graph as Tensor("sub:0", shape=(), dtype=float32

K.clear_session() use twice !!!  I solved it.

Glad to hear it, closing this.


docs: fix deleteKey example

As mentioned in #610, we should remove the const key =  as it implies that deleteKey() returns a value.

Thanks!


password-sync-create-service-account fails to create a project

Project creation is failing. It seems that the project display name [display_name] is too long.
Here's the console output.
Welcome! This script will create and authorize the resources that are necessary to use Password Sync. The following steps will be performed on your behalf:

1. Create a Google Cloud Platform project
2. Enable APIs
3. Create a service account
4. Authorize the service account
5. Create a service account key

In the end, you will be prompted to download the service account key. This key can then be used for PasswordSync.

If you would like to perform these steps manually, then you can follow the instructions at https://support.google.com/a/answer/7378726.

Press Enter to continue or 'n' to exit:
Creating project...
Failed to execute command: `ERROR: (gcloud.projects.create) INVALID_ARGUMENT: field [display_name] has issue [project display name must be at most 30 characters]
- '@type': type.googleapis.com/google.rpc.BadRequest
  fieldViolations:
  - description: project display name must be at most 30 characters
    field: display_name
- '@type': type.googleapis.com/google.rpc.Help
  links:
  - url: https://cloud.google.com/resource-manager/reference/rest/v1/projects

admin_@cloudshell:~$

Thank you! This has been fixed in 446d2a7422adf21e902d91ecc01e50bf50156c28.


F/xcake action

Adds action to run xcake command for  https://github.com/jcampbell05/xcake/

What does the second commit (https://github.com/jcampbell05/fastlane/commit/8b7ca848114db8a94940729de4a4bfd97efff44e) do in here?

@KrauseFx  I'm not sure, this showed up when I tried to squash. Must have been from a merge commit.

Looks great, thanks @jcampbell05 :rocket:


Bugfix duplicate+parallel http requests per part

If the same part is requested multiple times in quick succession, then multiple parallel HTTP requests will be fired. The fix here, makes sure that there's only 1 HTTP request per part.
Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[x] Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your master!
[x] Make sure you are making a pull request against the canary branch (left side). Also you should start your branch off our canary.
[x] Check the commit's or even all commits' message styles matches our requested structure.
[x] Check your code additions will fail neither code linting checks nor unit test.

Description
Please describe your pull request.
💔Thank you!

The change you're attempting here will cause an unexpected behavioral change because no subsequent call will ever create a new request, regardless of the success or failure of the original call, whereas the original code would try again. If the code using the partial loader has its own logic to retry the part registration/fetch (perhaps because it has some server status monitoring), then your implementation will cause a regression.
I propose a more extensive change to chain promises for subsequent calls. Such an implementation will allow subsequent calls to execute a retry on failure, but no parallel HTTP requests will be made and success will pass through without extra requests. This is in-line with the intent of the original logic, which prevents duplicate requests on success. I made this change for our app but have not had an opportunity to resolve why I can't push to this repository yet; here is a diff with my changes: https://www.diffchecker.com/3CroelqL

Thank you both. It will take some time looking into it.

Sorry for the delay, but it has taken a while.
The only change is that the result of the complete request incl. post processing (say line 63 self.tables[lang]) will be stored in this.tables[lang]. (Note: this and self are the same, so the change should be using the alias self avoiding any confusion).
So, we have three scenarios:

The request is be successful (calling then()): The change will override the already existing data because this.tables[lang] would have been refreshed already.

The request is not successful and an errorHandler is given: On a successful alternative response, the tables will be refreshed with new data. Otherwise see 2.2
The request is not successful and no errorHandler is given. No update of the tables.

But as a result of this change, always there will be a promise stored in tableswhere it should not be. And all others do not expect a promise in a table.

Process of loading fixed, replaced by #1692


Update Thermal Expansion Routines to Not Use Linearized Form

Description
This PR removes the unnecessary use of the linearized form of thermal expansion in ARMI. There are several to-do items remaining before this PR is ready to open:

[x] ARMI unit tests (coverage failure in CI looks like coverage spray)
[ ] fix unit testing in downstream applications
[x] update ARMI docs
[ ] determine merge order for downstream application updates

During downstream testing, a corner case was found that was not previously accounted for. When a block is not expanded/contracted, but its volume changes due to the changes from the blocks below it, its number densities were not updated. E.g., using one of the test fuel assemblies defined in armi/tests/refSmallReactorBase.yaml, if only the fuel components are artificially expanded, the plenum block will have its volume shrunk but not have the number densities updated (no growth factor for the components within it, but the number densities have changed). Commit https://github.com/terrapower/armi/pull/1279/commits/312aed7bdf0e5344b1d47586535f4c074c07284d addresses this by setting the growth factor equal to the change in volume of the block.

Checklist

[x] This PR has only one purpose or idea.
[x] Tests have been added/updated to verify that the new/changed code works.

[x] The code style follows good practices.
[x] The commit message(s) follow good practices.

[x] The release notes (location doc/release/0.X.rst) are up-to-date with any bug fixes or new features.
[x] The documentation is still up-to-date in the doc folder.
[x] The dependencies are still up-to-date in setup.py.

@alexhjames, please provide a review when available to.

@onufer @ntouran @jakehader fyi. The origin of this work is that it's an identified update for a release for a downstream application.

@sombrereau if this affects your project(s), let me know and I am happy to help resolve and provide necessary updates.
@drewj-usnctech a heads up, this will likely affect any internal testing suites you may have. I'd offer to help resolve, but I doubt that I can.

@albeanth Just two comments. I didn't really look through the test changes outside of linearExpansionFactor as I'm not well suited to reviewing those.

@albeanth, can you explain a bit more in the PR description of what the change is, what it means, and why it's needed, and is it generally correct for all materials?

I'm not sure this is physically correct. Thermal expansion data measured by dilatometer is almost always reported at deltaL/L0, so essentially "engineering strain" form, should be used for consistency with how the material properties were measured and are defined. Some discussion: https://www.continuummechanics.org/hydrodeviatoricstrain.html#volume_strains and https://www.continuummechanics.org/truestrain.html

@albeanth / @alexhjames please set up a time to discuss. Also, I'm not sure if the PR description about the change in volume for the plenum makes sense to me just yet but I think these are two separate changes in a single PR that may be independent?


Doesn't work instantly on launch

The extension works perfectly fine if chrome is already open, and you open a link from within chrome or any external app.
But if chrome is not open, and you open a link from another app, it doesn't work (You have to refresh the website then it works)
I only use for meet and classroom. I don't know why this happens. Or maybe I am doing something wrong?

@Techy05 it does work when opening the link from external app.
For example, when I open the Google Meet app, it redirects me to the correct account.
It can be that your URL already has the account specified, like "https://meet.google.com/nfw-mzoz-zjs?authuser=1"
In that case the extension respects the already specified account, and does not redirect.
If the link is without the account, like "https://meet.google.com/nfw-mzoz-zjs" — the extension would redirect to your specified default account.