configureScope setUser does not work in Electron main

Important Details
How are you running Sentry?
Saas (sentry.io)
Sentry SDK: JS<EMAIL_ADDRESS>Description
In Electron main process Sentry.configureScope with scope.setUser does not work when initiated by Electron IPC. When I check issues on https://sentry.io I see "Unknown User"
However, it works when Sentry.configureScope is called on the main process start.
Steps to Reproduce
I do
    Sentry.configureScope(scope => {
        scope.setUser({
            id: "...",
            email: "..."
        });
        scope.setTag("company", "...");
    });

with some test data just after the Sentry.init in the main process, it works OK.
However, the app get's the real user data in the BrowserWindow, then sends these data by Electron IPC to the main process and the main process (ipcMain.on(...)) calls Sentry.configureScope. Then, I see just "Unknown User" , but the tag "company" is set properly.
When I try debug that, it works OK. When Is use Sentry.setUser(...) (without configureScope) is works OK, too.
What you expected to happen
I expect the user to be set by Sentry.configureScope always.

Hi @xmedeko. I can look into this but there are quite a few ways to configure and use Electron and I need a bit more context. The simplest way to do this is to supply a minimal example that reproduces the issue you are seeing.

I have Electron 12 with contextIsolation:true, nodeIntegration:false and I've hit the same bug as https://github.com/getsentry/sentry-electron/issues/316#issuecomment-827504173, that Sentry.configureScope does not send scope from browser to main. So, I've sent user info from browser by a custom ipcRenderer.send (exposed function in preload.js) and then ipcMain.on handler called Sentry.configureScope(scope => { scope.setUser(...) }).

There will shortly be a release of 2.4.1 that fixes #316

That's great! Anyway, it's strange this scenario fails.


Link to latest Meeting Minutes

Hi all,
I have a feature request.
I have several bookmarks to the meetings I am responsible for or at least I attend. These bookmarks link to the meeting series where you have an overview of all the minutes for this meeting series.
For me it would be very helpful (to save one click all the time) to have a link which opens the latest minutes of a meeting series. Hereby it does not matter if the latest minutes is already finalized or if it is still open.
Best regards, Christoph

Hi Wolfram,
I assume the marked link is the "latest link" (e.g. https://myserver.com/meetingseries/XYZXYZXYZ/latests) and I can right-click on it and choose "copy Hyperlink" or something similar.
In this case, I am fine with this solution for this power user feature. Please mention it in the documentation in case I forget the solution and new users can get to know it.
Best regards
Christoph


Allow git-branchless to build on Windows

Disable default-features for cursive, as ncurses-backend is the default,
which is not available on Windows and isn't required with
crossterm-backend selected.
Use a bundled build of sqlite3.

@waych Thanks for fixing this! I don't have a Windows device to test on. Did you try it out, or did you just fix the build failures?

Yeah I kicked the tires a bit this morning. Haven't done much other than initialize a few repos and play with git-sl and git-undo a bit so far. I was a big fan of hg changeset evolution on piper, so I'm excited to try restack.
Thanks for the extensions!

@waych You might also be interested to try git move by installing from the latest master. It's similar to hg rebase in that it can rebase entire subtree. It tries an in-memory rebase first.
I intend to reimplement git restack in terms of it, which should improve the experience. The in-memory rebasing would also be useful for e.g. rewording commit messages.
The performance git move for large repos also needs to be fixed.

FYI I tried more stuff and found that git restack and git move commands are still broken on Windows, along with various tests.  Most of the issues seem to deal with the hooks not being directly executable on Windows (have to load via bash.exe) and uses of "true and /bin/echo". Nothing major.
I'm working through a stack of fixes that should fix the above.  Got everything to pass on Windows, and am now reworking it so my changes don't also break Linux use. Will send PR soon.


react-slick is not working correctly in RTL language

This issue still repros in the latest version v0.27.9.
The web page language is the Hebrew language which is RTL language.
Repro steps: There are 5 slide pages in this slider using react-slick. If you open the web page contains this slider in the Chrome browser, press F12 to open the developer window, select the 'Toggle device toolbar' to switch to the mobile layout.
See this gif below:

There are two issues shown in this gif:

The switch sequence is not correct. It should switch from 'folder1' to 'folder5'.
During the transition from one slide to another slide, it will try to load two slides and end up with one slide.

Please let me know if I there is any question, thanks!

Hello, any updates on this issue ?

strangely I am able to solve RTL issue with below param meter to slider component
**
currentSlide={0}
rtl={true}
**
This props not documented anywhere

@mandadimuralidharreddy thanks. It worked for me.

if RTL works properly then LTR not working properly

+1

+1

Any updates ?

strangely I am able to solve RTL issue with below param meter to slider component ** currentSlide={0} rtl={true} ** This props not documented anywhere

i had the same issue, removing the 'fade'  attribute solved it

Is there any updates?
I saw the rtl problem on their documentation of RTL too.
it starts from the 2 slide instead of 1.


Feature: bootstrap test layouts

Task
Create set of layouts for testing extension

added simple layouts from official docs https://getbootstrap.com/docs/5.0/layout/grid/

I've added examples from official bootstrap5 docs. Need for additional testing layouts might rise in the future.


Not GPU detected using tensorflow/tensorflow:latest-gpu docker image

Issue type
Support
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
tensorflow/tensorflow:latest-gpu
Custom code
Yes
OS platform and distribution
Ubuntu 20.04
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
sudo docker run --gpus all -it --rm tensorflow/tensorflow:latest-gpu    python -c "import tensorflow as tf; print('Num GPUs Available:', len(tf.config.list_physical_devices('GPU')))"
2024-11-22 08:20:55.695121: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:477] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
E0000 00:00:1732263655.707089       1 cuda_dnn.cc:8310] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
E0000 00:00:1732263655.710704       1 cuda_blas.cc:1418] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2024-11-22 08:20:55.722395: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-11-22 08:20:57.119693: E external/local_xla/xla/stream_executor/cuda/cuda_driver.cc:152] failed call to cuInit: INTERNAL: CUDA error: Failed call to cuInit: CUDA_ERROR_COMPAT_NOT_SUPPORTED_ON_DEVICE: forward compatibility was attempted on non supported HW
2024-11-22 08:20:57.119716: I external/local_xla/xla/stream_executor/cuda/cuda_diagnostics.cc:137] retrieving CUDA diagnostic information for host: 81f8d81af78d
2024-11-22 08:20:57.119720: I external/local_xla/xla/stream_executor/cuda/cuda_diagnostics.cc:144] hostname: 81f8d81af78d
2024-11-22 08:20:57.119789: I external/local_xla/xla/stream_executor/cuda/cuda_diagnostics.cc:168] libcuda reported version is: 545.23.6
2024-11-22 08:20:57.119804: I external/local_xla/xla/stream_executor/cuda/cuda_diagnostics.cc:172] kernel reported version is: 470.256.2
2024-11-22 08:20:57.119808: E external/local_xla/xla/stream_executor/cuda/cuda_diagnostics.cc:262] kernel version 470.256.2 does not match DSO version 545.23.6 -- cannot find working devices in this configuration
Num GPUs Available: 0
Standalone code to reproduce the issue
sudo docker run --gpus all -it --rm tensorflow/tensorflow:latest-gpu    python -c "import tensorflow as tf; print('Num GPUs Available:', len(tf.config.list_physical_devices('GPU')))"

I've also followed this recommendation. https://stackoverflow.com/questions/79127647/tensorflow-docker-not-using-gpu/79214187#79214187

Relevant log output
root@35b972e97b30:/# nvidia-smi
Fri Nov 22 08:44:56 2024
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.256.02   Driver Version: 470.256.02   CUDA Version: 12.3     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  Off  | 00000000:01:00.0 Off |                  N/A |
| N/A   38C    P0    22W /  N/A |     10MiB /  5946MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
+-----------------------------------------------------------------------------+
root@35b972e97b30:/# nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Wed_Nov_22_10:17:15_PST_2023
Cuda compilation tools, release 12.3, V12.3.107
Build cuda_12.3.r12.3/compiler.33567101_0

I able to reproduce the same behavior from my end with TensorFlow 2.18.0. I've added output log below for reference
Hi, @learning-to-play Please take a look into this issue. Thank you.
(tf) (base) maayara@venkat-gpu1:~$ sudo docker run -it --rm  tensorflow/tensorflow:latest-gpu python
Python 3.11.0rc1 (main, Aug 12 2022, 10:02:14) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import tensorflow as tf
2024-11-26 07:16:02.810759: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:477] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
E0000 00:00:1732605362.831679       1 cuda_dnn.cc:8310] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
E0000 00:00:1732605362.838272       1 cuda_blas.cc:1418] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2024-11-26 07:16:02.860261: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
>>> tf.__version__
'2.18.0'
>>> print(tf.config.list_physical_devices('GPU'))
2024-11-26 07:16:22.228348: E external/local_xla/xla/stream_executor/cuda/cuda_driver.cc:152] failed call to cuInit: INTERNAL: CUDA error: Failed call to cuInit: UNKNOWN ERROR (34)
[]
>>>

Thank you!

@Venkat6871 Please route this issue to the TensorFlow GPU team.

@Venkat6871 what driver version did you replicate under?

Hi @MichaelHudgins ,
Apologies for the delay, Here i am attaching driver version.
(tf) maayara@venkat-gpu1:~$ nvidia-smi
Tue Dec 10 05:18:37 2024
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.183.01             Driver Version: 535.183.01   CUDA Version: 12.2     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  Tesla T4                       Off | 00000000:00:04.0 Off |                    0 |
| N/A   59C    P8              11W /  70W |      2MiB / 15360MiB |      0%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+

