MS team bot fails to join the meeting with internal server erorr

Describe the issue
I am testing MS teams bot with my own domain (no ngrock) and it fails with internal server error.
Expected behavior
It is expected that the bot will join the meeting/call
Graph SDK (please complete the following information):
Microsoft.Graph 4.18
Microsoft.Graph.Communications.Calls <IP_ADDRESS>22
Microsoft.Skype.Bots.Media <IP_ADDRESS>-alpha
Call ID
Call ID: 531f5a00-568a-48f9-a924-f6ef33539113
Time: 1.10 AM IST 08 October
Logs
{"@odata.type":"#microsoft.graph.commsNotifications","value":[{"@odata.type":"#microsoft.graph.commsNotification","changeType":"deleted","resource":"/app/calls/4e1f5700-f12e-4603-8e2a-74f93c916c1f","resourceUrl":"/communications/calls/4e1f5700-f12e-4603-8e2a-74f93c916c1f","resourceData":{"@odata.type":"#microsoft.graph.call","state":"terminated","resultInfo":{"@odata.type":"#microsoft.graph.resultInfo","code":500,"subcode":7112,"message":"Server Internal Error. DiagCode: 500#7112.@"},"chatInfo":{"@odata.type":"#microsoft.graph.chatInfo","threadId":"19:meeting_YjU2ZmE1M2UtOGVhZi00OWJlLWJhNGItZGNlNWQyOTk4Mjcx@thread.v2","messageId":"0"},"meetingInfo":{"@odata.type":"#microsoft.graph.organizerMeetingInfo","organizer":{"@odata.type":"#microsoft.graph.identitySet","user":{"@odata.type":"#microsoft.graph.identity","id":"0de038b4-5c99-43d7-928b-32abd36c49f5","tenantId":"460f56dd-4e87-4c6b-8d03-2a700501da93"}}},"callChainId":"042b76e5-9344-4c7f-bfbc-cc652e9ba1f9"}}]}
X-Microsoft-Skype-Chain-ID=042b76e5-9344-4c7f-bfbc-cc652e9ba1f9
Scenario-Id=5d16ce5b-0a80-446a-9619-01001f4ca06f
X-Microsoft-Skype-Message-ID=d4f09f3c-d291-4058-9360-200ed4a51243
Accept=application/json
Authorization=Bearer eyJhbGciOiJSUzI1NiIsImtpZCI6IlB1SGdMbkVNLU0xVmx4U3p5MTBCVDZoRl9hRSIsInR5cCI6IkpXVCIsIng1dCI6IlB1SGdMbkVNLU0xVmx4U3p5MTBCVDZoRl9hRSJ9.eyJ0aWQiOiI0NjBmNTZkZC00ZTg3LTRjNmItOGQwMy0yYTcwMDUwMWRhOTMiLCJhcHBpZCI6IjI2YTE4ZWJjLWNkZjctNGE2YS05MWNiLWJlYjM1MjgwNWU4MSIsIm5iZiI6MTY2NTE2ODM0NywiZXhwIjoxNjY1MTY4NjQ3LCJpc3MiOiJodHRwczovL2FwaS5ib3RmcmFtZXdvcmsuY29tIiwiYXVkIjoiY2EzMDYxZDctZDg0YS00NWEwLWIxOWYtYjlkNGJiYTkwY2E5In0.UKzcxXLtcZA58XrfFKTz39ns4bPMPEZmicAco9jGnG0YJVTutc9w-ZaVQHXqwnzluZ7j7aBy87zrqhZ5_jSjFL8bg_4hbj9Xr7ztTy6Fb-eWGgHdd-muA8U1HNxd55fVlVYOPvs1RrkjdWy5tjckDaurGIkJFxM9h8uZLzIQtj_3_muI0hEpSTUZhs-r4tYmv_6T8xgH8DBxtP0SK0nHaOSJIbP9A-uVxQsFF_m4RkbyQbHWR4o6tO1uavndzWVvL5HNAaahWhvDcaDrNhzsv-fMBs-VlcZ8dzKW9aEaWuVhqzHTa3zRUW-Ac9VZJzgoEmGtPDQXTkqJGMS_FUkOSQ
Host=learnm365.in.net
User-Agent=Microsoft-Skype/3.0,(Calling/1.0)
Additional context
Add any other context about the problem here.

Could not verify connectivity to the bot's media platform instance at learnm365.in.net:444. Please verify that InstancePublicPort 444 on the load balancer for learnm365.in.net is mapped to InstanceInternalPort port 8445 on the local machine.
Please double check what public port should be used for media control. You should avoid using a port value like 443 or 444 which is commonly taken for handling HTTPS web API traffic. If you have deployed just a single VM, try using 8445.

Thank you, this has helped and issue is fixed. Could you please let me know how we can see this errors as I haven't seen this.


webpack does not generate always unique chunk hashes

Hello,
we have noted that sometimes webpack generates the same hash for a chunk, even if the file content has been changed.
Due to this, changes sometimes are not propagated, we experience an error similar to #959  and we're forced to clear the cache/CDN to make the things work.
We are using the following plugins in the given order:
ExtractTextPlugin
CommonsChunkPlugin
OccurenceOrderPlugin
WebpackAssetsMapPlugin //custom plugin, writes the json stats file to the disk
DeduplePlugin
UglifyJsPlugin

Let me know if you need further details,
V.

:+1:

Let me know if you need further details,

Yes, it would be nice if you could send me two different files which identical hash so I could reproduce it.

Should be fixed.

Good news. Could you please share with us what was wrong?

The hashes of referenced chunks were not included in the chunkhash of the entry chunks.
A entry chunk include a list of urls of all additional chunks that can be loaded. Depending on the configuration there is a flag for each chunk whether it need to use to global hash or the chunk hash for caching. webpack now throws an error when using [chunkhash] for a chunk which requires a global hash (i. e. with HMR enabled). In addition to that [chunkhash] and [name] in output.chunkFilename no longer require a global hash for the entry chunk, but influence the chunkhash instead.
The first change ensures that there is an error when [chunkhash] won't be unique.
The second change ensures that [chunkhash] and [name] can be used for chunk filenames.

@sokra That's great, but still I cannot find a new release or something like that to install/update.
Am I missing something to use this feature??

+1

@sokra Ping. I am not able to find the fix you're talking about.
I have also tested the thing on my environment and the issue persists.

