Add usage of CursorHoldI instead of CursorMovedI

This PR features:

Reduces amount of request that are being sent to an API.
A time after typing a symbol could be controlled and an API would not be bloated with outdated requests.

When I was using my own server I noticed that there are a lot of requests being made when I am still writing a code and not waiting for a suggestion to appear. I sincerely don't think that we need to generate a suggestion as soon as the user hits any symbol. And a request is still happening, server process it.
Vim basically waits certain amount of time until no new keys are pressed by the user and then fires up CursorHoldI event.
This autocmd is well documented and further info could be found here
And time in ms that could be used to control the behaviour is updatetime.
By default it is 4000ms.
set updatetime=500

If an idea is supported - would also change README.md to setting of updatetime

Hi @nenkoru, thanks for taking the time to submit your PRs !
I'm currently out of office, I'll take a look when I get back in a few days.

Have you tried increasing the value of opts.debounce_ms? I'm a pretty fast typer so 80ms works for me.
Could you provide some data (if possible) with the number of calls that were emitted with the corresponding text that was typed?

I'll close this for now as I consider it fixed. Feel free to open an issue/PR if there is anything else you want to add that was discussed in this PR.


Adds mention badges to channel list items

Summary
Introduces mention badges to the channel list item;
Ticket Link
Fixes https://mattermost.atlassian.net/browse/MM-42160
Checklist

[X] Added or updated unit tests (required for all new features)
[X] Has UI changes
[ ] Includes text changes and localization file updates
[ ] Have tested against the 5 core themes to ensure consistency between them.

Device Information
This PR was tested on:
Pixel 4A SIM API29
Screenshots

Release Note

@shazm just by looking at the screenshots the badges do not seem align with the channel display name

Deferring my review until the old badge component is used (or decided to use the new one).


Multiple Select selected items wrong rendering

Multiple Select should display selected items comma separated, but it only works if MenuItem's children is string.

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Multiple Select should render any Component which MenuItem accept
Current Behavior

non string values are rendered as [Object object]
Steps to Reproduce (for bugs)

https://codesandbox.io/s/721qw8l1q6
Context

I think that it's caused by join call which stringify components instead of proper react rendering https://github.com/mui-org/material-ui/blob/73f0a3fe10538eb92a7982577e06126d0f457713/src/Select/SelectInput.js#L261
Your Environment

Tech
Version

Material-UI
1.0.0-beta.34

React
16.2.0

browser
Chrome 64

etc

@nest-aka-swan This is the expected behavior. Use the renderValue() property or remove the <span>.


Don't pass unused environment variable

Test Plan
yarn flow

how did you find it??

I'm looking into how we might do a strict mode, so I was trying to figure out where the globals get injected. I was following that environment variable and got super confused. 😁

Codecov Report

Merging #6319 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6319   +/-   ##
=======================================
  Coverage   63.64%   63.64%
=======================================
  Files         227      227
  Lines        8638     8638
  Branches        3        4    +1
=======================================
  Hits         5498     5498
  Misses       3139     3139
  Partials        1        1

Impacted Files
Coverage Δ

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

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

Continue to review full report at Codecov.

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

This is ready if someone wants to merge it.


[Add] Mobbin

URL
https://mobbin.com/
Description of the above provided site
Mobbin is a hand-picked collection of latest design patterns from mobile apps that reflect the best in design.
Category
Frontend
Sub Category
design inspiration

Thank you, would you like to work on this?

can I work on it

can I work on it

Sure


[MINOR] Fix warnings reported by lgtm

What changes were proposed in this pull request?
Fix warnings reported by lgtm.
Why are the changes needed?
https://lgtm.com/projects/g/apache/incubator-uniffle/?mode=list
Does this PR introduce any user-facing change?
No.
How was this patch tested?
By CI.

LGTM

Thanks @frankliee and @jerqi for the review.


wemeet: init at <IP_ADDRESS>0

This commit adds wemeet to nixpkgs, a popular proprietary video conferencing software.
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 336638 run on x86_64-linux 1

1 package built:

wemeet

Thanks for you contribution!
wemeet is indeed a popular program.  I find that many people have packaged it in their own repos.  It would be good to have wemeet in Nixpkgs.
@gjz010 https://github.com/gjz010/nix-channel/blob/ef30e6e20984149f959c7d91a081605f2c03304f/pkgs/wemeetapp/default.nix
@novel2430 https://github.com/novel2430/my-nixos/blob/6bb7c1a5bf9747c73b4dad81f51070d7b2f0ceda/custom-pkgs/wemeet-bin-bwrap/default.nix
@linyinfeng https://github.com/linyinfeng/nur-packages/blob/e6bb50bd6fafdfe1a80351e2a57d857be27006ce/pkgs/wemeet/default.nix
Would you like to review this PR (and become a maintainer of wemeet)?

It crashes on my machine with SIGSEGV or SIGABRT.
Wayland:
$ NIXPKGS_ALLOW_UNFREE=1 nix build github:nixos/nixpkgs/pull/336638/head#wemeet --impure --refresh
$ ./result/opt/wemeet/bin/wemeetapp
wemeet:WemeetSatrt
xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb
xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb
Fontconfig error: "/etc/fonts/fonts.conf", line 5: not well-formed (invalid token)
Fontconfig error: Cannot load config file from /etc/fonts/fonts.conf
Error in received packet: No such file or directory
Error in received packet: Success
2024-09-06 05:05:19|140127257873088|xnn.XNNHandleMonitor|xnnhandlemonitor.cpp:35||regist handle,type:0 handle:1043125344
2024-09-06 05:05:19|140127257873088|xnn.XNNRTResource|xnnrtresource.cpp:20||the acc thread cnt is 0
2024-09-06 05:05:19|140127257873088|xnn.XNNContext|xnncontext.cpp:99||init xnn context succ
2024-09-06 05:05:19|140127257873088|XNNReg|xnnlayerreg.cpp:866||layer map inited
2024-09-06 05:05:19|140127257873088|xnn.XNNHandleMonitor|xnnhandlemonitor.cpp:35||regist handle,type:0 handle:1043126640
2024-09-06 05:05:19|140127257873088|xnn.XNNRTResource|xnnrtresource.cpp:20||the acc thread cnt is 0
2024-09-06 05:05:19|140127257873088|xnn.XNNContext|xnncontext.cpp:99||init xnn context succ
2024-09-06 05:05:19|140127257873088|XNNReg|xnnlayerreg.cpp:866||layer map inited
2024-09-06 05:05:19|140127257873088|xnn.XNNHandleMonitor|xnnhandlemonitor.cpp:35||regist handle,type:0 handle:1043208928
2024-09-06 05:05:19|140127257873088|xnn.XNNRTResource|xnnrtresource.cpp:20||the acc thread cnt is 0
2024-09-06 05:05:19|140127257873088|xnn.XNNContext|xnncontext.cpp:99||init xnn context succ
fish: Job 1, './result/opt/wemeet/bin/wemeeta…' terminated by signal SIGSEGV (Address boundary error)

XWayland:
$ WAYLAND_DISPLAY= ./result/opt/wemeet/bin/wemeetapp
wemeet:WemeetSatrt
Fontconfig error: "/etc/fonts/fonts.conf", line 5: not well-formed (invalid token)
Fontconfig error: Cannot load config file from /etc/fonts/fonts.conf
fish: Job 1, 'WAYLAND_DISPLAY= ./result/opt/w…' terminated by signal SIGABRT (Abort)


Handle system messages

And write a sys_SUITE.

Please feel free to use any code, particularly the tests, from the my
system message PRs targeting v1.1. Not sure any of it applies anymore but
be my guest all the same.
On 18 Feb 2017 7:59 pm, "Loïc Hoguin"<EMAIL_ADDRESS>wrote:

And write a sys_SUITE.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ninenines/cowboy/issues/1126, or mute the thread
https://github.com/notifications/unsubscribe-auth/AB6JTToDVeYKAmRac-9sFxFrb91YqGqrks5rd02NgaJpZM4MFPMm
.

Yes! I kept them open specifically for that reason. :-) Thanks!
They probably don't apply anymore since they pre-date the large internal rewrites in 2.0.0-pre.4. But they'll be a good checklist.
Note that this ticket is specifically about handling system messages, the processes already use proc_lib.

While I'm here...
https://github.com/ninenines/cowboy/pull/750
https://github.com/ninenines/cowboy/pull/754

Man these PRs were huge. I will only respond to system messages first, with no code_change/format_status and such (or rather, not change of state when code_change happens, etc.) and we can see later for bigger and better.

This part is done on master.


Added InMemoryCache Features

Added support for the following operations on the InMemoryCache object

GetCacheSize (returns cache size in bytes)
EntitySetsInCache (returns a list of all currently cached entity sets)

Thanks for your PR but I decided not to take it. Changing the ICache interface is out of the question - there are implementations of this interface shipped as external NuGet packages (e.g. to implement the cache using Redis or Distributed Cache) and changing the interface would break them. I also don't think the methods you are trying to add are a good fit for the ICache interface. I think that EntitySetsInCache is not very useful in general and if you cache only what needs to be cached you would use a custom caching policy to constrain entity sets (tables) to be cached. The GetCacheSize might be useful in some contexts (e.g. memory cache) but is probably not that useful in other contexts (e.g. when caching items in Redis). I also think it is not trivial to implement this method correctly. If this method is supposed to be used to limit the memory used by cached items then the implementation you proposed allocates more than 2 times of what is already allocated for cache items and the returned size is actually not accurate. I also don't think this method is essential to the ICache interface. I could imagine have a different interface (e.g. IDiagnostics) that contains method returning diagnostic information and a cache could implement both ICache
and IDiagnostics interface. This would however be outside of this project and I think can be implemented without changes in this project. It's worth noting that the InMemoryCache is just a toy implementation of a cache that is more of a sample than a production ready thing. A more comprehensive implementation would, for instance, have a task (timer or background thread) that periodically removes expired items from the cache. If you need a cache that has methods you added you can implement ICache interface in your project and augment the implementation. Feel free to copy and use the InMemoryCache as a starting point if you think it's good enough.
Thank you for your PR and your interest in the project!

