Allow running files without any cargo script header or doc comment at the top

Allow running files without any cargo script header or doc comment at the top
The minimal required header is just ///, right now, but it could maybe be even less (nothing)?

No comment at all should work just fine.  There's even a test for it.

Ok, here's a file where I find an error.
internal error: could not parse embedded manifest
macro_rules! trait_group {
    (@as_items $($it:item)*) => ($($it)*);
    (@replace_self with $rep:tt [$($st:tt)*] Self $($tail:tt)*) => {
        trait_group!{@replace_self with $rep [$($st)* $rep] $($tail)*}
    };
    (@replace_self with $rep:tt [$($st:tt)*] $t:tt $($tail:tt)*) => {
        trait_group!{@replace_self with $rep [$($st)* $t] $($tail)*}
    };
    (@replace_self with $rep:tt [$($st:tt)*]) => {
        trait_group!{@as_items $($st)*}
    };
    (pub trait $name:ident : $($t:tt)+) => {
        trait_group!{@as_items pub trait $name : $($t)+ { }}
        trait_group!{@replace_self with T [] impl<T> $name for T where T: $($t)+ { }}
    }
}

use std::ops::Add;

trait_group!(pub trait Test : Add<Self, Output=Self> + Copy);

fn foo<T: Test>(x: T) -> T { x + x }

fn main() { println!("{}", foo(2)); }

Ok, so it turns out the problem was prefix manifests.
The way they worked was that they terminated on the first --- (or longer) that it saw, or when it encountered what looked like Rust code; assuming there was something other than whitespace between the start of the file and the cutoff, it assumed it had found a manifest.
The problem was that this "looks like Rust code" check was implemented by just testing for every token a Rust source file could start with... except for macro_rules!.
Since I had to bump the major version a while ago due to language back compat problems, and I've been meaning to get rid of prefix manifests for a while, I just did that.
There are a few other things I want to sort out before making a new major release, so I'll probably wait a little longer before publishing.

Great, don't see the need of many different ways to specify the manifest anyway.

FYI it also didn't recognize the trait token :p
Could you perhaps upload a new stable version to crates.io?


Getting Errors after installing and importing this package

