make install sed error

Ran: brew install johnhcc/gs-x11/gv and got:
`...
==> make install
Last 15 lines from /Users/tom/Library/Logs/Homebrew/gv/02.make:
clang -DHAVE_CONFIG_H -I.  -DNON_BLOCKING_IO -DGV_CODE -DGV_LIBDIR="/usr/local/Cellar/gv/3.7.4/share/gv" -I../lib -I../lib -g     -g -O2 -DXAW_INTERNATIONALIZATION -DXAW_MULTIPLANE_PIXMAPS -DXAW_GRAY_BLKWHT_STIPPLES -DXAW_ARROW_SCROLLBARS -I/usr/local/Cellar/libxau/1.0.9/include -I/usr/local/Cellar/libxdmcp/1.1.3/include -I/usr/local/Cellar/libxcb/1.14_1/include -I/usr/local/Cellar/libx11/1.7.0/include -I/usr/local/Cellar/libxext/1.3.4/include -I/usr/local/Cellar/libice/1.0.10/include -I/usr/local/Cellar/libsm/1.2.3/include -I/usr/local/Cellar/libxt/1.2.1/include -I/usr/local/Cellar/libxmu/1.1.3/include -I/usr/local/Cellar/libxaw3d/1.6.3/include -I/usr/local/Cellar/xorgproto/2021.3/include -c Scrollbar.c
creating gv_user.ad
creating gv_system.ad
creating GV.ad
cat ./gv-update-userconfig.in > gv-update-userconfig
creating GV
sed -e 's/^[^!]/!&/' GV.ad > ../GV
echo "END" >> gv-update-userconfig
sed: RE error: illegal byte sequence
cat GV.ad >> gv-update-userconfig
make[2]: *** [../GV] Error 1
make[2]: *** Waiting for unfinished jobs....
cat ./gv_misc_res.dat >> gv-update-userconfig
make[1]: *** [install] Error 2
make: *** [install-recursive] Error 1
If reporting this issue please do so at (not Homebrew/brew or Homebrew/core):
https://github.com/johnhcc/homebrew-gs-x11/issues`
Noticed in ~/Library/Logs/Homebrew/gv/02.make:
`...
clang -DHAVE_CONFIG_H -I.  -DNON_BLOCKING_IO -DGV_CODE -DGV_LIBDIR="/usr/local/Cellar/gv/3.7.4/share/gv" -I../lib -I../lib -g     -g -O2 -DXAW_INTERNATIONALIZATION -DXAW_MULTIPLANE_PIXMAPS -DXAW_GRAY_BLKWHT_STIPPLES -DXAW_ARROW_SCROLLBARS -I/usr/local/Cellar/libxau/1.0.9/include -I/usr/local/Cellar/libxdmcp/1.1.3/include -I/usr/local/Cellar/libxcb/1.14_1/include -I/usr/local/Cellar/libx11/1.7.0/include -I/usr/local/Cellar/libxext/1.3.4/include -I/usr/local/Cellar/libice/1.0.10/include -I/usr/local/Cellar/libsm/1.2.3/include -I/usr/local/Cellar/libxt/1.2.1/include -I/usr/local/Cellar/libxmu/1.1.3/include -I/usr/local/Cellar/libxaw3d/1.6.3/include -I/usr/local/Cellar/xorgproto/2021.3/include -c Scrollbar.c
creating gv_user.ad
creating gv_system.ad
creating GV.ad
cat ./gv-update-userconfig.in > gv-update-userconfig
creating GV
sed -e 's/^[^!]/!&/' GV.ad > ../GV
echo "END" >> gv-update-userconfig
sed: RE error: illegal byte sequence
cat GV.ad >> gv-update-userconfig
make[2]: *** [../GV] Error 1
make[2]: *** Waiting for unfinished jobs....
cat ./gv_misc_res.dat >> gv-update-userconfig
make[1]: *** [install] Error 2
make: *** [install-recursive] Error 1
HOMEBREW_VERSION: 3.0.10
ORIGIN: https://github.com/Homebrew/brew.git
HEAD: 0ad2564c5f1ddf6f16f707f2861556b80546713c
...`
Looks like Homebrew removed the build directory (or I can't find it). From the command line, sed has no problem with the regular expression. Configure issue or Makefile quoting? I'm happy to dig further.
Macos 11.2.3 x86
Thanks!

The problem may not be here, but with the combination of macOS BSD sed, NLS, and the contents of the GV.ad file. If I hand run configure and make, the BSD sed call likewise fails. Setting LANG=C allows the BSD sed command to succeed, and using Gnu sed (Homebrew) does not need the LANG override. My zsh environment happens to contain LANG=en_US.UTF-8 (I don't recall setting this).
The configure script contains:
# NLS nuisances.
LC_ALL=C
export LC_ALL
LANGUAGE=C
export LANGUAGE

I'm not familiar with LANGUAGE, only LANG. These settings do not appear to make it into the Makefiles.
I see a few possible solutions:

Put LC_ALL=C on the make install command line in the gv.rb script here.
Add a dependency here on (Homebrew) gsed and edit src/Makefile(.am) here to use it.
Put the onus on Gnu to fix it.

Possibly relevant: https://unix.stackexchange.com/questions/509606/newlines-in-bsd-sed-vs-gsed

This results in a working gv:
make install LC_ALL=C

Thanks for looking into this!  I'll test your solution and make sure it doesn't break anything on the systems I have for testing, and make the change.  I much appreciate your report.

I'm still not 100% clear on why this is happening... but I've changed Line 21 in gv.rb from system "make", "install" to system "make", "install", "LC_ALL=C" for consistency with the configure script. At the very least this causes no problems for me, and at best it solves your problem! If you'll confirm that that's going to fix things on your end, I'll push the change.
Again, thanks for the report!

I traced the issue to a copyright line src/Makefile adds to some of the src/*.ad files while being composed, specifically the entry for José Marchesi (cf. below). The é is encoded in Latin-1 (ISO-8859-1; \351, 0xE9), and Apple's BSD sed in the Unicode (UTF-8) environment trips up on it (hence the LC_ALL=C override as a 'patch'). In nearly all other copyright lines in other files for this person, the 'e' does not have the accent (is ASCII). If I convert the Latin-1 é to UTF-8, Apple sed has no issue with it.
I initially considered this a bug with Apple's sed being overly picky, but now consider it an issue with Ghostview. It's old enough they may not want to fix it; I'll look into filing an issue with them. I installed gv only to have a second PostScript viewer while tracking down a music notation rendering bug in MuseScore 3.
../GV : GV.ad
@echo "creating GV"
sed -E -e 's/^[^!]/!&/' GV.ad > ../GV
GV.ad : gv_system.ad
@echo "creating GV.ad"
@cp gv_system.ad GV.ad
gv_system.ad : gv_user.ad
@echo "creating gv_system.ad"
@cp gv_user.ad gv_system.ad
gv_user.ad : $(srcdir)/gv_user_res.dat gv_intern_res_unix.dat gv_make_res.dat
@echo "creating gv_user.ad"
@echo "!"                                               >  gv_user.ad
@echo "!  gv_user.ad"                           >> gv_user.ad
@echo "!  User specific application defaults for gv"    >> gv_user.ad
@echo "!  Copyright (C) 1995, 1996, 1997  Johannes Plass"       >> gv_user.ad
@echo "!  Copyright (C) 2004,2005,2006,2007 José E. Marchesi"   >> gv_user.ad
@echo "!"                                               >> gv_user.ad
@cat $(srcdir)/gv_user_res.dat                                  >> gv_user.ad
@cat gv_intern_res_unix.dat                             >> gv_user.ad
@cat gv_make_res.dat                                    >> gv_user.ad

https://savannah.gnu.org/bugs/index.php?60337

I think that the files should spell people's names correctly, so the better solution is changing the makefile to use LC_ALL=C when running sed. Can you post a makefile that works? Or do you think that it is better to change the accented characters in all of the files from 8-bit Latin-1 ISO to UTF-8? I don't know what happened to the gv mainainer. I have a lot of gv patches, and I was thinking of posting an updated gv on github.

Interesting point, @william8000. It looks to me like the make install LC_ALL=C work-around produces a binary that is identical to that produced by systems with gnu sed installed (which contains the spellings without accented characters). I suppose either the authors weren't concerned about this, or weren't aware (or both).
I'll mess around with this a bit and see what I can come up with.  (If either of you comes up with something better first, please just update this post.)
Good question about what happened to maintenance of gv. If you decide to post an updated fork on github, let me know - it's easy enough for me to point this tap there.  Thanks!

I posted my repository to https://github.com/william8000/gv
I added LC_ALL=C before the sed line.
I am not sure what to do with the accented characters. I think that the old X11 code expects 8 bit ISO, but gv/src/nls has UTF-8, so maybe UTF-8 would work.
gv/NEWS has a list of my changes. Unfortunately it is all in one commit, but if you think that it would be useful but don't like some of the changes (in particular, I flipped pan and zoom on the mouse buttons), I could move those changes to a branch.


[Arctic-44][Hive][AMS]Impelement util to upgade hive table to arctic table with hive base store

Why are the changes needed?

Arctic Planned in 0.3.1 supports Hive table compatibility.  AMS Dash Dashboard need to support for upgrade a Hive table  to an Arctic table and also hive moudle need to move Hive data file to Arctic base table.
Brief change log

Support ams upgrade a Hive table to Arctic table
Support migrate Hive data file to Arctic Base table

How was this patch tested?
An environment was constructed and four types of tables were tested include pk partition table, no pk partition table, pk no partition table, no pk no partition table
Documentation

This pull request introduces a new feature.

@shendanfengg, could you please update the title from impelement to implement?


MBot: Persist messages from DMR

AS A Tester
I WANT incoming messages that are received by the MockBot from DMR to be persisted and retrievable (at least temporarily)
SO THAT I can make test assertions.
Update the existing code for the mock bot so that when it receives an inbound message from DMR, it is persisted in the in-memory Chats object and therefore will be returned by the FindAll action on the ChatController.
Acceptance Criteria

[ ] Update DmrController to properly persist the incoming message against the existing chat
[ ] Ensure the FindAll action in chat controller returns messages that have been received from Dmr
[ ] Update tests to pass coverage and mutation thresholds

This story has not really been started (I've spent about 1.5 hours on it) so it can go through to sprint 10 as it is without needing to split.


some python dependencies are missing

Thank you for this great work!
It's worth to mention in readme that some python modules are required:
# (optional) virtualenv venv
pip install docutils
pip install pygments

# without virtualenv
pip install --user docutils
pip install --user pygments

Good point @Tset-Noitamotua
I'll go add something for this, but probably try to keep it short (the readme is already long...)


fix hasn't initialize select vector when number of nested values equals zero

Proposed changes
Fix bug when reading array type in parquet file:
ERROR 1105 (HY000): errCode = 2, detailMessage = [INTERNAL_ERROR]Read parquet file xxx failed,
reason = [IO_ERROR]Decode too many values in current page

When reading normal columns, ScalarColumnReader::_read_values still calls ColumnSelectVector::set_run_length_null_map to initialize select vector, but ScalarColumnReader::_read_nested_column hasn't do this, making the number of values wrong. The situation where this error occurs is particularly extreme: The column pages have remaining values to be read, but all of them are null values at ancestor level, so there's no actual read operation, just skipping null values at ancestor level.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.77 seconds
stream load tsv:          427 seconds loaded<PHONE_NUMBER>9 Bytes, about 167 MB/s
stream load json:         21 seconds loaded<PHONE_NUMBER> Bytes, about 107 MB/s
stream load orc:          59 seconds loaded<PHONE_NUMBER> Bytes, about 17 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230423111246_clickbench_pr_133385.html

Is there any test case?

run p0

run buildall

run buildall


No Controls and Does not uninstall.

Griffeen Glen Vale:
I installed the "Apple macOS Dark Mode" theme to a 2009 iMac running High Sierra OS/X 10.13.6, but once installed it did not show up in my onboard list of extensions, nor was there any way to access controls for it. It's disturbing enough not knowing where this theme/extension installs itself, but even more-so that there is no way to uninstall it!
First, please tell me how to access the controls for it.
Second, please tell me how to uninstall it.
Thank you,
Douglas Pemberton

Hi Douglas,
Thank you for contacting us.

It’s not showing up in the extensions because it’s a theme and are treated different by Chrome
To remove a theme please follow -> https://support.google.com/chromebook/answer/148695?hl=en

￼
If you require any further information, feel free to contact me.

On 19 Jun 2023, at 08:38, Dapembe @.***> wrote:
Griffeen Glen Vale:
I installed the "Apple macOS Dark Mode" theme to a 2009 iMac running High Sierra OS/X 10.13.6, but once installed it did not show up in my onboard list of extensions, nor was there any way to access controls for it. It's disturbing enough not knowing where this theme/extension installs itself, but even more-so that there is no way to uninstall it!
First, please tell me how to access the controls for it.
Second, please tell me how to uninstall it.
Thank you,
Douglas Pemberton
—
Reply to this email directly, view it on GitHub https://github.com/hungryweb/apple-macos-dark-mode/issues/1, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4S27DTZX5GL4NNYTJMRHTXL7QUVANCNFSM6AAAAAAZLNHDSI.
You are receiving this because you are subscribed to this thread.

Thank you!

On Jun 18, 2023, at 10:47 PM, Hungryweb @.***> wrote:
https://support.google.com/chromebook/answer/148695?hl=en https://support.google.com/chromebook/answer/148695?hl=en
—
Reply to this email directly, view it on GitHub https://github.com/hungryweb/apple-macos-dark-mode/issues/1#issuecomment-1596562792, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4S27EXA6DWE4X5I6Z6EOLXL7UADANCNFSM6AAAAAAZLNHDSI.
You are receiving this because you commented.


Fix inconsistent doc formatting and wording in Maven Archetype page

Formatting on this page was a bit stuffed. I tried to make it consistent with formatting in the component docs.

Btw [line-through] is deprecated (and not rendering anyway). Is there a global role I should be applying instead?

Thanks @sohrab-


Compatibility with django >= 2.1

Django 2.1 removed the 'host' parameter from is_safe_url(), 'allowed_hosts' now is a required argument.
As stated here https://github.com/django/django/pull/9938 in Django 2.1 the TOKEN_* constants were replaced by TokenType enums.

One thing more: I'm afraid i did't respect python2 compatibility for the inspect.getfullargspec call. Will add that...

Yay!
Though some of the commits rather look like spam and probably should be removed (just squash them away).
Together with https://github.com/stephenmcd/mezzanine/pull/1916 we should get a big step toward Django 2.2 support.

Just noticed: https://github.com/fermorltd/mezzanine/commit/f6da0a2219fa4d1b7bce4cac4e47d864dab08844 is also necessary.

#1956 has been merged with support for Django >= 2.2


Can't start Jupyter server

VS Code Version:
Version: 1.56.0 (user setup)
Commit: cfa2e218100323074ac1948c885448fdf4de2a7f
Date: 2021-05-04T22:09:06.405Z
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.18363
OS Version:
Windows 10
Steps to Reproduce:

1."ctrl+shift+p".
2.type in "Jupyter: Select interpreter for Jupyter server"
Get below error:
Error loading webview: Error: Could not register service workers: TypeError: Failed to register a ServiceWorker for scope ('vscode-webview://c8dd3ae1-1477-42c7-a2cc-daed406c5969/') with script ('vscode-webview://c8dd3ae1-1477-42c7-a2cc-daed406c5969/service-worker.js?platform=electron&id=c8dd3ae1-1477-42c7-a2cc-daed406c5969&vscode-resource-origin=https%3A%2F%2Fc8dd3ae1-1477-42c7-a2cc-daed406c5969.vscode-webview-test.com'): ServiceWorker cannot be started.

Does this issue occur when all extensions are disabled?: Not applicable

/extPython

Actually duplicate of  https://github.com/microsoft/vscode/issues/122951 based on the error

Thank you for reference.


Fix missing SSE detection on x64 targets. Fixes #25

One important note on this PR: with this change, matrix_benchmarks takes twice as long to run on my test system with SIMD enabled as it does with SIMD disabled. That seems... unintuitive. And worth investigating further.

Re the CLA: I'm a Google employee. I just registered my GitHub account, though, so approval may still be processing.

To be precise: It takes twice as long to run for x64, and we don't know how much slower it was before, since on x64 it wasn't using SIMD at all, right?
This change seems otherwise ok to me, it is not like anything in this PR is causing a slowdown by itself, so I think it should go in. Finding out the slowdown is a separate issue.


feat: Set snappy as the compression type for Inference Logger

What this PR does / why we need it:

Without enabling compression, the Kafka log messages may be large. This PR enables snappy compression by default. In the future, if a need arises, the Compression Type could be made configurable.
Does this PR introduce a user-facing change?:

Enable compression of Kafka inference logging messages.

Checklist

[ ] Added unit test, integration, and/or e2e tests
[ ] Tested locally
[ ] Updated documentation
[ ] Update Swagger spec if the PR introduce API changes
[ ] Regenerated Golang and Python client if the PR introduce API changes

Thanks for the quick review @deadlycoconuts !


Clicking on whitespace in a graph to move it around deselects all selected items

Clicking on whitespace is necessary for moving the entire graph around.
However, a click on whitespace also results in undoing all selections.
So currently it is impossible to move the graph while keeping your selections intact.

This is the expected behaviour, you can move the graph keeping the selection by using the pan-zoom controller at the top left in the graph widget area.
Btw, we can keep in consideration your suggestion, maybe allowing users to lock/unlock the current selection.


Create wiki page about data formats

Since we are stablishing an unique data format, it no longer makes sense @jorgeyp . Closing!


Fix wrapping of exception alias patterns, issue 940

Fix for https://github.com/facebook/reason/issues/940
The wrapping around Ppat_exception's pattern with aliases was non-existent before.
What I did was parameterizing method pattern to add a wrapping whenever a Ppat_exception occured with an alias.

Comments & suggestions are integrated

Looks perfect, thanks @IwanKaramazow!

Thanks again, @IwanKaramazow !


demo does not work on osx 10.11 &  chrome v51

Cannot create RTCPeerConnection; WebRTC is not supported by this browser.

Try to use Chrome or Firefox instead of Safari.

i am using osx 10.11 & chrome v51

I can confirm that it not works with chrome version: 54.0.2840.98.

Doesn't works with Chrome version 55.0.2883.87

"WebRTC is not supported by this browser"
Chrome 56.0.2924.87
Windows 10

Tested with Google Chrome Version 67.0.3396.99 (Official Build) (64-bit) & Google Chrome Version 68.0.3440.75 (Official Build) (64-bit) Does not work with both

I've made some updates and it should be works on Chrome, Firefox, and Safari.
Please pull updates.

I working now, I think issue must closed now. I hope this will be maintained now regularly 👍


update set-owamailboxpolicy

remove the ambiguity in the description of the ReportJunkEmailEnabled parameter.

Docs Build status updates of commit 4e3619c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/client-access/Set-OwaMailboxPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

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

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

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/client-access/Set-OwaMailboxPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

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

Docs Build status updates of commit 07e0ef3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/client-access/Set-OwaMailboxPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

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


[Request] Custom TTL (Or 10m/2h/6h/12h option)

Hi,
The TTL of 1m/5m/15m/30m/60m/24h is almost perfect for 99%
But between 1h and 24h there is a big gap xD
Ans a 10m option would be nice too :-)
Or maybe an setting for custimze that time ranges. But thats not important, just a nice to have :-)
And still looking forward for the PTR Tab xD
because IPv6 entrys makes the whole dashboard ugly :-)
Cheers :-)

Sure. The actual values are already really good, but at least little bit custumization would be much better :-)
Seems like ngoduykhanh has no time atm :-)
However maybe we need to dig into the code and make some pull requests...
Cheers :-)


Documenting Application Cloudflare Access Token duration

Which Cloudflare product does this pertain to?
Zero Trust
Existing documentation URL(s)
https://developers.cloudflare.com/cloudflare-one/tutorials/cli/#using-the-token-as-an-environment-variable
What changes are you suggesting?
Let's add the lifetime of application tokens generated by cloudflared access token (e.g. 12-hrs, 24-hrs, infinite)
Additional information
No response

We can link to the token duration documentation: https://developers.cloudflare.com/cloudflare-one/identity/users/session-management/#session-duration

Yeah that would be great!  Also clarifying if cloudflared access token makes a global session token or application token in https://developers.cloudflare.com/cloudflare-one/tutorials/cli/#token


Bump BouncyCastle to 1.62

also introduce 'boucnyCastleVersion' in version.gradle.

Pull Request Test Coverage Report for Build 63

0 of 0   changed or added relevant lines in 0 files are covered.
7 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.5%) to 55.727%

Files with Coverage Reduction
New Missed Lines
%

pgpainless-core/src/main/java/org/pgpainless/util/KeyRingSubKeyFix.java
7
64.29%

Totals

Change from base Build 61:
-0.5%

Covered Lines:
832

Relevant Lines:
1493

💛  - Coveralls


how to use nested scene?

Version
Tell us which versions you are using:
"react-native-router-flux": "3.31.1",

react-native-router-flux v3.?.?

react-native v0.?.?
"react": "15.2.1",
"react-native": "0.30.0",

Expected behaviour
Go to nested scene2 without error
Actual behaviour
I go to the scene1 by clicking the scene1 tab at the bottom of the screen, then red screen shows with error as below:
ExceptionsManager.js:61 Objects are not valid as a React child (found: object with keys {key, name, sceneKey, parent, type, children, index, sceneStyle}). If you meant to render a collection of children, use an array instead or wrap the object using createFragment(object) from the React add-ons. Check the render method of View.
my router config:
router_config.txt
ps: I want the sub-scenes share the same parent scene.

Also seeing this behaviour. Example:
<Scene key='apply' component={ApplyWrapper}>
  <Scene key='address' component={Address} />
  <Scene key='mobile' component={Mobile} />
</Scene>

I think reason for the error is that ApplyWrapper is being passed the scene objects as children and doesn't know what to do with them.

Is my error related to this issue too?
See here:
https://github.com/aksonov/react-native-router-flux/issues/1589
The interesting part is that it works once I open the Chrome (V8) debugger. What is different there?

Desired the same functionality with my scenes as:
export default (
  <Scene key="root" hideNavBar={true} component={Layout}>
    <Scene key="login" component={Login} />
  </Scene>
);

Solution provided by Colin works with the following versions:
    "react": "~15.4.0-rc.4",
    "react-native": "0.40.0",
    "react-native-router-flux": "~3.37.0",

As an aside; Out of interest @afilp - what i18n library are you using within your React app?

As an update; I took a peek under the hood, and I saw DefaultRenderer being used by the Modal component etc, and it's exposed by react-native-router-flux. I was able to provide my wrapping Layout as:
import React, { Component } from 'react';
import { Text, View } from 'react-native';
import { DefaultRenderer } from 'react-native-router-flux';

class Layout extends Component {
  constructor(props) {
    super(props)
  }

  render() {
    const children = this.props.navigationState.children;
    const state = children[0];

    return (
      <View>
        <Text>Parent Layout</Text>
        <DefaultRenderer
          navigationState={state}
          key={state.key}
          {...state}
          onNavigate={this.props.onNavigate}
        />
      </View>
    )
  }
}

export default Layout;

I'm not sure if this is the intent of DefaultRenderer, however it is an alternative solution to @colinramsay's answer

I implemented it as you suggested @AlanFoster, but none of my TouchableHighlights work anymore. If I remove the Layout on my root scene, it all works.  Any idea where to look?

@AlanFoster I do not use any 'i18n library' (at least not explicitly, could a dependency do this?)

@AlanFoster Is this error related to issue #1589 ? Why does it work with certain settings? (Hot reloading AND Debug JS on?)

@AlanFoster

I do not use any 'i18n library' (at least not explicitly, could a dependency may do this? Does it matter somehow?)

Is this error related to issue #1589 ? Why does it work with certain settings? (Hot reloading AND Debug JS on?)

I found something new.
I changed
import 'babel-polyfill';
TO:
require('babel-polyfill');
and now it works!
I wonder why (and why the problem was only on Android, not iOS).
The above statement is the 1st one on Main.js component, even above the React and React Native imports.

I had the same problem withe nested Scenes and solution of colinramsay worked for me as well:
 <Provider store={store}>
        <Router>
            <Scene key="root" component={App}>
                <Scene key="search" component={Search} />
                <Scene key="common" component={Info} />
            </Scene>
        </Router>
    </Provider>

that means (in my case) using:
{this.props.children.map(scene => React.createElement(scene.component))}
instead of:
{this.props.children}
in {App}.
I think it would be a good idea to mention this workaround in the docs as nested layouts are very common (drawers, sidebars...). E.g. i use it with react-elements sidebar.

@axlider Did you have any trouble accessing the passed props in your children scenes? When I map them like you suggest, I lose access to them.

no trouble. The nested components look like this:
 <SideMenu
                isOpen={true}
                menu={MenuComponent}>
                <ScrollView
                    toggleSideMenu={false}
                >
                {this.props.children.map(scene => React.createElement(scene.component))}
                </ScrollView>
 </SideMenu>

But this is just what i can say about my initial view. I didn't try out any dynamic navigation yet.

So I've tried out nested scenes using the workarounds mentioned here, but I wouldn't recommend it, since it seems to break scene transition animations.

How does it look like in your case (breaking scene transition animations)?
When i open close the drawer in my nested sidebar example i cannot observe anything suspicous.

@axlider All of my transitions were were rendering like REPLACE transitions.

@petermikitsh
Aha. i do the same, but works fine.

@colinramsay

@leonardgithub having the same issue. Did you find a way to resolve to get the props passed on the Action call?

@leonardgithub @donovantc have you looked at the data prop from your scene?


Fix sample data clashing lessons bug

Codecov Report

Merging #281 (27ee4b5) into master (23f81e1) will not change coverage.
The diff coverage is 0.00%.

@@            Coverage Diff            @@
##             master     #281   +/-   ##
=========================================
  Coverage     68.16%   68.16%
  Complexity     1085     1085
=========================================
  Files           136      136
  Lines          3769     3769
  Branches        506      506
=========================================
  Hits           2569     2569
  Misses          979      979
  Partials        221      221

Impacted Files
Coverage Δ

.../java/seedu/address/model/util/SampleDataUtil.java
36.53% <0.00%> (ø)

Continue to review full report at Codecov.

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


continuous data compliance finsihed

Compliance tests added for continuous sequence annotations service (ga4gh/schemas#769).

Ran this against https://github.com/ga4gh/server/pull/1573/commits/be8cec1b9766621b3f80560e079295c67b796c59 and got:
[TESTLOG] Overall: Tests run: 148, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 72.181 sec

Looks good!


.withComponent(Link) 'Unknown prop'

When changing a styled components element using withComponent with Link from react-router-dom causes errors in react.
Version
2.1.1
Reproduction
https://www.webpackbin.com/bins/-KoDDes4XCRS2-VxAroy
(Look in console - not the log in webpackbin)
Steps to reproduce
Create Styled component, change element to Link using withComponent
Expected Behavior
Props not to be passed to html element
Actual Behavior
Props are passed to html element
Warning: Unknown prop 'primary' on <a> tag. Remove this prop from the element. For details, see https://fb.me/react-unknown-prop     in a (created by Link)     in Link (created by Styled(Link))     in Styled(Link) (created by Buttons)

That's because we are only filtering props for HTML elements and not for React components.

Thanks for clearing that up for me.
I thought this might be an issue with react-router's Link component...
Is there any workaround for this? I'd like to be able to have props on styled components using Link.
Since this isn't really an issue, I'll close this.

Is there any workaround for this? I'd like to be able to have props on styled components using Link.

Unfortunately to get rid of it, you'll have to filter the props yourself by wrapping Link. This will be solved eventually, if/once React introduces prop namespaces. You can also just ignore the warning, since it's safe to render unknown props.


Growth stage might still be better represented in schema as {"min": xx, "max": yy}

Arrays of fixed size are not self-describing.


Raises error if house number is non-numeric

Sometimes, a user may accidentally enter a non-numeric house number. If there is no house_number_addition, this causes an error in ApiPostcodeNl::API.address, line 71:
TypeError: wrong argument type nil (expected Regexp).

Hi mvz,
Feel free to submit a PR for this. This gem is not actively maintained anymore, but I'd appreciate any and all contributions.
Cheers,
Ruben

Fixed in #2.


Update password reset/change error messages

https://trello.com/c/ITSfGrTU/126-1-review-error-message-content-in-user-frontend
This will need a separate PR to remove the duplicate scenarios for staging, once we're ready to deploy. One of the scenarios (logged in admin user) isn't run on staging anyway, because we don't want to send a 'real' password change email for those accounts.

Thanks @gidsg - let's give it a go.


Key Vault secret expiration policy stops provisioning of ADE

There is a built-in Azure Policy definition called Key Vault secrets should have an expiration date (see Key Vault policy reference link) that conflicts with enabling Azure Disk Encryption. If the Key Vault secret expiration policy is assigned and set to the "Deny" effect then this policy will prevent the ADE extension from being successfully installed and a fault reason of "RUNTIME_E_KEYVAULT_SET_SECRET_FAILED" will appear under the Virtual Machine's Deployment blade. The workaround or solution to this issue is 1) set the policy effect to Audit or Disable, or 2) Create an exemption on Azure policy at the proper scope level e.g. Subscription or Resource Group. This information would be included under the troubleshooting page.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 29bf0357-bbeb-78c4-e1f5-7151934eb870
Version Independent ID: 9a3b2c47-6d8c-3bb5-60f2-4bf0d3dac710
Content: Azure Disk Encryption troubleshooting guide - Azure Virtual Machines
Content Source: articles/virtual-machines/windows/disk-encryption-troubleshooting.md
Service: virtual-machines
Sub-service: disks
GitHub Login: @msmbaldwin
Microsoft Alias: mbaldwin

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

Is there any new update on this request or issue? Will the public doc be updated with this scenario and mitigation steps?

Would like to have an update on this as well.
This policy is part of CIS compliance package.
The policy is non-compliant because the disk encryption keys are automatically generated without an expiry date.
Plus, having expiry date on disk encryption... I would not recommend this in general.
This policy needs to be updated to exclude BEK and other disk encryption labels.

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. If you are still experiencing a problem, you might want to move this question to Microsoft Q&A: https://learn.microsoft.com/en-us/answers/tags/94/azure-virtual-machines.  #please-close


Investigate main event loop logic

this part of a canonical kernel event loop:
if next_turn.expired == 0 || !tick.has_remaining {

seems to always evaluate to true - at least in the pomelo simulator.

This is working as intended --- it's a result of there not being very many tasks running on the kernel.
tick.has_remaining() will only ever be true if more than 256 tasks were woken since the last tick: https://github.com/hawkw/mycelium/blob/a06e352494ca83cddf541c61a06a898f4c4e356c/maitake/src/scheduler.rs#L837
next_turn.expired would be greater than 0 if the timer wheel turn woke any tasks. but if we are (almost) always woken by a timer interrupt, and we advance the timer immediately after the timer interrupt fires, those tasks have already been woken. we might see the second turn of the timer wheel (after ticking the scheduler) also wake tasks if the scheduler tick took longer than it does currently (e.g. there are more tasks running, or some tasks took a very long time to execute). but, our tick durations are currently very short, so it's extremely unlikely that any new timeouts would have completed since the last turn of the timer wheel.
This if condition is intended so that the kernel only goes to sleep and waits for an interrupt if there is no ready work remaining after the scheduler tick. Since the kernel isn't running very many tasks and we can poll all woken tasks in a single scheduler tick, we pretty much never need to continue ticking and can go ahead and wait for an interrupt, which is the correct behavior here. This might not be in the case in the future, if significantly more tasks are running on the scheduler. In that case, we might occasionally need to keep ticking until all the ready tasks have been polled, before going to sleep.

Maybe we should add a longer comment in the source explaining this...


How to develop and debug WecHaty locally

I did it in the following steps:
1、download wechaty and wechaty-puppet-padplus from github
2、remove [devDependencies.wechaty-puppet] and [peerDependencies.wechaty-puppety] in   package.json of wechaty-puppet-padplus
3、cd wechaty-puppet-padplus && npm install
4、cd wechaty && npm install
5、ts-node index.ts
then error:

my index.ts:

The term wechaty-puppet in wechaty differs from the version in the ipadplus
Thanks for your help:)

From my personal experience, here is what I usually do:

Clone wechaty, wechaty-puppet and wechaty-puppet-x(any puppet that you are trying to develop)
Do npm install in each project folder
Do npm run dist in each project folder
Do npm link in wechaty-puppet
Do npm link wechaty-puppet in wechaty and wechaty-puppet-x
Do npm run dist in wechaty and wechaty-puppet-x
Do npm link in wechaty and wechaty-puppet-x
Create a index.ts file in another folder to do test, with some test code in it.
Do npm link wechaty and npm link wechaty-puppet-x in the folder that has index.ts
Do ts-node index.ts

Then the error should be gone.
The main reason that you see that error is that wechaty and wechaty-puppet-x are not using wechaty-puppet from the same folder and same file. To solve this, I came up with the solution above, which will link the wechaty-puppet from local folder. This works for me, you could give it a try.
Let me know if you still having issue with this, and also let me know if you came up with better solution for this issue.

Related to https://github.com/wechaty/wechaty/issues/1930

This problem should be fixed with the latest code with the Wechaty version above v0.50.7.
Please let me know if it still has any problem, thank you very much!

Merge to #1930


Reorder execution of setup.sh

We noticed one problem with the installation order.
Assuming a clean ubuntu install, the repo's setup.sh script is executed after cloning, when ROS is not yet installed.
If we want to use the setup.sh script to install robot specific packages (primarly ROS packages) this is not going to work. Is there a way to reorder the install steps such that the script is executed after ros is installed?

That was already fixed a couple of weeks ago


Update EventSub to match latest live EventSub documentation (November '22)

Currently the following are out of sync
channel.ban
.event.banned_at (Missing from CLI)
channel.channel_points_custom_reward.add
.event.redemptions_redeemed_current_stream (Set to 0 in CLI, null in docs)
drop.entitlement.grant
.subscription.category_id (Missing from CLI)
.subscription.campaign_id (Missing from CLI)
.subscription.cost (Exists in CLI, doesn't exist in docs)
extension.bits_transaction.create
.subscription.cost (Set to 1 in CLI, 0 in docs)
.event.product.in_development (Set to true in CLI, false in docs)
channel.goal.begin / .progress
.event.ended_at (Given by CLI; Uses same logic as channel.goal.end so this appears when it shouldn't)
.event.is_achieved (Given by CLI; Uses same logic as channel.goal.end so this appears when it shouldn't)
channel.hype_train.begin / .progress / .end
.event.level (Missing from CLI; Reported in #190)
channel.prediction.begin / .progress / .lock
.event.outcomes.users (Consistent in CLI, inconsistent in doc. Is this optional?)
user.update
.event.email (Missing from CLI)
.event.email_verified (Missing from CLI)
The following are missing from the CLI
channel.charity_campaign.donate
Relevant links
https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types

user.update is also not in the same format as the rest of the CLI. It should be updated to user-update.
This wont make any breaking changes, as the EventSub event name always works anyway.

On channel.channel_points_custom_reward.add, the field should_redemptions_skip_request_queue sometimes doesn't exist (when tested in production).
This needs further investigation.


Add Open Telemetry

Purpose
Python is not configured to use the Open Telemetry library so I believe that this is the reason we are not seeing anything in Application Insights.
Fixes #547
TODO: Testing in the cloud.
Does this introduce a breaking change?
[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

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

How to Test
Do we start to see things in Application Insights!

Surprising how the coverage percentage dropped by 15%

Surprising how the coverage percentage dropped by 15%

Because the tests failed :-)


immich.machine-learning: drop packageOverrides argument

Description of changes
There is no need for it and it cannot be used to override the machine learning component used by the immich package.

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I just copied this from home assistant: https://github.com/NixOS/nixpkgs/blob/9357f4f23713673f310988025d9dc261c20e70c6/pkgs/servers/home-assistant/default.nix#L23
I don't really care either way

I just copied this from home assistant

I figured. There it's useful because custom components might require overrides. But that's not a thing for immich..


Don't mount files from /tmp/ directories

Currently we mount volumes (files) that are created and live in /tmp/ which are obviously ephemeral and could be erased at any time, don't do this:
https://github.com/bitcoin-dev-project/warnet/blob/9888538716f262b1441fb0751a83dfe380f67846/src/warnet/warnet.py#L119-L128
(I am in the process of adding a second like this, fork-observer)

oh dang I thought we were copying files into the containers

volumes is a mount. Also I think a config dir makes more sense anyhow, then we can use docker-compose down to stop (proper way?), and also give people easy access to their docker-compose.yaml, bitcoin core config files etc


fetch_robots: 0.8.3-0 in 'melodic/distribution.yaml' [bloom]

Sorry for yet another PR.
I've ran the prerelease jobs, and the pass. When trying to run the binary release job locally with 0.8.3, it still seemed to build version 0.8.2, so I think I wasn't setting up rosdistro correctly.
If this doesn't work, I'll ask @jacobperron to give me a tutorial in running the binary release jobs locally when he's home next week.
The source of all these 0.8.0, 0.8.1, 0.8.3 releases is trying to release a pre-combiled binary version of our drivers on the public build farm. https://github.com/fetchrobotics/fetch_robots/pull/27... we knew we were going to get into a bit of a mess at the beginning, hopefully it stabilizes.
Our pre-compiled binary is generated inside of docker and only targets intel / amd64.
So there is another open PR to blacklist the arm versions of our packages. https://github.com/ros-infrastructure/ros_buildfarm_config/pull/125

@dirk-thomas the doughnuts in the kitchen now have no strings attached... Just a two merge requests (this and ros-infrastructure/ros_buildfarm_config#125).
Sorry @clalancette doughnuts are in MV.
I wasn't able to pre-test the binary build job this morning, but reviewed it with @jacobperron and it should pass this time, otherwise I'll setup a mock build farm tonight.
As recommended this morning, I'll put it on our to-do list to move the tarball from http://packages.fetchrobotics.com/binaries/ to inside the git package for future releases.

otherwise I'll setup a mock build farm tonight.

You don't have to spin up a complete buildfarm. You can run every job type locally (the actual build will happen in Docker): e.g. https://github.com/ros-infrastructure/ros_buildfarm/blob/master/doc/jobs/release_jobs.rst#run-the-release-job-locally / https://github.com/ros-infrastructure/ros_buildfarm/blob/master/doc/jobs/devel_jobs.rst#run-the-devel-job-locally

I'll put it on our to-do list to move the tarball from http://packages.fetchrobotics.com/binaries/ to inside the git package for future releases.

I just wanted to mention it as good practice but you don't have to spend time on that in the near future. There is currently no plan to cut network access during the builds on the farm.

it should pass this time

Merging...:crossed_fingers: :wink:

Thanks!

otherwise I'll setup a mock build farm tonight.

You don't have to spin up a complete buildfarm. You can run every job type locally (the actual build will happen in Docker): e.g. https://github.com/ros-infrastructure/ros_buildfarm/blob/master/doc/jobs/release_jobs.rst#run-the-release-job-locally / https://github.com/ros-infrastructure/ros_buildfarm/blob/master/doc/jobs/devel_jobs.rst#run-the-devel-job-locally

Yes, I had followed most of those instructions but I think I missed this step:
https://github.com/ros-infrastructure/ros_buildfarm/blob/master/doc/custom_rosdistro.rst#update-reference-to-custom-cache

Passed. <3 Thanks everybody
http://build.ros.org/job/Mbin_uB64__fetch_drivers__ubuntu_bionic_amd64__binary/


Problem on function HTML documentation

At the web site in which there is the documentation (https://inilabs.github.io/libcaer/index.html)
some functions, like "caerDynapseWriteSramWords" function (on dynapse.h), are not included in the global function list, here:
https://inilabs.github.io/libcaer/globals_func.html
That happens also for other functions, mostly on dynapse.h. I noticed that this functions (that are not present in the global list) have also no documentation.

The documentation has been completed and fixed in the current Git include files. The inilabs.github.io site is only regenerated automatically on new releases, so when we release 2.4.0 it will automatically fix that.
If you need current documentation you can access it locally in docs/html/ and update it with 'make doc' (doxygen must be installed for it to work).


Git push does not ask for passphrase

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.65.2 (user setup)
OS Version:Windows_NT x64 10.0.22000

Steps to Reproduce:

using a ssh remote address for your repo
git commit using SDM in vscode
click Sync Changes button in the SDM window
finding no passphrase asked and cannot push, the icon keeping spinning.

I find the solution, you have to add openssh in your PATH


WIP 317 Add a date filter element

Addresses #317
@NealHumphrey
I've gone with a noUISlider element for controlling the date filter. This is to allow the user to set a rough date quickly and get a broad sense of which subsidies start/end when. I'm also thinking about adding an 'enter precise dates' link below the slider that swaps the slider for a set of text inputs (for month, day and year for min and max values).
In order to compare the dates of different 'items' in dataCollection.filterData, the code iterates through 'items', takes all the values of properties corresponding to 'date' components, and replaces them with JavaScript Date objects.
Currently the filtering is broken: While the date slider sets the app state with new Date values successfully, this doesn't yet do any actual filtering. We can check whether the units that are displayed by default have 'null' poa_start or poa_end values -- that might be one cause. Another could be the operation used to compare values of the filter element with values of the data. While comparison operators work with JS Date objects, I'm not sure if this is what's being used.
A side note: I've changed the file name of one of the images in the 'assets' folder. This is because the length of the name was preventing the Jekyll web server from running on my laptop. I'm pretty sure my use of OneDrive and Windows 10 is to blame, given OneDrive's restrictions on filenames.

@ptgott Sounds like a good start.
First off - this is my fault for not realizing the conflict when I suggested this task. You should make this branch off of the 'demo-v2-options-combined' branch instead of dev. On Thursday we decided to go ahead with this approach; since this merges the layer+filter functionality, there are some refactored changes to how these work (mostly one universal function for adding title text/formatting to the title of each filter control). It's probably easier to make a new branch and move your changes manually rather than trying to rebase or use git merges.
Whenever you're going to do work on this let me know - I'm planning to finalize the changes in demo-v2 today+tomorrow so that it can be merged into dev, which will also involve a bit of refactoring of how functions are organized between the filterView and mapView docs currently - hopefully I can get that done before you're ready to move the code over to be on top of demo-v2, which would be cleanest, but if you want to do any work on it before I'm done just let me know so I can make sure not to do anything that will interfere.
As you decide how to finalize this, we should think about how it overlaps with the other noUiSlider as well. In particular, as you observe we definitely want a way to type in the specific min/max for both dates and continuous values. We saw this in user testing - while users liked the sliders for rough use as you said, eventually everyone realized they also wanted precision.
I think the most useful way to do this might be to have min and max form fields below the slider. We could eliminate the slider tooltip box and instead have the slider update the value of the form field if the user moves the slider. Similarly, when the user changes the typed in value the slider could update (there's already code to do this when clearing filters) - probably triggered on the onfocusout event.
On a related note, what do you think about maybe having the slider change one year at a time when you drag it? It could always be set to 1/1/YYYY.  That might make the slider more useful - if you want to just set it based on the year, you could just drag, as opposed to dragging and then realizing you still need to set the specific date.
On your question about filtering not working, this is because the file /utils/filter.js has this code in it for handling dates:
if (component['component_type']== 'date') {
    //TODO determine whether dates will always be published as [start, end], or, if
    // not, in what format
}

@NealHumphrey The most recent set of commits merges the dev branch (as of today) into this topic branch, then gets the date filter component to modify the displayed project dots. The next step will be to change the component per your suggestions.

@ptgott I put most of my suggested comments (re: removing tooltips etc.) into the issue #395 . This one describes the specific changes related to continuous filters but since you're using the same slider and approach for date picker I think we want to make all the same changes and then just swap out the input box for a datepicker box.  Assuming you're going to do those next as you say, you should probably just claim issue #395 and do at all in one swoop.
Regarding the suggestion for the slider just moving year by year, I saw that noUiSlider has a 'steps' option - that might be the easiest way to cleanly implement this!
Maybe also implement steps for integer-type continuous sliders so they end up with clean integer numbers? Currently we're doing rounding on the front end and on the tooltip, disguising the fact that the user may have technically selected a decimal value, but actually storing the integer by forcing the user to select an integer via slider would also clean up the encoding of state in the url that we will be doing.

@NealHumphrey I've merged the most up-to-date dev branch into this PR and tweaked the Date slider to select only years.
Since the larger tweaks left to do to the Date filters also apply to other continuous filter components, shall we merge this (if it's working on your end) and devote the work in #395 to additional PRs?

@ptgott  I agree on pushing the other stuff into future PRs and merging this post testing. Unfortunately can't do it right now though, I'll circle back to it tonight. I'm putting one note of a change to make that I saw in a quick skim of the code though.


When i go to the GMImagePickerController

when am selecting image you are showning the "1 photo selected" or some thing in the toolbartitle
so what i want is we have to show the selected image and make them add
is this possible with this sdk
Thanks for the Good sample

Sorry, i do not understand you. You mean you want to show selected images in the toolbar?
This is not supported but you can customize it by digging in the code and modifying it to your needs. I doubt you will find any library support such a specific think so probably you are going to need to implement it by youself.

Yaa the same i want
Okay i will try
ᐧ
On Thu, Oct 29, 2015 at 1:27 PM, Guillermo Muntaner <
<EMAIL_ADDRESS>wrote:

Sorry, i do not understand you. You mean you want to show selected images
in the toolbar?
This is not supported but you can customize it by digging in the code and
modifying it to your needs. I doubt you will find any library support such
a specific think so probably you are going to need to implement it by
youself.
—
Reply to this email directly or view it on GitHub
https://github.com/guillermomuntaner/GMImagePicker/issues/29#issuecomment-152106565
.


Typehint DateTimeInterface for serializeDate() in Eloquent Model

Hi, I'm using 5.2 and want to replace Carbon with Chronos. So far I can extend the base Illuminate\Database\Eloquent\Model to make the idea work. But then serializeDate() typehints the concrete class DateTime and therefore it's not possible to use Chronos instances.
I wonder if we could change
    protected function serializeDate(DateTime $date)

into
    protected function serializeDate(DateTimeInterface $date)

for better customization?

Feel free to send a PR to 5.3. ;)

Will do : )


Adding code of conduct

This is a dumb script to cheat a mini game, it doesn't need a CoC.

I'm implementing docker and writing some tests, please bare with me.

That's cool and all, but this script doesn't need either of these.


After monitoring with osx, changes could not be captured

Thank you for a wonderful package.
I confirmed that the file specified by src exists.
You can also start the server.
It seems that you can set the target with the dump option.
godo server -w -D -v --rebuild --dump
 root  =>
   Tasks:
     server
         EffectiveWatchGlobs []
         SrcFiles []
         SrcGlobs [*.go **/*.go]

Execution environment
MacBook Pro (Retina, 15-inch, Mid 2015)
Go 1.8

Excuse me.  It was a misunderstanding.  Close.

I am very sorry, it is not misunderstanding.


Added client documentation.

First step of the documentation (This is only the client side).
MqttClientExtensions is still missing, I will do this soon (if needed).
@chkr1011 What do you think of this? I have tried to only add documentation where I thought it was useful. Nevertheless, I have no idea if I got everything (or too much) 😄
Fixes https://github.com/chkr1011/MQTTnet/issues/1052.

Thank you for the update, I will check this and hopefully work on it tomorrow again :)