Hi Pawel,
Thank you for taking the time to review my PR and sharing your insightful
feedback.
I'll keep looking into some improvements locally, especially for the cache
size (you're completely right about the 2-3x size issue), since that is
something that would greatly benefit the implementation of the cache in
this current application.
Thanks for a great tool!
Sincerely,
Alexander
2018-05-08 0:43 GMT-04:00 Pawel Kadluczka<EMAIL_ADDRESS>
Closed #26 https://github.com/moozzyk/EFCache/pull/26.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/moozzyk/EFCache/pull/26#event-1614404987, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AczW4XMrwRj5eWyh1_1iVxhhc013krxoks5twSJ4gaJpZM4T10bx
.


update awscli to 1.9.15

New versions should be sent upstream to Homebrew. Please see CONTRIBUTING.md


Job DSL plugin issue

When using the lockable-resources plugin with the Job DSL plugin, the generated snippet within config.xml appears to be incorrect:
        <org.jenkins.plugins.lockableresources.RequiredResourcesProperty>
            <resourceNames>lock-resource</resourceNames>
        </org.jenkins.plugins.lockableresources.RequiredResourcesProperty>

As expected, running the job(s) fails to lock the resource.
If I edit the generated job manually and configure the lockable resource, its replaced with this:
      <org.jenkins.plugins.lockableresources.RequiredResourcesProperty<EMAIL_ADDRESS>        <resourceNames>lock-resource</resourceNames>
      </org.jenkins.plugins.lockableresources.RequiredResourcesProperty>

This works as expected, so I'm not sure if the issue lies with JobDSL or lockable-resources plugin.
Jenkins: 1.638
Java: 1.8
Lockable Resources: 1.7
Job DSL: 1.40

Given the age of the issue and that I've never seen this problem in practice, I am inclined to close it. Feel free to revive if it still happens with current releases.


Adding an "active" flag to User model

As discussed in this week's meeting on Wednesday March 8, we should have an active column in User model to act as a flag, when we need to shutdown access of a user.
We would need to modify:

prisma\schema.prisma for the schema
prisma\seed.ts for seeding
app\models\user.server.ts for functions to set and check whether someone is active

I'd consider making it a negative vs positive: flagged vs. active.  We want to indicate that a user is in some special state.


NumericUpDown control

Describe the bug
When the NumericUpDown control is at a value of 5.6 and Increment is 0.01, if adjusted up, it will appear as 0.570000000000000001 instead of 0.57
Code
<NumericUpDown Value="0.56" Minimum="0" Maximum="10" Increment="0.01"/>
Expected behavior
The value should beThe value should be 0.57
Screenshots

Desktop (please complete the following information):

OS: win 10
Version  0.9.12

I know this is an error in floating-point calculations

I know this is an error in floating-point calculations

value is double, should we consider making it decimal?

value is double, should we consider making it decimal?

I suggest adding up-for-grabs label because the solution to this issue seems pretty easy to me

I suggest adding up-for-grabs label because the solution to this issue seems pretty easy to me

I think we should port NumericUpDown.DecimalPlaces from WPF to correctly round the values: https://docs.microsoft.com/en-us/dotnet/api/system.windows.forms.numericupdown.decimalplaces?view=net-5.0

I think we should port NumericUpDown.DecimalPlaces from WPF to correctly round the values: https://docs.microsoft.com/en-us/dotnet/api/system.windows.forms.numericupdown.decimalplaces?view=net-5.0

Related: https://github.com/AvaloniaUI/Avalonia/issues/4756
To fix this i'm using FormatString="{}{0:0.00}"

Related: https://github.com/AvaloniaUI/Avalonia/issues/4756
To fix this i'm using FormatString="{}{0:0.00}"


redefine index

https://github.com/hxdengBerkeley/PointCNN.Pytorch/blob/6ec6c291cf97923a84fb6ed8c82e98bf01e7e96d/utils/util_funcs.py#L57
It's unhealthy to define a variable "n" inside a loop that uses "n" as it's enumerator
(how does this even work?)

https://github.com/hxdengBerkeley/PointCNN.Pytorch/blob/6ec6c291cf97923a84fb6ed8c82e98bf01e7e96d/utils/util_funcs.py#L57
It's unhealthy to define a variable "n" inside a loop that uses "n" as it's enumerator
(how does this even work?)

seems the function is absolutely wrong,giving an incorrect index for K-Nearst Neighbors
knn is much easier in torch after torch.topk function released,just follow the codes below
def knn_indices_func_gpuuu(seed:cuda.FloatTensor,   #(B,C,npoint)
                            pts:cuda.FloatTensor,   #(B,C,N)
                            k:int
                            ):     #(N,npoint,K)
    _,_,N = seed.shape
    _,_,M = pts.shape
    mseed = seed.unsqueeze(-2).expand(-1,-1,M,-1)
    mpts  = pts.unsqueeze(-1).expand(-1,-1,-1,N)
    mdist = torch.sum((mpts-mseed)**2,dim=1)
    _,idx = torch.topk(mdist,k=k+1,largest=False)

    return idx[:,:,1:]

alone with the test code
import torch
from torch import cuda, FloatTensor, LongTensor
from shapenet import shapenet
from torch.utils.data import DataLoader

# shapedata = shapenet('../shapenet_part_seg_hdf5_data',split='val')
# shapeloader = DataLoader(shapedata,batch_size=5)
#data,label = iter(shapeloader).next()
#data=data.to('cuda')
#src = data[:,:,:10]
data = torch.tensor([[1,2,3,4,5,6,7,8,9],[1,2,3,4,5,6,7,8,9]]).to('cuda').unsqueeze(0).repeat(2,1,1)
src = torch.tensor([[0,1,2],[0,1,2]]).unsqueeze(0).to('cuda').repeat(2,1,1)
print(src.shape)
print(data.shape)

idx = knn_indices_func_gpuuu(data,src,2)
print(idx.shape)
print(idx)

and result
torch.Size([2, 2, 3])
torch.Size([2, 2, 9])
torch.Size([2, 3, 2])
tensor([[[1, 2],
         [1, 2],
         [2, 0]],

        [[1, 2],
         [1, 2],
         [2, 0]]], device='cuda:0')

hope it will help you even after two and half years,:D

https://github.com/hxdengBerkeley/PointCNN.Pytorch/blob/6ec6c291cf97923a84fb6ed8c82e98bf01e7e96d/utils/util_funcs.py#L57
It's unhealthy to define a variable "n" inside a loop that uses "n" as it's enumerator
(how does this even work?)

seems the function is absolutely wrong,giving an incorrect index for K-Nearst Neighbors
knn is much easier in torch after torch.topk function released,just follow the codes below
def knn_indices_func_gpuuu(seed:cuda.FloatTensor,   #(B,C,npoint)
                            pts:cuda.FloatTensor,   #(B,C,N)
                            k:int
                            ):     #(N,npoint,K)
    _,_,N = seed.shape
    _,_,M = pts.shape
    mseed = seed.unsqueeze(-2).expand(-1,-1,M,-1)
    mpts  = pts.unsqueeze(-1).expand(-1,-1,-1,N)
    mdist = torch.sum((mpts-mseed)**2,dim=1)
    _,idx = torch.topk(mdist,k=k+1,largest=False)

    return idx[:,:,1:]

alone with the test code
import torch
from torch import cuda, FloatTensor, LongTensor
from shapenet import shapenet
from torch.utils.data import DataLoader

# shapedata = shapenet('../shapenet_part_seg_hdf5_data',split='val')
# shapeloader = DataLoader(shapedata,batch_size=5)
#data,label = iter(shapeloader).next()
#data=data.to('cuda')
#src = data[:,:,:10]
data = torch.tensor([[1,2,3,4,5,6,7,8,9],[1,2,3,4,5,6,7,8,9]]).to('cuda').unsqueeze(0).repeat(2,1,1)
src = torch.tensor([[0,1,2],[0,1,2]]).unsqueeze(0).to('cuda').repeat(2,1,1)
print(src.shape)
print(data.shape)

idx = knn_indices_func_gpuuu(data,src,2)
print(idx.shape)
print(idx)

and result
torch.Size([2, 2, 3])
torch.Size([2, 2, 9])
torch.Size([2, 3, 2])
tensor([[[1, 2],
         [1, 2],
         [2, 0]],

        [[1, 2],
         [1, 2],
         [2, 0]]], device='cuda:0')

hope it will help you even after two and half years,:D


Specify when registered in multiple pollers

This adds documentation to add() describing what happens when a source is registered in multiple pollers. A test is also added to ensure this behavior.
Closes #81

Huh, weird, apparently that doesn't work for Windows? Not sure if that is an AFD implementation detail or not. Oh well, it's easy enough to paper over.


When page is opened image in vue-carousel is not visible. Need to click.

Bug Report
Hello,
Working with Laravel 5.7 / Vuejs 2.6 / Bootstrap 4.3 app I use "vue-carousel": "^0.18.0"
I have a problem that defing carousel with images at page opening the page is not visible at all.
But if to click on the empty image space then image is visible and carousel works ok.
in vue file :

						<carousel
								v-show="hostelImages.length"
								:centerMode="false"
								:perPage="1"
								:navigationEnabled="true"
								paginationColor="#7e7e7e"
								paginationPosition="bottom"
								class="m-4"
								zIndex= "100 !important"
						>
							<slide v-for="nextHostelImage, index in hostelImages" :key="nextHostelImage.id">

									{{ nextHostelImage.info }}

							</slide>
						</carousel>

                    ...


Command to add hackers with reimbursement to mail list

This substitutes https://github.com/hackupc/mercuryhack/issues/39.
Create a command to add to a mail list all hackers that have been assigned some travel reimbursement.
The mail list on SendGrid can be the already existing HackUPC W17 Travel Reimbursement.

done in #63


Android BLE Prov App leaves ESP device paired (IDFGH-8027)

Environment

Module or chip used:  ESP32-C3-MINI-1-N4
ESP-IDF v4.4.1
Build System:        idf.py
Operating System:    macOS
Using an IDE?: No
Power Supply:    USB
ESP BLE Prov App: Androidv2.0.13
Mobile device: Samsung S21 Ultra, Andoid 12, One UI 4.1

Problem Description
I am using the latest Android ESP BLE Prov mobile app with ESP-IDF code derived from https://github.com/espressif/esp-idf/tree/30e8f19f5a/examples/provisioning/wifi_prov_mgr.
The first BLE WIFI provisioning is successful, but after provisioning completes the ESP device is left paired with the Android device. If the ESP device is reset with wifi_prov_mgr_reset_provisioning(), and the BLE Prov mobile app is run again, the next attempt to provision the same ESP device will fail because there is an existing pairing. The failed provisioning seems to remove the paring and the following attempt will succeed, but that seems like a lucky coincidence rather than an explicit design.
Expected Behavior
The Android ESP BLE Prov mobile app can be used to repeatedly provision WIFI without errors or manually removing already paired ESP device.
Potential Solutions

I think the best solution would be to not cause permanent bonding/paring to occur. I believe the Android device itself may be initiating the bond (aka pairing) due to some characteristic returned by the ESP device. See "Initiating a bond" here: https://punchthrough.com/android-ble-guide/#Bonding-with-a-BLE-device
The reason I believe it is Android OS initiated is that the ESP BLE mobile app does not call createBond() and WIFI_PROV_BLE_BONDING is not set in the ESP32 firmware code. Also, using ESP-IDF 3.x this problem did not exist and a bond/pairing was not established. That makes me think the ESP-IDF library has changed some characteristic or other property that now triggers bonding (should be tested on iOS also).

Next option would be to allow the bond to be created, but change the mobile app to check for an existing pairing and reuse it. I believe that would avoid the error and disconnect that currently results from calling BluetoothDevice#connectGatt  and BluetoothGatt#discoverServices on a device that is already paired.
I have not tested this, but I assume that would be done by determining the device was already paired and then using BluetoothGatt#connect rather than BluetoothDevice#connectGatt

Use java reflection to always remove the bond during connection shutdown. This uses a hidden Android SDK method, but it seems to be well used and it still works when I tested it. In BLETransport.java in the BluetoothGattCallback's STATE_DISCONNECTED handler, add the following:

try {
  Method m = currentDevice.getClass().getMethod("removeBond", (Class[]) null);
  m.invoke(currentDevice, (Object[]) null);
} catch (Exception e) {
  Log.e(TAG, "removeBond failed: " + e.getMessage());
}

I had the same problem on iOS app, but disabling WIFI_PROV_BLE_BONDING helps.
Duble check if have this disabled.

@jacek12345 I mentioned that in the potential solutions #1... WIFI_PROV_BLE_BONDING is not set. I doubled checked sdkconfig:
CONFIG_WIFI_PROV_BLE_BONDING is not set

@bschick I suggest update ESP-IDF to 4.4.2 branch.
I found: "Fixed bond not saved properly after re-pairing" in this branch.

@jacek12345 Thanks for the pointer, while I don't believe the specific change you mentioned fixed he problem it did lead me to a different commit that did. My suspicion in the original report was correct... some ESP-IDF change in the past forced BT characteristics to be encrypted which triggers Android devices (and I'd assume iOS) to initiate bonding on their own.
The change below merged into v4.4 added support for removing forced characteristic encryption
https://github.com/espressif/esp-idf/commit/7a01fe7a713a33ba41d942fccb39c5fe30e3568e
Disabling the new CONFIG_WIFI_PROV_BLE_FORCE_ENCRYPTION flag stopped the undesired bond.
I assume the actual provisioning data passed of BLE (wifi ssid and password) are encrypted given that WIFI_PROV_BLE_SEC_CONN is still set.

