primordic/IssueDupesLite huggingface dataset:
Repository: nvm-sh/nvm

Issue #394: problem about installing nvm on ubuntu 1310 
Created: 2014-04-09T06:14:57Z
I tried to install nvm on ubuntu 1310. first I run command below:
curl https://raw.github.com/creationix/nvm/v0.4.0/install.sh | sh
and then i activated nvm:
source ~/.nvm/nvm.sh
intsalled nodejs:
nvm install 0.10
finally I could use node normal. but after i had restarted system, the nvm didn't work,when run command such as "nvm ls", i got error prompt:
user@ubuntu:~$ nvm ls
sbin
mkdir: cannot create directory ‘/usr/sbin/alias’: Permission denied

Duplicate issue #483: Error installing on fresh ubuntu 14.04
Created: 2014-07-24T21:36:57Z
Script as taken from the README.md file
lloyd@zenbook:~$ wget -qO- https://raw.githubusercontent.com/creationix/nvm/v0.12.1/install.sh | bash
=> Downloading nvm from git to '/usr/sbin'
=> fatal: destination path '/usr/sbin' already exists and is not an empty directory.
lloyd@zenbook:~$

Closing comment (2014-07-24T21:38:33Z): This is a duplicate of #394 - it contains a workaround.
Repository: nzbget/nzbget

Issue #741: Crashing every minute
Created: 2021-04-08T06:15:24Z
Hey guys, at the moment I'm getting a crash every minute or so that results in NZBGet reloading.
[INFO] nzbget 21.0 server-mode
[INFO] nzbget 21.0 server-mode
[INFO] nzbget 21.0 server-mode

This causes everything to stop, but then continues downloading for a minute or so, then restarts again.
I'm using the linuxserver.io container, but posting here because I don't think it's container specific.
Previously (and still occasionally) I get
[ERROR] Binding socket failed for 0.0.0.0: ErrNo 98, Address in use
[ERROR] Binding socket failed for 0.0.0.0: ErrNo 98, Address in use
[ERROR] Binding socket failed for 0.0.0.0: ErrNo 98, Address in use
[ERROR] Binding socket failed for 0.0.0.0: ErrNo 98, Address in use

But there is nothing else on or trying to be on the same port
# netstat -ntlpa | grep 6789
#

If anyone has thoughts or suggestions, I'd appreciate them. :)

Duplicate issue #743: NZBninja not connecting
Created: 2021-04-12T20:31:54Z
Hi,
I've been having a "Could not read from TLS-Socket: Connection closed by remote host" error from NZBninja for a few days. It was previously working perfectly fine. Ninja support tell me there has been other reports for the same issue recently and I wanted to check if that was identified here.
Thanks a lot !

Closing comment (2021-04-14T13:39:32Z): May be related to #741  #745
Repository: nzbget/nzbget

Issue #618: Update unrar to 5.7 and 7-zip to 19.0
Created: 2019-03-03T23:41:13Z
In this issue:

 Build unrar 5.7 for Linux, BSD and Android;
 Build unrar 5.7 for Mac;
 Update unrar to 5.7 on Windows;
 Improve Windows installer to provide unrar in 32 bit and 64 bit variants;
 Update 7-zip to 19.0 on Windows;
 Improve Windows installer to provide 7-zip in 32 bit and 64 bit variants;
 Update 7-zip to 16.02 on Mac (was 9.20 still);

7-zip on Linux, BSD, Android and Mac remains at version 16.02 as there is no newer version for these platforms.

Duplicate issue #616: Update Unrar and 7zip to current versions.
Created: 2019-03-03T21:37:25Z
7zip is currently at version 19.00
unrar is at 5.7 which removes .ace support and fixes a long standing CVE.
Can these be updated for next release?
Thank you.

Closing comment (2019-03-03T23:41:51Z): The progress will be tracked in #618.
Repository: nzbget/nzbget

Issue #500: Directories have wrong owner
Created: 2018-01-29T12:04:39Z
When starting nzbget with DaemonUsername=_not_root in nzbget.conf for the first time, a couple of directories (TEMPDIR, QUEUEDIR, and NZBDIR) are created in ${MainDir} with as owner root. This causes an issue as these directories cannot be used by nzbget after privileges have been dropped to _not_root.
Expected behaviour is that nzbget creates these directories with as owner _not_root.
Workaround is to chown these directories manually.
If I'm not mistaken TEMPDIR, QUEUEDIR, and NZBDIR are created as part of Options::InitOptions, which is used before privileges are dropped. 
  
    
      nzbget/daemon/main/Options.cpp
    
    
        Lines 662 to 668
      in
      7deb3c1
    
  
  
    

        
          
           CheckDir(m_destDir, OPTION_DESTDIR, mainDir, false, false); 
        

        
          
           CheckDir(m_interDir, OPTION_INTERDIR, mainDir, true, false); 
        

        
          
           CheckDir(m_tempDir, OPTION_TEMPDIR, mainDir, false, true); 
        

        
          
           CheckDir(m_queueDir, OPTION_QUEUEDIR, mainDir, false, true); 
        

        
          
           CheckDir(m_webDir, OPTION_WEBDIR, nullptr, true, false); 
        

        
          
           CheckDir(m_scriptDir, OPTION_SCRIPTDIR, mainDir, true, false); 
        

        
          
           CheckDir(m_nzbDir, OPTION_NZBDIR, mainDir, false, true); 
        
    
  


Setting the fifth argument in, e.g., L664 to false causes nzbget to error out with as message that the directory is not available. The latter is true as, e.g., TEMPDIR has not been created. As such, it seems that checking/creating of these directories only happens at startup, which is done before dropping privileges.
Is the above behaviour intentionally?

Duplicate issue #512: Folder permission issue
Created: 2018-02-24T07:01:55Z
Hi,
As user root, if I set DaemonUsername to another user (say aureq) and then run the command as root the command nzbget -p, folder like InterDir, NzbDir, QueueDir and TempDir are created (Ok),but the ownership belongs to root. This will later creates a permission issue.

Closing comment (2018-02-24T07:15:23Z): Duplicate of #500.
Repository: nzbget/nzbget

