Buffering

In this page: http://holoviews.org/user_guide/Streaming_Data.html
There is this bit code:

%%opts Curve [width=500 show_grid=True]
source_df = streamz.dataframe.Random(freq='5ms', interval='100ms')
sdf = (source_df-0.5).cumsum()
raw_dmap = hv.DynamicMap(hv.Curve, streams=[Buffer(sdf.x)])
smooth_dmap = hv.DynamicMap(hv.Curve, streams=[Buffer(sdf.x.rolling('500ms').mean())])
raw_dmap.relabel('raw') * smooth_dmap.relabel('smooth')

used to stream a random series and its mean to a graph.
How can I create my own buffer? I already have a function, let's call it 'getBuffer(input)', that returns me the values which I want to feed my buffer (as int). How can I invoke streamz.Stream.buffer() along with my custom getBuffer() function to get what I want (namely a streamz buffer)? I know I would have to feed a 'Streamz Buffer' type in the boldfaced area, but I don't know how to call streamz.Stream.buffer().

ps: I'm completely new to streamz and holoviews.

Apologies for the delay in replying. I suggest you skip streamz and just use Bufferdirectly, which is documented in that tutorial. Since this is a support question I'll close the issue but you can join us on Gitter: https://gitter.im/ioam/holoviews


[VTA] Support TLPP in function simulator.

Issue:
currently vta function simulator just doing serialized instruction
execution, the dependency logic of runtime ISA which use for task
level pipe line parallelism can not get verified by function simulator.
Solution:
make the simulator driver to be multiple thread and support TLPP.
Benefit:
TLPP support VTA function simulator would make VTA logic testing/debug
/change more easy.

Thanks for the contribution, some general style nits, we use Google C style that means CamelCase for functions, 2-space indent. etc. We might also need someone who is familiar with multi-threading to review the specific logics

Thanks for the contribution, some general style nits, we use Google C style that means CamelCase for functions, 2-space indent. etc. We might also need someone who is familiar with multi-threading to review the specific logics.
Personally, I think we don't need to use multi-threading, but instead having an event driven queue that schedules the events, and insert random interleaves might be fine(and also makes behavior reproducible)

@tqchen , thanks for the kindly follow up,  about the style issue yes i would address it.
about the multi-thread concern, the MT logic is very less and most related start/stop the thread, the cross thread synchronization totally depend the TLPP dependency and actually we not add much additional complexity to simulator, even we move to "event queue" solution, the most logic should be same, but we would lost the real parallel simulation.
another reason for MT is scale, we ever did some try to scale vta in house but found actually no good tool to verify these changes, TSIM is a option, but it is much complex for software engineer to do change, and function simulator looks more friendly, a MT simulator should be a good start to handle such scale  requirement because by launch more thread we can easily simulate multiple gemm/load/store core.
please kindly let me know how you think.

Hey @huajsj
Thanks for the contrib, here is my take on this.
Multi-threading support for functional simulator will only provide simulation-performance benefit or simulation time will be short.
However, if you want to use this infrastructure to have an idea how thread-level-parallelism would work then you got it wrong. The reason is that you are still assuming that Load, Compute and Store are executing on an infinite-clock-speed (functional simulator) but in reality each block/instructions will have different timing based on many factors. Therefore, having multiple threads executing at the same time but finishing early (infinite-clock-speed) won't help much in terms of analysis.

Hi @vegaluisjose ,
Thanks for the comments,  the most advantage of MT simulator with TLPP support is to decouple VTA software developing and hardware developing to make them be parallel,  before without MT TLPP support in simulator,  to verify a VTA change that need both hardware and software ready, and debug also cross hardware and software and difficult for narrow down, performance is a possible benefit but not the main target.
about the parallel analysis, I agree MT simulator can not help in clock level analysis,  but besides of that we also need to verify the synchronization logic between parallel load/compute/store, for this part a MT simulator would can help.
a idea scenario is first using function simulator verify vta run time change and finish software part logic independently, then(or parallel)  working on Emulator(TSIM) or FPGA to finish hardware change , after software and hardware ready then do the integrate.

@tqchen @tmoreau89 @vegaluisjose , the code style issue already addressed, could you please help to review this patch? thanks.

Thank you @huajsj for the contribution!
I don't fully understand how this change helps "decoupling VTA software developing and hardware development", do you mind further elaborating?
Re: "verify the synchronization logic between parallel load/compute/store" I'm not fully convinced that this will help us catch bugs, can you provide an example where the old simulator would not catch a synchronization bug that this simulator would catch?

Do you mind running some simple benchmarks (say the resnet example under vta/tutorials/frontend) and time the performance of the old simulator vs. this parallel implementation?

Thank you @huajsj for the contribution!
I don't fully understand how this change helps "decoupling VTA software developing and hardware development", do you mind further elaborating?
Re: "verify the synchronization logic between parallel load/compute/store" I'm not fully convinced that this will help us catch bugs, can you provide an example where the old simulator would not catch a synchronization bug that this simulator would catch?

Hi @tmoreau89,
Thanks for the follow up,  about catching bugs and decouple HW SW developing help, I can explain that from my experience, I ever did a vta change to let compute module do the 'weight' loading instead of let load module do that, doing so means we need to change the VTA runtime logic and hardware change, I first did the change in VTA runtime . I run it on simulator and every thing is work, then I changed hardware and i put new hardware with this new runtime together, the hardware stuck,  the problem trouble shooting very consume time ,first bitstream build time is very long, secondly the hardware debug is not so straightforward, Finally I found the issue caused by a dependency setting issue and be VTA Runtime problem, but to find such root cause I need to spend lot of effort in hardware part for isolation, if that time simulator can do the synchronization(tlpp)/dependency check, I can find the run time problem without involve hardware and save time, that is what i means , software and hardware developing decouple and catch bug help.
Regards
Hua

Do you mind running some simple benchmarks (say the resnet example under vta/tutorials/frontend) and time the performance of the old simulator vs. this parallel implementation?
@tmoreau89 , just tried resnet example, first run it on original TVM(no any change), but get some error 'NNVMError: KeyError: 'tile_ic'',  seems like this a new issue, not experience such issue weeks ago,  do I need to wait this issue get fixed, or any work ground can help?

old nnvm reset example still work , run it with old simulator and new one , get following data, the old simulator is faster.
old: 1.48 seconds
new: 2.68 seconds

Thanks for the reply; it seems like the runtime degradation is quite a bit higher. Can we find a middleground of catching synchronization bugs as you did earlier on without having to increase complexity due to the multi-threaded nature of this simulator implementation?

@tmoreau89 , unfortunate there is no other way can help to trouble shooting such sync bug in software level,without TLPP logic in simulator that actually should be there default. what I did before is to review code and debug in hardware, but that is not a good experience and very consume time.
some time overhead should be make sense  because time that coming from old simulator actually is not real( older simulator not check the dependency of instructions). in this patch I provided a configuration to disable simtlpp when user more concern time instead of VTA run time logic verification, do you think that may help?

I do think that the multi-threading can be de-coupled with the event driven and async flow. We could have the event queues but drive them in a single thread(or optionally de-couple to multi-thread)

@tqchen , thanks for the follow up,  seems like a single thread solution is more prefer, yes i can work for a solution with ST support, beside of that , is there any concern about "time performance"? after adding additional TLPP logic , for sure time would increase, with remove MT such time may increase more than MT solution, could I know how you think about time performance?

I think as long as we don't have order of magnitude time decrease it should be fine.
I also doubt if event driven code will slows things down, depends on how we implement it it might get similar perf if the execution of the logic is the bottleneck.

Thank you for clarifying @huajsj ; I do see utility in your contribution now; what it asserts is that if a dependence is not enforced properly (say a deadlock, or starvation), it will be caught by this new simulator rather than run correctly in simulation; then hang in hardware. What you are striving for is catching errors that would occur in hardware   during simulation, correct?

One thing I'd argue (and I believe @tqchen and @vegaluisjose agree) is that MT is not necessary to ensure correctness of dependence mechanmisms. We can use some type of event driven loop; it might even improve performance, and reduce complexity of the code (MT code is hard to debug).

Thank you for clarifying @huajsj ; I do see utility in your contribution now; what it asserts is that if a dependence is not enforced properly (say a deadlock, or starvation), it will be caught by this new simulator rather than run correctly in simulation; then hang in hardware. What you are striving for is catching errors that would occur in hardware during simulation, correct?

@tmoreau89 , yes, to catch errors early in simulator instead of doing trouble shooting in hardware is what this patch try to do, thanks for the more clearly explain.

@tqchen , @tmoreau89, about ST mode, yes I would work for a ST mode change and update later, thanks for the follow up and comments.

@tqchen @vegaluisjose @tmoreau89 ,  the TLPP single thread change already done, please help to review once you have time, following are the performance number.
old simulator:  1.44 seconds
new simulator: 1.44 -1.46 seconds

Thank you for the update, @huajsj ; the performance degradation looks a lot more tolerable

I made a few small comments about naming the functions and using consistent scheme. For guidance please follow: https://google.github.io/styleguide/cppguide.html

@tmoreau89 , thanks for the help, the style and cmake commets already get addressed, please kindly let me know if you have any other comments.

@huajsj I was thinking, is there any reason why we would ever want to turn USE_VTA_FSIM_TLPP off? Perhaps we should just build the simulator with TLPP simulation on all the time, since it doesn't affect performance and it will catch more bugs than the current simulator.

@huajsj I was thinking, is there any reason why we would ever want to turn USE_VTA_FSIM_TLPP off? Perhaps we should just build the simulator with TLPP simulation on all the time, since it doesn't affect performance and it will catch more bugs than the current simulator.
@tmoreau89 , sure, the tlpp control macro USE_VTA_FSIM_TLPP already get removed.

Great thanks!

I'll go ahead and merge the changes


Anticlockwise Support

Could you please support anticlockwise direction? This is a quite common requirement.

You can simply use progressView.transform = CGAffineTransform(scaleX: -1, y: 1)

Duplicates #36


Add KeyVault hosting statup attribute injection

https://github.com/aspnet/AzureIntegration/issues/160
We can't use AssemblyInfo because our attribute has a non-string parameter.

I'm not familiar with the desired behavior here. Is this meant to add this attribute to all projects that reference icrosoft.AspNetCore.AzureKeyVault.HostingStartup?
Also, was this approved for the 2.0.x patch? Maybe you meant to target release/2.1

I'm not familiar with the desired behavior here. Is this meant to add this attribute to all projects that reference icrosoft.AspNetCore.AzureKeyVault.HostingStartup?

Yes

