anaconda upload fails to upload package from Win64

While trying to upload a package with anaconda upload an error occurs:
D:\Anaconda\conda-bld\win-64>anaconda upload cchardet-1.0.0-py27_0.tar.bz2
Using anaconda-server api site https://api.anaconda.org
detecting package type ...
conda
extracting package attributes for upload ...
done

Uploading file User/cchardet/1.0.0/win-64/cchardet-1.0.0-py27_0.tar.bz2 ...
 uploaded 0 of 80Kb: 0.00% ETA: 0.0 minutes[TypeError] cannot make memory view because object does not have the buffer interface
Traceback (most recent call last):
  File "D:\Anaconda\Scripts\anaconda-script.py", line 5, in <module>
	sys.exit(main())
  File "D:\Anaconda\lib\site-packages\binstar_client\scripts\cli.py", line 93, in main
	description=__doc__, version=version)
  File "D:\Anaconda\lib\site-packages\binstar_client\scripts\cli.py", line 75, in binstar_main
	return args.main(args)
  File "D:\Anaconda\lib\site-packages\binstar_client\commands\upload.py", line 203, in main
	callback=upload_print_callback(args))
  File "D:\Anaconda\lib\site-packages\binstar_client\__init__.py", line 425, in upload
	s3res = requests.post(s3url, data=data_stream, verify=self.session.verify, timeout=10 * 60 * 60, headers=headers)
  File "D:\Anaconda\lib\site-packages\requests\api.py", line 109, in post
	return request('post', url, data=data, json=json, **kwargs)
  File "D:\Anaconda\lib\site-packages\requests\api.py", line 50, in request
	response = session.request(method=method, url=url, **kwargs)
  File "D:\Anaconda\lib\site-packages\requests\sessions.py", line 468, in request
	resp = self.send(prep, **send_kwargs)
  File "D:\Anaconda\lib\site-packages\requests\sessions.py", line 576, in send
	r = adapter.send(request, **kwargs)
  File "D:\Anaconda\lib\site-packages\requests\adapters.py", line 370, in send
	timeout=timeout
  File "D:\Anaconda\lib\site-packages\requests\packages\urllib3\connectionpool.py", line 559, in urlopen
	body=body, headers=headers)
  File "D:\Anaconda\lib\site-packages\requests\packages\urllib3\connectionpool.py", line 353, in _make_request
	conn.request(method, url, **httplib_request_kw)
  File "D:\Anaconda\lib\httplib.py", line 1053, in request
	self._send_request(method, url, body, headers)
  File "D:\Anaconda\lib\httplib.py", line 1093, in _send_request
	self.endheaders(body)
  File "D:\Anaconda\lib\httplib.py", line 1049, in endheaders
	self._send_output(message_body)
  File "D:\Anaconda\lib\httplib.py", line 897, in _send_output
	self.send(message_body)
  File "D:\Anaconda\lib\httplib.py", line 866, in send
	self.sock.sendall(datablock)
  File "D:\Anaconda\lib\site-packages\requests\packages\urllib3\contrib\pyopenssl.py", line 216, in sendall
	data = memoryview(data)
TypeError: cannot make memory view because object does not have the buffer interface

Current conda install:
			 platform : win-64
		conda version : 3.18.3
  conda-build version : 1.18.1
	   python version : 2.7.10.final.0
	 requests version : 2.8.1
	 root environment : D:\Anaconda  (writable)
  default environment : D:\Anaconda
	 envs directories : D:\Anaconda\envs
		package cache : D:\Anaconda\pkgs
		 channel URLs : https://repo.continuum.io/pkgs/free/win-64/
						https://repo.continuum.io/pkgs/free/noarch/
						https://repo.continuum.io/pkgs/pro/win-64/
						https://repo.continuum.io/pkgs/pro/noarch/
						https://conda.anaconda.org/User/win-64/
						https://conda.anaconda.org/User/noarch/
		  config file : C:\Users\User\.condarc
	is foreign system : False

@wikiped the looks like it is coming from the requests library. What version of requests do you have installed? (use conda list).  I will try and reproduce this error.

requests version : 2.8.1 (latest)

I thought so too...
So reinstalled it, but still getting error.

@wikiped can you try after downgrading requests:
conda install requests=2.7

Downgraded requests to 2.7 and upload works fine again without any errors.

Thanks @wikiped I don't think that the root error is fixed. I have had this error with requests 2.7 as well.  We are still working on a permanent fix.

kennethreitz/requests#2818
shazow/urllib3#719
Based on these two issues, either this will be resolved when a new version of requests is released with an upgraded urllib3 that has the memoryview call removed, or we will have to identify where we are letting unicode objects into the requests api.

To reproduce on OS X: conda install ndg-httpsclient pyasn1 PyOpenSSL and then try to upload a package.

This will make it into the next release. We will close the issue when that release makes it out.

This issue has been fixed in the latest release. There is still an outstanding issue with requests 2.8, but they are working on releasing 2.9, and for now you can downgrade to 2.7.

