MudSpacer component and API (if any) is not documented anywhere

Bug type
Docs (mudblazor.com)
Component name
MudSpacer
What happened?
I cannot find any documentation about MudSpacer - either defining its behaviour, or documenting any API it might have (though Visual Studio Intellisense seems to indicate it has nothing anyway).  It gets used and mentioned from time to time, so I feel it ought to at least be described in the documentation.  Some clarity as to what it can and cannot do would be helpful.
For example, I have a flex MudContainer with a row of buttons, justified to start, except I want the final button to justify left.  Perhaps I can do it with a MudSpacer?  Perhaps I can set flex Classes on a MudSpacer?  I have no way of determining this except through tedious experimentation.
Expected behavior
MudSpacer should be included as a Component in the documentation set.
Reproduction link
https://mudblazor.com/docs/
Reproduction steps
Go to https://mudblazor.com/docs/
Search for "Spacer" and "MudSpacer"
Check the list of Components for "Spacer"
Check the API list for "Spacer"
Relevant log output
No response
Version (bug)
6.0.17
Version (working)
No response
What browsers are you seeing the problem on?
Other
On what operating system are you experiencing the issue?
Other
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Agreed.  Even if it were just an empty page that would work.


Jenkinsfile

Jenkinsfile will automate build/test/deploy for Docker version of PanelSearch but not conda

Jenkinsfile has been tested. Build works. Testing currently fails because tests branch is needed. Deploy will work if tests pass.
.idea and pycache directories have been deleted


non-Python type signatures in docs are confusing for a Python package

The docs include confusing type signatures, using what I assume is Haskell syntax (please correct me if I'm wrong---I never learned Haskell). Two examples I found are:
https://jax.readthedocs.io/en/latest/_autosummary/jax.lax.scan.html#jax.lax.scan
https://jax.readthedocs.io/en/latest/_autosummary/jax.lax.fori_loop.html#jax.lax.fori_loop
PS: sorry, I didn't see an option to report an issue with the docs, so just used the "bugs" issue template.

Re-opening and assigning to @mattjj in case we want to add more info (cf. https://github.com/google/jax/pull/10700#pullrequestreview-973028228)


[DOC]GeoIP processor

What do you want to do?

[ ] Request a change to existing documentation
[X] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
We are targeting OpenSearch 2.8 to release GeoIP processor with auto database update. This feature is an enhancement of existing GeoIP processor. With this enhancement, a user can associate GeoIP processor with GeoIP database in an external endpoint. The GeoIP database will get updated periodically in the background while a user keep using GeoIP processor. Current GeoIP processor does not support auto update of GeoIP database.
FYI, we do not have a document for GeoIP processor which has been available since 1.0.x.
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
https://github.com/opensearch-project/OpenSearch/issues/5856
https://github.com/opensearch-project/OpenSearch/issues/5860

This got moved to the 2.10 train during the project call today.


Add/Improve unit tests for compaction with histogram

NOTE: this is for sparsehistogram branch.
This PR takes care of the following from #11171
- [ ] Compaction
	- [ ] normal compaction works (head block compaction and merging of 2 non-overlapping blocks)
		- [ ] Only histograms in a series (with other float series)
		- [ ] Mix of histograms and float in a series in the same block (with other float series)
		- [ ] One block having histogram series and the other block having float series
		- [ ] Multiple blocks having a mix of float and histograms for the same series
	- [ ] Vertical compaction works
		- [ ] A series with only histograms overlaps with a series with only histograms
		- [ ] A series with only histograms overlaps with a series with histograms and float
		- [ ] A series with only histograms overlaps with a series with only float
		- [ ] A series with histograms and float overlaps with a series with only float

The PR

Improves the existing head compaction test
Removed an unnecessary test that was testing block compaction.
Extend existing query on blocks test to also do compaction test

Even a rerun isn't helping. The failure happened before as well. The test passes locally and the error logs that say failed to open meta.json also appear in the passed test, so I don't think that is the problem. I will see what is up.

Closing in favour of https://github.com/prometheus/prometheus/pull/11342 and https://github.com/prometheus/prometheus/pull/11343. I will investigate the error in those PR.

Error is from changes in db_test.go


[rom] Disable the self hash test

Do we want to wait to merge this until the RTL blocker on master branch is removed? Since this test is part of the blocker: https://github.com/lowRISC/opentitan/blob/b4377652ece3609ff30b2da424a561f0a10807f6/BLOCKFILE#L127

Do we want to wait to merge this until the RTL blocker on master branch is removed? Since this test is part of the blocker:
https://github.com/lowRISC/opentitan/blob/b4377652ece3609ff30b2da424a561f0a10807f6/BLOCKFILE#L127

The self hash test will block merging ownership transfer related code to master since it touches silicon_creator libraries and drivers.

./ci/scripts/check_dv_sw_images.sh is failing due to this. Why is this disabled, and could this be done using different method, e.g. commenting out non-DV execution environments?


Build broken

Hi All
We are aware that the build is broken and are in the process of resolving the issue.
Kealan

FTR I'm still using the old version of the cmake build system, waiting to find some time to study the switch. I clearly see why you need a to improve the build system and why this is not easy, because of the way milagro generates files.
What I wonder is if substituting cmake with meson and ninja could help: the latter is inherently designed to provide two build stages, while keeping very simple and somehow similar to makefiles.

I think that the refactored cmake build is really very good. The issues I think that we need to address is the Makefile on top of cmake which is very confusing.
BTW the build is now passing.


Add background-color and border for modal header and modal footer

fixes #113

Original header contains extra style for close button (compare two screenshots)


test: unit xmir test for rule 2 transformation

Add unit test for 2-1-substitute-applications.xsl transformation. Closes #50

Codecov Report

Merging #59 (0eafd88) into master (d3260f6) will decrease coverage by 0.55%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##             master      #59      +/-   ##
============================================
- Coverage     88.63%   88.09%   -0.55%
+ Complexity        9        8       -1
============================================
  Files             2        2
  Lines            44       42       -2
  Branches          3        3
============================================
- Hits             39       37       -2
  Misses            5        5

Impacted Files
Coverage Δ

src/main/java/org/eolang/speco/Speco.java
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@volodya-lombrozo please help

@yegor256 This one can also be merged)

@rultor merge

@yegor256 Thanks!

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 10min)


