Strange behavior with hanging (empty) promises

Hello. I was expecting code below to hang forever on test2 promise because it never resolves or rejects but the program ends in the middle of the generator code. Can you please explain why and what should I do to hang it?
$ node --version
v5.3.0
$ node co-test.js
123

var co, test1, test2;

co = require('co');

test1 = function() {
  return new Promise(function(resolve, reject) {
    var err, error;
    try {
      return setTimeout(function() {
        resolve("123");
      }, 2000);
    } catch (error) {
      err = error;
      console.dir(err);
      reject(err);
    }
  });
};

test2 = function() {
  return new Promise(function(resolve, reject) {});
};

co(function*() {
  console.log((yield test1()));
  console.log((yield test2()));
  console.log("all went ok")
  return;
})["catch"](function(err) {
  console.dir(err);
});

UPD: Code update. It not prints "all went ok" also.

Thats an interesting one :)
Its actually a node feature and corner case.
node ends its process, because there is nothing to to anymore. All loops are done, all files and timers are closed, the main event loop is empty. Node shuts down, when there are no more events to process and the current routine is done.

Exactly. Node ends the process as soon as there is nothing more to execute in the event loop. In this case, the promise never resolves, but the function exits and, since it never resolves/reject and it never waits for anything (i.e. timer, callback, etc.) then the event loops exits, and the program is terminated.
You can test this by having a setTimeout that calls a function, inside your empty promise, but still don't resolve/reject it. Your test2 will wait for that timeout, then the program will exit.

The promise never resolves cause generator.next() never execute after prints '123', so it not prints "all went ok".

that's a very dangerous case ,it will cause memory leak ,because if there there are some actions is waiting for this, the resource hold by these actions will never be released.
consider code below:

const co = require('co');

const test1 = function() {
  return new Promise(function(resolve, reject) {
    var err, error;
    try {
      return setTimeout(function() {
        resolve("123");
      }, 2000);
    } catch (error) {
      err = error;
      console.dir(err);
      reject(err);
    }
  });
};

const test2 = function() {
  return new Promise(function(resolve, reject) {});
};

const func=function(){
  return co(function*(){
      let some_resource=new Buffer(1000000);
      //.....
     yield test1();
     yiled test2();

    return "done";//will never return ！！！
  })
}
//imagine function "func"  is been used frequently, there will be memory leak

you should do it more safely,and it's not the duty of co or Promise。 this is my solution:

const  TimeOutPromise=function(ms,func){
    let obj={};
    obj.pro=new Promise(function(resolve,reject){
        obj.reject=reject;
        func(resolve,reject);
    });
    setTimeout(obj.reject,ms,(new Error("timeout")));
    return obj.pro;
}

//and rewrite test2
const test2=function(){
   return TimeoutPromise(1000,function(resolve,reject){});
}