This is happening again in the osx worker
1254[Build Targets]
1255anaconda  -q -t $TOKEN upload --force --user Anaconda-Notebook --package nbwrapper  --channel dev /Users/binstar/miniconda/conda-bld/osx-64/*.tar.bz2 --build-id 5.2
1256Using anaconda-server api site https://api.anaconda.org
1257[WARNING] Distribution osx-64/nbwrapper-0.0.1dev-py27_0.tar.bz2 already exists ... removing
1258[ERROR]
1259Traceback (most recent call last):
1260  File "/Users/binstar/miniconda/bin/anaconda", line 6, in <module>
1261    sys.exit(main())
1262  File "/Users/binstar/miniconda/lib/python2.7/site-packages/binstar_client/scripts/cli.py", line 82, in main
1263    description=__doc__, version=version)
1264  File "/Users/binstar/miniconda/lib/python2.7/site-packages/binstar_client/scripts/cli.py", line 64, in binstar_main
1265    return args.main(args)
1266  File "/Users/binstar/miniconda/lib/python2.7/site-packages/binstar_client/commands/upload.py", line 203, in main
1267    callback=upload_print_callback(args))
1268  File "/Users/binstar/miniconda/lib/python2.7/site-packages/binstar_client/__init__.py", line 425, in upload
1269    s3res = requests.post(s3url, data=data_stream, verify=self.session.verify, timeout=10 * 60 * 60, headers=headers)
1270  File "/Users/binstar/miniconda/lib/python2.7/site-packages/requests/api.py", line 109, in post
1271    return request('post', url, data=data, json=json, **kwargs)
1272  File "/Users/binstar/miniconda/lib/python2.7/site-packages/requests/api.py", line 50, in request
1273    response = session.request(method=method, url=url, **kwargs)
1274  File "/Users/binstar/miniconda/lib/python2.7/site-packages/requests/sessions.py", line 468, in request
1275    resp = self.send(prep, **send_kwargs)
1276  File "/Users/binstar/miniconda/lib/python2.7/site-packages/requests/sessions.py", line 576, in send
1277    r = adapter.send(request, **kwargs)
1278  File "/Users/binstar/miniconda/lib/python2.7/site-packages/requests/adapters.py", line 370, in send
1279    timeout=timeout
1280  File "/Users/binstar/miniconda/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py", line 559, in urlopen
1281    body=body, headers=headers)
1282  File "/Users/binstar/miniconda/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py", line 353, in _make_request
1283    conn.request(method, url, **httplib_request_kw)
1284  File "/Users/binstar/miniconda/lib/python2.7/httplib.py", line 1053, in request
1285    self._send_request(method, url, body, headers)
1286  File "/Users/binstar/miniconda/lib/python2.7/httplib.py", line 1093, in _send_request
1287    self.endheaders(body)
1288  File "/Users/binstar/miniconda/lib/python2.7/httplib.py", line 1049, in endheaders
1289    self._send_output(message_body)
1290  File "/Users/binstar/miniconda/lib/python2.7/httplib.py", line 897, in _send_output
1291    self.send(message_body)
1292  File "/Users/binstar/miniconda/lib/python2.7/httplib.py", line 866, in send
1293    self.sock.sendall(datablock)
1294  File "/Users/binstar/miniconda/lib/python2.7/site-packages/requests/packages/urllib3/contrib/pyopenssl.py", line 216, in sendall
1295    data = memoryview(data)
1296TypeError: cannot make memory view because object does not have the buffer interface
1297command exited with status 1

@malev - in certain scenarios, there's a workaround - can you check with
Derek
On Mon, Dec 7, 2015 at 3:40 PM, Marcos Vanetta<EMAIL_ADDRESS>wrote:

This is happening again in the osx worker
1254[Build Targets]
1255anaconda  -q -t $TOKEN upload --force --user Anaconda-Notebook --package nbwrapper  --channel dev /Users/binstar/miniconda/conda-bld/osx-64/*.tar.bz2 --build-id 5.2
1256Using anaconda-server api site https://api.anaconda.org
1257[WARNING] Distribution osx-64/nbwrapper-0.0.1dev-py27_0.tar.bz2 already exists ... removing
1258[ERROR]
1259Traceback (most recent call last):
1260  File "/Users/binstar/miniconda/bin/anaconda", line 6, in
1261    sys.exit(main())
1262  File "/Users/binstar/miniconda/lib/python2.7/site-packages/binstar_client/scripts/cli.py", line 82, in main
1263    description=doc, version=version)
1264  File "/Users/binstar/miniconda/lib/python2.7/site-packages/binstar_client/scripts/cli.py", line 64, in binstar_main
1265    return args.main(args)
1266  File "/Users/binstar/miniconda/lib/python2.7/site-packages/binstar_client/commands/upload.py", line 203, in main
1267    callback=upload_print_callback(args))
1268  File "/Users/binstar/miniconda/lib/python2.7/site-packages/binstar_client/init.py", line 425, in upload
1269    s3res = requests.post(s3url, data=data_stream, verify=self.session.verify, timeout=10 * 60 * 60, headers=headers)
1270  File "/Users/binstar/miniconda/lib/python2.7/site-packages/requests/api.py", line 109, in post
1271    return request('post', url, data=data, json=json, **kwargs)
1272  File "/Users/binstar/miniconda/lib/python2.7/site-packages/requests/api.py", line 50, in request
1273    response = session.request(method=method, url=url, **kwargs)
1274  File "/Users/binstar/miniconda/lib/python2.7/site-packages/requests/sessions.py", line 468, in request
1275    resp = self.send(prep, **send_kwargs)
1276  File "/Users/binstar/miniconda/lib/python2.7/site-packages/requests/sessions.py", line 576, in send
1277    r = adapter.send(request, **kwargs)
1278  File "/Users/binstar/miniconda/lib/python2.7/site-packages/requests/adapters.py", line 370, in send
1279    timeout=timeout
1280  File "/Users/binstar/miniconda/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py", line 559, in urlopen
1281    body=body, headers=headers)
1282  File "/Users/binstar/miniconda/lib/python2.7/site-packages/requests/packages/urllib3/connectionpool.py", line 353, in _make_request
1283    conn.request(method, url, **httplib_request_kw)
1284  File "/Users/binstar/miniconda/lib/python2.7/httplib.py", line 1053, in request
1285    self._send_request(method, url, body, headers)
1286  File "/Users/binstar/miniconda/lib/python2.7/httplib.py", line 1093, in _send_request
1287    self.endheaders(body)
1288  File "/Users/binstar/miniconda/lib/python2.7/httplib.py", line 1049, in endheaders
1289    self._send_output(message_body)
1290  File "/Users/binstar/miniconda/lib/python2.7/httplib.py", line 897, in _send_output
1291    self.send(message_body)
1292  File "/Users/binstar/miniconda/lib/python2.7/httplib.py", line 866, in send
1293    self.sock.sendall(datablock)
1294  File "/Users/binstar/miniconda/lib/python2.7/site-packages/requests/packages/urllib3/contrib/pyopenssl.py", line 216, in sendall
1295    data = memoryview(data)
1296TypeError: cannot make memory view because object does not have the buffer interface
1297command exited with status 1
—
Reply to this email directly or view it on GitHub
https://github.com/Anaconda-Server/anaconda-client/issues/222#issuecomment-162672596
.

--
Stephen Kearns
Product Manager
w:<PHONE_NUMBER>
m:<PHONE_NUMBER>
t: @stephenakearns
skype: stephen.kearns

Who is @ContinuumJira ? As I said in FD, it is impossible that there is no way to do an HTTP POST in Python using requests.  That not working would be a super fundamental failure of the entire package.  There must be some way we can adapt the call we're making so it will work.

http://docs.python-requests.org/en/latest/community/updates/#release-and-version-history
Requests 2.9.1 has been released with a fix to the upload code. Upgrading your version of the library should resolve all instances of this issue.


Nd4j.shuffle

This method does not give a shuffle evenly.
If we view an ndarray as a list of vectors, then a vector with small index in the original list is more likely to have a small index in the new list after the shuffle, and so does a vector with large index.
The thing is that, in this method, every time after we swap the places of two vectors, we need to renew the value of the new index in 'vectorsAlongDimension', too.

Consolidated to newer issue. Thanks!


Error: signing ghcr.io/...: GET https://ghcr.io/token?...: DENIED: denied

Description
When running cosign attest on GitHub Actions cosign seems to use the ambient github token for retrieving data from the registry for the purposes of signing instead of using the provided registry password/token.
The situation is as follows:

Running inside a GitHub Actions workflow.
The workflow job's ambient GitHub token does not have packages: write permission.
A PAT token with packages: write is given to the workflow and passed to cosign login to authenticate.
Run cosign attest on a previously created ghcr.io image.

This results in an error occurring during signing. Something like:
Error: signing ghcr.io/...: GET https://ghcr.io/token?...: DENIED: denied

I would expect this flow to succeed by using the auth set by cosign login to retrieve registry data for signing.
Background: This is for a GitHub reusable workflow that deals with registries generically and does not request packages: write for the github token, instead relying on the user to pass a token with the proper package: write permissions as a secret and logging them in using cosign login.
Version
v1.13.1

I have reason to believe the error occurs somewhere in this block as the error occurs after the tlog entry is created and uploaded.
https://github.com/sigstore/cosign/blob/72dac4d760825f1fe7161e48c93d23bd7ec842a1/cmd/cosign/cli/attest/attest.go#L196-L222


Need to put norm_layer as a parameter.

https://github.com/pytorch/vision/blob/684f48db4e6f619389da3a6957b3edebf794ae79/torchvision/models/detection/backbone_utils.py#L47
It works fine with resnet50_fpn, but when I try to use another backbone, for example resnext101_32x8d
norm_layer=misc_nn_ops.FrozenBatchNorm2d may trouble with Imagenet pretrained  weights, which use BatchNorm
Traceback (most recent call last):
  File "tmp.py", line 4, in <module>
    m = maskrcnn_resnext101_32x8d_rpn(pretrained=True)
  File "/mnt/data/luan/maskrcnn/models.py", line 218, in maskrcnn_resnext101_32x8d_rpn
    "resnext101_32x8d", pretrained=pretrained)
  File "/mnt/data/luan/anaconda3/envs/mask/lib/python3.6/site-packages/torchvision/models/detection/backbone_utils.py", line 47, in resnet_fpn_backbone
    norm_layer=misc_nn_ops.FrozenBatchNorm2d)
  File "/mnt/data/luan/anaconda3/envs/mask/lib/python3.6/site-packages/torchvision/models/resnet.py", line 313, in resnext101_32x8d
    pretrained, progress, **kwargs)
  File "/mnt/data/luan/anaconda3/envs/mask/lib/python3.6/site-packages/torchvision/models/resnet.py", line 224, in _resnet
    model.load_state_dict(state_dict)
  File "/mnt/data/luan/anaconda3/envs/mask/lib/python3.6/site-packages/torch/nn/modules/module.py", line 830, in load_state_dict
    self.__class__.__name__, "\n\t".join(error_msgs)))
RuntimeError: Error(s) in loading state_dict for ResNet:
        Unexpected key(s) in state_dict: "bn1.num_batches_tracked", "layer1.0.bn1.num_batches_tracked", "layer1.0.bn2.num_batches_tracked", "layer1.0.bn3.num_batches_tracked", "layer1.0.downsample.1.num_batches_tracked", "layer1.1.bn1.num_batches_tracked", "layer1.1.bn2.num_batches_tracked", "layer1.1.bn3.num_batches_tracked", "layer1.2.bn1.num_batches_tracked", "layer1.2.bn2.num_batches_tracked", "layer1.2.bn3.num_batches_tracked", "layer2.0.bn1.num_batches_tracked", "layer2.0.bn2.num_batches_tracked", "layer2.0.bn3.num_batches_tracked", "layer2.0.downsample.1.num_batches_tracked", "layer2.1.bn1.num_batches_tracked", "layer2.1.bn2.num_batches_tracked", "layer2.1.bn3.num_batches_tracked", "layer2.2.bn1.num_batches_tracked", "layer2.2.bn2.num_batches_tracked", "layer2.2.bn3.num_batches_tracked", "layer2.3.bn1.num_batches_tracked", "layer2.3.bn2.num_batches_tracked", "layer2.3.bn3.num_batches_tracked", "layer3.0.bn1.num_batches_tracked", "layer3.0.bn2.num_batches_tracked", "layer3.0.bn3.num_batches_tracked", "layer3.0.downsample.1.num_batches_tracked", "layer3.1.bn1.num_batches_tracked", "layer3.1.bn2.num_batches_tracked", "layer3.1.bn3.num_batches_tracked", "layer3.2.bn1.num_batches_tracked",
"layer3.2.bn2.num_batches_tracked", "layer3.2.bn3.num_batches_tracked", "layer3.3.bn1.num_batches_tracked", "layer3.3.bn2.num_batches_tracked", "layer3.3.bn3.num_batches_tracked", "layer3.4.bn1.num_batches_tracked", "layer3.4.bn2.num_batches_tracked", "layer3.4.bn3.num_batches_tracked", "layer3.5.bn1.num_batches_tracked", "layer3.5.bn2.num_batches_tracked", "layer3.5.bn3.num_batches_tracked", "layer3.6.bn1.num_batches_tracked", "layer3.6.bn2.num_batches_tracked", "layer3.6.bn3.num_batches_tracked", "layer3.7.bn1.num_batches_tracked", "layer3.7.bn2.num_batches_tracked", "layer3.7.bn3.num_batches_tracked", "layer3.8.bn1.num_batches_tracked", "layer3.8.bn2.num_batches_tracked", "layer3.8.bn3.num_batches_tracked", "layer3.9.bn1.num_batches_tracked", "layer3.9.bn2.num_batches_tracked", "layer3.9.bn3.num_batches_tracked", "layer3.10.bn1.num_batches_tracked",
"layer3.10.bn2.num_batches_tracked", "layer3.10.bn3.num_batches_tracked", "layer3.11.bn1.num_batches_tracked", "layer3.11.bn2.num_batches_tracked", "layer3.11.bn3.num_batches_tracked", "layer3.12.bn1.num_batches_tracked", "layer3.12.bn2.num_batches_tracked", "layer3.12.bn3.num_batches_tracked", "layer3.13.bn1.num_batches_tracked", "layer3.13.bn2.num_batches_tracked", "layer3.13.bn3.num_batches_tracked", "layer3.14.bn1.num_batches_tracked", "layer3.14.bn2.num_batches_tracked", "layer3.14.bn3.num_batches_tracked", "layer3.15.bn1.num_batches_tracked", "layer3.15.bn2.num_batches_tracked", "layer3.15.bn3.num_batches_tracked", "layer3.16.bn1.num_batches_tracked", "layer3.16.bn2.num_batches_tracked", "layer3.16.bn3.num_batches_tracked", "layer3.17.bn1.num_batches_tracked", "layer3.17.bn2.num_batches_tracked", "layer3.17.bn3.num_batches_tracked", "layer3.18.bn1.num_batches_tracked", "layer3.18.bn2.num_batches_tracked", "layer3.18.bn3.num_batches_tracked", "layer3.19.bn1.num_batches_tracked", "layer3.19.bn2.num_batches_tracked", "layer3.19.bn3.num_batches_tracked", "layer3.20.bn1.num_batches_tracked", "layer3.20.bn2.num_batches_tracked", "layer3.20.bn3.num_batches_tracked", "layer3.21.bn1.num_batches_tracked", "layer3.21.bn2.num_batches_tracked", "layer3.21.bn3.num_batches_tracked", "layer3.22.bn1.num_batches_tracked", "layer3.22.bn2.num_batches_tracked", "layer3.22.bn3.num_batches_tracked", "layer4.0.bn1.num_batches_tracked", "layer4.0.bn2.num_batches_tracked", "layer4.0.bn3.num_batches_tracked", "layer4.0.downsample.1.num_batches_tracked", "layer4.1.bn1.num_batches_tracked", "layer4.1.bn2.num_batches_tracked", "layer4.1.bn3.num_batches_tracked", "layer4.2.bn1.num_batches_tracked", "layer4.2.bn2.num_batches_tracked", "layer4.2.bn3.num_batches_tracked".

Actually, the error you are facing has been fixed with https://github.com/pytorch/vision/pull/1728
But the PR that you linked is ok with me, I would have exposed **kwargs instead, but that's fine


[Android] When app is compiled with AGP 4.1.3 ('com.android.tools.build:gradle:4.1.3'), the map is blank

I'm submitting a ...  (check one with "x")

[ ] question
[ X ] any problem or bug report

OS:  (check one with "x")

[ X ] Android
[ ] iOS
[ ] Browser

cordova information:  (run $> cordova plugin list)
latest cordova-android master branch

If you use @ionic-native/google-maps, please tell the package.json (only @ionic-native/core and @ionic-native/google-maps are fine mostly)
@ionic-native/core : 4.20.0
@ionic-native/google-maps : ^2.7.0

Cause
I've done some investigation and have isolated the issue to be caused by the change in cordova-android dependency of  AGP from version 4.0.x to 4.1.3
Release notes for AGP
https://developer.android.com/studio/releases/gradle-plugin#4-1-0
Current behavior:

App starts with map being blank/white.
Expected behavior:

Shows the map
Screen capture or video record:

Related code, data or error log (please format your code or data):
Most the time no errors in logcat
Occasionally the following error is shown in logcat
 java.lang.AssertionError
     at org.apache.cordova.CordovaPlugin.privateInitialize(CordovaPlugin.java:52)
     at org.apache.cordova.PluginManager.getPlugin(PluginManager.java:178)
     at org.apache.cordova.PluginManager.exec(PluginManager.java:129)
     at org.apache.cordova.CordovaBridge.jsExec(CordovaBridge.java:59)
     at org.apache.cordova.engine.SystemExposedJsApi.exec(SystemExposedJsApi.java:41)
     at android.os.MessageQueue.nativePollOnce(Native Method)
     at android.os.MessageQueue.next(MessageQueue.java:326)
     at android.os.Looper.loop(Looper.java:160)
     at android.os.HandlerThread.run(HandlerThread.java:65)

Test project that shows the issue
https://github.com/ebhsgit/gmap-test/tree/android-9.1
You will need to edit config.xml to put in your Map API key
Please share your project files on Github or others(Bitbucket, Gitlabs...etc).
If you don't want to share your project files, please create a demo project, then share it.

Screen captures, and/or native logs(such as Logcat, xcode logs) are appreciate.

Giving much information, you are waiting time is less.
Thank you for your cooperation.

Support this plugin activity
I appreicate if you give me a beer :beer: from here

I have this problem.
Which android platform release do I have to install to solve it?

I also have the issue with blank map. Works when AGP 4.0.2 is used, but is broken with AGP 4.1.x and above.

@sergip76
It's not related to your target Android version. It's cause by change from 4.0.x to 4.1.x of AGP (Android Gradle Plugin)
Prior to AGP 4.1.+, assert keyword was not enforced.
Latest Cordova-Android started using AGP 4.1.+, which is causing the AssertionError

I have not tested fix #2872 but if it works please try to merge it so that we can use official release of this plugin and do not have to hack the solution ourselves in code. Without fix we are stuck to<EMAIL_ADDRESS>and can not use latest<EMAIL_ADDRESS>which needs Android Gradle Plugin (AGP) version 4.2.2. Thank you!


timed_dataframe has empty values when no electrons are present

Is your feature request related to a problem? Please describe.
when looking at the timed_dataframe, if there were no electrons for a specific pulseID, no other values are saved for any column, even if in principle these values are available in the h5 files
Describe the solution you'd like
I would like the dataframe to contain available values also for pulseIDs that have no electrons
Describe alternatives you've considered
I have not really considered any alternative, but i would be happy to

i don't think so, but maybe i did not understand your reply fully.
Let me explain my problem better. If during a train of 400 FEL pulses, there is a pulse with no electron counts, then the timed_dataframe has no entries for that FEL pulse. Simply no value, which would actually be available in the original h5 file, is saved in the dataframe. These data would still be of great value, even if no electrons are detected by the dld.

#311 addresses it


Jackson shading build issue

The following occurs completely randomly during some builds, but doesn't occur during most:
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] nd4j ............................................... SUCCESS [  0.853 s]
[INFO] nd4j-shade ......................................... SUCCESS [  0.009 s]
[INFO] jackson ............................................ FAILURE [  6.317 s]
[INFO] nd4j-common ........................................ SKIPPED
[INFO] nd4j-context ....................................... SKIPPED
[INFO] nd4j-buffer ........................................ SKIPPED
[INFO] nd4j-backends ...................................... SKIPPED
[INFO] nd4j-api-parent .................................... SKIPPED
[INFO] nd4j-api ........................................... SKIPPED
[INFO] nd4j-jdbc .......................................... SKIPPED
[INFO] nd4j-jdbc-api ...................................... SKIPPED
[INFO] nd4j-jdbc-mysql .................................... SKIPPED
[INFO] nd4j-instrumentation ............................... SKIPPED
[INFO] nd4j-perf .......................................... SKIPPED
[INFO] nd4j-backend-impls ................................. SKIPPED
[INFO] nd4j-native-api .................................... SKIPPED
[INFO] nd4j-serde ......................................... SKIPPED
[INFO] nd4j-base64 ........................................ SKIPPED
[INFO] nd4j-jackson ....................................... SKIPPED
[INFO] nd4j-native ........................................ SKIPPED
[INFO] nd4j-aeron ......................................... SKIPPED
[INFO] nd4j-kryo .......................................... SKIPPED
[INFO] nd4j-camel-routes .................................. SKIPPED
[INFO] nd4j-kafka ......................................... SKIPPED
[INFO] nd4j-gson .......................................... SKIPPED
[INFO] nd4j-jackson-reflectionloader ...................... SKIPPED
[INFO] nd4j-bytebuddy ..................................... SKIPPED
[INFO] nd4j-tests ......................................... SKIPPED
[INFO] nd4j-native-platform ............................... SKIPPED
[INFO] nd4j-cuda .......................................... SKIPPED
[INFO] nd4j-cuda-platform ................................. SKIPPED
[INFO] nd4j-parameter-server-parent ....................... SKIPPED
[INFO] nd4j-parameter-server-model ........................ SKIPPED
[INFO] nd4j-parameter-server .............................. SKIPPED
[INFO] nd4j-parameter-server-status ....................... SKIPPED
[INFO] nd4j-parameter-server-client ....................... SKIPPED
[INFO] nd4j-parameter-server-rocksdb-storage .............. SKIPPED
[INFO] nd4j-parameter-server-node ......................... SKIPPED
[INFO] nd4j-uberjar ....................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7.796 s
[INFO] Finished at: 2018-01-20T13:12:10+11:00
[INFO] Final Memory: 62M/744M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:3.0.0:shade (default) on project jackson: Error creating shaded jar: duplicate entry: META-INF/services/org.nd4j.shade.jackson.core.JsonFactory -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :jackson

Confirming that this still occurs. These days, I am seeing this on about 50% of my linux builds, and it makes scripts like buildAllVersions.sh fail in most cases, as it seems to have a chance of hitting this on each build...


Fix track sorting

The TrackManager change introduced a bug that causes tracks that don't
have callstack events to never show up. It also broke the previous
sorting policy which was to display tracks with instrumented functions
first. Reimplement track sorting and remove unused and duplicated
"thread_count_map_" and "event_count_" vectors.
This change also fixes introspection tracks not showing up anymore.

Hi @reichlfl , thanks for the review. To answer your questions:

As far as I understand, the issue was that GetSortedThreadIds runs through the thread_count_map_ instead of all tracks, and Threads without events do not show up there, is that the cause?

The issue was that thread_count_map_ was copied over from TimeGraph to TrackManager but it is not updated, causing tracks with timers but no events to not be displayed. The map is not really needed as we can access that count from the track themselves.

2. With this change, GetCallstackEventsOfTidCount is called during sorting, but this method should run in O(1) because it returns the size of a vector retrieved from a hashmap, so it should not result in decreased performance compared to keeping the running count in thread_count_map_.

Yes that's exactly right. Also, sorting happens once every second when capturing. For the number of tracks we are dealing with, that's really not a bottleneck.

Thanks for addressing this Pierric! :)

Thanks for addressing this Pierric! :)


More information about brotli experiment

Brotli was enabled for all M50 users.

What exactly does "Enabled via Chrome-Variations (92fb4fc2)" mean?

"Chrome-Variations" is a technology that allows to control chrome flags.
Open "chrome://version" page and it will show "Variations" section with a list of XXXXXXXX-YYYYYYYY values. XXXXXXXX is a hash of flag and YYYYYYYY represents the flag setting.

Ping?

Okay, got it. Wonder if there's a better way to express that though since I think it would confuse most people like that. Also if it's not enabled by default the value still needs to be n. If it is, the value should be y without the d. (sorry for the delay, on vacation)

Oh, sorry, didn't mean to disturb you on vacation.
So, it is now enabled by default, but still some users might need to restart their browser to apply this default.
Going to update PR soon.

lgtm, thanks!


Error: unexpected token tCOLON on valid code

I have the following Ruby code:
LOCALES = {
  'en-US': 'English / United States',
  'en-UK': 'English / United Kingdom',
  nl: 'Dutch / Netherlands'
}

When I run Rubocop:
Offenses:

config/initializers/app_settings.rb:9:10: E: unexpected token tCOLON
  'en-US': 'English / United States',

As far as I know 'string1': 'string2' is a valid hash notation in > ruby 1.9.
Ruby / Rails doesn't seem to complain when I run it. Is this a small Rubocop bug or is it me?
Rubocop version 0.31.0

Tested this in Ruby 2.1 and it results in a syntax error there. Are you sure this is valid syntax?

No syntax error here:
Loading development environment (Rails 4.2.1)
irb(main):001:0> a = { 'en-US': 'English' }
=> {:"en-US"=>"English"}

I'm running ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-linux-gnu]

Seems this was changed in Ruby 2.2. //cc @whitequark

This is quite insightful. See point 1 of mu is too short. It seems to be a change in Ruby 2.2.
http://stackoverflow.com/questions/10004158/is-hash-rocket-deprecated
I work under OSX but my VM with Ubuntu runs the code. So probably my Rubocop plugin is detecting this as a syntax error (because of Ruby 2.1), but it is running fine in Ubuntu (because of Ruby 2.2).

Funny thing is that Rubocopy changed it to the '...': '....' notation with the --auto-correct option.
Perhaps the auto-correct should leave string hashes alone for now.

Hrm.
$ ./bin/ruby-parse --22 -e '{"x":y}'
(hash
  (pair
    (sym :x)
    (send nil :y)))


Add nil check to generate kube config action

Problem:
The cluster generateKubeconfig action panics if cluster contains a nil localClusterAuthEndpoint.
Solution:
Nil check localClusterAuthEndpoint
Issue:
https://github.com/rancher/rancher/issues/23783
Notes:
This happens because to use access.byId the client cluster struct needs to be used, opposed to the regular management struct. Typically there is a default localClusterAuthEndpoint but all struct fields on the client cluster struct are pointers, and so the default is nil. This is a generated struct.
This only occurs when the request lacks a localClusterAuthEndpoint or it is explicitly set to null in the request. The UI is currently omitting the localClusterAuthEndpoint (see following issue):
https://github.com/rancher/rancher/issues/23913

We should drop the test as we don't have a good way to tell when cluster handles are done

lgtm


Static units cannot be enabled

Description
systemd version: 219
module version: 2.12.0
definition of worker.target
root@tst-api01 ~ # systemctl cat worker.target
# /etc/systemd/system/worker.target
[Unit]
Description=Queue Workers
Wants=rabbitmq-server.service<EMAIL_ADDRESS>api-default-queue

[Install]
WantedBy=multi-user.target

Definition of api-default-queue.service (instantiated from template) in hiera:
systemd::manage::unit_file:
<EMAIL_ADDRESS>    content: |
      [Unit]
      Description=default-queue-%i
      BindsTo=worker.target

      [Service]
      Type=simple
      ExecStart=FOO
      SyslogIdentifier=default-queue-%i
      Group=FOO
      User=FOO
      Restart=on-failure
      RestartSec=10
      TimeoutStartSec=10
<EMAIL_ADDRESS>    enable: true
    active: true

Expected behaviour:
Puppet tries to enables that unit but realizes that it's a static unit and does nothing.
Actual behaviour
Puppet restarts the unit
Debug: Executing: '/bin/systemctl is-enabled --<EMAIL_ADDRESS>Debug: Executing: '/bin/systemctl unmask --<EMAIL_ADDRESS>Debug: Executing: '/bin/systemctl enable --<EMAIL_ADDRESS>Debug: Executing: '/bin/systemctl is-enabled --<EMAIL_ADDRESS>Debug: Unable to enable or disable static service<EMAIL_ADDRESS>Notice: /Stage[main]/Systemd::Manage/Systemd::Unit_file[api-default-queue<EMAIL_ADDRESS>enable changed 'false' to 'true'

leads to
Feb 20 19:18:28 prd-api01 systemd[1]: Stopped api-default-queue-1.
Feb 20 19:18:28 prd-api01 systemd[1]: Started api-default-queue-1.

Suggested behaviour:
It's eventually a clash of responsibilites between systemd and puppet. Meaning: "who is, in the end, reponsible for managing the state of that unit". With harder dependencies, it seems to rather be within system`s jurisdiction, on the other hand though, when there are no hard bindings between units, it makes sense for puppet to manage that unit.
Since it obviously does not make sense for the module to try to understand the interdependency between defined units (in order to not allow enable: true for static units), I'd suggest that this module accepts "static" as a valid return-value (instead of only "enable" now, probably - not verified) for systemctl is-enabled $UNIT.

Turns out I have misused the module. I tried to manage instantiated units via systemd::manage::unit_file while I should have been managing those with systemd::manage::services.
Sorry for the irritation.
Cheers
Thomas


Handle new syntex for includedir statement

On newer sudo versions the default inclusion statement is @includedir instead of #includedir. After running the role the directory gets included a second time:
@includedir /etc/sudoers.d

For compatibility reasons I didn't change the line value so on newer installations the @includedir will be replaced by the old syntax.
Reference:

It is possible to include other sudoers files from within the -->

https://www.sudo.ws/docs/man/sudoers.man/#Including_other_files_from_within_sudoers
fixes #9

let's do two tasks instead. keep the new fresh and support the old.

Will have time to work on this in 2-3 weeks.


scrub the secrets

Description
Uses the same strategy that we use today via LogBook just via a simple function call. I decided not to use the built-in scrubbing from structlog because it's made to scrub named fields, which we are not doing here. We only have the values.
Checklist

[x] I have signed the CLA
[ ] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have updated the CHANGELOG.md and added information about my change

Tests also import SECRET_ENV_PREFIX to build secrets so it should probably stay a var.

Thanks for the heads up @emmyoop. It looks like the commit in exceptions.py is going to work just fine with the new system. I also agree that since the var is used in tests I should be referencing it as well. We can move it out of the old logger module later.


Publish pymupdf in homebrew, at least as a tap here

The main point of brew install edxu96/cmdict/cmdict is to host multiple formulas here, so we can also publish pymupdf, at least here.

Done by others, https://formulae.brew.sh/formula/pymupdf.


https://reacttraining.com/   can't open

please check that. I am from china.
thanks in advance

More info: https://reacttraining.com/ fails with this twttr is not defined error, and a blank page
https://reacttraining.com/react-router/ has the same error, but renders the expected page

Access to Twitter is currently blocked in China, so it's probably blocking the twitter.js file as well. I'll fix that on reacttraining.com.
However, we aren't even loading twitter.js anywhere in the router documentation site, so you shouldn't be seeing the error on reacttraining.com/react-router. Can you please double check, @richb-hanover?

Sorry, I only offered an incomplete bug report.

As noted, the main https://reacttraining.com site previously was blank. Console showed an error about twttr not defined...

The https://reacttraining.com/react-router site previously displayed as desired in the browser. However, at that time, Console showed the same/similar twttr not defined

Everything is good now: the main page and react-router page both display as expected, with only a minor error in Console for the latter page

thank you. now everything is okay.

You're welcome 👍


mup deploy not running app in production mode

I'm using mup to deploy to an Ubuntu based Digital Ocean droplet. Everything seems to work correctly but the application is running in 'debug' mode, ie. each file is being downloaded separately rather than as a bundle. Does anyone know why this is?
Thanks
Ryan

There are many was. Since version 1.0 you just put 'meteor debug' so im guessing you must have some old debug stuff exported options or something.
Look through the ideas options on this link until it stops assuming you run 'meteor' and not with the debug option.
http://stackoverflow.com/questions/11034941/meteor-debug-on-server-side
Oh also note that 'source map' mappings help you debug in the original files so if you put a break point inside a bundled file it will pop the source file but it's a client side debugging illusion I suppose you could say. Apparently this can be disabled in the browser.

This shouldn't happen, I specifically added the --debug flag in my fork.
First see if your meteorBinary is correct in your mup.json, it should be
"meteorBinary": "/usr/local/bin/meteor"

Now if that was /usr/local/bin/meteor --debug, that'd be your problem
Then try dumping args and seeing if the --debug flag is somehow there. You can fork it and make the changes as shown below.
e.g. I added this in build.js - console.log( 'buildMeteorApp', args );

  var isWin = /^win/.test(process.platform);
  if(isWin) {
    // Sometimes cmd.exe not available in the path
    // See: http://goo.gl/ADmzoD
    executable = process.env.comspec || "cmd.exe";
    args = ["/c", "meteor"].concat(args);
  }

  console.log( 'buildMeteorApp', args );

  var options = {cwd: appPath};
  var meteor = spawn(executable, args, options);
  var stdout = "";
  var stderr = "";

If you want control over this, check out my pull request which has support for the debug and server options
https://github.com/kadirahq/meteor-up/pull/680
Or just use my fork: https://github.com/ClarenceL/meteor-up


Gaps (or Seams) Between Multiple Materials on Mesh

Tested versions
Reproduced in 4.2.stable
System information
Windows 10, Godot 4.2.stable, RTX 3070, Driver 546.01, Vulkan
Issue description
When applying multiple materials to a mesh, there are visible gaps in the geometry after rendering.
This usually results in the skybox leaking through the gaps, or any objects on the other side of the gap.
I think these gaps shouldn't be there, as they are the same mesh.

Antialiasing can make it worse
This happens with texture materials, and plain color albedo

Steps to reproduce
Make a mesh with multiple materials, edged against a sharp angle, like a floor having a different material than a wall.
Place a plane under the mesh with a contrasting color and make it unshaded.
Point a camera at the sharp edge, and you should see the contrasting plane leaking through the seam.
Scene:

Results:

Minimal reproduction project (MRP)
MaterialSeamsIssue-main.zip

I took a look at the MRP locally. I see that there is a big cutout in the green plane that is approximately the shape of the grey structure.
I couldn't reproduce the gaps on my device unfortunately.
Most likely these come from floating point precision issues. Some GPUs are more susceptible to them than others. But ultimately it comes from the fact that floating point numbers don't have perfect precision, so after a few operations, you can get slightly different results.
Unfortunately, this means that you have to always design assets with a little bit of overlap. On the engine side, we do what we can to be careful with floating point operations, but this issue is coming from floating point operations that happen within the GPU (that we have no control over). This is why it only appears on some GPUs. NVidia especially tends to prioritize speed over accuracy. While intel (which is what I am using) tends to prioritize correctness over performance.

I appreciate the second set of eyes, and the insight, @clayjohn. Thanks!

Just adding a video example of this issue, shows the object in blender and in game. I don't think that adding overlap should be the solution as it would be a bit of a destructive workflow.
https://github.com/godotengine/godot/assets/100348125/f65b8d6d-cdc8-4538-96a1-e34732f01841

@clayjohn I wonder if we can have an import option to fix T-joints. This seems to be the most problematic aspect when you have flat-shaded faces encounter each other.
It would likely need to be disabled by default as it's slow and generally not needed on most meshes.

Been having this problem too. I exported my model as gltf and imported it in 4.0, 4.1 and 4.2. Seams seem to only appear in 4.2. Presumably this means it's being caused by something in the way 4.2 changed how it stores meshes.
Top image is 4.1, bottom image is 4.2.

Dear god, have I been developing a custom shader workflow so that I only have one material per mesh for nothing?!

Been having this problem too. I exported my model as gltf and imported it in 4.0, 4.1 and 4.2. Seams seem to only appear in 4.2. Presumably this means it's being caused by something in the way 4.2 changed how it stores meshes. Top image is 4.1, bottom image is 4.2.

Can you try importing the mesh with compression disabled to see if the new mesh compression is indeed causing the issue?

Been having this problem too. I exported my model as gltf and imported it in 4.0, 4.1 and 4.2. Seams seem to only appear in 4.2. Presumably this means it's being caused by something in the way 4.2 changed how it stores meshes. Top image is 4.1, bottom image is 4.2.

Can you try importing the mesh with compression disabled to see if the new mesh compression is indeed causing the issue?

I assume you are talking about this? I tried it and the issue is still present.

For me enabling "Force Disable Compression" then deleting the .import file did fix it. Re-disabling "Force Disable Compression" and then deleting the .import brought the problem back.
Certainly seems that's where the problem is.

I did some further testing with an NVidia graphics card and was able to reproduce this issue. There is a potential solution proposed in https://github.com/godotengine/godot/issues/91962, but I confirmed it does not help the MRP in this case.
Looking into the project closely, it seems that the two objects are not only unconnected, but they use very different scales in their transform. This can lead to floating point precision issues, and doubly so when using compressed textures.
If anyone else is willing to upload an MRP I can check and see if #91962 is able to resolve some of the other issues that people are facing. But a proper solution to the MRP will definitely need more work (and may inevitably not be solvable)

Hard to see them but made this MRP with very contrasting colors so it was easier for me to find them. Mostly when very close it's easier, scaling the object would work if it's float precission issues.

This is a single object with two materials, some 90 degree intersections, some plain.
Seams.zip

A potential solution would involve using a common AABB for all submeshes of a model. This way, the vertices would be unquantized in the same positions. A similar, though more complex solution is described in https://cg.postech.ac.kr/papers/mesh_comp_mobile_conference.pdf, where the AABBs have different positions and are aligned to a common grid, but have the same size and alignment.


Consistently set activeModal, always

Consistently set activeModal when using open / close triggers through data- properties.
Adresses https://github.com/ghosh/micromodal/issues/134
FYI, Micromodal.close() is now fixed, but is still inconsistent with the documentation (see https://github.com/ghosh/micromodal/issues/133)
In other words, Micromodal.close() now works, but doesn't accept any argument and closes only "activeModal". There seem to be an strategy inconsistency between

activeModal variable, which suggests only one modal can be opened at a time
documented Micromodal.close(id) which suggests many modals can be opened at a time

Hi thanks for the PR. Fixed in #113


Drop int? id field for non-persisted classes

We have some entities which are not persisted to the DB but which nonetheless contain the optional id field.
This often gets confusing, as e.g. an UpdateUserMessage would look like this:
class UpdateUserMessage {
  int? id;
  String name;
  int userId;
}

Then one has to be very careful to read from the userId in these cases instead of the usual id field for most entities.
I don't think having these id fields by default serves any purpose by default, and removing it would exclude a type of bug.

Fixed


Google Maps initialCameraPosition with bounding

I am using the google-maps package for flutter and I need to fit multiple markers. I tried to fix it by calculating the bounding box and the zoom level by myself, but this didn't quite work as expected. Sometimes, the camera is too far out.
Since a few versions, there is the ability to animate to a LatLngBounds, which would work and zoom correct. I tried to call the following, when map was created:
     controller.animateCamera(CameraUpdate.newLatLngBounds(LatLngBounds(         southwest: const LatLng(-38.483935, 113.248673),         northeast: const LatLng(-8.982446, 153.823821),       ), 10));
Sometimes this is working, but sometimes I get the following platform-exception:
Error using newLatLngBounds(LatLngBounds, int): Map size can't be 0. Most likely, layout has not yet occured for the map view.  Either wait until layout has occurred or use newLatLngBounds(LatLngBounds, int, int, int) which allows you to specify the map's dimensions.
I also tried to achieve this by adding the cameraTargetBounds property to the GoogleMap-Widget, but as I have seen in another issue, this will not zoom to fit correctly, and I do not want to bound the camera position, I only want to fit it at init.
Is there a solution or a workaround? Or do I have to wait, until it is officially supported?

+1. Getting the same error. I also have mapController.animateCamera(CameraUpdate.newLatLngBounds(...)) in _onMapCreated and get the error sometimes.

The same, it works sometimes and randomly. It is frustrating.

Here I found a hardcoded workaround 😄 , any contributions are welcomed:
Fixing method:
void check(CameraUpdate u, GoogleMapController c) async {
      c.animateCamera(u);
      mapController.animateCamera(u);
      LatLngBounds l1=await c.getVisibleRegion();
      LatLngBounds l2=await c.getVisibleRegion();
      print(l1.toString());
      print(l2.toString());
      if(l1.southwest.latitude==-90 ||l2.southwest.latitude==-90)
        check(u, c);
  }

Implemetation:
CameraUpdate u2=CameraUpdate.newLatLngBounds(bound.toLatLngBounds(), 10);
        this.mapController.animateCamera(u2).then((void v){
        check(u2,this.mapController);
 });

When it works as supposed, it doesn't change anything, but if it detect that not worked, start knocking the door 🤣.

same here, does not repro on iOS simulator but repro on iOS device

I can also confirm that the issue occurs when trying to use CameraUpdate.newLatLngBounds method inside onMapCreated method, here's sample code:
void _defaultOnMapCreated(GoogleMapController controller) {
    setState(() => _mapController.complete(controller));
    widget.latLngBounds == null
        ? animateToUserLocation() //works
        : animateToBounds(widget.latLngBounds); //doesnt work, throws mentioned exception
  }

  void animateToBounds(LatLngBounds bounds) async {
    final GoogleMapController controller = await _mapController.future;
    controller.animateCamera(CameraUpdate.newLatLngBounds(bounds, 32.0));
  }

  void animateToUserLocation() async {
    final location = await MapUtil.getActualUserLocation();
    if (location != null) {
      final GoogleMapController controller = await _mapController.future;
      controller.animateCamera(
        CameraUpdate.newCameraPosition(
          CameraPosition(target: location, zoom: 13.0),
        ),
      );
    }
  }

we have same error  running newLatLngBounds onMapCreated.
Bug first informed on march still team not capable to fix it ?

So I added a little hack to get this to work. It may help you get it working for now.
onMapCreated: (GoogleMapController controller) async{
// Add function to actually move camera
var update = () async{
var region = await controller.getVisibleRegion();
// check visible region
if(region.southwest.latitude == 0.0){
return false;
}
CameraUpdate update = CameraUpdate.newLatLngBounds(blah), 0);
controller.moveCamera(update);
return true;
};
// Can set timer or do some error checking here to make sure it doesnt go on forever
while(await update() == false){
update();
};
}

Same issue here. If I change the call to newLatLong or newCameraPosition, I never see the error.  I only get the error with newLatLngBounds.

Anyone solved this problem. I'm also facing this problem.

same here, especially when two points are not long distant. The behavior is that the camera lost focus

It's working some time correctly, but not working in some time. I need to solve this problem.

Same issue, setting cameraTargetBounds in GoogleMap constructor does not work in my case

Thanks @davidcurbina for the example workaround.
Here is an updated function people can use until this is fixed:
import 'package:google_maps_flutter/google_maps_flutter.dart';

Future<void> waitForGoogleMap(GoogleMapController c) {
  return c.getVisibleRegion().then((value) {
    if (value.southwest.latitude != 0) {
      return Future.value();
    }

    return Future.delayed(Duration(milliseconds: 100))
        .then((_) => waitForGoogleMap(c));
  });
}

I fixed this issue by adding my own functions that calculate center and zoom level.
This works just fine. I got it from this stackoverflow answer.

Hi @ItsPierre  and everyone
I cannot reproduce Error using newLatLngBound when running code sample on physical device or emulator on Android 10

code sample
import 'dart:async';

import 'package:flutter/material.dart';
import 'package:google_maps_flutter/google_maps_flutter.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Google Maps Demo',
      home: MapSample(),
    );
  }
}

class MapSample extends StatefulWidget {
  @override
  State<MapSample> createState() => MapSampleState();
}

class MapSampleState extends State<MapSample> {
  Completer<GoogleMapController> _controller = Completer();

  static final CameraPosition _kGooglePlex = CameraPosition(
    target: LatLng(37.42796133580664, -122.085749655962),
    zoom: 14.4746,
  );

  static final CameraPosition _kLake = CameraPosition(
      bearing:<PHONE_NUMBER>395799,
      target: LatLng(37.43296265331129, -122.08832357078792),
      tilt: 59.440717697143555,
      zoom: 19.151926040649414);

  @override
  Widget build(BuildContext context) {
    return new Scaffold(
      body: GoogleMap(
        mapType: MapType.hybrid,
        initialCameraPosition: _kGooglePlex,
        onMapCreated: (GoogleMapController controller) {
          // _controller.complete(controller);
          //
          controller.animateCamera(CameraUpdate.newLatLngBounds(
              LatLngBounds(
                southwest: const LatLng(-38.483935, 113.248673),
                northeast: const LatLng(-8.982446, 153.823821),
              ),
              10));
        },
      ),
      floatingActionButton: FloatingActionButton.extended(
        onPressed: _goToTheLake,
        label: Text('To the lake!'),
        icon: Icon(Icons.directions_boat),
      ),
    );
  }

  Future<void> _goToTheLake() async {
    final GoogleMapController controller = await _controller.future;
    controller.animateCamera(CameraUpdate.newCameraPosition(_kLake));
  }
}

flutter doctor -v
[✓] Flutter (Channel stable, 2.0.5, on Microsoft Windows [Version 10.0.19042.928], locale en-US)
    • Flutter version 2.0.5 at C:\Users\Taha\Code\flutter_stable
    • Framework revision adc687823a (12 days ago), 2021-04-16 09:40:20 -0700
    • Engine revision b09f014e96
    • Dart version 2.12.3

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at C:\Users\Taha\Code\SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = C:\Users\Taha\Code\SDK
    • Java binary at: C:\Users\Taha\Code\android-studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/windows#android-setup for more details.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✓] Visual Studio - develop for Windows (Visual Studio Community 2019 16.9.4)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.9.31205.134
    • Windows 10 SDK version 10.0.19041.0

[✓] Android Studio (version 4.1.0)
    • Android Studio at C:\Users\Taha\Code\android-studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[✓] IntelliJ IDEA Community Edition (version 2021.1)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.3.3
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.55.2)
    • VS Code at C:\Users\Taha\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.21.0

[✓] Connected device (4 available)
    • IN2011 (mobile)   • c9d8ee0c • android-arm64  • Android 11 (API 30)
    • Windows (desktop) • windows  • windows-x64    • Microsoft Windows [Version 10.0.19042.928]
    • Chrome (web)      • chrome   • web-javascript • Google Chrome 90.0.4430.93
    • Edge (web)        • edge     • web-javascript • Microsoft Edge 90.0.818.46

! Doctor found issues in 1 category.

Is there a way I can reproduce it reliably? Please provide complete reproducible steps
Thank you

Hi @ItsPierre  and everyone
If the issue still persists,  please provide the details to reproduce the issue.

Hi @TahaTesser
I just tried to reproduce this error on my devices.
It seems to be fixed, I cannot reproduce it on my physical or my emulator devices.
But I think, this does not solve this issue itself.
In my opinion, we should add the ability to create a CameraPosition using  LatLngBounds.
With that feature, we could create the CameraPosition and provide it to the initialCameraPosition when initializing the map.
This is exactly what I did myself, explained in this comment.
At the moment, the package only provides a function CameraUpdate.newLatLngBounds to create a CameraUpdate with the bounding, the same should be done with the CameraPosition.
What do you think about this?

Issue still persits only in the release mode now if I use the workaround from @tim-smart
GoogleMap(
        initialCameraPosition: CameraPosition(
          target: _initialMapCenter,
          zoom: _initialZoomLevel,
        ),
        buildingsEnabled: false,
        zoomControlsEnabled: false,
        myLocationButtonEnabled: false,
        mapToolbarEnabled: false,
        padding: EdgeInsets.only(bottom: 10 + widget.sheetHeight),
        markers: _markers.toSet(),
        onMapCreated: (GoogleMapController controller) async {
          _controller = controller;

          await MapUtil.waitForGoogleMap(controller, _initialMapCenter);

          _markers.addAll([
            await MapUtil.getOriginMarker(
              LatLng(
                widget._initialDriverRoute.origin.coordinate.latitude,
                widget._initialDriverRoute.origin.coordinate.longitude,
              ),
              'Origin',
            ),
            await MapUtil.getDestinationMarker(
              LatLng(
                widget._initialDriverRoute.destination.coordinate.latitude,
                widget._initialDriverRoute.destination.coordinate.longitude,
              ),
              'Destination',
            )
          ]);

          setState(() {
            controller.animateCamera(
              CameraUpdate.newLatLngBounds(MapUtil.getBounds(_markers), 100),
            );
          });
        });

  static LatLngBounds getBounds(List<Marker> markers) {
    final List<double> lngs = markers.map<double>((m) => m.position.longitude).toList();
    final List<double> lats = markers.map<double>((m) => m.position.latitude).toList();

    final double highestLat = lats.reduce(max);
    final double highestLng = lngs.reduce(max);
    final double lowestLat = lats.reduce(min);
    final double lowestLng = lngs.reduce(min);

    final LatLngBounds bounds = LatLngBounds(
      northeast: LatLng(highestLat, highestLng),
      southwest: LatLng(lowestLat, lowestLng),
    );

    return bounds;
  }

PS C:\Users\michael.dunkel\Desktop\fluidgo_flutter> flutter doctor -v
[√] Flutter (Channel stable, 2.2.3, on Microsoft Windows [Version 10.0.19043.1165], locale de-AT)
    • Flutter version 2.2.3 at C:\flutter
    • Framework revision f4abaa0735 (10 weeks ago), 2021-07-01 12:46:11 -0700
    • Engine revision 241c87ad80
    • Dart version 2.13.4

[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at C:\Users\michael.dunkel\AppData\Local\Android\sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Android Studio
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • android-studio-dir = C:\Program Files\Android\Android Studio
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[√] VS Code (version 1.59.1)
    • VS Code at C:\Users\michael.dunkel\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.26.0

[√] Connected device (3 available)
    • Pixel 4a (mobile) • 0A191JEC216171 • android-arm64  • Android 11 (API 30)
    • Chrome (web)      • chrome         • web-javascript • Google Chrome 93.0.4577.63
    • Edge (web)        • edge           • web-javascript • Microsoft Edge 93.0.961.38
    ```

I believe you're trying to show the polylines and 2 markers on the screen at the same time. This is how I solved mine.
String destination = "Wuse Market Road, Abuja";   String originLocation = "Utako Ultra Modern Market, Abuja";
Then you get the directions using the Google direction API
final String url =         "https://maps.googleapis.com/maps/api/directions/json?destination=$destination&origin=$originLocation&key=${SecretKeys.placeApiKey}";
This is the entire function
`Future getDirections(String originLocation, String destination) async {
final String url =
'https://maps.googleapis.com/maps/api/directions/json?destination=$destination&origin=$originLocation&key=${SecretKeys.placeApiKey}';
var response = await http.get(Uri.parse(url));
var json = jsonDecode(response.body);

setState(() {
  var northeastLat = json["routes"][0]["bounds"]["northeast"]["lat"];
  var northeastLng = json["routes"][0]["bounds"]["northeast"]["lng"];
  var southwestLat = json["routes"][0]["bounds"]["southwest"]["lat"];
  var southwestLng = json["routes"][0]["bounds"]["southwest"]["lng"];

  var cameraUpdate = CameraUpdate.newLatLngBounds(
    LatLngBounds(southwest: LatLng(southwestLat, southwestLng), northeast: LatLng(northeastLat, northeastLng)),
    15.0,
  );
  mapController?.animateCamera(cameraUpdate);
  mapController?.getVisibleRegion();
});

}`
This is the function for getting the polylines
`void getPolyPoints() async {
PolylinePoints polylinePoints = PolylinePoints();
PolylineResult result = await  polylinePoints.getRouteBetweenCoordinates(
  SecretKeys.placeApiKey,
  const PointLatLng(9.0664, 7.4455),
  const PointLatLng(9.068647, 7.465974),
);

if (result.points.isNotEmpty) {
  for (var point in result.points) {
    polylineCoordinates.add(LatLng(point.latitude, point.longitude));
  }

  setState(() {

    _polylines.add(
      Polyline(
        polylineId: const PolylineId('polyline'),
        color: ConstantColor.officialBlue,
        points: polylineCoordinates,
        width: 5,
      ),
    );
  });
}

}`
I mad use of 2 controllers in my Google map to resolve the issue
`final _controller = Completer GoogleMapController();
GoogleMapController? mapController;
don't forget the imports
import 'dart:async';
import 'package:google_maps_flutter/google_maps_flutter.dart';`
I know this is not ethical but it solves the issue with the bounds.

Here are some technical details from #135874
After looking at the code and the Android maps docs; my wild guess is that this behavior occurs due to not offering a lifecycle event for when the map is loaded vs. ready:
https://developers.google.com/maps/documentation/android-sdk/reference/com/google/android/libraries/maps/OnMapReadyCallback
From the docs:

As an example, if you want to update the map's camera using a LatLngBounds without dimensions, you should wait until both OnMapReadyCallback and OnGlobalLayoutListener have completed. Otherwise there is a race condition that could trigger an IllegalStateException.

As https://github.com/flutter/packages/blob/cfe0c212700bfe55690b03b094c5e2e1e399871a/packages/google_maps_flutter/google_maps_flutter_android/android/src/main/java/io/flutter/plugins/googlemaps/GoogleMapController.java#L222 waits for OnMapReadyCallback but not for the OnGlobalLayoutListener event to be fired to inform the flutter layer that the map is ready to be used.
Maybe you could consider exposing the OnMapLoadedCallback in addition to onMapCreated in flutter? So that existing clients don't have to wait till the map is loaded and clients that rely on a fully loaded map can opt in.

We are seeing if this is resolved with the latest version of the Maps SDK for iOS (potential underlying issue is fixed) and will update this issue if an upcoming release is able to fix it.


Added options for bringing in more tree orientations and also an opti…

…on to control the separation between various levels of a tree heirarchy (DagLevelDistance)
The challenge our internal users are facing is - while they would like to use the new "tree" feature instead of a force-directed graph for certain reports, there are little customization options of the resulting tree. ForceGraph2D has options to control both the orientation of the tree and the distance between different levels of the tree. These two options have been brought in with this PR. The need is a justified one since many graphs are actually shown best in left-right view or bottom-up view (or even right-left view). Also, sometimes the distance between various levels of tree needs to be controlled to ensure information is displayed correctly.
While the UI does get a bit cluttered - both the features added are required by my end users so I thought i'd make a PR for the same.
**NOTICE:**

The program was tested solely for our own use cases, which might differ from yours.
Author Info:
Brahm Prakash Mishra<EMAIL_ADDRESS>on behalf of Mercedes-Benz Research and Development India
https://github.com/mercedes-benz/mercedes-benz-foss/blob/master/PROVIDER_INFORMATION.md

Replaced by https://github.com/neo4j-labs/neodash/pull/690, thank you!


Type inference fails for generic React props with JSX syntax, works with regular syntax

TypeScript Version:  2.3.4
Code
With the react TS starter pack: create-react-app.cmd generics-fail --scripts-version=react-scripts-ts, modify index.tsx as follows:
import * as React from 'react';
import * as ReactDOM from 'react-dom';
import registerServiceWorker from './registerServiceWorker';
import './index.css';

interface Problematic<T> {
    key: T;
}

interface Props<T, R> {
    data: T;
    renderer: (props: Problematic<T>) => React.ReactElement<R>;
}

class InferenceFail<T, R> extends React.Component<Props<T, R>, {}> {

}

class Data {
  key: string;
}

let works = new InferenceFail({data: new Data(), renderer: ({key}) =>
{key.key}
});

let fails = <InferenceFail data={new Data()} renderer={({key}) =>
{key.key}
} />;
//                                                                          ^^^

ReactDOM.render(
  (

    {works}
    {fails}

),
  document.getElementById('root') as HTMLElement
);
registerServiceWorker();

Expected behavior:
No compiler error. The InferenceFail instance should be correctly inferred to have actual type parameter Data for T.
Actual behavior:
Compiler error:

(25,77): error TS2339: Property 'key' does not exist on type '{}'.

T is inferred to be {}.

duplicate of https://github.com/Microsoft/TypeScript/issues/14729

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.


str.listen is not support  inES6Store in ie9,10

The problem is found in defineReact.js. I find str.isES6Store in undefined in proto.componentWillMount, so 'str.singleton = new singleton;' is not covered during the running time

@maxguzenski

It worked for me by just adding export default <storeclassname>; At the end of the store class file

It is intentional, and documented, that the stores are automatically created during the mounting process. If you're relying on them being made automatically this is the proper time for it to be done.
The pull request for the newest additions also contains documentation as well as methods for creating them yourself before then should you choose for exactly this type of thing.
Unfortunately I don't control merging pull requests. But there is an edge version of reflux which has those features here: https://github.com/BryanGrezeszak/reflux-edge

Was there a solution to this other than using the experimental version of Reflux?
I get a similar error in IE10, SCRIPT438: Object doesn't support property or method 'listen' , which is triggered in defineReact(react, reflux), 			 this.__storeunsubscribes__.push(str.listen(this.setState.bind(this)));.
I tried using es5-shim and babel-polyfill but the error is still the same.

@fredabrahamson
The new version just allows you to instantiate the store sooner so that you can access it sooner than waiting for the react lifecycle to do it automatically. It's got nothing to do with polyfills/ES5 type stuff.
Whatever's going on with your stuff, you should probably post code that replicates the problem. I've got stuff that runs just fine on IE10.
Sidenote: Reflux ES6 API is just an API that is geared toward ES6 style usage of its API. It's not actually written in ES6 code that needs shims or polyfills or anything. The code you write that implements the API might need it (or might not, depends on your code and your application of it), but Reflux does not.

This is an issue with babel.
Babel uses __proto__ to handle static properties on transpiled classes. That is not good for anything less than IE11.
Read more here: https://babeljs.io/docs/usage/caveats/#internet-explorer

I'm getting this error in reflux 6.4.1 using react-native 0.50.3. What am I doing wrong?

Also getting the issue in reflux V6.4.1 and react v16.2.0 - just copied the StateStore example from the online docs...

I am getting this issue as well running reflux v6.4.1 and react v16.3.0, same as @codeuniquely

@BryanGrezeszak any ideas?


Allow to run custom shell script inside the builders

Allow to run custom hooks inside the builders

There are some builder hooks https://github.com/freebsd/poudriere/wiki/hooks. It's unclear what was missing for this bug.


Using atexit() binding crashes

Red/System []

#include %../C-library.reds

test: does [print "Exit"]

print on-quit as-integer :test

trueExit
*** Runtime Error 16: invalid virtual address
*** at: B767916Dh
This happens at least on Linux, and on Syllable using __cxa_atexit(). Setting the exit handler is OK, and it executes on quit, but after that it causes the crash.

Well, I have a good and a bad news. :-)
Good news: there is no error in the compiler, you just forgot to use the cdecl function attribut for the test function, which is required here, because it is called back by a C function.
Bad news: you missed it and I have missed it too when analyzing this report and only realized that when I examined the ASM output for the function, which was obviously missed some code parts. We are the programmers writing the most code for Red/System, yet we forgot about that! :-) So, this means that we are clearly needing either a better documentation (with perhaps a Callback header somewhere), or a better syntax for not forgetting about such things.
What do you (and others) think?

Oops, sorry about that.
Other than changing the compiler to use cdecl for all functions, I'm not sure what could be done about this. And that would prevent using fastcall later. Detecting passing a function to a system function already proved to be too problematic.
I think after a few more occasions we will start associating crashes with calling conventions immediately. It's just that everybody will have to go through that.

Confirmed working on x86 Linux and Syllable.


Update qt-creator to 3.6.0

Thank you for the contribution. It was merged directly as fb434774a014b0eb5252fa2f2a5cef7cab6ca772 to keep commit history cleaner. Your contribution is still credited to you.


adding cardview to angular project

How would I "Make sure you include xmlns:Card="nativescript-cardview" on the Page element" if I am using the "nativescript-angular/router"?

Hey @krismcfarlin that's non ng2. I should specify that I guess :) I don't use ng2 so I forget these things. With ng2 + NativeScript you'd registerElement(). There should be an example somewhere how to do that with ng2.

Check the doc on the DrawingPad plugin here: https://github.com/bradmartin/nativescript-drawingpad#angular


Accidents with wrong street resolution

Redash Query: https://redash.hasadna.org.il/queries/1037/source#1037
Street resolution: resolution=רחוב (News Flash table)

Calculate statistics - in how many accidents are we wrong regarding street1 and yishuv_name when compared to the news flash itself? (Sample last ~100-200 accidents with resolution=רחוב)
@shaysw this part can be done only using Redash and some python coding.

Based on this statistics either:

Very small amount: Create a code that can differ accidents good street resolution vs wrong resolution
Implement it either in the news flash API (excluding these accidents) OR in the news flash insertion process as a boolean indicator (would be happy to get your opinion of what you think is better)
OR
Medium amount (or if you have a good idea for improvement): Improve CBS location extraction for accidents with resolution=רחוב
(You can use python3 main.py update_news_flash update to check your suggested improvements)
If you add improvements, please add tests that verify that we do not lower precision. Also please check out tests in test_news_flash.py.

You can also implement both suggestions of section 2, which will be a double improvement, let me know what you think.

I've gone over the 1st point in the issue. from manually checking the validity of 200 news flashes (including duplicates, e.g., same NF from different sources) and a little less than half were incorrect


Correct Documentation Misdescriptions for Azure and OpenAI Model Usage

Summary
This PR updates the documentation to clearly differentiate between the usage of Chat and Completion models for Azure OpenAI and OpenAI services. It specifies the respective classes to be used with each model type and updates the code sample ranges for improved clarity and accuracy.
Changes

Separated Azure and OpenAI sections to outline specific instructions for each service.
Introduced AzureChatCompletion and AzureTextCompletion classes for Azure, specifying the code ranges for each.
Introduced OpenAIChatCompletion and OpenAITextCompletion classes for OpenAI, specifying the code ranges for each
Added a link for users to understand the differences between Chat Completions and Completions models.

Rationale
This update ensures that users can easily identify which class to use based on their chosen model type, facilitating a smoother integration process and enhancing the utility of the documentation.
Additional Notes
Users are encouraged to refer to the provided link to comprehend the nuances between different model types and their corresponding applications in the OpenAI platform.
Testing

Verify the hyperlinks to the code samples are accurate and lead to the correct file locations.
Ensure the documentation renders correctly and is easy to follow.

Please review the changes for accuracy and clarity, and provide any feedback or suggestions for improvement.

#sign-off


Autoplay/Captioned HOC not working

I'm trying to create a carousel with captioned images. When I run yarn start, this happens:
Failed to compile.
./node_modules/react-awesome-slider/src/hoc/autoplay/index.js
SyntaxError: /home/cabero/Code/Go/src/github.com/cbr9/southgate/client/node_modules/react-awesome-slider/src/hoc/autoplay/index.js: Unexpected token (8:9)
6 |
7 | export default function(props) {

8 |   return <AutoplayComponent transitionDelay={100} {...props} />;
|          ^
9 | }
10 |
import AutoplaySlider from 'react-awesome-slider/hoc/autoplay';

This happens when I try to import HOCs from the hoc folder. Since there is a version of Autoplay outside of this, I can make autoplay work, but I can't get captioned images to work. Is there any workaround?
I am using TypeScript 3.7.5.

Still can't get it to work. My original idea was to make an autoplay-captioned slider. I still get the unexpected token problem. Also if I import the styles and use them on the autoplay component, they just don't apply. How could this be achieved?

@cbr9 I wasn't thinking of a double composition. Although the CaptionedHOC isn't publicly exported I've done a bit of testing and it should work normally with the double composition.
Can you show me the basis of your implementation?

I tried wrapping the autoplay component with the captioned component, and viceversa, but I keep getting the unexpected token error.
`
import AwesomeSlider from 'react-awesome-slider';
import withAutoplay from 'react-awesome-slider/dist/autoplay';
import CaptionedComponent from 'react-awesome-slider/src/hoc/captioned-images/index';
const AutoplaySlider = withAutoplay(CaptionedComponent(AwesomeSlider));
const Carousel = () => {
return (

Alberto Gil Hernandez

Diego Chozas Cano

);
};`

Hey @cbr9. Just update to the latest version v4.0.2 and follow the HOC example. It should work fine.
import AwesomeSlider from 'react-awesome-slider';
import withAutoplay from 'react-awesome-slider/dist/autoplay';
import withCaption from 'react-awesome-slider/dist/captioned';

const AutoplaySlider = withAutoplay(withCaption(AwesomeSlider));

Hello @rcaferati, I'm looking for the exact same feature as @cbr9 but when I try your thing, it ends with an exception because captioned.js doesn't exist in react-awesome-slider/dist/..., only captioned.css does.
I tried to download the file from github and put it manually in dist/ but I get this error:
SyntaxError: D:\Users\Utilisateur\Documents\Projet iSim\iSim\client\node_modules\react-awesome-slider\dist\captioned.js: Unexpected token (87:2)
85 |
86 | const startupScreen = (

87 |

|   ^
88 |     <img
89 |       style={{ width: '20%' }}
90 |       alt="Rick and Morty Loader"

Did I miss something in the way to do it?


DNN-8552: Account Login Module Redirect Issue

Making sure redirect after login only works if request for home page and authentication occured in same lifecycle of request

This is not relevant to the DNN-8552


feat(authors): allow selection of preferred social

Current dependencies on/for this PR:

main

PR #97   👈

This stack of pull requests is managed by Graphite.


Improved error handling for bulk indexing to provide more information…

I've been trying to use the bulk indexer in an app we're writing, and we're finding that we need to be more intelligent about error handling.  For instance, in our setup we point the app at a load balancer which redirects to our Elasticsearch nodes.  If all nodes are down we get a 503 with some html, and the elastigo library returns this as a json parsing error.
I've put in some improvements for better error handling, and a unit test which more closely demonstrates our need.

Btw, this would fix #198

do you mind rebasing @gburgett?  I'm trying to get as many of these out of the way so we can focus on the breaking change PR's that are still pending.

I merged the fixes to the race condition in the bulk indexer and you will need to merge your changes again.  @gburgett

Thanks, unfortunately I'm no longer a member of the Concur organization.  @ryan-bunker should be able to finish out this pull request.


Categories to estimate

Consider effort in porting LegacyMan content:

[ ] region A reference documents. Check other categories

common for region (4: 3 easy, 1 diff) (2d)
type-specific (14 ).  (4d)
class-specific (30? ).  (3d if can automate, else 10d)
block-quote placeholders (15 in this region). (1d)
anchors in different location to content (40?). (1d)
couple of pdfs (nil)

[ ] region A other content

transmitters (s's & t's) 55 (4d)

[ ] look for reference documents in other regions/countries

none found (nil)

[ ] UK reference documents

one pdf (nil)

[ ] Rest of world

extend parser to handle region listings (2d)
probably just naming inconsistencies as found in region A (4d to work through failures)

[ ] other bodies of data

[ ] abbrevs (1d)
[ ] cover page (4h) custom DITA)
[ ] distribution (2h, custom DITA)
[ ] quality control (2h, custom DITA)
[ ] user guide (4d, custom DITA, including new screenshots)
[ ] folder of transmitters (hundreds) (3d scrape)
[ ] other reference pages (3d parser should be mature by then)
[ ] welcome content

[ ] strategy for what's new

Done. Refactored to discrete issues.


Quickstart log and pid directories do not auto-create

The example shells do not auto-create the log and pid directories.

@drcrallen nice catch. We shoudl fix this

@drcrallen did you run bin/init?

I tried this myself, I believe the issue you noticed is due to not running bin/init – I saw similar issues when I didn't run it, but things were OK when I did. Another note: as written, those "x.sh" scripts do not actually work with the quickstart, because they hardcode "conf" rather than having a switch between "conf" and "conf-quickstart" (not clear if this is intentional).
I think these are ok for 0.9.1 because,

the quickstart calls out that running bin/init is something one should do
the quickstart (or any of the docs) never mention the "x.sh" scripts

So I am inclined to move this to 0.9.2, as an improvement rather than a bug fix.

@gianm I spoke with @drcrallen and he didn't run bin/init

okay, I'll change the tags then. anyone interested, please chime in if you feel this should be a blocker for 0.9.1.

yeah, sorry, I didn't have a chance to double check this over the weekend. Let me check it now

Correct, my bad. Will update description and master comment a bit.


Dark theme flashes on page load/reload

If I manually select the dark theme, I notice that sometimes on page reopen or reload the page flashes - it shows the dark theme for a brief moment and then switches back to black
Is there a way to avoid it?

Thanks for reporting this. I'm looking into a fix.

From some limited testing I think abridge theme doesn't suffer from this (ssiyad's boring theme also flashes), might be worth looking into how it achieves that

It should be fixed now. I had to split the JavaScript logic in two files: one to set the theme (loaded in header), and one with the logic to switch the theme (deferred loading).
Inspiration for the fix: codeandmedia/zola_docsascode_theme@9485c9e30ebe80dc7072ba0f106ccf8909a2dcc7
Thanks again for the report.


WIP Test batchnorm conv.

Thanks @KellenSunderland for working on this. Can you please add PR description?
@mxnet-label-bot [pr-work-in-progress]

Just verifying in the CI that Dick Carter's changes fix our batchnorm
errors.  I believe they should.  Will close this PR in a day or so once
I've run a few tests.
On Mon, Oct 15, 2018, 8:07 PM Roshani Nagmote<EMAIL_ADDRESS>wrote:

Thanks @KellenSunderland https://github.com/KellenSunderland for
working on this. Can you please add PR description?
@mxnet-label-bot https://github.com/mxnet-label-bot
[pr-work-in-progress]
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-mxnet/pull/12824#issuecomment-429955602,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHGTE2VR_YwCAHpz3EgdeZH95Hn3htDdks5ulM7sgaJpZM4Xb1PQ
.

Tests look good, closing this one and focusing on the main PR.


Not able to fetch and install php 7.4 on nitro apply

I get these error after running nitro init and  nitro apply on first machine I created.
Works fine if i choose 7.2

seeing the same issue here

@delixyr and @lukebailey this might be related to #127. If your machine did not init properly you are going to have issues with the other commands as well.
Can you run the following steps we discussed here to see if its a DNS problem with the virtual machine?
Also, can you attach the contents of /var/log/cloud-init-output.log and /var/log/cloud-init.log?
Here are some steps to get those files from the machine to your host:

multipass transfer nitro-dev:/var/log/cloud-init-output.log cloud-init-output.log
multipass transfer nitro-dev:/var/log/cloud-init.log cloud-init.log

@delixyr and @lukebailey this might be related to #127. If your machine did not init properly you are going to have issues with the other commands as well.
Can you run the following steps we discussed here to see if its a DNS problem with the virtual machine?
Also, can you attach the contents of /var/log/cloud-init-output.log and /var/log/cloud-init.log?
Here are some steps to get those files from the machine to your host:

multipass transfer nitro-dev:/var/log/cloud-init-output.log cloud-init-output.log
multipass transfer nitro-dev:/var/log/cloud-init.log cloud-init.log
@jasonmccallister
cloud-init.log
cloud-init-output.log

@delixyr I think we have identified the issue, we are install php-cli on init which includes PHP 7.2 so we can install composer automatically. We discovered php-cli also install OCache by default. We are removing the php-cli in beta 5 and moving composer to nitro install composer.
Hoping this resolves the issue.

Having same issue, will wait for Beta 5.

Beta 6 was just released which should resolve this issue. I'm going to keep this open until we are sure but if you can update to the latest beta and try nitro init.

We just released Nitro 2 where we switched from Multipass to Docker and added a ton of new features. Please see the announcement for more details.
This issue was specific to Multipass so we are going to close this out. Please see the documentation on upgrading from Nitro 1.


[c#] [test] Mocking ServerCallContext

I am trying to unit test my server class and having trouble mocking  ServerCallContext.
Here's the method I am trying to unit test.
public override Task<KeyValueMessage> GetValue(KeyMessage request, ServerCallContext context)
{
    // some implementation
}

I tried creating the context myself but there is no public constructor.
I also tried mocking it using Moq and Mock<ServerCallContext> but that fails for the same reason.
Any ideas?

Currently, there is no way to mock ServerCallContext (and some other classes as well). We might expose the constructors at some point (the worry is not to break the public API), but until then you can setup your tests in a way that doesn't involve ServerCallContext (you should be testing your application logic, not emulating gRPC's behavior).

Any news on this?
It is a real problem since my application logic might depend on headers passed in the context and there is no way to write reliable tests.

https://github.com/grpc/grpc/pull/15214 should address this, it will be on the next release (v1.13.x)


Delete dead link in README

What is the goal of this PR?
We've deleted a dead link in the README file.

We have a duplicated line there.
A complete tutorial for TypeDB version >= 2.5.0 is in work and will be published asap.
A complete tutorial for TypeDB version >= 2.5.0 is in work and will soon be on Medium.

Implemented in #65


Add a flag to fidesctl sync that writes all server resources to local files

Is your feature request related to a specific problem?
In cases where a user might have set up fidesctl resources via the UI, we need to give users the ability to pull resources from the server to their local file system even when those resources might not exist locally.
Describe the solution you'd like
Some kind of flag that will pull all resources from the server to the local file system via the fidesctl sync command.
Describe alternatives you've considered, if any
N/A
Additional context
Might be cool to eventually be able to tag resources as belonging to a certain repository, and then able to automatically pull all resources for a specific repository

@NevilleS note the additional context, having a field to denote what "repo" something belongs to would be kind of cool


dnsencrypt-proxy.exe detected as virus

I'm using bitdefender free edition, and just today my antivirus detect it as virus. here's the screenshot:

@ukind are you using a signed or CI build?
Maybe check: https://www.virustotal.com

Or even better, report it to Bitdefender as a false positive.


[BUG] Provider Login via IDP

Is there an existing issue for this?

[X] I have searched the existing issues

What version of the Terraform provider are you using?
1.6.0
What version of the Terraform CLI are you using?
1.8.0
What type of issue are you facing
documentation issue
Describe the bug
Hi Team,
We are using Azure as IDP for our BTP landscape. We have been using Default IDP for out terraform needs. We would like to use our custom IDP for terraform authentication. I would like to understand if it is possible to use the IDP option in our case.
We are not replicating users into custom IAS.
Regards
Braham
Expected Behavior
Want to know if the IDP option can be used in our case.
Steps To Reproduce
Use the IDP option with terraform provider. Where IAS does not get users from IDP.
User's Role Collections
Global Admin
Add screenshots to help explain your problem
NA
Additional context
NA

@brahammittal I do not fully understand this issue: Are you running into an issue when authenticating via your custom IdP? Or is this a question on how to use the Terraform provider with the custom IdP.
If you have an issue, we need the information how to reproduce the issue based on your Terraform configuration.
If this is a question: if you are using a custom IdP for authentication you can specify the IdP via the provider configuration as described in the Terraform registry. The relevant field is idp where you specify the IdP as defined in the trust setup of your SAP BTP account.

As I said we have Azure as our IDP and we do not replicate the users to IAS, when I use IAS server which is maintained in trust config I get a 401. When I use Azure tenant link in I get 400 error.
provider "btp" {
globalaccount = "globalaccount"
username = var.admin
password = var.password
idp = IAS or Azure link
}
Hope this helps. We can have a call if need be to show what we have and then get the guidance

Able to login closing the issue.

Good to hear that it works. If you have further questions I recommend to ask them in the discussion area of the repository as Q&A..


provide Markdown convenience

Adding a module to hold convenience functionality around Markdown (rendering)

provide a function that makes a markdown link based on a provided URL and caption

:tada: This PR is included in version 1.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


ARR: AC and Reviewer checklist changes

The ARR editors have requested a few changes for the reviewer checklists in June (so needed once matching is complete - June 26th).

In the reviewer checklist, under "Need Ethics Review", please change the wording to:

"Should this paper be sent for an in-depth ethics review? Before you answer this question, please refer to  https://aclrollingreview.org/ethics-flagging-guidelines/ for guidelines on what papers should and shouldn't be flagged. If your answer is yes, then explain why below, and we will ry to ensure that it receives a separate ethics review."

The questions in the AC/AE checklist should have their wording modified to matching the reviewer checklist.

@jkkummerfeld for bullet 1 it says explain why below, which field should they explain the paper needs ethics review? ethical_concerns? that field is before needs_ethics_review.
I updated the description for the field in the review and metareview forms: https://github.com/openreview/openreview-py/pull/2212/commits/28fbe1acefc45cc0d95f4126009105a55061b79a

Ah, in that case, let's make the text:
"Should this paper be sent for an in-depth ethics review? Before you answer this question, please refer to https://aclrollingreview.org/ethics-flagging-guidelines/ for guidelines on what papers should and shouldn't be flagged. If your answer is yes, then ensure you have explained why in the question above, and we will try to ensure that it receives a separate ethics review."
This is a small edit so I don't think I need to run it by the editors for confirmation.


Add Marker-Img Option to Torque Wizard Interface

S/B 7923467
@xavijam
Context
Torque maps support using marker-file images (SVG) as the marker. However, it is not possible from any of the Torque wizard interfaces to upload an image to use as the marker. Rather, a user would need to have already uploaded an image to use as the marker using a different Wizard tab, then grab the url link and add to the marker-file CartoCSS property within their Torque visualization cartocss.
Torque Wizard Interface (no option to add an image as the marker)

Simple Wizard Interface (option available to add an image as the marker)

you're awesome @michellechandra

hah! thanks @andrewbt :+1:

Tag me when implemented so I can update the Docs.

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


[WIP] Lock Support

This is my initial attempt at support locks in HomeAssistant.  The backend stuff does seem to work (although there are a few things to clean up), but I wanted some input before I tackle the frontend.
I used "locked" and "unlocked" for the states as opposed to "on" and "off", because I was concerned the latter could be confusing in a potentially dangerous way - but looking at the frontend code (with my non-existent java script experience) it looks like it would have automatically configured a toggle-able card if it were "on" and "off".
Should this be on/off? Or should I modify the toggle criteria or create something more lock-specific?

Let's keep it at locked / unlocked. We should treat the lock as a new device.

I think I addressed all of the comments and fixed a few additional things.  I haven't changed the wink library dependency yet, and I'm still working on the tests and frontend, but I think the backend should work.

Merged :+1:


Questions for evaluation

Can we use the prompt and the role sentences for our model? are these sentences also included in the real test data?

Are support dialogs given in the actual evaluation data the same task as the test dialog(within-task setting), or just the same domain? (cross-task setting).

Is the number of support dialogs per one test case also 128 in real test data?

During the development phase, could we assume that it is similar with the actual evaluation environment to test our model on MutiWoz dataset by measuring slot/intent accuracy of the predicted user response using Task1 baseline NLU?

Could you provide a more detailed description on the automatic measures(e.g. F1 score or accuracy of the slot/intent detection) that will be used for the actual test environment?

Thank you!

Hi! Thank you for your interest and questions, see the response below:

No, please don't use the prompt and role sentences in your model. We ask this since our evaluation dataset does not have all of these annotations.

Our evaluation dataset supports both the pure-task and cross-task cases, and we will evaluate the models in both scenarios.

Yes there will be 128 dialogues in the support set for each test case. This applies to both the pure-task and cross-task cases as well.

Yes, as described in the task description you can make this assumption.

We will be measuring BLEU 1-4 of the predicted response, and the F1 score of intent-slot matches computed with the NLU output on the predicted response, and the NLU output on the ground-truth response. You can consider these as a minimum; we are finalizing our evaluation methodology and will make an announcement if we decide to add more.

@aatkinson  Will there be any preprocessing (tokenization, lowercase or others) before you calculate these scores?


CodeCombat level activities should have a solve button rather than a fetch button

For some reason, CodeCombat level activities have a "FETCH" button rather than a "SOLVE" button in the path view. All activities, including CodeCombat activities should have a "SOLVE" button.

Changed CodeCombat Activities to have SOLVE buttons instead of FETCH buttons.


Support for current dev version of qutip

I'm considering toying around with this and installing it on our GPU server for our group to use, but it seems that the last version of qutip-cupy is incompatible with the latest version of qutip:
Given
$ pip freeze | grep qutip
qutip @ git+https://github.com/qutip/qutip.git@f013a4f441de5f5f8d40adf57cfe73b183d62477
qutip-cupy @ git+https://github.com/qutip/qutip-cupy.git@320efa80992e8b051a02ebdb2da0151714eb8b24

I get the following error:
>>> import qutip_cupy
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/kevin/.local/lib/python3.8/site-packages/qutip_cupy/__init__.py", line 83, in <module>
    data.inv.add_specialisations([(CuPyDense, linalg.inv_cupydense)])
  File "qutip/core/data/dispatch.pyx", line 471, in qutip.core.data.dispatch.Dispatcher.add_specialisations
ValueError: specialisation (<class 'qutip_cupy.dense.CuPyDense'>, <function inv_cupydense at 0x7f414e458f70>) has wrong number of parameters: needed types for ('data',), an output type and a callable

I suppose qutip's API has changed sometime in the last two years and that made it incompatible with this backend. If this project is still alive, could someone take a look at relevant sections and fix what's needed to get it to run? I myself am not familiar with qutip or its inner workings, so I would have to catch up on a lot first to solve it myself...
@hodgestar @leofang in case either of you still consider yourself active in this project :)

Sorry, I am no longer active 😅 I guess there exists a combination of compatible versions of QuTiP and this plugin for things to work, @hodgestar should know better than I do.

@rkevk Hello! I'm still active, but currently have quite a lot of other QuTiP work while we're in the QuTiP v5 alpha stage.
Yes, as you correctly deduced there have been some changes in QuTiP v5 since qutip-cupy was last updated. For this particular error, I think one only needs to change that line to:
data.inv.add_specialisations([(CuPyDense, CuPyDense, linalg.inv_cupydense)])

If you're up for creating a PR for that, I would be very grateful. The main blocker on my side is getting access to a machine with GPU support (or fixing the AWS GPU test runners).

@hodgestar pull request done, let me know if there's something else I should do in regards to this issue.
Pull requests introduces 2 changes:

locked version of packaging (<=21.3.) due to te deprecation of LegacyVersion attribute used in qutip-cupy in newer versions of packaging library
change to support QuTiPv5

Test was conducted on AWS GPU instance and basic check looks good but due to dated packages and qutip-cupy there is possibility for other issues to exist.
Will try to get AWS GPU test runners back online to see status of tests.


how to get your custom keybindings with lua?

What is your question?
i am working on a custom pause screen and i can't get the keybindings with lua

if keyJustPressed(key)
key can be 'space', 'left', 'up', 'down', 'right', 'pause', 'back, 'accept', 'reset'
these are the keybinds

didn't work

if keyJustPressed(key)
key can be 'space', 'left', 'up', 'down', 'right', 'pause', 'back, 'accept', 'reset'
these are the keybinds

didn't work

if keyJustPressed(key)
key can be 'space', 'left', 'up', 'down', 'right', 'pause', 'back, 'accept', 'reset'
these are the keybinds

wait it work! thx!!!!!