Area not detecting Trimesh Static Bodies

Godot version: 3.1
OS/device including version: Windows 10 Home 1803
Issue description:
I'm trying to create stepping for a kinematic controller. I'm using is_on_wall() to detect if the player is being stopped by a collision and the Area node to detect walls taller than the step height.
The Area node does not detect overlap with generated Trimesh Static Bodies for custom environment models. Both the signals and the get_overlapping_bodies() function do not return anything. It works fine with convex and primitive statics. I've searched and haven't seen any issues addressing this. I can't even really find much information on Trimesh Statics.
Steps to reproduce:

Create a MeshInstance and generate a Trimesh Static Body for it
Create an Area Node with a script to accept signals, or call overlap methods
Move the Area Node into the Trimesh Static Body
Weep at the complete lack of activity

-Or-

Download my minimal
Use Arrow keys or WASD to move the Area into different statics to see results

Things I've tried:

Changing the shape of the Area
Making the static trimesh body the parent node
Using _on_Area_body_shape() signals

Minimal reproduction project:
AreaTrimeshBug.zip

This issue should be prioritized. Im having the same issue and its hard to find any good workarounds for me. :(

This issue should be prioritized. I'm having the same issue and its hard to find any good workarounds for me. :(

Are you trying to create stepping for a character? I did find a passable workaround, if you want it. I'll put it here regardless, for anyone else who might need it. I'd prefer using an Area for simplicity but:
I used two raycasts childed to my character's rotation node. One is at the step height (I used 0.3), the other is slightly above the ground (I set it at 0.05). I took my input vector, and converted it into a vector3 that could be used as a cast direction for the raycasts (so they always point in the direction the player is trying to move, not just the way they're facing).
I then check to see if the bottom raycast is colliding, but the top one is not. If so, do a small jump to get above the step height. If you play with the raycast lengths (I kept them at 1), they do not appear to trigger on slopes, and the setup also prevents wall climbing. It may not work for stairs, though, I haven't tried it. I would have just used a collider ramp for stairs.
It's a bit hacky, and if I cared to develop it further, I'd probably just directly set the characters position to the step height, but it works, and may even be more desirable depending on the game.

Code snippet:
# member variables:
var stepcast : RayCast
var minstep : RayCast
const STEP_SPEED = 4

# references in the _ready function:
stepcast = $CharacterAxis/StepHeight
minstep = $CharacterAxis/MinStep

# Stepping (placed in a function called from _physics_process)
	var cast_vector = Vector3(-input_movement_vector.x * stepcast_length, 0, input_movement_vector.y * stepcast_length)
	stepcast.set_cast_to(cast_vector)
	minstep.set_cast_to(cast_vector)
	if is_on_wall() and not stepcast.is_colliding() and minstep.is_colliding():
		vel.y = STEP_SPEED

I am also having no success with getting an Area to detect a Trimesh StaticBody. Using CollisionShapes would be nicer than RayCasts in many instances, so I hope this is fixed soon.

This seems to have been noted and "fixed" in #16392 and #21744, but it clearly is still an issue.
I'm trying to get a camera w/ Area sphere to detect collision with a StaticBody terrain.
Terrain sections are made in code from an ArrayMesh. A Shape is generated from the terrain with mesh.create_trimesh_shape(). That is put into a CollisionShape and connected to a StaticBody.
Collision with my KineticBody character and drawing collision debug lines work fine. I don't get the Area::body_entered signal when the Area collides with the terrain.
It will signal with a StaticBody sphere, or if I change the function to mesh.create_convex_shape(). However that does not provide an accurate collision shape.
Raycasts are a reasonable workaround for now.

This seems to have been noted and "fixed" in #16392 and #21744, but it clearly is still an issue in 3.2 master.

From what I can tell, a method for convex collision detection was implemented in #16392. Looking at space_bullet.cpp around line 720 shows that concave collisions are not yet implemented.

The reproduction project in the original post seems to work fine for me in 3.2.3, all three bodies can detect the cylinder fine.
Tested with both Bullet and GodotPhysics.


Temporary issue with uploading/syncing cloud project?

Hi, tody 18/12 I was trying to upload a public/community project but it looks like the system is 'pending'.
I am on QGIS 3.26.3 and QFieldSync 4.2.0.
It was possible to upload the project but the job is (since a couple of hours) pending.
The QFieldCloud project overview in QGis gives the project a status 'ok' (green dot).
But when I tried downloading the project locally on my mobile device, the device is syncing without ending. Downloading some other public projects isn't working neither.
I assume there is no mistake on my side, so I want to check...

The problem seems to be solved. Thank you.

e.png)


Error While Go Getting

When I run:
go get github.com/lair-framework/drone-nmap
I get:
src/github.com/lair-framework/drone-nmap/main.go:91: h.Os.OsMatch undefined (type nmap.Os has no field or method OsMatch)
src/github.com/lair-framework/drone-nmap/main.go:95: h.Os.OsMatch undefined (type nmap.Os has no field or method OsMatch)

Fixed, thanks for finding this.


Honeywell PYHTCC requests.session() is left open after the supervisor loop is complete

issue was observed in honeywell_integration test when supervisor test was run before basic checkout test

relevant discussion:  https://stackoverflow.com/questions/49253246/how-to-close-requests-session


Added support for series specific border radius on bar chart

New Pull Request
plotOptions.bar.borderRadius now excepts both a number and a number array.
This PR is a combination of a bug fix and a new feature.  By allowing plotOptions.bar.borderRadius to accept both a number and a number[], developers can now apply a border radius to a specific series in their chart.
Fixes #2592
The borderRadius property now behaves as follows:
borderRadius: 5 - when setting the border radius to a number, there is no change in behavior. All series will receive the same border radius value. Unless it's a stacked bar chart. In that case all series would have a border radius of 0 except for the last series in the stacked bar chart.
borderRadius: [5, 10, 5, 3] - when setting the border radius to an array, the border radius value will be applied to each series according to the index of the series. In this example, if there are 4 series, then the border radius would be applied in the order in which it is defined. Series 0 = Radius 5, Series 1 = Radius 10, Series 2 = Radius 5, Series 3 = Radius 3. This is specifically important when dealing with a stacked series bar chart. By default, all series in a stacked series bar chart would be forced to have a radius of 0 except for the last series index which would then have a border radius value set. With this new feature, this will force all series, even a stacked bar series, to have a border radius set.
borderRadius: [5] - when setting the border radius to a array with a single value, then all series will receive the same border radius value. This is specifically important when dealing with a stacked series bar chart. By default, all series in a stacked series bar chart would be forced to have a radius of 0 except for the last series index which would then have a border radius value set. With this new feature, this will force all series, even a stacked bar series, to have a border radius set.
In the case where there are more series than border radius values in the array, the last value in the borderRadius array will be applied to all remaining series.
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings

Looks good!
1 thing we need to check is what happens when the user toggles the series using legend? Does it show any weird behavior there? Merging this.

I see you have updated the TypeScript definitions as well 👍🏻
One place where it will need to be also updated is the ng-apexcharts library.
For future reference, any change that goes to the ApexCharts TypeScript definitions also has to be done at https://github.com/apexcharts/ng-apexcharts/blob/master/projects/ng-apexcharts/src/lib/model/apex-types.ts

I checked the toggling of the legend and the feature works with no issues.

If I have a stacked chart with some dynamic data (e.g.  first data[10,10,2,2,3]  and second data[2,4,**0,0,**2]), the third and fourth column wont have the border radius effect on them because the last item of the column is not present. Is there a way to set it with the array?

`var optionstack = {
series: [{
name: 'Current Sales Value',
data: data.greenBar
},
{
name: 'Shortfall Value',
data: data.greyBar
}],
colors : ['#38AB0F', '#CCC'],
chart: {
type: 'bar',
height: 350,
width:'100%',
stacked: true,
},
noData: {
text: "No data text",
align: "center",
verticalAlign: "middle",
},
responsive: [{
breakpoint: 375,
options: {
legend: {
position: 'bottom',
offsetX: -10,
offsetY: 0
}
}
}],
plotOptions: {
bar: {
horizontal: false,
borderRadius: [5, 5],
barWidth: '60%',
columnWidth:'40%',
borderRadiusOnAllStackedSeries: true
},
},
xaxis: {
categories: data.barCategories
},
yaxis: {
tickAmount: 5,
max: data.yaxisMax
},
dataLabels: {
enabled: false
},
legend: {
position: 'bottom',
horizontalAlign: 'center',
},
fill: {
opacity: 1
},
tooltip: {
enabled: true,
shared: true,
intersect: false,
fixed: {
enabled: false,
position: 'topRight',
offsetX: 0,
offsetY: 0,
},
},
states: {
hover: {
filter: {
type: 'none'
}
}
}
};
					var stackedChart = new ApexCharts(document.querySelector("#stackedChart"), optionstack);
					stackedChart.render();`

i have been trying to set border radius but still this is not working


Added Solution for Cofense Intelligence.

Required items, please complete
Change(s):

Added Cofense Intelligence Solution for certification.

Reason for Change(s):

New product

Version Updated:

Initial Version

Testing Completed:

Yes

Checked that the validations are passing and have addressed any issues that are present:

Yes

Hello @jayeshprajapaticrest please work on the changes requested above

Hello @jayeshprajapaticrest please work on the changes requested above

@v-prasadboke Changes are done.

Ok @jayeshprajapaticrest will give you an update till 7-07

Ok @jayeshprajapaticrest will give you an update till 7-07

OK Understood. Thanks

Hello @jayeshprajapaticrest as per latest guidelines issued, solution should be repackaged with V3 tool
https://github.com/Azure/Azure-Sentinel/blob/master/Tools/Create-Azure-Sentinel-Solution/V3/README.md
you can go through this readme file for the instructuons

Hello @jayeshprajapaticrest please share the release notes as well

Hello @jayeshprajapaticrest please go through this readme file to know more about this
https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/ReleaseNotesGuidance.md

Hello @jayeshprajapaticrest we are waiting for your response

Hello @jayeshprajapaticrest we are waiting for your response
@v-prasadboke
Yes working on it. Getting some validation error after generating solution with V3 tool.

@v-prasadboke
I have added ReleaseNotes.md and Updated PR with the solution package created using V3 tool.
So can you please proceed with the Merging process if everything looks good?

Hello @jayeshprajapaticrest sorry for the inconvenience, but we are still investigating this PR.
You can expect an update till 25 Jul 2023

Hello @jayeshprajapaticrest please update the sample data and custom table of ThreatIntelligenceIndicator.json
As threat_id is missing from these both.
As this solution contains only 2 content which is workbook and Data connector, both of them depends on the query which uses schemas and data from the sample data ingested.
Due to this im unable to test both the content, hence i request you to update the sample data and custom table.

Hello @jayeshprajapaticrest, can you provide any updates for above comments. Thanks, Prasad Boke.

Hello @jayeshprajapaticrest, can you provide any updates for above comments. Thanks, Prasad Boke.

@v-prasadboke "threat_id" is not actual field of any custom table. It gets extracted from "Tags" field using parse in the query automatically. So need to add it in the sample data. "Tags" is already available.
We can connect if you want to need more details on it if required.
Thanks.