Issue #792: [BREAKING] "Invalid option a", due to Win11 Default Terminal Swap
Created: 2021-11-23T15:12:30Z
https://forum.nzbget.net/viewtopic.php?t=3910
Win11 offers to default your terminal to the fancier (and superior) Windows Terminal. This breaks NZBG completely.  Easy to repro. See thread above for further details.

Duplicate issue #791: "Invalid option a"
Created: 2021-11-23T15:11:23Z

Closing comment (2021-12-18T10:43:15Z): Duplicate of : #792
Repository: nzbget/nzbget

Issue #594: downloads stopped working TLS-problems
Created: 2019-01-02T20:39:25Z
downloads stopped were working fine running v16 til 30/12, since then i keep getting the same errors:
-Could not resolve hostname usenet.premiumize.me: ErrNo 0, Success
-Could not read from TLS-Socket: Connection closed by remote host
-Could not write to TLS-Socket: Connection closed by remote host
after update to v20 I get these messages
-Article someshow.s1e1 [1/68] @ Premiumize (usenet.premiumize.me) failed, could not fetch article:
Connection closed by remote host.
-Could not receive data on socket from usenet.premiumize.me: ErrNo 104, Connection reset by peer
As a test i tried disableing encryption but this solved nothing, and when turning it on again the cypher "RC4-MD5" wasen't recognised anymore (solved after extra reload, or time fixed it idk).
i have contacted my newsprovider and they claim everything is working correctly on their side.
I installed sabnzb as a test and this would download fine with  pm.me .
thoughts?

Duplicate issue #746: Cipher auto-negotiation fails for usenet.premiumize.me
Created: 2021-04-15T15:29:00Z
Issue referenced in #594 witch was closed but never resolved.
This is the list of supported ciphers. Picking one of these manually, works fine.
Not sure if this is something that can be fixed in nzbget  but I'm posting this for reference.
Testing ECDHE-RSA-AES256-GCM-SHA384...YES
Testing DHE-RSA-AES256-GCM-SHA384...YES
Testing ECDHE-RSA-AES128-GCM-SHA256...YES
Testing DHE-RSA-AES128-GCM-SHA256...YES
Testing ECDHE-RSA-AES256-SHA384...YES
Testing DHE-RSA-AES256-SHA256...YES
Testing ECDHE-RSA-AES128-SHA256...YES
Testing DHE-RSA-AES128-SHA256...YES
Testing ECDHE-RSA-AES256-SHA...YES
Testing DHE-RSA-AES256-SHA...YES
Testing DHE-RSA-CAMELLIA256-SHA...YES
Testing ECDHE-RSA-AES128-SHA...YES
Testing DHE-RSA-AES128-SHA...YES
Testing DHE-RSA-SEED-SHA...YES
Testing DHE-RSA-CAMELLIA128-SHA...YES
Testing AES256-GCM-SHA384...YES
Testing AES128-GCM-SHA256...YES
Testing AES256-SHA256...YES
Testing AES128-SHA256...YES
Testing AES256-SHA...YES
Testing CAMELLIA256-SHA...YES
Testing AES128-SHA...YES
Testing SEED-SHA...YES
Testing CAMELLIA128-SHA...YES

Closing comment (2021-04-19T19:12:49Z): Please describe the issue in more details. From the very limited info you gave I don't see how this is related to #594. In the mentioned issue DNS requests did not work and many other things.
Repository: nzbget/nzbget

Issue #780: [Feature Request] Add check with cfv, renaming obfuscated files back to the original filenames
Created: 2021-08-29T08:19:12Z
As written here, https://forums.sabnzbd.org/viewtopic.php?t=13254, could nzbget integrate something similar?

Duplicate issue #781: .r00 files and unpacking then deleting
Created: 2021-09-02T19:16:58Z
Not really a bug as such, but when adding file types to be deleted after unpacked, how do I go about adding .r00 file types? The file types ascend in number with the parts, for instance; .r00, .r01, .r02, .r03 and so on.
Im on a linux docker system for reference as well.

Closing comment (2021-09-17T07:09:17Z): Is this similar to #780?
Repository: nzbget/nzbget

Issue #14: Final migration switch: update DNS record
Created: 2015-06-18T19:02:42Z
Update DNS record to point to new site on GitHub Pages.
Depends on #10, #11, #12, #13.

Duplicate issue #47: Check for Updates often fails
Created: 2015-07-07T08:52:00Z
After migration of the web-site to GitHub the function Check for Updates often shows error message:

Check failed. Please try again later.

After a few attempts the check succeeds eventually.

 investigate on which step the check fails;
 if not fixable on our side as a workaround possibly implement multiple retries before reporting error.

