primordic/IssueDupesLite huggingface dataset:
Repository: opentx/opentx

Issue #8288: Telemetry 4+2 without sliders causes radio to go into Emergency Mode
Created: 2021-02-14T03:01:57Z
Describe the bug
Get "Emergency Mode" screen when trying to setup widgets in 4+2 with sliders disabled.
To Reproduce
Steps to reproduce the behavior:

Go into Telemetry on Radiomaster TX16S
Select 4+2 widgets
Disable Sliders
Setup Widgets
"Emergency Mode"

Expected behavior
Able to setup the various widgets
Video
https://photos.app.goo.gl/ELboEAUj9pvbUABG9
General information

OpenTX version 2.3.11
Hardware: Radiomaster TX16S Color

Duplicate issue #8642: Emergency mode triggered while modifying telemetry screens
Created: 2021-07-29T20:22:34Z
On Radiomaster TX16S, 2.3.14:
In the attached model backup file, on model "Q12-X GRX", when working on the telemetry screens:
On the telemetry setup screen, after choosing "4+2 layout" and deselecting the sliders, the transmitter reverts to emergency mode when clicking on "setup widgets".
It happens every time, and it also crashes the simulator in exactly the same way.
document1.zip

Closing comment (2021-08-21T18:02:32Z): This looks like a duplicate of #8288 that I opened a while ago.  Nice to see someone else has reproduced this issue.
Repository: opentx/opentx

Issue #4848: Companion & Horus - model files are getting corrupt by SD sync
Created: 2017-04-24T04:54:03Z
Companion - any version (current 2.2.0N369)
TX - FrSky Horus
Issue
model files on TX are getting corrupt in case of SD card sync initiated before "Read models and Settings from Radio" is executed. Only the current selected model is ok still.
This happens especially when upgrading Companion to a newer version and doing the SD card sync before upgrading the TX for backup reasons.
The issue occured several times in the past with different versions of Companion & OpenTX.
Proposal
Sync *.bin files only in one direction from TX to PC or exclude them from SD card sync at all.
And do update of *.bin files on TX via "Write Models and Settings to Radio" (and "Read Models and Settings from Radio") only.

Duplicate issue #4885: N371 - X9D+ - Hello.wav does not play on start-up
Created: 2017-05-01T03:24:47Z
Just upgraded from N362.
Downloaded X9 zip
Synced SD using N371 version of companion.
hello.wav does exist on card but does not play.
This seems related to having existing files on the SD card or some other problem related to SD card.
Clearing the SYSTEM directory on the SD, then resyncing fixed the issue.
Needs more testing.
This occurred on Ubuntu Linux 16.04.02

Closing comment (2017-05-01T06:31:07Z): Most likely duplicate of #4848, SD sync has issues. Just fix things straight on the card for now.
Repository: oracle/node-oracledb

Issue #1261: Solution: Using node-oracledb with Cypress Project (Avoiding NJS-045)
Created: 2020-06-10T23:12:01Z
Running into issues with setting up node-oracledb in a cypress project. I'm unable to import the library. I'm getting the following error when running the project,
Error: NJS-045: cannot load a node-oracledb binary for Node.js 12.13.0 (darwin x64) 
  Node.js require('oracledb') error was:...

I have attempted the following,

Downgrade node to v10.16
Manually compiled node-oracledb by following the steps mentioned here

Cypress v4.8.0
node output
darwin
'v10.16.3'
'x64'
'4.2.0'
'19.3.0.0.0'

Oracle Database version?
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
PL/SQL Release 12.2.0.1.0 - Production
"CORE	12.2.0.1.0	Production"
TNS for Linux: Version 12.2.0.1.0 - Production
NLSRTL Version 12.2.0.1.0 - Production

Duplicate issue #1596: Cypress: NJS-069: node-oracledb 6.0.3 requires Node.js 14.6 or later. 
Created: 2023-08-23T09:47:48Z
Hi!
I have problem with  node-oracledb.
When I launch my test-case in Cypress - I get error: NJS-069: node-oracledb 6.0.3 requires Node.js 14.6 or later.
But my current version:
oracledb@6.0.3
Node JS version v18.16.0
Cypress package version: 12.17.4
Cypress binary version: 12.17.4
Electron version: 21.0.0
Bundled Node version:
16.16.0
Could you help me solve the problem?


What versions are you using?




Is it an error or a hang or a crash?


What error(s) or behavior you are seeing?




Include a runnable Node.js script that shows the problem.

Closing comment (2023-08-25T11:24:25Z): This is a duplicate of #1261. Hence closing this issue.
Request the user to refer to issue #1261
Repository: oracle/node-oracledb

Issue #559: Support DCN ( Database Change Notification ) ?
Created: 2016-11-29T02:04:49Z
Is it support DCN ?
I looked for the some examples ( python, java ... )on oracle websites.
but I didn't see anything node.js DCN examples .

Duplicate issue #659: query change notification (or sub/pub)
Created: 2017-03-27T17:35:31Z
There is a cool feature in "python-cx_Oracle" for query change notification (or sub/pub).
https://github.com/oracle/python-cx_Oracle/blob/master/samples/QueryChangeNotification.py
I'm currently making a node.js application that will connect to an Oracle db
And there is another application (which I have zero control over) connected to the same db.
So, I would like to listen for changes made by that application using a way similar to th python way mentioned above.
Is that possible with the current node-oracledb
Some Information:

Node.js v7.7.4.
node-oracledb v1.13.
Oracle client 12.1.
Oracle Database 11g.

Closing comment (2017-03-28T01:07:06Z): This is being tracked in #559
Repository: oracle/node-oracledb

Issue #147: Support PL/SQL and SQL types like Oracle Spatial SDO
Created: 2015-07-22T20:38:20Z
I keep getting NJS-010: unsupported data type in select list, when I try to retrieve sdo geometries from a database.
I then tried running a stored function(SDO2GEOJSON) but received the same NJS-010 error but didn't know if that was do to functions not being supported or geometries.
Or this could all be user error on my part.

