Command: vue upgrade

Command that should be run inside an existing project with @vue/cli-service present.

Resolve the version to upgrade to.

vue upgrade [patch|minor|major]: defaults to minor

If already latest, print message and exit
Otherwise, confirm via prompt
Find @vue/cli-service plus all packages in package.json that starts with @vue/cli-plugin-, and bump them to the target upgrade version
Run installDeps

What about upgrade hooks similar to the Generator API?

Hey there!
Is anyone working on this? I want to try to contribute with this project.

@TheMushrr00m Nobody is working on it, feel free to go ahead! Thanks!

@beardedpayton Can help you if you need any. But we definitely need to think about how other plugins like to handle upgrading. What happens when a plugin which has been added want to change something in the project in a future version? Does it need to reply on vue invoke vue-cli-plugin-x? Or can we add a command vue upgrade vue-cli-plugin-x?

It would definitely be awesome if plugins can handle upgrade scenarios, I hope that is kept in mind!
So far with each RC of Vue CLI I've vue invoke'd each plugin to see what it does differently and manually merge in the changes (e.g. vue-cli-plugin-unit-jest fixed the test match regex between rc.3 and rc.5).
Imagine if your Vue apps can ride along framework upgrades as smoothly as being generated...

What is the current workflow for upgrading one's vue-cli packages? Is it safe to do a plain yarn upgrade vue-cli-service --latest? I'm currently sitting at 3.0.0-beta.1. What I'm most interested in is getting vue-cli-plugin-babel up to speed so that I can hopefully resolve these sorts of debug / source map issues.
Should I do an upgrade only on vue-cli-plugin-babel?


fix DeprecationWarning on sklearn.cross_validation

sklearn.cross_validation module is deprecated in scikit-learn 0.18, this PR will resolve this problem.

Codecov Report

Merging #2075 into master will decrease coverage by -0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2075      +/-   ##
==========================================
- Coverage   30.67%   30.63%   -0.04%
==========================================
  Files          72       72
  Lines        5836     5836
  Branches      583      583
==========================================
- Hits         1790     1788       -2
  Misses       3970     3970
- Partials       76       78       +2

Impacted Files
Coverage Δ

src/objective/regression_obj.cc
89.26% <0%> (-1.7%)
:x:

src/data/simple_dmatrix.cc
58.66% <0%> (+0.66%)
:white_check_mark:

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 fd19b7a...7ccef49. Read the comment docs.

Traceback (most recent call last):
  File "/home/travis/build/dmlc/xgboost/tests/python/test_with_sklearn.py", line 21, in test_binary_classification
    kf = KFold(y.shape[0], n_folds=2, shuffle=True, random_state=rng)
TypeError: __init__() got an unexpected keyword argument 'n_folds'

Why? I don't get it. KFold do have argument n_folds or n_splits (depending on version).

@icyblade thanks so much for taking a whack at this! I've also found this to be a really annoying notification. Hope you find a fix for that latest bug- would love to see this merged when it is.

mind update the version and retrigger the test?

Sorry for the late reply, I'm working on it.

Hello. still getting the Deprecation Warning for sklearn:
/usr/local/lib/python3.6/site-packages/sklearn/cross_validation.py:41: DeprecationWarning: This module was deprecated in version 0.18 in favor of the model_selection module into which all the refactored classes and functions are moved.
running the latest version of xgboost.


Downgrade to .NET 4.5 (for better Win 7 compat)

LibGit2 downgraded to 24.1 from 26.1 to accomodate.

Dunno if this is necessary tbh, if people updated their Windows 7 in the last year it should have .NET 4.7 installed right?


mendeley: 1.17.3 -> 1.18, touchup update script

(support "1.18" instead of "1.18.0")

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: mendeley
Partial log (click to expand)
Cannot nix-instantiate `mendeley' because:
error: while evaluating 'callPackageWith' at /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/lib/customisation.nix:113:35, called from /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/top-level/all-packages.nix:16715:14:
while evaluating 'makeOverridable' at /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/lib/customisation.nix:72:24, called from /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/lib/customisation.nix:117:8:
while evaluating anonymous function at /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/applications/office/mendeley/default.nix:1:1, called from /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/lib/customisation.nix:74:12:
assertion failed at /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/applications/office/mendeley/default.nix:37:1

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: mendeley
Partial log (click to expand)
Cannot nix-instantiate `mendeley' because:
error: while evaluating 'callPackageWith' at /var/lib/gc-of-borg/nix-test-rs-20/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-20/lib/customisation.nix:113:35, called from /var/lib/gc-of-borg/nix-test-rs-20/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-20/pkgs/top-level/all-packages.nix:16715:14:
while evaluating 'makeOverridable' at /var/lib/gc-of-borg/nix-test-rs-20/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-20/lib/customisation.nix:72:24, called from /var/lib/gc-of-borg/nix-test-rs-20/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-20/lib/customisation.nix:117:8:
while evaluating anonymous function at /var/lib/gc-of-borg/nix-test-rs-20/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-20/pkgs/applications/office/mendeley/default.nix:1:1, called from /var/lib/gc-of-borg/nix-test-rs-20/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-20/lib/customisation.nix:74:12:
assertion failed at /var/lib/gc-of-borg/nix-test-rs-20/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-20/pkgs/applications/office/mendeley/default.nix:37:1

Oh, right.


Text is too small on mobile devices

We should make the content more compact on mobile devices such that text is larger.

fixed in https://github.com/fermyon/hippo-themes/commit/ce6d3c141aae0d6d1c73903c40e5fbc53a782996


Converting SO scraper to DayData

so that we don't print the empty Hospitalized lines any more for recent days

The test failed, you need to skip the first line with "bis 31.03.2020"

@metaodi Sorry about that. I've added a fix.


fix path validation when allow non-existing file

Fix half of #333

Thanks for this and the accompanying issue.
Due to changes in main since 0.6.4 I needed to work up a different solution to fix this. Hopefully it will all vanish when I release 0.6.5 next week. Or you can try out the current main branch once I merge #342 .
Closing it now.


Update dmutils and add dmapiclient package dependency

Update dmutils and add dmapiclient package dependency
Fixes imports to use the new dmapiclient package instead of
dmutils.apiclient and dmutils.audit.
Remove unused app.models module and dependencies
app.models seems to have been replaced by search API client and
is not imported anywhere
Update gulp-sass to work on node v4.2
We're using gulp-sass 2.0.4 on supplier app and it seems to work
with both old and new node versions.
Also sets npm and travis node versions to v4.2.
Switch from nostests to py.test runner
Using py.test allows us to send coverage reports similar to other
apps.
Enable coveralls coverage reports

:+1::+1::+1: Nice cleanup!


fix: fix bug with deleted inventory records reappearing after deleting profiles

fix bug with deleted inventory records reappearing after deleting profiles

:tada: This PR is included in version 1.0.0-beta.13 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add support to tcurl as another service

It would be useful to have a tcurl option to specify the requesting service.
Usecase: Testing auth changes
Something like...
tcurl --asService

I’m adding --cn #121
I’m also adding a $USER@ prefix to the caller name to increase traceability. Would that interfere with your use-case?

uhh, it might.  Our authorization models require exact service names.  If we prefix the service name with a $USER@ prefix it wouldnt match.

I will add a --sneaky flag then.


Help?

Where does one go for help on Sidekick? There are no active questions on Stackoverflow, is there are Usergroup or other where questions can be asked and the good folks who build Sidekick hang out to help us plebs out?
Thanks.

OK, thanks.
I'm trying to get started with Sidekick for Dapr, and am having trouble telling Sidekick where the dapr components are.
By default it's going to %USERPROFILE%.dapr\components, but I'd rather it go to a folder local to the solution.
Looking at the code it appears that adding the following to the appsettings.json should work, but it isn't picked up.
 "DaprSidekick": {
    "RuntimeDirectory": "dapr",
    "ComponentsDirectory": "C:\\Dev\\Intel\\DPS.ATG.AllInOne.Scratch\\DaprPOC\\components",
  }

However the components folder invariably becomes %USERPROFILE%\.dapr\components
This is from this Stack overflow question
https://stackoverflow.com/questions/72530687/how-to-specify-dapr-component-locations-with-sidekick

As you asked the question on StackOverflow as well I've answered it there,, but here's a copy:
When you set "RuntimeDirectory": "dapr" Sidekick will automatically look for component files in the dapr/components subdirectory in your solution. Try removing the ComponentsDirectory entry so it returns to defaults, and try a directory structure like this:
|-- MyProject
|   |-- MyProject.csproj
|   |-- dapr
|   |   |-- config.yaml
|   |   |-- components
|   |   |   |-- my_component.yaml

The Dapr Sidecar should then load my_component.yaml.

Simon answering here because it allows a better "conversation" as it were.
Also, thank you for your time and help, it's appreciated.
OK, so I set up my folder structure as above, still no joy.
This is what I have for sidekick in my appsettings.json.
 "DaprSidekick": {     "RuntimeDirectory": "dapr"   }
I've created a minimal sample that reproduces my problem, you can find it here.
https://github.com/BinaryWorrier/DaprNoddy

The problem is this line in your Program.cs:
builder.Services.AddDaprSidekick();

The samples and README instructions all pass the IConfiguration instance to that extension method which gives it access to all the configuration settings, including those in appsettings.json. Without that it won't know what you've defined as preferences :)
Try changing it to this:
builder.Services.AddDaprSidekick(builder.Configuration);

D'oh! 🙄
Thanks!


[Question] iOS support

Is there any way to set up the LSP to work with iOS apps? Specifically with iOS SPM packages? I have a project which is based on SPM modularized architecture.
I have found a way to compile packages for iOS using the following command:
 xcodebuild -scheme PackageName -destination 'platform=iOS Simulator,OS=16.4,name=iPhone 14'

However, when I try to develop some classes in my editor I get these errors in LSP logs:
[ERROR][2023-09-14 12:02:28] .../vim/lsp/rpc.lua:734	"rpc"	"/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/sourcekit-lsp"	"stderr"	"[2023-09-14 12:02:28.905] [error]: the library 'SomDependency' requires macos 10.13, but depends on the product 'Kingfisher' which requires macos 10.14; consider changing the library 'SomDependency' to require macos 10.14 or later, or the product 'Kingfisher' to require macos 10.13 or earlier.\n"

It looks like the LSP is trying to build the project for macOS. I tried configuring LSP like this:
    lspconfig["sourcekit"].setup({
      capabilities = capabilities,
      on_attach = on_attach,
      cmd = { "/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/sourcekit-lsp",
        "-Xswiftc", "-sdk",
        "-Xswiftc", "/Users/xyz/Downloads/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator.sdk",
        "-Xswiftc", "-target",
        "-Xswiftc", "arm64-apple-ios16.4-simulator" },
    })

but I get the same errors when I try to work with my Swift files. I would like to be able to work on my project in Neovim or VSCode.

There's currently no way to make LSP work with cross-compilation.

😢 so it looks like iOS developers are condemned to use Xcode forever 😭

Tracked in Apple’s issue tracker as rdar://115484487