+---------------------------------------------------------------------------------------+
| Processes:                                                                            |
|  GPU   GI   CI        PID   Type   Process name                            GPU Memory |
|        ID   ID                                                             Usage      |
|=======================================================================================|
|  No running processes found                                                           |
+---------------------------------------------------------------------------------------+
(tf) maayara@venkat-gpu1:~$

Thank you!


What exactly is the yml for the named conditions

This is super frustrating.
At the very beginning of this documentation it states:
On each step and job, you can specify the conditions under which the step or job will run.

Only when all previous tasks have succeeded
Even if a previous task has failed, unless the build or release was canceled
Even if a previous task has failed, even if the build was canceled
Only when a previous task has failed
Custom conditions

But nowhere on the page are the corresponding formulae documented.
Additionally in the full definition for the -task method "condition" is defined as a string, but it actually is a boolean.

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

ID: 3f151218-9a11-0078-e038-f96198a76143
Version Independent ID: 09c4d032-62f3-d97c-79d7-6fbfd89910e9
Content: Conditional tasks - Azure Pipelines
Content Source: docs/pipelines/process/conditions.md
Product: devops
Technology: devops-cicd
GitHub Login: @andyjlewis
Microsoft Alias: alewis

I played around with a task in the class editor and kept checking the YAML, this is what I've got:

Only when all previous tasks have succeeded: Not sure, this is the "default" so it doesn't show up in the YAML, I suspect it's succeeded()
Even if a previous task has failed, unless the build or release was canceled: succeededOrFailed()
Even if a previous task has failed, even if the build was canceled: always()
Only when a previous task has failed: failed()
Custom conditions: the documentation appears to cover this, indicating that a custom condition is just an expression (with the above values mixed in)

It's the end of the day so I won't make a PR right now but maybe next week I'll add these to the doc and make a PR

also not sure what to do about the boolean thing, using condition in VSCode with the Azure Pipelines extension autocomplete suggests either true or false, but I think that's an issue with the condition definition not the documentation, don't know where that data comes from

Or, presumably, now that I think about it, those are functions that will return a true or false value, so it's technically correct that Condition requires a boolean.  And now I see that the status are documented on the expressions page, https://docs.microsoft.com/en-us/azure/devops/pipelines/process/expressions?view=azure-devops, which explains that they're functions that will return a boolean value

Indeed, this link does appear to answer the originally posed question:
https://docs.microsoft.com/en-us/azure/devops/pipelines/process/expressions?view=azure-devops#job-status-functions
Thanks for the investigation.

Although, I'm going to leave this open since these descriptions should simply be on the original page I was looking at, where they are first described.

It looks like this was updated since this ticket was opened and there is now a link to the Job status functions.


[PartEditor] Introduce initial PartEditor

This will introduce initial PartEditor, to provide partition file editor.
ONE-vscode-DCO-1.0-Signed-off-by: SaeHie Park<EMAIL_ADDRESS>

initial screen looks like this;


How to enable loop_detection in COLMAP mapping?

Hi, thanks for your efforts of integrating the COLMAP for Python API !
I wondered how to enable loop_detection in pycolmap. I first found loop_detection flag in colmap::SequentialMatchingOptions with not seeing relevant API in pycolmap, could you please how to do that? Or is this part still under developing?
I use triangulate_points() in
https://github.com/colmap/pycolmap/blob/de3ce4c70678818950193a39425aa35cb1f10139/pipeline/sfm.cc#L28C1-L35C36
where there is a mapper_options leading to colmap::RunPointTriangulatorImpl->IncrementalMapperOptions->IncrementalMapper::Options
I also found a clue in your repository, how to modify the options?
https://github.com/colmap/pycolmap/blob/de3ce4c70678818950193a39425aa35cb1f10139/pipeline/match_features.cc#L133C2-L195C48

PyCOLMAP indeed supports sequential matching with loop closure:
help(pycolmap.SequentialMatchingOptions)  # check the options and their defaults
opts = pycolmap.SequentialMatchingOptions(...)
pycolmap.match_exhaustive(database_path, matching_options=opts)

This should be used as replacement of exhaustive matching, before the reconstruction process.


_get_configuration_warning() dialog box height does not return to normal after removing newlines

Godot version:
v3.2.2.stable.official (on steam)
OS/device including version:
Windows 10
(Version 10.0.19041 Build 19041)
Issue description:
When you add newlines to an overridden _get_configuration_warning() tool script, the dialog box does not fit to height.
This is demonstrated when you add several "\n\n\n\n" in the message, view it, and then remove the newlines. The dialog box has the same height, and does not shrink.
Default script message:

Script message after adding newlines:

Different script that does not have any newlines also show additional height:

Steps to reproduce:

Create a Node
Add script:

tool
extends Node

func _get_configuration_warning():
	var message = ""
	if(get_child_count() < 1):
		message += "Need a minimum of 1 child!"
	return message

Confirm the dialog box displays properly.
Add several newlines to the end of the message.

tool
extends Node

func _get_configuration_warning():
	var message = ""
	if(get_child_count() < 1):
		message += "Need a minimum of 1 child!\n\n\n\n\n\n\n\n"
	return message

View the dialog box, notice we have several new lines and that the height is longer.
Remove the newlines.

tool
extends Node

func _get_configuration_warning():
	var message = ""
	if(get_child_count() < 1):
		message += "Need a minimum of 1 child!"
	return message

View the dialog box, notice the new lines are not gone.

Unfounded theory on why this is happening: I notice that multiple dialog boxes from different scripts seem to share this extra height. Perhaps we are storing dialog box data (width/height) in places we should not? Are we ignoring empty spaces so that the newlines are being kept?
Minimal reproduction project:
Node.zip

Unless its actually keeping the new line characters in the text, this should be because labels dont shrink to the size of their text. And instead of instancing a whole new dialogue, the old one is reused.


Configurable Actuator endpoint & VM args - Maven Home/Binary separate configurations - Minor Fix in EcosystemManager - Shutdown endpoint enabled

Hi there, this PR addresses the following aspects:

Configurable Actuator endpoint & VM args: the current Trampoline only works when the actuator endpoint doesn't have a prefix (management.context-path). Thus the status update and the kill button don't work for those projects. Also in Spring microservices it's very usual that we need to set up VM arguments. Now we can do it.
Maven Home/Binary separate configurations: I am working with Ubuntu Linux. This distribution has its Maven Home in /usr/share/maven and its Maven Binary in /usr/bin. Now we can set up different Maven Home/Binary path. If the user doesn't specify the binary value it is derived from the Maven Home value -> MAVEN_HOME/bin
Minor Fix in EcosystemManager
Shutdown endpoint enabled: from Spring Boot 1.5+ endpoints such as /shutdown are secured by default. I have added a -Dmanagement.security.enabled=false flag.

I have tested this changes on Windows and Linux Ubuntu.

Hi sr Jose A. Iñigo,
First of all, thanks for contributing on Trampoline! This is for you: 🥇
As soon as I will complete my current task, I will proceed to review your pull request and to do a double check on Mac OS .
Again thanks for your time invested here and feel free to drop any comment or advice and you are wellcome to keep contributing... there are several features to be implemented!!
Also, I would like you to be included on Trampoline Team section, if so I will need the following:
Mandatory: Your name and a short description about you
Optional: Picture, Linkedin profile and/or Twitter profile.
<EMAIL_ADDRESS>#KeepCoding&Enjoying

Hi Ernest,
I hope you find this PR useful. In our current infrastructure we couldn't use Trampoline it without these changes. I'll email you the info for the team section. I'll be glad to keep contributing.
Regards!!

Hi Jose,
Well done! It's definitely an useful PR. Congatulations! I'm sure you will bring value on Trampoline! 👍
Three points I would like to mention (I will take care of them, no worries):
1. -Dmanagement.security.enabled=false
I'm sure you did it in order to avoid a possible firewall it could be, as spring documentation suggest:
"If you are deploying applications behind a firewall, you may prefer that all your actuator endpoints can be accessed without requiring authentication. You can do this by changing the management.security.enabled"
If we want it, we sould add security starter on microservice-example:

org.springframework.boot
spring-boot-starter-security

Otherwise it will fail when launching with this error below:
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'managementServerProperties' defined in class path resource [org/springframework/boot/actuate/autoconfigure/ManagementServerPropertiesAutoConfiguration.class]: Initialization of bean failed; nested exception is java.lang.NoClassDefFoundError: org/springframework/security/config/http/SessionCreationPolicy
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553) ~[spring-beans-4.2.3.RELEASE.jar:4.2.3.RELEASE]
....
Caused by: java.lang.ClassNotFoundException: org.springframework.security.config.http.SessionCreationPolicy
at java.net.URLClassLoader.findClass(URLClassLoader.java:381) ~[na:1.8.0_101]
at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[na:1.8.0_101]
at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[na:1.8.0_101]
... 51 common frames omitted
2. Null old maven attribute on Ecosystem class, breaking change
Just a comment; since you changed mavenLocation attribute name, I could not start old declared instances until I introduced maven location again.
An option would be to keep this old attribute mark it's get as deprecated and when on getMavenHomeLocation check if mavenHomeLocation is null or empty an if so, set it with old mavenLocation.
Not sure if make sense at this point in time, but it's an important detail to realize.
3. New Microservice Form
Add * for mandatory fields
Add placeholder new optional fields
As a user it's useful when sees new functionality for first time (for intance: how should I put this actuator prefix? Do I need to fill this field?)
Anyway, great job and feel this project like yours because you are in (as long as you wish)!
#KeepCoding&Enjoying


Improve browser launch in Linux distribution