Thank you @jayeshprajapaticrest for the updates, will schedule a call for this and CODE QL exceptions for better clarity.
Are you available for 2:30 PM (IST) tomorrow 26 Jul 2023.

Thank you @jayeshprajapaticrest for the updates, will schedule a call for this and CODE QL exceptions for better clarity.
Are you available for 2:30 PM (IST) tomorrow 26 Jul 2023.

Yes. Please share the invite.

Ok sure @jayeshprajapaticrest, I'll schedule a call for 2:30 PM IST next Tuesday i.e 01 Aug 2023.
And Thank you for the updates.

Ok sure @jayeshprajapaticrest, I'll schedule a call for 2:30 PM IST next Tuesday i.e 01 Aug 2023. And Thank you for the updates.

Sure. Please share the invite for the same.

Invite sent @jayeshprajapaticrest. Thank you.

Hello @jayeshprajapaticrest, If possible can you please rename the values for which the code QL validation is failing to something else. That would be very helpful. Thank you.

Other than that only change which is requested, Everything looks good.

Hello @jayeshprajapaticrest, we are waiting for the updates. Thank you.

Hello @jayeshprajapaticrest, we are waiting for the updates. Thank you.

@v-prasadboke
Can we connect to discuss about the Codeql validation error?

@v-prasadboke 12:15 PM tomorrow should works for me.

@v-prasadboke
Can you please share the link to connect at 12:15 PM today?

@v-prasadboke 12:15 PM tomorrow should works for me.

@v-prasadboke Can you please share the link to connect at 12:15 PM today?

Microsoft Teams meeting

Join on your computer, mobile app or room device

Click
 here to join the meeting

Meeting ID:
239 433 783 290
Passcode: 6mVVhw

Download
 Teams |
Join on the web

Or call in (audio only)

[+1<PHONE_NUMBER>,,687710123#](tel:+13238494874,,687710123#)
  United States, Los Angeles

Phone Conference ID: 687 710 123#

Find
 a local number |
Reset PIN
[Learn More](https://aka.ms/JoinTeamsMeeting)
 |
Meeting options

Hello @jayeshprajapaticrest, as discussed in the call you can Change the values for which the Code QL check is failing.

@v-prasadboke
As discussed in call I updated the constant name as well as tried by giving the value direct from the environment variable. But still I am getting the same CodeQL error.
I go through the more detail on the error and as per that we need to encrypt and decrypt the constant password values for the usage.

Hello @jayeshprajapaticrest, Thanks for the updates. As mentioned above, please go with it as needed.

@v-prasadboke Done and also Code-QL error gets resolved.

Can you please proceed with this and approve and merge as early as possible. Because it already took so much time in single issue?

Thank you @jayeshprajapaticrest for committing the change. Will have a look in it and update you about the same.

Thank you @jayeshprajapaticrest for committing the change. Will have a look in it and update you about the same.

@v-prasadboke Thanks

Hello @jayeshprajapaticrest, I've committed some minimal changes. Please take a look and confirm once.

Hello @jayeshprajapaticrest, I've committed some minimal changes. Please take a look and confirm once.
@v-prasadboke
Thanks for the update. Will check and let you know.

Ok sure, Thank you @jayeshprajapaticrest.

Hello @jayeshprajapaticrest, I've committed some minimal changes. Please take a look and confirm once.

@v-prasadboke Changes looks good. Can you please proceed further for merging?


I have similar issues as one that was apparently fixed a few days ago

I have cloned the NEWEST depo (today at 2PM EST) locally via git,
I have ran the deploy script, without making any changes to any file whatsoever, and using EASTUS as the target region, but I get the same error as some others had gotten, and apparently this was fixed.
I am also using strong passwords for when prompted to enter them.
We are using development boxes with latest version of VS2015 UP2, Azure PowerShell updated today JUN 27.
This must be something very obvious, but we are still not able to deploy this. Although we were able to deploy a few weeks ago, back in May 5th
Any help is appreciated
Thanks.
New-AzureRmResourceGroupDeployment : 3:00:10 PM - Resource Microsoft.DataFactory/datafactories/datasets 'mydriving-dfwso2h72e6lsn4/
"message": "Linked service AzureSqlLinkedService not found.",
"code": "LinkedServiceNotFound"
}'
At D:\MyDriving-master June 26 2016\scripts\PowerShell\deploy.ps1:147 char:16

... ployment2 = New-AzureRmResourceGroupDeployment -Name "$DeploymentName ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [New-AzureRmResourceGroupDeployment], Exception
FullyQualifiedErrorId : Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.NewAzureResourceGroupDeploymentCmdlet

could you please paste whole output?

hello, thanks......attaching all output to this reply
deploy output june 27 2016.txt

I confronted same issue!

I see it, I will try to simulate it and fix it
problem is probably with missing dependency in ARM json script
AzureSqlLinkedService is required earlier than deployment of this part is finished

Thank you David, much appreciated....

Could you pls help me with testing? I'm not able to simulate it but try to add this
,
			"[resourceId('Microsoft.DataFactory/datafactories/linkedServices', variables('dataFactoryName'), variables('sqlAnalyticsLinkedServiceName'))]"

at the end of line 1492
it's in part /* Dataset: FinalTempDataSet-Sql */ of file scripts\ARM\scenario_complete.json
and will look like this
"dependsOn": [
            "[resourceId('Microsoft.DataFactory/datafactories', variables('dataFactoryName'))]",
            "[resourceId('Microsoft.DataFactory/datafactories/linkedServices', variables('dataFactoryName'), variables('storageAsaLinkedServiceName'))]",
			"[resourceId('Microsoft.DataFactory/datafactories/linkedServices', variables('dataFactoryName'), variables('sqlAnalyticsLinkedServiceName'))]"
          ]

Thanks Dave.
OK, I have doen the above modification, added the one line to the scripts\ARM\scenario_complete.json file.
I now get the following error....
please take a look, it fails much earlier
Best regards,
ARTURO
Mydriving error june 28 2016.txt

probably some error during editing, I will try it to deploy and let you know

fixed, tested - try it please from repo
deployment_ok.txt

I used Powershell ISE to edit the file, all I did was to add the one line...hopefully I did not add any extra characters...;-)
	}
      },
      "dependsOn": [
        "[resourceId('Microsoft.DataFactory/datafactories', variables('dataFactoryName'))]",
        "[resourceId('Microsoft.DataFactory/datafactories/linkedServices', variables('dataFactoryName'), variables('storageAsaLinkedServiceName'))]"
        "[resourceId('Microsoft.DataFactory/datafactories/linkedServices', variables('dataFactoryName'), variables('sqlAnalyticsLinkedServiceName'))]"
      ]
    },

revert your changes and get last version from git, pls

OK, David, let me clone the repo again, and will let you know shortly.
So, I will clone the repo of which this dialog is part of...
Thanks and regards.

or try to edit as you can see here
https://github.com/Azure-Samples/MyDriving/commit/3564499b4dca826b7ad95af94f5e5036e8df964a
or get only this file from web here:
https://github.com/Azure-Samples/MyDriving/blob/master/scripts/ARM/scenario_complete.json

I cloned the entire repo, and it works very well now, thank you so much!!!
Best regards,
AQ

you are welcome


remove extra variable

near the top of main.ino, there's an unused variable declared called apogeeReached. This can cause quite a bit of confusion because there's another variable with the same name used later on that is unrelated. This unused variable should be deleted. Also, the //variables comment can be deleted since there won't be any global variables defined at that location.

Hello @JonathanSafer , I'd love to take this up. Kindly assign it to me.

Hi @Mannuel25, we are limiting contributions to this repository to HLA members only at this time

Okay, thanks.


[Checkout UI] Surface a Customer access token for new Buyer Identity directive (B2B)

Please list the related package(s)
checkout-ui-extensions
If this related to specific APIs or components, please list them here
Provide a compatible customer access token to run buyer specific storefront api queries - https://shopify.dev/docs/custom-storefronts/headless/b2b#step-3-contextualize-storefront-api-requests
Is your feature request related to a problem? Please describe.
I'd like to retrieve buyer contextualized product data using the Storefront api in checkout.
Describe the changes you are looking for
Surface a useCustomerAccessToken() to include in Storefront api calls within checkout extensions
Describe alternatives you’ve considered
Maybe I'm doing something wrong but I tried https://shopify.dev/docs/api/checkout-ui-extensions/unstable/apis/session-token and it didn't seem to work.

I'm facing a similar issue in where I want to grab more customer data from the storefront api but don't seem to have a customer access token available in checkout ui extension. Did you find a way to get it? (Other than building a backend app.)


update journal stream for new API, event names

This updates the transactor client to use the new event names and JournalStreamRequest definition from the streaming rpc changes on the transactor.
Works for me in a simple test at the repl; when you call journal_stream, you immediately get the contents of the current block, and on importing a new getty image you get an insertCanonicalEvent and an updateChainEvent

:+1:

great!


Fluid pipes wont work

i have 2 fluid pipes trying to transport oil and it wont send the the oil to the reciever. dont know if i am supposed to link the pipes somehow but please help

you are supposed to paint the pipes the same color... using BuildCraft's brush thingy.

just tested in latest version... fluid pipes work ok... just make sure to:

paint sender and receiver the same color (using buildcraft's paintbrush)
both sender and receiver are in loaded chunks (they won't chunk load themselves)


Start now takes group ordering into account

The way I did this is I have start_priority_containers look at a section called [groups] in the vent.cfg for an option called start_order, which lists off the groups in the order in which the user wants them to start, comma separated (image of this below). Do we want to start all containers of a certain group that have a priority over all the others, or just those that have a priority? Right now, those that don't have a priority just get started less in any order in start_remaining_containers.

Codecov Report

Merging #753 into master will increase coverage by 0.01%.
The diff coverage is 53.84%.

@@            Coverage Diff             @@
##           master     #753      +/-   ##
==========================================
+ Coverage   81.24%   81.26%   +0.01%
==========================================
  Files          50       50
  Lines        4463     4472       +9
==========================================
+ Hits         3626     3634       +8
- Misses        837      838       +1

Impacted Files
Coverage Δ

vent/api/plugin_helpers.py
73.36% <53.84%> (-0.14%)
:arrow_down:

vent/api/plugins.py
92.28% <0%> (+0.24%)
:arrow_up:

vent/menus/tools.py
80.46% <0%> (+0.46%)
:arrow_up:

Continue to review full report at Codecov.

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


How do I delete/disable dev spaces?

I would like to also delete any azure resources it created.

Option 1: az aks remove-dev-spaces -g <aks resource group> -n <aks resource name>
Option 2: go to the portal and delete the dev spaces resource.


Creation of World Enterprise Handbook

Objective:
To create a comprehensive World Enterprise Handbook outlining roles, responsibilities, and project descriptions for key team members, defining the mission, vision, and strategies for our enterprise.
Team Assignments:

Aleem – Agile Manager:
Aleem will oversee Agile methodologies within the organization. He will take responsibility for Android operations and lead the DROID Ops project, focusing on innovation and agile development practices.

Reza – Business Development Manager:
Reza will handle business development strategies and the growth of our enterprise. He will lead the ORBITALS project, dedicated to expanding market reach and strengthening partnerships.

Ayesha – Product Manager:
Ayesha will manage product development and strategy. She will be responsible for the RICE Matrix project, ensuring the development and success of our product roadmap, balancing priority and impact.

Project Descriptions:
DROID Ops (Led by Aleem): Focused on developing Android operations, implementing agile frameworks, and ensuring efficient deployment processes.
ORBITALS (Led by Reza): Strategic initiative aimed at business expansion, building global connections, and ensuring continuous growth in target markets.
RICE Matrix (Led by Ayesha): A project management approach for product development, ensuring high-impact decisions by focusing on Reach, Impact, Confidence, and Effort.
Handbook Content:
Mission: To lead in innovation, product development, and global market expansion through a collaborative approach.
Vision: To establish World Enterprise as a global leader in technology, product excellence, and market influence.
Additional Sections:
Agile Management Practices
Business Development Strategies
Product Management and Roadmap
Team Collaboration Guidelines
Future Project Visions
Next Steps:
Create a detailed handbook including the roles, projects, mission, vision, and all relevant strategies. Ensure each section is comprehensive, with clear guidelines and procedures for success.
This handbook will serve as a foundational guide for our enterprise, ensuring alignment and focus across all departments.
has context menu

Today's SMARTIN Goal:
I will focus on creating the initial draft of the World Enterprise Handbook, outlining the team roles (Aleem, Reza, Ayesha) and their respective projects (DROID Ops, ORBITALS, RICE Matrix). I'll dedicate 8 hours to collaborating with Reza and Ayesha to gather their input and structure the sections for Team Roles, Mission, and Vision. By the end of the day, I aim to complete 60% of the draft.


lodash-es not found on npm v3 due to nested dependency access

Error: ENOENT, no such file or directory '/app/node_modules/ember-lodash/node_modules/lodash-es'

This occurs because npm3 has a flat structure; there are no more nested node_modules directories. Now lodash-es lives on the top-level node_modules along with the main dependencies. As a result, we need a new way to load in the dependency for npm v3 users.

As a workaround, I was able to npm install at the app level and get this error, cd node_modules/ember-lodash, then npm install at that level, jump back up to the app level and re-run npm install without the error any more.
@mike-north I'm not a JavaScript or NPM expert (in fact, I just took your Frontend Masters Ember 2 course online last week), but could I help out in some way with this issue?

...and for those that are regretting upgrading to npm v3, you can install an older version by sudo npm install -g<EMAIL_ADDRESS> This Github issue wasn't the only problem I was finding in my Ember app as a result of "innocently" upgrading to npm v3.

@BigGillyStyle thanks you just saved me a lot of fumbling about.

Yeah this workaround worked for me (and was preferable to downgrading npm). Thanks @BigGillyStyle

Closed via #4

My workaround from @BigGillyStyle for deploying to heroku:
//package.json
{
  "scripts": {
    //...
    "postinstall": "cd node_modules/ember-lodash && npm install"
  }
}

For some reason, PR #7 doesn't fix this situation for me. If I console log the path for the lodash-es dependency in the index.js, I get the appropriate path in my node_modules, but I'm still seeing the error that the dependency is not found.
My situation is the result of broccoli-sane-watcher failing to find the paths when booting an Ember-CLI 1.13.13 app.

Yeah, this doesn't seem to have solved the issue.

Running into this issue on a fresh ember 2.2 app also.

Seeing this one as well.

I tried the above solution from @BigGillyStyle, however it didn't work for me (locally). the only think that worked for me was to downgrade my npm version to 2.x

Close for lack of activity


Validation Rule will not allow combining "numeric" with "min"

Laravel Version: 5.4.23
PHP Version: 7.1.5
Database Driver & Version:
SQLite

Description:
When setting up validation rules, using 'field' => 'numeric|min:5' doesn't seem to work. It will validate that's it's numeric, but not go on to validate that the number is at least 5 digits long.
Steps To Reproduce:
Won't validate length of 5
public functiion rules()
{
    return [
        'zipcode' => 'numeric|min:5'
    ];
}

WILL validate length of 5
public functiion rules()
{
    return [
        'zipcode' => 'required|min:5'
    ];
}

It will validate that the numerical value is greater than 5, you can try min:10000

This is not a bug. Open an issue in the laravel/internals repo

Yes when combined with numeric it will validate that the field is a number greater than 5. That's the expected behaviour.

@sede2 @themsaid Guys...read the question before closing the issue, or you're not doing any service to the community. I clearly said that's what it's NOT DOING.

The behaviour of min/size/max rules depends on the type. numeric|min:5 will check for a minimum numeric value of 5, not a minimum of 5 digits. If you need the latter, you should specify a range with between instead.

@chrisblackwell
validator([
    'zipcode' => '3',
], [
    'zipcode' => 'numeric|min:5'
]);

Validates fails with the following:
array:1 [▼
  0 => "The zipcode must be at least 5."
]

On the other hand this passes:
validator([
    'zipcode' => 5,
], [
    'zipcode' => 'numeric|min:5'
]);

So that's the expected behaviour.

It will validate that's it's numeric, but not go on to validate that the number is at least 5 digits long.

That's the behaviour you stated you expect in the issue description, that's why the issue was closed, but having it closed doesn't mean the discussion is over :)

Let's say we are trying to pass the number 123
Right now, this will return valid for both numberic and min:5
Should it not return valid for numeric and invalid for min:5?

Why not?

Because then people will confuse size with min. I think min should correspond to the length of the value, and size as the actual size. If we keep min as numeric value size, then we actually will never have a way to verify a number of digits.
For example; we could use digits_between to verify that it's 5 - 12 or something, but never just minimum 5 digits.

That doesn't make any sense. size is for specifying a value that must be matched (i.e. not less than, nor greater than) and it totally makes sense that it behaves in the same way as max and min in the way types are handled.
Also, you can validate the number of digits. Use between. In your case, between:10000,99999. Admittedly that's not perfect for your exact case, but it does what you're asking for and you could always implement your own validation rule if it's not acceptable.

I don't see why "min" would relate to minimum number of digits. In any scale where you have to pick of range of values (imagine a slider), the lowest allowed number is always called the "min". It is a common convention

Looks like the confusion lies between what "min" is.
According to the Laravel docs, "min" is referring to the value of the field (field is greater than X). However, in the OP's case he wants "min" to be the length of the field (field of XXXXX is valid, XXXX is not). He doesn't want a range, as suggested, just a single "min" length.
Looks like Laravel doesn't have that option (yet)

I know OP doesn't want a range, I only suggested it because it's the closest possible solution at the moment and changing the behaviour of min isn't an option. I think a PR or issue to introduce digits_min and digits_max would be a good idea (I searched the repo; seems it hasn't been suggested before).


Disabling _focus styling

Is there a way to disable the borderColor change when the component is focused?

@ASalcedoC :
.no-focus-outline:focus {
  outline:none;
}

<CurrencyInput className="no-focus-outline"/>


[SL-GRID] Very long grid cell text doesn't render properly

Provide a general summary of the issue here
If a grid cell has a very long text, the row is not high enough to show all text. Please see the example below.

🤔 Expected Behavior?
The cell should show all text
😯 Current Behavior

💁 Possible Solution
No response
🖥 Steps to Reproduce
clone the latest version of the example project
git clone https://github.com/fransdeboer/grid-poc.git
install dependencies
npm i
run the project
npm run dev
open a browser at http://localhost:5173/
filter the Profession column to check the option "This is a really long description of a profession"
only one row should be displayed, but the row is not high enough to show all text

What browsers are you seeing the problem on? (only for bugs in code)
Chrome
If other, please specify.
No response
What operating system are you using?
WSL
👤 Your name
Frans de Boer
🧢 Your product/team
Magister
🎨 Your Theme(s)
Magister

Presumably the issue is that the calculation of the height of the table is based on the default row height, either by looking at the first # rows, or just the rows that are in view.
When the filtering is then applied it uses incorrect "children sizes" to calculate the required height of the table.
Adding this.#virtualizer?._layout?._metricsCache?.clear(); and/or this.#virtualizer?._measureChildren();
doesn't fix the problem.
In a certain combination:

The rows are placed too far from each other (transform: translate(0px, 200px);), but only when the height of the page (or container) is way bigger than the newly filtered rows. In a smaller window the calculation seems to be correct. But when there is only one row left the height is incorrect.
In the case of incorrect placement of the rows and the incorrect height when there's only one row it uses row heights of 100px.
It feels like the 100px is some sort of default; when it can get or read any values it just calculates with that value...


Update helm chart to v0.26.0

Fixes https://github.com/kubernetes-sigs/descheduler/issues/1020

Ah
Failed to pull image "registry.k8s.io/descheduler/descheduler:v0.26.0": rpc error: code = NotFound desc = failed to pull and unpack image "registry.k8s.io/descheduler/descheduler:v0.26.0": failed to resolve reference "registry.k8s.io/descheduler/descheduler:v0.26.0": registry.k8s.io/descheduler/descheduler:v0.26.0: not found

So it looks like the updated helm chart version attempts to get installed. I'm thinking maybe this is the behavior now after https://github.com/kubernetes-sigs/descheduler/pull/911? @knelasevero any ideas for that?
Some ways around this for releases:

roll back/change #911
Build/tag the v0.26.0 image before merging the helm chart change.
manually trigger the v0.26.0 image build (if possible? this could be the right way to do things going forward)

We use the helm chart change as the final "no-op" merge to trigger a build with the proper git tag (https://github.com/kubernetes-sigs/descheduler/blob/master/docs/release-guide.md#flowchart). But this step could be replaced with another non functional change such as readme updates. The important part is that functional code is merged before tagging the release in Git, followed by another GCB build to pull in the new git tag.
If there's no easy change to #911 we could make now, I'll just open a no-op docs change or something to trigger the build. Or manually trigger it

Option 2 doesn't seem so bad.
Another option would be to add a step to the GitHub Action to query the latest image release and use that as the AppVersion. In other words, always use the latest published image but it does seem add a bit of confusion as it would not use the AppVersion defined in the Chart.

prefer option 2 (Build/tag the v0.26.0 image before merging the helm chart change)

prefer option 2 (Build/tag the v0.26.0 image before merging the helm chart change)

If there's no easy change to #911 we could make now

:heavy_plus_sign:

Another option would be to add a step to the GitHub Action to query the latest image release and use that as the AppVersion. In other words, always use the latest published image but it does seem add a bit of confusion as it would not use the AppVersion defined in the Chart.

This is indeed an option, and not that hard to make I guess, but I agree that it is confusing. Probably having a doc change to be the no op step and then the helm chart step coming next is the best friction-less option going forward, and building it locally and pushing is ok to unblock this PR here?

We actually have some other changes under the v0.26.0 tag (like https://github.com/kubernetes-sigs/descheduler/pull/995), so for this release that should be able to promote to the public image.
For the next release we'll need to think about this. It also might be good to add a "release-mode" blocker so that PRs don't merge automatically or accidentally while we're doing the release process.

/retest

Successful image tag, I'll work on updating the process for next release to address this.

/approve


Windows docker images

Existing implementation is available in https://github.com/alcionai/corso/tree/docker-windows . I'm unassigning myself from it for now until we decide to do it.


This repo is too big to clone...

Hi, developer. Such a good job to combine the ideas behind Exactly Gaussian Variation Inference and GPMP2! While I try to git clone this repo, I found it is too big to clone successfully. So I wander could you split this repo into several parts? For example, the modified version of GPMP2 in this repo, you could make a soft line. I will appreciate it if you can give me any other advice to clone this repo! @ChenZhenY @hzyu17.

Hi, developer. Such a good job to combine the ideas behind Exactly Gaussian Variation Inference and GPMP2! While I try to git clone this repo, I found it is too big to clone successfully. So I wander could you split this repo into several parts? For example, the modified version of GPMP2 in this repo, you could make a soft line. I will appreciate it if you can give me any other advice to clone this repo! @ChenZhenY @hzyu17.

Hi, thanks for your attention. I made the gvi algorithm a standalone submodule here: https://github.com/hzyu17/GaussianVI and cleaned some data files. I tried it on my PC, and it was successfully cloned. Please try to clone the master branch and let us know if the issue still remains. Please give us a star if you find this repo helpful, appreciate it!

Hi, developer. Such a good job to combine the ideas behind Exactly Gaussian Variation Inference and GPMP2! While I try to git clone this repo, I found it is too big to clone successfully. So I wander could you split this repo into several parts? For example, the modified version of GPMP2 in this repo, you could make a soft line. I will appreciate it if you can give me any other advice to clone this repo! @ChenZhenY @hzyu17.

And we did not modify gpmp2, we just included a already-built gpmp2 library inside ours so that we use the fixed version and users need not to build gtsam and gpmp2 from scratch.

@hzyu17 , Thank you for replying! I have successfully git clone the repo: GaussianVI. I believe it will be very useful for me to understand Gaussian Variational Inference. :)
And I understand the reason for including GTSAM and GPMP2 in this repo now. : )

And we did not modify gpmp2, we just included a already-built gpmp2 library inside ours so that we use the fixed version and users need not to build gtsam and gpmp2 from scratch.

So, the difference between GaussianVI and VIMP is that GuassianVI is the implementation of the algorithm in the RA-L paper, and VIMP is the implementation of the algorithm  in arxiv paper? I will close this issue, but I still looking for your reply. : ) 👍