@wojciech-kulik you can try my tool xcode-build-server to bind xcode project compile info to sourcekit-lsp.

There's currently no way to make LSP work with cross-compilation.

So -sdk and -target do not work? I've had UIKit, SwiftUI completion with these parameters. It becomes problematic when you need to build a full project. There are a number of hurdles there, but breaking everything off into libraries and compiling them using swift CLI generally works.

These issues might be helpful! (Signed, a stubborn Sublime user)
#730 - xcodebuild support for sourcekit-lsp
https://github.com/apple/swift-package-manager/issues/4328 - SPM multiple targets
https://github.com/apple/swift-package-manager/issues/5619 - SPM unknownOS in -triple

@wojciech-kulik you can try my tool xcode-build-server to bind xcode project compile info to sourcekit-lsp.

Thank you! It seems to work! I'm only struggling with root_dir detection by lspconfig. It doesn't work properly when my xcodeproj is not where .git is located. Any advice on how to find it?
I tried:
      root_dir = function(filename, _)
        local git_root
        git_root = lspconfig.util.find_git_ancestor(filename)

        local handle = io.popen("find \"" .. git_root .. "\" -type d -name \"*.xcodeproj\" | tail -n 1 | xargs dirname")
        local result = handle:read("*a")
        handle:close()

        return result
      end,

but for some reasons, it doesn't work.

@wojciech-kulik may be you should use handle:read("*l")?  "*a" return all output, which end with a invalid "\n".
anyway, the generated buildServer.json can be any dir, just ensure it same with your lsp root, it not have to in same dir as xcodeproj.

@SolaWing it helped. Thank you!
Is it also possible to use xcode-build-server together with VSCode with Swift Extension?
When I run the same project in VSCode, I can go to definitions, but the code completion doesn't work.

I’m closing this since it’s the same underlying issue that we’re already tracking in #730.

I described how to set up Neovim and VS Code here: https://wojciechkulik.pl/ios/how-to-develop-ios-and-macos-apps-in-other-ides-like-neovim-or-vs-code

@wojciech-kulik may be you should use handle:read("*l")? "*a" return all output, which end with a invalid "\n".
anyway, the generated buildServer.json can be any dir, just ensure it same with your lsp root, it not have to in same dir as xcodeproj.

Had the same problem, was keeping buildServer.json file in the same dir as the workspace, then moved it to the .git directory, and resolved the issue. Thank you


Small style fixups

Job VTB Documentation on e0ff07e wanted to post the following:
View the site here
This comment will be updated on new commits.


Update join.py

To solve signature-mismatch error

In order to solve the Python format test, you can try to use VS Code to format your code.

Closing because it was already addressed in the PRs submitted between October 19-20


Drop RACSignal support.

So after the discussion in #489, I took a stab at removing the support for old version of ReactiveCocoa. As always I'm open for any discussion, so if you think something could be improved, is redundant or is lacking, please let me know! 🐼

Awesome! CI failure is unrelated (really need to fix that...) gonna merge!


Split big methods into smaller methods

Aside from a good documentation, a function should also be split if it is too big (±30 lines). Smaller functions are easier to understand, maintain and are also more reusable and self-documented.
This issue is related to #83 and I will illustrate some possible approaches. Any suggestions are welcome.
Source code example
impl Trait for Struct {
    fn example0(&self) { ... very long source code ... }
    fn example1(&self) { ... very long source code ... }
}

First approach
Create smaller static methods within a corresponding struct.
Pros: Simple
Cons: Puts everything in the same file
impl Struct {
    /// Documentation
    fn do_this() { ... }

    /// Documentation
    fn do_that() { ... }

    /// Documentation
    fn fill_whatever() { ... }
}

impl Trait for Struct {
    fn example0(&self) {
        Struct::do_this();
        Struct::do_that();
    }

    fn example1(&self) {
        Struct::fill_whatever();
        Struct::do_that();
    }
}

Second approach
A method can have all its logic grouped in a separate module. Would be nice to have a common contract (Trait) that each separate module should implement.
Pros: More intuitive?
Cons: Complex, files name must be sync.
Structure
module
├── module_helper
│      ├── mod.rs
│      └── example0.rs
│      └── example1.rs
└── mod.rs

module/mod.rs
pub mod module_helper;

import self::module_helper;
import self::module_helper::{example0, example1};

impl Trait for Struct {
    fn example0(&self) {
        example0::do_this();
        module_helper::do_that();
    }

    fn example1(&self) {
        example1::fill_whatever();
        module_helper::do_that();
    }
}

There is no silver bullet to this problem but I will be very grateful if we all come to a conclusion about this whole thing.

Thanks for writing this up - I agree that this is something that we should address in the library. That said, for me it isn't the biggest issue on the table right now. Do you have some examples within the library where you think this is a problem?
I think it is somewhat inevitable in a linear algebra library to have some large functions. And moreover separating the function out just to achieve this goal can make the problem worse as it becomes more difficult to follow the logic (you have to chase functions around). For me the solution is clean, self-documenting (and line-commented) code. Of course, there are some cases where we probably do have some quite bloated functions.
The bigger issue for me, which is definitely related to this, is that we have a few very large modules. I find it hard to find things in them and I wrote the majority of them - I imagine for new contributors it is hell. In particular I'm talking about the impl_ops and slice modules. I want to split these out in much the same way that @Andlon sorted out the decomposition module.

Like @AtheMathmo I believe this is not the biggest issue for now. On the other hand I do not think a linalg is more prone to bigger function than any other library.
I agree that having a concrete example could help.

I haven't come across too many big functions in rulinalg so far. The exceptions are some of the numerical algorithms, but in these cases the code often mimics an algorithmic description, so it might not be desirable to split it up too much. However, as @AtheMathmo, some modules are very bloated, and this is something that should definitely be remedied.
Now, I think perhaps you're asking for advice on how to structure your work on #83 rather than a suggestion to make changes in the existing code base. In that case, I will try to give you some (hopefully useful) feedback on your suggestions.
The first approach
Remember that Rust allows you to have free functions. There's actually no reason to wrap functions in a Struct for this purpose. For example, you could do (horrible example, sorry. Obviously the pizza should be much more composable):
/// Feel free to document, but if it's a very obvious helper function,
/// this may not be necessary
fn make_dough() { unimplemented!() }
fn make_tomato_sauce() { unimplemented!() }
fn make_favorite_topping() { unimplemented!() }
fn assemble_pizza(crust: Crust, sauce: Sauce, topping: Topping) { unimplemented!() }

impl Dish for Pizza {
    fn prepare(oven: &Oven) -> Self {
         let dough = make_dough();
         let sauce = make_tomato_sauce();
         let crust = oven.prebake(dough);
         let topping = make_favorite_topping();
         let unbaked_pizza = assemble_pizza(crust, sauce, topping);
         oven.bake(unbaked_pizza)
    }
}

Second approach
Well, this is closer to what I would do, but it's perhaps a little over-the-top. Let's go back to the Pizza example, but let's assume that we want to accommodate combinations of all kinds of toppings. You could organize it like this:
pizza
├── pizza.rs
├── toppings.rs
└── mod.rs

In the above, mod.rs only imports the necessary types from pizza.rs and toppings.rs. The API of the pizza module is defined in mod.rs, but no actual implementation is done here. Rather, implementations are logically grouped depending on where they make the most sense, so that you should be able to find the appropriate types quickly just by looking at the filenames. You wouldn't expect to find anything about "dough" in topping.rs, would you? So it's probably in pizza.rs.
My (personal) guidelines for dividing things into individual (internal) modules is the following:

Separate concepts should be in separate files
For related things, start with a single file and break up as necessary
mod.rs should not contain implementations or definitions, but rather export the user-facing API. You can think of it as "transforming" the internal file organization into the API that the user sees.
If you find yourself naming modules or functions "helper", it might indicate that you're not setting the logical boundaries in the right places (however, there are many exceptions to this)

Especially the third point is not obeyed by many parts of rulinalg, and this is of course fair since I'm just stating my personal preferences here. That said, I do wish we could move more towards this pattern in the long run.

Thanks everybody, especially @Andlon. I guess that I have enough information to "standardize" my next PRs.
I look forward for formal code guidelines but this issue is too specific to such discuss, then @AtheMathmo can close it.

I agree - some additions to the contributions doc would be a good idea!


Android Compose Generics Objects and Extensions

Name of the Codelab or Codelab URL
https://developer.android.com/codelabs/basic-android-kotlin-compose-generics?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-compose-unit-3-pathway-1%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-compose-generics#6
Describe the problem
The printed text does not seem to correspond to the previous code.
In which lesson and step of the codelab can this issue be found?
Lesson "Generics, objects, and extensions", step 7, subtitle "Replace long object names using let()", step 6.
How to reproduce?
Versions
Additional information
codelab: basic-android-compose-training-add-scrollable-list

Hello @jensmoths ,
Thank you for reaching out to us. The code snippet was updated:


Windows support for pytest

I use several platforms for development, so suffered from some Windows incompatibility in the way it works with filesystem.
This should allow tests to pass in Windows platform.

@kevin-bates rebased


without use val dataset?

without use val dataset?
how about add it?

You can add it if you like. Similar to training. However, loss or accuracy of paired images can't represent tracking performance since tracking is a sequential problem.

Since no further question is asked, I'm closing it for now.
Please reopen it or create a new issue if you have further question.

You can add it if you like. Similar to training. However, loss or accuracy of paired images can't represent tracking performance since tracking is a sequential problem.

Excuse me , Whether what you said means that the process of training doesn't make use of the vid.json  in the dataset VID?


Cache repeated string instances in the lexer

When lexing a typical source file, there's going to be a lot of repeated strings - identifiers, literals, white space, and so on. We can't intern these, but it would make good sense to cache tokens up to a certain length and return the same instance instead of building them up repeatedly.
To implement this, instead of building up the token string in a StringBuilder, we would keep track of where the token starts and ends. When creating the token, if the length is below our caching threshold, we first look it up in the token cache. For larger tokens, we shouldn't bother as the lookup will take too long to be worth it.

Along with this work, we should also create lexed strings through SourceText.ToString(SourceTextSpan).

https://github.com/dotnet/runtime/issues/27229 should make this quite a bit easier to implement in .NET 9.


Add CI to verify Nix build

Because other projects depend on the ability for our flake to be build-able, it seems sensible to check build-ability in the CI.
I used GitHub actions because it's easier for me to write.

As I had hoped, this failed because it needs #40. So, this is a good check that we can indeed build on Linux!

With #40 merged this now passes!


[DOC-4544] Helm now defaults to secure deployments

[DOC-4544]
Related to https://github.com/cockroachdb/helm-charts/pull/166/
Includes some light restructuring and copyediting.

This change is


feat(aws-eventbridge-sqs) created new construct

Issue #292 , if available:
Description of changes:
-Created new construct aws-eventbridge-sqs
-Updated aws-events-rule-sqs to wrapper to support new construct
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-fkVQbXRiQi6A
Commit ID: 0e2fae9b49626deded668ff37a6b1ff3a661c13c
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-fkVQbXRiQi6A
Commit ID: 0ed60b1f7bb6dcf1f769be0be888fa80256531ec
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-fkVQbXRiQi6A
Commit ID: c19fd6c1427adbfcb820f4880485b12b3d02eb08
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Replace .format calls w/ f-strings