Even though I found a solution, I think this Issue still needs to be addressed. Currently on Android, and I'd assume iOS, a pairing is created when using the default settings of the ESP prov manager example:  https://github.com/espressif/esp-idf/tree/30e8f19f5a/examples/provisioning/wifi_prov_mgr
Then when the Mobile App is used to provision the same device again, an error results since the app doesn't handle ian established pairing. A few adjustments could be made to make the mobile app and the ESP example work better together:

Mobile app should be changed to reuse an existing pairing.
The ESP example should be configured with CONFIG_WIFI_PROV_BLE_FORCE_ENCRYPTION disable by default so no paring occurs.
ESP Prov manager configs should be changed to enable CONFIG_WIFI_PROV_BLE_BONDING when CONFIG_WIFI_PROV_BLE_FORCE_ENCRYPTION is enabled since the Mobile device will save the bond regardless

Changes pertaining to disabling CONFIG_WIFI_PROV_BLE_FORCE_ENCRYPTION by default are done which i believe should suffice to fix this issue.

Even though I found a solution, I think this Issue still needs to be addressed. Currently on Android, and I'd assume iOS, a pairing is created when using default configs for the ESP prov manager example: https://github.com/espressif/esp-idf/tree/30e8f19f5a/examples/provisioning/wifi_prov_mgr
When the Mobile App is used to provision the same ESP device a 2nd time, an error results since the app doesn't handle an already paired ESP device. A few adjustments could be made to make the mobile app and the ESP example work better together:

Mobile app should be changed to reuse an existing pairing.
The ESP example should be configured with CONFIG_WIFI_PROV_BLE_FORCE_ENCRYPTION disable by default so no paring occurs.
ESP Prov manager configs should be changed to enable CONFIG_WIFI_PROV_BLE_BONDING when CONFIG_WIFI_PROV_BLE_FORCE_ENCRYPTION is enabled since the Mobile device will save the bond regardless

For point 1,  since app side changes are not tracked on IDF side, i request you to please raise issue in   https://github.com/espressif/esp-idf-provisioning-android
For point 2 , change has bene done.
For point 3, this is configurable to cater to different use cases. So user can select / deselect the option as per their use.


Description on main page of website

Currently the first paragraph of the main page description reads: " We introduce a new dataset and model of pre-implantation mouse embryos with complete 3D instance segmentation of nuclei. This is one of the largest and most complete datasets of its kind with over 570 high resolution images from a light sheet microscope. Each image has a resolution of roughly 64x512x512 and every nucleus in each image is fully annotated in 3D by a series of contours in each slice."
To include the new dataset, I suggest we amend it to: " We introduce new ground truth datasets of 3D nuclear instance segmentation in pre-implantation mouse embryos as well as models trained on those datasets. One ground truth dataset (BlastoSPIM 1.0) is primarily composed of embryos from the 8-nuclei stage to the 64-nuclei stage. The other ground truth dataset (BlastoSPIM 2.0) is primarily composed of embryos from the 64-nuclei stage to the >100-nuclei stage. BlastoSPIM 1.0 and 2.0 are two of the largest and most complete datasets of their kind with 573 and 80 annotated light-sheet images, respectively. Each image has an xy-resolution of 0.208 micron and a z-resolution of 2.0 microns. For each of the 18336 nuclei across the two datasets, the ground-truth instance is defined by drawing a contour in each z-slice in which the nucleus appears."

Text changed as suggested: https://users.flatironinstitute.org/~awatters/blastospim/html/index1.html


Add Spark.Dsl.Patch.ReplaceEntity, DeleteEntity

Is your feature request related to a problem? Please describe.
When creating an entity to replace Ash's default entity, there is no way to remove the existing entity.
Describe the solution you'd like
Add Spark.Dsl.Patch.ReplaceEntity, DeleteEntity
Express the feature either with a change to resource syntax, or with a change to the resource interface
Instead of code with existing entity from Ash like below,
actions do
  create :insert do
    argument :foo, :integer, allow_nil?: true
    argument :bar, :integer, allow_nil?: false
  end
end

I want to write like this in my application.
actions do
  create :insert do
    opt :foo, :integer
    req :bar, :integer
  end
end

But there is no way to replace create entity with my custom create entity.
I can only add a new entity but it makes call create ambiguous.

I think for your specific example, there are two ways it could be approached.

we could alter spark to make AddEntity allow adding entities to entities. argument is a nested entity within the create entity.

you could define a macro

defmacro opt(name, type, opts) do
  quote do
    attribute unquote(name), unquote(type), unquote(Keyword.put(opts, :allow_nil?, true))
  end
end

I'm going to close this particular issue, because allowing extensions to overwrite entities by other extensions is a whole can of worms that we should avoid unless we have no other option :)


wasm-bingen fails to parse files with relaxed-simd instructions

Any Rust crate with a core::arch::wasm32::f32x4_relaxed_madd call will break wasm-bindgen thusly (as reported by wasm-pack):
Caused by:
    0: failed to parse input as wasm
    1: failed to parse code section
    2: relaxed SIMD support is not enabled (at offset 0x332b)
Error: Running the wasm-bindgen CLI
Caused by: Running the wasm-bindgen CLI
Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1
  full command: "/Users/dragos/.cargo/bin/wasm-bindgen" "/Users/dragos/Documents/rust/engine/target/wasm32-unknown-unknown/release/engine.wasm" "--out-dir" "/Users/dragos/Documents/rust/engine/pkg" "--typescript" "--target" "web"

It seems like this is caused by not having a way to enable the relaxed-simd feature in the parser.

I created a PR at Walrus for this: https://github.com/rustwasm/walrus/pull/281.
This should automatically start working with the next point release of Walrus, so I will go ahead and close this issue as there is nothing wasm-bindgen can do here.


Amavis config file permissions not secure, keeps looping

When spawning a new docker-mailserver, amavis complains that its config file is writable and then exit-loops.
Context
I spawned a fresh copy of this docker container using the instructions in the readme.
Here's the log from the container:
mail    | Apr  5 01:42:49 <host> amavis[167]: Net::Server: Group Not Defined.  Defaulting to EGID '111 111'
mail    | Apr  5 01:42:49 <host> amavis[167]: Net::Server: User Not Defined.  Defaulting to EUID '109'
mail    | Apr  5 01:42:49 <host> amavis[167]: (!!)FATAL: Config file "/etc/amavis/conf.d/61-dms_auto_generated" is writable, UID 109, EUID 109, EGID 111 111
mail    | Apr  5 01:42:49 <host> amavis[167]: (!!)TROUBLE in pre_loop_hook: SECURITY PROBLEM, ABORTING at /usr/sbin/amavisd-new line 12567.
mail    | 2020-04-05 01:42:49,623 INFO exited: amavis (exit status 255; not expected)

Not sure this is having an effect on me either way since spamassassin is disabled.
Expected Behavior
This shouldn't happen from a fresh docker-compose up command.
Actual Behavior
See above for the log.
Steps to Reproduce
Not sure how to reproduce, as this happened right from the start for me.
Your Environment

Amount of RAM available: 12GB
Mailserver version used: tvial/docker-mailserver:latest
Docker version used: Docker version 1.13.1, build cccb291/1.13.1
Environment settings relevant to the config:

HOSTNAME=<host>
DOMAINNAME=<domain>
CONTAINER_NAME=mail

Any relevant stack traces ("Full trace" preferred):
As log file above, copied below:

mail    | Apr  5 01:42:49 <host> amavis[167]: Net::Server: Group Not Defined.  Defaulting to EGID '111 111'
mail    | Apr  5 01:42:49 <host> amavis[167]: Net::Server: User Not Defined.  Defaulting to EUID '109'
mail    | Apr  5 01:42:49 <host> amavis[167]: (!!)FATAL: Config file "/etc/amavis/conf.d/61-dms_auto_generated" is writable, UID 109, EUID 109, EGID 111 111
mail    | Apr  5 01:42:49 <host> amavis[167]: (!!)TROUBLE in pre_loop_hook: SECURITY PROBLEM, ABORTING at /usr/sbin/amavisd-new line 12567.
mail    | 2020-04-05 01:42:49,623 INFO exited: amavis (exit status 255; not expected)

Was there some sort of insight, i.e. do you know more about this issue now?

This issue was closed due to one or more of the following reasons:

Age
Contributor inactivity
The issue seems to be resolved

If you think this happened by accident, or feel like this issue was not actually resolved, please feel free to re-open it. If there is an issue you could resolve in the meantime, please open a PR based on the current master branch so we can review it.

