fix(ui): Fix entity-info styling

Fixes unwanted UI changes introduced by #558

Before
After

⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠ ⚠
It seems that using styled-components the way it's done here does more harm than good. We didn't need to specify font-weight 'normal', or wrapperStyle in the past.
It's like using styled-component completely reset the style of the react-native-elements component, and we have to specify defaults again. Really weird.
Another painful thing is that before using SC, the hideChevron prop produced consistent margins no matter of its value. With SC, I got this difference for the first element:

I had to display the chevron, but transparent for that element, to produce a consistent margin.
The big question here: Is SC used as it should be here? Is this a bug of SC ?

Coverage decreased (-0.05%) to 34.457% when pulling 454a57d12a3e79f4f91ea159a3f09a1b3ce13b06 on machour:entity-info-fix into a9ae8408e5b4f56695a90bb7a29fb9040127a931 on gitpoint:master.

A bit random but @housseindjirdeh could you configure Coveralls to pass the Status Check as long as there's less than a 0.25% reduction in coverage? It's a bit silly to have it fail for this PR, or any PR that adds a tiny bit of complexity.

Actually not sure how I feel about that... Maybe we should keep it as is so we can be aware of when we're lowering coverage. Input?

+1 on keep in it like that for now @andrewda

Coverage decreased (-0.05%) to 34.457% when pulling 109ae28ed4b881f34911b1591016a22e7811c7c5 on machour:entity-info-fix into a9ae8408e5b4f56695a90bb7a29fb9040127a931 on gitpoint:master.

Alright, this should be fine to be merged. I'm adding a lot more tests for EntityInfo, but will follow those up in a future PR.

Coverage decreased (-0.05%) to 35.839% when pulling 3918af60c7a17dc6ceed2f2a1cc67dfd98949586 on machour:entity-info-fix into 5266fb247b8eec989b2c8d189c3f3970cb965aff on gitpoint:master.

Finally had the time to investigate a bit more, there's an incompatibility between Styled-Components & React Native Elements where the default container style get lost.
More info in this bug report: https://github.com/react-native-training/react-native-elements/issues/679

Closing this as #619 fixes the root cause


Update links to prs in changelog

Coverage remained the same at 92.118% when pulling ef6cb8373a66f460ef20aec281a5d475b855ddd2 on boguslavsky:changelog-formatting into b57e4ef0a5da9917dda07b5991b76b9e45b80541 on exonum:master.

Coverage remained the same at 92.118% when pulling ef6cb8373a66f460ef20aec281a5d475b855ddd2 on boguslavsky:changelog-formatting into b57e4ef0a5da9917dda07b5991b76b9e45b80541 on exonum:master.


which configuration file to choose in new scene?

Hi, If I want to render a scene like an underground parking lot, images captured by sensors on a car, which configuration file should I choose? I used blender_512.gin to train for 500000 epochs with batch size 4096, but found the result was poor (psnr only 21). Looking forward to your help. Thanks!

I'd try 360.gin


siRNA processing defintion

It seems that this term has been made narrower in scope.
The term processing refers to the production of a mature transcript. but the definition includes
"MAy also include amplification step of the siRNA by RNA-directed RNA polymerase."
This part of the process isn't processing.

What is the problem ? 'Processing' is defined differently for RNAs than for proteins, this encompasses the entire maturation. This is how it's used in the literature, I think it's better to leave it as it is.
What do you think?

It may be OK, will close until I try to curate the pathways. I struggle with these modules within modules.


Set postgres container imagePullPolicy to Always

When running the postgres pod with imagePullPolicy=Never we
get the error Container image "postgres:9.4" is not present with pull policy of Never

Closing as this is not needed


use local storage for data

Right now, RecentPDF can only load so many PDFs limited by the history API chrome provides.
If RecentPDF stored data about PDFs via a local json file. RecentPDF could prove to be a lot more useful. As well as a lot faster.

Can I also take on this as well?

@JuliaFC Yes. I would like to talk about how you want to implement it though :)

@alexweininger absolutely! As soon as I read through the code and study the best way to do it, I'd be happy to talk to you about it! Or is there anything you'd like to discuss right away?

@JuliaFC Nothing to discuss right away.


Error Unauthorized

In subscriptionConfiguration I changed changeType value to updated, and resource value to users. Then tried subscribe and I got error
{
  "error": {
    "innerError": {
      "date": "2019-07-03T11:29:39",
      "request-id": "5e7f1fc3-8ef4-4511-b661-35bf7d146cc3"
    },
    "message": "Operation: Create; Exception: [Status Code: Unauthorized; Reason: ]",
    "code": "ExtensionError"
  }
}

The app's configuration only gives it access to read the logged in user's mail, not to access the organizations user list. You'd need to update the app registration permissions to give it Users.Read.All and login with an administrator account.

Closing the issue as it's old and has been answered. If you're still running into feel free to open a new issue.


remove keypair info if rebuild-root not set keypair

这个 PR 实现什么功能/修复什么问题:
重装系统时，不指定秘钥则解绑之前的秘钥
是否需要 backport 到之前的 release 分支:

release/2.10.0
release/2.9.0
release/2.8.0

/area region
/cc @swordqiu @yousong

Codecov Report

Merging #1420 into master will decrease coverage by 0.02%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #1420      +/-   ##
=========================================
- Coverage    7.71%   7.69%   -0.03%
=========================================
  Files         408     408
  Lines       62368   62372       +4
=========================================
- Hits         4813    4797      -16
- Misses      57152   57169      +17
- Partials      403     406       +3

Flag
Coverage Δ