Thank you for the update, I will check this and hopefully work on it tomorrow again :)

@chkr1011 Does this look sufficient to you?

@chkr1011 Does this look sufficient to you?

@chkr1011 Did you have time to check this?

@chkr1011 Did you have time to check this?

@SeppPenner I am fine with that. These comments have a real value for the user and I will also add them to new properties etc. in the future 👍
Is there something to do or should I merge that state?

@SeppPenner I am fine with that. These comments have a real value for the user and I will also add them to new properties etc. in the future 👍
Is there something to do or should I merge that state?

@SeppPenner I am fine with that. These comments have a real value for the user and I will also add them to new properties etc. in the future 👍
Is there something to do or should I merge that state?

It can be merged :)

@SeppPenner I am fine with that. These comments have a real value for the user and I will also add them to new properties etc. in the future 👍
Is there something to do or should I merge that state?

It can be merged :)

@SeppPenner awsome. Thank you :)


Navmesh is not generated/updated sometimes

I noticed that the navmesh is sometimes not generated. Here is a screenshot:

I place red blocks on a green plane. In the screenshot above we see that the navmesh is constructed on top of the red box but the navmesh on the green plane is not updated.
The behavior is very inconsistent, because sometimes it is generated correctly. I also noticed, that blocks that are placed on two tiles sometimes generate/update the navmesh for only one tile:

Hmmm.
Could you share your NavMeshGeneration settings, plugin & bevy versions, etc?
This isn't much to go on at present.

Sorry for being so slow to come back to this.
My guess is that this has to do with your step_height being very high as this causes the nav-mesh to link points together.
I might be able to make some minor changes to improve this, but I would recommend looking over if 16 is the right step height for you.

Hi Grim,
tanks for your reply and support. I did some testing with the step_height. I reduced it to one, but that didn't help. Then I started to increase the step_height. It got a bit better when I reached 8, but there were still problems.
Now I increased the walkable_height to 40 (two times the character height) and now the problem is gone. I assume that the area IN the cube got identified as walkable and then it got combined sometimes with the walkable area outside the cube.
In another thread I red, that you plan to introduce negative volumes. Is this still on your roadmap?
Kind regards!

This should have been fixed by 0.5.2 a few days ago, please reopen if it is still an issue.


briefcase

Some work on this icon was already made in this issue https://github.com/primer/octicons-v2/issues/161

https://www.figma.com/file/2rjsQp42uKvzPXzLZIqOeA/Octicons-v2-Source?node-id=1109%3A3125

16px

24px

I was getting slight toolbox vibes and was playing around with these variations.

@edokoa what do you think about a little more curve?
cc @colebemis