Order by aggregation not present in selection

Supporting queries where order by is on aggregation, but that aggregation is not defined in the selection:
select subject from transcript group by subject order by count(*), sum(score) desc

Can we add some query for integration tests?

Can we add some query for integration tests?

Added some tests in CalciteSQlCompilertest. Our integration tests are still calling pql endpoint, so these cannot be added there

@npawar , Can we please add end-to-end query execution tests? I don't mean integration tests but tests in one of the files that extend BaseSingleValueQueriesTest and BaseMultiValueQueriesTest. All e2e query exec tests that test out the entire path from broker are there.

@npawar , Can we please add end-to-end query execution tests? I don't mean integration tests but tests in one of the files that extend BaseSingleValueQueriesTest and BaseMultiValueQueriesTest. All e2e query exec tests that test out the entire path from broker are there.

Added @siddharthteotia

Are we planning to support this for SQL only? In that case, we should rewrite the query (add all the order-by expressions to the selection list) for PinotQuery instead of in the converter and only have the rewrite in BrokerRequest. This will cause inconsistency between PinotQuery and BrokerRequest, which will make BrokerRequest deprecation harder.

closed this PR since @Jackie-Jiang fixed this in https://github.com/apache/incubator-pinot/pull/5637 and the tests have been moved to that PR


[Bug]: "Not Authenticated" error when uploading file in saas mode

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Describe the bug and reproduction steps
When uploading a file I see a “not authenticated” error. I uploaded a file using the “arrow-pointing-to-cloud” button in the workspace:

This is in the All Hands online version.
OpenHands Installation
Docker command in README
OpenHands Version
No response
Operating System
None
Logs, Errors, Screenshots, and Additional Context
No response

Wondering if this issue is resolved with all the auth fixes.

Not running into this issue anymore. Closing.


no servers inside upstream in /etc/nginx/conf.d/default.conf when specifying an hostname

I use docker-gen through nginx-proxy and got this https://github.com/nginx-proxy/nginx-proxy/issues/1548 which seems to be linked to docker-gen. It seems it can't find the ip of the other container with netiher /proc/self/cgroup" nor "/proc/self/mountinfo" (It seems I miss understood how the IP of the others containers was found). FYI I use docker swarm on arch, Here is my docker info
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.5.1-tp-docker)

Server:
 Containers: 10
  Running: 5
  Paused: 0
  Stopped: 5
 Images: 31
 Server Version: 20.10.5
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: active
  NodeID: REDACTED
  Is Manager: true
  ClusterID: REDACTED
  Managers: 1
  Nodes: 1
  Default Address Pool: <IP_ADDRESS>/8
  SubnetSize: 24
  Data Path Port: 4789
  Orchestration:
   Task History Retention Limit: 5
  Raft:
   Snapshot Interval: 10000
   Number of Old Snapshots to Retain: 0
   Heartbeat Tick: 1
   Election Tick: 10
  Dispatcher:
   Heartbeat Period: 5 seconds
  CA Configuration:
   Expiry Duration: 3 months
   Force Rotate: 0
  Autolock Managers: false
  Root Rotation In Progress: false
  Node Address: REDACTED
  Manager Addresses:
   REDACTED
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 05f951a3781f4f2c1911b05e61c160e9c30eaa8e.m
 runc version: 12644e614e25b05da6fd08a38ffa0cfe1903fdec
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
  cgroupns
 Kernel Version: 5.11.11-arch1-1
 Operating System: Arch Linux
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 15.59GiB
 Name: REDACTED
 ID: XB5C:65VO:KHNJ:DLXF:NGS2:LDHI:HX34:EOJW:PWSZ:IURK:UKSW:WFCJ
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false

WARNING: Support for cgroup v2 is experimental

Ok my problems was the specified hostname like said in https://github.com/jwilder/docker-gen/pull/336#issuecomment-813618470

I experience the same issue. No upstream servers. I use the nginx.tmpl from nginx-proxy. Like suggested by the docker hub page.
I tried to debug it and added some lines to the template at the top:
{{ $CurrentContainer := where $ "ID" .Docker.CurrentContainerID | first }}
{{ $CurrentContainer }}
{{ where $ "ID" .Docker.CurrentContainerID }}

Line 1 is in there by default and is later used to compare if a potential backend container is in the same network as the current container. Line 2 and 3 I added and it looks like they are empty:
<no value>
[]

I'm not good at go templates but I see there is a RuntimeContainer struct with Networks in the README (templateing). But I cannot figure out how to access it to fix the template. .RuntimeContainer.Networks did not work.

@Syphdias could you post the result of docker inspect youdockergencontainer ?

