doc: vulnerabilities: Add information about CVE-2023-4265

Add information about CVE-2023-4265

FWIW I am tempted to add a custom Sphinx directive to help with bringing more structure to the list of CVEs and make it easier to read for folks. Also would like to see them listed in reverse chronological order (most recent at the top) and have a clear visual clue of which are fixed vs. which ones aren't. Thanks!

@kartben that makes sense, the order. Having some ways to filter the list would be good to have too.


Stack: avoid re-chunking (dask) and insert new coordinates arbitrarily

The behavior of stack was not quite intuitive to me, and I'd like to understand if this was an explicit technical decision or if it can be changed.
First, with regard to chunking:
arr = xr.DataArray(da.zeros((2, 3, 4), dtype=np.int, chunks=(1 ,1, 1)), dims=['z', 'y' ,'x'])
stacked = arr.stack(v=('y', 'x'))
print(stacked)
--
xarray.DataArray 'zeros-6eb2edd0fca7ec97141e1310bd303988' (z: 2, v: 12)>
dask.array<reshape, shape=(2, 12), dtype=int64, chunksize=(1, 4), chunktype=numpy.ndarray>
Coordinates:
  * v        (v) MultiIndex
  - y        (v) int64 0 0 0 0 1 1 1 1 2 2 2 2
  - x        (v) int64 0 1 2 3 0 1 2 3 0 1 2 3
Dimensions without coordinates: z

Why did the number of chunks change in this case?  Couldn't the chunksize be (1,1)?
Next, why is it necessary to put the new dimension at the end?  It seems there are often more natural (perhaps just to my naive thought process) placements.  One example would be that same array above, but stacked on the first two dimensions.  I would want the new dimension to be the first dimension (again without the rechunking above).  To accomplish this, I do:
arr = xr.DataArray(da.zeros((2, 3, 4), dtype=np.int, chunks=(1 ,1, 1)), dims=['z', 'y' ,'x'])
stacked = arr.stack(v=('z', 'y')).transpose('v', ...).chunk({'v': 1})
print(stacked)
--
<xarray.DataArray 'zeros-6eb2edd0fca7ec97141e1310bd303988' (v: 6, x: 4)>
dask.array<rechunk-merge, shape=(6, 4), dtype=int64, chunksize=(1, 1), chunktype=numpy.ndarray>
Coordinates:
  * v        (v) MultiIndex
  - z        (v) int64 0 0 0 1 1 1
  - y        (v) int64 0 1 2 0 1 2
Dimensions without coordinates: x