Hi,
I am having the same issue.
Problematic files are those copied from target here: https://github.com/tomav/docker-mailserver/blob/a0c2dc27c8cb75ef97308c3234945f26e116fa33/Dockerfile#L164
Maybe a chmod after the COPY could fix that ?
chmod go-w /etc/amavis/conf.d/*
But it is weird that no one else is complaining about that...

I've re-opened. But to be honest, this seems more of a configuration / setup error, since, as you mentioned, more users would report on this.
@erik-wramner any thoughts on this?

Ok, the problem might be with the way I build the image. I just built it locally and access rights seems to be ok.
I'll investigate more on Monday and write done what I found.

@artonge do you build locally on Windows, by any chance? File permissions tend to go haywire for docker images built on Windows.

I am building on gitlab CI. Mabey their cloning strategy is weird

Right. Please see suggestion in PR, if we add user (numeric) and permissions to the COPY command that should do the job!

After some debugging on the Gitlab CI, I can't reproduce the incorrect build, seems like a quantum bug...
Moreover, I don't think that the method suggested by @erik-wramner works, as it only change user and group and not file permissions.
I have at least changed the PR to be more predictable on the final file permissions, but I am not sure that it still need to be merged. I leave it up to you :).
Thanks for your work anyway !

Thanks for reporting back on this @artonge!
@erik-wramner I would leave it up to you to decide whether we merge this or not. I personally find your idea about the COPY command worth merging, but I guess you'd need to provide a PR for that on your own. I would not merge the current PR (since the problem you mentioned is actually still there) - if this helps you in finding the decision yourself. We can then close this and the PR (or merge it).


Aborted: 31 commits are not yet pushed

My command:
➜  ~ cask-repair --cask-version <IP_ADDRESS>221,675049 slicer-nightly -i

The error:
Submitting…
Aborted: 31 commits are not yet pushed to fepegar/cask_repair_update-slicer-nightly
(use `-f` to force submit a pull request anyway)
Aborted: 31 commits are not yet pushed to fepegar/cask_repair_update-slicer-nightly
(use `-f` to force submit a pull request anyway)

There was an error submitting the pull request. Please open a bug report on the repo for this script (https://github.com/vitorgalvao/tiny-scripts).

I also tried this:
➜  ~ cask-repair --delete-branches
remote: Repository not found.
fatal: repository 'https://github.com/fepegar/homebrew-cask/' not found
ERROR: Repository not found.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
ERROR: Repository not found.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Delete the repo and try again.
Also, the cask token must be the last argument.

I already tried to delete it, but I don't have that fork. Should I delete it from my machine? Where can I find it?
I tried putting the cask token at the end, got the same.
Why do you close the issue? Should I open a new one if I still have questions?

No, we can just continue talking. I close issues fast because many people never reply and the issue stays lingering. This way if I think I have the fix I give it and close the issue. That does not mean the conversation is over. If I deem necessary, I’ll reopen.
Ok, thanks for the explanation.

Try brew untap caskroom/versions.
That worked, thank you. I'll let you know if this happens again.


Add handling of URL fields in deployment groups

Includes changes to the protobuf definitions and handling of Teams events, as well as changes to the frontend to allow for creating the deployment group with the specified URL.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Fix Analyzer usage

From https://github.com/mocobeta/janome/pull/77/, interface of Analyzer was changed(keyword-only arguments). But some usage is still old interface.

https://github.com/mocobeta/janome/blob/master/janome/analyzer.py#L74-L77

Thank you @syou6162 !


⚠ Spryr has degraded performance

In 803be69, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3352 ms

Resolved: Spryr performance has improved in 5dd91d3 after 12 minutes.


Unable to find DocumentReference.category in US Core 5.0.1 tests when provided

What happened?
After running US Core 5.0.1 tests on DocumentReference, Inferno was unable to find DocumentReference.category:us-core when our resource has the category field:
 "category": [{
      "coding": [{
          "system": "http://hl7.org/fhir/us/core/CodeSystem/us-core-documentreference-category",
          "code": "clinical-note",
          "display": "Clinical Note"
        }
      ],
      "text": "Clinical Note"
    }
  ]

Error message: Could not find identifier, content.format, DocumentReference.category:us-core in the 8 provided DocumentReference resource(s)

@bcastillomartel-va Did you run tests on inferno.healthit.gov or your local installation? If you run on inferno.healthit.gov, could you provide your test session url? If you don't want to post it here, you could send to<EMAIL_ADDRESS>Thank you.

Hi @yunwwang, I'll send the test session url to the email you provided. Thank you for your help!

@yunwwang I'll also post the test session url here https://inferno.healthit.gov/suites/test_sessions/477e194a-9bce-48d8-9609-b2ccdf646e53#us_core_v501-us_core_v501_document_reference


Noteskin Bug

Describe your bug here. Mind you, if you are modding, please try testing your bug in a clean version of the engine instead, this ensures the bug is actually caused by the engine itself. Also, if you're using an older version of JSE, please try the latest action build in the Actions tab or the latest release build. The issue has probably been fixed since that version. Oh yeah, and also be sure to check the pinned 'JS Engine: Known Issues' issue, to double check if your issue hasn't already been found!
So there is this bug where JS Engine will use the same noteskin from a previous song
I was Using the song "Bopeebo" To test a different noteskin

After that the notes are using the same noteskin as seen in the other image

I checked in Chart Editior and it says there is no custom noteskin added in the chart
I clicked on change notes to see if it fixes it, but it doesn't work

This bug also applies if you change the note style back to "Default" after using a different noteskin other then "Default"
Command Prompt/Terminal/Crash logs (if existing)
No response
Have you identified any steps to reproduce the bug? If so, please describe them below in as much detail as possible. Use images if possible.
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No
If you use 1.12.0 or earlier, did you have Optimized Chart Loading turned on?
No
Did you check for any similar issues to what you're reporting? Check, then come back here. If there is a similar issue, then do not report the issue, otherwise it will be marked as a duplicate.
Yes

hey there, i've already detected this issue. please try the latest commit as it should be fixed there!


 doesn't work when rendered into an iframe

🐛 Bug Report
When rendering something containing <FocusScope contain/> into an iframe, FocusScope has trouble detecting the newly-focused element and goes into an infinite focusing loop.
Here's a repro: https://codesandbox.io/s/react-aria-focusscope-in-iframe-0e6fkj?file=/src/App.tsx
You can focus on one input in the iframe, and as long as you focus on another input, FocusScope will keep switching focus between the two.
The issue seems to be that in FocusScope.tsx, onBlur, it is checking if the newly-focused element is within the focus scope, and if not, returns the focus to the previously-focused node. Unfortunately it is assuming that document.activeElement is the newly-focused element instead of using e.relatedTarget, and document refers to the parent frame and not the child frame, so it incorrectly tries to restore focus to the previously-focused input.
🤔 Expected Behavior
<FocusScope/> continues working in an iframe.
😯 Current Behavior
<FocusScope/> cannot detect focused element across iframes.
💁 Possible Solution
It's possible here to look for activeElement in all the iframes until you find one, instead of directly relying on document.activeElement.  But then, I'm not sure if this is even a use case that react-aria is trying to allow 😅 I see many direct references to document in the react-aria code, so they'll all probably break in some way when used across iframes.
🔦 Context
In Plasmic, we're allowing users to register React components that we then use to render in another iframe. This happens when those registered components use <FocusScope contain/>.
💻 Code Sample
https://codesandbox.io/s/react-aria-focusscope-in-iframe-0e6fkj?file=/src/App.tsx
🌍 Your Environment

Software
Version(s)

@react-aria/focus
3.6.1

🧢 Your Company/Team
Plasmic

Thanks for the sandbox, definitely not ideal. I forget exactly why I made this change, perhaps we could use e.relatedTarget instead of document.activeElement

I have a potential solution for this and would like to submit a RFC @LFDanLu

Sounds good, thanks! I'll bring it to the teams attention.

This appears to have been fixed, I can't reproduce with latest https://codesandbox.io/p/sandbox/react-aria-focusscope-in-iframe-forked-ds3vwm
Thanks @slye-stripe, I'm guessing one of your PRs fixed it!


Xtensa Special Register symbolic names #defines with very short identifiers (IDFGH-11606)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.1.2
Operating System used.
Windows
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
PowerShell
What is the expected behavior?
No excessively short macros defined in framework headers.
What is the actual behavior?
https://github.com/espressif/esp-idf/blob/master/components/xtensa/esp32/include/xtensa/config/specreg.h
https://github.com/espressif/esp-idf/blob/master/components/xtensa/esp32s2/include/xtensa/config/specreg.h
https://github.com/espressif/esp-idf/blob/master/components/xtensa/esp32s3/include/xtensa/config/specreg.h
Are indirectly included in <freertos/FreeRTOS.h>, meaning a large number of very short identifiers are macro replaced to numbers, causing build failures if those identifiers are used elsewhere in code.
Steps to reproduce.

#include <freertos/FreeRTOS.h>
Use BR, PS, DDR, SAR, MR, EPC, EPS, INTERRUPT, ICOUNT, etc as identifiers.

Build or installation Logs.
In file included from C:/Espressif/frameworks/esp-idf-v5.1/components/xtensa/include/xtensa/xtruntime.h:30,
                 from C:/Espressif/frameworks/esp-idf-v5.1/components/freertos/FreeRTOS-Kernel/portable/xtensa/include/freertos/portmacro.h:72,
                 from C:/Espressif/frameworks/esp-idf-v5.1/components/freertos/FreeRTOS-Kernel/include/freertos/portable.h:59,
                 from C:/Espressif/frameworks/esp-idf-v5.1/components/freertos/FreeRTOS-Kernel/include/freertos/FreeRTOS.h:71,
                 from C:/Users/Nebojsa/Work/Troo/mdf-firmware/troo_idf_components/freertos_cxx/include/freertos/ring_buffer.hpp:6,
                 from C:/Users/Nebojsa/Work/Troo/mdf-firmware/main/include/app/core/event/event_loop.hpp:9,
                 from C:/Users/Nebojsa/Work/Troo/mdf-firmware/main/include/app/main.hpp:9,
                 from C:/Users/Nebojsa/Work/Troo/mdf-firmware/main/src/main.cpp:6:
C:/Espressif/frameworks/esp-idf-v5.1/components/xtensa/esp32s3/include/xtensa/config/specreg.h:86:25: error: expected unqualified-id before numeric constant
   86 | #define PS              230
      |                         ^~~
C:/Users/Nebojsa/Work/Troo/mdf-firmware/troo_idf_components/external/mp-units/mp-units/src/systems/si/include/mp-units/systems/si/unit_symbols.h:494:23: note: in expansion of macro 'PS'
  494 | inline constexpr auto PS = peta<siemens>;
      |                       ^~

More Information.
No response

@nebkat Unfortunately there's not much we can do in this case. The include chain you are seeing is as follows:
freertos/FreeRTOS.h <- portable.h <- portmacro.h <- <xtensa/config/...h>
portmacro.h requires use of the Xtensa macros because a significant a large number of FreeRTOS porting macros are implemented as inline functions/asm indirectly inside portmacro.h. They are implemented inline to increase efficiency.
As an alternative, are you able to undef those identifiers?

@Dazza0 Thanks for the quick response!
The chain and reasoning make sense, but could we rename the macros, even just to XT_PS or REG_PS?
I am able to #undef, just it pollutes my library code that isn't strictly used with ESP-IDF.

@nebkat Upon further review, we've decided to rename the specreg.h and prefix them with XT_.... We'll leave a compatibility header with the old names just in case anyone needs them.


The results of different runs differ a lot.

I am implementing this code on my biological datasets. When  I run the code multiple times, it produces quite different results. The ARIs vary from 0.4 to 0.8.  I find out that the pretrained model matters a lot to the results. How can I achieve robust results by getting a good pretrained model? Is the pretrained denoising autoencoder important to stacked autoencoder  when the structure of the dae is not exactly the same as that of sdae?

What code are you using? stacked denoising autoencoder?

Sorry about the ambiguity! When I run the code VaDe multiple times, it produces quite different results. The ARIs vary from 0.4 to 0.8. I find out that the pretrained sdae model results matters a lot to the VaDe clustering results. How can I achieve robust results by getting a good pretrained sdae model? Is the pretrained denoising autoencoder important to sdae when the structure of the dae is not exactly the same as that of sdae?

This is actually the issue of the original paper and their released code. I also find this issue annoying. But I find that using xavier initialization for the weights could alleviate the problem a lot. You could try.

How to get the pretrained_vade-3layer.pt ?

@chulaihunde I converted from original VaDE page. But I really don't know how they get the pretrained weights. Let me know if you figured that out.

May be able to refer to https://github.com/piiswrong/dec/blob/master/dec/pretrain.py


Support sections in table

To be able to output the table with sections to divide some IPs from others and set a title for each section

I can work on this.

Thank you very much @Balaguru4580, I'll assign you to this issue

Also, what are the conditions for which the sections would be formed? Is that user determinable?

@Balaguru4580 Yes, the user will define it in their JSON config file


WCAG 1.4.3: (ExpenseItIntro/list box '' Names) [High Contrast Black] Contrast ratio failure for Regular text

The following accessibility issue needs investigation.
App: ExpenseItIntro
Element path: list box '' Names
Issue Details: Contrast ratio failure for Regular text
How To Fix: https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html
This accessibility issue was found using Accessibility Insights for Windows, a tool that helps debug and find accessibility issues earlier. Get more information and download this tool at https://aka.ms/AccessibilityInsights.


onFetchData not triggered at pagination

What version of React-Table are you using?
6.7.6
What bug are you experiencing, or what feature are you proposing?
When I try to wrap react-table as a customized component(called CReactTable) in my own components library, I imported this component in another repo and use the server-side data feature, onFetchData event has only been triggered once at componentDidMount. Pagination can change the page index, but can't trigger onFetchData nor onPageChange event.
        <ReactTable
          data={this.state.data} // should default to []
          pages={10}
          columns={[{ Header: "title", accessor: "title" }]}
          pageSize={50}
          manual // informs React Table that you'll be handling sorting and pagination server-side
          onPageChange={(pageIndex) => {
            // when I click next page, nothing happens here
            console.info('debug pageIndex', pageIndex)
          }}
          onFetchData={(state, instance) => {
            // console.info('debug state, instance', state, instance)
            // when I click next page, nothing happens here
            // show the loading overlay
            this.setState({ loading: true });
            // fetch your data
            Axios.get("https://jsonplaceholder.typicode.com/posts").then(
              res => {
                // Update react-table
                this.setState({
                  data: res.data,
                  loading: false
                });
              }
            );
          }}
        />

// another repo
import { CReactTable } from 'my-ui-lib'

const Test = () => {
    return <CReactTable />
}

What are the steps to reproduce the issue?
// my-ui-lib
yarn run watch
yarn link

// another repo
yarn link my-ui-lib

import { CReactTable } from 'my-ui-lib'

const Test = () => {
    return <CReactTable />
}

FYI:
// my babel config
  "scripts": {
    "watch":
      "BABEL_ENV=development babel --watch src --out-dir dist --source-maps --copy-files --ignore '**/*.test.js'",
  },
    "babel-cli": "6.26.0",
    "babel-core": "6.26.0",
    "babel-eslint": "8.0.3",
    "babel-jest": "21.2.0",
    "babel-loader": "7.1.2",
    "babel-plugin-transform-es2015-modules-commonjs": "6.26.0",
    "babel-preset-react": "6.24.1",
    "babel-preset-react-app": "3.1.0",
    "babel-preset-stage-1": "6.24.1",