F-strings are slightly faster than format calls.

Thanks!

Of course!

On May 7, 2019, at 8:28 PM, Ryan Shtirmer<EMAIL_ADDRESS>wrote:
Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/rshtirmer/ArcticWatch/pull/1#issuecomment-490302194, or mute the thread https://github.com/notifications/unsubscribe-auth/AKKMMKEGQJ34UT36MXSZM7DPUINDVANCNFSM4HLNI4OQ.


Gateways, allow for configuring a gatewaygroup as the default gateway.

Gateways, allow for configuring a gatewaygroup as the default gateway.
-Avoid changing routes by just visiting a webgui page.
-Avoid change some unneeded events when nothing changed.
There probably are still some improvements to be done.. Like using using the current checkboxes to set a default gateway, and converting the current config to the new selection box..
@jim-p can you tell if this pullrequest as a whole is going 'in the right direction' ?
p.s. It should not yet be pulled in its current state (there is a little manual configuration needed).. but before putting more hours into this, i would like to know it has a good chance of getting pulled..

I spoke with @PiBa-NL on IRC about this, there are a couple more tweaks he's going to make before we try testing it out.

Good to know @jim-p. So I'll wait for it too. BTW, it's too big for 2.4 so I marked to be merged post 2.4.0 release

@PiBa-NL I haven't looked at your code yet, but does this patch somehow fix https://redmine.pfsense.org/issues/5476 ? Enable traffic from the firewall itself to route using PBR?

@luckman212 I don't touch the pf and its pbr functionality, though my patch is aimed at addressing the issues of pfSense not having dns and other functionality when its 'default' gateway is not available. It will pick a new default from the chosen gatewaygroup that is still 'up'. That doesnt make pbr work, as that would be configureable to behave different for different firewallrules matching traffic.. My patch only juggles with the default route..

@PiBa-NL Is this complete now, or is there still something else you planned to add/change?

not complete yet.. ive got several more changes to add.. but need to clean them up a bit.. ill try and do that in next few days.

In an effort to improve the tracking of changes and bug/feature requests, we have decided to require an entry on the pfSense Redmine issue tracker associated with every pull request, and likewise the Redmine entry should also have a link back to the pull request.
If you could, please associate this PR to a Redmine issue either by locating an existing issue at https://redmine.pfsense.org or by creating a new issue. Add a link to the Redmine issue that points to this PR, and also add a link on the PR to the Redmine issue.
For more information, see https://doc.pfsense.org/index.php/Submitting_a_Pull_Request_via_Github
Thanks!

Redmine issue: https://redmine.pfsense.org/issues/8187

Okay bumped to 17.6 .

I will do what I can to test and merge this week.

Okay thanks, rebased it.

Hello @sbeaver-netgate,
Have you test PR ? Do you think you can merge it for 2.4.4 ?


Solace config-key username__passwordfilepath  truncates password

Reference: RT27210
Workaround in place:
Read the contents of the secrets file into username__password
This workaround should removed once issue resolved.

This has been resolved since SolOS8.8


Some domain doesn't work

It works properly for some domain names but not all of them. For example, no hotmail.com email addresses are valid.

Since this doesn't work on most email providers nowadays, I propose to disable the SMTP check by default and mentioning it in the README (so you can activate it if needed).


Incorrect function name referenced in example?

svgToMiniDataURI() in README.md example vs svgToTinyDataUri() exported in code

Oh, good catch. It’s the default export so the name doesn’t matter as far as I know. Is it giving you problems?

It’s all good. Just mentioning it for consistency. Is it tiny or mini? Big decisions 🤣

As you might have sussed out, I waffled between the two before publishing.
Now I realize this will drop in popularity as soon as somebody grabs the nano-svg-data-uri package name.


Ensure correct tools installation in goenv mode

Tools will be installed in the appropriated directory when goenv manages GOPATH.
I tried to make it work on Mac, Linux (Ubuntu), ~and Windows but I have no way of testing it on Windows~ 😅
goenv doesn't seem to be supported on Windows.

Hi, @faustind
Thanks for the PR.
The only concern I have is goenv_mode will be called each time when go.nvim needs to execute a binary.
Could you add a local dict so the result will be stored locally?
e.g. in utils.lua
local installed = {}
...
if installed['gomodifytags'] then return true end
else
-- check if it installed
-- if installed
installed['gomodifytags'] = true
return true

@ray-x,
Thanks for the suggestion. I cached the information about the installed tools in utils.lua
But the tests for gotags appear to randomly fail: I had the same jobs run on the same commit on my fork here.
I suspect the 100ms wait for gotags action to take effect is not enough. So I bumped the wait time from 100ms to 500ms for go_tags_spec.lua in 8112fbc

Timeout error might be caused by github actions. Sometimes there is more traffic.


Dirty upgrade to 0.43. Cannot link

In addition to other reports onto 0.43.x problems #12261
I've spend the past 4 hours manual merging the react-native-git-upgrade conflicts. I'm pretty sure that all my files are ok, tho I still have issues like this one after linking.
Something went wrong while linking. Error: Expected "/*" or ";" but "\"" found.
Please file an issue here: https://github.com/facebook/react-native/issues

I can attach *.xcodeproj files and Android related ones.

Hey, thanks for reporting this issue!
It looks like your description is missing some necessary information. Can you please add all the details specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported.
I am going to close this, but feel free to open a new issue with the additional information provided. Thanks!


Deduplicate docstrings

There are a number of kwarg docstrings that are duplicated, especially across the various consumer classes. We should find a way to deduplicate these while still allowing the documentation generator to see them.

I'm actually going to close this for now. It's very low priority and not as straightforward as I first expected.


message_store: Migrate message_store to typescript.

This will help with #26803 and having typescript support for search pills

Merged, thanks @evykassirer and @evykassirer!


Adding text input event

This change uses the SDL_TEXTINPUT event to capture text input from the user. It's useful for text fields and should support characters that require multiple key presses.
Thoughts:

Should this accumulate a text string and output it or just return individual characters?
Flash requires a dummy text field to work properly. Is forcing focus the right way to handle text input?

Thanks again, as I think you know, this has already been integrated in :smile:


Windows fixes

WHY are these changes introduced?
Windows CI is broken, this should fix it.
1 actual issue (small, output-related) was found.

WHAT is this pull request doing?

Makes sure we're working with properly formatted paths in all cases, both in code and in tests. Once they're passed through any path method this happens automatically, but sometimes we need to path.normalize explicitly.
How to test your changes?


data values not right when opening Xarray-generated zarr with ncdump

ncdump version: 4.8.1 of Apr 25 2022 (this is what came with netCDF4-python 1.6.0 when I installed that)
xarray version: 2022.3.0
operating system: Mac OS Monterey
python version: 3.10.5
I found this issue using the netCDF4-python library, but I think it must be at the netcdf-c level because I'm seeing the same weird data values with ncdump. That's why I'm submitting the ticket here rather than in the netCDF-python project.
To reproduce the issue:
1.  Create two directories: "download" for the netCDF file and "generated" for the zarr store.
2. Download the netcdf file into the download directory. Call it "GLDAS_NOAH025_3H.A20000101.0300.021.nc4": "https://hydro1.gesdisc.eosdis.nasa.gov/opendap/GLDAS/GLDAS_NOAH025_3H.2.1/2000/001/GLDAS_NOAH025_3H.A20000101.0300.021.nc4.nc4?time[0:1:0],lon[0:1:1439],lat[0:1:599],Rainf_tavg[0:1:0][0:1:599][0:1:1439]"
You will need to have earthdata login credentials download this URL. If you don't already have an earthdata login credential, you can create one for free here: https://urs.earthdata.nasa.gov/
3. Generate zarr using python's Xarray library. Verify that the latitude variable has values between -59.875 and 89.875
import xarray as xr
# read in the netCDF file
ds = xr.load_dataset("download/GLDAS_NOAH025_3H.A20000101.0300.021.nc4")

# check that latitude values look good. They should range from -59.875 to 89.875
print("Latitudes in original NetCDF4/HDF file:")
print(ds["lat"].values[:])

# write out zarr
ds.to_zarr("generated")

# read it in zarr using xarray
ds_from_zarr = xr.open_zarr("generated")

# print the latitudes again
print("Latitudes in zarr store, according to xarray:")
print(ds_from_zarr["lat"].values[:])

4. Now run ncdump on that zarr store:
ncdump -v lat "file://`pwd`/generated/#mode=nczarr,zarr"

ncdump gives me:
netcdf \#mode\=nczarr\,zarr {
dimensions:
	time = 1 ;
	lat = 600 ;
	lon = 1440 ;
variables:
	float Rainf_tavg(time, lat, lon) ;
		Rainf_tavg:cell_methods = "time: mean" ;
		Rainf_tavg:long_name = "Rain precipitation rate" ;
		Rainf_tavg:missing_value = -9999. ;
		Rainf_tavg:standard_name = "rainfall_flux" ;
		Rainf_tavg:units = "kg m-2 s-1" ;
		Rainf_tavg:vmax = 0.00333840004168451 ;
		Rainf_tavg:vmin = 0. ;
	float lat(lat) ;
		lat:axis = "Y" ;
		lat:long_name = "latitude" ;
		lat:standard_name = "latitude" ;
		lat:units = "degrees_north" ;
	float lon(lon) ;
		lon:axis = "X" ;
		lon:long_name = "longitude" ;
		lon:standard_name = "longitude" ;
		lon:units = "degrees_east" ;
	double time(time) ;
		time:axis = "T" ;
		time:bounds = "time_bnds" ;
		time:calendar = "standard" ;
		time:long_name = "time" ;
		time:standard_name = "time" ;
		time:units = "minutes since 2000-01-01T03:00:00" ;

