Add Vector3.GetAnglesBetweenVectorsForDirectionChange

Also add prettier settings to workspace settings.
See this PR for more details.
Demo PGs:
https://playground.babylonjs.com/#QYA3JC#20
https://playground.babylonjs.com/#QYA3JC#21
(Press space to start)
@BabylonJSGuide
I have the opportunity to talk with a physicist almost every day of the week, so I asked him about the problem and worked out the same equations used. After researching how Math.atan2 works though, and found an issue with the equations: for the phi calculation, the diff.y should have been the second parameter of Math.atan2, not the first.

Is it not similar to #13004

@sebavan,
How is this related to #13004?

Is it not similar to #13004

@sebavan, How is this related to #13004?

RotationQuaternionFromOntoToRef seems to be doing the exact same finding the required rotation bewtween two vectors.

RotationQuaternionFromOntoToRef seems to be doing the exact same finding the required rotation bewtween two vectors.

https://playground.babylonjs.com/#QYA3JC#24 It does not seem to work.

RotationQuaternionFromOntoToRef seems to be doing the exact same finding the required rotation bewtween two vectors.

https://playground.babylonjs.com/#QYA3JC#24 It does not seem to work.

Let s figure it out and only keep one implementation. We need to be careful and prevent duplicated features.

Agreed, could we maybe move it to this PR?
I'd like to know what @BabylonJSGuide thinks of this PR since we worked on it in #12942.

Not sure it should be moved in this PR, lets compare the functionalities and keep the one closest from the goal. You can check with @BabylonJSGuide.

@dr-vortex now understand the difference - yours deals with positions mine with directions.
Suggestions

Be clear about which axis of the mesh is following the curve

A better name would be pitchYawRollToMoveBetweenPoints(point0, point1)

Change comment from

Gets the angles between two vectors needed to change direction

to something like

gets the pitch, yaw, roll that enables a mesh/object(?) to move along a straight line between two points (vector3)

Possibly add an optional roll parameter, ie pitchYawRollToMoveBetweenPoints(point0, point1, roll?) which would default to zero but could be updated by the user to affect the roll as it follows the curve.

Need to wait to see if @RaananW and @sebavan think there is sufficient differences between both and/or between existing methods for none, one or both to be approved.

Yes, I've been thinking about it with positions. For your 4th point, I had originally included an offset in #12942 but removed it. I agree we should wait to see if they should be implemented separately.

Let s validate the naming and doc comment with @BabylonJSGuide and ready to ship :-)

Sounds good!

Before approval at least the following PG should be tested
https://playground.babylonjs.com/?snapshot=refs/pull/13012/merge#S7HDGQ#5

@dr-vortex I ll merge as soon as @BabylonJSGuide comments have been addressed.
Thanks a lot you both !!!


[Fixes #108] Fixed issue of poorly formatted phone numbers

You'll also have to do something for components/auto-link-text.
I know I'm a bastard, I used two separate libraries for the components since react-native-autolink can only do text output, but it does it really well. reac-native-autolink actually depends on autolinker though.
You could just use that same regex to test if the input is a phone number and replace it similarly.

noted

@a1gemmel Added fix for auto-link-text


WebSocket - sendStringByFuture support

We need to be able to send lots of WebSocket messages quite quickly and currently we are hitting a
"Blocking message pending 10000 for BLOCKING" error messages, it would appear that we could work around this by using the Async WebSocket support in Jetty which is accessible with session.sendStringByFuture() rather than session.sendString()
Is it possible that these methods could be exposed, or is there a way to get do the underlying Jetty session so that we can call them directly?

Isn't it available through wsSession.remote.sendStringByFuture()?

You are indeed correct - request can be closed as it's already present (and solves our issue!)

Great! We should consider making this the default in Javalin 3.0.


Add missing check for numeric value

The problem referenced in the comment:

Except for numbers because we don't want to confuse valuesMap indexes. i.e. 7 vs "7"

was still present if a number came first in the attribute list, i.e. {"version": 1, "id": "1"} - in this case you get id set to the number 1 instead of a string.

Thank you.


Fix integration test issues due to multi-arch

Currently our integration tests are broken due to the changes in the Dockerfile to add multi-arch support.
This is due to the lack of support in the dockertest library for the new BuildKit library from docker/moby. I have set a PR to dockertest to fix that https://github.com/ory/dockertest/pull/374
This PR changes the integration tests to use the patched version of dockertest, and replaces the library in go.mod to point to my fork. Hopefully this last part will be removed in a few days.

Going to close this, as we need to investigate what is making the continuous integration tests fail.


create a docker for selective search

installing all the dependencies is quite a pain on my mac, is it possible to make a docker for this purpose.

Hey ! Did you manage to do it ? :)


Add material ui styling to leave and cancel views

See issue #51

Hello @mrpresidentjk! Thanks for submitting the PR.

In the file events/views.py, following                are the PEP8 issues :

Line 109:80: E501 line too long (85 > 79 characters)


BIGIP: Add support for lsnpool (CGNAT)

@caphrim007
What issues does this address?
Fixes #1317
What's this change do?
Adds support for following CGNAT related resources. These are needed to address basic cgnat usecase.

[x] LSNpool collection and resource + tests
[x] LSN log profile collection and resource + tests
[x] Add missing ALG profile - IPsecALG

Helps with following user stories:

User is able to create LSN pool without lsn log profile
User is able to create LSN pool with lsn log profile
User is able to create a virtual and attach a lsn pool and ALG profile

Where should the reviewer start?

This work adds new functionality and can be reviewed in any order.
Recommended path:

LSN pool code(f5/bigip/tm/ltm/lsnpool.py) covered lsnpool + lsnpool log profile
Looking at tests (f5/bigip/tm/ltm/test/functional/test_lsnpool.py)
New profile added - f5/bigip/tm/ltm/profile.py

Any background context?

I work at F5 networks in CGNAT test org.

For some reason - my PR seems have pulled in changes that are not related to #1317. May be I messed up something - please let me know if its recommended to start a new PR.
[root@opensource-client functional]# git branch -vv

cgnat_support        094736a [origin/development: ahead 14] removing unused import
development          b2f5e1b [origin/development] Merge pull request #1316 from caphrim007/bugfix.allow-asm-tasks-to-import-to-partition

@PrashantSunkari this PR needs to be rebased that why you have the other PRs in there.

Closing this request and started a new request -  https://github.com/F5Networks/f5-common-python/pull/1321


Replaced pager links

Pjax builtin Yii2 causes replacing gridview pager links after clicking any action column button.
How to prevent it?

Please use forums for questions. GitHub is for reporting issues.

That's the issue. It shouldn't happened.

What do you mean by replacing? Overall, PJAX is replacing the whole container with new data. That's how it works.

Pagination uses default action to load data showed in GridView. When I click eg. delete button in action column, it goes to actionDelete and after success links in Pager are also related to this action (delete) but they really shoulnd't - pager should be still used only to change pages, not deleting data.

You mean after PJAX refresh pagination buttons are triggering delete?

Yes, but only when I firstly click delete button on any gridview row. When first page load and only changing gridview pages it works correctly but as I said it replaces pagination links after calling any gridview action column button, eg.

Correct pagination url:

http://ue_frontend/user/address/75?pjax=%23ustalenia-container&=1439279618439&page=2

Incorrect pagination url:

http://ue_frontend/user/deleteaddress/2520?pjax=%23ustalenia-container&=1439279618440&page=2
As you can see in second case controller's action is changed to deleteaddress and id parameter is set to id of last deleted row.

are you using enablePrettyUrl?

@dynasource yes.

do you have the same issue without it?

Yes.
Anyway I found temporary solution but now I need to edit whole project pjax action. It looks like:
$dataProvider->pagination->route = 'worker/address/'.$workerid;
I don't think it's good solution but it works.

dont you have data-pjax="0" in the delete links?

No. URLs I've posted are not from browser bar, but from inspecting element.

I cannot reproduce your issue. It looks like you're delete call does not finishes with a 302


Doesn't serialize in iron-form

https://github.com/vaadin/vaadin-checkbox/issues/45#issuecomment-344720726

See (and report) if radio-button has the same issue since it uses the same approach for name.


Bug Report: Game not running full speed with FlxG.fixedTimestep = true;

Description
FlxG.fixedTimestep is true by default. In my laptop, both hxcpp and HTML5 builds of the game, it did not run full speed. Proposed fix is to set FlxG.fixedTimestep to false in Main.hx. This can also potentially fix other issues, like linear interpolation being frame rate dependent.
Specifications
Windows (x86_64)
Friday Night Funkin' Kade Engine e02d9a546f1a3a13189de123e95d3c965810e87d

where exactly would this main.hx file be? i searched my pc drive for it and nothing came up via the search. do keep in mind im not necessarily savvy when it comes to things like this. # @gedehari

main.hx would be in the source folder of the source code

FlxG.fixedTimestep isn't on Main.hx yet, the proposed fix is to add that line somewhere after Flixel is added to Stage.

Wait is this the "menu goes at half speed until song started" bug?

Wait is this the "menu goes at half speed until song started" bug?

Yeah. Wait, it's been fixed?

Didn't say that. Just really annoys me when playing mods on KBH Games

Didn't say that. Just really annoys me when playing mods on KBH Games

Ah I see. This should fix it.

ah alrighty, thank y'all kindly

where exactly would this main.hx file be? i searched my pc drive for it and nothing came up via the search. do keep in mind im not necessarily savvy when it comes to things like this. # @gedehari

its kinda hard just get the source code and its in the source folder but to build it you have to go to the fnf repo and read the tutorial on building fnf in the desc.


Support for highlighting pointers

Hey! I love this tool! One thing that would be really useful for low level developers is highlighting pointers/memory addresses, potentially also splitting them up into 32bit chunks so they're easier to read :)

Hi @agnosticlines ! Glad you like tailspin!
Yes, I agree that this is something useful to highlight. I have some ideas on how to do it, I just want to make sure it turns out well.

Added in 3.0.0 🎉


HTTPS for AssetHost

[ ] Assethost can run on a dev machine
[ ] There is clear documentation on how to run AssetHost on a dev machine
[x] asset URLs are HTTPS
[x] we don't get any mixed content warnings in the major browsers because we're requesting assets using a different protocol (https <=> http)

I pushed the https change to assethost Saturday night and seems to be 👌


[SPARK-49113] Dont assert on translation bugs - silently swallow the exception

What changes were proposed in this pull request?

Why are the changes needed?

In this PR I propose that we do not assert and fail queries when V2ExpressionBuilder returns class that is not predicate. Instead I suggest that we silently swallow the exception, add log, and continue execution of query.
V2ExpressionBuilder has no compiler gurantees that Predicate will be returned. With this in mind, its very easy to add regressions that will suddenly start failing queries, without a workaround for users, other than code change.
In this PR, I suggest we add a flag, which when enabled, will absorb this bugs in V2ExpressionBuilder.
It is as if we are saying:

If we are trying to translate catalyst expression to V2Expression and are requesting Predicate, if predicate is not returned act as if we didn't know how to translate expression at all.

We return None, and rest of the system handles it as if we didn't know to translate to V2Expression
More details in JIRA ticket
Does this PR introduce any user-facing change?

Queries that failed because of pushdown failure, will now skip pushing down offending predicate, rather than failing the whole query.
How was this patch tested?

Unit tests.
Was this patch authored or co-authored using generative AI tooling?

No

This is still unclear. Basically, your changes are trying to simply skip the potential pushdown, instead of failing the queries.
However, in the test mode, we should still allow the query to fail. This will help us identify and capture any underlying bugs, rather than silently bypassing them. Ignoring these bugs could lead to missed opportunities for predicate pushdown, which might negatively impact query performance.
WDYT?

Agreed. Updated description and added test assert. Also refactored code to have cleaner API as per agreement with @sigmod

@gengliangwang  can you take a look?

Thanks, merging to master


Hi

Could you give a procedure to have hue2mqtt installed and running on Raspberry pi 3.
I have installed node.js version 8.x.x and when I run the command
sudo npm install -g hue2mqtt
I get and error:
npm ERR! code MODULE_NOT_FOUND
npm ERR! Cannot find module 'internal/util/types'
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-06-07T12_45_04_668Z-debug.log
Your help will be appreciated
Thanks