Describe the bug
It would be worth making sure we are using the most appropriate API call to launch the browser on Linux. In some circumstances, this can happen:
You have 15876M of free memory.
Your current configuration is set to use 1400M of memory.
OpenRefine can run better when given more memory. Read our FAQ on how to allocate more memory here:
https://github.com/OpenRefine/OpenRefine/wiki/FAQ:-Allocate-More-Memory
Starting OpenRefine at 'http://<IP_ADDRESS>:3333/'

15:02:40.754 [            refine_server] Starting Server bound to '<IP_ADDRESS>:3333' (0ms)
15:02:40.755 [            refine_server] refine.memory size: 1400M JVM Max heap:<PHONE_NUMBER> (1ms)
15:02:40.763 [            refine_server] Initializing context: '/' from '/home/projadmin/dj/openrefine-3.3/webapp' (8ms)
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/projadmin/dj/openrefine-3.3/server/target/lib/slf4j-log4j12-1.7.18.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/projadmin/dj/openrefine-3.3/webapp/WEB-INF/lib/slf4j-log4j12-1.7.18.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
15:02:41.204 [                   refine] Starting OpenRefine 3.3 [58b839b]... (441ms)
15:02:41.204 [                   refine] initializing FileProjectManager with dir (0ms)
15:02:41.204 [                   refine] /home/projadmin/.local/share/openrefine (0ms)
15:02:44.359 [                   refine] Sorry, some error prevented us from launching the browser for you.

It would be worth checking that we are using the best approach to open http://localhost:3333/ - the API to do this might have evolved. We could try different APIs in turn, too (making sure that we do not launch it twice).
Desktop (please complete the following information):

OS: Linux

OpenRefine (please complete the following information):

Version 3.3

Additional information
Mailing list thread: https://groups.google.com/forum/#!topic/openrefine/oo4W-zlSqc8

We could probably start by logging the exception so which know exactly which "some error" caused the problem.
One thing to try would be using the command open  http://<IP_ADDRESS>:3333/ at the shell and see if that opens the browser. If it doesn't it might given an error which indicates what the problem is.

Turns out that this is a popular issue in linux as I saw here: https://github.com/openmole/openmole/issues/140
The dependence we have in this case is the java.awt.Desktop. I would suggest using some other suitable call in case, like Runtime from java.lang...

Yes! Runtime.exec()

https://stackoverflow.com/a/54869038/1100717

This is actually what I had in mind. The client initially tries to launch using desktop, so adding another option to handle the not supported os could fix it. I currently use Linux only so I have been able to try this method on another application and it works well. Will need to try out with windows.

I can try out this on windows as I am window user. I would like to work on this issue. Kindly assign to me.

Hey @Binita-tech , thanks for opting 😄
I think I definitely needed help in the windows area. Please help out with this issue. I have not done my tests on the project itself, but I can show you how I tried it out and maybe that will land a solution. I will be assigning it to you.


Save activated ExperimentsDescriptions in DB

Save activated ExperimentsDescriptions in Experiments table
Call updateActivatedExperiments method in experiments activate method
Load activated ExperimentsDescriptions along with other experiment meta
bug/263139421

Trying to grok the structure of experiments in the database...
experiments table
---
key: experiment_payload          value: experiment a
key: experiment_payload          value: experiment b
key: experiment_active_payload   value: experiment a
key: experiment_active_payload   value: experiment c

Does that match your understanding?

Yeah, that's how it works in iOS. One table and keys that differentiate the data


Keybase: Files need to be rekeyed

I had to reinstall OSX on my Mac, and when I reinstalled keybase, I didn't have access to my paper key.  I then took the obviously foolish step of reissuing the paper key for my account, and now I'm receiving this message whenever I try to access my private kbfs folders:
Keybase: Files need to be rekeyed
Please open one of your other computers to unlock /keybase/private/ringmaster

Suffice to say that this Mac was is only system where I had keybase working reliably (keybase device list shows that I have one system apart from this Mac with keybase installed, but I haven't figured out how to upgrade that one on Ubuntu past version 0.8.25), and I'd just like it all to work again on this Mac.
My shared private folders seem to work fine, after creating one for a user that I hadn't created a folder for before, but my own private folder insists upon being rekeyed.
 END KEYBASE SALTPACK SIGNED MESSAGE.

Sorry for the trouble, I've already done safe things with my new paper key.

Thanks for the but report.
A question.  When you reinstalled on OSX, what was the previous version of
keybase?
Even though you reinstalled the software, you should have retained your
previous device key. Did you do anything like manually deleting files?
Thanks.
On Thursday, June 30, 2016, Owen Winkler<EMAIL_ADDRESS>wrote:

I had to reinstall OSX on my Mac, and when I reinstalled keybase, I didn't
have access to my paper key. I then did took the obviously foolish step of
reissuing the paper key for my account, and now I'm receiving this message
whenever I try to access my private kbfs folders:
Keybase: Files need to be rekeyed
Please open one of your other computers to unlock /keybase/private/ringmaster
Suffice to say that this Mac was is only system where I had keybase
working reliably (keybase device list shows that I have one system apart
from this Mac with keybase installed, but I haven't figured out how to
upgrade that one on Ubuntu past version 0.8.25), and I'd just like it all
to work again on this Mac.
My shared private folders seem to work fine, after creating one for a user
that I hadn't created a folder for before, but my own private folder
insists upon being rekeyed.
 END KEYBASE SALTPACK SIGNED MESSAGE.
Sorry for the trouble, I've already done safe things with my new paper key.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/3286, or mute the thread
https://github.com/notifications/unsubscribe/AA05_wPvBCm3l1CXjogwPTWVqapkHu6rks5qQ8CggaJpZM4JCJJv
.

Hi @ringmaster -- in theory wiping your OS X install and hence the local keybase files shouldn't revoke your old paper key -- it looks like you purposely did that as part of the new installation?  If your old paper key was still valid, you'd be able to recover the data, but unfortunately it was revoked; you should have been able to make a new paper key as part of the new provisioning without revoking your old paper key.  Do you remember if you explicitly chose to revoke it?
So sadly I think the only option is to reset your folders.  I see your message above, so I can go ahead and do that, but I'll wait for your confirmation again.

Going through the process of installing Keybase, I didn't realize that I could keep my old paper key and issue a new one.  I feel like I followed default prompts, though I can't be sure I didn't explicitly do something that it was warning me against.  It may be worthwhile reviewing the UI here to ensure that others don't make my same stupid mistake.
Yes, please reset my folders.  Thanks!

^ @patrickxb @maxtaco: do you know of anything in the provisioning process that would lead someone to revoke their old paper key?
I'll get to the folder resets soon and post back here when it's done.

Drat.  You know what, this is my fault.  I totally did this at the command line (while trying to figure out what my key was), and hit "y" instead of "n" in response to the "Also revoke existing key" prompt.
  Sincerest apologies.

Right, keybase paperkey gen prompts to ask if you'd like to revoke each existing paper key.
Perhaps we should be clear that it is ok to have multiple before starting that interaction.  The default is no, but still, couldn't hurt to be more clear.

@ringmaster: ok those folders are reset.  Can you confirm things look ok now?

Can you confirm things look ok now?

Yes, works great!  Thanks!

Cool, sorry for the inconvenience!


Do NOT allow variables in lambda expressions to shadow variables already defined in scope

Eliminate a class of bugs.
Rename lambda variables different from scoped ones.
This PR addresses issue #1844.

Closing unmerged, reasoning is in the associated issue: https://github.com/angular/angular-cli/issues/1844#issuecomment-242985449


tests: spin lock timeout test spin time

The spin loop to ensure time goes past the timeout is done in terms of the core clock, while the spin lock is timed on the system clock.
This difference is exasperated on systems where the core clock is much faster than the system clock and the test failed. Add a significant multiplier so the test works even when the system clock is much slower.
Signed-off-by: Tom Burdick<EMAIL_ADDRESS>

CI seems to have gotten stuck on something here, will have to rebase and push it seems losing all my +1's :(


Introduce a safe alternative to PatrolFinder.waitUntilVisible() that doesn't throw after timeout

Feature request:
Sometimes there are cases when we expect something to appear on the screen (after transition for ex.) and have to skip it and continue. So we have to wait for that element(s) but they might appear and might not appear. So using .waitUntilVisible() is not appropriate for that case as if element(s) not appear we receive exception and execution failed.
I propose update waiter with smth like that .waitUntilVisible({Duration? timeout, bool safe = false}) and setting optional safe=true if we want to wait for elem and not getting breaking exception in case nothing found.

Hi @ehabibov 👋 Thanks for creating this issue!
This sounds good to me. We'll think about it. For now, I suggest you create an extension method safeWaitUntilVisible/maybeWaitUntilVisible/tryWaitUntilVisible yourself:
extension PatrolFinderX on PatrolFinder {
  Future<void> tryWaitUntilVisible({Duration? timeout}) async {
    try {
      await tester.waitUntilVisible(this, timeout: timeout);
    } on WaitUntilVisibleTimeoutException catch (_) {
      // do nothing, it's okay
    }
  }
}
}

@ehabibov Let me know if the workaround works for you.

@bartekpacia yes, thank you, for hint.
I'll let you know soon.

@bartekpacia I'm sorry for delay. Yes, workaround worked and totally eligible - thank you. Would be nice having that in repo but not urgent at all.
Might be a case for .waitUntilExists() also but not sure as don't get for now how does it work (as I see all participant elems in overall widget tree but .waitUntilExists() works like .waitUntilVisible() when .waitUntilVisible() does not work).

We decided to not add this feature, workaround mentioned earlier can be used.


Update Stan to 2.36.0

Stan 2.36 released this morning.
This PR:

Updates the backend to use a newer commit of tinystan which includes Stan 2.36
Updates our copy of stanc.js