// global attributes:
		:CDI = "Climate Data Interface version 1.9.8 (https://mpimet.mpg.de/cdi)" ;
		:CDO = "Climate Data Operators version 1.9.8 (https://mpimet.mpg.de/cdo)" ;
		:Conventions = "CF-1.6" ;
		:DODS_EXTRA.Unlimited_Dimension = "time" ;
		:DX = 0.25 ;
		:DY = 0.25 ;
		:MAP_PROJECTION = "EQUIDISTANT CYLINDRICAL" ;
		:SOUTH_WEST_CORNER_LAT = -59.875 ;
		:SOUTH_WEST_CORNER_LON = -179.875 ;
		:acc_definision_ = "past 3-hour accumulation" ;
		:comment = "website: https://ldas.gsfc.nasa.gov/gldas, [https://lis.gsfc.nasa.gov/"](https://lis.gsfc.nasa.gov/%22) ;
		:conventions = "CF-1.6" ;
		:history = "created on date: 2019-11-04T10:06:10.461\n2022-07-06 15:11:10 GMT Hyrax-1.16.3 [https://hydro1.gesdisc.eosdis.nasa.gov/opendap/GLDAS/GLDAS_NOAH025_3H.2.1/2000/001/GLDAS_NOAH025_3H.A20000101.0300.021.nc4.nc4?time[0:1:0],lon[0:1:1439],lat[0:1:599],Rainf_tavg[0:1:0][0:1:599][0:1:1439]"](https://hydro1.gesdisc.eosdis.nasa.gov/opendap/GLDAS/GLDAS_NOAH025_3H.2.1/2000/001/GLDAS_NOAH025_3H.A20000101.0300.021.nc4.nc4?time[0:1:0],lon[0:1:1439],lat[0:1:599],Rainf_tavg[0:1:0][0:1:599][0:1:1439]%22) ;
		:inst_definision_ = "instantaneous" ;
		:institution = "NASA GSFC" ;
		:missing_value = -9999. ;
		:references = "Rodell_etal_BAMS_2004, Kumar_etal_EMS_2006, Peters-Lidard_etal_ISSE_2007" ;
		:source = "Noah_v3.6 forced with GDAS-AGRMET-GPCPv13rA1" ;
		:tavg_definision_ = "past 3-hour average" ;
		:title = "GLDAS2.1 LIS land surface model output" ;
data:

 lat = 1.892592e-36, 3.363116e-42, 3.363116e-42, 1.027152e-42, 2.802597e-44,
    1.821688e-44, 9.187894e-41, 1.301912e+10, 0, 1.040324e-41, 4.706426e-38,
    2.879904e-39, 2.32714e-29, 6.779446e-31, 2.734375, 5.36916e+08,
    -3.011738, 1.592435e-37, 1.849173e+28, 7.11524e+25, 2.731982e+23,
    1.048661e+21, 4.023993e+18, 1.543614e+16, 5.919361e+13, 2.269132e+11,
    8.695368e+08, 3330835, 12754.07, 48.81667, 0.1867685, 0.000714246,
    2.730185e-06, 1.043104e-08, 3.98332e-11, 1.520318e-13, 5.799419e-16,
    2.210975e-18, 8.424034e-21, 3.207596e-23, 1.220529e-25, 4.640977e-28,
    1.763385e-30, 6.694873e-33, 2.539658e-35, 9.625514e-38, -4.236914e+37,
    -6.286951e+32, -9.282427e+27, -1.368977e+23, -2.016553e+18,
    -2.966634e+13, -4.358293e+08, -6393.224, -0.09363129, -1.368862e-06,
    -1.997411e-11, -2.908485e-16, -4.225408e-21, -6.123076e-26,
    -8.848101e-31, -1.274586e-35, 3.303676e+35, 7.206622e+25, 1.564891e+16,
    3380374, 0.00072578, 1.547172e-13, 3.270122e-23, 6.840453e-33,
    -1.59729e+32, -7.589868e+12, -3.516092e-07, -1.581693e-26, 4.694368e+24,
    1.022974e-14, -3.22165e+10, 1.902141e-19, -2.000046, -1.05047e-09,
    1.769917e-24, 8.805741e+14, -2.041029e-31, -4.678544e-12, -1.031469e+08,
    -2.213423e+27, 2.463612e-35, 1.179822e-25, 5.624584e-16, 2.655094e-06,
    12431.56, 5.780842e+13, 2.672488e+23, 1.229273e+33, -7.610976e-37,
    -5.297439e-32, -3.67447e-27, -2.540968e-22, -1.752325e-17, -1.20547e-12,
    -8.27416e-08, -0.005667652, -387.498, -2.644775e+07, -1.802269e+12,
    -1.226348e+17, -8.333297e+21, -5.655496e+26, -3.833648e+31,
    -2.595822e+36, 2.369355e-38, 6.207163e-36, 1.637371e-33, 4.315412e-31,
    1.136424e-28, 2.990341e-26, 7.862878e-24, 2.066044e-21, 5.425129e-19,
    1.423664e-16, 3.733745e-14, 9.786652e-12, 2.563819e-09, 6.712972e-07,
    0.0001756818, 0.04595492, 12.01544, 3140.204, 820340.4, 2.142179e+08,
    5.591773e+10, 1.45909e+13, 3.805914e+15, 9.92399e+17, 2.586839e+20,
    6.74083e+22, 1.755994e+25, 4.57302e+27, 1.190578e+30, 3.098784e+32,
    8.063204e+34, 2.097541e+37, -1.180068e-38, -1.917611e-37, -3.115383e-36,
    -5.060139e-35, -8.217065e-34, -1.334065e-32, -2.16544e-31, -3.514201e-30,
    -5.701917e-29, -9.24978e-28, -1.500239e-26, -2.432821e-25, -3.944415e-24,
    -6.394106e-23, -1.036344e-21, -1.679409e-20, -2.721068e-19,
    -4.408132e-18, -7.140087e-17, -1.156346e-15, -1.872445e-14,
    -3.031579e-13, -4.907593e-12, -7.943455e-11, -1.285562e-09,
    -2.080273e-08, 5.115416e-39, -39.75, 4.658682e-20, 3.355623e+07,
    1.607556e-40, 7.018674e-38, -0.1259727, 0.7431449, 0.7470588, 3.003921,
    4.82226e-40, 3.547074e-38, 39.82422, 2.778307e+10, 48.5647, 9.24857e-44,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
    0, 0, 0, 0, 0, 0, 0, 0 ;
}

Thanks; I'm working on the Fortran release right now but we will take a look!

Can you send us a list of the expected values of lat?

Since I was not in a position to use python xarray directly, I tried the following instead. Note that I was using the current netcdf-c master, not 4.8.1

I used nccopy to create a zarr format file from the original .nc4.
I then used ncdump to dump the lat variable values and compared them to a dump of the lat values from the original .nc4. They appear to be the same.

So, I am attaching my zarr file to this message; you might see what python does with it. It is in file directory zarr format.
gldas.tar.gz

This is the zarr store I generated with xarray:
generated.tar.gz
e

Strangely, when I open your dataset with xarray, the latitude values look fine:

Ok, I can think of two reasons for this.

netcdf-c is not finding the filter (libz aka deflate) used in the file.
the python code is writing information that I did not expect or I am mis-interpreting.

#1 is the most likely cause. If you can send me the zarr file created by your python code, I can see if it is readable by netcdf-c version 4.9.0.

Assuming that filters are the problem, can you tell me where you are storing them?
Perhaps you are setting HDF5_PLUGIN_PATH, and if so, what is its value?

Awesome!
The tricky thing is that I didn't install any NetCDF or HDF stuff directly. I'm using anaconda python. So I used anaconda's package manager, conda, to install the NetCDF python package. Because NetCDF python needs NetCDF-C, conda installed that stuff too.
The good news is that anaconda isolates the stuff it installs for packages pretty well. So if you can give me some specific filenames to look for, I should be able to do that.

% uname -a
Darwin gs6102dscmc1csm 21.5.0 Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:22 PDT 2022; root:xnu-8020.121.3~4/RELEASE_X86_64 x86_64

@DennisHeimbigner @WardF Getting netCDF-C 4.9.0 for conda will require solving the build issues encountered on the update PR: https://github.com/conda-forge/libnetcdf-feedstock/pull/140  We'd love any help you all can give on that.

Am I understanding correctly that filters are somehow related to the compression? Can I somehow pick a different compression scheme that would work? Or is it that just reading the zarr chunks won't work regardless of compression?

Also, in the file you sent, the compressor was libz (aka zlib) (aka deflate).
You can read about it here: https://www.zlib.net/

I was more thinking about the fact that I am currently the one creating these zarr stores. So I can pick which compression algorithm is used. Can I pick one that should work when I read it back out?

I think I see. So yes, you can use whatever is supported by python zarr.
See here: https://numcodecs.readthedocs.io/en/stable/.

Okay! I created a zarr store where none of the variables have compression and I can run ncdump on everything just fine.
Note: This is  different data. I didn't use xarray. I used zarr and then I hand-crafted the additional metadata, so there may be mistakes.
zarr_no_compression.tar.gz
This should get me through my ESIP presentation the week after next. So thank you for all your assistance. I look forward to seeing the fix where the compression stuff is sorted out.

@dopplershift, I see that https://github.com/conda-forge/libnetcdf-feedstock/pull/140 was resolved last September, so I tried grabbing the latest anaconda python package of netCDF4, 1.6.2. Unfortunately, I'm getting what appears to be version 4.8.1 of the NetCDF-C library. Any idea when I should see v. 4.9.0 of the NetCDF-C library?
% python
Python 3.11.0 | packaged by conda-forge | (main, Jan 14 2023, 12:26:40) [Clang 14.0.6 ] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import netCDF4
>>> netCDF4.__version__
'1.6.2'
>>> exit()

% ncdump
ncdump [-c|-h] [-v ...] [[-b|-f] [c|f]] [-l len] [-n name] [-p n[,n]] [-k] [-x] [-s] [-t|-i] [-g ...] [-w] [-Ln] file
  [-c]             Coordinate variable data and header information
  [-h]             Header information only, no data
  [-v var1[,...]]  Data for variable(s) <var1>,... only
  [-b [c|f]]       Brief annotations for C or Fortran indices in data
  [-f [c|f]]       Full annotations for C or Fortran indices in data
  [-l len]         Line length maximum in data section (default 80)
  [-n name]        Name for netCDF (default derived from file name)
  [-p n[,n]]       Display floating-point values with less precision
  [-k]             Output kind of netCDF file
  [-s]             Output special (virtual) attributes
  [-t]             Output time data as date-time strings
  [-i]             Output time data as date-time strings with ISO-8601 'T' separator
  [-g grp1[,...]]  Data and metadata for group(s) <grp1>,... only
  [-w]             With client-side caching of variables for DAP URLs
  [-x]             Output XML (NcML) instead of CDL
  [-Xp]            Unconditionally suppress output of the properties attribute
  [-Ln]            Set log level to n (>= 0); ignore if logging not enabled.
  file             Name of netCDF file (or URL if DAP access enabled)
netcdf library version 4.8.1 of Oct 31 2022 22:27:12 $

@christine-e-smit We held off on migrating conda-forge packages to 4.9.0 because 4.9.1 was intended to be a quick follow-on. As I understand it, 4.9.1 should be about there and we can proceed with the needed rebuilds then. (@WardF 😉 )

@dopplershift  - thanks for the clarification. I skimmed over the relevant comment, I'm afraid, and focused on the "it's merged" part.

thanks; working on that now :).


[Skflow] Move skflow to learn and make it available by default.

Builds on top of #1832

@ilblackdragon README seems to be broken in .md format.

Can you rebase?

I merged #1829 and #1832, but conflicts.

Done.


Live preview with copy & paste

Hey @yeun @makepanic,
I was just thinking an additional, very nice feature would be a live preview of the colors (html) with a copy functionality (user should be able to choose the format?).
Just like here: http://flatuicolors.com
For example I am currently using the colors as defaults for some web components. However, I am not loading the package into the components to keep it small. For this kind of workflow, or other design tools that do not have a palett to include, this would be very awesome addition to /docs.