Closing comment (2015-07-07T12:18:46Z): This is related to #14.
Investigation
When using GitHub Pages with own root domains the GitHub's server may respond with 302-redirect. For subdomains GitHub serves the pages using CDN (and never responds with redirects). For root domains this is not possible because the root domains must be mapped to static IP-addresses (DNS A-Record). Therefore the pages on root domains have to be served by the main GitHub Pages server. That server doesn't like high loads and may respond with 302-redirect, as GitHub documentation says "to prevent DDOS attacks".
Back to NZBGet: when checking for updates NZBGet doesn't follow redirects. That causes the Check for Update-function to fail if GitHub responds with 302-redirect.
Quick solution
A quick and dirty solution is to configure DNS for the root domain to use CNAME-record (which points to GitHub's CDN) instead of using A-record. I did this and at least in my tests this has solved the issue. No single failure since after. The GitHub's documentation discourages the using of this technique as it may cause problems for other services on the same root domain, such as email. Luckily nzbget.net is used solely for web-hosting.
TODO
Nonetheless the implementation of Check for Update-feature must be improved to follow redirects. This will allow to switch the DNS back to A-record if any problem with current setup arise.
Repository: nzbget/nzbget

Issue #77: Communication errors in web-interface
Created: 2015-09-03T08:52:10Z
Sometimes web-interface looses connection to NZBGet, even on local network without network issues.

Duplicate issue #77: Communication errors in web-interface
Created: 2015-09-03T08:52:10Z
Sometimes web-interface looses connection to NZBGet, even on local network without network issues.

Closing comment (2015-10-13T20:00:07Z): As reported on forum there are issues with reverse proxies apache and nginx.
They are caused by using of custom header X-Auth-Token (related to #77), which these proxies use for their own needs. The problem doesn't always appear but depend on authentication mode configured in proxies.
TODO: to solve the issue we should rename X-Auth-Token to something unique like X-Auth-Token-2 :)
Repository: nzbget/nzbget

Issue #741: Crashing every minute
Created: 2021-04-08T06:15:24Z
Hey guys, at the moment I'm getting a crash every minute or so that results in NZBGet reloading.
[INFO] nzbget 21.0 server-mode
[INFO] nzbget 21.0 server-mode
[INFO] nzbget 21.0 server-mode

This causes everything to stop, but then continues downloading for a minute or so, then restarts again.
I'm using the linuxserver.io container, but posting here because I don't think it's container specific.
Previously (and still occasionally) I get
[ERROR] Binding socket failed for 0.0.0.0: ErrNo 98, Address in use
[ERROR] Binding socket failed for 0.0.0.0: ErrNo 98, Address in use
[ERROR] Binding socket failed for 0.0.0.0: ErrNo 98, Address in use
[ERROR] Binding socket failed for 0.0.0.0: ErrNo 98, Address in use

But there is nothing else on or trying to be on the same port
# netstat -ntlpa | grep 6789
#

If anyone has thoughts or suggestions, I'd appreciate them. :)

Duplicate issue #738: Debug Logging without recompile
Created: 2021-03-07T00:36:59Z
Hi Folks, I have an issue I'm running into that every few days I get Communication error! Invalid Status: 502 or Communication error! Cannot establish connection to NZBGet. (if I browse directly bypassing the reverse proxy) presented when I try to connect to nzbget. Restarting the container doesn't fix this and the only thing that does it to blow away the root directory and start again, then wait for the issue to come back. This isn't tenable.
I'd like to dig into this in more detail but can't recompile with the debug flag (or at least would prefer not to due to this being docker and I think it goes a bit beyond what I'm hoping). Is there a way to switch debug logging on without that? At the moment the only thing I can get from the logging is the below single line which is logged every time I browse to the site:
Sat Mar  6 16:25:56 2021	INFO	nzbget 21.0 server-mode

Closing comment (2021-04-14T13:40:15Z): May be related to #741 #745
Repository: nzbget/nzbget

Issue #784: TLS certificate verification failed for XXXXXX: certificate has expired. For more info visit http://nzbget.net/certificate-verification
Created: 2021-09-30T16:23:37Z
I'm assuming this issue is because of the LetsEncrypt Root CA expiration today that is affecting a lot of sites.  No nzb's will download unless Cert Check is disabled.

Duplicate issue #821: TLS certificate verification failed for nzbget.net: certificate has expired. For more info visit http://nzbget.net/certificate-verification
Created: 2022-07-19T17:53:41Z
Just started to get this error today. However the linked documentation doesn't have steps to resolve this issue.

Closing comment (2022-09-03T07:11:52Z): Duplicate of #784
Repository: objectionary/eo

Issue #1323: Not stable behaviour of "stdout" + "sprintf"
Created: 2022-09-07T14:40:55Z
I have a simple program:
[] > fff
  QQ.io.stdout > @
    QQ.txt.sprintf
      "out is %d\n"
      123

then I run:
eoc clean
eoc dataize fff

and I get the following error:
EOorg.EOeolang.EOstringν12="Error at "EOorg.EOeolang.EOio.EOstdout#text" attribute; caused by Can't #copy() package object 'org.eolang.txt.sprintf'"SF

BUT, if I run eoc clean again, and adding aliases to my code, so the code will looks like:
+alias org.eolang.txt.sprintf
+alias org.eolang.io.stdout

[] > fff
  stdout > @
    sprintf
      "out is %d\n"
      123

and then eoc dataize fff  -> All is working OK.
@yegor256 , I think there is something wrong with uploading objects

Duplicate issue #1477: Dataization fails for program from README
Created: 2022-11-21T11:58:27Z
I've created the program from README:
[] > app
  QQ.io.stdout > @
    QQ.txt.sprintf
      "Hello, %s!"
      "Jeffrey"

Then run the next command:
eoc clean
eoc dataize app
And I get the next error:
EO version is 0.28.11
EO objects registered in /Users/lombrozo/Workspace/EOlang/Projects/newcomer/.eoc/eo-foreign.json
EO version is 0.28.11
EO program assembled in /Users/lombrozo/Workspace/EOlang/Projects/newcomer/.eoc
EO version is 0.28.11
Java sources generated in /Users/lombrozo/Workspace/EOlang/Projects/newcomer/.eoc/generated-sources
EO version is 0.28.11
Java .class files compiled into /Users/lombrozo/Workspace/EOlang/Projects/newcomer/.eoc
EO version is 0.28.11
Executable JAR created at /Users/lombrozo/Workspace/EOlang/Projects/newcomer/.eoc/eoc.jar
EOorg.EOeolang.EOstringν21="Error at "EOorg.EOeolang.EOio.EOstdout#text" attribute; caused by Can't #copy() package object 'org.eolang.txt.sprintf'"SF

The problem: EOorg.EOeolang.EOstringν21="Error at "EOorg.EOeolang.EOio.EOstdout#text" attribute; caused by Can't #copy() package object 'org.eolang.txt.sprintf'"SF

Closing comment (2022-12-07T07:43:52Z): Duplicate of #1323
Repository: objectionary/eo

Issue #625: OyRemote.java:59-62: Resolve abbreviated hash to a proper...
Created: 2022-05-09T08:30:36Z
The puzzle 490-82991e51 from #490 has to be resolved:

  
    
      eo/eo-maven-plugin/src/main/java/org/eolang/maven/OyRemote.java
    
    
        Lines 59 to 62
      in
      fc50206
    
  
  
    

        
          
                * @todo #490:30m Resolve abbreviated hash to a proper hash. 
        

        
          
                *  In order to avoid collisions resolve hash 
        

        
          
                *  (or branch) to a complete sha-256 hash of the commit. 
        

        
          
                *  Use only sha-256 hashes as a caching criteria. 
        
    
  


The puzzle was created by @yegor256 on 09-May-22.
Estimate: 30 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

Duplicate issue #765: local Objectionary cache must depend on the version
Created: 2022-06-19T19:37:33Z
Now, the first build of local EO program downloads .eo sources into ~/.eo directory. Then, when I update the version of eo compiler to the latest one, I expect the latest .eo sources to come from Objectionary. However, the oldest versions are taken from the local cache.
To solve this, we should make local cache version-dependent. The request to Objectionary class should have two arguments instead of one: 1) object name, and 2) version of objectionary.