#aFlag
7.69% <0%> (-0.03%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/compute/models/guest_actions.go
0% <0%> (ø)
:arrow_up:

pkg/util/rbacutils/rbac.go
70.4% <0%> (-4.37%)
:arrow_down:

pkg/util/seclib2/seclib.go
91.48% <0%> (-4.26%)
: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 d5f4e5e...fc77d7b. Read the comment docs.

/approve
/lgtm


New demo -- cleaned up to display properly on Github.com

'''
    DS1302 Demo #2 (v3)
    Author: R_Moore
    Date:   9/3/2018
    Uses ShaoZiYang's DS1302 Driver from this URL:
        https://github.com/shaoziyang/microbit-lib/tree/master/misc/DS1302
        http://www.micropython.org.cn

    Improved demo/test program to be more Micro:bit user friendly...
'''
from microbit import *
import time
import DS1302

# The following function translates the 'day of week' code
# (an integer value btw 0 & 6, inclusive) into the
# equivalent English name for the day.

def xlateDayCode(day):
    if day == 0:
        return 'Sunday'
    elif day == 1:
        return 'Monday'
    elif day == 2:
        return 'Tuesday'
    elif day == 3:
        return 'Wednesday'
    elif day == 4:
        return 'Thursday'
    elif day == 5:
        return 'Friday'
    elif day == 6:
        return 'Saturday'
    else:
        return 'Error'

# Create an instance of a DS1302 class and call it 'ds'.
ds = DS1302.DS1302(clk=pin13, dio=pin14, cs=pin15)

# Use next line of code just one time to set the date/time of RTC module (un-comment it to use)
# ds.DateTime([2018, 3, 9, 4, 23, 0, 1])  # March 3, 2018 at 11:00:01 pm.

while True:
    # Display day of week...
    display.scroll('Today is ' + xlateDayCode(ds.Weekday()) + ', ')

    # Display current date in 'mm/dd/yyyy' format...
    display.scroll(str(ds.Month()) + '/' + str(ds.Day()) + '/' + str(ds.Year()))
    time.sleep_ms(1000)

    # Display current time in 'hh:mm:ss' format...
    display.scroll(str(ds.Hour()) + ':' + str(ds.Minute()) + ':' + str(ds.Second()))
    time.sleep_ms(10000)        # Wait 10 seconds & repeat...

Seems GitHub is not Python friendly when it comes to comments in the source code. Seems to want to interpret '#' as some kind of format character. Here's the code again stripped of comments:
`
from microbit import *
import time
import DS1302
def xlateDayCode(day):
if day == 0:
return 'Sunday'
elif day == 1:
return 'Monday'
elif day == 2:
return 'Tuesday'
elif day == 3:
return 'Wednesday'
elif day == 4:
return 'Thursday'
elif day == 5:
return 'Friday'
elif day == 6:
return 'Saturday'
else:
return 'Error'
ds = DS1302.DS1302(clk=pin13, dio=pin14, cs=pin15)
#ds.DateTime([2018, 3, 9, 4, 23, 0, 1])  # March 3, 2018 at 11:00:01 pm.
while True:
display.scroll('Today is ' + xlateDayCode(ds.Weekday()) + ', ')
display.scroll(str(ds.Month()) + '/' + str(ds.Day()) + '/' + str(ds.Year()))
time.sleep_ms(1000)
display.scroll(str(ds.Hour()) + ':' + str(ds.Minute()) + ':' + str(ds.Second()) + '  ')
time.sleep_ms(10000)        # Wait 10 seconds & repeat...
`

Now tab indents are gone.


Snap to view during scrolling

Is there a way to snap into a view during scrolling, maybe with the css module CSS Scroll Snap Module or with a js lib like scroll-snap?

seems like you could just incorporate those and scrollama would still work just fine?


Get-TestsFromBCContainer - WARNING: This license is not compatible with this version of Business Central.

Trying to use Get-TestFromNavContainer but it looks like Get-Test is returning, " WARNING: This license is not compatible with this version of Business Central." as the first element in the array.
This is causing the | ConvertFrom-Json to fail.
https://github.com/microsoft/navcontainerhelper/blob/5d0416973977504a1abd4de011b49d2698260165/AppHandling/Get-TestsFromNavContainer.ps1#L162

I can alter the Get-TestFromNavContainer to give me output I can work with but is there a better way to do this with the licenses?   I need to load our license to publish an app but could I switch back to the default container license for the tests?

This is because you are running as non-admin.
But - of course, it should work - I will look into this.

Thanks for the quick commit!  I've integrated it into my test builds and it functions just fine.

Fix shipped in <IP_ADDRESS>


Remove outer "questionnaire" wrap as it's breaking MUSIC's parser.

Pushing out for live testing by MUSIC.


How to use Core/SQL API with React and Azure Cosmos DB?

Is any option to use Core/SQl api with react and CosmosBD?
https://docs.microsoft.com/en-us/azure/cosmos-db/tutorial-develop-mongodb-react
I have refered this document i'm not able to find way to connect Core/SQl api with react and CosmosBD. Please help me any way to connect Core/SQl api with react and CosmosBD
///////
After using above reference document i'm getting this error. Please help me to get connect React application to cosmosdb by  Core/SQl api?

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

ID: 79e0a0b9-d316-fea3-f92d-db9535ea3400
Version Independent ID: 215ec001-4569-072c-01fb-32edba90db40
Content: MongoDB, React, and Node.js tutorial for Azure
Content Source: articles/cosmos-db/tutorial-develop-mongodb-react.md
Service: cosmos-db
Sub-service: cosmosdb-mongo
GitHub Login: @johnpapa
Microsoft Alias: jopapa

It looks like the error text may be missing from your post. If you update that I can possibly give you a clearer answer.
If you are trying to connect Cosmos directly to a SPA framework like Angular or React, that is not an officially supported scenario because the security risks involved in connecting to a database directly from a browser. If you are using a Node layer as an API in between, then there are Node tutorials available for the SQL API. The React layer should be similar to the mongo version: https://docs.microsoft.com/en-us/azure/cosmos-db/sql-api-nodejs-samples

@SamaraSoucy-MSFT
This is error i'm getting:
Access to XMLHttpRequest at 'Cosmos db url/' from origin 'https://localhost:44301' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

@SamaraSoucy-MSFT Is any other way to connect React to ComosDB directly?

Can you please check to see if you have CORS enabled on your CosmosDB? https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-configure-cross-origin-resource-sharing

The libraries might still work with React- it's just not supported officially. If you've considered the security implications of connecting to Cosmos from a browser and still want to do it, you could use the REST API directly even if you can't get the SDK to work through React directly: https://docs.microsoft.com/en-us/rest/api/cosmos-db/documents

Hi @poonkodi123 Have you had a chance to look at the CORS policy in Cosmos?

@poonkodi123 Since I haven't heard back I'm going to close this issue. You can still @ me if you have any additional questions and I will follow up.


pull request for e2e test at 01/05/2017 16:45:11

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


Broken bee model

When i try spawn bee by command:
Game.player.chat.sendMessage('/spawnmob 3880 71 2527 bee base');
I receive error in console:
mob_model.js:246 Uncaught TypeError: Cannot read properties of null (reading 'quat')
    at MobAnimation.head (mob_model.js:246)
    at MobAnimator.applyAnimation (mob_model.js:207)
    at MobAnimator.update (mob_model.js:189)
    at MobModel.update (mob_model.js:384)
    at MobModel.draw (mob_model.js:390)
    at Renderer.drawMobs (render.js:523)
    at Renderer.draw (render.js:434)
    at GameClass.loop (game.js:351)

Fixed by: #41


views: fix content type check

Uses the request mimetype instead of raw content type header.
(closes #118)

Signed-off-by: Leonardo Rossi<EMAIL_ADDRESS>

@hachreak can you please add some specific test case?

depends on https://github.com/inveniosoftware/invenio-rest/pull/60

@jirikuncar :shipit: ?

@jirikuncar done all.

LGTM

@jirikuncar :shipit: ?


Add an example of playing a WAV file.

Addresses #458.
Outstanding issues:

[ ] Is the claim about SDL_Mixer correct? I haven't used it before but the internet suggests it's the way to do this properly.
[ ] I get a "pop" on audio device close that isn't present in the other two examples. Why?

cc @nukep I figured out the AudioCVT thing, thanks for the hint.

Niiiice one. I don't know enough about the wav playing of SDL2, but this looks great.

Mixer claim seems to be correct but misleading, https://github.com/andelf/rust-sdl2_mixer exists and I should link to it (it's already in the README ... missed that first time around.)

Wonderful. Merging in!


Throw "Error: Unexpected token import" after running "npm run sequelize db:migrate"

Followed the instruction from this https://github.com/reactGo/reactGo/blob/master/docs/databases.md
to setup the Postgres database.
But it threw an error message,
Sequelize [Node: 7.4.0, CLI: 2.5.1, ORM: 3.29.0]
Error reading "server/db/sequelize/sequelize_config.js". Error: Unexpected token import" after running npm run sequelize db:migrate command.

Thanks for raising issue. It might be a regression since we webpack server side node

The error was introduced when I made everything import, including sequelize/sequelize_config.js. I tried running the command through babel-node but does not work.
For now, the workaround can be with changing .sequelizerc to point to
config: './server/db/postgres/sequelize_config.js',

to directly access the files!

Cool~ It works!! I did try babel-node without luck as well.
But I can start using it for a project now, thanks!

I was getting a "reserved word" error when trying to run postgres db migrations and this fixed that at well. Thanks.

The error was introduced when I made everything import, including sequelize/sequelize_config.js. I tried running the command through babel-node but does not work.

Rename webpack.config.js to webpack.config.babel.js and add /.babelrc with the following code:
{
  "presets": [
    "es2015"
  ]
}

You'll be able to use import statements in webpack's config as well.

@jsprzybylski that did not work for me. Is there anything else that you did?

@gemfarmer does @jsprzybylski solution did not work?

Is it ok that i'm getting this issue?
Tried 3 different machines, still failed to migrate.

@choonkending I think we need to fix this. It does not work out-of-the-box as is. And even if there is a CJS compatible config for postgresql, there does not seem to be one for mongo. We should probably do one of

use babel-node in our sequelize script (I haven't got this working)
change related code to be CJS compatible
something else?

Something else: Maybe we need to think about stopping running babel on the whole server side code. Maybe we just need to run it on the react related stuff (starting point would be middleware.js). That would allows us to use mongo/postgresql and any other module without worrying about babel or cases like this.

@slavab89 that an interesting thought, and somewhat related to #924. I have been experimenting with different approaches to switching out nodemon for either chokidar or webpack. Having a server that does not require transpialtion would make that a lot easier.
The very big downside to that is that it is not only React, but also other features which requires transpiling, such as async / await, object destructuring, class variable declarations, lexically bound class members etc. (depending on what version of node you are using)

yes that is correct, you would be "limited" to what node allows you to do, so you wont be able to use import and other features that you've mentioned (in node 6 for example).
Moreover, in case you want to take out some of the code of the server side to a different dedicated API project, it would be pretty easy because it would be regular and standard node code.
If you think that this is to much of a hassle then we'll have to find ways to deal with all of those different cases 😄

@slavab89

You are still able to do all the things that you want to do therefore i dont really see such a big downside here

I kind of disagree, because having to worry about two different syntax sets on the server and client adds a lot of mental overhead, as well as limits what can be shared between the two platforms. Depending on node version, there can be alot of unsupported syntax.
I do think there is a solution which would make for a good developer experience both on the client and on the server though, making use of webpack + babel on both ends. Within the scope of this issue, I think the best solution would be to make sequelize play well with ES6.

This really needs to be resolved. Maybe by doing what this SO post suggests.


[Feature request]:

Contact Details
No response
Description
Add a logger module. Maybe trying https://github.com/Delgan/loguru? Or logging?
Importance Level
Low
Affected Components
No response
Technical Requirements
No response
Acceptance criteria
No response

Needs to be send to Stderr because streaming uses stdout


[Grid] Failed prop type: The property xs of Grid must be used on item

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

Expected Behavior 🤔

Shouldn't throw a warning.
Current Behavior 😯

Throws a warning when page is reloaded, complaining about xs being set on a non-item grid tag, when the line throwing the warning doesn't have it.
Steps to Reproduce 🕹

Link:

Load the page at https://codesandbox.io/s/010p1j4o0l
Once it's loaded, hit the Reload icon on the internal browser (the one on the page, displaying the results. Not your own browser)

Context 🔦

The functionality seems to be correct regardless of the warning, but I'm wondering if this could have some more serious ramifications later on. I also HATE warnings ;)
Your Environment 🌎

Tech
Version

Material-UI
v3.9.1

React
v16.7.0

Browser
Chrome 72.0

TypeScript
No

etc.

@sgermain06 You should set the item={true} property as the warning is suggesting.

Care to elaborate? I tried adding item={true} and it's still throwing a warning.

Oh. I got it. Thanks!

It does give me the same warning even after doing this.
<Grid container xs={12}>
    <Grid item={true} xs={8} sm={10}></Grid>
</Grid>

@chilupa xs is only available on flex items, a flex container doesn't allow it.

This warning is quire misleading. I had to Google why I'm getting it. Maybe if "must" was replaced with "can only".

@bmakan What do you think about this diff?
Before

After

diff --git a/packages/material-ui-utils/src/requirePropFactory.js b/packages/material-ui-utils/src/requirePropFactory.js
index 4d6707aab1..8292921adb 100644
--- a/packages/material-ui-utils/src/requirePropFactory.js
+++ b/packages/material-ui-utils/src/requirePropFactory.js
@@ -15,7 +15,7 @@ export default function requirePropFactory(componentNameInError) {
     if (typeof props[propName] !== 'undefined' && !props[requiredProp]) {
       return new Error(
         `The prop \`${propFullNameSafe}\` of ` +
-          `\`${componentNameInError}\` must be used on \`${requiredProp}\`.`,
+          `\`${componentNameInError}\` can only be used together with \`${requiredProp}\`.`,
       );
     }

@oliviertassinari I think it's much better. It's harder to judge it now when I know what it means. Maybe adding word "prop" at the end might make it even more obvious?
The prop ${propFullNameSafe} of ${componentNameInError} can only be used together with ${requiredProp} prop.
I think item is a very generic term in programming and can cause confusion by itself when it shows up.

@bmakan Sounds great, do you want to work on a pull request? :)

@oliviertassinari  Can I create a PR for this?

@oliviertassinari Above is my PR, let me know if I'm missing anything.

That is super misleading, thanks for making this change.

That is super misleading, thanks for making this change.

Use   for (lg,md,sm,xs)

To me this was very confusing as I thought I'd OMITTED, in my case, the sm prop on a Grid item.
I searched my codebase, and I ensured every "Grid item" had a sm={int[1-12]} property.
Still receiving error message: "index.js:1 Warning: Failed prop type: The prop sm of Grid must be used on item."...
I started commenting out code and re-rendering site.
It ends up I had the sm prop on a "Grid container". Removing it fixed the issue. But, I think the message could be more clear. I thought I was being told, "Hey, you must have this property on a grid item."
But, what it was meaning was, "You have a property on a grid container that is only for grid item."

@neillindberg #23630 improves a bit the warning

It does give me the same warning even after doing this.
<Grid container xs={12}>
    <Grid item={true} xs={8} sm={10}></Grid>
</Grid>

This worked for me as well

same problem i am facing too

same problem i am facing too, I've taken care of it  by double grid
<Grid container justifyContent="center" >     <Grid item xs={11} sm={10} md={7}>         <Grid container spacing={1} justifyContent="center" >             {Array.from(Array(4)).map((_, index) => (                 <Grid item key={index} xs={11} sm={5}  md={3}>                     <SkeletonItem />                 </Grid>             ))}         </Grid>     </Grid> </Grid>

same problem i am facing too, I've taken care of it by double grid
<Grid container justifyContent="center" >     <Grid item xs={11} sm={10} md={7}>         <Grid container spacing={1} justifyContent="center" >             {Array.from(Array(4)).map((_, index) => (                 <Grid item key={index} xs={11} sm={5}  md={3}>                     <SkeletonItem />                 </Grid>             ))}         </Grid>     </Grid> </Grid>

            {Array.from(Array(4)).map((_, index) => (

            ))}

same problem i am facing too, I have corrected it correctly
<Grid container justifyContent="center" >
    <Grid item xs={11} sm={10} md={7}>
        <Grid container spacing={1} justifyContent="center" >
            {Array.from(Array(4)).map((_, index) => (
                <Grid item key={index} xs={11} sm={5}  md={3}>
                    <SkeletonItem />
                </Grid>
            ))}
        </Grid>
    </Grid>
</Grid>

Seems working very well with both cases
1-
2-

@oliviertassinari , Thanks !

// Incorrect usage
<Grid container xs={12}>
  {/* ...children... */}
</Grid>

// Correct usage as a container
<Grid container>
  {/* ...children... */}
</Grid>

// Correct usage as an item within another container
<Grid container>
  <Grid item xs={12}>
    {/* ...children... */}
  </Grid>
</Grid>

// Incorrect usage
<Grid container xs={12}>
  {/* ...children... */}
</Grid>

// Correct usage as a container
<Grid container>
  {/* ...children... */}
</Grid>

// Correct usage as an item within another container
<Grid container>
  <Grid item xs={12}>
    {/* ...children... */}
  </Grid>
</Grid>

How will this work in the following example?
<Grid
        container
        sx={{
          '--Grid-borderWidth': '1px',
          borderTop: 'var(--Grid-borderWidth) solid',
          borderLeft: 'var(--Grid-borderWidth) solid',
          borderColor: 'divider',
          'div': {
            border: '2px solid',
            borderColor: 'red',
            background: "rgba(2, 2, 2, .5)",
            color: 'white'
          },
        }}
      >
        <Grid container xs={8}>
          <Grid container xs={12}>
            <Grid xs={4}>5</Grid>
            <Grid container xs={8}>
              <Grid container xs={12}>
                <Grid xs={6}>5</Grid>
                <Grid xs={6}>6</Grid>
              </Grid>
              <Grid xs={12}>6</Grid>
            </Grid>
          </Grid>
          <Grid xs={12}>3</Grid>
        </Grid>
        <Grid container xs={4} sx={{ display: 'grid', gridTemplateRows: '0.6fr 1.4fr' }}>
          <Grid xs={12}>5</Grid>
          <Grid xs={12}>6</Grid>
        </Grid>
      </Grid>

// Incorrect usage
<Grid container xs={12}>
  {/* ...children... */}
</Grid>

// Correct usage as a container
<Grid container>
  {/* ...children... */}
</Grid>

// Correct usage as an item within another container
<Grid container>
  <Grid item xs={12}>
    {/* ...children... */}
  </Grid>
</Grid>

How will this work in the following example?
<Grid
        container
        sx={{
          '--Grid-borderWidth': '1px',
          borderTop: 'var(--Grid-borderWidth) solid',
          borderLeft: 'var(--Grid-borderWidth) solid',
          borderColor: 'divider',
          'div': {
            border: '2px solid',
            borderColor: 'red',
            background: "rgba(2, 2, 2, .5)",
            color: 'white'
          },
        }}
      >
        <Grid container xs={8}>
          <Grid container xs={12}>
            <Grid xs={4}>5</Grid>
            <Grid container xs={8}>
              <Grid container xs={12}>
                <Grid xs={6}>5</Grid>
                <Grid xs={6}>6</Grid>
              </Grid>
              <Grid xs={12}>6</Grid>
            </Grid>
          </Grid>
          <Grid xs={12}>3</Grid>
        </Grid>
        <Grid container xs={4} sx={{ display: 'grid', gridTemplateRows: '0.6fr 1.4fr' }}>
          <Grid xs={12}>5</Grid>
          <Grid xs={12}>6</Grid>
        </Grid>
      </Grid>

I got it:
<Grid container spacing={4}>
                <Grid item xs={8}>
                  <Grid container spacing={4}>
                    <Grid item xs={12}>
                      <Grid container spacing={4}>
                        <Grid item xs={4}>
                          1
                        </Grid>
                        <Grid item xs={8}>
                          <Grid container spacing={4}>
                            <Grid item xs={12}>
                              <Grid container spacing={4}>
                                <Grid item xs={6}>
                                  2
                                </Grid>
                                <Grid item xs={6}>
                                  3
                                </Grid>
                              </Grid>
                            </Grid>
                            <Grid item xs={12}>
                              <Grid container spacing={4}>
                                <Grid item xs={12}>
                                  4
                                </Grid>
                              </Grid>
                            </Grid>
                          </Grid>
                        </Grid>
                      </Grid>
                    </Grid>
                    <Grid item xs={12}>
                      5
                    </Grid>
                  </Grid>
                </Grid>
                <Grid item xs={4}>
                  <Grid
                    container
                    spacing={4}
                    sx={{ display: "grid", gridTemplateRows: "0.6fr 1.4fr" }}
                  >
                    <Grid item xs={12}>
                      6
                    </Grid>
                    <Grid item xs={12}>
                      7
                    </Grid>
                  </Grid>
                </Grid>
              </Grid>


Calculate height of moving object under camera

We have cardboard boxes flowing on a conveyor belt which a robotic system has to pick up. It is important to gauge the height of the object to the millimeter accuracy level. The camera D415 is mounted at 24" height from conveyor belt facing the conveyor belt. As the object enters the FOV of the camera we start measuring distances of the center of the boxes as seen from the camera.
We know the distances of each pixels when the conveyor belt is empty. So, when we measure distance to a pixel on the box, we need to know the angle of the pixel from the vertical plane of the camera in order to do the appropriate trignometry to compute the height of object.
How can i determine the angle (theta) of a particular pixel relative to the axis vertical to the plane of the depth sensors?
What we have:

Distance of pixel when no objects on conveyor (a)
Distance of pixel on the box when a box is placed on the conveyor (b)

What we need to compute:

Distance between a and b which will give us height of the cardboard box

I am guessing that you have the camera centered over the conveyor belt so that when a box passes underneath, the center of the box roughly corresponds to the center of the camera image?
If you want to be sure that the box is centered under the camera and you aren't reading its edge as it enters or exits the camera view, a couple of possibilities come to mind:

Define a 'bounding box' in the center of the camera image so that the camera ignores depth data outside of that box.

A recent article described a project where Lego bricks move under a vertically mounted downward-pointing camera on a makeshift conveyor and have bounding boxes defined around them to identify them.  This may give some useful insights about use of bounding boxes on conveyor objects.
https://github.com/IntelRealSense/librealsense/issues/5393
Or;

Set up a physical light sensor positioned just past the camera centerline so that the camera only performs a capture of the center of the box when the edge of the box that reaches the light sensor first passes through the light beam and breaks it whilst the box center is under the camera.

An alternative method might be to put a 'tag' image on the center of the top of the box that can be detected by the camera and trigger the robotic system to respond.  For a 400 Series depth camera, an Aruco tag could be used.
https://docs.opencv.org/3.1.0/d5/dae/tutorial_aruco_detection.html
If you just need to measure between two points though, the Measure C++ sample program may meet your needs.
https://github.com/IntelRealSense/librealsense/tree/master/examples/measure

Thank you for the ideas Marty. Will explore further. We're looking at simple trignometry to achieve the results. Also, do you know if depth calibration smoothes out the effects of lens warping?

If you are referring to concave and convex distortion effects such as barrel distortion and pincushion distortion, @dorodnic offers advice on the subject here:
https://github.com/IntelRealSense/librealsense/issues/4939#issuecomment-535458739

Thank you for the link Marty. Will do some tests on the two distortion types on empty conveyor and test objects.

You're very welcome.  Let us know how the tests turn out please!

This case will be closed after 7 days from the date of writing this if there are no further responses.   Thanks!


Cannot determine realm for numeric host address

I use solr on hue,  when os is redhat 6.7, the error is GSSError: (('Unspecified GSS failure.  Minor code may provide more information', 851968), ('Cannot determine realm for numeric host address', -1765328141))
when os is suse 11.3, it`t ok.

I fixed/etc/hosts, it worked.


Add optional CI workflow for clippy and cross-compilation tests

This PR includes a additional CI workflow for testing git2-rs for various targets.
          # - { os: ubuntu-latest  , target: arm-unknown-linux-gnueabihf , use-cross: use-cross }
          - { os: ubuntu-latest  , target: aarch64-unknown-linux-gnu   , use-cross: use-cross }
          - { os: ubuntu-latest  , target: aarch64-unknown-linux-musl  , use-cross: use-cross }
          - { os: ubuntu-latest  , target: i686-unknown-linux-gnu      , use-cross: use-cross }
          - { os: ubuntu-latest  , target: i686-unknown-linux-musl     , use-cross: use-cross }
          - { os: ubuntu-latest  , target: x86_64-unknown-linux-gnu    , use-cross: use-cross }
          - { os: ubuntu-latest  , target: x86_64-unknown-linux-musl   , use-cross: use-cross }
          - { os: macos-latest   , target: x86_64-apple-darwin }
          # - { os: windows-latest , target: i686-pc-windows-gnu }
          - { os: windows-latest , target: i686-pc-windows-msvc }
          - { os: windows-latest , target: x86_64-pc-windows-gnu }
          - { os: windows-latest , target: x86_64-pc-windows-msvc }

I found test or compilation errors in the targets as comments.
This CI workflow also include a clippy check for linux/mac/windows (due to specific sections for windows -- mac target could not be useful since there is no specific mac section)
Activating clippy has produced many warnings (promoted as errors in this CI workflow). I've fixed all of them (and sometimes I add an allow(clippy:xxx) pragmas:

clippy::new_without_default
clippy::unnecessary_cast
clippy::too_many_arguments
clippy::manual_non_exhaustive
clippy::should_implement_trait
clippy::transmute_ptr_to_ptr

I note 2 special cases of maybe useless "unsafe" function. I put them in a separate commit.
A coverage section is ready to use in the same workflow.

Thanks for the PR! This is a lot of code to review though and personally I would prefer to not take on a whole lot of CI configuration for this (I personally do not like to run clippy in CI). Could this be minimized into just the clippy changes?

Ok; I understand.
I move the CI to another branch (my idea will next be to investigate why there are problems on arm-unknown-linux-gnueabihf and i686-pc-windows-gnu).
To simplify the review I also split the changes into 4 commits:

shorthand initialization warnings
clippy directives to disable some warnings (because seems to be easier to understand like this)
(eg: allow(clippy::new_without_default), allow(clippy::unnecessary_cast)...)
all the others changes (except 2 in the next commit)
2 unsafe remove
If you prefer, I can also split these changes into distinct PRs.

Thanks, but I generally don't agree with many of the changes here. It's unfortunately pretty exhausting to deal with clippy PRs across so many projects. I don't really have the time/energy to review all sorts of clippy prs all over the place taking various stylistic actions that I don't agree with personally.
I'll leave this though if someone else would like to review.

No problem. I understand. Maybe clippy's advice isn't that helpful. It was just a suggestion (maybe not a good one). You can close this PR, if you prefer.
I did this in passing before trying to figure out the runtime and compilation issues on the two target architectures (arm-unknown-linux-gnueabihf and i686-pc-windows-gnu). Instead, I will focus on my original goal.
Thanks for your time.

I'm going to go ahead and close this out since it is quite old.


When i open the program, all my sound is gone.

I idea why i opened the program and let it use my mic and so on. Now i'm here all confused.

#257


The contributor guidelines are incorrect

Describe the bug
It also looks like the link populated in new pull requests needs to be changed from Please see https://docs.ark.io/docs/contributing for details before opening your pull request. to Please see https://docs.ark.io/guidebook/contribution-guidelines/ for details before opening your pull request.
To Reproduce
Steps to reproduce the behavior:

Open a new PR

Expected behavior
The contributor guidelines in the PR template should not reference a URL that returns a 404.

Thanks for opening this issue! A maintainer will review this in the next few days and explicitly select labels so you know what's going on.
If no reviewer appears after a week, a reminder will be sent out.

This issue has been closed. If you wish to re-open it please provide additional information.


Cached views call UI-router resolves on re-enter

Continuing #3487 which was closed by ionitron for reasons not quite comprehensible.
Still an issue with ionic v1.2.

+1

Well, there've been several workarounds suggested, ranging from the trivial (such as yours) to the rather involved, such as the one by chrfritsch here: https://forum.ionicframework.com/t/state-resolving-and-cached-views-in-beta-14/17870/8
So, thanks, but I guess everyone bugged by this issue has already a bunch of workarounds in use. One of the advantage of resolves is that they allow you to catch error before entering the view, which makes for a much improved user experience in some situations, so moving this into the controller is also not an option for me.
If you're not going to change, this, fine, I can understand. Though I question it is because of ui-router, since AFAIK the concept and implementation of cached views is special to Ionic.

@tkem, I think I may have been mistaken.  I believe this functionality is custom to Ionic.  I will take a look and see what we can do.  There are a few potential obstacles that I can think of.

Thanks for looking into this!

@tkem, just to keep you posted... I did come up with a way to do this.  Having said that, I don't know if the team will want to go for it or not.  It is modifying UI-router to accomplish it.
We could do it in a cleaner way long term (override $state.go, for example), but navigation is so much better in V2 and will eliminate many of the challenges with UI-router that I am not sure if it's worth it.
I will keep you posted.

agreed that the navigation in Ionic 2 is pretty awesome! @tkem as an aside have you gotten a chance to try Ionic 2 yet?

Hi @tkem, the team chose not to make the change to ui-router since there are decent work arounds in place and much better navigation on the horizon with V2.
Thank you for contributing and we really appreciate you using Ionic.  Thanks again for the very detailed responses.
Thanks,
Dan


Network ID and Device Address Incorrect

I am trying to run the BasicConnectivityTest for the DWM1000 chip and I am getting the following output:

I am unsure why the PAN is 00 and the Short Address is FF, I have not changed anything from the code (apart from adding a Serial.println later towards the end of the code).
I have connected the chip to an Arduino Uno as follows (The pins connected in the image to the Pro mini are the same as i have connected to my Uno):

At first I thought this may be to do with the fact Arduino pins give out 5v, however as I am getting the Device ID as DECA - model: 1, version: 3, revision: 3, I don't think this is the issue, although I may be wrong.
Please could someone advise me as to why this issue with the PAN and Short Address is occurring and how I may go about solving this?
Thank You!

This report does not satisfy the minimum requirement. (no used library version, no used example, no ide version...)
Please make a new issue where you use the template!!! https://github.com/thotro/arduino-dw1000/blob/master/.github/ISSUE_TEMPLATE.md
Thanks.


implement questionnaire model

Questionnaire

id
version number
list of questions

Question

questionnaire id
dimension - one of the five different dimensions in the model
activity - one of the 15 different activities
the question
list of answers

Answer

question id (which question is it an answer to)
text of answer (some will be just yes/no, others will be more descriptive)
scoring -- minimum maturity score if this answer is selected
list of suggested improvements

I've just noticed that this outline model doesn't include dependencies between questions/answers. This will need to be added.
Some questions will only become active if the user gives a specific answer to a previous question.
For example we might ask: "How widely adopted is your release process?". For this there are likely to be 3 answers: "its not yet used", "its used in some places", "its used across the organisation".
If the user selects either of the last two answers, then the next question in that section will be displayed.
I think the simplest option for implementing this is to:

specify dependencies between questions
flag each answer to indicate whether its a "positive or "negative" answer

So, if a question (Q2) has a dependency on another (Q1). Q2 will only be shown if the user selected one of the "positive" answers to Q1.

@ldodds - has the dependencies between questions/answers have been added, or is this task captured in a separate issue (then is so which one one).


statusCode: 400, body: { error_description: 'Resource owner authentication failed', error: 'invalid_grant' } } } Error: Authentication failed: Resource owner authentication failed

We are failing to upload our artifacts to all Env , please look this in priority. This is blocking our release activity. Please more logs: statusCode: 400, body: { error_description: 'Resource owner authentication failed', error: 'invalid_grant' } } } Error: Authentication failed: Resource owner authentication failed

@mani762 Did the above help you to resolve your issue and can we close this?


Update knative-serving package to latest

Feature Request
Knative is currently shipping 0.25.0
TCE is still on 0.22.0
Describe alternatives you've considered
Stay on the old version

@seemiller how does this look for the 0.10.0 package repo?
We can move it to 0.11.0 assuming the change did not make it in.

The latest 0.9.2 package repository has knative-serving 0.26.0 and 1.0.0.

@seemiller which PR did this work? Can we attach it to this issue?


Automated cherry pick of #2469: Bug fix in adding iptable rules * bug fix in

Cherry pick of #2469 on release-1.2.
#2469: Bug fix in adding iptable rules * bug fix in
For details on the cherry pick process, see the cherry pick requests page.

Codecov Report

Merging #2540 (ab20cf7) into release-1.2 (1a7658b) will decrease coverage by 0.04%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           release-1.2    #2540      +/-   ##
===============================================
- Coverage        42.18%   42.14%   -0.05%
===============================================
  Files              146      146
  Lines            18200    18218      +18
===============================================
  Hits              7678     7678
- Misses            9834     9851      +17
- Partials           688      689       +1

Flag
Coverage Δ

unit-tests
42.14% <0.00%> (-0.05%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/agent/util/iptables/iptables.go
0.00% <0.00%> (ø)

pkg/apiserver/storage/ram/store.go
77.44% <0.00%> (-1.51%)
:arrow_down:

pkg/apiserver/storage/ram/watch.go
88.46% <0.00%> (+3.84%)
:arrow_up:

/test-all

/test-networkpolicy
/test-ipv6-all
/test-ipv6-only-all

/test-ipv6-only-all

@lzhecheng there was a failure during test setup for jenkins-ipv6-only-conformance apparently
====== Cleanup Antrea Installation ======
Error from server (NotFound): namespaces "antrea-test" not found
ovs-vsctl: no port named gw0
command terminated with exit code 1
ovs-vsctl: no port named gw0
command terminated with exit code 1
ovs-vsctl: no port named gw0
command terminated with exit code 1

I'm going to merge this since I'll be running the tests again at release time.
@tnqn @lzhecheng does this also need to be backported to v0.13 and v1.1?

@antoninbas these failure won't affect the results.
I am not sure if we should remove the ovs-vsctl del-port br-int gw0 command. It was added into the script when gw0 is changed to antrea-gw0.

@antoninbas these failure won't affect the results.
I am not sure if we should remove the ovs-vsctl del-port br-int gw0 command. It was added into the script when gw0 is changed to antrea-gw0.

Do you know why the job is failing then? I couldn't find it in the logs

@antoninbas Indeed there's no clear log about failure. According to the available log, the build fails at the run-k8s-e2e-tests.sh...


dismiss keyboard has stopped working. (using the FocusNode method)

The following code does not work anymore to dismiss the keyboard.
The breakpoint hits the
FocusScope.of(context).requestFocus(new FocusNode());
code but does not really dismiss the keyboard.
main() {
    runApp(new Home());
}

class Home extends StatelessWidget {
    @override
      Widget build(BuildContext context) {
        var widget = new MaterialApp(
            home: new Scaffold(
                body: new Container(
                    height:500.0,
                    child: new GestureDetector(
                        onTap: () {
                            FocusScope.of(context).requestFocus(new FocusNode());
                        },
                        child: new Container(
                            color: Colors.white,
                            child:  new Column(
                                mainAxisAlignment:  MainAxisAlignment.center,
                                crossAxisAlignment: CrossAxisAlignment.center,

                                children: [
                                    new TextField( ),
                                    new Text("Test"),
                                ],
                            )
                        )
                    )
                )
            ),
        );

        return widget;
    }
}

Please add the output of flutter doctor -v.

Not sure if this should be made a dup of #7247
#7247 asks for docs, this is a regression that draws the proposed workaround invalid.

cc @HansMuller
Do we know when this regressed? A bisect to find the offending commit would be really useful.

I just upgraded and its still not working.
Flutter (Channel master, v0.5.8-pre.79, on Mac OS X 10.13.5 17F77, locale en-US)

any update on this ?

@manujbahl What version did this work on for you? I just tried your sample in v0.5.1, v.0.3.0, and v0.1.0, and it didn't work in any of those versions - I tap the text field, keyboard comes up, I tap elsewhere, nothing happens (but it is calling the onTap callback, I checked).

@Hixie not sure. I know it used to work on the alpha channel a couple months back. Im surprised other people are not reporting this

Any progress on this? This is currently blocking us from shipping our app

Is anyone planning on fixing this ?

We don't currently have anyone working on this but if you would like to debug the problem and submit a patch we would be happy to review it and work with you on it.

Any pointers on where to start or how it was being done before?

I'm not sure it was ever being done before, as noted above, I couldn't find a version where this test worked.
FWIW, it appears that calling "unfocus" on the node you wish to unfocus is one way to achieve what you're describing. See: https://docs.flutter.io/flutter/widgets/FocusNode/unfocus.html
To actually debug why the code above (requesting the focus be on a new node) doesn't work, I would begin by walking through the code in packages/flutter/lib/src/widgets/focus_manager.dart and packages/flutter/lib/src/widgets/focus_scope.dart.

To make @zoechi's reference more explicit: an easy way to fix this issue is to make it unnecessary to dismiss the keyboard in this way, and also make an obvious API to allow developers to dismiss the keyboard.
The fix is described in #20227, that is to expose FocusScopeNode._focus as .focus, so that it is easy to find the currently focused node, and to call unfocus on it.
Currently, as @manujbahl describes, and as I encountered, it is not straightforward to keep track of, or to walk though and discover, the currently focused node.
This looks to me like a one-liner to implement in FocusScopeNode, although I'm not sure what testing would be needed.

HOWEVER... I've debugged this issue, and I think I have the answer.
There is no regression. The issue in the sample code is to do with the binding of context and getting the correct FocusScope.
Using a builder allows to have a more useful context. See code attached, in which the keyboard goes away, as expected.
So, I think this bug can be closed. Even so, I'd still like FocusScopeNode.focus to be available, as it makes for more obvious code, as in #20227.
main() {
  runApp(Home());
}

class Home extends StatelessWidget {
  @override
  Widget build(BuildContext context) =>
      MaterialApp(
        home: Scaffold(
          body: Builder(
            builder: (context) => Container(
              height: 500.0,
              child: GestureDetector(
              onTap: () {
                FocusScope.of(context).requestFocus(FocusNode());
              },
              child: Container(
                color: Colors.white,
                child: Column(
                  mainAxisAlignment:  MainAxisAlignment.center,
                  crossAxisAlignment: CrossAxisAlignment.center,

                  children: [
                    TextField( ),
                    Text("Test"),
                  ],
                )
              )
            )
          )
        )
      ),
    );
}


NextjsRevalidationProps Interface May Be To Restrictive

Problem
The following code throws a TypeScript error when setting overrides for nextjsRevalidationProps,
const logRetention = RetentionDays.ONE_YEAR
const nextConstruct = new NextjsGlobalFunctions(this, 'Nebula', {
	buildContext: fileURLToPath(new URL('../../../../web', import.meta.url)),
	healthCheckPath: '/api/health',
	overrides: {
		nextjsGlobalFunctions: {
			nextjsRevalidationProps: {
				overrides: {
					functionProps: {
						functionName: this.stackName + 'Revalidation',
						logRetention,
					},
					queueProps: { queueName: this.stackName + 'Revalidation.fifo' },
				},
			},
		},
	},
})

I've been able to work around this by adding as unknown as NextjsRevalidationProps, but it would be nice if NextjsRevalidationProps did not require fn, and previewModeId when used as an override.
Error
Type '{ overrides: { functionProps: { functionName: string; logRetention: RetentionDays.ONE_YEAR; }; queueProps: { queueName: string; }; }; }' is missing the following properties from type 'NextjsRevalidationProps': fn, previewModeId

We cannot use TS Utility Types in CDK/JSII when it's exported from library, so it looks like we'll need to generate a new type. I'll look into this.

Okay, sounds good.
I am also seeing this restrictiveness for a few other interfaces...

FileSystemProps

NextjsFunctionsProps

As mentioned earlier, there is a workaround of casting to unknown and then casting to the required type.


Error updating the NVD Data always at the same Index 224000  (82%) v9.2.0

Describe the bug
I cannot update my NVD Data with any of the Versions 9.0.6, 9.0.7 and 9.2.0.
The update process always stops at the same index.
Purged the Database but this did not solve the problem.
I provide an api-Key and tried multiple delay-options.
I think this is some kind of memory Issue since the application uses over 4gb of Memory when stuck at 82% for a very long time.
i will try with 6gb or so but this is quiet a lot of memory for putting 10.000 additional entries into the database.
Version of dependency-check used
9.2.0 but i tried multiple 9er versions always the same at the same index.
So its unlikely an issue with service overused or something that would usually not happen exactly at the same Index 224000.
Log file
[INFO] Checking for updates
[INFO] NVD API has 255.878 records in this update
[INFO] Downloaded 10.000/255.878 (4%)
[INFO] Downloaded 20.000/255.878 (8%)
[INFO] Downloaded 30.000/255.878 (12%)
[INFO] Downloaded 40.000/255.878 (16%)
[INFO] Downloaded 50.000/255.878 (20%)
[INFO] Downloaded 60.000/255.878 (23%)
[INFO] Downloaded 70.000/255.878 (27%)
[INFO] Downloaded 80.000/255.878 (31%)
[INFO] Downloaded 90.000/255.878 (35%)
[INFO] Downloaded 100.000/255.878 (39%)
[INFO] Downloaded 110.000/255.878 (43%)
[INFO] Downloaded 120.000/255.878 (47%)
[INFO] Downloaded 130.000/255.878 (51%)
[INFO] Downloaded 140.000/255.878 (55%)
[INFO] Downloaded 150.000/255.878 (59%)
[INFO] Downloaded 160.000/255.878 (63%)
[INFO] Downloaded 170.000/255.878 (66%)
[INFO] Downloaded 180.000/255.878 (70%)
[INFO] Downloaded 190.000/255.878 (74%)
[INFO] Downloaded 200.000/255.878 (78%)
[INFO] Downloaded 210.000/255.878 (82%)
[ERROR] Error updating the NVD Data
org.owasp.dependencycheck.data.update.exception.UpdateException: Error updating the NVD Data
at org.owasp.dependencycheck.data.update.NvdApiDataSource.processApi(NvdApiDataSource.java:389)
at org.owasp.dependencycheck.data.update.NvdApiDataSource.update(NvdApiDataSource.java:116)
at org.owasp.dependencycheck.Engine.doUpdates(Engine.java:906)
at org.owasp.dependencycheck.Engine.initializeAndUpdateDatabase(Engine.java:711)
at org.owasp.dependencycheck.Engine.analyzeDependencies(Engine.java:637)
at org.owasp.dependencycheck.App.runScan(App.java:262)
at org.owasp.dependencycheck.App.run(App.java:194)
at org.owasp.dependencycheck.App.main(App.java:89)
Caused by: io.github.jeremylong.openvulnerability.client.nvd.NvdApiRetryExceededException: NVD Update Failed: attempted to retrieve starting index 224000 from the NVD unsuccessfully five times.
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.queueUnsuccessful(NvdCveClient.java:424)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.hasNext(NvdCveClient.java:300)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:323)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:324)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:324)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
at io.github.jeremylong.openvulnerability.client.nvd.NvdCveClient.next(NvdCveClient.java:343)
......
To Reproduce
I restart the Jenkins-Job or run it per cmd (dependency-check.bat --updateonly --nvdApiKey xxxxxxxx).
Expected behavior
Download of all entries without errors.
here is an image from VisualVM

Not a bug, but stability issues of the NVD infrastructure.
Duplicate of #6758

See also #6786


Runtime hardening followup tasks

for complicated steps like this it probably makes more sense to just make it a checked in bash file.
Originally posted by @anthonydresser in https://github.com/microsoft/azuredatastudio/pull/8663

[Action Needed by 4/1/2020]
Tracking this as well https://github.com/microsoft/azuredatastudio/pull/8663#discussion_r384824838

Not really a customer facing issue and I'll tackle this during DRI.


Support for strftime formatters in 0.3

I'm really surprised to see that strftime formatting options are not available in time. While the new formatting format is more readable, it's also significantly more verbose, and rewriting existing strftime formatting strings in this new format is error prone:
- static FORMAT: &str = "%a, %d %b %Y %H:%M:%S GMT";
+ static FORMAT: &[time::format_description::FormatItem<'_>] = format_description!(
+     "[weekday repr:short], [day] [month repr:short] [year base:calendar] \
+     [offset_hour]:[offset_minute]:[offset_second] GMT"
+ );

The documentation is also lacking, so I have no idea if these are actually equivalent. Examples would help, especially if they are exhaustive. For example, month says:

The long format is the full English name of the month, while the short format is the first three letters of it.

For the short format, is it written "Jan" or "jan" or "JAN"?

Would a tool like the one for 0.1 to 0.2 alleviate concerns over transitioning?
I don't dispute that it's more verbose, that's almost the point. I personally prefer to have something that can be both easily read and written, not just written (sorta like regex). Given the intermediate representation, I suppose it would be possible to have a parser for the older format. I'm not a huge fan of having two completely different formats, though, so that should probably fall to a third-party crate.
With regard to documentation, you're the one that asked for a release without waiting for full docs 😛  The short format is "Jan" — all it does is truncate it to three letters, still following standard English capitalization.

I've just updated the aforementioned tool to support converting 0.2 to 0.3. The only compatibility note here is that %C (the century-like part of the year) has been removed, so there's no equivalent. Everything other valid format should be converted to an equivalent format.
The format you included becomes
[weekday repr:short], [day] [month repr:short] [year] [hour]:[minute]:[second] GMT

Note that the output of the tool does not include any modifiers that are default — in this case the year's repr defaults to the calendar year.

year seems to work a bit differently that I would have expected, and presumably differently than it used to work, when the year has only two digits. I would expect that a format of [year] used to parse 20 would parse the year as 20. Instead, parsing fails unless I use repr:last_two. But this seems wrong. The year 20 is a valid year...the year 20.

The padded value has a width of 4. You can choose between padding with zeroes, spaces, or having no padding at all. The default is to pad the value with zeroes.

This is key. 20 is invalid for [year]. If you don't care about padding, you need to specify it with [year padding:none]. I've just confirmed this works:
use time::macros::format_description;
use time::Date;

fn main() {
    let date = Date::parse(
        "19-002",
        &format_description!("[year padding:none]-[ordinal]"),
    )
    .unwrap();
    dbg!(date);
}

The Parsed struct has the year and year_last_two fields, though the latter is currently not considered when constructing a Date. I'm not willing ruling out assuming it to be between (say) 1970-2069, hence the "not guaranteed" statement. Which field the value gets assigned to depends on whether repr is full or last_two.

This is key. 20 is invalid for [year]. If you don't care about padding, you need to specify it with [year padding:none]. I've just confirmed this works:

This is pretty weird and really unexpected. In any case, the converter should take this into account, then. I don't think %Y has the same restriction, and yet it is converted to [year].

Formatting and parsing will be better documented. Were it not for your request, I likely wouldn't have even released 0.3 yet, as I wanted to have better documentation first.

With respect to formatting, you've deviated substantially from the universally accepted, battle tested, understood norm. Yes, I totally missed this in pushing for the release, and I would advocated for keeping the previous formatting spec, but even so I don't think this is a mater of "better" documentation but about precision. There's enough documentation to be useful, but not enough to know if my code is correct. This is also the piece of time's documentation that appears to have the most effort put into it and so I would imagine that in considering what to pour effort into prior to a release, it would not have been particularly reconsidered. But who knows. Nevertheless, I think releasing 0.3 was absolutely the right thing to do.

This is pretty weird and really unexpected. In any case, the converter should take this into account, then. I don't think %Y has the same restriction, and yet it is converted to [year].

After quickly looking, this was likely a bug in 0.2. This function did not take the length of the consumed padding into account the same way it was here. Had I noticed it early on I probably would have fixed it. At this point it would effectively be a breaking change for 0.2. The converter could take this into account, but then the formatting wouldn't be the same, only parsing would.

With respect to formatting, you've deviated substantially from the universally accepted, battle tested, understood norm.

Unquestionably. I still believe this was the best decision, as it allows for far more flexibility, expansion possibilities, and future performance improvement. Single-letter components was error prone when writing, nearly impossible to read, and had near-zero possibility for expansions like case insensitive parsing — something relatively easy to implement now.

This is also the piece of time's documentation that appears to have the most effort put into it and so I would imagine that in considering what to pour effort into prior to a release, it would not have been particularly reconsidered.

It's hard to say definitively of course, but I likely would have improved documentation in that area, as I know it's still not thorough enough (I just wanted something basic to at least have it documented).

Shameless plug: I ended up with creating a crate doing it. It isn't "production-ready" quality (because I don't need that quality for my use case) and probably should be considered as a never-ending beta/experimental state, but in case anyone interested: https://github.com/MiSawa/time-fmt/


bump geneva image versions

bump geneva image versions

@nilsanderselde @Makdaam this needs to be in the next rollout


Need UCP please

Can you provide Web UCP of gamemode please?

I need it too, is there a link with it?


Not possible to get current NancyContext through dependency injection

When a component requires the current NancyContext through its constructor, an empty NancyContext is injected (probably a freshly new()ed instance). Adding the NancyContext to the Container in RequestStartup will cause all sorts of troubles since it is Disposed by the container before Nancy is finished with it (I believe that the Response stream is Disposed before Nancy has written the response to it if you do that).
Expected behavior: The current NancyContext is injected into the dependent component.
Work around: Create a wrapper around NancyContext and inject that into the container through the RequestStartup method on the bootstrapper, and ofcourse change the dependency to the wrapper object. This is what I currently do in my (very new) library for behavior chains: https://github.com/jvandertil/NancyChains. But if one wants to use more libraries which do the same trick (each having their own wrapper) this will result in a mess for the end user.
I was unable to find an issue for this previously, but is this something that can be fixed?

I found this issue because I also tried to inject NancyContext. Have you considered making the context a parameter on the IHandlerClient#Handle method?

@jvandertil hm, I see for example that your solution won't work with Windsor Bootstrapper, because it doesn't allow registering on request container and uses request scope instead.
There may be a middle ground a solution have you considered an IRequestStartup, which would set the context on a per-request registered type? Here's the code
public class NancyContextWrapper
{
	public NancyContext Context { get; internal set; }
}

public class NancyContextWrapperStartup : IRequestStartup
{
	private readonly NancyContextWrapper _contextWrapper;

	public NancyContextWrapperStartup(NancyContextWrapper contextWrapper)
	{
		_contextWrapper = contextWrapper;
	}

	public void Initialize(IPipelines pipelines, NancyContext context)
	{
		_contextWrapper.Context = context;
	}
}

public class NancyContextWrapperRegistrations : Nancy.Bootstrapper.Registrations
{
	public NancyContextWrapperRegistrations()
	{
		Register<NancyContextWrapper>(typeof(NancyContextWrapper), Lifetime.PerRequest);
	}
}

It's a bit hackish and whenever NancyContextWrapper is registered one has to guard against null in the Context property, which is a bummer. On the up side this will likely work with any container without manual setup in the bootstrapper

Using SimpleIoC and had to use the wrapper approach... not exactly a fun error to find.

I just encountered this need and here's what I ended up doing for Autofac:
Created a NancyContextWrapper:
public class NancyContextWrapper
    {
        public NancyContext Context { get; }

        public NancyContextWrapper(NancyContext context)
        {
            Context = context;
        }
    }

Then registered it by overriding the CreateRequestContainer to avoid calling Update() as it's obsolete:
protected override ILifetimeScope CreateRequestContainer(NancyContext context)
        {
            return ApplicationContainer.BeginLifetimeScope(MatchingScopeLifetimeTags.RequestLifetimeScopeTag,
                builder =>
                {
                    builder.Register(c => new NancyContextWrapper(context)).InstancePerRequest();
                });
        }

Whatever needs a NancyContext now just takes a dependency on NancyContextWrapper and gets at it that way. There were some downstream items that needed access to data that was being passed in via Request  Headers and this approach seemed to be working out fine. The consumer of this is a "Provider" that builds out a POCO by inspecting the RequestHeaders.
Reference on registering while creating a LifetimeScope: http://docs.autofac.org/en/latest/lifetime/working-with-scopes.html


Adds MML classes in SVG configuration.

Addresses issue #32.

LGTM.

I was going to say that an alternative to this would be to have the collapsing code (which inserts the mactions) mark the mactions with its own class name, so that (a) you don't need to turn on MML classes (so that the SVG is reduced in complexity and size), and (b) you can looks for the same class name in all the output modes, since it will be kept the same for them all.

@dpvc happy to revert and follow your suggestion.

I understand the reasoning. However, the additional structure makes it easier for the walker. In general for SVG accessibility more structure is better than less.
What is the additional complexity? Is it a constant factor?

OK, sounds good.  Leave it as is.

What is the additional complexity? Is it a constant factor?

Sorry forgot to answer this.  No, I don't think it is constant, but haven't tried to measure it exactly.  It consists of removing nested groups that are not necessary. so an mrow consisting of an mn, an mo, and an mn with addMMLclasses set to true would normally have a g element for each of the MathML elements, but without addMMLclasses, only the outer g for the mrow would be retained, and it would contain three path elements (assuming one character for each of the token elements).  If that g were a child of some other <g> higher up in the MathML structure, it could also be removed.


How to answer rootDSE query

I have an ldap server ticket that requires adding support for Apache directory studio concerning an error that occurs from the lack of a rootDSE response.
is there any docs out there on how I should answer it?
Based on  this
I am entering a ldapquery against a local instance
ldapsearch -h <IP_ADDRESS> -b "" -s base "(objectclass=*)"

I see immediately that the query is not reaching the bind or search handler. I tried adding the following code to the middleware with a hardcoded stub respnse.

try {
    console.log('############')
    Logger.info('INFO', 'DSE - ', JSON.stringify(req.filter.toString()) , "+", _.keys(req))
      if (req.filter.toString() === "(objectclass=*)") {
        console.log('capture!!!');
        res.send({
          "attributes":{"objectClass":["*"]},
          "dn2":"ou=users,dc=onelogintestpeter,dc=onelogin,dc=com"
        });
        return res.end();
      }
    } catch (err) {
      console.log('$$$$', err);
    }

However when I run the command I get

ldap_sasl_interactive_bind_s: No such attribute (16)

What is the proper way for me to respond to the rootDSE request?

From that error, it appears that the client is attempting to perform a SASL bind (and failing) before issuing the query against the rootDSE.  Unless you happened to have implemented SASL for your server, I would suggest configuring the client to do plain auth.

Thankyou!  I changed my connection to include a username and pass
ldapsearch -H ldap://<IP_ADDRESS> -D "cn=peter@escobar.com,ou=users,dc=onelogintestpeter,dc=onelogin,dc=com" -b "" -s base -w "fooBar50" "(objectclass=*)"

I'm still getting the DSE issue but I see now that I have programmatic conrol over the output. The one question is I'm not sure what I need to send down to satisfy apache directory studio.
what kind of parameters am I supposed to send? I've seen a few diserpate articles that list the need in terms of open ldap but I'm not sure what its specifically asking for.

nvm, this solved it
  res.send({
          "attributes":{
            "objectClass":["top", "OpenLDAProotDSE"],
            "subschemaSubentry": ["cn=subschema"]},
          "dn":"ou=users,dc=onelogintestpeter,dc=onelogin,dc=com",
        });

For anyone wandering where / how this can be applied:
https://github.com/phaus/shadow-ldap

⚠ This issue has been locked due to age. If you have encountered a recent
problem that seems to be covered by this issue, please open a new issue.
Please include a minimal reproducible example
when opening a new issue.


[CELEBORN-1323] Introduce ShutdownWorkerCount metric to record the count of workers in shutdown list

What changes were proposed in this pull request?
Introduce ShutdownWorkerCount metric to record the count of workers in shutdown list.

Why are the changes needed?
/shutdownWorkers lists all shutdown workers of the master at present. Therefore it's recommended to introduce ShutdownWorkerCount metric to record the count of workers in shutdown list.
Does this PR introduce any user-facing change?
No.
How was this patch tested?

Celeborn Dashboard

cc @FMX.


How to access maxprot ?

    let macho = object::read::macho::MachOFile64::<object::endian::LittleEndian>::parse(&*mmap).unwrap();
    for segment in macho.segments() {
        println!("{}", segment.maxprot()); // how to access maxprot ?
    }

How to access maxprot ?
#[derive(Debug)]
pub struct MachOSegment<'data, 'file, Mach, R = &'data [u8]>
where
    'data: 'file,
    Mach: MachHeader,
    R: ReadRef<'data>,
{
    file: &'file MachOFile<'data, Mach, R>,
    internal: &'file MachOSegmentInternal<'data, Mach, R>,
}

I found maxprot in segment in  internal.
#[derive(Debug, Clone, Copy)]
pub(super) struct MachOSegmentInternal<'data, Mach: MachHeader, R: ReadRef<'data>> {
    pub data: R,
    pub segment: &'data Mach::Segment,
}

So , how could I access maxprot ? Should I add functions for ObjectSegment ?
Thanks :)

For an example using the lower level API, see https://github.com/gimli-rs/object/blob/56299a3b6acb4d38fc14e0a2557112433f82e789/crates/examples/src/readobj/macho.rs#L541
I'm not sure that maxprot makes sense to access in the unified API. What would the equivalent be for ELF and PE/COFF?

Thanks.
I originally want to access R,W,E attribute for the load command.
For example,  ELF PT_LOAD exists p_flags.

PE/COFF exists a  Characteristics (section flags)
https://docs.microsoft.com/en-us/windows/win32/debug/pe-format#section-flags

We could certainly add a RWX flags function to ObjectSegment, but probably it should use initprot for Mach-O? I'm not sure.
What do you want to achieve by reading maxprot?

Oh, I get it. The initprot is what I really need. I just use maxprot as an example.
It's great if RWX flags  could be added.

Are you writing this new flag function ? Otherwise I think I could make a pull request. @philipc

I won't get to it immediately. Feel free to make a pull request.


chore(dependencies): Add jsonPath 2.2.0 dependency

Had to pin it to version 2.2.0, as the version in the Spring platform BOM 1.1.5 is the five years old version 0.9.1 (which broke unit tests, so I guess it will not work in practice either).
/cc @robzienert ref. https://github.com/spinnaker/orca/pull/1257

👍


Remove physics thread getting the gl context

For the reference, this was likely kept by mistake when copying the implementation from visual_server_wrap_mt.cpp.

Thanks!


Release 0.9-beta.5

This change is

Coverage increased (+0.03%) to 47.07% when pulling 4bdbe993fe6a04c7a570deda01bbd482b943a1ab on aledbf:beta5 into a1b6fa7d5b8d446bd661eeede651fe2a69612a6b on kubernetes:master.

Coverage increased (+0.03%) to 47.07% when pulling a0a7f013cc70f962e0dea5bdb00c570f89b94c9e on aledbf:beta5 into c8a9385d047c5754f1057b3639e49100ee5242a7 on kubernetes:master.

Can you please update ingress/controllers/nginx/Makefile too?

@ixdy done.

Coverage increased (+0.03%) to 47.07% when pulling 83cb03b51ccbbd380a467d2476b45caaf1fa3dd1 on aledbf:beta5 into c8a9385d047c5754f1057b3639e49100ee5242a7 on kubernetes:master.

Pushed gcr.io/google_containers/nginx-ingress-controller:0.9.0-beta.5, built with go1.8.1.
At some point @nicksardo should maybe take over doing this. :)

@ixdy No problem - happy to take this off your hands.

@ixdy thanks!


support for scala3

Are there any impediments to cross-building and publishing scala3 binaries?

This is currently blocked by eff not having a Scala3 version yet.
I have plans of not using eff at all in this project in the future; when that happens or if eff gets published for Scala3 I will immediately start cross-publishing for it too.

I understand.
Meanwhile, do you have any suggestion how to use the clipp 2.13 library from a scala3 program?
I managed to get almost there with this application:
https://github.com/NicolasRouquette/scala3-bundle-closure/blob/master/src/main/scala/io/opencaesar/oml2owl/Oml2OwlApp.scala
However, I get a strange compilation error without any source attribution:
[error] An existential type that came from a Scala-2 classfile cannot be
[error] mapped accurately to to a Scala-3 equivalent.
[error] original type    : (S[X], X => cats.free.Free[S, A]) forSome X
[error] reduces to       : (S[X], X => cats.free.Free[S, A])
[error] type used instead: (S[Any], Any => cats.free.Free[S, A])
[error] This choice can cause follow-on type errors or hide type errors.
[error] Proceed at own risk.
[error] one error found
[error] one error found
[error] (Compile / compileIncremental) Compilation failed
[error] Total time: 1 s, completed Apr 4, 2021, 4:24:30 PM

I could not find a way to solve this problem so I decided to copy just what I need of clipp to compile with scala 3.0.0-RC2.
https://github.com/NicolasRouquette/scala3-bundle-closure/tree/scala3-only

I don't know how to fix that existential type error, but will look into this and try to provide a Scala3 build or some workaround soon.

Seems like all the dependencies are now released for Scala 3, I'll try to make a release soon


AE2 channels

Trying to make a compact machine with a 2 ae assemblers, each with 4 interfaces.
Dense cable links outside and inside, but connecting to it via smart cables wont let all interfaces get a channel...
Extending on this, putting patterns into the interface, then breaking the CM block does not give back the patterns

I had no troubles with AE cables, using a dense cable inside and outside the same "tap" of the compact machine, with the tap setted to Auto let me bring in\out all 32 channels.

perhaps...im playing dns techpack and some of the interactions in that pack can be a bit weird

Currently working on a 1.10.2 version, the 1.7.10 version is not being maintained anymore, sorry.
Closing all issues not relevant for the new version.


Case-sensitive filesystems are treated insensitively

I'm trying to figure out how best to handle #121106, but while testing on a case-sensitive file-system I noticed that VS Code is treating it insensitively. Here I created two files differing only in case, but VS Code only shows one, and when I try to open the second one, VS Code instead just shows the first (the content here says lowercase but the tab shows FOO.DART, yet FOO.DART contains UPPERCASE:

If VS Code is going to treat all filesystems as case-insensitive, that would also simplify things for language extensions, but my understanding from #121106 is that the filesystems behaviour should be honoured. It's important that language servers know how the client will behave (and in the case of LSP that clients behave the same, or announce their behaviour).

We don't support case sensitive macOS: https://github.com/microsoft/vscode/issues/94307

@bpasero is there any way for me to understand what the rules are here for all platforms? For example on Windows and Linux does VS Code also assume all file-systems behave one way, or does it handle case-sensitivity based on the specific volumes there?
Thanks!

@DanTup check how our local native file system provider only adds the path case sensitive capability on Linux here:
https://github.com/microsoft/vscode/blob/c554dccf10a164fb51dae18e69c5663199d6c343/src/vs/platform/files/node/diskFileSystemProvider.ts#L61-L76
When you are connected to a remote (SSH, Docker, WSL), we respect the target OS in the same way.
tl;dr: only Linux is considered path case sensitive for VSCode.

@bpasero thanks! I just found something similar here:
https://github.com/microsoft/vscode/blob/fd529498f0e70feeb75730a5a155d5d878cb2750/src/vs/workbench/test/browser/api/extHostConfiguration.test.ts#L33

only Linux is considered path case sensitive for VSCode (either local or remote)

To clarify - this means where the extension host is running, right? So on Windows WSL, it would be considered Linux and sensitive?
Thanks!

Yeah thats right. And for any other file system provider we respect whatever is used when registering the provider:
https://github.com/microsoft/vscode/blob/e1a01761fdb4f4e537f18afe05986e56d9b5bf99/src/vs/vscode.d.ts#L10717-L10717

Got it - thanks! (I think that flag might not be available to LSP servers, although I suspect most do not currently support non-file:// URIs so maybe not a big issue).
Is this likely something that will be improved in the future? It seems like right now a language server will need to decide between doing what VS Code is doing, or doing what the underlying filesystem says (both of which will likely have some edge cases that may have issues).
Thanks!

It seems like right now a language server will need to decide between doing what VS Code is doing, or doing what the underlying filesystem says

Is this specifically for macOS that is configured to be case sensitive?

@bpasero the original issue I need to fix shows up for macOS case-insensitive too (https://github.com/microsoft/vscode/issues/121106), though it's not strictly caused by this (it's caused by VS Code telling us a file was renamed, but then sending events using its old casing). Fixing this is going to require changes in the language server (eg. to resolve all incoming paths to their underlying filesystem case, rather than assuming the one from VS Code is correct) so I want to make sure I fully understand the rules before making changes (to avoid potentially introducing other issues because we normalised paths somewhere VS Code was treating them as case-sensitive even if the filesystem did not).

I think we have so far stayed away from supporting case sensitivity on macOS simply because back in the days it seemed not recommended to run with given a lot of apps assume different. Unless there is overwhelming ask from the community I do not think we would tackle that anytime soon.

This affects Windows and Linux too - both of them support both types of filesystems. I don't know if they're common or fraught with danger though (although I'll note I do use USB sticks and external drives across platforms, so I guess at least at some times I'm using filesystems that wouldn't match VS Code's behaviour).
Probably it makes sense for the language server to use the underlying filesystem, otherwise it may introduce bugs for non-VS Code users. The number of affected users is probably fairly small (and if they do hit issues, it's more understandable given VS Code's behaviour than it would be in a non-VS Code editor that's behaving as expected).
Thanks for the info!


ci: run e2e on pipeline config related changes

I noticed that the e2e workflow did not run on #150. That PR only
changed some yaml files. When yaml files under src/ change, we want
to run e2e, just like we do with python source changes.
Signed-off-by: Russell Bryant<EMAIL_ADDRESS>

lgtm


Error adding a repeating set question

Description
Adding a repeating question set to a form results in a client error.
This may be from an invalid dynamically created script tag.
Steps to reproduce

Open a new or existing form in edit mode
Click on "Add"
Select Repeating set and add one
Try to preview the form
A client error is shown

Expected behaviour
Adding a repeating set to a form successfully displays on the preview screen.
Screenshots or videos
https://github.com/cds-snc/platform-forms-client/assets/107579368/91107acc-f7c0-41b8-82c0-4cf009befd1a

Unable to reproduce this bug locally. The issue is probably only on the PR environment. Closing for now


using Tablesaw inside WordPress themes

Hello,
Is it possible to use tablesaw inside wordpress?
I especially would like to know if sizzle.js (included with tablesaw's jquery.js file) is needed and if so, can it be added separately so that the jquery inside wordpress can continue to be used.
Thanks
Fraser

Yeah you can grab the sizzle.js file from the website and use that instead since its just the sizzle code without the included jquery. This will allow  you to keep using  your own jquery version.

@UmbraLimi If you use WP's version of jQuery, you won't need a seperate copy of sizzle. It will be included. A quick guide for setting up jQuery as a dependency is at
https://developer.wordpress.org/reference/functions/wp_enqueue_script/#comment-276

jQuery shouldn’t be bundled with Tablesaw. If it’s provided, it’s only for demo purposes and is referenced separately. Let me know if you have questions.


Update Publishing to IIS

Fixes #1264

Hi @GuardRex, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

I tried *** to get
's in there, but that didn't seem to work. Maybe I was doing it wrong? Maybe it was just because I was looking at it in my fork in GH and not actually rendered by the doc engine?
I pulled "Issue #," but I don't think it looks too good. I had to block the Troubleshooting lists (indent them) so that it wouldn't get rolled into the next set of behaviors.
I kind'a like what I had there on the first pass (w/o "Troubleshooting:"), but perhaps that was too confusing where one stopped and the next started. @danroth27, you said it didn't render well.

Behavior #1
Behavior #2
Behavior #3

Troubleshooting #1
Troubleshooting #2

Behavior #1
Behavior #2
Behavior #3

Troubleshooting #1
Troubleshooting #2

Behavior #1
Behavior #2
Behavior #3

Troubleshooting #1
Troubleshooting #2

If *** will render as
, then I could try again ...

Behavior #1
Behavior #2
Behavior #3

Troubleshooting #1
Troubleshooting #2

Behavior #1
Behavior #2
Behavior #3

Troubleshooting #1
Troubleshooting #2

Behavior #1
Behavior #2
Behavior #3

Troubleshooting #1
Troubleshooting #2

merged - it's taking some time to show up tho.

@Rick-Anderson Is this one ok? It looks like it's closed without being merged.

Hi @GuardRex, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

Let me know if it needs more work on the layout (e.g., go for
's between the Common Error issues).

@danroth27  I merged it - see https://github.com/aspnet/Docs/commits/master
I closed 6 PR's i merged - do they all need to be reopened?

@Rick-Anderson please include the commit hash in the PR before closing so that we can verify that things have been merged. No need to reopen anything if the commits on master can be accounted for.

Also, we were having build issues for a couple of days. This has been fixed, so changes should start showing up again.

Thanks! b5194e7da43b9ffa4ff7601fe6246a1be76c6c03

@GuardRex And yes, the formatting still bugs me :smile:. Also, now there is now way to link to individual issues, which I think would be useful.

@danroth27 Yep. The troubleshooting of one common error runs into the behaviors of the next.
The only problem with titling them was the 500.19 and one of the 502.3 issues, where there are multiple causes. Let me see what happens when I try to title them. I'll give that a shot and create a PR with some proposed titling that might work.


Domain definition extraction via DBeaver (question/bug)

Greetings.
I'm new to DBeaver and love the interface. Thank you for a great product;
I'm running 5.2.2 on macOS 10.12.6 (Sierra).
I'm trying to access user defined domain definitions via the interface without success. In order words, trying to get the equivalent of the following via psql:
PSQL:
my_data=# \dD 'domain_i_defined'
1) What follows is the query run via psql when \dD is executed at the psql prompt:
********* QUERY **********
SELECT n.nspname as "Schema",
t.typname as "Name",
pg_catalog.format_type(t.typbasetype, t.typtypmod) as "Type",
TRIM(LEADING
COALESCE((SELECT ' collate ' || c.collname FROM pg_catalog.pg_collation c, pg_catalog.pg_type bt
WHERE c.oid = t.typcollation AND bt.oid = t.typbasetype AND t.typcollation <> bt.typcollation), '') ||
CASE WHEN t.typnotnull THEN ' not null' ELSE '' END ||
CASE WHEN t.typdefault IS NOT NULL THEN ' default ' || t.typdefault ELSE '' END
) as "Modifier",
pg_catalog.array_to_string(ARRAY(
SELECT pg_catalog.pg_get_constraintdef(r.oid, true) FROM pg_catalog.pg_constraint r WHERE t.oid = r.contypid
), ' ') as "Check"
FROM pg_catalog.pg_type t
LEFT JOIN pg_catalog.pg_namespace n ON n.oid = t.typnamespace
WHERE t.typtype = 'd'
AND t.typname ~ '^(domain_i_defined)$'
AND pg_catalog.pg_type_is_visible(t.oid)
ORDER BY 1, 2;

2) The SQL in 1) above was derived by starting psql with psql -E
3) DBeaver neither shows me the definition of any user defined domain nor does the SQL above return anything meaningful when run in DBeaver's SQL editor; I get a blank table with all the "right" columns -  but no data.
Expected outcome  would be something like the following  - which I get via psql:
example:
biomonitoring_warehouse=# \dD 'biomonitoring_rating5'
********* QUERY **********
SELECT n.nspname as "Schema",
t.typname as "Name",
pg_catalog.format_type(t.typbasetype, t.typtypmod) as "Type",
TRIM(LEADING
COALESCE((SELECT ' collate ' || c.collname FROM pg_catalog.pg_collation c, pg_catalog.pg_type bt
WHERE c.oid = t.typcollation AND bt.oid = t.typbasetype AND t.typcollation <> bt.typcollation), '') ||
CASE WHEN t.typnotnull THEN ' not null' ELSE '' END ||
CASE WHEN t.typdefault IS NOT NULL THEN ' default ' || t.typdefault ELSE '' END
) as "Modifier",
pg_catalog.array_to_string(ARRAY(
SELECT pg_catalog.pg_get_constraintdef(r.oid, true) FROM pg_catalog.pg_constraint r WHERE t.oid = r.contypid
), ' ') as "Check"
FROM pg_catalog.pg_type t
LEFT JOIN pg_catalog.pg_namespace n ON n.oid = t.typnamespace
WHERE t.typtype = 'd'
AND t.typname ~ '^(biomonitoring_rating5)$'
AND pg_catalog.pg_type_is_visible(t.oid)
ORDER BY 1, 2;

                                 List of domains

Schema |         Name          |  Type   | Modifier |               Check
--------+-----------------------+---------+----------+-----------------------------------
public | biomonitoring_rating5 | integer |          | CHECK (VALUE >= 1 AND VALUE <= 5)
(1 row)
biomonitoring_warehouse=#
4)  I don't believe this is a permissions issue, given that I get no errors, and am working as user/role postgres.
Any help will be appreciated.
Cheers from South Africa.

If it is still actual - feel free to reopen the ticket


Start fails with ERRO Error loading machine: dial tcp: missing address

General information

OS: macOS
Hypervisor: hyperkit
Did you run crc setup before starting it (Yes/No)? Yes

CRC version
CodeReady Containers version: 1.16.0+bf72d3a
OpenShift version: 4.5.9 (embedded in binary)

CRC status
ERRO Cannot load machine: dial tcp: missing address
Cannot load machine: dial tcp: missing address

CRC config

Host Operating System
ProductName:	Mac OS X
ProductVersion:	10.15.6
BuildVersion:	19G2021

Steps to reproduce

crc setup
crc start --pull-secret-file ~/Downloads/pull-secret.txt --log-level debug

Expected
Creation of the openshift vm
Actual
DEBU CodeReady Containers version: 1.16.0+bf72d3a
DEBU OpenShift version: 4.5.9 (embedded in binary)
DEBU Total memory of system is<PHONE_NUMBER>6 bytes
DEBU No new version available. The latest version is 1.16.0
INFO Checking if oc binary is cached
DEBU Running '/Users/outcoldman/.crc/bin/oc/oc version --client'
DEBU oc binary already cached
INFO Checking if podman remote binary is cached
DEBU Currently podman remote is not supported
INFO Checking if goodhosts binary is cached
DEBU goodhost binary already cached
INFO Checking minimum RAM requirements
DEBU Total memory of system is<PHONE_NUMBER>6 bytes
INFO Checking if running as non-root
INFO Checking if HyperKit is installed
INFO Checking if crc-driver-hyperkit is installed
DEBU Checking if crc-driver-hyperkit is installed
DEBU Running '/Users/outcoldman/.crc/bin/crc-driver-hyperkit version'
INFO Checking file permissions for /etc/hosts
DEBU Checking if /etc/hosts ownership/permissions need to be adjusted after crc upgrade
INFO Checking file permissions for /etc/resolver/testing
ERRO Error loading machine: dial tcp: missing address
Error loading machine: dial tcp: missing address

The file cat /etc/resolver/testing is empty
Logs
You can start crc with crc start --log-level debug to collect logs.
Please consider posting this on http://gist.github.com/ and post the link in the issue.

Deleted .crc folder and recreated everything. Closing issue


Improve Onboarding Screen

Is your feature request related to a problem? Please describe.
When I opened the app, I didn't find any detailed information about how the app works.
Describe the solution you'd like
To demonstrate how the app works, I would like to use viewpager2 in order to display all the features of the app.
Describe alternatives you've considered
I can also implement a bubble showcase to show all the hidden features of the app.

Please assign me this issue

Please assign me this issue

Also confirm my understanding about your idea man

Yes i understood .


bug: after a long conversation the reply is taking too long ,the perfromence is slowing down...

We have written the needed data into your clipboard because it was too large to send. Please paste.

Hey @bxf1001g
the performance decrease on long conversations was already fixed.
If the issue persists, please fill out a new issue and provide all the information needed to reproduce the error:
Thank you

@PriNova
Hi,
Thank you for the fix! I’ve noticed a significant improvement, and I currently have no issues with the performance during long conversations.
However, I’m facing another challenge with the OpenAI 01 Preview: the responses are often incomplete, and I need to type "continue" repeatedly to get the full response. This can disrupt the workflow.
Is there any way to address this or a setting to ensure the responses are complete in one go?
Thank you......


Use common shelley credentials

See https://github.com/input-output-hk/ouroboros-network/commit/2194d81d745c75dda57063ba89e56e1ec6b37753

Let's use #2114 instead of duplicating it.


API onFailure Callback not working correctly

I am doing a standard API request and even though the following JSON is returned it is still going to the onSuccess callback instead of the onFailure callback.
{"success": false}

My Semantic UI API debugging trace as a JSON object.
[
  {
    "Name": "API called without element, no events attached",
    "Arguments": [

    ],
    "Execution Time": 1
  },
  {
    "Name": "Querying API endpoint immediately",
    "Arguments": [

    ],
    "Execution Time": 0
  },
  {
    "Name": "Looking up url for action",
    "Arguments": [
      "create quote version",
      {
        "create quote": "api/v1/quote/create",
        "create quote version": "api/v1/quote/create/version",
        "find client": "api/v1/client/find/{query}"
      }
    ],
    "Execution Time": 1
  },
  {
    "Name": "Querying URL",
    "Arguments": [
      "api/v1/quote/create/version"
    ],
    "Execution Time": 0
  },
  {
    "Name": "Sending request",
    "Arguments": [
      null,
      "post"
    ],
    "Execution Time": 0
  },
  {
    "Name": "Successful API Response",
    "Arguments": [
      {
        "success": false
      }
    ],
    "Execution Time": 434
  }
]

The API documentation clearly states that...
onSuccess: function(response) {
      // valid response and response.success = true
    },
    onFailure: function(response) {
      // request failed, or valid response but response.success = false
    },

What else could be going on here? Or is this a bug?

Please create a test case using JSFiddle provided in the readme. There's obviously something missing in your particular case which is not represented with the code you've provided.

Same here. And I have to set successTest to fix this:
$.fn.api.settings.successTest = function(response) {
  if(response && response.success) {
    return response.success;
  }
  return false;
};

Does Semantic UI have a default one?

Closing until there's a test case.