I'm not sure if @yeun wants to add this feature, but there are in general 2 ways of implementing it:

maximum compatibility: http://zeroclipboard.org/ which is old and relies on flash but has a better compatibility with older browsers
native browser api: execCommand which doesn't support older browser versions (minimum Chrome 43, FF 41, IE9, Safari 10).

There's a lib that uses execCommand and falls back to an input where the user has to manually copy the selection: https://clipboardjs.com/#browser-support

Hey @makepanic I would think something like the last lib would be idea. Since it is just a nicety feature, I think requiring modern browser support for convenience features is fine. 👍

Sorry, I'd like to keep the UI simple as possible, not thinking of browser support / progressive enhancement / etc. If you want to discuss more, please reopen.


X12 - Segment ISA - C

Hi,
I am puzzled because the ISA "component element separator" cannot be read (at positiion 16)
ISA*00*          *00*          *ZZ*SENDER         *ZZ*RECEIVER       *230912*1312*U*00401*000000001*0*T*>~

    [EdiValue("X(1)", Path = "ISA/15", Description = "ISA16 - Component Element Separator")]
    public string ISA_16_ComponentSeparator { get; set; }

The value is just null.
However, by implementing the interface IEdiGrammar, it works if the function IsSpecial does not take care of the ComponentDataElementSeparator.
    public bool IsSpecial(char character)
    {
        return character == SegmentNameDelimiter
               //|| character == ComponentDataElementSeparator
               || character == DataElementSeparator
               || character == SegmentTerminator;
    }

Please could you help me to understand ? Is it a parser issue ?
Additionally, we are specifying the ComponentDataElementSeparator in the grammar instead reading it from the file. I am not sure if this is critical, but could be potentially annoying I suppose. (see #244)
Thank you for your library and many thanks in advance for your answer.

The abstraction does not handle well the case of the X12 EDI format in terms of discovering the grammar by inspecting the first line (it was based on EDI Fact where it is simper).
The way it works now is in order to read and bind the first line because it also contains data itsef is by knowing the grammar upfront (delimiters etc.).
What needs to change:

I should be reading the first element ISA since it is of fixed length 106 characters
Figure out the delimiters from their fixed positions and update the grammar.
and then move the position of the stream to the beginning in order to start reading binding/deserializing.

While this is not such a difficult task I have not found the time to update the codebase in quite some time.
The above process is not compatible to the way the EDIFact figures out the grammar at the moment so we must make changes by not breaking the expected behavior.
If it is something you are up then fell free to make a pull request and I will try to check it out.

OK I understand.
I am currently not at a level where I can contribute, I am still discovering the EDI format, and I am currently making the EDI 940 and 943 object models. (note: It not so easy to make reusable segment object through different document type)
I will definitely try to contribute back later, once I really understand everything.


update-checkout: use semantic revision

Use the semantic name (v2.1.0-rc1) instead of an explicit ref to make it
easier to identify the revision in use.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test tensorflow

Sometimes we have to clean test when we change the update-checkout-config.json. I'll try triggering that.

@swift-ci please clean test tensorflow

CI fails with this error:
Updating '/home/swiftci/jenkins/workspace/swift-PR-TensorFlow-Linux/swift-tools-support-core'
Error on repo "/home/swiftci/jenkins/workspace/swift-PR-TensorFlow-Linux/swift-tools-support-core": Traceback (most recent call last):
  File "/home/swiftci/jenkins/workspace/swift-PR-TensorFlow-Linux/swift/utils/update_checkout/update_checkout/update_checkout.py", line 91, in update_single_repository
    config, repo_name, scheme_name, scheme_map, cross_repos_pr)
  File "/home/swiftci/jenkins/workspace/swift-PR-TensorFlow-Linux/swift/utils/update_checkout/update_checkout/update_checkout.py", line 58, in get_branch_for_repo
    scheme_branch = scheme_map[repo_name]
KeyError: u'swift-tools-support-core'

This error occurs because CI was last triggered for the tensorflow-merge -> tensorflow PR https://github.com/apple/swift/pull/28847, which involved changes to update-checkout-config.json.
Sometimes, CI machines are left in an incompatible state after testing tensorflow-merge -> tensorflow PRs, so a clean test (@swift-ci Please clean test tensorflow) is necessary.
This error should naturally go away when https://github.com/apple/swift/pull/28847 is merged soon today. I'd recommend waiting for that PR to be merged before this one.

@swift-ci please clean test tensorflow

@swift-ci Please clean test tensorflow

@swift-ci Please clean test tensorflow

CI fails:
You have bazel 0.26.1 installed.
Please upgrade your bazel installation to version 0.27.1 or higher to build TensorFlow!

I'll update bazel on all CI machines now.

@swift-ci Please test tensorflow


Interested in learning the logic which maps a library to CPE

I am looking for the logic which maps a developer library to CPE information.  I have already reviewed Jeremy's presentation which talks about lucene indexes.
Would you be able to point me in right direction?

The wiki discusses this some: https://github.com/jeremylong/DependencyCheck/wiki
The actual matching is done in the CPEAnalyzer: https://github.com/jeremylong/DependencyCheck/blob/main/core/src/main/java/org/owasp/dependencycheck/analyzer/CPEAnalyzer.java
Basically, we make a lucene index of the CPE vendor/product information and do searches with some added analyzers using the collected evidence.


Any plan for release date?

Guys we're going to create a new project and I'm absolutely willing to use your boilerplate, but it's at alpha/beta/unknown phase and you know it's a little bit risky to use it at an enterprise project, Do you have any idea about your first stable release?

We don't have a date, other than we're continuously chipping away at this in-between our client projects which mostly use this setup.
IMO, boilerplates projects like this tend to be in this state of perma-transition.
You likely took a look through, do you have any questions about dependency choices? techniques? lack of techniques?  over-engineering?  under-engineering?

We're getting close. Personally I'd like to be able to call it "stable" by Chain React in a few weeks, but we'll still be developing it after that point.

@kevinvangelder where does the stability of Bowser stand now, apart from the issues with RN 0.57.3?

@AlirezaAkbarix Thank you for the report. We plan to spend a lot more time testing Windows devices in the future. This project is open source, so if you're able to submit a pull request we'll definitely take a look.
Thank you!


Endless loading due to MongoDB ObjectID

Was getting an endless loading state in vike-react vike-react-query when using telefunc with MongoDB.
Here is an example
export default async function getEvent(eventCode: string) {
  const client = new MongoClient(process.env.MONGODB_CONNECTION_STRING || "");
  const db = client.db(process.env.MONGODB_DATABASE_NAME);

  const eventsDB = db.collection("Events");

  const event = await eventsDB.findOne<any>({
    Code: eventCode,
  });

  return event;
}

It can easily be fixed by converting the _id property from an objectID to a string, or delete the _id, filing because there was no error messages

Can you publish a reproduction? That'd be the best. I'll re-open then.


Move code from ORNL's Gitlab to Github and open source it

Move the code that Kris used in his dissertation from ORNL's Gitlab to Github.

Completed.


mup can't deploy with meteor 1.2.1

Hi, I'm using meteor 1.2.1 into Ubuntu 14.04 LTS server and this is my mup.json configuration:
{
  "servers": [
    {
      "host": "SERVER_IP",
      "username": "myapp",
      "pem": "myapp.pem"
    }
  ],
  "setupMongo": false,
  "setupNode": true,
  "nodeVersion": "0.10.40",
  "setupPhantom": false,
  "enableUploadProgressBar": false,
  "appName": "myapp",
  "app": ".",
  "env": {
    "ROOT_URL": "DOMAIN",
    "MONGO_URL": "mongodb://localhost:27017/myapp",
    "DISABLE_WEBSOCKETS": "1"
  },
  "deployCheckWaitTime": 120
}

I setup the server with mup setup and it's fine, but when I run mup deploy, it shows this error:
Invoking deployment process: FAILED

    -----------------------------------STDERR-----------------------------------
     args   '-Dnode_lib_file=node.lib',
    gyp info spawn args   '-Dmodule_root_dir=/opt/myapp/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt',
    gyp info spawn args   '--depth=.',
    gyp info spawn args   '--no-parallel',
    gyp info spawn args   '--generator-output',
    gyp info spawn args   'build',
    gyp info spawn args   '-Goutput_dir=.' ]
    gyp info spawn make
    gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
    gyp info ok
    npm WARN package.json<EMAIL_ADDRESS>No description
    npm WARN package.json<EMAIL_ADDRESS>No repository field.
    npm WARN package.json<EMAIL_ADDRESS>No README data
    stop: Unknown instance:
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed
 0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) Failed to connect to localhost port 80: Connection refused
    App did not pick up! Please check app logs.
    -----------------------------------STDOUT-----------------------------------
    > node ./build.js

    `linux-x64-v8-3.14` exists; testing
    Binary is fine; exiting
<EMAIL_ADDRESS>node_modules/ansi-regex

<EMAIL_ADDRESS>node_modules/ansi-styles

<EMAIL_ADDRESS>node_modules/chalk

<EMAIL_ADDRESS>node_modules/escape-string-regexp

<EMAIL_ADDRESS>node_modules/has-ansi

<EMAIL_ADDRESS>node_modules/strip-ansi

<EMAIL_ADDRESS>node_modules/supports-color

<EMAIL_ADDRESS>node_modules/eachline

<EMAIL_ADDRESS>node_modules/type-of

<EMAIL_ADDRESS>node_modules/amdefine

<EMAIL_ADDRESS>node_modules/asap

<EMAIL_ADDRESS>node_modules/underscore

<EMAIL_ADDRESS>node_modules/meteor-promise

<EMAIL_ADDRESS>node_modules/promise

<EMAIL_ADDRESS>node_modules/source-map-support

<EMAIL_ADDRESS>node_modules/semver

<EMAIL_ADDRESS>node_modules/source-map

<EMAIL_ADDRESS>node_modules/fibers
    Waiting for MongoDB to initialize. (5 minutes)
    connected
    myapp start/running, process 22270
    Waiting for 120 seconds while app is booting up
    Checking is app booted or not?
    ----------------------------------------------------------------------------

I'm using only three npm modules via meteorhacks:npm (which is running normally with meteor 1.2 localhost) and this is the packages.json:
{
  "formidable":"1.0.17",
  "xml2js":"0.4.10",
  "twit":"2.1.0"
}

This is the error when I run mup logs -f:
/opt/myapp/app/programs/server/node_modules/fibers/future.js:245
						throw(ex);
