imageSizes are ignored if they are in a conditional process.env.NODE_ENV === "production"

Hi,
I've noticed that conditional config parameters are ignored and default were used.
For example, this one with changed imageSizes will work as expected
next.config.js:
module.exports = {
  images: {
    loader: "custom",
    imageSizes: [16, 48, 54, 64, 100, 128, 144, 384],
    deviceSizes: [640, 750, 828, 1080, 1200, 1920],
  },
  env: {
    // ...
  },
}

but having a conditional in there, will ignore the changes and load the defaults:
module.exports = {
 images:
    process.env.NODE_ENV === "production"
      ? {
          loader: "custom",
          imageSizes: [16, 48, 54, 64, 100, 128, 144, 384],
          deviceSizes: [640, 750, 828, 1080, 1200, 1920],
        }
      : {
         // ...
        },
  env: {
    // ...
  },
}

I think it might be helpful to output a warning when the process isn't finding the values, so that one can see it will use defaults (like it warns when it doesn't find a next.config.js)

Hi @TimKraemer,
Thanks for the bug report. I now switched to the same method that Next.js uses to parse the next.config.js. Your bug should be fixed now in v1.0.1. Please give it a try.

works perfectly!


Possible bug with samples/net/sockets/echo_server overlay-tunnel.conf

Describe the bug
The echo_server does not get past boot when overlay-tunnel.conf is enabled. Since there are no instructions on how to test with the tunnel, it isn't 100% clear whether this is due to misuse or a bug in the overlay.
This is using the qemu_x86 platform on Ubuntu Linux.
To Reproduce
I derived the following test procedure by combining instructions from the following two pages:

https://docs.zephyrproject.org/3.2.0/samples/net/capture/README.html (Contains a very similar tunneling feature that I was told here should be roughly equivalent to the overlay-tunnel.conf overlay.)
https://docs.zephyrproject.org/2.7.0/guides/networking/qemu_setup.html (standard instructions for the echo_server sample without overlays on qemu_x86)

Terminal 1, in net-tools: sudo ./net-setup.sh -c zeth-tunnel.conf
Terminal 2, in net-tools: ./loop-socat.sh
Terminal 3, in net-tools: sudo ./loop-slip-tap.sh
Terminal 4, in echo-server sample: west build -p always -b qemu_x86 samples/net/sockets/echo_server -- -DCONF_FILE=overlay-tunnel.conf followed by west build -t run
Expected behavior
Sample should make it past boot and I should be presented with a shell terminal.
Observed behavior
Stalls on boot:
SeaBIOS (version zephyr-v1.0.0-0-g31d4e0e-dirty-20200714_234759-fv-az50-zephyr)
Booting from ROM..
*** Booting Zephyr OS build zephyr-v3.2.0-7691-ga01d40f6049a ***

Without the overlay, and following the normal instructions for echo_server the sample compiles, boots, presents shell, and is pingable from the host OS as expected

@glarsennordic I've tried to reproduce the issue, and failed. I've tried qemu_x86 and native_posix, same Zephyr revision as in the log you provide, and observe no issues with boot at all.
The virtual interface seems to be working correctly. The interface starts in admin DOWN state, but after bringing it up, it seems to be listed correctly:
uart:~$ net iface up 1
Interface 1 is up
uart:~$ net iface

Interface 0x149ea4 (Virtual) [1]
==================================
Name      : IPv4 tunnel
Attached  : 2 (Ethernet / 0x149f70)
Link addr : 91:8E:EF:EC:F2:BF
MTU       : 1480
Flags     : POINTOPOINT,NO_AUTO_START,IPv4,IPv6
IPv6 unicast addresses (max 3):
	2001:db8:200::1 manual preferred infinite
IPv6 multicast addresses (max 4):
	<none>
IPv6 prefixes (max 2):
	<none>
IPv6 hop limit           : 64
IPv6 base reachable time : 30000
IPv6 reachable time      : 44408
IPv6 retransmit timer    : 0
IPv4 unicast addresses (max 1):
	<none>
IPv4 multicast addresses (max 1):
	<none>

And once the interface is up, I can ping the tunnel interface from my Linux host (after running sudo ./net-setup.sh -c zeth-tunnel.conf - with native_posix this works out of the box, qemu_x86 requires slightly different configuration, but also works).
I do agree though, the documentation on the tunneling topic could be better though.
Anyways, since the original concern was about not breaking the tunneling with the new conn_mgr extension, and it doesn't seems to be the case (main works fine for me as well), maybe we should consider closing the issue? I don't see anything to fix here.

Strange -- I'd be curious what your exact build command was, but I agree, this is fine to close since the primary concern was making sure tunneling isn't broken after conn_mgr. I'm not sure why it fails to get past boot on my system


Use job announcement as first matrix test

It failed to post to the matrix because in plugins.yml there were unconfigured social media.
So either we have to configure all social media first or just remove the unwanted social media from plugins.yml.


Travis build fails due to "no output" for 10+ minutes

Starting from build https://travis-ci.org/int08h/roughenough/jobs/596836299
the AWS KMS build began taking >10 minutes, which Travis will abort
as a build failure.

After digging, found the travis_wait command and prefixed the cargo build and cargo test lines with it (in 9ee05c527ffc).
However, also found that the Travis build caches were >13 GB :face_with_head_bandage:. Deleted caches manually and now builds are finishing in <6 minutes. :man_shrugging:


Error: refusing to allow an OAuth App to create or update workflow

Hi @goedman -
I am trying to add the automated package updating that you added to MCMCBenchmarks, but I run into this error. Do you know what I need to do in order to fix it? Thanks!
To https://github.com/itsdfish/MCMCBenchmarkSuite
 ! [remote rejected] master -> master (refusing to allow an OAuth App to create or update workflow `.github/workflows/CompatHelper.yml` without `workflow` scope)
error: failed to push some refs to 'https://github.com/itsdfish/MCMCBenchmarkSuite'

Not 100% sure. Were you trying to add CompatHelper and TagBot by committing to a repo?
Just added these two using the Actions button on Github, but was that your question/issue?

Also enabled Travis testing on the repo. I am a bit concerned about the repo name, shouldn't it be MCMCBenchmarkSuite.jl (or MCMCBenchmarkSuite.jl.git)?

The PRs (pull requests) by CompatHelper are a bit tricky, at least on my system. I tend to indeed merge them in the correct sequence (otherwise I have seen merge conflicts arise) and then after confirming the merge I delete the branch (all on Github).

Thanks Rob. I guess I am learning a few things still. I will add those to the action list in the future.
I didn't realize that .jl was appended to the repo names. I think I can change that without too much trouble since the repo is not registered.


Configure AMA instead of Log Analytics agent

How do I configure my custom AutoManage profile to use the Azure Monitor Agent instead of the deprecated Log Analytics agent?  It keeps deploying the deprecated agent alongside the AMA which I am deploying through other policies.

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

ID: 36e91b66-2b15-07ec-9e94-388e7355c3eb
Version Independent ID: 2e540fb7-028e-acaf-4f56-3997e21d3d8c
Content: Create a custom profile in Azure Automanage for VMs
Content Source: articles/automanage/virtual-machines-custom-profile.md
Service: automanage
GitHub Login: @johnmarco
Microsoft Alias: johnmarc

@a-hackw
Thanks for your feedback! We will investigate and update as appropriate.

@a-hackw Can you please check if your custom profile has below property enabled?
"LogAnalytics/UseAma": true

It doesn't. I don't see that property in the documentation at all.

@a-hackw Yes, it's not updated in the document as of now. I have tested this in azure portal. Here is snapshot from my environment for your reference. We will update the document soon.

@a-hackw Thanks for the feedback! I have fixed the referenced change, and the change should reflect on the doc once approved by content author. We will now proceed to close this thread. If there are further questions regarding this matter, please revert and we will gladly continue the discussion.


Login/Logout Page

Is your feature request related to a problem? Please describe.
The main Login/Logout Page for going in and out of student dashboard and recording the data.
Describe the solution you'd like
A clear and consize login logout page

i would like to tell you , i am ready to this work for making login and logout page
so you can assign me this work..

@Deveshjoshi101  can you assign this issue to me

Hi Shubham,
Please check on the merge conflicts. Have you checked on them???
First check your forked repo is in sync with the remote origin.
Second check whether you have pulled properly. (try git pull in your local system)
Then check the differences (Merge Conflicts).
Regards,
Devesh


Example multi query

Hello, please tell me.
How to execute this code in one request and get two responses at once?
CREATE TABLE users (name TEXT, age INTEGER);
INSERT INTO users VALUES ('1: Alice', 1);
INSERT INTO users VALUES ('2: Bob', 2);
SELECT sqlite_version();
SELECT * FROM users;

Yon cannot.
There is nothing like https://docs.oracle.com/javase/7/docs/api/java/sql/Statement.html#getMoreResults().

Yon cannot.
There is nothing like https://docs.oracle.com/javase/7/docs/api/java/sql/Statement.html#getMoreResults().

I forgot that in trunk, there is https://github.com/rusqlite/rusqlite/blob/master/src/lib.rs#L859-L875

I forgot that in trunk, there is https://github.com/rusqlite/rusqlite/blob/master/src/lib.rs#L859-L875

I forgot that in trunk, there is https://github.com/rusqlite/rusqlite/blob/master/src/lib.rs#L859-L875
So you can manually iterate on your batch.
And you can use column_count to detect SELECT.

I forgot that in trunk, there is https://github.com/rusqlite/rusqlite/blob/master/src/lib.rs#L859-L875
So you can manually iterate on your batch.
And you can use column_count to detect SELECT.

Sorry I'm a beginner and do not understand much.
I got error:
use rusqlite::{Batch, params, Connection, NO_PARAMS};
               ^^^^^ no `Batch` in the root

Sorry I'm a beginner and do not understand much.
I got error:
use rusqlite::{Batch, params, Connection, NO_PARAMS};
               ^^^^^ no `Batch` in the root

No worry!
The Batch feature is not released yet. So you will have to use rusqlite = { git = "https://github.com/rusqlite/rusqlite" } until a new version is released.

No worry!
The Batch feature is not released yet. So you will have to use rusqlite = { git = "https://github.com/rusqlite/rusqlite" } until a new version is released.