@yyrdl
I don't think its dangerous. Your memory is released when the last reference to it dies, so an unused/unresolved Promise can't keep memory blocked. (Beside that I don't understand your solution. Not having some_resource changes the semantics of your solution...)

@freiit  try the code below :
const co=require("co");

const test1 = function() {
    return new Promise(function(resolve, reject) {
        var err, error;
        try {
            return setTimeout(function() {
                resolve("123");
            }, 2000);
        } catch (error) {
            err = error;
            reject(err);
        }
    });
};

const test2 = function() {
    return new Promise(function(resolve, reject) {});
};

const func=function(){
    return co(function*(){
        let some_resource=new Buffer(1000000);//represent the resource
        //.....
        yield test1();
        yield test2();// will block here

        return "done";//will never return ！！！so the 'some_resource' will never be GC
    })
}

const invoke=function () {
    func().then(function(){
        console.log("done");
    })
}
//simulate invoking the 'func' somewhere in your project
const run=function () {
    invoke();
    setTimeout(function () {
        run();
    },1);
}

var memory=process.memoryUsage().rss;

setInterval(function () {
    console.log(process.memoryUsage().rss-memory);
},1000)

@freiit   I am wrong.I misunderstand the question,  the question is why it didn't hang forever .

@yyrdl
A memory leak is defined as reserved memory that can be reached. You created an array in the global name space that keeps a lot of Buffers. Of course they consume memory, but no memory leaked, as it is still reachable through the global variable keep. That is not "hidden trouble", that is obvious trouble.
Beside that, yes, this is off topic. I'm out.


Update built-in handlers to not be sensitive to media support setup

The use of media operators (readers and writers) is sensitive to their registration order.
Our built-in services such as static content support, metrics or health-checks should not depend on the users setup of the media support.
We need to track all the built-in handlers and update them to not be sensitive to the media support ordering setup by the user:

[ ] static content
[x] metrics
[x] health checks
[ ] others?

We should also come-up with the proper way of doing this.
E.g. for a handler that needs to writer a Path to a response:
response.send(response
    .writerContext()
    .marshall(Single.just(path), PathBodyWriter.class, GenericType.create(Path.class), null));

The above (what we have in 2.0.0-M2) is rather ugly, we should update it something like this:
response.send((ctx) -> ctx.marshall(Single.just(path), PathBodyWriter.class, GenericType.create(Path.class)));

This approach is not order dependent but still relies on the PathBodyWriter to be registered in the media support. This is registered by default when the media support is not provided explicitly to the webserver.
However one can setup the media support without the default operators and pass it to the webserver, in this case the code above would not work:
WebServer.builder(Routing.builder().register(StaticContentSupport.create("/WEB")))
    .mediaSupport(MediaSupport.builder().build())
    .build();

We need to decide if this is acceptable or if our built-in handlers should be completely standalone WRT to media support.
Instead of using the underlying operator context to select the operator by class name, we can produce the Publisher manually.
E.g. for the same handle that needs to send a Path to a response:
FileChannel fc = FileChannel.open(path, StandardOpenOption.READ);
response.send(new ReadableByteChannelPublisher(fc, RetrySchema.linear(0, 10, 250)));

One of the drawback of not using an operator is that the underlying publisher implementation needs to be public like ReadableByteChannelPublisher above, and that the headers related work performed by the operator has to be done by hand.
One can also use the operator manually:
PathBodyWriter writer = PathBodyWriter.create(); // can be static
response.send(writer.write(Single.just(path), GenericType.create(path), response.writerContext()));

This approach seems best as it does not rely on the MediaSupport setup and prevent code duplication and also let the operator do the header work if needed.

@Verdent @ljnelson @tomas-langer You guys might be familiar with this issue, let me know if you have comments / thoughts about this.

Fixed in HealthSupport by #1884
Fixed in MetricsSupport by #1899

Fixed in static content by #1922

@romain-grecourt is there any other are we should fix this in, or can we close this issue once the last PR is merged?

Some of the changes you've made are a little problematic, it by-passes the internal filter that provides tracing. Ideally we would implement #1906 to do this properly.
It's not a big change (and not incompatible) so we may want to target that for RC2.


pip install error on Ubuntu due to pyOpenSSL breaking change

I just tried a vanilla sudo pip install mitmproxy from Ubuntu 14.10 and it failed to run with the following error.
sudo mitmproxy --version
Traceback (most recent call last):
  File "/usr/local/bin/mitmproxy", line 2, in <module>
    from libmproxy.main import mitmproxy
  File "/usr/local/lib/python2.7/dist-packages/libmproxy/main.py", line 6, in <module>
    from . import version, cmdline
  File "/usr/local/lib/python2.7/dist-packages/libmproxy/cmdline.py", line 6, in <module>
    from . import filt, utils, version
  File "/usr/local/lib/python2.7/dist-packages/libmproxy/filt.py", line 37, in <module>
    from .protocol.http import decoded
  File "/usr/local/lib/python2.7/dist-packages/libmproxy/protocol/__init__.py", line 1, in <module>
    from .primitives import *
  File "/usr/local/lib/python2.7/dist-packages/libmproxy/protocol/primitives.py", line 4, in <module>
    import netlib.tcp
  File "/usr/local/lib/python2.7/dist-packages/netlib/tcp.py", line 8, in <module>
    from OpenSSL import SSL
  File "/usr/local/lib/python2.7/dist-packages/OpenSSL/__init__.py", line 8, in <module>
    from OpenSSL import rand, crypto, SSL
  File "/usr/local/lib/python2.7/dist-packages/OpenSSL/rand.py", line 11, in <module>
    from OpenSSL._util import (
  File "/usr/local/lib/python2.7/dist-packages/OpenSSL/_util.py", line 6, in <module>
    from cryptography.hazmat.bindings.openssl.binding import Binding
ImportError: No module named cryptography.hazmat.bindings.openssl.binding

I resolved this by reverting pyOpenSSL to 0.14. The pip install process had installed pyOpenSSL-0.15.1-py2.py3-none-any.whl
sudo pip install pyOpenSSL==0.14

This was for mitmproxy 0.11.3
Thanks for the very useful software.

Thanks for the report. Looks like there finally a new pyOpenSSL release, we
should adjust ASAP.
(cc @cortesi)
Cheers,
Max
Derek Kozel<EMAIL_ADDRESS>schrieb am Mi., 15. Apr. 2015 17:36:

I just tried a vanilla sudo pip install mitmproxy from Ubuntu 14.10 and it
failed to run with the following error.
sudo mitmproxy --version
Traceback (most recent call last):
File "/usr/local/bin/mitmproxy", line 2, in
from libmproxy.main import mitmproxy
File "/usr/local/lib/python2.7/dist-packages/libmproxy/main.py", line 6, in
from . import version, cmdline
File "/usr/local/lib/python2.7/dist-packages/libmproxy/cmdline.py", line 6, in
from . import filt, utils, version
File "/usr/local/lib/python2.7/dist-packages/libmproxy/filt.py", line 37, in
from .protocol.http import decoded
File "/usr/local/lib/python2.7/dist-packages/libmproxy/protocol/init.py", line 1, in
from .primitives import *
File "/usr/local/lib/python2.7/dist-packages/libmproxy/protocol/primitives.py", line 4, in
import netlib.tcp
File "/usr/local/lib/python2.7/dist-packages/netlib/tcp.py", line 8, in
from OpenSSL import SSL
File "/usr/local/lib/python2.7/dist-packages/OpenSSL/init.py", line 8, in
from OpenSSL import rand, crypto, SSL
File "/usr/local/lib/python2.7/dist-packages/OpenSSL/rand.py", line 11, in
from OpenSSL._util import (
File "/usr/local/lib/python2.7/dist-packages/OpenSSL/_util.py", line 6, in
from cryptography.hazmat.bindings.openssl.binding import Binding
ImportError: No module named cryptography.hazmat.bindings.openssl.binding
I resolved this by reverting pyOpenSSL to 0.14. The pip install process
had installed pyOpenSSL-0.15.1-py2.py3-none-any.whl
sudo pip install pyOpenSSL==0.14
This was for mitmproxy 0.11.3
Thanks for the very useful software.
—
Reply to this email directly or view it on GitHub
https://github.com/mitmproxy/mitmproxy/issues/557.

Having trouble re-producing, this, not sure it is a pyOpenSSL issue.  I have mitmproxy 0.11.4 on an Ubuntu 14.04 machine and it is running fine with the 0.15.1 release of pyOpenSSL.

Thanks @elitest - I was on mobile earlier, looks like you're right here. @dkozel, can you still reproduce the issue somehow? If so, I'd be very interested in the output of pip freeze.
Thanks!
Max

I'll give it a shot tomorrow. This was a completely fresh machine, I had to
install pip just before!
On 15 Apr 2015 23:35, "Maximilian Hils"<EMAIL_ADDRESS>wrote:

Thanks @elitest https://github.com/elitest - I was on mobile earlier,
looks like you're right here. @dkozel https://github.com/dkozel, can
you still reproduce the issue somehow? If so, I'd be very interested in the
output of pip freeze.
Thanks!
Max
--
Reply to this email directly or view it on GitHub
https://github.com/mitmproxy/mitmproxy/issues/557#issuecomment-93588266.

sudo pip install pip-autoremove
sudo pip-autoremove mitmproxy
sudo pip-autoremove pyOpenSSL
sudo pip install mitmproxy

This did not cause the issue to reoccur. I guess close up this issue and I'll reopen if I can persuade it to come up again. I'm having trouble getting mitmproxy to intercept my Android app communications so I'll be playing with different systems all day.
Thanks again.

dkozel  thanks


CMD ERROR: Unpatched function in C:/projects/kyty/source/emulator/src/Loader/RuntimeLinker.cpp:514

Why is this happening and how can I fix it?

hey, is this gow ragarok? and did u find any way to fix the error?

same error. how I solve?


Add option for different SG generation in Gaussian generator for discriminator training.

See updated CSDPrior with new and improved features.


Using CLUSTER_NAME values containing "-" causes failures to reconcile

When the cluster-name config value contains the hyphen character, load-balancer reconciliation will never happen, do to the code below: (from ELBV2.DescribeLoadBalancers)
if strings.HasPrefix(*loadBalancer.LoadBalancerName, *clusterName+"-") {
  if s := strings.Split(*loadBalancer.LoadBalancerName, "-"); len(s) == 2 {
    if s[0] == *clusterName {
      loadbalancers = append(loadbalancers, loadBalancer)
    }
  }
}

An error should be thrown when - is used, or else it should be converted to something else, like _ before being used in the loadbalancer name.

Fixed in master. thanks!


How can I get a vector in the center of the screen?

Hi @544531645, I'm not sure what you are looking for, can you explain more what you are trying to achieve?

Closing due to inactivity. Please reopen with additional info requested if you are still having problems. Thanks


"type": "module" change

When attempting to use v7 of the library, we ran into an error that stated that import can't be used outside a module.

After digging around a bit, I found this solution to the problem, which states adding "type": "module" to package.json. All other changes in this Draft are to support this change, and make sure everything commits and builds without further problems.
I've yet to test this out locally, but opened the Draft for investigation.

Can someone create a simple repro case?  I think the better way is to set "module": "index.js" vs. the entire output as a module.  I believe that has some un-intended consequences.

Closing due to inactivity


Add symbol legend

Hello,
I've used this app for a while now and I must say is incredibly useful.
Although, I have a hard time understanding sometimes what a specific symbol means.
And apart from me non understanding I think that a new user of the app would appreciate a clearer explanation on what he is seeing.
How the app works is explained clearly,  but often you end up with symbols with a meaning that is not really straightforward and nowhere to look for some kind of documentation, or at least not immediately clear where to look.
Just a little legend in the starting guide section would go a long way helping to understand what is going on with the app.
Thanks!

So, what's specific symbol?

Actually, you can always tap the icon (symbol?) to see it's meanings.

Actually, you can always tap the icon (symbol?) to see it's meanings.

Then it's my fault, I'm sorry.
Although adding a tip somewhere where you mention this wouldn't hurt.
Thank you for your amazing work!!


Go to Ogre v2.2

Since Ogre 2.2 is no longer WIP, it's time to go to v2.2.

[x] Can build & compile with Ogre 2.2
[ ] Preview & replace texture
[ ] Backgrounds
[ ] Obj importer/exporter
[ ] Ogre glTF

I need to adapt Ogre glTF to 2.2 too! 😉

https://github.com/chchwy/ogre-v2-mesh-viewer/tree/ogre-v22

‘I have a problem when trying to open a .mesh file `
20:18:28: OGRE EXCEPTION(4:ItemIdentityException): A material datablock with name '[Hash 0xe9c2f1c4]' already exists. in Hlms::createDatablock at D:/ogre/ogre-next/OgreMain/src/OgreHlms.cpp (line 1753)
20:18:28: OGRE EXCEPTION(4:ItemIdentityException): A material datablock with name '[Hash 0xe9c2f1c4]' already exists. in Hlms::createDatablock at D:/ogre/ogre-next/OgreMain/src/OgreHlms.cpp (line 1753)
20:18:28: Mesh: Loading pet_2021aobai.mesh.
20:18:28: OGRE EXCEPTION(2:InvalidParametersException): Header chunk didn't match either endian: Corrupted stream? in Serializer::determineEndianness at D:/ogre/ogre-next/OgreMain/src/OgreSerializer.cpp (line 91)
20:18:28: Mesh: Loading pet_2021aobai.mesh.
20:18:28: OGRE EXCEPTION(2:InvalidParametersException): Header chunk didn't match either endian: Corrupted stream? in Serializer::determineEndianness at D:/ogre/ogre-next/OgreMain/src/OgreSerializer.cpp (line 91)

``` `

‘I have a problem when trying to open a .mesh file `
20:18:28: OGRE EXCEPTION(4:ItemIdentityException): A material datablock with name '[Hash 0xe9c2f1c4]' already exists. in Hlms::createDatablock at D:/ogre/ogre-next/OgreMain/src/OgreHlms.cpp (line 1753)
20:18:28: OGRE EXCEPTION(4:ItemIdentityException): A material datablock with name '[Hash 0xe9c2f1c4]' already exists. in Hlms::createDatablock at D:/ogre/ogre-next/OgreMain/src/OgreHlms.cpp (line 1753)
20:18:28: Mesh: Loading pet_2021aobai.mesh.
20:18:28: OGRE EXCEPTION(2:InvalidParametersException): Header chunk didn't match either endian: Corrupted stream? in Serializer::determineEndianness at D:/ogre/ogre-next/OgreMain/src/OgreSerializer.cpp (line 91)
20:18:28: Mesh: Loading pet_2021aobai.mesh.
20:18:28: OGRE EXCEPTION(2:InvalidParametersException): Header chunk didn't match either endian: Corrupted stream? in Serializer::determineEndianness at D:/ogre/ogre-next/OgreMain/src/OgreSerializer.cpp (line 91)

``` `

What mesh were you opening? can you give me the mesh so I can have a look?

Sorry for the late,
This is the mesh i have a problem, please help me fix this.
This is the link
https://drive.google.com/file/d/12mDW_8a5hzW_3swaWOuY3cALAMOk6vf8/view?usp=sharing
Vào Th 5, 20 thg 7, 2023 vào lúc 09:29 Matt Chang <
@.***> đã viết:

‘I have a problem when trying to open a .mesh file `
20:18:28: OGRE EXCEPTION(4:ItemIdentityException): A material datablock with name '[Hash 0xe9c2f1c4]' already exists. in Hlms::createDatablock at D:/ogre/ogre-next/OgreMain/src/OgreHlms.cpp (line 1753)
20:18:28: OGRE EXCEPTION(4:ItemIdentityException): A material datablock with name '[Hash 0xe9c2f1c4]' already exists. in Hlms::createDatablock at D:/ogre/ogre-next/OgreMain/src/OgreHlms.cpp (line 1753)
20:18:28: Mesh: Loading pet_2021aobai.mesh.
20:18:28: OGRE EXCEPTION(2:InvalidParametersException): Header chunk didn't match either endian: Corrupted stream? in Serializer::determineEndianness at D:/ogre/ogre-next/OgreMain/src/OgreSerializer.cpp (line 91)
20:18:28: Mesh: Loading pet_2021aobai.mesh.
20:18:28: OGRE EXCEPTION(2:InvalidParametersException): Header chunk didn't match either endian: Corrupted stream? in Serializer::determineEndianness at D:/ogre/ogre-next/OgreMain/src/OgreSerializer.cpp (line 91)
``` `
What mesh were you opening? can you give me the mesh so I can have a look?
—
Reply to this email directly, view it on GitHub
https://github.com/chchwy/ogre-v2-mesh-viewer/issues/1#issuecomment-1643013290,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A34DKZJZYT5PTZSTNQVZG33XRCJZLANCNFSM4JAJKC4Q
.
You are receiving this because you commented.Message ID:
@.***>


create separate metric for last polled block

#86  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @iuwqyir and the rest of your teammates on  Graphite


Support custom max value for bar charts

Is your feature request related to a problem? Please describe.
I would like to print out multiple bar charts aligned to a common max value. With the current version every bar chart uses the full width for its highest value. Compared to other bar chart this might give a wrong visual impression.
Describe the solution you'd like
It would be nice to have the possibility to pass a max value to the bar chart, which will be used to draw the individual bars. E.g. if I define 10 as max value and the highest value of a bar is 5, the bar for 5 would only use 50% of available width for the bar.
Describe alternatives you've considered
None
Additional context
Example how it looks with the current version (Note the values (2, 7 & 8) for the warning bar):

@pascalberger Sounds like a good idea! Would you like to take a stab at this?


Events card styling

Iskcon events card styling is not good. I want to improve this.
Please assign me this issue under gssoc'23.

assigning u


Add applications support

Fix #764
Admin applications weren't supported yet so I added this feature.
One can test these new functionnalities with a specific example and a docker image.

Thanks to you!


Upgrade tabzilla

@johngian r?

Please squash this to a single commit.

Tested it locally and tabzilla gets rendered as expected in both desktop/mobile view. Also code lgtm.
r+wc


[tools] Restore cmd to take version

Allow a version param to be passed to ol restore so that epoch-archive bundles with blocks other than epoch boundary can be restored from.

When I restore -e 169 -v 37334543 it works, but when I run full node:
2022-04-26T19:20:38.570493Z [main] WARN storage/diemdb/src/lib.rs:1053 DiemDB API returned error. {"api_name":"get_account_state_with_proof_by_version","error":"Missing state root node at version 37334543, probably pruned."}
2022-04-26T19:20:38.593678Z [main] ERROR common/crash-handler/src/lib.rs:38 details = '''panicked at '[diem-node] failed to get Diem root address account state: Missing state root node at version 37334543, probably pruned.', diem-node/src/lib.rs:181:10'''
backtrace = '''

When I run only epoch: restore -e 169
2022-04-26T19:22:58.865832Z [main] ERROR storage/backup/backup-cli/src/utils/error_notes.rs:14 Error raised, see notes. {"error":"No such file or directory (os error 2)","notes":""/home/abed/.0L/restore/169/transaction_37255419-.3c33/37255419-.chunk""}
2022-04-26T19:22:58.865890Z [main] INFO storage/backup/backup-cli/src/backup_types/transaction/restore.rs:315 transaction restore started. Manifest: /home/abed/.0L/restore/169/37334543/transaction_37255419-.3c33/transaction.manifest
2022-04-26T19:22:58.866512Z [main] ERROR storage/backup/backup-cli/src/bin/db-restore.rs:60 main_impl() failed: transaction restore failed: Preheat failed: No such file or directory (os error 2)
Error: transaction restore failed: Preheat failed: No such file or directory (os error 2)


Add python3-qt5-bindings rule for RHEL

python3-qt5-devel is part of EPEL: https://apps.fedoraproject.org/packages/python3-qt5-devel
sip-devel is part of Base:
$ yum list available sip-devel --showduplicates -q
Available Packages
sip-devel.x86_64                       4.14.6-4.el7                        base

Actually, hold off on this. The sip executable isn't working right.

This is now the correct rule, but there is a packaging bug stemming from the non-standard sip executable that needs to be addressed before this can be used: https://bugzilla.redhat.com/1742219
The python_qt_binding package also needs to be updated to account for the non-standard sip executable.

@cottsay should we merge this as is and wait for the upstream bug before using it then?

The rule is correct as-is - this is the package that satisfies the dependency. I think it can be merged, and I'll continue to track the bug upstream and keep the affected packages out of the CentOS nightlies until it is resolved.
tl;dr - I think it can be merged whenever.


Added missing default_numbers_to_display() in NumberLine Class

Overview: What does this pull request change?

I added a default_numbers_to_display function in the NumberLine class.

Motivation and Explanation: Why and how do your changes improve the library?

To fix issue #2473 - default_numbers_to_display is currently being called by get_number_mobjects in NumberLine without being defined.
Links to added or changed documentation pages

Further Information and Comments

Reviewer Checklist

[ ] The PR title is descriptive enough for the changelog, and the PR is labeled correctly
[ ] If applicable: newly added non-private functions and classes have a docstring including a short summary and a PARAMETERS section
[ ] If applicable: newly added functions and classes are tested

Hello, thanks for your interest in contributing to Manim :)
When I try to test out the code, I get an error about op not existing, and fixing that I get an attribute error about there being no attribute tick_frequency on NumberLine.
For clarity, here's the test scene I used (straight from the issue mentioned)
class NumberlineNumberMobjects(Scene):
    def construct(self):
        line = NumberLine(include_numbers=True)
        numbers = line.get_number_mobjects()
        self.add(line)

I'll mark this PR as a draft until it's ready :)
Feel free to open it when you feel like it's working again.


Double registering error.

Players can try registering twice and this causes an error.

fixed https://github.com/AbooMinister25/Curse-of-the-Mites/commit/0cbf71efa02c0d6f4fbc79d6e0411f8017c561f9

im an idiot. this is still an issue


Optimize sparse matrix construction, add option to select column based on their diagonal elements.

The new way of building matrices is slightly slower for small matrices, but uses much less memory for large ones. The cutoff argument can now be passed to BasisSetRep, Matrix, and sparse to skip constructing columns with high-energy diagonal elements. This should not have a noticeable effect on performance when not used.
Increased the default size limits for building sparse matrices to 1e6 added a default estimates for the amount of storage needed when constructing the matrix.
momentum can now be called on an address to get its total momentum. Optional fold argument folds the momentum into the Brillouin zone

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

68 of 68 (100.0%)  changed or added relevant lines in 2 files are covered.
12 unchanged lines in 4 files lost coverage.
Overall coverage increased (+0.09%) to 90.386%

Files with Coverage Reduction
New Missed Lines
%

src/Interfaces/stochasticstyles.jl
1
95.24%

src/Hamiltonians/HubbardReal1DEP.jl
2
92.59%

src/RimuIO.jl
2
77.78%

src/Hamiltonians/correlation_functions.jl
7
87.01%

Totals

Change from base Build<PHONE_NUMBER>:
0.09%

Covered Lines:
4024

Relevant Lines:
4452

💛  - Coveralls


ARG-MINER website

Hello
i can't access ARG-MINER web site (https://bench.cs.vt.edu/argminer) as before.
was ARG-MINNER removed or transferred to another link

Hello. Thanks for your interest in this work. We have not changed the name of the repo or the links to it. The public link of the project is https://argrecsys.github.io/arg-miner/ and the link of the repo is https://github.com/argrecsys/arg-miner
Kind regards

I will close this issue.


check the error under 05 section

Your code is wrong.

yeal，I see
发自我的iPhone
------------------ Original ------------------
From: aQua<EMAIL_ADDRESS>Date: Mon,Oct 7,2019 7:18 PM
To: aQuaYi/LeetCode-in-Go<EMAIL_ADDRESS>Cc: Jingke<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [aQuaYi/LeetCode-in-Go] check the error under 05 section (#50)
Your code is wrong.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Feature/cldn 1282

SUMMARY

This is the PR for the associated CLDN-1282 task
Changes include adding a new endpoint to the back-end that serves as a proxy to Alfred, as well as the modification of the Application Links viz to work with this new endpoint. The control panel of the Application Links viz was also modified so that the chart will display properly regardless of the dataset that it is made on.
It is not seen in this PR, but I also had to edit the extra-ca-certs Kubernetes secret on the PB-stg cluster by adding in a .pem file from the Alfred website.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

N/A
TESTING INSTRUCTIONS

N/A
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[X] Introduces new feature or API
[ ] Removes existing feature or API

Closing this PR as I will open another one on the cccs-1.5 branch

Closing this PR as I will open another one on the cccs-1.5 branch


PageList filterByPublicDate option to filter pages

The filterByPublicDate function already exists. But you can't set it in the block settings.
Option: filterByPublicDate
Values: Now, Now +/- x days, specific date
Comparison: >=, <=, =, between (start and end date)

This isn't something that we're going to worry about, but we'd be happy to accept a well-formed pull request for it.

This can be closed.


Navigation issue when Back button pressed

Hi,
First of all, thank you to the Framework7 team for creating such a awesome mobile app framework.
I am switching my android app to Framework7 using Template7. I am facing issues with the Navigation. When I am navigating deep (2 or more) and again going back to page, the page is refreshing and the compiled templates not displaying. For example
News page->Detail page->Back to News page (working fine)
But---
News page->Detail Pages->More Detail Page->Back to Detail Page->Back to News Page (Not displaying the template rendering)
Please help..

I got it worked by adding domCache:true

Congratulations on being the 1000th issue.
Would i be right in thinking this issue can be closed?


Styling improvements

This pull request will conflict with https://github.com/thehyve/heim-SmartR/pull/176
Also I'm not sure why you removed the color setting. I like the idea of having a visual input in form of a green color to see whether the inputs are sane. Feedback in form of text is a good idea, though.

@kretep could you help rebase?

I'll close this one, because the new pull request will be significantly different from this one.


the page presents your name, a photo, links to sections about you, your work, and how to contact you

When the page is loaded the page presents your name, a recent photo or avatar, and links to sections about you, your work, and how to contact you

I have not added a profile image as it is not necessary ant this point


Implement resolving a topic

This issue describes a specific implementation for #11154. See also CZO discussion thread.
We should implement marking a topic as resolved by making it easy to prepend a "check mark button" emoji (✅) to the topic name.
Note that this feature makes it much more urgent to resolve #15290.
Three-dot topic menu in left sidebar:
[for users with permissions to edit topic name only]

If topic name does not start with a ✅, show "Mark topic as resolved" below the "Move topic" menu option, using a checkmark as the icon. Selecting this option:

Renames the topic by prepending a ✅.
Sends a Notification Bot message to the new (resolved) topic that says: "This topic was marked as resolved by [user]."
Does not send a message to the old (unresolved) topic, since we want it to disappear from the list.

If topic name starts with a ✅, show "Mark topic as unresolved" below the "Move topic" menu option, using a checkmark as the icon. Selecting this option:

Renames the topic by removing all initial ✅.
Sends a Notification Bot message to the new (unresolved) topic that says: "This topic was marked as unresolved by [user]."
Does not send a message to the old (resolved) topic, since we want it to disappear from the list.

Compose box:
When user starts composing a message to a topic whose name starts with  ✅, show a warning banner in the style of the banner shown when @-mentioning a user who is not a member of the stream.

Text: You are composing a message to a resolved topic.
For users with permissions, also show an "Unresolve topic" button on the right side of the banner.

I have one amendment to help with prototyping this, which is that we should use the existing Notification Bot messages for the first version of this.  The rest of this proposal doesn't require any changes to the API, since we can just call https://zulip.com/api/update-message with the right parameters (e.g. change_all), and if we can implement that and test-deploy it on chat.zulip.org, that'll let us confirm our intuition that this is an approach that will work well.
I think the rest of this should be just adding the UI as described above, since the existing fancy logic for rerendering the UI after a topic is edited should happen automatically.

Following #18808, we've implemented everything here except for the compose box notice.
Folks should feel free to claim that remaining work.  I intend to also open an issue for search in "resolve topic".

@Signior-X would you be up for implementing the compose_error work, which I think is all that remains here?  I figure you're the best person to do it since you'll want to serialize it with splitting compose.js in some reasonable way :).

I really like this feature, it's really useful for Q&A-style streams :)
It might be nice to have an option to disable this on a per-stream basis with an org-wide default. It doesn't make sense in all streams and may even cause needless confusion in some cases (happy to link to/show an example via DM if you want).

Yeah, I expect we'll want to add something like that probably in the form of a "Who can resolve topics" setting, with one option being nobody, since I expect there will also be demand for limiting who has access to do it.

Please rename the issue to reflect what this is actually about now :)

Thanks for flagging @xeruf ! I moved the remaining part to a new issue (#20584).


Instead of clearing the search on tab change, update the search across the tab

I think there was some reason behind why the search string is cleared by brackets on every tab switch  #5856 #7388. I have marked this to review to be sure before going ahead with this.

Closing as the decision to clear the search string on tab switch was an XD choice.


Does not transmit sound.

Hi, I have a problem, my bot does not transmit sound.
I'm sleepy, maybe I'm dulling a little.

Code - https://hastebin.com/ikafisaziq.cs

That code definitely looks like it should work... I've been having some really bizzare issues with the voice API recently as well so I have a few questions:

What version of Discore are you using?
Have you tried changing the server's voice region? (I'm not saying this is a legit fix, but certain voice regions had this issue for me)
Did this code previously work?

If you're having the same issue I am, it seems to be related to the version of the voice API Discore uses as well as certain voice servers. If you are using 3.x, I would give the bug/voice-fixes branch a try. It contains work in progress support for the latest version of the Discord voice API.
Another weird side-effect I've noticed is that when voice data is currently being sent (but no audio is actually going across), all users in the server can't hear each other...

1 -

2 - voice region - In terms of the location of the server?
3 - I do not know, I use your library for the first time, I wrote everything, everything works, but voice does not want.

Is there a Nuget or Myget on the branchs?

voice region - In terms of the location of the server?

I'm talking about the server option here:

I've noticed for example that US East will have weird issues, but US Central won't.

Is there a Nuget or Myget on the branchs?

Since that branch is still a work in progress, not yet. You should be able to just clone the branch, add the project file to your solution, and swap the NuGet reference with the project ref.

So, when you let your code run, does the loop get stuck from the call to Connection.CanSendVoiceData(transferBuffer.Length), or does it actually send all of the voice data but you just can't hear it? If it's the latter case, then ffmpeg isn't the problem, the socket is functioning, and that WIP branch will probably do the trick for now.
The Discord developers have just recently documented more of the voice API (and coincidentally looks like they partially broke v1 of the voice API), so in v3.1.0 Discore will support the latest voice API version which should solve the issue you're having. I'm planning on releasing that this weekend which will contain the fixes from that branch.

Yes, the sound seems to be transmitted, but it's not audible, okay, I'll wait for the general branch, I'm too lazy to configure GitHub for Visual Studio: D I hope it does not take long. :)

Server Region - The server is in Russia.

Wait so, you do hear something? Is it just messed up sounds spaced out over a few seconds, or just constant screwed up sound? The former is what I get on certain voice regions.
Out of curiosity, I would try and change the server to like US Central or really anything else and see if you get different results.
Also you shouldn't need to link GitHub and VS, just clone it down via CLI or something like GitKraken. Through VS you should be able to do "Add existing project" and just select Discore's .csproj.

What is the problem?

It looks like VS isn't building Discore, unless there's an inner exception with more details?
You removed the NuGet reference right?
How did you add the project?
The way I do it is:

Right click on solution in solution explorer -> Add -> Existing project...
Right click on Dependencies under my bot's project -> Add reference...
Select the projects tab on the left (which should be default) and check off Discore on the right

The only other thing I can think of is maybe the solution config got messed up. Try opening up the Configuration Manager (Build -> Configuration Manager...) and make sure that your bot and Discore have matching platforms and are both checked off to build.
If all else fails, try restarting VS then clean and rebuild the solution...?

Yes, I do everything as you do, but the build with Nuget works. 3.1.0 does not work.

VS is definitely not building Discore then, try building Discore specifically, then running again.
Also, I think Discore is set to build in 64-bit mode by default... If your bot isn't, it may be looking in the wrong folder under bin/Debug for Discore.dll.

@Flex1337 Sorry, I thought you were @SunnyElite in my last comment lol...
If neither of you can get the branch to work, could one of you send me an example project with the audio issue? That may make life a little easier here...

One friend's account, but it's all me :D

So...unfortunately I cannot bring stable voice API v3 support to Discore this weekend. According to the devs, v3 is not ready until the PR for its documentation is merged over at https://github.com/hammerandchisel/discord-api-docs.
Assuming that your code is correct (which is certainly looks to be), the only "fix" for this issue as of now is to change your server to a different voice region.
The actual fix will be included in Discore v4.0.0 (since it's going to change some public API stuff) and can be tracked at #22 .
You can still use the bug/voice-fixes branch if you would like to, but it's proven to still be buggy even though it works in most voice regions now...

 I've noticed that my bot is now working fine on us-east servers.

Going to close this for now since there's no identifiable cause. Discore 4's support for the newest voice API seems to be working fine and will likely fix this once it's done anyway.


Allow resub messages to show in /mentions tab

Pull request checklist:

[x] CHANGELOG.md was updated, if applicable

Description
This PR aims to fix resub messages not showing in the mentions tab when they trigger a highlight. Previously resub/sub messages were explicitly excluded from the /mentions tab (for whatever reason). This clause has been removed.
The sub message block (first clause in the highlight parser) has had the return statement removed so it can handle more highlights. I've added checks to see if the message is a sub message in all other highlight checking blocks so the colour of the sub message isn't overridden.
Fixes #1013

Using the test message stuff in Window.cpp (didn't know that existed):
In the channel:

In /mentions:


Can't install

I tried to run the command from my terminal:
pip3 install soundscrape
it returns an error:
No files/directories in /tmp/pip-build-hc6mbno9/soundscrape/pip-egg-info (from PKG-INFO)
I tried installing other packages from other sources, and it works perfectly.

Try installing as much as needed python3- packages with apt-get as you see pulled in at /usr/local/lib/python3.5/dist-packages Remove those that you could inatll from that directory and try pip3 install again. That worked for me.

Can't reproduce, sorry. Works for me.


1.20.4?

Hewwo :3 Id love it you could port it to 1.20.4 please

Hi! Thank you for taking an interest on the mod! I really appreciate it! ^^
I haven't had much time lately due to college, but I want to release an update as soon as possible. Sorry for the inconvenience.


Progress Radial with "x-small" size goes out of containing div

Describe the bug (actual behavior)

ProgressRadial with size set to "x-small" goes out of containing div. If you set the width and height of the ProgressRadial smaller and smaller, it goes out of the div more and more. The first picture is with the height and width of the radial set to 16 pixels and the second is set to 10 pixels. It seems to have room in the containing div but does not stay in it.

Expected behavior

The ProgressRadial to stay inside of its containing div at all times.
Reproduction
Link to a minimal repro:
Linked is a sandbox that demonstrates the issue https://codesandbox.io/s/optimistic-booth-k7w4pc?file=/src/App.tsx .
Steps to reproduce

Use a Progress Radial with size set to "x-small"
Color the background red
Watch it go out of the container

Additional information

the sandbox looks fine to me?

If you zoom on the top radial you can see where it slips out on the bottom of the div. Might be a little harder to see in dark mode. It will be more evident if you decrease the size of the radial more

this is valid! i can see it better when zooming.
@joehenry9498 we can discuss how to fix it, but i want to first make sure that you're not trying to override the size using css. these sizes are pre-defined for consistency reasons and we cannot guarantee it will work if you change it to say, 10px

this is valid! i can see it better when zooming.
@joehenry9498 we can discuss how to fix it, but i want to first make sure that you're not trying to override the size using css. these sizes are pre-defined for consistency reasons and we cannot guarantee it will work if you change it to say, 10px

We are just using the regular "x-small" size and not overriding the css properties, the 10px example was just to showcase the problem more definitively

@joehenry9498 We are currently working on our next major release (v3) and have completely refactored progress-radial, so this issue is actually fixed in v3. https://codesandbox.io/s/strange-kate-y567dt?file=/src/App.tsx
However, this should be a simple fix in v2, so would you like to contribute a fix to the main branch so it's available for you? I believe you'll just need to add position: absolute here:
https://github.com/iTwin/iTwinUI/blob/6f24416899053c9de831ba2b7e898b9ac0f2b6d5/packages/itwinui-css/src/progress-indicator/radial.scss#L14-L16
We can discuss specifics / alternate solutions in your PR. You can look at our contributing guide to get started.

Pull request with fix is linked

fix has been released in 2.11.8, thanks @joehenry9498


Don't show the failure screen after SYM has run.

Note: While all requests are welcome, finding available cycles to custom-code a feature we won't use in our production environment is always challenging.

Is your feature request related to a problem? Please describe.
Not a problem, just something that would be nice to have.
Describe the solution you'd like
A variable to not let the failure dialog pop up. Standard it should still pop-up but having the ability to turn it off would be nice to have.
Describe alternatives you've considered
I tried tinkering myself a bit but writing extensions in someone else's code is not the same 😄

Thanks, Michiel!

@DevliegereM:
What would you like to happen if there are failures reported in the main SYM dialog, but the so-called "Failure" dialog has been disabled?

@DevliegereM:
Please test-drive 1.10.0-rc14 (in the development branch) by setting failureDialog to false.

@DevliegereM:
What would you like to happen if there are failures reported in the main SYM dialog, but the so-called "Failure" dialog has been disabled?

I would like it to be sent to the .log file (which already happens) so that works fine for me. Users are already rebooted after SYM completes so the recurring check-in for missing items will happen when they log in.

Thanks, @DevliegereM!


[BUG] RKE1 Node driver cluster creation fails on SLE-15-SP5 and SP4.

Rancher Server Setup

Rancher version: v2.8.0-rc1
Installation option (Docker install/Helm Chart): Docker

Information about the Cluster

Kubernetes version: v1.27.6-rancher1-1
Cluster Type (Local/Downstream): Downstream

If downstream, what type of cluster? : Node Driver (AWS)

User Information

What is the role of the user logged in? Admin

Describe the bug
RKE1 Node driver cluster provisioning fails on SLES-15-SP5 and SLES-15-SP4 OSes with following error in journalctl.
failed to start daemon: error initializing graphdriver: [graphdriver] ERROR: the overlay storage-driver has been deprecated and removed; visit https://docs.docker.com/go/storage-driver/ for more information: overlay
To Reproduce

Create a rancher server v2.8.0-alpha2
Create a node template with AMI ID - ami-0e2ff454233f50e3d (If this AMI is not accessible use any AMI with docker version 24.0.5 or create a new AMI with docker version 24.0.5)
Docker version on this AMI is v24.0.5
Provision a RKE1 node driver cluster with the SLES 15 OS and docker version 24.0.5

Result
Cluster creation fails with below error.
failed to start daemon: error initializing graphdriver: [graphdriver] ERROR: the overlay storage-driver has been deprecated and removed; visit https://docs.docker.com/go/storage-driver/ for more information: overlay
Expected Result
Cluster provisions successfully.
Additional context
Issue was encountered while testing - https://github.com/rancher/qa-tasks/issues/1003

RKE1 node driver cluster provisioning using OpenSUSE 15.5 and 15.4 is also failing with following error on UI :
Error creating machine: ssh command error: command: sudo systemctl -f restart docker err: exit status 1 output: Job for docker.service failed because the control process exited with error code.
With below workaround, cluster provisioning is successful :

In node template -> Engine Options -> Storage Driver -> provide overlay2


Support new standard grid layout properties

What version of Sass Lint are you using?

1.12.1

Please include any relevant parts of your configuration

no-misspelled-properties: true

What did you do? Please include the actual source code causing the issue.

Use row-gap in one sass file.

What did you expect to happen?

row-gap is now the new standard and should be supported.

What actually happened? Please include any error messages given to you by Sass Lint.

error  Property row-gap appears to be spelled incorrectly  no-misspelled-properties

If you're using a IDE plugin have you tried the CLI too?

yes

really? No updates in almost 2 years?


If port 80 is already in use by the user app (public url) then capture portal can not also use port 80

Can you add to the list for V3 the ability for the hotspot to work on port 80, even if an app is already using it....my node app uses port 80 (public URL) which means the capture portal does not auto load.  I had to change it to use a different port then access it via http://something:1234 in order to set the wifi credentials

Hi ashleycoker! I'm facing the same issue. Now, What I'm doing is
server.close(function() {
  setWifi();
});

And then rebooting the device, so the server connection can start again at port 80.
I'm creating a spawn process for the change-wifi shell script, but I wish I could spawn a node process for changing the wifi, and when the subprocess finish, re-create the express server connection. For now I'll leave as it, because it's just a demo, and we're are focusing on other parts of the application, but I want to get better at doing this sort of thing with nodejs.
I think I must embed the Dbus part of the shell script inside the app.coffee of resin-wifi-connect. But hasn't tested yet. Any thoughts?

similar use case.  I wish not want to integrate this coffeescript into my existing nodejs service.  that means my other app is going to listen to port 80 too.  any workaround/pointers ?

I'm facing the same problem, I wanted to use an express app on port 80 that tells the wifi config portal to start. I guess I should return a success message, close the server, then start the wifi config script.

WOW this fixed my problem!

Closing this as fixed, as we introduced a command line argument + env var for this:
-o, --portal-listening-port listening_port, $PORTAL_LISTENING_PORT`.

Listening port of the captive portal web server

Default: 80


Don't block payment on failed fee probe

Current Behavior: A payment is blocked when the fee probe fails.
Desired Behavior: Don't block payment and have a more helpful error message.

If the fee is for onchain the payment will most likely fail anyway (onchain wallet depleted)
Where the behavior is different is with lightning when probe doesn't always works

And the message is indeed very misunderstood by the users

because "fee probe unsuccessful" (or whatever is the message we have now) is not something user really understand. ie: the concept of probing over the lightning is too technical in nature and showing max fees is a better behavior for instance.
right now we're blocking the payment when fee is pending. but previous behavior (v1+) was to allow payment even if fee probe was pending, when we would return the result of the query we would either 1/ show the fees 2/ show the errors above. I'm talking about the error above.

I was confused because I didn't understand why we would display an error but allow the user to continue, but I understand now.  The way I see it we have two options.

Display something like "unknown" in the fees field in the event that the call fails.  We can also show a question mark icon next to it which will allow the user to tap on it to display more information about why the fees are unknown if they want to know more.
Display the max fee in the fees field in the event the call fails.  Again we could show a question mark icon next to it which could display a modal explaining that this is max fee but it might end up costing them less once payment is made.

Also I see we have added the logic to return early from the fee probe on the backend which is great https://github.com/GaloyMoney/galoy/pull/1420

agree for option 2.
we should also lower the amount of max fees. currently it's 2% AFAIR. This could be 0.5% instead.


cannot import name SEASON_TYPE_TO_IDX error

Hi, thanks for your great contribution!
I am having trouble executing customizationmanager.pyc. It gives the following error message in python.log (worldoftanks <IP_ADDRESS> (compiled at 12:03:51 Jul 30 2019) starting on Wed Aug  7 15:14:30 2019):
==============================================================
2019-08-07 15:14:54.941: INFO: [SL_PRO] Skipped Script: mod_customizationmanager.pyc
2019-08-07 15:14:54.941: INFO:
2019-08-07 15:14:54.942: ERROR: [EXCEPTION] (, 611):
Traceback (most recent call last):
File "", line 599, in _findValidMODs
File "scripts/common/Lib/importlib/init.py", line 37, in import_module
File "./scripts/client/gui/mods/mod_customizationmanager.py", line 18, in
ImportError: cannot import name SEASON_TYPE_TO_IDX
==============================================================
Is this a common problem or am I doing something wrong? Thanks

hi, somehow it  was sorted in the next iteration of Aslain mod. It was probably something to do with the modpack. Cheers and thanks for the work!


Steam doesn't use KDE cursor

Issue description
Steam use default cursor when trying to use breeze or oxygen cursors. Manually installed cursors (for example this https://store.kde.org/p/999970/ ) works fine
Steps to reproduce
Pick one of default cursors
Launch steam
Technical details

System: NixOS 17.03.1082.4aab5c5798 (Gorilla)
Nix version: nix-env (Nix) 1.11.8
Nixpkgs version: 17.03.1082.4aab5c5798

IIRC, Breeze and Oxygen cursors are SVG; some applications cannot handle SVG cursors. It is also possible that Steam hardcodes XDG search paths, so it find user-installed themes but not system-installed themes.
CC: @jagajaga

Breeze cursor works fine on my end.

Breeze cursor does not work fine on my end. I'm on Plasma 6 on the unstable channel.

Adding a manual override to the steam package fixes the cursor.
  programs.steam.package = pkgs.steam.override {
    extraPkgs = p: [
      p.kdePackages.breeze
    ];
  };

I can't reproduce.

@SuperSamus Installed through Flatpak or nixpkgs?

programs.steam.enable = true;

Weird to say the least.

Try deleting all theme related files/folders (like .config/gtk*) and reapplying the theme on KDE's settings?

Gave that a try right now, sadly didn't work.
I wonder why adding the breeze package directly into Steam extraPkgs makes it work though.


Makes expanded as internal

LGTM. /cc @jbalsas

LGTM

To complement the PR, it will be internal, but there's still a way to make it start open by changing the state with this function https://github.com/metal/metal-dropdown/blob/master/src/Dropdown.js#L69


create-stack: stream output from Docker

Currently when running jam create-stack it appears to hang while building the images:
Building io.buildpacks.stacks.jammy.full
  Building on linux/amd64
    Building base images

In the case of the full stack, this process can take many minutes.
When running a docker build command, there is constant streaming output.
It would be a significant UX improvement to jam create-stack if we could stream this same output (or similar) while we build the stack.

Is this a dupe of #70 or is there a difference there that I'm missing?

I view them as different. I would expect to stream the docker output regardless of verbose mode. I view the --verbose flag as a more general debugging that would include output that indicates steps taken by jam as well as the docker output.

Can you provide some more detail on that other issue? I don't understand what else gets output if the command always prints its current output and then also always streams the output from the docker build.

Similar to #70, I'm going to close this issue. If there's feedback that stack creators would significantly benefit from streaming docker logs in real-time we can re-open and re-evaluate.


Fix bug in UG

Fixes #233
Change AddressBook to ResearchRoster in "Editing the data file" warning

LGTM


Vmclarity updates from repo

@chrisgacsal Updated with https://github.com/openclarity/vmclarity/pull/916/


More visible light mode colors

In dark mode the icons are clearly visible:

But in light mode not so much:

Actually this problem happens without the Bubble theme as well and I would prefer to keep the default theme anyway, so I'm going to close this one and open one in Bubble Card.

I didn't even have to open one, someone else already reported this issue: https://github.com/Clooos/Bubble-Card/issues/692


Aggregate the process to fetch and unarchive to one module

In task/main.yml, fetch and unarchive modules to get a Tower's bundle image can be put together by specifying its URL in src argument of unarchive module.

This was resolved on the commit 91bd3db


Ensure compatibility check readiness

Coming from https://github.com/opensearch-project/opensearch-devops/issues/114#issuecomment-1548868449
Overview
In order to detect the breaking changes between OpenSearch (core/min) and plugins, we recently onboarded a compatibility check gradle task with OpenSearch. See the pull request.
The task is dependent on publishToMavenLocal task (that publishes the core engine artifacts to maven local). It then clones the plugins' repository in temporary directory and runs ./gradlew assemble.
Action Items
In order to avoid false positives and false negatives, we need to make sure the tasks in below checklist are complete:

[ ] The build.gradle file in this repository uses mavenLocal() as the first entry in repositories() section. This will ensure that when core/min dependencies are published to maven local, gradle looks at maven local first and gets the required core/min dependencies rather than fetching from snapshots or maven central resulting in false checks.
[ ] ./gradlew assemble task passes for the plugin build. If the task itself is broken, checking compatitibility is irrelevant as it will always fail.

Please close this issue once the above checklist is complete.
Thanks!

@davidlago  can you please provide an update?

Raised https://github.com/opensearch-project/security/pull/2980
Verified this.

[Triage] @scrawfor99  will complete this before EOD.

[Triage] Closing before @owaiskazi19 completed. Thank you!


Allow directly reading audio data

A basic solution to Proposal

Bugsquad edit, closes: https://github.com/godotengine/godot-proposals/issues/7601

This is essentially a duplicate of:

https://github.com/godotengine/godot/pull/75065

I wonder if it would be better if all virtual methods could be called


Responsive nav_logo is unable to appear

nav_logo bug
The responsive nav_logo "SurPath Hub" is unable to display when the minimum width size reaches 767 and below.
To Reproduce
Steps to reproduce the behavior:

Go to '[https://surpathhub.github.io/]'

Inspect elemets or F12

Click on 'Toggle device emulation'

Edit the width to 767

See the 'SurPath Hub' unable to appear

Expected behavior
The 'SurPath Hub' nav_logo needs to appear at any screen size of a device
Screenshots

Working Environment
Operating System : Windows 10
Browser : Microsoft Edge
Device : Laptop and Phone

Do you want to take this issue?

Do you want to take this issue?

Sure! why not.

Hehehe salamats

I fixed the issue by changing the block value of display property of nav__logo rule to flex.

Thank you <3


Make bnb_4bit_compute_dtype consistent with torch_dtype

If torch_dtype is set and is not "auto" we set bnb_4bit_compute_dtype to this.
No reason but intuition, but I expect that being able to align compute_dtype to whatever type the model was loaded in (assuming this is the same type it was trained using) should mitigate any dynamic range issues.
Optionally could have another arg to explicitly set the bnb compute type, but that seems excessive as I can't think of any case where this would be necessary, and just adds another arg.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Improving sheets for several spanish sheets [Robotta, Máscaras del Imperio, Ablaneda, Esoterroristas and Against the Dark Master

Changes / Comments
This is the first step to make permanent background images links for the spanish version of these sheets:

Robotta
Máscaras del Imperio
Ablaneda
Esoterroristas
Against the Dark Master

Additionally, the permanent image link for Tenra Bansho Zero was added.
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[x] Does the pull request title have the sheet name(s)? Include each sheet name.
[x] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.

Hi @Ravencrow we generally only allow for a single sheet to be modified with any given pull request, as it makes it very difficult to undo changes to a specific sheet. Could you please make a separate pull request for each?
Many thanks,
Nic

Hi, @nmbradley !
Ok, I understand. I'll create a new PR per game today.
What about my other PR? https://github.com/Roll20/roll20-character-sheets/pull/9348
Do I need to do something in there to help with the review?
Thanks for the message and the review.


Transform emissions_control_equipment table from EIA 860 EnvrAssoc

Short summary: From 2014-2021, important summary information on each plant's associated control equipment is compiled in the Emissions Control Equipment table. From 2009-2021, the same information on IDs, cost, equipment type and operational status for SO2 and PM control is available in the table associated with each type of equipment in the EnvrEquipment dataset. More minimal information is also available on NOx and mercury controls. To effectively incorporate information on control equipment investments and operational status throughout time, we should pull the data from both the EnvrEquip tables and the Emissions Control Equipment table, where available. When there is more than one source of information available for a given piece of control equipment (i.e. 2014-2021 data), we should compare these values and harmonize them.
The output of this result will be an Emissions Control Equipment table for 2009-2021, with a unique ID for each piece of control equipment, containing the following information:

Control ID
Control type (boolean for particulate type)
Equipment type
Operating month and year of the control equipment
Operational status
Acid gas control (boolean)
Capital cost of equipment

Tasks to clean this dataset:
Metadata preparation

[ ] Rename operating and retirement dates in pudl.package_data.eia860 to distinguish from generator operating/retirement dates

Emissions Control Equipment Table (2014-2021)

[ ] Add all code columns to fields.py and define code metadata
[ ] Convert inservice month and year columns to a date
[ ] Minor QC on total cost column
[ ] Normalize “Acid Gas Control?” column into boolean
[ ] Define a unique PUDL ID for each piece of equipment, and make a shared control_id_pudl column that acts as a primary key for this dataset. Propagate this column to other incorporated datasets.

Association tables (2009-2021): Boiler Cooling, Boiler Particulate Matter, Boiler SO2, Boiler NOx, Boiler Mercury

[ ] Add all code columns to fields.py and define code metadata
[ ] Minor cleaning (e.g., make sure no plant or control IDs are missing)
[ ] Propagate unique PUDL ID from Emissions Control Equipment tab, or generate ID following same format for data prior to 2014

EnvrEquipment tables (FGD, FGP)

[ ] Extract ID column, Inservice Month, Inservice Year, and Cost Total columns. For the FGP table, this is only applicable to 2009-2013 data.
[ ] Subject these columns to same transforms as above. Reuse functions.
[ ] 2014-2021 FGD data : Compare these values to those reported in the Emissions Control Equipment table.
[ ] For each plant, if the same ID appears in multiple tables, compare cost, service date, and equipment type columns to identify whether they refer to the same piece of equipment (see Anticipated problems below)

Denormalized boiler-control equipment table

[ ] Join boiler IDs from association tables to the Emissions Control Equipment table, matching on plant and utility and control ID

Anticipated problems:

[ ] There are no NOx or mercury control IDs prior to 2014 in this dataset. In the 2009-2013 data there is a boolean associated with mercury control, several columns containing operational status of NOx controls and column with information on control types in the Controls tab of the EnvrEquip data. These are reported at the boiler level, and are already integrated into the boiler attribute tables. As these are not associated with cost or installation dates, there doesn't seem to be much value into faking control IDs for this information, which may reflect 1 or more pieces of equipment. NOx control equipment IDs are reported prior to 2014 in the EIA 923 Schedule 8c data, and could also be incorporated into this analysis if it is of interest.
[ ] Equipment to boiler associations are not 1:1, but m:m. This shouldn’t be too much of an issue so long as we aren’t trying to bring this table into our existing entity structure, but should be kept in mind when performing joins.
[ ] Cost values are sometimes reported in thousands of dollars, and sometimes in dollars. Units should be harmonized.
[ ] Sometimes NOX ID 1 and SO2 ID 1 are the same piece of equipment in a plant, and sometimes not. This is spelled out explicitly in the EnvrEquip table, but not prior to 2014. We will need to compare additional columns to see whether these are the same or not when creating control equipment IDs. Simultaneously, this strengthens the argument for adding a unique ID column.
[ ] EnvrEquip and EnvrAssoc data for identical columns may differ for 2014-2021 data. We'll need to decide how to reconcile these differences.

Additional possible tasks:

[ ] In the boilers_annual_eia860 table, existing columns refer to strategies for emissions control, but are often empty. We could compare these to operational control equipment to generate more accurate records of what emission control strategies are in place at the boiler-level. Perhaps we should collapse the many strategy code columns in the boilers entity table into a few consolidated columns based on observed equipment types.
[ ] Attempt to backfill acid gas control boolean column
[ ] Incorporate cooling IDs, cost and installation dates in the same manner as above. Potentially, bring in the cooling system data reported in EIA923.
[ ] EIA923 Schedule 8C also reports FGD, FGP, Mercury and NOx control information from 2008-2021, including operational status. This does not include information on in-service date, but does include information on FGD operational and maintenance costs, among other information that may be of interest.

We'd be very interested in seeing if there is a way to get access to this data or ease the process of, outside of PUDL, accessing this data. In particular we are interested in the following:

The in-service date for emission control equipment
The capital costs of emission control equipment

This data helps understand important details about recent investment in coal plants which helps with prospects for retirement or CCS.
I'm wondering if there is a way of bringing in this data without fully cleaning it. Things like merging together all the environmental equipment association tables and the basic fixing of EIA data weirdness in emissions_control_equipment.
It probably also makes sense to connect with @mariacastillo21 since she's worked with these tables and might have suggestions about how they could be processed.

@zaneselvans To my understanding, capital costs are currently reported in the Total Cost (Thousands of Dollars) column of the Emissions Control Equipment table, which has the following definition:
"The nominal installed cost for the existing emissions control equipment or the anticipated cost to bring the planned piece of emissions control equipment into commercial operation"
@arengel If this is not the column you're referring to, this would of course be helpful to know!

Ah! You're right. I was thinking of the EIA-860 Environmental Equipment table. I guess this is where that information got moved to!

Hmm. It looks like there's also a bunch of detailed emissions equipment O&M and capital cost data in the EIA-923 Schedule 8.  Maybe There was more detailed cost reporting for a couple of years in the EIA-860 and it got incorporated into EIA-923? I'm not sure where I was getting this idea from.
Oh, it looks like it was probably the flue gas particulate emissions control costs, which show up in the EIA-860 through 2012, but not in later years.

There is definitely more detailed cost information in Schedule 8. The FGP control costs from 2014-present are now reported in the Emissions Control Equipment tab (which has one row for each piece of control equipment), as is noted above! There's some tab and ID renaming that happens between 2013-2014.

Thanks @e-belfer!
Total Cost (Thousands of Dollars) on the Emissions Control Equipment tab of 6_1_EnviroAssoc_YXXX.xlsx is indeed the one I was referring to, I don't remember how long its been there but it is definitely there in 2021.
In terms of what I think would be useful I think we'd want a couple things:

All the columns from the Emissions Control Equipment tab. The total cost and inservice date columns are the most important but we'd also want retirement date, status, and the others.
I think the hard part is what to do with the all the emission control equipment IDs and providing a way to link them to boilers using the association tables without turning this into a grand many:many problem in which you have to aggregate or allocate costs. My proposal here would be 2 tables, at least as an interim step:

one that is basically just the cleaned Emissions Control Equipment tab.
one that combines all the boiler <> equipment ID association tabs, this table will capture all those many:many associations. Hopefully this could just be an association table or crosswalk that would not change between years.

This allows you to make the data accessible without having to figure out a general approach to integrating it all together. For a lot of uses I think the integration can be a simple aggregation, but I'd argue against doing it in PUDL because for other use cases you are looking at a small number of plants and want as granular data as is available. Also, after using this data some, we might come up with better ideas of how to do a general integration.
As for other column / tabs, there is valuable information in the Cooling, FGP, FGD, and Stack Flue tabs of 6_2_EnviroEquip_YXXX.xlsx but I'd put it as a lower priority. In those cases, if it isn't too big a pain to do a simple cleaning of those tables, I wouldn't want to stand in your way, but I wouldn't go much beyond basic cleaning (e.g. I wouldn't worry about reconciling costs between them and Emissions Control Equipment). Users could then use the equipment association table mentioned in (ii) above to link this data to boilders and then generators.

Before saying anymore, I want to acknowledge that I am not that familiar with issues around boiler reporting and how they get associated with generators. But, it sort of seems like, at least as regards Emissions Control Equipment, sorting out the issues with differently reported past years may not be as important or even required because the table in the most recent year is complete. And if not I'd be fine with only going back to 2013 or whenever the data becomes more or less consistent.

@arengel, @e-belfer correct me if I'm wrong here, but I think that the main difference between getting all years vs. just 2014+ is where the columns come from. If we only want 2014+ we can take the table from the Emissions Control Equipment tab as is, and if we want older years, we'll combine columns from various tabs in the the EnviroEquip spreadsheet. They're all reported at the same granularity, so there's no need for any aggregation or complex merging. The only difference is that the earlier years of data may have less mercury and NOx data.
Let me know if there are any preliminary checks you'd like us to run to see if the older years would satisfy your needs. Otherwise we can just go ahead and integrate 2014+

I think the complex merging is with connecting emission control equipment to boilers, that's what I was proposing to avoid figuring out for now.
On going back further, it is lower priority on our side, so I'd propose sticking with the tables that are easy-ish to deal with for now.
Also, it's not obvious to me, at least for the Emissions Control Equipment tab that you need all years, it looks like the most recent year might be complete. Or it might only be complete for currently operating boilers or plants.

I wouldn't be surprised if the emissions control equipment associations aren't entirely constant with time. We've been surprised in the past at just how many of the generator attributes do slowly evolve, for example the changes in the prime mover or technology type. But hopefully those instances are rare, since big reconfigurations of how the units in a plant connect to each other are also rare.

@mariacastillo21 or @arengel do you know what's up with the rows in the Emissions Control Equipment table that have all NA values for XX_control_id and acid_gas_control? What are those rows reporting? Those rows still have a emission_control_equipment_type listed, but nothing else. Do you know what it means for a plant to have emissions equipment but no control ids or acid gas control? It only occurs for emission_control_equipment_type values 'SR', 'OT', 'ACI', 'LNB'

Also @mariacastillo21 I'm assuming that control ids reported in the same row are part of the same equipment given the shared emission_control_equipment_cost , installation_year, and emission_control_equipment_type columns. Does that seem fair? Not all of controls ids are the same in a given row (though many of them are), and I'm assuming this difference is not important (I don't plan on cleaning the control_id columns unless you think it's worth exploring).

@aesharpe There are a bunch of other tasks in this issue that should get written into a separate issue if you want to close it - otherwise, it should probably stay open!

Jumped the gun here, sorry!
On Tue, Oct 1, 2024 at 2:15 PM E. Belfer @.***> wrote:

@aesharpe https://github.com/aesharpe There are a bunch of other tasks
in this issue that should get written into a separate issue if you want to
close it - otherwise, it should probably stay open!
—
Reply to this email directly, view it on GitHub
https://github.com/catalyst-cooperative/pudl/issues/2338#issuecomment-2386984746,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL4RJMYPNTZFAEUONACMUADZZL7HVAVCNFSM6AAAAABPGEKZC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBWHE4DINZUGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

I added it to the list of "RMI was interested in this what do we do now"
issues here
https://docs.google.com/document/d/14KkCg5L_F2Bm9olO48eIYiQpdnNU1LFGE2j0xeP4xDU/edit#heading=h.fsti2yyqy2sy
.
On Tue, Oct 1, 2024 at 2:32 PM Austen Sharpe @.***>
wrote:

Jumped the gun here, sorry!
On Tue, Oct 1, 2024 at 2:15 PM E. Belfer @.***> wrote:

@aesharpe https://github.com/aesharpe There are a bunch of other tasks
in this issue that should get written into a separate issue if you want to
close it - otherwise, it should probably stay open!
—
Reply to this email directly, view it on GitHub
https://github.com/catalyst-cooperative/pudl/issues/2338#issuecomment-2386984746,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL4RJMYPNTZFAEUONACMUADZZL7HVAVCNFSM6AAAAABPGEKZC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBWHE4DINZUGY
.
You are receiving this because you were mentioned.Message ID:
@.***>


Build error - hello-reason example - macOS host, iOS simulator target

Trying to build the hello-reason example under macOS 11.5.2:
% esy generate ios.simulator.x86_64
...
    Undefined symbols for architecture x86_64:
      "_libiconv", referenced from:
          _g_iconv in libglib-2.0.a(libglib_2_0_la-gconvert.o)
          _g_convert_with_iconv in libglib-2.0.a(libglib_2_0_la-gconvert.o)
          _g_convert_with_fallback in libglib-2.0.a(libglib_2_0_la-gconvert.o)
      "_libiconv_close", referenced from:
          _g_iconv_close in libglib-2.0.a(libglib_2_0_la-gconvert.o)
          _g_convert in libglib-2.0.a(libglib_2_0_la-gconvert.o)
          _g_convert_with_fallback in libglib-2.0.a(libglib_2_0_la-gconvert.o)
          _g_filename_display_name in libglib-2.0.a(libglib_2_0_la-gconvert.o)
      "_libiconv_open", referenced from:
          _g_iconv_open in libglib-2.0.a(libglib_2_0_la-gconvert.o)
    ld: symbol(s) not found for architecture x86_64
    clang: error: linker command failed with exit code 1 (use -v to see invocation)
    make[2]: *** [pkg-config] Error 1
    make[1]: *** [all-recursive] Error 1
    make: *** [all] Error 2
    error: command failed: 'make' (exited with 2)
    esy-build-package: exiting with errors above...

  building yarn-pkg-config@github:esy-ocaml/yarn-pkg-config#db3a0b63883606dd57c54a7158d560d6cba8cd79

Can you give me your esy.json? So that I can reproduce, but my bet is that it's some package which doesn't work well on macOS 11.5

I cloned this repo, then cd examples/hello-reason, then followed the readme to build it. I don't see esy.json in that dir. Below is the package.json:
{
  "name": "hello-reason",
  "version": "0.0.0",
  "esy": { "build": "dune build @all" },
  "scripts": { "start": "#{self.target_dir}/default/bin/hello.exe" },
  "dependencies": {
    "@opam/reason": "^3.7.0",
    "@opam/dune": "*",
    "@reason-native/console": "^0.1.0",
    "@reason-native/pastel": "^0.3.0",
    "ocaml": "4.12.x"
  },
  "resolutions": {
    "@esy-ocaml/reason":
      "EduardoRFS/reason:reason.json#35aa4df3de0daa60bdc1133dcf97855decac48f7"
  },
  "devDependencies": {
    "generate":
      "github:EduardoRFS/reason-mobile:generate.json#7ba258319b87943d2eb0d8fb84562d0afeb2d41f"
  }
}

On the other hand, there is an esy.lock dir in there. Am I not doing something right?

@dboris you're probably following it right, not sure why the problem is happening, my guest is that Apple did something again and I need to fix this.

This SO comment gives a hint. How can I tell esy to link to libiconv from a specific directiory?


PyTorchClassifier.compute_loss() doesn't accept index-based labels

Describe the bug
The PyTorchClassifier.compute_loss() method does not accept index-based labels, contradicting the documentation.
To Reproduce
Steps to reproduce the behavior:

Go to the get_started_pytorch.py example.
Follow steps 0-3 in the example.
Run
y = np.array(range(10)); classifer.compute_loss(x_train[:10,...], y)
When compute_loss calls reduce_labels(y_preprocessed), reduce_labels will try to take an argmax along dim=1, raising an error.

Expected behavior
I expected the compute_loss method to accept index-based labels, following the documentation.
Possible fix
Similar to the case of binary classification, in the case that self.nb_classes > 2, reduce_labels could check whether len(y.shape) == 2.
System information (please complete the following information):

Python version 3.6.3
ART version 1.6.1
PyTorch version 1.7

Hi @jacobalanbond Thank you very much for reporting this bug! We'll fix it in the next release.


Text strings must be rendered within a  component

My code:
const Login = ({ navigation }) => {
 const [ email, setEmail ] = useState('')
 const [ password, setPassword ] = useState('')
 async function login(){

 }
 return (
     <View style={login.card}>
         <Text>Email</Text>
         <TextInput
<EMAIL_ADDRESS>             placeholderTextColor= "#999"
             autoCapitalize="words"
             autoCorrect={false}
              onChangeText={setEmail}
          />
          <Text>Password</Text>
         <TextInput
             placeholder="senha123"
             placeholderTextColor= "#999"
             autoCapitalize="words"
             autoCorrect={false}
             onChangeText={setPassword}
         />
         <TouchableOpacity onPress={login}><Text>Logar</Text></TouchableOpacity>
     </View>
 )}

error:
Text strings must be rendered within a <Text> component.
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:4137:14 in <anonymous>
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:4134:2 in createTextInstance
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:15909:12 in completeWork
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:19409:28 in completeUnitOfWork
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:19380:30 in performUnitOfWork
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:19347:39 in workLoopSync
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:18997:22 in renderRoot
* [native code]:null in renderRoot
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:18709:28 in runRootCallback
* [native code]:null in runRootCallback
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:5642:32 in runWithPriority$argument_1
- node_modules/scheduler/cjs/scheduler.development.js:643:23 in unstable_runWithPriority
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:5638:22 in flushSyncCallbackQueueImpl
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:5627:28 in flushSyncCallbackQueue
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:18556:30 in scheduleUpdateOnFiber
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:21822:15 in scheduleRootUpdate
- node_modules/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-dev.js:23042:20 in ReactNativeRenderer.render
- node_modules/react-native/Libraries/ReactNative/renderApplication.js:52:52 in renderApplication
- node_modules/react-native/Libraries/ReactNative/AppRegistry.js:116:10 in runnables.appKey.run
- node_modules/react-native/Libraries/ReactNative/AppRegistry.js:197:26 in runApplication
- node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:436:47 in __callFunction
- node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:111:26 in __guard$argument_0
- node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:384:10 in __guard
- node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js:110:17 in __guard$argument_0
* [native code]:null in callFunctionReturnFlushedQueue

React-Native Version:
System:
    OS: Linux 5.3 Ubuntu 18.04.4 LTS (Bionic Beaver)
    CPU: (2) x64 AMD A4-6300 APU with Radeon(tm) HD Graphics
    Memory: 400.00 MB / 7.80 GB
    Shell: 4.4.20 - /bin/bash
  Binaries:
    Node: 12.16.1 - /usr/bin/node
    Yarn: 1.22.0 - /usr/bin/yarn
    npm: 6.13.4 - /usr/bin/npm
  npmPackages:
    react: ~16.9.0 => 16.9.0
    react-native: https://github.com/expo/react-native/archive/sdk-36.0.0.tar.gz => 0.61.4

@Miguel-Coruj it's working fine on my side.

My guess is that that you have some Text somewhere without a Text tag in your code. So until proven otherwise via a repository with a reproduction of a bug, I have to assume that the bug was in fact pre-existing in your code.

I think you must enclose the text within the Text tag
example: <Text --your text here-- />


Sprint 3 Review

Assignment
Points
Grade
Evidence

Tri 1-3 Review Ticket
3

Sprint 3 Team Issue(s)/Plan
2

Beginning-2-End Contribution
2

N@tM Team Presentation
2

Live Review Indi Demo
1

Total
10

Skill
Points
Grade
Evidence

Work Habits (Analytics)
1

Frontend:  Backend:

Evidence of Role in Team
1

Function / Purpose Design
1

Live Review
2

Total
5

I had the same issues with mcq but I think for these types of complex problems we should just write out the full table for each iteration instead of doing it in your head or something.