Closing comment (2022-07-19T13:40:37Z): Duplicate of #625
Repository: objectionary/eo

Issue #748: float objects according to "On the Origins of Objects"
Created: 2022-06-16T17:11:17Z
Should we get rid of these objects because they are not included in the "Origin of objects" article ? Or we should add them to it?

float.neq
float.neg
float.signum (will be implemented in eo-math)
float.pow  (will be implemented in eo-math)
float.abs (will be implemented in eo-math)
float.sin (will be implemented in eo-math)
float.cos (will be implemented in eo-math)
float.as-int
float.as-string

Duplicate issue #773: get rid of `float.sin` and `float.cos`
Created: 2022-06-21T13:15:17Z
Since eo-math was released, it has angle object with sin and cos, so they are not needed here any more

Closing comment (2022-06-21T13:24:46Z): @maxonfjvipon I think this issue is duplicate of #748
Repository: objectionary/eo

Issue #1791: Allow division by float zero in `EOfloat$EOdiv`
Created: 2023-02-11T13:16:23Z
Allow division by float zero in EOfloat$EOdiv for being able to make nan, positive-infinity and negative-infinity decorated 0.0.div 0.0, 1.0.div 0.0 and -1.0.div 0.0
This task had to be created by pdd bot after this PR but it hadn't for some reason.
@Graur please assign me

Duplicate issue #1800: nan.eo:28-30: Allow division by float zero in...
Created: 2023-02-15T10:07:52Z
The puzzle 1253-c101194f from #1253 has to be resolved:

  
    
      eo/eo-runtime/src/main/eo/org/eolang/nan.eo
    
    
        Lines 28 to 30
      in
      6abf13e
    
  
  
    

        
          
           # @todo #1253:30min. Allow division by float zero in EOfloat$EOdiv for being 
        

        
          
           #  able to make float.nan, float.positive-infinity and float.negative-infinity 
        

        
          
           #  decorated 0.0.div 0.0, 1.0.div 0.0 and -1.0.div 0.0 accordingly 
        
    
  


The puzzle was created by @rultor on 15-Feb-23.
Estimate: 30 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

Closing comment (2023-02-15T10:23:16Z): Duplicate of #1791
@yegor256 please close
Repository: objectionary/eo

Issue #846: 'failOnWarnings' into eo-runtime
Created: 2022-07-10T03:36:03Z
Let's add this flag to eo-maven-plugin in eo-runtime module and fix all warnings

Duplicate issue #971: apply new style of sorting `meta` to native objects
Created: 2022-08-01T11:41:00Z
on version 0.26.0, meta information in native objects still remains unsorted:

Closing comment (2022-08-03T11:34:06Z): Duplicate of #846
Repository: objectionary/eo

Issue #3257: eo:xmir-to-phi is too slow
Created: 2024-07-07T12:41:06Z
I tried to run xmir-to-phi goal with the following configuration:
<plugin>
  <groupId>org.eolang</groupId>
  <artifactId>eo-maven-plugin</artifactId>
  <version>0.38.4</version>
  <executions>
    <execution>
      <id>convert-xmir-to-phi</id>
      <phase>process-classes</phase>
      <goals>
        <goal>xmir-to-phi</goal>
      </goals>
      <configuration>
        <phiInputDir>${project.build.directory}/generated-sources/jeo-xmir</phiInputDir>
        <phiOutputDir>${project.build.directory}/generated-sources/jeo-phi</phiOutputDir>
      </configuration>
    </execution>
  </executions>
</plugin>