Thanks a lot, it works!
    let sql = r"
        CREATE TABLE users (name TEXT, age INTEGER);
        INSERT INTO users VALUES ('1: Alice', 1);
        INSERT INTO users VALUES ('2: Bob', 2);
        SELECT sqlite_version();
        SELECT sqlite_version(), * FROM users limit 2;
         ";

    let mut batch = Batch::new(&conn, sql);
    let mut cix = 0;
    while let Some(mut stmt) = batch.next()? {
        cix = cix + 1;
        let mut ros = stmt.query([])?;
        while let Some(row) = ros.next().unwrap() {
            let c = row.column_count();
            println!("count: {:?}  {:?} ", cix, c);

        }
    }

Thanks a lot, it works!
    let sql = r"
        CREATE TABLE users (name TEXT, age INTEGER);
        INSERT INTO users VALUES ('1: Alice', 1);
        INSERT INTO users VALUES ('2: Bob', 2);
        SELECT sqlite_version();
        SELECT sqlite_version(), * FROM users limit 2;
         ";

    let mut batch = Batch::new(&conn, sql);
    let mut cix = 0;
    while let Some(mut stmt) = batch.next()? {
        cix = cix + 1;
        let mut ros = stmt.query([])?;
        while let Some(row) = ros.next().unwrap() {
            let c = row.column_count();
            println!("count: {:?}  {:?} ", cix, c);

        }
    }

