What's the expected GA date for this feature?

What's the expected GA date for this feature?

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

ID: 9a558a9e-10d0-ea34-8780-d9084f87f952
Version Independent ID: 60dda4e0-7630-f358-aa3a-6a992eae61e2
Content: Managing the Azure Storage Lifecycle
Content Source: articles/storage/blobs/storage-lifecycle-management-concepts.md
Service: storage
GitHub Login: @yzheng-msft
Microsoft Alias: yzheng

@sopelt , When it is globally available you can check here in the official documentation of blob life cycle management and also you can subscribe to the blob here to get notified for the latest updates of blob life cycle management. Hope this helps you !


Database Design

Which database design do we need for this app?
Which models, and with which fields?
We are going to use MongoDB (NoSQL), in Node.
Mongoose is a good option for this.
You should provide js files containing Mongoose Schemas describing the models and their relationships.
You have 3 days (due date 16/02/2016)
Make a PR to this repo, adding the files to design/models folder
Example of folder structure for this PR:
design
  models
    user.js
    hospitals.js
    ...
    another_model.js

@lucasbsilva and @tzdesing will work together on this issue

Which server will be hosted the database ? I would like suggest Firebase, because we can create a free account. React has a good integration API for Firebase as well.

@keuller never tried Firebase but I guess we can use it as long as it's easy to export our data if we need to scale later.


Update babel-eslint dep