Ooo I like the first one @ashygee ❤

I like them. I like the first and second most, but maybe the second gets lost in small sizes.

What about this 24px version?
https://www.figma.com/file/2rjsQp42uKvzPXzLZIqOeA/Octicons-v2-Source?node-id=1119%3A2122

Looks good to me 👍

I opened a PR to add this to Octicons: https://github.com/primer/octicons/pull/434
I'll merge when I have approvals from @ashygee and @edokoa


表单宽度异常

如图，ant-col {  width: 100%; } 去掉后，表单宽度出问题了

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days


variables and macros in link texts

variables and macros in links don't get converted to code, shows only the raw text aka. "Hi $name! How are you?". Something like "Hi "+ Vars.name + "! How are you?" would be expected

Hi, which story format are you using?

I'm using Harlowe 1.2.4

Could you please show me the context in which this is used? Is it within a
function call or directly in the passage text?
On Thu, Jun 29, 2017 at 10:13 AM Harald Lønmo<EMAIL_ADDRESS>wrote:

I'm using Harlowe 1.2.4
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/daterre/Cradle/issues/45#issuecomment-311882569, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABwejMrKqoIdB9Kdlh7bIKe1gnF4zx0Xks5sI06fgaJpZM4OIFNE
.

--
web: daterre.com http://daterre.com/
twitter:  @tonicwoods https://twitter.com/tonicwoods
http://www.lofipeople.com/