Sure
❯ docker-compose exec revproxy-gen /usr/local/bin/docker-gen --version # for good measure
0.7.5
❯ docker inspect revproxy-gen
[
    {
        "Id": "d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e",
        "Created": "2021-04-10T15:13:25.659568865Z",
        "Path": "/usr/local/bin/docker-gen",
        "Args": [
            "-notify-sighup",
            "revproxy",
            "-watch",
            "-only-exposed",
            "/etc/docker-gen/templates/nginx.tmpl",
            "/etc/nginx/conf.d/default.conf"
        ],
        "State": {
            "Status": "running",
            "Running": true,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 221692,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2021-04-10T20:11:19.517464833Z",
            "FinishedAt": "2021-04-10T20:11:18.709340623Z"
        },
        "Image": "sha256:a467dff5e74dfc91427f4b0403fb5543584a5fb4e429d34d2e94b2ea337a8215",
        "ResolvConfPath": "/var/lib/docker/containers/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e/resolv.conf",
        "HostnamePath": "/var/lib/docker/containers/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e/hostname",
        "HostsPath": "/var/lib/docker/containers/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e/hosts",
        "LogPath": "/var/lib/docker/containers/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e-json.log",
        "Name": "/revproxy-gen",
        "RestartCount": 0,
        "Driver": "overlay2",
        "Platform": "linux",
        "MountLabel": "",
        "ProcessLabel": "",
        "AppArmorProfile": "docker-default",
        "ExecIDs": null,
        "HostConfig": {
            "Binds": [
                "/var/run/docker.sock:/tmp/docker.sock:rw",
                "/home/syphdias/docker/revproxy/nginx.tmpl:/etc/docker-gen/templates/nginx.tmpl:rw"
            ],
            "ContainerIDFile": "",
            "LogConfig": {
                "Type": "json-file",
                "Config": {}
            },
            "NetworkMode": "revproxy_backend",
            "PortBindings": {},
            "RestartPolicy": {
                "Name": "unless-stopped",
                "MaximumRetryCount": 0
            },
            "AutoRemove": false,
            "VolumeDriver": "",
            "VolumesFrom": [
                "09f7256e82f3f08d2efb8b0135a0aef213c47c3b111d09358f8735f0cc0c321f:rw"
            ],
            "CapAdd": null,
            "CapDrop": null,
            "CgroupnsMode": "host",
            "Dns": null,
            "DnsOptions": null,
            "DnsSearch": null,
            "ExtraHosts": null,
            "GroupAdd": null,
            "IpcMode": "private",
            "Cgroup": "",
            "Links": null,
            "OomScoreAdj": 0,
            "PidMode": "",
            "Privileged": false,
            "PublishAllPorts": false,
            "ReadonlyRootfs": false,
            "SecurityOpt": null,
            "UTSMode": "",
            "UsernsMode": "",
            "ShmSize": 67108864,
            "Runtime": "runc",
            "ConsoleSize": [
                0,
                0
            ],
            "Isolation": "",
            "CpuShares": 0,
            "Memory": 0,
            "NanoCpus": 0,
            "CgroupParent": "",
            "BlkioWeight": 0,
            "BlkioWeightDevice": null,
            "BlkioDeviceReadBps": null,
            "BlkioDeviceWriteBps": null,
            "BlkioDeviceReadIOps": null,
            "BlkioDeviceWriteIOps": null,
            "CpuPeriod": 0,
            "CpuQuota": 0,
            "CpuRealtimePeriod": 0,
            "CpuRealtimeRuntime": 0,
            "CpusetCpus": "",
            "CpusetMems": "",
            "Devices": null,
            "DeviceCgroupRules": null,
            "DeviceRequests": null,
            "KernelMemory": 0,
            "KernelMemoryTCP": 0,
            "MemoryReservation": 0,
            "MemorySwap": 0,
            "MemorySwappiness": null,
            "OomKillDisable": false,
            "PidsLimit": null,
            "Ulimits": null,
            "CpuCount": 0,
            "CpuPercent": 0,
            "IOMaximumIOps": 0,
            "IOMaximumBandwidth": 0,
            "MaskedPaths": [
                "/proc/asound",
                "/proc/acpi",
                "/proc/kcore",
                "/proc/keys",
                "/proc/latency_stats",
                "/proc/timer_list",
                "/proc/timer_stats",
                "/proc/sched_debug",
                "/proc/scsi",
                "/sys/firmware"
            ],
            "ReadonlyPaths": [
                "/proc/bus",
                "/proc/fs",
                "/proc/irq",
                "/proc/sys",
                "/proc/sysrq-trigger"
            ]
        },
        "GraphDriver": {
            "Data": {
                "LowerDir": "/var/lib/docker/overlay2/cd31ae31ae1aede18ad8c98c5f46703a9b5b41f1ddbb58477e0867c9a485bc6a-init/diff:/var/lib/docker/overlay2/4e3589f7badb112db34b5e938ee3219693bca0aa037b4eea3aee9d3425981260/diff:/var/lib/docker/overlay2/7148944f948af3a2193fcdcfe9255032a505e62bbf7501c91db8925df37f5e2b/diff:/var/lib/docker/overlay2/a354b31fa8aad270d396da5227bc5b2f1a1e62c0db59a8ad845fd4e192ced0b1/diff",
                "MergedDir": "/var/lib/docker/overlay2/cd31ae31ae1aede18ad8c98c5f46703a9b5b41f1ddbb58477e0867c9a485bc6a/merged",
                "UpperDir": "/var/lib/docker/overlay2/cd31ae31ae1aede18ad8c98c5f46703a9b5b41f1ddbb58477e0867c9a485bc6a/diff",
                "WorkDir": "/var/lib/docker/overlay2/cd31ae31ae1aede18ad8c98c5f46703a9b5b41f1ddbb58477e0867c9a485bc6a/work"
            },
            "Name": "overlay2"
        },
        "Mounts": [
            {
                "Type": "volume",
                "Name": "revproxy_nginx-conf",
                "Source": "/var/lib/docker/volumes/revproxy_nginx-conf/_data",
                "Destination": "/etc/nginx/conf.d",
                "Driver": "local",
                "Mode": "",
                "RW": true,
                "Propagation": ""
            },
            {
                "Type": "bind",
                "Source": "/var/run/docker.sock",
                "Destination": "/tmp/docker.sock",
                "Mode": "rw",
                "RW": true,
                "Propagation": "rprivate"
            },
            {
                "Type": "bind",
                "Source": "/home/syphdias/docker/revproxy/nginx.tmpl",
                "Destination": "/etc/docker-gen/templates/nginx.tmpl",
                "Mode": "rw",
                "RW": true,
                "Propagation": "rprivate"
            },
            {
                "Type": "bind",
                "Source": "/home/syphdias/docker-data/certs/letsencrypt/live/redacted.com/fullchain.pem",
                "Destination": "/etc/nginx/certs/redacted.com.crt",
                "Mode": "",
                "RW": false,
                "Propagation": "rprivate"
            },
            {
                "Type": "bind",
                "Source": "/home/syphdias/docker-data/certs/letsencrypt/live/redacted.com/privkey.pem",
                "Destination": "/etc/nginx/certs/redacted.com.key",
                "Mode": "",
                "RW": false,
                "Propagation": "rprivate"
            }
        ],
        "Config": {
            "Hostname": "d8411145f6d7",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "SSL_POLICY=Mozilla-Modern",
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "VERSION=0.7.5",
                "DOCKER_HOST=unix:///tmp/docker.sock"
            ],
            "Cmd": [
                "-notify-sighup",
                "revproxy",
                "-watch",
                "-only-exposed",
                "/etc/docker-gen/templates/nginx.tmpl",
                "/etc/nginx/conf.d/default.conf"
            ],
            "Image": "jwilder/docker-gen:0.7.5",
            "Volumes": {
                "/etc/docker-gen/templates/nginx.tmpl": {},
                "/tmp/docker.sock": {}
            },
            "WorkingDir": "",
            "Entrypoint": [
                "/usr/local/bin/docker-gen"
            ],
            "OnBuild": null,
            "Labels": {
                "com.docker.compose.config-hash": "6c7e681cd63280d323b72baa96aa6215cab8beb88473d7834d50ee9340854ff5",
                "com.docker.compose.container-number": "1",
                "com.docker.compose.oneoff": "False",
                "com.docker.compose.project": "revproxy",
                "com.docker.compose.project.config_files": "docker-compose.yml",
                "com.docker.compose.project.working_dir": "/home/syphdias/docker/revproxy",
                "com.docker.compose.service": "revproxy-gen",
                "com.docker.compose.version": "1.28.6",
                "maintainer": "Jason Wilder<EMAIL_ADDRESS>            }
        },
        "NetworkSettings": {
            "Bridge": "",
            "SandboxID": "69c1087908801795f67f0a2f862d6a70a7f214f1d1d254c603df914d9626c081",
            "HairpinMode": false,
            "LinkLocalIPv6Address": "",
            "LinkLocalIPv6PrefixLen": 0,
            "Ports": {},
            "SandboxKey": "/var/run/docker/netns/69c108790880",
            "SecondaryIPAddresses": null,
            "SecondaryIPv6Addresses": null,
            "EndpointID": "",
            "Gateway": "",
            "GlobalIPv6Address": "",
            "GlobalIPv6PrefixLen": 0,
            "IPAddress": "",
            "IPPrefixLen": 0,
            "IPv6Gateway": "",
            "MacAddress": "",
            "Networks": {
                "revproxy_backend": {
                    "IPAMConfig": null,
                    "Links": null,
                    "Aliases": [
                        "revproxy-gen",
                        "d8411145f6d7"
                    ],
                    "NetworkID": "c70404d73a369d78551310a1d3414c6a59b3c8f714653441bac558709e1716f8",
                    "EndpointID": "ea7b1ccf1abe3b0631612f989aa312304a4830bc7196ef675d0dcf4197277b7b",
                    "Gateway": "<IP_ADDRESS>",
                    "IPAddress": "<IP_ADDRESS>",
                    "IPPrefixLen": 16,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "02:42:ac:12:00:09",
                    "DriverOpts": null
                }
            }
        }
    }
]

@Syphdias thanks, could you also post results of
 docker exec revproxy-gen cat /proc/1/cpuset
 docker exec revproxy-gen cat /proc/self/cgroup
 docker exec revproxy-gen cat /proc/self/mountinfo

Will check as soon as I am home. I guess you are suspecting not enough privileges or capabilities?

The last two files are currently used to search for the container ID, the first one will be added by #336. I'm curious to see if your container ID is actually inside one of those files, and if not why / how should we update the GetCurrentContainerID() function to work in this case.

❯ docker exec revproxy-gen cat /proc/1/cpuset
/docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e
❯ docker exec revproxy-gen cat /proc/self/cgroup
12:rdma:/
11:cpuset:/docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e
10:blkio:/docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e
9:freezer:/docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e
8:hugetlb:/docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e
7:memory:/docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e
6:perf_event:/docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e
5:devices:/docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e
4:pids:/docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e
3:net_cls,net_prio:/docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e
2:cpu,cpuacct:/docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e
1:name=systemd:/docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e
0::/system.slice/docker.service
❯ docker exec revproxy-gen cat /proc/self/mountinfo
1422 1337 0:68 / / rw,relatime master:459 - overlay overlay rw,lowerdir=/var/lib/docker/overlay2/l/ZSACOL773WXPGHNWG2EH7AH6FO:/var/lib/docker/overlay2/l/V7XSR656VLMXCMUBSAA4DV3I2G:/var/lib/docker/overlay2/l/HH2GJ6T6C7QKS6ADY3DLKO6SBB:/var/lib/docker/overlay2/l/LOUMZPZEZQAFTW5AAAFBK4A5RH,upperdir=/var/lib/docker/overlay2/cd31ae31ae1aede18ad8c98c5f46703a9b5b41f1ddbb58477e0867c9a485bc6a/diff,workdir=/var/lib/docker/overlay2/cd31ae31ae1aede18ad8c98c5f46703a9b5b41f1ddbb58477e0867c9a485bc6a/work,index=off
1423 1422 0:94 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw
1424 1422 0:95 / /dev rw,nosuid - tmpfs tmpfs rw,size=65536k,mode=755,inode64
1425 1424 0:96 / /dev/pts rw,nosuid,noexec,relatime - devpts devpts rw,gid=5,mode=620,ptmxmode=666
1426 1422 0:97 / /sys ro,nosuid,nodev,noexec,relatime - sysfs sysfs ro
1427 1426 0:98 / /sys/fs/cgroup rw,nosuid,nodev,noexec,relatime - tmpfs tmpfs rw,mode=755,inode64
1428 1427 0:30 /docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e /sys/fs/cgroup/systemd ro,nosuid,nodev,noexec,relatime master:11 - cgroup cgroup rw,xattr,name=systemd
1429 1427 0:33 /docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e /sys/fs/cgroup/cpu,cpuacct ro,nosuid,nodev,noexec,relatime master:15 - cgroup cgroup rw,cpu,cpuacct
1430 1427 0:34 /docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e /sys/fs/cgroup/net_cls,net_prio ro,nosuid,nodev,noexec,relatime master:16 - cgroup cgroup rw,net_cls,net_prio
1431 1427 0:35 /docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e /sys/fs/cgroup/pids ro,nosuid,nodev,noexec,relatime master:17 - cgroup cgroup rw,pids
1432 1427 0:36 /docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e /sys/fs/cgroup/devices ro,nosuid,nodev,noexec,relatime master:18 - cgroup cgroup rw,devices
1433 1427 0:37 /docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e /sys/fs/cgroup/perf_event ro,nosuid,nodev,noexec,relatime master:19 - cgroup cgroup rw,perf_event
1434 1427 0:38 /docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e /sys/fs/cgroup/memory ro,nosuid,nodev,noexec,relatime master:20 - cgroup cgroup rw,memory
1435 1427 0:39 /docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e /sys/fs/cgroup/hugetlb ro,nosuid,nodev,noexec,relatime master:21 - cgroup cgroup rw,hugetlb
1436 1427 0:40 /docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e /sys/fs/cgroup/freezer ro,nosuid,nodev,noexec,relatime master:22 - cgroup cgroup rw,freezer
1437 1427 0:41 /docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e /sys/fs/cgroup/blkio ro,nosuid,nodev,noexec,relatime master:23 - cgroup cgroup rw,blkio
1438 1427 0:42 /docker/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e /sys/fs/cgroup/cpuset ro,nosuid,nodev,noexec,relatime master:24 - cgroup cgroup rw,cpuset
1439 1427 0:43 / /sys/fs/cgroup/rdma ro,nosuid,nodev,noexec,relatime master:25 - cgroup cgroup rw,rdma
1440 1424 0:87 / /dev/mqueue rw,nosuid,nodev,noexec,relatime - mqueue mqueue rw
1441 1424 0:99 / /dev/shm rw,nosuid,nodev,noexec,relatime - tmpfs shm rw,size=65536k,inode64
1442 1422 0:24 /docker.sock /tmp/docker.sock rw,nosuid,nodev,relatime - tmpfs run rw,mode=755,inode64
1443 1422 259:2 /var/lib/docker/containers/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e/hosts /etc/hosts rw,noatime - ext4 /dev/nvme0n1p2 rw
1444 1422 259:2 /var/lib/docker/containers/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e/resolv.conf /etc/resolv.conf rw,noatime - ext4 /dev/nvme0n1p2 rw
1445 1422 259:2 /var/lib/docker/containers/d8411145f6d775560b9169f5347d433a6ea32b01fb9a3903d50a98bae4a0421e/hostname /etc/hostname rw,noatime - ext4 /dev/nvme0n1p2 rw
1446 1422 259:2 /var/lib/docker/volumes/revproxy_nginx-conf/_data /etc/nginx/conf.d rw,noatime master:1 - ext4 /dev/nvme0n1p2 rw
1448 1422 259:2 /home/syphdias/docker/revproxy/nginx.tmpl /etc/docker-gen/templates/nginx.tmpl rw,noatime - ext4 /dev/nvme0n1p2 rw
1449 1422 259:2 /home/syphdias/docker-data/certs/letsencrypt/archive/example.com/fullchain6.pem /etc/nginx/certs/example.com.crt ro,noatime - ext4 /dev/nvme0n1p2 rw
1450 1422 259:2 /home/syphdias/docker-data/certs/letsencrypt/archive/example.com/privkey6.pem /etc/nginx/certs/example.com.key ro,noatime - ext4 /dev/nvme0n1p2 rw
1338 1423 0:94 /bus /proc/bus ro,relatime - proc proc rw
1339 1423 0:94 /fs /proc/fs ro,relatime - proc proc rw
1340 1423 0:94 /irq /proc/irq ro,relatime - proc proc rw
1341 1423 0:94 /sys /proc/sys ro,relatime - proc proc rw
1342 1423 0:94 /sysrq-trigger /proc/sysrq-trigger ro,relatime - proc proc rw
1343 1423 0:181 / /proc/asound ro,relatime - tmpfs tmpfs ro,inode64
1344 1423 0:182 / /proc/acpi ro,relatime - tmpfs tmpfs ro,inode64
1345 1423 0:95 /null /proc/kcore rw,nosuid - tmpfs tmpfs rw,size=65536k,mode=755,inode64
1346 1423 0:95 /null /proc/keys rw,nosuid - tmpfs tmpfs rw,size=65536k,mode=755,inode64
1347 1423 0:95 /null /proc/latency_stats rw,nosuid - tmpfs tmpfs rw,size=65536k,mode=755,inode64
1349 1423 0:95 /null /proc/timer_list rw,nosuid - tmpfs tmpfs rw,size=65536k,mode=755,inode64
1350 1423 0:95 /null /proc/sched_debug rw,nosuid - tmpfs tmpfs rw,size=65536k,mode=755,inode64
1351 1423 0:183 / /proc/scsi ro,relatime - tmpfs tmpfs ro,inode64
1352 1426 0:184 / /sys/firmware ro,relatime - tmpfs tmpfs ro,inode64