Also updates the docker image to use a newer emscripten and the new repo link for TBB.
To verify, you can use a new function like
generated quantities {
  real rng = beta_neg_binomial_rng(0.2,0.4,0.3);
}

@magland how manual is the process to update the public server?


Routing rules overview doc

This change is

I will hold off on merging this until the bookinfo demo is updated to conform. Unfortunately bookinfo isn't working ATM with latest images - some kind of problem with ingress controller that needs to be debugged and fixed first


[core] Save a few bytes

This is a follow-up on #34289, I'm giving up on the idea of having title !== '' && title !== node an invalid value. We can be less opinionated about the best practice. Instead:

I believe we can shorten the logic
While I am at it, I'm continuing the migration to use screen as much as possible that Sebastian started. It's supposed to be simpler to work with.

What's the rationale behind using screen in favor of render result methods?

What's the rationale behind using screen in favor of render result methods?

@michaldudak The rationale was that it's easier to work with, meaning when you write a new test, it's easier to access a global variable than to go up to the render() to get your helper, and then go down to use it. This problem alone could be solved by writing something like const mountingPoint = render( but we never mount two components at the same time (I assume nor will we ever need to), so why not move this even one scope further up?
@eps1lon Does it match with the value you envision?
I can revert the changes in the tests if we are not comfortable with them.

What's the rationale behind using screen in favor of render result methods?

render results will break once you introduce a Portal. screen is easier to c&p around.

:+1: I'm fine with this change. My only concern is that it doesn't really fall into the "Save a few bytes" label. Could we make it a separate PR?


Fix segmentation fault on key retrieve using sdsdup and sdsfree

If I use the sample mybot.c implementation I get a segmentation fault on key retrieval.
If I set a key and then I try to retrieve it I get:
....Sent message IDs: chat_id:131178217 message_id:35
.0. fabio? |
Errore di segmentazione
It seems to be fixed by using sdsdup and corresponding sdsfree for the request copy.

Hi Fabio, if you get the segfault there is a problem, however the fix looks like randomly tried just to make it work. I can't see why there is any need to switch to sdsdup(), nor the free outside the if is an error, since sdsfree() will do nothing if NULL is passed to it. It's better to fully understand the bug :) Please could you send me the trace you get with the debugger? Thank you.

Please could you try adding the following lines on top of mybot.c to see if it gets fixed?
#define _DEFAULT_SOURCE
#define _XOPEN_SOURCE 600

That's the trace I get on the error:
Thread 8 "mybot" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff6b6e6c0 (LWP 198797)]
0x000055555555f421 in handleRequest (dbhandle=0x7ffff0001828, br=0x5555556b7cb0) at mybot.c:56
56	        copy[reqlen-1] = 0;
(gdb) backtrace
#0  0x000055555555f421 in handleRequest (dbhandle=0x7ffff0001828, br=0x5555556b7cb0) at mybot.c:56
#1  0x000055555555e8f7 in botHandleRequest (arg=0x5555556b7cb0) at botlib.c:601
#2  0x00007ffff7c45044 in start_thread (arg=) at ./nptl/pthread_create.c:442
#3  0x00007ffff7cc561c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Yes the two defines provided fix the issue :)

Thanks, I pushed the changes :)


Fault Tolerance

We need to figure out how fault tolerance is going to be handled in this system. Perhaps for the moment we can just implement a replay message if not acknowledged mechanism.

Anti-Entropy will be what provides our fault tolerance for lower consistency levels, and Raft has an automatic method of doing this.


ImportError: No module named '_pywrap_tensorflow_internal'

System information

OS Platform and Distribution: Windows 10
TensorFlow installed from (source or binary): i don't know which one; I'm fairly new to this. i installed via the command pip install --user --upgrade tensorflow iirc
TensorFlow version: I am not sure; but its the version that pip currently installs i guess.
Python version: 3.8.3
Installed using virtualenv? pip? conda?: pip, as stated above.
CUDA/cuDNN version: unsure how to find this.
GPU model and memory: Nvidia GeForce gtx970, 3.5gb (if I'm not mistaken)

Describe the problem
I downloaded this repo and attempted to run "test.py" after installing all requirements successfully:
https://github.com/ialhashim/DenseDepth
i get an error message:
ModuleNotFoundError: No module named '_pywrap_tensorflow_internal'
Any other info / logs
please see test.py from the above repository:
https://github.com/ialhashim/DenseDepth/blob/master/test.py
here is my stack trace:
Traceback (most recent call last):
File "C:\Users\aekna\AppData\Roaming\Python\Python38\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 18, in swig_import_helper
fp, pathname, description = imp.find_module('_pywrap_tensorflow_internal', [dirname(file)])
File "C:\Program Files (x86)\Python38-32\lib\imp.py", line 296, in find_module
raise ImportError(_ERR_MSG.format(name), name=name)
ImportError: No module named '_pywrap_tensorflow_internal'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\aekna\AppData\Roaming\Python\Python38\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "C:\Users\aekna\AppData\Roaming\Python\Python38\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 28, in
_pywrap_tensorflow_internal = swig_import_helper()
File "C:\Users\aekna\AppData\Roaming\Python\Python38\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 20, in swig_import_helper
import _pywrap_tensorflow_internal
ModuleNotFoundError: No module named '_pywrap_tensorflow_internal'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "test.py", line 8, in
from keras.models import load_model
File "C:\Users\aekna\AppData\Roaming\Python\Python38\site-packages\keras_init_.py", line 3, in
from . import utils
File "C:\Users\aekna\AppData\Roaming\Python\Python38\site-packages\keras\utils_init_.py", line 6, in
from . import conv_utils
File "C:\Users\aekna\AppData\Roaming\Python\Python38\site-packages\keras\utils\conv_utils.py", line 9, in
from .. import backend as K
File "C:\Users\aekna\AppData\Roaming\Python\Python38\site-packages\keras\backend_init_.py", line 1, in
from .load_backend import epsilon
File "C:\Users\aekna\AppData\Roaming\Python\Python38\site-packages\keras\backend\load_backend.py", line 90, in
from .tensorflow_backend import *
File "C:\Users\aekna\AppData\Roaming\Python\Python38\site-packages\keras\backend\tensorflow_backend.py", line 5, in
import tensorflow as tf
File "C:\Users\aekna\AppData\Roaming\Python\Python38\site-packages\tensorflow_init_.py", line 24, in
from tensorflow.python import pywrap_tensorflow  # pylint: disable=unused-import
File "C:\Users\aekna\AppData\Roaming\Python\Python38\site-packages\tensorflow\python_init_.py", line 49, in
from tensorflow.python import pywrap_tensorflow
File "C:\Users\aekna\AppData\Roaming\Python\Python38\site-packages\tensorflow\python\pywrap_tensorflow.py", line 74, in
raise ImportError(msg)
ImportError: Traceback (most recent call last):
File "C:\Users\aekna\AppData\Roaming\Python\Python38\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 18, in swig_import_helper
fp, pathname, description = imp.find_module('_pywrap_tensorflow_internal', [dirname(file)])
File "C:\Program Files (x86)\Python38-32\lib\imp.py", line 296, in find_module
raise ImportError(_ERR_MSG.format(name), name=name)
ImportError: No module named '_pywrap_tensorflow_internal'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\aekna\AppData\Roaming\Python\Python38\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "C:\Users\aekna\AppData\Roaming\Python\Python38\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 28, in
_pywrap_tensorflow_internal = swig_import_helper()
File "C:\Users\aekna\AppData\Roaming\Python\Python38\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 20, in swig_import_helper
import _pywrap_tensorflow_internal
ModuleNotFoundError: No module named '_pywrap_tensorflow_internal'
Failed to load the native TensorFlow runtime.

@Fennecai,
The GitHub repo you have linked was tested with TF 1.x. I was able to run the test.py file on TF v1.15 without any issues. Please find the gist of it here. Thanks!

A similar problem is raised for me. If you can help it will be greatful
ImportError                               Traceback (most recent call last)
~.anaconda\anaconda1\envs\deeplearning\lib\site-packages\tensorflow\python\pywrap_tensorflow.py in
57
---> 58   from tensorflow.python.pywrap_tensorflow_internal import *
59
~.anaconda\anaconda1\envs\deeplearning\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py in
27             return _mod
---> 28     _pywrap_tensorflow_internal = swig_import_helper()
29     del swig_import_helper
~.anaconda\anaconda1\envs\deeplearning\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py in swig_import_helper()
23             try:
---> 24                 _mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
25             finally:
~.anaconda\anaconda1\envs\deeplearning\lib\imp.py in load_module(name, file, filename, details)
241         else:
--> 242             return load_dynamic(name, filename, file)
243     elif type_ == PKG_DIRECTORY:
~.anaconda\anaconda1\envs\deeplearning\lib\imp.py in load_dynamic(name, path, file)
341             name=name, loader=loader, origin=path)
--> 342         return _load(spec)
343
ImportError: DLL load failed while importing _pywrap_tensorflow_internal: The specified module could not be found.
During handling of the above exception, another exception occurred:
ImportError                               Traceback (most recent call last)
 in