Here are some examples
Hi! How do you do? [[...->Intro02Response01]] [[Hi $name! It is going great, and you?->Intro02Response02]]
results in code:
yield return text("Hi! How do you do?"); yield return lineBreak(); yield return link("...", "Intro02Response01", null); yield return lineBreak(); yield return link("Hi $name! It is going great, and you?", "Intro02Response02", null); yield break;
and something like
[[...washing machine? Sorry, we dont sell that.->Intro02Response01]] [[...to the (either:"left","right") for the (either:"fish","drinks").->Intro01Response03]]
results in code
yield return link("...washing machine? Sorry, we dont sell that.", "Intro02Response01", null); yield return lineBreak(); yield return link("...to the (either:"left","right") for the (either:"fish","drinks").", "Intro01Response03", null); yield break;

Thanks, I'm going to test this and see what the Harlowe lexer outputs.

I can confirm that this is currently unsupported because Harlowe considers this a string and evaluates it dynamically - i.e. it doesn't parse this content until it is displayed:
"tokens": [
    {
        "text": "link-goto:",
        "type": "macroName"
    },
    {
        "innerText": "...to the (either:\\\"left\\\",\\\"right\\\") for the (either:\\\"fish\\\",\\\"drinks\\\").",
        "text": "\"...to the (either:\\\"left\\\",\\\"right\\\") for the (either:\\\"fish\\\",\\\"drinks\\\").\"",
        "type": "string"
    },
    {
        "text": ",",
        "type": "comma"
    },
    {
        "innerText": "Intro01Response03",
        "text": "\"Intro01Response03\"",
        "type": "string"
    }
]

Cradle uses Harlowe's lexer during import in the Unity editor and so doesn't support dynamic evaluation while the game is running. I'll consider adding some basic variable parsing support - but macros embedded in string will not be supported I'm afraid.

would it not be possible for the lexer to output something like:
yield return link("...to the " + macros1.either("left","right") + " for the " + macros1.either("fish","drinks") + ".", "Intro01Response03", null);  yield break;

It could if you write the link like this in Harlowe:
(link-goto:"...to the " + (either:"left","right") + " for the " + (either:"fish","drinks") + ".", "Intro01Response03")
Cradle sees it like this:
IStoryThread passage1_Main()
{
	yield return link("...to the " + macros1.either("left","right") + " for the " + macros1.either("fish","drinks") + ".", "Intro01Response03", null);
	yield return lineBreak();
	yield break;
}

That works :-) that method works with variables as well. I'll be using that method for now. Thanks allot for the support

My bad! It seems that the Harlowe importer assumed incorrectly that [[links]] are treated the same as (link-goto) by the lexer when they are in fact fully tokenized. I will fix this as soon as possible. The long-form syntax should work for now though. Thanks for your help in discovering this bug!


Add support for ALL_WORLDS config

I should note that this PR makes it possible to define one world type that is applied automatically to any world, regardless of the name

I should note that this PR makes it possible to define one world type that is applied automatically to any world, regardless of the name

How would this work with multiple OTG presets installed?

How would this work with multiple OTG presets installed?

The presets that match the world name are given precedence. And I'm so sorry for the massive formatting differences, my personal formatter appears to have messed with the files quite a bit.