Duplicate issue #777: Support of binding IN parameters for SQL queries
Created: 2017-11-01T08:31:51Z
Would like to ask if support for binding IN parameters for SQL queries be added to upcoming release for node-oracledb or not?
It's seem that support for binding array parameter in PL/SQL is added already, not sure if there's any particular reason (i.e. security reason) for not extending support on normal queries as well?
In my opinion constructing SQL statement in runtime is not a very good approach, it reduces the expressiveness of the application codes.
Thank you very much :)
Cheers!

Closing comment (2017-11-01T10:56:05Z): Dup of #147.  It's definitely on the wish list.  Node-oracledb v2  is a step in the right direction since its new, underlying ODPI-C layer will help.
Repository: oracle/node-oracledb

Issue #565: Support for cursor column in select
Created: 2016-12-08T12:08:27Z
There are a plan to support cursor column in a select ?
Example:
var sql = "" + 
"select d.department_id,\n" +
"       d.department_name,\n" +
"       cursor (select employee_id,\n" +
"                      first_name,\n" +
"                      last_name,\n" +
"                      phone_number\n" +
"                from employees e\n" +
"               where e.department_id = d.department_id) emps\n" +
"  from departments d\n" +
" where department_id = :department_id";

connection.execute(sqlPo, { department_id: 80 }, function(err, result) {  
	if (err) {  
		console.error(err.message);  
		doRelease(connection);  
		return;
	}  
	
	callback(result);
}); 

Result:
NJS-010: unsupported data type in select list

Duplicate issue #646: NJS-010 for nested cursors
Created: 2017-03-09T08:26:40Z
I get this error when I try to call database function which returns nested cursors
NJS-010: unsupported data type in select list

var bindVars = {
    ret: {type: oracledb.CURSOR, dir: oracledb.BIND_OUT},
    first_name: 'first',
    last_name: 'last',
    id_number: '00000000000'
};