The dask graph for this last bit insert a rechunk and two transposes, but my intent was not to have any of the underlying chunks change at all.  Here is 1 of 8 pieces of the graph (with optimization off -- optimization combines operations, but doesn't change the topology or the operations):

Is it technically feasible for stack to avoid rechunking, and for the user to determine where the new dimensions should go?

dask seems to rechunk when reshaping
dask.visualize(arr.data.reshape((6, 4)))

The core stack operation is here:
https://github.com/pydata/xarray/blob/2acd0fc6563c3ad57f16e6ee804d592969419938/xarray/core/variable.py#L1456-L1478
I think the dimension is at the end for coding convenience...

There has been some discussion on the dask chunking issue here:
https://github.com/dask/dask/issues/3650
https://github.com/dask/dask/issues/5544
Regarding the position of the inserted variable, it is not related to the chunking.  It seems possible to do this.  Would this be an acceptable change?  If so, the first problem is the signature, as multiple dimensions may be passed in.  :/

Amazing. Thanks @phofl


JSON Error on Android in Foreground

Hey,
I'm thinking this is a bug, but I'm not truly sure since this is my first time dabbling with push notifications.
On Android, while in the foreground, I get this error during the onMessageReceived event:
W/System.err( 2830): org.json.JSONException: No value for message
W/System.err( 2830): 	at org.json.JSONObject.get(JSONObject.java:389)
W/System.err( 2830): 	at org.json.JSONObject.getString(JSONObject.java:550)

My onMessageReceived looks like this:
notificationCallbackAndroid: (message, data, notification) => {
    console.log("MESSAGE: " + JSON.stringify(message));
    console.log("DATA: " + JSON.stringify(data));
}

While in the foreground, the message is always null, but data contains some actual data.  The data parameter contains the following:
{
    "foreground": true,
    "custom-key1": "custom-value1",
    "custom-key2": "custom-value2"
}

It contains all my custom key-value pairs, but not the actual message that was sent.  For clarity, I am using FCM which I believe is the only option now, but honestly I'm not sure.
I've confirmed that in the background, I do in fact receive a notification in the tray.  However, it is still useful to receive the message in the foreground.
Please let me know.
NativeScript 2.5.4
Android 5.1.1
macOS Sierra
Thanks,

Seems sort of related to this https://github.com/NativeScript/push-plugin/issues/98, but not really.

I'm not 100% sure, but when I remember right I've experienced the same issue. I guess it's related to my ticket here: https://github.com/NativeScript/push-plugin/issues/100

As an update, it seems the problem could be a mismatch between how the Firebase dashboard sends messages, vs what is in their API documentation.
When I send via Postman, everything is fine in the background and foreground.  When I use the Firebase dashboard, I get strange results.

Just to back that comment up: I have the same experience with the Firebase plugin and the Firebase dashboard. Using a CURL script works fine though.

My 2 cents - the message parameter in the callback is populated only if there is data.message key and value, so this is pretty much expected. More information is in the [README] (https://github.com/NativeScript/push-plugin#receive-and-handle-messages-from-fcm-on-android) section for handling messages from FCM.

+1 having the same problem


Tip26 Adding folder and ruby markdown file

issue #60
Tip26 Adding folder and ruby markdown file

Code on this page is deprecated
Unable to validate any code
Able to validate copy content, except for instructions related to deprecated code
Fixed broken links

Sent message to Diego asking what to do about this tip since it contains deprecated resources and links. Pending possible deletion.


Use default value that's safe with<EMAIL_ADDRESS>

<EMAIL_ADDRESS>will throw an error if you pass a line number equal to
0. See:
https://github.com/mozilla/source-map/blob/0.1.43/lib/source-map/source-map-consumer.js#L285-L287
Since Karma is not wrapping that in a try catch, the exception will just crash karma. Changing the default line number to 1 will not throw and a test exception stack trace will still output correctly.

@karma/owners ping

I would put fix(***) in the commit message, but I'm not sure what to put in the parenthesis for this.

@mtscout6 Thanks.
When line is not defined or equal '0'?

Related issue https://github.com/karma-runner/karma/issues/1274

I understand your sentiment about feeling like this is just fixing the symptom, so let me explain the issue a little deeper. I'm currently seeing this issue isolated to Firefox.
For example without my fix I get the following output and the karma process crashes, it does not matter it the error is in a test or the code being tested.
➜  one-exchange git:(team-4) ✗ karma start
INFO [karma]: Karma v0.12.31 server started at http://localhost:9876/
INFO [launcher]: Starting browser Chrome
INFO [launcher]: Starting browser Firefox
INFO [launcher]: Starting browser PhantomJS
INFO [Firefox 34.0.0 (Mac OS X 10.10)]: Connected on socket z-Wd2IS8Ga2bGoA-4Djx with id 96357773
INFO [Chrome 40.0.2214 (Mac OS X 10.10.2)]: Connected on socket SWejfJH3UCtjk3Xw4Djw with id 61391085
INFO [PhantomJS 1.9.7 (Mac OS X)]: Connected on socket EY2QNttHkOjUIX4A4Djy with id 82304088
PhantomJS 1.9.7 (Mac OS X) Directive: addToCart toggles the text FAILED
        ReferenceError: Can't find variable: test
            at /mnt/Resources/dev/one-exchange/src/ExtendHealth.OneExchange/content/scripts/specs/test-main.js:218:0 <- webpack:///src/ExtendHealth.OneExchange/content/scripts/specs/add-to-cart-directive-spec.js:58:0
PhantomJS 1.9.7 (Mac OS X): Executed 1 of 2002 (1 FAILED) (skipped 2001) ERROR (0.609 secs PhantomJS 1.9.7 (Mac OS X): Executed 1 of 2002 (1 FAILED) (skipped 2001) ERROR (0.609 secs / 0.02 secs)
Firefox 34.0.0 (Mac OS X 10.10): Executed 0 of 2002 SUCCESS (0 secs / 0 secs)
ERROR [karma]: [TypeError: Line must be greater than or equal to 1, got 0]
TypeError: Line must be greater than or equal to 1, got 0
    at SourceMapConsumer_findMapping [as _findMapping] (/mnt/Resources/dev/one-exchange/node_modules/source-map/lib/source-map/source-map-consumer.js:286:15)
    at SourceMapConsumer_originalPositionFor [as originalPositionFor] (/mnt/Resources/dev/one-exchange/node_modules/source-map/lib/source-map/source-map-consumer.js:346:24)
    at /mnt/Resources/dev/one-exchange/node_modules/karma/lib/reporter.js:49:28
    at String.replace (native)
    at /mnt/Resources/dev/one-exchange/node_modules/karma/lib/reporter.js:36:23
    at /mnt/Resources/dev/one-exchange/node_modules/karma/lib/reporters/base.js:105:14
    at Array.forEach (native)
    at specFailure (/mnt/Resources/dev/one-exchange/node_modules/karma/lib/reporters/base.js:104:16)
    at onSpecComplete (/mnt/Resources/dev/one-exchange/node_modules/karma/lib/reporters/base.js:85:12)
    at null.<anonymous> (/mnt/Resources/dev/one-exchange/node_modules/karma/lib/events.js:15:22)

With the fix:
➜  one-exchange git:(team-4) ✗ karma start
INFO [karma]: Karma v0.12.31 server started at http://localhost:9876/
INFO [launcher]: Starting browser Chrome
INFO [launcher]: Starting browser Firefox
INFO [launcher]: Starting browser PhantomJS
INFO [PhantomJS 1.9.7 (Mac OS X)]: Connected on socket jpJiybv612ww-62s5lpN with id 96250461
INFO [Chrome 40.0.2214 (Mac OS X 10.10.2)]: Connected on socket s1OMD9qBcbfgwpK35lpM with id 61230800
INFO [Firefox 34.0.0 (Mac OS X 10.10)]: Connected on socket IV13FDfieF_aEtCk5lpO with id 9808170
PhantomJS 1.9.7 (Mac OS X) Directive: addToCart toggles the text FAILED
        ReferenceError: Can't find variable: test
            at /mnt/Resources/dev/one-exchange/src/ExtendHealth.OneExchange/content/scripts/specs/test-main.js:218:0 <- webpack:///src/ExtendHealth.OneExchange/content/scripts/specs/add-to-cart-directive-spec.js:58:0
PhantomJS 1.9.7 (Mac OS X): Executed 1 of 2002 (1 FAILED) (skipped 2001) ERROR (0.562 secs PhantomJS 1.9.7 (Mac OS X): Executed 1 of 2002 (1 FAILED) (skipped 2001) ERROR (0.562 secs Firefox 34.0.0 (Mac OS X 10.10) Directive: addToCart toggles the text FAILED
        ReferenceError: test is not defined in /mnt/Resources/dev/one-exchange/src/ExtendHealth.OneExchange/content/scripts/specs/test-main.js:1:0 <- null:0:0 (line 218)
        __WEBPACK_AMD_DEFINE_RESULT__</</<@/mnt/Resources/dev/one-exchange/src/ExtendHealth.OneExchange/content/scripts/specs/test-main.js:218:10 <- webpack:///src/ExtendHealth.OneExchange/content/scripts/specs/add-to-cart-directive-spec.js:58:0

PhantomJS 1.9.7 (Mac OS X): Executed 1 of 2002 (1 FAILED) (skipped 2001) ERROR (0.562 secs PhantomJS 1.9.7 (Mac OS X): Executed 1 of 2002 (1 FAILED) (skipped 2001) ERROR (0.562 secs / 0.02 secs)
PhantomJS 1.9.7 (Mac OS X): Executed 1 of 2002 (1 FAILED) (skipped 2001) ERROR (0.562 secs / 0.02 secs)
Chrome 40.0.2214 (Mac OS X 10.10.2) Directive: addToCart toggles the text FAILED
        ReferenceError: test is not defined
            at null.<anonymous> (/mnt/Resources/dev/one-exchange/src/ExtendHealth.OneExchange/content/scripts/specs/test-main.js:218:10 <- webpack:///src/ExtendHealth.OneExchange/content/scripts/specs/add-to-cart-directive-spec.js:58:0)
PhantomJS 1.9.7 (Mac OS X): Executed 1 of 2002 (1 FAILED) (skipped 2001) ERROR (0.562 secs / 0.02 secs)
PhantomJS 1.9.7 (Mac OS X): Executed 1 of 2002 (1 FAILED) (skipped 2001) ERROR (0.562 secs / 0.02 secs)
Firefox 34.0.0 (Mac OS X 10.10): Executed 1 of 2002 (1 FAILED) (skipped 2001) ERROR (1.25 secs / 0.031 secs)
Chrome 40.0.2214 (Mac OS X 10.10.2): Executed 1 of 2002 (1 FAILED) (skipped 2001) ERROR (0.987 secs / 0.058 secs)

I didn't realize it when I first submitted this pull request, but with my fix there's no Firefox exception details... Thoughts?

After applying the patch from #1098 I'm seeing better results than I am with this. I'd rather see that one go through.

ReferenceError: test is not defined in /mnt/Resources/dev/one-exchange/src/ExtendHealth.OneExchange/content/scripts/specs/test-main.js:1:0 <- null:0:0 (line 218)

Strange output...
Are you use jasmine?

Yes, and I'm sure it's an old version for this project....

@mtscout6 Thanks.
I think the problem in jasmine error formatter not in Firefox


[semantic-arc-opts] Add some file level flag headers to organize the code by function.

Just slicing the onion of refactoring commits on top of adding support for eliminating SIL phi arguments.

@swift-ci smoke test and merge


Fill

Now if you select fill option,the image will fill your screen

@w278206624
Thank you for PR.
I've checked your changes.
Why did you comment out some lines?

I want a kind of image into the screen after a full effect, note that this line of code can achieve this effect, of course, can also provide a choice to achieve this effect.

@w278206624
You can use ZoomMode.
Is this useless?


Docs on how to use UEFI feature

Currently if I run my os:
[dependencies.bootloader]
version = "0.10.0"
features = ["binary", "uefi_bin"]

I get:
   Compiling bootloader v0.10.0
error: failed to run custom build command for `bootloader v0.10.0`

Caused by:
  process didn't exit successfully: `H:\Andy\Rust\aero\target\debug\build\bootloader-2cdadb50cdaed247\build-script-build` (exit code: 101)
  --- stderr
  thread 'main' panicked at 'The UEFI bootloader must be compiled for the `x86_64-unknown-uefi` target.', C:\Users\user\.cargo\registry\src\github.com-1ecc6299db9ec823\bootloader-0.10.0\build.rs:41:13
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Which is kindof obvious but until bootimage get support for it?

Also some docs on windows user how to get OVMF.fd without WSL if thats possible :)

See https://docs.rs/bootloader/0.10.1/bootloader/ for some instructions on how to create the bootable disk images. The idea is that you create your own "boot" crate instead of using bootimage. Unfortunately there is no example project yet, but I'm working on an step-by-step explanation here.

All good! I will check it out thanks!

Also some docs on windows user how to get OVMF.fd without WSL if thats possible will be great :)

Absolutely, thanks for the suggestion! I'm still figuring out the best way to do this, but it seems like downloading a precompiled version is the easiest solution. The question is where from... For now, I think you should be able to use the precompiled versions of the pebble project.

Thanks!

@phil-opp is there a flag for the bootloader to only build UEFI, or better, only the boot-uefi-<kernel>.efi file? I do not need the other files, and they waste time so to speak.

Thanks for your response. I found the flag I need - it was --firmware uefi when invoking the builder command to just build UEFI related files :)


dag: explanation of what pipelines are

Fixes #1500

Thanks for the attempt @imhardikj but a) I'm not sure why we're working on this in the context of your GSoD project (is it a 1.0 update or a how-to?) and b) the current changes aren't very meaningful, probably not more correct than before either.
I realize it's a draft so maybe you had other intentions but as GSoD is coming to an end soon, there'll be no time to help you with this so I'm closing it for now. Thanks again


unpac.me plugin - API access is now for paid account

Within the readme.md it says that a free account is needed to obtain the API key:
You will first need to sign up for a free account before you can use it. The first time you try to upload or download you will be prompted for your API Key which is available from your account page.
However, the access of the API of unpac.me is now only available for paid accounts.

Same problem here. TAT


Feat: Multiple Selection Support

Feature request
Overview
Dear radix-ui team,
I love using the Select primitive in radix-ui, but I have a feature request.
Currently, the Select component allows single-item selection only. I kindly request adding support for multiple selection, as it would significantly enhance its usability.
Examples in other libraries
Native select
<select id="multiSelect" multiple>
  <option value="option1">Option 1</option>
  <option value="option2">Option 2</option>
  <option value="option3">Option 3</option>
  <option value="option4">Option 4</option>
  <option value="option5">Option 5</option>
</select>

Many other libraries, etc.:
react-select
material-ui
...
Who does this impact? Who is this for?
Users can select multiple items at once, saving time and effort.
Developers can use the Select primitive for efficient data filtering by allowing users to select multiple options.
Many users are already accustomed to multi-select functionality, making the component more intuitive.
Thank you for considering this feature request! 🙏 Your dedication to improving radix-ui is truly appreciated. 🚀 Looking forward to seeing the library become even more versatile and user-friendly with multiple selection support. If you have any questions or need further input, please don't hesitate to reach out. Keep up the fantastic work! 👍😊

I would like to +1 this feature request.
It would be great to have an element that

has feature parity with the builtin <select multiple> element, with regard to keyboard behavior in particular (I'll expand below)
has all the Radix UI goodness in terms of composability and stylability
perhaps also has a nicer API for accessing the selected options compared to the builtin <select multiple>'s API :)

Use case / who is this for?
This primitive / element will enable UIs where users can perform bulk actions on multiple items at once. Examples include

Selecting multiple todos in a todo list app to delete / move to a new list / favourite
Selecting multiple tabs in a chrome extension to close / move to a new window / bookmark
Selecting multiple songs in a music app to add to a playlist / delete from a playlist / favourite

This pattern is common in many native apps, most notably every native file manager (Windows Explorer, Finder, etc). These apps allows you to select multiple files in order to perform actions (open / copy /cut / move/ delete, etc) on multiple files.
Keyboard goodness of builtin <select multiple>
Crucially (for me 😁), native apps and the builtin <select multiple> have a great keyboard experience for powerusers. You can do the following:

press DOWN / UP to select the next/previous item
press SHIFT + DOWN / UP to expand the selection to include both the currently selected and the next / previous item
press CMDorCTRL + DOWN / UP to move the active item down / up without modifying the selected items
press SPACE to toggle the selected state of the current active item.
Mouse actions: You can also do CMDorCTRL and click to select multiple items using the mouse, or SHIFT + click to select a range of items.

Shortcomings of existing implementations in other libraries
The builtin <select multiple> has all the keyboard goodness, but is not styleable and customisable
Various other libraries, including react select, Material UI and even Tanstack React Table provide versions of the select multiple pattern, and are headless or provide ways of showing custom UIs, but none of them (that I have found) have the keyboard goodness described above.

Isn't this a duplicate of #1342?

Hello Guys.
any update for multi select in radix ui?
@kimskovhusandersen @buzzb0x

A multi-select would be rly awesome

Duplicate of #1270


:memo: Fix: remove tevm bundler references and docs

Description
Concise description of proposed changes
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1207  👈
#1206
#1205
main

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

Join @roninjin10 and the rest of your teammates on  Graphite


default permissions for /root and /var/tmp are questionable

In 2.1.2, bootstrap creates /root and /var/tmp with 755 permissions.
World-readable /root is not a good idea normally. 750 should be fine.
System-wide tmp dir should normally be writeable for all and have a sticky bit - 1777.
Re-reporting the issue here as agreed in #197.

Fixed in [master 0721d4e]


Added the production config option

The other half of its Implementation: PR for the Zero-framework repo

Merged in release 3.3


SOLR-16397: Modify v2 'renamecore' API to be more REST-ful

https://issues.apache.org/jira/browse/SOLR-16397

Description
V2(JAX-RS) Endpoints for core admin op "RENAME".
Solution
This commit changes the v2 "renamecore" API to be more in line with the REST-ful design we're targeting for Solr's v2 APIs.
Following these changes, the v2 API now appears as:
POST /api/cores/coreName/rename {...}
Although not shown above, the 'rename' command specifier has been removed from the request body. This commit also converts the API to the new JAX-RS framework.
Tests
Already few test cases are present which are modified as per the new changes.
Checklist
Please review the following and check all that apply:

[x] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[x] I have created a Jira issue and added the issue ID to my pull request title.
[x] I have given Solr maintainers access to contribute to my PR branch. (optional but recommended)
[x] I have developed this patch against the main branch.
[x] I have run ./gradlew check.
[x] I have added tests for my changes.
[x] I have added documentation for the Reference Guide

Thanks again for the PR @iamsanjay !  Really starting to crank through these now - it's awesome!


DSA overlapping accesses

DSA should be able to recognize and overlapping access. (ie if two addresses are read into 128 bit register, stored in  memory and then accessed separately).
https://github.com/UQ-PAC/BASIL/pull/222#issuecomment-2337117908
R31 + 0x10 refers to a stack element node with two cells. One at offset 0 (R31 + 0x10) and one at offset 8(R31 + 0x18).
The issue here is that the analysis doesn't merge the cell for add_six with the second cell in of R31 + 0x10 node since it can't yet tell the 128 bit reads add_six as well as add_two.
Each global is represented using separate node. the analysis currently merges add_two's node with the node of the stack position.
On possibility would be to represent globals that have overlapping accesses as one node. similar to the stack.  ( i think this is only safe if we we can find all the accesses to the globals to soundly do this) however unlike the stack we can't find all accesses locally (even indirect stack references can't be found without a pointer analysis). Alternatively we can group consecutive globals into one node.
// 0x10DC0 contains a pointer to the procedure add_two
// 0x10DC8 contains a pointer to the procedure add_six
00000404: R8 := R8 + 0xDC0
// loading 128 bits from 0x10DC0 loads both the 64-bit pointer at address 0x10DC0
// and the 64-bit pointer at address 0x10DC8 to V0, concatenated together
0000040b: V0 := mem[R8, el]:u128
// storing V0 to the stack stores the pointer to add_two at R31 + 0x10 and the pointer to add_six at R31 + 0x18
00000413: mem := mem with [R31 + 0x10, el]:u128 <- V0
0000041a: R8 := mem[R8 + 0x10, el]:u64
00000422: mem := mem with [R31 + 0x20, el]:u64 <- R8
00000429: R8 := mem[R31 + 0x10, el]:u64
0000042e: R30 := 0x7D0
00000431: call R8 with return %00000433

00000433:
// the DSA says that R8 at this assignment points to node 434 which is empty, but it should point to add_six
// or alternatively some node that represents that the pointers to add_two and add_six were loaded together and stored on the stack together
00000438: R8 := mem[R31 + 0x18, el]:u64
0000043d: R30 := 0x7D8
00000440: call R8 with return %00000442

indirect overlapping accesses are also an issue:
R0 = G + 8  // where G is base address for the heap
R1 = G + 12 // two consecutive globals
R2 = Malloc()
*R2 = R0 // 64 bit write
R3 = *R2  // 64 bit read
R4 = *R3 // 128 bit read

It's not going to work to try to detect these accesses before the DSA. You will need a way of checking if an access is accessing multiple nodes simultaneously in this way so they can be concatenated and merged.

I don't think your pseudocode is the clearest example. Global variables aren't on the heap, so the base address of the heap isn't relevant, and the global variable with address G + 8 is only 32 bits, so even a 64-bit access to it would also access the global variable at G + 12

yeah my example is not great. I confused myself a little while thinking about the heap objects. since what you suggested can be done for stack and globals where the adjacent  node is known. can check if what is being accessed is stack or global (or both if they have been unified prior) and do the merge. But it doesn't make a lot of sense for the heap objects. one possibility is to expand the heap nodes like we do now to accommodate the access regardless of its size. This is similar to if we have malloc and access outside of the allocated size of the memory block.
currently the analysis expands the malloc. The analysis will know what address R1 holds with respect to the malloc base.
if malloc creates a new node M. R0 -> (M, 0) and R1 -> (M,32).
However, the analysis won't be able to tell if writes to R1 will change the contents of another object in memory
R0 = Malloc(16)
R1 = R0 + 32

You don't need to worry about this sort of case for heap objects - if you access out of the allocated size of the heap object, you don't know what will be accessed (most likely is it causes a segfault), so there should be some sort of collapse of the node. This is not a case that will be encountered in code that is working correctly.


Internal: enable Next.js ESLint plugin

Summary
Enables the Next.js ESLint plugin: https://nextjs.org/docs/basic-features/eslint
Functionality to review

Google Analytics
Docsearch
Images load correctly in the docs

References

https://github.com/vercel/next.js/blob/canary/errors/no-script-in-document-page.md
https://github.com/vercel/next.js/blob/canary/errors/next-script-for-ga.md#using-gtagjs

What advantages does this get us over our previous eslint setup?


Issue 10

WIP for deploy preview

Also you git history is a bit weird.  It looks like you pulled in some of @wrunion 's commits.  It would probably be a good idea to clean that up a bit.

PR no longer necessary


Re-enable docs cache with fixes

~This is built on top of #78614, to be tested after 4.1 is out.~

No more custom resource type.
Fixed the API scope of EditorSettings.

Fixes #77878.
Fixes #78647.

Thanks for testing.
It seems that ClassDB::class_exists("EditorSettings") is always true, so I'm removing that check. There's no harm in redundant GDREGISTER_CLASS(), as far as I can tell.

I forgot to unmark it. I've smoke-tested it just in case. Seems good to go.

Thanks!

As of this PR being merged (92960b7a22dabe26bb724b7b0d00a5fd03324f3a) I am getting an immediate crash when opening a project:
libc++abi: terminating due to uncaught exception of type std::__1::system_error: recursive_mutex lock failed: Invalid argument

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	       0x1842fc724 __pthread_kill + 8
1   libsystem_pthread.dylib       	       0x184333c28 pthread_kill + 288
2   libsystem_c.dylib             	       0x184241ae8 abort + 180
3   libc++abi.dylib               	       0x1842ecb84 abort_message + 132
4   libc++abi.dylib               	       0x1842dc3b4 demangling_terminate_handler() + 320
5   libobjc.A.dylib               	       0x183fb303c _objc_terminate() + 160
6   libc++abi.dylib               	       0x1842ebf48 std::__terminate(void (*)()) + 16
7   libc++abi.dylib               	       0x1842eed34 __cxxabiv1::failed_throw(__cxxabiv1::__cxa_exception*) + 36
8   libc++abi.dylib               	       0x1842eece0 __cxa_throw + 140
9   libc++.1.dylib                	       0x18426a8b4 std::__1::__throw_system_error(int, char const*) + 100
10  libc++.1.dylib                	       0x18425f11c std::__1::recursive_mutex::lock() + 40
11  godot.macos.editor.arm64      	       0x104ba1abc ResourceImporterTexture::update_imports() + 96
12  godot.macos.editor.arm64      	       0x104596958 EditorNode::_notification(int) + 2764
13  godot.macos.editor.arm64      	       0x1045fea98 0x102ce4000 + 26323608
14  godot.macos.editor.arm64      	       0x10721e178 Object::notification(int, bool) + 32
15  godot.macos.editor.arm64      	       0x10535d530 SceneTree::_process_group(SceneTree::ProcessGroup*, bool) + 280
16  godot.macos.editor.arm64      	       0x10535b398 SceneTree::_process(bool) + 676
17  godot.macos.editor.arm64      	       0x10535bafc SceneTree::process(double) + 240
18  godot.macos.editor.arm64      	       0x10309ae88 Main::iteration() + 952
19  godot.macos.editor.arm64      	       0x10304ca2c OS_MacOS::run() + 116
20  godot.macos.editor.arm64      	       0x103075db8 main + 304
21  dyld                          	       0x183fdbf28 start + 2236

The previous merge commit c4e582262fa45483b1d68c5e7fa05351070355a0 works fine.

@aaronfranke Make sure to remove editor cache or use the self-contained mode.

@YuriSizov Thanks, clearing the editor cache fixed it. I had previously tried clearing the project cache which did not work, but clearing the editor cache works. Also I'm not sure but I think you have to clear both the editor cache and the project cache at the same time, since I did have one crash occur after clearing the editor crash, but then I cleared the project cache again and it worked.

Well, the crash is back again, and now it keeps happening even after clearing all the caches. Maybe #79936.

Well that stack points to ResourceImporterTexture::update_imports() for some reason. Latest PRs to touch the texture importer don't seem to have anything to do with this, https://github.com/godotengine/godot/pull/68460 and https://github.com/godotengine/godot/pull/78456.
This is with debug symbols already? We can't get more information from the stack trace?


PATCH not available (post requires all fields)

Fixed in https://github.com/kasappeal/sparrest/commit/93f2918c33976dc11263931a6cbe368e4e851456


Fix dependency on gevent to get pykafka installing again

The pykafka 2.2.1 is not installing in a clean virtualenv at the moment, because it appears to be having some trouble using >= and < with gevent's release candidate version number scheme. This switches over to ~, which should be equivalent to what was originally intended, but appears to work with versions
like 1.1rc6. This may need to be revisited once gevent 1.1 actually is released though.

Thanks for catching this, @erickt.


updated configuration to make sure that cross module coverage works

Codecov Report

Merging #9141 into develop will increase coverage by 9.63%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #9141      +/-   ##
=============================================
+ Coverage      42.55%   52.18%   +9.63%
- Complexity     28327    35975    +7648
=============================================
  Files           2523     2526       +3
  Lines         197276   197338      +62
  Branches       35347    35353       +6
=============================================
+ Hits           83947   102989   +19042
+ Misses         99563    79377   -20186
- Partials       13766    14972    +1206

Impacted Files
Coverage Δ
Complexity Δ

...re/storage/cache/chm/readbuffer/BoundedBuffer.java
82.85% <0%> (-5.72%)
2% <0%> (ø)

...nt/distributed/network/OUDPUnicastNodeManager.java
76.74% <0%> (-4.66%)
10% <0%> (-1%)

...entechnologies/orient/etl/OETLExtractorWorker.java
95.83% <0%> (-4.17%)
5% <0%> (ø)

...re/storage/cache/chm/readbuffer/StripedBuffer.java
37.77% <0%> (-2.23%)
11% <0%> (-3%)

...ntechnologies/orient/server/OClientConnection.java
71.51% <0%> (-1.22%)
53% <0%> (+1%)

...echnologies/common/concur/lock/ScalableRWLock.java
43.75% <0%> (-0.79%)
13% <0%> (-1%)

...ogies/orient/distributed/network/ONodeManager.java
74.16% <0%> (-0.77%)
63% <0%> (-1%)

...ies/orient/core/sql/operator/OQueryOperatorOr.java
41.37% <0%> (ø)
10% <0%> (+2%)
:arrow_up:

...e/sql/functions/math/OSQLFunctionMathAbstract.java
8.69% <0%> (ø)
2% <0%> (+1%)
:arrow_up:

...orient/core/sql/parser/OEqualsCompareOperator.java
63.63% <0%> (ø)
6% <0%> (+1%)
:arrow_up:

... and 929 more

Continue to review full report at Codecov.

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


Remove 'NOT' from a conditional

NOT is not a bash keyword.
The negation is done via '!'
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Merged in https://github.com/awslabs/aws-c-common/pull/922


Promote the YAML config on project import

This PR modifies the manual import screen to streamline things and promote the YAML config file for importing new repositories.

Link the YAML configuration docs
Update the YAML configuration docs to have a commented YAML file with the most common options
Remove the "advanced project options". All of those can be set after the project is built except documentation type (eg. sphinx) and that can be set in the YAML config.

Fixes #5414
Screenshots
Before

After

It seems that it does also affect the "automatic" import from VCS services, not only "Manual import".

I'll take a look at that. I thought they were totally separate.

As-is, this change works fine with the corporate side and with the automatic import via VCS integrations. Interestingly, the automatic import with integrations sends the project description but that was never used with the advanced form.
This change does impact the corporate side in that there will be no way to specify before importing to use a different documentation type (eg. mkdocs, sphinx dirhtml) other than with the YAML file. Are we ok with that?
I do think that it could simplify things to refactor the ImportWizardView to not be a wizard but just be a regular view. That is a bigger change however as it involves completely refactoring the view on .org and where it is overridden in .com. I am not opposed to it but it will take a bit more time and coordination. Thoughts?

This change does impact the corporate side in that there will be no way to specify before importing to use a different documentation type (eg. mkdocs, sphinx dirhtml) other than with the YAML file. Are we ok with that?

I'm not sure, I mean people using a different location from sphinx will face an error too or people that need a requirements file, and they need to go the admin page anyway.
So, I'm ok with removing the advanced options from the import menu, something we can't do is remove the advanced option from the admin page, not till we have a solution for changing settings to build old versions of docs

So, I'm ok with removing the advanced options from the import menu, something we can't do is remove the advanced option from the admin page, not till we have a solution for changing settings to build old versions of docs

Agreed.

This change does impact the corporate side in that there will be no way to specify before importing to use a different documentation type (eg. mkdocs, sphinx dirhtml) other than with the YAML file. Are we ok with that?

I'm not 100% convinced yet.
On one side, if we want to promote the YAML file and make the user to use it, giving the "Advanced" options at import time is not a good idea.
On the other side, the on-boarding experience for all the MkDocs projects won't be amazing (the first build will always fail --unless a YAML file propoerly configured already exists in the repo)

I do think that it could simplify things to refactor the ImportWizardView to not be a wizard but just be a regular view. That is a bigger change however as it involves completely refactoring the view on .org and where it is overridden in .com. I am not opposed to it but it will take a bit more time and coordination. Thoughts?

I'm :+1: on this. Although, if this PR is ready to be merged, we can merge it and make the refactor as a second step.

On the other side, the on-boarding experience for all the MkDocs projects won't be amazing (the first build will always fail

Actually, there a lot of projects that will fail if they are not correctly setup, like having the correct requirements file, having the conf.py file in another directory than docs, needing to install the project, etc. We were trying to do some magic trying to guess this stuff, but in the end it caused more problems in my opinion.

I wonder if it's worth just adding the callout to the YAML file for now, but allowing users to edit advanced options still? That way we get both benefits, but don't make a worse experience for users who are not on YAML yet.

I just wanted to comment here in case we come back to this. We decided to go with #5485 which does the promotion without removing the advanced project settings for now. The advanced project settings can probably go away but it looks like it is a bigger change.


Some improvements to blue-app-monero.rst

Renaming folder "developper" to "developer".

Changes in blue-app-monero.rst

Normalizing spelling of "pre-hash" => "prehash".
Various typo and spelling fixes.

Thanks for the review
Yes it was "come". I fixed it with dEBRUYNE-1 suggestion.

Cheers  :-)


Improve Latex visualisation error message for xypic, qcircuit and standalone

What is the expected enhancement?
Recently when trying to run the latex circuit drawer in a new environment I encountered a vague error that took some digging through the latex logs to find what the actual problem was. In the end all I needed was to install xypic, qcircuit and standalone. It would be good if we had a better error message like we have for pillow and pdflatex.
Suggested implementation
Update qiskit/visualization/circuit_vizualization to throw an error if xypic, qcircuit or standalone are not installed. They can all be installed with tlmgr install

This is not trivial to do, mostly because those error messages get raised by an external process. Mainly we can't know this until we try to run latex to generate the visualization. The missing package is part of your latex distribution and only the latex compiler can tell if it's missing. We're not really in a place to detect whether the latex packages are installed because it's specific to each individual latex distribution. The best we can do is really just parrot what latex tells us when we call out to the external program. This was actually one of the first issues I worked on in qiskit: https://github.com/Qiskit/qiskit-terra/issues/792 which was fixed in: https://github.com/Qiskit/qiskit-terra/pull/808
I'm not sure what else we can realistically do here, the exception message explicitly says that latex compilation failed look at the latex error log for the details: https://github.com/Qiskit/qiskit-terra/blob/main/qiskit/visualization/circuit_visualization.py#L424-L430
As for the tlmgr step that's not actually a general solution, it depends on how you have latex installed and which latex distribution you're using.

There are ways we could potentially improve the error message, still - if raising an error is expected to be a termination point of a program (i.e. we don't expect anybody to try/catch it), then we could do some extra checks to provide better errors if we wanted.
For example, we could take a leaf out of C build processes, and try to do things like LaTeX-compile three dummy files that simply try to \usepackage the right thing, without actually typesetting anything - regardless of the TeX distribution, we already assume that the compiler is pdflatex.


Minimize Bugs in the backend

https://github.com/sopra-fs23-group-32/SoPra23_Server/commit/d1cf4385e9b2666ca726703ca03296a910460b6d
https://github.com/sopra-fs23-group-32/SoPra23_Server/commit/5aa04d127d03f6550006c71426a606449e0b0d3d


Minor fixes (proposal)

@juanibiapina The project is not maintained anymore. Feel free to fork and release.

Starting to bring it back into shape :bowtie: - couldn't commit to this for, well, 9 years. Thanks for the fixes!

@qrush Glad to see some maintenance again. I'm still pretty happy with the tool-- Easy to get use, gets out the way, not much new to learn to use it.
Once set up, new commands can be written in Node.js, Fish or another language of your choice-- our use of it is not limited to bash scripting.


Narrow via discriminant property through optional chain

Not yet sure this is right
Fixes #40397

@typescript-bot pack this

@typescript-bot pack this

@typescript-bot test this
@typescript-bot user test this
@typescript-bot run dt

@typescript-bot test this
@typescript-bot user test this
@typescript-bot run dt

User and RWC tests are clean

User and RWC tests are clean

I'm still tweaking the DT tests, and the DT run was going to give the wrong output, so I cancelled the current run. I'll start a new one:
@typescript-bot run dt

I'm still tweaking the DT tests, and the DT run was going to give the wrong output, so I cancelled the current run. I'll start a new one:
@typescript-bot run dt


Any update for wwgc/www/CardboardDevice.proto file?

i think this file is too old now, should be update with Daydream controller and Daydream keyboard info.
for wwgc/www/CardboardDevice.proto file, I need it to see is it possible to make  GVRProfileViewer for current_device_param

#114 Read Cardboard Profile QR Code and update Distortion in googlevr/gvr-ios-sdk


KeyError on missing zarr chunks

Hi!
I'm playing around with mdio and came across this error on one of my test files
mdio = MDIOReader(
       "abfs://somefile.mdio",
       return_metadata=True,
       storage_options={ ... }
)

 _ = mdio[:,:,:100] // KeyError: somefile.mdio/data/chunked_012/5/3/24'

The files is stored in an azure blob store. The error is correct in the sense that the chunk does not exist. The survey is irregular and the segy is padded around the edges to make a nice regular grid. Fill-value is 0, both in zarr and the original segy. Hence I wonder if the missing chunks is a zarr-optimisation:

There is no need for all chunks to be present within an array store. If a chunk is not present then it is considered to be in an uninitialized state. An uninitialized chunk MUST be treated as if it was uniformly filled with the value of the “fill_value” field in the array metadata. If the “fill_value” field isnull then the contents of the chunk are undefined [1].

But I havn't investigated further. It might also be user-error. Any suggestions for the root cause or a solution for this?
Thanks,
[1] https://zarr.readthedocs.io/en/stable/spec/v2.html#chunks

The error originates in fsspec. It seams like something that should be handled gracefully by zarr
Traceback (most recent call last):
  File "/home/erlend/scripts/zarr/mdiotest.py", line 22, in <module>
    il_mask, il_headers, il_data = mdio[180,100:1300,:1000]
  File "/home/erlend/.local/lib/python3.9/site-packages/mdio/api/accessor.py", line 390, in __getitem__
    self._traces[item],
  File "/home/erlend/.local/lib/python3.9/site-packages/zarr/core.py", line 788, in __getitem__
    result = self.get_basic_selection(pure_selection, fields=fields)
  File "/home/erlend/.local/lib/python3.9/site-packages/zarr/core.py", line 914, in get_basic_selection
    return self._get_basic_selection_nd(selection=selection, out=out,
  File "/home/erlend/.local/lib/python3.9/site-packages/zarr/core.py", line 957, in _get_basic_selection_nd
    return self._get_selection(indexer=indexer, out=out, fields=fields)
  File "/home/erlend/.local/lib/python3.9/site-packages/zarr/core.py", line 1252, in _get_selection
    self._chunk_getitems(lchunk_coords, lchunk_selection, out, lout_selection,
  File "/home/erlend/.local/lib/python3.9/site-packages/zarr/core.py", line 1985, in _chunk_getitems
    cdatas = self.chunk_store.getitems(ckeys, on_error="omit")
  File "/home/erlend/.local/lib/python3.9/site-packages/zarr/storage.py", line 1361, in getitems
    results = self.map.getitems(keys_transformed, on_error="omit")
  File "/home/erlend/.local/lib/python3.9/site-packages/fsspec/mapping.py", line 101, in getitems
    return {
  File "/home/erlend/.local/lib/python3.9/site-packages/fsspec/mapping.py", line 104, in <dictcomp>
    if on_error == "return" or not isinstance(out[k2], BaseException)

Hi @ErlendHaa!
Thanks for reporting this.
Your interpretation of the missing chunk treatment is correct. When we ingest we don't write chunk keys to the store, and Zarr normally understands this and gracefully returns the fill value when a chunk key doesn't exist.
The behavior you're seeing is therefore not expected and we have never seen it before (maybe adlfs issue, we haven't used Azure much). Can you please share the following versions so we can diagnose further?
Python
MDIO
Zarr
Fsspec
Adlfs
Also, are these conda or pip installed?

Sure thing, my environment:
erlend:~$ python3.9 --version
Python 3.9.12

erlend:~$ python3.9 -m pip --version
pip 22.2.2 from /home/erlend/.local/lib/python3.9/site-packages/pip (python 3.9)

erlend:~$ python3.9 -c "import mdio; print(mdio.__version__)"
0.2.0

erlend:~$ python3.9 -c "import zarr; print(zarr.__version__)"
2.12.0

erlend:~$ python3.9 -c "import fsspec; print(fsspec.__version__)"
2022.8.2

erlend:~$ python3.9 -c "import adlfs; print(adlfs.__version__)"
2022.0

Too narrow it down a bit a I stored the same .mdio file to disk. Then it reads just fine.

Too narrow it down a bit a I stored the same .mdio file to disk. Then it reads just fine.

This is very helpful, thank you.
It is starting to feel like it is an adlfs and Zarr integration issue, I will drill down a little and report it if that is the case.

@ErlendHaa, I was able to reproduce your issue.
It worked fine on GCP and AWS but I will double check again in case an update broke something.
If it works on other clouds, we can bring this up with Zarr developers and they'll fix it upstream.
The demo file is also zero-padded; just like your file, it will have "empty" chunks that are not on the object store.
Steps:

Create Azure Storage Account defaultmdio. Default settings.
Create container mdio-test.
Grabbed the account key from Azure Portal.
Ran the MDIO Quickstart with the following syntax changes:

from mdio import segy_to_mdio

default_storage_options={'account_name': "defaultmdio", 'account_key': "..."}

segy_to_mdio(
    segy_path="filt_mig.sgy",
    mdio_path_or_buffer="az://mdio-test/filt-mig.mdio",
    index_bytes=(181, 185),
    index_names=("inline", "crossline"),
    storage_options=default_storage_options,
    chunksize=(16, 16, 1024),  # to get the empty chunks because file is small
)

Can't query the file because of KeyError

Great! How should we proceed? Do you want me to make an issue upstream to zarr ?

I tracked down the root to the adlfs.AzureBlobFileSystem._expand_path method [1]. More specifically to this continue [2] which strips out paths to none-exising blobs. This method is called by  adlfs.AzureBlobFileSystem.cat [3] which again is called by fsspec.FSmap.getitems [4]. The continue basically undermines the "omit" option in getitems and cat by striping the path list anyway. As a result getitem raises on KeyError when trying to index on of the striped out paths.
I guess we can close this issue now, as the bug is clearly unrelated to mdio. I'll make an upstream issue for it. Thanks for the help!
[1] https://github.com/fsspec/adlfs/blob/591485b9d77448cd6e791b49bda8942ef03507bf/adlfs/spec.py#L1672
[2] https://github.com/fsspec/adlfs/blob/591485b9d77448cd6e791b49bda8942ef03507bf/adlfs/spec.py#L1725
[3] https://github.com/fsspec/adlfs/blob/591485b9d77448cd6e791b49bda8942ef03507bf/adlfs/spec.py#L1610
[4] https://github.com/fsspec/filesystem_spec/blob/bb9989ce5bf0ed0c0a5f7d3540c3a59581d259ce/fsspec/mapping.py#L69

@ErlendHaa thanks a lot for all the debugging! You can go ahead and open an issue with Zarr. I'll go ahead run a couple more tests on other clouds and if it works ok there I'll close this issue.
Again, thanks a lot!

@ErlendHaa, I opened an issue with a minimal reproducible example.
I tested, and this does NOT happen on Google Cloud or S3.
Thanks for finding this!

Sorry, forgot to reply back! The bug lies with adlfs, not zarr. I submitted a patch for it, which addresses the root cause of the KeyError. Hopefully they'll accept it

Here is reference to the PR by @ErlendHaa
https://github.com/fsspec/adlfs/pull/350

@ErlendHaa, is this issue resolved with the latest adlfs released a couple weeks ago (2022.10.0)?
If it works as expected, we can close this issue. Thanks again!

Sadly, no! I'm not sure what happened there tbh. They seemed to approve my PR, but did not include it in their linted version of it

But as the cause definitely lies with adlfs I thing we can close this one

Sounds good. This is a big problem since many enterprise users use Azure. I will follow up with adlfs.
Opened an issue with adlfs to redo that PR https://github.com/fsspec/adlfs/issues/358


Add mid-circuit measurement before conditional operation in random_circuit

Fixes #9016
This PR add a mid-circuit measurement of all the qubits before a conditional operation in  random_circuit. Additionally, skips the possibility of conditional operations in the first layer, since that will implied a measure before any other operation.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.04%) to 84.556%

Files with Coverage Reduction
New Missed Lines
%

src/sabre_swap/layer.rs
2
98.95%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
62844

Relevant Lines:
74322

💛  - Coveralls

Closing in favor of https://github.com/Qiskit/qiskit-terra/pull/10401.


The document page has a dead link: https://spidernet-io.github.io/spiderpool/usage/multiple-subnet.md

open page https://spidernet-io.github.io/spiderpool/；will see the following：

Clicking on it will redirect you to an empty page.

This link is a meaningless dead link

THX！It will be fixed soon

Fixed, not showing up as NONE on the page


[Enable Continuous Monitoring] Add the capability to use a different Azure subscription for the App Insights resource

Hi,
When I was looking to enable Continuous Monitoring on my App Services, I noticed the Application Insights resource has to be in the same Azure subscription than the App Service resource. I have a scenario where those 2 resources (Application Insights and App Service) are in two separate Azure subscriptions. Would it be possible to add a "Application Insights Azure subscription" parameter to the task in order to support this use case?
Thank you

Thank you for your suggestion! We haven't heard this request from our other customers.
Please add your request or vote for this feature on the Visual Studio UserVoice site (https://visualstudio.uservoice.com), which is our main forum for product suggestions.
Continuous Monitoring option in Azure App Service manage task mainly does 2 things:

Add application insights extension to Azure web app
Add application insights instrumentation key in app settings of Azure web app.

As a workaround, you can perform these 2 steps using ARM or PowerShell task.

Closing this based on @imalokagrawal comments, since we will track this based on Visual Studio UserVoice response.


Lower MSRV to 1.57

What does this PR address?

Lowers the Minimum Supported Rust Version of Nixpacks from 1.58.1 to 1.57.
Before submitting:

[x] Make sure to follow GitHub's guide on creating PR.
[x] Did you read through contribution guidelines?
[x] Did your changes require updates to the documentation? Have you updated those accordingly?
[ ] Did you write tests to cover your changes? Did it pass locally when running cargo test?
[x] Have you run cargo fmt, cargo check and cargo clippy locally to ensure that CI passes?

What is the reasoning for lowering the MSRV?

Mainly compatibility with lower Rust versions.


Update TableMapReduceUtil.java

TableMapReduceUtil is an utility class. I can't get it why these handy methods convertStringToScan and convertScanToString are package protected?
We need to setup server side filters for mapreduce jobs so we must provide a scan object to TableInputFormat and we need those methods to put it into the job configuration. It just does not make sense.

Could you please open an issue on our project tracker describing the issue and attach a patch:
https://issues.apache.org/jira/browse/HBASE
for more information on submitting contributions to the project, please read through our new contributor section:
http://hbase.apache.org/book.html#getting.involved

This same change was made in HBASE-15223, and will be available in HBase 1.3.0+ and 2.0.0+


Make autopages.display_name available to title

Is there a way to output the display name along with the page x of x string? I tried swapping page.title with page.autopages.display_name but it loses the Page :num of :max bit.
page.tag = "Foo Bar"
{{ page.title }} ~> foo-bar - Page x of x
{{ page.autopages.display_name }} ~> Foo Bar

Thanks for creating a new ticket, I will look into this as soon as I can :)

@mmistakes  OK Michael so this was much simpler feature than I had expected so I just went ahead and added it.
The data is available under a new meta data structure for the pagination logic, the docs go into the details https://github.com/sverrirs/jekyll-paginate-v2/blob/master/README-GENERATOR.md#reading-pagination-meta-information


esp32 sdk v3 support

any plans to upgrade to v3 ?

yes, in progress but will be a while.

HomeSpan 2.0.0-rc.1 supporting v3 of the Arduino-ESP32 Board Manager has just been released.


Login and Register via API

Support login and round gister via the API

Functionality already exists in the User endpoint


Can I have this and another version of Python at the same time?

If I have the Python Coding Pack for VS Code installed, and I want to install Python for Visual Studio (which includes Python 3.7.8) will both Python versions interfere with each other? What about the system path? Can they coexist peacefully?

@zooba Is this possible?

Closing, Visual Studio does not add Python 3.7.8 to PATH.


Please add dehumidifier feature and add support!

Hi,
please add support for widetech 30L & 12L (nwt.derh.312en).
Thank you.

Will check it out and try to add that device! Will let you know when it is ready.

BTW, power on/off should already work now since the generic device will be used.

Oh, I thought It wouldn't work while it is no support. I'll try.

It should work because power on/off is usually the same on all devices :)

Support has been added in version 0.7.0. Please test it and let me know if everything works as expected.

I tested it today, but it cannot specify the device :( I tried to use "model" : "nwt-derh-312en", but it won't work.

You can just remove that field from the config.json, it will detect the model automatically.

No, I am saying it is not detecting device model automatically.

That what you specified in the model property is incorrect. Your device model is nwt.derh.312en as specified by you and that is what you need to put there.
Besides that your device will be detected automatically and you do not need to specify any model in the config.

Now I get device profile in homekit, but it does not properly working. This is my debug log.
[5/3/2021, 4:56:21 PM] [miot] Initializing devices
[5/3/2021, 4:56:21 PM] [miot] [제습기] Got device configuration, initializing device with name: 제습기
[5/3/2021, 4:56:21 PM] [miot] [제습기] Device model known: nwt.derh.312en! Creating device!
[5/3/2021, 4:56:21 PM] [miot] [제습기] Initializing device properties
[5/3/2021, 4:56:21 PM] [miot] [제습기] Missing name! Cannot create property!
[5/3/2021, 4:56:21 PM] [miot] [제습기] Initializing device actions
[5/3/2021, 4:56:21 PM] [miot] [제습기] Device successfully created! It is a Dehumidifier device!
[5/3/2021, 4:56:21 PM] [miot] [제습기] Initializing accessory!
[5/3/2021, 4:56:21 PM] [miot] [제습기] Accessory successfully initialized!

From the log which you specified all looks good.
You need to enable debug log in homebridge and check the output there. There will be more information which can tell where the issue is.

[5/3/2021, 5:07:36 PM] [miot] Initializing miot platform...
[5/3/2021, 5:07:36 PM] Loading 1 accessories...
[5/3/2021, 5:07:36 PM] [miot] Found cached accessory 제습기
[5/3/2021, 5:07:36 PM] [miot] Removing all cached accessories
[5/3/2021, 5:07:36 PM] [miot] Initializing devices
[5/3/2021, 5:07:36 PM] [miot] [제습기] Got device configuration, initializing device with name: 제습기
[5/3/2021, 5:07:36 PM] [miot] [제습기] Device info file does not exist yet!
[5/3/2021, 5:07:36 PM] [miot] [제습기] Device model known: nwt.derh.312en! Creating device!
[5/3/2021, 5:07:36 PM] [miot] [제습기] Creating miot device!
[5/3/2021, 5:07:36 PM] [miot] [제습기] Device Factory - Creating device instance by model: nwt.derh.312en!
[5/3/2021, 5:07:36 PM] [miot] [제습기] Initializing device properties
[5/3/2021, 5:07:36 PM] [miot] [제습기] Missing name! Cannot create property!
[5/3/2021, 5:07:36 PM] [miot] [제습기] Device properties: {
"power": {
"name": "power",
"siid": 2,
"piid": 1,
"format": "bool",
"access": [
"read",
"write",
"notify"
],
"unit": "none",
"valueRange": [],
"valueList": [],
"value": false
},
"mode": {
"name": "mode",
"siid": 2,
"piid": 3,
"format": "uint8",
"access": [
"read",
"write",
"notify"
],
"unit": "none",
"valueRange": [],
"valueList": [
{
"value": 1,
"description": "Tagget-humid"
},
{
"value": 2,
"description": "Dry-cloth"
}
],
"value": 0
},
"target_humidity": {
"name": "target_humidity",
"siid": 2,
"piid": 5,
"format": "uint8",
"access": [
"read",
"write",
"notify"
],
"unit": "none",
"valueRange": [],
"valueList": [
{
"value": 30,
"description": "Continue"
},
{
"value": 40,
"description": "Humidity 40"
},
{
"value": 50,
"description": "Humidity 50"
},
{
"value": 60,
"description": "Humidity 60"
},
{
"value": 70,
"description": "Humidity 70"
}
],
"value": 0
},
"fan_level": {
"name": "fan_level",
"siid": 2,
"piid": 7,
"format": "uint8",
"access": [
"read",
"write",
"notify"
],
"unit": "none",
"valueRange": [],
"valueList": [
{
"value": 0,
"description": "Auto"
},
{
"value": 1,
"description": "Level1"
}
],
"value": 0
},
"alarm": {
"name": "alarm",
"siid": 4,
"piid": 1,
"format": "bool",
"access": [
"read",
"write",
"notify"
],
"unit": "none",
"valueRange": [],
"valueList": [],
"value": false
},
"led": {
"name": "led",
"siid": 5,
"piid": 1,
"format": "bool",
"access": [
"read",
"write",
"notify"
],
"unit": "none",
"valueRange": [],
"valueList": [],
"value": false
},
"child_lock": {
"name": "child_lock",
"siid": 6,
"piid": 1,
"format": "bool",
"access": [
"read",
"write",
"notify"
],
"unit": "none",
"valueRange": [],
"valueList": [],
"value": false
},
"device_fault": {
"name": "device_fault",
"siid": 2,
"piid": 2,
"format": "uint8",
"access": [
"read",
"notify"
],
"unit": "none",
"valueRange": [],
"valueList": [
{
"value": 0,
"description": "No Faults"
}
],
"value": 0
},
"relative_humidity": {
"name": "relative_humidity",
"siid": 3,
"piid": 1,
"format": "uint8",
"access": [
"read",
"notify"
],
"unit": "percentage",
"valueRange": [
0,
100,
1
],
"valueList": [],
"value": 0
},
"temperature": {
"name": "temperature",
"siid": 3,
"piid": 7,
"format": "float",
"access": [
"read",
"notify"
],
"unit": "celsius",
"valueRange": [
-30,
100,
1
],
"valueList": [],
"value": 0
},
"coil_temp": {
"name": "coil_temp",
"siid": 7,
"piid": 1,
"format": "float",
"access": [
"read",
"notify"
],
"unit": "celsius",
"valueRange": [
-30,
200,
1
],
"valueList": [],
"value": 0
},
"compressor_status": {
"name": "compressor_status",
"siid": 7,
"piid": 2,
"format": "bool",
"access": [
"read",
"notify"
],
"unit": "none",
"valueRange": [],
"valueList": [],
"value": false
},
"water_tank_status": {
"name": "water_tank_status",
"siid": 7,
"piid": 3,
"format": "bool",
"access": [
"read",
"notify"
],
"unit": "none",
"valueRange": [],
"valueList": [],
"value": false
}
}
[5/3/2021, 5:07:36 PM] [miot] [제습기] Initializing device actions
[5/3/2021, 5:07:36 PM] [miot] [제습기] Device actions: {}
[5/3/2021, 5:07:36 PM] [miot] [제습기] Device successfully created! It is a Dehumidifier device!
[5/3/2021, 5:07:36 PM] [miot] [제습기] Initializing accessory!
[5/3/2021, 5:07:36 PM] [miot] [제습기] Accessory Factory - Creating Dehumidifier accessory for device 제습기!
[5/3/2021, 5:07:36 PM] [miot] [제습기] Accessory successfully initialized!
[5/3/2021, 5:07:38 PM] [miot] [제습기] Error: Could not connect to device, handshake timeout
[5/3/2021, 5:07:38 PM] [miot] [제습기] Could not connect to the device! Retrying in 30 seconds!
[5/3/2021, 5:08:10 PM] [miot] [제습기] Error: Could not connect to device, handshake timeout
[5/3/2021, 5:08:10 PM] [miot] [제습기] Could not connect to the device! Retrying in 30 seconds!
[5/3/2021, 5:08:42 PM] [miot] [제습기] Error: Could not connect to device, handshake timeout
[5/3/2021, 5:08:42 PM] [miot] [제습기] Could not connect to the device! Retrying in 30 seconds!

The plugin cannot connect to your device, make sure the ip and token are correct and that the device is reachable in your network.

I have another device in this homebridge container, and it connects well. There's no problem in my vlan setting and ip address is correct. But I cannot figure out token is right. Is there way I can check whether it is right?

If you are not sure about the token then you should try to get the token again. It can be that your token is wrong. Every time when you reset the device the token will change.


Disable suggestion list tooltip

When I press Enter key to select suggested word from dropdown list, this word is being shown in tooltip (see screenshot).
The problem is this tooltip is being shown for a significant time (until I click mouse on it etc) and it hides some of the previous text. It is very disturbing IMO.
Is it possible not to show this tooltip at all?

Agreed, these tooltips don't make sense.


Fixed HasRequiredNonBodyField method

Changes
Fixed HasRequiredNonBodyField method logic to be inline with the name and also checking for  vsPath, IsQuery values
Tests

[x] make test passing
[x] make fmt applied
~[ ] relevant integration tests applied~

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Files
Coverage Δ

openapi/code/package.go
58.20% <100.00%> (ø)

service/compute/spark_version.go
0.00% <ø> (ø)

openapi/code/entity.go
26.88% <0.00%> (ø)

:loudspeaker: Thoughts on this report? Let us know!.


Can't open or takes a long time to open the extension if I previously turned off the extension in the NFT tab ...

Describe the bug
Can't open or takes a long time to open the extension if I previously turned off the extension in the NFT tab ...
To Reproduce
Steps to reproduce the behavior:
Test with address: 5HMkyzwXxVtFa4VGid3DuDtuWxZcGqt57wq9WiZPP8YrSt6d

Try with 1 account have many NFTs
Open the NFT Tab and then turn off the extension
Go to another job about 60 - 90'
Go back and open the extension
Result: https://www.loom.com/share/8c7b81baf49e41e89f5098bf65ce0f13

Expected behavior
Open the extension quickly
Desktop (please complete the following information):

OS: OSX
Browser: All

@saltict fix with issue #80


Database Updates do not work

Look at branch bugs/UpdateExample
If you run ExampleRestApi.IntegrationTests/UriTests/UpdateCustomer you will see the problem.
Put a try-catch block around _db.Update(customer); in Examples\Example.Domain\Customers\Commands\UpdateCustomerCommand.cs:Line37.
Note the Unit test works OK.  See ExampleConsoleApp.UnitTests/UpdateCustomer.
The issue is:
The instance of entity type 'Customer' cannot be tracked because another instance with the same key value for {'Id'} is already being tracked. When attaching existing entities, ensure that only one entity instance with a given key value is attached. Consider using 'DbContextOptionsBuilder.EnableSensitiveDataLogging' to see the conflicting key values.

This is all good.  Need to do a Get instead of a Query to get the item.


Reducing dependencies, building with xtensor-python

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

To use Scikit-build, you need to map the PYTHON_x variables to Python_x in your CMakeLists. I know I've either done this or seen this done somewhere, but have forgotten where. Hopefully we will fix it soon, it's on the roadmap.

(I was going to do it here, but it would be better to try https://github.com/scikit-build/scikit-build/issues/554 .

Thanks @henryiii , I will try. The other horse I was betting on was to use FindPythonLibs through pybind11's CMake support and to rely on the FindNumPy you provided in scikit-build. But somehow I'm still doing something wrong I think, because the library is ultimately not installed https://github.com/tdegeus/QPot/pull/36/files

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@henryiii I think I'm nearly there... I'm able to use scikit-build locally : https://github.com/tdegeus/QPot/pull/36 (I will put some more comments there), however, I get hopeless failures here on conda-build. In particular, I get the error:
CMake-installed files must be within the project root.
       Project Root  : /tmp/pip-req-build-3s1kxo05/_skbuild/linux-x86_64-3.6/cmake-install
       Violating File: /home/conda/feedstock_root/build_artifacts/qpot-split_1629792833267/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_/./_QPot.cpython-36m-x86_64-linux-gnu.so

Do you know what to do about this ?
Note that in the example you linked, I found
        if(APPLE)
            set_target_properties(${PYPROJECT_NAME} PROPERTIES INSTALL_RPATH "@loader_path/${CMAKE_INSTALL_LIBDIR}")
        else()
            set_target_properties(${PYPROJECT_NAME} PROPERTIES INSTALL_RPATH "$ORIGIN/${CMAKE_INSTALL_LIBDIR}")
        endif()

I tried both with and without, with exactly the same error message

Found it @henryiii , see https://github.com/scikit-build/scikit-build/issues/588

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

Fixed by https://github.com/conda-forge/qpot-feedstock/pull/33


chore(lib): Remove old validation check preventing loop=True with auto_next=True

Description
#299 added support for stopping looping slides smoothly, at which point specifying both loop=True and auto_next=True on a next_slide starts making sense. There is an old validation check in the code referencing #299 that was never removed.
This functionality (on the next press, waiting for the current loop to end and then immediately proceeding to the next slide) seems to work without issues on the QT presenter. The reveal.js presenter doesn't like it as much, but it's also not supported by --next-terminates-loop.
Check List (Check all the applicable boxes)

[x] I understand that my contributions needs to pass the checks.
[x] If I created new functions / methods, I documented them and add type hints.
[x] If I modified already existing code, I updated the documentation accordingly.
[x] The title of my pull request is a short description of the requested changes.

Looks great, thanks!

Would you mind adding an entry to the CHANGELOG file?


A very simple fix to avoid builder push collisions

What this PR does / why we need it:
It is easy to override tags with the current builder bump flow. Since
quay.io does not keep images based on digest, if they have no tag,
applying a simple workaround to avoid that people accidentaly override
each others builder images.
It actually just happened right now. I restored the builder image from my local machine, but we need to prevent that.
This is really just a very simple workaround. On the long run I expect the builder image to be replaced with the kubevirtci/bootstrap image with bazel being installed as the only requirement.
The downside of risking to get different images from the same tag is tried to be minimized by creating the tags in a pretty unique way.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:
NONE

/cc @enp0s3
/cc @fgimenez

/approve

/lgtm

/retest


Find a better way to exclude unused coins from cap table

Right now excludes the one with the highest value.  Doesn't work after 1M+ coins are awarded from the project/community.

dco->coluAssetAddress


why predict result is different in same model and environment?

Thank for your excellent work. I use PICK to train invoices, but why the predict result is different in same model and environment? Looking forward to your reply.

I got the answer. The test process need add random seed. @wenwenyu

@Helloworld0214 Where do you set the random seed?

@Helloworld0214 Where do you set the random seed?

I set it before in  test model  loaded.

I have the same problem, I trained with GPU on an EC2 instance, now I am running it on CPU and the test results change, Can I be more explicit in the use of the seed? This is during the test? Even inserting the seed the result is different

I have the same problem, I trained with GPU on an EC2 instance, now I am running it on CPU and the test results change, Can I be more explicit in the use of the seed? This is during the test? Even inserting the seed the result is different

yes, I modify code in test file.
SEED = 2021
def set_seed():
    torch.manual_seed(SEED)
    torch.cuda.manual_seed(SEED)
    torch.backends.cudnn.benchmark = False
    torch.backends.cudnn.deterministic = True
    np.random.seed(SEED)
    random.seed(SEED)

and model_eval function in parse_config
def model_eval(self):     module_args = self._config['model_arch']['args']     # print(dict(module_args))     for Key, Value in module_args.items():         if isinstance(Value, collections.OrderedDict):             for key, value in Value.items():                 if key == 'dropout':                     Value[key] = 0.0                 elif isinstance(value, collections.OrderedDict):                     for k, v in value.items():                         if k == 'dropout':                             value[k] = 0.0

config refers to the class or the instance within the ConfigParser class?
Thanks for your quick response

Hi, can you post the set_seed() function? @Helloworld0214


fix: ensure checkpoint storing isnt racey

Mainly there are two problems:

You still access shared memory (checkpoint and lastID) without locking :aditi_grimace:
You ignore past results if they come in different order

E.g. 1 3 2

So after 3 is set for checkpoint, the 2 will be ignored
If 2 failed on 100-120, but 3 succeed on 120-150, the checkpoint will be 150 and we will never comeback to reDas the 100-120 ones
So it makes sense to keep checkpoint for the lowest broken one?

i'm gonna squash merge this into daser


Antimalware Service Executable high CPU usage when command palette try to load tasks

VSCode Version:
Version: 1.29.0 (user setup)
Commit: 5f24c93878bd4bc645a4a17c620e2487b11005f9
Date: 2018-11-12T07:47:15.448Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64

OS Version: Windows 10 Professional 1809 (Build 17763.55)

Steps to Reproduce:

Use shortcut keys to run svn commit/update tasks.
Vscode gets slow, Windows task manager showing high CPU usage from "Antimalware Service Executable". After 10 or 20 secends, integrated terminal is expanded and the tasks finally get started and done.

It's interesting that the "ASE" does not react when do the commit/update by using TortoiseSVN client or by typing commands in the terminal.
This problem is since the 1.29.0 update.

Does this issue occur when all extensions are disabled?: Yes.
Update:
So it seems nothing to do with shortcut keys 👇

@Monkey-D-Pixel is this happening every time. We see something comparable with gulp but only when starting the task the first time.

@Monkey-D-Pixel is this happening every time. We see something comparable with gulp but only when starting the task the first time.

yes, every time

might be a specific case of #63055, not just svn tasks

Adding @alexr00 since she is on #63055. How does the SVN task look like? Can you provide use with a GitHub repository we can clone that demos this?

One try. If you add the following settings
	"npm.autoDetect": "off",
	"gulp.autoDetect": "off",
	"grunt.autoDetect": "off",
	"jake.autoDetect": "off"

to the workspace settings does it still reproduce ?

@dbaeumer just user defined configurations in task.json, like this:
        {             "taskName": "svn update",             "type": "shell",             "command": "svn update ${fileDirname} ",             "group": {                 "kind": "svn",                 "isDefault": true             }         }
It's still reproducing after adding those settings.
And just found more about this:
If I ctrl+p, select "Run task" in the command palette, MOSTLY "ASE" will also spike, while there is a loading indicator at the bottom of the palette until the tasks are loaded. Then I choose one, the task is invoked immediately. SOMETIMES, normally after several times of trying the same steps, the tasks are loaded very quickly, with "ASE" not spiking.
So I think there is something wrong during loading tasks.

I can repro. It does look as though something is very slow during loading tasks.

I think the sequence is: (slow down and DOES NOT work) -> (slow down and work) -> (slow down and DOES NOT work) -> (slow down and work) -> ...

I forgot one task provider. Can you disable that one as well:
"typescript.tsc.autoDetect": "off"

@alexr00 Yes, slows down both times.
@dbaeumer Finally, NO MORE slow down with this line added. But why?

@Monkey-D-Pixel TypeScript provides task to build typescript project automatically and this seems to gotten slower in 1.29.

@mjbvz, any ideas on why the typescript task provider has gotten slower in 1.29?

Does this involve searching? Does it do a findFiles('**/tsconfig.json') or something?

I forgot one task provider. Can you disable that one as well:
"typescript.tsc.autoDetect": "off"

Thx, it solved my problem #63026

I believe this is the same issue as https://github.com/Microsoft/vscode/issues/63055.

Yes, same root cause as #63070. The tsc task detector searches the workspace for all tsconfig.json files.

@roblourens for FYI.


Check for a valid action/model combo

Per slack chat, added a check for no model being found.

Added in one commit for the latest pre-commit template file.

Updated both template per conversation with Bracey


Independent reserve implement getDynamicFee

add account getDynamicFee method for independent reserve

https://github.com/knowm/XChange/pull/3970


PDFs are detected as CVE-2018-4993(!g1)

Maybe adding additional triggers? Like the Eicar string or similar

issue is sloved

Eicar test PDF, file has been added.
Commit: https://github.com/jonaslejon/malicious-pdf/commit/bd12b2c257f7a8e60ba9605022c470329d151360


Upgraded Ionic 5 to Ionic 6(#1yky46z)

Updated PR: https://github.com/hotwax/bopis/pull/61. Closing


fix(buttons): WIP - disable ripple on buttons everywhere, add focus style

Resolves #328
Impact: minor
Type: style
Issue
Our official style is to not have any Material UI button ripples anywhere.
Solution
Disabled the ripple on:

Navigation item button
Profile button
Profile: Sign in button
Profile: Create account button
Profile: Sign out button
Cart button

PDP

Add to cart
+ button
- button

Testing

Test nav, both signed in and signed out
Test PDP

@nnnnat when testing could you verify that these buttons have focus rings when tabbing through the app. If they do not, then that should also be addressed as an accessibility concern.

The best way to accomplish this is to create a wrapper component, for example, create a wrapper Button component in the starter kit and pass the disable prop to the wrapped component. See: https://material-ui.com/getting-started/faq/#how-can-i-disable-the-ripple-effect-on-the-whole-app-

Confirmed - adding disableRipple makes the button focus invisible. Thanks for the catch @mikemurray 👍 I'm going to update this ticket to include 1) adding a wrapper to disableRipple and also 2) adding a focus style to that wrapper.

Closing for now

Disconnecting this so that it no longer appears in progress.


Rewrite PodSecurityPolicy migration guide

Add a lot more detail to the PSP migration guide. Notable changes include:

Detailed step-by-step guide for how to migrate PSP resources
Additional detail around permissions & policies for namespaces
Detailed table of PSP fields, with mutating/validating type and PSA equivalents

Fixes https://github.com/kubernetes/website/issues/31367
As a side note, if anyone is interested in building some tooling to assist with the migration, the most manual steps are:

Verification of mutating pods (step 2c)
PSP simplification steps, in general
RBAC review tooling (who can relabel namespaces, which PSPs are bound to a namespace, etc.)

/kind documentation
/sig auth security
/assign @liggitt @tabbysable @sftim @photoni-137

Thanks for all the feedback. I've addressed most comments, and responded on the ones I didn't.

/lgtm

Broke out PSP fields table into separate page
Added "no-word-break" class on tables
Added unnumbered section anchors
@sftim PTAL

/approve

/label tide/merge-method-squash

/hold cancel
Addressed last comment & squashed commits.

Reapply lgtm from previous reviews.
/lgtm


Environment variables warning

Hi,
I was able to complete the steps listed in the README. When I start wekan, I am getting the below warnings. Can I ignore them as they are set in the Dockerfile?

jean:src$docker-compose start
WARNING: The NODE_VERSION variable is not set. Defaulting to a blank string.
WARNING: The METEOR_RELEASE variable is not set. Defaulting to a blank string.
WARNING: The NPM_VERSION variable is not set. Defaulting to a blank string.
WARNING: The ARCHITECTURE variable is not set. Defaulting to a blank string.
WARNING: The SRC_PATH variable is not set. Defaulting to a blank string.
WARNING: The METEOR_EDGE variable is not set. Defaulting to a blank string.
WARNING: The USE_EDGE variable is not set. Defaulting to a blank string.
Starting wekandb ... done
Starting wekan ... done

Thanks!
Jean

@jeanabraham
wekan-dev has not been updated for some time, it most likely uses old version of Wekan. You can look at current working Wekan's Dockerfile and add wekan-dev specific additions to it. If you get wekan-dev working, please submit pull request. Thanks!
https://github.com/wekan/wekan/blob/devel/Dockerfile

Hi @xet7, I was able to have a local version running inspite of the warnings, without having to make any changes to what I cloned from wekan-dev.

This should be fixed


Hitting CTRL+C while in Inquirer prompt breaks everything

The output looks like this:
(^C again to quit)
function (str) {
  if (str === undefined) {
    return this._delimiter;
  }
  this._delimiter = String(str).trim() + ' ';
  if (this.isLocal()) {
    this.parent.ui.refresh();
  } else {
    this.parent._send('vantage-delimiter-downstream', 'downstream', {value: str, sessionId: this.id});
  }
  return this;
}
_

You can still type but nothing happens. Only way to recover is hitting CTRL+C again.

Yikes! Okay will check out.

Hi Team,
Is above issue solved?

Issue is still present.

Hey Scott - sorry I haven't been very active recently. A lot of things are changing in life right now, so I haven't had too much time for OSS. Hope to get back fairly soon and close all these issues.
Otherwise, all your help's been very appreciated. I wouldn't mind adding you to the Vorpal team, if you're down with that.

Don't worry about it; that's how open source is sometimes. You contribute
when you can, and mostly when you need it yourself. ;)
I would appreciate the abilities to accept pull requests and deploy code to
npm if possible.
-Scott
On Monday, December 14, 2015, dc<EMAIL_ADDRESS>wrote:

Hey Scott - sorry I haven't been very active recently. A lot of things are
changing in life right now, so I haven't had too much time for OSS. Hope to
get back fairly soon and close all these issues.
Otherwise, all your help's been very appreciated. I wouldn't mind adding
you to the Vorpal team, if you're down with that.
—
Reply to this email directly or view it on GitHub
https://github.com/dthree/vorpal/issues/42#issuecomment-164513070.

Okay Scott, giving you access now.
Feel free to make any patches you need, obviously add tests as you go. Just check with me before committing anything that alters the API, or any breaking changes.
Thanks for all your help!

Okay this should be good now. Can you please try it? v1.5.2

No luck.
C17PR768G8WP:cli shovestadt$ cli
cli:
function (str) {
  if (str === undefined) {
    return this._delimiter;
  }
  this._delimiter = String(str).trim() + ' ';
  if (this.isLocal()) {
    this.parent.ui.refresh();
  } else {
    this.parent._send('vantage-delimiter-downstream', 'downstream', {value: str, sessionId: this.id});
  }
  return this;
}
function (str) {
  if (str === undefined) {
    return this._delimiter;
  }
  this._delimiter = String(str).trim() + ' ';
  if (this.isLocal()) {
    this.parent.ui.refresh();
  } else {
    this.parent._send('vantage-delimiter-downstream', 'downstream', {value: str, sessionId: this.id});
  }
  return this;
Username: test
Password:

^C/usr/local/lib/node_modules/cli/node_modules/rx-lite/rx.lite.js:75
    throw e;
    ^

TypeError: Cannot read property 'removeListener' of null
    at [object Object].UI.close (/usr/local/lib/node_modules/cli/node_modules/inquirer/lib/ui/baseUI.js:45:10)
    at [object Object].PromptUI.onCompletion (/usr/local/lib/node_modules/cli/node_modules/inquirer/lib/ui/prompt.js:54:8)
    at AnonymousObserver.Rx.AnonymousObserver.AnonymousObserver.completed (/usr/local/lib/node_modules/cli/node_modules/rx-lite/rx.lite.js:1550:12)
    at AnonymousObserver.Rx.internals.AbstractObserver.AbstractObserver.onCompleted (/usr/local/lib/node_modules/cli/node_modules/rx-lite/rx.lite.js:1489:14)
    at Subject.Rx.Subject.addProperties.onCompleted (/usr/local/lib/node_modules/cli/node_modules/rx-lite/rx.lite.js:5871:19)
    at Subject.tryCatcher (/usr/local/lib/node_modules/cli/node_modules/rx-lite/rx.lite.js:63:31)
    at AutoDetachObserverPrototype.completed (/usr/local/lib/node_modules/cli/node_modules/rx-lite/rx.lite.js:5796:56)
    at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onCompleted (/usr/local/lib/node_modules/cli/node_modules/rx-lite/rx.lite.js:1489:14)
    at AutoDetachObserver.tryCatcher (/usr/local/lib/node_modules/cli/node_modules/rx-lite/rx.lite.js:63:31)
    at AutoDetachObserverPrototype.completed (/usr/local/lib/node_modules/cli/node_modules/rx-lite/rx.lite.js:5796:56)
    at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onCompleted (/usr/local/lib/node_modules/cli/node_modules/rx-lite/rx.lite.js:1489:14)
    at InnerObserver.onCompleted (/usr/local/lib/node_modules/cli/node_modules/rx-lite/rx.lite.js:2966:65)
    at InnerObserver.tryCatcher (/usr/local/lib/node_modules/cli/node_modules/rx-lite/rx.lite.js:63:31)
    at AutoDetachObserverPrototype.completed (/usr/local/lib/node_modules/cli/node_modules/rx-lite/rx.lite.js:5796:56)
    at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onCompleted (/usr/local/lib/node_modules/cli/node_modules/rx-lite/rx.lite.js:1489:14)
    at AutoDetachObserver.tryCatcher (/usr/local/lib/node_modules/cli/node_modules/rx-lite/rx.lite.js:63:31)

Can you show me the code with the inquirer prompt?

// Login command only available in CLI, requires user input.
vorpal
  .command('login [userKey] [userSecret]')
  .description('Set user key and user secret key.')
  .action(function(args, callback) {
    this.prompt([
      {
        type: 'input',
        name: 'userKey',
        message: 'User key: ',
        validate: (input) => {
          return input.length > 10;
        }
      },
      {
        type: 'input',
        name: 'userSecret',
        message: 'User secret key: ',
        validate: (input) => {
          return input.length > 20;
        }
      }
    ], (answers) => {
      self.userKey = self.commands.userKey = answers.userKey;
      self.userSecret = self.commands.userSecret = answers.userSecret;
      callback();
    });
  });
}

Thanks. Checking it out.

Oh - haha - it only breaks on multi-inputs. Looks like the Inquirer cancellation doesn't handle an array of inputs.

Ugh. Cancelling inquirer prompts is literally the messiest part of my code, because Inquirer doesn't support command cancellation, so I have to hack it. This is going to take longer to fix.

Running into this as well... where's the like button? :+1:

Got it. This one's... gnarly. Will try to work on it some more soon.

Any chance this issue can be resolved?
I think I'm running into something similar, where I now need to press CTRL-C twice before it exits my script when prompt is running.

This problem still exists and breaks the REPL

I also encountered this issue, but I think it's possible to workaround this issue by implementing a helper function that calls each question individually using prompt.
async function startPrompt (questions, cmdInstance) {
  const answers = {}
  for (const question of questions) {
    const singleAnswer = await cmdInstance.prompt(question)
    if (singleAnswer[question.name]) {
      _.extend(answers, singleAnswer)
    } else {
      throw new Error('cancelled prompt')
    }
  }
  return answers
}


Task: Documentation

Story: #2694
Description
Prepare documentation outlining the defined roles, their associated permissions, and the rationale behind each role's definition.
Include guidelines for future modifications or additions to roles.


Support ThermoPro TempSpike (TP96x)

This is still a WIP, need to add support for multi-probe devices like TP962R.
Looking for feedback.
Thanks in advance!

@bdraco  I think this may be close to complete, would you mind providing some feedback?


Feature request: Equivalent Maven plugin

Kover looks very exciting!  Thank you for the Gradle plugin.
Request: an equivalent Maven plugin.  Projects I work on are around 50/50 Gradle/Maven for builds (these are for backend, not mobile).

+1
working with server side banking project.
Look forward to the maven equivalent.

Hi,
at the moment, the development of the Maven plugin is not included in the short-term plans.
We will be happy to listen to your use cases, it will help to develop an API for the Maven plugin.

+1
working with server side apm project.
Look forward to the maven equivalent

+1
Building maven based kotlin backend (REST API) application. I would like maven to create reports with kover during my CI.

+1

+1

+1 Very much interested in Kover Maven Plugin. JaCoCo still does not fully serve the purpose. For example JaCoCo does not exclude getters and setters from the code coverage of data classes.

+1
Server-side enterprise development

+1
Server-side enterprise development

+1
Server Side enterprise dev

A big reason I'm looking at Kover rather than JaCoCo is inline function coverage.  See https://github.com/jacoco/jacoco/issues/654.
@shanshin As to "use cases", I assume you mean why Maven?  I don't want to have a religious debate of Gradle vs Maven ;-) I'm a consultant, and make recommendations to client teams and organizations on tech choices. For me, I often (but not always) prefer Maven, especially for certain types of client, because of stability and reproducibility of builds.  And I encourage them to move to Kotlin from Java when feasible, and coach developer teams in that transition.

+1

+1

+1

+1

1!

+1

+1

+1
from the issue https://github.com/jacoco/jacoco/issues/654

Our long-term plan is the following: polish and stabilize Gradle API (so it's complete, future-proof and supports both Android and merged reports in a concise manner). As soon as it's done, we'll release it and start transferring this API shape into Maven plugin (which, alas, will be much less configurable and probably won't support merged reports as well).
No specific timeframes for this tho, it's just an outline of our overall direction

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

Implemented in 0.8.3


Are calls to override wanted?

Reading the docs (master&next) of the afterfunction:

If three parameters are given to the callback, the first will be the error object, the second will be the top level context unless you have specified both server and override, in that case the context will be what the override returns, and the third the done callback.

My understanding is that the .after interfaces with one or two params don't call the override
Instead override is always called:
'use strict'

const server = { count: 0 }
const avvio = require('.')(server)

avvio.override = function (s, fn, opts) {
  console.log('override', s.count)
  const res = Object.create(s)
  res.count = res.count + 1
  return res
}

avvio
  .use(function hello (server, opts, done) {
    console.log('hello server', server.count)
    done()
  })
  .after(function (err, done) {
    if (err) throw err
    done()
  })
  .after(function (err, context, done) {
    if (err) throw err
    console.log('context', context.count)
    done()
  })

avvio.ready(() => { console.log('ready') })

Show:
override 0
hello server 1
override 0
override 0
context 0
ready
start

is this wanted/needed?
Does not this behaviour add unuseful overhead?
With this (fast) code on plugin.js all our tests are green and also on fastify.next all is green:
if (!this.isAfter || func.length === 3 || (func.length === 2 && func.then)) {
  this.server = this.parent.override(server, func, this.opts)
}

Doubt born by https://github.com/fastify/fastify/pull/2166

Fire a PR against next, I don’t think that’s ok.


Add Core Validation Test Script (v.9.1.3 LTS) for Data Comparison Tool / DDE Module

My first PR on this project, so apologies for the inevitable mistakes!

Well, I've merged into the master branch by mistake and made the PR from there... Let me know what you'd like done about it (e.g., close this PR and do another) 😬 @aldefouw

Well, I've merged into the master branch by mistake and made the PR from there... Let me know what you'd like done about it (e.g., close this PR and do another) 😬 @aldefouw

Closing this PR. Going to start a new one from proper branch.

Closing this PR. Going to start a new one from proper branch.


Problems encountered in using proxy mode

Which version are you using?
v0.15.2
Question
When I use proxy mode as follows:

When the first client accesses rtsp://<IP_ADDRESS> : 8554 / proxied1, one function is normal, but at this time, if two clients are opened to access at the same time rtsp://<IP_ADDRESS> : 8554 / proxied1 cannot be opened and the following error is reported:

Thank you for your reply. When I set the value of sourceondemand to no, multiple clients can access it rtsp://<IP_ADDRESS>:8554 proxied1 or rtsp://<IP_ADDRESS>:8554 proxied2 is normal and there is no error log. But this is not what I want, because I have a lot of streams, and I don't want them to work all the time, which is a waste of bandwidth.

Hello, from the log you provided, it seems that the proxied1 source is not working properly, and therefore clients cannot read from it. In my opinion you have to find out why the source is not working, by setting sourceOnDemand to no and reviewing the logs.
The number of clients have no influence on the fact that the source works or not, since clients don't interact with the camera, but only with the server.

Thank you for your reply. When I set the value of sourceondemand to no, multiple clients can access it rtsp://<IP_ADDRESS>:8554 proxied1 or rtsp://<IP_ADDRESS>:8554 proxied2 is normal and there is no error log. But this is not what I want, because I have a lot of streams, and I don't want them to work all the time, which is a waste of bandwidth.

Just noticed that this is the same issue of #334 - a fix is available and has been added to v0.15.4

I’m truly grateful for your help.


Configure CI to build the "main" branch of langchain4j

Make CI green - while we are waiting for a release
Adapt code to handle the langchain4j API change
Drop CI for java 11 (the extension use 17)

Green CI, awesome!


#BUG : First view controller not displaying properly for the first time.

I've added 3 controllers. When the first one presented for the first time, view didn't loaded properly. Some portion at the bottom was missing. After moving to second page, it all work out properly. After that coming back to the first also worked properly. Please provide the solution.

In the setUpUserInterface function, change this line:

"controllerScrollView.frame = CGRect(x: 0.0, y: configuration.menuHeight, width: self.view.frame.width, height: self.view.frame.height - configuration.menuHeight)"
to :
"controllerScrollView.frame = CGRect(x: 0.0, y: configuration.menuHeight, width: self.view.frame.width, height: self.view.frame.height)"

I have with the same problem when I add this into children view of self.view.
When I add to self.view is no problem!.

@samvirani Thanks for the solution 👍 .

@samvirani Thanks for the solution. Why does this work though. Shouldn't removing -configuration.menuHeight further increase the frame size and shift it further down below?

@samvirani Thanks for the solution👍. I have the same problem.

@samvirani thanks for the solution.

thanks for the solution, does this mean we need to fork our own and modify the pod?

this solution make new BUG.
My childVC only have a CollectionView.
First view controller not displaying properly for the first time.
CollectionView can't scroll to the end of bottom.
when I change this line:
"controllerScrollView.frame = CGRect(x: 0.0, y: configuration.menuHeight, width: self.view.frame.width, height: self.view.frame.height)"
to :
"controllerScrollView.frame = CGRect(x: 0.0, y: configuration.menuHeight, width: self.view.frame.width, height: self.view.frame.height - configuration.menuHeight)"
It work

Thanks.....samvirani....you saved my day


merge from konsum-frontend-svelte

package.json

chore(deps): add ^10.7.5 remove ^10.7.3 (devDependencies.npm-pkgbuild)

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

npm package (@latest dist-tag)
v1.31.18
GitHub release

Your semantic-release bot :package::rocket:


HU language typo

Description
I have found some mistype and a few missing item in hungarian translation. Corrected.
Yout tests run with v14, v16 and v17 and works well. npm run setup shows engine error, because package.json. Corrected.
Type of change
Please delete options that are not relevant.

User Interface
Translation update
package.json

Checklist

[x] My code follows the style guidelines of this project
[ ] I ran ESLint and other linters for modified files
[x] I have performed a self-review of my own code and test it
[ ] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[ ] My code needed automated testing. I have added them (this is optional task)

"Auto Test / auto-test (macos-latest, 14.x) (pull_request)" test has only timeout problem.

@BCsabaEngine Please run npm run update-language-files and translate the latest keys added in https://github.com/louislam/uptime-kuma/pull/902

Please ignore the test fail for now.

@BCsabaEngine Please run npm run update-language-files and translate the latest keys added in #902

I have understand the method and completed. New PR created, waiting for checks. Thx!

New PR: https://github.com/louislam/uptime-kuma/pull/996


tarballs not present after conda install

in init.sh script the tarball copy lines (like "cp -v $env_pkgs_dir/astropy-*.tar.bz2 .") fail because the tarballs are not present after doing a conda install.

This is weird, because I just tested init.sh and it ran just fine and created the artifacts directory with the tar.bz2's in it.  We need to look at why we get different outcomes.


⚠ Bofrost.lu has degraded performance

In 69818fb, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2044 ms

Resolved: Bofrost.lu performance has improved in 986b267 after 8 minutes.


Prevent running this plugin if Spyder is using PyQt4

This is an important thing to do and something I forgot to mention before. This is because PyQt4 uses a websockets version that is too old for modern standards.
The plugin should deactivate itself and show a warning message in that case.

How do I indicate Spyder to discard the plugin if PyQt version is lower than 5?

I don't think it's necessary to do it in Spyder, I think it can be done here.
You could not declare PLUGIN_CLASS in spyder_terminal/__init__.py if running in PyQt4. You can use the PYQT5 constant of qtpy for that.


memory leak: the stored scheduling results should be deleted after Pod get scheduled

/kind bug
/priority next-release
/priority important-longterm
/assign
We need to clear the data in resultstore after Pod's scheduled.
https://github.com/kubernetes-sigs/kube-scheduler-simulator/blob/4cfcea0193d23d048f1fc2a0e1cd60dfca05e4ba/simulator/scheduler/plugin/resultstore/store.go#L129

/close
Nah, it's already implemented.


patch to handle debugfs not mounted

I have tried to add a patch using shelljs to handle the case when debugfs is not mounted(Issue #61 [still exists]).The issue is solved after adding the patch and I also did note the run-time before and after the change(for this example script: http://beagleboard.org/Support/BoneScript/getPinMode/), the results are :
before making the change :
real	0m8.573s
user	0m7.748s
sys	0m0.564s
after making the change(when debugfs already mounted) :
real	0m8.783s
user	0m8.068s
sys	0m0.516s
after making the change(when debugfs not mounted) :
real	0m10.074s
user	0m9.192s
sys	0m0.680s

Coverage remained the same at 35.912% when pulling e03ad17c6f485b5de3db2ad400600896c45c1090 on vaishnav98:master into 2148f35a4217f036eaf5faed43310a7fc2397fcb on jadonk:master.

I just found that using shelljs was actually a slower alternative than doing .exec() , did not know about it earlier will fix it while submitting another patch.

https://github.com/beagleboard/bonescript/issues/16