I have the same problem. Files are identical (looking through md5sum ./dist/*) but hash is different on different machines, but on the same machine hash stays the same.

I'm having the same problem as @dmitry both hash and chunkhash are different on different machines for the same git commit.

@viz looks like the absolute path is the root of the issue.

@dmitry - have you been able to fix it? My problem is that I need builds on CircleCI and Heroku to have the same hash...

@viz at the moment I fixed that with webpack-md5-hash but I don't like this approach.

hmm, I tried that but I still get different hashes on Circle versus Heroku. Perhaps I'm doing something wrong - I am new to webpack, so I'm not completely clear on the whole config. Like you, I started with react-redux-universal-hot-example but adding webpack-md5-hash as per the readme doesn't fix it for me...

I am still getting the issue with latest version. I am afraid this one wasn't fixed.

I found the issue is appears when imported library imports at least one file in itself. For example, I've tried remove all the react imports (requires) - hash was generated identically, then I've tried to import one library in a react library - it started to generate hash differently. It depends on absolute path, because I was able to reproduce that issue on the same machine but with different root paths.

yes, I found that one as well - unfortunately seems it is still an outstanding bug. If I had the skill to develop a patch I would, but getting into the guts of webpack is a bit beyond me at the moment. I'll have to look for another solution..

@dmitry Are you using a particular webpack version? I am getting an error using latest version (1.12.6) and webpack-dev-server as well (1.12.1)

@XVincentX here we are using webpack 1.12.2

1.12.2 here as well
Sent from my iPad

On 19 Nov 2015, at 10:40 PM, Dmitry Polushkin<EMAIL_ADDRESS>wrote:
@XVincentX here we are using webpack 1.12.2
—
Reply to this email directly or view it on GitHub.

@dmitry
I do not get if your workaround is working or not...sorry :(

For me adding the new WebpackMd5Hash() (webpack-md5-hash) inside the webpack plugins is working.

@dmitry are you using common chunks as well and it works? We're finding that different builds can generate different chunk references within the common chunk file itself as mentioned here

@bradrobertson no common chunks plugin used in our webpack config.

I am using them. Perhaps it's the reason for the error I'm getting.

Looks like this isn't fixed as of<EMAIL_ADDRESS>and is causing us a lot of problems with subresource integrity because cached contents are getting served that don't have a matching integrity sha. @bebraw is a plan for a fix in the works for webpack 2?

@dtothefp I tagged the issue under webpack-2 label so we won't forget. Thanks for bringing this up.

@bebraw thanks...this is a very bad bug because if you are using subresource integrity and filenames overlap sometimes the CDN will serve previously cached content that does not match the subresource integrity hash for the current bundle, and therefore the JS/CSS generated through Webpack will not load

Yep, that sounds pretty bad. Do you have a way/repo to reproduce it reliably? That would be a big help.

@jhnns essentially it took months of build of in S3 for this to start happening. I'm using [chunkhash]-[name] for CSS and JS compilation. We also switched from Webpack 1.x to Webpack 2.1.0-beta.22, not sure if that somehow could have allowed an overlapping of file name hashes? I'm using the SRI stats plugin https://github.com/mikechau/sri-stats-webpack-plugin to generate the subresource integrity stats.
Essentially here is the flow that results in failure that took us a while to figure out what was going on:

webpack generates CSS/JS files in CI with the hashed filename
SRI plugin generates stats for sha of the file that can be included on the integrity attribute for a script or link tag
static template generator  tags
CSS/JS assets get uploaded to S3, if a previous filename exists on S3 it is overwritten by uploaded content
template is generated on server, static template generator, or lambda using the generated hashed filenames and SRI to make the script and link
if there was a filename collision on S3 due to improper hashing by webpack then cached content will potentially be served and this content will NOT match the SRI integrity attribute sha
everything breaks and people get 😢  / 😠

I wish I could reproduce when / how this happens but it seems to start showing up lately across many of our applications through many Travis CI builds that upload static assets to S3. I resorted to using the md5 webpack plugin and seems to be working for now.

As far as I'm understanding it, we have two issues here:

Some people are complaining about different hashes although the file content is the same @dmitry
Some people are complaining about the same hashes although the file content has changed @dtothefp

Please note that webpack hashes the final result (chunks and assets), which means that loaders and plugins have been executed before. Thus it is possible that you don't get the same hashes for the same file content, because you might have installed different versions of loaders and plugins (at least when using npm).
Same goes the other way round. For instance, if you're using tree-shaking, you might get the same hashes for different file contents if unused code is removed.
It would be very helpful if you could reproduce the error without any plugin. @dtothefp maybe it's an error with the sri-stats-webpack-plugin? Try to remove as much as the possible so that we can locate the error.

@jhnns I've reproduced such issue with simple code: just webpack settings without any plugins and react library (could be used any other module, that loads other modules in it). I believe I've explained this year ago somewhere here: #1479

I'm using webpack 2, and it's so bad I always need to go fiddle with the urls. I've thrown in all the things: [name].js?[chunkhash][id][hash] but it still isn't unique always. I think I'll just start to write the darn date in there instead.

@jhnns @bebraw any word on this? Looks like Webpack 2 was released without a fix

@dtothefp Nope. It's a huge and complicated issue and I don't think there's a simple fix in sight. Reading back, a minimal case to showcase the problem would likely help.

@bebraw I just quickly put together this repo https://github.com/dtothefp/webpack-broken-sha. Made a branch where I changed JS slightly and got a different sha so ¯\_(ツ)_/¯.
What we saw in the past is that this happened overtime, some deploys with differing content had the same hash and some had different. The only way we knew is when subresource integrity broke because it got cached content (i.e. a deploy with changed content had the same hash as a previous deploy and the CDN served the previous deploys content).
If anyone wants to play around with the repo above to try and reproduce feel free. It's just a basic setup with React and CSS modules.

Anyone using https://github.com/scinos/webpack-plugin-hash-output plugin to work around this problem?
It generate the hash from the final content files.

@le12484 I am using https://github.com/erm0l0v/webpack-md5-hash and it has been working fine for me these past few months.

The same hash in filename for different entry files with different contents. Why? Is it normal behavior?
Doesn't matter if CommonsChunkPlugin is used or not, the result hash in filenames is the same.
child.js
'use strict';
let child = (params) => {
    return params;
}

export default child;

fileA.js
'use strict';
const React = require('react');
import child from './child';

let a = 10;
console.log(a);

child({a: 10})

fileB.js
'use strict';
import child from './child';

webpack config.js
'use strict';

const NODE_ENV = process.env.NODE_ENV || 'development';
const path = require('path');
const webpack = require('webpack');

module.exports = {
    context: path.resolve(__dirname, '..'),
    entry: {
        'public/fileA': './src/fileA',
        'public/fileB': './src/fileB',
    },
    output: {
        filename: '[name]-[hash].js',
        // path: path.resolve(__dirname, '..', 'dist'),
    },
    plugins: [
        // new webpack.optimize.CommonsChunkPlugin({
        //     name: 'commons',
        //     filename: "public/commons-[hash].js",
        //     minChunks: 0,
        //     // chunks: ["pageA", "pageB"],
        // })
    ]
}

"webpack": "^3.7.1"

Switching from [chunkhash] to [contenthash] solved the problem with the same name of the css file with the different content.
new ExtractTextPlugin({ filename: "css/[name].[chunkhash].css" })
vs
new ExtractTextPlugin({ filename: "css/[name].[contenthash].css" }),

As @le12484 recommended, I wrote https://www.npmjs.com/package/webpack-plugin-hash-output to precisely fix this problem. It guarantees that you'll get a [chunkhash] that is always a hash of the content. It solves the two errors in this thread (as summarized by @jhnns).
It even has the option to fail the compilation if, for whatever reason, that postcondition is not met (see option validateOutput).


IPC lost after auto-update restart (Address already in use)

Bug report
Description
After self-restart doing auto-update IPC listener can't rebind (old process not exited yet) and ASF runs without one. Not the case while using "restart" command.
Expected behavior
New process expected to start correctly.
Actual behavior
Application drops exception and starts with feature disabled.
Steps to reproduce
Just do auto-update.
Full log.txt recorded during reproducing the problem
2018-05-26 20:15:01|ArchiSteamFarm-3107|INFO|ASF|InitASF() ArchiSteamFarm V<IP_ADDRESS> (924ca885-f911-46cf-92e6-09a63ec3a30c)
2018-05-26 20:15:04|ArchiSteamFarm-3107|INFO|ASF|Start() Starting IPC server on http://<IP_ADDRESS>:1242/...
2018-05-26 20:15:04|ArchiSteamFarm-3107|ERROR|ASF|Start() System.Net.HttpListenerException (0x80004005): Address already in use
   at System.Net.HttpEndPointManager.GetEPListener(String host, Int32 port, HttpListener listener, Boolean secure)
   at System.Net.HttpEndPointManager.AddPrefixInternal(String p, HttpListener listener)
   at System.Net.HttpEndPointManager.AddListener(HttpListener listener)
   at System.Net.HttpListener.Start()
   at ArchiSteamFarm.IPC.Start(HashSet`1 prefixes)
2018-05-26 20:15:04|ArchiSteamFarm-3107|INFO|ASF|CheckAndUpdateProgram() ASF will automatically check for new versions every 1 day.
2018-05-26 20:15:04|ArchiSteamFarm-3107|INFO|ASF|CheckAndUpdateProgram() Checking for new version...
2018-05-26 20:15:10|ArchiSteamFarm-3107|INFO|ASF|CheckAndUpdateProgram() Local version: <IP_ADDRESS> | Remote version: <IP_ADDRESS>

Global ASF.json config
{
	"AutoRestart": true,
	"AutoUpdates": true,
	"BackgroundGCPeriod": 0,
	"Blacklist": [],
	"ConnectionTimeout": 60,
	"CurrentCulture": null,
	"Debug": false,
	"FarmingDelay": 15,
	"GiftsLimiterDelay": 1,
	"Headless": false,
	"IdleFarmingPeriod": 8,
	"InventoryLimiterDelay": 3,
	"IPC": true,
	"IPCHost": "<IP_ADDRESS>",
	"IPCPort": 1242,
	"LoginLimiterDelay": 10,
	"MaxFarmingTime": 10,
	"MaxTradeHoldDuration": 15,
	"OptimizationMode": 0,
	"Statistics": true,
	"SteamOwnerID": REMOVED_FROM_DUMP,
	"SteamProtocols": 1,
	"UpdateChannel": 1
}

Additional info
Yep, I know, no support for IPC. But since it's not bugfix request but bug report - it makes no harm. Mark it "Won't fix" or whatever.

Yep, I know, no support for IPC.

You got it wrong, no support for IPC GUI, not IPC itself, because IPC is entirely within ASF scope and support.
As of the rest - https://github.com/JustArchi/ArchiSteamFarm/issues/754#issuecomment-370865690

Let me know if this issue won't disappear after we're done with https://github.com/JustArchi/ArchiSteamFarm/issues/799


Created new file for the town of Glen Ridge, NJ

Extended description woud go here if you really want to type a longer description, closes #23

Chaz left a comment about this pull request

Hey @githubteacher - can you take a look at this?

Chaz, please approve.

Hola.. :last_quarter_moon_with_face:

I agree to merge based on the recommendation on the one and only restaurant in town.


From CommonCrawl WET files,  for each web page count the lengths of texts of different languages

WET files contain text of wet page, and latest ones have languages info of text. However, the earlier WET files    may have no language info, so we have to identify the languages of text in Web pages.


add get committe info in FN

as title. This unblocks the work to use remote FN for txn submission in load gen

cc @joyqvq @gegaowp who might be interested

Is this same as 0x5 object?
I thinks it's a good addition to the apis, LGTM
you probably need to regenerate the openrpc.json file

yes, on the latest epoch,  you can get this from 0x5


ansible: update deployment instructions to use container

Previous to this commit, the instructions stated to install
Ansible, Go and other tools needed to deploy CIAO successfully.
This commit changes the deployment instructions to make use
of the clearlinux/ciao-deploy container instead, removing
all the depdendencies install steps.
Signed-off-by: Simental Magana, Marcos<EMAIL_ADDRESS>

This fixes a non-imported issue from clear-config-management

Coverage remained the same at 65.934% when pulling b9fd745f7970e29ea84cf6b525bb101336799391 on mrkz:ansible_readme_update into 3c0cf66e6c5611c82d7f6c93694d02b94641f0c5 on 01org:master.

Coverage remained the same at 65.912% when pulling 2ddb2f9048b226e7244b269d0470a5de88677c3d on mrkz:ansible_readme_update into a3799e319997d49458399d713ceecac462e6f407 on 01org:master.

Coverage increased (+0.005%) to 65.917% when pulling bc5fd8104668c8fc0548f7e6433a08c6c628cc32 on mrkz:ansible_readme_update into a3799e319997d49458399d713ceecac462e6f407 on 01org:master.

Coverage increased (+0.03%) to 65.945% when pulling 2cac9a61eaa1f6565e96ff1848da3d13f65f6047 on mrkz:ansible_readme_update into a3799e319997d49458399d713ceecac462e6f407 on 01org:master.

+1

Coverage decreased (-0.2%) to 65.802% when pulling c896ab8920e0e17d7888b84b896133decbec62d9 on mrkz:ansible_readme_update into e147d5d685253ff1d7ce368e7b4578527e363b51 on 01org:master.

Coverage decreased (-0.08%) to 65.879% when pulling efd5ee49ddad69fd151d364597d4beb263813845 on mrkz:ansible_readme_update into e147d5d685253ff1d7ce368e7b4578527e363b51 on 01org:master.


TestClientLibrary is racy

Hit this failure with https://github.com/influxdb/influxdb/pull/2376, does not occur locally.
server_integration_test.go:165: Test: single server integration via client library: creating database mydb
server_integration_test.go:172: Creating retention policy myrp for database mydb
server_integration_test.go:1620: testing single server integration via client library - mulitple points, multiple values
server_integration_test.go:1643: query expected result: {"results":[{"series":[{"name":"network","columns":["time","rx","tx"],"values":[["2015-04-22T02:31:27.095925376Z",1.1,2.1],["2015-04-22T02:31:27.095925377Z",1.2,2.2],["2015-04-22T02:31:27.095925378Z",1.3,2.3]]}]}]}
server_integration_test.go:1644: query got result:      {"results":[{"series":[{"name":"network","columns":["time","rx","tx"],"values":[["2015-04-22T02:31:27.095925376Z",1.1,2.1]]}]}]}

@corylanou

Kicked the build and then everything worked.

https://circleci.com/gh/influxdb/influxdb/1844 was the failing build.

No longer applicable in new design.


fix: resolve typos and grammar issues from files

- What I did
Fixed some typos from documentation.
- How to verify it
- Description for the changelog

@wanderer163 thanks very much for your contribution.
Your commit seems not passing on DCO cheeking, can you please follow this guide on docs?
Since you already commit the changes, you can use the --amend to just change the actual commit.
The lint workflow seems not passing too, you can rebase with the our main to fix this workflow running:

git fetch
git rebase origin/main # Assuming that your origin is the  github.com/ZupIT/horusec repository

After these changes you can make git push --force


Can't use path_provider 1.0.0

Because flutter_advanced_networkimage >=0.4.5 depends on path_provider ^0.5.0 and ... depends on path_provider ^1.0.0, flutter_advanced_networkimage >=0.4.5 is forbidden.

Using  ^0.5.0-alpha.2 and flutter master

https://www.dartlang.org/tools/pub/dependencies#dependency-overrides

That works - closing. Maybe add support for path_provider 1.0.0 later?


Sigmoid returns negative values

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
CentOs Linux 7 (Core)
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):
pip3 installed tensorflow-gpu
TensorFlow version (use command below):
2.1.0
Python version:
3.6.0
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
cuda 10.1 cudnn 7.6.4
GPU model and memory:
Tesla P100 75GB

Describe the current behavior
The last output layer is a sigmoid function, but the AUC metric says output is not >= 0 element-wise. I've also tried this using activation='sigmoid' in the output layer directly, which also results in the same error.
I've verified that after removing AUC as a metric,  the code works but the min output value becomes negative after a few epochs.
Describe the expected behavior
Sigmoid output should be 0-1
**Last part of the code **
    ypred = tf.keras.layers.Dense(
            1, name="%s_out" % target_variable,
            kernel_regularizer=tf.keras.regularizers.l2(beta))(x)

    ypred = tf.nn.sigmoid(ypred)

    model = tf.keras.models.Model(inputs=inputs, outputs=ypred)
    optimizer = tf.keras.optimizers.Adam(lr)
    model.compile(optimizer=optimizer,
                  loss='binary_crossentropy',
                  metrics=['accuracy', 'AUC', 'mse'])

    early_stopping = tf.keras.callbacks.EarlyStopping(patience=100)

    callbacks = [early_stopping]

    model_start_time = time.time()

    model.evaluate(test_ds, verbose=2)

    history = model.fit(
            train_ds, validation_data=(test_ds), epochs=num_epochs,
            verbose=2, callbacks=callbacks)

Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.
Traceback (most recent call last):
  File "lol_embed_ntf_champs.py", line 162, in <module>
    save_results=args.save_results, **datum)
  File "/auto/rcf-40/yioujian/ntf-embed/lol_embedding_ntf_champs.py", line 160, in run_embed_ntf
    verbose=2, callbacks=callbacks)
  File "/home/rcf-proj2/ef/yioujian/.local/lib/python3.6/site-packages/tensorflow_core/python/keras/engine/training.py", line 819, in fit
    use_multiprocessing=use_multiprocessing)
  File "/home/rcf-proj2/ef/yioujian/.local/lib/python3.6/site-packages/tensorflow_core/python/keras/engine/training_v2.py", line 342, in fit
    total_epochs=epochs)
  File "/home/rcf-proj2/ef/yioujian/.local/lib/python3.6/site-packages/tensorflow_core/python/keras/engine/training_v2.py", line 128, in run_one_epoch
    batch_outs = execution_function(iterator)
  File "/home/rcf-proj2/ef/yioujian/.local/lib/python3.6/site-packages/tensorflow_core/python/keras/engine/training_v2_utils.py", line 98, in execution_function
    distributed_function(input_fn))
  File "/home/rcf-proj2/ef/yioujian/.local/lib/python3.6/site-packages/tensorflow_core/python/eager/def_function.py", line 568, in __call__
    result = self._call(*args, **kwds)
  File "/home/rcf-proj2/ef/yioujian/.local/lib/python3.6/site-packages/tensorflow_core/python/eager/def_function.py", line 599, in _call
    return self._stateless_fn(*args, **kwds)  # pylint: disable=not-callable
  File "/home/rcf-proj2/ef/yioujian/.local/lib/python3.6/site-packages/tensorflow_core/python/eager/function.py", line 2363, in __call__
    return graph_function._filtered_call(args, kwargs)  # pylint: disable=protected-access
  File "/home/rcf-proj2/ef/yioujian/.local/lib/python3.6/site-packages/tensorflow_core/python/eager/function.py", line 1611, in _filtered_call
    self.captured_inputs)
  File "/home/rcf-proj2/ef/yioujian/.local/lib/python3.6/site-packages/tensorflow_core/python/eager/function.py", line 1692, in _call_flat
    ctx, args, cancellation_manager=cancellation_manager))
  File "/home/rcf-proj2/ef/yioujian/.local/lib/python3.6/site-packages/tensorflow_core/python/eager/function.py", line 545, in call
    ctx=ctx)
  File "/home/rcf-proj2/ef/yioujian/.local/lib/python3.6/site-packages/tensorflow_core/python/eager/execute.py", line 67, in quick_execute
    six.raise_from(core._status_to_exception(e.code, message), None)
  File "<string>", line 3, in raise_from
tensorflow.python.framework.errors_impl.InvalidArgumentError: 2 root error(s) found.
  (0) Invalid argument:  assertion failed: [predictions must be >= 0] [Condition x >= y did not hold element-wise:] [x (model/tf_op_layer_Sigmoid/Sigmoid:0) = ] [[0.323994398][0.177097648][0.000274539]...] [y (metrics/AUC/Cast_1/x:0) = ] [0]
	 [[{{node metrics/AUC/assert_greater_equal/Assert/AssertGuard/else/_1/Assert}}]]
	 [[metrics/AUC/assert_less_equal/Assert/AssertGuard/pivot_f/_13/_39]]
  (1) Invalid argument:  assertion failed: [predictions must be >= 0] [Condition x >= y did not hold element-wise:] [x (model/tf_op_layer_Sigmoid/Sigmoid:0) = ] [[0.323994398][0.177097648][0.000274539]...] [y (metrics/AUC/Cast_1/x:0) = ] [0]
	 [[{{node metrics/AUC/assert_greater_equal/Assert/AssertGuard/else/_1/Assert}}]]
0 successful operations.
0 derived errors ignored. [Op:__inference_distributed_function_4015]

Function call stack:
distributed_function -> distributed_function

Update: it seems that the issue might be related to AUC and not sigmoid, because after removing AUC there were no negative outputs. However, I also realized the result is not deterministic (even though I've seeded everything, I don't know why)
I did manage to fix the problem by manually clipping the value to be between 0 and 1, however.

@julie-jiang
Please, let us know   is this still an issue. Please, close this thread if your issue was resolved.
If the issue was not resolved request you to share colab link or simple standalone to reproduce the issue in our environment.It helps us in localizing the issue faster.Thanks!

@julie-jiang I'm running into the same issue. Can you share how you clip the value to be between 0 and 1?

@Namzakku You can either use tf.clip_by_value or tf.clip_by_norm. Here's a complete example


Better handle error message

the hive error message is a compact cake, that would be better to extract the error and pop it nicely

@parisni : are messages all handled correctly thanks to @bharatl latest PR?

@Dubrzr  yes thanks


Added -t flag for multithread

Indicate number of threads with -t flag, e.g., "suppa.py diffSplice -t 10". Default is 1. Equal to previous asynchronous ver with 1 thread.

@trinhan Thanks Anne, I leave this for now until Oggy deemed it's necessary. We already merged a working optimised version (asynchronous, single thread). This is an upgrade on that one for multi-thread and was tested with NYG data successfully.


Create PULL_REQUEST_TEMPLATE.md

Fixes #543
Checklist

[x] I have made a material change to the repo (functionality, testing, spelling, grammar)
[x] I have read the [Contribution Guide] and my PR follows them.
[x] I updated my branch with the master branch.
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation about the functionality in the appropriate .md file
[ ] I have added in line documentation to the code I modified

Short description of what this PR does:

Creates a pull request template to help describe what has changed in the pull request being submitted
Uses the new template content that merges ideas we got from contributors on other repos

If you have questions, please send an email to Sendgrid, or file a Github Issue in this repository.
@mbernier

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hello @duncanleung,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


Fix build error on Travis CI

Fix a following build errors.

Gem::InstallError: rack requires Ruby version >= 2.2.2.
Gem::InstallError: nokogiri requires Ruby version >= 2.1.0.
Travis 'Ruby rbx-2' failing on master (https://github.com/vmg/redcarpet/issues/580)

And old patch version of MRI had been used. Bumped them.
cf. https://travis-ci.org/bkeepers/dotenv/builds/147221473

Thanks!

Thanks too!


3 blog posts

Proofing "Stellar" blogpost now.

@RichardLitt has finished the proofreads, @lgierth everything is good for merge :)

hey guys, could you wait for an ok from me before shipping out blog posts? since the blog will be our loudspeaker to the whole world, i want to keep a certain focus and also level of quality. call me a curator! And, not that these posts arent good-- they are. i want to make sure i'm aware of the communications being shipped out, and the order. We will build a following to this blog, and it is important to carefully curate the readers' attention. It will also be good to get @kyledrake's feedback before shipping them. we can build a backlog of posts and ship them out as we choose them.

@diasdavid

[ ] i dont think https://ipfs.io/blog/2-idempotent-encoder-decoder/ makes sense for the IPFS blog. we should keep the ipfs blog ipfs focused, not random cs stuff.

To give some direct feedback, it's very much a personal discovery type of post, which ignores Coding Theory and Programming Languages (PL) Theory. it makes sense for a personal blog -- which traces your history as you research and discover and think about things -- but not for "The Official IPFS Blog", which represents the whole IPFS community. IPFS is a thing that very smart PL people are following and want to use (for implementing CRDTs, LVars, replicators(?)). But if they saw this post pushed as "an official representation of the level of PL theory understanding of the IPFS team", they would rightfully be very concerned.

[ ] on numbering, @kyledrake's other post was 2, so removing the encoder/decoder one should allow that one to merge into the right order.

(hit enter too soon)
@diasdavid

**Both the ipscend and stellar module management are great!! :) :+1: **
[ ] can you verify the image of the world in https://ipfs.io/blog/4-registry-mirror/ is CC-by or you have rights to use + distribute it? (i've been keeping my use of images very kosher with copyright, to the best result of my looking. some may have escaped, but just be aware and try to make sure licensing is solid.
[ ] can we use ipfs-update to simplify the dev0.4.0 instructions? (ask @whyrusleeping for help)
[ ] a claim like "there is no way for the list to be compromised" is waaaaay too strong -- there could be a cryptographic break, or a problem in our protocols or implementations, how about: "This list is fetched and kept up to date through IPNS. This ensures secure distribution, as IPNS records are signed and validated with the publisher's private key."
[ ] maybe "in the part of the network you are currently in" --> "the network you are currently in" ("part of" suggests distance/network-diameter problems)
[ ] "IPFS would be able to find it through Peer and Content Routing (with a DHT)." --> "IPFS would be able to find it through its Peer and Content Routing (e.g. with a DHT)."
[ ] "Through cryptographic hashing -- the IPFS strategy to find, deliver and check that the content it received was what was requested -- you can always be sure that what you are running was what you were looking for." this line implies that "cryptographic hashing" is a strategy for finding and delivering content. it is not, we use "cryptographic hashing" as part of the strategy. how about: "Just like git, IPFS verifies the content received using cryptographic hashing, making sure it is exactly what was requested -- you can always be sure that what you are running is what you asked for."
[ ] the demo video really, really needs narration. I only know what's going on because i know what's going on.

i dont think https://ipfs.io/blog/2-idempotent-encoder-decoder/ makes sense for the IPFS blog. we should keep the ipfs blog ipfs focused, not random cs stuff.

ok, sounds good ( I had it tagged with IPFS since it came from the CBOR discussions, as it is referenced).
Since this already got merged, I'll submit a separate PR with your proposed changes :)


Deploy a relayer to connect the hub and rollapp for local testnet

@mtsitrin I believe this is done right?


Clicking on a course name in professors causes race conditions

Reproduce:

go to professors page
click on a course name under recently taught. You may have to try with a few different course names.

Expected behavior:

it shows the course and doesn't mess up browser history

Eventually, what actually happens with those two steps:

the professor page is shown.
clicking the browser back goes to the course you clicked

Race between the click event on the professor hit item div and the course link. (component)
https://github.com/user-attachments/assets/670848ac-9af5-4b4d-bd83-01a21a45cf78


Adaptive card values not persisting after submit

Say I have a Teams Bot that responds with an adaptive card with an input element, such as Input.Text (although I see this behavior with any of the input elements). When running in Teams, after the user types something and submits, I see that the adaptive card clears out the text. Is there a way to not have the text get cleared out and just leave what the user typed?
const { ActivityHandler, CardFactory } = require('botbuilder');
const InputCard = require('../resources/InputCard.json');

class TestBot extends ActivityHandler {
    constructor(userState) {
        super();
        this.userState = userState;
        this.onMembersAdded(async (context, next) => {
            await next();
        });
        this.onMessage(async (context, next) => {
            await context.sendActivity({
                attachments: [CardFactory.adaptiveCard(InputCard)]
            });
            await this.userState.saveChanges(context);
            await next();
        });
    }
}

module.exports.TestBot = TestBot;

{
  "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
  "type": "AdaptiveCard",
  "version": "1.0",
  "body": [
    {
      "type": "Input.Text",
      "id": "message"
    }
  ],
  "actions": [
    {
      "type": "Action.Submit",
      "title": "OK"
    }
  ]
}

@roalexan Action.Submit submits the details entered by the user in the Text field to the Bot. You can get those values in activity.Value. However once the details are submitted the values in the input fields disappear.

Thanks. Yes, I have no problem getting the values. The problem is with the user experience. It does not seem correct to remove the settings after hitting OK. What I need help with is how to either not remove the settings or restore the settings. Attached are a few screenshots showing what I'm talking about.
From Teams (note the settings are gone after hitting ok):

BTW, here's what it looks like from the Bot Emulator (note the setting remain, which is the behavior I'm trying to achieve in Teams):

And here's another view of what I'm talking about, this time using an Input.ChoiceSet.
From Teams:

From Bot Emulator:

Yes that is by design. It's very similar to how HTML forms work. No current plans to change this behaviour.
There is an option to update your card when user click on submit action as explained here https://github.com/OfficeDev/BotBuilder-MicrosoftTeams/issues/192#issuecomment-494316723.


Add support for Halloween storage

Adds an option in the config to override specific props into their Halloween variants.
TODO: Add support for winter storage & whatnot

Closing this PR and making a new one from a different branch


Add composer.json + questions

Hi @joakimbo,
I'd like to use your plugin as a required of one I'm currently building, but I have some few questions:
Could it be possible to publish the package on packagist? The plugin I want to use it is actually for another platform (WinterCMS) and I'd love to use composer.json to include your plugin into mine.
Also OctoberCMS 2.0 only support plugins updates through composer.
I see in the code that you have created a custom formwidget which reproduce the exact same behavior/appearance of the core's PermissionEditor formwidget. Is there a good reason to do that? Did you try to extend it but faced blocking problem?
Also I see that you've used condition to insert or not the sidemenu link to the Users controller, why didn't you use the basic permission key on the menu?
If you are interested in those changes, I could do some separated PR to implement them individually.

Hi @RomainMazB, and thank you for your interest in this plugin.
Regarding publishing this plugin on packagist, this is not something I am interested in and its reasons are more or less answers to your other questions. The codebase for this plugin was written in 2019 and I'm sorry to say that I do not remember what the best practices were back then nor do I know what they are today regarding plugins for OctoberCMS, nor do I remember specifics about what issues I might have encountered during the development of this plugin.
For me to approve any pull requests I would need to get up to date about these thing which is unfortunately not something I currently have the time to do. I will point out however that the code is licensed under MIT so you are free to fork and/or copy this code to distribute and improve upon any way you like as long as you adhere to the license.
I apologize for not being of more use but I wish you the best with your endeavours.
/ joakimbo

@joakimbo, thanks for the rapid answer.
That's not a problem, I'll just look at the codebase to inspire myself to reproduce what I need.


chore(deps): update dependency semantic-release to v17.2.1

This PR contains the following updates:

Package
Type
Update
Change

semantic-release
devDependencies
patch
17.2.0 -> 17.2.1

Release Notes

semantic-release/semantic-release
v17.2.1
Compare Source
Reverts

Revert "feat: throw an Error if package.json has duplicate "repository" key (#1656)" (3abcbaf), closes #1656 #1657

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

Available now for Enterprise: Renovate Pro with real-time webhook handling and priority job queue.

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

v6.1.4
GitHub release

Your semantic-release bot :package::rocket:


Expose API functions from top-level

Also update cookiecutter package in https://github.com/cthoyt/cookiecutter-snekpack/commit/fa032ffc3c718c208d3a03e212aaa299c193de94 to have this be a part by default

Codecov Report

Merging #7 (e6ff3c3) into main (5e1a0cb) will increase coverage by 0.29%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main       #7      +/-   ##
==========================================
+ Coverage   79.56%   79.85%   +0.29%
==========================================
  Files           4        4
  Lines         137      139       +2
  Branches       25       25
==========================================
+ Hits          109      111       +2
  Misses         17       17
  Partials       11       11

Impacted Files
Coverage Δ

src/torch_ppr/__init__.py
100.00% <100.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 5e1a0cb...e6ff3c3. Read the comment docs.

@mberr i'd suggest a new release with this one now so you don't have to do from torch_ppr import api


add config for filesystem.private

Please describe the feature you would like to see implemented.
No response

We won't do this because this file system can be configured to behave in a specific way.


border radius controls on rotated element

Problem:
When an element is rotated via translate: transform, border radius controls show up in the wrong place
Fix:
use element.globalFrame instead of element.specialSizeMeasurements.{width/height} when calculating element bounding box
Visually
After

Before

NB we've got the same issue with the reorder control


overrides are not applied

Hi,
I would like to apply an override to installed flatpak:
    nix-flatpak.url = "github:gmodena/nix-flatpak?ref=v0.3.0";
...
  services = {
    flatpak = {
      enable = true;
      update.onActivation = true;  # Trigger update on system activation
      uninstallUnmanagedPackages = true;
      remotes = [
        {
          name = "flathub";
          location = "https://flathub.org/repo/flathub.flatpakrepo";
        }
      ];
      packages = [
        { appId = "io.freetubeapp.FreeTube"; origin = "flathub"; }
      ];
      overrides = {
        # global = {
          Context.sockets = ["wayland"];
        };
      };
    };
  };

But the overrides are not applied:
$ sudo flatpak override --show io.freetubeapp.Freetube

$ sudo flatpak override --show

$ flatpak run io.freetubeapp.Freetube --ozone-platform=wayland
<error>

$ flatpak run --socker=wayland io.freetubeapp.Freetube --ozone-platform=wayland
<works>

Thanks
Same result with
...
        "io.freetubeapp.FreeTube" = {
          Context.sockets = ["wayland"];
        };
...

hey @yellowhat could you share some details on how you installed and configured nix-flatpak?
I applied the config you provided to a nixos created using the testing-base/ sample configs and flakes. nix-flatpak is installed as a nixos module.
This is the content of flatpak.nix:
{ lib, ... }: {
    services = {
    flatpak = {
      enable = true;
      update.onActivation = true;  # Trigger update on system activation
      uninstallUnmanaged = true; # I am tracking master, where this config has been introduced.
      packages = [
        { appId = "io.freetubeapp.FreeTube"; origin = "flathub"; }
        { appId = "com.brave.Browser"; origin = "flathub"; }
        "com.obsproject.Studio"
        "im.riot.Riot"
      ];
      overrides = {
        global = {
          Context.sockets = ["wayland"];
        };
      };
    };
  };
}

I built a vm with:
nix build .#nixosConfigurations.test-hm-module.config.system.build.vm

After activation (on boot):
[antani@nixos:~]$ /nix/store/wwkvnj972s80c835ssnci4f2sgzggrjc-flatpak-1.14.4/bin/flatpak override --show
[Context]
sockets=wayland

Sure.

flake.nix:

{
  description = "HTPC on NixOS";

  inputs = {
    nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
    nix-flatpak.url = "github:gmodena/nix-flatpak?ref=v0.3.0";
    home-manager = {
      url = "github:nix-community/home-manager/master";
      inputs.nixpkgs.follows = "nixpkgs";
    };
    disko = {
      url = "github:nix-community/disko";
      inputs.nixpkgs.follows = "nixpkgs";
    };
  };

  outputs = { nixpkgs, nix-flatpak, home-manager, ... }@attrs:
    let system = "x86_64-linux";
    in {
      nixosConfigurations = {
        # Build qcow2 images and run in VM
        qcow2 = nixpkgs.lib.nixosSystem {
          inherit system;
          modules = [
            nix-flatpak.nixosModules.nix-flatpak
            (import "${home-manager}/nixos")
            ./os/common.nix
            ./os/qcow2.nix
          ];
        };
        # htpc host
        htpc = nixpkgs.lib.nixosSystem {
          inherit system;
          specialArgs = attrs;
          modules = [
            nix-flatpak.nixosModules.nix-flatpak
            (import "${home-manager}/nixos")
            ./os/common.nix
            ./os/htpc.nix
          ];
        };
      };
    };
}

common.nix

{ pkgs, home-manager, ... }: {
...
  services = {
    fstrim.enable = true;
    openssh.enable = true;
    flatpak = {
      enable = true;
      update.onActivation = true; # Trigger update on system activation
      uninstallUnmanagedPackages = true;
      remotes = [{
        name = "flathub";
        location = "https://flathub.org/repo/flathub.flatpakrepo";
      }];
      packages = [
        {
          appId = "io.freetubeapp.FreeTube";
          origin = "flathub";
        }
        {
          appId = "org.mozilla.firefox";
          origin = "flathub";
        }
      ];
      overrides = {
        global = {
          # Force Wayland by default
          Context.sockets = ["wayland" "!x11" "!fallback-x11"];
        };
      };
    };
    pipewire = {
      enable = true;
      alsa.enable = true;
      pulse.enable = true;
    };
  };
}

I have just retried, and I am not sure what changed but the "overrides" shows now:
$ flatpak override --show
[Context]
sockets=!fallback-x11;!x11;wayland

But seems not applied for the application:
$ flatpak run io.freetubeapp.FreeTube --ozone-platform=wayland
<error>

$ flatpak --socket=wayland run io.freetubeapp.FreeTube --ozone-platform=wayland
<works as expected>

Sorry for wasting your time, seems a problem with FreeTube and running in a VM.
On bare-metal everything works as expected.
Thanks for this amazing project.

Yeah, this is still a problem.
The Context.filesystems overrides do absolutely nothing. I've tried reinstalling the flatpaks, still no overrides applied. It's unfortunate, but I've just resorted to writing them by file for the time being.


when starting nodeos for the first time, it creates corrupt block log if port already in use

If you have an error in your config.ini such that the port is already in use, then the blocks log is actually created corrupt and nodeos will never start unless you remove the corrupt blocks.
The startup sequence probably needs to be re-arranged to prevent this problem.
$ nodeos -c config/config.ini -l config/logging.json -d data --genesis-json=config/genesis.json
info  2019-01-20T16:20:45.098 thread-0  http_plugin.cpp:422           plugin_initialize    ] configured http to listen on <IP_ADDRESS>:8888
info  2019-01-20T16:20:45.098 thread-0  chain_plugin.cpp:335          plugin_initialize    ] initializing chain plugin
info  2019-01-20T16:20:45.098 thread-0  chain_plugin.cpp:616          plugin_initialize    ] Using genesis state provided in 'config/genesis.json'
warn  2019-01-20T16:20:45.098 thread-0  chain_plugin.cpp:618          plugin_initialize    ] Starting up fresh blockchain with provided genesis state.
info  2019-01-20T16:20:45.123 thread-0  net_plugin.cpp:2762           plugin_initialize    ] Initialize net plugin
info  2019-01-20T16:20:45.123 thread-0  net_plugin.cpp:2787           plugin_initialize    ] host: <IP_ADDRESS> port: 9875
info  2019-01-20T16:20:45.123 thread-0  net_plugin.cpp:2859           plugin_initialize    ] my node_id is f77f40f0fb07f4df8697244f903efd2c41b046177a5cd5079e2e7aadf3f8be69
info  2019-01-20T16:20:45.123 thread-0  http_plugin.cpp:377           operator()           ] configured http with Access-Control-Allow-Origin: *
error opening GELF socket to endpoint graylog.eosn.io:12201
info  2019-01-20T16:20:45.124 thread-0  main.cpp:107                  main                 ] nodeos version v1.6.0-rc2-16-g1630648ff
info  2019-01-20T16:20:45.124 thread-0  main.cpp:108                  main                 ] eosio root is /root/.local/share
info  2019-01-20T16:20:45.124 thread-0  main.cpp:109                  main                 ] nodeos using configuration file config/config.ini
info  2019-01-20T16:20:45.124 thread-0  main.cpp:110                  main                 ] nodeos data directory is data
info  2019-01-20T16:20:45.124 thread-0  http_plugin.cpp:486           plugin_startup       ] start listening for http requests
error 2019-01-20T16:20:45.124 thread-0  http_plugin.cpp:493           plugin_startup       ] http service failed to start: Address already in use
error 2019-01-20T16:20:45.132 thread-0  main.cpp:149                  main                 ] Address already in use

$ nano config/config.ini
[fixing the duplicate port error]
$ nodeos -c config/config.ini -l config/logging.json -d data --genesis-json=config/genesis.json
info  2019-01-20T16:20:59.618 thread-0  http_plugin.cpp:422           plugin_initialize    ] configured http to listen on <IP_ADDRESS>:8885
info  2019-01-20T16:20:59.618 thread-0  chain_plugin.cpp:335          plugin_initialize    ] initializing chain plugin
warn  2019-01-20T16:20:59.618 thread-0  chain_plugin.cpp:707          plugin_initialize    ] 3190000 block_log_exception: Block log exception
Block log was not setup properly.
    {}
    thread-0  block_log.cpp:537 extract_genesis_state
error 2019-01-20T16:20:59.618 thread-0  main.cpp:129                  main                 ] 3190000 block_log_exception: Block log exception
Block log was not setup properly.
    {}
    thread-0  block_log.cpp:537 extract_genesis_state
rethrow
    {}
    thread-0  chain_plugin.cpp:707 plugin_initialize

Now if you remove the contents of the data directory, it starts fine.

In order to focus our efforts on issues that are currently creating difficulty for the community we are closing tickets that were created prior to the EOSIO 2.0 release.  If you believe this issue is still relevant please feel free to reopen it or create a new one.  Thank you for your continued support of EOSIO!

The case of a port being already in use and creating a inconsistent data seems to work fine on 2.0.6


chore: remove notifee-json.gradle script

Good idea, forgot about this 😀 there's also types here: https://github.com/invertase/notifee/blob/master/packages/react-native/src/types/Module.ts#L605-L677

ah thanks. good catch on the types. will remove them too :)


Miscellaneous Improvements for SubFrames

Add miscellaneous improvements especially preparing for SubFrames.

:zap: Promote DataFrame#shape_str to public
:sparkles: Introduce Vector#concatenate
:zap: Add #numeric? in refinements of Array
:recycle: Rename Array refinements to the same name as Vector
:butterfly: Fix Vector#shift when boolean Vector
:zap: Add Vector#cumulative_sum_checked and #cumsum

It will often be used in subframe operations.

:zap: Add Vector#resolve method

It is convenient to create a same type Vector of self.

:zap: Add DataFrame#tdra method

A shortcut for #tdr(:all)

:zap: Add #expand as an alias for Vector#propagate
:zap: Add #glimpse as an alias for DataFrame#tdr

:shirt: Unify style of MethodCallIndentation as relative to reciever

:shirt: Unify style of MethodCallIndentation as relative to reciever

Change indentation style of method call to relative to receiver style.baseframe
  .pick(group_keys)
  .slice(offset_indices)
  .assign(aggregator)


Show expense report in LHN if user doesn't have access to parent policyChat (removed manager condition)

Details

This is a follow-up to https://github.com/Expensify/App/pull/48661, where I'm realizing we don't even care if the user is the report manager -> If the user doesn't have access to the expense report's parent report, we want to show this report in the LHN so the user always has access somehow
Fixed Issues
$ https://github.com/Expensify/App/issues/49318
$ https://github.com/Expensify/Expensify/issues/422963
Tests

Create a Control policy in OldDot, make sure it has policy expense chats enabled, make sure it has "Advanced Approvals" enabled in members tab

To enable policy expense chats, enter this into the console on the policy screen in OldDot: p = Policy.getCurrent(); p.policy.isPolicyExpenseChatEnabled = "true"; p.save();

Either In OldDot or NewDot, invite 3 people as users (non-admins): A submitter and 2 approvers
In members tab in OldDot, make sure the submitter's submitsTo is set to Approver 1. Approver 1 and Approver 2 should NOT have a forwardsTo set.

Note: You can also do this flow in NewDot if preferred

As the submitter, log in to NewDot & go to the workspace chat that was just created for you

Submit an expense and submit the report to Approver 1
Keep this tab open! Keep track of the reportID so you have it for later.

In a new tab / device, as the policy owner, go to the approval workflow settings (either NewDot or OldDot)

Change the submitter's submitsTo to Approver 2

Verify Approver 1 no longer has access to the workspace chat
Also Verify that Approver 1 can now see the expense report in the LHN
As Approver 1, Open the previously created report
Verify Approver 1 sees GBR to that report in the LHN & that Approver 1 sees the Approve button in the report header
Click Approve, make sure it works w/out errors
Click into a different report, verify the expense report still shows up in Approver 1's LHN

[ ] Verify that no errors appear in the JS console

Offline tests
N/A - the above steps require internet
QA Steps
Same as above

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[ ] I linked the correct issue in the ### Fixed Issues section above
[ ] I wrote clear testing steps that cover the changes made in this PR

[ ] I added steps for local testing in the Tests section
[ ] I added steps for the expected offline behavior in the Offline steps section
[ ] I added steps for Staging and/or Production testing in the QA steps section
[ ] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[ ] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[ ] I included screenshots or videos for tests on all platforms
[ ] I ran the tests on all platforms & verified they passed on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[ ] I followed proper code patterns (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[ ] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I followed the guidelines as stated in the Review Guidelines
[ ] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] I verified that if a function's arguments changed that all usages have also been updated correctly
[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@jjcoffee - this PR is ready for review - it's only a slight modification to previous PRs so I haven't thoroughly tested 😬  but I do plan to test on Monday 🙏

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@Beamanator It seems like the expense report disappears from the LHN if I don't keep it open (as approver 1) when switching the submitsTo to approver 2. Signing out and back in fixes this (and all previous test reports "come back", so I don't know if there's maybe a pending BE change for this?
https://github.com/user-attachments/assets/ae122342-709f-477d-85f6-63d724141ed9

@jjcoffee ooh yes those are very good points - at this exact moment we are still pending those backend changes, so as long as the front end works great i think we're good to go with this PR 🙏

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


Docs.MS Release Updates for azure_mgmt_appconfiguration

Update docs metadata and targeting for release of azure_mgmt_appconfiguration

Docs Build status updates of commit ab9a911:
:clock10: Full build: the average full build time is 172 min(s) 21 sec(s), this is based on the last 542 build(s) for this repository.

Docs Build status updates of commit ab9a911:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/mgmt-appconfiguration-readme.md
:warning:Warning
View (azure-python)
Details

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.yml
:warning:Warning
View (azure-python-preview)
Details

ci-configs/packages-latest.json
:white_check_mark:Succeeded

docs-ref-services/mgmt-appconfiguration-readme.md

Line 21: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 27: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.yml

[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.call_http) has already been defined in preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.call_http.yml.
[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.continue_as_new) has already been defined in preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.continue_as_new.yml.
[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.new_uuid) has already been defined in preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.new_uuid.yml.
[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.task_all) has already been defined in preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.task_all.yml.
[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.task_any) has already been defined in preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.task_any.yml.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 708b232:
:clock10: Full build: the average full build time is 178 min(s) 52 sec(s), this is based on the last 568 build(s) for this repository.

Docs Build status updates of commit 708b232:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/mgmt-keyvault-readme.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/mgmt-automanage-readme-pre.md
:warning:Warning
View (azure-python) View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.yml
:warning:Warning
View (azure-python-preview)
Details

docs-ref-services/mgmt-keyvault-readme.md

Line 21: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 27: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.

docs-ref-services/mgmt-automanage-readme-pre.md

Line 21: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 21: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 27: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 27: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.yml

[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.call_http) has already been defined in preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.call_http.yml.
[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.continue_as_new) has already been defined in preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.continue_as_new.yml.
[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.new_uuid) has already been defined in preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.new_uuid.yml.
[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.task_all) has already been defined in preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.task_all.yml.
[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.task_any) has already been defined in preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.task_any.yml.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Upgraded to V4, got theme.spacing is not a function error?

I just upgraded to V4.5 from V3 following the upgrade guide. I updated all the theme.spacing.unit to theme.spacing(x). But then I got the above error.
Note: I have everything wrapped inside MuiThemeProvider with my custom theme created using createMuiTheme
import 'react-app-polyfill/ie11';
import 'react-app-polyfill/stable';
import React from 'react';
import ReactDOM from 'react-dom';
import './index.css';
import App from './AppContainer.js';
import * as serviceWorker from './serviceWorker';
import configureStore from './configureStore';
import { Provider } from 'react-redux';
import {MuiThemeProvider} from '@material-ui/core/styles';
import {defaultTheme} from './theme.dsdefault.js';

const store = configureStore();

ReactDOM.render(
    <MuiThemeProvider theme={defaultTheme}>
        <Provider store={store}>
            <App />
        </Provider>
    </MuiThemeProvider>,
    document.getElementById('root')

import {createMuiTheme} from '@material-ui/core/styles';

export const defaultTheme = createMuiTheme({
....
});

@82949712 You might still have code "unmigrated" code. We can't help without a reproduction.


displayLedMatrix with displayInterval of 0 should not time-out

currently it is disappearing after some ~30s

25.5s to be more exact
This is actually a firmware issue and the limit is there to prevent battery draining


trouble getting this to work with jsx

This is my config:
  {
    'nvim-treesitter/nvim-treesitter',
    dependencies = {
      'JoosepAlviste/nvim-ts-context-commentstring',
    },

    build = function()
      pcall(require('nvim-treesitter.install').update { with_sync = true })
    end,

    config = function()
      require('nvim-treesitter.configs').setup {
        ensure_installed = {
          'json', 'query', 'tsx', 'yaml', 'c', 'html', 'javascript', 'lua', 'cpp', 'go', 'lua', 'python', 'rust', 'typescript', 'vimdoc', 'vim', 'regex', 'bash', 'css', 'scss',
        },

        -- Install parsers synchronously (only applied to `ensure_installed`)
        sync_install = false,

        -- Automatically install missing parsers when entering buffer
        -- Recommendation: set to false if you don't have `tree-sitter` CLI installed locally
        auto_install = false,

        highlight = {
          enable = true,

          ------------------------------------------------------------------------------
          -- !!! THIS IS WHAT MAKES MARKDOWN HEADINGS H1 ABLE TO BE DIFFERENT COLORS: !!
          ------------------------------------------------------------------------------
          disable = { "markdown" },

          additional_vim_regex_highlighting = false,

        },

        context_commentstring = {
          enable = true,
        },

      }
    end
  },

Is there something I am missing?

Hey @michael-odonovan! The configuration seems correct. Here are a few questions and things to try:

Which commenting plugin are you using? How are you checking whether or not this plugin works?
Which file type are you testing this on?
It looks like you're using the default CursorHold autocommand. Have you configured your updatetime to be smaller? E.g., vim.opt.updatetime = 100
To check if this plugin is set up correctly, you can try running :=require('ts_context_commentstring.internal').calculate_commentstring(). This should return the correct commentstring based on your cursor location.

Glad to hear it! Although it should still work without the integration. Oh well 😄


Tests should create contracts with host functions

What problem does your feature solve?
Tests currently create contracts by directly manipulating ledger state instead of using the appropriate host functions. For example
https://github.com/stellar/rs-soroban-env/blob/db1b4764fec63844677ba2ebc3c1305ff4e0c229/soroban-env-host/src/test/util.rs#L60-L78
What would you like to see?
Tests should create contracts by using appropriate host functions.
What alternatives are there?
TODO

Closing because we now use invoke_function to create contracts in tests - https://github.com/stellar/rs-soroban-env/blob/d803b0922d1d9eb4d3cfde5e6d574c7776c23388/soroban-env-host/src/test/util.rs#L161.


Unable to resolve name traci.start

I have followed the steps provided in the manual to download and install traci4matlab, but whenever I run traci_test.m, I get the below error:
`Unable to resolve the name traci.start.
Error in traci_test (line 24)
[traciVersion,sumoVersion] = traci.init();`
Any advice on how to resolve this?
Thanks

I have a similar problem
`Unable to resolve the name 'traci.start'.
Error in traci_test (line 22)
[traciVersion,sumoVersion] = traci.start(['sumo -c ' '"' scenarioPath '"']);`
Any idea how to solve it ?
TIA


Not working in node 0.12.7

I have tried to run the module in an node v0.12.7 and all tests failed.
It seems that the problem is in lines 195-196 sftp-packet.ts
if ((<any>Buffer)._charsWritten != charLength) //WEB: // removed
   throw new Error("Not enough space in the buffer");

I have set up a docker container with node v0.10.40 and it works perfectly there.
I think https://github.com/joyent/node/commit/526c54c9#commitcomment-1143045 might prove somewhat useful.

Thanks! Looks like node devs removed _charsWritten because it was "never read from" (which seems obvious if it was intended to be used by third-party code), thus making it impossible to determine whether the preceding write call properly wrote all the string characters... Fortunately, I already had a replacement function in the web-based version. Using that with node as well solves the issue. The current version should be compatible with node v0.12.x.

Lukaaash, thanks for solving the problem.
But there is still another problem when running in node v0.12. In 0.10 all tests pass, but in 0.12 those with "no-path" apparently throw different errors.
Connection accepted.
    ✓ flags
    ✓ callback(fail)
    ✓ realpath('.')
    1) realpath(no-path)
    ✓ realpath(path)
    2) mkdir(no-path)
    ✓ mkdir(path)
    3) rmdir(no-path)
    ✓ rmdir(path)
    4) opendir(no-path)
    ✓ opendir(path)/readdir/close (109ms)
    5) rename(no-path, path2)
    6) rename(path1, no-path)
    ✓ rename(path1, path2)
    7) unlink(no-path)
    ✓ unlink(path)
    8) open(no-path, 'r+')
    ✓ open(path, 'r+')/read/close
    ✓ open(no-path, 'w+')/write/close
    ✓ read(no-handle)
    ✓ write(no-handle)
    ✓ close(no-handle)
    ✓ fstat(no-handle)
    9) stat(no-path)
    ✓ stat(path)
    10) lstat(no-path)
    ✓ lstat(path)
    ✓ fstat(closed-handle)
    ✓ fstat(handle)
    11) setstat(no-path)
    ✓ setstat(path)
    ✓ open(path)/fsetstat

  32 passing (336ms)
  11 failing

  1) Basic Tests realpath(no-path):

      AssertionError: Unexpected error code: EFAILURE
      + expected - actual

      -EFAILURE
      +ENOENT

      at error (tests/core-tests.js:62:16)
      at Client.<anonymous> (tests/core-tests.js:126:55)
      at finish (lib/util.js:57:26)
      at SftpClientCore.checkResponse (lib/sftp-client.js:414:17)
      at SftpClientCore.parsePath (lib/sftp-client.js:441:19)
      at SftpClientCore._process (lib/sftp-client.js:139:32)
      at WebSocketChannel.onmessage (lib/sftp-client.js:534:22)
      at WebSocket.<anonymous> (lib/channel-ws.js:29:23)
      at readableAddChunk (_stream_readable.js:163:16)
      at Socket.Readable.push (_stream_readable.js:126:10)
      at TCP.onread (net.js:538:20)

  2) Basic Tests mkdir(no-path):

      AssertionError: Unexpected error code: EFAILURE
      + expected - actual

      -EFAILURE
      +ENOENT

      at error (tests/core-tests.js:62:16)
      at Client.<anonymous> (tests/core-tests.js:136:52)
      at finish (lib/util.js:57:26)
      at SftpClientCore.checkResponse (lib/sftp-client.js:414:17)
      at SftpClientCore.parseStatus (lib/sftp-client.js:423:19)
      at SftpClientCore._process (lib/sftp-client.js:139:32)
      at WebSocketChannel.onmessage (lib/sftp-client.js:534:22)
      at WebSocket.<anonymous> (lib/channel-ws.js:29:23)
      at readableAddChunk (_stream_readable.js:163:16)
      at Socket.Readable.push (_stream_readable.js:126:10)
      at TCP.onread (net.js:538:20)

  3) Basic Tests rmdir(no-path):

      AssertionError: Unexpected error code: EFAILURE
      + expected - actual

      -EFAILURE
      +ENOENT

      at error (tests/core-tests.js:62:16)
      at Client.<anonymous> (tests/core-tests.js:148:52)
      at finish (lib/util.js:57:26)
      at SftpClientCore.checkResponse (lib/sftp-client.js:414:17)
      at SftpClientCore.parseStatus (lib/sftp-client.js:423:19)
      at SftpClientCore._process (lib/sftp-client.js:139:32)
      at WebSocketChannel.onmessage (lib/sftp-client.js:534:22)
      at WebSocket.<anonymous> (lib/channel-ws.js:29:23)
      at readableAddChunk (_stream_readable.js:163:16)
      at Socket.Readable.push (_stream_readable.js:126:10)
      at TCP.onread (net.js:538:20)

  4) Basic Tests opendir(no-path):

      AssertionError: Unexpected error code: EFAILURE
      + expected - actual

      -EFAILURE
      +ENOENT

      at error (tests/core-tests.js:62:16)
      at Client.<anonymous> (tests/core-tests.js:161:62)
      at finish (lib/util.js:57:26)
      at SftpClientCore.checkResponse (lib/sftp-client.js:414:17)
      at SftpClientCore.parseHandle (lib/sftp-client.js:435:19)
      at SftpClientCore._process (lib/sftp-client.js:139:32)
      at WebSocketChannel.onmessage (lib/sftp-client.js:534:22)
      at WebSocket.<anonymous> (lib/channel-ws.js:29:23)
      at readableAddChunk (_stream_readable.js:163:16)
      at Socket.Readable.push (_stream_readable.js:126:10)
      at TCP.onread (net.js:538:20)

  5) Basic Tests rename(no-path, path2):

      AssertionError: Unexpected error code: EFAILURE
      + expected - actual

      -EFAILURE
      +ENOENT

      at error (tests/core-tests.js:62:16)
      at Client.<anonymous> (tests/core-tests.js:195:61)
      at finish (lib/util.js:57:26)
      at SftpClientCore.checkResponse (lib/sftp-client.js:414:17)
      at SftpClientCore.parseStatus (lib/sftp-client.js:423:19)
      at SftpClientCore._process (lib/sftp-client.js:139:32)
      at WebSocketChannel.onmessage (lib/sftp-client.js:534:22)
      at WebSocket.<anonymous> (lib/channel-ws.js:29:23)
      at readableAddChunk (_stream_readable.js:163:16)
      at Socket.Readable.push (_stream_readable.js:126:10)
      at TCP.onread (net.js:538:20)

  6) Basic Tests rename(path1, no-path):

      AssertionError: Unexpected error code: EFAILURE
      + expected - actual

      -EFAILURE
      +ENOENT

      at error (tests/core-tests.js:62:16)
      at Client.<anonymous> (tests/core-tests.js:202:61)
      at finish (lib/util.js:57:26)
      at SftpClientCore.checkResponse (lib/sftp-client.js:414:17)
      at SftpClientCore.parseStatus (lib/sftp-client.js:423:19)
      at SftpClientCore._process (lib/sftp-client.js:139:32)
      at WebSocketChannel.onmessage (lib/sftp-client.js:534:22)
      at WebSocket.<anonymous> (lib/channel-ws.js:29:23)
      at readableAddChunk (_stream_readable.js:163:16)
      at Socket.Readable.push (_stream_readable.js:126:10)
      at TCP.onread (net.js:538:20)

  7) Basic Tests unlink(no-path):

      AssertionError: Unexpected error code: EFAILURE
      + expected - actual

      -EFAILURE
      +ENOENT

      at error (tests/core-tests.js:62:16)
      at Client.<anonymous> (tests/core-tests.js:219:53)
      at finish (lib/util.js:57:26)
      at SftpClientCore.checkResponse (lib/sftp-client.js:414:17)
      at SftpClientCore.parseStatus (lib/sftp-client.js:423:19)
      at SftpClientCore._process (lib/sftp-client.js:139:32)
      at WebSocketChannel.onmessage (lib/sftp-client.js:534:22)
      at WebSocket.<anonymous> (lib/channel-ws.js:29:23)
      at readableAddChunk (_stream_readable.js:163:16)
      at Socket.Readable.push (_stream_readable.js:126:10)
      at TCP.onread (net.js:538:20)

  8) Basic Tests open(no-path, 'r+'):

      AssertionError: Unexpected error code: EFAILURE
      + expected - actual

      -EFAILURE
      +ENOENT

      at error (tests/core-tests.js:62:16)
      at Client.<anonymous> (tests/core-tests.js:232:65)
      at finish (lib/util.js:57:26)
      at SftpClientCore.checkResponse (lib/sftp-client.js:414:17)
      at SftpClientCore.parseHandle (lib/sftp-client.js:435:19)
      at SftpClientCore._process (lib/sftp-client.js:139:32)
      at WebSocketChannel.onmessage (lib/sftp-client.js:534:22)
      at WebSocket.<anonymous> (lib/channel-ws.js:29:23)
      at readableAddChunk (_stream_readable.js:163:16)
      at Socket.Readable.push (_stream_readable.js:126:10)
      at TCP.onread (net.js:538:20)

  9) Basic Tests stat(no-path):

      AssertionError: Unexpected error code: EFAILURE
      + expected - actual

      -EFAILURE
      +ENOENT

      at error (tests/core-tests.js:62:16)
      at Client.<anonymous> (tests/core-tests.js:312:58)
      at finish (lib/util.js:57:26)
      at SftpClientCore.checkResponse (lib/sftp-client.js:414:17)
      at SftpClientCore.parseAttribs (lib/sftp-client.js:428:19)
      at SftpClientCore._process (lib/sftp-client.js:139:32)
      at WebSocketChannel.onmessage (lib/sftp-client.js:534:22)
      at WebSocket.<anonymous> (lib/channel-ws.js:29:23)
      at readableAddChunk (_stream_readable.js:163:16)
      at Socket.Readable.push (_stream_readable.js:126:10)
      at TCP.onread (net.js:538:20)

  10) Basic Tests lstat(no-path):

      AssertionError: Unexpected error code: EFAILURE
      + expected - actual

      -EFAILURE
      +ENOENT

      at error (tests/core-tests.js:62:16)
      at Client.<anonymous> (tests/core-tests.js:326:59)
      at finish (lib/util.js:57:26)
      at SftpClientCore.checkResponse (lib/sftp-client.js:414:17)
      at SftpClientCore.parseAttribs (lib/sftp-client.js:428:19)
      at SftpClientCore._process (lib/sftp-client.js:139:32)
      at WebSocketChannel.onmessage (lib/sftp-client.js:534:22)
      at WebSocket.<anonymous> (lib/channel-ws.js:29:23)
      at readableAddChunk (_stream_readable.js:163:16)
      at Socket.Readable.push (_stream_readable.js:126:10)
      at TCP.onread (net.js:538:20)

  11) Basic Tests setstat(no-path):

      AssertionError: Unexpected error code: EFAILURE
      + expected - actual

      -EFAILURE
      +ENOENT

      at error (tests/core-tests.js:62:16)
      at Client.<anonymous> (tests/core-tests.js:360:68)
      at finish (lib/util.js:57:26)
      at SftpClientCore.checkResponse (lib/sftp-client.js:414:17)
      at SftpClientCore.parseStatus (lib/sftp-client.js:423:19)
      at SftpClientCore._process (lib/sftp-client.js:139:32)
      at WebSocketChannel.onmessage (lib/sftp-client.js:534:22)
      at WebSocket.<anonymous> (lib/channel-ws.js:29:23)
      at readableAddChunk (_stream_readable.js:163:16)
      at Socket.Readable.push (_stream_readable.js:126:10)
      at TCP.onread (net.js:538:20)

Actually, the node 0.12.x compatibility commit should fix that as well - it looks like node started reporting a different error code for ENOENT on Windows (see the change in src/lib/sftp-server.ts file).
Please make sure you are testing with the latest version, and if the tests still fail, let me know. The server-side at least needs a better debug logging to make it possible to easily tell what is going on.

Lukaaash,
The latest commit is this one, right?
commit 0b10883a36af55e46c2e04deb07851c8a3fe3ee5
Author: Lukas Pokorny<EMAIL_ADDRESS>Date:   Sun Aug 30 20:58:41 2015 +0200

Converted gulpfile.ts to gulpfile.js - needed for 'gulp' to work instantly

I've run the tests inside a docker container with node 0.12.7.
Just tried again and same results :/
(and thanks for the gulpfile.js, before I had to run tsc and then gulp)

Found the issue! It turns out that node 0.12.x uses yet another errno for ENOENT on Linux... So that's three possible values now: https://github.com/lukaaash/sftp-ws/commit/b3f2e58242831b2cdb2a5759b8889a9d94ec38c5
Also added better server-side logging, it might be useful next time :-)


MMS with Copilot?

Hello!
I see that there was a previous PR https://github.com/sfreiberg/gotwilio/pull/44 that added functionality for MMS with Copilot, along with a LookupPhone function, but was ultimately closed. I am in need of MMS usage over Copilot, and would like to add just the SendMMSWithCopilot function that was proposed as part of the PR above. Please let me know if there's any more context here about that decision; otherwise, look out for a PR from me coming soon!
Thank you, Andrew

Fixed in #69.


Is it possible to add a 'type' property in fields?

for indicating whether is field is password, text, textrarea etc?
it's useful for generating markups.

That is currently not supported. But you're welcome to write up a proposal as to how it might be accomplished.

Is it needed? I just pass a prop to the form with data derived from the
same source I used to generate the fields list.
I have things like label, type and description.
I loop over this list, create a widget, lookup the appropriate field and
pass that as well
On 11 February 2016 at 08:20, Erik Rasmussen<EMAIL_ADDRESS>wrote:

That is currently not supported. But you're welcome to write up a proposal
as to how it might be accomplished.
—
Reply to this email directly or view it on GitHub
https://github.com/erikras/redux-form/issues/631#issuecomment-182586602.


Increase the timeout for TableSizeReaderTest.

The test starts servers within process which timeout sometimes on the travis
machine. Increasing the timeout for requests. Increased timeout should not impact
test runtime adversely on fast platforms.

LGTM


Motor G7 biometric doesn't work

Moto G7 power
Vendor Metro by T-Mobile
Android 10

Tested on Moto Z3 Play and Razr 2019 - seems like all ok, even FaceUnlock api detected.
Waiting for Moto G7 users

Seems like solved


[FLINK-25744] Support native savepoints

What is the purpose of the change
We introduce a savepoint type flag both to the CLI and REST API that
controls the binary format of the savepoint to take. Native savepoints
are taken in the state backend specific binary format. They can be
faster to take and restore from, but they do not support e.g. changing
the state backend.
This commit does not support RocksDB incremental savepoints yet. When
incremental savepoints are configured, native savepoints will fail.
Brief change log
See commit log
Verifying this change
Added tests in SavepointFormatITCase
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Hey, @akalash I added a single commit for documentation of the savepoint format. Could you take a look at #cdc389d as well?


Laravel unique key extractor and PDO type exceptions

I had to make the following changes to get this working with Laravel. Specifically changing ?string to ?Builder.
diff vendor/fab2s/yaetl/src/Extractors/PdoUniqueKeyExtractor.php ../YaEtl-2.0.0/src/Extractors/PdoUniqueKeyExtractor.php
14d13
< use Illuminate\Database\Query\Builder;
29c28
<      * @param Builder|null  $extractQuery

 * @param string|null  $extractQuery

53c52
<     public function __construct(\PDO $pdo, ?Builder $extractQuery = null, $uniqueKey = 'id')

public function __construct(\PDO $pdo, ?string $extractQuery = null, $uniqueKey = 'id')

126a126

diff vendor/fab2s/yaetl/src/Extractors/UniqueKeyExtractorAbstract.php ../YaEtl-2.0.0/src/Extractors/UniqueKeyExtractorAbstract.php
14d13
< use Illuminate\Database\Query\Builder;
94c93
<      * @param Builder|null  $extractQuery

 * @param string|null  $extractQuery

117c116
<     public function __construct(?Builder $extractQuery = null, $uniqueKeySetup = 'id')

public function __construct(?string $extractQuery = null, $uniqueKeySetup = 'id')

Hello,
You are right, this one does not work as expected. Thanks for reporting, I will soon update it.

I just had a look and it seems to me that the best strategy would be to just call setExtractQuery before the parent call and in the constructor like it is done with the regular LaravelExtractor. I cannot test right now, but replacing :
    public function __construct(Builder $extractQuery, $uniqueKey = 'id')
    {
        parent::__construct($extractQuery->getConnection()->getPdo(), $extractQuery, $uniqueKey);
    }

with
   public function __construct(Builder $extractQuery, $uniqueKey = 'id')
   {
       $this->setExtractQuery($extractQuery);

       parent::__construct($extractQuery->getConnection()->getPdo(), null, $uniqueKey);
   }

in src/Laravel/Extractors/UniqueKeyExtractor.php should do it.

Thank you. I was considering forking to fix this, but it looks like you are actively maintaining the project. Appreciate it!


query string parameters support in urlFor

tests need more fixes

Sorry the PR seem to have more than the urlFor fix, can we strip this back to just the urlFor fix please

oh sorry, i was try to unserstand the error in travis, i forgot to close it. Are those other build issues resolved?


update text

The location of scopes changed in the portal + View Channels was renamed to Read Messages/View Channels

Thank you, included it in the updated docs.


Alternative instance MonadState s (ContT r m)

I notice that instead of requiring MonadState s m, it's possible to require MonadReader s m:
instance MonadReader s m => MonadState s (ContT r m) where
    get = ContT (\smr -> ask >>= smr)
    put s = ContT (\umr -> local (\_ -> s) (umr ()))

Is this preferable?

This would violate user expectation somewhat severely.

Just as a datapoint, it happened to be the instance I wanted, inasmuch as MonadReader is "simpler" than MonadState: indeed you can kinda/sorta make MonadReader a superclass of MonadState, though I'm not actually proposing this.
instance MonadReader s m where
    ask = get
    -- | imperfect, but you get the idea
    local ss ma = do
        s <- get
        put (ss s)
        a <- ma
        put s
        return a

Reader and State do have a sort of incestuous relationship.
Codensity (Reader s) ~ State s, because State is made up of the composition of Reader s and its adjoint functor: (, s). Using this you can always embed reader effects into State.
In an almost equally universal manner you can embed writer effects into state, but there are some minor complications on that front, and while the reader embedding costs you commutativity the latter costs you productivity.

Would it be worth the trouble to come up with a ContT wrapper offering this instance?

Possibly. If so it should belong in transformers though, not mtl, and then mtl would inherit support for it.


add model and serial to device listing

In order to support the Home Assistant Entity Registry we need to be able to construct a stable identifier value for every device. I don't know the details of how Lutron issues serial numbers, but I assume a combination of model ID and serial number will be unique within every home.

Related: home-assistant/home-assistant#14013

Wondering, isn't the device ID already stable ?

There are probably a few ways it could change, such as if you got a new bridge or did a factory reset or maybe even some firmware updates. The model and serial number of the switches themselves should be more reliable.


Load config from /data/data

Postfix removed in latest rev.
However need some universal way for android for searching configs.