// .babelrc
{
  "plugins": ["transform-es2015-modules-commonjs"],
  "presets": ["stage-1", "react"]
}

onPageChange is not a notification - it is an override that allows you to control the page changing yourself and then you need to push the page back in as a prop (the changing page prop will then trigger the onFetchData. So there is not much use in combining onFetchData and onPageChange because onFetchData will be called when a page changes - but by providing the onPageChange you are short-circuiting the paging mechanism.
Remove onPageChange and, if you need the page number, get the page information from the state prop passed to onFetchData.
As far as your external component  is concerned - it may also be causing a problem but it would have to be provided in a codesandbox to provide any further advice.

Thanks for your apply. I added the onPageChange just to show this event is not triggered. After I removed the onPageChange and this problem is still there.
I forked the codesandbox, and it works fine within it.
Also, I tried to move the CReactTable to the repo needs to use it. It works fine too.
So I guess this problem results from babel or yarn link. Another situation is that other simpler components line Input, Button, etc. are not effected. So It really make it hard to find out where the bug is.
Sorry for it seems that codesandbox doesn't support yarn(npm) link, so I can't reproduce it online.

Unfortunately, build environments vary greatly and if your component logic works in a well structured and maintained build environment (e.g. codesandbox) then it's difficult to provide any additional advice. I doubt it is related to yarn specifically (but could be related to how you are creating the symbolic link).  However, that is going to be so specific to your environment the only thing for it is to do the research and see if anyone else has had a similar problem (not specifically with React Table - just generically).
But, many people are using React Table - both just "as is" as well as build a wrapping component around it - that I doubt it is an issue with React Table.
It is still probably best to ask on the #react-table Slack channel - in case anyone has experienced issues with their build environment.


[v2] Set config all at once

We currently issue one SetAllConfig RPC for each user-specified config. This is slow but it has important correctness guarantees:

The order we apply config matters -- if the user specifies foo: foo followed by foo: bar, the net result must always be foo: bar.
The Pulumi CLI (and therefore Automation API) only allows specifying --path on an all-or-nothing basis. This is bad for us because we potentially have a blend of path and non-path keys.

Ideally we would be able to supply all of our configs to the automation API in a single call, and in the case where all of our config keys are path-like (or all are not path-like) we actually can do that because we no longer have limitation (2).
This PR makes that possible in the general case by transforming our config keys in a way that allows us to treat them as if they are all path-like.
In particular:

The agent's SetAllConfig handler is modified to take a list of configs instead of a map in order to preserve config order. The top-level path param is also removed and handled on a per-key basis.
While resolving configs, we escape any non-path keys so subsequent path parsing treats them as verbatim. For example foo.bar gets escaped as ["foo.bar"].
We can then supply all of our keys at once to Automation API with Path: true.
If there are no configs to set then the operator doesn't invoke SetAllConfig.

Fixes https://github.com/pulumi/pulumi-kubernetes-operator/issues/650

Confirmed config still propagates as expected. Of course the StacK API is currently just a map with no path information, so all of the path optimizations are only relevant for the Workspace API. However it does give users the ability -- although somewhat clunky -- to specify somewhat structured (path: true) config via the workspaceTemplate.


Support drds createtable SQL statement

注：暂时不合并
示例：
create table t13 (a int) dbpartition by hash (a) dbpartitions 2 tbpartition by hash (a) tbpartitions 2;
show tables;
show topology from t13;

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

Comparison is base (57676e1) 40.47% compared to head (fd0c134) 40.47%.

Files
Patch %
Lines

pkg/boot/watcher.go
83.33%
1 Missing :warning:

pkg/runtime/ast/ast.go
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #811   +/-   ##
=======================================
  Coverage   40.47%   40.47%
=======================================
  Files         265      265
  Lines       26711    26711
=======================================
+ Hits        10811    10812    +1
- Misses      14736    14737    +1
+ Partials     1164     1162    -2

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


No windows showing on Windows list

When I click the monkey icon on the taskbar and select the drop-down menu "Windows", no actions happen and no drop-down list shows up, even though I have multiple windows open.
I am using Arch Linux with the gnome Desktop Environment and installed the extensions through Firefox and the package chrome-gnome-shell-extensions.

I am also having this issue on Manjaro. Gnome 3.30.1

Hi @KiloLiuton @Kivarnis  please note a patch was provided some time ago and it was committed on the testing branch (v. 3).
Have you already tried to replace the v.2 with the latest version?

Hi @medenagan , thanks for the response.
How can I force version v. 3? The readme file on the testing branch shows latest version as v. 2 to me. I recently tried reinstalling from the gnome shell extensions website but the problem persists.

Hi @KiloLiuton, version 3 has not been submitted yet to the GNOME Shell Extensions team. An automatic installment is not available for now.
About the readme file, unfortunately it does not acknowledge these changes yet. But extension.js was updated and metadata.json shows v.3.
If you want to force the testing version being set up:
You need to find these two files on your system. You can look for their directory on a terminal with locate<EMAIL_ADDRESS>or you can press ALT + F2 from your desktop, type lg and choose Show source from the Extensions tab.
Normally the path is<EMAIL_ADDRESS>You can just replace these 2 files mentioned above with their newer version and restart the shell by pressing ALT + F2 and typing R

Hi @medenagan,
I had just testing the v3 on Ubuntu 18.10 and now I can see the list of windows but when I selected one, there is no preview displaying.
Any clue ?

#9 Worked for me...  =D

Me too ! Thx @gctrevino

I have substituted the files as suggested by @medenagan and it is working again, thanks!


CIRCLE-6546 Ensure that each AWS Region has the Ubuntu 14.04 AMI that…

… we want to use

LGTM merging. Thanks @smaant !


Changelog out of date.

Changelogs are the way most of us look through changes to see what might break for us. Any chance you could update the log to make it easier?

labeling as bug to ensure we re-enable changelog in the release workflow in v3

closing this, changelog should be updated by the GHA release workflow:
https://github.com/jsforce/jsforce/blob/main/CHANGELOG.md


Move /controller to /pkg/pki/ca/controller

Jenkins job auth/presubmit passed

Jenkins job auth/presubmit passed


No option to delete teams

Need to delete teams from Super league division of the main winter 23 season.
When team is associated with this division only then there should be a delete button in the assign to seasons dialog.
For other scenarios the team can be unassociated from the season.

De-assigning a team from all seasons will delete the team


Create github milestones with each release

Each time a library is released, close the existing milestone, and create new milestones for the next prerelease (if currently in alpha/beta), patch, and minor (if not currently alpha/beta).
Example of these milestones can be found at: https://github.com/AzureAD/microsoft-authentication-library-for-js/milestones

Coverage increased (+9.9%) to 92.746% when pulling 368c9723b2df944b629b2221c0ae6c3974299561 on releases-github-milestone into 8bc85a4eeab142e4fe2103530c21086e604c7564 on dev.


Make acceleration customizable

Is your feature request related to a problem? Please describe.
With a wide range of rotaries being used by users, acceleration values may not be ok for all of them.
Describe the solution you'd like
I would like to be able to fine tune  the acceleration value from the desktop app.
Describe alternatives you've considered
Additional context

I could transfer over my exponential acceleration stuff for this one. Only one value is needed to adjust the acceleration.

Sounds good. That being said I'm going to wait a bit until we got a solution for the encoder.


[BUG] Fix confusing treatment of paths / top level folder

Currently in configs paths must include the full path including the project name. e..g
/path/username/my_project

the docs are wrong, as they show remote_path=/path/username

this is confusing because the project is already initialised with the project name. So it should only be necessary to input the path to the project folder, then the project folder should be read from the project name.

This is marked as a bug because of the docs, but it is also just super confusing.

However, maybe it is a little more robust to just put the project name, and we can raise error if the last folder of  remote_path or local_path is not project_name.
There is no instance in which users will be switching these projects based on the path in the project config file, so it is not a concern to keep it dynamic.  This is only really relevant when inputting the path during configs. There are other functions such as show_local_path() where it makes much mroe sense to show the full filepath including the project name. Under the hood we could concatenate these, but then it requires maintaining two paths and concatenating, without any gain (because we do not need this flexibility). So instead, I think change the docs and raise an error during config setup.


Works for no comments

Thanks for pointing out this issue! I was going to ask you to add a test, but since this plugin doesn't have any tests right now, I won't insist on it.
I'll merge this to master as well as the releases/3.3 branch, so the fix will be included in JSDoc 3.3.0.


Missing instructions for vtk

I'm trying to install biomesh following the instructions in branch feature-fiber.
I started with
cd biomesh
cmake .
make

But I get the following error

vtkSmartPointer.h: No such file or directory

I tried fixing it by doing sudo apt-get install libvtk9-dev, but the installation was not successful. The error I encounter is

The following packages have unmet dependencies:
python3-paraview : Conflicts: python3-vtk9 but 9.1.0+really9.1.0+dfsg2-3build1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

@carme-hp It would be advisable to build VTK from source. You can follow these instructions.
git clone https://github.com/Kitware/VTK.git
mkdir vtk_build && cd vtk_build
cmake .
make -j8

@carme-hp I would advise to build the dependencies from source or use spack.

@carme-hp I would advise to build the dependencies from source or use spack.

This should only be a temporary workaround, though, or be documented in detail on what conflicts and for which reason.

@MakisH Yes your point is valid. I have mentioned a few points on the README. I agree that a more comprehensive documentation is required.


PAPI counters don't work

Unsure if this is a system, PAPI, APEX, or HPX issue, so looking for input from e.g. @khuck and @biddisco.
 As far as I know nothing has changed in our PAPI counters for a long while (except build-related options). That particular example asks for PAPI_FP_INS which --hpx:papi-event-info=all does not list, papi_avail also lists it as not available, so in that sense the failure is reasonable. However, I've tried with other counters that are listed as available and the same error appears. The exception is thrown by the PAPI performance counters in HPX but it seems like APEX is unhappy with something before that as well.
Has anyone tried the PAPI counters recently? This does smell like it's just a problem with PAPI on Piz Daint.

Hmmm...there were some recent changes to proc_read.cpp but they are completely unrelated to this error.  Can you point me to some instructions on how I can reproduce this configuration?

Hmmm...there were some recent changes to proc_read.cpp but I don't think they are related to this error. Can you point me to some instructions on how I can reproduce this configuration? The error from APEX is trying to enable RAPL power metrics that Piz Daint may have recently enabled in their PAPI configuration. If you try papi_native_avail you'll see if the RAPL component has been enabled.

The CMake configuration options are here: https://cdash.cscs.ch/buildSummary.php?buildid=115247#!#Configure. I don't think the compiler is relevant, it's clang 8. The PAPI version may be relevant (<IP_ADDRESS>). Otherwise it's a normal build with C++17, HPX_WITH_APEX=ON, HPX_WITH_PAPI=ON, APEX_WITH_PAPI=ON. If you're able to use the PAPI counters normally in your build I would say this is just a configuration issue.
As for RAPL, papi_native_avail says this:
 Native Events in Component: cray_rapl
===============================================================================
| cray_rapl:::UNITS:POWER                                                      |
|            Scaling factor for power (internal)                               |
--------------------------------------------------------------------------------
| cray_rapl:::UNITS:ENERGY                                                     |
|            Scaling factor for energy (internal)                              |
--------------------------------------------------------------------------------
| cray_rapl:::UNITS:TIME                                                       |
|            Scaling factor for time (internal)                                |
--------------------------------------------------------------------------------
| cray_rapl:::THERMAL_SPEC                                                     |
|            Thermal specification                                             |
|     Units: W                                                                 |
--------------------------------------------------------------------------------
| cray_rapl:::MINIMUM_POWER                                                    |
|            Minimum power                                                     |
|     Units: W                                                                 |
--------------------------------------------------------------------------------
| cray_rapl:::MAXIMUM_POWER                                                    |
|            Maximum power                                                     |
|     Units: W                                                                 |
--------------------------------------------------------------------------------
| cray_rapl:::MAXIMUM_TIME_WINDOW                                              |
|            Maximum time window                                               |
|     Units: s                                                                 |
--------------------------------------------------------------------------------
| cray_rapl:::PACKAGE_ENERGY                                                   |
|            Energy used by chip package                                       |
|     Units: nJ                                                                |
--------------------------------------------------------------------------------
| cray_rapl:::DRAM_ENERGY                                                      |
|            Energy used by DRAM in package                                    |
|     Units: nJ                                                                |
===============================================================================

which I guess looks ok. Based on the error messages I don't think RAPL is actually the problem here.

I think I agree that APEX isn't causing the exception.  When APEX encounters that problem getting a RAPL counter name, it just continues on to the next one: https://github.com/khuck/xpress-apex/blob/c59fac98a25230b8909a7bbfd062f37ae4099dd7/src/apex/proc_read.cpp#L122-L131 (I just updated that code to give more error information).  You could try toggling HPX_WITH_PAPI=ON, APEX_WITH_PAPI=OFF and HPX_WITH_PAPI=OFF, APEX_WITH_PAPI=ON to see which library is triggering the exception.  It is possible that both libraries are trying to use an exclusive resource within PAPI.

I can confirm that APEX is unrelated to this, and things still work in 1.4.1, so something has gone wrong on master along the way. I'll try to fix this before 1.5.0 (not necessarily for the first release candidate).


[CO-334] Implement remaining V0 endpoints to V1

Description
This topic branch tracks the implementation of the last few V0 endpoints in V1, under a special daedalus namespace.
Linked issue
https://iohk.myjetbrains.com/youtrack/issue/CO-334
Type of change

[ ] 🐞 Bug fix (non-breaking change which fixes an issue)
[x] 🛠 New feature (non-breaking change which adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
[ ] 🔨 New or improved tests for existing code
[ ] ⛑ git-flow chore (backport, hotfix, etc)

Developer checklist

[ ] I have read the style guide document, and my code follows the code style of this project.
[ ] If my code deals with exceptions, it follows the guidelines.
[ ] I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.

Testing checklist

[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

QA Steps

Screenshots (if available)

Note (wasn't maybe really clear from the requirements). What we use to call development API and this new internal API are the same thing.
"Development" just conveys a wrong idea of what it is. Therefore, we have to unify this with:
https://github.com/input-output-hk/cardano-sl/blob/develop/wallet-new/src/Cardano/Wallet/API/Development.hs

What we use to call development API and this new internal API are the same thing.

I agree in principle. The way I see it, there are two subtle faces of the same coin, as the original spirit of that Development endpoints was to capture that there were endpoints what frontend folks were using only for the sake of testing or troubleshooting the wallet, the endpoint to dump the full WalletStorage being the perfect example.
I think that in principle though unifying everything into only one category make sense, although I'm not sure how this would work in practice: for example (if I recall correctly) we do not even expose certain dev endpoints if the --wallet-debug option is not set.

@adinapoli-iohk Yes, and this has still the same meaning / behavior although we will also expose the documentation for these endpoints somewhere. These update apply and update postpone things aren't especially used in testing but they fall in the category of frontend-specific endpoints that are irrelevant for exchanges.

Nice job with the commit history @KtorZ :) I'll get this merged once CI passes.

CI was green, but something was merged to develop conflicting in generate-swagger-file/Main.hs ... Rebased, fixed, aaaaaaaaand going for another 2-hour trip :)

Everything is green, no conflicts, GOTTA GO FAST


[Question] Error publishing API : One or more fields contain incorrect values

Release version
V5.0.1
Question Details
failed with status code 400. Content is '{"error":{"code":"ValidationError","message":"One or more fields contain incorrect values:","details":[{"code":"ValidationError","target":"credentials","message":"Property 'func-ecs-generalutility-key' not found."}]}}'.
func-ecs-generalutility-key - It is one of the named value and it is present at the source API. I'm trying to extract API from one PAI instance and publish it to another API instance.
Expected behavior
Able to successfully extract and publish API from one instance to another
Actual behavior
Publish API failed
Reproduction Steps
Configure APIOPS DEVOPS tools kit to extract and publish API

Please search some of the closed issues which touch on the same topic. Usually this means that you are not passing the overrides in your configuration file. Remember to close this issue if you manage to resolve the problem you are dealing with.


update usage reporter config

Add a function to update the config druid.monitor.usageReporter.kafkaBrokers with the environment variable USAGE_KAFKA_BROKERS from the kubernetes kafka configmap.

I'm currently testing these in a local build, but sent out the PR early to try to get reviews before the weekend if successful


[V9RC4] Target class [\Concrete\Core\Permission\Key\GatheringKey] does not exist.

On update from 8.5.6 to v9 RC4
This is a largish older site which has been updated many times (started with early version 7). Advance Permissions are enabled.

Note that whether it is the best solution or not simply copying the missing class from the 8.5.6 codebase into v9RC4 resolves the above.

Hi,
confirmed.
Copying the file \concrete\src\Permission\Key\GatheringKey.php from 8.5.6 to \concrete\src\Permission\Key\ of 9.0.0 RC4 makes the update work until it throws #9881
Olaf

confirmed
In Container.php line 875:
  Target class [\Concrete\Core\Permission\Key\GatheringKey] does not exist.

In Container.php line 873:
  Class \Concrete\Core\Permission\Key\GatheringKey does not exist

after copying of old concrete/src/Permission/Key/GatheringKey.php update continues
until it fails at
PHP Fatal error:  Trait method registerAssets has not been applied, because there are collisions with other trait methods on Concrete\Theme\Atomik\PageTheme in .../concrete/themes/atomik/page_theme.php on line 14

This has been fixed in the 9.0rc branch and will be released in the next release candidate.


Essence of Murmur name doesn't fit in the Artifact card

@TracyTheBoy I think you reported this, right? What's your screen resolution? I don't get the issue on my end.

@TracyTheBoy I think you reported this, right? What's your screen resolution? I don't get the issue on my end.

WQHD -> 2560 x 1440

From research this is a resolution issue and I can't do anything about it.


Process env substiturion in ADD, COPY commands

In a Containerfile Commands like:
COPY --chown=${NB_USER}:users stuff /stuff
The ${NB_USER} needs to be substituted from the environment.
Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

This should fix https://github.com/containers/buildah/issues/1806

@TomSweeneyRedHat @nalind PTAL

@bparees PTAL

can we get a test?

I was doing the test in buildah, not here.

I was doing the test in buildah, not here.

ok
/lgtm


Roadmap to Inclusion with Python?

@sethmlarson: In the project ReadMe, you state the following:

Long-term the hope is to make truststore the default way to verify HTTPS certificates in pip and to add this functionality into Python itself.

Since you're actively working within the PSF on projects including urllib3 and requests, you do seem to be in a good place to drive this kind of change.  Do you have a high-level roadmap toward making truststore inclusion a reality?  What can the community do to help?
Many thanks to you and your contributors for all your hard work!

Thanks for the kind words! The Sovereign Tech Fund has an active engagement with Trail of Bits and PyPI/Python that includes work that fits the description of what you're looking for. Quoting the linked page:

The Python programming language includes the ssl module, which exposes an SSL/TLS API. This API is widely adopted in the Python ecosystem due to its default availability, but also presents significant usability, security, and maintainability risks. This effort will help revive the Unified TLS standardization effort, include much needed updates to the API from the last 6 years, and deprecate APIs that have replacements. This would have a substantial impact on the overall health, usability, and maintainability of the Python standard library.

The Unified TLS standardization effort (ie PEP 543) is what Truststore is based on originally and having spoken to @woodruffw I believe that it would be included in this project. Since this work is already funded through Trail of Bits it's unlikely that I'll personally be leading it, although I will be helping any way I can!
Hope that answers your question :)

Thanks for the ping @sethmlarson!
To confirm on my end: my team will be working on a successor PEP for the ssl module, which will include trustscore in its scope. My hope is to have more public information on that in the next month or so.

Going to close this issue as complete, thanks for raising! :rocket:

For anyone looking for an update on @woodruffw's progress regarding the ssl successor PEP, strap in...
https://discuss.python.org/t/pre-pep-discussion-revival-of-pep-543/51263


Broken Link to Product Feedback

There is a broken link when clicking "This product" under the feedback section.
Error 404: No match found for '/spaces/21/index.html'
Seems like it might should open: https://developercommunity.visualstudio.com/report?space=21&entry=problem

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

ID: 5c2c2355-60a5-d53f-2c72-8f032c1b8cf2
Version Independent ID: 711bf22d-99c9-51b2-382c-e095bdb2c37f
Content: Resource limits & constraints - Azure DevOps
Content Source: docs/integrate/concepts/rate-limits.md
Product: devops
Technology: devops-ecosystem
GitHub Login: @roferg
Microsoft Alias: kaelli

@davislabs Thanks for your feedback; we appreciate it. You can submit issues related to overall site experience, or suggestions for improved site functionality or design, at https://aka.ms/sitefeedback/.


AlternateValues/Identifiers for Community objects.  Identifier displa…

STUB
Added

GeographicAreas autocomplete references alternate values

Changed

Alternate values can be used on GeographicAreas, they are shared across projects [#2506]
Global identifiers are shared across projects
Optimized identifier next/previous, not fully resolved [#3078]

Fixed

Cross-project local identifiers incorrectly displaying

Data

Migrates many annotations on Community data to be accessible across projects

Codecov Report

Merging #3082 (ad68c79) into development (02ec95d) will decrease coverage by 19.71%.
The diff coverage is 53.48%.

:exclamation: Current head ad68c79 differs from pull request most recent head 3eb668d. Consider uploading reports for the commit 3eb668d to get more accurate results

@@               Coverage Diff                @@
##           development    #3082       +/-   ##
================================================
- Coverage        86.89%   67.18%   -19.72%
================================================
  Files             1898     1502      -396
  Lines            67954    44945    -23009
================================================
- Hits             59052    30196    -28856
- Misses            8902    14749     +5847

Impacted Files
Coverage Δ

app/controllers/alternate_values_controller.rb
30.00% <0.00%> (-46.67%)
:arrow_down:

app/controllers/identifiers_controller.rb
34.32% <0.00%> (-38.81%)
:arrow_down:

app/helpers/alternate_values_helper.rb
35.89% <0.00%> (-14.11%)
:arrow_down:

app/helpers/annotations_helper.rb
26.08% <0.00%> (-65.22%)
:arrow_down:

app/helpers/sqed_depictions_helper.rb
21.50% <0.00%> (ø)

lib/queries/helpers.rb
33.33% <ø> (-33.34%)
:arrow_down:

app/models/concerns/shared/identifiers.rb
41.81% <12.50%> (-56.26%)
:arrow_down:

app/helpers/identifiers_helper.rb
31.14% <13.33%> (-37.38%)
:arrow_down:

app/models/concerns/shared/is_data/annotation.rb
69.76% <22.22%> (-22.55%)
:arrow_down:

app/models/geographic_area.rb
41.91% <75.00%> (-36.55%)
:arrow_down:

... and 749 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Bad scrolling performance

Hello. We recently upgraded our cluster from v7 to v8 and had to migrate from olivere/elastic package to this official client at some service.
But after that we met serious performance degradation, service started responding 6-8 times longer than with client we used before (after reverting to olivere/elastic degradation is gone so this is confirmed).
Our code is pretty simple, we just scroll searches in goroutine and push data to a channel, see code below:
this is how client created
c, err := elasticsearch.NewTypedClient(elasticsearch.Config{
	Addresses: []string{makeEsURL()},
	Username:  cfg.EsUser,
	Password:  cfg.EsPass,
})

this is how we build initial query
esResults := make(chan esResult, 1)
...
scroll := es.Search().
	Index(r.GetIndex()).
	Raw(strings.NewReader(r.GetQuery())).
	Size(cfg.EsScrollSize).
	Scroll("15s")

err := scrollEsQuery(ctx, scroll, esResults)

this is how it is processed
func scrollEsQuery(ctx context.Context, scroll *search.Search, esResults chan<- esResult) error {
	var scrollID string
	res, err := scroll.Do(ctx)
	if err != nil {
		return err
	}
	if len(res.Hits.Hits) == 0 {
		return nil
	}

	esResults <- newEsResult(res.Hits)

	if res.ScrollId_ != nil {
		scrollID = *res.ScrollId_
	}

	defer func() {
		if scrollID != "" {
			es.ClearScroll().ScrollId(scrollID).Do(gCtx)
		}
	}()

	for {
		res, err := es.Scroll().ScrollId(scrollID).Scroll("15s").Do(ctx)
		if err != nil {
			return err // something went wrong
		}
		if res.ScrollId_ != nil {
			scrollID = *res.ScrollId_
		}
		if len(res.Hits.Hits) == 0 {
			return nil
		}

		select {
		case <-ctx.Done():
			return gCtx.Err()
		case esResults <- newEsResult(res.Hits):
		}
	}
}

Code is pretty simple and i can't understand what can cause such a big performance difference, am I doing anything wrong?

Hi @hotrush
I've tested your snippet and something comes to my attention, you are passing a raw request and setting the size at the same time. Size is trying to be set in the body but fails because raw takes precedence. Hence size is not properly propagated to the body of the request and you are effectively returning the full match of your request on the first call.
Can you check this assumption? If that is so I'll work on a way of preventing that.


Session Key Info is Wrong

https://docs.substrate.io/fundamentals/accounts-addresses-keys/#specialized-accounts
Most of this is incorrect. For starters, there are no "session accounts".

The session account represents the public/private key pair used by validators to sign consensus-related messages. The session account is not intended to control funds. These keys are also defined generically in the Session pallet and made concrete in the runtime. To create the session account key pair, you must attest that the account acts on behalf of your stash account and nominators by signing a transaction with your controller key and publishing the session certificate on the chain. You can generate and register new session keys on chain using a session.setKeys transaction. You can change session keys using the author_rotateKeys RPC call.

@joepetrowski, thanks for pointing this out. The information came from an older article about session keys. I think I've heard that controller keys/accounts were being phased out.
Should that whole Specialized accounts section just be deleted as too Polkadot-specific?

Which older article? The last article I knew about them was this one from 2020.
We have discussed substituting stash/controller for another proxy type, but I'd leave that out; I don't know of any concrete plans. I logged this issue specifically about the session key info.

The session account

There is no account. The PR above points this out explicitly. The entire purpose of the set_keys transaction is to connect the session keys with an account.

represents the public/private key pair

Can just be "Session keys are a set of private keys used by nodes to sign consensus-related messages." (I would even consider removing "consensus-related" since you could argue that not all messages are consensus-related, but generally the messages relate to consensus or consensus-related roles, like collation.)

The session account is not intended to control funds.

"Session keys are not intended to control funds." (How can an account control funds?)

To create the session account key pair, you must attest ...

Huh? How does attesting create a key?

by signing a transaction with your controller key and publishing the session certificate on the chain.

The transaction is, in effect, the certificate. It's a signed message from one key (representing a controller account) with a payload of other public keys that says, "these keys sign messages from my node."

You can generate and register new session keys on chain using a session.setKeys transaction.

How does making a transaction generate keys? It only registers them, you need to generate them by telling your node to generate new keys (or you can generate them how you like and inject them to the node).

You can change session keys using the author_rotateKeys RPC call.

This just generates new keys in a node. They won't actually be used until you do a set_keys transaction to tell the chain that your node is now using these new keys.

There was a somewhat different article from 2021, but I am pretty sure I'm the one who butchered the reference to session accounts instead of session keys in an (probably misguided) attempt to standardize the language around references to accounts and key pairs. I'll take a stab at cleaning this up but always appreciate your help in getting the info right. Hope it's okay for me to tag you to take a look at the revision.

session accounts instead of session keys in an (probably misguided) attempt to standardize the language around references to accounts and key pairs.

But why? These are completely different concepts. It's like trying to standardize the language around locks and doors. Locks can be used for lots of different things (doors, bikes, safes, luggage, etc.) and doors can have many ways to secure them (locks, security cameras, alarms). Just because people happen to put locks on some doors doesn't mean that doors are locks.

Hope it's okay for me to tag you to take a look at the revision.

Yes, no problem.


Cannot run production build for ejected projects

Problem
I think title is quite self-explanatory here. Before app ejection I run
ng build -prod
For building production app. Unlike usual build this minify my project and does some other things.
After ejection there is a webpack configuration which as I think corresponds to usual build. There's no webpack configuration for production environment.
Possible fix
Project ejection should create production webpack configuration that will reflects ng build -prod behavior.  And add webpack --config -p webpack.config.prod.js to scripts in package.json

You can do this by using ng eject --prod. The eject command runs with the same flags as the build command.

I've already figure this out. That's why I closed the issue ;)

OK I think don't understand how eject meant to be... Why can't I eject the project and have a development AND production environment afterwards?
I thought eject is like you do it once and then you cannot use angular-cli features anymore, but you're more flexible in configuration? So how am I supposed to make custom changes (https://github.com/angular/angular-cli/issues/5362#issuecomment-310298275) and build for development and production afterwards?
Thank's for every help!

@creat-or you can it's just how you do so can get opinionated pretty quickly.
One common approach is to to have an environment variable , like NODE_ENV and set it prior to builds.  Then in your webpack config test against it like const isProd = process.env.NODE_ENV === 'production' ? true : false;
Then later in your config you can use isProd to make choices about what plugins to use etc...
Taking a deeper dive would go waaay off topic.  I bet there are blog posts about this somewhere.

i think in an angular-cli ejected project the command yarn run build (npm run build) must be smart and read arguments --prod -aot and pass them to webpack. That way things will run better and we stay on the same path as ng build options

Can we re-open this? @dagi12.
Also whenever you do an ng-eject --prod you must manually remove all package.json scripts and the webpack.config.jsfile in order for it to work.

Reopened

+1

@hikumealan I think the code coverage in CLI works out of the box, at least with HTML/lcov.  Plus IIRC the karma config is customizable with or without ejecting.

I ran into this issue after running ng eject  and found this issue. It isn't very difficult to work around, just more hassle than it should be and shouldn't require a workaround at all.
IMHO running ng eject should spit out a webpack.dev.config and a webpack.prod.config. It should also create npm scripts for build:prod, and watch, in addition to the other scripts it creates.
So until an official solution presents itself, here's my workaround.

run ng eject
rename webpack.config.js to webpack.dev.config.js
delete all the npm scripts in package.json
run ng eject --prod
(optional) rename the new webpack.config.js to webpack.prod.config.js
setup your npm scripts in package.json
run npm i

And here is what my npm scripts look like when I'm done.
"scripts": {
    "build": "webpack --config webpack.dev.config",
    "watch": "webpack --watch --config webpack.dev.config",
    "build:prod": "webpack --config webpack.prod.config",
    "start": "webpack-dev-server --port=4200 --config webpack.dev.config",
    "test": "karma start ./karma.conf.js",
    "pree2e": "webdriver-manager update --standalone false --gecko false --quiet",
    "e2e": "protractor ./protractor.conf.js"
  }

I really dont want to maintain different web pack settings and I need to have custom options in it
why is the eject not creating something that can manage different environements, at least dev/prod

eject functionality is no longer available in the latest version (6.0+).  For custom webpack configurations the following unofficial add-on is a suggested solution: https://github.com/manfredsteyer/ngx-build-plus


Prevent concurrent writes

Concurrent writes might lead to invalid JSON being saved in the cookie jar.
Hopefully fixes #1883 .

Shouldn't this be backported to the master so it'll be available for the 6.x version too?

Yeah, that's a good idea. Are you up for it?


s2n can't self-talk

Problem:
Our tls13 integration tests only verify that s2n can talk to openssl.
However, tls13 can't talk to itself, either in the unit tests or the integration tests, or just by running the command manually and tweaking arguments. The s2n_tls13_handshake_test looked like it was successfully performing most of the handshake, but was actually set up wrong and fails after the ServerHello. I have a corrected version here that can reproduce the problem.
Decryption of handshake records is failing. Specifically, EVP_DecryptFinal_ex is failing, and if you trace the failure down into OpenSSL code, it's because the encryption tags do not match. It fails for all tls1.3 cipher suites.
What I've tried:

Using ChaCha20 instead of AES. Same error, different file :(
Resetting the session key to a known value for both client and server before the EncryptedExtensions are sent. Same error. :(
Copying the output of the server writing the encrypted record back to the server, so that the server tries to decrypt it instead of the client. Same error. :(
Removing all calls to set conn->server/client to conn->secure from s2n_handshake_io.c, basically forcing the handshake to be unencrypted. That worked, although it's not particularly helpful.

The best guess I have is that we're setting up conn->secure wrong, but I have no idea how or where. It might be a clue that we CAN talk to openssl; whatever mistake we're making, openssl is correcting for.
Proposed Solution:
I have absolutely no idea, but the problem is consistent and easy to reproduce.
Someone with a better understanding of block ciphers + the low level details of how s2n configures them should pull down https://github.com/lrstewart/s2n/commit/1de2f5e61da63b5798b74fac4e9b82cb2680539e and try to get s2n_tls13_handshake_test.c to pass.

see the comment on PR #1547:

The s2n_conn_update_required_handshake_hashes function has no case label for TLS1.3 so is leaving the required_hash_algs struct empty.

looking at the code, the naming is off, but tls12_prf_alg is correctly set with the HKDF hash for the TLS1.3 cipher suites.

perhaps we should rename that member.

Closed by #1547


Cannot use GHC 7.10.1-RC2 with xmonad (or any environment)

I understand GHC 7.10.1 isn't production-ready yet, but I think the issue is on our end.
I get this error message when attempting to use GHC 7.10.1-RC2 to rebuild my system, after every library individually compiled and installed to store :
http://lpaste.net/119368
This is what my configs look like:
https://github.com/MP2E/nix-projects/commit/dd0048842f9f7d7ce7a953ae056a88cd86702460
Very similar errors happen if I try to install haskellEnv(also in that commit) via nix-env. Both of these environments work fine under GHC 7.8.4

These errors are caused by GHC's wonderful "non-determinism" feature. My guess is that you mixed up locally built binaries with ones downloaded from Hydra. @Fuuzetsu might be interested in asking you some questions because he's working on fixing that issue in GHC. Anyway, the only way to remedy this is issue is to run nix-store --delete <GHC> where GHC is the store path of your local 7.10.1-rc2 compiler. This will delete GHC and all package it has built from your system. Now re-build your your environment and hope for the best. :-)
Anyway, this issue is not related to Nix; it's a "feature" of GHC and this issue occurs randomly with all versions of GHC, unfortunately.

I am indeed interested in such cases but this one is something we can not fix easily: before GHC 7.10.x, the non-determinism occured often. This means that your GHC 7.10.x was bootstrapped with a compiler that produced ‘unexpected’ ABI hashes: it is just the 7.8.4 (and earlier) problem applied to GHC 7.10 core libs. So as peti says, the only thing you can do is get rid of that build and try again, preferably getting a binary from Hydra or whatever cache you use. Once you obtain a GHC 7.10.x with ABIs expected by rest of packages, it should be smooth sailing: if you have ABI problems compiling stuff with GHC 7.10 itself then that is of great interest to me and I would love to hear about it, get the contents of the relevant store paths and any further info.
I don't really see a way out of this particullar issue except trying until you get good hashes for your 7.10. We could do something like compile our 7.10 with a binary 7.10 but that seems a bit silly.
The GHC Trac number is 4012 if you're interested in looking at the problem.

Thanks for the feedback, your explanations make a lot of sense, however I still cannot get any environments to build. It keeps giving the same error.
This is what I tried:
1st attempt

I used 'ls /nix/store/ghc-7.10' to get every ghc 7.10.1 path from the store(I found 2)
I used nix-store --delete to delete both of the store paths and a few other paths as well
Rebuild, note that build cache is grabbed this time

2nd attempt

delete the 2 ghc 7.10 store paths using the above steps again
Rebuild, pass option 'use-binary-caches false'

3rd attempt

Uninstall current GHC 7.8.4 environment from user, remove all traces of haskell and xmonad from configuration.nix, rebuild
Reboot and run 'sudo nix-collect-garbage -d'
Check /nix/store is empty of Haskell packages via 'ls /nix/store/haskell && ls /nix/store/ghc'
Rebuild, noting that build cache is grabbed again

4th attempt

Same as 3rd attempt except passed option 'use-binary-caches false'

I'm not sure if this is still the problem described, so I'll reopen this issue just to be safe.

When nix-store --delete is run, does it warn you that some paths could not be deleted because they're still "alive"?

 I'm not sure how to explain that phenomenon. The use-binary-caches false flag should guarantee that your system is consistent. As far as I can tell, it should be impossible for that error to occur when you've build the Haskell compiler and all packages locally.
I'll have to think about this.

Okay. The problem is that some well-known troublemaker has broken the GHC 7.10.1 derivation in https://github.com/NixOS/nixpkgs/commit/a9b774204b6570593635cfb9f46b20cc2f9246f1: Nix and the compiler disagreed on its version number, and as a result the wrapper script failed to symlink the compiler's base libraries into the generated environment. That issue has been fixed in 86753ed.
The current master branch should work fine for you.

@peti Sorry about that...


Setup BookStore website

What does this PR do?
This PR is raised to implement the following features: 👍 :

[x] Set up project
[x] Add linters files.
[x] Add react-routes-dom.

Description of the task to be completed ↓↓

Add two routes to bookstore.

How should it be tested
Clone the repository
git clone https://github.com/SamTush/bookstore.git

Navigate to the folder
cd bookstore

Checkout the branch
git checkout feature/setup

How should it be run
Run website in browser.
  npm start

Thanks for reviewing my PR 😊

Thank you for reviewing my PR @tufoinnkuo10 👍🏽. Happy coding 😎

Thank you @MaganaAsiati for reviewing my PR👍🏽. Happy coding 😎