Also, was this approved for the 2.0.x patch? Maybe you meant to target release/2.1

Part of work approved in https://github.com/aspnet/AzureIntegration/issues/137

Talked in person. This would cause _AssembyInfo.KeyVaultHostingStartup.cs so appear in the solution explorer in VS for all projects referencing it. We might need to use MSBuild to generate this code instead. Should be <50 lines of msbuild.
cc @danroth27

Added target to hide the file.


return an error message when processing a corrupted tarball

:convenience_store:
Closes https://github.com/opscode/supermarket/issues/950

:+1:


School Upload

https://www.ulsachihuahua.edu.mx
https://www.ulsachihuahua.edu.mx/tecnologias-de-la-informacion-inter

@BraianAvalos First stage of verification passed, official domain is ulsachihuahua.edu.mx as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@BraianAvalos Pull request merged. Thank you.


retry: be more robust against transient failures

Apertis' OBS server suffers from sometimes long(ish) periods of time during which it issues 504. This causes the job to fail after 10 minutes whereas it would succeed if we kept retrying.
As a temporary workardound, let's ignore the retry time limit for now, so the job will keep trying until successful or the process is killed (e.g. by cancelling the job).
Fixes #11

The latest updates have removed timeouts fixing the same :)


Alpha 9: 'md-button' is not a known element

Hi everyone,
I encountered a bug while upgrading to the new version of material.
In my main and library modules, I removed all imports of the different material modules I use and replaced them with the single import of MaterialModule.forRoot().
However, when I now load my app I get the following error: 'md-button' is not a known element. This makes me think there is something wrong with the import. Any thoughts?

You only call MaterialModule.forRoot() in your appmodule. Every other module must import MaterialModule but without forRoot().

Thanks for the feedback. I did that but it didn't solve the problem. Fixed it now.  is apparantly no longer a directive. Changing it to  fixed the problem.

Oh didn't know that it was always that way. Been using it always that way
Bla


Fixed error in PinDclNode code generator. Corrected by visiting right child instead of left.

 Fix PinDclNode code generation


Rethink snake_case to camelCase prop conversion

Current Situation
The snake_case to camelCase prop conversion was created with the theory that it should be zero impact.
Related PR:

https://github.com/reactive-python/reactpy/pull/919
https://github.com/reactive-python/reactpy/pull/841

However, we've received our first report of this behavior causing incompatibilities with third party libraries. In this case, it was related to the Google auth library.
Proposed Actions
Either revert this change, or make it togglable through configuration settings.

my opinion is that, in general, magic changes like renaming things aren't preferable. There's a couple things to consider about this:

These are key values in a dictionary so there's no obligation to change the name to match a naming convention, because there is no naming convention
Keeping values identical to the naming convention of React makes knowledge more transferrable. For example, GPT-4's first assumption is that the keys use camelCase. Reverting the change would align things with how one would intuitively expect them to behave
Renaming breaks "grepability". If I wanted to see all references to where something comes from, from the perspective of the front-end, I now need to know ahead of time that a different name is used. Maintaining grepability is a huge plus to the developer experience and efficiency.
As we saw, renaming creates a point of friction when using 3rd party libraries that expect things to be named exactly like their script expects.

As far as implementing the corrected behavior - one could use a new keyword argument that doesn't make the mutation, and the position argument could be deprecated. Once the old positional argument is removed, the keyword argument could become the new positional one at a later minor version.


Fix node_modules sourcemap config (which will fix VSCode debugging of CRA apps)

This PR fixes #6044 and fixes #6296, which are sourcemap-related problems that make the VSCode debugger unable to debug code in node_modules of CRA apps.  "Unable to debug" means:

breakpoints set on node_modules code trigger on different code lines than where the breakpoint was set
stepping into node_modules code will highlight the wrong line, and sometimes even the wrong module!
selecting a particular frame in a call stack will highlight the wrong line in a node_modules file

The cause of this problem was a Babel config change in #5096 from Sept 2018:
https://github.com/facebook/create-react-app/blob/57ef103440c24e41b0d7dc82b7ad7fc1dc817eca/packages/react-scripts/config/webpack.config.js#L432-L436
The goal of that change was to force debuggers to show transpiled code instead of original source.  Unfortunately, that's not what it did. Webpack still generates a sourcemap for node_modules (to see it, open https://localhost:3000/static/js/0.chunk.js.map in any CRA app in dev mode), but this sourcemap doesn't match the code that Babel generated for each module. Notably there are differences in whitespace (extra blank lines) and comments between the sourcemap code in sourcesContent and the original source.  When VSCode tries to set a breakpoint or step into node_modules code, the sourcemap points to the wrong line in the webpack node_modules chunk.
BTW, this explains why the problem doesn't show up in the Chrome debugger, because the Chrome debugger only uses the inline sourcesContent code in the sourcemap-- it ignores the actual source files on disk. VSCode, however, will try to load the original source files from disk using the sources array in the sourcemap. This provides a better debugging experience-- for example, if you quit your debug session the same source files are still loaded, and you can set breakpoints before your app is running to debug startup behavior.
Anyway, this PR changes Babel config to ensure that Babel is correctly generating sourcemaps for node_modules code. Heads up: it will likely make build times longer, because the original change in #5096 made build times shorter.
To validate that the PR is working, use the following steps:

git clone https://github.com/justingrant/cra-sourcemap.git - this repo is unaltered CRA boilerplate code. The only changes I made was to add VSCode config files to make it easier for VSCode newbies to get a debug session going to repro the problem and validate the fix.
Open VSCode
Choose File->Add Folder to Workspace and choose the cra-sourcemap folder you cloned above
Open src/index.js in the IDE editor
Set a breakpoint on the call to ReactDOM.Render. If you don't know how to set a breakpoint in VSCode, one way to do it is to set the cursor on that line of code and press F9.
yarn start
Press F5 to start a debug session.  It should start debugging immediately, but if you're asked, choose "Chrome" from the dropdown menu and then it will start.
Now refresh the browser. This should trigger the breakpoint you set above.
Click "Step Into", which is the down arrow on the debug toolbar.  Or press F11.

You'll now be in some webpack boostrap module-loading code that you'll need to get out of, so press Step Into (F11) a few more times until the editor returns to index.js. Now it's actually ready to call into React code.
Now click Step Into one more time.

Expected (after PR is applied):
IDE highlights the first line of createElementWithValidation(), which is what ReactDOM.Render resolves to inside React's original source code.

Actual (current behavior):
A line of code is highlighted in the middle of a method-- it's clearly the wrong line.

BTW, to validate this PR I wrote a webpack plugin that compared the code in sourcesContent of 0.chunk.js.map to the actual code sitting on disk. I ran it on my main project and got 870 of 1029 source files don't match the source map static/js/0.chunk.js.map.  Then I ran it against the PR configs and zero mismatches were reported.
Here's an excerpt from the plugin's output for current CRA configs, omitting the first 867 (!!!) mismatched files:
/Users/justingrant/Documents/hdev/h3/web/node_modules/webpack/buildin/global.js doesn't match sourcemap, starting at line 1, col 7
Original Line 1: var g;
     Map Line 1: var g; // This works in non-strict mode
Original Line 2:
     Map Line 2:

/Users/justingrant/Documents/hdev/h3/web/node_modules/webpack/buildin/module.js doesn't match sourcemap, starting at line 1, col 26
Original Line 1: module.exports = function(module) {
     Map Line 1: module.exports = function (module) {
Original Line 2:        if (!module.webpackPolyfill) {
     Map Line 2:   if (!module.webpackPolyfill) {

/Users/justingrant/Documents/hdev/h3/web/node_modules/zen-observable/lib/Observable.js doesn't match sourcemap, starting at line 7, col 33
Original Line 6:
     Map Line 6:
Original Line 7: var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
     Map Line 7: var _createClass = function () {
Original Line 8:
     Map Line 8:   function defineProperties(target, props) {

WARNING: 870 of 1029 source files don't match the source map static/js/0.chunk.js.map

I just noticed that @gordonmleigh pointed me back in March to exactly the solution implemented in this PR.  But I didn't notice his comment. Arrrgh. Anyway, kudos to Gordon for figuring out the solution. I could have saved a lot of time by paying closer attention!
Gordon also had a related suggestion which is to add source-map-loader to webpack config. Doing this will make it possible to "drill down" while debugging into the original source of node_modules libraries which have themselves been transpiled and bundled.  Unfortunately, source-map-loader has a bad problem currently which is that parent-relative links (e.g. ../src/foo.js) are not resolved properly. There's a pending PR from @Volune that fixes this problem (and improves performance and error messaging too) so I'm planning to wait until that PR lands in source-map-loader, and then I'll do a follow-up PR to see if we can get source-map-loader into CRA to make debugging even better.
BTW, if any CRA maintainers are reading this, could you unlock #6296 so I can close the loop for people who come to that issue looking for answers?  I'd like to refer them to this PR.

Until this gets merged, should we be on an older version of react-scripts?
Right now this breaks error logging in bugsnag (maybe Sentry? I haven't checked)

@justingrant Thanks for the PR. Sorry we haven't looked yet, it's been very busy few months. Do you have a sense of how much slower this makes the build?

@gaearon - no worries, thanks for taking a look!  In totally unscientific testing with my largest project on my dev machine (2015 MBP), I'm seeing about 10% slower npm start (measured from starting the command to the URLs being displayed in the terminal) with this PR enabled. Without the PR it's 11 seconds, with the PR it averaged a little over 12 seconds.  For npm run build, the times were 21s with the PR, 17s without the PR, so about 24% more.  You guys have access to much larger CRA projects than I do, so YMMV.
In a minimal project like the repro repo in this PR, the difference was also too small to accurately measure-- a few hundred msecs or less.  Hot reloads on my biggest project were also too fast to reliably tell the difference between with and without the PR.
Given that performance-sensitive users already have a command-line option to disable sourcemaps completely, it seems like folks who are concerned about build times already have a way to speed things up much more than 10%.  But newbies who want to fix bugs or to understand react or other libraries by debugging into them with VSCode (or any IDE whose debugger matches sourcemaps to files like VSCode does) have no easy options today regardless of perf impact. Given CRAs prime directive as the on-ramp to the React ecosystem, I'd argue for "it just works" being the default.  Folks with big apps or who are obsessive about initial build time can (like they already can today) opt into faster builds by turning off sourcemaps.  What do you think?

I rebased to catch up with the last few months of commits. No changes on my end.  Hope that this can make it into 3.2!

Looks like 3.2 shipped and this is in the 3.3 list. It would be awesome to see this in 3.2.1 to get it sooner though!
Myself and colleagues have been using 2.1.4  which seems to be the last version with fully working VSCode debugging (as noted here: https://github.com/facebook/create-react-app/issues/6074#issuecomment-475505177)

Thanks a lot, this looks great!


Update dependency from Dotnet 7.0 to Dotnet 8.0

Dotnet 7.0 has reached its end of life.  The download page for Dotnet Runtime recommends upgrading to Dotnet 8.0.

Currently blocked by https://github.com/microsoft/vscode-azurearmtools/issues/1733


noInterfaceFoundText: 'No supported webcam interface found.'

I open the ACTIVEX of IE ,then I solve the question

No supported webcam interface found

This issue got resolved for me when I hosted my website over https


Open and close Sections in Module menu

I do often need screenshots that show where in the module menu the module can be found. usually it is a good thing to close all sections and just open the section you need. Afterwards to "clean up" i need to open everything back up. Everything I tried didn't work out except always waiting a second. This leads to long and not nice sections for a simple task. Can we somehow simplify this? It takes a long time to run and it is just confusing to have it like that in the json.

          {"comment": "Close all Module Sections"},
          {"action": "switchToMainFrame"},
          {"action": "click", "link": "button#web"},
          {"action": "wait", "timeout": "1"},
          {"action": "click", "link": "button#site"},
          {"action": "wait", "timeout": "1"},
          {"action": "click", "link": "button#file"},
          {"action": "wait", "timeout": "1"},
          {"action": "click", "link": "button#system"},
          {"action": "wait", "timeout": "1"},
          {"action": "click", "link": "button#tools"},
          {"action": "wait", "timeout": "1"},

  {"comment": "Modules Admin Tools"},
          {"comment": "************************************"},

          {"action": "click", "link": "button#tools"},
          {"action": "wait", "timeout": "1"},
          {"action": "scrollModuleMenuTo", "toSelector":  "button#system"},
...

          {"action": "click", "link": "button#tools"},
          {"action": "wait", "timeout": "1"},
          {"comment": "************************************"},
          {"comment": "Modules System"},
etc...

          {"comment": "Open all Module Sections again"},
          {"action": "click", "link": "button#web"},
          {"action": "wait", "timeout": "1"},
          {"action": "click", "link": "button#site"},
          {"action": "wait", "timeout": "1"},
          {"action": "click", "link": "button#file"},
          {"action": "wait", "timeout": "1"},
          {"action": "click", "link": "button#system"},
          {"action": "wait", "timeout": "1"},
          {"action": "click", "link": "button#tools"},
          {"action": "wait", "timeout": "1"}

To show the menu item you could use action scrollModuleMenuTo instead.

I do want to make pictures like these:
https://docs.typo3.org/m/typo3/tutorial-getting-started/master/en-us/_images/CreateNewGroup.png
Scrolling doesn't give me the same overview over the module menu

Mh, i would keep it streamlined and decide to always show the menu folded or always scroll to the menu item. With the current implementation it is intended to always scroll to the menu item: Are you sure, that your new approach is worth the additional effort? The default backend module menu is unfolded so at least i would prefer to see it like that in the documentation too.
Nevertheless, what would happen, if you remove all timeouts except the last one:
{"comment": "Close all Module Sections"},
{"action": "switchToMainFrame"},
{"action": "click", "link": "button#web"},
{"action": "click", "link": "button#site"},
{"action": "click", "link": "button#file"},
{"action": "click", "link": "button#system"},
{"action": "click", "link": "button#tools"},
{"action": "wait", "timeout": "1"},

If I don't wait in between the clicks fail. If I wait for the submenu by id then it gets only half loaded.
If you compare the two screenshots:
https://docs.typo3.org/m/typo3/tutorial-getting-started/master/en-us/_images/CreateNewUser.png
And
https://docs.typo3.org/m/typo3/tutorial-getting-started/master/en-us/_images/BeUsersModule.png
I just think, that the earlier one gives the better overview and is cleaner and less distracting. And it has often been done like that in manual screenshots. Of course that is a philosophical question. As it is it however messes up the whole screenshot.json and is hard to controll.
Except in rare cases where we want to show an overview of the complete backend this would be my prefered way of doing it....

What does "clicks fail" mean: Is there an error thrown?

I am sorry, I don't have the json like that anymore. I just kept trying until some setup did what I need. So I can't get the exact error for you but yes there where error messages. Something like: "Another element would receive the click" or Element not found as it would flow out of focus by the other parts still moving

Ok. I suggest to keep using the action scrollModuleMenuTo in an unfolded module menu for the moment. And you can create a new issue of type "enhancement" with the target to create a next module menu action which folds the menu accordingly which can then be easily applied to all screenshots.json by search & replace for scrollModuleMenuTo.

Thats a good idea


skip box won't start on OS X el capitan

BlueFin-MacBook-Pro:skippbox imusayev$ npm start

<EMAIL_ADDRESS>start /Users/imusayev/skippbox
nw

[3773:0126/114133:WARNING:dns_config_service_posix.cc(151)] dns_config has unhandled options!
[3773:0126/114133:INFO:CONSOLE(103)] "", source: file:///Users/imusayev/skippbox/js/controllers/services.js (103)
[3773:0126/114133:INFO:CONSOLE(107)] ""Error: [$injector:undef] http://errors.angularjs.org/1.4.5/$injector/undef?p0=config\n    at Error (native)\n    at file:///Users/imusayev/skippbox/js/lib/angular.min.js:6:416\n    at Object.$get (file:///Users/imusayev/skippbox/js/lib/angular.min.js:37:32)\n    at Object.e [as invoke] (file:///Users/imusayev/skippbox/js/lib/angular.min.js:39:96)\n    at file:///Users/imusayev/skippbox/js/lib/angular.min.js:40:410\n    at d (file:///Users/imusayev/skippbox/js/lib/angular.min.js:38:308)\n    at Object.e [as invoke] (file:///Users/imusayev/skippbox/js/lib/angular.min.js:39:64)\n    at Q.instance (file:///Users/imusayev/skippbox/js/lib/angular.min.js:80:151)\n    at L (file:///Users/imusayev/skippbox/js/lib/angular.min.js:61:140)\n    at g (file:///Users/imusayev/skippbox/js/lib/angular.min.js:54:326)"", source: file:///Users/imusayev/skippbox/js/lib/angular.min.js (107)

thanks for reporting the issue @serverchief looking into it.

Can you try to hit CMD + R

@runseb @serverchief Check your version of Chrome? Found some hits on nwjs forums as well as the atom repo on this error, it seems like there's been a patch in Chrome to fix it.
In Atom's case it was not a fatal error, doesn't seem like it should be for nwjs either.

Hi @runseb @serverchief
This issue occurs when you have no ~/kube/config file.
The fatal error was due to the fact that an Angular factory always expect a return object.
Additionally, the error message was not printed in the logs.


Add support for the quarto filetype

Quarto is a pandoc-based extension of the rmd format: quarto.org

Thanks for adding this. With all the markdown sub-formats around, is there a way to handle all of them in one go? I don't know much about them, but it would be very handy to have.


align text with the initial value

An alternative fix in code like here
input.validate+label {
    text-align: initial;
}

Instead of putting it only on the validate class, I put it on input-field > label. It was just one line so I made the change myself here 4df1e100dd1301cdba5b7b38046d739f52b2becc

Perfect.


Detect version of squid installed. Fix issue #50

Description
Detect version of squid installed automatically. Before version of squid installed were hardcoded according to Linux distribution & version. It didn't work well since squid version is sometimes changed in the same distribution (e.g. Ubuntu 14).
Moreover bug with bad service name is fixed for Ubuntu 16.
Issues Resolved
Issue #50
Issue #67
Check List

[x] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[n/a] New functionality includes testing.
[n/a] New functionality has been documented in the README if applicable
[x] The CLA has been signed. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

@jpmat296 You'll need to rebase these changes with the DCO sign off. Sorry the docs in this repo still refer to the CLA. See https://blog.chef.io/2016/09/19/introducing-developer-certificate-of-origin/ for some more information.


ci: Pin Kvrocks docker image to 2.5.1 to avoid test failure

This closes #3191

@git-hulk do we have a corresponding ticket in Kvrocks side so that we're notified when the upstream issue fixed?

Yes, @Xuanwo has filed an issue to track this and resolved now, but need to wait for the next release. Refer: https://github.com/apache/kvrocks/issues/1783


pull request for e2e test at 12/10/2016 23:26:03

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add builtin emoji support

Before this series of commits, the emojis shown on the device where vendor-specific and relied on the keyboard to be inserted. Now, there's an integrated popup where one can insert emojis. Also, the displayed emojis are changed, as shown on the image:

The library that I used was vannkitec's, but some changes were needed to integrate it on this project, so I made a couple of modifications for that purpose. Until the new build is released, those changes are only available on the snapshot.
The emojis used are the ones from emoji-one for personal reasons (those were the ones I liked the most); but it can be changed easily modifying the dependency.
For more discussion about the need for built-in emoji support, refer to #819
I tried to follow the contribution guides; but I may have missed something. In that case, I'd appreciate some comments and I'll try to fix whatever problem there may be.
Signed-off-by: Foo-Manroot<EMAIL_ADDRESS>

Hi @Foo-Manroot ,
Thanks for the PR. Contribution guide has been followed :) . We will discuss internally to decide if we can merge it. Do you know what can be the impacts on the other client (iOS/Web) when emojis are sent?
Benoît

This is just an aesthetic change, as the message is the same. It just differs on its presentation to the user. On riot-desktop there's already a builtin emoji set (incidentally, the same set as the one I used, from EmojiOne), so they're viewed exactly the same.
As per other clients, they'll still see the emojis exactly the same as they've until now. For example, this is a comparative of this app before this pull request (the latest version on F-Droid), this app after the PR and Riot-desktop:

Before PR
After PR
Desktop

(the background colour of the second image is black because I had the two apps installed, and I wanted to distinguish between them... :D)
As I say, on the rest of clients the emojis will appear as always has been.

When users use android-riot app - they see emoji from android.
They are often better then on a PC.
If we are remove this "feature" and all emoji will be such as PC - this is will bad for users.
Compare emoji from Telegram and desktop riot:

Default emoji in riot is ugly.
This is no problem fore geeks and hackers - they are use textual smiles such :-) and :), :(
But it is major for any other girls and womans. We
We do not want the matrix to use only geeks? I thin we want, that matrix will use many many people. :-)

I... don't really know what's your point, @progserega; but I think there has been a consensus over at #android:matrix.org about giving the option to use these new font or the default one through configuration.
Right now I'm quite busy and I don't think I may be able to take a look at it in a while, but I encourage anyone to try to implement this as configurable feature.

ok


Add Speech Recognition to Search Bar

This feature should be accessible and provide accurate voice recognition.

@codervivek5
Please assign this issue to me under GSSoC'24.

Any update?

please assign me this issue i will try to solve it

Can you assign me this issue? I have implemented speech recognition before using APIs

Assign to me.

@codervivek5 assign this to me i will definatily do it today

@codervivek5  Can you assigne this issue to me ? We can use react-speech recognition to make this feature


Add files via upload

Please add the file inside the CP folder. And thanks for collaborating with me!!


error: Error:Could not find property 'plugin'

Hi I just started to learn android, I use Android Studio.
I got error:
Error:Could not find property 'plugin' on com.android.build.gradle.LibraryExtension_Decorated@176deea7.
How can I fix it? thanks > <

I'm not sure what this is from. Can you post you build.gradle files? Also what version of gradle are you using?

I download the project zip file, open it with Android Studio.
first I got
"Error:Gradle 2.4 requires Android Gradle plugin 1.2.0 (or newer)  but project is using version 1.1.0. Please use Android Gradle plugin 1.2.0 or newer.
Fix plugin version and sync project"  <= I click this ,
then I got :
Gradle 'SimpleBluetoothLibrary-master' project refresh failed
Error:Could not find property 'plugin' on   com.android.build.gradle.LibraryExtension_Decorated@385b9d3d.      <=@xxxxxx are different
I try paste:  'com.github.developerpaul123.simplebluetoothlibrary:library:1.3'
in dependencies ，the error always appear again.

This should be fixed in the new version (I hope) update your build.gradle line to the following:
'com.github.developerpaul123.simplebluetoothlibrary:library:1.4@aar'

Did that solve the problem?

Please use the Jitpack.io releases now


Animation doesn't seem to be working, or maybe I have to do something to use it

I tried the animation glTF samples, e.g. AnimatedTriangle. When it's imported, I don't see any animation on the triangle's rotation (as specified in the glTF file) or any keyframes in the graph editor. I see in the import code it's doing something with the animation, I just don't know how to get that to actually animate.

Perhaps I can help implement it - it's an important feature for me. I don't know the Blender API hardly at all, but I did just write a glTF exporter. Do you know a good resource to start with the Blender API?

Hello guys,
I am working on another glTF 2.0 importer implementation for one of my client,  where animations (objects / ShapeKeys / Rigs) should work :
https://github.com/julienduroure/gltf2-blender-importer
Please have a look on it :)

There is some animation loading working on my dev branch.

Hi!
How to add keyframes to fluid simulation in blender so that it can be imported to Unity to work smoothly? @garyo @scurest

Animation support is in the latest release; just tick the "Import Animations" box when you import. There's some support for the EXT_property_animation extension too.
An animation is imported as a set of actions, one for each object, named like animation name@object name. The first animation plays by default. You can switch what action is played on a object through the Action Editor in the Dope Sheet.


chore: apply stricter linter config

What kind of change does this PR introduce?
ci
What is the new behavior?
inspired by https://github.com/google/go-github/blob/master/.golangci.yml
Additional context
Add any other context or screenshots.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

11 of 14 (78.57%)  changed or added relevant lines in 7 files are covered.
7 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.06%) to 61.804%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/utils/deno.go
0
1
0.0%

internal/testing/apitest/project.go
4
6
66.67%

Files with Coverage Reduction
New Missed Lines
%

internal/gen/keys/keys.go
7
7.94%

Totals

Change from base Build<PHONE_NUMBER>:
-0.06%

Covered Lines:
4749

Relevant Lines:
7684

💛  - Coveralls


Churn with aws_iam_role.this

Describe the Bug
There is a permanent name change with aws_iam_role.this which is causing the resource to be recreated on every apply.
This is causing further issues with KMS permissions in the lambda function being revoked, including permissions to the default KMS key.
See https://github.com/serverless/examples/issues/279 for context regarding KMS key
Expected Behavior
IAM role should not be constantly recreated.
Steps to Reproduce
Apply module, apply again.
Screenshots
No response
Environment
No response
Additional Context
No response

It appears this is only a problem when using this module with...
module "lambda" {
  ...
  ...

  depends_on = [data.archive_file.lambda_zip]
}

Because the zip file gets refreshed on every deploy, then the data sources for region, partition etc are refreshed
causing the roles to think they must be re-created because they depend on apply-time stuff.
this is a tricky one to fix. I am going to implement a workaround in my infra now so I can continue moving forward. Idk if I will find time to implement a fix.


Support RTP extensions properly

It seems that we don't handle RTP extensions properly. If they are set (in SDP offer/answer) our depayloaders receive improper payloads. This happens both for OPUS and H264 depayloaders. Removing RTP extensions from SDP answer seems to resolve problem.
Example extension set that causes errors in OPUS (audio):
    a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level
    a=extmap:2 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
    a=extmap:3 http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01
    a=extmap:4 urn:ietf:params:rtp-hdrext:sdes:mid
    a=extmap:5 urn:ietf:params:rtp-hdrext:sdes:rtp-stream-id
    a=extmap:6 urn:ietf:params:rtp-hdrext:sdes:repaired-rtp-stream-id

Example extension set that causes errors in H264 (video):
    a=extmap:14 urn:ietf:params:rtp-hdrext:toffset
    a=extmap:2 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
    a=extmap:13 urn:3gpp:video-orientation
    a=extmap:3 http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01
    a=extmap:12 http://www.webrtc.org/experiments/rtp-hdrext/playout-delay
    a=extmap:11 http://www.webrtc.org/experiments/rtp-hdrext/video-content-type
    a=extmap:7 http://www.webrtc.org/experiments/rtp-hdrext/video-timing
    a=extmap:8 http://www.webrtc.org/experiments/rtp-hdrext/color-space
    a=extmap:4 urn:ietf:params:rtp-hdrext:sdes:mid
    a=extmap:5 urn:ietf:params:rtp-hdrext:sdes:rtp-stream-id
    a=extmap:6 urn:ietf:params:rtp-hdrext:sdes:repaired-rtp-stream-id

The task is to investigate where is the problem.

please share a sample packet that fails to be parsed

Sure, I will share example packets that should be parsed properly but on Monday morning if it's not a problem

So when appending the above extensions for video we can't depayload following packets:
12:51:53.310 [warn]  [:depayloader] An error occurred while parsing RTP packet.
Reason: malformed_data
Packet: %Membrane.Buffer{metadata: %{rtp: %{payload_type: 108, sequence_number: 30873, ssrc:<PHONE_NUMBER>, timestamp:<PHONE_NUMBER>}, timestamp: 0}, payload: <<160, 49, 0, 1, 64, 49, 0, 0, 0, 103, 66, 192, 31, 140, 141, 64, 80, 30, 144, 15, 8, 132, 106>>}

or
12:51:53.321 [warn]  [:depayloader] An error occurred while parsing RTP packet.
 Such extensions are not put into the extension header, but just into the payload. Thus, some extensions may have to be turned off if we don't support them, or they will lead to 'malformed data' or 'corrupted stream' anyway.


Embedded object constraints

This branch has already merged the 232-updates branch.
In addition, it includes 3 separate changes:

the schema translation Python uses pathlib instead of os.path,
exceptions in translation pieces propagate properly to the interface,
source schema are first parsed into a new object-type-keyed data structure to make JSON translation flow better.

Oops, fixed now.

@tanaya-mankad, is this PR now obsolete?

PR is closed; I'll make sure the branch has nothing left I want to merge and then delete it as well.


Fixed some memory leaks

Fixes some memory leaks:

In the Linux backend, the deleter of a std::unique_ptr didn't call delete;
The hdr_config type and its sensor were holding mutual shared pointers to each other, causing them to not be deleted;
In synthetic-stream.cpp, set on_set method is called on a ptr_option, which stores the function passed to that method. However, the lambda passed captures the shared pointer, giving another shared pointer loop.

@Rheel17 , thank you for the contribution.
Actually we've been doing a parallel investigation into some of the issues highlighted, so we'll check the proposed changes and update.

@Rheel17 , thank you for the contribution.
Actually we've been doing a parallel investigation into some of the issues highlighted, so we'll check the proposed changes and update.


"End" key works incorrectly in TextBox

Cursor should be moved to the end of current line but it moved to the next line.

I'm unable to reproduce this in ControlCatalog. Can you give any more details?

This issues is reproducing only with \r\n newlines. I fixed it and will make PR in soon.


pull request for e2e test at 11/12/2016 15:26:06

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


add: pranshuj73

Description
updated profile.json with my profile
Related Issues
[Include any related issues or pull requests that this PR addresses or is related to. Use GitHub's shorthand syntax to link to them, like #1234.]
Changes Proposed
added my profile to profile.json in src/data
Checklist

[x] I have read and followed the Contribution Guidelines.
[x] All new and existing tests passed.
[x] I have updated the documentation to reflect the changes I've made.
[x] My code follows the code style of this project.
[x] The title of my pull request is a short description of the requested changes.

Screenshots
Note to reviewers

@pranshuj73 Thank you so much for your contribution! Your efforts are greatly appreciated and will go a long way in improving our project. Please feel free to share it with others and help us grow even further!

Will definitely share it with others, thank you for merging!


drivers: fuel_gauge: various non-breaking fixes

This PR fixes a couple of issues that was seen when compiler with g++.

fix integer comparison issue
fix missing device struct pointer cast
add "missing" const from read-only arrays.

I do not believe either of these changes to be breaking API changes as they should have no impact on downstream drivers or applications. I may be wrong.

@aaronemassey I believe this is as ready for review now.
My initial statement that these are non-breaking changes was not entirely true as I had to add some missing initializations to a couple of fuel gauge test cases because of compiler warnings that apparently are only emitted when the props are const.

@teburd this LGTM.


Added Concurrently as a new script in main package.json

By adding concurrently as a new package and script. This allows users to run pnpm dev in the root and run both the playground and package at the same time. Removing the need to run 2 terminals.

Sure thing! Will get it done

Got them updated!


[quickfix] website generation

TestPlan:

cd website
node ./server/generate.js

@facebook-github-bot shipit

By analyzing the blame information on this pull request, we identified @sahrens and @caabernathy to be potential reviewers.

Thanks for importing. If you are an FB employee go to Phabricator to review.


early out if role already deployed

This change add a check to early out from
the reconcile loop if the openstack dataplane role
status is deployed and it is not marked for deletion.
role reconciliation once completed should only happen again
if the end user sets deployed to false.
This prevents looping of reconciling the NovaExternalCompute
CRs by preventing the role reconcilation form triggering
a reconciliation of all the NovaExternalComputes.
manually triggering deployment can be done as follows
oc delete -n openstack openstackAnsibleEE dataplane-deployment-validate-network-edpm-compute
oc patch openstackdataplanerole edpm-compute --subresource status --type merge  -p '{"status":{"conditions":[{"type":"validate-network service ready", "status": "Unknown", "lastTransitionTime": "2023-08-03T17:32:39Z" }]}}'
oc patch openstackdataplanerole edpm-compute --subresource status --type json -p='[{"op": "replace", "path": "/status/deployed", "value": false}]'
Closes: #327
(cherry picked from commit f8fb92be31982314526fefdd787abd5a1ba36b6a)
Signed-off-by: Sean Mooney<EMAIL_ADDRESS>

/retest

/retest-required

recheck

/test all


Docs: top-level refresh and restructure

Revisiting our CLI docs, with more of an end-user perspective and aiming for simpler/clearer documentation.
Main sections of work planned

[x] Manage OpenAPI files (split/join/bundle), useful for API producers
[x] Ensure good API governance (lint, decorate, preprocess), useful for API producers, maybe also for consumers, and wider compliance
[x] Build beautiful docs (build-docs, preview-docs), for API producers, but also consumers if no good docs are provided

We also need a better way to preview docs locally and check links, since I'm unsure about the formatting and very sure I'm breaking things :) Probably this is needed for us to be able to review this properly, but I'll keep working on content (hopefully the commit history helps explain what I'm thinking)
Not included this time (because this PR is already too big):

Config docs
Custom plugin docs
Decorators
Migration guides from previous CLI tools/versions

I'd also really like to make the bullets at the top of the index page into cards or something, if anyone can add that?

"Bullets --> Cards"

Let's do this as an update after this is merged.

In an attempt to get this PR mergeable (it's already HUGE), I've moved a couple of discussions to separate issues

#1060 for a better landing page layout with cards
#1061 to consider naming of assert things

@adamaltman along our naming discussion, I opened https://github.com/Redocly/redocly-cli/pull/1062 to propose using rule/i-made-a-rule as the configurable rules key in the config file. You may have opinions.


Logging to file and stdout

Is it possible to configure logging to write logs to stdout and file at the same time?

It doesn't have a built-in way to log to both files & stdout. (If you only need files and stderr, then the flag --alsologtostderr can make it, well, also log to stderr, when you use logging.get_absl_handler().use_absl_log_file() to make it log to files too).
If you need both files and stdout, you'll need to attach your own log handlers so it writes to stdout, likely with absl's own formatter
Let me know if this helps.

Closing due to inactivity. Feel free to re-open if you have more questions.


Error: Type 'DecoderCallback' not found.

I am getting below error while running flutter app please help not able to solve.
".pub-cache/hosted/pub.dev/photo_manager-2.8.1/lib/src/internal/image_provider.dart:"
my flutter version = 3.16.3
and how am i suppose to change version of photo_manger because it is internal package.
please help.

https://github.com/fluttercandies/flutter_photo_manager/issues/1021#issuecomment-1817299912


fetch doesn't work with proxies

const HttpProxyAgent = require('http-proxy-agent');
const puppeteer = require('puppeteer');
async function run () {
    const browser = await puppeteer.launch({headless: false, slowMo: 10});
    page = await browser.newPage();
    await page.setRequestInterception(true);
    var Agent = new HttpProxyAgent('http://user:pass@ip:port');

    await page.evaluate((Agent) => {
        fetch('https://api.ipify.org?format=json', {agent: Agent}).then(response => response.json()).then(data => console.log(data))
    }))

The result is my real IP, instead of the proxy's. And I don't think there's anything wrong with my code, so could it be that fetch just refuses to use proxies?

Hello can someone reply?

Does't it work with socks5 proxy ?

when fetching inside page.evaluate() it calls browsers fetch api which does not support proxies and there is on agent option,
you have to use proxy at puppeteer level, for example https://www.npmjs.com/package/puppeteer-page-proxy, which will proxify all request including page.evaluate's requests


Custom Computations

As defined in https://github.com/capeprivacy/coordinator/issues/476
Builds on https://github.com/capeprivacy/pycape/pull/130

@bendecoste ok to close this?


Update analytics providers

Added Google in the list of providers for analytics
Replace Adobe Analytics for Google Universal as the analytic provider

@quidampepin Here are the links for review:

https://deploy-preview-27--blog-tbs.netlify.app/
https://deploy-preview-27--blogue-sct.netlify.app/


why two empty projects exist?

Could you turn to https://hongyi-huang.github.io/projects/ to figure out why there are two placeholder-like empty projects? How could I move them away?

Projects prefixed with the GitHub logo are considered remote projects (fetched from your GitHub repositories), to configure (add/delete) them, modify the remote-projects filed in pages/projects.html's front matter.


2.14.1: Compilation issue on NetBSD

When compiling on NetBSD (8.99.27/amd64) the build stops because sockaddr_storage is not defined.
The problem is that in library/net_sockets.c, the symbol _POSIX_C_SOURCE is defined to 200112L. In contrast to Linux, NetBSD removes symbols from the namespace when particular namespaces are requested.
(I think this might also be a problem on Solaris because it also likes to removes symbols.)
Workaround:
--- library/net_sockets.c.orig  2018-12-02 13:20:52.000000000 +0000
+++ library/net_sockets.c
@@ -22,7 +22,7 @@
 /* Enable definition of getaddrinfo() even when compiling with -std=c99. Must
  * be set before config.h, which pulls in glibc's features.h indirectly.
  * Harmless on other platforms. */
-#define _POSIX_C_SOURCE 200112L
+//#define _POSIX_C_SOURCE 200112L

 #if !defined(MBEDTLS_CONFIG_FILE)
 #include "mbedtls/config.h"

Please note the comment is incorrect ;)

struct sockaddr_storage is in SUSv3 with no note that it's an extension to POSIX.1-2001, so #define _POSIX_C_SOURCE 200112L should bring it in. What does it take to get struct sockaddr_storage on NetBSD?

We don't have NetBSD on our CI. A patch would be welcome, but of course it mustn't break other platforms. Commenting out #define _POSIX_C_SOURCE 200112L breaks glibc according to this comment so that's out. Note that Mbed TLS runs on many platforms that only implement a subset of POSIX, so sometimes strict conformance to POSIX isn't enough.

AFAIK, both Solaris and NetBSD hide symbols when particular requirements are defined using e.g. _POSIX_C_SOURCE.
The simple solutions IMO are:
1.
#ifndef __NetBSD__
#define _POSIX_C_SOURCE 200112L
#endif

or
2. (in my eyes preferred) just define the symbol on the platform(s) that need it. I don't know the defines for that, sorry.


Support HTTP proxies

My corporate network requires HTTP/S connections to go through a squid proxy.
libcloud should respect the $https_proxy environment variable so that this can work seamlessly.

Closing. This has been resolved.


Write broker-style API to archiver that returns documents

We recently thought of this as another light-weight package, but I think it could probably live happily in dataportal.
Suggested API:
dataportal.archiver.get_period(start_time, end_time, pvs)
dataportal.archiver.get_events(header, pvs)
dataportal.archiver.get_table(header, pvs)

where pvs is a list of strings. We could add get_table, too, but I think we can wait. We may not need it or want users to use it because I suspect that in almost every case their next step will be to align that data. So the workflow will probably be:
dm = DataMuxer.from_events(broker.get_events(header))
dm.append_events(archiver.get_events(header, pvs))
dm.bin_on('whatever')

Here is a snippet of code I wrote while helping users at CSX. It might be a useful starting point.
import uuid
from metadatastore.doc import Document

def new_uid():
    return str(uuid.uuid4())

dummy_desc = Document('descriptor', uid='dummy', data_keys={'ring_current': {'source': 'dummy'}})
ring_data_as_events = [Document('event', time=t, timestamps={'ring_current': t}, data={'ring_current': d},
                                uid=new_uid(), descriptor=dummy_desc)
                       for d, t in zip(ring_data['ring_current'], unix_times)]

Done in https://github.com/NSLS-II/databroker/pull/51


Fullscreen mode?

Either I am missing something or this project needs a full screen mode, i.e. no window title bar and (if there is one on the computer screen in question) no task bar or similar. Very useful on laptops with smaller screens, for teaching / in presentations and on multi-monitor setups.

I'm not sure that it "needs" full screen but it can be added to backlog

how about "Zen Mode"?

how about "Zen Mode"?

Please make separate issue

Currently not possible since druid doesn't implement it

Are there keyboard shortcuts that correspond to all the panel toggles? Might be able to mimic the behavior by remapping the keybindings for file system and terminal to the same combo, then toggle between two states, file system and integrated terminal both open, and both closed. Comes very close to "zen mode" in terms of screen space.


res.sendStatus drop on an error at browser side

Using angular httpClient when i do a sendStatus(200) i recibe that error on frontend. it's cause angular or something wrong on express?

with status(200).send() it's everything okay at frontend

that don't drop on any error

From your client-side error, it looks like the client is expecting a JSON response. The res.sendStatus method sends a text response, which results in a JSON parse error on the client. You likely have three options:
(1) Change the client is not attempt to parse JSON if you do not intend to send JSON responses.
(2) Send an empty body, which apparently does not trigger the error. This is what you're doing with res.status(200).send()
(3) Send a JSON body with something, perhaps even an empty object, if the client really wants JSON responses. An example would be res.status(200).json({})
I hope this helps!


Document the abuse interstitial

what is it
when it shows up
how to get around it
common questions

completed in https://ngrok.com/docs/guides/limits/#why-is-there-an-interstitial-in-front-of-my-html-content


The machine cannot start when the GPU becomes available after retrying with no GPU

When choosing a Free GPU, if it is available, simply click "start" and the machine will start as expected.
However, if there is no GPU available initially and you click "start," there may be an error. This error is actually a good sign because it means that the free GPU has become available. I can manually start the machine after receiving this error, as it indicates that the machine is now ready for use.

hi, which error did you encounter?


mlp.dense_4h_to_h.bias is useless with GPT-J residual

"mlp.dense_4h_to_h.bias" is useless when gpt_j_residual = true because "attention.dense.bias" plays the same role. So I suggest to remove either "mlp.dense_4h_to_h.bias" or "attention.dense.bias" when gpt_j_residual = true.

Yes, we are aware. However implementing this has seemed like it’s more work than it’s worth and could negatively impact code readability and mantainability.


[2.0] Limitation Filter not working

I can not get the limitation filter working I even tried putting the example given in my config file (knowing it should fail) and it still logs the user in. Also even though I have bind model to user set as false it still inserts a user into my users table when authenticating.
This is how I have the limitation filter w/ the example (it should be failing since the group is all wrong):
'limitation_filter' => '(memberof:1.2.840.1135<IP_ADDRESS>1:=CN=MyGroup,DC=example,DC=com)',
AuthController:
$credentials = $request->only('username', 'password');
if (Auth::attempt($credentials)) {
       return redirect()->intended('home');
}

Is your configuration being cached?

Also even though I have bind model to user set as false it still inserts a user into my users table when authenticating.

Thats not what this option controls, that's actually the adldap auth driver, it will always create a new user record for LDAP users logging in who do not have an account.

I cleared my cache and it is still doing this. If I type the incorrect password it kicks me back to the login so I know that is working. Typing the correct credentials takes me past the login screen but with that limitation filter it should be kicking me out right? The CN and DC doesn't even match my base DN.

Yup you're right, the newAdldapUserQuery() method is being overridden by a local class method. Can't believe I missed this. Thanks!
Fixing now.

Fixed: https://github.com/Adldap2/Adldap2-Laravel/commit/80b6f9c1ea4ef6f6d0f482a4863519c24597e1f7
Please update to v2.0.4, thanks for bringing this up!


Clean up Sift tests

For the 0.3.0 release we find that the unittests for sift should be cleaned up

Using -v request user input for some tests
there is global const USE_LENA which allows to use or not content from home
maybe test_transform.py is the only one

valls@linkdick:~/workspace/silx.git$ grep -r paleo
silx/image/sift/test/test_transform.py:            image = scipy.misc.imread("/home/paleo/Titanium/test/frame0.png")
silx/image/sift/test/test_transform.py:            image2 = scipy.misc.imread("/home/paleo/Titanium/test/frame1.png")
valls@linkdick:~/workspace/silx.git$ grep -r USE_LENA
silx/image/sift/test/test_transform.py:USE_LENA = True
silx/image/sift/test/test_transform.py:        if (USE_LENA):

On Wed, 12 Oct 2016 08:10:39 -0700
Valentin Valls<EMAIL_ADDRESS>wrote:

For the 0.3.0 release we find that the unittests for sift should be cleaned up

Using -v request user input for some tests
there is global const USE_LENA which allows to use or not content from home
maybe test_transform.py is the only one

valls@linkdick:~/workspace/silx.git$ grep -r paleo
silx/image/sift/test/test_transform.py:            image = scipy.misc.imread("/home/paleo/Titanium/test/frame0.png")
silx/image/sift/test/test_transform.py:            image2 = scipy.misc.imread("/home/paleo/Titanium/test/frame1.png")
valls@linkdick:~/workspace/silx.git$ grep -r USE_LENA
silx/image/sift/test/test_transform.py:USE_LENA = True
silx/image/sift/test/test_transform.py:        if (USE_LENA):

I agree cleaning-up is needed...
Jérôme Kieffer
tel +33 476 882 445

Looks to be fixed


Issue links are not underlined when posted

Summary
Links posted from this workflow aren't underlined when posted to channel

Not sure if I could've posted this via workflow, but here's the issue this was noticed in:


Fix link to Security & Compliance Center PowerShell

@diecknet PR merged. Thanks for making this fix!


Configurable option to truncate activity tracking logs after n days

We have some apps that track a fair amount of very granular activity, but it's not clear that there is much value in saving this data indefinitely at the cost of having the xh_track table rowcount increase in an unbounded way.
We should add a configurable option to have the server delete activity data older than a certain number of days. If enabled, this routine could be run once a day via a timer in TrackService.
Default value is up for discussion - safest is probably to have it disabled by default (although one could argue that having some limit on track entry storage is "safer" in another way). We could check with our clients before enabling, but could aim to make setting to something like 365 days a best practice.

We would also want to do some testing to ensure that an app that had a very large track table ran its deletes in some managed fashion after release.  E.g. assuming the delete routine runs daily or every n hours on a timer, we could set a limit to how many logs could be deleted at once.  It might then take a while for an app to "prune back" to its configured limit, but we would avoid a potential database/replication storm of some kind triggered by deleting 2m rows in one shot...


Threshold setting or control for Detection score in Object detection[DNN and MMOD].

Hello, I have trained an object detector based on DNN MMOD loss layer in DLIB to detect "A" in an image. For high res images, I can detect "A" in an image. But in case of low resolution images, I am not able to detect. In order to understand why, I tried to visualise the detector output scores and I get the below result.

I can see that I get good score for some pyramid scale(bottom left in the pyramid), but the output of the detector does not return any rectangles. I am guessing, there is a threshold that is set and the score is not above the threshold. So my question is, is my guess right, if yes, do I need to look into loss.h file or any other file ? (please let me know) and if not, how do I go about getting the mmod_rect as result on "A".

You could certainly change the detection threshold.  You will probably get
false alarms as well though.  But in any case, you can easily adjust the
threshold by calling net.process().  See the documentation
http://dlib.net/dlib/dnn/core_abstract.h.html#add_loss_layer

Thank you very much @davisking for the help. This is what I was looking for.


Update Romanian translation for 1.7.0

Updated Romanian strings for 1.7.0 release
Check if this PR fulfills these requirements:

[x] My changes respect the Kodi add-on development rules
[x] I have read the CONTRIBUTING document.
[x] I made sure there wasn't another one Pull Requests opened for the same update/change
[x] I have successfully tested my changes locally

Types of changes

[ ] New feature (non-breaking change which adds functionality)
[ ] Feature change (non-breaking change which change behaviour of an existing functionality)
[x] Improvement (non-breaking change which improve functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

In case of Feature change / Breaking change:
Describe the current behavior

Describe the new behavior

Screenshots (if appropriate):

The Addon Disclaimer text was updated.


Steps out of date?

The set of steps on this page don't appear to be accurate anymore. In Step 2 there isn't any "Increase protection from advanced threats" on the Setup page.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 43be63d8-b28e-1a2c-e2d5-7e0e55919553
Version Independent ID: 56399ab7-cd7f-bd65-afe0-a8724ae28b60
Content: Manage Safe Links
Content Source: microsoft-365/business-video/safe-links.md
Service: o365-administration
GitHub Login: @KwekuA
Microsoft Alias: kwekua

@Beschorr Thank you for your feedback. We have made changes to the steps via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/5403
Meanwhile, Steps 1 and 2 still remain the same. If you have the Microsoft Defender ATP license, you should be able to see the options.
Thanks
Sri

Thanks Sri. I was looking at an M365 Business Premium admin center when it appeared that the steps were different. Perhaps we need some note for customers using that SKU that their steps may appear slightly different?
Ben Schorr (he/him)
Senior Content Designer | Experiences + Devices | Microsoft 365 Cybersecurity
https://support.microsoft.com/security
[Microsoft Logo]

From: Sriraman M S @.>
Sent: 6/23/2021 02:29
To: MicrosoftDocs/microsoft-365-docs @.>
Cc: Ben Schorr @.>; Mention @.>
Subject: Re: [MicrosoftDocs/microsoft-365-docs] Steps out of date? (#5356)
@Beschorrhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FBeschorr&data=04|01|beschorr%40microsoft.com|80eb42c705c8440c048c08d93629746f|72f988bf86f141af91ab2d7cd011db47|0|0|637600373961692462|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=bgbNB4ri8HAow6rhHKzRlAIi7lXvLFnWUofNp87hwb0%3D&reserved=0 Thank you for your feedback. We have made changes to the steps via PR##5403https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-365-docs%2Fpull%2F5403&data=04|01|beschorr%40microsoft.com|80eb42c705c8440c048c08d93629746f|72f988bf86f141af91ab2d7cd011db47|0|0|637600373961692462|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=PNhj5ZKCpANbSR3Wc6luVvKSxhOx3VBdCjT9CDA%2B9p8%3D&reserved=0
Meanwhile, Steps 1 and 2 still remain the same. If you have the Microsoft Defender ATP license, you should be able to see the options.
Thanks
Sri
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-365-docs%2Fissues%2F5356%23issuecomment-866682568&data=04|01|beschorr%40microsoft.com|80eb42c705c8440c048c08d93629746f|72f988bf86f141af91ab2d7cd011db47|0|0|637600373961702453|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=zzUWhGlD182gUr4VzpfWU0FezGFu%2FqXz5qkaR6Kbt4k%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKINHFVKAYZP5HVDF7WKW2TTUGSRBANCNFSM464AADOA&data=04|01|beschorr%40microsoft.com|80eb42c705c8440c048c08d93629746f|72f988bf86f141af91ab2d7cd011db47|0|0|637600373961712450|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=FCyAhO4UxgwYuGoBHHjQWDdQJ%2Ft04300F2lAhnO%2F10I%3D&reserved=0.

@msbemba Thank you very much for the contribution and updating the documentation with PR. @Beschorr Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Double-printing text in django runserver_plus

On a Django project using django_extensions, using python manage.py runserver_plus with the latest werkzeug (v0.15.1) results in double-printing all logging statements. This is not an issue in v0.14.1; the issue arose in commit 4cf77d2. The reason for this issue is that runserver_plus modifies the werkzeug logger by setting its log level and adding a handler. Older versions of werkzeug only added a log handler if there was no log level and no handler on the root logger. Since that commit, werkzeug adds a log handler if there is no handler on the root logger, regardless of log level. This results in there being two handlers, and thus all logging statements get printed twice. If werkzeug checks for a handler on the werkzeug logger instead of the root logger, the second handler won't get added. Is there a reason to check the root logger for handlers, seeing as werkzeug doesn't use the root logger?

See #1407 cc @ramnes

Needs the same level check as pallets/flask#2436.


Use debian base image instead of alpine

Ensuring ctrd-fuse-overlayfs is present
# cat README.md
# nerdctl (full distribution)
- nerdctl: v1.1.0-320-g4349a92
- containerd: v1.6.16
- runc: v1.1.4
- CNI plugins: v1.2.0
- BuildKit: v0.11.2
- Stargz Snapshotter: v0.14.1
- imgcrypt: v1.1.7
- RootlessKit: v1.1.0
- slirp4netns: v1.2.0
- bypass4netns: v0.3.0
- fuse-overlayfs: v1.10
- containerd-fuse-overlayfs: v1.0.5

Signed-off-by: Manu Gupta<EMAIL_ADDRESS>

The benefits are not significant in terms of latency.

Ensuring ctrd-fuse-overlayfs is present

Sorry what do you mean, and how it is relevant to the distro?

I feel glibc is less stable for static linking, and may produce statically linked applications requires at runtime the shared libraries from the glibc version used for linking issues for some programs.
So I'd prefer to adhere to musl (Alpine) unless there is a strong reason

Makes sense! I was trying to optimize CI times. I will
Close it.


text of larger sizes is not correctly centered vertically

some work is already in flight on the textdebug branch

some good info here
https://stackoverflow.com/questions/68167081/vertically-centered-text-in-p5-js-is-not-aligned-properly


Change docs to say travis-ci.org

travis.org is a church website :smile:

Haha, thanks for catching that @malaretv!
I know it's a tiny change, but can you send over a contributor license agreement (CLA) so we can merge this?  You can find instructions here: CONTRIBUTING.md

@hpinkos sent!

Thanks @malaretv, we received your CLA.  Can you also please add yourself to https://github.com/AnalyticalGraphicsInc/cesium/blob/master/CONTRIBUTORS.md in this pull request?

@pjcozzi done.

Thanks again @malaretv!


Consider adding plugin for ApplicationInsights logs

See https://github.com/Azure/azure-sdk-for-net/blob/Azure.Monitor.Query_1.3.1/sdk/monitor/Azure.Monitor.Query/README.md

basic support now added


Adds OPDS authentication content type header matching

Adds check for Content-Type header per the Authentication for OPDS draft spec, 2.2 Content Conformance.

Excellent point!
Thorium currently implements support for OPDS2 authentication (via OAuth access tokens) based on HTTP 401 responses ("Unauthorized") and the application/opds+json HTTP header content-type ... but we definitely need to let application/opds-authentication+json through as well.
Thanks :)


Can you update rootston's handle_surface_commit to use this?


Actually use gdc-9 for testing

Because `d: dmd` is applied after `DC=gdc` is exported,
it overrode DC and we ended up testing with DMD.

Since gdc-9 does not have a critical bug to Phobos that I made, this is blocked on a new release of gdc-9. Iain, the maintainer, might include it in 9.2.

That will not happen for a while, we need at least GDC10, which is not released yet, and if we want to use all the ~nice new features~ bug fixes we made I don't see us using GDC for a while.


Tread PlsrDAC ringing

Some FE-I4 (especially after irradiation) show a ringing PlsrDAC:

If the injection loop is too quick the injected charge can change leading to measured higher noise and a charge that depends on the injection speed. We should add an additional injection delay with std. value = 0 to all scans using the PlsrDAC to be able to make the injecion speed slower.

In the picture there is no ringing before the pulse. Can you explain?

OK, I try to explain: The standard delay is around 80us and the next pulse would be still inside the dangerous region (10us/dev). So this plot either show the first pulse or injections with already extended delay.

Long delay. I misscalculated. We can have 400 us injection delay with our current FPGA cmd sequenzer implementation (16000 * 25 ns). That is sufficient. So we just have to add a parameter in software.

Just to make it clear how the analog scan (and thus all other scans) with std. settings (3rd mask) looks like:

The ringing can be fixed by increasing the OP amp bias of the:
IV converter op amp

responsible for the slow return to baseline.
The configuration for a not ringing PlsrDAC is: PlsrVgOpAmp = 150
Disclamer: I think that is this is this OP amps bias. There is also another gain 2 OP amp to increase the rail to rail amplitude. It is not mentioned anywhere, neither in schematics nor the manual. So that is an educated guess.

Since that does not have to be fixed in software I close this issue.


The config should be under provider property

In the Serverless framework, the provider specific configuration is usually set under the provider property. It would be great if that practice is followed in the serverless-cloudflare-workers plugin as well.
https://github.com/cloudflare/serverless-cloudflare-workers/blob/44a3addc73b73932263502b17aac0dcd0c927c37/provider/cloudflareProvider.js#L32

Good call. Will see about updating this.

I've opened a PR that fixes the behavior in a backwards compatible way. Please let me know after a merge and new release of the package, so that, I can update templates in the framework.

Thanks. Please keep @rita3ko in the loop regarding templates and docs changes! We'll keep this updated on our end as well.


To understand: Maintenability

I needed some new functionalities of my local version of LibWiser, so to make it shorter I thought it could be possible
just to substitute my files (Foundation.py etc) into the folder of miniconda.
This was not possible:
apprantelry, this prevented Oasys to recognize the widged, and the widget were not loaded (not only in the ow space, but also in the menu).
Probably this is a "feature", not a bug.
But as it is unexpected (to me, maybe not for you), I would like to know a little bit more on that.
Any comments?

In any case, for better debugging OASYS-WISER, it would be easier if I could use the last version of LibWiser.
Can we find a pipeline for that?

This can be done by running
python3 setup.py sdist develop
prior to running Oasys from the correct venv.


[NO NEED MERGE]: wifi setup service

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jianlong.gaojianlo seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


What happens if the cache memory gets full and we try to set new values?

Hi. I am having a doubt. What happens when cache memory gets full and we try to set new values in it?
Actually I am using this library in a project. But somehow I suspect there is some issue in setting data into the cache. Somehow empty value gets set in the cache. Can this be due to memory issues?
Please help.

It might depend on your machine memory limit. If you reach to the memory  boundry, the application crashed.

Greetings. Great utility. Is would be great if we could limit the size of the cache instead or in addition to the expiration time.


Update suite.yml for v1.11.1+suite.1

What does this PR do?

Preps for v1.11.1+suite.1 release
Fixes test failure that came from a change to real release notes

What ticket does this PR close?
Resolves #194
Release checklist: https://github.com/cyberark/conjur-oss-suite-release/wiki/v1.11.1-suite.1
Draft release notes: https://gist.github.com/izgeri/0a60f26246decfdcac8fe1c5e3856abf
Early draft of docs output: ConjurSuite.htm.zip - ~would like to resolve #199 before creating actual docs HTML~ - there is one manual change required to the docs link in the upgrade instructions section (so it won't pop up in a new window).
Release PRs
If you are preparing for a release, are the following items complete?

[x] The PR title / description clearly state the suite release version.
[ ] The Jenkins dashboard shows no ongoing
build failures for any included components.
[x] The PR includes a link to a markdown release notes draft - this can be
generated by running:summon -p keyring.py   --yaml 'GITHUB_TOKEN: !var github/api_token' \
  ./parse-changelogs \
  -v {suite-version} \
  -t release
  -o RELEASE_NOTES.md

[ ] The PR includes PM-approved "What's new" text.

@alexkalish - re: your points above.
Conjur

The image isn't public yet, though I hope it will be public by the time we publish this release. It shouldn't be added to the page you linked (which is for Docker Compose) - when it's ready to be used (i.e. when cyberark/conjur-oss-helm-chart#113 is complete) it will be referenced from the helm chart docs.
I've updated the release docs ticket to ask that the GCP cloud function authentication docs be published at the same time as the suite release notes are published (the docs are already written, they are just in "do not publish" mode until the software is released).

K8s authn

There is a docs ticket to add a troubleshooting related to the changes you're referencing - I've also added it to the release docs ticket so that it will be published with these release notes.

Draft "What's New" Content
DRAFT - ready for comments

What's New
This Suite release aligns with Conjur Server version 1.11.1. It includes quality and troubleshooting improvements to the Conjur SDK, as well as enhancements in the Conjur Kubernetes and Google Cloud Platform authenticators. Notable updates are highlighted below.
For a reminder of the Conjur Open Source Suite Release structure please refer to the documentation introduction.
Conjur Core
Deployment and Upgrades
The Helm Chart is updated to support strings for image tag values. Previously, only numeric values were allowed, but this could lead to semantic versions provided in the form {major}.{minor}, where {minor} is a multiple of 10, being interpreted as decimal values and truncating the final 0. With this change, the helm chart can now accept non-numeric image tag values such as latest.
Conjur API
Conjur now raises an Unauthorized error when a user attempts to rotate the API key of a nonexistent role. Previously, the operation would result in a successful rotation of the user's API key, with no indication that the target of the operation had changed.
NEW Google Cloud Platform (GCP)f Support for Google Cloud Functions
Google Cloud Function (GCF) applications can now authenticate to Conjur using the GCP authenticator. For more information on how to get started using this new feature, reference the GCP authenticator documentation.
Kubernetes Authenticator
When the Conjur Kubernetes authenticator encounters an error while injecting the authentication certificate into the client container, it now writes the error message into a file in the client container at the path /tmp/conjur_set_file_content.log. Together with the changes in the Kubernetes authenticator client available in this release, this allows for easier troubleshooting of certificate injection issues.
Conjur Integrations
Kubernetes Authentication client
As noted above, with this release the Conjur Kubernetes authenticator has been updated to write error messages due to problems in the certificate injection process into a file in the container at the path /tmp/conjur_set_file_content.log. With this release, the authenticator client has also been updated so that if it cannot read the certificate file within 10 seconds, it will attempt to log the contents of the error log file to the authenticator client container logs. This makes it possible to observe all Kubernetes authentication steps when experiencing issues during the certificate injection process by reviewing the client container logs and the Conjur server logs.
In addition, the authenticator container logs have been updated to make the default log level less verbose and make errors more obvious. Detailed logs are enabled by setting the DEBUG=true environment variable on the authenticator container.
Previously, log entries included a timestamp with precision in seconds. For example: “2020/09/15 08:50:21”. Now, log entries have a timestamp with microsecond precision. For example: “2020/09/15 08:50:21.682962”. The additional precision enhances observability of multiple events that occur within a single second.
Further, the authenticator client log prefixes are updated to remove the log level suffix from the log message codes (e.g. CAKC001E -> CAKC001). Existing monitors or alerts on these code need to be updated.
Secrets Provider for Kubernetes
Secrets Provider for Kubernetes has been updated to use the Kubernetes authenticator client v0.19.0. With this change, users benefit from the changes made to the Kubernetes authenticator client in this release for improved performance and troubleshooting capabilities during the client certificate injection process.
Secrets Delivery
Secretless Broker
Secretless Broker's Conjur secret provider has been updated to use the Kubernetes authenticator client v0.19.0 so that when using Secretless with the Conjur Kubernetes authenticator, users may also benefit from improved performance and troubleshooting capabilities during the client certificate injection process.
Deprecations
Support for OpenShift versions 3.9 and 3.10 will be officially deprecated with the next suite release.  These versions have already been declared end of life by Red Hat and were deprecated by CyberArk Dynamic Access Provider in version 11.7. Users are encouraged to upgrade their OpenShift clusters to at least version 3.11, which is supported by both Red Hat and the Conjur OSS Suite.

@izgeri Thanks for taking the lead here !
some comments / questions
I would consider the following as bugs rather than news.
In the CyberArk release notes (RN) we focus What's New (WN) on significant value. Bugs are listed in another  section. In OSS case the bugs would hopefully be covered by respective changelogs. Let's assess that, and if the are articulated as clearly as you have here then these would be bugs rather than news:

helm chart with strings
Conjur API Unauthorized error (BTW which bug does this refer to in the RN ? Is this not a security related issue?

*** WIP  saving for draft   I'll erase this linme when done ***

@boazmichaely I updated the draft based on your feedback, and reviewed the 12.0 RRN to make sure the language we've used here is consistent. There are some slight tweaks I've made to remove some ambiguity in the text given the way we have the information organized here.
Note that for the API / helm chart changes I removed, there are changelog entries that cover the removed text. In particular for the helm chart, the change log says:

Image tag values must now include surrouding quotes when they are set in a values.yaml file. Arbitrary tag strings are allowed now (e.g. "latest" is allowable).

and for the API change, the change log says:

Conjur now raises an Unauthorized error when a user attempts to rotate the API key of a nonexistent role. Previously, the operation would result in a successful rotation of the existing user's API key, with no indication that the target of the operation had changed.

@izgeri (CC @alexkalish, others ) let's separate getting 1.11.1 out and learning from our mistakes.
I'll start with the latter.
1. going forward

We have suffered from lack of communication about the source of truth for existing release notes as that SOT moves up over time from the AAM Rolling Release notes (RRN) through the  PAS release notes in WORD, to the final version in Flare.  That SOT includes both What's New (WN) and specific bug description
How do we minimize the confusion ?

Bugs:  When we review bug fix text, can the modified text be updated back into  the changelog?
WN: Where should we store the SOT and keep track of common OSS/DAP features to know what was published when ?

2. this release

Feels like the description for the Kubernetes Authentication client does not belong here. It should be captured in docs and we should make a high level statement here with reference to the doc link.
A high level could be:
The Conjur Kubernetes Authentication now better handles delays in internal communication between the  Kubernetes Authentication Client and Conjur, and the logs now provides a better view of that communication. In addition several enhancements were made to the log.See CHANGELOG1 , CHANGELOG2  for specific changes to the log and to DOC  LINK for detailed documentation.

@izgeri  WDYT? Can we move those descriptions back into the respective changelogs ?


Question: Adding a field to generated root type.

First thanks for the library!  I'm really enjoying my first resolver-first graphql experience and I think it has a lot to do with the composibility nexus allows.
I'd like to supplement nexus' internal typegen for root type in a field resolver.
I'm working with TypeORM + Nexus where the true ID of types are masked in graphql.
Simplified Example:
export const PostType = objectType({
  name: "Post",
  definition(t) {
    t.id("uuid");
    t.string("body");
  },
});

export const postQuery = queryType({
  definition(t) {
    t.field("post", {
      type: PostType,
      args: { uuid: idArg({ required: true }) },
      resolve: async (_, { uuid }, { loaders }) => {
        return getRepository(Post).findOne({where: { uuid }});
      },
    });
  },
});

@Entity()
export default class Post {
  @PrimaryGeneratedColumn()
  id: number;

  @Column({ type: "text", default: "someIDGenFunction()" })
  uuid: string;

  @Column({ type: "text" })
  body: string;
}

When I query post I get a record that looks like { id, uuid, body }.  Note the id field that is here, that is not on the PostType.  This is the hidden internal id we don't want to expose to the graph.
This is fine until I need to consume the id in a field resolver (for us, implementing data-loader).
Imagine using data loader to get an imaginary field tags: [Tag]!:
export const PostType = objectType({
  name: "Post",
  definition(t) {
    t.id("uuid");
    t.string("body");
    t.field("tags", {
      resolve: (root, _, { loaders }) => loaders.tagsByPostId.load(root.id);
    });
  },
});

This throws a type error because nexus does not think they type of root has a field id, even though it is there.
Is there a way I can tell nexus that certain types in my schema have these hidden fields that can only be accessed server side like the data-loader example above?
I suspect typegenAutoConfig might be the way to do this, but I could not determine how to do it from the examples (and I don't want to hand-write type definitions that TypeORM gives me for free).
Thank you!

So here's my way to bandage over the issue,  but it would still be ideal if I could tap into the typeGen to add this id field to all the types automatically rather than writing these types myself (but this is way better than what I was about to do!).
import { NexusGenRootTypes } from "../../generated/schemaTypes";
type PostRoot = NexusGenRootTypes["Post"] & { id?: number };

export const PostType = objectType({
  name: "Post",
  definition(t) {
    t.id("uuid");
    t.string("body");
    t.field("tags", {
      resolve: (root: PostRoot, _, { loaders }) => loaders.tagsByPostId.load(root.id);
    });
  },
});

Hi @pckilgore, you're right, you have to use typegenAutoConfig to add sources for your backing root types.
There is a discussion on this at issue #277

See also https://github.com/prisma-labs/nexus/issues/36#issuecomment-463649216 and https://github.com/prisma-labs/nexus/issues/139#issuecomment-494048131
Better docs are on the todo list.

@lvauvillier @tgriesser Thanks, I'll take a look.
If I have questions, is there a preferred pathway to ask questions over github issues?

For anyone that finds this later, the pattern that gets you there is:
import * as types from "types/";

export const schema = makeSchema({
  types,
  outputs: { /* ...  * /},
  typegenAutoConfig: {
    sources: [
      {
        alias: "PostRootType",
        source: path.join(__dirname, "entities", "Post.ts"
      }
    ]
  }
});

And where, and this tripped me up the Post typeORM entity was a named export from the file and not a default export.
This is really sweet, thanks @tgriesser  and team.


withGraphFetched Fails silently when snake case naming is used injunction with knexSnakeCaseMappers

withGraphFetched will return no results when knexSnakeCaseMappers is used and relation mapping of join table is specified in snake case format. Here's example:
Model:
export class Product {
  static tableName = "products";

  static relationMappings = {
    variants: {
      relation: Model.HasManyRelation,
      modelClass: Variant,
      join: { from: "products.id", to: "variants.product_id" },
    },
  };
}

export class Variant {
  static tableName = "variants";

  static relationMappings = {
    product: {
      relation: Model.BelongsToOneRelation,
      modelClass: Product,
      join: { from: "variants.product_id", to: "products.id" },
    },
  };
}

Query:
const variants = await Variant.query()
    .whereIn("variants.id", [138, 142])
    .withGraphFetched("product")

Actual Result:
  Variant {
    id: '138',
    productId: '40',
    product: null
  }

Expected Result:
  Variant {
    id: '138',
    productId: '40',
    product: Product {
      id: '40',
    }
  }

If I change join condition to Camelcase i.e. join: { from: "variants.productId", to: "products.id" } , it works. withGraphJoined works just fine it.
Objection.JS file
export const knex = Knex({
  client: "postgresql",
  connection: {
    database: config.database.database,
    user: config.database.username,
    password: config.database.password,
  },
  ...knexSnakeCaseMappers(),
});

// Give the knex instance to objection.
Model.knex(knex);

https://vincit.github.io/objection.js/guide/contributing.html#issues

Yes, that is true and we'll documented.


Error: watch ENOSPC

Tying to start a simple nodejs program with forever (runs when called from node) like this:
NODE_ENV=production forever --minUptime=1000 --spinSleepTime=1000 -l /u/logs/scad3_forever.log -o /u/logs/scad3_out.log -e /u/logs/scad3_err.log scad3/server/scad3.json

Get the error message:
events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: watch ENOSPC
    at errnoException (fs.js:1028:11)
    at FSWatcher.start (fs.js:1060:11)
    at Object.fs.watch (fs.js:1085:11)
    at createFsWatchInstance (/usr/lib/node_modules/forever/node_modules/forever-monitor/node_modules/chokidar/lib/nodefs-handler.js:37:15)
    at setFsWatchListener (/usr/lib/node_modules/forever/node_modules/forever-monitor/node_modules/chokidar/lib/nodefs-handler.js:80:15)
    at EventEmitter.NodeFsHandler._watchWithNodeFs (/usr/lib/node_modules/forever/node_modules/forever-monitor/node_modules/chokidar/lib/nodefs-handler.js:228:14)
    at EventEmitter.NodeFsHandler._handleFile (/usr/lib/node_modules/forever/node_modules/forever-monitor/node_modules/chokidar/lib/nodefs-handler.js:255:21)
    at EventEmitter.<anonymous> (/usr/lib/node_modules/forever/node_modules/forever-monitor/node_modules/chokidar/lib/nodefs-handler.js:468:21)
    at Object.oncomplete (fs.js:107:15)

/dev/sda5       8.2G  2.3G  5.5G  30% /

5GB not enough? How much do I need to use forever-monitor? And why does it need so much disk space???
Thank you very much in advance and kind regards,
Anton

Seems to have nothing to do with the free space, but with the number of files being watched.
Solution (for Debian, Ubuntu, ..:):
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Source:
http://stackoverflow.com/questions/16748737/grunt-watch-error-waiting-fatal-error-watch-enospc
If anybody is searching for that, seems a common problem. Maybe it should be put into the readme.


[FEATURES]add master and fuse resource option for jindoruntime

What feature you'd like to add:
add master and fuse resource option for jindoruntime
Why is this feature needed:

closed by #1046


A POC that replaces all BigInt to JSBI.BigInt

Summary
This is a proof of concept that replaces all reference of BigInt to JSBI
See commit https://github.com/jessealama/decimal128/commit/39760558d33a0aa3274e58c1c187517293a481c1
Technical note:
rollup config output interop is set to default to ensure compatibility between JSBI CJS default export and CJS environment
Related
Related to #100
How is this tested?
All existing tests pass
Testing failing @ 8b43670a6954f684f15e1c64abce1b70230703a4

I appreciate the help here. I'm not sure if replacing native BigInts with a JSBI variant of them matches what I have in mind for this package. I intend this package to be a reference implementation of proposal-decimal, not necessarily a production-ready package that works in the widest spectrum of JS environments. BigInts are fairly widely available by now (though I understand that they're not available everywhere).

I've merged in your changes that allow us to emit both CJS and ESM -- thanks! Would you like to rebase your work here on top of the latest state?

re-worked on top of the latest commit of main branch (b218eaa47be2bd48402fa29c0c3e5b5fbca815e3)
force pushed new commit at d4789ffcbf546aff6eba6ff32187db52db3a5ef5
all existing test passed

Thank you!