----> 1 from keras.layers import Convolution2D
~.anaconda\anaconda1\envs\deeplearning\lib\site-packages\keras_init_.py in
1 from future import absolute_import
2
----> 3 from . import utils
4 from . import activations
5 from . import applications
~.anaconda\anaconda1\envs\deeplearning\lib\site-packages\keras\utils_init_.py in
4 from . import data_utils
5 from . import io_utils
----> 6 from . import conv_utils
7 from . import losses_utils
8 from . import metrics_utils
~.anaconda\anaconda1\envs\deeplearning\lib\site-packages\keras\utils\conv_utils.py in
7 from six.moves import range
8 import numpy as np
----> 9 from .. import backend as K
10
11
~.anaconda\anaconda1\envs\deeplearning\lib\site-packages\keras\backend_init_.py in
----> 1 from .load_backend import epsilon
2 from .load_backend import set_epsilon
3 from .load_backend import floatx
4 from .load_backend import set_floatx
5 from .load_backend import cast_to_floatx
~.anaconda\anaconda1\envs\deeplearning\lib\site-packages\keras\backend\load_backend.py in
88 elif _BACKEND == 'tensorflow':
89     sys.stderr.write('Using TensorFlow backend.\n')
---> 90     from .tensorflow_backend import *
91 else:
92     # Try and load external backend.
~.anaconda\anaconda1\envs\deeplearning\lib\site-packages\keras\backend\tensorflow_backend.py in
3 from future import print_function
4
----> 5 import tensorflow as tf
6 from tensorflow.python.eager import context
7 from tensorflow.python.framework import device as tfdev
~.anaconda\anaconda1\envs\deeplearning\lib\site-packages\tensorflow_init_.py in
39 import sys as _sys
40
---> 41 from tensorflow.python.tools import module_util as _module_util
42 from tensorflow.python.util.lazy_loader import LazyLoader as _LazyLoader
43
~.anaconda\anaconda1\envs\deeplearning\lib\site-packages\tensorflow\python_init_.py in
48 import numpy as np
49
---> 50 from tensorflow.python import pywrap_tensorflow
51
52 # Protocol buffers
~.anaconda\anaconda1\envs\deeplearning\lib\site-packages\tensorflow\python\pywrap_tensorflow.py in
67 for some common reasons and solutions.  Include the entire stack trace
68 above this error message when asking for help.""" % traceback.format_exc()
---> 69   raise ImportError(msg)
70
71 # pylint: enable=wildcard-import,g-import-not-at-top,unused-import,line-too-long
ImportError: Traceback (most recent call last):
File "C:\Users\BASHEER.anaconda\anaconda1\envs\deeplearning\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "C:\Users\BASHEER.anaconda\anaconda1\envs\deeplearning\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 28, in
_pywrap_tensorflow_internal = swig_import_helper()
File "C:\Users\BASHEER.anaconda\anaconda1\envs\deeplearning\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 24, in swig_import_helper
_mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
File "C:\Users\BASHEER.anaconda\anaconda1\envs\deeplearning\lib\imp.py", line 242, in load_module
return load_dynamic(name, filename, file)
File "C:\Users\BASHEER.anaconda\anaconda1\envs\deeplearning\lib\imp.py", line 342, in load_dynamic
return _load(spec)
ImportError: DLL load failed while importing _pywrap_tensorflow_internal: The specified module could not be found.
Failed to load the native TensorFlow runtime.
See https://www.tensorflow.org/install/errors
for some common reasons and solutions.  Include the entire stack trace
above this error message when asking for help

@basheerghub,
This solution from a similar issue should fix the ImportError.
If you still need further help, please submit a new issue from this link and fill in the template, so that we can track the issue there. Thanks!

It worked for me after doing this command :
pip install tensorflow-gpu == 1.15.5

I was previously with tensorflow-gpu 1.15.0 when it was showing the error


vswhere does not work with preview version of VS

C:\GIT\ELL>external\vswhere.2.1.3\tools\vswhere.exe -legacy
Visual Studio Locator version 2.1.3 [query version 1.17.1176.60362]
Copyright (C) Microsoft Corporation. All rights reserved.

C:\GIT\ELL>external\vswhere.2.1.3\tools\vswhere.exe
Visual Studio Locator version 2.1.3 [query version 1.17.1176.60362]
Copyright (C) Microsoft Corporation. All rights reserved.

C:\GIT\ELL>"%ProgramFiles(x86)%\Microsoft Visual Studio\Installer\vswhere.exe"
Visual Studio Locator version 2.5.2+gebb9f26a3d [query version 1.17.1176.60362]
Copyright (C) Microsoft Corporation. All rights reserved.

C:\GIT\ELL>

This is the DevEnvDir value:
DevEnvDir=C:\Program Files (x86)\Microsoft Visual Studio\Preview\Enterprise\Common7\IDE\

Per the /? usage, you need to pass -prerelease.


controller.go:96: No RenderArg names found for Render call on line 5 (Action Test.Index )

Hi friends.
I cannot reference variants in templates. The console output line:
controller.go:96: No RenderArg names found for Render call on line 5 (Action Test.Index )

Here is my controllers/test.go
    package controllers

    import "github.com/revel/revel"

    type Test struct {
            *revel.Controller
    }

    func (c Test) Index(xxx string) revel.Result {
            println(xxx)
            return c.Render(xxx)
    }

Then, I read controller.go, I found this:
    func (c *Controller) Render(extraRenderArgs ...interface{}) Result {
        // Get the calling function name.
        _, _, line, ok := runtime.Caller(1)
        if !ok {
            ERROR.Println("Failed to get Caller information")
        }

        // Get the extra RenderArgs passed in.
        if renderArgNames, ok := c.MethodType.RenderArgNames[line]; ok {
            if len(renderArgNames) == len(extraRenderArgs) {
                for i, extraRenderArg := range extraRenderArgs {
                    c.RenderArgs[renderArgNames[i]] = extraRenderArg
                }
            } else {
                ERROR.Println(len(renderArgNames), "RenderArg names found for",
                    len(extraRenderArgs), "extra RenderArgs")
            }
        } else {
            ERROR.Println("No RenderArg names found for Render call on line", line,
                "(Action", c.Action, ")")
        }

        return c.RenderTemplate(c.Name + "/" + c.MethodType.Name + "." + c.Request.Format)
    }

I change _, _, line, ok := runtime.Caller(1) to xa, xb, line, ok := runtime.Caller(1) and dump them, I get follow error:
2015/01/23 02:32:54 controller.go:96: No RenderArg names found for Render call on  134586657 /home/jcz/go/src/github.com/revel/revel/samples/chat/app/controllers/test.go  line 5 (Action Test.Index )

Then I read other codes in revel, I known revel expect got 11 instead of 5.
And I think 11 is a right value, not 5. Maybe there is a bug in gogcc.
I known I'd better to report this issue to golang project.
But I cannot reproduce this issue without revel, because I am a beginner of golang(I learn golang since today).

Thank you.

@jinchizhong we'll need to test this issue to see if we can reproduce it. I can't do that now, but I'll try to soon.
In the mean time, can you try something like:
func (c Test) Index() revel.Result {
    xxx := "test string
    return c.Render(xxx)
}

Hi @brendensoares
I change controllers/test.go to:
package controllers

import "github.com/revel/revel"

type Test struct {
    *revel.Controller
}

func (c Test) Index() revel.Result {
    xxx := "Test String"
    return c.Render(xxx)
}

Nothing is changed.
BTW, the official demo is also cannot works good in my machine.
Here are two warnings:
2015/01/23 04:11:42 controller.go:96: No RenderArg names found for Render call on  134580909 /home/jcz/go/src/github.com/revel/revel/samples/chat/app/controllers/app.go  line 7 (Action Application.Index )
2015/01/23 04:12:09 controller.go:96: No RenderArg names found for Render call on  134586543 /home/jcz/go/src/github.com/revel/revel/samples/chat/app/controllers/test.go  line 5 (Action Test.Index )

revel/revel/samples/chat/app/controllers/app.go is also work badly.
It must be 12 not 7 in revel/revel/samples/chat/app/controllers/app.go

Hi @brendensoares
I'm very happy to tell you a message.
I install another package in ubuntu that also provide go.
And then I rerun the demo, everything is OK.
I hope that can help you.
sudo apt-get install golang

So, the issue has been resolved? I'm closing it then. Feel free to reopen.

Confirm. I had the same issue. And it disappeared after updating golang in Debian (from 1.3.1 to 1.3.3) and rebuilding the project.

Sorry. It appared again:
ERROR 2015/05/07 10:16:16 controller.go:97: No RenderArg names found for Render call on line 281 (Action Units.Index )

I tried my xxx suggestion above in Revel v0.12 and Go 1.4 on Mac OS X and it works fine.
I'm going to close this unless it can be proven. We could schedule a time to talk on IRC if needed to confirm the issue.
Thanks.

Is there any hope of re-opening this? We are experiencing the exact same problem after upgrading from Go 1.7 to Go 1.9.

@wildattire have you tried a revel clean and rebuild ?
Worst case you can assign the values into c.ViewArgs like
a,b,c := 1,2,3
c.Render(a,b,c)

is the same as
c.ViewArgs["a"]=1
c.ViewArgs["b"]=2
c.ViewArgs["c"]=3
c.Render()

I will try to test this later today

Thanks. Yes, we've done a clean rebuild of revel and pretty much all dependencies everywhere.
in this line:
if renderArgNames, ok := c.MethodType.RenderArgNames[line]; ok { ... }
The value of line is 478, but c.MethodType.RenderArgNames has a single entry in it, with a key of 479. So perhaps there is an off-by-one error somewhere?
We've kludged up a little patch in the Render() function to reassign line in the event there's only one entry in the map:
	if _, ok := c.MethodType.RenderArgNames[line]; !ok && len(c.MethodType.RenderArgNames) == 1 {
		for k := range c.MethodType.RenderArgNames {
			line = k
		}
	}

Which resolves the error.
I can also confirm that your suggestion of manually setting ViewArgs prior to zero-param Render() also works. Thanks.

@wildattire
Hmm, what type of variables are you passing ? I tried a int, string, time.Time - all worked without errors (go 1.9). I tried with one and two variables

I figured it out ! This fails
	return c.Render(
		a,
		b)

This works
	return c.Render(a,b)

We are passing:

2 large structs with strings, ints, bools, []strings, etc
7 struct slices, all of different types, each with nested structs, strings, etc
5 strings

15 parameters total, most of which are slices of structs. It's a fair amount of data. Sorry, not at liberty to explicate the structure of all of them.

Oops, I only saw your question for some reason, not the fix. I can confirm, when we put all our parameters on a single line, it works fine. Thanks!

I can see why you went multiline ! Lol
On Thu, Oct 5, 2017, 8:27 PM Wild Attire, Inc<EMAIL_ADDRESS>wrote:

Oops, I only saw your question for some reason, not the fix. I can
confirm, when we put all our parameters on a single line, it works fine.
Thanks!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/revel/revel/issues/861#issuecomment-334648869, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABUsBi2yGqE_0Fzu0zZMb7nLUtDqyVekks5spZ4ogaJpZM4DV9uE
.


Roadmap: Target Annotation - Target safety

Summary
On-target adverse effects are a major contributor to drug candidate attrition due to precinical or clinical toxicity (Brennan 2017). Therefore, an early assessment of target safety is an important step in selecting a drug target candidate.
We will investigate how to include information on target safety on the Open Targets platform.
How
Information on target safety will be added in two phases.

Curation of publications that provide information on targets with known safety issues.
A target safety pipeline will be implemented to combine different data sources into a safety score.

Tickets associated with the different phases

Curation of publications that provide information on targets with known safety issues

[x] Initial data research
#396 Compile list of targets with potential safety concerns
[ ]  #412 Prepare data for targets with known safety concerns for Open Targets pipeline
[x] #460 + #461 Specify where and how safety warnings will be shown in OT Platform
[x] Implement data injection
[ ] #460 + #461  Front end changes

Target safety pipeline

[x] Initial data source research
[ ] Develop the target safety pipeline
[ ] Specify where and how safety score will be used in OT Platform
[ ] Implement data injection
[ ] Front end changes

See the notes from related meetings here.

Additional literature for known safety risks provided by Anne Hershey (CHEMBL) (HeCaTos project). See the collected lists of interesting targets here.
This includes tables of targets important for safety, but not necessarily linked to an ADR. Additionally, the mode of action (activation/inhibition) is not specified in all tables. Including this information will require:

[ ] modifying the organisation of the known safety literature tables as well as the corresponding json schema.
[ ] Front end changes to include this additional safety information


Allow storage queries for items that are still pending

I've considered alternative approaches to this, and in the end decided to propose 2 new methods for MapRead:

a required get_batched, which works much like a MapRead::get, but on the pending atomic write batch
a provided get_speculative method which first performs a plain get, and only falls back to get_batched if the former doesn't return a value

One of the existing related tests was extended with the new calls.
As for alternatives, the existing get could be extended with a bool parameter indicating whether the search should include the pending batch, but that would require a lot of changes to the existing calls. Making it the default is also not necessarily desirable, as it is a performance penalty.
Optional tweaks: the new get_speculative method could first check the pending batch and only then fall back to the "finalized" records; it's a performance consideration that depends on the expected use cases. The new method names could be changed too.
Closes https://github.com/AleoHQ/snarkVM/issues/1203.

This is great @ljedrz. I've been thinking about this problem some more.
BlockStorage, ConsensusStorage, TransactionStorage and TransitionStorage do not necessarily need this feature, however ProgramStorage always needs this feature.
Perhaps to minimize performance penalties for the former 4 storage, we could introduce two new traits (i.e. SpeculativeWrite/SpeculativeRead to mirror MapWrite/MapRead), and introduce these new traits only to the later trait (ProgramStorage) without giving it access to the original MapWrite/MapRead.

Optional tweaks: the new get_speculative method could first check the pending batch and only then fall back to the "finalized" records; it's a performance consideration that depends on the expected use cases. The new method names could be changed too.

Would you mind reordering that get_speculative in this order? This is the desired functionality of that endpoint.


Introduce aggressive pruning and the related 'uses' keyword for constants and functions

Related Dafny issue: https://github.com/dafny-lang/dafny/issues/1585
Includes changes from: https://github.com/boogie-org/boogie/pull/449
Introduce the aggressive pruning option /prune:2, which will remove any axioms that aren't reachable as a definition axiom. To prevent removing most axioms, the keyword uses is introduced that can be used to provide, for functions and constants, a definition axiom that only partially defines the definition, and it can be used to define multiple definition axioms. Here's an example:
const unique fourOrThree : int uses {
    axiom four == 4 || four == 3;
}

function returnsThree(x: int): int uses {
    axiom (forall x: int :: x != 0 ==> returnsThree(x) == 3);
    axiom (forall x: int :: x == 0 ==> returnsThree(x) == 3);
}

procedure validates()
  requires fourOrThree != 3
  ensures returnsThree(4) == 3;
  ensures fourOrThree == 4;
{

}

The uses keyword can also be used to handle situation where automatic pruning and exclude_dep would otherwise incorrectly remove an axiom.
An example is the following:
function {:exclude_dep} $Box<T>(T): Box;
function {:identity} {:exclude_dep} Lit<T>(x: T): T { x } uses {
  axiom (forall<T> x: T :: { $Box(Lit(x)) } $Box(Lit(x)) == Lit($Box(x)) );
}

Without the uses keyword, the axiom would be pruned since $Box and Lit are marked as {:exclude_dep}.

function returnsThree(x: int): bool uses {
    axiom (forall x: int :: returnsThree(x) == 3);
}

Did you mean function returnsThree(x: int):int  ?

To prevent removing most axioms, the keyword uses is introduced that can be used to provide multiple definition axioms for functions and constants, like so:...

The sentence above in the PR description seems to suggest that it is possible to provide more than one axiom for each function or constant symbol.  Yet, the code after the sentence does not contain any example of multiple axioms for a single symbol.  Please clarify.

@RustanLeino :  I request your input here.  This PR (and earlier PRs by your intern) are addressing an important problem.  In the course of this work, several attributes and features are being added.  Is it time to take a step back and rethink the approach?

@RustanLeino : I request your input here. This PR (and earlier PRs by your intern) are addressing an important problem. In the course of this work, several attributes and features are being added. Is it time to take a step back and rethink the approach?

Hey, I understand the apprehension towards this and related PRs. I think the problem could also be resolved at the SMT level.
Let me restate the problem: the Z3 solver can strongly change its behavior in terms of solve time and output of check-sat when making changes to the sent commands for which we wouldn't expect a change in behavior.
We're currently working around this problem by making sure that Dafny's verification pipeline, which includes Boogie, sends the exact same SMT commands to the Z3 solver when verifying two proofs that we can easily normalise to the same proof. The advantage of this approach, as opposed to changing the solver, is that it will work for any solver. A disadvantage is, I think, that we're more limited in detecting the equivalence between two proofs. Tackling this problem at the solver level might allow constant solver behavior for much larger classes of equivalent input.

@keyboardDrummer:  You are indeed addressing an important problem.  Thank you for your efforts which will help all Boogie users.
Based on the PR description, I detect three players in this game:  uses keyword, prune option, and exclude_dep attribute.  Am I missing anything?
I would love to see one description of what a Boogie user could expect once this PR lands.  If the description is compact, it should find its way into a comment into the code also.

@keyboardDrummer: You are indeed addressing an important problem. Thank you for your efforts which will help all Boogie users.
Based on the PR description, I detect three players in this game: uses keyword, prune option, and exclude_dep attribute. Am I missing anything?
I would love to see one description of what a Boogie user could expect once this PR lands. If the description is compact, it should find its way into a comment into the code also.

Added a description here: https://github.com/boogie-org/boogie/blob/56b011f654f2dc49a2715e74b04d5908324991c4/Source/Core/CommandLineOptions.cs#L574

Ok, let us merge after renaming UsesClauses to UsesDecls.
On Tue, Nov 23, 2021, 1:56 PM Remy Willems @.***> wrote:

@.**** commented on this pull request.
In Source/Core/CommandLineOptions.cs
https://github.com/boogie-org/boogie/pull/450#discussion_r755532291:

@@ -569,7 +566,77 @@ void ObjectInvariant2()
public bool InstrumentWithAsserts = false;
public string ProverPreamble { get; set; }= null;
public bool WarnNotEliminatedVars = false;

public bool PruneFunctionsAndAxioms = false;

public enum PruneMode {

 None,

@shazqadeer https://github.com/shazqadeer can we merge this? I don't
have a strong opinion on the name of the UsesClauses enum. I think the
difference with Automatic pruning, is that it only automatically detects
outgoing edges in axioms, so something like OnlyUseOutgoingAxiomEdges
could be the name.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/boogie-org/boogie/pull/450#discussion_r755532291, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB2RCFVHF4RTAD3FDE7TMQDUNQEZNANCNFSM5HVSEH7Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@keyboardDrummer :  Do you have a timeline on the dropping of :exclude_dep and Automatic?

@keyboardDrummer : Do you have a timeline on the dropping of :exclude_dep and Automatic?

I think a month is a pretty safe upper bound.


fix: rerun tests affected by file changed by build script

This PR addresses point 3 in #2532.
For some reason, when rebuilding a dependency with vite, the vitest watcher emitted an unlink event, but no add or change event. This change allows vitest's behavior to be consistent with vite's HMR and build watching. Additionally, strictly speaking, it seems sensible to rerun tests that include a removed file somewhere in its dependency chain.
If a test is needed/desired, I'd need some guidance on how to test watch mode behavior.

strictly speaking, it seems sensible to rerun tests that include a removed file somewhere in its dependency chain

If the file was removed in the change, then it will probably break on rerun, so I don't see a lot of reason to rerun it - better to wait for the change even in that case


Windows build failure on CUDA 11.2

This fails with CuPy v8.6.0 and likely v9.0.0rc1 as well: https://github.com/conda-forge/cupy-feedstock/pull/113#issuecomment-807202827
    nvcc warning : The 'compute_35', 'compute_37', 'compute_50', 'sm_35', 'sm_37' and 'sm_50' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning).
    cupy_thrust.cu
    cupy/cuda/cupy_thrust.cu(145): error C3615: constexpr function 'thrust::less<thrust::complex<float>>::operator ()' cannot result in a constant expression
    cupy/cuda/cupy_thrust.cu(148): note: failure was caused by call of undefined function or one not declared 'constexpr'
    cupy/cuda/cupy_thrust.cu(148): note: see usage of '_cmp_less'
    cupy/cuda/cupy_thrust.cu(157): error C3615: constexpr function 'thrust::less<thrust::complex<double>>::operator ()' cannot result in a constant expression
    cupy/cuda/cupy_thrust.cu(160): note: failure was caused by call of undefined function or one not declared 'constexpr'
    cupy/cuda/cupy_thrust.cu(160): note: see usage of '_cmp_less'
    cupy/cuda/cupy_thrust.cu(169): error C3615: constexpr function 'thrust::less<thrust::tuple<unsigned __int64,thrust::complex<float>,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type>>::operator ()' cannot result in a constant expression
    cupy/cuda/cupy_thrust.cu(172): note: failure was caused by call of undefined function or one not declared 'constexpr'
    cupy/cuda/cupy_thrust.cu(172): note: see usage of '_tuple_less'
    cupy/cuda/cupy_thrust.cu(181): error C3615: constexpr function 'thrust::less<thrust::tuple<unsigned __int64,thrust::complex<double>,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type>>::operator ()' cannot result in a constant expression
    cupy/cuda/cupy_thrust.cu(184): note: failure was caused by call of undefined function or one not declared 'constexpr'
    cupy/cuda/cupy_thrust.cu(184): note: see usage of '_tuple_less'
    cupy/cuda/cupy_thrust.cu(223): error C3615: constexpr function 'thrust::less<float>::operator ()' cannot result in a constant expression
    cupy/cuda/cupy_thrust.cu(226): note: failure was caused by call of undefined function or one not declared 'constexpr'
    cupy/cuda/cupy_thrust.cu(226): note: see usage of '_real_less'
    cupy/cuda/cupy_thrust.cu(235): error C3615: constexpr function 'thrust::less<double>::operator ()' cannot result in a constant expression
    cupy/cuda/cupy_thrust.cu(238): note: failure was caused by call of undefined function or one not declared 'constexpr'
    cupy/cuda/cupy_thrust.cu(238): note: see usage of '_real_less'
    cupy/cuda/cupy_thrust.cu(247): error C3615: constexpr function 'thrust::less<thrust::tuple<unsigned __int64,float,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type>>::operator ()' cannot result in a constant expression
    cupy/cuda/cupy_thrust.cu(250): note: failure was caused by call of undefined function or one not declared 'constexpr'
    cupy/cuda/cupy_thrust.cu(250): note: see usage of '_tuple_less'
    cupy/cuda/cupy_thrust.cu(259): error C3615: constexpr function 'thrust::less<thrust::tuple<unsigned __int64,double,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type>>::operator ()' cannot result in a constant expression
    cupy/cuda/cupy_thrust.cu(262): note: failure was caused by call of undefined function or one not declared 'constexpr'
    cupy/cuda/cupy_thrust.cu(262): note: see usage of '_tuple_less'
    cupy/cuda/cupy_thrust.cu(287): error C3615: constexpr function 'thrust::less<__half>::operator ()' cannot result in a constant expression
    cupy/cuda/cupy_thrust.cu(288): note: failure was caused by call of undefined function or one not declared 'constexpr'
    cupy/cuda/cupy_thrust.cu(288): note: see usage of '_real_less'
    cupy/cuda/cupy_thrust.cu(297): error C3615: constexpr function 'thrust::less<thrust::tuple<unsigned __int64,__half,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type,thrust::null_type>>::operator ()' cannot result in a constant expression
    cupy/cuda/cupy_thrust.cu(300): note: failure was caused by call of undefined function or one not declared 'constexpr'
    cupy/cuda/cupy_thrust.cu(300): note: see usage of '_tuple_less'
    error: command 'D:\\bld\\cupy_1616682886118\\_build_env\\Library\\bin\\nvcc.bat' failed with exit status 2

My theory is that on our Windows CI we use VS2015, but on Conda-Forge we use VS2017. According to the VS docs the C3615 is only raised with VS2017, so we didn't catch it.

What I don't understand is why it only failed with CUDA 11.2.

Maybe related: https://github.com/cupy/cupy/pull/4698 https://github.com/cupy/cupy/pull/4730

I thought #4735 fixed it...?

I guess we should have used the value of _MSVC_LANG  to determine use of constrexpr, instead of just _WIN32 flag...?
https://github.com/NVIDIA/thrust/blob/96a7e7b6bd99027c8450b11d02195a0209df6fa7/thrust/detail/config/cpp_dialect.h#L61-L69

Yeah... see my earlier comment: https://github.com/cupy/cupy/pull/4713#issuecomment-784366574


TypeError: r is not a function

Thanks for reporting an issue to us! We're glad you are using and invested in Enzyme.
Before submitting, please read over our commonly reported issues to prevent duplicates!
All common issues

common issues

Notoriously common issues

Webpack build issues
Cannot find module 'react-dom/lib/ReactTestUtils'
Query Selector fails
Testing third party libraries

If you haven't found any duplicated issues, please report it with your environment!
Current behavior
    TypeError: r is not a function

      13 |     }
      14 |   ]
    > 15 |   const el = mount(
         |              ^
      16 |     <ManageScormPage
      17 |       topic={{
      18 |         workspace_id: 1,

      at t.children (node_modules/react-dropzone/src/index.js:391:12)
      at finishClassComponent (node_modules/react-dom/cjs/react-dom.development.js:14391:31)
      at updateClassComponent (node_modules/react-dom/cjs/react-dom.development.js:14346:24)
      at beginWork (node_modules/react-dom/cjs/react-dom.development.js:15213:16)
      at performUnitOfWork (node_modules/react-dom/cjs/react-dom.development.js:18780:12)
      at workLoop (node_modules/react-dom/cjs/react-dom.development.js:18820:24)
      at renderRoot (node_modules/react-dom/cjs/react-dom.development.js:18903:7)
      at performWorkOnRoot (node_modules/react-dom/cjs/react-dom.development.js:19800:7)
      at performWork (node_modules/react-dom/cjs/react-dom.development.js:19712:7)
      at performSyncWork (node_modules/react-dom/cjs/react-dom.development.js:19686:3)
      at requestWork (node_modules/react-dom/cjs/react-dom.development.js:19555:5)
      at scheduleWork (node_modules/react-dom/cjs/react-dom.development.js:19364:5)
      at scheduleRootUpdate (node_modules/react-dom/cjs/react-dom.development.js:20032:3)
      at updateContainerAtExpirationTime (node_modules/react-dom/cjs/react-dom.development.js:20060:10)
      at updateContainer (node_modules/react-dom/cjs/react-dom.development.js:20117:10)
      at ReactRoot.Object.<anonymous>.ReactRoot.render (node_modules/react-dom/cjs/react-dom.development.js:20413:3)
      at node_modules/react-dom/cjs/react-dom.development.js:20550:14
      at unbatchedUpdates (node_modules/react-dom/cjs/react-dom.development.js:19915:10)
      at legacyRenderSubtreeIntoContainer (node_modules/react-dom/cjs/react-dom.development.js:20546:5)
      at Object.render (node_modules/react-dom/cjs/react-dom.development.js:20615:12)
      at Object.render (node_modules/enzyme-adapter-react-16/build/ReactSixteenAdapter.js:367:114)
      at new ReactWrapper (node_modules/enzyme/build/ReactWrapper.js:134:16)
      at mount (node_modules/enzyme/build/mount.js:21:10)
      at Suite.<anonymous> (front-end/src/pages/manage-scorm-page/ManageScormPage.spec.js:15:14)
      at Object.describe (front-end/src/pages/manage-scorm-page/ManageScormPage.spec.js:8:1)

Expected behavior
no type error
Your environment
API

[ ] shallow
[X] mount
[ ] render

Version

library
version

enzyme
3.8.0

react
16.8.0

react-dom
16.8.0

react-test-renderer
16.8.0

adapter (below)
1.9.1

Adapter

[X] enzyme-adapter-react-16
[ ] enzyme-adapter-react-16.3
[ ] enzyme-adapter-react-16.2
[ ] enzyme-adapter-react-16.1
[ ] enzyme-adapter-react-15
[ ] enzyme-adapter-react-15.4
[ ] enzyme-adapter-react-14
[ ] enzyme-adapter-react-13
[ ] enzyme-adapter-react-helper
[ ] others ( )

oh this is in react-dropzone, sorry


Spelling mistake in Text.txt

Please fix spelling mistakes in Text.txt

Fixed with Dan's pull request


Phonetic translation

I use Android SDK for voice recognition, and when I translate voice, I return multiple bytes []. How can I synthesize multiple bytes [] into a single audio seamlessly?
Now in recognizer. synthesizing. addEventListener this callback will return multiple byte [], if I add all byte [] to an array and convert it into audio playback, it will only play the first returned byte [] audio, not all playback.

When receiving a synthesizing event, please check the Reason member. If it is SynthesizingAudio, the byte array in the event contains synthesized audio which contains a WAV header and data. If it is SynthesiszingAudioCompleted, it indicates the audio for the current translated text is complete. The audio size must be zero in this case.
In your case, each non-zero byte array contains its own wav header. If you want to concatenate them into a single one for playback, you need to remove wav header in the byte array. Alternatively, you can play each byte array as an independent wav file.


Feature/cdr 561

Changes

First change

Related issue

Additional information and checks

[ ] Pull request linked in changelog

The build fails. I think this is because our builder image uses java 11, so we should adjust this.

@micha1970 a new entry should be added to CHANGELOG.md which mentions the update of baseline java to 17 and granular scopes for REST endpoints

I updated the CHANGELOG.md and moved points from 0.23 to unreleased until a new release is done.
Other than that LGTM


Remove Message Chunking

This functionality can be replicated by exposing mbit as a reply flag
The classic example is
My name is Bill. What is your name? or My name is Bill, what is your name?
This should match:
+ my name is * AND + * what is your name in the same flow.
This can be done by having a force continue tag.

I think we've done all this now @silentrob?

Yep, I took this out a little while back.


[SPARK-36625][SPARK-36661][PYTHON] Support TimestampNTZ in pandas API on Spark

What changes were proposed in this pull request?
This PR adds:

the support of TimestampNTZType in pandas API on Spark.
the support of Py4J handling of spark.sql.timestampType configuration

Why are the changes needed?
To complete TimestampNTZ support.
In more details:

(#33876) For TimestampNTZType in Spark SQL at PySpark, we can successfully ser/de TimestampNTZType instances to naive datetime (see also https://docs.python.org/3/library/datetime.html#aware-and-naive-objects). This naive datetime interpretation is up to the program to decide how to interpret, e.g.) whether a local time vs UTC time as an example. Although some Python built-in APIs assume they are local time in general (see also https://docs.python.org/3/library/datetime.html#datetime.datetime.utcfromtimestamp):

Because naive datetime objects are treated by many datetime methods as local times ...

semantically it is legitimate to assume:

that naive datetime is mapped to TimestampNTZType (unknown timezone).
if you want to handle them as if a local timezone, this interpretation is matched to TimestamType (local time)

(#33875) For TimestampNTZType in Arrow, they provide the same semantic (see also https://github.com/apache/arrow/blob/master/format/Schema.fbs#L240-L278):

Timestamp(..., timezone=sparkLocalTimezone) ->  TimestamType
Timestamp(..., timezone=null) ->  TimestampNTZType

(this PR) For TimestampNTZType in pandas API on Spark, it follows Python side in general - pandas implements APIs based on the assumption of time (e.g., naive datetime is a local time or a UTC time).
One example is that pandas allows to convert these naive datetime as if they are in UTC by default:
>>> pd.Series(datetime.datetime(1970, 1, 1)).astype("int")
0    0

whereas in Spark:
>>> spark.createDataFrame([[datetime.datetime(1970, 1, 1, 0, 0, 0)]]).selectExpr("CAST(_1 as BIGINT)").show()
+------+
|    _1|
+------+
|-32400|
+------+

>>> spark.createDataFrame([[datetime.datetime(1970, 1, 1, 0, 0, 0, tzinfo=datetime.timezone.utc)]]).selectExpr("CAST(_1 as BIGINT)").show()
+---+
| _1|
+---+
|  0|
+---+

In contrast, some APIs like pandas.fromtimestamp assume they are local times:
>>> pd.Timestamp.fromtimestamp(pd.Series(datetime(1970, 1, 1, 0, 0, 0)).astype("int").iloc[0])
Timestamp('1970-01-01 09:00:00')

For native Python, users can decide how to interpret native datetime so it's fine. The problem is that pandas API on Spark case would require to have two implementations of the same pandas behavior for TimestampType and TimestampNTZType respectively, which might be non-trivial overhead and work.
As far as I know, pandas API on Spark has not yet implemented such ambiguous APIs so they are left as future work.

Does this PR introduce any user-facing change?
Yes, now pandas API on Spark can handle TimestampNTZType.
import datetime
spark.createDataFrame([(datetime.datetime.now(),)], schema="dt timestamp_ntz").to_pandas_on_spark()

                          dt
0 2021-08-31 19:58:55.024410

This PR also adds the support of Py4J handling with spark.sql.timestampType configuration:
>>> lit(datetime.datetime.now())
Column<'TIMESTAMP '2021-09-03 19:34:03.949998''>

>>> spark.conf.set("spark.sql.timestampType", "TIMESTAMP_NTZ")
>>> lit(datetime.datetime.now())
Column<'TIMESTAMP_NTZ '2021-09-03 19:34:24.864632''>

How was this patch tested?
Unittests were added.

cc @ueshin FYI

Test build #142883 has started for PR 33877 at commit 2354abf.

Test build #142883 has finished for PR 33877 at commit 2354abf.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47386/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/142883/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47386/

Test build #142957 has started for PR 33877 at commit abce481.

Test build #142957 has finished for PR 33877 at commit abce481.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/142957/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47457/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47457/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47457/

Test build #142982 has started for PR 33877 at commit 6bdfad2.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47483/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47483/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47483/

Test build #142983 has started for PR 33877 at commit b4fc1fa.

cc @MaxGekk @gengliangwang @cloud-fan too FYI

Test build #142984 has started for PR 33877 at commit 785d89f.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47484/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47485/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47486/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47485/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47485/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47486/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47486/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47484/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47484/

Test build #142985 has started for PR 33877 at commit 83afb0b.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47487/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47487/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47487/

Test build #142983 has finished for PR 33877 at commit b4fc1fa.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class DatetimeNTZConverter(object):
case class UnixSecondsUTC(child: Expression) extends TimestampToLongBase

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/142983/

Test build #142984 has finished for PR 33877 at commit 785d89f.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class DatetimeNTZConverter(object):
case class UnixSecondsUTC(child: Expression) extends TimestampToLongBase

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/142984/

Test build #142982 has finished for PR 33877 at commit 6bdfad2.

This patch fails from timeout after a configured wait of 500m.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class DatetimeNTZConverter(object):
case class UnixSecondsUTC(child: Expression) extends TimestampToLongBase

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/142982/

Test build #142985 has finished for PR 33877 at commit 83afb0b.

This patch fails from timeout after a configured wait of 500m.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/142985/

Test build #143008 has started for PR 33877 at commit 3f30ab9.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47510/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47510/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47510/

Test build #143011 has started for PR 33877 at commit 178c70b.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47513/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47513/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47513/

This PR is ready for a review.

Test build #143013 has started for PR 33877 at commit 7a920ad.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47515/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47515/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47515/

Test build #143016 has started for PR 33877 at commit 128f796.

Test build #143008 has finished for PR 33877 at commit 3f30ab9.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class DatetimeNTZOps(DatetimeOps):
case class CastTimestampNTZToLong(child: Expression) extends TimestampToLongBase

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143008/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47518/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47518/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47518/

Test build #143011 has finished for PR 33877 at commit 178c70b.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143011/

Test build #143021 has started for PR 33877 at commit 7485ced.

Test build #143016 has finished for PR 33877 at commit 128f796.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class DatetimeNTZOps(DatetimeOps):
class DatetimeNTZConverter(object):
case class CastTimestampNTZToLong(child: Expression) extends TimestampToLongBase

This PR is ready for a review.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143016/

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47523/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47523/

Test build #143022 has started for PR 33877 at commit 488f1e6.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47524/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47524/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47524/

Test build #143013 has finished for PR 33877 at commit 7a920ad.

This patch fails from timeout after a configured wait of 500m.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class DatetimeNTZOps(DatetimeOps):
class DatetimeNTZConverter(object):
case class CastTimestampNTZToLong(child: Expression) extends TimestampToLongBase

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143013/

Test build #143021 has finished for PR 33877 at commit 7485ced.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class DatetimeNTZOps(DatetimeOps):
class DatetimeNTZConverter(object):
case class CastTimestampNTZToLong(child: Expression) extends TimestampToLongBase

Test build #143022 has finished for PR 33877 at commit 488f1e6.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class DatetimeNTZOps(DatetimeOps):
class DatetimeNTZConverter(object):
case class CastTimestampNTZToLong(child: Expression) extends TimestampToLongBase

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143022/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143021/

Test build #143037 has started for PR 33877 at commit 6620ade.

I cleaned up a bit more.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47540/

Test build #143038 has started for PR 33877 at commit f83511b.

I cleaned up a bit more.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47540/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47541/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47540/

Overall LGTM. Thanks for the work!

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47541/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47541/

Test build #143037 has finished for PR 33877 at commit 6620ade.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class DatetimeNTZOps(DatetimeOps):
class DatetimeNTZConverter(object):
case class CastTimestampNTZToLong(child: Expression) extends TimestampToLongBase

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143037/

Test build #143038 has finished for PR 33877 at commit f83511b.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class DatetimeNTZOps(DatetimeOps):
class DatetimeNTZConverter(object):
case class CastTimestampNTZToLong(child: Expression) extends TimestampToLongBase

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143038/

Merged to master.

fyi, im gonna revisit all the dt operations in pandas api on Spark in q4.


Added Anthill Inside and Rootconf Hyderabad

Details of the conference:

Website: https://hasgeek.com/anthillinside/2019/

Date: 23 Nov

Venue: Taj M G Road, Bangalore

Description: On infrastructure for AI and ML: from managing training data to data storage, cloud strategy and costs of developing ML models

Website: https://hasgeek.com/rootconf/2019-hyderabad/

Date: 16 Nov

Venue: T-Hub, IIIT-H Campus, Hyderabad

Description: India's largest community and conference on infrastructure security, DevOps and distributed systems

@nikhita Don't be :)


CI Elasticsearch Label

We're now introducing an agent which does not offer elasticsearch. The implications to this are that jobs will have to explicitly define a label if it requires elasticsearch.  Otherwise, the job may be executed on an agent without it's requirements.

Should we put a version number on the label liek we do with mongo for when we start testing ES5?