after npm install and npm run lint causes "TypeError: Cannot read property 'visitClass' of undefined".(https://github.com/babel/babel-eslint/issues/243) So updated it with the newest version.

The correct version for us to use is 4.x, not 5.x.


Review modifier options for seqvar ACMG tool

Is your feature request related to a problem? Please describe.
The selection options for the seqvar ACMG tool are not 100% compliant with most recent manuscripts.
Describe the solution you'd like
We should refine the options for selecting modifiers in the seqvar ACMG tool.
Describe alternatives you've considered
N/A
Additional context

#291
#321
#324

Newest ACGS Guidelines change a lot of stuff again: https://www.acgs.uk.com/media/12443/uk-practice-guidelines-for-variant-classification-v1-2023.pdf

Please just allow all grades (Very Strong, Strong, Moderate, Supporting) on all criteria. This is most flexible and anything outside sane standards should just create a warning message for the user.


how to distribute aab file

i would like to distribute app bundle through this plugin but i can't.
i explored this document, it does not have such a function.
does it have this way?
or do you have a plan it will be implemented?

i got to know firebase_app_distribution doesnt have this way
i will close

platform :android do
desc "My awesome app"
lane :distribute do
build_android_app(task: "bundle", ...)
# build_android_app is a built-in fastlane action.
    firebase_app_distribution(
        app: "1:123456789:android:abcd1234",
        testers<EMAIL_ADDRESS><EMAIL_ADDRESS>        release_notes: "Lots of amazing new features to test out!",
        android_artifact_type:"AAB",
      android_artifact_path: '../build/app/outputs/bundle/release/app-release.aab',
    )

end

end

platform :android do
desc "My awesome app"
lane :distribute do
build_android_app(task: "bundle", ...)
# build_android_app is a built-in fastlane action.
    firebase_app_distribution(
        app: "1:123456789:android:abcd1234",
        testers<EMAIL_ADDRESS><EMAIL_ADDRESS>        release_notes: "Lots of amazing new features to test out!",
        android_artifact_type:"AAB",
        android_artifact_path: '../build/app/outputs/bundle/release/app-release.aab',
    )

end

end


Fix docs linter

https://github.com/puppeteer/puppeteer/commit/4205ff79d93c1d27b9cadde6f56c19be04397abd
removed the header in the Mouse class documentation, but the linter
requires the reference to that header to be removed as well.

Cheers!


Categories in Loader GUI

Goal
Visually organise assets according to a "category" in the Loader, such as "Environments", "Characters", "Props", etc.

Mimick the look of Launcher.


v1.1.0 changes the focus to browsers

v0.13.22 and v1.0.0 keep the focus of IDE after running tests with watch mode. v1.1.1 changes the focus to browsers. So I must change the focus to IDE everytime. Its behavior is very unuseful.
Expected behavior
Keep the focus.
Actual behavior
Change the focus to browsers.
Enviroment Details

Karma version (output of karma --version): v1.1.0
Relevant part of your karma.config.js file

module.exports = function (config) {
  config.set({
    basePath: '',
    client: {
      useIframe: false
    },
    frameworks: ['mocha'],
    files: [
      { pattern: 'https://cdn.polyfill.io/v2/polyfill.min.js', watched: false, served: false, included: true },
      { pattern: 'node_modules/power-assert/build/power-assert.js', watched: true, served: true, included: true },
      { pattern: 'node_modules/lodash/lodash.js', watched: true, served: true, included: true },
      { pattern: 'node_modules/benchmark/benchmark.js', watched: true, served: true, included: true },
      { pattern: 'dist/*.js', watched: true, served: true, included: true }
    ],
    exclude: [
    ],
    espowerPreprocessor: {
      options: {
        emitActualCode: false,
        ignoreUpstreamSourceMap: true
      }
    },
    reporters: ['dots'],
    coverageReporter: {
      dir: 'coverage',
      subdir: function (browser, platform) {
        return browser.toLowerCase().split(' ')[0];
      },
      reporters: [
        { type: 'lcov' },
        { type: 'text-summary', subdir: '.', file: 'summary.txt' }
      ]
    },
    autoWatch: true,
    browsers: ['Chrome'],
    browserNoActivityTimeout: 100 * 1e3
  });
};

Steps to reproduce the behaviour

Clone https://github.com/falsandtru/spica
npm i && npm i<EMAIL_ADDRESS>gulp watch
Update any source files in the src directory.
Karma runs incremental tests.
Karma changes the focus to browsers.

What OS are you using? I tried to reproduce this behaviour on latest MacOS 10.11.5 but it works perfectly fine. Firefox and Chrome are both opened in the background and do not get focus.

I'm using win7 x64 and node v6.2.1.

v1.1.1 works completely. thanks!
Note: 1.0.0 and 1.1.0 always open the new blank tab. Then browsers always has 2 tabs. 1.1.1 is not.

Sorry, not fixed. Only when I set the client.useIframe = true, this issue will be occurred.


Replace role with required permission

Using a role for invite managers to access commands seems unintuitive, why not just check for Manage Server/Administrator perm?

I’ll make it so it’s both in the next release.

This has been added as of release v2.0.4


New Trait Bounds

One of the behaviors inherited from pijul are many of the original trait bounds. Unfortunately these make things quite hard to improve various aspects of the implementation. In particular for instance the main inputs for the diff functions look something like this:
pub fn diff<Old, New, D>(
    d: &mut D,
    old: &Old,
    old_range: Range<usize>,
    new: &New,
    new_range: Range<usize>,
) -> Result<(), D::Error>
where
    Old: Index<usize> + ?Sized,
    New: Index<usize> + ?Sized,
    D: DiffHook,
    New::Output: PartialEq<Old::Output>,
{
  // ...
}

There are two issues with this that need to be solved:

Old::Output and New::Output are only required to be PartialEq to each other.  In practice however it's significantly more useful for them to be the same type. This for instance allows one to put the items into a HashMap<&'a T, usize> for de-duplication. Patience gets around this currently by handlign each side separately and then to compare by the original value again which is unnecessary wasteful.
There is no relationship of old to old_range and new to new_range. This both makes the code less than ideal to read but it also means that it's very hard to get rid of the bounds checks. In practice there is an argument to be made that any diffing shall be going through a deduplication step first at which point we might as well require things to look more like slices. Maybe the trait bounds can stay like this externally as a result.

The first issue is not as problematic. There is now a type called IdentifyDistinct which can work with the current trait bounds and still produces unique IDs for them.


Fix pluralization in the worker bootstrap lab

This lab sets up worker-1 by hand. The next lab sets up the rest.

Closed with no explanation. How rude.

this can be applied for any n of worker nodes. and u can submit a new request with only this "In this lab you will bootstrap the first worker node. We already have Docker installed."

This makes sense. Thank you!


Translate French

Hi,
Can you add the translate French in you module, see the file in Att.
Thank you
Traduire module Better Roof.txt

done, use a pull request next time please


First person camera improvements & raw mouse input

Great PR! I'm looking forward to trying this out. 😄

bors r+


Use of axios lower than 1.6.0 results in CVE-2023-45857

This module is using<EMAIL_ADDRESS>https://github.com/logdna/logger-node/blob/87463cbff9f6e64db596ce1f450bdd064bb1b22d/package.json#L109
This makes it vulnerable to CVE-2023-45857:

https://security.snyk.io/vuln/SNYK-JS-AXIOS-6032459
https://github.com/axios/axios/issues/6006

Moving to at least 1.6.0 resolves the CVE

Thanks for reporting this, @andyedwardsibm .  This showed up in our security scans as well, and the notifications for that system have been made louder so we're aware of issues moving forward.


Thanks

Just a big thank you from me, that's all. I've been trying to get a working GPU accelerated Pytorch install for my sm_30 card for days and have had a total nightmare.
Just getting a working CUDA 10.2 installation on my Ubuntu 22.04 O/S has been a nightmare enough with dependency issues from both the Ubuntu and NVIDIA packages, which I could only resolve by using the 18.04 repo and a custom built dummy package to trick it into being happy with my driver and X server versions.
Then, having been reassured from multiple sources that building Pytorch from source for CUDA 10.2 with an sm_30 GPU was possible and finding out it's not as straight forward as I was lead to believe and a lot of misinformation on exactly what version supports it (if any), I came across your project, tested the image and it worked, proving to me that it WAS possible just at the point I was about to give up.
I'm not using your Docker image, but the Dockerfile has given me the information that I need  - basically that I can build NCCL for an sm_30 architecture and then build Pytorch with USE_SYSTEM_NCCL to avoid the compilation error I was getting due to the lack of the __funnelshift_r() intrinsic in 3.0 GPUS.
I don't know how much work you put into this, but there's at least one person here who appreciates your effort because I have been pulling my hair out trying to put this jigsaw puzzle together.
I might be jinxing myself as the build is still working and I have had so many instances where I thought I'd managed to get somewhere only to be presented with another compilation error, and I still don't understand how CuDNN can work because NVIDIAs support matrix says "no" for sm_30, but it has at least allowed me to move forward on to my next challenge.
So - thank you!

Glad to hear that my efforts saved someone else's time!


Update aws-msk-iam-auth to 1.1.8

About this PR
📦 Updates software.amazon.msk:aws-msk-iam-auth from 1.1.4 to 1.1.8
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (1.1.4).
You might want to review and update them manually.
CHANGELOG.md

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.msk", artifactId = "aws-msk-iam-auth" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "software.amazon.msk", artifactId = "aws-msk-iam-auth" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

Superseded by #483.


Issues when prerendering subfolder pages

I'm working on deploying a site and I have found that if any page in a subfolder route (like /src/routes/about/faq.svelte or similar) is prerendered then directly accessing the page will throw an AWS access error. And non pre-rendered pages in the same folder will entirely fail to load.
This is because the CloudFront Distribution Behaviors are setup to load /folder/* (in this example /about/*) from the s3 origin.  Only the default behavior runs through the @edge lambda. These sub folders will not load the index.html file. For example /about/faq won't load when directly accessed since S3 will try to serve s3:bucket/about/faq.html however SvelteKit renders it out as /about/faq/index.html. This is partly an AWS/CF/S3 issue.  However, I would like to try and solve this.
Solution Part 1
When creating the static file behaviors for the CF Distribution process non "reserved" static asset folders (like _app, assets, etc), recursively and add the s3 behavior only to each individual prerendered page. This should force the dynamic pages to fallback to the lambda and render properly.
But this only solves one of the issues
Solution Part 2
Update the lambda to re-write the URL to include the /index.html at the end if the page is a pre-rendered page rather than try and render the page. So it will fetch it from the right place.
This does force all sub-pages to go through the lambda but directly accessing sub-folder pages does not work currently if you want to pre-render them at all.
Part 2 Alternate Solution
An alternate approach to the second part to try and avoid using the lambda at all would be to rename the files before/when they are uploaded to s3 so it does not have to load index.html but just the expected file. This just hit me while I was writing this up so I haven't entirely thought through it. There could be collision issues maybe? But its another approach at least.
Are there any thoughts on these approaches? Have they been tried/considered before and maybe there are issues I'm not thinking about?

I expected that CloudFront configuration would be the most difficult part to get right, but I don't have a prepared plan for it.
One more partial solution in addition to the ones you mentioned would be to preprocess requests with a CloudFront function to make it easier to configure the CF behaviors.
But anyway, first I'll create a minimal SvelteKit app that reproduces the problem. So far I've used mostly the demo app and it's clearly not sufficient any more.

Added minimal site that demonstrates the problem (deployed here: https://d3a63laq3irdpc.cloudfront.net)

@KayoticSully
I started with renaming the pre-rendered files so S3 can server them directly. I think collisions are quite unlikely.
Having pre-rendered and dynamic pages or endpoints in same folders is more difficult.
Adding behaviours for all pre-rendered pages is problematic because there could be thousands of them and behaviours have soft limit of 25.
Would it be terrible if the adapter checked that and refused to build if pre-rendered and SSR were mixed under same top level route?
Are you using lambda@edge or regular lambda? It might be possible to place lambda@edge SSR to origin request handler so that it handles the request if it hits dynamic page or endpoint, and otherwise passes the request on to the origin (s3). If that worked, it would allow mixing pre-rendered and dynamic pages in same folders. But with that approach regular lambda doesn't fit to the same pattern.


对数字的朗读效果不好

Describe the bug
包含较多数字，如12345678或者2022年12月29日，的句子，朗读效果差。

this is due to frontend process. we will use wetextprocessing to replace it, or you can convert it to character manually. these cases cannot be numerated, so we will not focus on fixing these bug

we have used wetextprocessing to replace ttsfrd, update the code and install requirements to see whether it fix the bug


Add a Dockerfile to be used on pre-commit jobs

Once we merge this Dockerfile we can validate if Prow image promotion can provide this image to other operator's repo.

/lgtm


Figure out way to add links to indicators from the Campaign page

Currently we only list the indicator itself and don't include any associated metadata (specifically the _id field) to take us to /network//info. We need to figure out a way to grab the _id field for the indicator and then pass that to the function so we can get back to the object.

Fixed in latest release. Added a new route to search the mongo database by object instead of _id


bump

needs https://github.com/OpenVoiceOS/ovos-ocp-audio-plugin/pull/86
needs https://github.com/OpenVoiceOS/OVOS-workshop/pull/112
needs https://github.com/OpenVoiceOS/ovos-PHAL/pull/20

some issue was introduced in the past 9 ovos workshop commits, i had this branch checked out and tests pass  (both here and in workshop) with it
https://github.com/OpenVoiceOS/OVOS-workshop/pull/113
except for undiagnosed get_response failing in ovos-core
@NeonDaniel any idea?


chore: upgrade nvm to 8.11.0

Closed as it is overridden by https://github.com/imin-ltd/speck/pull/33


Use integrated queries for searches instead of 'doc:' separation.

Use integrated queries instead of doc: separation to search for jobs by state point and document.
Requires https://github.com/glotzerlab/signac/pull/188 .

I guess the failing unit tests are to be expected since I broke backwards-compatibility. I'm going to wait for input from @bdice before proceeding.

@csadorf Thanks for this! Let's settle on an API for the signac PR before we deal with this. This PR would also change the version requirement of signac in its current state - perhaps there's a good fallback?

@csadorf Thanks for this! Let's settle on an API for the signac PR before we deal with this. This PR would also change the version requirement of signac in its current state - perhaps there's a good fallback?

I think we should be ok with an backwards-incompatible change here. After all, dashboard is in an early development stage.

@bdice are you OK with closing this for now? We can reopen later, but as we're doing with other signac projects I think we should close PRs that are stalled until they're ready for review again (and we're stalled here because the corresponding signac PR is closed).

@vyasr, yes. Closing.


TDD is not working on my windows machine

Hi @prashaantt ,
I have Visual Studio Code v1.15.1 with Node TDD plugin. I can see the symbol in status bar which means that it is activated. However, it is not getting invoked at all. Am I missing something? It is not very clear from project readme.

Thanks,
Sanjeev

I'm sorry. This is a known issue. Until I have a proper fix published, please find a solution in this thread, which also tracks this bug.


Update task-set-5.md

Taking up Task 1 and 2.

@LoneWolf36 Only single task is allowed. If you complete it and there is still vacancy, you can take up another task.


Accept repository invites on behalf of users

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 78 (3.85%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 23.783%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

web/webserver.go
0
1
0.0%

scm/helper.go
0
3
0.0%

scm/fake.go
0
8
0.0%

scm/gitlab.go
0
14
0.0%

web/courses.go
3
20
15.0%

scm/github.go
0
32
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
2267

Relevant Lines:
9532

💛  - Coveralls

Codecov Report

Merging #590 (375d8e7) into master (e1a6703) will decrease coverage by 0.11%.
The diff coverage is 6.66%.

:exclamation: Current head 375d8e7 differs from pull request most recent head 2d5df92. Consider uploading reports for the commit 2d5df92 to get more accurate results

@@            Coverage Diff             @@
##           master     #590      +/-   ##
==========================================
- Coverage   21.82%   21.71%   -0.12%
==========================================
  Files          53       53
  Lines        7563     7622      +59
==========================================
+ Hits         1651     1655       +4
- Misses       5625     5677      +52
- Partials      287      290       +3

Flag
Coverage Δ

unittests
21.71% <6.66%> (-0.12%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

scm/fake.go
0.00% <0.00%> (ø)

scm/github.go
0.00% <0.00%> (ø)

scm/gitlab.go
0.00% <0.00%> (ø)

scm/helper.go
0.00% <0.00%> (ø)

scm/scm.go
0.00% <ø> (ø)

web/webserver.go
0.00% <0.00%> (ø)

web/courses.go
36.98% <6.25%> (-1.53%)
:arrow_down:

database/gormdb.go
69.07% <60.00%> (-0.50%)
:arrow_down:

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 e1a6703...2d5df92. Read the comment docs.


Update vendor.conf to correspond to vendor folder…

… and re-ran vndr on an empty vendor folder to make sure it maps
closely (and compiles).

Adds some README/LICENSE/… files (recent version of vndr do not
clean those anymore)
Update libtrust as the commit hash from Godeps.json does not
correspond to the vendor code
Same for kr/text and spf13/pflag

The only way to update dependencies is by updating the hash(es) in vendor.conf and re-run vndr. If there is any doubt, remove vendor folder before running vndr (to make sure we start from a clean state — especially important if we remove a dependency).
Closes #1204
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>

Thanks for updating this @vdemeester!  Ran this locally - LGTM!


How to shutdown the process bash or sh in k8s pod?

hello man:
May I ask you that when i use "gotty -w kubectl", i succeed entry into the pod, then i close the browser.In pod the bash or sh process do not shutdown.
How can i do it?
Thank you!

I also meet this issue. who can help us.

hello man:
May I ask you that when i use "gotty -w kubectl", i succeed entry into the pod, then i close the browser.In pod the bash or sh process do not shutdown.
How can i do it?
Thank you!

linux支持设置bash命令的关闭时间。你设置1个小时关闭就可以了。基础镜像改一下就ok了

hello man:
May I ask you that when i use "gotty -w kubectl", i succeed entry into the pod, then i close the browser.In pod the bash or sh process do not shutdown.
How can i do it?
Thank you!

linux支持设置bash命令的关闭时间。你设置1个小时关闭就可以了。基础镜像改一下就ok了

所以这里面需要改k8s管理镜像的bash/sh的自动关闭时间对吧？但我们的镜像很多，所有的都需要改吗？

hello man:
May I ask you that when i use "gotty -w kubectl", i succeed entry into the pod, then i close the browser.In pod the bash or sh process do not shutdown.
How can i do it?
Thank you!

linux支持设置bash命令的关闭时间。你设置1个小时关闭就可以了。基础镜像改一下就ok了

所以这里面需要改k8s管理镜像的bash/sh的自动关闭时间对吧？但我们的镜像很多，所有的都需要改吗？


[Task]: Correctly parse address

Currently the address is not being parsed from any deep link. This has to be fixed for the send and swapOut operation.

I used the wrong URL format, which is why it didn't work


v0.3.1

Codecov Report

Merging #117 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #117   +/-   ##
=======================================
  Coverage   68.55%   68.55%
=======================================
  Files          14       14
  Lines         795      795
=======================================
  Hits          545      545
  Misses        250      250

Impacted Files
Coverage Δ

bowtie/__init__.py
100% <100%> (ø)
: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 862fb0c...be92998. Read the comment docs.


Add information about how to cite software

As part of the #83 PR, @arfon brought up the point that we should add information about how to cite the software.
So, a PR should be put in that adds information about how to cite the software (e.g., bibtex), and/or a __citation__ method, and/or a CITATION file.

There is some interesting semi-recent discussion of how to cite (python) software at https://groups.google.com/forum/#!topic/python-ideas/RHBcpu1QNIA (including input from Guido).  This discussion from 6 months ago also reference https://github.com/adrn/CitationPEP (which is authored by several here, cough cough, including Arfon, Tom and Erik).
Around 8 months ago astropy made an addition to  __citation__ / CITATION (https://github.com/bsipocz/astropy/blob/f84c287f73e76984825fb5aabd73123f9c0cf9bf/astropy/init.py#L263).  The CITATION file contains text that suggests how to reference astropy including a bibtex entry.
I think https://citation-file-format.github.io might be a step too far right now and  not sure how much traction there is for it currently.
I don't see any citation information in the code for numpy and scipy currently. They both appear to include it in their documentation.


feat: initial draft for nextjs nested layouts

Related: #103
Start testing it:
yarn create r3f-app <next> my-app <tailwind|styled>? -ts? -b layouts-rfc
Introduces <Three/> wrapper which forces the client-side rendering and portal any children into the canvas

TODO:

Move folders to ./src as it's cleaner
Add <View /> example inside <Three /> with potentially a smooth scroll OOTB in the blob page

With Typescript yarn run dev gives this error message
error - ./src/helpers/components/Three.ts
Error:
  x Expected '>', got '{'
   ,-[/Users/username/git/shader-experiments/src/helpers/components/Three.ts:3:1]
 3 | import { r3f } from '@/helpers/global'
 4 |
 5 | export const Three = ({ children, ...rest }) => {
 6 |   return <r3f.In {...rest}>{children}</r3f.In>
   :                  ^
 7 | }
   `----

Caused by:
    Syntax Error

Import trace for requested module:
./src/helpers/components/Three.ts
./app/page.tsx
wait  - compiling /_error (client and server)...

Without Typescript yarn run dev works with a few warnings

updating to new Metadata API
default export is deprecated for Zustand
several useLayoutEffect warnings like this...

Warning: useLayoutEffect does nothing on the server, because its effect cannot be encoded into the server renderer's output format. This will lead to a mismatch between the initial, non-hydrated UI and the intended UI. To avoid this, useLayoutEffect should only be used in components that render exclusively on the client. See https://reactjs.org/link/uselayouteffect-ssr for common fixes.
at In (webpack-internal:///(sc_client)/./node_modules/tunnel-rat/dist/index.cjs.js:19:7)
at Three (webpack-internal:///(sc_client)/./src/helpers/components/Three.js:10:18)
at Lazy
at ScrollAndFocusHandler (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/layout-router.js:145:1)
at InnerLayoutRouter (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/layout-router.js:186:30)
at RedirectErrorBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/layout-router.js:343:9)
at RedirectBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/layout-router.js:349:29)
at NotFoundErrorBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/layout-router.js:375:9)
at NotFoundBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/layout-router.js:381:29)
at LoadingBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/layout-router.js:304:32)
at ErrorBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/error-boundary.js:69:26)
at RenderFromTemplateContext (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/render-from-template-context.js:10:34)
at Lazy
at OuterLayoutRouter (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/layout-router.js:21:30)
at Lazy
at div
at Layout (webpack-internal:///(sc_client)/./src/components/dom/Layout.jsx:13:19)
at Lazy
at body
at html
at ReactDevOverlay (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/react-dev-overlay/internal/ReactDevOverlay.js:61:9)
at HotReload (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/react-dev-overlay/hot-reloader-client.js:19:22)
at Router (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/app-router.js:45:23)
at ErrorBoundaryHandler (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/error-boundary.js:57:9)
at ErrorBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/error-boundary.js:69:26)
at AppRouter (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/app-router.js:23:13)
at Lazy
at Lazy
at ServerComponentWrapper (/Users/username/git/shaders/node_modules/next/dist/server/app-render.js:304:28)
at ServerComponentWrapper (/Users/username/git/shaders/node_modules/next/dist/server/app-render.js:304:28)
at InsertedHTML (/Users/username/git/shaders/node_modules/next/dist/server/app-render.js:1117:33)

Thanks for the feedback.
tunnel-rat PRs should silence the warning:
https://github.com/pmndrs/tunnel-rat/pull/17
https://github.com/pmndrs/tunnel-rat/pull/18
Regarding the props error, I can just remove it but we're currently investigating a potentially better implementation so let's wait a bit

they're in

Just tested the latest version.
With non-TS the useLayoutEffect warning is gone but I'm still getting a warning about zustand.
[DEPRECATED] Default export is deprecated. Instead use `import { create } from 'zustand'`.

With TS there's now a different error.
error - ./src/helpers/components/Three.ts
Error:
  x Unterminated regexp literal
   ,-[/projectname/src/helpers/components/Three.ts:3:1]
 3 | import { r3f } from '@/helpers/global'
 4 |
 5 | export const Three = ({ children }) => {
 6 |   return <r3f.In>{children}</r3f.In>
   :                             ^^^^^^^^
 7 | }
   `----

Caused by:
    Syntax Error


Panel not expanding while user is touching the screen.

I want to be 100% sure that panel slides to EXPANDED state no matter what.
However when user is in middle of a listview/viewpager scroll and possibly other touch interactions, the panel does not appear.
this is basically what happens:
onPanelStateChanged() called with: previousState = [COLLAPSED], newState = [DRAGGING]
onPanelSlide() called with: slideOffset = [1.0]
onPanelStateChanged() called with: previousState = [DRAGGING], newState = [COLLAPSED]

starts dragging and collapses instantly.
I can work around this with disabling touch events. By overriding dispatchTouchEvent(MotionEvent ev)to return true (without calling super) before setting setPanelState(Panelstate.EXPANDED) and until onPanelStateChanged()newState is EXPANDED.
however this seems super hacky and unreliable. Maybe you guys have more ideas how to tackle it?

I also got this error while scrolling a listview. I set a timer to auto-expand the panel after a fixed time. But when the timer end while I'm scrolling the listview, the Panel is not expanded and gets the same state as you showed.

I had the same issue because I was disabling the user from interacting with the panel and setting the state programmatically.  If the user clicked anywhere on the root layout while the panel was moving, the panel would get stuck and stop expanding or collapsing.
I was able to use @mtyy's suggestion and override the dispatchTouchEvent(MotionEvent ev) and only returning the super if the panel state was dragging.
@Override
public boolean dispatchTouchEvent(MotionEvent ev) {
   return this.getPanelState() == PanelState.DRAGGING || super.dispatchTouchEvent(ev);
}

In my case, when drawer is collapsing or expanding, a tap on the screen will stop the animation. My workaround, put a view (visibility:gone) above the sliding layout and apply the following actions:
`slidingLayout.addPanelSlideListener(new SlidingUpPanelLayout.PanelSlideListener() {
@Override
public void onPanelSlide(View panel, float slideOffset) {
        }

        @Override
        public void onPanelStateChanged(View panel, SlidingUpPanelLayout.PanelState prevState, SlidingUpPanelLayout.PanelState newState) {
            if( ( prevState == SlidingUpPanelLayout.PanelState.COLLAPSED || prevState == SlidingUpPanelLayout.PanelState.EXPANDED ) && newState == SlidingUpPanelLayout.PanelState.DRAGGING ) {
                clickInterceptor.setVisibility(View.VISIBLE);
            }
            else if( prevState == SlidingUpPanelLayout.PanelState.DRAGGING && ( newState == SlidingUpPanelLayout.PanelState.COLLAPSED || newState == SlidingUpPanelLayout.PanelState.EXPANDED ) ) {
                clickInterceptor.setVisibility(View.GONE);
            }

        }
    });`

Anyone with a knowledge of a nicer solution - let me know.

We encountered this issue today. I was able to fix it by modifying SlidingUpPanelLayout#dispatchTouchEvent() to only call ViewDragHelper#abort() if ViewDragHelper is in STATE_IDLE.
I've created PR #917 to fix this issue.

I also ran into this issue. This happens when we tap outside the panel (non-panel area) when the panel is sliding. Here, the newState is set to ANCHORED. So we can force it to slide down to COLLAPSED.
This would be natural for the user as he had already tapped outside the panel which means that he wanted to touch the area behind it.
			@Override 			public void onPanelStateChanged(View panel, SlidingUpPanelLayout.PanelState previousState, SlidingUpPanelLayout.PanelState newState) {
			switch (newState) {
				case EXPANDED:
					// your logic
					break;
				case COLLAPSED:
					// your logic
					break;
				case ANCHORED:
					// this is when we tap outside the panel when it is sliding. Here, we will force it to slide down to COLLAPSED.
					slidingUpPanelLayout.setPanelState(SlidingUpPanelLayout.PanelState.COLLAPSED);
					break;
			}
		}

To escape the aftermath of these unintended touches on objects (buttons, etc) while you are not ready to act on those touches, use setFadeOnClickListener so all the touches are forwarded to our SlidingUpPanelLayout where we will not do anything about these touches.


Avoid using "unsandboxed" in user-facing pages

In computing, "unsandboxed extensions" or "unsandboxed plugins" have a bad history. We should avoid using that word, and use something that is both more descriptive and less scary to users.

Maybe internal or integrated extensions, it describes that they work on a different level while not having that un prefix shared with unsafe.


Add code for simulating caching of IO

Gonna start hooking Simulate into the UI now.
$ go test . -count=1 -v
=== RUN   TestSimulate
=== RUN   TestSimulate/0
=== RUN   TestSimulate/0/basic
=== RUN   TestSimulate/0/only_L5_&_L6
=== RUN   TestSimulate/0/only_user-facing_reads
=== RUN   TestSimulate/0/large_block_size
=== RUN   TestSimulate/0/write-thru
=== RUN   TestSimulate/0/write-thru_&_only_user-facing_reads
=== RUN   TestSimulate/1
=== RUN   TestSimulate/1/basic
=== RUN   TestSimulate/1/only_L5_&_L6
=== RUN   TestSimulate/1/only_user-facing_reads
=== RUN   TestSimulate/1/large_block_size
=== RUN   TestSimulate/1/write-thru
=== RUN   TestSimulate/1/write-thru_&_only_user-facing_reads
--- PASS: TestSimulate (0.00s)
    --- PASS: TestSimulate/0 (0.00s)
        --- PASS: TestSimulate/0/basic (0.00s)
        --- PASS: TestSimulate/0/only_L5_&_L6 (0.00s)
        --- PASS: TestSimulate/0/only_user-facing_reads (0.00s)
        --- PASS: TestSimulate/0/large_block_size (0.00s)
        --- PASS: TestSimulate/0/write-thru (0.00s)
        --- PASS: TestSimulate/0/write-thru_&_only_user-facing_reads (0.00s)
    --- PASS: TestSimulate/1 (0.00s)
        --- PASS: TestSimulate/1/basic (0.00s)
        --- PASS: TestSimulate/1/only_L5_&_L6 (0.00s)
        --- PASS: TestSimulate/1/only_user-facing_reads (0.00s)
        --- PASS: TestSimulate/1/large_block_size (0.00s)
        --- PASS: TestSimulate/1/write-thru (0.00s)
        --- PASS: TestSimulate/1/write-thru_&_only_user-facing_reads (0.00s)
PASS
ok  	github.com/RaduBerinde/pebble_analysis/objiotracing/lib	0.178s

TTFR! Will merge & come back to these comments.

Not sure if it helps, but the Java simulator includes a rewriter to convert one of its supported traces to a common format. This is useful to compare algorithms implemented in different languages or validate an implementation is close to a reference one. Or maybe just see if any of the traces are interesting for you to use, where my preferred subset is of very different workload patterns.


Update CompareTimeSeries for CompareFlags

Need to update the CompareTimeSeries command documentation for new CompareFlags parameter.

I updated the documentation.  Close the issue.


tests: speed up unit tests

remove -p limit so that tests from different modules can run in parallel
and parallelized some of the tests

the bottleneck seems to be tests in activation module, but they don't want to work in parallel so leaving it for future

from ubuntu job
566:2023-04-18T06:29:20.5484770Z ok  	github.com/spacemeshos/go-spacemesh/activation	84.469s
849:2023-04-18T06:29:29.0528101Z ok  	github.com/spacemeshos/go-spacemesh/api/grpcserver	4.846s
1196:2023-04-18T06:30:35.7036192Z ok  	github.com/spacemeshos/go-spacemesh/beacon	63.428s
1200:2023-04-18T06:30:36.9075696Z ok  	github.com/spacemeshos/go-spacemesh/beacon/metrics	0.034s
1240:2023-04-18T06:30:39.2794133Z ok  	github.com/spacemeshos/go-spacemesh/beacon/weakcoin	0.693s
1388:2023-04-18T06:30:49.3837782Z ok  	github.com/spacemeshos/go-spacemesh/blocks	7.176s
1436:2023-04-18T06:30:50.4492055Z ok  	github.com/spacemeshos/go-spacemesh/bootstrap	0.194s
1459:2023-04-18T06:31:06.3999566Z ok  	github.com/spacemeshos/go-spacemesh/cmd/bootstrapper	3.223s
1473:2023-04-18T06:31:06.7805155Z ok  	github.com/spacemeshos/go-spacemesh/cmd/flags	0.024s
1564:2023-04-18T06:31:13.9513384Z ok  	github.com/spacemeshos/go-spacemesh/cmd/node	3.402s
1892:2023-04-18T06:31:16.1296377Z ok  	github.com/spacemeshos/go-spacemesh/common/types	0.075s
1900:2023-04-18T06:31:16.9106990Z ok  	github.com/spacemeshos/go-spacemesh/common/util	0.034s
1910:2023-04-18T06:31:19.0901148Z ok  	github.com/spacemeshos/go-spacemesh/config	0.088s
1918:2023-04-18T06:31:28.6242970Z ok  	github.com/spacemeshos/go-spacemesh/config/presets	7.465s
1942:2023-04-18T06:31:30.7594213Z ok  	github.com/spacemeshos/go-spacemesh/datastore	0.118s
1958:2023-04-18T06:31:31.5331567Z ok  	github.com/spacemeshos/go-spacemesh/eligibility	0.045s
1964:2023-04-18T06:31:32.5003045Z ok  	github.com/spacemeshos/go-spacemesh/events	0.045s
2166:2023-04-18T06:31:37.7604879Z ok  	github.com/spacemeshos/go-spacemesh/fetch	2.396s
3607:2023-04-18T06:31:45.0632165Z ok  	github.com/spacemeshos/go-spacemesh/genvm	4.602s
3651:2023-04-18T06:31:46.2460152Z ok  	github.com/spacemeshos/go-spacemesh/genvm/core	0.075s
3729:2023-04-18T06:31:47.2599712Z ok  	github.com/spacemeshos/go-spacemesh/genvm/templates/multisig	0.055s
3759:2023-04-18T06:31:48.1935906Z ok  	github.com/spacemeshos/go-spacemesh/genvm/templates/vault	0.040s
3822:2023-04-18T06:31:49.2116379Z ok  	github.com/spacemeshos/go-spacemesh/genvm/templates/wallet	0.044s
4229:2023-04-18T06:33:28.8781560Z ok  	github.com/spacemeshos/go-spacemesh/hare	95.173s
4288:2023-04-18T06:33:34.1117571Z ok  	github.com/spacemeshos/go-spacemesh/hare/eligibility	2.965s
4295:2023-04-18T06:33:34.8018849Z ok  	github.com/spacemeshos/go-spacemesh/layerpatrol	0.024s
4304:2023-04-18T06:33:35.3641310Z ok  	github.com/spacemeshos/go-spacemesh/log	0.024s
4366:2023-04-18T06:33:37.6244421Z ok  	github.com/spacemeshos/go-spacemesh/malfeasance	0.149s
4458:2023-04-18T06:33:42.2189066Z ok  	github.com/spacemeshos/go-spacemesh/mesh	1.910s
4464:2023-04-18T06:33:42.9319569Z ok  	github.com/spacemeshos/go-spacemesh/metrics	0.034s
4507:2023-04-18T06:33:45.8074200Z ok  	github.com/spacemeshos/go-spacemesh/miner	0.483s
4521:2023-04-18T06:33:47.8088974Z ok  	github.com/spacemeshos/go-spacemesh/p2p	0.129s
4583:2023-04-18T06:33:48.3891270Z ok  	github.com/spacemeshos/go-spacemesh/p2p/book	0.044s
4595:2023-04-18T06:33:49.6710659Z ok  	github.com/spacemeshos/go-spacemesh/p2p/handshake	0.058s
4606:2023-04-18T06:33:52.7869457Z ok  	github.com/spacemeshos/go-spacemesh/p2p/peerexchange	1.852s
4611:2023-04-18T06:33:54.2659952Z ok  	github.com/spacemeshos/go-spacemesh/p2p/pubsub	0.273s
4628:2023-04-18T06:33:55.4480368Z ok  	github.com/spacemeshos/go-spacemesh/p2p/server	0.070s
4771:2023-04-18T06:33:58.9563713Z ok  	github.com/spacemeshos/go-spacemesh/proposals	0.577s
4809:2023-04-18T06:34:02.2052343Z ok  	github.com/spacemeshos/go-spacemesh/signing	2.372s
4815:2023-04-18T06:34:03.0124346Z ok  	github.com/spacemeshos/go-spacemesh/sql	0.034s
4825:2023-04-18T06:34:03.9637675Z ok  	github.com/spacemeshos/go-spacemesh/sql/accounts	0.055s
4855:2023-04-18T06:34:06.1474865Z ok  	github.com/spacemeshos/go-spacemesh/sql/atxs	0.148s
4873:2023-04-18T06:34:07.2221255Z ok  	github.com/spacemeshos/go-spacemesh/sql/ballots	0.075s
4881:2023-04-18T06:34:08.1541940Z ok  	github.com/spacemeshos/go-spacemesh/sql/beacons	0.054s
4899:2023-04-18T06:34:09.1562266Z ok  	github.com/spacemeshos/go-spacemesh/sql/blocks	0.075s
4907:2023-04-18T06:34:10.1347285Z ok  	github.com/spacemeshos/go-spacemesh/sql/certificates	0.056s
4913:2023-04-18T06:34:11.0595161Z ok  	github.com/spacemeshos/go-spacemesh/sql/identities	0.046s
4927:2023-04-18T06:34:12.0173068Z ok  	github.com/spacemeshos/go-spacemesh/sql/kvstore	0.066s
4943:2023-04-18T06:34:12.9956810Z ok  	github.com/spacemeshos/go-spacemesh/sql/layers	0.076s
4954:2023-04-18T06:34:13.9230358Z ok  	github.com/spacemeshos/go-spacemesh/sql/poets	0.054s
4962:2023-04-18T06:34:14.8997188Z ok  	github.com/spacemeshos/go-spacemesh/sql/proposals	0.056s
4966:2023-04-18T06:34:15.8025564Z ok  	github.com/spacemeshos/go-spacemesh/sql/rewards	0.036s
5014:2023-04-18T06:34:17.1666786Z ok  	github.com/spacemeshos/go-spacemesh/sql/transactions	0.203s
11572:2023-04-18T06:34:33.9793976Z ok  	github.com/spacemeshos/go-spacemesh/syncer	13.646s
11608:2023-04-18T06:36:13.9198759Z ok  	github.com/spacemeshos/go-spacemesh/systest/validation	0.076s
11642:2023-04-18T06:36:16.0825432Z ok  	github.com/spacemeshos/go-spacemesh/timesync	1.295s
11679:2023-04-18T06:36:18.2418169Z ok  	github.com/spacemeshos/go-spacemesh/timesync/peersync	0.231s
12032:2023-04-18T06:36:30.3082482Z ok  	github.com/spacemeshos/go-spacemesh/tortoise	8.536s
12037:2023-04-18T06:36:41.0852182Z ok  	github.com/spacemeshos/go-spacemesh/tortoise/model	8.749s
12077:2023-04-18T06:36:41.8478655Z ok  	github.com/spacemeshos/go-spacemesh/tortoise/opinionhash	0.044s
12298:2023-04-18T06:37:09.6220954Z ok  	github.com/spacemeshos/go-spacemesh/txs	25.045s

bors merge

Error from server (BadRequest): Unable to find "/v1, Resource=configmaps" that match label selector "testid=systest-", field selector "": unable to parse requirement: values[0][testid]: Invalid value: "systest-": a valid label must be an empty string or consist of alphanumeric characters, '-', '' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue',  or 'my_value',  or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9.]*)?[A-Za-z0-9])?')

bors merge

golangci/golangci-lint info checking GitHub for tag 'v1.52.0'
golangci/golangci-lint info found version: 1.52.0 for v1.52.0/linux/amd64
make: *** [Makefile:63: install] Error 1
Error: Process completed with exit code 2.

bors merge


APA Style not working correctly

I guess the citation style APA is not working correctly.
e.g.
multiple authors are displayed as (author 1/ author 2, 2022) instead of (author 1 & author 2, 2022)
multiple non author and non date entrys are displayed like o.A. (o.D.a): ... and o.A. (o.D.b): ... instead of just o.A. (o.D.):....
website bib items don't show title of the website, last access date and the url.
Got someone a fix to that?

Hello @MrcoSchrnr,
I'm afraid that APA has not yet made its way to here.
What's currently there is not yet apa but the once IU-internal citation style which has been recently replaced by APA.
Feel free to try to apply apacite but I warn that the APA citation style is quite a monster and it is difficult to get right (this is a summary, the specification, among others, is more than 100 pages big which you can find here).

Hi guys, I am currently facing the same issue, but I think there could be a solution that avoids using apacite. By replacing the usage of natbib with biblatex, the bibliography style is like defined in the IU citation style guide. What I did in my current thesis template is following:
Head of document:
% import biblatex and apply the APA 7th edition
\usepackage[style=apa, sorting=nyt, backend=biber]{biblatex}

% references the .bib file
\addbibresource{bibliography/bibliography.bib}

% The IU citation style guide does not use an ampersand as delimiter of multiple authors in the bibliography
% This basically replaces the ampersand by a comma
\DeclareDelimFormat[bib]{finalnamedelim}{\addcomma\space

Body of document:
% add the bibliography to the doc
/printbibliography

.bib-File:
% monography
@book{mustermann.2010,
   author       = {Max Mustermann}, % multiple authors are seperated by 'and'
   title            = {Buchtitel},
   publisher   = {Verlag XY},
   year           = {2010}
 }

% article
@article{muster.2020,
  author          = {Max Mueller and Maxi Mustermann},
  journal         = {Zeitschriftenname},
  number        = {1},
  title               = {Titel des Artikels},
  volume         = {8},
  year              = {2020},
  pages           = {S. 82 - 87}
}

@online{online.2019,
  author   = {Der Autor},
  title        = {Online Titel},
  year       = {2017},
  url          = {https://google.com},
}

To use a certain source you just have to add parencite[][]{mustermann.2010} to the document (for footnote footcite[][]{mustermann.2010}).


Tree Don't consume mouse event by collapse arrow which isn't shown

Collapse/folding arrow is shown only when TreeItem has children (has the first child) and it should handle a mouse event only if it's actually visible.

It is some improvement, but what exactly does this change? I don't see any difference in behavior.

It is some improvement, but what exactly does this change?

It makes mouse events not being handled/consumed by an invisible collapse/folding arrow.

I don't see any difference in behavior.

For reference: I've noticed this wrong behavior because of #55774 (I'm mentioning this PR in https://github.com/godotengine/godot/issues/55774#issuecomment-991144344).
For example open Editor -> Manage Editor Features... dialog. Currently for tree items with no children checkboxes can be toggled by clicking on the left from the invisible collapse arrow (you can test it yourself) but not by clicking over that invisible arrow (because it handles the event):

But if the checkbox (or anything else) is supposed to handle mouse event on the left then the invisible arrow shouldn't block it. And that's what this PR is fixing. With this PR:

And this PR isn't really about the checkboxes and whether it makes sense to toggle them by clicking to the left from them (that's what #55774 is about). It's just an example. An invisible collapse/fold arrow shouldn't handle/consume mouse event over it no matter (as it's kinda nonexistent) what and that's what this PR is fixing.

Thanks!


as path doesn't work properly (or does it?)

It seems that router.on('routeChangeComplete', path => ...) returns the asPath for the path argument. I need to clarify this still. But I'm trying to do something like this: router.push('/dashboard/my-artists/djkhaled', '/@djkhaled') where the URL should show the asPath /@djhkhaled.
However, it seems that the LinkTo component is trying to navigate to /@djkhaled instead of the href. This is breaking for me on Web, since my React Navigation linking config expects the more normal URL. So I'm going to look more into this.
It's possible we read from the Router directly inside of the routeChangeComplete event, since I would assume that that's all it's passing down to us anyway.
However, what is the desired behavior? Do we want React Navigation reading the as path, or the href? I think it should be the href, since that lets us use the correct URLs for navigating within a specific tab, etc.
Discussion
This isn't a bug, but rather a discussion over desired behavior. I think React Navigation should deal with the normal paths, rather than asPaths.
However, this wouldn't work for native deep linking.
In my case, I have a rewrite in Next.js. Any URL to /@:slug → /artists/[slug].
However, for deep linking into an app, if I send you beatgig.com/@djkhaled on like iMessage, and you open it from your phone, the native app will handle that as /@djkhaled, so we'd have to rewrite this here as well, presumably inside of getPathFromState. 🥲

Ignore this, but more discussion at #17


metainfo: invalid direction 0

We found this error in the object browser of the nightly deployment:
<Error>InternalError<Message>We encountered an internal error, please try again.: cause(uplink: metainfo: invalid direction 0)</Message><BucketName>bucket1</BucketName><Resource>/bucket1</Resource><RequestId>17276D17ED0D2F14</RequestId><HostId></HostId></Error>

But the same problem is reported on the forum, too:
https://forum.storj.io/t/cant-open-bucket-if-store-a-lot-of-objects/20440

After debugging it with a local gateway-mt, the problem is restricted to this code fragment in gateway.go:
func (layer *gatewayLayer) listObjectsFast(
	ctx context.Context,
	project *uplink.Project,
	bucket, prefix, continuationToken, delimiter string,
	maxKeys int,
	startAfter string,
) (
	prefixes []string,
	objects []minio.ObjectInfo,
	nextContinuationToken string,
	err error,
) {
	defer mon.Task()(&ctx)(&err)

	...

	for limit > 0 && list.Next() {
		item := list.Item()

		limit--

		if item.IsPrefix {
			prefixes = append(prefixes, item.Key)
		} else {
			objects = append(objects, minioObjectInfo(bucket, "", item))
		}

		nextContinuationToken = item.Key
	}
	if list.Err() != nil {
		return nil, nil, "", list.Err()
	}

	more := list.Next()
	if list.Err() != nil {
		return nil, nil, "", list.Err()
	}

      ...
}

Here we have two listNext() call after each other. I don't know exactly the reason, why.
In case of the encryption key is bad, the first list.Next returns with more=false, and doesn't expect any more calls.
Doesn't expect means that the options are reset to a zero object in types.go project of storj/uplink:

// NextPage returns options for listing the next page.
func (opts ListOptions) NextPage(list ObjectList) ListOptions {
	if !list.More || len(list.Items) == 0 {
		return ListOptions{}
	}

	return ListOptions{
		Prefix:                opts.Prefix,
		Cursor:                list.Items[len(list.Items)-1].Path,
		Delimiter:             opts.Delimiter,
		Recursive:             opts.Recursive,
		IncludeSystemMetadata: opts.IncludeSystemMetadata,
		IncludeCustomMetadata: opts.IncludeCustomMetadata,
		Direction:             After,
		Limit:                 opts.Limit,
	}
}
```

The problem is in the `return ListOptions{}`, which resets the direction (assuming nobody else will call the next, again.

Not sure if it's an `uplink` or `gateway` error, maybe we can fix it on bot sides.

Thanks for the report.
What does it mean that the encryption key is bad? Shouldn't that be an error?
This code has existed in the gateway forever; the reason we do an extra call to Next is to make look up if there are more items in the listing, in which case we return the continuation token and signal that there are more items to list.
Were there any recent changes to libuplink? Should we try redesigning this so that gateway doesn't assume that Next is idempotent (it feels like people would run into it anyway)?

from sprint planning: @pwilloughby has a bucket to reproduce this issue


fix(table): adjust padding on empty state

Closes #3236
Summary
Removed the left margin on the svg image and added padding to the left side to align the empty-state on the grid
Change List (commits, features, bugs, etc)

removed margin on left edge of image
added more padding

Acceptance Test (how to verify the PR)

matches grid in original issue

Regression Test (how to make sure this PR doesn't break old functionality)

tests here

Things to look for during review

[ ] Make sure all references to iot or bx class prefix is using the prefix variable
[ ] (React) All major areas have a data-testid attribute. New test ids should have test written to ensure they are not changed or removed.
[ ] UI should be checked in RTL mode to ensure the proper handling of layout and text.
[ ] All strings should be translatable.
[ ] The code should pass a11y scans (The storybook a11y knob should show no violations). New components should have a11y test written.
[ ] Unit test should be written and should have a coverage of 90% or higher in all areas.
[ ] All components should be passing visual regression test. For new styles or components either a visual regression test should be written for all permutations or the base image updated.
[ ] Changes or new components should either write new or update existing documentation.
[ ] PR should link and close out an existing issue

@ben-bacon or @dianatran18 can you verify that this is changed to match spec?

Yep! this change now matches spec - Thank you!


[WIP] [RFC] Add initial crypto driver framework

This is a proposal for a crypto framework using HW acceleration in MCUs that have the support.
It was tested with the added app (crypto_test) as well as enc_flash + encrypted images on NXP K64F and Nrf52840-PDK.
Still a few TODOS before this is complete for reviews:

Some error handling in the main driver needs finishing
Expand doxygen comments
STM32 driver must be finished (remove IRQ handling because it's slower)

PS: there are two commits which are not part of the PR but are helping me on my tests, will remove them soon... (UPDATE: one commit!)

@mkiiskila Most issues were already addressed, ended up being a overhaul in the API but more extendable now IMO, although can still be clean up. STM32 will be done next.

@mkiiskila STM32 should be OK now (apart from locking); I removed the NXP library because it seems to be Categoy-X (thread here: https://mail-archives.apache.org/mod_mbox/www-legal-discuss/201902.mbox/browser) and added a C implementation with https://github.com/apache/mynewt-core/pull/1649/commits/f0326e539c254034a0bb444d55c9393b15414cdc (does not yet expand keys above AES-128); I will add a global locking per driver now; also considering adding a few syscfg for the low-level driver to export the functionality it supports (to allow link time removal of some symbols) and syscfgs for a library/app declare functionality it needs (or disable what it does not, so it can be link time removed from build).

Ops, correct ML link: https://mail-archives.apache.org/mod_mbox/www-legal-discuss/201902.mbox/<0551171b-8d4b-4064-84b9-9ad0030be810%40www.fastmail.com> and commit https://github.com/apache/mynewt-core/commit/52f9682c833e5653b9092e1e70eddf20fa82cce0

Thanks for going through the process of verifying license!
I don't think we need to complete the individual drivers with all the features, as long as the API seems like something we can start with :) We probably should merge it earlier, and then let the API soak for a release or two.

This seems like a reasonable start with this. I'd be ok starting with this.


Benchmarking batch span processor

Baseline
It's the current implementation, using Mutex
Benchmark
Batch span processor benchmark
BatchSpanProcessor/with 1 concurrent task
                        time:   [1.2616 ms 1.2833 ms 1.3027 ms]
Found 4 outliers among 50 measurements (8.00%)
  1 (2.00%) low severe
  2 (4.00%) low mild
  1 (2.00%) high severe
Benchmarking BatchSpanProcessor/with 2 concurrent task: Collecting 50 samples in estimated 5.3349 s (2550                                                                                BatchSpanProcessor/with 2 concurrent task
                        time:   [1.3328 ms 1.3597 ms 1.3865 ms]
Found 6 outliers among 50 measurements (12.00%)
  1 (2.00%) low mild
  2 (4.00%) high mild
  3 (6.00%) high severe
Benchmarking BatchSpanProcessor/with 4 concurrent task: Collecting 50 samples in estimated 5.1455 s (2550                                                                                BatchSpanProcessor/with 4 concurrent task
                        time:   [2.0018 ms 2.0323 ms 2.0620 ms]
Found 3 outliers among 50 measurements (6.00%)
  1 (2.00%) low mild
  1 (2.00%) high mild
  1 (2.00%) high severe
Benchmarking BatchSpanProcessor/with 8 concurrent task: Collecting 50 samples in estimated 8.9514 s (2550                                                                                BatchSpanProcessor/with 8 concurrent task
                        time:   [3.5355 ms 3.5884 ms 3.6419 ms]
Found 2 outliers among 50 measurements (4.00%)
  1 (2.00%) low severe
  1 (2.00%) high severe
Benchmarking BatchSpanProcessor/with 16 concurrent task: Warming up for 3.0000 s
Warning: Unable to complete 50 samples in 5.0s. You may wish to increase target time to 7.9s, enable flat sampling, or reduce sample count to 20.
Benchmarking BatchSpanProcessor/with 16 concurrent task: Collecting 50 samples in estimated 7.8658 s (1275                                                                                BatchSpanProcessor/with 16 concurrent task
                        time:   [6.2420 ms 6.3020 ms 6.3641 ms]
Found 1 outliers among 50 measurements (2.00%)
  1 (2.00%) low severe
Benchmarking BatchSpanProcessor/with 32 concurrent task: Collecting 50 samples in estimated 5.4253 s (450                                                                                BatchSpanProcessor/with 32 concurrent task
                        time:   [10.392 ms 10.673 ms 11.037 ms]
Found 7 outliers among 50 measurements (14.00%)
  6 (12.00%) high mild
  1 (2.00%) high severe

Trace benchmark
start-end-span/always-sample
                        time:   [983.51 ns 987.61 ns 991.96 ns]
Found 3 outliers among 100 measurements (3.00%)
  1 (1.00%) low severe
  2 (2.00%) high mild
start-end-span/never-sample
                        time:   [182.74 ns 184.56 ns 186.62 ns]
Found 6 outliers among 100 measurements (6.00%)
  5 (5.00%) high mild
  1 (1.00%) high severe

Benchmarking start-end-span-4-attrs/always-sample: Collecting 100 samples in estimated 5.0099 s (2.3M iter                                                                                start-end-span-4-attrs/always-sample
                        time:   [1.8911 us 1.9332 us 1.9838 us]
Found 18 outliers among 100 measurements (18.00%)
  2 (2.00%) low mild
  2 (2.00%) high mild
  14 (14.00%) high severe
Benchmarking start-end-span-4-attrs/never-sample: Collecting 100 samples in estimated 5.0003 s (24M iterat                                                                                start-end-span-4-attrs/never-sample
                        time:   [201.21 ns 202.06 ns 203.11 ns]
Found 4 outliers among 100 measurements (4.00%)
  4 (4.00%) high mild

Benchmarking start-end-span-8-attrs/always-sample: Collecting 100 samples in estimated 5.0058 s (2.1M iter                                                                                start-end-span-8-attrs/always-sample
                        time:   [2.4407 us 2.4635 us 2.4876 us]
Found 2 outliers among 100 measurements (2.00%)
  1 (1.00%) low mild
  1 (1.00%) high mild
Benchmarking start-end-span-8-attrs/never-sample: Collecting 100 samples in estimated 5.0002 s (20M iterat                                                                                start-end-span-8-attrs/never-sample
                        time:   [245.90 ns 246.81 ns 247.89 ns]
Found 6 outliers among 100 measurements (6.00%)
  3 (3.00%) high mild
  3 (3.00%) high severe

Benchmarking start-end-span-all-attr-types/always-sample: Collecting 100 samples in estimated 5.0081 s (2.                                                                                start-end-span-all-attr-types/always-sample
                        time:   [2.0650 us 2.0853 us 2.1070 us]
Found 5 outliers among 100 measurements (5.00%)
  1 (1.00%) low mild
  2 (2.00%) high mild
  2 (2.00%) high severe
Benchmarking start-end-span-all-attr-types/never-sample: Collecting 100 samples in estimated 5.0004 s (22M                                                                                start-end-span-all-attr-types/never-sample
                        time:   [221.73 ns 223.62 ns 225.50 ns]
Found 4 outliers among 100 measurements (4.00%)
  1 (1.00%) low severe
  1 (1.00%) low mild
  2 (2.00%) high mild

Benchmarking start-end-span-all-attr-types-2x/always-sample: Collecting 100 samples in estimated 5.0027 s                                                                                start-end-span-all-attr-types-2x/always-sample
                        time:   [4.5712 us 4.6128 us 4.6549 us]
Found 1 outliers among 100 measurements (1.00%)
  1 (1.00%) low mild
Benchmarking start-end-span-all-attr-types-2x/never-sample: Collecting 100 samples in estimated 5.0011 s (                                                                                start-end-span-all-attr-types-2x/never-sample
                        time:   [280.07 ns 282.77 ns 285.20 ns]

Async-channels
Using async-channels create's mpmc channels.
Benchmark
Batch span processor benchmark

Trace benchmark

Relay message via thread
This implementation uses an unbounded crossbeam channel to send a message to a dedicated thread, where the thread then relays the message to the exporter in async.
Benchmark
Batch span processor benchmark
BatchSpanProcessor/with 1 concurrent task
                        time:   [653.97 us 664.78 us 676.51 us]
                        change: [-50.439% -47.925% -44.654%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 3 outliers among 50 measurements (6.00%)
  1 (2.00%) low mild
  1 (2.00%) high mild
  1 (2.00%) high severe
Benchmarking BatchSpanProcessor/with 2 concurrent task: Collecting 50 samples in estimated 5.4214 s (6375                                                                                BatchSpanProcessor/with 2 concurrent task
                        time:   [848.47 us 865.06 us 882.19 us]
                        change: [-41.421% -38.363% -35.214%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 2 outliers among 50 measurements (4.00%)
  1 (2.00%) low mild
  1 (2.00%) high severe
Benchmarking BatchSpanProcessor/with 4 concurrent task: Collecting 50 samples in estimated 5.9611 s (5100                                                                                BatchSpanProcessor/with 4 concurrent task
                        time:   [1.1289 ms 1.1662 ms 1.2127 ms]
                        change: [-44.206% -41.354% -38.359%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 10 outliers among 50 measurements (20.00%)
  2 (4.00%) low mild
  2 (4.00%) high mild
  6 (12.00%) high severe
Benchmarking BatchSpanProcessor/with 8 concurrent task: Collecting 50 samples in estimated 6.5517 s (3825                                                                                BatchSpanProcessor/with 8 concurrent task
                        time:   [1.6954 ms 1.7181 ms 1.7418 ms]
                        change: [-52.986% -51.476% -50.023%] (p = 0.00 < 0.05)
                        Performance has improved.
Benchmarking BatchSpanProcessor/with 16 concurrent task: Collecting 50 samples in estimated 7.6125 s (2550                                                                                BatchSpanProcessor/with 16 concurrent task
                        time:   [3.0791 ms 3.1372 ms 3.1982 ms]
                        change: [-51.680% -50.452% -49.215%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 4 outliers among 50 measurements (8.00%)
  2 (4.00%) low mild
  1 (2.00%) high mild
  1 (2.00%) high severe
Benchmarking BatchSpanProcessor/with 32 concurrent task: Warming up for 3.0000 s
Warning: Unable to complete 50 samples in 5.0s. You may wish to increase target time to 7.0s, enable flat sampling, or reduce sample count to 20.
Benchmarking BatchSpanProcessor/with 32 concurrent task: Collecting 50 samples in estimated 7.0406 s (1275                                                                                BatchSpanProcessor/with 32 concurrent task
                        time:   [5.0141 ms 5.0886 ms 5.1789 ms]
                        change: [-51.929% -49.967% -48.009%] (p = 0.00 < 0.05)
                        Performance has improved.

Trace benchmark

Relay message via thread
This implementation uses an unbounded crossbeam channel to send a message to a dedicated thread, where the thread then relays the message to the exporter in async.
Benchmark
Batch span processor benchmark
BatchSpanProcessor/with 1 concurrent task
                        time:   [653.97 us 664.78 us 676.51 us]
                        change: [-50.439% -47.925% -44.654%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 3 outliers among 50 measurements (6.00%)
  1 (2.00%) low mild
  1 (2.00%) high mild
  1 (2.00%) high severe
Benchmarking BatchSpanProcessor/with 2 concurrent task: Collecting 50 samples in estimated 5.4214 s (6375                                                                                BatchSpanProcessor/with 2 concurrent task
                        time:   [848.47 us 865.06 us 882.19 us]
                        change: [-41.421% -38.363% -35.214%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 2 outliers among 50 measurements (4.00%)
  1 (2.00%) low mild
  1 (2.00%) high severe
Benchmarking BatchSpanProcessor/with 4 concurrent task: Collecting 50 samples in estimated 5.9611 s (5100                                                                                BatchSpanProcessor/with 4 concurrent task
                        time:   [1.1289 ms 1.1662 ms 1.2127 ms]
                        change: [-44.206% -41.354% -38.359%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 10 outliers among 50 measurements (20.00%)
  2 (4.00%) low mild
  2 (4.00%) high mild
  6 (12.00%) high severe
Benchmarking BatchSpanProcessor/with 8 concurrent task: Collecting 50 samples in estimated 6.5517 s (3825                                                                                BatchSpanProcessor/with 8 concurrent task
                        time:   [1.6954 ms 1.7181 ms 1.7418 ms]
                        change: [-52.986% -51.476% -50.023%] (p = 0.00 < 0.05)
                        Performance has improved.
Benchmarking BatchSpanProcessor/with 16 concurrent task: Collecting 50 samples in estimated 7.6125 s (2550                                                                                BatchSpanProcessor/with 16 concurrent task
                        time:   [3.0791 ms 3.1372 ms 3.1982 ms]
                        change: [-51.680% -50.452% -49.215%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 4 outliers among 50 measurements (8.00%)
  2 (4.00%) low mild
  1 (2.00%) high mild
  1 (2.00%) high severe
Benchmarking BatchSpanProcessor/with 32 concurrent task: Warming up for 3.0000 s
Warning: Unable to complete 50 samples in 5.0s. You may wish to increase target time to 7.0s, enable flat sampling, or reduce sample count to 20.
Benchmarking BatchSpanProcessor/with 32 concurrent task: Collecting 50 samples in estimated 7.0406 s (1275                                                                                BatchSpanProcessor/with 32 concurrent task
                        time:   [5.0141 ms 5.0886 ms 5.1789 ms]
                        change: [-51.929% -49.967% -48.009%] (p = 0.00 < 0.05)
                        Performance has improved.

Trace benchmark

Runtime channel(Tokio)
This implementation uses tokio's mpsc channel.
Benchmark
Batch span processor benchmark
                                                                                BatchSpanProcessor/with 1 concurrent task
                        time:   [815.87 us 829.74 us 842.96 us]
                        change: [-37.875% -36.049% -33.945%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 2 outliers among 50 measurements (4.00%)
  1 (2.00%) low mild
  1 (2.00%) high severe
Benchmarking BatchSpanProcessor/with 2 concurrent task: Collecting 50 samples in estimated 5.0790 s (6375                                                                                BatchSpanProcessor/with 2 concurrent task
                        time:   [770.21 us 795.87 us 819.60 us]
                        change: [-47.068% -43.885% -40.265%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 2 outliers among 50 measurements (4.00%)
  1 (2.00%) high mild
  1 (2.00%) high severe
Benchmarking BatchSpanProcessor/with 4 concurrent task: Collecting 50 samples in estimated 5.0076 s (5100                                                                                BatchSpanProcessor/with 4 concurrent task
                        time:   [978.84 us 994.49 us 1.0142 ms]
                        change: [-52.975% -50.992% -49.105%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 2 outliers among 50 measurements (4.00%)
  2 (4.00%) high severe
Benchmarking BatchSpanProcessor/with 8 concurrent task: Collecting 50 samples in estimated 5.6770 s (3825                                                                                BatchSpanProcessor/with 8 concurrent task
                        time:   [1.5345 ms 1.5818 ms 1.6360 ms]
                        change: [-57.686% -55.862% -54.103%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 2 outliers among 50 measurements (4.00%)
  2 (4.00%) high mild
Benchmarking BatchSpanProcessor/with 16 concurrent task: Collecting 50 samples in estimated 7.0147 s (2550                                                                                BatchSpanProcessor/with 16 concurrent task
                        time:   [2.6791 ms 2.6978 ms 2.7197 ms]
                        change: [-57.499% -56.752% -55.918%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 3 outliers among 50 measurements (6.00%)
  1 (2.00%) low mild
  1 (2.00%) high mild
  1 (2.00%) high severe
Benchmarking BatchSpanProcessor/with 32 concurrent task: Warming up for 3.0000 s
Warning: Unable to complete 50 samples in 5.0s. You may wish to increase target time to 6.7s, enable flat sampling, or reduce sample count to 30.
Benchmarking BatchSpanProcessor/with 32 concurrent task: Collecting 50 samples in estimated 6.7026 s (1275                                                                                BatchSpanProcessor/with 32 concurrent task
                        time:   [5.0974 ms 5.1896 ms 5.2855 ms]
                        change: [-50.867% -48.256% -45.433%] (p = 0.00 < 0.05)
                        Performance has improved.
Found 1 outliers among 50 measurements (2.00%)
  1 (2.00%) high severe

Trace benchmark

Benchmark
Baseline(Current implementation)
mpmc channel
new thread
Tokio channel

BSP/1 task
1.2ms
1.4ms ( +14%)
664us (-47%)
759us(-8%)

BSP/2 tasks
1.3ms
930 us (-31%)
865us(-38%)

BSP/4 tasks
2.0ms
1.07ms(-45%)
1.16ms(-41%)

BSP/8 tasks
3.5ms
1.69ms(-52%)
1.7ms(-51%)

BSP/16 tasks
6.3ms
2.68ms(-57%)
3.1ms(-50%)

BSP/32 tasks
10.6ms
4.7ms(-55%)
5.0ms(-49%)

start-end-span/always-sample
987ns
488ns(-47%)

start-end-span/never-sample
184ns
152ns(-18%)

start-end-span-4-attrs/always-sample
1.9us
1.16us(-42%)

start-end-span-4-attrs/never-sample
202 ns
207ns(-2%)

start-end-span-8-attrs/always-sample
2.4us
1.7us(-28%)

start-end-span-8-attrs/never-sample
246ns
234ns(-4%)

start-end-span-all-attr-types/always-sample
2.0us
1.4us (-27%)

start-end-span-all-attr-types/never-sample
223.62ns
192ns(-6%)

start-end-span-all-attr-types-2x/always-sample
4.6 us
2.7us(-55%)

start-end-span-all-attr-types-2x/never-sample
282ns
250ns(-75%)


Documentation website domain triggers Chrome's warning

Docs website, of course, is: https://twitchtv.github.io/twirp/
I hope it is possible to contact Google from your side and fix this 😅

We're aware of this issue and tracking internally. No progress yet, but definitely known.

https://issuetracker.google.com/issues/342242650
Thank you for submitting your submission. We have successfully fetched and processed your digital asset link manifests across the following domains:
  * twitch.tv
  * twitchtv.github.io

Within a few days, lookalike warnings should stop showing on these sites. If you're still seeing the warnings in 1 week, feel free to follow-up here.

Will leave this open until issue is confirmed gone.

Confirmed the issue is no longer present. Closing.


Fix random failures on Travis

This changeset has resulted in a broken build for no obvious reason as it was only documentation related, so I think we're facing random failures here.

Any feedback with this one, we're forced to move our tests to inactive test folder since Travis CI is giving us random failures all the time?

@asimd Could you please point us to your failing test suite? There is at least one known issue with popups that invariably creates intermittent errors when travis is under high load. The problem here is that we know what fails but not yet how to replicate it under controlled conditions nor how to fix it.

I am closing this. We have some identified sources of random failures that are fixed now, a rather long streak of passing builds and know the reason for recent build failures (bitbucket throttling).
Feel free to re-open if this hits again in a random manner.


Linux CentOS 7.1 64-bit no longer exists in Exoscale

it is now 7.2, so the component examples/images/centos-7 must be changed accordingly

old


Trinity.TSL.CodeTemplates.csproj build error when $(ProjectDir) path contains whitespaces

In GraphEngine/src/Trinity.TSL/Trinity.TSL.CodeTemplates/Trinity.TSL.CodeTemplates.csproj:
⋮
  <Target Name="AfterBuild">
    <Exec Command="$(OutputPath)Trinity.TSL.Metagen.exe $(ProjectDir)" />
  </Target>
</Project>

My temp fix for that problem is
<Exec Command="$(OutputPath)Trinity.TSL.Metagen.exe "$(ProjectDir)\" />

However, I have also observed that the tsl script is not compiled correctly

for paths with white spaces.
E.g. the SSSP sample cannot create API code from templates properly. But when I move the whole dir to a path without white space (such as C:\samples\SSSP) the sample works fine (after cleanup and remove all obj and bin stuff)

My Env-Specs:

Windows 10 64bit
Visual Studio 2017 with Windows 10 SDK (10.0.15063.0) for Desktop C++, .NET Core SDK 2.0,  Visual Studio 2015 C++ toolchain as per README

hi @rucub100!
thanks for reporting the problem! that's kind of 'uh oh' because I've been working on the spaces quite often.. I'll fix this one and update master.
however, I'm pretty sure that Trinity.TSL.MetaGen.exe is only used to build Trinity.TSL.CodeGen.exe, not for user tsl templates; Could you please try again with a project in spaced path? Sometimes unloading the user proj from VS and reloading it will help -- a VS problem. :)


iOS TextField, Add support for keyboardOptions in iOS

Right now if to set keyboardOptions = KeyboardOptions(keyboardType = KeyboardType.Number) to TextField it works for Android but is ignored for iOS.
Android:

iOS:

The fix for that will be available in the next release of Compose Multiplatform 1.5.0 (was fixed in the related issue #2735)

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Domain of Demo-Shop expired

Hey!
I just stumbled upon the SilverShop module and wanted to checkout the demo store. But it seems that the domain has expired.
Is there another demo or will it be fixed soon? I'd like to have a look at a running instance before testing it for myself.
Thanks
Philipp

@bummzack thoughts? Should we setup a http://demo.silvershop.io/ domain? I am happy to provide hosting for it.

@wilr Sorry, I didn't see this one. Are there any useful up-to-date templates for shop? Otherwise this is going to be bad advertisement 😂
This is quite low on my priority list to be honest. To get a glimpse of the CMS, one can just set up a new shop and use the populate shop task. To get an impression of the frontend it's probably better to have some sort of showcase?

@bummzack Yes to both. I think we should get a page on the site with a showcase if you have any good links but a demo would be useful for us as well..
I've started rewriting the templates to BEM so love to get that work on demo. We've got the shop recipe that would be the basis.
If someone can setup demo.silvershop.io to record <IP_ADDRESS> I'll play around with the rest

Ok, I think @jelicanin is the man for that. Milan, could you set up the domain name?

Hi guys,
sry for a late reply, I'm ill last few days...
Subomain demo.silvershop.io is pointed.
Can you check it?

Thanks @jelicanin perfect. Will get the recipe up there next couple of days.

@wilr How's your progression on the templates? I think we should make these modifications before releasing, since templates are probably also part of the public api (semver)? What do you think?
@jelicanin Thanks for installing the subdomain and get well soon!

When did you want to release? Few templates to update left and then testing so perhaps a week or 2 away..

I don't have a fixed deadline… take your time :)
Although I wanted to do much more, I think it's a good idea to release the module in the current state and not change too much. I'll try to fix some of the open bugs and improve documentation before we release.


de.adesso.wicked-charts:wicked-charts-wicket8:3.0.0 missing from central repository?

I cannot find wicked-charts in jcenter repository? Wanted to use it with Wicket 8...

Hello @VaclavC, a Wicket 8 module is available in wicked charts 3.1.0. That should fix the issue :)

Ah, thank you ;-). Perhaps an update of the readme would be nice. There is 3.0.0 version mentioned.


Update peer deps to make compatible with RN 0.63

Without this change, npm audit --fix will not work in projects that use NB v3 and RN 0.63.x, introducing possible security vulnerabilities.

Not stale.
On Wed, 2 Feb 2022, 04:55 stale[bot], @.***> wrote:

This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Thank you
for your contributions.
—
Reply to this email directly, view it on GitHub
https://github.com/GeekyAnts/NativeBase/pull/3694#issuecomment-1027576730,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABYQJZVHMKR2SIFL7OJBDVDUZC2NVANCNFSM4462ORGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Appstudio update test-component-pac-sejt

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-sejt-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
9 seconds
init

✅ Succeeded
18 seconds
clone-repository

✅ Succeeded
42 seconds
build-container

✅ Succeeded
26 seconds
deprecated-base-image-check

✅ Succeeded
24 seconds
inspect-image

✅ Succeeded
10 seconds
clair-scan

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
23 seconds
label-check

✅ Succeeded
21 seconds
optional-label-check

✅ Succeeded
7 seconds
show-summary

✅ Succeeded
6 seconds
show-sbom

Pipelines as Code CI/test-component-pac-sejt-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
15 seconds
init

✅ Succeeded
17 seconds
clone-repository

✅ Succeeded
38 seconds
build-container

✅ Succeeded
24 seconds
inspect-image

✅ Succeeded
20 seconds
deprecated-base-image-check

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
12 seconds
clair-scan

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
27 seconds
label-check

✅ Succeeded
28 seconds
optional-label-check

✅ Succeeded
5 seconds
show-sbom

✅ Succeeded
9 seconds
show-summary


Alternate to Symbols

Would it be possible to create a toggle for keys that are represented with a symbol such as Shift and Tab to be written out like Ctrl and Alt?

I would like that too. I think it will be more consistent that way.

This should be expanded to all keys.


SREP-1593 Account Reuse

Added finalizer to accountClaim, triggering:

EBS Volume deletion
EBS Snapshot deletion
S3 buckets deletion
Update account state and claimed (to false) in Status
Carry over LegalEntity data from deletedClaim to account (for older accounts)

Updated Account Claim process to:

Look for reused accounts prior to claiming new ones
Match LegalEntity.ID to look for possible accounts to reuse

Updated Account Pool controller to ignore reused accounts when counting the pool size

Added reuse metrics:

aws_account_operator_total_aws_account_reused_available
aws_account_operator_total_aws_account_reused_failed

@jewzaam per our discussion today I created a card for us to evaluate the benefits of delaying the account cleanup in AWS versus possible issues: (https://jira.coreos.com/browse/SREP-1813). For this PR will consider the cleanup to be done as part of the finalizer, when the accountClaim gets deleted.

/hold

/hold cancel

/hold

@jharrington22 Fixed the metrics issue we discussed today. I will leave the PR on hold for you to remove as soon as you do lgtm and approve.

/hold cancel

@jhernand @nimrodshn merged!


Search existing creators both via LDAP and locally added creators

Populate the work version edit form with existing aliases and creators taken from our local database (possibly via Solr) and via LDAP.
Blocked by #93
WDLL

search bar within creators that search both local creators and LDAP and inserts new creators from the selection in the search bar
UI feature parity with Scholarsphere 3

Our Friends in EIT have developed a rest-service "search-service" that may fit these needs. I'm going to be looking to see if it provides the information we need in the coming days for another project, but wanted to share here.
Their swagger dogs are hosted here:
https://identity.apps.psu.edu/search-service/resources


rasa test core not working for stories in a folder

Rasa version:
Current master
Rasa SDK version (if used & relevant):
N/A
Rasa X version (if used & relevant):
N/A
Python version:
Operating system (windows, osx, ...):
Issue:
rasa test core doesn't work when the stories are in a subfolder, e.g., rasa test core --stories data/core on rasa-demo
In this case, it finds 0 test stories.
(My suspicion is that it comes from rasa.data.get_test_directory)
Error (including full traceback):

Command or request that led to error:
rasa test core --stories data/core

in rasa-demo
Content of configuration file (config.yml) (if relevant):

Content of domain file (domain.yml) (if relevant):

This is intentional, it was designed that way (I am not sure why but the conversation tests required a test/ folder). In terms of backwards compatibility, I am not sure we should change this.

Previously, you could test your model on the training set but now you can't :(
And in that function which I changed the filters which are used for YAML and MD are different

mhm interesting, it might be that it worked when specifying the directory and only the auto detection was looking for that specific folder. in that case I think you might be right and we should change it :+1:

I think this issue is actually harder than I thought...
what was the motivation for the test conversations to be only in the test/ folder? it seems like it was for end-to-end test stories but then we're not checking whether it is in use_e2e mode


Fixed the incorrect repo and url naming: react-theming -> storybook-boilerplate

Thank you very much!


Update string-natural-compare

The new version requires all values to be strings, so the values are forced to string values before calling sort.

Codecov Report

Merging #701 (965f95b) into master (f11f178) will not change coverage.
The diff coverage is 90.00%.

@@           Coverage Diff           @@
##           master     #701   +/-   ##
=======================================
  Coverage   93.54%   93.54%
=======================================
  Files          19       19
  Lines         837      837
  Branches      199      198    -1
=======================================
  Hits          783      783
  Misses         38       38
  Partials       16       16

Impacted Files
Coverage Δ

src/utils/index-of.js
50.00% <66.66%> (ø)

src/search.js
96.47% <100.00%> (ø)

src/sort.js
96.92% <100.00%> (ø)

src/utils/to-array.js
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


rpm not work in CentOS release 6.8 - Dependency: python(abi) = 2.7

cat /etc/redhat-release
CentOS release 6.8 (Final)
yum install centos-package-cron-1.0.8-1.el7.centos.x86_64.rpm
Loaded plugins: fastestmirror
Setting up Install Process
Examining centos-package-cron-1.0.8-1.el7.centos.x86_64.rpm: centos-package-cron-1.0.8-1.el7.centos.x86_64
Marking centos-package-cron-1.0.8-1.el7.centos.x86_64.rpm to be installed
Loading mirror speeds from cached hostfile
 * base: ftp.fau.de
 * epel: ftp.uni-stuttgart.de
 * extras: ftp.plusline.de
 * updates: mirror1.hs-esslingen.de
Resolving Dependencies
--> Running transaction check
---> Package centos-package-cron.x86_64 0:1.0.8-1.el7.centos will be installed
--> Processing Dependency: python(abi) = 2.7 for package: centos-package-cron-1.0.8-1.el7.centos.x86_64
--> Processing Dependency: python-sqlalchemy >= 0.5.5 for package: centos-package-cron-1.0.8-1.el7.centos.x86_64
--> Processing Dependency: yum-plugin-changelog >= 1.1.30 for package: centos-package-cron-1.0.8-1.el7.centos.x86_64
--> Running transaction check
---> Package centos-package-cron.x86_64 0:1.0.8-1.el7.centos will be installed
--> Processing Dependency: python(abi) = 2.7 for package: centos-package-cron-1.0.8-1.el7.centos.x86_64
---> Package python-sqlalchemy.noarch 0:0.5.5-3.el6_2 will be installed
---> Package yum-plugin-changelog.noarch 0:1.1.30-37.el6 will be installed
--> Processing Dependency: python-dateutil for package: yum-plugin-changelog-1.1.30-37.el6.noarch
--> Running transaction check
---> Package centos-package-cron.x86_64 0:1.0.8-1.el7.centos will be installed
--> Processing Dependency: python(abi) = 2.7 for package: centos-package-cron-1.0.8-1.el7.centos.x86_64
---> Package python-dateutil.noarch 0:1.4.1-6.el6 will be installed
--> Finished Dependency Resolution
Error: Package: centos-package-cron-1.0.8-1.el7.centos.x86_64 (/centos-package-cron-1.0.8-1.el7.centos.x86_64)
           Requires: python(abi) = 2.7
           Installed: python-2.6.6-66.el6_8.x86_64 (@updates)
               python(abi) = 2.6
           Available: python-2.6.6-64.el6.x86_64 (base)
               python(abi) = 2.6
           Available: python34-3.4.5-1.el6.i686 (epel)
               python(abi) = 3.4
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

I'm not sure where the = 2.7 dependency is coming from. The rpmspec lists this:
Requires:         python >= 2.6

I haven't committed the test yet but when I built a Docker image to replicate the problem noted in https://github.com/wied03/centos-package-cron/issues/18, I wasn't seeing this problem. Any more details you can provide?

i test this on 3 centos 6.8 systems.
On all my Centos 7.x systems its working...

what can i do to give you more informations?

I think the issue might be that you're trying to use the RPM built for CentOS 7 with 6. I haven't published the 6.x RPMs to the Github downloads section.

aaahhh, can you published the 6.x rpm for me ^^ :)

I'll try this week.
sent from my mobile device
On Feb 9, 2017 11:40 AM, "daswars"<EMAIL_ADDRESS>wrote:

aaahhh, can you published the 6.x rpm for me ^^ :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/wied03/centos-package-cron/issues/20#issuecomment-278697902,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AASIo6wwLyKyXdAT7i9vN7HVeJPPPukqks5ra0F-gaJpZM4L8PDy
.

@daswars - I uploaded el6 packages to https://github.com/wied03/centos-package-cron/releases/tag/releases%2F<IP_ADDRESS> generated with 6.7. They should work OK on 6.8. If not, let me know.


Other devices

Hi there and a big thank you for making this tool available!
Do you have any plans on integrating other devices types?
(RGB lights, radiator valves, other temperature sensors?)
Unfortunalty Javascript/Electron/ is not really my world -- I'd be willing to test, provide mqtt messages etc if that helps :)
Have a great day,
Felix

Maybe a port of https://github.com/Koenkk/zigbee2mqtt/blob/03ba647dc6b5f299f8f3ab441712999fcb3a253e/lib/extension/homeassistant.ts would be possible ?

Hi, I do not plan to actively add new devices other than the once I use or eventually some submissions (what is your use case?)
My current setup is to connect the device to Z2M (on my main location) and then copy the entries for use with the ZBBridge. (I use the ZBBridge in another smaller location, where I did not want to setup a full home-assitant/z2m).
Creating an automatic conversion is a lot of work, which is not needed since Z2M can already directly use ZBBridge over TCP https://www.zigbee2mqtt.io/advanced/remote-adapter/connect_to_a_remote_sonoff_zbbridge.html
Regards,
Boris

I have a zbbride with some switches, lights and valves at one location and want to connect it via mqtt to a home assistant instance running somewhere else -- so really similar to your setup.
It's an interesting idea to copy over the messages! I will try that out, thanks!


Support generated-from-java and hand-migrated ObjC together

@brunobowden  continuing our discussion from #56
how have you been tackling it?
btw, the way I'm doing this right now (until we can finish #51), is:

j2objc plugin attached to each of my individual Java projects (let this be JP), each with --build-closure.
a) translateExcludeClass for entire classes that just don't make any sense in ObjC land and no one depends on.
b) for libraries I don't control or want to muck too much with, I create a sparse parallel Java source tree which stubs out the methods not compatible with ObjC land.  then I add this sparse source tree to the translateSourcepath, while also keeping the original library's jar on the classpath.  (or if I have both the original and mine as sources, put them both in the sourcepath, with my overlay first)
a seperate gradle build project (that depends on all of the above ones) with a single task that copies all of the j2objcCopy output directories from projects in list JP into a single output directory.  They are copied in reverse order of the gradle project dependencies (i.e. if :appx depends on :libx, :appx's j2objcCopy destDir is copied into the final objc directory, and then :libx's destDir is copied on top of it.  this prevents any ill effect from '--build-closure', since the project that 'owns' that source is guaranteed to have the final overwrite for its translated ObjC files).
finally I overlay hand-written objc files in a sparse source tree on top of the output of (2).

I find this to be a somewhat cleaner approach than putting a bunch of OCNI in my code, and it isn't possible for libraries I don't control anyway.

You're ahead of me right now. I've deliberately limited myself to J2ObjC
standard libraries and what I've built myself. I'd quite welcome a design
doc around this and I'm planning to write a design doc for some other areas
myself. In general, I would like to make it easy to import a number of
standard libraries, e.g. okhttp and others.
On Wed, May 13, 2015 at 3:55 AM Advay Mengle<EMAIL_ADDRESS>wrote:

@brunobowden https://github.com/brunobowden continuing our discussion
from #56 https://github.com/brunobowden/j2objc-gradle/pull/56
how have you been tackling it?
btw, the way I'm doing this right now (until we can finish #51
https://github.com/brunobowden/j2objc-gradle/issues/51), is:

j2objc plugin attached to each of my individual Java projects (let this
by JP), each with --build-closure.
a) translateExcludeClass for entire classes that just don't make any sense
in ObjC land and no one depends on.
b) for libraries I don't control or want to muck too much with, I create a
sparse parallel Java source tree which stubs out the methods not compatible
with ObjC land. then I add this sparse source tree to the
translateSourcepath, while also keeping the original library's jar on the
classpath. (or if I have both the original and mine as sources, put them
both in the sourcepath, with my overlay first)
a seperate gradle build project (that depends on all of the above ones)
with a single task that copies all of the j2objcCopy output directories
from projects in list JP into a single output directory. They are copied in
reverse order of the gradle project dependencies (i.e. if :appx depends on
:libx, :appx's j2objcCopy destDir is copied into the final objc directory,
and then :libx's destDir is copied on top of it. this prevents any ill
effect from '--build-closure', since the project that 'owns' that source is
guaranteed to have the final overwrite for its translated ObjC files).
finally I overlay hand-written objc files in a sparse source tree on
top of the output of (2).

I find this to be a somewhat cleaner approach than putting a bunch of OCNI
in my code, and it isn't possible for libraries I don't control anyway.
—
Reply to this email directly or view it on GitHub
https://github.com/brunobowden/j2objc-gradle/issues/59.

Heh looks like I fixed this in #158

@advayDev1 Awesome!

@confile, you can try it out by using extraObjcSrcDirs in j2objcConfig

@advayDev1 Okay I will check it

@advayDev1 Shouldn't this be named extraJavaSrcDirs because it specifies additional Java sources?

@advayDev1 I check this out when it gets merged or do you want me to checkout your pull request?

No.  Extra java directories should be added to your main SourceSet.  Remember we aren't using anything but sourceSets for Java now.
This is .m or .h files that you have written that should be used in addition to translated ones in order to compile your library.  This occurs for example when you want to provide a native ObjC implementation of a given function.

@advayDev1 Yes, got it. I add additional source dir with this
sourceSets {
  main {
    java {
      srcDir 'build/source/apt'
      srcDir 'build/source/base'
    }
  }
}

Why do we need  generatedSourceDirsanymore? Why do I need extraObjcSrcDirs?

extraObjcSrcDirs is needed when, for example, you have JNI methods that need objective-c replacements.  (I use this at the moment, there is no way to replace it with Java).
I don't know about generatedSourceDirs, I don't use it myself, as I do what you do above.  If you feel we can remove it, please file a separate issue.