let mut batch = Batch::new(&conn, sql);
while let Some(mut stmt) = batch.next()? {

you should use column_count to either call execute or query
if stmt.column_count() == 0 {
   stmt.execute([]);
   continue;
}

    let mut ros = stmt.query([])?;
    while let Some(row) = ros.next().unwrap() {
        let c = row.column_count();

let mut batch = Batch::new(&conn, sql);
while let Some(mut stmt) = batch.next()? {

you should use column_count to either call execute or query
if stmt.column_count() == 0 {
   stmt.execute([]);
   continue;
}

    let mut ros = stmt.query([])?;
    while let Some(row) = ros.next().unwrap() {
        let c = row.column_count();

let mut batch = Batch::new(&conn, sql);
while let Some(mut stmt) = batch.next()? {

if there is a division by teams,
can I find out the name of the current command?
let name = stmt.get_command_name()?;

(select,create,insert,..)

expanded_sql, no ?


namespaces with numbers fail

when namespaces are a number (e.g. "namespace":"973585995"), the quotes around the config are removed after changing contexts using KubeContext
kube config before using KubeContext
contexts:
- context:
    cluster: somecluster
    namespace: "973585995"
    user: someuser
  name: somename

kube config after using KubeContext
contexts:
- context:
    cluster: somecluster
    namespace: 973585995
    user: someuser
  name: somename

resulting in the following error:
$ kubectl config get-contexts
error: Error loading config file "/Users/mark/.kube/config": v1.Config.Contexts: []v1.NamedContext: v1.NamedContext.Context: v1.Context.Namespace: ReadString: expects " or n, but found 9, error found in #10 byte of ...|mespace":973585995,"|..., bigger context ...|ext"},{"context":{"cluster":"somecluster","namespace":973585995,"user":"someuser"},"name":"somename"},{"c|...

@mark-armstrong sorry for late reply.
I could reproduce and found the root cause of the problem which is a (fixed) bug in the library we are using: https://github.com/jpsim/Yams/issues/263
Updated to latest version and verified that issue is fixed.

love the app and appreciate the follow up, thanks @turkenh


About mask decoding

Regarding the number of object queries, it seems to be inconsistent with what is expressed in the article.

Thanks for your interest in our work. Since multimask_output is set to False during mask_decoder forward, we only use the primary mask output, and the other multitask outputs are not utilized during training or inference. You can also set num_multimask_outputs to 0 as it is not needed.


Add support for resume state in sidelining

testing 1 2 3

22323

I know you have a doc somewhere, but it may be helpful to updatethe PR description with clear definitions of all the states and what they mean.

This PR will need a README overhaul, I'd like to work on that in a separate PR.

I want to add the validation mentioned by StevieP but I'd like to do it in a separate PR as part of the work on #75 as I think it'll be easier to address when that interface allows saving partitions together.


Hints like unused_local_variable missing from linter docs

Describe the issue
https://dart-lang.github.io/linter/lints/index.html
https://dart-lang.github.io/linter/lints/unused_local_variable.html - 404 error

unused_local_variable is not a Lint defined in the linter, but a Hint (more like a Warning) defined in the SDK. See https://dart.dev/tools/diagnostic-messages#unused_local_variable.

CC @bwilkerson. I think you discussed a common diagnostics location, on another issue.

Maybe if there is was some indication in the dart analyze output that says whether a rule is a lint or a diagnostic it would be less confusing

Confusion abounds. :-(
A diagnostic is an indication of a problem in the code. A lint is a diagnostic that is disabled by default.
The fact that lints are implemented in the linter package while every other kind of diagnostic is implemented in the analyzer package is an implementation detail that shouldn't be visible to users. Unfortunately, because of where we've put the documentation for lints, it becomes somewhat visible.

Maybe if there is was some indication in the dart analyze output that says whether a rule is a lint ...

I'm not sure whether that would be a good thing or not. Ideally the user shouldn't need to know which are from lints. Of course, the current state is not ideal, so ... :-/
But I will point out that dart analyze includes, as part of its output, the URL of the documentation for every diagnostic that has documentation. You should be able to use that URL to navigate to the documentation without needing to think about whether the diagnostic was generated by a lint or not.

Yes, we've discussed moving the lint documentation to the same location as the other diagnostics. Not sure whether it's a good idea (especially given the evidence that some users are very familiar with the current location)

The fact that lints are implemented in the linter package while every other kind of diagnostic is implemented in the analyzer package is an implementation detail that shouldn't be visible to users. Unfortunately, because of where we've put the documentation for lints, it becomes somewhat visible.

imo if this is an implementation detail that users aren't meant to see, i think it would be better if the documentation was moved even if there are some users used to the current state

But I will point out that dart analyze includes, as part of its output, the URL of the documentation for every diagnostic that has documentation. You should be able to use that URL to navigate to the documentation without needing to think about whether the diagnostic was generated by a lint or not.

is there an argument i need to pass to enable for this? i'm not seeing any urls in the output:
>dart analyze
Analyzing project...

  error • lib\screens\foo.dart:13:11 • The value of the local variable 'foo' isn't used. Try removing the variable or using it. • unused_local_variable
  error • test\widget_test.dart:10:8 • Target of URI doesn't exist: 'package:project/main.dart'. Try creating the file referenced by the URI, or Try using a URI for a file that does exist. • uri_does_not_exist
  error • test\widget_test.dart:15:35 • The name 'HomeRoute' isn't a class. Try correcting the name to match an existing class. • creation_with_non_type
   info • lib\screens\foo.dart:5:7 • This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: ReportRoute.report, ReportRoute.onSave • must_be_immutable

4 issues found.

i know there are documentation links when you hover over the warnings in the IDE, but i think they should also be present in the dart analyze output like you said, especially if it's not obvious where to look for said docs

I thought it was the default behavior, but it appears that you need to include the --verbose flag in order to get that information. FWIW, I consider that to be a bug.
dart analyze
   info • lib/test.dart:2:7 • The value of the local variable 'x' isn't used. Try removing the variable or using it. •
          unused_local_variable

dart analyze --verbose
   info • lib/test.dart:2:7 • The value of the local variable 'x' isn't used. Try removing the variable or using it. •
          https://dart.dev/diagnostics/unused_local_variable

CC @parlough and @pq was this resolved recently?

I think the core issue here is that linter rules are treated differently by the analyzer from other diagnostics. To solve this, we're currently working on adding consistent diagnostic documentation for linter rules to the same location and in the same format as other diagnostics.
We're tracking that work in https://github.com/dart-lang/site-www/issues/4498 among other issues, so perhaps this issue can be closed in favor of those.


Learn and implement arrays

Learn about static arrays and dynamic arrays

This issue is now closed because I was able to learn about the array data structure and implement it with acquired knowledge.


Max Width

Is there a max size on the Svg component? I can't seem to get it any larger than 1365, and I was wondering why this is (or if there's anything I can do to get rid of the restriction).

Darn, I found out this bug too right now. Seems there's a critical performance issue with large graphics, even with a simple Circle and its RadialGradient fill (as in my case).

+1
Defect found on Sony Z3 Android phone.
Defect not present on Samsung S7 phone.

+1  On iOS Simulator

Use a device with more memory available, or decrease the size of your canvas, the bytes need to be stored somewhere.


Reinitialize package

Update CI and dependency management to new organizational standards

This PR only changes the outer structure, it doesn't touch the code itself.
I'm going to merge with all the failing lints because most/all of the code is about to be replaced.


[Doc] Update en of features and architecture

Why I'm doing:
What I'm doing: add shared-data architecture and features, align the capitalization of properties in create commands
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[x] Doc
[ ] Tool

Does this PR entail a change in behavior?

[x] Yes, this PR will result in a change in behavior.
[ ] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[x] 3.1
[ ] 3.0
[ ] 2.5

@mergify rebase


Use quickstart for e2e environment setup

Why
Quickstart is used to setup the environment for release testing
Quickstart is used to setup the environment for new users
Quickstart is (mostly) used for folks doing development
Using it to setup the environment for e2e test will mean any issues will be identified.
What
Update the e2e ci to use quickstart script for environment setup.
Update the quickstart to allow for use with any provider, and for that to be specified via an env or similar
Scale down the controller that comes with the quickstart
Remove the local-setup code?

This issue is stale because it has been open for 60 days with no activity.

This issue was closed because it has been inactive for 30 days since being marked as stale.


/accounts//trades broken

does not show sold_amount, sold_asset_type, bought_amount, bought_asset_type, offer_id

This has been fixed in the horizon side: https://github.com/stellar/go/pull/417
Needs to be re-implemented in laboratory


Do not use a dict as intermediate format and use Sockets directly

Simplify code and remove side effects from sharing a mutable container.

I'm ok with this change as long as we are a bit more proactive with the checks. Let's add a check in add_component to make sure the instance is not present already in the graph and returns a meaningful error to the user. Otherwise this can cause hard-to-trace bugs imho, because it doesn't fail but just causes side effects.

Let's add a check in add_component to make sure the instance is not present already in the graph

We can do this in another PR, I just fixed the tests because they were wrong and I stumbled upon them working on the refactoring


Fix NWChem links

The current document has links points to a website that is has been bought by cyber-squatters to advertise questionable software.
I have updated the link with the current website https://nwchemgit.github.io/
This is the same as https://github.com/MicrosoftDocs/quantum-docs/pull/619, plus a second link update

@Bradben
Can you review the proposed changes?


Compilation error from git - same as issue #797

Dear all,
I got the same issue as #797 ? Does anyone know how to resolve it?
I got it on 3 separate machines, Win7 x64, centos x64, and ubuntu 14  server x64, when installing from my own git(vykhand/xgboost) and from dmlc as well. I fetched changes to my own git just now and tested it again. No luck.
Here are the commands I am running :

Here is the error message :

Drat installation works. But would like to install form github in order to test changes to R package

You can follow the manual clone , but with an recursive option

@hetong007 @thirdwing Maybe we should consider remove intstall_git instruction, which seems does not include recursive cloning as well, but instead give an instruction to do recursive clone and install manually

That should be removed. CRAN version and drat version should be enough for R users.

On Feb 23, 2016, at 12:08 PM, Tianqi Chen<EMAIL_ADDRESS>wrote:
@hetong007 https://github.com/hetong007 @thirdwing https://github.com/thirdwing Maybe we should consider remove intstall_git instruction, which seems does not include recursive cloning as well, but instead give an instruction to do recursive clone and install manually
—
Reply to this email directly or view it on GitHub https://github.com/dmlc/xgboost/issues/821#issuecomment-187794685.

This instruction is for developers like @vykhand who like to test their local changes

@thirdwing can you help adding this advanced build instruction? Thanks!

Hi @tqchen, what do you mean by "You can follow the manual clone , but with an recursive option", can you point me to some step-by-step to do this?

Hi, @vykhand ,
Please try the following lines:
git clone --recursive https://github.com/dmlc/xgboost
cd xgboost
make Rbuild
R CMD INSTALL xgboost_0.4-3.tar.gz

Hi @thirdwing, thank you, that worked!


Throw error when trying to format unknown language

When the language parameter is anything else than "n2ql" or "db2" then we should throw an error indicating  that given language is unsupported.

Related code in XRebel: https://bitbucket.org/zeroturnaround/xr-agent/commits/638ddbdb5e7625a7186dbe3dea349c33d9568f61

@nene It is not cool to reference ZT internal repository like this on an open-source project. :-P

Sorry @nemecec that you can't access it. But you're welcome to come to the office and I can walk you through that part of the code :)

:-D

Just a few weeks later, and I managed to publish it :)


Fixed matchAny so that all methods are matched, ...

... not just standard methods
See: https://github.com/scotty-web/scotty/issues/196

Coverage increased (+0.3%) to 57.975% when pulling e8a812b8c6fa1138f96fb070a7c3da1219d11a1c on taphu:matchAny into cd713b14b560bf0168bd5dd8955d0e35fb84f329 on scotty-web:master.

Coverage increased (+0.3%) to 57.975% when pulling 34edb8e35498799db348ae4abfa35164fa95e832 on taphu:matchAny into cd713b14b560bf0168bd5dd8955d0e35fb84f329 on scotty-web:master.


Verify scopes are non-empty for Google service accounts + DWD

Address this comment.

Ping @patrick-codaio


Implement a compiler to C++, and link to the existing runtime

This set of commits implements a compiler from Lean's expression type to C++. This is still very much a prototype and needs more testing and features.
I am opening this pull request now, even though it is not done because I was able to write and successfully link a few example programs with IO, and it would be great to merge it now. I am working on finishing a POPL submission, and will probably be less free in the coming weeks.
I would also appreciate getting some code review, and general feedback since I'm pretty rust-y at C++.
I have a couple more things I want to add before its merged, but would like to start the conversation in a structured fashion, and not just over email.
In terms of specifics of this patch, @leodemoura it would be great to get some feedback on the runtime, since I believe I found some bugs. I "fixed" a few of them, but have questions about a couple more, and will comment on the appropriate code below.
My future wish list for this is:

user provided optimizations in the form of proofs
a rich typed pointer API for interacting with foreign code
a structured mechanism for reasoning about partiality
lots of optimizations both on expr and the simple_expr level
runtimes and code generators for different output languages (specifically Rust, since it would
allow verified code to interact with low-level systems code with stronger properties than C++)
possibly emitting LLVM IR

A couple issues I think are important to resolve before merging:

[ ] integrate running tests into the testing infrastructure
[ ] automatically select and invoke the compiler programmatically
[ ] clean up the emitted code
[ ] add a bunch more tests
[ ] add more configuration

I'll try to address the above issues tomorrow if time permits.
Also shoutout to @lukenels who I bounced a bunch of ideas at, and who helped with some of the IO code.

Nice! I love that it already supports monadic IO.
May I ask why you decided on C++ as the (first) target language? Even with the runtime being shared with lean3's VM, I would have assumed a 'managed' language like OCaml to be a much easier target. I suppose it would be interesting to have both at some point and compare their performance.

@Kha I met with Leo sometime last month, and it seemed that he was interested in generating C++ code coupled with my interest in being able to model and program against low level system APIs.
Another goal of mine was to design this like a compiler and not an extraction mechanism. I didn't want to copy Coq's approach since frankly its not very robust, and configurability comes in the form of stringly typed code. I want to take more of GHC style approach and design APIs and optimizations that allow programmers performance and control without resorting to using string replacement.
With that said modulo a little bit of generalization it should be easy to write backends for other languages. Specifically I'm interested in targeting Rust, since I think it is a better candidate for implementing a safe, high performance runtime.

@jroesch Thanks for making the pull request.
I'm currently on vacation. I will be back next Saturday. I will integrate your changes as soon as I get back.
BTW, I will also merge your commits with the lean3 branch.
The efficient interpreter is showing signs of life in this branch.
Some of the preprocessing steps used in the interpreter may also be useful for C++ code extraction.

In terms of specifics of this patch, @leodemoura it would be great to get some feedback on the runtime, since I believe I found some bugs. I "fixed" a few of them, but have questions about a couple more, and will comment on the appropriate code below.

No problem. I will take a look when I get back.

@leodemoura sounds great, enjoy your vacation! there are a couple lurking issues that I will try to iron out before you get back, busy working on our POPL submission so may not find time this week, but will let you know.

Was just looking over the lean3 branch, looks like your infrastructure can replace some of the functionality I have. I should be able to use the computational irrelevance analysis, and inliner, if not more.
My current view is that we should do mark terms for erasure, do inlining on the expr representation, then lowering to the proc/simple_expr types I have, we can then do lower-level imperative optimizations, and output to C++ code or even LLVM if we are so inclined.

I looked around a little more tonight, and it seems that this whole chunk of code should be able to replace the first part of my backend: https://github.com/leanprover/lean/blob/3b47d91b3ed6486aa6d88fc67e17571a9db90ab2/src/library/compiler/preprocess_rec.cpp#L116.
I have my changes rebased on top of the lean3 branch, but the standard library doesn't build due to all the sorrys, and a couple of my tests rely on it.

Branch here: https://github.com/jroesch/lean/tree/lean3-cg.

@jroesch This is great. We can discuss the details and remaining issues when we meet in person.

Closing this PR in favor of my new one, which is also a WIP. https://github.com/leanprover/lean/pull/1090


We should provide backward compatibility.

I opened an issue about ansible 2.4 compliance before seeing that you already have this one. I've already close it, but you may find useful information in it.

Hello
I updated both ansible and molecule with pip, ended up with ansible 2.4 and molecule 2.1, wich broke my test due to molecule generated inventory including &id001, $id001, ...
I thought I'ld just paste my error log, so people might end up here googling.
[WARNING]:  * Failed to parse /opt/ansible-playbooks/roles/rgarrigue.python/mo
lecule/default/.molecule/ansible_inventory.yml with ini plugin: /opt/ansible-pl
aybooks/roles/rgarrigue.python/molecule/default/.molecule/ansible_inventory.yml
:6: Expected key=value host variable assignment, got: &id001

[WARNING]: Unable to parse /opt/ansible-playbooks/roles/rgarrigue.python/molec
ule/default/.molecule/ansible_inventory.yml as an inventory source

[WARNING]: No inventory was parsed, only implicit localhost is available

I'm actually tempted reverting this work all together, which was implemented in #921.  I don't think many people actually use it, and was on the fence about it since the beginning.
Importing data from an outisde ansible.cfg seems like a recipe for weird bugs, when molecule.yml allows the config to be customized.

yes, @retr0h you can revert it. looks like that general 'ansible.cfg' for providing pass to libraries and so on use I only.

@kharkevich how long before you would have a fix?  Just curious.

@retr0h I have a fix and I test it internally. So, I'll hope that i fix it today.

@kharkevich I am likely going to put the breaks on this feature.  We can discuss further.  However, the feature mostly goes against the way we want to modify Molecule's ansible.cfg.  Especially b/c it can introduce weird bugs from an external ansible.cfg.  Since Molecule supports configuring it's own ansible.cfg from molecule.yml, I'm going to ask that we continue to use that method.'
Closing this particular bug since the functionality was reverted in #977.

@retr0h Ok, let's get back to discus in #956, because one case of using external ansible.cfg - using dynamic inventory


Turn down repo archiving to 18 months

Background

We have been archiving repos for a while. We are now happy to turn this down to 1 year.
Acceptance Criteria

[ ] Archiving script updated

Reference
How to write good user stories

Changed this to 18 months and the 1 year list was quite large, will revisit in a few months.

Changed this to 18 months and the 1 year list was quite large, will revisit in a few months.


v2 emulation over v3

Still WIP; rough around the edges and I would like to get discovery.etcd.io working. Interested in general comments.
This patch set:

changes v2http, etcdhttp to accept etcdserver.Server* interfaces instead of *EtcdServer
splits out store tests into whitebox/blackbox tests
implements store.Store using clientv3.Client
adds --experimental-enable-v2v3

Passes most blackbox Store tests. The watch tests fail expecting the 'Action' to be preserved, which would be expensive to emulate. However, v2http doesn't need the exact action, so the returned action can be relaxed to make it easier to emulate.
Currently untested with integration/e2e tests. etcdctl sort of works.


[Draft] Add speculative decoding

First attempt at adding speculative decoding! Discussed in #276
A few things to note

It does not support models with different tokenizers, this feels pretty hard to achieve
It does not currently support vectorised prompt inputs or multiple samples, this probably could be achieved but not sure how desirable since speculative decoding already uses up a lot of parallel resources
I have tried to make it work for arbitrary sequence so including regex etc. But in a quite hacky way where I reproduce an instance of the received sequence. I think this could be greatly simplified/improved

I realise now that I have coded parallel_multi_step in a silly overkill way and all of the pseudo-prompts are not needed! For a transformer you can get logits for the whole previous sequence with just a single call to the model 🤯. Might need to go into the hidden_state of the transformer output to extract this and also would need to think about how to do so in a way that conforms to arbitrary outlines sequences (regex etc)

It does not support models with different tokenizers, this feels pretty hard to achieve
It does not currently support vectorised prompt inputs or multiple samples, this probably could be achieved but not sure how desirable since speculative decoding already uses up a lot of parallel resources

Yeah, don't worry about these for now.  We can follow up in later PRs.

Oh, don't forget to set up pre-commit locally!

Just made a relevant update to the interface in https://github.com/outlines-dev/outlines/pull/318.


Makefile: Remove run target

What have you changed?
I've removed the run target in Makefile, as @siddontang suggested, since it won't work anyway.
What is the type of the changes?

Bugfix (a change which fixes an issue)

How is the PR tested?
There's no need for testing.
Does this PR affect documentation (docs) or should it be mentioned in the release notes?
No.
Does this PR affect tidb-ansible?
No.

PTAL @overvenus

PTAL @breeswish

@siddontang Are tests stuck?

/merge


Harmonise use of the word "process" in labels and definitions

Description of the issue
From PR #1256:
Some energy transformation processes contain the word "process" in the label and the definition while others do not. This should be harmonised.
Ideas of solution
If you already have ideas for the solution describe them here
Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[ ] I already read the latest version of the workflow for this repository
[ ] The goal of this ontology is clear to me

I am aware that

[ ] every entry in the ontology should have a definition
[ ] classes should arise from concepts rather than from words

I am not sure whether we should add "process" to all energy transformations. However, I see that it might be useful to add "process" to all classes that contain the word "generation". This makes a clear distinction from process attributes and quantity values which also contain the word "generation".
So I suggest to relabel combined heat and power generation to combined heat and power generation process.
We might think about adding the terms without "process" as alternative labels. This would be:

electricity generation to electricity generation process
fuel-powered electricity generation to fuel-powered electricity generation process
combined cycle electricity generation to combined cycle electricity generation
heat generation to heat generation process

For other energy transformation subclasses I currently do not see the need to add "process" in the label.

@stap-m : Any thoughts on my last comment?

Agreed. Ready for implementation?

I'll implement 🚀


[Bug] Cannot generate ore patches high in the sky

Minecraft Version

1.16.5

Forge Version

1.16.5-forge-36.2.23

Mod Version

OreTweaker-1.16.5-2.6.0

Describe the bug

I recently started tweaking ores with OreTweaker but when I wrote this JSON file it didn't worked as intended (nothing is generated)
{
"oreConfig": [
{
"ore": "minecraft:stone",
"filler": "minecraft:air",
"minY": 200,
"maxY": 250,
"maxVeinSize": 32,
"spawnRate": 5.0,
"biomeBlacklist": [],
"biomeWhitelist": ["OVERWORLD"]
}
]
}
normally this is meant to generate stone patches high in the sky but it seems there is a y-level cap for the mod to generate ores (I tried with minY=1 and maxY=250 and the highest patch found was at y=105

How to reproduce

Just type the code in a JSON file and run the game

Link to crashlog [If Applicable]

There is no crash-log

Screenshots / Images

Its a limitation to the vanilla Minecraft world generator they made for performance reasons.
For them there is no reason to attempt to generate a ore in a place where there is no other world generation going on (the sky).
Therefor you are currently unable to generate any ores floating high up in the sky..
I can look into creating my own custom generator that would allow you to do this but this might take a little while to get fixed.

It would be so helpful to be able to generate "clouds" made out of ores in the sky, early thanks if you decide to create it

Moved to discussions: https://github.com/EwyBoy/OreTweaker/discussions/66


[AutoPR] engagementfabric/resource-manager

Created to accumulate context: engagementfabric/resource-manager

Closing PRs that have been open for more than 1 month.


Support HTMLElement Type Checking

Type checking of Element access is currently not implemented.
when aurelia-pal-nodejs is implemented (tracked issue), we  can use jsdom to create a HTMLElement in memory, based off the tag. Then we can compare the access chain against the actual object.

I honest cannot remember where I saw this kind of usage (where you bind directly to a DOM tree object). Will close for now.

I guess You don't mean the opposite case where ref is bound to field using ref attribute?

I thought I saw an example where you could bind to some DOM element/method, but I cannot find anything to confirm that. I'll reopen if someone shows me an example; otherwise I'll assume I was wrong.

Did you mean @children decirator to bind DOM element to viewmodel?


Setup configuration file spec

Overview
This PR adds configs modules for setting up the main configuration file data validation and settings management.
The fields are based on the original master configuration file. This PR uses pydantic technology to define the configurations.
@johnbdesanto could you go through the descriptions and ensure that I have the accurate text for the fields? Please focus on the solver configuration. Also, if you have another name for this too, please let me know.
Original
2022-09-28 00:00:00
3
     0    08       45.302064471    -124.978181346   -1176.5866      0.200000d0       1481.551
     1    12       45.295207747    -124.958752845   -1146.5881      0.320000d0       1481.521
     2    22       45.309643593    -124.959348875   -1133.7305      0.440000d0       1481.509
6378137.d0<PHONE_NUMBER>01d0   ! ellipsoid parameters  WGS84
0.05d0               ! Maximum GPS positional sigma (m)
0                   ! Input GPS positional uncertainties given as: if std. dev. = 0, if var. = 1
n                   ! Constrain buoy-buoy baselines
y                   ! Hold PXP geometry and orientation fixed
n                   ! Hold PXP baseline lenghts fixed
n                   ! Hold ellipsoid heights constant
n                   ! Constrain PXP to move together vertically
n                   ! Estimate body frame offsets
n                   ! Compute residuals only
0                   ! Correction to tabluated acoustic times (sec.)
-26.59d0           ! Geoid undulation at sea surface point
0                   ! =0 scale factor, =1 1-D ray trace
1.d-10              ! xacc tolerance for ray trace bisection
45.3023d0 -124.9656d0   ! Latitude/Longitude array center (decimal degrees)
1.d-10              ! Variance (s**2) of PXP two-way travel time measurement
0.0d0               ! Transponder Wait Time (seconds); ship/SV3 = 0.0s, WG = 0.1s

Updated sample
site_id: NCL1

solver:
  transponders:
    - lat: 45.302064471
      lon: -124.978181346
      height: -1176.5866
      internal_delay: 0.200000
      sv_mean: 1481.551
    - lat: 45.295207747
      lon: -124.958752845
      height: -1146.5881
      internal_delay: 0.320000
      sv_mean: 1481.521
    - lat: 45.309643593
      lon: -124.959348875
      height: -1133.7305
      internal_delay: 0.440000
      sv_mean: 1481.509
  reference_ellipsoid:
    semi_major_axis: 6378137.000
    reverse_flattening:<PHONE_NUMBER>01
  gps_sigma_limit: 0.05
  std_dev: true
  geoid_undulation: -26.59
  bisection_tolerance: 1e-10
  array_center:
    lat: 45.3023
    lon: -124.9656
  travel_times_variance: 1e-10
  transponder_wait_time: 0.0

Related issues

#19
#21

First, the trivial thing: change "transpoder_wait_time" to "transponder_wait_time".
There is an argument to be made that the sv_mean variable is not needed. Although it is given in the master file, if you look through the proc_sfgsolve_center_WG.csh script you will find that one of the things the software does before calling the sfgsolvvm executable is it recalculates the harmonic mean sound velocity for each transponder. This is done by calling the proc_harmonic_mean_2_sfg_file.csh script with the sound velocity input and transponder depths for each transponder, which then integrates the sound velocity profile from the seafloor depth to the surface using the executable cal_sv_harmonic_mean. The source code for this is found in src/cal_sv_harmonic_mean. Since this is something we should calculate anyway we don't need to ask a user to run the calc as long as they provide a sound velocity profile. (and if they don't have an svp then we could use a default value for the mean sv like 1500 m/s.)
The std_dev and bisection_tolerance values may also be unnecessary, although I suppose it depends on how we choose to build out the code.

First, the trivial thing: change "transpoder_wait_time" to "transponder_wait_time".

Looks like it is that way in the code. I must have misspelled that in the example above.
@johnbdesanto  Are you able to see the code view (https://github.com/uw-ssec/offshore-geodesy/pull/57/files)?

This is done by calling the proc_harmonic_mean_2_sfg_file.csh script with the sound velocity input and transponder depths for each transponder, which then integrates the sound velocity profile from the seafloor depth to the surface using the executable cal_sv_harmonic_mean.

Great! I will remove that. I see that this calculation will need to happen at the start of the process.

The std_dev and bisection_tolerance values may also be unnecessary, although I suppose it depends on how we choose to build out the code.

For now I will leave this be until I get a handle on the processes that uses these values.

@carlosgjs Please quickly review this and see if there are anything that stands out to you that I need to fix. Note that I don't have tests for this part yet. I'll do that in a separate PR. Thanks!

@johnbdesanto I've now made sv_mean to be an optional field that will be filled in during the process after sound speed velocity has been calculated. See https://github.com/uw-ssec/offshore-geodesy/pull/57/commits/72e720eaec3f63c5cb6084ab672f8bb8747477fe.


Added excel api to get data from OTE

Implement Excel API to get data from excel sheet. Could be interface as HTML or Excel get the common data structure.

The excel api implemented and tested


Pylance intellisense does not highlight object methods in case of its creation with different arg types

Environment data

Language Server version: 2021.9.3 (pyright d2771b18)
OS and version: Ubuntu 20.04
Python version (& distribution if applicable, e.g. Anaconda): 3.7

Code Snippet / Additional information
Assume class DecisionEngine, which creates an instance of DBClient, passing an integer instead of string as specified below:
class DBClient:

    def __init__(self, param: str):
        self.param = param

    async def setup(self):
        pass

class DecisionEngine:

    def __init__(self):
        self.db: DBClient = None

    async def setup(self):
        self.db = DBClient(1)
        await self.db.setup()

Expected behaviour
at setup method of DecisionEngine class it is possible to drill down into setup method of db object:

Actual behaviour
it interprets db object as Any type

despite the fact that it is correctly recognize the type of db object at upper line of code

This seems like a bug in some async handling, at least in the hover; repeat the same thing and I get:

Making setup return something lets me see:

First, there's a type error in the sample above. The expression DBClient(1) isn't valid because the constructor for DBClient accepts a str, not an int. If you enable type checking, this error will be flagged.
Second, I'm not able to repro the behavior you're seeing @jakebailey. I can't see all of your code, so perhaps there are differences? Where is the value of 1234 coming from? Here's what I see:

from typing import Optional

class DBClient:
    def __init__(self, param: str):
        self.param = param

    async def setup(self):
        pass

class DecisionEngine:
    def __init__(self):
        self.db: Optional[DBClient] = None

    async def setup(self):
        self.db = DBClient("1")
        reveal_type(await self.db.setup())

The code I have is this:
class DBClient:
    def __init__(self, param: str):
        self.param = param

    async def setup(self):
        return 1234

class DecisionEngine:
    def __init__(self):
        self.db: DBClient = None

    async def setup(self):
        self.db = DBClient(1)

        self.db.setup()
        await self.db.setup()

        reveal_type(self.db.setup())
        reveal_type(await self.db.setup())

Revealing the type produces the right result, but try hovering on db inside of the await and compare it to outside of the await. Hovering on it within reveal_type also says it's Any.

I did a bit of debugging, and our hover code sees that it's a name node, then asks for declarations from the type evaluator, but when it does getType, it returns undefined. (That's as far as I went to debug before seeing it was going to be an evaluator thing.)

First, there's a type error in the sample above. The expression DBClient(1) isn't valid because the constructor for DBClient accepts a str, not an int. If you enable type checking, this error will be flagged.
Second, I'm not able to repro the behavior you're seeing @jakebailey. I can't see all of your code, so perhaps there are differences? Where is the value of 1234 coming from? Here's what I see:

from typing import Optional

class DBClient:
    def __init__(self, param: str):
        self.param = param

    async def setup(self):
        pass

class DecisionEngine:
    def __init__(self):
        self.db: Optional[DBClient] = None

    async def setup(self):
        self.db = DBClient("1")
        reveal_type(await self.db.setup())

I didn't see any type error at VS Code, why?

@wvolkov Type checking isn't enabled by default in Pylance; you need to set python.analysis.typeCheckingMode or set it in a pyrightconfig.json.

Ah, so fixing the type error fixes this. That's interesting.

I'm not really sure why that would be the case, if reveal_type gets the right answer, and it works here:

Yes, good catch. There is a bug here that causes the hover type for self.db to appears as Unknown even though it is eventually resolved to DBClient. The problem is that the logic that evaluates the type for the await statement was not honoring the "incomplete" flag and was marking the type evaluation for itself as completely resolved. A fix for this bug will be included in the next release.

This issue has been fixed in version 2021.9.4, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/main/CHANGELOG.md#202194-29-september-2021


Metadata listing in DPUL does not completely reflect options for South Asian Ephemera

DPUL seems to be missing:
Translit title
Geo subject
am I missing them?

Geo Subject is coming through as coverage, Transliterated Title is certainly not coming through.


Cannot run Vitest UI with Vue

Describe the bug
When trying to open Vitest UI in StackBlitz, a blank screen appears instead. The console log shows:
Uncaught SyntaxError: The requested module '/node_modules/.vite/deps/vue.js?v=ac2f29cf' does not provide an export named 'createElementBlock' (at App.vue:2:35)

This does not happen locally.
Link to the blitz that caused the error
https://stackblitz.com/edit/vue-vitest-mock-module-function-nrzcsw?file=package.json,.stackblitzrc
Steps to reproduce

Go to linked blitz.
Observe the blank screen appears in the preview window.
Observe the error message in the browser's console.

Expected behavior
Vitest UI works normally like it does for non-Vue projects. https://vitest.new opens Vitest UI just fine, but that's a vanilla JS project.
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
No response
Platform
Browser name  = Chrome
Full version  = 100.0.4896.88
Major version = 100
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.88 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 68709055,
  "usedJSHeapSize": 64111911,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Hash = 5428dc6786c976e0e08fde1105586a722833c4ef

Additional context
No response

Hey 👋 Thanks for reporting this issue. I tried to reproduce this with the link you provided and was successful in doing so. I have also tested this locally and it works as well. I am not sure why that happens in WebContainer but not locally.

Curious, can this be solved if the dependencies are updated? 🤔

Hey! I just wanted to let you know that if you visit manually __vitest__/ in your preview it works.
If you want to make sure that this path is always opened in the preview you can add the initialPath query parameter like so:
https://stackblitz.com/edit/vue-vitest-mock-module-function-nrzcsw?file=package.json,.stackblitzrc&initialPath=__vitest__/
I'm going to close this issue for now, let us know if you run into any other issues! :smiley:


Improve documentation for Gantt charts

Description
The Gantt chart documentation in docs/manuals/gui/viselements/charts/gantt.md is difficult to understand. Notably:

Definition of the task duration is confusing.
The resolution of the image (docs/manuals/gui/viselements/charts/ganttlike1.png) is too low to be readable. This made it hard for me to reverse engineer and figure out what the code was doing.

Expected change

Improve the description for defining a Gantt chart. Perhaps have each line begin with the name of the "parameter". Be clear with how task durations are defined (as the offset from 1970-01-01).
Increase the resolution of the attached image.

I hope things are clearer now in the User Manual/GUI/Visual Elements/Charts/Gantt section...


Add projects config validation

Summary
Closes #9761.
Test plan
Unit tests added.

@jeysal

Codecov Report

Merging #9767 into master will increase coverage by 0.01%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##           master    #9767      +/-   ##
==========================================
+ Coverage   64.90%   64.91%   +0.01%
==========================================
  Files         288      288
  Lines       12198    12202       +4
  Branches     3025     3027       +2
==========================================
+ Hits         7917     7921       +4
  Misses       3640     3640
  Partials      641      641

Impacted Files
Coverage Δ

packages/jest-config/src/normalize.ts
76.92% <80.00%> (+0.25%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update edf8c0a...3b6eefc. Read the comment docs.

Hey, @SimenB anything wrong with this PR? If it needs some changes I can do it.

No, I think this is good to go. @jeysal?
My only comment is that I'd like to solve this a bit more generally than just for testSequencer, but I'm not sure how that would look so we can definitely land this for now 👍

I do think we should make this validation more generic - even if we don't have the beautiful io-tsish config validation mechanism we'd like at the moment, I think this is rather easily achievable. We have groupOptions inside jest-config - we can apply that to the project entry, take the projectConfig from the result, and throw if the globalConfig from the result contains anything.

I think I'd like to solve this via #11963 (and then validating the output as well). Thanks for the PR though! (and help with the schema is very much welcome)


Remove values from string cache

@raviqqe dashmap includes a dashset, which might be more fit for this

Yeah, I tried to use it but somehow it doesn't .entry() equivalent method. Do you think we can do atomically without it?


Compressed vertex/index mesh buffers

We haven't managed to figure out how it's compressed so far.

These files exist in Dota 2 too now.

Got a reply from Valve, they use https://github.com/zeux/meshoptimizer


Crash with "Ursache 4000"

Describe the bug
After restarting the phone and clicking on cwa, immediately crash report appears on my phone.
See details in screenshots

Expected behaviour
no crash
Steps to reproduce the issue
not reproducable
Technical details

Mobile device: HUAWEI P30 lite
Android version: <IP_ADDRESS>

Possible Fix
Additional context

Thanks for your bug report. this comes due to a UnknownHostException that could have happened due to a network reset or a problem during the establishment of the connection. This is not a real "crash" and will not affect App functionality once your standard internet connectivity is restored. Sometimes this can be caused when your phone is connected to WiFi but your WiFi has no connectivity towards the internet.


ESLint

I guess this is more of a suggestion than an issue per se - but, after a weekend of hacking on Lexical, Payload, and some of the plugins you've created here, I think it might help in terms of overall code quality if you followed the Payload ESLint setup - https://github.com/payloadcms/payload - or even the eslint-config-standard-with-typescript module.
Payload even have their own npm package @trbl/eslint-config and so you could just drop their  .eslintrc.js into the project.
There were a few other things I noticed that I'd be glad to lend a hand with if you fancied chatting.

I thiink their ESLint setup is subject to change, as they probably want to switch to a prettier setup eventually. Payload is also using a completely different eslint setup for one of their official plugins vs. their main repository.
So, might make sense to either wait or switch to something like the airbnb ESLint config over giving up prettier


feat:add logging

there are a few issues with the implementation that we need to discuss offline. setting on hold for now


add hardLine to force line breaks

close #76
The inspiration here was to split #117 into two. The first part was #176 which we could add without relaxing laws. This is the second part which exposes the ability to make hardLine documents.
We only removed two laws:

Line never appears other than on the left of FlatAlt. This is obvious since it is the feature we are adding.
Union(a + b, a + c) == a + Union(b, c) is only true if a contains no hardLines.

We found a simpler, but very similarly performing implementation (sometimes faster sometimes a bit slower) of fill which was easier to reason about and allowed us to not have to give up that combinator. Here are the benchmarks. The x suffix means the previous implementation:
[info] Benchmark                 (size)   Mode  Cnt     Score     Error   Units
[info] PaigesBenchmark.fill0          1  thrpt   10  6506.563 ± 189.848  ops/ms
[info] PaigesBenchmark.fill0         10  thrpt   10   605.373 ±  17.366  ops/ms
[info] PaigesBenchmark.fill0        100  thrpt   10    63.641 ±   0.662  ops/ms
[info] PaigesBenchmark.fill0       1000  thrpt   10     6.344 ±   0.041  ops/ms
[info] PaigesBenchmark.fill0      10000  thrpt   10     0.625 ±   0.007  ops/ms
[info] PaigesBenchmark.fill100        1  thrpt   10  6530.974 ± 240.346  ops/ms
[info] PaigesBenchmark.fill100       10  thrpt   10   631.062 ±  10.576  ops/ms
[info] PaigesBenchmark.fill100      100  thrpt   10    47.490 ±   0.323  ops/ms
[info] PaigesBenchmark.fill100     1000  thrpt   10     5.010 ±   0.036  ops/ms
[info] PaigesBenchmark.fill100    10000  thrpt   10     0.535 ±   0.015  ops/ms
[info] PaigesBenchmark.fillx0         1  thrpt   10  6041.646 ±  38.923  ops/ms
[info] PaigesBenchmark.fillx0        10  thrpt   10   657.951 ±  43.749  ops/ms
[info] PaigesBenchmark.fillx0       100  thrpt   10    63.629 ±  17.652  ops/ms
[info] PaigesBenchmark.fillx0      1000  thrpt   10     7.019 ±   0.452  ops/ms
[info] PaigesBenchmark.fillx0     10000  thrpt   10     0.709 ±   0.016  ops/ms
[info] PaigesBenchmark.fillx100       1  thrpt   10  6029.988 ± 358.575  ops/ms
[info] PaigesBenchmark.fillx100      10  thrpt   10   623.129 ±   4.476  ops/ms
[info] PaigesBenchmark.fillx100     100  thrpt   10    44.471 ±   3.276  ops/ms
[info] PaigesBenchmark.fillx100    1000  thrpt   10     5.174 ±   0.208  ops/ms
[info] PaigesBenchmark.fillx100   10000  thrpt   10     0.559 ±   0.003  ops/ms

This does not make flatten and flattenOption private. Maybe we should. But it does change the contract: there is no guarantee there are no newlines, the result may have hardLine in them. It may be better to just make them private. I don't know if anyone really needs them.
This was work @non and I did together, but highly based on the excellent pathbreaking work of @seanmcl.
cc @olafurpg @seanmcl

Codecov Report

Merging #181 into master will decrease coverage by 0.38%.
The diff coverage is 95.31%.

@@            Coverage Diff             @@
##           master     #181      +/-   ##
==========================================
- Coverage   97.84%   97.46%   -0.39%
==========================================
  Files           4        4
  Lines         279      315      +36
  Branches       27       38      +11
==========================================
+ Hits          273      307      +34
- Misses          6        8       +2

Impacted Files
Coverage Δ

core/src/main/scala/org/typelevel/paiges/Doc.scala
97.89% <95.31%> (-0.12%)
:arrow_down:

.../src/main/scala/org/typelevel/paiges/package.scala
0% <0%> (-100%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 21f0d09...6d4d87b. Read the comment docs.


Use pprof with serialized profiling session

If i'm not mistaken, Profile.getdict(data) should only work in the same process that the profiler was running.
In order to visualize a serialized session, one will need to pass in the lookup table as well!
(still need to test this, but didn't want this edit to get lost)

Probably, I have started to use PProf.jl for serialization :P
But with tests this would be a welcomed PR.

Makes sense to me! +1 to tests! <3 :D

https://github.com/JuliaPerf/PProf.jl/pull/26 provided this functionality, so perhaps close? :)


webrtc: make preflight OPTIONS requests work with external auth (#1941)

Fixes #1941

Codecov Report

Merging #1964 (0c404cb) into main (0d1aad2) will increase coverage by 0.05%.
The diff coverage is 31.25%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main    #1964      +/-   ##
==========================================
+ Coverage   60.98%   61.03%   +0.05%
==========================================
  Files         108      108
  Lines       11459    11462       +3
==========================================
+ Hits         6988     6996       +8
+ Misses       3948     3945       -3
+ Partials      523      521       -2

Impacted Files
Coverage Δ

internal/core/core.go
84.33% <ø> (ø)

internal/core/webrtc_http_server.go
61.29% <26.66%> (+0.06%)
:arrow_up:

internal/core/hls_http_server.go
63.96% <100.00%> (ø)

... and 2 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Feature Request: Pagination prop

Currently, there are no options to adjust the pagination style, or even to completely remove it. Thoughts would be including a renderPagination={(...) => React.ReactElement}, or at the very least, pagination={boolean}? I'll PR this!

对了 ，能不能加一个隐藏pagination的方法

renderPagination={(...) => null} supposed to work.
And as you can see, you can pass the whole react component, so you are in control whatever you want, including styling.


Add enhanced copyFormatting

Docs for microsoft/terminal#6004

Docs Build status updates of commit d71c0fe:
:warning: Validation status: warnings

File
Status
Preview URL
Details

TerminalDocs/new-terminal-arguments.md
:warning:Warning
View
Details

TerminalDocs/customize-settings/global-settings.md
:white_check_mark:Succeeded
View

TerminalDocs/customize-settings/key-bindings.md
:white_check_mark:Succeeded
View

TerminalDocs/new-terminal-arguments.md

Line 11, Column 1: [Warning-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading.
Line 11, Column 1: [Suggestion-duplicate-h1s] H1 'New Terminal Arguments in the Windows Terminal' is duplicated with other articles: 'new-terminal-arguments.md(11,1), new-terminal-arguments.md(11,1)'. First level headings must be unique within a docset. NOTE: This Suggestion will become a Warning in late September, 2020.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


FVT scenarios for EdgeX

The FVT scenarios.

Several EdgeX FVT scenarios were added, and close the issue.


Link to why try catch is a bad idea

catching exceptions has issues will tail recursion. discussed somewhere can't find link. Need to add it to an FAQ on why by default OK does not work with exceptions.

I was thinking about this. If the problem has to do with tail recursion, is this when you try to catch the exception at every level of the nested case statements produced by OK.with?
I would think that there could be a possible alternative, like OK.try_with that is simply syntactic sugar that wraps the entire OK.with block in a single try...catch statement. I would be very surprised if this would create problems.
Another route would be to have an option flag, possibly related to #12 "options for with" issue, so you could say something like
OK.with(rescue/catch: true) do
  # normal statements here, but any exceptions get
  # converted to error tuple e.g. {:error, {:exception, arithmetic_error}}
  ...
  {:exception, exception} ->
    # handle exception error
end

Note: The catch: true would be the implicit square brackets ([ ]) that Elixir has.
I am unsure of rescue vs. catch in this case, but I would lean towards rescue as I am thinking specifically about exceptions being raised.

@CrowdHailer That sounds like an implementation issue more than an actual problem. I get why we're avoiding exceptions and try to stick with idiomatic (but not compiler(!) enforced) success/error tuples but the user of OK shouldn't have to concern themselves with these things. If a poorly implemented third party libs throws an exception it should just be wrapped as an error tuple and returned in the else block. Anything else is noise.
At least that's how I see this. I wrote my own Either, so obviously I'm rife with opinion :)

This is what should happen
{:ok, 6} ~>> Kernel.div(0)
      {:error, "bad argument in arithmetic expression"}

If I want it to be thrown and let a supervisor handle it I wouldn't use OK piping, so it would make sense that the user would expect it to be managed for them. Just my take.

@bill-mybiz @CrowdHailer I take it OK has no intention of making sure exceptions are transformed to error tuples? I'm guessing https://github.com/CrowdHailer/OK/pull/25 this tackles that?
This is something I am interested of as I find Elixir exceptions to be very ambiguous.
I don't want issues where method/2 does not exist. That's not my error.
My error is the data I got does not match my expectations. This is one of my main grips with Elixirs standard MO. I get the happy path coding, but the error thrown are ambiguous and not related to the ACTUAL issues I need to find out about.
Which means most of the time I want to capture the exception and make sure it throws the right exception which I can than tackle with idiomatic beam/elixir/erlang and handle it with supervisors and logging.

@seivan there are problems with using try catch blocks relating to how erlang manages tail call optimisation, that is my biggest concern with catching errors. also catching every exception raised is rather heavy handed.
The second point is the difference between exceptions from user input/external systems and errors from inaccurate coding.
Kernal.div(a) should return int() if a is always expected to be non_zero but {:ok, int()} if a could be zero. If you have worked on the assumption that a is always nonzero then you would like it to raise as it is a coding error.
I'm still very open to exploring options and usecases.

I take it OK has no intention of making sure exceptions are transformed to error tuples? I'm guessing #25 this tackles that?

#25 has to do with getting rid of a compiler warning that exists because currently the else block always adds a clause instead of conditionally adding it. Nothing to do with "exceptions" in the sense that you are talking about, rather that is just the variable name that is used for an error tuple match. (But it does serve as a reminder that that PR is still open. Perhaps @CrowdHailer could either accept it to resolve #24 or reject it to move forward in a different direction.)
There seems to be some gray area distinguishing error paths and errors thrown. Possibly in hindsight, they should have recommended exceptions be named MyException instead of MyError when using defexception to help to highlight this.
With this in mind...

Which means most of the time I want to capture the exception and make sure it throws the right exception which I can than tackle with idiomatic beam/elixir/erlang and handle it with supervisors and logging.

With the first "exception", I know you're talking about exceptions proper. But then with "make sure it throws the right exception", do you mean that you would like to wrap it in the error tuple and take it down the unhappy path? Or are you talking about re-throwing an exception proper to "handle it with supervisors and logging"? :confused: If the former, then my above suggestion (or similar) would take care of it. If the latter, I'm not sure if that is in the purview of this lib?

@seivan @bill-mybiz Eventually I found the reference I was looking for.
Just in source code

Note that calls inside try/1 are not tail recursive since the VM needs to keep the stacktrace in case an exception happens.

https://github.com/elixir-lang/elixir/blob/22bd10a8170af0b187029d115abe4cc8edcf2ae6/lib/elixir/lib/kernel/special_forms.ex#L1622
I don't think I have a full understanding of all the issues here, might be something I put to the forum at some other time

Added to FAQ


Feat: Add close old issue bot

What feature?
Proposal: Close Old Issue Bot
Description: The Close Old Issue Bot is an automated tool designed to identify and close inactive or resolved issues in a timely manner. It improves issue management efficiency by reducing clutter and ensuring active focus on relevant tasks.
Features:

Issue Tracking: Monitors issue activity and identifies those that have remained inactive for a specified period.
Automatic Closure: Closes old or resolved issues based on predetermined criteria, promoting a clean and organized issue tracker.
Customizable Settings: Allows users to define their own criteria for determining issue activity and closure, adapting to the specific needs of their project.

Add screenshots
n/a
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

we already have a stale issue checker.


Adopting glide for dependencies management

Ref - https://github.com/elastic/libbeat/pull/278

@mrkschan We are still testing it, so hold your horses ;-)

@ruflin actually i don't really know the differences between glide and godep and i just know that they both support vender/ convention in golang 1.5. And, Travis by default support godep 1, why make a switch?

@mrkschan Currently we are only testing alternatives to see if there is a better solution. Nothing decided yet.

Updates - https://github.com/elastic/beats/pull/620


Removed remaining .ps1 references from doc in multi_plateform_configu…

In 0.11.0 pixi version basic usage documentation was updated to remove .ps1 files from activation section, but there were still some references in multi platform documentation.
I just removed those.
Btw: pixi is great!

Thank you!!


[Refactor] installer

Describe the current issue
The current installer is very monolithic. This monolithic structure is error prone and makes developing and testing installations very difficult.
Where is the problem
The entire installer is in one file. However the installer is run in three environments at the same time. This makes development very difficult since we need to cover 3 cases (with 3 different environments) This can give undesired effects
How should it change
Instead of calling dialogarchinstaller with options. Abstract each type into a different file eg

dialog.sh
baseinstaller.sh
display.sh
custom.sh
loader.sh
etc

What are the benefits?
The code will be easier to maintain since it is easier to wrap your head around.
Additional context
Don't forget to change the wget clone of dialogarchinstall in customie_airootfs.sh to include all different shell files

We are now working on a api for installing an OS. This is now happening in the TOS-installer-backend. Repo a frontend has to be written but isn't available yet

I will update this issue until a proper new installer is present

A fully working curses installer is now present. However installing a kde version or server version is now not possible. This means we still need to add that functionality back

The installation now happens using calamares the tos-cli-installer with tos-backend is also fully functional. Thus this issue has been fixed.


[MAINT] add mkdocs enhancements

Closes #1616

link to repo in navbar
dark mode
mastodon link in footer
an edit button

Not a huge deal (and definitely doesn't need to be addressed here), but the DRAFT is much more prominent in dark mode:

If we could set that to switch with dark mode, then a version with inverted luminance would probably work well.

Not a huge deal (and definitely doesn't need to be addressed here), but the DRAFT is much more prominent in dark mode:

will check if some CSS magic can do the trick

Much better:

Thanks to @nellh and @rwblair for their knowledge of CSS that was updated more recently than 2009.

Thanks to @nellh and @rwblair

Well if the help of our web wizard and sorceress was required I did not stand a chance. 🤗

for their knowledge of CSS that was updated more recently than 2009.

hey at least you have some CSS knowledge... I just say I do.
Thanks y'all!


Add hint for empty API key

I am open to suggestions. We will point users to an example GitHub Action with Dataplane credentials only, that writes to Vespa Cloud with no warnings - the current version is at https://github.com/vespa-engine/documentation/blob/master/.github/workflows/feed.yml
What do you suggest we do to get to this?

Complete or close ?

There's a ticket tracking the solution to this.


Crashlytics and performance monitoring

Placeholder issue to decide on crash and performance monitoring solution.
It would be good to have something in place as early as possible so that we can catch crash/perf issues before they become wide spread.
Case example: A large contingent in a certain country use a certain device which is very different to the developers devices and emulators, causing that contingent to crash and be unavailable to participate.
Firebase Crashlytics and Perf (disclaimer, I work at Firebase, this is the one I am familiar with)

https://firebase.google.com/pricing (Free for both perf and crash)
Unsure if installing crash/perf implies installing the Google Analytics SDK

There are certainly other options for crash and perf too.
Open questions:

Might a crash and/or perf monitoring SDK cause additional privacy concerns for the users?

Crashlytics is certainly great to use when you have a complex app, but for the simplicity (?) of this, I can't imagine to see the benefit outweigh the extra load of adding new library dependencies and the extra weight (and tarnishing?) of privacy. (First the app focused on privacy, then we start adding libraries that undo most of those privacy measures.)  Dumping a simple logcat text file can probably help resolve 95% of any future issues.

@E3V3A brings up a good point, but I don't think grep'ing text files is a scalable or accessible solution either. @tstirrat is there a pragmatic way to implement the necessary features of firebase without risking the mission of being privacy focused?

What sort of privacy concern is there with Crashlytics, provided we're not intentionally logging any PII?

@efalkner

What sort of privacy concern is there

Crashlytics can be uploading all sorts of very device specific info (incl, serial numbers etc.)
But my main issue is the extra needless bloat taking away from development effort.
@alecharmon

I don't think grep'ing text files is a scalable

I'm not suggesting running external shell commands, and since every language have built-in regex, this is trivial. I have done a lot of this before, but if you need an already working code, that even scrubs user specific data, I suggest using that built-in to the Signal app, in the logsubmit functions here.

extra needless bloat

Seeing detail of crashes, percentage of crashes and stack traces is extremely helpful to a dev. So I wouldn't call it needless bloat.
These tools group crashes into similar by comparing stack traces, and by version so you can track "issues" over time across multiple versions.... I would say this is significantly better in almost every dimension than manual log scanning. I would consider the tools to be  adding a lot of value to the Dev effort and in my humble opinion "worth it" (not speaking specifically of Firebase or CL but crash tools in general)
Specifically on Firebase tools: They can be made user opt-in. I verified with Crashlytics folks if they can be useful without the broader Google analytics SDK, and the response was:

Crashlytics can work without GA SDK, but loses a couple of user segmentation (i.e crashes by country) features

Performance Monitoring does not need it in the first place.

Manual log scanning has another set of privacy concerns. Because I as the log reader do not have control over what you, as a developer with different needs, might have accidentally or intentionally spammed into a log.
The question still remains if users would feel more hesitation using the app knowing these things were installed even if they could opt-out. And I suppose this is a good question for the UX research team.

@tstirrat  think we can close this out?


graph age check should avoid times in the future

last_update field in graph edges can have a date in the future. That is because channel policy info can be whatever a node sends. It is not checked by lnd since it would be tricky because clocks aren't always in sync
So, this dates in the future should be avoided when checking if the graph is too old (currently more than 6 hours)
I'm sending a pull request to solve this

Merged, thanks for the contribution!


Fix container test suite dependencies

Looks good. Is this the only dependency we need to add? There are more of these idep modules https://github.com/droolsjbpm/jbpm/tree/master/jbpm-container-test/jbpm-in-container-test/jbpm-container-integration-deps ( I don't really know these tests, so it may be that we really need just the one, but better to be sure)

Adding other modules the jbpm-container-test-suite depends on. As the jbpm-remote-ejb-test-suite already defines dependencies on KJAR modules, it's instability might be caused by runtime scope of these dependencies (parallel build might decide to postpone them). Changing them to compile scope.

looks good to me, is this ready to be merged?


BuildFrameworkTcImports: no resolution of FSharp.Core, Version=<IP_ADDRESS>

F# projects with FSharp.Core library <IP_ADDRESS> do not work in VS Code 1.10.x
Error message:
file: 'file:///startup'
severity: 'Error'
message: 'internal error: BuildFrameworkTcImports: no resolution of 'FSharp.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a''
at: '1,1'
source: ''

Reference in my project file:
<Reference Include="FSharp.Core">
  <Name>FSharp.Core</Name>
  <AssemblyName>FSharp.Core.dll</AssemblyName>
  <HintPath>$(MSBuildProgramFiles32)\Reference Assemblies\Microsoft\FSharp\.NETFramework\v4.0\$(TargetFSharpCoreVersion)\FSharp.Core.dll</HintPath>
</Reference>

The library itself exist, and the project works well in Visual Studio 2017.
A related link to StackOverflow

same problem here.

+1

Also experiencing the same issue.

I have a student here with this issue. Windows 10, Ionide 2.24.1. Working on a single file, no project file.
Any work-arounds?

I think that adding project file and setting FSharp.Core version to <IP_ADDRESS> or using FSharp.Core from NuGet should fix issue

After adding the project file the error is not coming.

Having the same issue.

Also having the same problem. Does this mean that ionide is not working for anyone right now?

Having the same problem on ionide. I created a new project using the dotnet CLI tools described in this tutorial.

@efvincent Yes this looks like a bug that's stopping ionide from functioning right now

@Krzysztof-Cieslak I'd like to add that I get this error even when setting <TargetFSharpCoreVersion><IP_ADDRESS></TargetFSharpCoreVersion> in the project file and also using FsharpCore from nuget.

@Krzysztof-Cieslak I'd like to further add I have a multi-project solution (net45).  When I switch to <TargetFSharpCoreVersion><IP_ADDRESS></TargetFSharpCoreVersion> the project furthest up the dependency chain (doesn't depend on any other projects) works fine with ionide, but projects that depend on it exhibit the error.  (The solution is a mix of F# and C# projects)

Should be fixed in 2.25.4

Still encounter that issue.
After creating a new project everything works but suddenly after a few minutes (maybe after the first build) it throws that error. Which also results in 'not parsed' errors for the source files, thus no linting, type hinting, etc works.

3.10.1 also affected


Setting a higher number for 'n_cells=' argument in cellrank.tl.estimators.GPCCA.set_terminal_states_from_macrostates

Dear developers, thank you very much for the great tool that is very easy to use and informative. I would like to know whether setting a higher 'n_cells=' number in cellrank.tl.estimators.GPCCA.set_terminal_states_from_macrostates increases power to identify drivers genes? The default number is 30 and this seems very small. I have >500 cells in my terminal clusters.
Thanks,
Jesse

Thank you very much @Marius1311 !
Could you kindly advise on whether I can use all good quality genes (not just highly variable or those with >20 spliced counts) in my dataset when looking for driver genes when using either the PseudotimeKernel or VelocityKernel. I see no reason to limit my genes to only highly variable or those with high spliced counts.

Hi @JesseRop, for sure, these are gene filtering routines for velocity computation and representation learning, you may use other filters for driver gene identification - for example, you may want to include some genes that are expressed at lower levels (many TFs are expressed at low levels) or you may want to filter out mitochondrial, ribosomal or cell-cycle genes.

Many thanks @Marius1311 .
I presume the only preprocessing I will need to do on the raw counts is normalization to cell size and log transformation before running pseudotimeKernel if I already have the pseudotime computed?

Thank you very much @Marius1311 . I have raised an issue requesting for a feature to easily incorporate all genes in driver analysis here https://github.com/theislab/cellrank/issues/870#issue-1234432016 . If you have advice on this, I will be grateful. Thanks


Changes to support cumulus setuptools refactor

To test this either:

Checkout setuptools-dist in cumulus folder at same level in directory as this repo's checked out folder and run with DEVELOPMENT=1 vagrant up

Modify the Vagrantfile to include the following patch and run with vagrant up

@@ -83,7 +83,8 @@ Vagrant.configure(2) do |config|
     ansible.verbose = "vv"
     ansible.extra_vars = {
       default_user: "vagrant",
-      development: dev
+      development: dev,
+      cumulus_version: "setuptools-dist"
     }

     ansible.playbook = "ansible/site.yml"

LGTM


unsupported url watch.aecrimecentral.com

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2022.10.04 (update instructions) or later (specify commit)
[X] I've searched the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
is https://watch.aecrimecentral.com/ not supported? the url in question is,
https://watch.aecrimecentral.com/shows/my-crazy-ex/season-4/episode-1
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

There is an open issue to add support for aecrimecentral.com: #3114
Do not abuse the "Question" template to post incomplete issues/feature requests. Properly fill out an appropriate issue form (and search the issue tracker before doing so)


ERROR: Quaternion Not Properly Normalized and Topics not being published

Hi
I am trying to launch the inertial_sense_node. It shows that it has established connection with the uINS sensor along with a warning "MSG to TF: Quaternion Not Properly Normalized". Also /ins topic is not being published at all. When I try to launch using the default launch file test.launch, it shows the same error along with the phrase "bad data" and streams data continuously on the screen.
Any help to resolve this is appreciated.
Thanks

Do you know the software version of your uINS?

No. It is not available on the sensor anywhere. I have not changed any firmware on the sensor. It is just like how it was bought. Do I need to upgrade the sensor firmware? If yes, how can I do it?

Yeah, can you bring the firmware up to the latest?  (At this point, it is 1.6.2)
https://github.com/inertialsense/InertialSenseSDK/releases/tag/1.6.2
You can use the graphical utility if you have access to a windows computer, and use that to flash the firmware.
If you don't, you can use the command line utility.  Here are the commands I just performed on my machine to build and run the cltool (change the file paths as necessary)
cd InertialSenseSDK-1.6.2/
cd CLTool/
mkdir build
cd build/
cmake ..
make -j4 -l4
./bin/cltool -c=/dev/ttyUSB0 -baud=921600 -b=/home/superjax/Downloads/IS_uINS-3_v<IP_ADDRESS>_b2781_2018-06-29_175015.hex
./bin/cltool -c=/dev/ttyUSB0 -baud=921600 -msgINS2

I also just pushed a 1.6.2 branch that I confirmed works with the latest firmware.

Did you do a submodule update?
On Thu, Jul 19, 2018, 1:27 PM Akshay Kumar<EMAIL_ADDRESS>wrote:

Thanks. I updated the firmware using CLTool just as you suggested and
result was success.
I just cloned that branch and tried to test it and now I am getting a new
error:
"[FATAL] [1532028328.247633576]: inertialsense: No response when
requesting flash configuration from uINS on "/dev/ttyUSB0", at 3000000 baud"
Can you please help me solve this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/inertialsense/inertial_sense_ros/issues/14#issuecomment-406387894,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHAPjhpql6HJIyfVYhdmzvLl4mZd9peKks5uIN2ogaJpZM4VWx0F
.

Yes. Still the same error and no data is showing up on any topic.
But the sensor is successfully connected as it shows here.
[ INFO] [1532029836.154221301]: Connecting to serial port "/dev/ttyUSB0", at 3000000 baud
[ INFO] [1532029836.155681791]: Connected to uINS on "/dev/ttyUSB0", at 3000000 baud
[FATAL] [1532029839.156206723]: inertialsense: No response when requesting flash configuration from uINS on "/dev/ttyUSB0", at 3000000 baud

The color is green with red flashing intermittently.

It appears that the serial protocol submodule is messed up in the ROS node.  I just update the release branch to be up to date with 1.6.2.  Could you please try blasting away the repository and cloning it down fresh, with the current release?

Also, the autobaud detection only runs the first time the uINS is connected to something.  So, if you've connected to the CLTool at 921600 you either have to reset the device (one of the buttons) or change the baudrate parameter of the ROS node to 921600

If need, there is a flash config bit on the uINS that disables the autobaud feature.
--
Walt's phone

On Jul 20, 2018, at 11:51 AM, James Jackson<EMAIL_ADDRESS>wrote:
Also, the autobaud detection only runs the first time the uINS is connected to something. So, if you've connected to the CLTool at 921600 you either have to reset the device (one of the buttons) or change the baudrate parameter of the ROS node to 921600
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

It is working.
I reflashed the firmware using CLTool and re-cloned the release branch. it is working. It seems to work on 3000000 baudrate as well.
Thanks for your support. I will close this issue now. I have some new issues regarding INS data which I will post as a new question.


Invite a User Should by Styled like a Button

It's currently a link and should probably be a button.

This will be rendered moot by #176


shouldRevalidate is skipped

What version of Remix are you using?
1.19.3
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce

export shouldValidate function that always returns false
call api that counts calls
navigate back and forward and watch counter go up

I also added a test that reproduces it !7309
Expected Behavior

shouldValidate should be called
if souldValidate returns false loader should not be called

Actual Behavior

shouldValidate is not being called
loader is executed

Navigating away from and back to a route is not a revalidation, so shouldRevalidate is not called.  Coming back to a route is a fresh new instance of the route and therefore a fresh load of the data.  This is required because once a route is navigated away from, it's loader data no longer exists.
Revalidations are when the loader data already exists and Remix is about to reload it after an action, or a useRevalidator call, or a search param update, etc.

Thanks for the reply.
The docs are confusing/make false promises imo:

This function lets apps optimize which routes data should be reloaded after actions and for client-side navigations.
from https://remix.run/docs/en/1.19.3/route/should-revalidate#defaultshouldrevalidate

We always accept PRs to improve the docs!

Hello. Is there a way for using existed loader data, or just skip loader call when 'Navigating away from or back to a route'.

It depends on whether the route remains or not during the navigation away and back.
If your route persists (such as the parent route in /parent -> /parent/child -> /parent), then your loader will be revalidated according to shouldRevalidate.
If the route disappears (such as /parent -> /elsewhere -> /parent) then you would need to implement Cache-Control headers to use cached data


TP2000-392: Remove preview workbasket page

TP2000-392: Remove preview workbasket page

Why

Updating to match newest design

What

Instead of going to the preview page first the user is sent straight to the workbasket review page

Codecov Report

Merging #640 (68687a6) into master (ac46ebf) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #640      +/-   ##
==========================================
- Coverage   93.32%   93.30%   -0.02%
==========================================
  Files         323      323
  Lines       20675    20667       -8
  Branches     1654     1653       -1
==========================================
- Hits        19294    19283      -11
- Misses       1070     1072       +2
- Partials      311      312       +1

Impacted Files
Coverage Δ

workbaskets/urls.py
100.00% <ø> (ø)

workbaskets/tests/test_views.py
97.98% <100.00%> (-2.02%)
:arrow_down:

workbaskets/views/ui.py
78.37% <100.00%> (-0.90%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ac46ebf...68687a6. Read the comment docs.

@gabelton in the PR or in the code?

Just in the PR would be great


Various fixes for compatibility with SPT 3.9.4

Works on my end with Realism and other clientside mods.
Only thing that I think is curious is the AmbiguousMatchException for SimpleTooltip.Show(). I've seen that exception when trying to access functions with overrides in the same class without specifying parameters. However SimpleTooltip.Show() has no overrides so not sure where the exception is stemming from but specifying parameters removes the exception

Is it possible to release an unofficial build?


Zipato RGBW Bulb V2

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.116%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2425

Relevant Lines:
2523

💛  - Coveralls

Thanks for contributing.
brightness.csv may be removed because this is a color mode which cannot be used for this lights. HA specs say that if a light supports anything else than only dimming then brightness should not be a possible option. You can also see that when inspecting supported_color_modes attribute for your light in developer mode.
When eyeballing the color_temp.csv for correctness I saw 2 strange things.

On lower mired levels power stays below 1 watt even on the highest brightness levels. I don't think I have seen this by any lights before. Maybe it's a bug in the light firmware where the light is actually quite dim when set on for example brightness 255 / mired 163.
The first mired value on each brightness increase still shows a relatively high watt value, and then on 163 it drops to below 1 watt. See screenshot.

Could you verify these findings by manually setting your light to these values and see if you get similar readings?

I have tested it manually and all the values match up.

Thanks for verifying.
So you did also notice the light being a lot dimmer at brightness 255 and color_temp 163 in contrast to 255 / 153?
As that should definitely the case looking at the power readings.
It's consuming 10 times less power between these 2 settings, which is very strange.

Going to merge it, maybe it's some bug in the firmware. But that's not something you or powercalc can fix.


Fix Test and declare module

Fix npm test script to run with presubmit
Fix any linting problem
Declare extension code to use ECMAScript Module, and modify any CommonJS code to use .cjs file type

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (c4438c2) 53.77% compared to head (fd48e9a) 77.63%.

Additional details and impacted files
@@             Coverage Diff             @@
##             main      #76       +/-   ##
===========================================
+ Coverage   53.77%   77.63%   +23.86%
===========================================
  Files          21        4       -17
  Lines         318      161      -157
  Branches       30       21        -9
===========================================
- Hits          171      125       -46
+ Misses        144       36      -108
+ Partials        3        0        -3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[Python] Not able to import pyarrow.parquet

Describe the usage question you have. Please include as many useful details as  possible.
I am trying to load datasets library from Hugging Face but it gives me this error.

ImportError: The pyarrow installation is not built with support for the Parquet file format (DLL load failed while importing _parquet: The specified procedure could not be found.)

so I tried the following,
import pyarrow.parquet as pq

Which gave me the same error.
My pip is up to date and PyArrow is also up to date so why am I facing this issue. Can anyone help me with this??
Component(s)
Parquet

Out of curiousity what's the version of arrow you're using?

is it the pip package, or a Conda package?
I faced this issue in a Conda environment, when installed pyarrow-core=17.0.0=py310h85d79f8_1_cpu from conda-forge, and I solved it by installing libarrow=17.0.0=h974b3c2_11_cpu

I have the same issue, did you figure out what the issue was ?


Pin Cake versions to a set that works together.

I can do an Evergreen patch build if you think it is worth it.
I did run "git clean -xfd" before testing the change to force a new download of all the Cake components.

I've created an Evergreen patch but only activated some of the tasks:
https://evergreen.mongodb.com/version/5c76acec5623434756b7c137

p.s. Does pushing to master count as testing on Evergreen? :)


Add ivegotwood plugin

This is a simple plugin that allows the user to display a default or customizable message above the character's head while woodcutting, fishing, mining, or constructing objects.

You need real details in your plugin properties file, not just "Example", "Nobody", etc.
LGTM otherwise

@Nightfirecat should be good to go now! thank you