[SERVER_IP] Cannot find module 'formidable'[SERVER_IP]
[SERVER_IP] error: Forever detected script exited with code: 8[SERVER_IP]
[SERVER_IP] error: Script restart attempt #2976[SERVER_IP]
[SERVER_IP]
[SERVER_IP] /opt/myapp/app/programs/server/node_modules/fibers/future.js:245[SERVER_IP]
[SERVER_IP] 	[SERVER_IP] 	[SERVER_IP] 	[SERVER_IP] 	[SERVER_IP] 	[SERVER_IP] 	[SERVER_IP] throw(ex);[SERVER_IP]
[SERVER_IP] 	[SERVER_IP] 	[SERVER_IP] 	[SERVER_IP] 	[SERVER_IP] 	[SERVER_IP] 	[SERVER_IP]  [SERVER_IP]  [SERVER_IP]  [SERVER_IP]  [SERVER_IP]  [SERVER_IP]  [SERVER_IP] ^[SERVER_IP]
[SERVER_IP] Error: [SERVER_IP] Cannot find module 'formidable'[SERVER_IP]
[SERVER_IP] error: Forever detected script exited with code: 8[SERVER_IP]
[SERVER_IP] error: Script restart attempt #2977[SERVER_IP]

Could anyone help me solve this problem?

[<IP_ADDRESS>] x Invoking deployment process: FAILED

	-----------------------------------STDERR-----------------------------------
	     at Process.ChildProcess._handle.onexit (child_process.js:820:12)
	gyp ERR! System Linux 3.13.0-57-generic
	gyp ERR! command "node" "/opt/nodejs/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
	gyp ERR! cwd /opt/axmath/tmp/bundle/programs/server/npm/vsivsi_file-collection/node_modules/mongodb/node_modules/mongodb-core/node_modules/kerberos
	gyp ERR! node -v v0.10.36
	gyp ERR! node-gyp -v v1.0.1
	gyp ERR! not ok
	npm WARN package.json<EMAIL_ADDRESS>No description
	npm WARN package.json<EMAIL_ADDRESS>No repository field.
	npm WARN package.json<EMAIL_ADDRESS>No README data
	stop: Unknown instance:
	  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
	                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) Failed to connect to localhost port 80: Connection refused
	App did not pick up! Please check app logs.
	-----------------------------------STDOUT-----------------------------------
	rs
	> node ./build.js

	`linux-x64-v8-3.14` exists; testing
	Binary is fine; exiting
<EMAIL_ADDRESS>node_modules/ansi-regex

<EMAIL_ADDRESS>node_modules/ansi-styles

<EMAIL_ADDRESS>node_modules/escape-string-regexp

<EMAIL_ADDRESS>node_modules/chalk

<EMAIL_ADDRESS>node_modules/strip-ansi

<EMAIL_ADDRESS>node_modules/supports-color

<EMAIL_ADDRESS>node_modules/has-ansi

<EMAIL_ADDRESS>node_modules/eachline

<EMAIL_ADDRESS>node_modules/type-of

<EMAIL_ADDRESS>node_modules/amdefine

<EMAIL_ADDRESS>node_modules/asap

<EMAIL_ADDRESS>node_modules/underscore

<EMAIL_ADDRESS>node_modules/meteor-promise

<EMAIL_ADDRESS>node_modules/promise

<EMAIL_ADDRESS>node_modules/source-map-support

<EMAIL_ADDRESS>node_modules/semver

<EMAIL_ADDRESS>node_modules/source-map

<EMAIL_ADDRESS>node_modules/fibers
	Waiting for MongoDB to initialize. (5 minutes)
	connected
	axmath start/running, process 9313
	Waiting for 15 seconds while app is booting up
	Checking is app booted or not?
	----------------------------------------------------------------------------
Completed TaskList: Deploy app 'axmath' (linux)

Same problem, no npm modules. Meteor 1.2.1.

Changing to node version 0.10.40  should fix this.

I'm using 0.10.40, and we solve the problem removing from .gitignore the folder packages to send the node_modules we are using.

It seens that mup does not run fine with meteorhacks:npm into Meteor 1.2.1

I advocate mupx
Your log shows
gyp ERR! node -v v0.10.36

Glad it's working and thanks for the tips.

I update node, npm and install mupx, find a problem in my seed.js when app inits, fix it and now deploy successfully.

Oh double posters. I thought it was one. My apologies for any confusion.
I'm glad they're both working now!

the only file inside .gitignore is "local", packages not exits. This error appears:
/opt/leaderboard/app/programs/server/node_modules/fibers/future.js:245
throw(ex);
^
Error: /opt/leaderboard/app/programs/server/npm/npm-bcrypt/node_modules/bcrypt/build/Release/bcrypt_lib.node: invalid ELF header
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at bindings (/opt/leaderboard/app/programs/server/npm/npm-bcrypt/node_modules/bcrypt/node_modules/bindings/bindings.js:74:15)
at Object. (/opt/leaderboard/app/programs/server/npm/npm-bcrypt/node_modules/bcrypt/bcrypt.js:3:35)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
error: Forever detected script exited with code: 8.
If I try use node 0.10.40, "Meteor requires Node v0.10.40 or later."

looks like the same problem here. Whats the recommend way to fix this? In my mup.json i specified "nodeVersion": "0.10.40", and node -v shows 0.10.40 on the server. But why is it complaining about 0.10.36 ?
x Invoking deployment process: FAILED

	-----------------------------------STDERR-----------------------------------
	t_dir=/root/.node-gyp/0.10.36',
	gyp info spawn args   '-Dmodule_root_dir=/opt/myproject/tmp/bundle/programs/server/npm/npm-bcrypt/node_modules/bcrypt',
	gyp info spawn args   '--depth=.',
	gyp info spawn args   '--no-parallel',
	gyp info spawn args   '--generator-output',
	gyp info spawn args   'build',
	gyp info spawn args   '-Goutput_dir=.' ]
	gyp info spawn make
	gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
	gyp info ok
	npm WARN package.json<EMAIL_ADDRESS>No description
	npm WARN package.json<EMAIL_ADDRESS>No repository field.
	npm WARN package.json<EMAIL_ADDRESS>No README data
	  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
	                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (7) Failed to connect to localhost port 8080: Connection refused
	Latest deployment failed! Reverted back to the previous version.
	-----------------------------------STDOUT-----------------------------------
	odules/ansi-regex

<EMAIL_ADDRESS>node_modules/ansi-styles

<EMAIL_ADDRESS>node_modules/escape-string-regexp

<EMAIL_ADDRESS>node_modules/chalk

<EMAIL_ADDRESS>node_modules/supports-color

<EMAIL_ADDRESS>node_modules/has-ansi

<EMAIL_ADDRESS>node_modules/strip-ansi

<EMAIL_ADDRESS>node_modules/eachline

<EMAIL_ADDRESS>node_modules/type-of

<EMAIL_ADDRESS>node_modules/amdefine

<EMAIL_ADDRESS>node_modules/asap

<EMAIL_ADDRESS>node_modules/underscore

<EMAIL_ADDRESS>node_modules/meteor-promise

<EMAIL_ADDRESS>node_modules/promise

<EMAIL_ADDRESS>node_modules/source-map-support

<EMAIL_ADDRESS>node_modules/semver

<EMAIL_ADDRESS>node_modules/source-map

<EMAIL_ADDRESS>node_modules/fibers
	Waiting for MongoDB to initialize. (5 minutes)
	connected
	myproject stop/waiting
	myproject start/running, process 28266
	Waiting for 15 seconds while app is booting up
	Checking is app booted or not?
	myproject stop/waiting
	myproject start/running, process 28327
	----------------------------------------------------------------------------

I would suggest trying mupx and see if it works better for your deployment target.

@MasterJames is mupx now to be preffered over mup so that i should consider to migrate any time soon in general? I will try that tomorrow and give feedback.

From what I can tell. (Not official opinion).
It seems that mupx will move to the kadirahq suite and be the way forward. (Actually this was mentioned by Arunoda but not officially yet... soon)
Mupx didn't work better for every situation but I think meteorhacks support will be depreciated for the cleaner kadirahq projects of which mupx will be joining.
There's always galaxy! And I'm sure other players in meteor deployment shaping up for different situations and providers.

mup works, but only from scratch wit aws, try creating a new instance (in aws case), and then configure your mup file:
    {
      // Server authentication info
      "servers": [
        {
          "host": "ec2-0-0-0-0.us-west-1.compute.amazonaws.com",
          "username": "ubuntu",
          "pem": "~/Downloads/your-pem_file.pem"
        }
      ],

      // Install MongoDB in the server, does not destroy local MongoDB on future setup
      "setupMongo": true,

      // WARNING: Node.js is required! Only skip if you already have Node.js installed on server.
      "setupNode": true,

      // WARNING: If nodeVersion omitted will setup 0.10.36 by default. Do not use v, only version number.
      "nodeVersion": "0.10.40",

      // Install PhantomJS in the server
      "setupPhantom": true,

      // Application name (No spaces)
      "appName": "project-name-folder",

      // Location of app (local directory)
      "app": "/Users/Username/Documents/projects/project-name-folder",

      // Configure environment
      "env": {
        "PORT": 80,
        "ROOT_URL": "http://ec2-0-0-0-0.us-west-1.compute.amazonaws.com"
      },

      // Meteor Up checks if the app comes online just after the deployment
      // before mup checks that, it will wait for no. of seconds configured below
      "deployCheckWaitTime": 15
    }

run mup setup and mup deploy.
It worked for me

@caio-ribeiro-pereira I'm confused, so you deleted the .gitignore file from your meteor project to make mup deploy work?

@Goawayjose I just removed from .gitignore the packages folder and it worked for me.


setext_with_atx shouldn’t generate warnings when ATX only headers are used

Rule MD003 for headers should accept ATX only headers as well when setext_with_atx value is given to style option.
With this commit I added a test case that proves a fix is necessary.
@mivok this PR doesn’t contain the fix however. I :pray: you will still appreciate and add fixing commits. :beers:

I'm afraid this one is working as intended - the setext_with_atx rule was intended to say: h1 and h2 headers should be setext, and h3 onwards should be atx style. In other words, you should use setext headers if possible, but if you can't then ATX is fine. It's not really intended to say "you can use any of setext or atx".

@mivok thanks for the feedback. However, the following content in Markdown will get a linter warning/error:
# Header 1

## Header 2

### Header 3

Don't you think, this should be valid instead?


Request failed

Describe the bug
In log there are request failed and there is no update of the objects.
Screenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.
Versions:

Adapter version:
JS-Controller version

:
node js v14.17.6
nem 6.14.15

fixed

The Problem is still there


TopLoader stopped showing after upgrade to Next v14.

I have updated my proejct ot Next 14 and I can not able to see toploader.
In app/layout.tsx
import { Toaster } from "@/components/ui/toaster";
import<EMAIL_ADDRESS>import type { Metadata } from "next";
import NextTopLoader from "nextjs-toploader";

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return (
    <html lang="en" suppressHydrationWarning>
      <NextTopLoader height={500} zIndex={9999} color="black" />
      <body>
        {children}
        <Toaster />
      </body>
    </html>
  );
}

I have tried to make layout.tsx to a client component, it still not working.

Working on mine. :)

I have updated my proejct ot Next 14 and I can not able to see toploader.
In app/layout.tsx
import { Toaster } from "@/components/ui/toaster";
import<EMAIL_ADDRESS>import type { Metadata } from "next";
import NextTopLoader from "nextjs-toploader";

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return (
    <html lang="en" suppressHydrationWarning>
      <NextTopLoader height={500} zIndex={9999} color="black" />
      <body>
        {children}
        <Toaster />
      </body>
    </html>
  );
}