These are the error logs when I import the package to use it.
Flutter version: 3.10.5
Steps:
Just add the package and import to use
: Error: The class 'Drag' can't be used as a mixin because it isn't a mixin class nor a mixin.
../…/src/crop.dart:63
class CropState extends State with TickerProviderStateMixin, Drag {
^
: Error: The method 'PageMetrics.copyWith' doesn't have the named parameter 'devicePixelRatio' of overridden method 'Object with ScrollMetrics.copyWith'.
../…/lib/preload_page_view.dart:179
PageMetrics copyWith({
^
: Context: This is the overridden method ('copyWith').
../…/widgets/scroll_metrics.dart:51
ScrollMetrics copyWith({
^
: Error: The method '_PagePosition.copyWith' doesn't have the named parameter 'devicePixelRatio' of overridden method 'ViewportOffset with ScrollMetrics.copyWith'.
../…/lib/preload_page_view.dart:302
PageMetrics copyWith({
^
: Context: This is the overridden method ('copyWith').
../…/widgets/scroll_metrics.dart:51
ScrollMetrics copyWith({
^
: Error: Required named parameter 'devicePixelRatio' must be provided.
../…/lib/preload_page_view.dart:170
}) : super(
        ^

I also had this issue 4 months ago , you can try https://pub.dev/packages/images_picker, let me know if you find a better multi image crop package


link to Kudo/scm not placed to scm.privatelink.azurewebsites.net DNS zone

Describe the bug
DNS records for the Private endpoint are automatically generated but one of them is placed in the wrong private DNS zone.
Both DNS records of type A are located in the private DNS zone 'privatelink.azurewebsites.net'
The Private endpoint for Azure Web App is linked to two FQDN that point to aliases:
[appname].privatelink.azurewebsites.net         --->[appname].azurewebsites.net
[appname].scm.privatelink.azurewebsites.net     --->[appname].scm.azurewebsites.net

Based on private-endpoint-dns documentation private DNS zone are created in line with recommended naming
privatelink.azurewebsites.net
scm.privatelink.azurewebsites.net
DNS zone configuration can be added for the Private endpoint through the portal or az command
az network private-endpoint dns-zone-group add
The result DNS zone configuration for the Private endpoint is here:
{
  "etag": "W/\"88888888-8888-8888-8888-888888888888\"",
  "id": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/app-resource-group/providers/Microsoft.Network/privateEndpoints/test-service-private-endpoint/privateDnsZoneGroups/default",
  "name": "default",
  "privateDnsZoneConfigs": [
    {
      "name": "scm_privatelink_azurewebsites_net",
      "privateDnsZoneId": "/subscriptions/11111111-1111-1111-1111-111111111111/resourceGroups/hub-network-rg/providers/Microsoft.Network/privateDnsZones/scm.privatelink.azurewebsites.net",
      "recordSets": []
    },
    {
      "name": "privatelink_azurewebsites_net",
      "privateDnsZoneId": "/subscriptions/11111111-1111-1111-1111-111111111111/resourceGroups/hub-network-rg/providers/Microsoft.Network/privateDnsZones/privatelink.azurewebsites.net",
      "recordSets": [
        {
          "fqdn": "test-service.privatelink.azurewebsites.net",
          "ipAddresses": [
            "<IP_ADDRESS>"
          ],
          "provisioningState": "Succeeded",
          "recordSetName": "test-service",
          "recordType": "A",
          "ttl": 10
        },
        {
          "fqdn": "test-service.scm.privatelink.azurewebsites.net",
          "ipAddresses": [
            "<IP_ADDRESS>"
          ],
          "provisioningState": "Succeeded",
          "recordSetName": "test-service.scm",
          "recordType": "A",
          "ttl": 10
        }
      ]
    }
  ],
  "provisioningState": "Succeeded",
  "resourceGroup": "app-resource-group"
}

Command Name
nslookup appname.scm.privatelink.azurewebsites.net
Errors:
Server:  UnKnown
Address:  <IP_ADDRESS>

*** UnKnown can't find appname.scm.privatelink.azurewebsites.net: Non-existent domain

To Reproduce:
Steps to reproduce the behavior.

create Web App with the Private endpoint
create private  DNS zones  privatelink.azurewebsites.net
create private  DNS zones  scm.privatelink.azurewebsites.net
add the private DNS zone "scm_privatelink_azurewebsites_net" configuration  for the Private endpoint
az network private-endpoint dns-zone-group add --endpoint-name {} -n {} --resource-group {} --zone-name "scm_privatelink_azurewebsites_net" --private-dns-zone {}
add the private DNS zone "privatelink_azurewebsites_net" configuration  for the Private endpoint
az network private-endpoint dns-zone-group add --endpoint-name {} -n {} --resource-group {} --zone-name "privatelink_azurewebsites_net" --private-dns-zone {}
run nslookup appname.scm.privatelink.azurewebsites.net  command from a host in the same vNet

Expected Behavior
"test-service.scm.privatelink.azurewebsites.net" record  will be added to "scm.privatelink.azurewebsites.net" zone, not to "privatelink.azurewebsites.net
and nslookup will resolve the name appname.scm.privatelink.azurewebsites.net to the IP address
Environment Summary
Windows-10-10.0.19045-SP0
Python 3.10.8
Installer:

azure-cli 2.45.0 *

Extensions:
account 0.2.5

Dependencies:
msal 1.20.0
azure-mgmt-resource 21.1.0b1

Additional Context

@necusjz for awareness

Same issue for me. I'm not able to reach scm through private endpoint. Any updates on this? @yonzhan

I'm hitting this issue as well, all though I'm using azure policy DINE to deploy this, do we have any updates?
                "resources": [
                  {
                    "name": "[concat(parameters('privateEndpointName'), '/deployedByPolicy')]",
                    "type": "Microsoft.Network/privateEndpoints/privateDnsZoneGroups",
                    "apiVersion": "2020-03-01",
                    "location": "[parameters('location')]",
                    "properties": {
                      "privateDnsZoneConfigs": [
                        {
                          "name": "sites-privateDnsZone",
                          "properties": {
                            "privateDnsZoneId": "[parameters('privateDnsZoneIdSites')]"
                          }
                        },
                        {
                          "name": "sitesScm-privateDnsZone",
                          "properties": {
                            "privateDnsZoneId": "[parameters('privateDnsZoneIdSitesScm')]"
                          }
                        }
                      ]
                    }
                  }
                ]

Join those who have this issue

It has been a long time.  Can we get some clarification from Microsoft on this?
It seems that Azure documentation on this is not consistent.  For example here, it is stated that just one private DNS zone should be created: https://learn.microsoft.com/en-us/azure/app-service/overview-private-endpoint#dns


After update yeelink.light.ceiling5 unable to Night mode in automations and scenes

Device model / 设备型号
yeelink.light.ceiling5
Component version / 插件版本
1.0.6
HA core version / HA版本
2024.12.1
Integrated mode / 集成方式
Local (本地模式)
The problem / 问题详情
After a recent update, sadly I don’t know the previous working version I was on,
the “Night” effect no longer works in scenes and automations, however manually selecting “Night” effect in the dashboard still works.
Despite the scene YAML having effect: Day and light.mode: 2, it toggles effect to Night but does not toggle light mode to 1 and then shortly after effect will go back to Day.
Please let me know if I need to provide anything to diagnose the issue.
Entity attributes / 实体属性
device_class: update
icon: mdi:information
friendly_name: Master Bedroom Light Info
info: Bedroom Light
model: yeelink.light.ceiling5
did: 131833522
mac: 04:CF:8C:8F:0D:E0
lan_ip: <IP_ADDRESS>
app_link: mihome://device?uid=237943445&did=131833522
miot_type: urn:miot-spec-v2:device:light:0000A001:yeelink-ceiling5:1
available: true
home_room: Home Bedroom
updater: local
updated_at: 2024-12-24 20:14:03.083700+08:00
light.on: true
light.brightness: 100
light.mode: 1
light.color_temperature: 2702
light.flex_switch: false
light.off_delay_time: 0
converters: button.info, light.light.on, light.brightness, light.color_temperature, light.mode, number.light.off_delay_time
customizes:
number_properties: off_delay_time
switch_properties: bg_on
extend_miot_specs: yeelink.light.ceiling1

Home Assistant Logs / 系统日志
No response

Show the yaml of scene/automation.

name: Master Bedroom NIGHT MODE
entities:
  light.yeelink_ceiling5_0de0_light:
    min_color_temp_kelvin: 2700
    max_color_temp_kelvin: 5700
    min_mireds: 175
    max_mireds: 370
    effect_list:
      - Day
      - Night
    supported_color_modes:
      - color_temp
    icon: mdi:light-recessed
    friendly_name: Bedroom Light
    supported_features: 4
    effect: Night
    color_mode: color_temp
    brightness: 255
    color_temp_kelvin: 2702
    color_temp: 370
    hs_color:
      - 28.391
      - 65.659
    rgb_color:
      - 255
      - 167
      - 88
    xy_color:
      - 0.524
      - 0.388
    light.on: true
    light.mode: 2
    light.brightness: 100
    light.color_temperature: 2702
    state: "on"
  number.yeelink_ceiling5_0de0_off_delay_time:
    min: 0
    max: 60
    step: 1
    mode: auto
    unit_of_measurement: minutes
    friendly_name: Master Bedroom Master Bedroom Master Bedroom Light Light off_delay_time
    light.off_delay_time: 0
    state: "0"
icon: mdi:lightbulb-night-outline
metadata: {}


Unified settings management and sound fixes

fixed: speech was not paused during pause menu
fixed: allow sound levels to reach min value 0.0 (=muted)

So to confirm what I'm reading in the code, the expected behavior of this change is that all audio settings are written to an external configuration file?

So to confirm what I'm reading in the code, the expected behavior of this change is that all audio settings are written to an external configuration file?

Actually the change is that all user settings (such as audio volumes, resolution, fullscreen, language and such) are "centralized" in Project Settings, instead of just being put in a local Dictionary in escoria object as it was before.
This is done using the new ESCSettingsManager (that makes calls to ESCProjectSettingsManager). Saving the settings using ESCSettingsManager.save_settings() save the settings in user://settings.json file as before.

I started a game (F5) started in English, paused and changed language. I had the following error :

I started a game (F5) started in English, paused and changed language. I had the following error :

Fixed

Crash going from room 1 to room 2 (started with F6) in event_action_manager

The talking face has disappeared in room 1

Crash going from room 1 to room 2 (started with F6) in event_action_manager

Fixed.

The talking face has disappeared in room 1

Strange behaviour, sometimes the folder to res://game/dialog_avatars/ is removed from project settings...

When I loaded this branch it errored on 9-verbs and disabled the plugin - I had to restart to fix it. I'm guessing that's an expected fault.

I had this issue too. I had to reload the project to fix it. Not sure why this happened though.

I get an immediate crash on the latest commit
--- Debugging process started ---
Godot Engine v3.5.stable.official.991bb6ac7 - https://godotengine.org
OpenGL ES 3.0 Renderer: NVIDIA GeForce GTX 970/PCIe/SSE2
Async. shader compilation: OFF
ESC (2022-08-26T17:47:13) I main_scene.gd: Escoria starts...
ESC (2022-08-26T17:47:13) W esc_settings_manager.gd: Settings file user://settings.tres doesn't existSetting default settings.

Error in file esc_project_settings_manager.gd

Hah, I was too confident. Sorry about that. I'll fix it.

Not sure why it was breaking for me last time. I had recently deleted all my Godot cache, so it was likely something related that has fixed itself.
I'll mark it approved though there's one issue that might be related @StraToN - if I open Godot, then open room 5 and run it directly (F6), it works but I get these errors.
Godot Engine v3.5.stable.official (c) 2007-2022 Juan Linietsky, Ariel Manzur & Godot Contributors.
--- GDScript language server started ---
Switch Scene Tab
Switch Scene Tab
 res://addons/escoria-core/game/core-scripts/esc_terrain.gd:73 - Invalid get index 'logger' (on base: 'Node (esc_autoload.gd)').
 res://addons/escoria-core/game/core-scripts/esc_room.gd:69 - Invalid get index 'room_manager' (on base: 'Node (esc_autoload.gd)').

If I stop Escoria and restart room 5 the errors disappear.


[Enhancement] Enhance functions such as current_user

What type of PR is this：

[ ] Enhancement

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 2.5
[ ] 2.4
[x] 2.3
[ ] 2.2

spark and presto can execute
select current_user() , select current_user
select user() , select user
but starrocks only execute such as
select current_user()
select user()
so enhance functions like spark and presto， now we can execute
select current_user
select user

starrocks_fe_unittest

run starrocks_fe_unittest

run starrocks_fe_unittest

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

I remove the key word
spark and presto can execute "select current_user"
so, sr also wants to execute "select current_user"
@imay

mysql also support this. I think you can backport to 2.3~2.5, not only 2.3

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

run starrocks_admit_test

https://github.com/Mergifyio backport branch-2.4


Unable to see LastLogonDate in Report only mode for initial analysis.

Terrific script and really well laid out comments within, having a small issue which perhaps is user error (I did read the Readme.md!).
When I run it in remote only mode (Remove-StaleGuests.ps1 -ExportCSVPath guest.csv) I don't see a column value showing last logon, and using excel to look at the RefreshToken field only runs dates until February this year (but AAD sign in logs will only have last 90 days, and.....
I see recent LastLogonDate events when running it in (remote-staleguests.ps1 -InactiveTimeSpan 90 -exportcasvpath blah.csv) but without the remove $true, it attempts (I haven't yet elevated to roles capable of making changes, just global/sec reader), it begins to write-host "SUCCESS:  addding lastlogondate to CustomAttribue1".  Which is great, of course it errors hugely because it can't write the attributes but I just did it as a test to see if I misunderstood your instructions.
I need to be able to provide initial stats on how many of our guests are stale, so we can plan the impact of deleting them.  How can I run the script in report only mode, to obtain the LastLogon dates?  Is this possible?

Hi @tolarianNZ, thanks for the feedback!
Can you check you are using version 1.0.1 we updated this a couple of weeks ago. (Maybe you have an old copy?) Your csv should have lastlogon value and it should now also be displayed to screen.
I noted today that it's down to 7 days for free accounts and 30 days for P1 and P2. I'm guessing guest accounts sign in logs will be 7 days :(
https://docs.microsoft.com/en-us/azure/active-directory/reports-monitoring/reference-reports-data-retention#how-long-does-azure-ad-store-the-data
To get the right results you will need to grant the write access and schedule the script to run each week and wait until you reach the time expiry period.

Thanks for the snappy reply Joshua,
We have 10k AADPP2 licences, and 4.5k guests, I'm keen to know how many are
stale before engaging the hatchet.
I downloaded your script today, used latest AzureAD-Preview ( x.x.2.101
from memory) and the v2 of Exchange Online PS.
I'll check again tomorrow but did not see that CSV column in report mode,
although it piped out to screen.
On Tue, 7 Jul 2020, 11:05 pm Joshua Bines<EMAIL_ADDRESS>wrote:

Hi @tolarianNZ https://github.com/tolarianNZ, thanks for the feedback!
Can you check you are using version 1.0.1 we updated this a couple of
weeks ago. (Maybe you have an old copy?) Your csv should have lastlogon
value and it should now also be displayed to screen.
I noted today that it's down to 7 days for free accounts and 30 days for
P1 and P2. I'm guessing guest accounts sign in logs will be 7 days :(
https://docs.microsoft.com/en-us/azure/active-directory/reports-monitoring/reference-reports-data-retention#how-long-does-azure-ad-store-the-data
To get the right results you will need to grant the write access and
schedule the script to run each week and wait until you reach the time
expiry period.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JBines/Remove-StaleGuests/issues/2#issuecomment-654843303,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZPSAC6Y2MNMLUJIZPOE6TR2MMTLANCNFSM4OSWDIGA
.

I just reran it now and you should see a lastlogondate in the csv

Hi @tolarianNZ any feedback on this issue?


Nice effort guys!

Hey,
Have you considered supporting almost a year old Dockerized Drupal initiative (FYI I'm the initial author of that project) as this project is also trying to make Drupal development with Docker easier. I think that we are trying to achieve the same goal here, but correct me if I'm wrong.

Thanks for the link, I personally didn't know about this initiative, we'll definitely take a look at your project. The main reason we started this initiative is that docker has finally launched a native app for mac/windows, so we decided it might be a good opportunity to share our bundles with the community.

I took a look at  Dockerized Drupal initiative and it looks interesting as the idea of having isolated local development is the way to go.
The main difference is in virtualization technology: Dockerized Drupal is using older Docker method (toolbox) while docker4drupal is using more modern Docker for Mac application.
Vagrant - virtual box works for older systems (pre Intel core processors before 2010) and is still the only solution for those and systems not running 10.10.3 ref: Docker docs
Since Mac machines that are newer than 2010 and have 10.10.3 or newer OS version have hypervisor they do not need vagrant/virtualbox as an additional virtualization layer (sure, there is still a long way to stabilize both native Docker clients for Mac and Windows but I think it is preferred way to go) so they are more lightweight than old toolbox solution.
Other than that, on a container level there probably could be some common ground.

@viljaste I found your documentation quite confusing. Not that I personally could not find the way to make that work but it could be improved (streamlined) considerably and that would help adoption.
Current appearance (style) is also very hard to follow so I'd suggest cleaning style or using some other system like Git Book or Read The Docs like Drush, even plain giihub pages or wiki offer nice, easy to follow appearance and structure.
But technology stack should also be improved to current ones.

I'm going to close the issue due to no activity.


0.52 release did not get completed

👋 looks like 0.52 release was not completed, ie did not get marked as latest release. Raise this issue for some awareness. Thanks!
relates to https://github.com/Homebrew/homebrew-core/pull/181179

@chenrui333 it was released "for real" the other day

thanks, closing the issue. 👍


add framework for verification plugins

Codecov Report

Merging #38 (dfd9845) into master (0fd7aae) will increase coverage by 0.20%.
The diff coverage is 91.30%.

@@            Coverage Diff             @@
##           master      #38      +/-   ##
==========================================
+ Coverage   59.09%   59.29%   +0.20%
==========================================
  Files          34       34
  Lines        2887     2904      +17
==========================================
+ Hits         1706     1722      +16
- Misses       1181     1182       +1

Impacted Files
Coverage Δ

sram22/src/lib.rs
14.66% <50.00%> (ø)

magic_vlsi/src/lib.rs
57.75% <85.71%> (+0.24%)
:arrow_up:

sram22/src/cells/gates/nand/mod.rs
100.00% <100.00%> (ø)

sram22/src/cells/gates/nand/single_height.rs
100.00% <100.00%> (ø)

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Exception from AutoMapper after publishing new build

I am using the newest server nuget packages 2.0.0 like Microsoft.Azure.Mobile.Server.
The following message appears in my app service logs, once every time I publish a new build:
Warning     Message='Exception thrown while getting types from 'AutoMapper.Net4, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=be96cd2c38ef1005'.', Exception=System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module)
at System.Reflection.RuntimeModule.GetTypes()
at System.Reflection.Assembly.GetTypes()
at System.Web.Http.Tracing.Tracers.DefaultHttpControllerTypeResolverTracer.GetTypesAndTrace(Assembly assembly)
However everythings works as expected, but maybe its better to fix this exception?
Maybe there is a problem because I use the newest AutoMapper 5.2.0?

It seems that the old AutoMapper.Net4.dll was in the bin folder on the server. I deleted this, now there no more errors.


Unclear terminal output: looping loop

Hi @AhmetCanSolak ,
I'm just testing napari-aydin and have some questions about the terminal output. First of all, the predicted time works well, that's super cool! I'm just wondering about the progress loss/quality-wise and number of iterations.
Used dataset: C2-DrosophilaEggChamber-small.zip
(Source: Image data adapted from Sarah Machado, Vincent Mercier, & Nicolas Chiaruttini. (2018). LimeSeg Test Datasets [Data set]. Zenodo. http://doi.org/10.5281/zenodo.1472859 Shared under CC-BY 4.0 )
Used code/napari-aydin version: https://github.com/haesleinhuepf/napari-aydin/commit/62b98bd716997189599c0c70d7f6daf6a49c8be2
To reproduce setup an environment like this:
mamba create --name aydin-env python=3.9 napari=0.4.15 -c conda-forge
conda activate aydin-env
cd napari-aydin
pip install -e .
napari

Then, load the tif image linked above and click the menu Tools  Filtering / noise removal > noise2self (fgr-catboost, aydin) and Run.

Two questions:

Would it be possible to clarify the output? In the block bestTest, bestIteration: could it print out how often it will do this? It appears training is running in a loop. A novice user couuld conclude that the algorithm runs in an endless loop.
Would it be possible to limit the number of iterations? The learn / test output above seems not improving much after the first 150 iterations. Can we specify 150 as max?

And for completeness, a screenshot. The results look fantasti!

Thanks!
Best,
Robert

Hello @haesleinhuepf ,

Two questions:
Would it be possible to clarify the output? In the block bestTest, bestIteration: could it print out how often it will do this? It appears training is running in a loop. A novice user couuld conclude that the algorithm runs in an endless loop.

It is actually not an endless loop but also not a loop with a pre-determined number of iterations. Here these logs you are observing actually generated by the framework we used underneath(CatBoost: https://catboost.ai/en/docs/ ) and we don't do any customization on their logs(a little tricky to do so).

Would it be possible to limit the number of iterations? The learn / test output above seems not improving much after the first 150 iterations. Can we specify 150 as max?

Technically possible. However, limiting number of iterations with such regressor seemed us as a bad idea. In this case maybe you don't observe too much change  after 150 iterations but for a different dataset it could be a totally different situation. We like to keep it more generic and welcoming to different datasets. You can always specify patience as a smaller number with Aydin API but again for the plugin we probably don't want to do this, so we can comfort various datasets.


PhantomJS 2.1.1 ReferenceError: Can't find variable: Map

my unit test can run successfully in the browser, but with phantomjs, it occurs an error below:
PhantomJS 2.1.1 (Windows 8 0.0.0) ERROR
ReferenceError: Can't find variable: Map
at C:/Users/handane/Desktop/react/Refactor/tests.webpack.js:46538 <- webpack:///~/react-render-hook/lib/componentMap.js:3:0

Looks like you'll need a ES6 Map polyfill for PhantomJS - https://www.npmjs.com/package/es6-map and use the es6-map/implement version.
Can you let me know if that works?

npm i -D babel-polyfill
2.the karma config looks like :
files: [ 'node_modules/babel-polyfill/dist/polyfill.js'],


atom-shell causing problems

https://github.com/brianmcd/contextify/pull/145
I hope this is just some temporary fork and that they'll move to io.js instead of running yet another fork. It will be impossible to support three things each claiming to be Node without any reliable way of telling them apart. Why can't v8 announce which version it is?

Why can't v8 announce which version it is?

I can try sending a patch.  I remember looking into it one time and not quite being able to figure out how their homegrown release script updated version numbers.

That would be good. However, Node forkers need to backport that patch too, because having it only in the very latest version of v8 won't do much good in the short time.

You can detect that the version macro is not there, that at least tells you something.  But yes, it won't do a great deal of good in the short term.

What if every fork could add a define to node-version.h
#define MY_UNIQUE_DEFINITION 1

or use a standard name, but unique value,
#define NODE_FORK_IDENTIFIER 23

It could work but it's not ideal because we're really only interested in the V8 version.  Also, it may be an unreliable indicator when linked against a shared libv8.

Here's some workaround possibilities; tl;dr PREPARSER_H in in 3.25 and 3.26 but not in 3.29, lots of changes in v8 3.14 to 3.25 (V8_ARRAY_BUFFER_VIEW_INTERNAL_FIELD_COUNT for instance)  I have not downloaded iojs yet.
node 11.14 and 11.13 (v8 3.26.33, 3.25.30)
bizarro% grep \\#define v8*
v8-debug.h:#define V8_V8_DEBUG_H_
v8-platform.h:#define V8_V8_PLATFORM_H_
v8-preparser.h:#define PREPARSER_H
v8-preparser.h:#define V8EXPORT __declspec(dllexport)
v8-preparser.h:#define V8EXPORT __declspec(dllimport)
v8-preparser.h:#define V8EXPORT
v8-preparser.h:#define V8EXPORT __attribute__ ((visibility("default")))
v8-preparser.h:#define V8EXPORT
v8-profiler.h:#define V8_V8_PROFILER_H_
v8-testing.h:#define V8_V8_TEST_H_
v8-util.h:#define V8_UTIL_H_
v8.h:#define V8_H_
v8.h:#define TYPE_CHECK(T, S)                                       \
v8.h:#define V8_ARRAY_BUFFER_INTERNAL_FIELD_COUNT 2
v8.h:#define V8_ARRAY_BUFFER_VIEW_INTERNAL_FIELD_COUNT 2
v8config.h:#define V8CONFIG_H_
v8stdint.h:#define V8STDINT_H_

atom-shell (v8 <IP_ADDRESS>)
bizarro% grep \\#define v8*
v8-debug.h:#define V8_V8_DEBUG_H_
v8-platform.h:#define V8_V8_PLATFORM_H_
v8-profiler.h:#define V8_V8_PROFILER_H_
v8-testing.h:#define V8_V8_TEST_H_
v8-util.h:#define V8_UTIL_H_
v8.h:#define V8_H_
v8.h:#define TYPE_CHECK(T, S)                                       \
v8.h:#define V8_ARRAY_BUFFER_INTERNAL_FIELD_COUNT 2
v8.h:#define V8_ARRAY_BUFFER_VIEW_INTERNAL_FIELD_COUNT 2
v8config.h:#define V8CONFIG_H_
v8stdint.h:#define V8STDINT_H_

node 10.35 (v8 <IP_ADDRESS>)
v8-debug.h:#define V8_V8_DEBUG_H_
v8-debug.h:#define EXPORT __declspec(dllexport)
v8-debug.h:#define EXPORT __declspec(dllimport)
v8-debug.h:#define EXPORT
v8-debug.h:#define EXPORT __attribute__ ((visibility("default")))
v8-debug.h:#define EXPORT
v8-platform.h:#define V8_V8_PLATFORM_H_
v8-preparser.h:#define PREPARSER_H
v8-preparser.h:#define V8EXPORT __declspec(dllexport)
v8-preparser.h:#define V8EXPORT __declspec(dllimport)
v8-preparser.h:#define V8EXPORT
v8-preparser.h:#define V8EXPORT __attribute__ ((visibility("default")))
v8-preparser.h:#define V8EXPORT
v8-profiler.h:#define V8_V8_PROFILER_H_
v8-profiler.h:#define V8EXPORT __declspec(dllexport)
v8-profiler.h:#define V8EXPORT __declspec(dllimport)
v8-profiler.h:#define V8EXPORT
v8-profiler.h:#define V8EXPORT __attribute__ ((visibility("default")))
v8-profiler.h:#define V8EXPORT
v8-testing.h:#define V8_V8_TEST_H_
v8-testing.h:#define V8EXPORT __declspec(dllexport)
v8-testing.h:#define V8EXPORT __declspec(dllimport)
v8-testing.h:#define V8EXPORT
v8-testing.h:#define V8EXPORT __attribute__ ((visibility("default")))
v8-testing.h:#define V8EXPORT
v8-util.h:#define V8_UTIL_H_
v8.h:#define V8_H_
v8.h:#define V8EXPORT __declspec(dllexport)
v8.h:#define V8EXPORT __declspec(dllimport)
v8.h:#define V8EXPORT
v8.h:#define V8EXPORT __attribute__ ((visibility("default")))
v8.h:#define V8EXPORT
v8.h:#define V8EXPORT
v8.h:#define TYPE_CHECK(T, S)                                       \
v8config.h:#define V8CONFIG_H_
v8stdint.h:#define V8STDINT_H_

Seems atom-shell is about to upgrade to Chromium 40 and will raise NODE_MODULE_VERSION to 100 https://github.com/atom/node/commit/83f1b415e95e4d47e70c1cd064fdf153fc65fc47 and move to io.js. Hopefully the original problem will resolve itself then.
However, being able to actually condition on the v8 version is still highly desirable.

100?  lol.  But there are still incompatible v8 that contextify (among others) have to worry about, though now it's 3 instead of 4 (although I don't know what will happen with node-webkit) if I remember correctly, the list node minor = 10,11,13,17,100 (but 100 == 17), or are you saying that io.js will also change to 100, but no atom might want their freedom and fork io.js too.
I think I have a solution in mind though, but it will take some cooperation.  Does anyone not use node-gyp these days?

io.js will stay in range 42 -- 100, atom will be 100+, nw.js will bundle io.js
I imagine atom needs forking mostly to match v8 versions with chrome, which no other project cares about.
This might all still be manageable, but the underlying problem of not being able to reliably identify the version of v8 remains.

Why do node.js and io.js not offer a V8 version macro of the embedded version? I think the V8 team won't add a macro because there were some tries before and they were rejected. But still a backporting problem :/

The problem is shared dependencies. Lesser packagers insist on removing bundled dependencies with no regard to patches and modifications.

This can be solved, I feel, so long as the maintainers of node-gyp are agreeable.

Hi, I'm upgrading atom-shell to Chrome 40, and I have noticed the problem with compatibility with nan.
In v1.6, nan assumes NODE_MODULE_VERSION < 42 is Node, otherwise it would be io.js v1.0.0. However atom-shell uses neither, we are currently using https://github.com/atom/node/commit/0d02515d6eb2d57cb602b3924c950936f9745adc which is io.js < v.1.0.0, because atom-shell uses the stable release of Chrome and from https://github.com/atom/node/commit/7f9a6c6213763fbc072e4052e7ce13c6c00648e4 io.js started to use ES6 octal literals that is not available in Chrome 40.
Once after atom-shell starts to use Chrome 41, I can safely set NODE_MODULE_VERSION to 42 to make atom-shell compatible with nan, however currently changing NODE_MODULE_VERSION to neither 42 or some value smaller won't work.
How about making nan compatible with V8 <IP_ADDRESS> (used by Chrome 40) when NODE_MODULE_VERSION is set to 41? So nan still works with Node and io.js v1.0.0, and I can set NODE_MODULE_VERSION to 41 in make atom-shell to make it compatible with nan.
And please make sure NODE_MODULE_VERSION in io.js bumps when V8 version changes, otherwise we will still have this headache  in future.

That might work, but the version matrix is already rather complicated. Adding another exception is not the preferred way, but remains a last resort. A related problem is testing, does atom run on travis? How to set it up? Can't know if something breaks if we can't test it.
io.js would not be interested in following chrome versions, will this problem not show up again in the future?

There is still some ongoing discussion on how to set up the release train (iojs/io.js#544) but I believe everyone agrees that io.js will stick to stable V8 releases in the future, meaning it's going to ship the V8 from the latest Chrome release.  We're currently at 4.1 and that won't change until 4.2 goes stable.


Earning multiplier

Earnings are multiplied by (up to) amount of clients, probably from the shipping earnings menu screen.

If this is still occuring, the easiest fix would be an edit that "If I'm not the host, I don't get paid by the shipping earnings."

Probably a good idea. (Although it's a bit late to be saying that. :P)


Extract the video url of a youtube live stream

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've searched known issues and the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
Hi, currently is it possible to extract the video URL of a youtube live stream from a youtube channel ?
If so, how do I go about doing it.
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

yt-dlp --print urls "URL"

yt-dlp --print urls "URL"

Sorry I just saw your message, I tried it but I'm only getting the hls m3u8 link of the current live stream on my YouTube channel.
Currently, I'm trying to retrieve the permanent video link of the live stream so can I send it to my viewers through a messaging app

ah, then
yt-dlp --print webpage_url "https://www.youtube.com/@yourchannel/live"

yt-dlp --print webpage_url "https://www.youtube.com/@yourchannel/live"

Thank you. I have been spending the last few hrs trying to figure this out 😅


SimpleRegressor Test Cases

Description of feature/enhancement
Test cases for SimpleRegressor class. This should ideally test multiple algorithms that are considered as the most "accurate".
Description of implementation
Use datasets directly from sklearn to remove the need data wrangling.
Why this is a good feature/enhancement
Will be able to have an automated way to validate SimpleRegressor class.
Additional context
n/a

@eranns for this issue would you mind creating a new directory labelled regressors under the tests directory?

@eranns for this issue would you mind creating a new directory labelled regressors under the tests directory?


Populate article Export-Trace

Related to https://github.com/MicrosoftDocs/windows-powershell-docs/pull/2493

Docs Build status updates of commit a990698:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2016-ps/provisioning/Export-Trace.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/provisioning/Export-Trace.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/provisioning/Export-Trace.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@get-itips  Do you have any comments?

@velkovb
Hi, Borislav,
After you resolve the file conflict, please @ mention me, and then I'll merge this PR.
Thanks!

@tiburd Conflicts resolved.

Docs Build status updates of commit fb6cbd3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2016-ps/provisioning/Export-Trace.md
:white_check_mark:Succeeded

docset/winserver2019-ps/provisioning/Export-Trace.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/provisioning/Export-Trace.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


merge from arlac77/npm-package-template-esm-only

package.json

chore(package): remove<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 -x 'tests/**/*' --temp-directory build/tmp ava && c8 report -r lcov -o build/coverage --temp-directory build/tmp
chore(engines<EMAIL_ADDRESS>
.travis.yml

chore(travis): (jobs.include)
chore(travis): add 12.13.1 remove 12.13.0 (jobs.include.node_js)
chore(travis): (script)

Codecov Report

Merging #872 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #872   +/-   ##
=======================================
  Coverage   88.55%   88.55%
=======================================
  Files           7        7
  Lines         769      769
  Branches       92       92
=======================================
  Hits          681      681
  Misses         87       87
  Partials        1        1

Continue to review full report at Codecov.

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

:tada: This PR is included in version 5.3.8 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Bug]: WAZ not parsing properly

Describe the bug
This is an example article that does not get parsed (plaintext is None) https://www.waz.de/sport/lokalsport/bochum/article241975812/Tabubruch-Wattenscheid-Fans-schreiben-an-die-Stadt-Bochum.html
How to reproduce
from fundus import Crawler, PublisherCollection

crawler = Crawler(PublisherCollection.de)

for article in crawler.crawl(max_articles=50, only_complete=False):
    print(article.title)
    print(article.free_access)
    print(article.html.responded_url)
    print(article.authors)
    print(article.topics)
    print(article.plaintext)
    print("\n")

Expected behavior.
Parsed Plaintext
Logs and Stack traces
„Tabubruch“: Wattenscheid-Fans schreiben Offenen Brief an die Stadt Bochum
True
https://www.waz.de/sport/lokalsport/bochum/article241975812/Tabubruch-Wattenscheid-Fans-schreiben-an-die-Stadt-Bochum.html
['Philipp Ziser']
['Sporteinrichtung', 'Sportpolitik', 'Verein', 'Bochum', 'Milton Keynes', 'SG Wattenscheid 09', 'VfL Bochum', 'WAZ-Gruppe']
None

Screenshots
No response
Additional Context
No response
Environment
MACOS

Hey @addie9800 thanks for reporting this.
It seems that there is already a PR #388 open, addressing some Issues regarding waz. Does this still happen using said branch?

No, my bad. I came across this issue while working on another PR and didn't remember that you had already fixed it.


add test_connection option to RESTler

Description
It is currently difficult to debug when RESTler cannot reach the service.  A new option should be added (for example, restler test_connection <all or a subset of restler test arguments> which simply tries to connect to the service and provides detailed diagnostic information if there is a failure.

Related issues: #631, #445

This should provide good diagnostics in cases where the host name is missing or incorrect.  Also, if the spec is using x-ms-parameterized-host, the diagnostics should make it clear that the host name needs to be specified.


Unable to get raw Left & Right IR streams from D415

Probably related to #1140 and #1707, but opening new issue since I am using D415 and not using OpenCV

Tried various combinations of resolution, format, fps, stream indexes, not specifying stream indexes, enabling depth stream like suggested in #1140. But I cant get both raw streams. I can get one raw stream and the depth

I included the rs-sensor-control output on supported streams at the end

Required Info

Camera Model
D415

Firmware Version
<IP_ADDRESS>

Operating System & Version
Win 10

Platform
PC

SDK Version
2

Issue Description
Unable to get left & right raw IR from D415
I am getting the exception
RealSense error calling rs2_pipeline_start_with_config(pipe:0000021B41720E90, config:0000021AFCE11240):
Failed to resolve request. No device found that satisfies all requirements
	cfg.enable_stream(RS2_STREAM_INFRARED, 1, 1280, 720, RS2_FORMAT_Y8, 30);
	cfg.enable_stream(RS2_STREAM_INFRARED, 2, 1280, 720, RS2_FORMAT_Y8, 30);

	//cfg.enable_stream(RS2_STREAM_INFRARED, 0, 640, 480, RS2_FORMAT_UYVY); // << works by itself, gets index 0
	//cfg.enable_stream(RS2_STREAM_INFRARED, -1, 640, 480, RS2_FORMAT_Y8); // << works by itself, gets index 1
	//cfg.enable_stream(RS2_STREAM_INFRARED, 1, 640, 480, RS2_FORMAT_Y8); // << works by itself, gets index 1
	//cfg.enable_stream(RS2_STREAM_INFRARED, 2);
	//cfg.enable_stream(RS2_STREAM_INFRARED, 2, 1280, 720, RS2_FORMAT_Y8, 30);
	//cfg.enable_stream(RS2_STREAM_DEPTH);
	// Declare RealSense pipeline, encapsulating the actual device and sensors
	rs2::pipeline pipe;
	// Start streaming with default recommended configuration
	pipe.start(cfg);

0  : Infared #0 (Video Stream: UYVY 1280x720@ 6Hz)
1  : Infrared #1 (Video Stream: Y8 1280x720@ 6Hz)
2  : Infrared #0 (Video Stream: BGRA8 1280x720@ 6Hz)
3  : Infrared #0 (Video Stream: RGBA8 1280x720@ 6Hz)
4  : Infrared #0 (Video Stream: BGR8 1280x720@ 6Hz)
5  : Infrared #0 (Video Stream: RGB8 1280x720@ 6Hz)
6  : Infrared #0 (Video Stream: UYVY 1280x720@ 4Hz)
7  : Infrared #1 (Video Stream: Y8 1280x720@ 4Hz)
8  : Infrared #0 (Video Stream: BGRA8 1280x720@ 4Hz)
9  : Infrared #0 (Video Stream: RGBA8 1280x720@ 4Hz)
10 : Infrared #0 (Video Stream: BGR8 1280x720@ 4Hz)
11 : Infrared #0 (Video Stream: RGB8 1280x720@ 4Hz)
12 : Infrared #0 (Video Stream: UYVY 640x480@ 30Hz)
13 : Infrared #1 (Video Stream: Y8 640x480@ 30Hz)
14 : Infrared #0 (Video Stream: BGRA8 640x480@ 30Hz)
15 : Infrared #0 (Video Stream: RGBA8 640x480@ 30Hz)
16 : Infrared #0 (Video Stream: BGR8 640x480@ 30Hz)
17 : Infrared #0 (Video Stream: RGB8 640x480@ 30Hz)
18 : Infrared #0 (Video Stream: UYVY 640x480@ 15Hz)
19 : Infrared #1 (Video Stream: Y8 640x480@ 15Hz)
20 : Infrared #0 (Video Stream: BGRA8 640x480@ 15Hz)
21 : Infrared #0 (Video Stream: RGBA8 640x480@ 15Hz)
22 : Infrared #0 (Video Stream: BGR8 640x480@ 15Hz)
23 : Infrared #0 (Video Stream: RGB8 640x480@ 15Hz)
24 : Infrared #0 (Video Stream: UYVY 640x480@ 6Hz)
25 : Infrared #1 (Video Stream: Y8 640x480@ 6Hz)
26 : Infrared #0 (Video Stream: BGRA8 640x480@ 6Hz)
27 : Infrared #0 (Video Stream: RGBA8 640x480@ 6Hz)
28 : Infrared #0 (Video Stream: BGR8 640x480@ 6Hz)
29 : Infrared #0 (Video Stream: RGB8 640x480@ 6Hz)
30 : Infrared #0 (Video Stream: UYVY 640x480@ 4Hz)
31 : Infrared #1 (Video Stream: Y8 640x480@ 4Hz)
32 : Infrared #0 (Video Stream: BGRA8 640x480@ 4Hz)
33 : Infrared #0 (Video Stream: RGBA8 640x480@ 4Hz)
34 : Infrared #0 (Video Stream: BGR8 640x480@ 4Hz)
35 : Infrared #0 (Video Stream: RGB8 640x480@ 4Hz)
36 : Infrared #0 (Video Stream: UYVY 480x270@ 60Hz)
37 : Infrared #1 (Video Stream: Y8 480x270@ 60Hz)
38 : Infrared #0 (Video Stream: BGRA8 480x270@ 60Hz)
39 : Infrared #0 (Video Stream: RGBA8 480x270@ 60Hz)
40 : Infrared #0 (Video Stream: BGR8 480x270@ 60Hz)
41 : Infrared #0 (Video Stream: RGB8 480x270@ 60Hz)
42 : Infrared #0 (Video Stream: UYVY 480x270@ 30Hz)
43 : Infrared #1 (Video Stream: Y8 480x270@ 30Hz)
44 : Infrared #0 (Video Stream: BGRA8 480x270@ 30Hz)
45 : Infrared #0 (Video Stream: RGBA8 480x270@ 30Hz)
46 : Infrared #0 (Video Stream: BGR8 480x270@ 30Hz)
47 : Infrared #0 (Video Stream: RGB8 480x270@ 30Hz)
48 : Infrared #0 (Video Stream: UYVY 480x270@ 15Hz)
49 : Infrared #1 (Video Stream: Y8 480x270@ 15Hz)
50 : Infrared #0 (Video Stream: BGRA8 480x270@ 15Hz)
51 : Infrared #0 (Video Stream: RGBA8 480x270@ 15Hz)
52 : Infrared #0 (Video Stream: BGR8 480x270@ 15Hz)
53 : Infrared #0 (Video Stream: RGB8 480x270@ 15Hz)
54 : Infrared #0 (Video Stream: UYVY 480x270@ 6Hz)
55 : Infrared #1 (Video Stream: Y8 480x270@ 6Hz)
56 : Infrared #0 (Video Stream: BGRA8 480x270@ 6Hz)
57 : Infrared #0 (Video Stream: RGBA8 480x270@ 6Hz)
58 : Infrared #0 (Video Stream: BGR8 480x270@ 6Hz)
59 : Infrared #0 (Video Stream: RGB8 480x270@ 6Hz)
60 : Infrared #0 (Video Stream: UYVY 480x270@ 4Hz)
61 : Infrared #1 (Video Stream: Y8 480x270@ 4Hz)
62 : Infrared #0 (Video Stream: BGRA8 480x270@ 4Hz)
63 : Infrared #0 (Video Stream: RGBA8 480x270@ 4Hz)
64 : Infrared #0 (Video Stream: BGR8 480x270@ 4Hz)
65 : Infrared #0 (Video Stream: RGB8 480x270@ 4Hz)
66 : Depth #0 (Video Stream: Z16 1280x720@ 6Hz)
67 : Depth #0 (Video Stream: Z16 1280x720@ 4Hz)
68 : Depth #0 (Video Stream: Z16 640x480@ 30Hz)
69 : Depth #0 (Video Stream: Z16 640x480@ 15Hz)
70 : Depth #0 (Video Stream: Z16 640x480@ 6Hz)
71 : Depth #0 (Video Stream: Z16 640x480@ 4Hz)
72 : Depth #0 (Video Stream: Z16 480x270@ 60Hz)
73 : Depth #0 (Video Stream: Z16 480x270@ 30Hz)
74 : Depth #0 (Video Stream: Z16 480x270@ 15Hz)
75 : Depth #0 (Video Stream: Z16 480x270@ 6Hz)
76 : Depth #0 (Video Stream: Z16 480x270@ 4Hz)`

Hi @arunrajagopalan
What about realsense-viewer? Can you find the desired configuration in the viewer?
If I recall correctly, the D400 come out of the box with Right IR stream disabled but you can unlock it by activating advanced mode (the simplest way is by activating one of the visual presets from the viewer).

Ok, so if you can modify presets and use the advanced mode params, the camera is already in advanced mode, that's good.
What version of the SDK you use?
We had a bug prior to 2.11.1 (@ev-mp, can you confirm please) that affected specific Windows 10 versions (RS3 build) and may be related to what you experience.

Hello @arunrajagopalan ,
The log and the description indicate that D415 is recognized as USB2 (and not USB3) device. In USB2 mode the device is designed to expose only a subset of streaming profiles according to USB bandwidth budget.
Running Realsense-Viewer will present the USB connection type. Make sure it displays USB3+ mode, otherwise check the cable/USB connectors/port to fix it.

@ev-mp Realsense-Viewer is showing USB 3.1 when connected to one port and USB 3.0 when connected to another port

@dorodnic SDK version is 2.11.1

Hi @arunrajagopalan , what is the windows build you're using (type "winver").
The port that reports 3.1 is configured correctly. You should be able to stream Left+Right IR/HD in 30fps.
With regards to 3.0 - it is not common that a PC has multiple USB3 controllers, are you using USB3 PCI-E extension?
Additionally, can you post output of rs-enumerate-devices when connecting the camera to both ports ?

@ev-mp  winver is Version 1803, OS Build 17134.48
Attachment has enumerate devices output
PS: my responses may be delayed for a couple days. I appreciate very much your help!
rs-enumerate-devices.txt

[Realsense Customer Engineering Team Comment]
hi @arunrajagopalan,
I've confirmed D415 with Realsense viewer, I can do IR stream from Left and Right IR camera at the same time under 1280x720x30fps, from your rs-enumerate-devices also say this is supported.
since you mentioned your realsense viewer have only single IR stream, can you please confirm that D415 us showing USB3.1 and you checked Infra 1 and Infra 2 under Stereo Module when stream is off?
if so can you please find another PC and see if the issue can reproduce on the other PC?
would like to identify if this issue is PC depended.
thanks.

Folks, I got a different PC . I am able to get the left and right IR from the d415 with 1280x720 x 30 fps on a USB 3.1 on that PC. The posted code also works and gets both streams
On the first computer … an ideapad, the realsense viewer shows both IR left & right on the 3.1 port,.
However the code to get the streams fails. Not sure why. So @RealSense-Customer-Engineering I agree its PC dependent. But since the viewer sees both cameras but the posted code doesn't, I would think somethings wrong with my code too

Fols, I can get both streams on the New PC now, even in the code. So this is definitely PC dependent.

[Realsense Customer Engineering Team Comment]
hi @arunrajagopalan,
thanks for confirm, so maybe we can close this ticket and please feel free to create new ticket if any follow up question?

I think we can close it, but it would be good to know what about the PC makes it not work

I am having the frame drop problem on a notebook. Any advances in knowing what it is about the PC that may cause problems?

I am facing a weird issue. Using code or realsense viewer, I am not able to simultaneously get both infrared images. (2 images show up but they don't have any offset/disparity between them)
But if I stream only left and right independently, then I get the different images (disparity is present)
Any idea what is causing this?


[Help] how to use shared entities between Electron and vue

Hello,
I want to use shared entities between Electron and Vue.
Where should I put them and how to configure that?
Thank you.

The location of the placement is not the point.
You have to make it clear that the Renderer-Process and the Main-Process are two processes, there is no common entity, just simply use the same copy of the code.

@caoxiemeihao  Imagine you are defining a types.ts file for declaring types and interfaces in typescript and you should probably be able to access this file in main and renderer process. so how to achieve this?

@alisherafat01 You can try see this https://github.com/electron-vite/electron-vite-vue/issues/429

@caoxiemeihao I can't read that language


Ability to remove UIView from runtime

I would like a function that allows me to remove all features and functionality runtime.add added to my UIView. In another, a function that will make my UIView back to normal.

Our short-term solution for this may be to ensure that all interactions support being disabled.

Yea, this is what I was going to suggest in discord.
On Fri, Apr 14, 2017, 11:38 AM featherless<EMAIL_ADDRESS>wrote:

Our short-term solution for this may be to ensure that all interactions
support being disabled.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/material-motion/material-motion-swift/issues/98#issuecomment-294210795,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAr8KprZfi1N7028_zhAF4moFcwFVNRqks5rv70ZgaJpZM4M91xh
.

Going to mark this as won't fix for now with the recommendation being to use the enabled property on relevant interactions. Please reopen if this isn't sufficient for your use cases.


Get " ‘Use’ is not a member of ‘node::Buffer’" when install

When I use "npm install && node install.js" to install jupyter-nodejs,I get a Error say this:
... ... ... ... ... ... ... ...
../node_modules/nan/nan.h:683:12: error: ‘Use’ is not a member of ‘node::Buffer’
return node::Buffer::Use(v8::Isolate::GetCurrent(), data, size);
^
make: *** [Release/obj.target/contextify/src/contextify.o] 错误 1
make:离开目录“/home/duhan/.jupyter/jupyter-nodejs/node_modules/contextify/build”
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/duhan/.nvm/versions/node/v4.1.2/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:270:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 3.13.0-61-generic
gyp ERR! command "/home/duhan/.nvm/versions/node/v4.1.2/bin/node" "/home/duhan/.nvm/versions/node/v4.1.2/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/duhan/.jupyter/jupyter-nodejs/node_modules/contextify
gyp ERR! node -v v4.1.2
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok
npm ERR! Linux 3.13.0-61-generic
npm ERR! argv "/home/duhan/.nvm/versions/node/v4.1.2/bin/node" "/home/duhan/.nvm/versions/node/v4.1.2/bin/npm" "install"
npm ERR! node v4.1.2
npm ERR! npm  v2.14.4
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the contextify package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls contextify
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/duhan/.jupyter/jupyter-nodejs/npm-debug.log
How can I do to pass the install??

I just fixed this, by removing the contextify dependency


Wrong word

In this sentence:
As a result, the JWT token issued by Azure AD B2C, omits the family_name instead of ClaimType name surname.
omit should be emit

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

ID: 3e31c230-4294-6b21-91c2-b829852f80a3
Version Independent ID: ea251507-2a65-6ceb-0ccf-fa4f75133fa3
Content: ClaimsSchema  - Azure Active Directory B2C
Content Source: articles/active-directory-b2c/claimsschema.md
Service: active-directory
GitHub Login: @davidmu1
Microsoft Alias: davidmu

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

@rbrayb The PR for the fix has been created and it will be merged soon. Thanks again for pointing this out, I am closing the issue based on this update, please let us know if there is something else that we can help you with.


#52 Expand channel documentation

Closes #52
A small PR based on what I learned about channels. Regard every change I made with suspicion, I am still starting out in learning about channels, multithreaded communication etc.
I very deliberately stole a lot of the descriptions from Nim's channels_builtin module (example ) and adjusted them to keep descriptions somewhat consistent.
I also added an external hyperlink to std/isolation to the general module docs, because the imports don't show in them and neither does Isolated have any hyperlinks to its own type. This makes it unclear for users where to find the type if they have no context (I mean, I had none, I'm just diving into the multithreading space now) and therefore there should be a link somewhere.
I am also very uncertain about a sentence I used repeatedly here:
## The memory src is moved, not copied.
That is my current understanding of threading/channels, but I don't quite know that for sure, so if that needs correcting please say so.

Sorry, I'm late to the party. Scanned through the changes and in general it's all good with an exception of tryRecv. Usually, "can fail for all sort of reasons" is not what you want to put in the documentation :P.
The fail case is single and known: an empty channel.
Moreover, "This returns immediately" is also not guaranteed, we're trying to acquire the lock unconditionally after all. May be we need to add the clarification that the procs don't block waiting for the data/space to appear in the channels, but block on lock contention.

Happy to make a correction PR!
The failure bit I just took from builtin_channels.nim, the fact that tryRecv does not return immediately was actually not known to me, thanks for explainer!


Cannot access sails config in grunt task

I have written a custom grunt task that needs to access the sails config.
module.exports = function (grunt) {
  grunt.registerTask('customtask', function () {
    console.log(sails.config.session.secret);
  });
};

But i cannot access the sails object. I get the following error:
Warning: sails is not defined Use --force to continue.

Aborted due to warnings.

How can I access the sails config?
(Also how can I access the services?)

I believe this is due to Grunt running before Sails does. What I've done in the past is just manually require the config file:
var configLocal = require('./config/local.js');

Is there a better solution?
I like that Sails builds all the assets each run, and it depends on the environment I set.
And I like that Sails has a powerful config that also depends on the environment.
It'll be good to unite this two for custom grunt tasks.

Curses. This is what I feared. Now I'll have to do something fairly hacky.
I need to access the sails base url because I'm running behind a proxy (in a subfolder), which breaks all the absolute paths that are in the default sails-linker.


chore: Update tf version to 0.12.0

Description
Updates the version to 0.12.0
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that validate the behaviour of the software
[ ] I validated that new and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have bumped the version of the library

This tries to merge from 1.4 to main.


The "test_videodatainfo.json" is not available from MSR anymore

Hi,
The "test_videodatainfo.json" is not available from MSR-VTT official website anymore. So, right now we cannot execute "run_s2vt.py --test" anymore. It generates an error at line 67.
Can you please provide the "test_videodatainfo.json"?
Thanks,
Peratham

They still provide "test_annotation.zip" but there is no "test_videodatainfo.json". It has "test_videodatainfo_nosen.json" instead which means there is no sentence annotation release anymore...

OK. I found the link http://ms-multimedia-challenge.com/static/resource/test_videodatainfo.json. They removed the old test data when they updated their webpage for the 2017 competition.

Hi!
Thanks for pointing to this. Indeed, they rearranged the data for 2017 challenge but old versions are still available (maybe temporarily) by direct links. I added them to readme.
Right now they provide only json with an index and links to 10k files on YouTube. Some of original files might be deleted from YouTube.

:)

@ramanishka Hi, the download of "train_val_annovation.zip" always failed, do you know where i can find them?
@Peratham Hi,I see you find test_annotation.zip, could you offer me the link?
Thanks,
Victoria


Emoji Request: Black Bird

Official Emoji Name: BLACK BIRD
Unicode codepoint: U+1F426 U+200D U+2B1B
Link to emoji (On cubeupload or assets): https://assets.scratch.mit.edu/6f1bb911aad77a088b6fb8cb09b25358.png
An adaptation of notwait's BIRD.

I had made that one back in February, but whoever put the normal bird forgot to put the black bird https://u.cubeupload.com/notwait/blackbird.png
https://scratch.mit.edu/discuss/post/6968863/

I've added @notwait's version; its colour scheme is more in line with the rest of the emojis.

I had made that one back in February, but whoever put the normal bird forgot to put the black bird

That would be @lopste. The black bird emoji is new to Emoji 15.0, which I had just added support for, so he may have assumed it wasn't supported.


adding key

please test this

Can one of the admins verify this patch?

please test this

please test this

please test this

please test this

please test this

ok to test

please test this

please test this

Both Travis and Jenkins builds have passed, so merging this pull request.


Refactor nox to separate integration tests

This PR removes all integrations deps from dev dependencies
and instead adds them to a new group in poetry, you can install
all like this:
poetry install --with integrations

Meanwhile on CI will be able to run tests based on the individual
dependency. This should make it easier to tests with newer python versions

Hi, thanks for contributing to Strawberry 🍓!
We noticed that this PR is missing a RELEASE.md file. We use that to automatically do releases here on GitHub and, most importantly, to PyPI!
So as soon as this PR is merged, a release will be made 🚀.
Here's an example of RELEASE.md:
Release type: patch

Description of the changes, ideally with some examples, if adding a new feature.

Release type can be one of patch, minor or major. We use semver, so make sure to pick the appropriate type. If in doubt feel free to ask :)
Here's the tweet text:
🆕 Release (next) is out! Thanks to @patrick91 for the PR 👏

Get it here 👉 https://github.com/strawberry-graphql/strawberry/releases/tag/(next)

Apollo Federation Subgraph Compatibility Results

Federation 1 SupportFederation 2 Support

_service🟢@key (single)🟢@key (multi)🟢@key (composite)🟢repeatable @key🟢@requires🟢@provides🟢federated tracing🔲@link🟢@shareable🟢@tag🟢@override🟢@inaccessible🟢@composeDirective🟢@interfaceObject🟢

Learn more:

Apollo Federation Subgraph Specification
Compatibility Tests

Btw, don't know if it is codecov that is going crazy or something wrong in this change, but codecov is reporting a -5.23% project coverage

Btw, don't know if it is codecov that is going crazy or something wrong in this change, but codecov is reporting a -5.23% project coverage

this is because of the changes, I'm still not done (I thought I was) :D

yay!

Merging #2950 (https://github.com/strawberry-graphql/strawberry/commit/cb7efcfed832222e65f23b9bd172c0c5372c3595) into main (https://github.com/strawberry-graphql/strawberry/commit/60bfd7639c612f0dbd34a14f0a75823c34802246) will increase coverage by 0.24%.
The diff coverage is 94.08%.

yay!

Merging #2950 (https://github.com/strawberry-graphql/strawberry/commit/cb7efcfed832222e65f23b9bd172c0c5372c3595) into main (https://github.com/strawberry-graphql/strawberry/commit/60bfd7639c612f0dbd34a14f0a75823c34802246) will increase coverage by 0.24%.
The diff coverage is 94.08%.


Enable automatic webhook installation

Switch the webhook service to use secrets by Istio CA
Patching the K8S webhook config on startup
Fix the webhook Helm templates.
Tested it for both intall.sh and make deploy/all

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ldemailly
Assign the PR to them by writing /assign @ldemailly in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@yusuoh: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
a2a276ff86d59363991482fcf0713df1f4e47821
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yusuoh: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
a2a276ff86d59363991482fcf0713df1f4e47821
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-v1alpha3.sh
a2a276ff86d59363991482fcf0713df1f4e47821
link
/test istio-pilot-e2e-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yusuoh: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-v1alpha3.sh
a2a276ff86d59363991482fcf0713df1f4e47821
link
/test istio-pilot-e2e-v1alpha3

prow/istio-pilot-e2e.sh
4ede16dcd940f2047b73e3327e3f0cead01750c4
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yusuoh: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
4ede16dcd940f2047b73e3327e3f0cead01750c4
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-v1alpha3.sh
4ede16dcd940f2047b73e3327e3f0cead01750c4
link
/test istio-pilot-e2e-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

overall patch looks really good!  I'm a little concerned about the handling of the mutating web hook on platforms that don't have that enabled.  I think we either want to switch to a flag to enable mutating web hooks (rather than discern it from the Capabilities feature) - and then use the Capabilities feature to expose an error if the flag is true and capabilities indicate no webhook support.  I have asked @jascott1 to offer any suggestions (Helm reviewer).
This allows folks to disable mutating webhooks and use manual injection if they, for whatever reason, don't have a cluster which supports mutating webhooks and use manual injection instead.
That is the best suggestion I have - perhaps @jascott1 has a better one.

We already have a flag in Helm (sidecar-injector.enabled) to switch on and off the sidecar service as a whole. The sidecar injector is implemented based on the webhook mechanism and won't work well if it is not supported. It is not very useful if we only install the sidecar injector webhook service but not the webhook config part. So I think a single flag should be good enough.
The question is how to enable/disable the flag based on the platform. I wonder whether we can move the logic to the deployment phase. E.g. use capability to generate the values.yaml, instead of doing the check in templates themselves. We want the Helm templates to be used for Istio release, so they should not have any dependency on those dynamic features.

@yusuoh: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-v1alpha3.sh
4ede16dcd940f2047b73e3327e3f0cead01750c4
link
/test istio-pilot-e2e-v1alpha3

prow/istio-pilot-e2e.sh
f54f72b065dde46064839efad03a74c12c9f61d4
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yusuoh: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
f54f72b065dde46064839efad03a74c12c9f61d4
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-v1alpha3.sh
f54f72b065dde46064839efad03a74c12c9f61d4
link
/test istio-pilot-e2e-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Can I have a lgtm for this PR? We need to make it work first and tune other parts later.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: costinm
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [costinm]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@yusuoh: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
f54f72b065dde46064839efad03a74c12c9f61d4
link
/test istio-pilot-e2e

prow/istio-pilot-e2e-v1alpha3.sh
f54f72b065dde46064839efad03a74c12c9f61d4
link
/test istio-pilot-e2e-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yusuoh: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-v1alpha3.sh
f54f72b065dde46064839efad03a74c12c9f61d4
link
/test istio-pilot-e2e-v1alpha3

prow/istio-pilot-e2e.sh
f54f72b065dde46064839efad03a74c12c9f61d4
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yusuoh @ayj This PR breaks prow/e2e-simpleTests.sh and prow/e2e-bookInfoTests.sh
Please fix it.
kubectl logs -n simple-auth-test-6498f9f8b3e2401c9d37   istio-ca-5bfc5489c7-jzfkm
Error: unknown flag: --append-dns-names
Usage:
istio_ca [flags]
istio_ca [command]
Available Commands:
help        Help about any command
probe       Check the liveness or readiness of a locally-running server
version     Prints out build version information
Flags:
--cert-chain string                          Path to the certificate chain file
--grpc-hostname string                       The hostname for GRPC server. (default "localhost")
2018-03-30T11:38:00.929005Z     error   unknown flag: --append-dns-names
--grpc-port int                              The port number for GRPC server. If unspecified, Istio CA will not server GRPC request.
-h, --help                                       help for istio_ca
--istio-ca-storage-namespace string          Namespace where the Istio CA pods is running. Will not be used if explicit file or other storage mechanism is specified. (default "istio-system")
--kube-config string                         Specifies path to kubeconfig file. This must be specified when not running inside a Kubernetes pod.
--listened-namespace string                  Select a namespace for the CA to listen to. If unspecified, Istio CA tries to use the ${NAMESPACE} environment variable. If neither is set, Istio CA listens to all namespaces.
--liveness-probe-interval duration           Interval of updating file for the liveness probe.
--liveness-probe-path string                 Path to the file for the liveness probe.
--log_as_json                                Whether to format output as JSON or in plain console-friendly format
--log_callers                                Include caller information, useful for debugging
--log_output_level string                    The minimum logging level of messages to output, can be one of "debug", "info", "warn", "error", or "none" (default "info")
--log_rotate string                          The path for the optional rotating log file
--log_rotate_max_age int                     The maximum age in days of a log file beyond which the file is rotated (0 indicates no limit) (default 30)
--log_rotate_max_backups int                 The maximum number of log file backups to keep before older files are deleted (0 indicates no limit) (default 1000)
--log_rotate_max_size int                    The maximum size in megabytes of a log file beyond which the file is rotated (default 104857600)
--log_stacktrace_level string                The minimum logging level at which stack traces are captured, can be one of "debug", "info", "warn", "error", or "none" (default "none")
--log_target stringArray                     The set of paths where to output the log. This can be any path as well as the special values stdout and stderr (default [stdout])
--max-workload-cert-ttl duration             The max TTL of issued workload certificates (default 168h0m0s)
--probe-check-interval duration              Interval of checking the liveness of the CA. (default 30s)
--root-cert string                           Path to the root certificate file
--self-signed-ca                             Indicates whether to use auto-generated self-signed CA certificate. When set to true, the '--signing-cert' and '--signing-key' options are ignored.
--self-signed-ca-cert-ttl duration           The TTL of self-signed CA root certificate (default 8760h0m0s)
--self-signed-ca-org string                  The issuer organization used in self-signed CA certificate (default to k8s.cluster.local) (default "k8s.cluster.local")
--signing-cert string                        Path to the CA signing certificate file
--signing-key string                         Path to the CA signing key file
--upstream-auth string                       Specifies how the Istio CA is authenticated to the upstream CA. (default "mtls")
--upstream-ca-address string                 The IP:port address of the upstream CA. When set, the CA will rely on the upstream Istio CA to provision its own certificate.
--upstream-ca-cert-file string               Path to the certificate for authenticating upstream CA.
--workload-cert-grace-period-ratio float32   The workload certificate rotation grace period, as a ratio of the workload certificate TTL. (default 0.5)
--workload-cert-min-grace-period duration    The minimum workload certificate rotation grace period. (default 10m0s)
--workload-cert-ttl duration                 The TTL of issued workload certificates (default 19h0m0s)
Use "istio_ca [command] --help" for more information about a command.

@sbezverk It seems that the CA image is not built using the latest version. Please make sure that the TAG and HUB options are set to latest one when running the e2e test.

@yusuoh Last night I cloned latest master, create a private branch and run this test. Is cloning the latest master not guarantee that the latest tags will be used?

I think you also need to build the docker images locally before running the e2e test.
See
https://github.com/istio/istio/tree/master/tests/e2e#step-4-export-test-script-variables

@sbezverk did you try rebuilding your images from master?
Cheers
-steve


[Production] Create composite indexes for departed users

Issue Description
To enable the proper execution of the departed users and orphaned tasks APIs, composite indexes must be added in Firebase. The relevant links are provided below for reference:
https://console.firebase.google.com/v1/r/project/<project-id>/firestore/indexes?create_composite=Clpwcm9qZWN0cy9yZHMtYmFja2VuZC0yYzMwZC9kYXRhYmFzZXMvKGRlZmF1bHQpL2NvbGxlY3Rpb25Hcm91cHMvdXNlcnMvaW5kZXhlcy9DSUNBZ0ppbTE0QUsQARoSCg5yb2xlcy5hcmNoaXZlZBABGhQKEHJvbGVzLmluX2Rpc2NvcmQQARoMCgh1c2VybmFtZRABGgwKCF9fbmFtZV9fEAE
https://console.firebase.google.com/v1/r/project/<project-id>/firestore/indexes?create_composite=Ck9wcm9qZWN0cy9yZHMtYmFja2VuZC0yYzMwZC9kYXRhYmFzZXMvKGRlZmF1bHQpL2NvbGxlY3Rpb25Hcm91cHMvdXNlcnMvaW5kZXhlcy9fEAEaEgoOcm9sZXMuYXJjaGl2ZWQQARoUChByb2xlcy5pbl9kaXNjb3JkEAEaFgoSdXNlcm5hbWVfbG93ZXJjYXNlEAEaDAoIX19uYW1lX18QAQ
https://console.firebase.google.com/v1/r/project/<project-id>/firestore/indexes?create_composite=Ck9wcm9qZWN0cy9yZHMtYmFja2VuZC0yYzMwZC9kYXRhYmFzZXMvKGRlZmF1bHQpL2NvbGxlY3Rpb25Hcm91cHMvdXNlcnMvaW5kZXhlcy9fEAEaEgoOcm9sZXMuYXJjaGl2ZWQQARoUChByb2xlcy5pbl9kaXNjb3JkEAEaGAoUZmlyc3RfbmFtZV9sb3dlcmNhc2UQARoMCghfX25hbWVfXxAB
https://console.firebase.google.com/v1/r/project/<project-id>/firestore/indexes?create_composite=Ck9wcm9qZWN0cy9yZHMtYmFja2VuZC0yYzMwZC9kYXRhYmFzZXMvKGRlZmF1bHQpL2NvbGxlY3Rpb25Hcm91cHMvdXNlcnMvaW5kZXhlcy9fEAEaEgoOcm9sZXMuYXJjaGl2ZWQQARoUChByb2xlcy5pbl9kaXNjb3JkEAEaFwoTbGFzdF9uYW1lX2xvd2VyY2FzZRABGgwKCF9fbmFtZV9fEAE
Expected Behavior
The departed users api must work as expected without any issues related to composite index creation in firebase.
Current Behavior
The departed users api (users?departed=true&dev=true) will fail with 500 status once deployed to production.
Screenshots

Steps to follow for each of the above links:

Replace <project-id> in the link with the staging project ID.
Open the modified link in your browser.
Review the composite index details displayed on the Firebase Console.
Click Save to add the composite index.
Wait for the index to finish building in the Composite Indexes section of Firestore.

@prakashchoudhary07 Can you please help in adding these composite indexes in production firebase.

@iamitprakash Can you please help in adding these composite indexes in production firebase.


Cannot export all my repos

Hi, I am trying to use vcstool to export the repository states to a file. All the repos share the same folder, so that I run  vcs export > repos.cfg and the output is almost OK:
folderA/repo1: Could not determine ref: fatal: No upstream configured for branch 'branch1'
folderB/repo2:: Could not determine ref: fatal: No upstream configured for branch 'branch2'
The configuration for these repos and the others are exactly the same (non of them have an upstream remote, but a origin). Why does this error exactly mean ?

Your branches branch1 / branch2 are likely not tracking a remote branch. I assume you can't call git pull for those successfully either. Can you confirm this?
This can happen if you have create the branches only locally or only pushed them to origin or upstreamwith -u. If this is the case git does not know which remote branch you local branch is associated to and therefore vcstool can't generate a url / version for it.

Hi Dirk,
Both repos have the origin remote properly set (I regularly pull). These branches are created with git checkout -b and then I push them (usually without the -u option), but I can do git pull origin branchX in all cases.
However, you are right :) After doing git push -u origin branchX I got the message
 Branch X set up to track remote branch X from origin. Everything up-to-date
And now there it no warning (it is surprising that my other repos are working, I never do the -u!). Thank you so much!

@jvgomez just as a note: On recent git versions, if you check out a remote branch as a local branch for the first time using git checkout my-branch (which works as long as my-branch is unique among your remotes), then the local branch is set up to be tracking automagically.

I see, and now everything makes sense, thank you @NikolausDemmel !


fix: use fs.createWriteStream instead of fs-extra

In one of our services the packaging process seems to be hanging after opening the write stream to a zipped file. The stream seems to be creates, but the open event never fires. Nothing is written to the file and no errors occur.
I couldn't find any difference between several projects and this one, and the only thing that seems to have helped is switching to using createWriteStream from the fs package instead of fs-extra. I don't think using fs-extra for this particular function provides any benefit?
Weirdly enough, if I create a separate file like this and run it I get the contents written to the file:
const fs = require("fs-extra");
const output = fs.createWriteStream(/* zip path here */);

output.on('open', () => {
  output.write('test')
  output.end()
});

Please let me know how to proceed. Thanks.

Hello what versions of serverless esbuild and nodejs have you got on your systems?

I tried with serverless-esbuild 1.23.4 and 1.26.1 (latest) and my node version is v16.5.0. Please note that the same combination of versions works for other projects.

I'm pretty sure fs-extra just creates a wrapper around the node fs one but if this works for you then sure, it shouldn't be too much of a biggie I guess

Yep, that's what I thought as well. It does some monkey-patching of streams though so that maybe a cause of the issues.
Strangely enough, I just tried the same project today and it worked. I guess I'll investigate deeper if it occurs again.


Process.MaxChatCharacterLimit should just take MaximumMessageLength from chatsettings.

There could be a slight chance that someone happened to increase the maximum chat length to something higher than 250, while this would be rare, it might really confuse someone why it isn't working.

Or if the limit has been exceeded, post a warning in server logs.

Where's this?

@Sceleratis heres an example print(chatsettings.MaximumMessageLength) that would print the MaximumMessageLength, so using the same chatsettings variable and chatsettings.MaximumMessageLength this should be able to be used for seeing what the maximum is set to.

And this is usable serverside?

Also it feels unlikely that anyone would go through the effort to alter that...

Yes, this works on the server-side, I tested it.

Either close this or make a PR.

I agree


Idiomatic help from reddit

Fixes all warnings and errors from "all", "pedantic", and "nursery" lint groups except for those that come from a new or expanding project (e.g. "unused variable", "associated function is never used", and "this could be a 'const fn'") and name repetition (e.g. "GameStatus" in the "Game" module instead of "Status").
I don't recommend actually merging this pull request as I assume this is a tutorial/learning project for you and you may not agree with all of the lints.
The only addition which wasn't recommended by clippy was my addition of a .gitignore file and adding some simple linting rules to the cargo.toml, though I do recommmend those.

Thank you!
These changes are definitely necessary, and I’m glad to see Rust has such useful linters. Merging :)


PDFTable last row cut every Page and also Page number not display in New Version TPPDF

Hello We  are face issue PDFTable last row cut and second page first row cut in new version of TPPDF.Please see the attachment.

TPPDF version 2.3.1

@philprime any update

@jigs777 , same here.

For me, the fix in branch feature-205 fixed my issue for cut table cell. Though, still have issue if there is an header displayed in the next page. It hides few rows.

I am also facing the same issue in v2.3.1, last row of first page and first row of the next page are always cut off when using single table with a long list of rows. Can anyone please help

@dipen0510, take the changes from "feature/205-optional-table-cell-splicing" branch and use the line below (already the default value)
table.shouldSplitCellsOnPageBreak = false

Thank you @icarus31 for the info, but if I set showHeadersOnEveryPage = true then the same problem happens although if I set it to false then it works perfectly fine. Any clue to resolve this?

@dipen-sekhsaria , that's interesting that when you have showHeadersOnEveryPage set to true, you have the table cells cut. From my side, the only issue I had with that setting was to loose 2 to 3 cells on the next page because hidden by the table header! That part, still waiting for answer here: https://github.com/techprimate/TPPDF/issues/205

I just released 2.3.2, please try it out and let me know if the issue still remains (some issues with footer height were corrected)

@philprime hi, i'm using version 2.3.2, the next page is still cut by the table header.

This might be fixed in 2.3.5, please confirm

Closed due to inactivity


multiple, conflicting postgres sequences are generated for each new domain class.

The diff generates an explicit sequence change statement for each new domain.
This sequence is bad, and should never be put in the database.
This did not happen in grails2.x version of this plugin.
Given a new domain class, DuplicateDetection.groovy
`package com.temp
class DuplicateDetection {
static constraints = {
}

}`
Running diff generates:
`databaseChangeLog = {
changeSet(author: "me (generated)", id: "1486614694673-1") {
    createSequence(sequenceName: "seq_duplicate_detection")
}

changeSet(author: "me (generated)", id: "1486614694673-2") {
    createTable(tableName: "duplicate_detection") {
        column(autoIncrement: "true", name: "id", type: "BIGINT") {
            constraints(primaryKey: "true", primaryKeyName: "duplicate_detectionPK")
        }
    }
}

}`
Running update generates the following table and corresponding, conflicting sequence:
CREATE TABLE public.duplicate_detection (   id bigint NOT NULL DEFAULT nextval('duplicate_detection_id_seq'::regclass),   CONSTRAINT "duplicate_detectionPK" PRIMARY KEY (id) ) WITH (   OIDS=FALSE ); ALTER TABLE public.duplicate_detection   OWNER TO postgres;
'seq_duplicate_detection' is incorrect, and breaks the convention of all other tables and sequences previously generated by the grails2.x plugin.
This statement should not be generated by the diff.
The grails 3.x plugin is  still correctly generating  'duplicate_detection_id_seq' and attaching that to the new table.
(I'm guessing this is due to a liquibase core or a hibernate bug.)

runtime 'org.grails.plugins:database-migration:2.0.0
grails 3.1.14
postgres 9.6
java 8

Did you specify compile 'org.liquibase:liquibase-core:3.5.3' in your build.gradle?

Yes, I did.
   compile 'org.liquibase:liquibase-core:3.5.3'

ah, I think I see the problem. I have several tables that need to use a specific sequence name for legacy reasons.
The old plugin correctly detected and handled the custom sequence defined in the mapping. The new plugin does not handle it, so it keeps trying to generate a new sequence each time.
	static mapping = { 		id column: "duplicate_detection_id", generator: "native", params: [sequence: 'duplicate_detection_id_seq'] 	}


setstdin a library that allow to provide binary with alternative STDIN data

setstdin a library that allow to provide binary with alternative STDIN data by substituting read, fread, fgetc, getc and getchar calls

Thanks!


Doesn't copy all files

Here's my config file:
'use strict';
module.exports = {
publish: {
	files: {
		"./": "app/**"
	},
	options: {
		host: '<%= secret.host %>',
		username: '<%= secret.username %>',
		password: '<%= secret.password %>',
		path: '<%= secret.www_dir %>',
		srcBasePath: "app/",
		showProgress: true
	}
}
};

Not all files are being copied over, and absolutely no sub directories are either. Not sure what the problem is. Tried lots of variations but the documentation doesn't account for this.
Hopefully someone can set me straight, or perhaps this is an issue that needs fixing?

For me SFTP works great (all files under any depth of folder structure gets copied), apart from .htaccess file, which is ignored big time. Here is my setup:
sftp: {
      staging: {
        options: {
          host: '<%= secret.staging.host %>',
          path: '<%= secret.staging.path %>',
          username: '<%= secret.staging.username %>',
          password: '<%= secret.staging.password %>',
          srcBasePath: '<%= config.dist %>',
          createDirectories: true,
          showProgress: true,
          dot: true
        },
        files: {
          "./": "<%= config.dist %>/**"
        }
      }
    }

Any ideas on successful sftp-ing the .htaccess files onto the server are much appreciated, cheers!

Just found a temporary solution to my problem. Keep the .htaccess file htaccess without the dot and copy it over to the remote server. Once SFTP finished, use the sshexec task to rename that file to .htaccess.
Here is my sshexec setup:
sshexec: {
      staging: {
        command: 'mv <%= secret.staging.path %>/htaccess <%= secret.staging.path %>/.htaccess',
        options: {
          host: '<%= secret.staging.host %>',
          path: '<%= secret.staging.path %>',
          username: '<%= secret.staging.username %>',
          password: '<%= secret.staging.password %>'
        }
      }
    }

I hope it helps. But I more hope, that the dot option will be refactored and it will work soon :)


build show message "no ENTRYPOINT/CMD"

20220407PWEA:/tmp$ slim build --target xprobe/xinference:v0.14.0 --tag xprobe/xinference:v0.14.0-slim
cmd=build info=param.http.probe message='using default probe'
cmd=build state=started
cmd=build info=params tags='xprobe/xinference:v0.14.0-slim' image-build-engine='internal' target.type='image' target.image='xprobe/xinference:v0.14.0' continue.mode='probe' rt.as.user='true' keep.perms='true'
cmd=build state=image.inspection.start
cmd=build info=image id='sha256:ef25a8c0d302bdbf03f14926e561ca6d6cfede82383cad85d3fc978ae95bc983' size.bytes='15526677283' size.human='16 GB'
cmd=build info=image.stack name='xprobe/xinference:v0.14.0' id='sha256:ef25a8c0d302bdbf03f14926e561ca6d6cfede82383cad85d3fc978ae95bc983' index='0'
cmd=build state=image.inspection.done
cmd=build state=container.inspection.start
cmd=build info=target.image.error status='no.entrypoint.cmd' image='xprobe/xinference:v0.14.0' message='no ENTRYPOINT/CMD'
cmd=build state=exited code=33554438
cmd=build info=report file='slim.report.json'
cmd=build info=exit version='linux/amd64|Transformer|1.40.11|1b271555882eacdfb4e6598d6d0552e9b9b1449b|2024-02-02_01:36:22PM' location='/usr/local/bin' code='33554438'

@icewizardry the container image you are targeting, xprobe/xinference:v0.14.0, has no entrypoint or cmd information, so the container can't start on its own without explicitly specifying what needs to execute inside of the container.
If you run docker inspect xprobe/xinference:v0.14.0 you will see that in the "Config" section "Cmd" is null and "Entrypoint" is null. It appears that the image was created with the ENTRYPOINT []` instruction, which reset the container startup information.
To deal with container images like that you need to specify the entrypoint and/or cmd info using the --entrypoint and --cmd flags.


Add release interview for 1.21

Publish the abridged transcript of the Kubernetes Podcast interview with Nabarun Pal as a kubernetes.io blog post.
See also: #22882, #22716, #17963 et al.
/cc @castrojo @palnabarun

@craigbox -- the contents are all good! Just pointed some nits here and there.

/assign @mrbobbytables


Per-application opt-out of all mappings?

I love chunkwm and skhd. I also like i3, which I run in a VM on my mac. It's a little painful keeping the keyboard mappings for chunkwm from swallowing those of skhd. I think if there were a way to configure skhd to completely ignore an application it would make it a lot easier to manage this particular use case. Thoughts?

+1 Came here hoping to find an option for this

That's a good workaround, if only temporary. thanks

Fixed on master. See updated sample config and/or README for information. I'll be posting the syntax for it here as well.
There is now a new category in the grammar called options, and these begin with a . followed by the name of the option. Currently there is one option .blacklist which require a list of process-names that are to be ignored by skhd.
e.g:
.blacklist [
    "google chrome"
    "kitty"
    "vmware fusion"
]

Part of release v0.3.2, closing this.

Thank you!


pnotify.removeAll()

You could add
 removeNotifications: function() {
                        return PNotify.removeAll()
                    }

so it can be called by notificationService.removeNotifications().
At the moment, only way is window.PNotify.removeAll();

Implemented in 0.1.2


Should migrations in modules be disabled?

Looking at the Craft 3 docs, migrations aren't available in modules but only in plugins link.

Probably yes. Modules can use content migrations, but probably there isn't a whole lot we can do with that from a scaffolding POV.


Bael 3265 po c

Hi, usually thers a 'download project' button but i cannot see it , this 'pull request' i want to download the spring-boot + angular demo (https://www.baeldung.com/spring-boot-angular-web) can you help me ?

Hi @orenhpygilant  You need to clone or download the repository first: https://github.com/eugenp/tutorials and then import only the project you're interested in in an IDE or run it from the command line.
Also, please open an issue if you have a question, not a pull request: https://github.com/eugenp/tutorials/issues
Thanks,


fix(docs): broken link

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/scullyio/scully/blob/main/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Other... Please describe:

What is the current behavior?
On the doc app, there is no corresponding route for the DOCS link in the footer
What is the new behavior?
The route matchs the Introduction route.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

@SanderElias for further contributions on the doc, do you want me to push the updated jest snapshot or you prefer to keep control on it?

@geromegrignon Feel free to push the updated snapshots. as long as its just docks snapshot that are changing.
We added this to the test suite because we now do an automated deploy, and we want to be sure the docs build.
Also, the docs use a different render path as our sample-blog and this makes sure both paths are working as expected.


Responsive Design and Improved User Experience

I would like to raise an issue regarding the need to make the website more responsive and user-friendly across various devices, including mobile, desktop, tablets, and other screen sizes. Currently, the website does not adapt well to different devices, which can result in a suboptimal user experience.
Some specific areas that could be improved include:

Mobile-Friendly Layout: The website should have a layout that adjusts seamlessly to smaller screens, ensuring that all elements are easily readable and accessible on mobile devices.

Desktop Optimization: The website should also be optimized for desktop screens, providing a visually appealing and user-friendly experience for users accessing the website from desktop computers.

Tablet Compatibility: The website should be designed to work well on tablet devices, with appropriate layout adjustments and touch-friendly interactions.

hey @VivekChatterjee !
please add the labels of hectoberfest.
thankyou!

I would like to contribute in resolving some of the issues in a mobile phone's layout in the website.

The search button can be placed in a better way.
Some additional padding and margin can be added in the bottom.
The scrollbar can be disabled or placed in the rightmost part of the screen for mobiles. It would look even better if we implement a progress bar instead of a scrollbar.
The movie heading and movie tags can be moved to separate lines which would increase readability.
So, can you please assign me to resolve these issues.

@adv8j sagar is already working on this, you can raise another issue