You've made one of the classic blunders: confused Java and Javascript. Despite the similar names, these languages have nothing to do with each other. npm (and nodejs, etc.) are all written to handle Javascript, but this project is written in the completely separate language Java. In order to build and run this project, you will need Java tools, not Javascript tools.
In particular, you need Gradle (a build system -- roughly equivalent to Webpack in the Javascript world), as well as the Java Development Kit (a compiler and runtime -- roughly equivalent to nodejs). Gradle made some changes recently, so you will need version 4 for now (#18 changes this project to work with Gradle 5). This project works with JDK 8 (it might work on later versions, I haven't tested).


add a fake /bin/systemctl

We should then be able to mount into moonraker container to allow shutdown, reboot, status, etc

We have added this, but it doesn't look like it will work mounting it.


Extract main tasks to Application module

Closes #40.
With this module in place, all of the theme names are declared dynamically so we don't have to edit much when we go to release a new gem, just a couple of rake task descriptions and the namespace inside the task file itself.
For lack of a better name I named this module Application directly namespaced under BulletTrain::Themes, but if we want to name it something else I'm open to other options.

The only task I decided to not write dynamically is the release task.
The reason for this is because I'm assuming we want all themes to stem directly from Bullet Train's Light theme, so I added a message that exits the developer from the task if they are trying to release a custom theme based off of anything else besides light.
Also, when a developer goes to release a gem, they clone our Light theme gem to their local repository, then we replace any changed views with their custom files in the task. For this reason, since we're originally cloning off of the light theme gem I thought it would make sense to keep this task as is.
If we DO want to write it dynamically though so developers can "cascade" custom theme publishing, I'd be glad to work on that part as well.


ImportError: cannot import name longpoll while running crossbar python example

OS: Mac OSX 10.10.2
Python Version: 2.7.6
Crossbar: 0.11.1
Autobahn: 0.11.0
2015-12-03T13:21:52+0530 [Controller  77106] Stale Crossbar.io PID file (pointing to non-existing process with PID 77030) /Users/voidabhi/stuff/py/hello/.crossbar/node.pid removed
2015-12-03T13:21:52+0530 [Controller  77106]      __  __  __  __  __  __      __     __
2015-12-03T13:21:52+0530 [Controller  77106]     /  `|__)/  \/__`/__`|__) /\ |__)  |/  \
2015-12-03T13:21:52+0530 [Controller  77106]     \__,|  \\__/.__/.__/|__)/~~\|  \. |\__/
2015-12-03T13:21:52+0530 [Controller  77106]
2015-12-03T13:21:52+0530 [Controller  77106]     Version: 0.11.1
2015-12-03T13:21:52+0530 [Controller  77106]
2015-12-03T13:21:52+0530 [Controller  77106] Starting from node directory /Users/voidabhi/stuff/py/bingo-backend/cb/.crossbar
2015-12-03T13:21:53+0530 [Controller  77106] Traceback (most recent call last):
2015-12-03T13:21:53+0530 [Controller  77106]   File "/usr/local/bin/crossbar", line 9, in <module>
2015-12-03T13:21:53+0530 [Controller  77106]     load_entry_point('crossbar==0.11.1', 'console_scripts', 'crossbar')()
2015-12-03T13:21:53+0530 [Controller  77106]   File "/Library/Python/2.7/site-packages/crossbar/controller/cli.py", line 834, in run
2015-12-03T13:21:53+0530 [Controller  77106]     options.func(options, reactor=reactor)
2015-12-03T13:21:53+0530 [Controller  77106]   File "/Library/Python/2.7/site-packages/crossbar/controller/cli.py", line 523, in run_command_start
2015-12-03T13:21:53+0530 [Controller  77106]     from crossbar.controller.node import Node
2015-12-03T13:21:53+0530 [Controller  77106]   File "/Library/Python/2.7/site-packages/crossbar/controller/node.py", line 49, in <module>
2015-12-03T13:21:53+0530 [Controller  77106]     from crossbar.worker.router import RouterRealm
2015-12-03T13:21:53+0530 [Controller  77106]   File "/Library/Python/2.7/site-packages/crossbar/worker/router.py", line 50, in <module>
2015-12-03T13:21:53+0530 [Controller  77106]     from crossbar.twisted.resource import StaticResource, StaticResourceNoListing
2015-12-03T13:21:53+0530 [Controller  77106]   File "/Library/Python/2.7/site-packages/crossbar/twisted/resource.py", line 42, in <module>
2015-12-03T13:21:53+0530 [Controller  77106]     from autobahn.twisted import longpoll
2015-12-03T13:21:53+0530 [Controller  77106] ImportError: cannot import name longpoll

@oberstet any specific reason for closing?

looks like this is an issue with autobahn 0.11.0. Reverting to 0.10.9 seems to solve it. Unfortunately as crossbar doesn't pin it's version this will remain broken until autobahn fixes its breaking interface or crossbar pins to 0.10.9

Looks like longpoll was moved to crossbar, so also upgrading crossbar to master would likely work. But yes, until there's a release of crossbar with longpoll in it, downgrading autobahn is likely the best option ...

This is likely to break older versions of crossbar (I'm using crossbar 0.11.0) as well as it doesn't pin a version of autobahn in its dependencies. BTW, where can I find release notes so I can see what changed in 0.11.1?

I have this issue also, why closing it ?

+1

+1

yeah, sorry. fixed in https://pypi.python.org/pypi/crossbar/0.11.2

@voidabhi @remisharrock I misunderstood the issue (wasn't looking closely enough) - it's a crossbar/autobahn version incompat.
@stopthatcow we totally should have release notes;) - means: there are none. crossbar is still moving fast, and we (as a project) simply don't have the resources for everything. a lame excuse, I know. sorry.

@stopthatcow For a quick-and-dirty idea of what changes between tags, it's of course possible via Git: "git log --oneline v0.11.0..v0.11.2". We've also been using "milestones" on GitHub more recently, so that can give you a clue as to which issues went into which release. I know neither of those replace proper release-notes :/
...and if you have the motivation, a PR against docs/changelog.rst would be a great way to contribute to the project! :)

Thanks @meejah looks like I will be trying out 0.11.2


Add an action to publish the grammar automatically

This PR allows to publish automatically tree-sitter-python on crates.io when a new tag is set.
Thanks in advance for your review! :)

@tausbn
What's the status of this PR?

I have no opinion on this PR. (I mostly concern myself with fixing bugs inside the grammar itself. Decisions about the the administrative aspects of tree-sitter-python are somewhat outside my area of expertise.)
Maybe @maxbrunsfeld could weigh in on it?

Hello @tausbn and sorry for the late reply
@maxbrunsfeld has already given consent to this action here for tree-sitter-java language

Will supersede with my own soon


Fix Package version

Its breaking earlier functionality of library. Its not backward compatible. So, Please update major version instead of updating minor version.
Thanks !

thanks. I didn't think this would break anything, but if people are using require().default in there code, this would break it. Thanks for the PR. I'm going to unpublish 1.4.0


pyvista vulnerability fixed in version 0.39.0

Related to this: https://github.com/pyansys/pyfluent/issues/1552
As identified by akaszynski, there is also a new VTK version in the works that fixes another vulnerability on zlib (https://gitlab.kitware.com/vtk/vtk/-/issues/18962). Need to wait until that one is released to update this here as well.

Realized we are going to need to update the python requirement as well, going to take a look at it

I think it should work now, bumped VTK version too, to remove a function that isn't necessary anymore as requested by @mkundu1
Will need to update VTK version again once the vulnerability fix mentioned in the original post gets to a release version
Going to clean up the commented code if all the checks succeed


Minor fixes of compatibility issues and some cleanup.

Coverage decreased (-0.5%) to 89.246% when pulling f0cb153968d7a06612d3565ee02b96d25112c852 on michakraus:master into 5e97930c6e5b1d4361d45f5aef3199302d5e5de8 on DDMGNI:master.

Coverage decreased (-0.5%) to 89.246% when pulling f0cb153968d7a06612d3565ee02b96d25112c852 on michakraus:master into 5e97930c6e5b1d4361d45f5aef3199302d5e5de8 on DDMGNI:master.

Coverage decreased (-0.5%) to 89.246% when pulling f0cb153968d7a06612d3565ee02b96d25112c852 on michakraus:master into 5e97930c6e5b1d4361d45f5aef3199302d5e5de8 on DDMGNI:master.


⚠ sandbox-api.piste.gouv.fr healthcheck has degraded performance

In ce85270, sandbox-api.piste.gouv.fr healthcheck (https://sandbox-api.piste.gouv.fr/cassation/judilibre/v1.0/healthcheck) experienced degraded performance:

HTTP code: 200
Response time: 2584 ms

Resolved: sandbox-api.piste.gouv.fr healthcheck performance has improved in cb73962.


docs: add api_rst which stores the autogenerated rst files to gitignore

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 86.559%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
7599

Relevant Lines:
8779

💛  - Coveralls


[devtools] add note about canary in WNDT64

What's changed, or what was fixed?

explain how readers can use the local overrides feature right now via canary

Fixes: N/A
Target Live Date: 2018-02-08 (today)

[x] This has been reviewed and approved by @kaycebasques (me)
[x] I have run gulp test locally and all tests pass. (travis build passed)
[x] I have added the appropriate type-something label.
[x] I've staged the site and manually verified that my content displays correctly. (verified on staging)

CC: @petele

Whoops!
There were 1 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2017/11/devtools-release-notes.md#L170 - Updates post is missing comment widget: {% include "comment-widget.html" %}

:tada: This has been pushed live to https://developers.google.com/web/


on teacher launch, don't load default unit

this also includes various refactoring to simplify things

This PR lowers the test coverage percent slightly. This is because much of the code requires a portal launch and tests that do these portal launches have proven flakey. If we have time in the future we could refactor some of the authentication code so the demo, qa, and dev appModes faked the authentication at a lower level, then we could cover more of this code without needing to launch from the portal.


Game Won't Launch

Describe the bug
Once you click launch, a "BH3" program appears in Task Manager, but the game does not start.
To Reproduce
1 - Open Launcher
2 - Click Launch (I am using SEA)
Expected behavior
The game should launch upon clicking launch.
Log
BetterHI3Launcher v1.5.20231203.0
Working directory: D:\Games\Honkai Impact\Honkai Impact 3
OS version: Windows 10 Pro (Version 22H2, Build 19045.3693)
OS language: en-GB
Launcher language: en (autodetect)
Using server: SEA
Using mirror: HoYoverse
Checking for game update...
Game version: 7.0.0
Game directory: D:\Games\Honkai Impact\Honkai Impact 3
Screenshots

The game launches normally for me, pls close the game via Task Manager and try running it again or reboot your PC.

I tried closing via Task Manager, I will restart my PC and let you know if that resolves the issue.


Certificates

We will need to do this when there is a domain. I'm not sure how to set this up for a new user that is doing the deployment, other than to provide instruction.
letsencrypt.com
https://gethttpsforfree.com

This is done, next issues at hand are #9 and #8


Add table azure_spring_cloud_app Closes #713

Integration test logs

Logs
No env file present for the current environment:  staging
 Falling back to .env config
No env file present for the current environment:  staging
customEnv TURBOT_TEST_EXPECTED_TIMEOUT undefined

SETUP: tests/azure_spring_cloud_app []

PRETEST: tests/azure_spring_cloud_app

TEST: tests/azure_spring_cloud_app
Running terraform

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # azurerm_resource_group.named_test_resource will be created
  + resource "azurerm_resource_group" "named_test_resource" {
      + id       = (known after apply)
      + location = "eastus"
      + name     = "turbottest95879"
    }

  # azurerm_spring_cloud_app.named_test_resource will be created
  + resource "azurerm_spring_cloud_app" "named_test_resource" {
      + fqdn                = (known after apply)
      + https_only          = false
      + id                  = (known after apply)
      + is_public           = false
      + name                = "turbottest95879"
      + resource_group_name = "turbottest95879"
      + service_name        = "turbottest95879"
      + tls_enabled         = false
      + url                 = (known after apply)

      + identity {
          + principal_id = (known after apply)
          + tenant_id    = (known after apply)
          + type         = "SystemAssigned"
        }
    }

  # azurerm_spring_cloud_service.named_test_resource will be created
  + resource "azurerm_spring_cloud_service" "named_test_resource" {
      + id                             = (known after apply)
      + location                       = "eastus"
      + name                           = "turbottest95879"
      + outbound_public_ip_addresses   = (known after apply)
      + required_network_traffic_rules = (known after apply)
      + resource_group_name            = "turbottest95879"
      + sku_name                       = "S0"
    }

Plan: 3 to add, 0 to change, 0 to destroy.

 Resources: 3 added, 0 changed, 0 destroyed.

Outputs:

region = "eastus"
resource_aka = "azure:///subscriptions/3510ae4d-530b-497d-8f30-53b9616fc6c1/resourceGroups/turbottest95879/providers/Microsoft.AppPlatform/Spring/turbottest95879"
resource_aka_lower = "azure:///subscriptions/3510ae4d-530b-497d-8f30-53b9616fc6c1/resourcegroups/turbottest95879/providers/microsoft.appplatform/spring/turbottest95879/apps/turbottest95879"
resource_id = "/subscriptions/3510ae4d-530b-497d-8f30-53b9616fc6c1/resourceGroups/turbottest95879/providers/Microsoft.AppPlatform/Spring/turbottest95879/apps/turbottest95879"
resource_name = "turbottest95879"
subscription_id = "3510ae4d-530b-497d-8f30-53b9616fc6c1"

Running SQL query: test-get-query.sql
Warning: terminal options has been deprecated and will be removed in a future version of Steampipe.
These can now be set in a steampipe workspace.
(/Users/parthas/.steampipe/config/default.spc:34,20-42,2)
[
  {
    "id": "/subscriptions/3510ae4d-530b-497d-8f30-53b9616fc6c1/resourceGroups/turbottest95879/providers/Microsoft.AppPlatform/Spring/turbottest95879/apps/turbottest95879",
    "name": "turbottest95879",
    "region": "eastus",
    "resource_group": "turbottest95879",
    "subscription_id": "3510ae4d-530b-497d-8f30-53b9616fc6c1"
  }
]
✔ PASSED

Running SQL query: test-list-query.sql
Warning: terminal options has been deprecated and will be removed in a future version of Steampipe.
These can now be set in a steampipe workspace.
(/Users/parthas/.steampipe/config/default.spc:34,20-42,2)
[
  {
    "id": "/subscriptions/3510ae4d-530b-497d-8f30-53b9616fc6c1/resourceGroups/turbottest95879/providers/Microsoft.AppPlatform/Spring/turbottest95879/apps/turbottest95879",
    "name": "turbottest95879",
    "region": "eastus",
    "resource_group": "turbottest95879",
    "subscription_id": "3510ae4d-530b-497d-8f30-53b9616fc6c1"
  }
]
✔ PASSED

Running SQL query: test-not-found-query.sql
Warning: terminal options has been deprecated and will be removed in a future version of Steampipe.
These can now be set in a steampipe workspace.
(/Users/parthas/.steampipe/config/default.spc:34,20-42,2)
[]
✔ PASSED

Running SQL query: test-turbot-query.sql
Warning: terminal options has been deprecated and will be removed in a future version of Steampipe.
These can now be set in a steampipe workspace.
(/Users/parthas/.steampipe/config/default.spc:34,20-42,2)
[
  {
    "akas": [
      "azure:///subscriptions/3510ae4d-530b-497d-8f30-53b9616fc6c1/resourceGroups/turbottest95879/providers/Microsoft.AppPlatform/Spring/turbottest95879/apps/turbottest95879",
      "azure:///subscriptions/3510ae4d-530b-497d-8f30-53b9616fc6c1/resourcegroups/turbottest95879/providers/microsoft.appplatform/spring/turbottest95879/apps/turbottest95879"
    ],
    "name": "turbottest95879",
    "title": "turbottest95879"
  }
]
✔ PASSED

TEARDOWN: tests/azure_spring_cloud_app

SUMMARY:

1/1 passed.

Example query results

Results
> select * from azure_spring_cloud_app
+--------+-----------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------+---------------+----------+--------+--------------------+------------------------>
| name   | id                                                                                | type                              | service_name  | location | public | provisioning_state | created_time           >
+--------+-----------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------+---------------+----------+--------+--------------------+------------------------>
| test34 | /subscriptions/3510ae4d-530b-497d-8f30-53b9616fc6c1/resourceGroups/turbot_rg/providers/Microsoft.AppPlatform/Spring/testservice43/apps/test34 | Microsoft.AppPlatform/Spring/apps | testservice43 | eastus   | false  | Succeeded          | 2024-01-15T20:40:46+05:>
| testpy | /subscriptions/3510ae4d-530b-497d-8f30-53b9616fc6c1/resourceGroups/turbot_rg/providers/Microsoft.AppPlatform/Spring/testservice43/apps/testpy | Microsoft.AppPlatform/Spring/apps | testservice43 | eastus   | false  | Succeeded          | 2024-01-15T20:40:46+05:>
+--------+-----------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------+---------------+----------+--------+--------------------+------------------------>

> select * from azure_spring_cloud_app where name = 'test34' and service_name = 'testservice43' and resource_group = 'turbot_rg'
+--------+-----------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------+---------------+----------+--------+--------------------+------------------------>
| name   | id                                                                                | type                              | service_name  | location | public | provisioning_state | created_time           >
+--------+-----------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------+---------------+----------+--------+--------------------+------------------------>
| test34 | /subscriptions/3510ae4d-530b-497d-8f30-53b9616fc6c1/resourceGroups/turbot_rg/providers/Microsoft.AppPlatform/Spring/testservice43/apps/test34 | Microsoft.AppPlatform/Spring/apps | testservice43 | eastus   | false  | Succeeded          | 2024-01-15T20:40:46+05:>
+--------+-----------------------------------------------------------------------------------------------------------------------------------------------+-----------------------------------+---------------+----------+--------+--------------------+-----------------------

Currently, the table utilizes the AppsClient.List API call with the 2020-07-01 API version, which has been deprecated.
Attempting to make the API call with the 2020-07-01 version results in an UnsupportedApiVersion error.
According to Azure's API documentation, the current API version is 2023-12-01. The API version is working fine until 14th January 2024.
To integrate this table, it's necessary to adopt the package github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/appplatform/armappplatform.
Updating the SDK used by the Steampipe plugin for Azure is required, which may introduce breaking changes.

This PR is therefore being marked as on hold.


Create a "bot" yewstack account

Current publish actions in this repo do not work because they cant push to master branch bump commits.
To fix it a @yewstack/core-maintainers person needs to:

[ ] Create a bot account
[ ] Give it permissions to push to yew master branch
[ ] Create a personal access token using it
[ ] Put the token in github serects
[ ] Let me know how its called so that I can update the github actions for releasing

And then we can finally release yew.

BEEP BOOP


#585: migrate to private ips

PR for #585.

add private_ip() for AWS and GCP
use private ips for GCP to GCP data transfer
Also add fix for #603

Private ips for GCP throughput profiling is in #605

Can you profile a typical GCP to GCP transfer before+after this change?

@parasj Here's an example of transferring 9GB of data from gcp to gcp.
Before (using public ips): transfer runtime = 17.18s, throughput = 4.23 Gbps

After (using private ips): transfer runtime = 10.29s, throughput = 7.06 Gbps

There's around 1.7x throughput improvement and 40% runtime reduction

Great! glad to see it helps so much


Possible Error in "RandRangeDemo" function

While trying to learn about the "rand" function for C, came across a possible
error with the example function "RandRangeDemo."
Function appears to be producing a result which is
-1 * [range_min, range_max)

rather than the intended result of
[range_min, range_max)

I believe this to be due to this line of code:
int u = (double)rand() / (RAND_MAX + 1) * (range_max - range_min)+ range_min;

" (RAND_MAX+1) " appears to be causing an integer overflow or some other similar effect.
Testing appears to show that to achieve the intended result, the line should be
changed to " (RAND_MAX - 1) ."
In full, the line (with the suggested change) would read:
int u = (double)rand() / (RAND_MAX - 1) * (range_max - range_min)+ range_min;

Here is a link to the page in which I did the testing:
Link to test of Example Implementation
I hope this helps resolve this error, and I wish you all a pleasant day!

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

ID: d29a1829-6726-2b46-a3f1-647732a81083
Version Independent ID: 7f066cc1-c72e-3b2d-1453-9b420e0afab9
Content: rand
Content Source: docs/c-runtime-library/reference/rand.md
Product: visual-cpp
Technology: cpp-ucrt
GitHub Login: @TylerMSFT
Microsoft Alias: twhitney

Hi @Al-B-Bach (great user name :-)
I didn't reproduce your problem, but updated the sample to remove the +1. What I think that's about is an attempt to lessen the bias of not selecting the highest value in the range. This approach is fraught with problems:

rand() is low quality and has a small output range, which means that it isn't suitable for generating values across a large range.
using srand() to seed with time(nullptr) has multiple problems, including introducing data loss when converting from the time_t to the unsigned int taken by srand(), and the fact that if you run this twice within the period of a second, the seed will be the same.
using the formula in this sample will result in a non-uniform distribution.
For more info about these issues, I recommend this talk: rand() considered harmful. If you must use the CRT library rand() function, I'm not aware of anything better. But if you can use the C++ library  functions, you'll be better off if you need high quality random numbers.  Here's an example of how you could do it with that library:

#include <iostream>
#include <random>

int main() {
    std::random_device rd; // cryptographically secure (in MSVC's implementation)
    const unsigned int seed = rd(); // 32-bit seed; production usage may need more entropy

    // A fresh seed is generated every time this program runs.
    // This is better than calling time(nullptr).

    std::mt19937 engine{seed}; // fast, but not cryptographically secure; know the difference for production usage

    // Calling engine() directly will generate a random 32-bit value.
    // We should NOT use the modulo operator (the % operator) to transform this to a desired range,
    // as that will produce biased results (some values will be more likely than others).
    // Instead, std::uniform_int_distribution will produce uniform results (all values equally likely).

    std::uniform_int_distribution<int> d20{1, 20}; // we want values 1 through 20, inclusive

    // Now we can simply call d20(engine) to use the engine and the distribution object together:

    std::cout << "Rolling a 20-sided die: ";

    for (int i = 0; i < 50; ++i) {
        std::cout << d20(engine) << ", ";
    }

    std::cout << "done!\n";
}

The update I made to the topic should be live by the weekend. Closing now.


Option for docstring to not add empty lines and indentation at end

Issue Report Checklist

[x] Searched the issues page for similar reports
[x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[x] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[x] Could not reproduce inside jupyter qtconsole (if console-related)
[x] Tried basic troubleshooting (if a bug/error)

[x] Restarted Spyder
[x] Reset preferences with spyder --reset
[x] Reinstalled the latest version of Anaconda
[x] Tried the other applicable steps from the Troubleshooting Guide

[x] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
Docstring created with Ctrl+Alt+D has two new lines and an indentation at the end of the inserted docstring.
Please, add checkbox to Preferences / Editor / Advanced settings / Docstring type with the label No empty lines at end that by default is not checked. This will save the developer navigating to the end of the relevant part and hitting minimally ten times the delete button.
What steps reproduce the problem?

Open a Python file with a function, method or class declaration.
Navigate to the first line of it.
Press Cltr+Alt+D

What is the expected output? What do you see instead?
Expected:
    def credentials(filename: str, parent: bool = False) -> dict:
        """

        :param filename: DESCRIPTION
        :type filename: str
        :return: DESCRIPTION
        :rtype: dict"""

instead:
    def credentials(filename: str, parent: bool = False) -> dict:
        """

        :param filename: DESCRIPTION
        :type filename: str
        :return: DESCRIPTION
        :rtype: dict

        """

Paste Traceback/Error Below (if applicable)
n/a
Versions

Spyder version: 5.5.3  (pip)
Python version: 3.10.12 64-bit
Qt version: 5.15.2
PyQt5 version: 5.15.10
Operating System: Linux-6.8.0-76060800daily20240311-generic-x86_64-with-glibc2.35

Dependencies
n/a

Hi @PanderMusubi thank you for the feedback! If I understand correctly, what you would like for the generated docstring is for it to look something like:
    def credentials(filename: str, parent: bool = False) -> dict:
        """

        :param filename: DESCRIPTION
        :type filename: str
        :return: DESCRIPTION
        :rtype: dict
        """

right? Seems like a \n is missing over the example provided.
What do you think @spyder-ide/core-developers ?


Add double click function to BREAD row

Add a way the user can navigate through the BREAD views. By double
clicking the row, the user goes to the view or edit page, depending
on their rights. To simplify the way to delete a single item, add a
delete button in the browse view if the user has rights to delete it.
Fixes https://github.com/the-control-group/voyager/issues/2333

Could be cool, but you modified a lot of lines by reindenting them. You shouldn't commit spaces change I think.

@SteamWind I tried to improve the indenting to make lots of lines more readable. Do you think I should undo the improvements or leave it as it is right now?

Hey @emptynick,
I corrected my mistake, could you give it another review?
Kind regards

The delete part was token care of elsewhere. I suggest you remove it completely.

Closing as this PR wasn't touched for nearly a year and there are still requested changes.
If someone else want's to implement this functionality please open a new PR.


Ignore label/annotation checking if not included in template

Signed-off-by: Will Kutler<EMAIL_ADDRESS>Fixes a bug where if a mustonlyhave policy without any annotations or labels specified was set to enforce, the controller would try to remove any autogenerated annotations in the object. These annotations would therefore be repeatedly removed and generated again, which made mustonlyhave policies use significantly more CPU than they needed to.

Can you add some test cases to ensure it does skip checking labels/annotations when they are not specified in the policy using mustonlyhave?

@willkutler can you rebase?


[#170234614] refactor build system and docs

This PR lets you run the frontend application seamlessy with or without docker with hot module reloading enabled in both cases.

Warnings

:warning:
This PR changes a total of 634 LOCs, that is more than a reasonable size of 250. Consider splitting the pull request into smaller ones.

Messages

:book:
:tada: - congrats on your new release

Affected stories

🌟 #170234614: Come DEV voglio poter sviluppare in locale il frontend utilizzando dei dati fittizi

New dependencies added: dotenv-cli, npm-run-all, parcel-plugin-html-externals and shx.
dotenv-cli
Author: entropitor
Description: A global executable to run applications with the ENV variables loaded by dotenv
Homepage: https://github.com/entropitor/dotenv-cli#readme

Createdover 4 years agoLast Updated21 days agoLicenseMITMaintainers1Releases10Direct Dependenciescross-spawn, dotenv, dotenv-expand and minimist

README
dotenv-cli
Installing
NPM
$ npm install -g dotenv-cli

Yarn
$ yarn global add dotenv-cli

Usage
$ dotenv <command with arguments>

This will load the variables from the .env file in the current working directory and then run the command (using the new set of environment variables).
Custom .env files
Another .env file could be specified using the -e flag:
$ dotenv -e .env2 <command with arguments>

Multiple .env files can be specified, and will be processed in order:
$ dotenv -e .env3 -e .env4 <command with arguments>

Check env variable
If you want to check the value of an environment variable, use the -p flag
$ dotenv -p NODE_ENV

Flags to the underlying command
If you want to pass flags to the inner command use -- after all the flags to dotenv-cli.
E.g. the following command without dotenv-cli:
mvn exec:java -Dexec.args="-g -f"

will become the following command with dotenv-cli:
$ dotenv -- mvn exec:java -Dexec.args="-g -f"

or in case the env file is at .my-env
$ dotenv -e .my-env -- mvn exec:java -Dexec.args="-g -f"

Variable expansion
We support expanding env variables inside .env files (See dotenv-expand npm package for more information)
For example:
IP=<IP_ADDRESS>
PORT=1234
APP_URL=http://${IP}:${PORT}

Using the above example .env file, process.env.APP_URL would be http://<IP_ADDRESS>:1234.
License
MIT

npm-run-all
Author: Toru Nagashima
Description: A CLI tool to run multiple npm-scripts in parallel or sequential.
Homepage: https://github.com/mysticatea/npm-run-all

Createdover 4 years agoLast Updated13 days agoLicenseMITMaintainers1Releases58Direct Dependenciesansi-styles, chalk, cross-spawn, memorystream, minimatch, pidtree, read-pkg, shell-quote and string.prototype.padendKeywordscli, command, commandline, tool, npm, npm-scripts, run, sequential, serial, parallel and task

README

index
npm-run-all
run-s
run-p
Node API

npm-run-all

A CLI tool to run multiple npm-scripts in parallel or sequential.
⤴ Motivation

Simplify. The official npm run-script command cannot run multiple scripts, so if we want to run multiple scripts, it's redundant a bit. Let's shorten it by glob-like patterns.
Before: npm run clean && npm run build:css && npm run build:js && npm run build:html
After: npm-run-all clean build:*
Cross platform. We sometimes use & to run multiple command in parallel, but cmd.exe (npm run-script uses it by default) does not support the &. Half of Node.js users are using it on Windows, so the use of & might block contributions. npm-run-all --parallel works well on Windows as well.

💿 Installation
$ npm install npm-run-all --save-dev
# or
$ yarn add npm-run-all --dev

It requires Node@>=4.

📖 Usage
CLI Commands
This npm-run-all package provides 3 CLI commands.

npm-run-all
run-s
run-p

The main command is npm-run-all.
We can make complex plans with npm-run-all command.
Both run-s and run-p are shorthand commands.
run-s is for sequential, run-p is for parallel.
We can make simple plans with those commands.
Yarn Compatibility
If a script is invoked with Yarn, npm-run-all will correctly use Yarn to execute the plan's child scripts.
Node API
This npm-run-all package provides Node API.

Node API

📰 Changelog

https://github.com/mysticatea/npm-run-all/releases

🍻 Contributing
Welcome♡
Bug Reports or Feature Requests
Please use GitHub Issues.
Correct Documents
Please use GitHub Pull Requests.
I'm not familiar with English, so I especially thank you for documents' corrections.
Implementing
Please use GitHub Pull Requests.
There are some npm-scripts to help developments.

npm test - Run tests and collect coverage.
npm run clean - Delete temporary files.
npm run lint - Run ESLint.
npm run watch - Run tests (not collect coverage) on every file change.

parcel-plugin-html-externals
Author: stoically
Description: ParcelJS plugin to ignore certain script and stylesheet link tags in html files marked as externals
Homepage: https://github.com/stoically/parcel-plugin-html-externals#readme

Created5 months agoLast Updated5 months agoLicenseMITMaintainers1Releases3Direct Dependenciesminimatch

README
ParcelJS plugin to ignore certain script and stylesheet link tags in html files marked as externals.

Parcel will probably support externals out of the box in the future, related issue here.

Install
npm install --save-dev parcel-plugin-html-externals

Usage
Put an externals key into your package.json, e.g.
{
  "externals": {
    "vendor/**/*": false
  }
}

will ignore all script / stylesheet link tags whose src / href attribute starts with vendor/, e.g
<script src="vendor/thirdparty.min.js"></script>

The externals key can be a string or any glob accepted by minimatch,
the value must be false to trigger ignoring.
Caveats
The plugin monkey patches Parcel internals by extending the HTMLAsset class and proxying its ast walker, so it might just break in an upcoming version.
License
MIT

shx
Author: Unknown
Description: Portable Shell Commands for Node
Homepage: https://github.com/shelljs/shx#readme

Createdover 3 years agoLast Updatedover 1 year agoLicenseMITMaintainers2Releases11Direct Dependencieses6-object-assign, minimist and shelljsKeywordsshelljs, shell, unix, bash, sh, exec, cli and zsh

README
Shx

shx is a wrapper around ShellJS Unix
commands, providing an easy solution for simple Unix-like, cross-platform
commands in npm package scripts.
Difference Between ShellJS and shx

ShellJS: Good for writing long scripts, all in JS, running via NodeJS (e.g. node myScript.js).
shx: Good for writing one-off commands in npm package scripts (e.g. "clean": "shx rm -rf out/").

Install
npm install shx --save-dev

This will allow using shx in your package.json scripts.
Usage
Command Line
If you'd like to use shx on the command line, install it globally with the -g flag.
The following code can be run either a Unix or Windows command line:
$ shx pwd                       # ShellJS commands are supported automatically
/home/username/path/to/dir

$ shx ls                        # files are outputted one per line
file.txt
file2.txt

$ shx rm *.txt                  # a cross-platform way to delete files!

$ shx ls

$ shx echo "Hi there!"
Hi there!

$ shx touch helloworld.txt

$ shx cp helloworld.txt foobar.txt

$ shx mkdir sub

$ shx ls
foobar.txt
helloworld.txt
sub

$ shx rm -r sub                 # options work as well

$ shx --silent ls fakeFileName  # silence error output

All commands internally call the ShellJS corresponding function, guaranteeing
cross-platform compatibility.
package.json
ShellJS is good for writing long scripts. If you want to write bash-like,
platform-independent scripts, we recommend you go with that.
However, shx is ideal for one-liners inside package.json:
{
  "scripts": {
    "clean": "shx rm -rf build dist && shx echo Done"
  }
}

Unsupported Commands
Due to the differences in execution environments between ShellJS and shx (JS vs CLI) some commands are not supported:

Unsupported command
Recommend workaround

shx cd
Just use plain old cd (it's the same on windows too)

shx pushd
Just use plain old pushd. Use forward slashes and double-quote the path. (e.g. pushd "../docs". This would fail on Windows without the quotes)

shx popd
Just use plain old popd

shx dirs
No workaround

shx set
See below

shx exit
Just use plain old exit

shx exec
Instead of shx exec cmd, just use plain old cmd

shx ShellString
No workaround (but why would you want this?)

Shx options
Shx allows you to modify its behavior by passing arguments. Here's a list of
supported options:

set flag
shell.config setting
shx command
Effect

-e
config.fatal = true
Not supported
Exit upon first error

-v
config.verbose = true
shx --verbose cd foo
Log the command as it's run

-f
config.noglob = true
shx --noglob cat '*.txt'
Don't expand wildcards

N/A
config.silent = true
shx --silent cd noexist
Don't show error output

Team

Nate Fischer
Ari Porad
Levi Thomason

  Generated by :no_entry_sign: dangerJS against 979f3f50d475af47dedb603a1e805b74567db521

The docker part seems not to work properly. At least following the steps in the README. Seems that or the port are not exposed from the containers but the host from localhost seems unreachable. The browser is not able to find the provided url and keep trying.

this sounds odd since the ports are exposed inside docker-compose.yml. can you please do some debugging ? (which OS are you running as host ?)

Instead the part without docker works.

Sorry, on my tired mac os x has taken some minutes before completely start with docker. In the end works also the docker compose. Great!!!!!


Please review

This is a new repository that provides a ctypes interface to the Shibutani Fortran receiver function code. The expectation is that this will free us from use of f2p in CoFI, which is used by the current espresso version. I think it all works, but would appreciate any feedback on bugs or issues. Indeed feel free to just fix them and update.

I created a new environment using mamba and tried to install the package with pip. At first, I encountered errors, which I resolved by installing gfortran in my environment with:
mamba install gfortran

I was then able to successfully install the package with:
pip install git+https://github.com/inlab-geo/pyrf96

In Python, I tried to import the library by typing:
import pyrf96

However, I got errors due to missing dependencies (numpy and matplotlib). After installing these dependencies, I was able to run the example on the homepage.
This suggests that it would be beneficial to have a setup.py file listing all required dependencies, so they are automatically installed if missing when pip-installing the package.

The dependencies go in the pyproject.toml.  I'm on it

There's an issue with editable installs pip install -e . but that can be ignored for now.

Whats an editable install?

It means when you're developing a python package you don't have to keep doing pip install . when ever you make changes and want to run tests.  It basically puts a link in your environment to your working directory rather than doing a full install of the package.


ubuntu-22.04 / 20240609.1.0 issues with IPv6 DNS resolution inside container

Description
Somewhat related to #10061, we're seeing occasional DNS resolution issues of some of our internal domains when trying to resolve inside a container that do not occur on the runner itself since upgrading - tcpdump of the runner shows only AAAA lookups being performed.  We use a This seems to be related to the docker version upgrade as well, and when forcfully downgrading docker <26 this is resolved.
This is with IPv6 forcefully disabled on the host prior to the runner agent starting, eg.:
sysctl -w net.ipv6.conf.all.disable_ipv6=1
sysctl -w net.ipv6.conf.default.disable_ipv6=1
sysctl -w net.ipv6.conf.lo.disable_ipv6=1

tcpdump of the AAAA requests being made:

Platforms affected

[ ] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] Ubuntu 24.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
20240609.1.0
Is it regression?
yes - did not exist in 20240603.1
Expected behavior
As the host does not have an ipv6 interface and the sysctl's explicitly have ipv6 disabled, prior to docker starting, we would've expected this not to happen
Actual behavior
AAAA DNS calls are being made, resulting in DNS resolution failures
Repro steps
inside a container on a host with runner image 20240609.1.0, curl http://some-domain-without-ipv6-results.

@samjarrett - Thank you for bringing this issue to us. We are looking into this issue, we will update you on this issue after investigating the error you have faced.

As an update, we tried the following to 100% disable ipv6 in the kernel:
echo 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash ipv6.disable=1"' > /etc/default/grub.d/10-disable-ipv6.cfg
update-grub

And still get the same issue.

@samjarrett - You can try with the below approach -
you can lower the priority of IPv6 addresses by making changes to the /etc/gai.conf file, there should be enough to add the line "precedence ::ffff:0:0/96 100"
Please let us know once you try it.

@ijunaidm in the container? Or on the host? The host has ipv6 disabled at a kernel level - I don't see what this would achieve?

@samjarrett - yes, in the docker container. Try this workaround it may work for you.

I don't think reconfiguring networking inside a container is a viable solution to ask of people?

@ijunaidm hello - as an update, we added the change to /etc/gai.conf on the machine and it continues to fail. I've realised that this only seems to be alpine-based container images that have this issue. Specifically,  we're seeing it most commonly on node:20-alpine.

@samjarrett - Okay. Its basically from the Docker update (with docker 26 ) and probably Docker will not roll back to the previous version. We cannot do much on this as this is from the Docker . I am Closing this issue. Thank you.


print-file two times in a row crashes the frontend

The dialog exits after printing, so it won't matter.


New theme: Huginn

Theme submission
Before submitting a theme please make sure you've read the README.md. It describes in detail what information are needed and which requirements have to be fulfilled for the submission. The check list below can help you.
Link to my theme repository: https://framagit.org/staticman-gitlab-pages/huginn
:memo: Edited: I've just exported my Framagit repo to GitLab.com, where some themes are uploaded: https://gitlab.com/VincentTam/huginn.
I made sure that...

[x] the repository contains a good README.md describing my theme
[x] an open source license has been added to LICENSE.md
[x] all metadata have been added to theme.toml
[x] screenshots have been added in the images/ folder with the required dimensions
[x] in case I'm using a customized demo via the exampleSite folder that

[x] https://example.com is set as base url in exampleSite/config.{toml, yaml, json} to avoid the abuse of unused domains
[x] I tested that my theme's demo works with the content directory of gohugoio/HugoBasicExample

[x] I tested my theme against the gohugoio/HugoBasicExample

[x] I've checked the developer tools' console in my browser for error messages

[x] in case my theme is using Hugo Pipes features like toCSS and PostCSS that I have committed the /resources directory with all generated assets, for my theme to work in the basic version of Hugo

Feel free to ask questions. We're glad to help.

Hello @VincentTam
Before proceeding with the review can you please tell me a bit about the git provider that you use https://framagit.org/ ?
I am asking because as you've probably seen in the theme submission guidelines we do not allow self-hosted git repositories.

Most of the themes in this repo are hosted on GitHub. We also include themes hosted on GitLab and similar, but we do not add themes living on a self-hosted repository.

Kindly let me know or point me to a link where I can read more about the framagit service.
Thanks.

As you've probably seen in the theme submission guidelines we do not allow self-hosted git repositories.

Thanks for pointing me the README.  Reading the Hugo docs page about new theme submission, I didn't see the README there.
In fact, Framagit is a fork of the software GitLab hosted by a non-profit company Framasoft.
It's docs page is a better page for reference.

Framagit est la forge logicielle de Framasoft reposant sur le logiciel Gitlab.
Elle est ouverte à tous, dans la limite de 42 projets par personne.

Here's another piece of info about the name of Framasoft: https://github.com/Pyromaths/pyromaths/issues/26.

le MA de FRAMAGIT signifie mathématiques :) (à l'origine, framasoft est un annuaires de logiciels SOFT pour le français FRA et les maths MA) ;

Framasoft = French + math + software
Anyways, lemme change it to GitLab.com.

@VincentTam
Thank you for changing the repo.
When I test your theme's demo with the Hugo Themes Build Script it renders, however I have noticed the following issues:

Please replace all instances of https://framagit.org/staticman-gitlab-pages/hugo-theme-huginn/ with https://gitlab.com/VincentTam/huginn so that the links in theme.toml and in your theme's README resolve to the new repo.

The description parameter in line 7 of theme.toml needs to be only plain text. So please remove the markdown link to the Pelican theme that inspired you. You already mention this theme in the README there is no need to mention it in the description.

Your theme's demo content will be inherited from the Hugo Basic Example repo. Due to the requirements of various themes in that repo we have a /posts/ section with the actual content files and a /post/ section with symlinks to the content files under /posts/.

The way that you have chosen to populate your posts list on the index page of the theme demo has the side effect of displaying all content twice, both the actual content under https://github.com/gohugoio/hugoBasicExample/content/posts/ and the symlinks under https://github.com/gohugoio/hugoBasicExample/content/post/.
To fix the above we need to use the mainSections internal parameter.
So please replace line 2 of /layouts/index.html to the following:
{{- $paginator := .Paginate (where site.RegularPages "Type" "in" site.Params.mainSections) 5 -}}
{{- range $paginator.Pages -}}

Once you do the above please let me know so that I can test your theme further.
Thanks

@onedrawingperday Thanks for your code example.  Suggestion done @dc5a80f7a.

@VincentTam
Thank you for committing the changes.
There is only the matter of the link in the footer that still points to https://framagit.org/staticman-gitlab-pages/huginn I suggest that from within the huginn/tree/master/i18n folder you perform a recursive search & replace with your favorite editor so that you make the link point to the GitLab repo of your theme.

@onedrawingperday Excuse me for such careless mistakes.  Done at my recent commit.  Now, the only reference to Framagit is the Framagit bot of Staticman called "@staticmanlab1".  All screenshots have been replaced with a GitLab.com domain name.  Thanks for your feedback.

@VincentTam Thanks you!
@digitalcraftsman This theme is ready to be added to the showcase when you can.

Hello Vincent,
thank you for sharing this theme with the Hugo community. Your theme should be listed soon on the themes site.
Furthermore, I'll promote your theme on Hugo's official Twitter account.


[FLOC-3377] Drop sleep workaround

This adds a test for datasets being attached before container is restarted by container agent, and removes 120 second sleep on startup which is no longer necessary because of previous work.

See http://build.clusterhq.com/boxes-flocker?branch=drop-sleep-workaround-FLOC-3377

Cool test idea, hopefully it works on buildbot without raising havoc :+1:
I do have 1 request to rename reboot.py as it seems to not actually do any rebooting. Also some concern that this test might not verify that the original problem that forced us to add the 120s sleep is tested? I don't know the specifics of that issue, but I was surprised there weren't any cluster health checks at the end. Actually thinking about it again now perhaps the mere presence of the reboot.py job being brought back up is evidence enough that the cluster is healthy? Maybe just add a comment in that case.
Probably wait for tests to be green and address and merge at will. Thanks!

The original issue was that after reboot it takes some amount of time reattach cloud volume to machine. Meanwhile, container agent might rely on stale data from the control service that says dataset is already there, and so start the container too soon.

If I disable 120 second sleep and add a sleep to dataset agent this fails on older versions. So possibly the test is too hard to write in a reasonable way that actually prove we're doing the right thing... Ideas welcome.

Additionally the test is somewhat flaky.

Probably going to add per-OS code for disabling dataset agent before reboot, re-enabling after test finishes.

I have verified updated test fails consistently on 1.6.1 with the 120 second sleep removed.

Oh, except this test won't work on latest code since container won't ever start. So... I need to loop until reboot is done and then wait until container agent is up and then start the dataset agent in the test itself. Brilliant.

No issues with the code, I'm fine with the enable_service script. :+1:
I do have some concern that this test has decently high probability of adding flakiness to our test suite. It's probably a waste of time to wait for two green columns on http://build.clusterhq.com/boxes-flocker?branch=drop-sleep-workaround-FLOC-3377&num_builds=10... but this feels like the sort of test that almost merits that kind of caution.
I trust your judgment. Certainly wait for green test runs, if you get them--go ahead and merge.

I'm going to require green because this supposed to fix the most common flaky acceptance test.

But on the plus side the only failing acceptance test on previous run on centos was a bug I introduced and then fixed, so I'm hopeful.

http://build.clusterhq.com/builders/flocker%2Facceptance%2Frackspace%2Fubuntu-14.04%2Frackspace/builds/3429/steps/trial/logs/stdio :( - I know you're done for the day, so I might dive in and see if I can figure out what happened  a little later so I can kick off  another round of tests before the end of the day.


Minor tweaks to the overall documentation and document links

While looking into #12 I made some changes to the README to make it easier for me to understand :smile:

thanks, merged into 6.1.2


feat: allow apps to register elements itself

This gets very important with webpack 5 which will be able to completely remove unused components. This needs a PR from N https://github.com/NativeScript/NativeScript/pull/9133 to be fully functional.
However this is already an improvement in webpack 4 as app “loading” will get faster.
Also if at one point we manage to "auto" detect used components that flag should also be set to false
I am creating that PR now because it could already be used by users who wants faster loading time. And it does not break anything nor change the default behavior.

@halfnelson i would really need that. could you have a look at it?

Not a fan of the big global. For this to be useful I guess we would need to provide a "register" method for each native element which the consumer could call

I can sneak in a breaking change in 1.0.0 that requires the template to call registerAllComponents() to remove the need for the global

@halfnelson fine with me. the global even if not perfect has the benefit of being very clear for webpack to know what it can "remove"

@halfnelson would you consider that now please? AUTO_REGISTER_UI_MODULES is now part of N and webpack 5


#4207 ENH: streamline processing CTF files

clean_names function was added to the SetChannelsMixin.

Hi @OlehKSS thank you for picking up this one. In fact what needs to be done here is rather a private function that strips the CTF ch names optionally. The CTF names can come with suffixes like "-4408" etc. which need to be stripped. The idea would be to expose an argument in the CTF constructor that allows to clean the names everywhere necessary. I'd suggest to remove this from the mixin and add a private function to the RawCTF class. Then we need to write tests.

Ok, thanks @dengemann. Could you share some examples of data that I can use for testing this functionality?

@OlehKSS have a look at mne.datasets.brainstorm.bst_restingwhich exposes this issue. Note that we are currently about to update the data, the io might slightly change, however, not the issue. Also, even simpler, checkout mne/io/ctf/tests/test_ctf.py.

@dengemann I have made changes to RawCTF class, please take a look when it will be possible. Does CTF adds prefixes only to 'comps' field of  a raw file info, like you showed in the issue description, or it can change any fields? So, show it be possible to specify on which fields to perform _clean_names operation?

please also update a test

@agramfort I have updated tests and made changes according to your suggestions. Could you take a look?

@OlehKSS can you see why travis is not happy?

@agramfort I have fixed code styling errors that caused Travis to fail build

Great! I’ll pull in a bit and take a look how it behaves with my problem
case.
On Wed 21 Mar 2018 at 11:34, Oleh Kozynets<EMAIL_ADDRESS>wrote:

@OlehKSS commented on this pull request.
In mne/io/ctf/ctf.py
https://github.com/mne-tools/mne-python/pull/5004#discussion_r176036969:

@@ -165,6 +165,35 @@ def _read_segment_file(self, data, idx, fi, start, stop, cals, mult):
_mult_cal_one(data_view, this_data, idx, cals, mult)
offset += n_read

def _clean_names(self):

   """Clean up CTF suffixes from channel names."""

   for comp in self.info['comps']:

       for key in ('row_names', 'col_names'):

           comp['data'][key] = _clean_names(comp['data'][key])

@dengemann https://github.com/dengemann I've added cleaning of main
channels to _clean_names method and deleted overloading of rename_channels
method.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/5004#discussion_r176036969,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fir6vlBtk8UivQ1zQ3hCqaXkEXyJ1ks5tgizCgaJpZM4Sk8ld
.

@OlehKSS can you update whats_new.rst API section to document the new parameter?
thanks

@agramfort , @larsoner I have updated pull request according to your comments.
@larsoner I have failed to update this inequality check link to file, due to this error. In detail, if I use != operator I receive a ValueError from numpy about array evaluation in boolean context, which do not relate to the inequality check (I compare two lists of strings).

I receive a ValueError from numpy about array evaluation in boolean context, which do not relate to the inequality check (I compare two lists of strings).

Are you absolutely sure you are comparing two list of str? It sounds like at least one of them is a np.ndarray of str...
If that's the case you either (implicitly) cast both to ndarray using assert_array_equal or you can cast the object(s) that is(are) ndarray of str to list of str. assert  is only good for builtin types, not ndarray.
Make sense?

@larsoner , as you can see here I do equality check and it works just fine, but if I change operator to != I will obtain that ValueError. I have checked types of operands in the debugger, they are of type list. I have been testing this code with the == operator and it works as expected. Probably there are implicit casting from ndarray to list or vice versa, the question why it happens with !=, and does not affect ==.

Probably there are implicit casting from ndarray to list or vice versa

assert  will not cast anything, assert_array_equal will cast both to ndarray.

I have checked types of operands in the debugger, they are of type list

If I change line 240 to use assert :
            assert _clean_names(test_comp['data'][key]) != comp['data'][key]

and run:
pytest mne/io/ctf/tests/test_ctf.py -k test_rawctf_clean_names --pdb

It does indeed fails. But then:
(Pdb) p type(_clean_names(test_comp['data'][key]))
<class 'list'>
(Pdb) p type(comp['data'][key])
<class 'numpy.ndarray'>

In other words, one is list and one is ndarray. It's fine to leave it as assert not array_equal in this case.
Perhaps you missed this subtlety and were checking line 250, where they are both indeed lists. Presumably what was originally an ndarray was been changed by that point in the code to be list by your _clean_names function, which is fine -- just need to keep track of what is what and when they become those things.

Just waiting on OSX which is horribly delayed so I'll merge, thanks @OlehKSS

@larsoner Thanks


Ensure authResponse is not falsy before logging authResponse.json

I am currently having issues with the revoke method, as it attempts to log authResponse.json even though authResponse is null. This PR changes to logging authResponse && authReponse.json instead so null and undefined values don't cause errors

Thank you @Matthew-John-Emerson , this PR is merged now.


npm config set msvs_version 2015 not working with VS15 alpha2

even after npm config set msvs_version 2015
npm install - triggered node-gyp build module with MSBuild 15.0 when Visual Studio 15 preview2 is installed
Is it so difficult to make MSBuild 15.0 works with node-gyp?

Upstream gyp doesn't support VS 15 yet so neither does node-gyp.

@bnoordhuis What I mean is even if I installed MSVS2015 or VC++Builder, same thing happens if I also installed MSVS15

Ah, that I don't know.  It sounds like VS 15 does something (clobber the environment? the registry?) that confuses gyp.
Just to be sure, does npm install --msvs_version=2015 work?

@bnoordhuis  nope, same
Error: C:\Program Files (x86)\MSBuild\15.0\bin\msbuild.exe failed with exit code: 1

@alanpurple if node-gyp cannot find MSBuild.exe on the %PATH% it looks into the registry and then takes the latest version found there, thus it's shelling out to VS15 Alpha/Preview instead of VS 2015.
Doing
SET PATH=C:\Program Files (x86)\MSBuild\14.0\Bin;%PATH%

before calling npm install should solve this.

Old issue, but VS15 would be --msvs_version=2017

Old issue, but VS15 would be --msvs_version=2017

We did not upgrade to the latest version of GYP, and the current version does not know what 2017 is. For now we're lying to it that it's 2015 with v141 toolset.
Ref: https://github.com/nodejs/node-gyp/blob/master/lib/configure.js#L156
Anyway I'm closing this issue, since we do auto detect VS15 a.k.a. VS2017 since<EMAIL_ADDRESS>

npm -v  = 6.14
node -v = 10.15.3
os          = windows 7 sp1

npm i -g --production windows-build-tools

npm install --global --production<EMAIL_ADDRESS>
still gettting error, could
D:\gulaqWorkspace\api\node_modules\iconv>if not defined npm_config_node_gyp (nod
e "C:\Users\Admin\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycl
e\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (no
de "C:\Users\Admin\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bi
n\node-gyp.js" rebuild )
gyp ERR! find VS
gyp ERR! find VS msvs_version was set from command line or npm config
gyp ERR! find VS - looking for Visual Studio version 2015
gyp ERR! find VS VCINSTALLDIR not set, not running in VS Command Prompt
gyp ERR! find VS could not use PowerShell to find Visual Studio 2017 or newer
gyp ERR! find VS looking for Visual Studio 2015
gyp ERR! find VS - not found
gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8
gyp ERR! find VS
gyp ERR! find VS valid versions for msvs_version:

https://support.microsoft.com/en-us/help/4057281/windows-7-support-ended-on-january-14-2020

@cclauss what i have to do now?  i need to upgrade ? But i have using windows-7 service pack 1

Yes.  It is time to upgrade.  The operating system that you are running on is no longer supported. It is not right to ask others to support that for free.

Ah, that I don't know. It sounds like VS 15 does something (clobber the environment? the registry?) that confuses gyp.
Just to be sure, does npm install --msvs_version=2015 work?

Nothing worked, including npm config edit, but I came across a god answer.
In my case, it happened while installing sodium package.


Can not build with --target=x86_64-apple-darwin on Mac M1

Hi,
When I build my rust project with --target=x86_64-apple-darwin.
cargo build --target=x86_64-apple-darwin

Encountered the following error:
  = note: ld: in /Users/farmer/Projects/my-project/rust/target/x86_64-apple-darwin/debug/deps/libwhisper_rs_sys-cb1bd74588817382.rlib(ggml.c.o), archive member 'ggml.c.o' with length 244616 is not mach-o or llvm bitcode file '/Users/farmer/Projects/my-project/rust/target/x86_64-apple-darwin/debug/deps/libwhisper_rs_sys-cb1bd74588817382.rlib'

Cross building might not be supported by upstream, you may have to build on the target host.

The upstream project, whisper.cpp itself, may not fully support cross compilation. whisper.cpp itself definitely supports x86_64 Macs, as I've seen issues on this repo mentioning x86_64 on MacOS working fine. You'd probably have to pass some flags to CMake to see if it works. From a quick internet search, I found this: https://cmake.org/cmake/help/book/mastering-cmake/chapter/Cross Compiling With CMake.html but it looks like a huge headache to implement without turning build.rs into a mess.

I did find ggerganov/whisper.cp#514, but that gives little to no help.

@tazz4843
It looks that adding below command into CMakeLists.txt can output the dylib file supporting both x86_64 and arm64 arch.
set(CMAKE_OSX_ARCHITECTURES "x86_64;arm64")

You'd have to make a PR to upstream and wait for it to be released before this can get upgraded.

@farmer00317558 did you ever figure this issue out? Getting the same error when building (M1 Max).

@farmer00317558 did you ever figure this issue out? Getting the same error when building (M1 Max).

I abandoned the library, wrote a C++ file myself that references the whisper.cpp directly, and built a dynamic library for my project.

@farmer00317558 that's really cool. Would you mind sharing the code with me?

@richtermb https://github.com/farmer00317558/hello-dart-ffi
Here, I hope that helps.

Gonna close this due to age, if you've resolved it feel free to let us know.


Add parameters for multi-sig contract actions to cleos

In order to use the multisig contract currently the user must use cleos to send an action to the contract by building up the proper JSON string.  Add a “propose” option to cleos to make this simpler for users.  Any other actions in the multisig contract should have corresponding cleos options.

Duplicate of #2163

Duplicates to https://github.com/EOSIO/eos/pull/2427


[BUG] help() references __signature__, which does not exist on native_func's.

Bug description
When calling the help() function on a native function, the following error message is printed:
  Traceback (most recent call last):
    File "main.py", line 3
      help(somefunc)
    File "<builtins>", line 173, in help
      print(obj.__signature__)
  AttributeError: 'native_func' object has no attribute '__signature__'

Steps to reproduce

Create a native function
call help() on it

Environment information
main branch, OS not relevant.
Additional context
I'd be open to implement __signature__ on native_func. Alternatively, the help() function could be changed to print the name of the function instead of the signature.
(Also, I realize I reported a few things over the last few days, please let me know if this is ok or if I should stop reporting issues.)

Hi. I know this. The current docstring/help system is not fully operational.
Please keep this issue open. I may improve it in the v2.0 branch.

(Also, I realize I reported a few things over the last few days, please let me know if this is ok or if I should stop reporting issues.)

It is ok. However, I am working on v2.0 branch. The main branch is going to be frozen. And low priority issues will not be fixed on the main branch. Critical bugs could be fixed on main and then cherry-pick to v2.0.

Sure! You can help implement this feature in v2.0.
For native_func
You can get its name and argc. Assume the name is f:

argc != -1, signature could be "f(_0, _1, ..._argc)"
argc == -1, signature is f(*args, **kwargs)

There is no docstring support. __doc__ always returns None.
For function
You need to inspect its FuncDecl_ to generate its signature. It is a bit complex.
And __doc__ should return the true docstring.

bind is our new style bindings API. It creates a function object. bind_func creates old style native_func.

I know your game needs a better doc system. There are some defects if you rely on the builtin help() (even with future improvements).
Most of the builtin classes and functions do not have any doc. For example, list and dict. If you want to provide a comprehensive doc system like cpython, you need replace the builtin help() with your own one. And you can use a custom database to provide such docs.

About inspect, currently there is no way to get internal information of pocketpy classes and functions. Because these information are treated as "private". We often change the internal structures with few breaks to user-level functionalities. However, if inspect module is provided, such "private" details become public. I cannot ensure it is stable. It is better to do this in user-level.

The main task on v2.0 can be roughly described as follows:

do a major refactor to improve overall code quality. Every source file changes.
significantly improve memory management (far less gc!)
provide a pybind11-compatible bindings API

v2.0 will be released in 2~3 months. And v1.x will be a LTS version. No more features, only bug fixes.

If you want to fix v1.x, the correct way is to comment the signature call out or raise NotImplementedError. As I said, v1.x accepts bug fixes but not new features. Inspection is in fact a not supported ability.

Feel free to fix or patch. However, please keep this issue open and I'd like to improve it on v2 if I have time!


Decide on multi root actions naming

Today we have two actions around multi root that we should finalize on the naming:

Add Root Folder
Remove Root Folder

Alternatives:

Add Folder / Remove Folder
Add Folder To Workspace / Remove Folder from Workspace
Add Workspace Folder / Remove Workspace Folder
more?

@Microsoft/vscode feedback welcome

I vote for "Add Folder to Workspace / Remove Folder from Workspace"
Please keep in mind the scenario where a user selects something in the explorer and chooses this action which can be easily confused with "create me a folder where I have selection".

If we use 'Workspace' in the command name, that makes a workspace a concrete 'thing' and then could lead to expectations for opening and saving workspaces.
An alternative that doesn't expose workspace would be 'Add existing folder...' (with the ellipsis as the result of this command would be a folder picker dialog).
As for removing folders, I would consider just 'Remove folder' as a command. Will we be able to make sure that this command is only enabled when the user has selected a folder that was previously added to a workspace? Otherwise this could lead to confusion however we name it as the user could select any folder and try to remove it.

I like "Add Folder" and "Remove Folder". I don't think it's ambiguous next to "New folder", and I agree that we should be careful about introducing a "workspace" term.

I'm with @roblourens, i.e. going with the simpler names. Using "workspace" however is something we have been doing for quite some time. We talk about workspace settings, open symbols in workspace, etc.

:+1: for "Add Folder"/"Remove Folder". I think it's understandable when it's next to "Open Folder", also it's not a destructive command; if users didn't want that to happen then they can just remove it after.

I vote for "Add Folder to Workspace / Remove Folder from Workspace" as long as we call this feature Multi Root Workspace.
"Add Folder" <--> "New Folder" may be more ambiguous when we translate to other languages.

"Add Folder" <--> "New Folder" may be more ambiguous when we translate to other languages.

I've seen this raised on something else as well, if it is indeed an issue we should be able to optionally annotate localized strings with descriptions of their purpose. This shouldn't drive our English strings. Examples:

"Paste" could be a noun or a verb whose translation may differ based on the language).
What does "Kill" mean in the "Kill Terminal" command.

I think it depends on the semantic we want to achieve. If the end goal is that a workspace with n folders conceptually behave like one folder with n subfolders (e.g open symbols in workspace, search, ...) then we should call the actions Add Folder to Workspace / Remove Folder from Workspace. If add folders are considered to be second class then I would call the action Add Folder... / Remove Folder

Current votes:

Add Folder to Workspace / Remove Folder from Workspace: 6
Add existing folder / Remove Folder: 2
Add Folder / Remove Folder: 3


index.js: 1437 Warning: Please use `require("react-router-dom").withRouter

You cannot use this statement
import {withRouter} from "react-router-dom/withRouter";
because it gives this error
index.js:1437 Warning: Please use require("react-router-dom").withRouter instead of require("react-router-dom/withRouter"). Support for the latter will be removed in the next major release

We are getting rid of releasing a package with multiple modules in favor of a single package. This means that everything will have to be imported from react-router-dom; you can no longer cherry pick imports from a nested module. Right now, we have helper modules that allow you to use the cherry picking syntax, but with warnings that this is going away.
import { withRouter } from 'react-router-dom';


EAGLE-205 Metric dashboard support multi metrics

Support multi metric display in one chart
support more data series in one chart

LGTM  +1


Remove ProxyStubs from appxmanifests

Suggested new feature or improvement
Should be done for both extensions, but core Dev Home stays the same.
Default proxy stubs are included in Microsoft.Windows.Widgets.dll and your appxmanifest should be prepopulated with the registration entries when you build with 1.5.

Host proxy stubs should still stay in place :)