The presets that match the world name are given precedence. And I'm so sorry for the massive formatting differences, my personal formatter appears to have messed with the files quite a bit.

Hi @TheGreatRambler , sorry for the late reply. Will merge this into PG85:1.12-v9-Spigot-Java-11, as that's not used by anyone else I think. Normally we'd implement features for both platforms and review what might change/break for existing presets before merging something like this. Unfortunately there are also so many formatting changes that I can't clearly see what's happened or what the intention is. We're currently developing for 1.16, so we don't expect to do any more updates for 1.12.2.


Add partition to README.md

Following PR #131, I'm suggesting also adding partition to README.md.

Great, thanks!


[Breaking] Input inside nodes are not editable

None of the input inside nodes get focus or are editable and makes the entire drawflow unworkable. Same is happening with Drawflow's Live Demo too (https://jerosoler.github.io/Drawflow/)
My guess is the inputs lose focus as soon as they are clicked. However, apart from onclick event, no other event gets triggered: onfocus, onfocusin, onfocusout.

The problem is on last version 0.0.57
Try version 0.0.56.
I look to fix it.

Hello @jerosoler ,
When do you think that you'll release the 0.0.58v ? Maybe we should use 0.56v while.
Thanks and thank you for the project!


"Listen" in textMessageMenu doesn't work | iOS Version: 16.3.1 Model Name: iPhone 14