Add integration and unit tests for auction APIs

Add integration and unit tests for auction APIs
Corresponding PR: https://github.com/Real-Dev-Squad/website-backend/pull/225/files

Closing as this is a duplicate of https://github.com/Real-Dev-Squad/website-backend/issues/234


Improve performance

Look into improving performance of panoptes. Use Spring Boot? Netty? Go?

Akka-http?

We've been running this for 5 years now. Performance is pretty good.


Crash when minimizing and opening the app again

Steps to reproduce:

Open the camera (Demo app also)
Go to homescreen
Switch back to the App
Camera is black. Click on it and it crashes.

Same issue, quite annoying. Except that, great library, thanks a lot btw :)

Resolved in f135f2a99f374e66b6d8f21bd7d1ee09610df894


Fix phedex delete call - wmagent version

wmagent version of #8625
We missed this delete call when these changes https://github.com/dmwm/WMCore/pull/8164 were applied, and now (well, for half an year, the T0 agent fails to delete blocks...)

I meant to backport it to 1.1.12 instead of 1.1.10...


enhancement disable sync rocksdb by default for better performance

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


C++ catching/finding connection and stream errors  & continuous/infinite speech recognition

Hi,
I'm building an example (c++ based) in which I've a GRPC server which receives continuous audio 100 milli second chunks/bytes (using GRPC bidirectional streaming) from client (real time audio speaking from mic). My server code sends the audio to Google cloud speech to get text from speech. I'm using this example streaming_transcribe.cc. I've three questions:

How do I handle errors like:  when I can not connect to google speech or can not create a channel due to network connectivity issues or server is down, how to catch such exceptions ? Also the stream errors out in the middle of streaming audio (google closes streaming due to time exceeds or long pauses), where and how can I handle such errors.

