[Upstream][Security] Use execFileSync over exec for cases with uncontrolled absolute paths

Summary
In our fork React Native macOS, we run Github's CodeQL  to analyze for vulnerabilities. One common one that comes up is the use of exec with an uncontrolled absolute path (Example: https://github.com/microsoft/react-native-macos/security/code-scanning/14). The very simple fix to this is to replace calls to exec with execFileSync, which more or less does the same thing (but more securely!).
Changelog
[INTERNAL] [SECURITY] - Use execFileSync over exec for cases with uncontrolled absolute paths
Test Plan
CI should pass

Any update on this one?


Prototype Fix #2037 - Context length check does not take into out pad tokens for visual models

Motivation
Found a bug a few days ago when running Qwen2-VL through VLLM: https://github.com/sgl-project/sglang/issues/2037
I have tracked down the issue to the fact that the context-length limit is not respected once you account for padding tokens in visual language models.
Ex. you might have a request like this "user: what is in the following image?<image_pad>" in your initial request, which is below your context-limit.
But then, the provided image might expand out <image_pad> into 500 new tokens, pushing you over the limit, and leading to crashes (see #2037 for stack trace)
Modifications
I tried to add a check for this in the scheduler, however now I get a crash in a new location:
[2024-11-20 14:05:10 TP0] Traceback (most recent call last):
  File "/root/sglang/python/sglang/srt/managers/scheduler.py", line 1403, in run_scheduler_process
    scheduler.event_loop_overlap()
  File "/root/.conda/envs/sglang/lib/python3.11/site-packages/torch/utils/_contextlib.py", line 116, in decorate_context
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/root/sglang/python/sglang/srt/managers/scheduler.py", line 390, in event_loop_overlap
    batch = self.get_next_batch_to_run()
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/sglang/python/sglang/srt/managers/scheduler.py", line 744, in get_next_batch_to_run
    new_batch = self.get_new_batch_prefill()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/sglang/python/sglang/srt/managers/scheduler.py", line 822, in get_new_batch_prefill
    req.init_next_round_input(None if prefix_computed else self.tree_cache)
  File "/root/sglang/python/sglang/srt/managers/schedule_batch.py", line 271, in init_next_round_input
    rid=self.rid, key=self.adjust_max_prefix_ids()
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/sglang/python/sglang/srt/managers/schedule_batch.py", line 283, in adjust_max_prefix_ids
    if self.sampling_params.max_new_tokens > 0:
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: '>' not supported between instances of 'NoneType' and 'int'

Can someone from the team please help and let me know what expected path I should go in resolving this issue?
There is at least a nice neat repro test case you can use to see the issue for yourselves.
Checklist

[x] Format your code according to the Contributor Guide.
[X] Add unit tests as outlined in the Contributor Guide.
[x] Update documentation as needed, including docstrings or example tutorials.

@merrymercy Unfortunately my fix doesn't actually fix the issue. I instead get this error now:
[2024-11-20 14:05:10 TP0] Traceback (most recent call last):
  File "/root/sglang/python/sglang/srt/managers/scheduler.py", line 1403, in run_scheduler_process
    scheduler.event_loop_overlap()
  File "/root/.conda/envs/sglang/lib/python3.11/site-packages/torch/utils/_contextlib.py", line 116, in decorate_context
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/root/sglang/python/sglang/srt/managers/scheduler.py", line 390, in event_loop_overlap
    batch = self.get_next_batch_to_run()
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/sglang/python/sglang/srt/managers/scheduler.py", line 744, in get_next_batch_to_run
    new_batch = self.get_new_batch_prefill()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/sglang/python/sglang/srt/managers/scheduler.py", line 822, in get_new_batch_prefill
    req.init_next_round_input(None if prefix_computed else self.tree_cache)
  File "/root/sglang/python/sglang/srt/managers/schedule_batch.py", line 271, in init_next_round_input
    rid=self.rid, key=self.adjust_max_prefix_ids()
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/sglang/python/sglang/srt/managers/schedule_batch.py", line 283, in adjust_max_prefix_ids
    if self.sampling_params.max_new_tokens > 0:
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: '>' not supported between instances of 'NoneType' and 'int'

Do you have some suggestions for how to tackle it?

@merrymercy Done, and fixed the linter too


Works for url to json, but not with file or string

I have put flashcard definitions in a file called "flash.json". If I load that file from a URL the package works well. But, if I try any of these variants, it fails with Javascript Error: Cannot read properties of null (reading 'dataset')
display_flashcards('flash.json'). # a file ref

display_flashcards(open('flash.json').read()) # string of the json

display_flashcards(json.loads(open('flash.json').read())). # list of dictionaries

it seems like all three should work.

Yes, I'm seeing this, too now. It was working before, so let me track down what changed.
Thank you for letting me know!

Please upgrade to the latest (1.9.9), which is in PyPI:
pip install --upgrade jupytercards
Hopefully, it is fixed. I merged a PR that had some fixes, but the contributor accidentally put the JavaScript stuff before the HTML, which caused this break.

That does seem to have fixed it. Thanks for the quick reply!


Request: Merge IPTV data with custom channels

Heyoo! Me again.
I've got another request. Would it be possible to make it so that we could use IPTV data in conjunction with DizqueTV?
For example, I've got a m3u an xmltv from tv.xyz.com. I open DizqueTV, import those files, they are added to the normal lineup in Dizque, with the option to maybe rename or renumber the channels?

This sort of thing is out of dizqueTV's scope. Normally we use xTeVe to create aggregated TV line ups.  xteve is a project that can take different m3u and xmltvs from different sources (including dizquetv) and aggregate them together into a single one or a simulated HDHR https://github.com/xteve-project/xTeVe


fix(auth): prevent login for non admin for ldap and oauth

EE-648

Closes https://github.com/portainer/portainer/issues/5889


How do I specify the theme?

I can't work out how to specify which theme to use?

Write into your .vimrc :let g:airline_theme='dark'


Prepublish checklist tooltip on previously published stories does not display

Bug Description
“There are items in the checklist to resolve” tooltip
Doesn’t display over “Update” button (if story is already published)
Too subtle
Expected Behaviour

Steps to Reproduce

Screenshots

Before publish:

After publish (now an update)

Additional Context

Plugin Version:
WordPress Version:
Operating System:
Browser:

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

Verified in QA

@carlos-kelly @csossi I still don't see any warning in the "update" button if there are checklist warnings/errors. Can you clarify what's expected? I'm testing in
https://stories-new-wordpress-amp.pantheonsite.io/wp-admin/post.php?action=edit&post=14849#page=%2522e3579ada-1fb7-453f-ba1c-2a5666d58b44%2522

@carlos-kelly @csossi I still don't see any warning in the "update" button if there are checklist warnings/errors. Can you clarify what's expected? I'm testing in
https://stories-new-wordpress-amp.pantheonsite.io/wp-admin/post.php?action=edit&post=14849#page=%2522e3579ada-1fb7-453f-ba1c-2a5666d58b44%2522

@carlos-kelly @csossi There is still no warning but is the message an expected action for hoverstate only for the update button?

@carlos-kelly @csossi There is still no warning but is the message an expected action for hoverstate only for the update button?

@carlos-kelly @csossi @BrittanyIRL I still don't see anything here, what is this ticket meant to capture?

@carlos-kelly @csossi @BrittanyIRL I still don't see anything here, what is this ticket meant to capture?

Well, it should look like this PR specifies: https://github.com/google/web-stories-wp/pull/5548
but it appears that in the time this passed QA and revising for UAT something happened and it got overwritten.

Well, it should look like this PR specifies: https://github.com/google/web-stories-wp/pull/5548
but it appears that in the time this passed QA and revising for UAT something happened and it got overwritten.

New ticket or send this one back?

New ticket or send this one back?

New ticket or send this one back?

@BrittanyIRL New ticket in this case.

New ticket or send this one back?

@BrittanyIRL New ticket in this case.

Just as heads up, I have tested and the bug is still there.

Just as heads up, I have tested and the bug is still there.

@ivayloklissarov thanks, there's a follow up ticket since the issue resurfaced, you can see it linked above your comment (also here: https://github.com/google/web-stories-wp/issues/5972) so the fix is in ready for QA and hasn't been merged so it's not on staging quite yet.

@ivayloklissarov thanks, there's a follow up ticket since the issue resurfaced, you can see it linked above your comment (also here: https://github.com/google/web-stories-wp/issues/5972) so the fix is in ready for QA and hasn't been merged so it's not on staging quite yet.

Working good, closing the ticket.


Rename picframe data directory to picframe_data

Not realy a bug, but folder name and executable shouldn't have the same name. And you can't run the executable if you are on the same level as the directory.
This requires:

change setup.py
change paths configuration_example.yaml
wikie command line interface

fixed and merged into dev


startupScriptContent does not seem to run when installing helm chart

I'm trying to install Localstack along side a custom application using Helm. A part of my deployment is making sure an S3 bucket exists in LocalStack ahead of time. I thought startupScriptContent would have been the correct parameter to use but it seems as if that script is never executed. The bucket is not created, and I don't see any logs indicating the script encountered an error or even tried to run.
I don't think having the Localstack chart as a subchart would really effect this but I figured it's worth mentioning my setup.
Here is the directory structure.
charts/
    myapp.0.1.0.tgz
   localstack-0.6.5.tgz
Chart.yaml
values.yaml

The contents of Chart.yaml
apiVersion: v2
description: a custom app deployed alongside localstack
engine: gotpl
name: my-custom-app
version: 0.1.2
dependencies:
- name: my-custom-service
  alias: myapp
  version: 0.1.0
  repository: file://charts/myapp
- name: localstack
  alias: s3
  version: 0.6.5
  repository: https://localstack.github.io/helm-charts

The contents of my values.yaml file
localstack:
  startServices: s3
  enableStartupScripts: true
  startupScriptContent: |
    !#/bin/sh
    awslocal s3 mb s3://hl-modelscan

When I run helm install myapp . everything deploys w/o and error but the bucket is not there.
Here's a sample of the logs for the localstack pod just after deloyment.
LocalStack version: 3.0.1.dev
LocalStack build date: 2023-11-17
LocalStack build git hash: 32a7946f

2023-11-19T18:58:05.994  INFO --- [-functhread4] hypercorn.error            : Running on https://<IP_ADDRESS>:4566 (CTRL + C to quit)
2023-11-19T18:58:05.994  INFO --- [-functhread4] hypercorn.error            : Running on https://<IP_ADDRESS>:4566 (CTRL + C to quit)
2023-11-19T18:58:06.028  INFO --- [  MainThread] localstack.utils.bootstrap : Execution of "start_runtime_components" took 603.21ms
Ready.
2023-11-19T18:58:54.093  INFO --- [   asgi_gw_1] localstack.request.aws     : AWS s3.ListBuckets => 200

If there's any other information I need to provide please let me know and I'm happy to do so.

Hi @hop-along-polly!
I haven't tested it when being used as a sub-chart, but using the following values and command works perfectly fine:
$ cat test-values.yaml
debug: true
startServices: s3
enableStartupScripts: true
startupScriptContent: |
  #!/bin/bash
  awslocal s3 mb s3://hl-modelscan
$ helm install ls-helm-demo localstack/localstack -f test-values.yaml
...
$ kubectl logs -f ls-helm-demo-localstack-5b7bdbdf5b-24r8f
...
2023-11-20T13:05:59.021 DEBUG --- [  MainThread] localstack.runtime.init    : Running READY script /etc/localstack/init/ready.d/ls-helm-demo-localstack-init-scripts-config.sh
2023-11-20T13:05:59.584  INFO --- [   asgi_gw_0] localstack.request.aws     : AWS s3.CreateBucket => 200
make_bucket: hl-modelscan
...

It seems like your shebang is wrong (it has to be #!..., not !#...).
If this does not solve your problems, please check if your subchart config is working well.
If this still does not solve your issues, please post the rendered deployment here: kubectl get deployment -o json <localstack-deployment-name>
Thanks!

I figured it out. In my Chart.yaml file I was creating an alias for localstack but in my values.yaml I was using localstack instead of the alias.
# Chart.yaml
apiVersion: v2
description: a custom app deployed alongside localstack
engine: gotpl
name: my-custom-app
version: 0.1.2
dependencies:
- name: my-custom-service
  alias: myapp
  version: 0.1.0
  repository: file://charts/myapp
- name: localstack
  alias: s3  # <- Since I alias "localstack" to "s3" I need to use "s3" in my values file instead of "localstack"
  version: 0.6.5
  repository: https://localstack.github.io/helm-charts

Here is the corrected values.yaml file
s3: # <- This needed to be s3 instead of localstack
  startServices: s3
  enableStartupScripts: true
  startupScriptContent: |
    #!/bin/sh
    awslocal s3 mb s3://hl-modelscan


The spec file is not looked for recursively.

https://github.com/pvalena/abrt-ruby/pull/8#issuecomment-672111803

We're not doing this recursively locally:
https://github.com/packit/packit/blob/master/packit/config/package_config.py#L346
Thought I'm not sure about this one https://github.com/packit/packit/blob/master/packit/config/package_config.py#L369
@lbarcziova could you clarify please?

Thought I'm not sure about this one https://github.com/packit/packit/blob/master/packit/config/package_config.py#L369

Looks like get_files() method from ogr which we use gets files only from the top-level dir by default.
And locally it is searched recursively.

FYI your FAQ (or docs, not sure atm) says it works recursively ;).

Looks like get_files() method from ogr which we use gets files only from the top-level dir by default.

Can we switch to recursive=True then to match local behaviour and docs?


Enable testnet for developer testing of GlacierScript

This PR adds an undocumented -testnet flag to glacierscript.py, a set of self-checking tests, and a Makefile to run all the tests.
Motivation
With a set of self-checking tests:

Developers modifying glacierscript.py can work with much more confidence that they are not breaking any functionality;
Reviewers can quickly and easily see what behavior has changed (if any) by examining the changes to the tests, and running them to doublecheck;
Newly discovered bugs can be easily demonstrated by writing a failing test.

Implementation
I chose to use testnet instead of mainnet so that I could create actual addresses and transactions in the blockchain for testing purposes without spending real money on miner fees (which were sky-high at the time I was coding this). All of the withdrawal tests were real transactions which I sent to the testnet blockchain to prove correctness. They can be viewed using any testnet block explorer.
To use testnet, bitcoind and bitcoin-cli need extra arguments, so this necessitated changes to glacierscript.py to provide those extra arguments.
To automate the test running, I created a Makefile that runs all tests and returns 0 iff all tests pass.
To simulate the conditions of the quarantined laptop, which never has a network connection, wallet, or blockchain, I run a new instance of bitcoind for every test, with a newly-created wallet directory.
To speed up the test execution, which can be slow because of the need to spin up a new bitcoind for each test, I enabled parallel make by giving each bitcoind a unique RPC port, in addition to a unique directory.
Each test consists of a *.run file, which is a bash script that launches glacierscript.py with the appropriate command line, and feeds in a script of the user input. The output of *.run is then compared with a matching *.golden file. If the actual output does not match the golden, the test fails.
How to use
Simply run make and watch as the tests pass.
Tests will run using whatever bitcoind and bitcoin-cli are found in the PATH (just as glacierscript.py does).
If a test fails, manually examine the *.out and the *.golden files to find the differences.
There are instructions in the Makefile for writing new tests.
Review
Since there are no previous tests to compare against, this needs careful review. The changes made to glacierscript.py are limited to extra command-line options to bitcoind and bitcoin-cli when glacierscript is run with -testnet. There is also a different WIF prefix for testnet, as specified by Bitcoin standards. When not using -testnet, the behavior should be identical to before.
Note
This is built on top of my compressed-keys branch, and contains tests for withdrawing from both uncompressed (i.e. older Glacier versions) and compressed keys. PR #10 should be merged first, and then this PR rebased and merged.

from my previous comment on #10 this looks good to me!

This is a really good contribution @bitcoinhodler. Thank you for submitting it, it will make testing a lot easier for everyone.
LGTM


Update csv2geojson

Is it possible?
To fix this issue: https://github.com/mapbox/csv2geojson/issues/46
Thanks!

As in the PR, 5.0.2 is included in the current semver range.


[Topic] Expand dependency  newrelic_rpm version to (=> 6.12", < 8.0)

Update the dependency version range of newrelic_rpm gem

from ~> 6.12
to ">= 6.12, < 8.0

Proof
version >= 6.12
version 7.x.x
version 8.x.x


[Template] init template app

Init of spa
add focus kit stater
add layout
add menu

@Tommass  Don't forget to use import instead of require everywhere (i know moost of the code is legacy).

@pierr i know. but it does not work everywhere


UI updates for who we are

Fix # https://adobe-acs-group.atlassian.net/browse/WRLDBAEMS-82
Test URLs:

Before: https://main--world-bank--aemsites.hlx.live/en/who-we-are
After: https://dev-who-we-are--world-bank--aemsites.hlx.live/en/who-we-are

@Akshaya284 Keep PR in drafts state if there are lint issues.

@Akshaya284 Keep PR in drafts state if there are lint issues.

Noted.

@mkbansal1 Will handle that in a separate PR. Thanks.


UofT-DSI | Python - Assignment 2

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Adding code and using functions to go through csv file data.
What did you learn from the changes you have made?
How to open files and go through their data using functions.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
No this was the same approach i was considering as it is similar in JavaScript.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
No challenges.
How were these changes tested?
I had done print tests and also made sure the code worked by running them through different files.
A reference to a related issue in your repository (if applicable)
No.
Checklist

[x] I can confirm that my changes are working as intended

Assignment marked.


Fix colcon build error

Error occurred on setuptools
UserWarning: Usage of dash-separated will not be supported in future versions
Change dash to underscore in setup.cfg (still not available in setuptools==64.4.0, but in 58.2.0)

Hi, I cloned your repository and used colcon to build a package.
but there was following errors.
Starting >>> px4_offboard
/home/as06047/.local/lib/python3.8/site-packages/setuptools/dist.py:788: UserWarning: Usage of dash-separated 'script-dir' will not be supported in future versions. Please use the underscore name 'script_dir' instead
  warnings.warn(
/home/as06047/.local/lib/python3.8/site-packages/setuptools/dist.py:788: UserWarning: Usage of dash-separated 'install-scripts' will not be supported in future versions. Please use the underscore name 'install_scripts' instead
  warnings.warn(
--- stderr: px4_offboard
/home/as06047/.local/lib/python3.8/site-packages/setuptools/dist.py:788: UserWarning: Usage of dash-separated 'script-dir' will not be supported in future versions. Please use the underscore name 'script_dir' instead
  warnings.warn(
/home/as06047/.local/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
---
Finished <<< px4_offboard [3.54s]

Summary: 1 package finished [4.13s]
  1 package had stderr output: px4_offboard``

I found out that it was the problem of the version of setuptools.
After I replaced dashes to underscores and manually installed lower version of setuptools which is 58.2.0, colcon finally worked.(In the latest version, which is 64.4.0, colcon build failed due to using setup.py.)

@ChanJoon Thanks for the contribution.
Could you provide details on what system setup you are using?
I am a bit confused with the issue, since that part was generated through the ros2 package creator.

I'm using
OS: Ubuntu 20.04
ROS2: Foxy
Python: 3.8.10

@ChanJoon Hmm, okay that is odd.
I will try to add a CI for ROS foxy to reproduce this problem.

Thanks. It seems like the setup.py installation way is no more supported with the newer Python version.
there is opened issue https://github.com/colcon/colcon-core/issues/454
Anyway, I'm currently learning a lot from you as an undergrad!


When a Gradle build cache upload fails, log its size

Expected Behavior
When a Gradle remote build cache upload fails because the file is too large, Gradle should print the file size. For example:
Could not store entry 08c49350bda6742bfd206d107284da1f of size 152MB in remote build cache: Storing entry at 'https://[REDACTED]/cache/08c49350bda6742bfd206d107284da1f' response status 413: Request Entity Too Large

Current Behavior (optional)
Gradle does not display the size of the file it tried to upload.
Could not store entry 08c49350bda6742bfd206d107284da1f in remote build cache: Storing entry at 'https://[REDACTED]/cache/08c49350bda6742bfd206d107284da1f' response status 413: Request Entity Too Large

Context
Depending on the task, it is more or less difficult to find out what the size of the produced file is. Even when it's simple, it requires re-running it locally when the failure happens in CI.
It would improve the dev experience by a lot if Gradle just printed the file size. It would be much easier to configure the build cache, based on this information.

Thank you for your interest in Gradle!
This feature request is in the backlog of the relevant team, but this area of Gradle is currently not in focus. It might take a while before it gets implemented.


Add more APIs for getting current Site

Change description
Add more APIs for getting the current Site. This is needed in the backend and other packages
Type of change

[ ] Bug fix (fixes an issue)
[x] New feature (adds functionality)

Related issues
Checklists
Development

[ ] Lint rules pass locally
[ ] Application changes have been tested thoroughly
[ ] Automated tests covering modified code pass

Security

[ ] Security impact of change has been considered
[ ] Code follows company security practices and guidelines

Code review

[x] Pull request has a descriptive title and context useful to a reviewer. Screenshots or screencasts are attached as necessary
[x] "Ready for review" label attached and reviewers assigned
[ ] Changes have been reviewed by at least one other contributor
[ ] Pull request linked to task tracker where applicable

Ready now dear @OmarIthawi


RDS Plugin: See an error related to the logging stuff when terminating

When I terminate the CAT found here:
https://github.com/RightScale-Demo/ss_assets/tree/master/Docker-WordPress_RDS_backend
I get the error shown below in SS.
If I terminate the now "Failed" cloud app, it will get to a terminated state. So the problem only occurs the first time through.
SS ERROR:
terminate failed:

Problem:
  JSON value assigned to reference
Origin:
  line: 380, column: 10
    definition: rs_aws_rds.sys_log.detail
    task: /root/1
    expression: @audit = $$audits[task_name()]
Summary:
  JSON values must be assigned to variables such as $foo and not references such as @audit
Resolution:
  Use a variable to assign JSON values

Looks like a sys_log issue.  as, the audits for terminate are boring, not necessary, and can be added by anyone that consumes the plugin by adding to their CAT, the fix here is to remove the sys_log calls in the terminate definitions


Add note about Workspace.PersistentLoaded

Changes

Added an important note to the documentation for Workspace.PersistentLoaded about it only being accessible on the server, as mentioned in its release announcement: https://devforum.roblox.com/t/new-improvements-to-streaming-enabled/2185535

Checks
By submitting your pull request for review, you agree to the following:

[x] This contribution was created in whole or in part by me, and I have the right to submit it under the terms of this repository's open source licenses.
[x] I understand and agree that this contribution and a record of it are public, maintained indefinitely, and may be redistributed under the terms of this repository's open source licenses.
[x] To the best of my knowledge, all proposed changes are accurate.

Hi there, thanks for the suggestion, but PersistentLoaded can actually be used in a LocalScript (although that's not the typical usage for it). Because of the loading order for persistent models, they are most likely already loaded by the time your LocalScript runs, so the event will not detect them loading (because that happened previous to that time). To test, you can place the LocalScript inside ReplicatedFirst and the event will fire.

We'll update the forum post as well, since it was unclear. It's the properties and functions that are server-side, but the note implied that it was all (our bad). Thanks for flagging this!


Feature: Add OpenAPI3 doc for user_capacities endpoint.

Adding documentation for new endpoint we are currently developing.
A few remarks on POST and PUT requests :

We might want to specify that some params (eg: L5204-L5221) can be used several times.

We might want to explain about the orders of the params :

A request with params
name:Cap
channels[][channel_id]:id_1
channels[][default_capacity]:1
channels[][max_capacity]:2
channels[][channel_id]:id_2
channels[][default_capacity]:1
channels[][max_capacity]:10
And with params (just switching orders) :
name:Cap
channels[][channel_id]:id_1
channels[][channel_id]:id_2
channels[][default_capacity]:1
channels[][max_capacity]:2
channels[][default_capacity]:1
channels[][max_capacity]:10
Will NOT yield the same results (actually the second one will be rejected).
I tried to mention it on the documentation but it might be unclear, so I wanted to bring that up.
Ticket

@aymebou is there a way to have a preview of this Branch/MR doc ? AFAICT the js I did on https://ringcentral.github.io/engage-digital-api-docs/digital/ only support master.
Would there be a nice way to visualize result ? And you 2 guys have you actually visualized results or just did yaml editing ?

@aymebou is there a way to have a preview of this Branch/MR doc ? AFAICT the js I did on https://ringcentral.github.io/engage-digital-api-docs/digital/ only support master.
Would there be a nice way to visualize result ? And you 2 guys have you actually visualized results or just did yaml editing ?

I found https://editor.swagger.io/ which we can use to view the yaml before merging actually.

I found https://editor.swagger.io/ which we can use to view the yaml before merging actually.

@CedricBm I think you can have a look now, besides my last comment I think we're good

@CedricBm I think you can have a look now, besides my last comment I think we're good


Integrate all Boxstarter Base & WinConfig Features

it would be nice to have all Boxstarter options (i.e. Install-WindowsUpdates) available without needing to install Boxstarter on a remote machine.

start with https://github.com/mwrock/boxstarter/blob/master/Boxstarter.Bootstrapper/Invoke-Boxstarter.ps1


[WIP] Google Cloud Storage connectors

Pull request
Description
Contributes a Google Cloud Storage linked transport sink to tremor.
Related
Partial completion of https://github.com/tremor-rs/tremor-runtime/issues/724
Checklist

[x] The RFC, if required, has been submitted and approved
[ ] Any user-facing impact of the changes is reflected in docs.tremor.rs
[ ] The code is tested
[ ] Use of unsafe code is reasoned about in a comment
[ ] Update CHANGELOG.md appropriately, recording any changes, bug fixes, or other observable changes in behavior
[x] The performance impact of the change is measured (see below)

Performance
No access to the production test environment. Not done.

Coverage decreased (-0.1%) to 83.098% when pulling c188dc5a7843c230f0d4128f5fe58a8d6e152e51 on jigyasak05:jk_gcs_connectors into 96adc418c94f84f65c0757ebb3f4545e030a3480 on tremor-rs:main.

Indeed!


[msal-angular] Typedocs and Instrumentation

This PR:

Adds additional instrumentation to msal-angular@2
Adds typedocs to msal-angular@2

Coverage increased (+11.5%) to 93.373% when pulling 9aafd3790b23a7ccf4835ca558ac09da4f3f169c on angular-instrumentation into 02fdb108e4f3252544670bbe0c3e2c54e3c7f5b5 on dev.

Coverage increased (+11.5%) to 93.373% when pulling 9aafd3790b23a7ccf4835ca558ac09da4f3f169c on angular-instrumentation into 02fdb108e4f3252544670bbe0c3e2c54e3c7f5b5 on dev.


A version tag would be great for vendoring purposes

Would it be possible to get v1.0 (or whatever you seem fit) version tag?
Thank you very much,
Andrey

What, like this one? :) Thank you for the feedback!
p.s. Yes, I did just create that :)

That will work 👍


Command line arguments for maintenance tool

I know this isn't an issue but is actually a question which I can't seem to get a definitive answer on. I've posted in Yuzu, Citra forums and subreddits but it's getting me nowhere as people are just pointing towards This which is about the Yuzu exe, not the maintenance tool which is what my question is in regards to. I know that the Citra, Yuzu and Yuzu128bit installers are directly related to the maintenance tools I am wanting to automate and are basically the same thing, which is why I figured asking here may be more fruitful than asking in the emulator forums and subreddits.
Here's a copy/paste of my posts:
"Hey all, I have been creating tasks in task scheduler for silently updating my emulators, portable apps etc and I am now working on getting Yuzu and Citra implemented. As the previous statement suggests, I want to create a task in to run the maintenance tool nightly at 3am to check for and install updates so I am always running the latest and greatest. So, are there any command line arguments to update silently? Thanks in advance!!!!"

The maintainance tool wasn't supposed to be cli based, you can launch the shortcut and it will install and quit by itself. You can check out J-selby's liftinstaller as it was the code we used, there might be more info there. I might consider adding that to version 0.3 but there simply isn't enough demand for it. Message me on Discord if you need more info, I have the same username.


fix: (example) Make the newly added node position more accurate in DragNDrop example

In DragNDrop example as mentioned above, nodes are added to where the mouse is released, however,  we are able to drag from anywhere in the sidebar node, causing the position of the added node to be visually biased. The solution is to record the offset of the drag point from sidebar node when dragging, and apply this offset when dropped.

Thanks for you solution, but this makes the example more complicated. These examples are just for testing and on the websites we try to keep the examples as simple as possible.


Adding section stage depending in job output

The following example would have saved me several hours of trying and failing

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

@mariusstrom Thanks for your contribution! I wasn't able to get your code sample working and made a couple changes. Can you look this over?
stages:
- stage: plan_dev
  jobs:
  - job: terraform_plan_dev
    steps:
    - bash: echo '##vso[task.setvariable variable=terraform_plan_exitcode;isOutput=true]2'
      name: terraform_plan
- stage: apply_dev
  dependsOn: plan_dev
  condition: eq(dependencies.plan_dev.outputs['terraform_plan_dev.terraform_plan.terraform_plan_exitcode'], '2')
  jobs:
  - job: part_b
    steps:
    - bash: echo "BA"

@juliakm I think you meant to tag @mariussm (who also has a pretty awesome first name 👍 )

@mariussm Can you take a look at the updated code sample when you have a chance?

#sign-off

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


no await for response when send command issued

I need to send command for ef dbContext to update records from asp.net core controller. But i don't need to wait when SaveChanges works.
Is it proper to call mediator.Send(new UpdateMessageStatusesCommand { Id = 1 }); without await?
I see that controller returns result and then handler writes in console:
async Task<bool> IRequestHandler<UpdateMessageStatusesCommand, bool>.Handle(UpdateMessageStatusesCommand command, CancellationToken cancellationToken)
        {
            await Task.Delay(5000);
            Console.WriteLine("UpdateMessageStatusesCommandHandler: " + command.Id);
          using (var scope = _scopeFactory.CreateScope())
            {
                var dbContext = scope.ServiceProvider.GetRequiredService<MessagesDbContext>();
                var message = dbContext.Messages.First(p => p.Id == command.Id);
                message.IsRead = true;
                dbContext.SaveChanges();
            }
        }

and i need to create scope of dbContext as it's disposed. But record updated successfully.

Hi @vlapenkov.
Can't you register your DbContext as lifestyle scoped and inject it on your handler(s)? Assuming that your handlers are application code, and not infrastructure, they should not have access to your DI Container.
About the await question: I advise you always await Task methods. I had seen cases where the components tree was disposed before the methods ended to run.

I recommend U to use a library like HangFire to Run the Task in the background


Update 5 to Debian Stretch

(Jessie is on the short road to EOL)

@jethr0null does this seem reasonable? (I bumped some of the tool versions too while I was at it since it needed some minor changes to how they're fetched anyhow)

We talked about this and 5.x will likely be EOL before Jessie is, so we'll just hold off on this instead. :+1:


[Core] Ubuntu2004_NETCore31_PackageRef_Debug failing in nightly runs

Core nightly test runs are failing with:

[error]The job running on agent azsdk-pool-mms-ubuntu-2004-general 83 ran longer than the maximum time of 60 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134

For more details check here:

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1691218&view=results

@jsquire for notification.

@v-xuto:  Josh Free is not the correct person to assign here.   Please leave unassigned for triage.

Timeout issue in the pipeline is known and mitigation is in progress.


New macro: accepted

require 'bundler/setup'
require 'dry-validation'

schema = Dry::Validation.Schema do
  required(:terms).accepted
end

result = schema.(terms: '')
puts result.success? # => false
puts result.messages # => {:terms=>["must be accepted"]}

The macro should expand to bool? & true?.

I've noticed that a similar macro confirmed isn't implemented directly on Dry::Validation::Schema::Rule, but on Dry::Validation::Schema::Value, that translates to the following syntax:
schema = Dry::Validation.Schema do
  required(:password).filled(min_size?: 12).confirmation
end

Are macros that chains required allowed?

@jodosha confirmation is a little different as it actually add an extra rule onto another key (implemented here: https://github.com/dry-rb/dry-validation/blob/master/lib/dry/validation/schema/value.rb#L77-L83

@fran-worley Thanks, but why there isn't required(:password).confirmed?

I realised after I wrote that that I wasn't answering your question. I actually don't know why not. I had kinda assumed that that would work also...

Chaining is not supported yet, but will be in 0.8.0. It wasn't trivial to make it work so I had to postpone it. It's tricky because these objects are mutable and they gather rules, but there are cases where you don't want to add a new rule and instead you just want to return it for further composition.
In example:
# this needs to create a rule from `:int?` and *add it* to rules for the :age key
required(:age).value(:int?)

# this needs to create a rule inside a block (composition via `|`) and simply
# return it, and then inside `required` method we *add it* to the rule set
required(:age) { int? | some_other_pred? }

My goal is to enable chaining so things like that will work:
required(:nums).value(min_size?: 3).each(:int?)

@solnic This ticket isn't about chaining, it's #154 instead.

This is about a feature request: accepted macro.
schema = Dry::Validation.Schema do
  required(:terms).accepted
end

Do you think it makes sense to have implement this macro? Thank you! 😉

@jodosha I think the value of such macro would be to have a nicer default error message by default, since it's so common I believe it makes sense

I've re-opened this. Let's think it through if it's worth the effort /cc @timriley @AMHOL @fran-worley

@solnic all that this macro would do is essentially alias required(:terms).value(:true?) rather than required(:terms).value(:accepted?).
The only benefits I can see is to keep syntax inline with ActiveModel which has a similar validation and to  enable a more sensible default message than must be true.
Are default messages used that much? I'd hate to make an alias for the sole purpose of providing a more applicable default message for users to just override with their own.

I think this macro can collapse value(:true?) into acceptation just like we did with confirmation and then provide a default error message for :acceptation rule.

But as @jodosha points out, confirmation has can't be applied directly on the key (e.g. required(:password).confirmation so what you'd end up with in your example is having to do required(:terms).maybe.accepted which I don't find any better than required(:terms).value(:true?) other than the benefit in error message. (unless I'm missing something...)

It's a matter of defining this macro on Rule object

@solnic do we make it a macro available to both Form and Schema? As it is really aimed at forms I'd rather see it be implemented within Form in some way.

there's no mechanism for schema-type-specific-macros yet...we could think about it though

I stand in a similar place for 'confirmation' as to me that is quite a form specific macro.

We have now an API for defining custom macros, we could use it to extend Form with acceptance macro :)

@solnic Do you think it's worthy do be implemented by dry-v or you're suggesting elsewhere (eg. Hanami)?

@jodosha I wouldn't be against having that in dry-v, it's super common :)

@solnic ok, time to choose, 1.0, 2.0, ∞? :)

For the record, starting from 1.0.0 this type of macros should be implemented on top of the new rule API, rather than dry-schema's DSL, ie:
class NewUserContract < Dry::Validation::Contract
params do
required(:terms).filled(:string)
end
rule acceptance: :terms # or something like this
end

After all, this landed in master already and will be part of 1.0.0. I added support for macros as an experimental feature for now. :acceptance is the first macro, here's how it looks like:
class MyContract < Dry::Validation::Contract
  schema do
    required(:terms).value(:bool)
  end

  rule(:terms).validate(:acceptance)
end

Nice thing is that you can "chain" multiple macros ie rule(:terms).validate(:check_this, :check_that, :etc) and those will be executed as part of one rule, which means better performance.


Missing types.db file for collectd plugin causes server to fail to start

Maybe this is intended behavior, but I wanted to make a note regardless. Should plugin startup failing cause the server to die?

Yes, this has always been the case. I see no reason why the server should carry on if an explicitly configured plugin won't start.

To be clear, it shouldn't panic, but it should error with a clear message in the logs or at STDERR.

I don't believe there is any issue here.


[WIP] Email notifs

Resolves #116

Need to figure out what notifications to send (document approval, rejection, messages?)
Need to generate notifications
[x] Populate notification table if not already set up
[x] When update_status called for document, create a notification
[x] Create tests for endpoints
[x] When notification created, create an email message using specific parameters
[ ] Need to be able to access which user is doing what to pass it to the messages table
[x] Template emails

Notes:

Emails sent in a row from the same sender will stack, so notifications to the same fps and pms won't look ugly
Noticed that some POST endpoints just return status=200 because to_dict gets messed up after you commit to database

ok so this is kind of late but the problem is that each "message" (notif) requires a pm_id and fp_id, but there is no fp_id or pm_id stored in the front end so i can't call the endpoint bc there's not enough information to be creating a new notif
like if i wanted to make a notification for updating the document status, i can pass in the document-related info but not the fp or pm related to that document


help me

how to replace "Channel or Group user Name With @" by "channel/group id"?? i want this for private channels/groups.

lol


Will Adafruit PiTFT 3.5" display work?

Currently have an Adafruit PiTFT 3.5" display. Exactly the one below for visuals.

After getting everything setup I keep getting greeted with two issues. The text does not render all the way on the screen resulting in a cut off blue screen.
The second issue being a red message "Screen is not refreshing itself ... please ENTER to continue". I'm assuming this may be because wallet is locked?

Debug Log
https://termbin.com/e7ci

"Screen is not refreshing itself ... please ENTER to continue" is displayed if you run the infoi screen from the main menu. The main menu is not to be displayed on the LCD - its normally just what you have when you login as user admin thru SSH. The LCD should run as user pi - that auto logs in on start and the LCD is just displaying the status information.
So someting maybe wrong with the user running on that screen.

@denisinla Could you retry this with the current release v1.3?

pls close this.


Added support for VS Code.

This PR introduces support for VS Code as an IDE by adding the following:

Recommended extensions:

C#
C# Dev Kit
IntelliCode for C# Dev Kit

Standard tasks:

Build
Publish

Settings:

Default solution for C# Dev Kit

Normally, a watch task is also created for supporting C# repositories in VS Code, but in this case there isn't a project to actually watch so it is currently redundant. However, if it ever becomes prevalent, one could simply add the following to the tasks.json file:
{
    "version": "2.0.0",
    "tasks": [
        ...
        {
            "label": "watch",
            "command": "dotnet",
            "type": "process",
            "args": [
                "watch",
                "run",
                "--project",
                "${workspaceFolder}/DotnetFetch.Tests/DotnetFetch.Tests.csproj"
            ],
            "problemMatcher": "$msCompile"
        }
    ]
}

Finally, I'd like to point out that the C# Dev Kit automatically adds an entry in settings.json for the default solution, which is strange behavior compared to the average extension (in my experience at least).

This PR fixes issue #27.


code-insiders --status no longer works

Steps to Reproduce:

run an instance of code-insiders
run code-insiders --status
=> 🐛 no output

I traced this down to the watch task getting cancelled here:
https://github.com/microsoft/vscode/blob/b03fe7a97c06ae1906efd62e616d383704ee95e7/src/vs/code/node/cli.ts#L404
I did push some larger refactorings around watchFileContents earlier this milestone so maybe that triggered it. I still though believe that the watcher does the right thing of returning immediately when it is being cancelled.

Added a setTimeout for now.
The main issue is we want the watcher to quit once it has nothing left to read, but the current implementation gives the decision-making to whoever holds the cancellation token instead. Therefore, the CLI script must decide when to stop the watcher, when in this case we want the watcher to decide for itself.

Closing for verification.

The main issue is we want the watcher to quit once it has nothing left to read, but the current implementation gives the decision-making to whoever holds the cancellation token instead. Therefore, the CLI script must decide when to stop the watcher, when in this case we want the watcher to decide for itself.

How could the file watcher know when to stop watching the file for changes? There is no signal the file watcher could use to know that the file is no longer updated, no?
The 200ms seems quite random and fragile to me.

When the main process exits there are no other process that will be writing to the watched file, it is incorrect to expect the file watcher to stop based on a particular signal, rather we should just flush the remaining contents of the file that have not been read before closing the cli process.


Added support of Native Menus in Linux

To test this global.brackets.nativeMenus  in https://github.com/adobe/brackets/blob/master/src/utils/Global.js#L84 needs to be set to true.
// cc @abhijitapte for review.
@eyelash Could you also review the part added by me?
Screenshot for Ubuntu 16.04

it's been 3 years since I wrote that code :smile:

sorry, can't review linux cpp code

Thanks @eyelash for reviewing this PR :smile:
I have updated the PR as per your comments.

@saurabh95 GetDisplayKeyString could probably be static as well. The rest looks fine to me. As I said, I only took a quick look at your code without compiling and I'm also no expert on GTK+ shortcuts.

I'm sorry, but I cannot review cpp code

Great work @saurabh95 👍

I don't know if that was intentional but while merging this work to master all the commits were squashed (aa0336076aa485aed852af67f3194e970540a15c). Just to give you guys some feedback for the future: Seeing all your work merged without getting credit for it is not very motivating for a community contributor like me.

@eyelash it was by mistake and we will be having Release Notes in which we highlight top features and their authors and we will have your name in that.
We will definitely take care of this from next time.

@saurabh95 Thank you, I'm glad to hear that.


Using STI to store versions instead of home made association

Hi!
I was wondering why you are using a single value array containing a Hash to store the historic able object (id and type) rather than using STI ?
We could then just have an 'id' and '_type' attribute referring to historic able object. It could be easy to add a dependent destroy on our models to automatically delete historic with the referenced object.

@gottfrois, sorry for the long delay. I agree with you that the string doesn't need to be saved.
Though I do not contribute new code to this gem anymore (my project got cancelled), I still act as a maintainer of this gem, and would be happy to merge and check pull requests and release new gems on a regular basis.
That being said, if you can send me a pull request with changes to this ticket, I'd be happy to merge / check / release for you.
Thank!
AQ

Allright, I will take a look at it sometime then :)


Move HTML attribute observer controller to new controllers directory

We now have a controllers directory, so it makes more sense for this to live there. No README currently; I want to get the move done early because I need to use this in the HTML editor and would prefer not to have to play the "race BSI when I rename things" game. 😅

Haha good luck with the race! If it proves really difficult, you could temporarily have a stub file in the old location that imports and exports the new thing.

Thankfully I haven't merged the PR where I implemented this quite yet, so I should be safe there. These come up so often that I've learned to be much more careful about my order of operations. 😅


V2.1.6 upgrade to v2.2.1 failed，unable to recognize "management-statefile_path_redacted"

see https://forums.rancher.com/t/v2-1-6-upgrade-to-v2-2-1-failed-unable-to-recognize-management-statefile-path-redacted/13790

@galal-hussein , we have seen  similar issue when upgrading rancher-server from 2.1.6->2.2.0 which is tracked in https://github.com/rancher/rancher/issues/19059 . In this case this error seen was temporary and the cluster was able to recover automatically from this state  within the next few minutes.

I saw this error as well, but for us it turned out to be a blip in dns resolution.

tried to reproduce this issue.
Verified on an upgrade setup from v2.1.6 to v2.2.1.
Steps taken:

On rancher v2.1.6, a HA setup, created a cluster with 3 nodes(all roles) type - hosted-Amazon EC2.
Upgraded to rancher:v2.2.1.

Observations:

Cluster went to Unavailable state.

It changed to Provisioning state with the below error message. This was for a couple of seconds.

It transitioned to Unavailable state and finally to Active state after few seconds.

Closing as a duplicate of https://github.com/rancher/rancher/issues/19273


How to avoid reoptimizing all images between builds?

It seems that on each build, all images are re-optimized (not just new images) and this slows down the build. What's the best way to only build images that are not in the .next/static/images folder yet (i.e. new images)? Is there a recommended way to cache these files?

I would like to know too. I'm building a very image-heavy website, and reprocessing images all the time slows down work significantly.


fix: incorrect alert comparison message

Fix incomplete sentence on alert comparison message

Codecov Report
Patch and project coverage have no change.

Comparison is base (def4cfa) 89.87% compared to head (295c1bb) 89.87%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1364   +/-   ##
========================================
  Coverage    89.87%   89.87%
========================================
  Files          192      192
  Lines         6143     6143
========================================
  Hits          5521     5521
  Misses         622      622

Flag
Coverage Δ

py3.8-ubuntu-22.04-pandas
89.87% <ø> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Websocket connection to support permessage-deflate compression

http/websocket-client and http/websocket-connection now except optional argument :compression? to enable permessage-deflate extension.
I also added support for an optional pipeline-transform as it's done for HTTP connections. The problem is that It was not even possible to activate extension "manually" as a websocket connect didn't provide any flexibility with channel pipelines.
/cc https://github.com/ztellman/aleph/issues/304

🤔 this build failed on Travis CI with leak detector exception. Not sure why that happened, but I'm not able to reproduce the problem. Will try to dig deeper into that.

  I don't see anything in this change that would make this flaky (other than maybe the underlying Netty functionality, so I'm going to do a real merge and let you do some more investigation before I cut a full release with this functionality.

@ztellman Sure, I'll check!

Okay, this is actually very reliably failing in CI now, but I can't reproduce it on my machine.  I've tried targeting the latest Netty, just to see if that would help, and it doesn't.  I've commented out the tests for now.  If you're able to fix it soon, great, otherwise I'll disable the functionality for now and we can reactivate it in a future release.


Build React Naturally

This issue might sound boring, but it's one of Void's most important unresolved issues.
In the build instructions, we run npm run buildreact to compile all the files in react/src/*.tsx into react/out/*.js. We then we import those files elsewhere. This is not a great way of working with React because we need to re-build every time we change a React file.
We have two options to fix this problem:

Figure out how to allow global imports like 'react' in the browser/ environment so we don't have to build React ourselves. This was possible in vscode's previous yarn edition, and would be the ideal solution.
Or, keep bundling the way we do now, but don't crash the build script - this probably means moving build.js's contents into gulpfile.js watch-client.

Hey @andrewpareles been working on this and I have a solution that watches changes in the browser environment and auto updates the scope-tailwind, tsup transpilation, and watch-client (without crashing it). I can make a PR if you're interested?

Sounds amazing. Feel free to PR!

This works and is awesome!
Keeping this issue open for some minor other items:

In the future it would be great to incorporate this into the gulpfiles so that it 1. auto-watches when you press Ctrl+Shift+B and 2. auto-builds when you run the build script.


feat(primitives): Add y_parity_byte_non_eip155 to Parity

Motivation
In the case of a signature without EIP155 applied, the y_parity byte should be returned as 27 or 28. y_parity_byte only returns it as {0,1}.
Solution
This adds a fn which, only in the case of NonEip155(_), we get 27 or 28, or None otherwise.
PR Checklist

[ ] Added Tests
[ ] Added Documentation
[ ] Breaking changes

nope @onbjerg, but we'll need a minor release of core to bump on alloy-rs/alloy.

lgtm


Running SPFX with Cloud 9 IDE browsing to workbench does not work

Not Sure how to Categorise this may be an issue with how cloud 9 IDE resolves URL's. Any help with this would be appreciated.
Expected or Desired Behavior
After running gulp trust-dev-cert and gulp serve was expecting to be able to browse to the SPFX developer workbench
Observed Behavior
The commands above seem to run successfully however when the generated url is clicked and the open in preview browser selected the browser in cloud 9 IDE opens the URL but nothing happens. Two behaviours have been observed.

The browser window says the request took too long ( this happens on my home computer)
The browser window displays make sure you have the right web address (this happens at work)

Steps to Reproduce
Follow all the steps as documented on creating your first SPFX webpart in the link below.
https://dev.office.com/sharepoint/docs/spfx/web-parts/get-started/build-a-hello-world-web-part
Use the cloud 9 IDE, start with the default node template updated with all the prerequisites.
Thanks for your contribution! Sharing is caring.

Hi there,
I tried using the Cloud 9 IDE and at this point we are unable to debug where the problem is. We think Cloud9 workspace has some issues with the gulp-connect serve module which basically serves the application in the respective ports. We also upgraded the node to the latest 6.11.0 from 4.7.3 which was available and yet I get the following error when trying to navigate to the workbench.html:
ECONNRESET: Request could not be proxied!
There was an error proxying the request.

We also had to change the ports to 8081 and 8082 in the config\serve.json to the following:
{
  "port": 8081,
  "initialPage": "https://localhost:8082/workbench",
  "https": true,
  "api": {
    "port": 8082,
    "entryPath": "node_modules/@microsoft/sp-webpart-workbench/lib/api/"
  }
}

Please contact Cloud9 IDE support and work with them to debug it in their server. If you do find out there is some issue with the SPFx project system, please let us know and open a new issue.
I am closing this issue for now.
Thanks,
Chaks

I'm having the same problem:
After running gulp trust-dev-cert and gulp serve was expecting to be able to browse to the SPFX developer workbench!
But it does not because it's run for a while and then stop/ hung after:
[22:34:17] Finished subtask 'write-manifests' after 393 ms
[22:34:17] Starting subtask 'reload'...
[22:34:17] Finished subtask 'reload' after 2.04 ms
Appreciated it, if you let me know how this issue was resolved.
Thank you!


Mandatory magnet links

Is there no way these days to circumvent these downloads? A lot of people including me will never use torrents for obvious reasons and back when I hacked my 3DS it was not mandatory, there weren't even any torrent links.
I mean I don't need the guide anymore, but I'm baffled.

legal reasons


Merges service result with procedures

Description
We previously had three types of compute pathways:

results, started in the queue, and were deposited in the results table.
procedures, started in the queue, and deposited their results in both the results and procedures table (geometry optimizations as an example).
services which iteratively created new tasks for the queue.

This above had several complexities:

The result and procedures table only contained complete results while the services table could contain both complete and incomplete results.
The services and procedures table could have nearly identical jobs (geometry optimizations run all on node, or new geometries spawned from the server as a service)

This PR makes the following changes:

Changed the queue names to task_queue and services_queue to better reflect their purpose.
services_queue now deposits their results into the procedures

This PR also adds geometry optimization ORM.
Status

[x] Ready to go

Codecov Report

Merging #43 into master will increase coverage by 0.2%.
The diff coverage is 91.39%.

This pull request introduces 1 alert when merging 01ea130835190111572e397028814681b6fb2d3b into 42cf530355145d00b87d02484f01e1a6a9f61271 - view on LGTM.com
new alerts:

1 for Unused import

Comment posted by LGTM.com

Yet to be enumerated, I think we need a dual on-node and as-a-service example to delineate the processes.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v3.13 to before v5.4.155",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1c7a4c24fbfd99442cc6e14dc80fcb00f118e8b8",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7ab488d7228a9dceb2456867f1f0919decf6efed"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "1c7a4c24fbfd99442cc6e14dc80fcb00f118e8b8",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "7ab488d7228a9dceb2456867f1f0919decf6efed",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "NFC: digital: fix possible memory leak in digital_tg_listen_mdaa()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.4.155 by commit 7ab488d7228a9dceb2456867f1f0919decf6efed, it was introduced in version v3.13 by commit 1c7a4c24fbfd99442cc6e14dc80fcb00f118e8b8. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001999


feat: Catch up ZRANGE options

This closes #1117.
I'll add tests later.

All existing tests passed without change. Merging as no regression...
I'm preparing a follow-up to clean up code a bit.


Updating docs for global install usage

Update the docs to include examples and patterns for global install.
Closes #16

lgtm!

@jasonwilson -- Great work! LGTM


Feature baremetal removal

All occurrences of BAREMETAL ifdefs have been removed. The result has successfully been tested with a SCSI and an ISO image.
@akuker Before proceeding with other open issues I will wait for this PR and https://github.com/akuker/RASCSI/pull/134 to have been merged. Otherwise I will drown in merge conflicts.

@akuker I just notied that the code line setting the result message was lost in the develop branch. I re-added it in the branch of this PR . In case there are still any formatting issues please tell me.


wiki

Hi,
The usage of the plugin is unclear to me, is there some sort of a wiki?
Thanks

Hey, there is no full documentation yet. To get started, there is a file in your plugins folder that tells you about the first steps. If there is anything unclear in particular, feel free to ask here and i can give you a detailed explanation!

The documentation can be found here. Files that are not yet fully created named "WIP - ...", but I plan to finish it within the next days


Update KeepWordsTokenFilter to match the spec

Make the Json match the spec
https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-keep-words-tokenfilter.html

LGTM :+1: Thanks @davidtme !  Would you mind signing the CLA so we can pull this in?

@gmarz I have signed the CLA (and confirmed my email address) but it doesn't seem to have update the status

It looks like it has now.  Thanks!


Hpanel accurate info with draw calls

From the author, since the PR is missing a description:

I figured out the issue. I was calling info reset in the stats which only gets called when h panel is open since you added the check game.debugMode in render loop. So when h panel was off, not resetting info was causing rendering issues


assumption of existence of templateOptions

there are several places where the code assumes that field.templateOptions is defined. This may not be the case (or it may be that some code adding templateOptions if is undefined is missing)
this obviously causes problems
A couple of examples of this are:
function ngModelAttrsTransformer : if (typeof field.templateOptions[name] !== 'undefined')
return field.type === 'input' && field.templateOptions.type === 'number';
etc

@jmls You work on PR if you want.
I will fix it by the end of the week.

It will be fixed in the next release


30fps drop when staring into a blank wall with collision.

Godot version
3.5.1
System information
Windows 10, OpenGL ES 3.0 Renderer: NVIDIA GeForce GTX 960/PCIe/SSE2
Issue description
The issue is probably that I am trying to make a 3D game in this engine, it's been joy to use for the 2D game I am soon releasing.
I have been trying to finish my first 3D FPS in time for the Halloween, nothing complex, just a bootleg slenderman.
When player is standing close to a wall and faces it at a slight angle, I get 30 fps drop while in fullscreen mode.
Steps to reproduce

turn on fullscreen mode
walk towards a wall
at a slight angle, best to wiggle your camera around for a bit while pacing forward and back
enjoy the 30fps drop

https://user-images.githubusercontent.com/114881518/198006975-0d84685f-4047-4a85-8a27-e0096a753ccb.mp4
Minimal reproduction project
Here the game was reduced to only relevant scenes.
I previously used Zylann's terrian plugin, while testing the problem, I deleted it though and the issue still persists, so I think that wasn't the cause. Mentioned here for posterity.
slender.zip

Since you are locked to 60 at the start, I assume you have VSync enabled. This means that any time your FPS were to drop to a value below 60, it will be locked to 30 instead to guarantee a stable frame rate. This does however mean that a dip to 59 fps will result in a dip all the way down to 30.
Now that out of the way.
Can you disable vsync, then enable the profiler, and check again. Then report the performance values you get in the profiler. Both for when the problem is present, and when it is not.
You can also do this with vsync enabled, if you want to be thorough.
For the most part though this seems like a "Do thing nobody will ever reasonably do, then things go wrong." kind of scenario.

@TheDuriel Good points about VSync, however I fail to see what is unreasonable in the report? Staring at a wall at an angle is definitely something that happens...

I fail to see what is unreasonable in the report

Intentional creation of a scenario in which their frame rate dips by 0.00001 and vsync kicks in. We have no evidence to believe that this actually would happen in normal gameplay.
Hence why they will want to get some detailed stats from the profiler, not from inference. If we first assume competence on the part of the engine and user. Then this might just be a case of "I can run my scene at 61 fps unlocked, but sometimes I get some lag and it tips to 59." Which isn't actually a problem whatsoever.

That's not what I asked. Though we can simplify the question: Is that stable, or does it occasionally drop to sub 60?
The relevant profiler information is here: https://docs.godotengine.org/en/latest/tutorials/scripting/debug/the_profiler.html We need a graph containing the very first 3 or so properties in the profiler, showing both normal behavior and when you are wall rubbing.

Intentional creation of a scenario in which their frame rate dips by 0.00001 and vsync kicks in. We have no evidence to believe that this actually would happen in normal gameplay.

For the most part though this seems like a "Do thing nobody will ever reasonably do, then things go wrong." kind of scenario.

Please refrain from assuming people's intentions, this kind of comment is absolutely unproductive.
If you see anything you deem unreasonable in the player code, please point it out.

We have no evidence to believe that this actually would happen in normal game play.
This is not an argument, as we don't have evidence of the opposite either. QA testers specifically test for edge cases, so even if it's an edge case it should be looked into, because it could help us discover an engine bug.


Feature/fetch content

Hi,
as discussed in #348 my implementation to use fetch content instead. I've also added instructions on how to use the lib and two examples (one for fetch content and one for find package).
I also made a little bit more fetch friendly for example by including CTest (which will automatically provide a BUILD_TESTING cache variable) and automatically deactive test, if it's not the top level project.
The main.cpp is empty in both though, do you have a very short code using any of the methods from the lib? Just to verify that everything is working. I browsed in the tests, but they seemed a little bit too complicated for this simple example. It doesn't have to be a useful example.

Thanks for the pull request! I will need a bit of time to do a more thorough review.
For main.cpp
test_serializer/Insert.cpp might be a good inspiration?
compare(__LINE__, insert_into(bar).default_values(), "INSERT INTO tab_bar DEFAULT VALUES"); could be a good one-liner (plus includes).
When quickly scrolling through, I noticed that you set the C++ standard to C++14? Ideally, it should still work with C++11.

No worries, take your time. I will be also happy to explain you some thing, if something is unclear. Btw. where is the travis build, shouln't it show up here?
Thanks for the example, I will have a look. I also wondered if I should include the two examples in the pipeline? As kind of an deployment test? I'm not a travis expert, but I think this would be possible and helpful.

When quickly scrolling through, I noticed that you set the C++ standard to C++14? Ideally, it should still work with C++11.

This is only the C++ Version of the examples, it was just randomly chosen :) But I agree, it would be best to set it to the minimum version possible for testing purposes. I will change it

For main.cpp
test_serializer/Insert.cpp might be a good inspiration?
compare(__LINE__, insert_into(bar).default_values(), "INSERT INTO tab_bar DEFAULT VALUES"); could be a good one-liner (plus includes).

The problem is that this needs compare.h, which needs MockDb.h ... I don't wont to depend on these files, because people just just use that sample as a quick test to see if everything is working (so use it outside of this repository).
Anything else, which just depends on the official headers?

OK, so how about this as a one-liner?
select(sqlpp::value(false).as(sqlpp::alias::a)));

Does not do anything, but if this compiles, we should be in good shape.
We could serialize without MockDb, if you want some runtime test, too.

Re Travis: Thanks for noticing. They are here: https://travis-ci.org/github/rbock/sqlpp11/pull_requests and they failed. Strange that they are not shown.

I think this should be ready except the fact that the url in fetchConent is still pointing to my repo. (So I will leave it a draft). When you approve the pull request I will change that to your repo and the development branch.
I tested both the find_package as well as the fetchConent approach on my Linux machine.

Looks great!
In addition to the two comments: Please add copyright and license to the new example files, too.

Okay all done :)

Great! Assuming that the checks pass (strange that travis still does not show up), I'll merge during the weekend.

Great! Assuming that the checks pass (strange that travis still does not show up), I'll merge during the weekend.

I saw that issue on other repos as well, a quick search found this
https://travis-ci.community/t/travis-ci-build-no-longer-showing-as-check-on-github-pull-request-page/6955/10
Perhaps you have to renew something?

Thanks for the hint. Apparently, I needed to sign up to beta to migrate some of the repositories.

I updated the readme to point to travis-ci.com now. Could you rebase, please? We could see if the travis build shows up again :-)

Seems to work again :)

Great! I would squash and merge using these comments, OK?

Add date as a dependency, make fetch friendly
Add example
Add alias
Update readme
Add find_package example
Update travis

Sure, go ahead! :+1:

Done.
I'll let this stew for a couple of days before tagging a new release.


Falco Hot Reloader Proposal

Motivation
The Falco project has a built-in hot-reload feature, so what is our concern to do that kind of project? Simple, the Falco project can reload itself when it receives a SIGHUP signal, so think of that scenario in a Kubernetes environment; the Falco uses a ConfigMap, which includes configuration and rule files Falco can use. We want to add support to monitor these files, detect changes against them, and send SIGHUP signals to Falco. To do that, we need to know a couple of things:

How can access PID of the Falco process within the same Pod?
Are ConfigMaps mounted inside the Pod reloading itself against updates?

How can access PID of the Falco process within the same Pod?
We know that Pod is a concept that can include one or more containers in it, and we are generally using Pods with one container inside it. However, sometimes we might need an extra container to assist the main container in Pod. So, how containers in the Pod can communicate with each other? There are multiple ways of doing this, such as Shared Volume, IPC, localhost net interface, etc. In our case, we will share the process namespace between containers in a Pod; with that, we will now access the Falco container PID from a different container.
To get more detail about the concept, please follow the link.
Are ConfigMaps mounted inside the Pod reloading itself against updates ?
There is a really well-explained section about this question in the Kubernetes documentation, and it says:

When a ConfigMap currently consumed in a volume is updated, projected keys are eventually updated. The kubelet checks whether the mounted ConfigMap is fresh on every periodic sync. However, the kubelet uses its local cache for getting the current value of the ConfigMap. The type of the cache is configurable using the ConfigMapAndSecretChangeDetectionStrategy field in the KubeletConfiguration struct. A ConfigMap can be either propagated by watch (default), TTL-based or redirecting all requests directly to the API server. As a result, the total delay from the moment when the ConfigMap is updated to the moment when new keys are projected to the Pod can be as long as the kubelet sync period + cache propagation delay, where the cache propagation delay depends on the chosen cache type (it equals to watch propagation delay, TTL of cache, or zero correspondingly). ConfigMaps consumed as environment variables are not updated automatically and require a pod restart.

We can configure this sync frequency in the Kubelet with a parameter called --sync-frequency.
Feature
@Issif @Kaizhe @Dentrax and I developed a little Go binary that continuously monitors Configmap which includes rules and configuration of the Falco. Whenever the binary sees that there is a change about the rules, it will send a SIGHUP signal to the Falco's container within the same Pod. By doing that Falco can be able to reload itself and continue to work with the new configurations.
You can access all the details about the project by following the repository link.

I think we should provide a way to test this feature with a fork of helm chart which embeds your docker as sidecar.

Question: why do you need a separate binary to do this?  Why can't you just have an inotify within falco that monitors the mounted configmap, and reloads the policy engine when there are changes?  We did this in a different but related project and it seemed to work well.  Maybe I'm missing something.

@terylt of course we can, the idea was to POC without writing C code in falco core.

I agree that it would be more ideal to implement inside Falco. Maybe we can have it in the roadmap. Meanwhile, I also think hot-reloader is helpful before the feature is ready (if it is not ready in the next release). A few things I guess would be needed here for this idea:

A falcosecurity/falco-rule-hot-reloader image name
A dedicated YAML file
An option in the Falco helm chart.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

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.

/reopen
/remove-lifecycle rotten

@jasondellaluce: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

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 had an idea related to this proposal. See my comment here :point_down:
https://github.com/falcosecurity/falco/pull/1849#issuecomment-1066980074

Update:
I've had a nice chat with @FedeDP, and we have come up with a possible implementation.
Basically, as a first step, we want to implement a simple file watching mechanism (i.e., using inotify) directly into Falco and rely on the existing hot reload feature. Although this solution may be suboptimal, we would achieve the same result this proposal described (but only using the Falco binary). Moreover, it's possible to use inotify in combination with signals, so we probably won't need to use a separate thread or other syscalls repeatedly.
Further improvements can come later without breaking this contract with the user. For example, in a second step, we could improve the way Falco reloads itself when only rules are changed (in most cases, just switching the ruleset at runtime, without a full reload, should be enough and faster).
N.B.

the current hot reload implementation should already work fine with plugins, but I have realized right now that it's not extensively tested. So maybe we should start by checking if the current hot-reload works as expected.

/assign

Yes, this issue has been fixed. @developer-guy is anything missing in your opinion?

Great, I'm closing this one, thanks.


Implement dark mode

Task

Implement dark mode for the dashboard

Deliverables

Dark mode functionality for the dashboard

Size Estimation: Medium (2-4 hours)

Implemented w/ persistent state @Yuxuan-Wu @davidtso1219


Could not connect to Conbee 3

I recently bought a brand new Conbee III and have a fresh installation with Debian 12 on intel NUC 6.
The Conbee was updated on Windows PC with newest Firmware. Deconz installed via Docker Image.
With all deconz docker images (beta/stable/latest) I got the same issue.
failed to reconnect to network
COM: /dev/ttyUSB0 / serialno: , ConBee
ttyUSB0 is the right port as given by:
ls -al /dev/serial/by-id/usb-dresden_elektronik_ConBee_III_DE...........-port0
--> ../../ttyUSB0
The Deconz GUI is available and shows me the correct frontend version, depending on the image.
On the gateway page the firmware is "not connected"
zigbee channel 0 and network id "unknown"
I also tried ttyACM0 and any other possibiliies I found in the web with no success.
Starting with sudo doesn't help. "privileged" parameter is set in the docker-compose.yaml.
My productive installation with ConBee I on Debian 9 runs without any issues on another NUC.
Any hints?

https://github.com/deconz-community/deconz-docker?tab=readme-ov-file#notes-for-conbee-3-users

I added my user to the dialers group and set the baudrate. Restarted the system bot had no success.
``ỳaml
version: '3'
services:
deconz:
image: deconzcommunity/deconz:2.23.02
container_name: deconz
network_mode: host
restart: always
privileged: true
volumes:
- /home/psc/Docker-Env/deconz/data/:/opt/deCONZ
devices:
- /dev/ttyUSB0
environment:
- DECONZ_WEB_PORT=8080
- DECONZ_WS_PORT=8443
- DEBUG_INFO=1
- DEBUG_APS=0
- DEBUG_ZCL=0
- DEBUG_ZDP=0
- DEBUG_OTAU=0
- DECONZ_BAUDRATE=115200
- DECONZ_UID=0
- DECONZ_GID=0
- DECONZ_VNC_MODE=0
- DECONZ_DEVICE=/dev/ttyUSB0
- DECONZ_VNC_PORT=5959
- DECONZ_VNC_PASSWORD=xxxxxxxxx
``

I don't think Conbee 3 was yet supported in the version you try to run

Yes you're right. With the "latest" release (2.25.2) it works now. Thank you very much.


[WIP]Send slack notification for alarms

What is this PR trying to achieve?
Send slack notification for alarms
Who is this change for?
Devs
Have the following been considered/are they needed?

[ ] Run terraform apply.

flake8 is upset about whitespace
+docker run -v /home/travis/build/wellcometrust/platform-api/lambdas:/data python3.6_ci:latest
flake8 /data
/data/post_to_slack/post_to_slack.py:43:5: E122 continuation line missing indentation or outdented
/data/post_to_slack/post_to_slack.py:44:5: E122 continuation line missing indentation or outdented


Bug: The dialog doesn't close evertime when i am on firefox

Sometimes when pressing the close button of a dialog the dialog stays visible in firefox.
This might be caused by the animation repeatedly being triggered

Closing since this issue is fixed in Fylgja Dialog v1.4
Thank you @JoshuavanGelder for bringing this issue to our attention.


dnsmasq updates

Fixes a little bug that prevented dnsmasq from getting the consul DNS data when consul binds to all interfaces (<IP_ADDRESS>). In this case, dnsmasq will now just query localhost.
Adds the dnsmasq listen-address option, only configured if provided.
Updates the dnsmasq service management to make sure it is enabled, and restarted if config is changed.

👍 Thanks!


After installing thefuck terminal starts blank and takes quite a few seconds to show "username@devicename ~/Folder$". Purging thefuck fixes the delay issue, but everytime I open terminal (konsole & xterm) it shows "Command 'thefuck' not found, but can be installed with:  sudo apt install thefuck".

 Please update and reopen if still an issue. Please add as much information as you can (i.e. please fill the spaces where it says “fill this in” – a.k.a. please help us help you)


Unconfirmed balance not showing

BUG REPORT
Hello, I firstly stopped to mine due to another cause on the miners during circa 2 weeks. I then changed my email adress because I thought it would maybe change something and can't see nothing as unconfirmed balance. Only my past balance.
Stack Trace or error message
No error mesage
Expected Behavior
To see the pool mining some uncofirmed balance
How to reproduce it (as minimally and precisely as possible)
Get a key via nanoppol to mine SIA
Mine 205 SIA
Wait for one weeks without mining
Re connect your Wallet on the pool
Nothing happen and hasrate cuurent is 1032
Environment : I don't know what you need as information for this item.

Sia version: SIA v1.3.1

OS: Windows 7 64 bit

Thanks for your time and answer and have a good day,*
Pierre

Double check that Sia has the correct pool information.  This sounds like an issue with nanopool and not Sia.  You might try opening an support ticket with them.  You may also be able to get more support in the Sia Discord server.
I'm going to close this issue as there is not action the Sia devs need to take.  If you think it was prematurely closed feel free to reopen it and mention why.


Using baseUrl and paths on node

I notice the feature is for requirejs and systemjs. And as this comment said, the emitted js code is unchanged by the configuration:
https://github.com/Microsoft/TypeScript/issues/5039#issuecomment-206451221
So the primary usage is to resolve packages in various locations (e.g. jspm_packages) for transpilation.
I have the following interesting use case. It worked for me so far as I was using jspm, i.e. the actual module loading happens on the browser. However it fails when I try to do the same using ts-node (fail because it runs on node and the reason above).
Is there a way to support this?
Here is the example:
// tsconfig.json
{
  "compileOptions": {
    "baseUrl": ".",
    "paths": {
      "my-package": [ "src/" ]  // i.e. mapping the package name to the source folder
    }
  }
}

// test/sometest.ts
import abc from 'my-package';
...

i.e., using paths so tests can reference the source as if it is a regular module.
🌷
Reference issue on ts-node: https://github.com/TypeStrong/ts-node/issues/138

this is already supported in TS today. if you run tsc it should resolve your module. i would say this is specific to how ts-node works.

Yes. Tsc compiles successfully. But as you mentioned in the past, there is no change(path rewrite) on the emitted js files. If I run the test js file through node, would result in the same error

But as you mentioned in the past, there is no change(path rewrite) on the emitted js files. If I run the test js file through node, would result in the same error

But that is the purpose of these settings, to allow module loaders than can remap modules to remap modules.  The CommonJS loader in NodeJS was not designed as a module loader that is configurable in this way, because the base assumption is that you would have access to a file system with a very deterministic resolution pattern for resolving modules.
I personally would not want TypeScript to re-write MIDs, but giving the flexibility to resolve modules in the way my loader will resolve modules at run-time, which TypeScript 2.0 does perfectly.
Especially with CJS under NodeJS, because the default loader is not configurable in that sense, any remapping by TypeScript would require making invalid assumptions about the run-time environment and likely result in code that does not work at run-time and certainly not a distributable package that could be consumed by anyone using npm.
Because of the assumptions made by the CJS loader in NodeJS we distribute our packages in UMD format and recommend people use an AMD loader that easily allows remapping, even when running under NodeJS.  But knowing that there is a "cowpath" to CJS we include an index.js in the root of our packages which loaders a transpiled main.ts (which is the "default" for AMD) which exports the public API of the package.  We use dts-generator to create a .d.ts where the main module for the package gets exported as the package name, therefore providing the types when the package is required.  It does mean that those loading only under CJS are limited to the main module, while those using AMD or another configurable loader can reference each module individually.

But that is the purpose of these settings

Fully understand that is how it should be used, just that I found this use case interesting because it creates a mental disconnect between what's appear to be working on the IDE but failed on runtime.
One option is to add a mapPathForNode flags that will create a separate js file that does the remapping under node (I'm not excel in node so I don't know if this is possible).
Just brainstorming.

To make sure I deliver my message correctly, I don't want to suggest a feature that doesn't have a real use case.
In this case, it is like "I abuse the system and complain it doesn't work". Fully aware of that. Just want to open the discussion to see if this would lead to some interesting possibilities.
🌷

One option is to add a mapPathForNode flags that will create a separate js file that does the remapping under node (I'm not excel in node so I don't know if this is possible).

That seem clearly the domain for tooling outside of the scope of TypeScript.  Especially considering the design goals:

Impose no runtime overhead on emitted programs.
Preserve runtime behavior of all JavaScript code.

And anti-goal:

Add or rely on run-time type information in programs, or emit different code based on the results of the type system. Instead, encourage programming patterns that do not require run-time metadata.

Appreciating TS's position, here's a simple solution to the 90% use case for those of us using node, but wanting the convenience of using baseUrl relative require() calls without any fuss.
This solution hooks node's require() call, and resolves requests using the dirname of "main" to mimic baseUrl. It therefore assumes the baseUrl compiler option was also set to the same directory where the source "main.ts" was located.
To use, paste this tiny chunk of code at the top of your "main.ts".
import * as path from 'path'
import * as fs from 'fs'
const baseUrl = path.dirname(process['mainModule'].filename)
const moduleProto = Object.getPrototypeOf(module)
const origRequire = moduleProto.require
const CH_PERIOD = 46
moduleProto.require = function(request) {
  if(!path.isAbsolute(request)) {
    if(request.charCodeAt(0) !== CH_PERIOD) {
      const hasJsExt = path.extname(request).toLowerCase() === '.js'
      const basedRequest = path.join(baseUrl, hasJsExt ? request : request + '.js')
      if(fs.existsSync(basedRequest)) request = basedRequest
    }
  }
  return origRequire.call(this, request)
}

@papercuptech This is brilliant. I modified your code and it worked like a charm in my isomorphic react project.
(function () {
  const existsCache = {d: 0};
  delete existsCache.d;
  const baseUrl = path.join(cwd, tsConfig.compilerOptions.baseUrl);
  const moduleProto = Object.getPrototypeOf(module);
  const origRequire = moduleProto.require;
  const pathKey = {};
  for (const [key, value] of Object.entries(tsConfig.compilerOptions.paths)) {
    pathKey[key.slice(0, -2)] = value[0].slice(0, -2);
  }
  moduleProto.require = function (request) {
    if (request[0] === '@') {
      let existsPath = existsCache[request];
      if (existsPath === undefined && request[0] === '@') {
        const pathName = request.match(/(@.*?)\//)[1];
        const relativeToBase = path.relative(path.dirname(this.id), baseUrl);
        existsPath = relativeToBase + '/' + pathKey[pathName] +  request.slice(pathName.length);
        existsCache[request] = existsPath
      }
      return origRequire.call(this, existsPath || request)
    }
    return origRequire.call(this, request);
  };
})();

Here I'm assuming that the tsconfig.json is like
    "paths": {
      "@pages/*": ["./ui/pages/*"],
      "@components/*": ["./ui/components/*"],
    },

where the keys in the paths start with @. If someone needs it to be more general, modifications could be made further.

@papercuptech So many people on the internet want this. Would be a neat idea to implement this into a stable package possibly.

Maybe you'd be interested in https://github.com/jonaskello/tsconfig-paths?

Maybe you'd be interested in https://github.com/jonaskello/tsconfig-paths?

Yes. Thank you.

Maybe you'd be interested in https://github.com/jonaskello/tsconfig-paths?

The problem with this is, that tsconfig-paths or require hook and tsconfig.json  also have to be used in production, where it is preferable to have just TS build output results. I think TS compiler here could really help to get rid of excessive tooling overhead and double mapping configuration. It could be made configurable and of course optional.
Here is a link to another issue about it https://github.com/Microsoft/TypeScript/issues/18951

Re-writing module names is really quite dangerous and not something TypeScript should involve itself with.  Providing the right tooling to make what is written work like it would at run-time under different loaders is the most logical solution.  TypeScript is not a module loader.  While the default loader with NodeJS does not support remapping, there are many loaders and bundlers that run under NodeJS that provide a lot of flexibility and configuration.  We should tools what they are designed for.

Probably, it would be good to have open plugin API for the compiler (there is one not stable yet) and convenient way of applying plugins to the standard compilation process (there is none as I'm aware of), something like babel has. This would allow solving such tasks.

Typescript should give an option to allow "directory expansion" for path alias defined in "tsconfig.json" and used in module importation.  it would be nice to have something like:
{
    "compilerOptions": {
          "expandImport":true,
	   "paths": {
			"@fooPath/*":["./path/to/manyfoos/*"]
            }
     }
}

TS Code:
import {Foo} from "@fooPath/MyFoo"
Compilation:
const Foo = require("path/to/manyfoos/MyFoo");

Oh wow I just got burned by this - thought it was a shortcut for easy readability.
Is there an open request for similar functionality to paths but like shortcuts instead?

@arogozine  you could instead try to use one of the following two strategies:

Using a typescript alias path loader for node.js projects:
https://www.npmjs.com/package/@momothepug/tsmodule-alias

Avoid using path alias and instead define index.ts for each module you have like in:
https://github.com/palantir/tslint/blob/master/src/index.ts

You can define an "index.ts" inside your "module" or "submodule directory", then  you should "export" many "alias import" as you want, for instance, if you have an "AnimalModule" with an structure like:
AnimalModule/
------DogModule/
------------dogs/
------------------------kind1/dog1.ts
------------------------kind2/dog2.ts
------------------------kind3/dog3.ts
------CatModule/
------------cats/
------------------------kind1/cat1.ts
------------------------kind2/cat2.ts
------------------------kind3/cat3.ts
------IguanaModule/
------------iguanas/
------------------------kind1/iguana1.ts
------------------------kind2/iguana2.ts
------------------------kind3/iguana3.ts

// DogModule/index.ts:
import * as dog1 from "./dogs/kind1/dog1.ts";
import * as dog2 from "./dogs/kind2/dog2.ts";
import * as dog3 from "./dogs/kind3/dog3.ts";
export {dog1, dog2, dog3};

// CatModule/index.ts:
import * as cat1 from "./cats/kind1/cat1.ts";
import * as cat2 from "./cats/kind2/cat2.ts";
import * as cat3 from "./cats/kind3/cat3.ts";
export {cat1, cat2, cat3};

// IguanaModule/index.ts:
import * as iguana1 from "./iguanas/kind1/iguana1.ts";
import * as iguana2 from "./iguanas/kind2/iguana2.ts";
import * as iguana3 from "./iguanas/kind3/iguana3.ts";
export {iguana1, iguana2, iguana3};

Then you can use any module defined before like this:
// MyApp.ts
import {iguana1} from "./AnimalModule/IguanaModule"
import {cat3} from "./AnimalModule/CatModule"
import {dog2} from "./AnimalModule/DogModule"

And Also you can now define submodules declarations inside a parent module like the following example:
// AnimalModule/index.ts:
import * as dogs from "./DogModule";
import * as cats from "./CatModule";
import * as iguanas from "./IguanaModule";
export {dogs, cats, iguanas};

Using AnimalModule definition like this:
// MyApp.ts
import {iguanas, cats, dogs} from "./AnimalModule"
// iguanas.iguana1
// cats.cat3
// dogs.dog2

As a side note, it would be better to not rely on namespacing. i.e.
// instead of
import * as cat1 from "./cats/kind1/cat1.ts";
import * as cat2 from "./cats/kind2/cat2.ts";
import * as cat3 from "./cats/kind3/cat3.ts";
export {cat1, cat2, cat3};

// just re-export
export * from './cats/kind1/cat1.ts'
export * from './cats/kind2/cat2.ts'
export * from './cats/kind3/cat3.ts'

Tree shaking and namespacing doesn't work well together.

@unional  awesome!  It's a better way, thanks.


Is it possible to mimic the firebase links preview page behavior, without it?

as we approach developing deep linking into our apps a question about the firebase dynamic links preview page came up.
if we want to use a link to the native apps inside our website, do we still have to use the preview page to get the most reliable user identification results on ios? can't we just mimic it's behavior in our js code?
copying the link to the clipboard is rather simple. is that the only thing it does? i didnt find any documentation about it and it seems rather odd we don't have a way to build our own preview page or building it's functionality into our existing web pages. is there a greater cause for this?
thanks.

Hi..currently this is not supported. You can though add more content to your app preview page. https://firebase.google.com/docs/dynamic-links/link-previews


Create a plugin for the Kitura Credentials framework that supports FaceBook tokens from mobile apps.

 Issue by KALLNER
Tuesday Jan 26, 2016 at 16:39 GMT
Originally opened as https://github.ibm.com/ibmswift/Phoenix/issues/73

Create a plugin that can be used by servers to validate FaceBook OAuth tokens sent from mobile apps.
Note This is not the same as logging in a web app using one's FaceBook ID. Here we assume that the mobile app has used a FaceBook SDK to perform a login using FaceBook and is now sending requests to the server using an OAuth token the app received from FaceBook.

This issue is complete except for a README.md file which will be done in the next sprint under issue #253

Validated.


Editing Makefile

Hey! I was just trying to install the software (LINUX-X86_64-G95-MPI) and when I tried to make I realized the path for the FC and LD flags seem to be hardcoded in the makefile? Shouldn't they better use the MPI_HOME variable? Or is it necessary to install OPENMPI-1.6.5-g95-0.94-intel in the specified location?
I'd appreciate a fast reply so I can resume installation

Helpful.

Was able to solve this. Would probably be a great idea not to hardcode all your flag destinations in the cofigure file


Fix broken links in WB recipes docs

R: @petele @Snugug

Whoops!
There were 14 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/tools/workbox/modules/workbox-recipes.md#L17 - Line must be at most 100 characters
src/content/en/tools/workbox/modules/workbox-recipes.md#L21 - Line must be at most 100 characters
src/content/en/tools/workbox/modules/workbox-recipes.md#L23 - Line must be at most 100 characters
src/content/en/tools/workbox/modules/workbox-recipes.md#L78 - Line must be at most 100 characters
src/content/en/tools/workbox/modules/workbox-recipes.md#L80 - Line must be at most 100 characters
src/content/en/tools/workbox/modules/workbox-recipes.md#L119 - Line must be at most 100 characters
src/content/en/tools/workbox/modules/workbox-recipes.md#L121 - Line must be at most 100 characters
src/content/en/tools/workbox/modules/workbox-recipes.md#L158 - Line must be at most 100 characters
src/content/en/tools/workbox/modules/workbox-recipes.md#L160 - Line must be at most 100 characters
src/content/en/tools/workbox/modules/workbox-recipes.md#L201 - Line must be at most 100 characters
src/content/en/tools/workbox/modules/workbox-recipes.md#L203 - Line must be at most 100 characters
src/content/en/tools/workbox/modules/workbox-recipes.md#L250 - Line must be at most 100 characters
src/content/en/tools/workbox/modules/workbox-recipes.md#L252 - Line must be at most 100 characters
src/content/en/tools/workbox/modules/workbox-recipes.md#L303 - Line must be at most 100 characters


C1083	Cannot open include file: 'pangolin/pangolin_export.h': No such file or director

Cannot open include file: 'pangolin/pangolin_export.h': No such file or directory	_pangolin	C:\Users\Shuprio\Desktop\pangolin-master\include\pangolin\platform.h	45

Has anyone tried this on window?

@shuZro what was the solution?

I'm in the same problem. How do I solve it?