Host proxy stubs should still stay in place :)

Task updated. Thanks!


Delphi / VisualBasic Syntax Mode

Is it possible to add a few more languages like Delphi or VisualBasic?
Regards

This responsibility is on the ACE plugin side, not PBCKCode. Please upgrade ACE to the last version to get the needed languages.


Fix role_arn for IAM role with path not being picked up correctly from config

Slashes are used to denote paths in IAM roles: https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_identifiers.html#identifiers-friendly-names
This fixes role_arn's with slashes not being picked up correctly from the config. When using the extension without the fix with a role which includes paths, the result is being redirected to the Switch Role screen with an error. Instead of the full role path (e.g. foo/bar) only the first part of the path of the role's path is being used (e.g. foo):

Could also result in the wrong role being used should a role with that name happen to exist.
Before:

After:

Cool, test are now green. Thank you for the contribution. I'll merge it later and try to upload a new release this week (i have to manually e2e test the extension).

@janstuemmel Thanks for the fast review and release, works perfectly now!


Percentage difference between day before avg and current avg

As the title says, is this possible to do with Kuiper SQL? I am getting the timestamp in UNIX, if that matters. I am assuming it may be a tumbling window function, but am unsure how to pull it off.

Yes.

I think there are two approaches

Use a hopping window to contain all the two days' data and use a group by to calculate the avg for each and then compare. The psudo SQL would be like:

SELECT (ts - windowStart() > 24 hours) as isToday, AVG(col) as avg FROM device GROUP BY HoppingWindow(dd, 2, 1), isToday ORDER BY isToday

By this way, we can get a list of two averages. Then we can use data template to calculate the percentage and format the output. However, this is not working now as there is still a missing function to get the window start time and to calculate the percentage in data template. We will implement that in the next release.
2. Develop custom function to use in a one day tumbling window. In the function, you'll need to calculate the average of the current window and store the last average in memory or by state API. This will need development of function plugin by yourself.

Ok, great. Glad to hear that functionality is coming. When creating a plugin that is to be used with a window function, I would not need to set isAggregate() to true, correct?

When creating a plugin that is to be used with a window function, I would not need to set isAggregate() to true, correct?

If you need to calculate the aggregation (such as average) of the window tuples, you'll need to set isAggregate() to true.

Ok, I see. When trying to use my plugin, the server crashes with error "no plugin module data". I am using the Docker compile method and putting my .so into the /usr/local/kuiper/plugins/functions/ directory to register. Any suggestions on what to do? I have tried building the AccumulateWordCount function in the extensions directory as well with the same result.

I never encounter this problem. After some research, it seems the error is likely from golang itself such as this issue.
I also tried to reproduce the problem but had no luck. I am using ubuntu 20.04.2 to run docker. I tried with kuiper:1.2.0 docker image. Below are my steps:

Run the kuiper docker container and build the plugin

docker run -p 9081:9081 -d --name kuiper_dev -e MQTT_SOURCE__DEFAULT__SERVERS=[tcp://<IP_ADDRESS>:1883] emqx/kuiper:1.2.0
docker exec -it kuiper_dev /bin/bash
### inside kuiper_dev, build the plugin
go build -trimpath --buildmode=plugin -o _build/kuiper-1.2.0-linux-amd64/plugins/functions/AccumulateWordCount.so plugins/functions/accumulateWordCount/accumulateWordCount.go

Exit and restart the docker container to let kuiper pick up the built plugin
Create stream and rule to verify the plugin, it works

CREATE STREAM commandStream (cmd string, base64_img string) WITH (DATASOURCE="commands", FORMAT="JSON")
SELECT accumulateWordCount(cmd, \" \") as wc FROM commandStream

Did you do anything different to mine?

So when I build the .so file and place it in the container, I am placing it under /usr/local/kuipers/plugins/functions, is that the right place? I should also mention, I only get that error when I try a POST request containing the rule, which looks like:
{
"id": "rule1",
"sql": "SELECT accumulateWordCount(name, " ") as wc from my_stream",
"actions": [{
"log": {}
}]
}
I am using Debian to run my docker containers.

The SELECT statement is actually "SELECT accumulateWordCount(name, " ") as wc from my_stream", the parentheses are escaped.

The space in the SELECT statement is escaped.

So when I build the .so file and place it in the container, I am placing it under /usr/local/kuipers/plugins/functions, is that the right place?

No. In the docker container, the running kuiper binary is in _build/kuiper-1.2.0-linux-amd64. So you should place it under the plugin directory there, to be specific _build/kuiper-1.2.0-linux-amd64/plugins/functions/AccumulateWordCount.so

I should also mention, I only get that error when I try a POST request containing the rule,

This is expectable. The plugin will only be loaded when a rule use it firstly.

I see. I placed it in the correct place and am still getting the error when POSTing the rule. I am using go version 1.16.5, do you suspect that may be the issue?

A little update:
I was able to get a different error and not have the server crash. Here are the steps I took and the error I got:

Cloned repo onto local machine
mounted ./extensions folder into kuiper-1.2.0 container
ran go build -trimpath --buildmode=plugin -o /go/kuiper/_build/kuiper-1.2.0-linux-amd64/plugins/functions/AccumulateWordCount.so functions/accumulateWordCount/accumulateWordCount.go
Restarted docker container
Posted the rule, same as above
Error I am getting is "plugin was built with a different version of package github.com/emqx/kuiper/xstream/api"

Any suggestions?

I am using go version 1.16.5, do you suspect that may be the issue?

Yes, that could cause issues. But I don't understand why you have another go version. The docker image emqx/kuiper:1.2.0 should have come with the go environment and kuiper source code. It was intended to replicate the build env where kuiper itself used so that the very strict golang plugin requirement can be met.

6. Error I am getting is "plugin was built with a different version of package github.com/emqx/kuiper/xstream/api"
Any suggestions?

This does not surprize me. Again, the source code is already inside the docker image emqx/kuiper:1.2.0. No need to clone and moute it which may not be the same version.

Could you point me in the right direction on where the extensions folder is inside the docker container? I cannot seem to find it in /go/kuiper. I don't have much experience with go plugins so I apologize, seems very touchy.

Could you point me in the right direction on where the extensions folder is inside the docker container? I cannot seem to find it in /go/kuiper. I don't have much experience with go plugins so I apologize, seems very touchy.

It's fine. We all understand the go plugin is touchy.
The folder is in _build/kuiper-1.2.0-linux-amd64/plugins/functions. Could u take a close look at my second reply which is a step by step instruction .


RFC: OPA integration proposal.

Signed-off-by: Chao Li<EMAIL_ADDRESS>

Hello @evanchaoli,
what is the status of this RFC wrt the merged code in concourse/concourse#5034?
should this RFC be merged as done or are there missing parts?

Hello @evanchaoli,
what is the status of this RFC wrt the merged code in concourse/concourse#5034?
should this RFC be merged as done or are there missing parts?

Came across this by random and it looks nice! Planning to add this to the OPA ecosystem page. One thing I couldn't find on the Concourse site was docs around how to integrate with OPA. I am not too familiar with the project so might just be I'm not looking in the right places. Could anyone help me out? :)

@anderseknert the only docs I am aware of are in the PR description, see https://github.com/concourse/concourse/pull/5034#issuecomment-693252774

@evanchaoli ping regarding https://github.com/concourse/rfcs/pull/41#issuecomment-769054867

Thanks @marco-m-pix4d 👍  Hoping that gets added to the docs then so that I can point to this as a good example of OPA in CI/CD integrations.


Removed redundant what's new test.

This test is no longer needed due to the simple whatsnew process, as documented here:

https://scitools-iris.readthedocs.io/en/latest/developers_guide/documenting/whats_new_contributions.html

Could not review pull request. It may be too large, or contain no reviewable changes.

@tkknight TGTM 👍


tsImport() not register CJS handling when type: module presented in root package

Acknowledgements

[X] I read the documentation and searched existing issues to avoid duplicates
[X] I am reporting a confirmed bug (not seek debugging help)
[X] I understand this is a collaborative project and relies on my contributions
[X] I read and understood the Contribution guide

Minimal reproduction URL
https://github.com/antfu/repro-tsx-tsimport-cts
Problem & expected behavior (under 200 words)
In repro's README
Bugs are expected to be fixed by those affected by it

[ ] I'm interested in working on this issue

Compensating engineering work financially will speed up resolution

[X] I'm willing to offer financial support

:tada: This issue has been resolved in v4.13.1
If you appreciate this project, please consider supporting this project by sponsoring :heart: :pray:

Hm, I'm seeing 0a78bfd11b20fcb6460fdcdea7d3b1daebfe3ad0 and<EMAIL_ADDRESS>break our projects:
$ tsx scripts/seedDatabase.ts
/home/runner/work/courses/courses/packages/database/util/connect.ts:2
import { cache } from 'next/dist/compiled/react/index.js';
         ^
SyntaxError: The requested module 'next/dist/compiled/react/index.js' does not provide an export named 'cache'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:134:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:217:5)
    at async ModuleLoader.import (node:internal/modules/esm/loader:3[16](https://github.com/upleveled/courses/actions/runs/9413420232/job/25930125960?pr=2494#step:12:17):24)
    at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:123:5)
Node.js v20.14.0

Not sure why tsx is having trouble resolving the cache export in compiled/react/index.js:
compiled/react/index.js
'use strict';

if (process.env.NODE_ENV === 'production') {
  module.exports = require('./cjs/react.production.js');
} else {
  module.exports = require('./cjs/react.development.js');
}

`
// ...

exports.cache = cache;
// ...


Can call method through tag reference using generics

Hi,
I've been playing around with generics, and it appears that capability bounds aren't checked properly.
The following code manages to call foo on a Bar tag, which I believe should not be allowed.
trait Foo
  fun foo()

class Bar is Foo
  fun foo() => None

actor Main
    fun call_foo[X: Foo #any](x: X) =>
      x.foo() // This works, but probably shouldn't work

    new create(e: Env) =>
      let x : Bar tag = Bar
      call_foo[Bar tag](x)

      // This fails to type check as expected
      // x.foo()

I've tried both ponyc 0.9 and 0.10 and get the same result

Yes, I believe this is another manifestation of a known high priority bug - #1328 ("Refcap violation via gencap-constrained type parameter").  It's unfortunate that this hasn't been fixed yet, but it is non-trivial.

I'm going to close this ticket as a duplicate for administrative purposes, but we appreciate you bringing it to us, and I will add your specific repro snippet to the ticket.

This is indeed the same bug, sorry for the duplicate.
Thanks for the pointer, I'll be keeping an eye the other issue then

No worries - we'd rather have two reports of the same bug than have a bug go unreported.
I've slated the bug for discussion during next weeks sync call, to see if we can get progress kickstarted on it again.