I saw the merge #345. Will the template need to change? Because I tried latest it and it's still broken:
❯ doc exec revproxy-gen head -3 /etc/docker-gen/templates/nginx.tmpl
{{ $CurrentContainer := where $ "ID" .Docker.CurrentContainerID | first }}
{{ $CurrentContainer }}
{{ where $ "ID" .Docker.CurrentContainerID }}
❯ doc exec revproxy-gen /usr/local/bin/docker-gen -only-exposed /etc/docker-gen/templates/nginx.tmpl |head -2
<no value>
[]
❯ docker inspect revproxy-gen |jq '.[].Image'
"sha256:c333921e96464c8abdc5d5db1a724a8f6ad5a358b2c9362c4e93d64d9d9a95ff"
❯ docker inspect c333921e9646 |jq '.[].RepoDigests[]'
"jwilder/docker-gen@sha256:4a88cb1ddb519b646e2966eba2d1b810189b906229eb72fb5b6c5faff289c3ee"

Oh, btw .Docker.CurrentContainerID yields the same result as docker inspect revproxy-gen |jq '.[].Id' -r.

Found a fix:
-only-exposed excludes the docker-gen container from the variable $ thus it can no longer be found by ID. I guess there are two options:

expose a port
don't use -only-exposed

Found a fix:
-only-exposed excludes the docker-gen container from the variable $ thus it can no longer be found by ID. I guess there are two options:

expose a port
don't use -only-exposed

This fixed it for me

@Syphdias is it still broken with #356 merged in ?

@buchdag, I tired to test this by building from source with make and docker cp-ing the binary into my container but I have trouble getting it to work at all. Outside the container it works. Maybe I need to build it differently?
bash-5.1# ldd /usr/local/bin/docker-gen
/lib/ld-musl-x86_64.so.1: /usr/local/bin/docker-gen: Not a valid dynamic program
bash-5.1#
bash-5.1# ldd /usr/local/bin/docker-gen2
  /lib64/ld-linux-x86-64.so.2 (0x7f1f6cceb000)
  libpthread.so.0 => /lib64/ld-linux-x86-64.so.2 (0x7f1f6cceb000)
  libc.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7f1f6cceb000)

@Syphdias is it still broken with #356 merged in ?

Using the 0.9.0 docker image, this is still an issue. Exposing a random port seems to fix this issue.

Seeing the same issue, using the template from this repo, which is 8 years old. Is it up to date?
I'm running 0.10.4-22-gedc74cc docker image, via compose with my command being:
      -endpoint 'unix:///var/run/docker.sock'
      -keep-blank-lines
      -notify "echo 'Change detected!'"
      -wait 1s:3s
      -watch
      '/etc/docker-gen/templates/nginx.tmpl'

(yes, it dumps it to the console only).
The endpoint I had to added, because the default (unlike the documentation states) is /tmp/docker.sock, set via DOCKER_HOST somehow.
Docker-get does see changes when I start/stop an container; but then just states the default entry isn't any different, and generates something near-empty.
riley-docker-gen-1  | 2023/05/31 20:17:16 Received event die for container 6410dd7b32cf
riley-docker-gen-1  | 2023/05/31 20:17:17 Received event stop for container 6410dd7b32cf
riley-docker-gen-1  | 2023/05/31 20:17:18 Debounce minTimer fired
riley-docker-gen-1  | server {
riley-docker-gen-1  |   listen 80 default_server;
riley-docker-gen-1  |   server_name _; # This is just an invalid value which will never trigger on a real hostname.
riley-docker-gen-1  |   error_log /proc/self/fd/2;
riley-docker-gen-1  |   access_log /proc/self/fd/1;
riley-docker-gen-1  |   return 503;
riley-docker-gen-1  | }

The container ID is correct, and running docker inspect 6410dd7b32cf within the docker-get (after apk add) shows up the usual info.
What magic is needed to make things work/debug? Are there any special labels needed on the origin containers to part of parsing? When turning on 'only published' and other options, I do actually see correct numbers in the output as well.
As a 'expose random port' I used 65535:65535/tcp but even this made no difference. Is my docker host too old? I see alpine has 23.06 and I only have Docker version 20.10.17, build 100c701 which was 'stable' from docker.com, but I see that a few months ago 23.06 was bumped to stable. Will try that next ...

Seeing the same issue, using the template from this repo, which is 8 years old. Is it up to date?

@oliv3r no this template isn't up to date. The templates in the repo were meant as minimal examples only and unfortunately aren't really maintained. In the case of nginx reverse proxy template, there is an actively maintained version, the one used in nginx-proxy/nginx-proxy.

I switched to using the template linked above as it does everything I wanted it to do :) Took some time to figure out how the template worked though. But I still think the template in this repo should work, even if it is basic, as it is used as a 'starting point'?


python310Packages.aioecowitt: 2022.11.0 -> 2023.01.0

Diff: https://github.com/home-assistant-libs/aioecowitt/compare/refs/tags/2022.11.0...2023.01.0
Changelog: https://github.com/home-assistant-libs/aioecowitt/releases/tag/2023.01.0
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

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

3 packages built:

home-assistant-component-tests.ecowitt
python310Packages.aioecowitt
python311Packages.aioecowitt


⚠ Spryr has degraded performance

In 93f6ae7, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 5713 ms

Resolved: Spryr performance has improved in cf061fc after 10 minutes.


Fix vtable stability issue with shared code

Pull request #2096 made sure that lazily built vtables of Foo<X> and
Foo<Y> contain the same entries if their canonical forms are the same,
but didn't make sure the order of the entries is the same. This can lead
to bugs at runtime where the wrong slot is used to dispatch a virtual
method call. To make sure the vtables look the same, we need to also
sort the vtable.

@nattress Please take a look!


🌟 [PLUGIN] New 3rd party plugin for syntax highlighting ~ Glow!

[!NOTE]

🌐 Website:-  arnavk-09.github.io/lume_glow/
🔌 Deno Plugin:- deno.land/x/lume_glow/plugin.ts
🌟 Github Repo:- github.com/ArnavK-09/lume_glow
🍳 Glow Highlighter:- https://nuejs.org/docs//concepts/syntax-highlighting

Great plugin!!
thank you ❤


Type inference when using array destructuring assignment fails to catch undefined values when the array is shorter than the destructure expression

Bug Report

🔎 Search Terms