I have tried to make layout.tsx to a client component, it still not working.

Seems like you're not using the TopLoader inside the body tags, just include the TopLoader inside the body tags.
export default function RootLayout({ children }: { children: React.ReactNode }) {
   return (
     <html lang="en">
       <body>
         <NextTopLoader height={500} zIndex={9999} color="black" />
         {children}
         <Toaster />
       </body>
     </html>
   );
 }


Month displayed is not synced with the provided date

Hello and thanks for this well designed library!
Anyway I found a bug (or maybe it is a design choice?).
If I pass a date as props to SingleDatePicker that it outside the current month(s), like this:
<SingleDatePicker
    focused
    date={moment().add(70, 'days')}
/>

The DayPicker keep showing the current month(s) without displaying the selected date, and that may confuse the user.
I think that the right behaviour is that if a date is provided then the DayPicker should show the month of that date instead the current one.

I think you are right! and I think this is a duplicate issue of https://github.com/airbnb/react-dates/issues/17
We've had a lot of discussion there, but I think the best way to do this moving forward is to provide a prop that allows the parent component to set the visible month on opening. If we allow that to be a moment object, it'd be very easy to do as you describe:
const date = moment().add(70, 'days');
<SingleDatePicker
  focused
  date={date}
  initialVisibleMonth={date}
/>

I'm going to close this issue as a duplicate, but feel free to hop on the conversation over there!

Sorry, I didn't notice that there was already an issue opened! I will follow there, thanks for your response!


Can't resolve 'Fabric/fabric.require' in node_modules.

Module not found: Error: Can't resolve 'fabric/dist/fabric.require' in '.\node_modules\tui-image-editor\dist'
I've already looked at former issues with fabric, these are not fixing the problem.
Version

"tui-image-editor": "^3.2.2"
Angular 6.1.0
Node 8.11
Tried with fabric 1.6.7 and 2.4.2
// Write example code
instance = new ImageEditor(document.querySelector('#tui-image-editor'),
        { cssMaxWidth: 700, cssMaxHeight: 500, selectionStyle: { cornerSize: 20, rotatingPointOffset: 70 }
        });

"Fixed" the problem by replacing
HTTP = require("http"), HTTPS = require("https")
into
HTTP = require("@angular/http"), HTTPS = require("@angular/http")

"postinstall": "npm install --no-save --no-optional<EMAIL_ADDRESS>
this seems to be a work-around

This issue is very annoying. How can I solve this using yarn?

@Fridthjof 's solution worked for me, I also modified the fabric.js file.

@hestellez what did you change in fabric.js?

The solution here and in documentation didn't work for me, unfortunately.

"Fixed" the problem by replacing
HTTP = require("http"), HTTPS = require("https")
into
HTTP = require("@angular/http"), HTTPS = require("@angular/http") in the fabric.require.js file.

Inside node modules, I don't know If there are problems when deploying, but it let me work for the moment

I got the same issue when I tried to install it, and this command solved the issue!
      npm install --save --no-optional<EMAIL_ADDRESS>

There is no fabric.require.js in fabric/dist/, there is only fabric.js but tui-image editor is still looking for fabric.require
Could somebody finally please fix this? The suggested workarounds did not help in my case.

It was released in v3.7.3.