I run this goal on the project with thousands of xmir files and it took me hours to convert only some xmir files (I haven't managed to wait until the end of printing and stopped the test.) Could you speed up the printing process somehow, please?

Update: The problem is still here even in 0.50.0 version.
Latest observations: #3257 (comment)

Duplicate issue #3490: XSL Transformations In `eo-parser` Are Extremely Slow
Created: 2024-11-12T10:48:22Z
The transformations under eo-parser/src/main/resources/org/eolang/parser are extremely slow. They cause such problems like:

objectionary/jeo-maven-plugin#834
objectionary/hone-maven-plugin#69

We need to optimise the most wasteful transformations.

Closing comment (2024-11-12T11:30:39Z): @volodya-lombrozo very much related to #3257
Repository: objectionary/eo

Issue #2689: Prettify phi-calculus expression
Created: 2023-12-08T13:07:05Z
Now phi-calculus expression is printed in one line which makes it hard to read. It would be nice to make it more vertical with indentations, like in this blog post

Duplicate issue #2777: one-line phi expression generated by PhiMojo is not readable by a human
Created: 2024-01-15T09:12:50Z
Currently, we print it all in one line. It's hard to read. Would be great if we can format it somehow, by adding EOLs and TABs (two spaces) where it's appropriate.

Closing comment (2024-01-15T09:14:22Z): @yegor256 duplicate of #2689
Repository: objectionary/eo

Issue #2610: PhiMojo
Created: 2023-11-21T06:37:18Z
Let's create a new PhiMojo, which takes .xmir files from the target/eo/2-optimize directory and generates .phi files, saving them into the target/eo/phi directory. Let's stick to the format of phi expressions already defined at https://github.com/objectionary/try-phi

Duplicate issue #2535: to create a translator from `xmir` to `phi-calculus`
Created: 2023-10-11T07:58:36Z
We need to create a translator from xmir to phi-calculus.
It should be a new Mojo. This mojo must get xmir as input and transform it to the phi-calculus.
Here is some examples of the existing software (can help to implement this task):

try-phi,
phie

Closing comment (2023-11-21T06:40:59Z): duplicate of #2610
Repository: objectionary/eo

Issue #3322: `xmir-to-phi` doesn't fail on invalid attribute names
Created: 2024-08-08T06:47:29Z
When I run xmir-to-phi goal I successfully convert all xmir files into PHI expressions. However, recently we realised that PHI expressions we get have a mistake:
I-0 ↦ Φ.org.eolang.param,


AFAIK, in PHI, all attribute labels must start with a lowercase letter.

You can read more about it here.
Expected behaviour: xmir-to-phi throws an error that is saying about the wrong naming.
Here is my configuration:
<plugin>
  <groupId>org.eolang</groupId>
  <artifactId>eo-maven-plugin</artifactId>
  <version>0.39.0</version>
  <executions>
    <execution>
      <id>convert-xmir-to-phi</id>
      <phase>process-classes</phase>
      <goals>
        <goal>xmir-to-phi</goal>
      </goals>
      <configuration>
        <phiInputDir>${opeo.modified}</phiInputDir>
        <phiOutputDir>${eo.phi.output}</phiOutputDir>
      </configuration>
    </execution>
  </executions>
</plugin>

Duplicate issue #3346: PhiMojo doesn't fail on invalid identifiers
Created: 2024-08-22T04:34:33Z
See objectionary/opeo-maven-plugin#411
If I pass this XMIR to PhiMojo, it generates .phi file:
         DRETURN-1 ↦ Φ.org.eolang.jeo.opcode(
            α0 ↦ Φ.org.eolang.int(
              α0 ↦ Φ.org.eolang.bytes(
                Δ ⤍ 00-00-00-00-00-00-00-AF
              )
            )
          )
 

This is an obvious syntax error in phi (the identifier name DRETURN-1 is not valid, it must start with a small English letter). PhiMojo should not generate such files, but fail with an error.

Closing comment (2024-08-22T14:44:57Z): @yegor256 I is a duplicate of #3322
Repository: objectionary/eo

Issue #1008: eo-test - new module for test utils
Created: 2022-08-08T15:29:23Z
Let's create a new module and move the following existing classes into it:

CheckPack - let's turn it into Hamcrest matcher
CheckXSL - also, let's make a matcher out of it

Then, let's create a new JUnit5 ArgumentsProvider, and use it in PacksTest, SyntaxTest, and OptimizePacksTest.

Duplicate issue #1109: SnippetTest.java:69-71: Method `jdkExecutable` is...
Created: 2022-08-29T07:45:25Z
The puzzle 1107-eeae8c2b from #1107 has to be resolved:

  
    
      eo/eo-maven-plugin/src/test/java/org/eolang/maven/SnippetTest.java
    
    
        Lines 69 to 71
      in
      e21f9fc
    
  
  
    

        
          
            * @todo #1107:30m Method `jdkExecutable` is duplicated in eo-runtime. 
        

        
          
            *  Find a way to make it reusable (i.e making it part of 
        

        
          
            *  VerboseProcess) and remove it from MainTest. 
        
    
  


The puzzle was created by rultor on 29-Aug-22.
Estimate: 30 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

Closing comment (2022-09-19T12:18:49Z): @l3r8yJ Indeed, it is duplicate of #1008
Repository: oblador/react-native-vector-icons

Issue #480: Build get error with com.atlassian.mobile.video
Created: 2017-05-27T10:33:15Z
I have use react-native-vector-icons version "react-native-vector-icons": "^4.0.1",
But when i build the project on Android get error:
A problem occurred configuring project ':app'.
> Could not resolve all dependencies for configuration ':app:_debugApk'.
   > A problem occurred configuring project ':react-native-vector-icons'.
      > Could not resolve all dependencies for configuration ':react-native-vector-icons:_debugPublishCopy'.
         > Could not find com.atlassian.mobile.video:okhttp-ws-compat:3.7.0-atlassian1.
           Required by:
               followme:react-native-vector-icons:unspecified > com.facebook.react:react-native:0.42.3-atlassian-1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug
option to get more log output.

My project information:
"dependencies": {
    "native-base": "^2.0.12",
    "react": "15.4.2",
    "react-native": "0.42.0",
    "react-native-animatable": "^1.1.1",
    "react-native-calendar": "^0.10.0",
    "react-native-datepicker": "^1.4.7",
    "react-native-fbsdk": "^0.5.0",
    "react-native-fetch-blob": "^0.10.5",
    "react-native-google-places": "^2.0.9",
    "react-native-image-picker": "^0.26.2",
    "react-native-loading-spinner-overlay": "^0.4.2",
    "react-native-localization": "^0.1.29",
    "react-native-maps": "^0.12.4",
    "react-native-md5": "^1.0.0",
    "react-native-popup-dialog": "^0.7.22",
    "react-native-router-flux": "^3.38.1",
    "react-native-simple-modal": "^5.0.0",
    "react-native-sortable-listview": "^0.2.2",
    "react-native-vector-icons": "^4.0.1",
    "realm": "^1.1.1"
  },

I clean build and rebuild still get this error.
Please check me why?
Thank you.

Duplicate issue #482: Could not find com.atlassian.mobile.video:okhttp-ws-compat:3.7.0-atlassian1.
Created: 2017-05-28T14:55:32Z
Hello,
I have this issue with ignite-cli when I use your package:
* What went wrong:
A problem occurred configuring project ':app'.
> Could not resolve all dependencies for configuration ':app:_debugApk'.
   > A problem occurred configuring project ':react-native-vector-icons'.
      > Could not resolve all dependencies for configuration ':react-native-vector-icons:_debugPublishCopy'.
         > Could not find com.atlassian.mobile.video:okhttp-ws-compat:3.7.0-atlassian1.
           Required by:
               app:react-native-vector-icons:unspecified > com.facebook.react:react-native:0.42.3-atlassian-1

Thanks 😄

Closing comment (2017-05-28T15:12:42Z): My bad, duplicate of #480
Repository: oblador/react-native-vector-icons

Issue #626: Error: While resolving module `react-native-vector-icons/MaterialIcons`, the Haste package `react-native-vector-icons` was found.
Created: 2018-01-12T20:59:01Z
After upgrading my react native project and also my react-native-vector-icons I started receiving this error.
error: bundling failed: Error: While resolving module `react-native-vector-icons/MaterialIcons`, the Haste package `react-native-vector-icons` was found. However the module `MaterialIcons` could not be found within the package. Indeed, none of these files exist:

 * `/Users/user/my-app/node_modules/react-native/local-cli/core/__fixtures__/files/MaterialIcons(.native||.ios.js|.native.js|.js|.ios.json|.native.json|.json)`
  * `/Users/user/my-app/node_modules/react-native/local-cli/core/__fixtures__/files/MaterialIcons/index(.native||.ios.js|.native.js|.js|.ios.json|.native.json|.json)`

The same issue happens with Font Awesome



Module
Version




React-Native
0.52.0


React
16.2.0


React-native-vector-icons
4.5.0

Duplicate issue #639: Error once import react-native-vector-icons with version 0.52.2
Created: 2018-01-31T11:33:54Z
import Icon from 'react-native-vector-icons/FontAwesome';
Error :
The development server returned response error code: 500
URL: http://10.0.3.2:8081/index.delta?platform=android&dev=true&minify=false&deltaBundleId=0
Body:
{"type":"InternalError","errors":[],"message":"Metro Bundler has encountered an internal error, please check your terminal error output for more details"}
processBundleResult
BundleDownloader.java:242
access$100
BundleDownloader.java:41
onResponse
BundleDownloader.java:208
execute
RealCall.java:135
run
NamedRunnable.java:32
runWorker
ThreadPoolExecutor.java:1113
run
ThreadPoolExecutor.java:588
run
Thread.java:818

Closing comment (2018-02-02T13:49:07Z): Dup of #626
it's an RN issue facebook/react-native#17610
Will be fixed by facebook/react-native#17672
Workaround #626 (comment)
Repository: oblador/react-native-vector-icons

Issue #104: Inline icons are not rendered correctly when inside "bold" text
Created: 2016-01-29T15:39:25Z
If I have (fontawsome) icon inline in text with style fontWeight: 'bold' the icon is rendered as "crossed box". Problem is solved by removing font weight property.
Not sure if this can be easily handled by the library or at least documentation should state this limitation.

Duplicate issue #112: FontAwesome with Android and fontWeight: '600'
Created: 2016-02-14T19:39:25Z
I had an icon with fontWeight: '600' which displayed correctly on iOS. However, on the Android app, it shows up as a weirdly skewed box with an X through it. I don't think the fontWeight actually did anything to the font, but it caused a weird bug that took a little bit for me to figure out. Not sure if you want to do anything about it but it might be something you should be aware of.

Closing comment (2016-02-14T19:47:26Z): Dupe of #104. Upgrading should fix this error :-)
Repository: oblador/react-native-vector-icons

Issue #626: Error: While resolving module `react-native-vector-icons/MaterialIcons`, the Haste package `react-native-vector-icons` was found.
Created: 2018-01-12T20:59:01Z
After upgrading my react native project and also my react-native-vector-icons I started receiving this error.
error: bundling failed: Error: While resolving module `react-native-vector-icons/MaterialIcons`, the Haste package `react-native-vector-icons` was found. However the module `MaterialIcons` could not be found within the package. Indeed, none of these files exist:

 * `/Users/user/my-app/node_modules/react-native/local-cli/core/__fixtures__/files/MaterialIcons(.native||.ios.js|.native.js|.js|.ios.json|.native.json|.json)`
  * `/Users/user/my-app/node_modules/react-native/local-cli/core/__fixtures__/files/MaterialIcons/index(.native||.ios.js|.native.js|.js|.ios.json|.native.json|.json)`

The same issue happens with Font Awesome



Module
Version




React-Native
0.52.0


React
16.2.0


React-native-vector-icons
4.5.0

Duplicate issue #653: Not working with react native 0.52.2
Created: 2018-02-17T22:27:51Z
Hi,
Using react native 0.52.2 with react 16.2.0 and the latest version of this package I am having the following error:
error: bundling failed: Error: While resolving module `react-native-vector-icons/Feather`, the Haste package `react-native-vector-icons` was found. However the module `Feather` could not be found within the package. Indeed, none of these files exist:

It works with the 0.51.0 but not the the 0.52.2 or 0.53.

Closing comment (2018-02-18T08:05:44Z): Dup of #626.
Please use search before opening an issue. This applies to every repo on the interweb.
Repository: oblador/react-native-vector-icons

Issue #553: Importing only custom icons library
Created: 2017-09-19T13:52:32Z
I'd created a font library with fontello and imported it to my React Native project with react-native link. But when I do this, all the vector icons libraries are imported too and I don't use it. How can I import only my custom font?

Duplicate issue #565: How to use only FontAwesome
Created: 2017-10-08T06:09:51Z
I get Extra 1 mb due to other fonts such as material Icons Etc, How to I just use only FontAwesome Icons

Closing comment (2017-10-08T09:48:10Z): Duplicate of #553 et al.
Repository: oblador/react-native-vector-icons

Issue #380: Include path on iOS
Created: 2017-01-07T22:14:14Z
I had to remove the React/ prefix for all RCT*.h includes on iOS. The iOS Xcode project includes React/ and enables recursive search. Some of the headers are located in React/Base so React/RCTxxx.h won't work.

Duplicate issue #385: 'React/RCTBridgeModule.h' file not found
Created: 2017-01-19T23:16:37Z
I am receiving a 'React/RCTBridgeModule.h' file not found error after installing.  I have tried installing manually and using react-native link.  I am on react native version 0.39.1 using react-native-vector-icons version 4.0.0.  The issue was observed on iOS.  I have not tested android.

Closing comment (2017-01-20T09:36:48Z): Duplicate of #380
Repository: oblador/react-native-vector-icons

Issue #626: Error: While resolving module `react-native-vector-icons/MaterialIcons`, the Haste package `react-native-vector-icons` was found.
Created: 2018-01-12T20:59:01Z
After upgrading my react native project and also my react-native-vector-icons I started receiving this error.
error: bundling failed: Error: While resolving module `react-native-vector-icons/MaterialIcons`, the Haste package `react-native-vector-icons` was found. However the module `MaterialIcons` could not be found within the package. Indeed, none of these files exist:

 * `/Users/user/my-app/node_modules/react-native/local-cli/core/__fixtures__/files/MaterialIcons(.native||.ios.js|.native.js|.js|.ios.json|.native.json|.json)`
  * `/Users/user/my-app/node_modules/react-native/local-cli/core/__fixtures__/files/MaterialIcons/index(.native||.ios.js|.native.js|.js|.ios.json|.native.json|.json)`

The same issue happens with Font Awesome



Module
Version




React-Native
0.52.0


React
16.2.0


React-native-vector-icons
4.5.0

Duplicate issue #652: Custom Fontello font causes 500
Created: 2018-02-16T11:37:55Z
Hi
I am trying to load a custom font using fontello but whenever I try using createIconSetFromFontello I get a 500 bundler error with no explanation on android (have not tried iOS yet).
Here is the code I am using:
import fontelloConfig from '../utils/icons/custom.json';
import { createIconSetFromFontello } from 'react-native-vector-icons';
const Icon = createIconSetFromFontello(fontelloConfig);

When I just pull in the config and do a console.log it looks fine, It is just when I use the createIconSetFromFontello function.
The font file is present in the android fonts folder and also in my assets/fonts folder.
This is baffling me... anyone have any ideas?

Closing comment (2018-02-20T12:49:57Z): Probably dup of #626.
Repository: oblador/react-native-vector-icons

Issue #626: Error: While resolving module `react-native-vector-icons/MaterialIcons`, the Haste package `react-native-vector-icons` was found.
Created: 2018-01-12T20:59:01Z
After upgrading my react native project and also my react-native-vector-icons I started receiving this error.
error: bundling failed: Error: While resolving module `react-native-vector-icons/MaterialIcons`, the Haste package `react-native-vector-icons` was found. However the module `MaterialIcons` could not be found within the package. Indeed, none of these files exist:

 * `/Users/user/my-app/node_modules/react-native/local-cli/core/__fixtures__/files/MaterialIcons(.native||.ios.js|.native.js|.js|.ios.json|.native.json|.json)`
  * `/Users/user/my-app/node_modules/react-native/local-cli/core/__fixtures__/files/MaterialIcons/index(.native||.ios.js|.native.js|.js|.ios.json|.native.json|.json)`

The same issue happens with Font Awesome



Module
Version




React-Native
0.52.0


React
16.2.0


React-native-vector-icons
4.5.0

Duplicate issue #412: [Android Device] Unknown named module: 'react-native-vector-icons/Ionicons'
Created: 2017-02-23T02:08:04Z
Hi,
I am getting this error on my android device:
Unknown named module: 'react-native-vector-icons/Ionicons'
The simulator works fine, iOS works fine on both simulator and device. I can't figure this out.
I have tried deleting node modules and cleaning the cache with npm cache clean and rm -fr $TMPDIR/react-*. I have tried replacing Ionicons in my fonts folder, I have restarted the packager, I have uninstalled and reinstalled react-native-vector-icons. Nothing seems to work.
I am currently on version 0.41.2, and upgrading did not help.
Any ideas?

Closing comment (2018-02-26T17:48:19Z): Looks like a dup of #626
Repository: oblador/react-native-vector-icons

Issue #1053: Plans to integrate Font Awesome Duotone
Created: 2019-07-30T20:06:35Z
Font awesome just released duotone icons today. Are there plans to integrate it on React-Native-Vector icons.

Duplicate issue #1100: Font Awesome 5 Duotone icons 
Created: 2019-11-20T20:36:29Z
FA5 now has a whole new duotone style/set (Along with light, regular and solid). It would be amazing to have this included in react-native-vector-icons.
The new version is 5.11.2
Cheers.

Closing comment (2020-01-08T04:14:49Z): Duplicate of #1053
Repository: oblador/react-native-vector-icons

Issue #230: Unrecognized font
Created: 2016-06-10T16:46:10Z
So We have seen this issue time and time again and the docs are very explicit on how to get it to work, how ever my question for you is: is this an error with React native or you? because at this point I have followed all your instructions to a T, which you can see in this issue I raised with React Native, 8051.
Its pretty straight forward, if I run the application with the run button the fonts are added and life is grand. if I use their command to run the application: react-native run-ios then the fonts are missing and all hell breaks loose.
Can any one confirm or deny that this isn't me?

Duplicate issue #241: Unrecognized font family 'lonicons',How to solve ?
Created: 2016-07-07T01:20:24Z
my react native version is 0.29.0 ,  react  version  is 15.2.0

Closing comment (2016-07-10T22:03:35Z): Dupe of #230
Repository: ocaml/merlin

Issue #140: Enhancement to type alias expansion
Created: 2013-11-22T22:21:33Z
Take a look at the type of [Core_extended.Std.Shell.sh_test].
The first C-c C-t shows:
('a, bool) sh_cmd with_test_flags
The second time it shows:
?true_v:int list -> ?false_v:int list -> ('a, bool) sh_cmd with_process_flags
Subsequently the type aliases [('a, bool) sh_cmd with_process_flags] are no longer expanded out. I wish there was a way to get merlin to expand these out as well. Can we have C-c C-t recursively expand one set of type aliases in some sort of a controlled fashion?

Duplicate issue #191: Better type alias expansion
Created: 2014-03-14T11:40:18Z
Take a look at the type of Core_extended.Shell.run_one. We see something like:
Shell.run_one: ?eol:char -> string option Shell.cmd Shell.with_run_flags

Asking for the type of this again does not expand the type aliases on the RHS of ->. It would be helpful if it did.

Closing comment (2014-03-14T12:04:30Z): Duplicate of #140 .
Repository: ocaml/merlin

Issue #220: emacs settings should be dummy proof
Created: 2014-07-01T10:57:16Z
Propose a nice default by default and give the experimented users a way to disable them (see https://github.com/OCamlPro/ocp-index/blob/master/tools/ocp-index.el#L164)

Duplicate issue #319: meta-issue about judiciously suggesting incorrect completions
Created: 2014-11-27T11:04:39Z
In #282 @dbuenzli rightly insists on the importance of code-completion working under the assumption that our knowledge of the environment may be wrong (because of previous programming errors). It would be nice to centralize the discussion (which has been sprawling over several issues) in a single place to make it easier to go back to the arguments in the future.
I think there are important questions to be discussed among, for example:

how do we understand the act of programming and its reliance on completion?
what is a good design for handling incorrect assumptions? Should we enrich the type-context-computation of Merlin to be fuzzier (eg. assume recursivity of the current definition), or have a separate heuristic for "dummier" completion candidates, and combine them somehow?
should we aim to be merely distracted, or rather dummy, or just plain stupid? Is it important to understand finely what the programmer errors may be, or is just any non-context-dependent completion strategy the right fallback? (This probably depends on how suggestions are combined -- point (2))

Closing comment (2014-11-28T09:11:42Z): And I don't think it is our job to decide for the user what kind of completion he wants. We provide one such "source", a "semantic" one, if you want a more "fuzzy" one on the side feel free to enable it, but I don't think we should be the ones to enable it (or disable it).

To rephrase @dbuenzli reply, most users assume that the emacs and vim bindings are also part of merlin, and as such, they should have sensible default: this is related to #220.
Repository: ocaml/merlin

Issue #633: MerlinTypeOf fails on some expressions after `let%lwt`
Created: 2017-04-09T21:41:48Z
In this example:
let _ =
  let%lwt a = Lwt.return 5 in
  let b = 6 in
  Lwt.return_unit
MerlinTypeOf fails on b and 6 (and in general, normal let bindings after let%lwt).

Duplicate issue #660: Types displayed when using ppx.lwt are incorrect
Created: 2017-06-13T02:33:47Z
let test_lwt () =
    let%lwt _value = Lwt.return_none in
    let val2 = 3 in
    Lwt.return val2
If I ask for the type of val2, merlin tells me it's _a option Lwt.t and highlights the whole code except the first line.
Merlin 2.5.4 in emacs.

Closing comment (2017-06-13T08:49:18Z): Maybe related to #633 / ocsigen/lwt#337
Repository: ocaml/merlin

Issue #1637: Refine cache for typing the buffer
Created: 2023-06-26T12:36:56Z
The buffer cache splits the parsetree into "last typing result can be re-used" and "needs to be typed". That splitting is currently only done on the level of top-level structure/signature items. Let's refine it on two levels:

 module (type) definitions/declarations
 function definitions

Duplicate issue #1694: Improve the granularity of the typer cache to maximise reuse.
Created: 2023-10-23T14:32:15Z
This is a performance improvement that improve merlin response time.
Draft, to be filled with more detail

Closing comment (2023-10-24T07:20:20Z): Duplicate of #1637
Repository: ocaml/merlin

Issue #1226: Type enclosing confuses module names and type constructors
Created: 2020-12-18T15:13:50Z
Given the program:
module Foo = struct
  let bar = 42
end

type t = Foo of int

let a = Foo 3
Asking the type for Foo in Foo 3 merlin will answer sig val bar : int end instead of t.

Duplicate issue #1125: Badly resolved ambiguity when a GADT constructor's name match the one of a module. Since OCaml 4.08
Created: 2020-04-08T15:15:03Z
Given the following code:
type _ term =
  | Int : int -> int term
end
When asked the type of  Int Merlin wrongly answers (module Stdlib__int) since OCaml versions >= 4.08.

Closing comment (2021-01-06T15:13:55Z): Duplicate of #1226.
Repository: ocaml/merlin

Issue #425: String STring macosx
Created: 2015-08-21T14:20:38Z
file system. @def-lkb knows what I mean.

Duplicate issue #453: source files have the same name -- but one of them does not exist
Created: 2015-10-18T18:02:45Z
i am getting this error when using locate on CCHashtbl from containers:
 Several source files in your path have the same name: 

and then the path is exactly the same, in my opam install location, but the two file names are CCHashtbl.mli and cCHashtbl.mli. the second one does not exist at that location.

Closing comment (2015-10-19T10:19:35Z): Related to #425
Repository: ocaml/merlin

Issue #624: merlin-locate misses by 1 character
Created: 2017-03-03T16:08:00Z
In example below, in emacs, if I place point on "W" after the colon and invoke merlin-locate then it fails with message "Not a valid identifier".
It successfully locates the module if I place point on the adjacent "x" or even on a "." adjacent to that.
module Wx = struct type t end

module type Q = sig
  val f : x:Wx.t -> unit
end

Duplicate issue #652: 'merlin-locate' - "Not a valid identifier" message
Created: 2017-05-17T12:53:33Z
Merlin-master, OCaml 4.03.0 (4.04.1 | 4.05.0)+flambda , Spacemacs
With the following examples, a 'merlin-locate' pointing on the 2nd 'x'
prints the message "Not a valid identifier" :
fun x -> [x] ;;
fun x -> {x} ;;
fun x -> [|x|] ;;
fun x -> {|x|} ;;
fun x -> {<x>} ;;
fun x -> ~x ;;

(*Also: *)
fun a x -> (a,x) ;;
Examples without problem :
fun x -> [ x] ;; (* OK : Use C-c & to go back. *)
fun x -> { x} ;;
fun x -> [| x|] ;;
fun a x -> (a, x) ;;

(* Also OK : *)
fun x -> (x) ;;

Closing comment (2018-03-22T16:53:05Z): Closing as this is indeed a duplicate of #624 .
No one has had time to look at this yet, sorry for the annoyance.
Feel free to ping #624 again in a few weeks if it hasn't been resolved by then.
Repository: ocaml/merlin

Issue #425: String STring macosx
Created: 2015-08-21T14:20:38Z
file system. @def-lkb knows what I mean.

Duplicate issue #567: Go-to-definition on Mac OS & Emacs
Created: 2016-09-01T10:15:53Z
Going to definition opens a buffer with wrong capitalized name on mac os x.
Typically, when looking for module A, Merlin on emacs opens A.ml buffer from file a.ml, and modifications now go to file A.ml and overwrites a.ml...

Closing comment (2016-09-01T10:24:39Z): Must be related to #425