array destructure assignment inference rest undefined
(found semi-related https://github.com/microsoft/TypeScript/issues/21519)
🕗 Version & Regression Information

Found in version 4.0.0, reproduced in nightly
⏯ Playground Link

Playground link with relevant code
💻 Code

const arr: number[] = [];

// foo and bar are both inferred to be of type number, but they should be (number | undefined).
const [foo, bar] = arr;

// Same here, baz is a number but should be (number | undefined). rest is correctly inferred as number[].
const [baz, ...rest] = arr;

console.log({ foo, bar, baz, rest }); // foo, bar and baz are undefined (!)

const add = (a: number, b: number) => a + b;

// This should be an error like "Argument of type 'undefined | number' is not assignable to parameter of type 'number'".
// Instead it compiles with sum inferred to be a number, but in fact it is NaN.
const sum = add(foo, 2);
console.log(sum);

🙁 Actual behavior

When destructuring an array, if the number of declared variables is longer than the length of the array, the extra ones will be undefined. However, TypeScript always infers the type of these variables to be defined. This can lead to uncaught errors when destructuring arrays that can be empty. Passing these destructured values to functions that require defined parameters will cause errors at run time that the compiler could easily catch.
🙂 Expected behavior

I would expect the inferred type of these destructured variables to be T | undefined where the type of the array is T[].

This is working as intended. When you enable noUncheckedIndexedAccess you get number | undefined.

Ah! Oops, thanks.


addresses issue in #401 whitelists all links with typegraphs

all typegraph headings have an id of typegraphrelations
if a target contains this, the target is passed
it will not work if the target is in an external file, so this test is too broad, but given the rarity of such a link, I think this fix is the best use of time

@coke I haven't been able to test this locally.

Can we narrow it down slightly? This seems like it would also allow
#invalidtypegraphrelations

@coke I did a search of the rendered documents (`rak 'typegraphrelations' .) and there is no other link with this combination of characters. Not quite sure how to narrow simply.


Refactor handlers params

Description
In this PR I tried to get handlers parameters in the same way we do with FindParams.
Count and delete handlers parameters were updated. More to come in the next PRs.
Closes #2465.

Readiness checklist

[ ] I added/updated unit tests.
[ ] I added/updated integration/compatibility tests.
[x] I added/updated comments and checked rendering.
[x] I made spot refactorings.
[ ] I updated user documentation.
[ ] I ran task all, and it passed.
[x] I ensured that PR title is good enough for the changelog.
[x] (for maintainers only) I set Reviewers (@FerretDB/core), Labels, Project and project's Sprint fields.
[x] I marked all done items in this checklist.

Oh, that's the exact thing I tried before, and Alexey didn't approve because there are not enough params in count and delete to move them to a common package...

Well, I guess we have to wait until Monday then...

and Alexey didn't approve because

Because it wasn't the task your were working on. This issue is literally about moving things to the common code.

Why we updated msg_count but not msg_delete and msg_explain for Tigris?

I'm on it.


Support execution with now dev

With a recent change to how now dev works, it is important to pass the provided meta object to the download() function, otherwise it attempts to overwrite the existing files in the working directory.
Related to https://spectrum.chat/zeit/now/is-it-normal-for-now-dev-to-empty-out-all-files-in-my-project~1f21924c-67c3-46d1-8771-52766c3de9ed.

Hi @TooTallNate. Thanks for this PR ❤


Update bufbuild plugin references

Small cleanup to the buf.gen.yaml plugin references:

https://buf.build/community/planetscale-vtprotobuf
https://buf.build/protocolbuffers/go

We've made some changes to Remote Plugins and figured it'd be nice to update references in popular open-source projects.

Thanks!


How multiple Conditional Access authentication strength policies are evaluated for registering security info

I've tested the part "How multiple Conditional Access authentication strength policies are evaluated for registering security info", but when I try to register a FIDO key using a TAP (not using WHFB), I'll end up in a loop where I cannot register any method.

The sign in fails on the first CA policy, so it seems that the register security info policy is not preferred over other authentication strength policies that target All cloud apps.
Am I holding it wrong?

The device is compliant, so I'd expect that I can access my Sign-in portal with TAP and a compliant device.
I'm using password only to sign-in into my compliant device, so bypassing WHFB for a moment.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 14d95746-1fc3-daba-85ac-c07ce9f67ab4
Version Independent ID: ee143f12-672f-455b-cc9b-4c8c3def0a17
Content: Overview of Microsoft Entra authentication strength - Microsoft Entra ID
Content Source: docs/identity/authentication/concept-authentication-strengths.md
Service: active-directory
Sub-service: authentication
GitHub Login: @InbarckMS
Microsoft Alias: justinha

@BakkerJan
Thanks for your feedback! We will investigate and update as appropriate.

@BakkerJan
I'm going to assign this to the document author so they can take a look at it accordingly.
@InbarckMS
Please review it.


JSON models got moved to separate module

See https://github.com/apple/swift-package-manager/pull/3199

@swift-ci please test

@swift-ci please test

No logic change. Builds succeeded locally.

No logic change. Builds succeeded locally.


feat(watt): styling of shell component

Description

Watt Design System

Style Shell component according to Figma (sidebar, toolbar)
Add padding to main content
Make Shell component responsive

References

https://github.com/Energinet-DataHub/MightyDucks/issues/215

PLEASE NOTE
Before merging a frontend pull request, be sure that all checks have passed. Currently, jobs done by a Git-bot (like formatting and adding licenses) don't trigger a re-run of all the other checks. The "merge button" can therefore give you a false positive signal.

Should be fixed now. The border was changed to border-bottom only with a lighter value.


react warning: duplicated keys

(replace is not working through multiple contexts)
-> move to helper

done


[BUG] Backupvolume doesn't sync if the backup is deleted from another cluster pointing to same backup store

Describe the bug
Two clusters having same backup store, if a backup is deleted from cluster A, it doesn't reflect as deleted in the cluster B. Although from backup store, the backup gets deleted.
To Reproduce
Steps to reproduce the behavior:

Create 2 clusters, point backup to the same backup store.
Delete one backup from backup page from cluster A.
Wait for sometime for backup to get deleted.
Check cluster backup page, the deleted backup is still available.
Check the kubectl get backupvolumes -n longhorn-system, it has the deleted backup.

Expected behavior
The delete object should also be sync.
Log or Support bundle
On restoring the deleted backup, below is the log which is as expected.
longhorn-manager-cks5l] E1215 22:08:16.354952       1 engine_controller.go:701] failed to update status for engine volume-test-1-e-64393c01: failed to restore backup backup-29bc1dd38cfc4087 in engine monitor, will retry the restore later: failed to execute: /var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-master-head/longhorn [--url <IP_ADDRESS>:10000 backup restore s3://<bucket-name>/?backup=backup-29bc1dd38cfc4087&volume=pvc-85d9de64-d1e4-4262-bbc0-35b5a492fdfa], output failed to get the current restoring backup info: cannot find backupstore/volumes/c4/17/pvc-85d9de64-d1e4-4262-bbc0-35b5a492fdfa/volume.cfg in backupstore

Environment

Longhorn version: v1.2.3-rc2
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): kubectl

cc: @jenting

Not an issue, my cluster has Backupstore Poll Interval set to high value.


[Backend] Set a new instance for Moonbeam in Transaction service

Deploy a new instance of the transaction service for the Moonbeam network.

An example of this can be found here (Config for Polygon)

Analyze the risk and how to implement it.

@ArseniiPetrovich  Can you take a look at this ticket and check how it will be the best way to implement it?.

@veaceslavdoina Can you give us a bit more info on your findings about the Transaction Service (https://github.com/gnosis/safe-transaction-service)? What is the approximate costs, etc?
@fapesteguia Do we need to deploy it already somewhere, or are we still investigating?

@ArseniiPetrovich, beases on our tests:

         RDS
             \
               Safe Transaction <-- ALB <-- Client
             /
ElastiCache

Costs

Component
Type
Size
Price

LB
ALB
-
$18.40

DB
RDS
db.t3.small
$37.80

Redis
Elasticashe
cache.t3.small
$32.12

Safe-transaction
EC2
c5.large
$78.15

Moonbeam
EC2
c5.2xlarge
$315.09

TOTAL: $481.56
Such deploy can serve for about 300 requests per second.


Not include javascript script within .html export

I'm running this command
vulcanize ./polymer/fold-over.html --inline --csp vulcanize.js

And I have this in the last line of my vulcanize.html file.
<script charset="utf-8" src="vulcanized.js"></script>

I need to remove that script tag from the export.

I made something to strip a doc of <script> tags.
https://github.com/reggi/node-rmscripts
Feel free to close if not essential to vulcanize.

Why are you removing the script tag? It contains the script you had in your import. Without it, any elements in your import will probably fail to work.

Is this related to #139?

Yes and No. I'm using a host that sets up their own assets. (Shopify)
I need a way to point to my assets in the theme directly.
<link rel="import" href="{{ polymer-components.html | assets_url }}">
<script src="{{ polymer-components.js | assets_url}}"></script>

That link is a server-side variable that links tho their CDN.
I'd imagine wordpress themes would need the same kind of support.

Works! I get it --strip is a function of uglify, which doesn't understand es6 syntax. Thanks for the help @azakus!!


Check for location permissions when loading Nearby

Fix #650 . Adds runtime permissions checking when Nearby is loaded, tells user that Nearby places cannot be found if permissions denied.

Codecov Report

Merging #707 into master will increase coverage by 0.06%.
The diff coverage is 45.45%.

@@            Coverage Diff            @@
##           master    #707      +/-   ##
=========================================
+ Coverage       6%   6.06%   +0.06%
=========================================
  Files          94      94
  Lines        5012    5028      +16
  Branches      443     446       +3
=========================================
+ Hits          301     305       +4
- Misses       4686    4696      +10
- Partials       25      27       +2

Impacted Files
Coverage Δ

...ava/fr/free/nrw/commons/nearby/NearbyActivity.java
44.85% <45.45%> (-2.65%)
: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 5b4dc4e...e6e141e. Read the comment docs.

I disagree with Codacy that I should be splitting a 101 character line up any further. >.> Not sure if we want a default clause for the permissions result switch?

I can confirm for emulator API 24 and 25 that it asks me for the permissions. Denying the permissions goes to an endless loading screen. Maybe a message "You need GPS permissions to use Nearby" would be more helpful than the loading icon. When the permissions are granted I still sometimes get no results, probably because of https://github.com/commons-app/apps-android-commons/issues/674.

Ah, good point. I'm not sure how useful it would be to have a screen with just those words though. Maybe I could use the toast, but just send them back to the previous activity.

Just for reference this is what I am thinking of:

The user should now be taken to a screen that explains Nearby Places can't be shown if they deny permission. It's not anywhere near as pretty as the screenshots here :) , but that could be a future enhancement. Also, a future enhancement could give the user an option to be asked for permissions again at NoPermissionsFragment without having to go back to NearbyActivity to do it, but I don't think that is essential for the time being.
Note that I have included a temporary fix for #709 . I considered doing a separate PR for that, but since that fix is absolutely needed in order for this PR to work, it made sense to me to tie them together.

@misaochan I really like the way you implemented the message!
I am justing testing the branch. If I deny location permissions then the nearby mapview will crash in the showMapView() function in the NearbyActivity. Haven't been able to figure out why yet.

Thanks @tobias47n9e . :) Could you post the crash logs?

06-02 19:07:17.736 3376-3376/fr.free.nrw.commons E/AndroidRuntime: FATAL EXCEPTION: main
Process: fr.free.nrw.commons, PID: 3376
java.lang.NullPointerException:
Attempt to invoke virtual method 'android.os.AsyncTask$Status fr.free.nrw.commons.nearby.NearbyActivity$NearbyAsyncTask.getStatus()' on a null object reference
at fr.free.nrw.commons.nearby.NearbyActivity.showMapView(NearbyActivity.java:180)
at fr.free.nrw.commons.nearby.NearbyActivity.onOptionsItemSelected(NearbyActivity.java:82)
at android.app.Activity.onMenuItemSelected(Activity.java:3204)
at android.support.v4.app.FragmentActivity.onMenuItemSelected(FragmentActivity.java:408)
at android.support.v7.app.AppCompatActivity.onMenuItemSelected(AppCompatActivity.java:195)
at android.support.v7.view.WindowCallbackWrapper.onMenuItemSelected(WindowCallbackWrapper.java:113)
at android.support.v7.view.WindowCallbackWrapper.onMenuItemSelected(WindowCallbackWrapper.java:113)
at android.support.v7.app.ToolbarActionBar$2.onMenuItemClick(ToolbarActionBar.java:69)
at android.support.v7.widget.Toolbar$1.onMenuItemClick(Toolbar.java:206)
at android.support.v7.widget.ActionMenuView$MenuBuilderCallback.onMenuItemSelected(ActionMenuView.java:776)
at android.support.v7.view.menu.MenuBuilder.dispatchMenuItemSelected(MenuBuilder.java:822)
at android.support.v7.view.menu.MenuItemImpl.invoke(MenuItemImpl.java:156)
at android.support.v7.view.menu.MenuBuilder.performItemAction(MenuBuilder.java:969)
at android.support.v7.view.menu.MenuBuilder.performItemAction(MenuBuilder.java:959)
at android.support.v7.widget.ActionMenuView.invokeItem(ActionMenuView.java:623)
at android.support.v7.view.menu.ActionMenuItemView.onClick(ActionMenuItemView.java:154)
at android.view.View.performClick(View.java:5610)
at android.view.View$PerformClick.run(View.java:22265)
at android.os.Handler.handleCallback(Handler.java:751)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6077)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:865)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755)

The recent commit should fix it hopefully.

@misaochan Clicking the map button works now avoids the crash. Just one small problem remains. Pressing refresh in that view makes the message disappear and after that I can click back and forth on the map without any messages anymore that I am missing the location permissions.

If that is the only remaining issue and it otherwise works fine, shall we merge first and make that a separate issue (possibly a beginner friendly enhancement)? I was hoping to push this fix to beta by Monday, as currently everyone in beta has to give permissions manually. :)


feat: Allow users to set custom profile pictures (#2405)

Enhancing the functionality of the MSColab server to allow users to upload small images which would replace generic initials as identifiers during login. This feature personalizes user accounts and significantly enhances the visual aspect of user identification and interaction within the MSColab platform.
Purpose of PR?:
Part of the GSoC 2024 improve MSUI project:  Introduce a new feature to mscolab, enabling users to upload and set personalized profile pictures.
Fixes #1287

reminder: never delete a GSOC branch


uv ignores python_version marker when conjoined with platform markers

For example, SQLAlchemy 2.0.32 has a dependency on greenlet, marked for certain platforms and only for Python < 3.13^1:
greenlet != 0.4.17;(python_version<"3.13" and (platform_machine=='aarch64' or (platform_machine=='ppc64le' or (platform_machine=='x86_64' or (platform_machine=='amd64' or (platform_machine=='AMD64' or (platform_machine=='win32' or platform_machine=='WIN32')))))))

Now, something changed in uv 0.2.37 that the python_version marker is ignored. For example:
# requirements.txt
sqlalchemy==2.0.32

With uv 0.2.36
$ UV_NO_CACHE=1<EMAIL_ADDRESS>pip compile --python python3.13 --python-platform x86_64-manylinux_2_31 requirements.txt
Resolved 2 packages in 1.16s
# This file was autogenerated by uv via the following command:
#    uv pip compile --python python3.13 --python-platform x86_64-manylinux_2_31 requirements.txt
sqlalchemy==2.0.32
    # via -r requirements.txt
typing-extensions==4.12.2
    # via sqlalchemy

but with uv 0.2.37
$ UV_NO_CACHE=1<EMAIL_ADDRESS>pip compile --python python3.13 --python-platform x86_64-manylinux_2_31 requirements.txt
Resolved 3 packages in 1.16s
# This file was autogenerated by uv via the following command:
#    uv pip compile --python python3.13 --python-platform x86_64-manylinux_2_31 requirements.txt
greenlet==3.0.3
    # via sqlalchemy
sqlalchemy==2.0.32
    # via -r requirements.txt
typing-extensions==4.12.2
    # via sqlalchemy

When the platform is not one of those in the markers, the dependency is correctly excluded:
$ UV_NO_CACHE=1<EMAIL_ADDRESS>pip compile --python python3.13 --python-platform aarch64-apple-darwin requirements.txt
Resolved 2 packages in 1.17s
# This file was autogenerated by uv via the following command:
#    uv pip compile --python python3.13 --python-platform aarch64-apple-darwin requirements.txt
sqlalchemy==2.0.32
    # via -r requirements.txt
typing-extensions==4.12.2
    # via sqlalchemy

Maybe related:

https://github.com/astral-sh/uv/issues/6168

Interesting, thanks.

I’ll try to take a look at this today.

I have at least one idea of what’s going on here.

Ah ok I see the issue.

(It's unique to 3.13, since only pre-releases are available, and it relates to a mishandling of pre-releases there. Will fix.)

Thanks @charliermarsh!

Thanks for reporting!


Project Rename / Version numbering

@mondus suggested thinking of a new name rather than FLAME GPU 2, which will lead to potentially confusing version numbers (at least until the first full release)

FLAMEGPU

Just call the project FLAME GPU as a a major release in the FLAME GPU system - i.e FLAME GPU 2.0.0
Massive breaking changes / entirely different model to FLAME GPU 1
Overwriting the FLAMEGPU/FLAMEGPU repo might lead to issues with people using it in submodules and not targetting specific tags.

FLAMEGPU2

The 2 is in the name, rather than a version number
Pre-releases could be FLAMEGPU2 0.x.y, with FLAMEGPU2 1.0.0 for the first release with a stable interface.
Separate repo FLAMEGPU/FLAMEGPU2 doesn't break other projects
Keeps history / clear successor to FLAMEGPU1
Would want to update the flamegpu1 readme to point to fgpu2 for all future dev.

Other renames

Competely change the name to clearly show its different from FLAME GPU 1.
Might lose the clear history / weight from FLAME GPU
Do we want to keep/lose the association with FLAME as the parent project?
Semver starting 0.1.0 and moving to 1.0.0 once api is stable would make sense.
Suggestions (not all serious)

Pheonix (via mondus)
FLAML GPU - it's a Library not an environment

pheonix?

When renaming the repo, the current github urls will still work as long as we do not create a new repo of the same name

When you rename a repository, all existing information, with the exception of project site URLs, is automatically redirected to the new name, including:

Issues
Wikis
Stars
Followers

Warning: If you create a new repository under your account in the future, do not reuse the original name of the renamed repository. If you do, redirects to the renamed repository will break.

https://docs.github.com/en/github/administering-a-repository/renaming-a-repository

FLAME GPU 2 is the name, and _dev has been removed from the repo name.
We should update all other repos to reflect this, although they will work fine with _dev.
Versioning is still an open question:

FLAME GPU 2 2.0.0 as first stable release,

with prior tags as  2.0.0-alpha, 2.0.0-alpha.1, ...

FLAME GPU 2 1.0.0 as first stable release.

FLAME GPU 2 0.1.0 etc.

We are using SemVer starting at 2.0.0-alpha as the initial tagged release.
Subsequrent pre-release versions may be of the formats alpha.N, beta, beta.N, rc.N where N is a positive integer.
We will use alpha as the pre-release component until we expect no more breaking changes to occur, moving onto either beta releases or a release candidate.
Once we're happy with an RC versions, we will then move to teh first stable non-pre-release 2.0.0
Following that, we will adhere to SemVer, with new features being included in new minor versions, and breaking changes in the public API leading to a new major versioon (at which point we might shimmy round some repository names)


Integration Tests, Errors: Writing a signed Int to an unsigned column

We should add a test that confirms and tracks the behavior and error message when you try to write a signed Int to an unsigned Int column.
See https://github.com/prisma/prisma/issues/1823#issuecomment-670524499

Can you link to the integration test that covers this @eemmiillyy please? Thanks.

Integration tests have been added for these with (https://github.com/prisma/prisma/pull/3683) in (https://github.com/prisma/prisma/commit/cd8361cf5a1e4c8786f40075db9888e188e701c1#diff-6e4bbddeca93b81ae24c82eaef9bbf5e)


Currency Data Standardisation - Minutes of Initial Meeting 24 June 2020

Currency Data Standardisation - Initiative Discussion Meeting
Wed Jun 24, 2020 12:30pm – 1:15pm ET
Attendees
Sailesh Pandey (Nomura)
Ted Sanborn (ISDA)
Ian Sloyan (ISDA)
Aitana Myohl (FINOS)
Rob Underwood (FINOS)
Siddharthan Rajagopalan (Barclays)
Yeonje Jo (Bloomberg)
Ffion Wiggins (GS)
Vijayesh Chandel (GS)
Summary Of Discussion
Initiative to standardise currency data for which the Securities Reference Data project allows for an open source cloud based solution:
https://finosfoundation.atlassian.net/wiki/spaces/DT/pages/1670774789/Currency+-+Defining+standard+Object
Data input/maintenance would follow an open source workflow:

Firm XYZ submits data mapping/proposal to the cloud
Request for consensus approval from participants – minimum number would be required
If approved, data can be merged in for consumption via APIs

The initiative would require two parts for standardisation: i) Currency data and ii) Country data
Initial POC modelled in Alloy Studio: https://alloy.finos.org/studio/review/UAT-33/18
Suggestions Proposed:

Light and full editions; the former capturing minimum set of required data attributes
Additional classes/properties:

Source Enumerations: Lists out different types of sources of data e.g. ISO, ISDA etc
Effective/End Dates: Provides dates for which a currency code is active

Bi-weekly forum to be set up for this group.

thanks @Vijayesh-Chandel I'll close this issue now


Backwards compatability

Flank is a mature enough project where a backwards compatibility strategy is necessary to avoid breaking users as changes are made.
Ideas

Print to log when deprecated keys are used
Support legacy key names until the next major release
Auto rewrite YAML file to use the new keys (either automatically or on demand via doctor command)

If a user has a legacy key name that's no longer supported, what should we do?

Exit with an with an error message?
Auto rewrite YAML to the new key name (if auto migration is possible)?
Continue to run but ignore the key and print a warning to standard out

I would go with:

deprecation warning on console
support for legacy functionality for 1 major release
on-demand fixing of the configs (as opposed to automatic)
exiting with an error message once the legacy value is no longer supported


Environment is not able to be overridden.

I can see these env vars in this sdk.
{
"AWS_LAMBDA_FUNCTION_VERSION": "$LATEST",
"AWS_EXECUTION_ENV": "AWS_Lambda_nodejs20.x",
"HOSTNAME":
"POWERTOOLS_SERVICE_NAME": "lambda",
"AWS_DEFAULT_REGION": "eu-west-1",
"AWS_LAMBDA_LOG_STREAM_NAME": "$LATEST",
"AWS_REGION": "eu-west-1",
"PWD": "/var/task",
"_HANDLER": "index.exampleHandler",
"TZ": ":/etc/localtime",
"AWS_LAMBDA_FUNCTION_HANDLER": "index.exampleHandler",
"LAMBDA_TASK_ROOT": "/var/task",
"HOME": "/root",
"AWS_SAM_LOCAL": "true",
"LANG": "en_US.UTF-8",
"AWS_SECRET_ACCESS_KEY":
"AWS_LAMBDA_LOG_GROUP_NAME":
"AWS_LAMBDA_RUNTIME_API": "<IP_ADDRESS>:9001",
"AWS_LAMBDA_FUNCTION_MEMORY_SIZE": "128",
"LAMBDA_RUNTIME_DIR": "/var/runtime",
"AWS_LAMBDA_LOG_FORMAT": "JSON",
"AWS_LAMBDA_LOG_LEVEL": "INFO",
"ENVIRONMENT": "Dev1",
"AWS_LAMBDA_FUNCTION_TIMEOUT": "29",
"AWS_ACCOUNT_ID": "123456789012",
"SHLVL": "0",
"AWS_ACCESS_KEY_ID":
"LD_LIBRARY_PATH": "/var/lang/lib:/lib64:/usr/lib64:/var/runtime:/var/runtime/lib:/var/task:/var/task/lib:/opt/lib",
"NODE_PATH": "/opt/nodejs/node20/node_modules:/opt/nodejs/node_modules:/var/runtime/node_modules:/var/runtime:/var/task",
"AWS_LAMBDA_FUNCTION_NAME": "ExampleFunctionB28997EC",
"PATH": "/var/lang/bin:/usr/local/bin:/usr/bin/:/bin:/opt/bin",
"AWS_SESSION_TOKEN": ""
}
But I can not override some env vars by setting them in env file such as "TZ", "SHLVL"

Hi @blkdot, I also wasn't able to override the SHLVL environment variable with the help of the .env file. However, I was able to overwrite EDITOR which is set on my Laptop. Therefore, I assume that the overridden variables are overridden again during the execution.
You could try to set the TZ variable via a shell initialization file like .bashrc.

Got it. thanks