Checking package only if Glog dependency is enabled(WITH_GLOG_DEPENDE…

Conditional check for the Glog package.

From my side looks fine, I'd wait for @SeptimiuVana's approval as well


Rework recycleview for consistnecy and efficiency

This PR basically reworks recycleview to make it more consistent and performant. I reworked it like a piece of dough, so it has many changes throughout and hopefully did not go down the road of undesired changes. I do think this makes it a lot more consistent and cleans up some remaining issues.
Here are some of the bigger changes:

I made RecycleView a ScrollView because I don't see the reason for wrapping it. The scrollview props should be available to the user, e.g. scroll pos, effects, etc. Otherwise we'd have to wrap access to them. Also, e.g. the view manager already assumes that there's a scrollview in the stack by setting its props etc. So why not make RecycleView a scrollview directly?
Instead of making container hardcoded, I made it a property so it can be changed. Not sure this is needed, but it makes it more robust.
I removed the default_adapter/layout manager and made them alias props which cleans up the on_adapter etc methods. Also, similar to default adapter/manager, if it is set to None, we create a default adaper/manager.
Really though, I think we should not do this but leave it to None at the user's peril, except for initially making sure it's not None. But if the user sets it to None, they probably know what they are doing.
In order to ensure that the least amount of updates is done to the views I added _refresh_flags to RecycleView. Setting these flags depending on what changed requiring the update we can do this. Here's the flags and it's doc in that class:

_refresh_flags = {
        'recycleview': True, 'data': True, 'data_size': True,
        'data_add': True, 'view': True
    }
    '''These flags indicate how much the view is out of sync and needs to
    be synchronized with the data. The goal is that the minimum amount
    of synchronization should be done. The flags are ordered such that for
    each flag, all the ops required for the proceeding flags are reduced by
    some known info about the change causing the refresh.

    Meaning of the flags:
    -recycleview: Initial setup of the recycleview itself. E.g. do_scroll_x.
        Updates everything.
    -data: Signal that the data changed and all the attributes/size/pos
        may have changed so they need to be recomputed and all attrs
        re-applied. This
    -data_size: Signal that the pos/size attrs of the data may have changed,
        new data may have been added, and or old data was removed. However,
        no existing data attrs was changed, beyond the size/pos values. This
        means that we don't need to re-apply the data attrs, other than
        size/pos for existing data insatances because they did not change.
        Added data will get new class instances and will have their values
        applied.
    -data_add: Similar to `data_size`, except that data, if added, was added
        at the end. This will allow further possible optimizations, but may
        be implemented as `data_size`.
    -view: The items visible changed, so we have to move our viewport.
        Other than viewport, nothing is recalculated.
    '''

Note: https://github.com/kivy/kivy/pull/3483 is required for this to work. That PR allows us to know the level of changes done to the data in order to reduce the updating. This in particular would be required for a FileChooser because as the file list is read in at every clock cycle and appended to the end of the list of processed files, we don't want to have to recompute everything. By knowing that data was only added at the end, we can just update and compute the stuff for the new files only.

My goals after this is to try to add a gridded/stack view, try to convert filechooser to use this, and add selection if possible (probably with CompoundSelectionBehavior or something based on it).

Some further optim that we could allow; currently, if the user changes a single data element, they have to do on_data_changed() because we have to assume everything changed. Instead, we could allow the user to specify the indices of the items that changed so we don't have to repopulate everything, only the changed items. But we'd still need to recompute the sizes. But we would save a ton of setattr(...).
Similarly, in addition to the saving the last op in ListProperty we can save the indices of the last items changed as well so we can do a similar optim. However, I'm not sure this part is really needed yet, but it may be nice.

This should take care of all the issues.
@tito, I did not change viewport to layout because after thinking about this, layout implies that the layout itself changed (i.e. sizing), but it's only the viewport that changed. So I think viewport is more representative.

Use of fbind() should be a conditionnal too, as it doesn't exists on 1.9

Fixed. In the last commits I also added the following features:

a observable_dict class (as a property) in recycleview, which if you use it as the dict class instances you store in data, any change of the dict, i.e. recycleview.data[0]['text'] = '4', will automatically trigger a data update.
I added a global cache for invalidated classes. They get cleaned periodically when the cache count exceeds a certain value.

With the last commit I implemented appending for linear view without having to recalc everything. For example:
view = RecycleView(viewclass='Label')
view.data = [{'text': str(i)} for i in range(2000)]
Clock.tick()
view.data.extend([{'text': str(i)} for i in range(2000, 4000)])
ts = clock()
view.layout_manager.compute_positions_and_sizes(append=True)
print clock() - ts
ts = clock()
view.layout_manager.compute_positions_and_sizes(append=False)
print clock() - ts

prints
0.00106185489543
0.00174471053778


Remove yarnPath

What are the relevant tickets?

N/A
Description (What does it do?)

Removes yarnPath from .yarnrc.yml so that we can run yarn commands again.
The flake.* file changes are for local nix based dev environments. It works for me and I don't expect anyone to test this.

How do I test?

Ensure you have a modern npm installed w/ corepack enabled
cd src/typescript/mit-open-api-axios
yarn --version should give you `4.1.01
yarn install --immutable should work and not change anything

It seems @ChristopherChudzicki didn't have any issues. I ran through these steps and saw this:
gumaerc@gumaerc-work:~/Code/open-api-clients/src/typescript/mit-open-api-axios$ yarn --version
4.1.0
gumaerc@gumaerc-work:~/Code/open-api-clients/src/typescript/mit-open-api-axios$ yarn install --immutable
➤ YN0000: · Yarn 4.1.0
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed
➤ YN0000: ┌ Post-resolution validation
➤ YN0002: │ @mitodl/open-api-axios@workspace:. doesn't provide @types/node (pb4072), requested by ts-node.
➤ YN0086: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0013: │ 23 packages were added to the project (+ 3.51 MiB).
➤ YN0000: └ Completed in 0s 534ms
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed
➤ YN0000: · Done with warnings in 0s 738ms

Note that I'm seeing Yarn 4.1.0, but after running through this process I don't see a changed lockfile.


Clear tempTrans Position After Updating oldTrans Coords

Make sure that we clear our tempTrans coordinates after updating the
oldTrans cached coordinates so that simple clicks on the ngDraggable
element do not compound the previous translation on the next drag
(causing the element to jump on screen).

This is a fix for issue #11.
Thanks for all your work on this project - very helpful!


Fix the performance regression with ragged attention on for llama2 7b.

We split the attention calculation in the generate step into 2 parts, the self attention of the existing KV cache and the newly calculated cache. For the 2nd part, since the cache length is 1, we should not use ragged attention because of performance. That accounts for ~15% of the attention calculation time.

Can you add a short description about this PR? Did this PR fix the performance issue of ragged attention? I also saw some repeat kv change in this PR.

That's because it's based on the another PR. After that one is pushed, I'll rebase and it'll be more clear.

Can you add a short description about this PR? Did this PR fix the performance issue of ragged attention? I also saw some repeat kv change in this PR.

Rebased.


Interop with MTL classes

@adamConnerSax on #34 wrote:
A question, slightly off-topic maybe.
I feel like there is something similar about this hoist function and the MonadRandom thing we have been talking about over in polysemy-zoo.
All of them are ways of trying to accommodate a different version of an effect that polysemy supports.
So, two questions:

Maybe these should be in a separate library, polysemy-mtl or polysemy-interop? That would get rid of the dependencies for users who don't care about mtl.
What is the ideal form for such a thing? I can imagine three versions, though maybe not all would work equally well for all effects.

Something like hoist: hoistX:: Sem (X ': r) a -> XT (Sem r) a
Some kind of orphan instance: instance (Member X r) => MonadX (Sem r) where ...
A function--like liftIO---which discharges the constraint within Sem : liftX :: (MonadX m, Member X r) => m a -> Sem r a.
I'm not quite sure how that third version would work, but it seems like it keeps most of the convenience of instances without the issue of actually having them.

I'm going to think about how to do that for MonadRandom in RandomFu.

Some points:

mtl is a tiny dependency, that people are guaranteed already going to pull in transitively from somewhere. I'm not concerned about this.

Furthermore, State is a pretty fundamental concept, and I'm not sure that having special cases for it should imply we must also have special cases for other effects. I can imagine maybe also providing hoistErrorIntoExceptT :: Sem (Error e ': r) a -> ExceptT e (Sem r) a, but would be hard-pressed to go further than that.
Orphan instances really really really shouldn't exist in library code. They're maybe OK in application code, but in library code it's just asking for your program to explode in mysterious ways in a few years' time. You can get around this by packaging the orphan instance in the same place as you define the effect, but it still strikes me as a bad idea.
That function like liftIO is just sendM :)

Point 3 seems like the best to me, especially because you can implement it separately from the effect, and it has no relation on the effect's algebra. For example, you could write:
liftRandomIO :: (Member RandomFu r, Member (Lift IO) r) => (forall m. MonadRandom m => m a) -> Sem r a

by just instantiating your forall'd MonadRandom'd m as IO and then sendMing that.

However, working backwards like this I think is the wrong strategy. If you have in mind "I want to use RandomFu" from the get go, you are going to just use RandomFu, and a huge chunk of the abstraction capabilities of polysemy will immediately be lost to you.
We learned this lesson the hard way at Takt, where we wanted a Redis effect. And so we wrote a Redis effect, but then it turns out, you can never mock that thing short of /just writing a working Redis implementation/ which is not really a mock at all! Instead what we found was to delegate Redis to be an interpretation layer only, meaning it wasn't allowed to appear in application code. Instead you'd write against higher abstractions, like having a KVStore k v you could read and write from, and then interpreting that thing  (and others) into Redis.
MonadRandom is clearly an "abstraction" for writing application code. If you simply only have access to the effect algebras that you need rather than having access to all that are possible, you're suddenly afforded a great deal of liberty.

TL;DR: yes.

mtl dependency is no big deal. I agree.  Others on these threads and you had expressed varying levels of grumpiness with mtl dependency/style and so I was thinking of that.  But your response to 3 clarifies and make sense of that.  Enough said.

That makes sense.
That also makes sense! So we'll drop the instance.  I don't think I can get around it as you say because it's an instance on Sem not RandomFu but maybe I'm missing something?
Is that function sendM? Doesn't sendM require a Member (Lift m) r constraint?  I wasn't imagining writing this function as a call to something else but instead by "routing" it through the RandomFu effect, which is then interpreted however.  Which, I think, is your point.

I agree about building up effects in this way, one which defers and makes flexible all the decisions about implementation by limiting your power to just what you need.  And that's sort of the idea of the mtl constraints, right?  MonadRandom m just says that I can get pseudo numbers via some function calls but it doesn't require a specific implementation.
So we agree, I think.  We don't want to encourage using specific implementations.
[Sidebar 1: That talk is cool!  Though I'll need to watch the adjunctions part again.  And, maybe I missed it, but when talking about Applicative vs. Monad, I wished he mentioned parallelism.  To me, that's one of the coolest examples and clearest examples of why using more general things gets you more power.  I mean, also lenses, but ouch.]
And thus the question/idea:  Can we write the function I proposed in #3, but without sendM?  Can we discharge the constraint by, at the most extreme, creating a dictionary on the fly which routes the calls through the Random or RandomFu effect?  Then I think we're accomplishing both of our goals:  we encourage and support writing against higher abstractions (either Member Random r or MonadRandom m), we allow the full variety of interpretations, and we make it easy to deal with already written code with an mtl-style constraint.
I was hoping something along the lines of
newtype RandomSem r a = RandomSem { unRandomSem :: P.Sem r a } deriving (Functor, Applicative, Monad)

$(R.monadRandom [d|
        instance P.Member Random r => R.MonadRandom (RandomSem r) where
            getRandomPrim :: R.Prim t -> RandomSem r t
            getRandomPrim = RandomSem . getRandomPrim
    |])

liftMonadRandom
  :: forall r a
   . P.Member Random r
  => (forall m .   I think because knowing that m has a MonadRandom instance is not the same as being able to choose any m with a MonadRandom instance, and that's what my lift function requires.  So I'll keep thinking about it...
[Sidebar 2: Having this conversation around the Random effect(s) is confusing it some, because, as you've already pointed out, there shouldn't be two of them!  Or, more generally, not all effects will have one-interface-to-rule-them-all and that presents a puzzle at the level of the abstraction rather than the interpretation.]

Thanks for writing that all out --- I think I understand your point now!
The point is: if people have already done their due diligence and written their apps in an MTL-esque tagless final style using MonadX typeclasses, then we should do them the favor of acknowledging that work? Yes, I agree!
At the wildest, we could use reflection to spin up that MonadRandom dictionary on the fly. I have some other, weirder experiments in dealing with orphan instances too.
But maybe you're right. Maybe the solution is to just embrace orphans, but possibly with the caveat that they must be in their own package and "buyer beware?" It's not a solution for classes with fundeps, but fundamentally I think there's only so much we can do.

This is fixed by https://github.com/isovector/polysemy-zoo/pull/8, when it lands


Intel display driver crashes when closing application, with depth-testing on

So I ran in to this issue where my intel driver on windows 10 crashes as I close the window to my application (thus shutting it down). This only started happening with the additional drawstate command for depthtesting: .depth(gfx::state::Comparison::LessEqual, true)
I am using a batch::Core for batch and supplement it during the draw call. Soon as I added the depth test to DrawState I started having this issue. Perhaps I am wrong how I am using drawstate. Most interesting is that if I switch to using the nvidia card the problem subsides. I also tested this on an another computer without intel integrated graphics, and it ran without issue. So this issue is directly related to intel graphics, some how. I have an i7-4712HQ mobile processor with intel HD 4600 integrated. What should I do to fix this? Is there a way to properly shut down the graphics driver in this case, as it looks like it hangs while closing (for about 2 seconds) then closes and crashes.

//excerpt from drawing
    pub fn draw<P>(
        &mut self,
        batch : &Batch<P>,
        params: &P,
        )
        where P: gfx::render::shade::ShaderParam<Resources=gl::Resources>,
    {
        self.stream
            .draw(&batch.batch.with(
                &batch.slice,
                params,
                &gfx::DrawState::new().depth(gfx::state::Comparison::LessEqual, true)
                    .blend(gfx::BlendPreset::Alpha),
                ))
            .unwrap_or_else(|e| panic!("Error drawing graphics: {:?}", e));
    }

My shader programs are as such:

// vert
        #version 120

        attribute vec3 pos;
        attribute vec3 norm;

        uniform mat4  model;
        uniform mat4  view;
        uniform mat4  proj;

        uniform float size;
        uniform vec3  color;

        varying vec3 v_color;
        varying vec3 v_position;
        varying vec3 v_normal;

        void main() {
             v_position = pos;
             v_normal = norm;
             gl_Position = proj * view * model * vec4(v_position, 1.0);
             v_color = color;
        }

// frag

       #version 120
       varying vec3 v_normal;
       varying vec3 v_color;

       const vec3 LIGHT = vec3(-0.2, 0.8, 0.1);
       void main() {
            float lum = max(dot(normalize(v_normal), normalize(LIGHT)), 0.0);
            vec3 color = (0.3 + 0.7 * lum) * v_color;
            gl_FragColor = vec4(color, 1.0);
       }

Could you try testing this with any of the gl-rs examples? Also, what OS/driver are you on?

I'm on Windows 10 64-bit, I realized as I wrote this that I should update my drivers. I'll look through the examples to see if any run depth tests with alpha blending. I'll let you know what I find out

So upgrading my intel driver did not fix this. The program is fine on Radeon and nVidia, but intel 4600 driver itself crashes when closing the program-- the program does not crash but does take a while to close and hangs after closing (for about 2 seconds). This only started when I added depth+blend in batch parameters, it was fine before this. Is there an example which uses both depth and alpha blending like the code above? If so I can test against it.

Out deferred rendering example uses it, please try it.

I guess I need cmake setup in order to build and run. Unfortunately I'll have to dock this for later, as such we can close this issue for now-- as this is likely an issue with my intel driver/method of using gfx-rs
$ cargo run --example deferred
...
Build failed, waiting for other jobs to finish...
failed to run custom build command for `glfw-sys v3.1.3`
Process didn't exit successfully: `C:\Users\Chris\gfx\target\debug\build\glfw-sys-a256251833e28409\build-script-build` (exit code: 101)
--- stderr
thread '<main>' panicked at 'Failed to execute cmake: The system cannot find the file specified.
 (os error 2)', C:\Users\Chris\.cargo\registry\src\github.com-121aea75f9ef2ce2\glfw-sys-3.1.3\build.rs:15

Actually, you can remove glfw dependency from Cargo.toml and try again. The deferred example doesn't need it, IIRC.

I can confirm that the example did run, @kvark  and looks fantastic btw :+1:  I'll have to rummage through my code some more when I have a moment, thanks again!

Yay! This makes me wonder if we should re-consider stripping the examples out of glfw completely. It doesn't bring much to the table, so I'd be fine with it for as long as Glutin works on all platforms.

I am personally using glutin these days, as glfw is a pain to get up and running on windows compared to glutin. I would not be opposed to migrating the examples away from glfw. But we should probably keep a basic one alive and kicking if we plan to keep supporting gfx_window_glfw. Maybe we can hide it behind a feature flag to make sure it compiles, but wont get in the way of new developers.

:+1:


rezeored turret

I think DutyCycleEncoder has a setAbsoluteOffset method in WPILib 2022.4.1, would be worth using it instead. Should be able to get the offset from the DutyCycle object on LiveWindow.


add multiple owners to project?

perhaps add myself and @sndrsmnk as project owners so we can help setup travis, github pages, pypi, etc
i registered ypconfig.net to serve up gh-pages from this repo

No longer needed because of #5


Can I download from this kind of website?

The URL of the target TS chunks look like this:
https://dash.example.club/videos/66434f13ddcad3715b59cf24/index1.ts
https://dash.example.club/videos/66434f13ddcad3715b59cf24/index2.ts
https://dash.example.club/videos/66434f13ddcad3715b59cf24/index3.ts
https://dash.example.club/videos/66434f13ddcad3715b59cf24/index4.ts

I tried the following command using Pycharm and none of them worked.
 .\download.py -o example.mp4 https://dash.example.club/videos/66434f13ddcad3715b59cf24/index{counter}.ts
 .\download.py -o example.mp4 https://dash.example.club/videos/66434f13ddcad3715b59cf24/index({counter}).ts
 .\download.py -o example.mp4 https://dash.example.club/videos/66434f13ddcad3715b59cf24/{counter}.ts
 .\download.py -o example.mp4 https://dash.example.club/videos/66434f13ddcad3715b59cf24/({counter}).ts

Is it possible to download from this kind of websites using your script? Thanks and have a good day :)

Did you manage to make it work?