connection.execute(
    "BEGIN :ret := super_searcher" +
    "(:full_name, :first_name, :last_name, :id_number, :middle_name); END;",
    bindVars,
...
My "obfuscated" database function is
open v_result for
  select ap.app_id,
         cursor (select n.user_name from table1 n where n.id=ap.id) as master,
         cursor (select no.name from table2 no where no.id=ap.id) as no_name,
         cursor (select p.id from table4 p where p.id = ap.id) as p_info
    from apps ap where ap.id = x;
return v_result;

In java this snippet works correctly
stmt.registerOutParameter(1, OracleTypes.CURSOR);
ResultSet rSet = stmt.getCursor(1);
while (rSet.next()) {
    int id = rSet.getInt("app_id");
    try(ResultSet attrRslt = (ResultSet) rSet.getObject("master")) {
        while (attrRslt.next()) {
            String userRealName = attrRslt.getString("user_name");
        }
    }
Does node-oracledb package support nested cursors? If yes, how can I read results with nested cursors?
node-oracledb: 1.12.2
nodejs: 7.6.0
OS: Ubuntu 16.04

Closing comment (2017-03-12T10:37:57Z): Dup of #565
Repository: oracle/node-oracledb

Issue #128: SIGINT not terminating process
Created: 2015-06-26T18:02:18Z
when I setup an express app including oracledb and use cntrl + C ( SIGINT ) to terminate the process, the process hangs.
It works fine when I use oracledb with node version v0.10.32 , but I am facing this issue with node versions 0.12.x

Duplicate issue #271: Express + OracleDB does leaves a hanging process when terminated
Created: 2015-11-06T15:43:50Z
I created a repo for the bug with express + OracleDB, in the most minimal code that reproduces the bug.
https://github.com/mrchess/oracledb-express
When I start this express server, and terminate it with CTRL+C the node process does not terminate and lingers in the background.
Any thoughts of this?

Closing comment (2015-11-06T15:54:21Z): Dup of #128
Repository: orchest/orchest

Issue #646: Make environments gate more granular: only consider environments used by pipelines
Created: 2022-01-14T14:01:55Z
Describe the problem this improvement solves
The improvement I am proposing is making the environments gate stricter, such that the gate only considers environments that are used by pipelines. Required changes:

Changing the environments gate
In the step properties we need to prevent new environments to be selected if they are not yet built. Or, when the user does select them the pipeline needs to be put in read-only mode.

Problems this improvement solves and other benefits:

Faster project startup on project import/creation. When opening a pipeline of a project, it will first check whether all environments have been build. This means that if an environment takes a very long time to build it will prevent the entire pipeline from being opened in edit mode.
No read-only mode on environment creation. Currently, whenever you create a new environment, all pipelines of the resp. project are put in read-only mode. This is very intrusive given that the environment isn't even used yet. JupyterLab that is open in another tab will actually still work (even though the kernel of the new environment will not start), which is somewhat similar to #502.
Creation of new jobs. Why prevent a job from being created if the pipeline doesn't even use a "not-yet built" environment?

Describe the solution you'd like
Instead of checking whether all environment have been build, we should check whether all environments that the pipeline uses have been build. In a project it can very well be that a pipeline doesn't use all environments.
Cons:

The kernels that are shown in jupyterlab will now also show kernels that won't actually start. But that shouldn't be too hard to fix as we can just create the kernel after a successful build of the environment.

The "annoying" environments are building dialog

Duplicate issue #502: Avoid unloading JupyterLab on environment build
Created: 2021-09-28T15:20:31Z
Describe the solution you'd like
Avoid unloading JupyterLab <iframe> on environment build
What does your solution aim to solve?
Annoying behavior that isn't strictly necessary
TODO: check if indeed no assumptions are violated if we stop doing this. @fruttasecca ?

Closing comment (2022-06-03T17:32:32Z): Similar to #646, especially #646 (comment). Quite annoying indeed!
Repository: orchest/orchest

Issue #485: Add "dashboard" view to see jobs and running sessions cross-projects
Created: 2021-09-21T13:18:53Z
Describe the solution you'd like
Add "dashboard" view to see running jobs/sessions.
What does your solution aim to solve?
Make it easier to see at a glance what is running (and has failed to run) in Orchest.

Duplicate issue #738: Cross projects jobs view
Created: 2022-02-23T08:38:39Z
Describe the feature you'd love to have in Orchest
Having a general understanding of what jobs are running or are going to run (and when) becomes difficult as the number of projects and jobs increases. A way to having a cross projects view of that would help. Things that should be easier to know with the blink of an eye:

how many active cronjobs are there?
what's the timeline for the next cronjobs that are going to be triggered? (i.e. the N closest cronjobs that are going to run)
how many jobs have some runs that are running right now?
...

Closing comment (2022-02-23T17:31:02Z): Duplicate of #485.
I do like extending the scope of the dashboard though and showing additional information, e.g. not only running jobs but also a timeline for next running jobs.
Repository: orchest/orchest

Issue #1055: Can we remove `node-agent` in favor of utilizing kubelet's garbage collection?
Created: 2022-06-22T15:43:12Z
Describe the problem this improvement solves
We currently use the node-agent to pre-pull images to the nodes in the cluster and delete unused images (primarily used for environments). This behavior might not be needed due to the garbage collection that kubelet is running by default.
Would need some more digging around given that the node-agent is used to reduce disk pressure by removing images that are no longer need by Orchest, e.g. managing environment images lifecycles.
A more thorough discussion can be found in:

#1048 (comment)
#1048 (comment)
#1048 (comment)
#1048 (comment)
#1048 (comment)
...

Duplicate issue #854: Change node-agent to not depend on the Docker sock
Created: 2022-04-01T10:11:21Z
Describe the problem this improvement solves
The main downside now is that we're tying the service to the Docker container runtime which not every k8s cluster uses.
Describe the solution you'd like
Potentially we can use the CRI spec to generalize how we pull (against various container runtimes).
YAML pointing to sock: https://github.com/orchest/orchest/blob/master/deploy/helm/charts/node-agent/templates/daemonset.yaml
node-agent behavior: https://github.com/orchest/orchest/blob/master/services/node-agent/app/main.py

Closing comment (2022-07-19T07:47:22Z): Related to #1055.
Repository: orchest/orchest

Issue #550: Clean up old pipeline runs in jobs
Created: 2021-11-16T11:43:54Z
Is your feature request related to a problem? Please describe.
When running a pipeline as part of a job, the job can create many pipeline runs when e.g. on a short cron schedule (run every 5 minutes). Each run has its own "checkout" of the project files. This can fill the disk pretty rapidly in some cases (large project files, e.g. node_modules/ in some cases).
Describe the solution you'd like
Introduce an option to retain only the last X number of pipeline runs. This automatically frees up space and allows cron jobs to run for longer durations more reliably.
Credits to Serhii Ostapchuk for bringing up the problem & idea.

Duplicate issue #601: Ability to delete pipeline runs as part of jobs
Created: 2021-12-16T14:49:07Z
Is your feature request related to a problem? Please describe.
You might want to delete pipeline runs of jobs for numerous reasons:

You want to keep a clean slate (maybe you only want to keep 20 at maximum - that could be another feature though)
Delete the data of jobs (without deleting its logs)

Deleting jobs through the filesystem is pretty much impossible as you need to know the structure and a way to link the uuids with the correct run you want to delete.
Describe the solution you'd like
Ability in the table to delete pipeline runs as part of the job.
In #398 we will introduce a way to abort an individual pipeline run. Would be great if it can also be deleted.

Closing comment (2021-12-17T16:11:33Z): Related to #550
Repository: orchest/orchest

Issue #496: Error attempting to connect to Gateway server url 'http://jupyter-EG-93c7d122-a3b1-435f-d8f6a2d0-6584-4c1c:8888'.  Ensure gateway url is valid and the Gateway instance is running.
Created: 2021-09-27T11:05:09Z
Describe the bug
When we open pipeline in jupyterlab and run cell it fail to execute cell and throws following error.
Error attempting to connect to Gateway server url 'http://jupyter-EG-93c7d122-a3b1-435f-d8f6a2d0-6584-4c1c:8888'.  Ensure gateway url is valid and the Gateway instance is running. 
To Reproduce
Create new project -> new pipeline -> open in jupyter notebook  
Screenshots

Environment

elementary os (linux)

Duplicate issue #757: Error Starting Kernel when edit in jupyter lab
Created: 2022-03-04T03:58:40Z
Describe the bug
./orchest start
import quickstart project
open pipeline , open step and edit in jupyterlab
in jupyterlab show error:
Error Starting Kernel
HTTP 500: Internal Server Error (Error attempting to connect to Gateway server url 'http://jupyter-EG-f6249899-51e3-474b-0915b350-b929-4cbd:8888'.  Ensure gateway url is valid and the Gateway instance is running.)
Expected behavior
should start a kernel
Screenshots
If applicable, add screenshots to help explain your problem.

Environment

OS (e.g. macOS): win10 21h1 with wsl2 (ubuntu 20.04.2)
Docker 20.10.12
Browser (e.g. Chrome): edge
Orchest's version (in the settings page): v2022.02.9

Closing comment (2022-03-04T08:06:46Z): Hi @huangkai31 thanks for raising this issue!
Your issue is related to #496. It would be great if we can continue the conversation there.

Detailed version of all the images

Based on your output it seems like not all images are running on the same version (which is required for Orchest to run correctly). The remedy should be to run ./orchest update to get all images on the same version again.
Please reply in the other issue if that doesn't fix it for you.
Repository: orchest/orchest

Issue #466: Updated job name is not used after duplicating a job
Created: 2021-09-08T13:51:39Z
Describe the bug
Updated job name is not used after duplicating
To Reproduce
Steps to reproduce the behavior:

Create a job
Duplicate that job
Change the name of the job
Submit the job
See the name change has not been saved when submitting the job

Expected behavior
The name of the job in the input field should be used.

Duplicate issue #558: When changing a job from cron to one-off after duplication it still runs as a cron job
Created: 2021-11-24T14:50:58Z
Describe the bug
When changing a job from cron to one-off after duplication it still runs as a cron job
Environment

OS: Linux
Browser: Brave
Version: v2021.11.11
Environment: prod, cloud

Closing comment (2021-11-24T15:22:15Z): Might be related to #466.
Repository: orchest/orchest

Issue #138: Unified approach for alternative Jupyter kernels like jupyter-xeus
Created: 2021-02-03T12:44:51Z
Currently the Jupyter Enterprise Gateway (JEG) requires a container image that includes the kernel launcher and language dependencies for each remote kernel.
This implies that we require at least 1 container image per kernel currently. The JEG project has provided kernel-py/kernel-r, and we created our own kernel-py with GPU support and kernel-julia to support GPU-enabled Python/Julia kernels in Orchest.
Because of the proliferation of kernels through projects such as jupyter-xeus we want to create a more generic image creation process that we can re-use for all types of kernels. This could be as simple as a well structured Dockerfile and build script.
Nothing is set in stone regarding an implementation approach, and we should seek collaboration on this with the Jupyter Enterprise Gateway project to reduce duplicate effort and maximize community benefit.

Duplicate issue #776: how to enable jupyter debugger
Created: 2022-03-09T06:09:51Z
Describe the problem this improvement solves
It would be great if can enable jupyter debugger by default
I have tried to

in settings,  configure jupyterlab and pip install xeus-python
in jupyter lab ,  install @jupyterlab/debugger
Still can't get the debugger working.

Closing comment (2022-03-09T08:02:07Z): This issue is related to #138.
My guess would be that installing xeus-python inside JupyterLab does not lead to the kernel being picked up (i.e. not shown in the dropdown when selecting a kernel) because JupyterLab asks the Jupyter Enterprise Gateway for the kernels it supports. Since the kernel is installed in JupyterLab and not in the Enterprise Gateway, the Enterprise Gateway has no knowledge of such kernel.
Repository: orchest/orchest

Issue #327: Adding a button to the pipeline editor to (re)run the entire pipeline
Created: 2021-06-18T15:45:13Z
Describe the solution you'd like
A one-click button in the pipeline editor to (re)run the entire pipeline.
Alternatively, the selection of a pipeline run gets lost after changing things in the editor. As of now, you need to reselect the same subset of steps, what if we just had a button that allows you to rerun the previous ran pipeline selection?
What does your solution aim to solve?
Currently, I often find myself selecting the entire pipeline. Would be great if this could be done with a single button.
Additional context
The most common flows should also have the best UX.

Duplicate issue #428: Run all step shortcut
Created: 2021-08-19T11:53:17Z
Describe the solution you'd like
is there a way to run all step with shortcut? when selecting and panning 20+ steps can be frustrating
What does your solution aim to solve?
ease of running all the steps at once
Describe alternatives you've considered
Add more shortcuts just like ctrl + alt + enter to run all.

Closing comment (2021-08-19T11:55:56Z): Thanks for opening an issue. I definitely like the idea!
Duplicate of #327.
Repository: orchest/orchest

Issue #589: Add a right-click context-menu for actions in the pipeline editor
Created: 2021-12-13T10:49:40Z
Is your feature request related to a problem? Please describe.
Add a right-click context-menu for actions in the pipeline editor
Describe the solution you'd like
Normal right-click menu override that looks consistent with the rest of the MUI components. It can handle actions like:

New step
Duplicate step
Delete step
Run step
Run all incoming steps
Edit in JupyterLab

Duplicate issue #534: Make it easy to duplicate a step
Created: 2021-11-01T09:52:03Z
Is your feature request related to a problem? Please describe.
It's cumbersome to create the same step twice.
Describe the solution you'd like
Add a button to duplicate a step in the pipeline editor.
Ideas
We could combine this with some other ideas in a context menu (right click).
Credit to Serhii Ostapchuk for contributing this on Slack.

Closing comment (2022-02-16T08:49:21Z): Related to #589.
Repository: orchest/orchest

Issue #413: Improve job creation pipeline list when the list contains many elements
Created: 2021-08-05T15:12:38Z
Creating a job when a project has many pipelines leads to a not so nice UX because of the pipeline list in the job creation process. See the attached picture.

Describe the solution you'd like
The list should be improved, perhaps by allowing the pipelines list to take up more screen space.

Duplicate issue #547: Dialog overflow when creating a job
Created: 2021-11-11T13:38:12Z
Describe the bug
Dialog doesn't overflow when creating a job.
To Reproduce
Steps to reproduce the behavior:

Go to Jobs page
Create a new job
(make sure you have multiple pipelines to choose from)
Observe that the select dropdown is contained in the dialog box.

Expected behavior
It should overflow the dialog. A simple overflow: visible on the outer dialog element fixes this.
Environment

OS: Linux
Browser: Brave
Version: 2021.11.1
Environment: prod, cloud

Closing comment (2021-11-12T17:51:57Z): Duplicate of #413
Repository: orkestral/venom

Issue #2308: WAPI Injection throwing an error on recent update. Fix suggestion... 
Created: 2023-06-14T17:57:59Z
The code below is raising an error in recent update, preventing the code to inject the parasite and leading all Store dependencies to failures.

  
    
      venom/src/lib/wapi/wapi.js
    
    
         Line 182
      in
      962d539
    
  
  
    

        
          
           window[injectConfig.webpack] = window[injectConfig.webpack] || []; 
        
    
  


Based on a recent code update in waconnect-team/wajs, instead of forcing the setting of chunk key on window object, we should first check if it exists and, if not, set as an empty array, as shown below:
wppconnect-team/wa-js@5339618
So the proposed fix would be to override that line with:
if (typeof window[injectConfig.webpack] === 'undefined') { window[injectConfig.webpack] = []; }
Already tested locally and it works.

Duplicate issue #2304: window.WAPI.onInterfaceChange not working
Created: 2023-06-14T11:04:46Z
Description
window.WAPI.onInterfaceChange does not provide any status.
Environment

Venom version(s): 5.0.1
Browser: Microsoft Edge 114.0.1823.43
OS: Windows 11
Node version: Node 20

Steps to Reproduce

Add listener by calling window.WAPI.onInterfaceChange(console.log) in browser console after injected WAPI.js

Closing comment (2023-06-14T18:04:20Z): Maybe related to #2308
Repository: orkestral/venom

Issue #2133: Stuck at "update chrome" window in headless mode
Created: 2023-01-25T03:05:27Z
Description
WhatsApp Web keeps stuck at "update chrome" window if you sync the first time in headless mode.
Environment

Venom version(s): v4.3.7
Browser: Chrome 109
OS: Windows 10
Node version: Node 16

Steps to Reproduce

Close all open Chrome instances/windows
Delete "tokens" folder
Start venom in headless mode
Read QR CODE
Close venom
Open venom

In headless mode it gets stuck at "Checking is logged..." message.
If you disable headless mode, you'll see WhatsApp Web is stuck at "update chrome" warning as in screenshot below.
Additional context / Screenshot

Duplicate issue #2121: Checking is logged eternally in the terminal
Created: 2023-01-20T14:45:13Z
Description
Hi, my venon-bot in ubuntu terminal does not connect, nor does it show the qr code. It stays "Checking is logged" and does not go to the next one. Any help please?
Environment

**Venom version(s):**4.3.7
Browser: How get?
OS: Ubuntu 22.04
Node version: Node 19.4.0

Closing comment (2023-01-25T03:09:23Z): This might be related to #2133
Repository: orkestral/venom

Issue #631: Problem with method client.getMessageById
Created: 2021-02-24T12:31:54Z
Description
I'm having trouble when I try to get a message by message id.
Environment

Venom version(s): venom-business
Browser: [e.g. Chrome 87, Chromium 85]
OS: Ubuntu 20 LTS
Node version: Node 12

Steps to Reproduce
const message = await client.getMessageById(messageId)
Log Output
You have triggered an unhandledRejection, you may have forgotten to catch a Promise rejection:
Error: Evaluation failed: Error: MsgKey fromString error: str is null or not a string
     at t.default (https://web.whatsapp.com/app2.a1c0feef6c698420f1cc.js:2:1498763)
     at Function.fromString (https://web.whatsapp.com/app2.a1c0feef6c698420f1cc.js:2:743489)
     at Object.e [as getMessageById] (/var/www/html/node/comunique/node_modules/venom-business/dist/lib/wapi/wapi.js:1:17687)
     at _puppeteer_evaluation_script_:1:37
     at ExecutionContext._evaluateInternal (/var/www/html/node/comunique/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:217:19)
     at process._tickCallback (internal/process/next_tick.js:68:7)

Duplicate issue #645: unhandled promise rejection while number is invalid
Created: 2021-02-26T12:23:52Z
Description
give an error not readable if number is invalid, not return reason why message is not sent
Log Output
(node:7364) UnhandledPromiseRejectionWarning: Error: Evaluation failed: Error: MsgKey fromString error: str is null or not a string at t.default (https://web.whatsapp.com/bootstrap_main.5c62c9ecb1108604f507.js:2:1889667) at Function.fromString (https://web.whatsapp.com/bootstrap_main.5c62c9ecb1108604f507.js:2:1889406) at Object.e [as getMessageById] (D:\laragon\www\wafree\node_modules\venom-bot\dist\lib\wapi\wapi.js:1:22970) at __puppeteer_evaluation_script__:1:37 at ExecutionContext._evaluateInternal (D:\laragon\www\wafree\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:217:19) at processTicksAndRejections (internal/process/task_queues.js:82:5) at async ExecutionContext.evaluate (D:\laragon\www\wafree\node_modules\puppeteer\lib\cjs\puppeteer\common\ExecutionContext.js:106:16)

Closing comment (2021-02-26T16:15:16Z): duplicate #631
use nightly build
Repository: orkestral/venom

Issue #211: OnAnyMessage  download file from send message 
Created: 2020-10-13T03:54:18Z
onAnyMessage  download file from send message not work, receive message works
sender isMe equal true  can't download the file with onAnyMessage event
client.onAnyMessage(async (message) => {
     const buffer = await client.decryptFile(message);
     or 
     const mediaBlob = await client.downloadFile(message);

......

Duplicate issue #613:  message is missing critical data needed to download the file.
Created: 2021-02-19T16:19:44Z
Description
[Description of the bug, When Issue Happens]
Environment

Venom version(s): [2.2.4]
Browser: [e.g. Chrome 87, Chromium 85]
OS: [Windows 10]
Node version: [v10.16.3]

Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Log Output

This problem happens when I am receiving my own messages in the onAnyMessager method

I need to see my own messages

Please when you can answer me

Your Code
(node:10556) UnhandledPromiseRejectionWarning: Error: message is missing critical data needed to download the file.
at Whatsapp. (C:\Users\Lugotech_RD_2\Desktop\PythonSele\Venuz\venom\dist\api\whatsapp.js:238:35)
at step (C:\Users\Lugotech_RD_2\Desktop\PythonSele\Venuz\venom\dist\api\whatsapp.js:46:23)
at Object.next (C:\Users\Lugotech_RD_2\Desktop\PythonSele\Venuz\venom\dist\api\whatsapp.js:27:53)
at C:\Users\Lugotech_RD_2\Desktop\PythonSele\Venuz\venom\dist\api\whatsapp.js:21:71
at new Promise ()
at __awaiter (C:\Users\Lugotech_RD_2\Desktop\PythonSele\Venuz\venom\dist\api\whatsapp.js:17:12)
at Whatsapp.decryptFile (C:\Users\Lugotech_RD_2\Desktop\PythonSele\Venuz\venom\dist\api\whatsapp.js:227:16)
at client.onAnyMessage (C:\Users\Lugotech_RD_2\Desktop\PythonSele\Venuz\venom\examples\basic\index.js:347:37)
at EventEmitter. (C:\Users\Lugotech_RD_2\Desktop\PythonSele\Venuz\venom\dist\api\layers\listener.layer.js:246:21)
at EventEmitter.emit (events.js:198:13)
(node:10556) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 12)
If relevant, paste all of your challenge code in here

Additional context / Screenshot
Add any other context about the problem here. If applicable, add screenshots to help explain.

Closing comment (2021-02-22T10:32:05Z): Duplicate of  #211
Repository: orkestral/venom

Issue #2200: SendButtons not working on multi-device
Created: 2023-03-23T18:50:34Z
Description
The whole conversation is erased and the buttons are not showing on android devices
Environment

Venom version(s): [4.3.7]
Browser: [e.g. Chrome 87, Chromium 85]
OS: [e.g. OSX 10.13.4, Windows 10]
Node version: [18.12.1]

Steps to Reproduce
Log Output

If relevant, paste all of your Log Output

Your Code
client.onMessage(async(message) => {
    const buttons = [
        {
          "buttonText": {
            "displayText": "Text of Button 1"
            }
          },
        {
          "buttonText": {
            "displayText": "Text of Button 2"
            }
          }
        ]
    if (message.body === 'hi') {
        try{
            await client.sendButtons(message.from, 'Buttons',buttons,'description')
            
        }
        catch(err){
            console.log(err)
        }
      
    }
  });

Additional context / Screenshot
Add any other context about the problem here. If applicable, add screenshots to help explain.

Duplicate issue #2237: SendButtons Doesn't working
Created: 2023-04-17T16:08:50Z
sendbuttons function doesnt working on new 5.0.0 version
Environment

**Venom version(s): 5.0.0

Closing comment (2023-04-19T08:42:00Z): And same as #2200
I think its about whatsapp web changes, many libraries struggling this atm.
Hope for best devs can do to find new ways to export this functionality to library again.
Repository: orkestral/venom

Issue #2308: WAPI Injection throwing an error on recent update. Fix suggestion... 
Created: 2023-06-14T17:57:59Z
The code below is raising an error in recent update, preventing the code to inject the parasite and leading all Store dependencies to failures.

  
    
      venom/src/lib/wapi/wapi.js
    
    
         Line 182
      in
      962d539
    
  
  
    

        
          
           window[injectConfig.webpack] = window[injectConfig.webpack] || []; 
        
    
  


Based on a recent code update in waconnect-team/wajs, instead of forcing the setting of chunk key on window object, we should first check if it exists and, if not, set as an empty array, as shown below:
wppconnect-team/wa-js@5339618
So the proposed fix would be to override that line with:
if (typeof window[injectConfig.webpack] === 'undefined') { window[injectConfig.webpack] = []; }
Already tested locally and it works.

Duplicate issue #2306: Error after scanning QR Code and connecting
Created: 2023-06-14T16:55:15Z
Description
As soon as the session status arrives in "waitChat" the puppeteer gives a timeout error
Environment

**Venom version: 4.3.7
OS: Linux Ubuntu 22.04.2 LTS
Node version: Node v16.19.0

Steps to Reproduce

[First Step] Normal connection procedure
[Second Step] Scan the qr code
[and so on...] Wait to finish the connection

Log Output
TimeoutError: waiting for function failed: timeout 30000ms exceeded
at new WaitTask (/app/node_modules/puppeteer/lib/cjs/puppeteer/common/DOMWorld.js:680:34)
at DOMWorld.waitForFunction (/app/node_modules/puppeteer/lib/cjs/puppeteer/common/DOMWorld.js:611:26)
at Frame.waitForFunction (/app/node_modules/puppeteer/lib/cjs/puppeteer/common/FrameManager.js:1089:32)
at Page.waitForFunction (/app/node_modules/puppeteer/lib/cjs/puppeteer/common/Page.js:2385:33)
at injectApi (/app/node_modules/venom-bot/dist/controllers/browser.js:140:16)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Object.create (/app/node_modules/venom-bot/dist/controllers/initializer.js:302:9)

Closing comment (2023-06-14T18:04:57Z): Maybe related to #2308
Repository: orkestral/venom

Issue #595: Error: Evaluation failed: ReferenceError: WAPI is not defined
Created: 2021-02-15T12:51:17Z
After updating to the latest venom version, i'm getting this error "Error: Evaluation failed: ReferenceError: WAPI is not defined"

Duplicate issue #597: Stuck on initializing when bot restarts
Created: 2021-02-15T14:51:38Z
Description
When I create a client and run venom-bot, It works fine. After I connect, the token is generated.
When I turn off the bot and try to re-create the client with the same token, I got stuck on initializing.
This bug was not happening on venom-bot 2.2.3.
Steps to Reproduce

Start any application.
Connect the venom bot, reading the QR code.
Restart the application, with the same token.

Log Output
Stuck here:
info:     [instance_1000050:browser] Initializing browser...
info:     [instance_1000050:client] Initializing...

Expected
The bot should reconnect with the same token.

Closing comment (2021-02-15T17:08:30Z): This issue is related to #595.
But the issue was closed without answers.
Repository: orkestral/venom

Issue #67: QRCode callback not invoked if autoClose is false
Created: 2020-07-15T16:45:48Z
In my case, I want to keep venom runinng and the QRCode refreshing.
For this I defined this config for venom session creation:
const VENOM_CONFIG = { 
    logQR: false, 
    headless: true, 
    browserArgs: ['--no-sandbox'], 
    useChrome: false, 
    autoClose: false, 
    debug: false, 
    devtools: false, 
    disableSpins: true,
    refreshQR: 15000
};
When I run my application, it starts a venom session and the QRCode callback export it as a PNG to my frontend.
Inside the callback I also use a websocket message to notify the frontend that exists a new QRCode, and the frontend download the PNG again to display it to the enduser.
And here is the BUG, the callback is never called again.
Try to open https://web.whatsapp.com/ without pairing it, and keep viewing the QR Code. It will change every minute, and the venom does not intercept the change.
Another bug is, after a while the https://web.whatsapp.com/ will require a user iteration, a click over the QRCode area to force the geration of a new QRCode.

Duplicate issue #61: QRCode is not working
Created: 2020-07-05T12:42:07Z
My phone doesn't recognize the QR Code.
as a temporary solution I've used this options:
{ headless: false, logQR: false, useChrome: true } and read QRCode at Chrome Window, but it doesn't work at my terminal

Closing comment (2020-07-17T11:25:14Z): I think this is related to #67
Repository: orkestral/venom

Issue #2308: WAPI Injection throwing an error on recent update. Fix suggestion... 
Created: 2023-06-14T17:57:59Z
The code below is raising an error in recent update, preventing the code to inject the parasite and leading all Store dependencies to failures.

  
    
      venom/src/lib/wapi/wapi.js
    
    
         Line 182
      in
      962d539
    
  
  
    

        
          
           window[injectConfig.webpack] = window[injectConfig.webpack] || []; 
        
    
  


Based on a recent code update in waconnect-team/wajs, instead of forcing the setting of chunk key on window object, we should first check if it exists and, if not, set as an empty array, as shown below:
wppconnect-team/wa-js@5339618
So the proposed fix would be to override that line with:
if (typeof window[injectConfig.webpack] === 'undefined') { window[injectConfig.webpack] = []; }
Already tested locally and it works.

Duplicate issue #2305: Store.Chat is no longer available
Created: 2023-06-14T11:07:35Z
Description
Store.Chat no longer available and causes checkNumberStatus and sendMessage function to fail
Environment

Venom version(s): 5.0.1
Browser: Microsoft Edge 114.0.1823.43
OS: Windows 11
Node version: Node 20

Steps to Reproduce

Inject WAPI.js script through browser console
Call window.WAPI.checkNumberStatus('<whatsapp-id>')

Closing comment (2023-06-14T18:04:35Z): Probably related to #2308
Repository: osTicket/osTicket

Issue #1304: Feature request - Make it easier for teams to find their tickets
Created: 2014-09-23T12:15:41Z
Currently, when a ticket is assigned to a team, it doesn't show up in any team member's "My Tickets" tab.  If it could be adjusted for the tickets to show up under "My Tickets" for all team members, that would be very helpful.  Alternatively, adding a new tab labeled "Team Tickets" would also work.
The reason for this request is because currently, our team members are having to use the advanced search to filter for open tickets assigned to their team.  This works, but they would love to have all assigned tickets easily viewable in a tickets tab.  We use teams extensively here, very few people are assigned tickets directly to themselves.

Duplicate issue #1305: Assignign tickets to teams
Created: 2014-09-23T12:17:59Z
2 issues (ost 1.9.2)
if i am a member of "team1" i cannot reassign a ticket currently assigned to me to team1
it could be usefull to see in "my tickets" the tickets assigned to teams that i am member of.
thank you

Closing comment (2014-09-24T14:49:31Z): This is partially a duplicate of #1304
Repository: osTicket/osTicket

Issue #2855: develop-next: Email Autocompletion (SCP) broken
Created: 2016-01-12T10:00:14Z
If I create a new ticket, the email search does not contain the right address anymore.
Before (somwhere commit 3e47a23)

After (at commit 364044e):

I don't have time to bisect further right now, but maybe someone else can...

Duplicate issue #2862: Delevelop Next breaks user search via LDAP plugin
Created: 2016-01-13T23:56:44Z
I notice can no longer search for users via LDAP unless I fully spelled out their name.

Closing comment (2016-01-13T23:57:49Z): I noticed is the same as  #2855
Repository: osTicket/osTicket

Issue #3293: v1.10-RC3: Lazy Lock Issue - Your lock is expiring soon
Created: 2016-07-28T02:57:59Z
When I edit a ticket I get the "Your lock is expiring soon".
The lock you hold on this ticket will expire soon. Would you like to renew the lock? prompt. I click "Renew" and it spins forever.
If I submit the reply I get the " This action requires a lock. Please try again" alert.
Server Information
osTicket Version    v1.10-rc.3 (907ec36) —  Up to date
Web Server Software Apache
MySQL Version   5.5.45
PHP Version 5.6.22

Duplicate issue #3302: V1.10-RC3: Ticket "locked" / User logged out
Created: 2016-08-03T11:23:24Z
When a user was automatically logged out (timeout) while answering a ticket the error message "Ticket locked by another agent" (or something like that) appears when trying to send.

Closing comment (2016-08-03T17:03:51Z): I wonder if it might be related to #3293
Repository: osTicket/osTicket

Issue #3178: error: error get info from ticket when delete custom forms "getDynamicFields() on a non-object "
Created: 2016-06-06T14:04:35Z
made custom forms or fiels (can be in dinamic forms or in users organizations)
made some tickets using web or angent interface with those custom forms enabled
delete all custom forms
try to edit the issue created recently that used the custom forms

got that error:
Fatal error: Call to a member function getDynamicFields() on a non-object in /var/www/osticket/include/class.dynamic_forms.php on line 877
this due the custom fields in the fomrs deleted in the issues triying to edit are not existing, obviously due are now deleted in step 3, so cannot edit the ticket
happened in 1.9.11 and 1.10rc, in 1.10 only some times.
in any time, i not using in production 1.10 ! so due theres is not 1.10 oficial firts production release

Duplicate issue #1485: 1.9.4 - Cannot delete (empty) organization
Created: 2014-11-12T20:33:34Z
Im in screen Organizations. I Click 1 organisation open and try to delete that particular organization. I I confirm with " yes Delete" . I see "Loading" ,,, It stays on "loading forever" .. it does not delete the organization. I can only escape the screen by pressing "Esc"

Closing comment (2016-06-06T14:08:21Z): similar to #3178
Repository: osTicket/osTicket

Issue #1984: [develop-next] Installation fails when using language pack (German) as default language
Created: 2015-04-21T07:53:14Z
Hey, just having some time to check again at the develop-next version, so I guess some more issue to come, starting with this one here.
My setup:

Fresh installation (not an upgrade)
osTicket develop-next (--> 3278541)
ldap plugin
passthru plugin
german language pack

When I then tried to install it with German as the default language, the following error showed up:
PHP Fatal error: Uncaught exception 'OrmException' with message 'Group: id: Feld nicht definiert' in /srv/www/htdocs/oscaroo-next/include/class.orm.php:220 Stack trace: #0 /srv/www/htdocs/oscaroo-next/include/class.orm.php(224): VerySimpleModel->get('id', NULL) #1 /srv/www/htdocs/oscaroo-next/include/class.group.php(55): VerySimpleModel->__get('id') #2 /srv/www/htdocs/oscaroo-next/include/class.group.php(148): Group->getId() #3 /srv/www/htdocs/oscaroo-next/include/class.group.php(265): Group->updateDeptAccess(Array, Array) #4 [internal function]: Group::__create(Array, Array) #5 /srv/www/htdocs/oscaroo-next/include/class.i18n.php(78): call_user_func_array('Group::__create', Array) #6 /srv/www/htdocs/oscaroo-next/setup/inc/class.installer.php(158): Internationalization->loadDefaultData() #7 /srv/www/htdocs/oscaroo-next/setup/install.php(52): Installer->install(Array) #8 {main} thrown in /srv/www/htdocs/oscaroo-next/include/class.orm.php on line 220
When using English as the default language everything works fine.

Duplicate issue #1964: error [develop-next]: call to member function on a non-object
Created: 2015-04-15T22:53:39Z
i toggle today the current lasted from developmen-next and got this at new install:
Fatal error: Call to a member function getPrimaryLanguage() on a non-object in /opt/osticket/osticket-git/include/class.i18n.php on line 360

i delete the older tarring and i cannot install now! i cant remember from what commit i download the previously tar file
[edited] change to real path due i have a network SAN mounted as osticket!

Closing comment (2015-04-27T15:18:09Z): this iisue its related to #1984 seems that languaje support changed a lot and its very unstable..
Repository: osTicket/osTicket

Issue #672: Ticket Filters - "Stop Processing On Match" doesn't work
Created: 2014-03-10T22:50:11Z
I'm using the 1.8 develop-next branch of osTicket
I have one filter whose Execution Order is set to "1" and the "Stop Processing On Match" checkbox is checked.
I have another filter whose Execution Order is set to "98".
To me, this seems like it would apply filter #1 and then stop running through the rest of the filters, correct? However, it actually appears to skip filter #1 completely and just apply filter #98.
After doing some more investigation, it appears as though the filters are being applied in reverse order. If I edit line 762 in include/class.filter.php and change it to "$sql.=' ORDER BY execorder DESC';", the filters seem to work as expected so far.
I'm not sure if that's the correct place to edit & I'm new to git/github and osTicket, so I figured I should let someone else investigate this.

Duplicate issue #802: Ticket Filters Continue processing after match
Created: 2014-04-25T12:57:12Z
I setup multiple ticket filters and told them to stop processing after a match.  All my tickets continue processing filters until all filters are checked.
For example: I have tickets that are high or emergency priority assigned to our supervisor team.  I put it the process order as #1 and told it to stop processing on match.  Later in my filters another rule processed the same ticket and reassigned to another team based on schools assignment.
How are filters processed?  Low to High or High to Low?  Should the #1 rule checking priority stop processing the ticket once it matches the filter rule?
When I changed the execution order around everything seemed to work the way I expected.  I made the high priority rule #99 and the school filters #98 and the ticket assigned as expected.  Checking and unchecking stop on match did not seem to help.
TIA for all of your help.

Closing comment (2014-04-28T13:29:48Z): Thanks for posting this. I've look at the code several times and haven't seen the bug yet. This is a duplicate of #672
Repository: osTicket/osTicket

Issue #526: Error on RC
Created: 2014-02-04T15:54:11Z
Sorry if this has been posted before. On RC getting the following for certain tickets
Fatal error: Call to a member function getPhoneNumber() on a non-object in
class.ticket.php on line 311
Tickets show as follows in the alert to admin

and then in osticket


Sorry if etiquette is incorrect first issue report on github
All tickets created via email
System IIS7

Duplicate issue #598: 1.8.1 'osTicket Upgraded!' ticket will not load
Created: 2014-02-22T21:43:30Z
When I performed my upgrade to 1.8.1, the upgrade went perfectly. The system updated, and performed all the steps.
As in previous version, when you upgrade the system leaves behind a nice Support ticket (osTicket Upgraded!).
However, when I open this ticket to delete, archive, or work with I get the following error:
Fatal error: Call to a member function getPhoneNumber() on a non-object in /path/to/support/include/class.ticket.php on line 311
As shown below:

If I attempt to EDIT the ticket I get this:
Fatal error: Call to a member function getName() on a non-object in /path/to/support/include/staff/ticket-edit.inc.php on line 36

Closing comment (2014-02-22T23:22:28Z): duplicate of #526
Already resolved with pull #588
Here is the change needed to resolve.
edit include/class.ticket.php
Change line 2287 from:
.' ,user_id='.db_input($user->id)
to:
.' ,user_id='.db_input($user->getId())