[Solved | I'm not sure how]
Environment:
iOS Version: 16.3.1
Model Name: iPhone 14
"Listen" in textMessageMenu doesn't work. Nothing happens.

You probably had the device in silent mode.


Allow BlockLength to add padding before repeating groups

From the SBE spec RC2:

In order to force messages or groups to align on byte boundaries or map to an existing data
structure, they may optionally be specified to occupy a certain space with a blockLength
attribute in the message schema. The extra space is padded at the end of the message or
group. If specified, blockLength must be greater than or equal to the sum of the sizes of
all fields in the message or group.
The blockLength attribute applies only to the portion of message that contains fix-length
fields; it does not apply to variable-length data elements of a message.
Extra octets specified for padding should be filled with binary zeros.

As far as I can tell, the OTF decoder currently does not respect messages with a BlockLength greater than the sum of the lengths of the fixed-length fields. This causes problems with CME's MDP feed.

The Java OTF decoder honours the block length.


Four consecutive seeds give the same RNG when using pcg64_fast or pcg32_fast

Four consecutive seeds give identical random numbers for the pcg64_fast or pcg32_fast generators. For example pcg64_fast(0),  pcg64_fast(1),  pcg64_fast(2), and  pcg64_fast(3) return identical states and thus identical random numbers.
See output of my test script (example.zip):
checking seed 0 to 9 using pcg32_fast..
	0	0<PHONE_NUMBER><PHONE_NUMBER>
	1	0<PHONE_NUMBER><PHONE_NUMBER>
	2	0<PHONE_NUMBER><PHONE_NUMBER>
	3	0<PHONE_NUMBER><PHONE_NUMBER>
	4	0	517360375<PHONE_NUMBER>
	5	0	517360375<PHONE_NUMBER>
	6	0	517360375<PHONE_NUMBER>
	7	0	517360375<PHONE_NUMBER>
	8	0<PHONE_NUMBER>	231179071
	9	0<PHONE_NUMBER>	231179071
checking seed 0 to 9 using pcg64_fast..
	0<PHONE_NUMBER>24636832<PHONE_NUMBER>539479119<PHONE_NUMBER>661987954
	1<PHONE_NUMBER>24636832<PHONE_NUMBER>539479119<PHONE_NUMBER>661987954
	2<PHONE_NUMBER>24636832<PHONE_NUMBER>539479119<PHONE_NUMBER>661987954
	3<PHONE_NUMBER>24636832<PHONE_NUMBER>539479119<PHONE_NUMBER>661987954
	4<PHONE_NUMBER>656324337<PHONE_NUMBER>533855969<PHONE_NUMBER>7466136655
	5<PHONE_NUMBER>656324337<PHONE_NUMBER>533855969<PHONE_NUMBER>7466136655
	6<PHONE_NUMBER>656324337<PHONE_NUMBER>533855969<PHONE_NUMBER>7466136655
	7<PHONE_NUMBER>656324337<PHONE_NUMBER>533855969<PHONE_NUMBER>7466136655
	8<PHONE_NUMBER>499390773<PHONE_NUMBER>069323010<PHONE_NUMBER>5254633783
	9<PHONE_NUMBER>499390773<PHONE_NUMBER>069323010<PHONE_NUMBER>5254633783
checking seed 0 to 9 using pcg32..
	0<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>
	1<PHONE_NUMBER><PHONE_NUMBER>	124312908
	2<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>
	3<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>
	4	78042152<PHONE_NUMBER>	598054463
	5	338748765<PHONE_NUMBER>	893179696
	6<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>
	7<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>
	8<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>
	9<PHONE_NUMBER>	298473608<PHONE_NUMBER>
checking seed 0 to 9 using pcg64..
	0<PHONE_NUMBER>0212977<PHONE_NUMBER>323000979<PHONE_NUMBER>0994476282
	1<PHONE_NUMBER>1062200314<PHONE_NUMBER>5107364105<PHONE_NUMBER>010881979
	2<PHONE_NUMBER>3767829887<PHONE_NUMBER>8563605758<PHONE_NUMBER>8879526868
	3<PHONE_NUMBER>009979848<PHONE_NUMBER>419763765<PHONE_NUMBER>6649002760
	4<PHONE_NUMBER>793293256<PHONE_NUMBER>7439189285<PHONE_NUMBER>824653137
	5<PHONE_NUMBER>2235852897<PHONE_NUMBER>430366615<PHONE_NUMBER>5512261919
	6<PHONE_NUMBER>1768679421<PHONE_NUMBER>820487750<PHONE_NUMBER>766610057
	7<PHONE_NUMBER>276969522<PHONE_NUMBER>2244286679<PHONE_NUMBER>017472731
	8<PHONE_NUMBER>143149122<PHONE_NUMBER>76085417<PHONE_NUMBER>157136437
	9<PHONE_NUMBER>077628350<PHONE_NUMBER>634521278<PHONE_NUMBER>037025941
It appears that that seed = 4*n+i for i in {0,1,2,3} gives identical results for a fixed n for the two fast variants. Additionally, the 32 bit fast variant seems to start at zero.
Checking whether the problem remains for higher seeds:
pcg64_fast: All checked generators are memory identical for fixed seed // 4
pcg32_fast: All checked generators are memory identical for fixed seed // 4

You are right!
A workaround solution is to add 4 instead of adding 1 when you increase the seed value.
Here are notes I made when I discovered this problem a while back.
//      When the stream model is no_stream, the constructor engine(seed)
//      overwrites the two low-order bits of seed, setting them both to
//      one. Thus, the two low-order bits are effectively discarded.
//      One surprising consequence is that adding 1 to a seed may not
//      change the seed used by PCG.
//
//      For example, suppose you are launching multiple threads, and
//      for whatever reason, have decided to use no_stream. As each
//      thread is launched, you add one to the seed used on the
//      previous thread. Whoops! Three out of every four engines
//      are using a duplicate seed that was already used before.
//
//      As an alternative, it may be better to discard the two high-
//      order bits when seeding is performed. Rather than
//
//         state = seed & 3;  // discard two low-order bits
//
//      consider using
//
//         state = (seed << 2) & 3;  // discard the two high-order bits
//
//      The biggest problem I see with this alternative occurs when
//      "toy" 8-bit engines are being used. Discarding any bits, be
//      they low-order or high, could be problematic, depending exactly
//      what the value of the seed is in the first place!
//
//      A second alternative would be to "hash" or "stir" or "condition"
//      the user-supplied seed BEFORE discarding any bits. If done
//      effectively, there might not be much difference between
//      discarding low-order bits and discarding high-order bits.
//
//      I favor the second alternative. Frankly, I never understood why
//      the seed in a no_stream was not "conditioned" in the first place.


Fix Linter complaining about being outdated

This PR aims to make the Linter lint our PR's :)

LGTM


Create hello-world.py

A Hello World File

We love contribution, but we suggest you try and submit more meaningful PRs by exploring any of our open issues. If you have any problem or need help, please join our Discord community: https://appwrite.io/discord and use the #maintainers channel.


IDVA6-938 expired invitations in people digitally authorised page

Link to Jira:
https://companieshouse.atlassian.net/browse/IDVA6-938
Changes:

Additional logic added to display associations with valid invitations

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found


Make tarball a generic argument.

Closes #249

Don't need this anymore as we aren't using shiplift

Don't need this anymore as we aren't using shiplift


File format not supported: danfojs-node

Describe the bug
Attempting to drop na's from a Series where first value is null and a "File format not supported message" returned.
To Reproduce
Run the following code:
new dfd.Series([null, 100, null, 200], { index: [0, 1, 2, 3] })
.dropna()
.print();
Node JS: v12.22.1
Expected behavior
Standard Print() without the 2 null entries.
Additional context
Error: File format not supported
at new NDframe (/Users/berniemac/Develop/projekt1/server/node_modules/danfojs-node/dist/core/generic.js:43:15)
at new Series (/Users/berniemac/Develop/projekt1/server/node_modules/danfojs-node/dist/core/series.js:39:7)
at /Users/berniemac/Develop/projekt1/server/src/expression/lib/math/function/statistics/max.js:62:11
at Array.forEach ()
at Function._maxHandler (/Users/berniemac/Develop/projekt1/server/src/expression/lib/math/function/statistics/max.js:59:21)
at /Users/berniemac/Develop/projekt1/server/node_modules/typed-function/typed-function.js:1108:43
at processTicksAndRejections (internal/process/task_queues.js:97:5)

Fixed in latest version v0.3.0


Question: [How to navigate to a new page using WinUI3 with C++ desktop app?]

Firstly I create a project using template "Blank App, Packaged(WinUI in Desktop)" in Visual Studio.
Then I changed code in MainWindow.xaml to a simple Frame:

And then I add a BlankPage and try to navigate to the BlankPage like this:
rootFrame().Navigate(xaml_typename());
And then visual studio give me error:
winrt\Windows.UI.Xaml.Interop.h(643,29): error C2338: T must be WinRT type.
I don't know how to do...

I think you want something like what this thread suggests: https://stackoverflow.com/questions/53688012/c-winrt-navigation-between-two-pages

so: rootFrame().Navigate(xaml_typename<BlankPage>());

rootFrame().Navigate(xaml_typename()); is exactly what I code...but same error.

rootFrame().Navigate(xaml_typename()); is exactly what I code...but same error.

You are passing the implementation type instead of the projection type. This issue occurs when you are inside the implementation namespace. Instead write the fully qualified type name eg: YourApp::YourPage instead of just YourPage


Slower compilation when using<EMAIL_ADDRESS>

Initially reported in https://github.com/angular/angular/issues/26674#issuecomment-443263655 by @sod

hm indeed, just updating ngtools gives me the slowdown. Also using angular 7.1 with old ngtools 7.0.7 is significantly faster.

versions
1st run
2nd run
3rd run
4th run
5th run

@angular 7.0.4, @ngtools 7.0.7
31s
15s
7s
5s
5s

@angular 7.0.4, @ngtools 7.1.0
29s
14.5s
15.5s
12s
12s

@angular 7.1.1, @ngtools 7.1.0
29s
13.5s
13.5s
15s
16s

@angular 7.1.1, @ngtools 7.0.7
28s
12.8s
7s
5s
4.2s

this is how the chart looks in the 4th run with 7.0.7

and this with 7.1.0

Seems like diagnostics runs even though that should run in a seperate process?

So I guess https://github.com/angular/angular-cli/pull/12824 caused this?

Just another data point here:

Angular
ngtools
1st
2nd
3rd

@angular 7.1.1
@ngtools 7.0.7
25317ms
5131ms
4316ms

@angular 7.1.1
@ngtools 7.1.0
36403ms
27959ms
27833ms

Hi, How can i downgrade @ngTools to 7.0.7?
Thanks

‘npm i<EMAIL_ADDRESS>

Was working a bit on this today and noticed that the results I took yesterday were of rebuilds without a vendor chunk, which great inflate total rebuild times.
To get more granular information I also used an internal profiling flag we have to see where time is spent in compilations.
The results I got were:

<EMAIL_ADDRESS>rebuilds took ~0.5s

i ｢wdm｣: Compiling...
TypeChecker._update: 0.173ms
AngularCompilerPlugin._createOrUpdateProgram.ts.createProgram: 8.969ms
AngularCompilerPlugin._findLazyRoutesInAst: 0.563ms
TypeChecker._createOrUpdateProgram.ts.createProgram: 14.826ms
TypeChecker.gatherDiagnostics.ts.getSyntacticDiagnostics: 0.269ms
AngularCompilerPlugin._emit.ts+D:/work/angular/aio/src/main.ts+.emit: 12.643ms
AngularCompilerPlugin._emit: 13.173ms
AngularCompilerPlugin._update._emit: 13.638ms
AngularCompilerPlugin._update: 43.407ms
AngularCompilerPlugin._make: 43.848ms
ngcLoader+D:\work\angular\aio\src\main.ts+.ngcLoader.AngularCompilerPlugin: 17.118ms
ngcLoader+D:\work\angular\aio\src\main.ts+: 20.312ms
TypeChecker.gatherDiagnostics.ts.getSemanticDiagnostics: 264.195ms
TypeChecker.message: 281.368ms

Date: 2018-12-13T11:45:50.889Z - Hash: 16ad75ffacc918bb20c2 - Time: 511ms
22 unchanged chunks
chunk {main} main.229bfd5f540aafd21011.js, main.229bfd5f540aafd21011.js.map (main) 201 kB [initial] [rendered]

<EMAIL_ADDRESS>rebuilds took ~3.3s

i ｢wdm｣: Compiling...
TypeChecker._update: 0.151ms
TypeChecker._createOrUpdateProgram.ts.createProgram: 10.518ms
TypeChecker.gatherDiagnostics.ts.getSemanticDiagnostics: 327.532ms
TypeChecker.message: 339.517ms
AngularCompilerPlugin._createOrUpdateProgram.ts.createProgram: 1592.257ms
AngularCompilerPlugin._emit.ts.gatherDiagnostics.ts.getSyntacticDiagnostics: 0.573ms
AngularCompilerPlugin._emit.ts+D:/work/angular/aio/src/main.ts+.emit: 197.366ms
AngularCompilerPlugin._emit: 200.312ms
AngularCompilerPlugin._update._emit: 200.506ms
AngularCompilerPlugin._update: 2803.878ms
AngularCompilerPlugin._make: 2804.271ms
ngcLoader+D:\work\angular\aio\src\main.ts+.ngcLoader.AngularCompilerPlugin: 1192.022ms
ngcLoader+D:\work\angular\aio\src\main.ts+: 1194.172ms

Date: 2018-12-13T11:50:28.263Z - Hash: 770163b2af42fff274b6 - Time: 3566ms
22 unchanged chunks
chunk {main} main.4eecb9fa84b0b62a9195.js, main.4eecb9fa84b0b62a9195.js.map (main) 201 kB [initial] [rendered]

<EMAIL_ADDRESS>rebuilds took ~1.1s (includes #13133)

i ｢wdm｣: Compiling...
TypeChecker._update: 0.154ms
AngularCompilerPlugin._createOrUpdateProgram.ts.createProgram: 4.893ms
TypeChecker._createOrUpdateProgram.ts.createProgram: 10.950ms
TypeChecker.gatherDiagnostics.ts.getSemanticDiagnostics: 258.325ms
TypeChecker.message: 270.538ms
AngularCompilerPlugin._emit.ts.gatherDiagnostics.ts.getSyntacticDiagnostics: 0.317ms
AngularCompilerPlugin._emit.ts+D:/work/angular/aio/src/main.ts+.emit: 10.914ms
AngularCompilerPlugin._emit: 11.688ms
AngularCompilerPlugin._update._emit: 12.224ms
AngularCompilerPlugin._update: 616.467ms
AngularCompilerPlugin._make: 616.803ms
ngcLoader+D:\work\angular\aio\src\main.ts+.ngcLoader.AngularCompilerPlugin: 596.443ms
ngcLoader+D:\work\angular\aio\src\main.ts+: 598.446ms

Date: 2018-12-13T11:55:02.640Z - Hash: 9fbd23000feec6a6452b - Time: 1141ms
22 unchanged chunks
chunk {main} main.5c50f6c3037acf65f46c.js, main.5c50f6c3037acf65f46c.js.map (main) 201 kB [initial] [rendered]

<EMAIL_ADDRESS>rebuilds took ~1.2s (includes extra logging from #13159)

i ｢wdm｣: Compiling...
TypeChecker._update: 0.151ms
AngularCompilerPlugin._createOrUpdateProgram.ts.createProgram: 5.154ms
AngularCompilerPlugin._listLazyRoutesFromProgram.createProgram: 0.065ms
TypeChecker._createOrUpdateProgram.ts.createProgram: 16.334ms
TypeChecker.gatherDiagnostics.ts.getSemanticDiagnostics: 283.161ms
TypeChecker.message: 300.672ms
AngularCompilerPlugin._listLazyRoutesFromProgram.listLazyRoutes: 630.713ms
AngularCompilerPlugin._emit.ts.gatherDiagnostics.ts.getSyntacticDiagnostics: 0.338ms
AngularCompilerPlugin._emit.ts+D:/work/angular/aio/src/main.ts+.emit: 13.726ms
AngularCompilerPlugin._emit: 14.763ms
AngularCompilerPlugin._update._emit: 15.229ms
AngularCompilerPlugin._update: 669.832ms
AngularCompilerPlugin._make: 670.866ms
ngcLoader+D:\work\angular\aio\src\main.ts+.ngcLoader.AngularCompilerPlugin: 650.003ms
ngcLoader+D:\work\angular\aio\src\main.ts+: 652.326ms

Date: 2018-12-13T12:14:41.442Z - Hash: 646a2507d4b49c72b08d - Time: 1186ms
22 unchanged chunks
chunk {main} main.68f05d7dcc3f58fc730b.js, main.68f05d7dcc3f58fc730b.js.map (main) 201 kB [initial] [rendered]

A few notes about these profiling messages:

AngularCompilerPlugin._make is the total time taken inside the ngtools/webpack plugin
TypeChecker.* refers to the forked type checker, in a separate process
Time spent in ngtools/webpack is only part of the story, as webpack also needs to recreate bundles and sourcemaps

My previous guess was that syntactic diagnostics on rebuilds were still taking too long, but that doesn't really hold true since in<EMAIL_ADDRESS>they are shown to take less that 1ms (AngularCompilerPlugin._emit.ts.gatherDiagnostics.ts.getSyntacticDiagnostics: 0.317ms).
What does seem to take a lot longer is AngularCompilerPlugin._update, clocking in at 43.407ms in 7.0.7 but increasing to 616.467ms in 7.1.2. The main contributor is AngularCompilerPlugin._listLazyRoutesFromProgram.listLazyRoutes, only visible in the profile logs for 7.1.3.
That increase seems related to https://github.com/angular/angular-cli/pull/12418, where the way we process lazy routes and their errors changed.

I can confirm. The rebuild is slower with @ngtools/webpack 7.1.3 due to listLazyRoutes:
With
@angular-devkit/architect         0.11.3
@angular-devkit/build-angular     0.11.3
@angular-devkit/build-optimizer   0.11.3
@angular-devkit/build-webpack     0.11.3
@angular-devkit/core              7.1.3
@angular-devkit/schematics        7.1.3
@angular/cdk                      7.2.0
@angular/cli                      7.1.3
@angular/material                 7.2.0
@ngtools/webpack                  7.1.3
@schematics/angular               7.1.3
@schematics/update                0.11.3
rxjs                              6.3.3
typescript                        3.1.6
webpack                           4.23.1

cli_7_13.zip
And with
@angular-devkit/architect         0.10.7
@angular-devkit/build-angular     0.10.7
@angular-devkit/build-optimizer   0.10.7
@angular-devkit/build-webpack     0.10.7
@angular-devkit/core              7.0.7
@angular-devkit/schematics        7.0.7
@angular/cdk                      7.2.0
@angular/cli                      7.0.7
@angular/compiler                 7.0.4
@angular/compiler-cli             7.0.4
@angular/material                 7.2.0
@ngtools/webpack                  7.0.7
@schematics/angular               7.0.7
@schematics/update                0.10.7
rxjs                              6.3.3
typescript                        3.1.6
webpack                           4.19.1

cli_7_07.zip

When can we fix this problem？I'm looking forward to resolve it. Thanks!

@filipesilva In my case,  run npm run build:demo takes 30 seconds,

Once I upgrade @angular/cli to 7.1.4 , it takes 80 seconds.

my repo is https://github.com/worktile/ngx-tethys, you can reproduce use npm run build:demo

@why520crazy, I'll be working on this today.

@why520crazy this issue is regarding rebuild performance in JIT mode and will have no effect on initial builds or production (AOT) builds.
Your issue is more likely due to this terser (the JavaScript minifier) issue: https://github.com/terser-js/terser/issues/204

@clydin  I see, thanks.
I think both should be needed.

@why520crazy this issue is regarding rebuild performance in JIT mode and will have no effect on initial builds or production (AOT) builds.
Your issue is more likely due to this terser (the JavaScript minifier) issue: terser-js/terser#204

I had the same issue and forcing a higher version of terser fixed my build.
npm install terser@latest --save-dev


go_pre_compile does not work

I followed the instructions in the readme for go.mod setup, I have compiled a golang executable to be run and generate database specific code before building the actual app, I named the executable go_pre_compile and put it in the bin/ directory relative to the project path... It doesn't work!
build myapp.com/api: cannot load myapp.com/api/prisma/db: cannot find module providing package myapp.com/api/prisma/db
 !     Push rejected, failed to compile Go app.
 !     Push failed

I just figured that the naming convention was wrong, it should have been go-pre-compile instead.
Now, It doesn't have access to the environment variables ....

@darmie This is a bit unfortunate – as part of the Buildpack API (https://devcenter.heroku.com/articles/buildpack-api), config variables are not available directly during the compile step of the buildpack.
Typically, you'd have to reach into ENV_DIR and extract them if you need them at compile time.


save png compression regression

Compare AbstractPlotting v0.9.27 vs v0.11.2
using GLMakie, AbstractPlotting
m = GLMakie.loadasset("cat.obj")
scene = mesh(m)
save("cat.png", scene)

file sizes are 44 kB (v0.9.27) vs 2706 kB (v0.11.2).
PNGFiles does have the option for compression_level
using PNGFiles
PNGFiles.save("debug0.png", fill(UInt8.(0), 720, 1280), compression_level=0)
PNGFiles.save("debug1.png", fill(UInt8.(0), 720, 1280), compression_level=1)

debug0.png is 903 kB, debug1.png is 3 kB`.

Here are the relevant lines:
https://github.com/JuliaPlots/GLMakie.jl/blob/9dec4a4b761f092d709ea8f46f2130a5f42f788b/src/gl_backend.jl#L77-L85
If we take a dependency on PNGFiles, we could easily do this.  cc @SimonDanisch

Already now AbstractPlotting.jl takes a dependency on ImageIO.jl that depends on PNGFiles.jl.
I proposed that PNGFiles.jl would default to Z_BEST_SPEED, let's see the response on that.
Otherwise we could write in GLMakie.jl/src/gl_backend.jl something like
function AbstractPlotting.backend_show(::GLBackend, io::IO, m::MIME"image/png", scene::Scene)
    img = scene2image(scene)
    PNGFiles.save(raw_io(io), img, compression_level = PNGFiles.Z_BEST_SPEED)
end

PNGFiles.jl v0.3.0 and IOImage.jl v0.3.0 have been tagged, and https://github.com/JuliaPlots/AbstractPlotting.jl/pull/475 has been merged. Now only a tag on AbstractPlotting.jl is needed to close this issue.  cc @SimonDanisch

Size of cat.png with AbstractPlotting v0.11.4 is 103 kB, that is 3x compared to 44 kB when using v0.9.27.  Reason is that now the image is 24 bpp vs 8 bpp.  As compression is fine, I close the issue.


Wrong behavior when handling discontinuous ranges.

I use serve-static middleware with expressjs to serve a big file, when I request discontinuous partial content of that big file, serve-static will response with the whole file and the status code is 200 rather than 206.
e.g. content of my big file (localhost:5052/test.txt) is:
0123456789

If I request with:
GET /test.txt HTTP/1.1
Host: localhost:5052
Range: bytes=1-3,6-8 // note, discontinuous
Cache-Control: no-cache

The response will be the whole file
0123456789

But if the range is continuous, it works fine.
Please give some advises. Thanks

I realized that this is a problem of send, and I noticed that there is a merge request  in progress to solve this problem, please update your send version once the merge request is done. Thanks!

The send version used is already the latest version.


List days

"list" shows overdue and pending
"list all" shows everything include done
Tests updated
used the containDate method... but prepareList still looks a bit messy because of the try catch :/
close #193

Coverage increased (+0.3%) to 69.809% when pulling 6739263b7470ecc7c4a78bbb782042435e74f618 on list-today into 8e326a023c339a6a4d0707f1e6ad89b0503d9a42 on master.

reviewed

Coverage increased (+0.4%) to 69.907% when pulling 44017b21eaf29534534bd8790ea1373444fc1899 on list-today into f8b8764dd9b4102609ec1005f1e44d80e9ca1c35 on master.

Coverage increased (+0.4%) to 70.258% when pulling e56f702747c5f45cf9e94ee35306d46728fcc815 on list-today into 23ef6776d927542e76571157e85a0625b71c104a on master.

Coverage increased (+0.5%) to 71.478% when pulling b2bb22b3a3dc9d3242bd762bb1df08b2fceb7792 on list-today into 9f9180f7cdbd38deb1ba8b707b7e85ce03e38ae2 on master.

Coverage increased (+0.5%) to 72.8% when pulling 2a75d4fc29a933e80b5d86ea0b9701e1a1d7bffa on list-today into 8afe9566d32405eed0879e119739dde0f38ef64c on master.

Coverage increased (+0.4%) to 74.19% when pulling ec9abb794872288f9462fb3d6cf5322755d7cfb1 on list-today into e0d21f2e522ffe1138f0fae0a2805a9799d73cab on master.


emulated_hue error

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.37.1
Python release (python3 --version):
Python 3.4.2
Component/platform:
emulated_hue on RPi 2, Raspbian Lite, manual install
Description of problem:
I'm getting the following error when I enable emulated_hue:
Exception in thread Thread-13: Traceback (most recent call last):   File "/usr/lib/python3.4/threading.py", line 920, in _bootstrap_inner     self.run()   File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/emulated_hue/upnp.py", line 152, in run     if "M-SEARCH" in data.decode('utf-8'): UnicodeDecodeError: 'utf-8' codec can't decode byte 0xfe in position 390: invalid start byte
SSDP traffic on my network seems to contain data that emulated_hue cannot decode. Wireshark shows SSDP traffic from several devices, but the message that can't be decoded seems to be coming from my Synology router. I didn't troubleshoot the problem further.
Expected:
emulated_hue should not crash if a device sends a bad SSDP message.
Problem-relevant configuration.yaml entries and steps to reproduce:
emulated_hue:
  expose_by_default: false

Traceback (if applicable):

Additional info:
My workaround was to modify upnp.py to ignore decode errors (line 152):
 if "M-SEARCH" in data.decode('utf-8', errors='ignore'):
With this change, emulated_hue seemed stable and my Harmony Hub and Amazon Echo were able to discover my emulated hue devices. However, I don't know if this is the correct fix or if there will be unintended consequences.

You can also just set emulate_hue to only show certain devices groups which will fix it. You must have some odd characters in your synology name.

I have the issue same issue.  I made the same fix.
if "M-SEARCH" in data.decode('utf-8','ignore'):
and have positive results and the google home connecion is
My hass version
0.38.3
To limit the number of device groups don't fixes the problem.

Apologies for bringing up from the dead this issue, but I also experienced this, and had to add 'ignore' to be able to get my echo to discover my devices

I was bitten by this as well and the mentioned fix made it work. It finally allowed me to drop HABridge and run with the build in emulated bridge. I happen to also have a Synology device which is not always on so this could explain why Echo discovery sometimes worked and sometimes didn't. Created a pull request to get this into the official release.


Added Ipfs with TiddlyWiki

What kind of change is it?

[X] Addition
[ ] Removal
[ ] Edit
[ ] Other

Checklist

[X] I edited the /data directory instead of the README.md.
[X] This PR includes only one addition/removal/edit.
[X] I ran the make build command following my edits to the /data directory.
[X] I have followed the CONTRIBUTING.md guidelines.

Details
Provide details of your changes here.
Thanks

@xmaysonnave in spare moment, please apply above suggestions (Ipfs → IPFS).
I was unable to apply them due to error:

@lidel I did my best here. Synchronized from upstream, update according to your suggestion and tried to push a new PR with the updates. However there are some side effects related to other topics (Cyber and IPSE). Give me your thoughts if I can improve the situation. Thanks for your effort.


JSHint error

modules/sl-ember-components/components/sl-grid-cell.js: line 15, col 10, 'ColumnAlign' is not defined.
modules/sl-ember-components/components/sl-grid-cell.js: line 28, col 10, 'ColumnSize' is not defined.
modules/sl-ember-components/components/sl-grid.js: line 14, col 10, 'ColumnAlign' is not defined.
modules/sl-ember-components/components/sl-grid.js: line 27, col 10, 'ColumnSize' is not defined.

May become resolved by https://github.com/softlayer/sl-ember-components/issues/588

Resolved by https://github.com/softlayer/sl-ember-components/pull/609


NIFI-5037 - ConsumeEWS Fails to Read Emtpy Message Body Emails

When an email has no message body, ConsumeEWS fails to read the message.
There is nothing wrong with having no message body, but setting an empty message body in Apache Email Commons is not allowed. Added step to not set the message body if empty. In testing this resolved the issue.
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

+1, merging to master, thanks @patricker


Merges Master to Live. See commits for details.

OPS Build status updates of commit 87af930:
:warning: Validation status: warnings

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOHubSite.md
:warning:Warning
View (sharepoint-ps)
Details

exchange/exchange-ps/exchange/devices/Get-MobileDeviceStatistics.md
:white_check_mark:Succeeded
View (exchange-ps)

sharepoint/sharepoint-ps/sharepoint-online/Connect-SPOService.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOExternalUser.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUserOneDriveLocation.md
:white_check_mark:Succeeded
View (sharepoint-ps)

skype/skype-ps/skype/Get-CsTeamsInteropPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Get-CsTeamsUpgradePolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsInteropPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsUpgradePolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsInteropPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Test-CsFederatedPartner.md
:white_check_mark:Succeeded
View (skype-ps)

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOHubSite.md

Line 5: [Warning] The content part of NOTE/WARNING/CAUTION/IMPORTANT/NEXT syntax is suggested to start in a new line.

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

OPS Build status updates of commit 12e0cd8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/devices/Get-MobileDeviceStatistics.md
:white_check_mark:Succeeded
View (exchange-ps)

sharepoint/sharepoint-ps/sharepoint-online/Connect-SPOService.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOExternalUser.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOHubSite.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOUserOneDriveLocation.md
:white_check_mark:Succeeded
View (sharepoint-ps)

skype/skype-ps/skype/Get-CsTeamsInteropPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Get-CsTeamsUpgradePolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsInteropPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsUpgradePolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsInteropPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Test-CsFederatedPartner.md
:white_check_mark:Succeeded
View (skype-ps)

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


Remove support for "inlineEdgeToEdge" in HostConfig.actions.actionMode

"inline" is enough. Renderers should always render inline cards "edge-to-edge" as it is consistent with the handling of background images/colors in containers.

@dclaux,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


r2.2-rc3 cherry-pick request: Fix a bug that profile XLA gpu crashes OOM.

Remove data redundancy by remove xla expression in trunk annotation.
Don't create device tracer when there's no GPU in the system.

Thanks!


Need help in running the example project in the example directory

Hi,
I need help in running the example project, Can anyone guide me on how to run it on android.
I have never worked with Mobx and I m getting several errors while trying to run the project.

What kind of errors?


Numbers (digits) not permitted in padatious intent files

If you use in a padatious .intent file var names with a number inside intent isn't recognized. Example:
(enter | add) room {room1} won't work but (enter | add) room {room_one}.

this is a problem in padatious itself, not on ovos-workshop, moving this issue to ovos-core so we can track it there, perhaps we can workaround it once we introduce the pipeline plugins


Create MSBuild Nuget packages targetting multiple platforms

The current MSBuild nuget packages only target .net core. We should come up with a packaging strategy that targets .net core, net46, and mono.
The .net core binaries are built on xplat. net46 binaries are built on master. Mono binaries could be built on either.

https://github.com/dotnet/corefx/issues/8398 suggests this approach as well.