Client can keep sending audio for long duration ( may be like 1 hour). When the google speech stream is open for more than 5 mins, I'm getting the following error Exceeded maximum allowed stream duration of 305 seconds. The streamingrecognize requests have a limitation of 5 mins it seems as mentioned here. The same page mentions a few examples about endless streaming tutorials with some code in java and python. If I can get an example of how to implement this in c++ in https://github.com/GoogleCloudPlatform/cpp-samples/blob/master/speech/api/streaming_transcribe.cc, that would be very helpful, at least a peudo code.
The examples mentioned in endless streaming tutorials closes current stream and reconnects new stream after about 290 seconds. But in the streaming_transcribe.cc, the stream is passed to a thread for writing audio bytes to the stream and the main thread reads responses from stream. How to close and create a new stream in the MicrophoneThreadMain (https://github.com/GoogleCloudPlatform/cpp-samples/blob/master/speech/api/streaming_transcribe.cc#L36)  function ?
A similar thread has been posted here but It was not that helpful for me.

How do we implement backoff and reconnect to Google stream (speech server) in case of errors (https://cloud.google.com/speech-to-text/sla). If I know how to catch or find the connection has errors (asked in [1], then we can implement this but it would be great to provide an example.

Any help is much appreciated , Thank you very much.

I found the above conversation very very helpful.  Actually in my implementation, I have a parent program which is written in C. Whenever a transcribe request is made to the parent program, It forks to this C++ application providing a named pipe in argument to send audio to this C++ program which can be further sent to Google, and when the inactivity is detected. C++ sends finish() request to get the final response. Till then the parent program is waiting with waitpid(). After the C++ program exits, parent program picks up the PID and does rest of the processing.
My question is, is this design okay or should I change it?

I found the above conversation very very helpful.  Actually in my implementation, I have a parent program which is written in C. Whenever a transcribe request is made to the parent program, It forks to this C++ application providing a named pipe in argument to send audio to this C++ program which can be further sent to Google, and when the inactivity is detected. C++ sends finish() request to get the final response. Till then the parent program is waiting with waitpid(). After the C++ program exits, parent program picks up the PID and does rest of the processing.
My question is, is this design okay or should I change it?

My question is, is this design okay or should I change it?

This is a difficult question to answer.   Since you are using both C and C++ the idea of forking a process seems fine.  Whether a named pipe has the necessary capacity and does not get full, deadlocking your two programs, is a different question.  Blocking on waitpid() without reading from the pipe or allowing for timeouts seems dangerous to me, I would consider pselect() to wait for I/O, signals (SIGCHLD in this case), and a timeout, all at the same time.

My question is, is this design okay or should I change it?

This is a difficult question to answer.   Since you are using both C and C++ the idea of forking a process seems fine.  Whether a named pipe has the necessary capacity and does not get full, deadlocking your two programs, is a different question.  Blocking on waitpid() without reading from the pipe or allowing for timeouts seems dangerous to me, I would consider pselect() to wait for I/O, signals (SIGCHLD in this case), and a timeout, all at the same time.

Seems like the questions posed here are answered. Closing


s/netherland/netherlands

Either should be Nederland which is how it is called in Dutch, or the Netherlands, which is how it is called in English. There's no in between.

thanks!


Documentation Change - Fixes #92

Documentation Change - Fixes #92
Description:
This PR addresses issue #92 by making modifications to the README.md file. The changes primarily focus on enhancing the documentation for better clarity and understanding.
Changes Made:

Modified the README.md file.
Enhanced the appearance of the README.md file
Included information on preparing data, running the Databus server, publishing the first artifact, and querying metadata

Context:
Issue #92 highlighted the need for improved documentation regarding storage options in the README.md file. This PR aims to fulfill that need by providing a comprehensive guide on storage options within the README.md file.
Related Issues:

Closes #92

Checklist:

[ ] The documentation changes have been reviewed and approved.
[x] The PR has been tested for accuracy.
[x] All checks have passed.

Thank you for sending pull request! We will review asap and merge if agree with the changes :). Our team atm is quite busy, so it may take more than a week!

@Debaditya-Som hey! I do not understand how do your changes address #92 What I see is that you just did some minor changes in the docs more like beutify... In general I don't see why would we use them...
#92 is about make a guide like https://dbpedia.gitbook.io/databus/guides/publish-guide for different storage options for files.

@Debaditya-Som hey! I do not understand how do your changes address #92 What I see is that you just did some minor changes in the docs more like beautify... In general I don't see why would we use them...
#92 is about make a guide like https://dbpedia.gitbook.io/databus/guides/publish-guide for different storage options for files.

@Debaditya-Som hey! I do not understand how do your changes address #92 What I see is that you just did some minor changes in the docs more like beautify... In general I don't see why would we use them...
#92 is about make a guide like https://dbpedia.gitbook.io/databus/guides/publish-guide for different storage options for files.

Okay so I need to create a guide like the one mentioned.
Yes actually this PR modifies the README.md file and enhances it to make it more appealing to the users and contributors. I'll surely work on making a guide like the one you have mentioned.
Thank you.

I will close this pull request, feel free to submit a new one, but related to an open issue.

@manonthegithub
Okay I'll work on that issue accordingly
Can I open an issue regarding enchantment of the README.md files and work on that too as in my opinion the README.md could have been more appealing and user friendly that it is currently?

@Debaditya-Som sure you are free to create new issues. It is just not our priority to work on prettifying readme atm (the changes you propose are quite arguable in my opinion and do not bring much value), so it may take some time (weeks). We were also planning to change the readme in the future as we already had some arguing on what should be left there and what moved to other parts of the documentation...

@Debaditya-Som what is important also, so when you create pull requests or issues, not just to propose changes, but motivate what is wrong and how your changes improve current situation, and the motivation should be compelling/obvious to the others. So far, you did not motivate your changes except saying that in your opinion it is better (not really compelling). to motivate better first decribe the problem (like it is hard to navigate or see information or whatever) and then explain how your solution (pull request) solves it. Then it could be discussed.

@Debaditya-Som what is important also, so when you create pull requests or issues, not just to propose changes, but motivate what is wrong and how your changes improve current situation, and the motivation should be compelling/obvious to the others. So far, you did not motivate your changes except saying that in your opinion it is better (not really compelling). to motivate better first decribe the problem (like it is hard to navigate or see information or whatever) and then explain how your solution (pull request) solves it. Then it could be discussed.

Surely, I will look forward to contribute in an issue that is more motivating. But in my opinion having a user friendly and enhanced README.md would attract more users to contribute in this particular project and make it more convenient for the and contributors to understand the motive and workflow of the particular project. So, that's the main reason behind this PR

@Debaditya-Som sure you are free to create new issues. It is just not our priority to work on prettifying readme atm (the changes you propose are quite arguable in my opinion and do not bring much value), so it may take some time (weeks). We were also planning to change the readme in the future as we already had some arguing on what should be left there and what moved to other parts of the documentation...

Alright then for the time being shall I create an issue regarding this and work on this minor issue? I know that its not of much importance but it will certainly have a positive impact on the whole project and repository


Extracted characters in SpreadsheetExtractionAlgorithm missing first character

Cell text extracted using SpreadsheetExtractionAlgorithm is missing the first character if the character is very close to the cell boundary. Whereas same can be read using BasicExtractionAlgorithm.
In the attached jpg, for the cell having text 'No SS Number', using SpreadsheetExtractionAlgorithm, value read is 'o SS Number'
Please suggest how can I read the entire cell text using SpreadsheetExtractionAlgorithm.

A JPG unfortunately isn't enough, if you can, please provide the PDF.
The first thing I would do now, just out of curiosity because I just read it in another issue and would like to try it:java -cp tabula-0.9.1-jar-with-dependencies.jar technology.tabula.debug.Debug -p [PAGE] -r the.pdf
This will create a the-PAGE.jpg in the PDF's directory showing the detected rulers, which could tell use if the detected rulers are "wrong". This JPG would be helpful :D
Enjoy!

I've observed this off-by-one error on page 102 of this PDF file.

java -cp tabula-1.0.1-jar-with-dependencies.jar technology.tabula.debug.Debug -page 102 -r 0930AQ-carillion-annual-report-2016-original.pdf


Cannot build "hello-edge" template

Describe the bug
Heyoooo !
I've cloned your starter project https://github.com/nuxt-hub/hello-edge and tried to build but without success.
Steps to reproduce
Steps to reproduce the behavior:

git clone
cd hello-clone
pnpm i
pnpm run dev
pnpm build
Have an error :

[nitro 18:51:40]  ERROR  RollupError: node_modules/.cache/nuxt/.nuxt/dist/server/server.mjs (7:9): "CapoPlugin" is not exported by<EMAIL_ADDRESS>imported by "node_modules/.cache/nuxt/.nuxt/dist/server/server.mjs".

5: import { sanitizeStatusCode, createError as createError$1 } from "h3";
6: import { setHeadInjectionHandler } from "@unhead/vue";
7: import { CapoPlugin } from "unhead";
            ^
8: import { START_LOCATION, createMemoryHistory, createRouter as createRouter$1, RouterView } from "vue-router";
9: import { toRouteMatcher, createRouter } from "radix3";

[18:51:40]  ERROR  node_modules/.cache/nuxt/.nuxt/dist/server/server.mjs (7:9): "CapoPlugin" is not exported by<EMAIL_ADDRESS>imported by "node_modules/.cache/nuxt/.nuxt/dist/server/server.mjs".

  at getRollupError (node_modules/.pnpm/rollup@4.27.2/node_modules/rollup/dist/es/shared/parseAst.js:396:41)
  at error (node_modules/.pnpm/rollup@4.27.2/node_modules/rollup/dist/es/shared/parseAst.js:392:42)
  at Module.error (node_modules/.pnpm/rollup@4.27.2/node_modules/rollup/dist/es/shared/node-entry.js:15980:16)
  at Module.traceVariable (node_modules/.pnpm/rollup@4.27.2/node_modules/rollup/dist/es/shared/node-entry.js:16427:29)
  at ModuleScope.findVariable (node_modules/.pnpm/rollup@4.27.2/node_modules/rollup/dist/es/shared/node-entry.js:14210:39)
  at Identifier.bind (node_modules/.pnpm/rollup@4.27.2/node_modules/rollup/dist/es/shared/node-entry.js:5211:40)
  at CallExpression.bind (node_modules/.pnpm/rollup@4.27.2/node_modules/rollup/dist/es/shared/node-entry.js:2704:23)
  at CallExpression.bind (node_modules/.pnpm/rollup@4.27.2/node_modules/rollup/dist/es/shared/node-entry.js:11593:15)
  at ArrayExpression.bind (node_modules/.pnpm/rollup@4.27.2/node_modules/rollup/dist/es/shared/node-entry.js:2700:28)
  at ExpressionStatement.bind (node_modules/.pnpm/rollup@4.27.2/node_modules/rollup/dist/es/shared/node-entry.js:2704:23)

[18:51:40]  ERROR  node_modules/.cache/nuxt/.nuxt/dist/server/server.mjs (7:9): "CapoPlugin" is not exported by<EMAIL_ADDRESS>imported by "node_modules/.cache/nuxt/.nuxt/dist/server/server.mjs".

Expected behavior
Build OK

Can you please use Node 20 at least?

Can you please use Node 20 at least?

I'm on v20.18.0

Why do I see ../../.nvm/versions/node/v16.14.0/... then?
I guess you may have the Nuxt Devtools installed globally, make sure to install it locally then

Olala @atinux , thank you for putting me on the right track... I really didn't understand why it forced a version of node for Nuxt Devtools when I could change it just fine with nvm..
And then, I discovered the existence of the .nuxtrc file. It contained a configuration for a global installation of @nuxt/devtools with a specific version. I removed this and everything works fine now 🙏 Thanks again

My pleasure 🙂


ci: add automatic PR labeler

Description

This PR labels PR automatically depending on edited file names.
Following labels should be added:

component:control
component:localization
component:map
component:perception
component:planning
component:sensing
component:simulation
component:system

Tests performed

Not applicable.
Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

Thanks for the update and contribution.
Personally I also suggest the label for [RViz] *.rviz file and [Doc] *.md file

Thanks for the update and contribution. Personally, I also suggest labels like [RViz] *.rviz file and [Doc] *.md file to make the labeler more complete.

@Owen-Liuyuxuan Thanks for your suggestion. In that cases, what do you think the suitable name of label for *.rviz?

For documents, I suggest following AWF/universe:
https://github.com/autowarefoundation/autoware.universe/blob/main/.github/labeler.yaml
"type:documentation":
  - docs/**/*
  - "**/*.md"
  - "**/*.rst"
  - "**/*.jpg"
  - "**/*.png"
  - "**/*.svg"

For RViz, reference are limited, but I would suggest component:visualization

@Owen-Liuyuxuan Sorry for late reaction. I updated the labeler configuration. Could you check this out? https://github.com/autowarefoundation/autoware_launch/pull/972/commits/4e17ef8f66b92cb661c28a528c1cdb70b47edd03
If it is OK, I will add new labels.

This looks good, once this is done, we need something like https://github.com/lannonbr/issue-label-manager-action on main repositories too. If you have time and you could set it up, I would be very happy.
Until now I've been keeping track of the labels manually in here: https://docs.google.com/spreadsheets/d/1JWQ-PfGamJ_2TO2dM0TV5OQQF1PztpWKIm9O5sI3fQk/edit?usp=sharing

For RViz, reference are limited, but I would suggest component:visualization

I would go with component:ui

For RViz, reference are limited, but I would suggest component:visualization

I would go with component:ui

I've applied component:ui

I added new corresponding labels

type:**: https://github.com/autowarefoundation/autoware_launch/labels?q=type
component:**: https://github.com/autowarefoundation/autoware_launch/labels?q=component


Create views for User application.

The User application needs views. Focusing on these three:

User Homepage
Login
Logout

https://github.com/eliaseraphim/blog/commit/c3ab0f167d0bba2405b22d5f7c3d72767679e204
Views for User/login/logout are done satisfactory for now.


Check the channel names?

Describe the bug
During the demo, the Vanderbilt folks said that the first channel, the nuclear stain, doesn't look like it's being applied to nuclei.
It's possible they are confused, or the source data is mislabeled?

We fixed this in vitessce-data https://github.com/hubmapconsortium/vitessce-data/pull/90


Feature/contacts list api

Implement Rest-Api actions for the contact avatar
tasks:

[ ] gather feedback for my changes
[x] test coverage
[x] cget-action and fields-action for contact media
[x] cget-action and fields-action for account media

Depending PRs:

merge after: https://github.com/sulu-io/sulu/pull/1472

informations:

q
a

Fixed tickets
none

BC breaks
none

Documentation PR
none

General code style: PHPDocs start with capital letters, please correct that in every comment.

@danrot your comments are fixed

There is a check missing, if you access one of these media controller with a not existing user id (e.g. /contacts/15124/medias) a 500 error is returned, whereby it should probably be a 404.


Lwm2m bootstrap tests

This PR implements

LightweightM2M-1.1-int-4 - Bootstrap Delete
LightweightM2M-1.1-int-5 - Server Initiated Bootstrap
LightweightM2M-1.1-int-6 - Bootstrap Sequence
LightweightM2M-1.1-int-7 - Fallback to bootstrap
LightweightM2M-1.1-int-103 - Deregistration

These tests depends on functionality added in https://github.com/zephyrproject-rtos/zephyr/pull/65745

Rebased on top of main.
Fixed those compliance issues.


Print locale in flutter doctor

This helps to debug encoding issues that are believed to only happen for certain locales (see https://github.com/flutter/flutter/issues/10198 for example).
DO NOT SUBMIT until Dart SDK has been bumped (https://github.com/flutter/flutter/pull/10110) as this depends on new API form Dart 1.24.


Input does not render correctly in StackNavigator

Hi there,
I've a weird display of input inside navigator.
Could you help me on this please ?
Thanks
react-native, react and native-base version
"native-base": "^2.3.10",
"react-native": "0.54.1",
"react-navigation": "^1.5.1"

Expected behaviour
Normal input rendering
Actual behaviour
Weird border, placeholder misplaced
Steps to reproduce (code snippet or screenshot)
import React, { Component } from 'react';
import { Container,Header, Content, Input, Item } from 'native-base';
import { StackNavigator } from 'react-navigation';

class Home extends Component{
  render() {
    return(
        <Item regular>
          <Input placeholder="Render Ko" />
        </Item>
    );
  }
}
const Navigator = StackNavigator({
  Home:{screen:Home}
},{headerMode:'none'})

export default class App extends Component {
  render() {
    return (
      <Container>
        <Header/>
        <Content>
          <Item regular>
            <Input placeholder="Render Ok" />
          </Item>
          <Navigator />
        </Content>
      </Container>
    );
  }
}

Screenshot of emulator/device

Is the bug present in both ios and android or in any one of them?
Present on iOS, not tested on android

NB: 2.3.10
RN: 0.54.0


Dockerize Part 2

[x] Changed base to Alpine linux to reduce image size
[x] Dockerized Block Store

Did a review - looks awesome. Waiting on travis, then will merge.

LGTM, and tests passed, merging.


Create chinese_remainder_theorem.py

Add it as my contribution

Have you read the Contributing Guidelines on Pull Requests?
(Write your answer here.)
yes I have read.
Description
(Write your answer here.)
This is code for the Chinese remainder theorem in python.
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
(Write your answer here.)
def multiply_fun(li):
result = 1
for i in li:
result *= i
return result
k = int(input("Enter size of array : "))
print("Enter value of coprime divisors :", end=' ')
n = list(map(int, input() . split()))
print("Enter value of remainders :", end=' ')
a = list(map(int, input().split()))
def chineserem(n, a):
sum = 0
pr = multiply_fun(n)
for n_i, a_i in zip(n, a):
p = pr/n_i
sum += a_i * muinv(p, n_i)*p
return sum % pr
def muinv(a, b):
b0 = b
x0, x1 = 0, 1
if b == 1:
return 1
while a > 1:
q = a//b
a, b = b, a % b
x0, x1 = x1 - q * x0, x0
if x1 < 0:
x1 += b0
return x1
print("x = ", chineserem(n, a))
Sample Input -->
Enter size of array : 3
Enter value of coprime divisors : 2 3 5
Enter value of remainders : 1 2 4
Output -->
x =  29.0
it is the program of the Chinese remainder system in python please add it as my contribution

please check

update readme.md file

i have updated readme @atarax665 @iamrajiv  plz merge it and make me assignee

@all-contributors add @ashu-cybertron  for code :+1:


Kapture last N seconds…

Inspired by RetroClip, it'd be interesting to explore a feature allowing you to capture the last few seconds or minutes of your primary/active display. That means that, if enabled, Kap is constantly recording the full screen in the background.
From Kap in the menubar you would be able save a clip, which could have a customisable predefined length (defaulting to 30 seconds?). On saving, you are immediately presented with a preview of the recording in the editor, allowing you to export as normal – with the benefits of trimming, plugins, and formats including GIF.

This would require adding a new method to Aperture to record into a rotating memory buffer instead of a file.

While looking for resources, I stumbled upon this, which describes exactly how to implement this feature including AVFoundation code snippets in Swift.
https://engineering.giphy.com/doing-it-live-at-giphy-with-avfoundation/
Keeping it here for when I attempt to implement it, or for anyone else who wants to give it a try


Third Round (Still Alpha) Release

Small Steps to reach a better UX

accidentally committed with #3 in that sprint


no excerpt: breaks search

If the excerpt: is not in the YAML front matter, the search will break, because the default page.excerpt ist surrounded with  and then the search did not show an result.
Currently I do not know how to get the default excerpt (first paragraph) without the html paragraph.

{{ page.excerpt | strip_html | strip_newlines }}
might help. But if there are some other formattings it will break again, as on my site.

Probably going to remove excerpts from search. It's way too fragile of a solution to guard against since everyone does their posts differently.

Fixed in 808c1043dfed9ee173bea9c740e5aa655407ff0a


Add the computation of t

Description
Following the notation from Ligero's paper (https://ia.cr/2022/1608), t denotes the number of columns that the verifier asks the prover to open.
I tried to explain the logic in the comments. There are two questions:

Should we care about the value $\frac{n}{|\mathbb{F}|}$? I think we can simply ignore it.
We are computing t with the assumption that we only have unique decodability. Namely, the relative distance is not greater than $\frac{1-\rho}{2}$. Should we change this to a smaller distance? And why? As far as I understand, computing for a weaker distance guarantee is better.

Refs: [BCI+20]
closes: #22

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (master)
[ ] Linked to Github issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[ ] Wrote unit tests
[ ] Updated relevant documentation in the code
[ ] Added a relevant changelog entry to the Pending section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer

I believe we can remove $\frac{n}{|\mathbb{F}|}$. Let us have a semi-concrete example.
First of all, we should have $\frac{n}{|\mathbb{F}|} < 2^{-\lambda}$, and otherwise, the computation of t is meaningless. Preferably, we want $\frac{n}{|\mathbb{F}|}$ to be significantly smaller than $2^{-\lambda}$. Say, we want $\frac{n}{|\mathbb{F}|} = 2^{-(\lambda+z)}$ for some positive integer $z$. Say $n$ is around $2^{20}$. Then, we need $|\mathbb{F}| \geq 2^{\lambda + z +20}$. Assuming $\lambda =128$, this means with such $n$, any field with a size more than 151-152 bits is suitable for us to ignore the term $\frac{n}{|\mathbb{F}|}$ while calculating t. Or, for $\lambda=80$, we require a field with a size bigger than 104 bits.
It is fair to assume that the used fields are as big as mentioned. I think.

@giorgos-ml Can you confirm if the argument above makes sense?


Update K8s default to 1.20, also test 1.17

Use the new ability of the shared E2E GHA to configure the Kubernetes
version to add a CI matrix dimension for K8s versions.
Change the default K8s version tested in E2E to be the latest K8s
version, providing good coverage for minimal additional jobs.
Test 1.17 as it is the version we currently build with, and doing so
provides default-E2E coverage for the oldest version we support.
Signed-off-by: Daniel Farrell<EMAIL_ADDRESS>

We could easily add 1.17 or 1.18 if we want that coverage, but given the push-back to adding more jobs I wanted to propose the absolute minimum.

We could easily add 1.17 or 1.18 if we want that coverage, but given the push-back to adding more jobs I wanted to propose the absolute minimum.

As noted in the other PR, perhaps we should test against 1.17  instead of 1.19 since we build against it. So full coverage for 1.20, sanity check for 1.17 and skip in between.

I think we should try to have gating 1.19 coverage eventually, as it's a version we want to be sure to support as I understand it. I'll work on updating from 1.17 elsewhere, then we can change this 1.17 job to a 1.19 job.


AAD Linux Login Public Preview Refresh

I updated the existing document to contain a number of changes and updates related to the upcoming public preview refresh of the feature. The main things added:

Feature specific changes
Linux version number changes
More robust AZ CLI instructions
MSI instructions
Cloud Shell instructions
VM Scale Set instructions

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

Hi @mepples21
This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. Also, substantial updates should be made in the private repo so that the changes and additions pass the validations and quality checks that are applied in the private repo. (For example, images that are referenced in an article must be added to the repository; they can't be referenced through links to a website. And, images that are added to the repo must meet standards that are defined in the internal contributor guide. )
Would you make this content update in the private repo instead? Let me know if you need information about doing that; I can email it to you.
We'll close this PR. Thanks.

Thanks, any details you can share via email would be great


fix: handle null test cases in strategy generation

Add null/undefined checks for strategy test cases
Update strategy results to accurately reflect valid test count
Prevent 'Cannot read properties of undefined (reading metadata)' error

any idea where these nulls come from? 👿


'point_cloud' in ddad dataset not found.

Hello, I attempt to reproduce training and test on DDAD dataset and faces multiple errors. I'd like to ask about the 'point_cloud' in ddad dataset. First, the point_cloud in DDAD.tar are in .npz file but not .npy file, Then, the camera timestamp index_temporal does not match file name of point cloud. Last, the point_cloud seems not used later. Should I just neglect the point cloud file?

I eval the DDAD dataset with official checkpoint and gets the log
ddad_log.txt. Is it normal for depth prediction?

I eval the DDAD dataset with official checkpoint and gets the log ddad_log.txt. Is it normal for depth prediction?

Yes, it is normal though a little worse than my test, you can do some 3d occ visualization.

Hello, I attempt to reproduce training and test on DDAD dataset and faces multiple errors. I'd like to ask about the 'point_cloud' in ddad dataset. First, the point_cloud in DDAD.tar are in .npz file but not .npy file, Then, the camera timestamp index_temporal does not match file name of point cloud. Last, the point_cloud seems not used later. Should I just neglect the point cloud file?

Yes, you can neglect the unused files.


Multiline in debugger

In a normal Julia REPL the following works fine
julia> 5 +
       2
7

However, in the debugger within Juno, using Juno.@run, I can't find a way to enter a multiline statement.
debug> 5 +
ERROR: syntax: invalid syntax (incomplete #<julia: "incomplete: premature end of input">)
Stacktrace:
...

will be fixed by https://github.com/JunoLab/Atom.jl/pull/218

nice


Add missing space

Yeah, I know - very trivial, but ¯_(ツ)_/¯ :)

@dracan If you signed the CLA agreement, can you just respond to this with "I signed it" and I will get this merged? Thanks.

I signed it

All that for a single whitespace character ;)

thanks!


Revert "fix(deps): update dependency three to v0.155.0"

Reverts Magickbase/ckb-explorer-frontend#78

This dep is reverted because the color-mix in banner is abnormal


avoid panic when using cancel and the Rc is still live

Included test demonstrates the scenario; I don't think a panic is warranted in this case and that we can safely return None because the entry was removed by the cancel method

Published in 1.2.0


Replaces Route Handlers with Server Actions

This replaces the POST, PUT, and DELETE handlers with Server Actions`.
This affects the following actions in the app:

Adding items to the cart
Removing items from the cart
Updating item quantity in the cart

Closes #1018
Fixes #1011, #989

This is ready for review. I noticed an existing issue with the cart that I was going to try and also fix in this PR, but decided to not to, otherwise it would get too noisy with unrelated changes.
The issue, which is not due to these changes, it logged in https://github.com/vercel/commerce/issues/1051.

I noticed the same bug, good call out 👍


Added support for matplotlib additive plot

Hi,
I have started porting the Additive visualizer code from JS to matplotlib (https://github.com/slundberg/shap/issues/27). It is in a state where the code currently works, at least on the examples I was able to test on. However some functionality is not supported: custom color maps for example.
As it is still a draft, the code can be improved by increasing modularity and test more edge cases.
To plot a using matplotlib instead of JS, use:
shap.force_plot(explainer.expected_value, shap_values[i], X_test.iloc[i], link='logit', matplotlib=True, show=True)
instead of:
shap.force_plot(explainer.expected_value, shap_values[i], X_test.iloc[i], link='logit')

Thanks!! This is a great feature to have. I'll review as soon as can (which isn't today unfortunately).

Looking through this is doesn't change any current functionality, so I am going to merge it for now and I'll suggest any improvements once I have time to test it out fully.

Thanks again for adding this :)
I had a chance to try it out, and overall it looks great! A few things it would be good to address at some point (either you or I or someone else):

#275 seems like a simple fix
I added an error check if people try to use matplotlib = True when multiple samples are passed.
There a few differences from the JS version would be good to adjust for the sake of consistency:

Base value doesn't fall in the center of the plot.
labels are not centered under a bar segment.
font sizes seem a bit smaller
some minor spacing differences and line fade effects

If you have any thoughts on these ideas let me know!


Component Webpack and Tests

This PR implements Webpack component bundling and a testing environment/framework for all JS components and utilities.
Please see the "Important Info" section below.
Motivation and Context

In order to provide automated testing for Components and their utilities, as well as having a manageable module structure, we need to be able to use ES6 imports easily. Webpack essentially forms a tree of all import/export dependencies and "bundles" them into a single JS file, which is then required by the page.htmlfile.

We need a way to manage modules and also to easily test components.

Approach

Node Environment / Makefile Additions
In order to have both the testing and webpack abilities at the ready, we needed to add a node environment and dependency installation process to the Makefile. We use nodeenv, which is very friendly with virtualenv. The installation process is seamless.
All build or test commands can be run manually from object_database/web/content, since that is where the main package.json file resides.
The Makefile has also been adjusted to run the JS test suite automatically when using make test.
Building
In order to produce the correct JS dependencies, you need to build the bundle. Note that we do not include this bundle in the repository, so if you try to run the test frontend without first building you will see an import error in the browser console.
To run the build process, be sure you are sourced into the venv created by the install and navigate to object_database/web/content. Then run the command npm run build. That's it. Now you should be able to run the frontend as normal.
Testing Manually
To run just the JS tests (without using the Makefile), be sure you are sourced into the venv and navigate to object_database/web/content. Then run the command npm test. That will run the full test suite.
Testing Framework
For testing in JS, we use a combination of Mocha and Chai. These are well supported and pretty standard in the JS world.
How Has This Been Tested?
We ran the full test suite, including the JS tests.
See the "Important Info" section below for additional information. We used the test frontend to ensure that components were in working order.

Important Info
The work implemented in this PR is not new. However, the dev branch and our working branches got so far off base from each other that this PR branch is in fact a rebase of several branches on top of dev. This means that there might be some weirdness that we have not caught, since the resolution process required a lot of manual work. PLEASE BE SURE TO TEST THIS IN A LIVE UI.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Cool.  (a) Does the webpack get run when we return setup.py and get
included in the built binary? (b) what's the best dev process when you're
iterating on the JS in this model?
On Fri, Jun 21, 2019 at 1:01 PM Eric Gade<EMAIL_ADDRESS>wrote:

@darth-cheney https://github.com/darth-cheney requested your review on:
#106 https://github.com/APrioriInvestments/nativepython/pull/106
Component Webpack and Tests.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/APrioriInvestments/nativepython/pull/106?email_source=notifications&email_token=AB6OHBDUIUCBGZE3OJYICWTP3UCPTA5CNFSM4H2TICSKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSDSLQZQ#event-2430908518,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB6OHBDXUMAGXHUA6LCTZFTP3UCPTANCNFSM4H2TICSA
.

@braxtonmckee Nothing webpack related should be included in the setup.py binary. These changes will only affect files in object_database/web/content.
The dev process is pretty simple: you just need to run the build process whenever you make changes to any JS files. We can certainly set up a watch process down the road and add that. For now it's easy enough to just run the build (the procedures for doing that are outlined in the PR). Does that answer your question?

Ok, so on setup.py, when we deploy this how will the files in
object_database/web/content get populated?
On Fri, Jun 21, 2019 at 1:26 PM Eric Gade<EMAIL_ADDRESS>wrote:

@braxtonmckee https://github.com/braxtonmckee Nothing webpack related
should be included in the setup.py binary. These changes will only affect
files in object_database/web/content.
The dev process is pretty simple: you just need to run the build process
whenever you make changes to any JS files. We can certainly set up a watch
process down the road and add that. For now it's easy enough to just run
the build (the procedures for doing that are outlined in the PR). Does that
answer your question?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/APrioriInvestments/nativepython/pull/106?email_source=notifications&email_token=AB6OHBBFV2WXZBJEOZL4AC3P3UFNHA5CNFSM4H2TICSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYJCMPQ#issuecomment-504505918,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB6OHBA5SZSZMAMKJ5QOJNTP3UFNHANCNFSM4H2TICSA
.

@braxtonmckee we can commit the latest js bundle build with every PR - that way you can just import and use it (granted that your prod setup is similar to the web test we use/see)

The prod setup is slightly different. We install the python library, and
expect to be able to run the active web service out of it. Ideally setup.py
would build the webpack and include its files in the manifest. It already
does this with page.html and the other javascript files.
On Fri, Jun 21, 2019 at 2:11 PM dkrasner<EMAIL_ADDRESS>wrote:

@braxtonmckee https://github.com/braxtonmckee we can commit the latest
js bundle build with every PR - that way you can just import and use it
(granted that your prod setup is similar to the web test we use/see)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/APrioriInvestments/nativepython/pull/106?email_source=notifications&email_token=AB6OHBFFKQPBP6HSK64IR2DP3UKV7A5CNFSM4H2TICSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYJGCUI#issuecomment-504521041,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB6OHBCIZR7U2AJLLHKXH7DP3UKV7ANCNFSM4H2TICSA
.

@braxtonmckee the main bundle is added, and included in the MANIFEST.in file, see this commit
That seems better than having setup.py install the entire node env, webpack etc just to build this bundle 1x