Iss 262 workspaces

related to #262

Workspaces concept page + how to switch between WS, how to create a new WS, how to delete a WS
Working with Organisations marked as deprecated. This page could be hidden from the sidebar (to keep the link and content if it's referenced elsewhere).
Permissions updated to include members/guests
How to share, transfer, delete projects - updated

A warning added to pages that are not yet updated (that require screenshot from MM Input and QGIS plugin).
Updated:

tutorial - Working Collaboratively updated
sign up from web
subscriptions
home page and dashboard
project history and versions

@alex-cit https://merginmaps.com/blog/introducing-workspaces-simplified-collaboration

Thanks for addressing the comments @alex-cit !


Use Ppx_deriving_show directly

I would like to use the Ppx_deriving_show module directly, for the str_of_type and sig_of_type functions. I don't see any documentation on how to link it properly. What is the best way to do that?

You can't, the side effect of using this module is registration of a deriver. What's the use case?

I am building a programming language that essentially has ppx_deriving.show built-in. It compiles to OCaml. In the parsing stage it's just another one of several AST transforms. It would be nice to get access to those two functions.

Right now we vendor ppx_deriving_show.ml directly, which is an ugly hack.

It seems like vendoring is a better option here. Consider: say I add a new option to ppx_deriving_show.  Is this good?

Currently we pin version 4.1, so as far as I understand, the interface of the language would not change.

So does that mean using the reason package and any other version of ppx_deriving together is impossible? That seems annoying, except if Reason always lives in its own opam switch.

I don't think so, but I very well could be wrong. I am not super familiar with how the OCaml ecosystem works just yet. But here is why I think that could be OK. The use for Reason is at the moment something like:

Write Reason code
Use the provided refmt (which bundles in ppx_deriving.show) to transform the code into OCaml code (or JS, I suppose), optionally with generated printer functions

Since it's just refmt that uses the transform and not any other part of the toolchain, it seems to me as though other versions of ppx_deriving could be used at other points in time. Please correct me if I am wrong.
If we would rather not vendor, what would you say is the best way to do an AST transform manually? Or is the only option to vendor?

There can only be one version of ppx_deriving (or any other package) installed in opam at any one time. So if you choose to depend on ppx_deriving, there are two options:

Either the user is forced to remain on the version of ppx_deriving that Reason uses (and I'm quite uncomfortable with that, because it effectively means ppx_deriving is now frozen);
Or whichever version of ppx_deriving is used in Reason implicitly becomes a part of its public interface.

Which part of the Reason toolchain performs the conversion is immaterial.

If we would rather not vendor, what would you say is the best way to do an AST transform manually?

You could be a "ppx driver" and add the [@@deriving show] annotation before running ppx_deriving.

@whitequark We've vendored ppx_deriving and ppx_deriving_show. Cheers!


POLYFILLS: find alternatives

The Array.find polyfill is included at the top of a few elements, so it gets re-run for each of those elements that gets imported.  I also am uncomfortable with having a polyfill installed invisibly.  If it's included into a project that already has a polyfill for Array.find, it could prevent that project's polyfill from being installed, potentially leading to a very difficult to isolate bug.
A partial import of lodash's find function would be a great solution, ex: import { find } from "lodash".  It would solve the problem completely.  But, we can't, because we can only import third-party dependencies that have global references.  Maybe there is some way to make it work.

I made this subject line a little more general because I think polyfills are an issue we need to solve globally

Closing in favor of this approach: https://github.com/patternfly/patternfly-elements/issues/1363


Line mismatch error possibly associated with memory error

The attachment was too big, so it's at pds-gamma:~rchen/a16.zip
If I validate the whole bundle, validate gives some strange warning for the file a16_psr_ch11_lsm.xml, but if I validate that file directly, validate passes:
% validate -f -t a16
PDS Validate Tool Report
Configuration:
Version 1.15.0
Date 2019-06-23T22:59:00Z
Parameters:
Targets file:/Users/rchen/Desktop/a16/
Severity Level WARNING
Recurse Directories true
File Filters Used [*.xml, *.XML]
Force Mode on
Data Content Validation on
Max Errors 100000
Registered Contexts File /PDS4tools/validate/resources/registered_context_products.json
Product Level Validation Results
PASS: file:/Users/rchen/Desktop/a16/bundle.xml
PASS: file:/Users/rchen/Desktop/a16/document/l1b2l1alsmpds.xml
PASS: file:/Users/rchen/Desktop/a16/document/getlsmcvs.xml
PASS: file:/Users/rchen/Desktop/a16/document/getclockrate.xml
PASS: file:/Users/rchen/Desktop/a16/document/a16_lsm_raw_arcsav_descr.xml
PASS: file:/Users/rchen/Desktop/a16/document/a16_psr_ch11_lsm.xml
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.sun.xml.bind.v2.runtime.reflect.opt.Injector$1 (file:/PDS4.9b.tools/validate-1.15.0/lib/jaxb-impl-2.2.4.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
WARNING: Please consider reporting this to the maintainers of com.sun.xml.bind.v2.runtime.reflect.opt.Injector$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
FAIL: file:/Users/rchen/Desktop/a16/document/collection.xml
Begin Content Validation: file:/Users/rchen/Desktop/a16/document/collection_inventory.csv
ERROR [error.table.records_mismatch] table 1: Number of records read is not equal to the defined number of records in the label (expected 91, got 5).
End Content Validation: file:/Users/rchen/Desktop/a16/document/collection_inventory.csv
Summary:
1 error(s)
0 warning(s)
Message Types:
1 error.table.records_mismatch
End of Report
% validate -f -t a16/document/a16_psr_ch11_lsm.xml
PDS Validate Tool Report
Configuration:
Version 1.15.0
Date 2019-06-23T23:00:13Z
Parameters:
Targets file:/Users/rchen/Desktop/a16/document/a16_psr_ch11_lsm.xml
Severity Level WARNING
Recurse Directories true
File Filters Used [*.xml, *.XML]
Force Mode on
Data Content Validation on
Max Errors 100000
Registered Contexts File /PDS4tools/validate/resources/registered_context_products.json
Product Level Validation Results
PASS: file:/Users/rchen/Desktop/a16/document/a16_psr_ch11_lsm.xml
Summary:
0 error(s)
0 warning(s)
End of Report

@richardchenca I can't seem to find this data? can you make sure this is on pds-gamma?

a16.zip
Sorry, I saw that file in my directory, didn't remember what it was for, and deleted it. Attached here is a reduced directory that still gives the weird warnings. I've encountered it many times since.
Last login: Wed Aug 21 13:21:53 on ttys000
/Users/rchen> cd Desktop/
/Users/rchen/Desktop> validate -f -t a16
PDS Validate Tool Report
Configuration:
Version                       1.15.0
Date                          2019-08-21T20:28:51Z
Parameters:
Targets                       [file:/Users/rchen/Desktop/a16/]
Severity Level                WARNING
Recurse Directories           true
File Filters Used             [*.xml, *.XML]
Force Mode                    on
Data Content Validation       on
Max Errors                    100000
Registered Contexts File      /PDS4tools/validate/resources/registered_context_products.json
Product Level Validation Results
PASS: file:/Users/rchen/Desktop/a16/a16_psr_ch11_lsm.xml
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.sun.xml.bind.v2.runtime.reflect.opt.Injector$1 (file:/PDS4.9b.tools/validate-1.15.0/lib/jaxb-impl-2.2.4.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
WARNING: Please consider reporting this to the maintainers of com.sun.xml.bind.v2.runtime.reflect.opt.Injector$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
PASS: file:/Users/rchen/Desktop/a16/collection.xml
Summary:
0 error(s)
0 warning(s)
End of Report
/Users/rchen/Desktop>
/Users/rchen/Desktop>
/Users/rchen/Desktop>
/Users/rchen/Desktop>
/Users/rchen/Desktop>
/Users/rchen/Desktop> validate -f -t a16/a1
a16_psr_ch11_lsm.pdf  a16_psr_ch11_lsm.xml
/Users/rchen/Desktop> validate -f -t a16/a16_psr_ch11_lsm.xml
PDS Validate Tool Report
Configuration:
Version                       1.15.0
Date                          2019-08-21T20:29:06Z
Parameters:
Targets                       [file:/Users/rchen/Desktop/a16/a16_psr_ch11_lsm.xml]
Severity Level                WARNING
Recurse Directories           true
File Filters Used             [*.xml, *.XML]
Force Mode                    on
Data Content Validation       on
Max Errors                    100000
Registered Contexts File      /PDS4tools/validate/resources/registered_context_products.json
Product Level Validation Results
PASS: file:/Users/rchen/Desktop/a16/a16_psr_ch11_lsm.xml
Summary:
0 error(s)
0 warning(s)
End of Report
/Users/rchen/Desktop>
/Users/rchen/Desktop>
/Users/rchen/Desktop>
/Users/rchen/Desktop>
/Users/rchen/Desktop>
/Users/rchen/Desktop>
/Users/rchen/Desktop> validate --version
Validate Tool
Version 1.15.0
Release Date: 2019-04-01 07:56:51
Core Schema: PDS4_PDS_1C00.xsd
Core Schematron: PDS4_PDS_1C00.sch
Copyright 2010-2018, by the California Institute of Technology.
ALL RIGHTS RESERVED. United States Government Sponsorship acknowledged.
Any commercial use must be negotiated with the Office of Technology Transfer
at the California Institute of Technology.
This software is subject to U. S. export control laws and regulations
(22 C.F.R. 120-130 and 15 C.F.R. 730-774). To the extent that the software
is subject to U.S. export control laws and regulations, the recipient has
the responsibility to obtain export licenses or other export authority as
may be required before exporting such information to foreign countries or
providing access to foreign nationals.
/Users/rchen/Desktop>

We have noticed similar errors on our side and I believe @fran-vallejo suspected the jaxb library. @richardchenca are you using java >8?

Hi, Mark,
% java --version
java 12.0.1 2019-04-16
Java(TM) SE Runtime Environment (build 12.0.1+12)
Java HotSpot(TM) 64-Bit Server VM (build 12.0.1+12, mixed mode, sharing)
Did another ticket clean this up? I don't see one linked, but here's a current validate on my machine on the .zip attached earlier. It'd be nice not to have that extraneous message, but it's not so disconcerting.
% validate -t Desktop/a16
PDS Validate Tool Report
Configuration:
Version                       1.17.4
Date                          2019-10-25T14:51:49Z
Parameters:
Targets                       [file:/Users/rchen/Desktop/a16/]
Severity Level                WARNING
Recurse Directories           true
File Filters Used             [*.xml, *.XML]
Data Content Validation       on
Product Level Validation      on
Max Errors                    100000
Registered Contexts File      /PDS4tools/validate/resources/registered_context_products.json
Product Level Validation Results
PASS: file:/Users/rchen/Desktop/a16/a16_psr_ch11_lsm.xml
Oct 25, 2019 7:51:53 AM com.sun.xml.bind.v2.runtime.reflect.opt.AccessorInjector
INFO: The optimized code generation is disabled
PASS: file:/Users/rchen/Desktop/a16/collection.xml
Validation complete.
Summary:
0 error(s)
0 warning(s)
End of Report

@rchenatjpl I think there was a ticket out there that fixed this regarding "JAXB error". Unfortunately, this is the best I've got at the moment. I can't figure out how to ignore the third party library messages but I will see what I can do.

@msbentley, those warnings were an issue with the jaxb fixed in version 2.3.1 as described at https://github.com/eclipse-ee4j/jaxb-ri/issues/1197
I have tried to build a pds4-jparser with an updated jaxb-impl dependency in its pom (from 2.2.4 to 2.3.1) to check if that fixed the problem, but it caused a couple follow-up problems:

It raises a ClassNotFoundError when building pds4-jparser.
Adding the jaxb-core as dependency to pds4-jparser fixes the ClassNotFoundError but causes more errors and tests failures.

@fran-vallejo thanks for the shot. that was the concern i had with trying to upgrade right at the build boundary. we will look into this more deeply next build.

@msbentley @fran-vallejo @rchenatjpl I just merged a temporary fix for this to suppress the INFO messages in Validate and a point build is being deployed as we speak. there is probably a better way to do this programmatically in PDS4 JParser, but I'm already spent a ton of time on this :-)


Viewer: scrubber component

Who it's for
Viewer users - for navigating through a work
Problems to be solved

Give sense of length of work and positioning within it.
Allow quick movement through a work, rather than hunting and pecking.

Scrubber metaphor (used in audio and video) useful as a starting point. May want to implement thumbnails within scrubber at later date.
TODO

[ ] Visual design
[ ] Build component

Acceptance criteria
Success
TBD

#4325


Fix event emissions

Fixes/Closes

Closes #
Description
Fixes issue noticed by @dragaDoncilaPop wherein adding and deleting nodes on a graph layer does not emit events.
This is a bug fix that addresses that issue by emitting an event when adding and removing nodes.
How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change
[ ] example: I check if my changes works with both PySide and PyQt backends
as there are small differences between the two Qt bindings.

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

Hi @jamesyan-git,
Some tests would benefit this PR.
It's unclear to me that selected_data will always be set. For example, Graph.remove without setting selected_data.
And, in my opinion, it should emit the indices in world (not buffer) space.

@jni @JoOkuma this is ready for review now, have added some tests as well!

@JoOkuma Thanks! I think I have addressed everything

LGTM!


feat(tools): add function to convert beam index

A convenience function to convert from beam indices going from 0 through 1023 to the ones used in the CHIME/FRB beam_model package (and other places?) that are of the form 0-255, 1000-1255, etc.

The function looks fine. I would question if this is the right repo for this one. Do we have much other HFB code in ch_util? The beam indices aren't used anywhere in the cosmology pipeline. If there isn't anything else, I would just put this into ch_pipeline

It looks fine. Please just add a description for the parameter beam_index.


hotReloadCapable recognized on podman

What type of PR is this:
/kind bug
What does this PR do / why we need it:
Which issue(s) this PR fixes:
Fixes #6425
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

How to test changes / Special notes to the reviewer:

/override windows-integration-test/Windows-test
Flaky e2e test


feat: Make default depth configurable for table lineage graph view

Summary of Changes
For certain deployments the graph view can get unreadable when it displays nodes at too great a depth. The app hardcodes the table lineage graph depth to 5 currently. This PR makes that value configurable using the config-types pattern that the rest of the front end uses.
There is some discussion about the feature in a previous PR that I botched:
https://github.com/amundsen-io/amundsen/pull/2069
Tests
Added a unit test for the function that gets the default graph depth
Documentation

CheckList
Make sure you have checked all steps below to ensure a timely review.

[x] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[x] PR includes a summary of changes.
[x] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

@Golodhros - I think I got this sorted out. I didn't see the instructions for signing/rebasing the commits until after I made the new PR. Going to close the old PR. Sorry about the thrash on that.

No prob!

Fixes https://github.com/amundsen-io/amundsen/issues/2068

@jsnb-devoted could you remove my commit and fix it. yourself?

@jsnb-devoted could you remove my commit and fix it. yourself?

fixed and did a force push -- that should do it ya? @Golodhros

@jsnb-devoted could you remove my commit and fix it. yourself?

fixed and did a force push -- that should do it ya? @Golodhros

Yay, thanks!

@all-contributors please add @jsnb-devoted for code, ideas, question

I'll fix these tests -- I need to update the function arguments in a few places

hey @Golodhros -- I would love to actually get this fixed. I tried to sneak it in there by fixing the build errors I was seeing in CI but that isn't working. I'm trying to get the local dev environment figured out but npm is giving me all kinds of grief. I'll try to get it sorted out this week. The npm install keeps saying I'm not authenticated. I created an npm account and logged in and it still gives me this:
npm ERR! code E401
npm ERR! Incorrect or missing password.
npm ERR! If you were trying to login, change your password, create an
npm ERR! authentication token or enable two-factor authentication then
npm ERR! that means you likely typed your password in incorrectly.
npm ERR! Please try again, or recover your password at:
npm ERR!     https://www.npmjs.com/forgot
npm ERR!
npm ERR! If you were doing some other operation then your saved credentials are
npm ERR! probably out of date. To correct this please try logging in again with:
npm ERR!     npm login

hey @Golodhros -- I would love to actually get this fixed. I tried to sneak it in there by fixing the build errors I was seeing in CI but that isn't working. I'm trying to get the local dev environment figured out but npm is giving me all kinds of grief. I'll try to get it sorted out this week. The npm install keeps saying I'm not authenticated. I created an npm account and logged in and it still gives me this:
npm ERR! code E401
npm ERR! Incorrect or missing password.
npm ERR! If you were trying to login, change your password, create an
npm ERR! authentication token or enable two-factor authentication then
npm ERR! that means you likely typed your password in incorrectly.
npm ERR! Please try again, or recover your password at:
npm ERR!     https://www.npmjs.com/forgot
npm ERR!
npm ERR! If you were doing some other operation then your saved credentials are
npm ERR! probably out of date. To correct this please try logging in again with:
npm ERR!     npm login

Oh, I see. I have seen somebody else reporting something similar, but it doesn't make a lot of sense (you shouldn't need an npm account to install dependencies).
I will try to check this out today and get back to you!


Use includeDates to derive implied minDate or maxDate for getDateInVi…

Use case: I had a list of dates starting in April, but my calendar still defaulted to a March display. I could fix this by explicitly setting minDate. But this seemed redundant, since the minimum date can be derived from the includeDates.
Solution: I've rewritten getDateInView() to derive an implied minimum date from includeDates. That is, the earliest current or future date. For symmetry, I've also derived an implied maximum date where no implied minimum exists.

Crap! My own unit test broke. It worked fine for me locally.
I'll take a look at this later and resubmit.

Current coverage is 94.44%

Merging #431 into master will decrease coverage by -0.70% as of 4d9a861

@@            master    #431   diff @@
======================================
  Files            9       9
  Stmts          206     216    +10
  Branches        44      50     +6
  Methods         90      92     +2
======================================
+ Hit            196     204     +8
- Partial          2       4     +2
  Missed           8       8

Review entire Coverage Diff as of 4d9a861

Powered by Codecov. Updated on successful CI builds.


#140 Ability to register Parameter parsers from User code

This pullrequest is for https://github.com/getgauge/gauge-java/issues/140
I needed to change quite heavily, how the parsers are stored in gauge-java and how they are chained, as the previous solution was fine for parsers, that were known at compile time, but not at runtime.
To identify all custom parsers provided by the user I introduced a new library dependency, to easily retrieve all implementations of the parser hook.
As an alternative, gauge-java could offer a registration entity, where the custom parser implementations could register themselves.
BasicParameterParser was retired and the ParameterParser interface took over responsibilty over
FailBackParameterParser is deleted, as the ParameterParserChain now the responsibility holds to ensure that a conversion happens.
Finally, I could not add unit tests for this feature, as I was not able to integrade a custom parser, when it resides in the test folder. It simply was not loaded. It was tested with a separate gauge project.
Comments are welcome

@jackperalta Thanks for the contribution. Really appreciate your efforts and look forward to many more!!


Fix checkpoint test to not fail at etcd rolling out

Issue #, if available:
Description of changes:
Test fails at waiting for external etcd to be ready because of the 2X replicas hard limit on etcd. This changes the checkpoint test to not fail at etcd rolling out but at cp rolling out to avoid the test timing out waiting for external etcd to be ready when more etcd nodes cannot be rolled out.
Testing (if applicable):
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/cherry-pick release-0.17


The Database Factory namespace does not behave as expected when "App\" is included in the Model namespace

Laravel Version
11.29.0
PHP Version
8.3.11
Database Driver & Version
No response
Description
My Laravel project has the following directory structure:
├── app
│     ├── ...
├── database
│     └── factories
│           └── Feature
│                 └── FooApp
│                       └── Models
│                             └── UserFactory.php
├── feature
│     └── FooApp
│           └── Models
│                 └── User.php

PSR-4 configuration in composer.json:
{
    "psr-4": {
        "App\\": "app/",
        "Feature\\": "feature/",
        "Database\\Factories\\": "database/factories/",
        "Database\\Seeders\\": "database/seeders/"
    }
}

In this setup, I expect the Factory class for Feature\FooApp\Models\User to resolve to Database\Factories\Feature\FooApp\Models\UserFactory.
However, it resolves to Database\Factories\Models\UserFactory instead.
If you call Feature\FooApp\Models\User::factory() ,
you will get the error Class "Database\Factories\Models\UserFactory" not found.
This causes issues when there are models with the same name in different namespaces (e.g., Feature\FooApp\Models\User and Feature\BarApp\Models\User), as it results in duplicate Factory namespaces.
As a workaround, since my project doesn't have any models in 'App', I've written the following code in the boot method of AppServiceProvider:
Factory::guessFactoryNamesUsing(static function (string $modelName) {
    return Factory::$namespace . $modelName . 'Factory';
});

I apologize if my English sounds unnatural. Thank you.
Steps To Reproduce

Set up a Laravel project with the above structure
The content of User.php is as follows:<?php

namespace Feature\FooApp\Models;

use Illuminate\Database\Eloquent\Factories\HasFactory;
use Illuminate\Database\Eloquent\Model;

class User extends Model
{
    use HasFactory;
}

The content of UserFactory.php is as follows:<?php

namespace Database\Factories\Feature\FooApp\Models;

use Feature\FooApp\Models\User;
use Illuminate\Database\Eloquent\Factories\Factory;

class UserFactory extends Factory
{
    protected $model = User::class;

    public function definition(): array
    {
        return [];
    }
}

Call Feature\FooApp\Models\User::factory()
Get error: Class "Database\Factories\Models\UserFactory" not found.

hi @darmats ,
I got the same error when removing appServiceProvider code

But after adding the service provider code it works

Hey there,
While this may be a legitimate issue, can you first try posting your problem or question on one of the support channels below? If this issue can be definitively identified as a bug, feel free to open up a new issue with a link to the original one and we'll gladly help you out.

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

Thanks!

Thanks!
I will try posting on one of the support channels.


grub2: workaround parallel build failure by building .po files sequen…

…tially
Without the change grub2 build occasionally fails as:
https://hydra.nixos.org/log/h04imslmgy9l33z6xxsaf9v4svqsc3n2-grub-2.12-rc1.drv

$ msgmerge --update  --lang=de de.po grub.pot
$ msgmerge --update  --lang=de de.po grub.pot
...
de.po:745: end-of-file within string
de.po:745: missing 'msgstr' section

Here msgmerge --update attempts to update de.po from two parallel make calls when translation updates are happening.
The change works around de.po stomping bu regenerating translations sequentially.
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 248886 run on x86_64-linux 1

11 packages built:

grub2 (grub2_light)
grub2.debug (grub2_light.debug)
grub2_efi
grub2_efi.debug
grub2_pvgrub_image
grub2_xen
os-prober
timeshift
woeusb
woeusb-ng
woeusb-ng.dist

I was able to get six consecutive builds to work without failing. Seems that this solves the issue.
Thanks very much for quick response and a proper fix!
I wonder if the comment should be changed to link to this PR instead of mine?

I was able to get six consecutive builds to work without failing. Seems that this solves the issue.

Aha, nice! Apparently I forgot my loop-test in the background and it survived 120 grub2 rebuilds. Previously it used to fail on about every ~10th run.

I wonder if the comment should be changed to link to this PR instead of mine?

I linked the PR as a source of a bit of debugging (it's not too much details here). I linked specific comment instead to make it a bit clearer and re-pushed:
--- a/pkgs/tools/misc/grub/default.nix
+++ b/pkgs/tools/misc/grub/default.nix
@@ -151,7 +151,7 @@ stdenv.mkDerivation rec {
   postConfigure = ''
     # make sure .po files are up to date to workaround
     # parallel `msgmerge --update` on autogenerated .po files:
-    #   https://github.com/NixOS/nixpkgs/pull/248747
+    #   https://github.com/NixOS/nixpkgs/pull/248747#issuecomment-1676301670
     make dist
   '';

Ah right the original thread did have more debugging. And for whatever reason on my system it fails maybe 70% of the time. Way more frequently than 10%. As a result I'd like to see this merged ASAP.

I haven't tested, but it smells right from reading it. So assuming it works, it's approved for all but the trivial nit.

Squashed/rebased with a newline added after postConfigure.


Fixed example for Table.upsert()

Fixes #<issue_number_goes_here> (it's a good idea to open an issue first for discussion)

[x] Tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

Thanks for the fix @sulaysumaria!


[V3 AntiMentionSpam] write to modlog

Currently, AntiMentionSpam does not writes case in modlog when mutes/bans for mention spam

Currently it relies on Red's builtin unclaimed case detection. There's an open issue which will allow more flexibility with this in a way I'm willing to do.

As of Cog-Creators/Red-DiscordBot#2901 this can feasibly be added.
However, as it's a large breaking change, this won't be added until the 3.2 release of Red. I'll package together the required changes for this and other planned breakage later.


Add 'Evo' engine API evolution experiment

Evo is an exploration of a new engine <-> task/rule API. It actually
predates and informed some of the new TaskInterface APIs. The current
implementation doesn't scale particularly well, as it burns
a thread per executing rule. However, it is worthwhile having in the
codebase for a bit as we consider future directions.

@swift-ci please smoke test

@swift-ci please smoke test linux


build and objects download

in my case I'm building the whole  project (which also contains dll files), my question is,
does  the blobs objects(that I understand that are the ones increasing the size on disk) will be downloaded
once they are fetch in the build?
will the move from TFVC to GVFS will still be useful?   or the repository will  grow to a point where working with git will be impossible?

We have discussed this outside of GitHub, but for completeness here, yes if your build consumes every file, then GVFS will have to download every file. In general, GVFS is best for repos that have many files, but a typical developer only needs to consume a small percentage of them.


No ES6 support: Unexpected token name «of», expected punc «;»

The following code snippet doesn't compress using jscompress.com:
function copyAttributes(src, dest, attrList)
{
	for(attrName of attrList)
	{
		dest.setAttribute(attrName, src.getAttribute(attrName));
	}
}

This make me think that jscompress.com doesn't support the for..of loop.

JSCompress uses Uglify.js 2 for minification. I just checked over there, and it looks like ES6 support is being worked on in this issue: https://github.com/mishoo/UglifyJS2/issues/448

Thanks for the link! I will follow that issue.
On 30/06/2015 03:30pm, Vance Lucas wrote:

JSCompress uses Uglify.js 2 for minification. I just checked over
there, and it looks like ES6 support is being worked on in this issue:
mishoo/UglifyJS2#448 https://github.com/mishoo/UglifyJS2/issues/448
—
Reply to this email directly or view it on GitHub
https://github.com/vlucas/jscompress.com/issues/11#issuecomment-117207560.

Latest version of UglifyJS still doesn't support ECMAScript Next but I have added an option to use things from harmony branch.

Cool, thanks!


Make release of tkey-devtools/tkey-runapp

Make an official release of tkey-runapp, to make it easier for users to access it would needing to compile themselves.

Assigning @mchack-work for review

Release done.
homebrew-tap updated.


[WIP] Add implementation for automatically inferring requirements without Banyanfile

Implementation for https://github.com/banyan-team/banyan-julia/issues/20

@cailinw Please ensure before you merge: (1) look at all usage of create_job/with_job and (2) look at all the test-specific dependencies (in [extras] and [targets] in the Project.tomls) and migrate them to the test-specific Project.tomls.


JOIN CONSORTIUM button doesn't work.

Describe the bug
JOIN CONSORTIUM button doesn't work.
To Reproduce
Steps to reproduce the behavior:

Start from a fresh devdata
Go to the Consortia page
Click JOIN CONSORTIUM on Test Consortia 2
See error

Expected behavior
Clicking the JOIN CONSORTIUM button should make the user join the consortium
Screenshots

Thanks @dylanmartin!
This exact bug happened on a call earlier today and your report made it easier for me to reproduce it locally.


caddy+h2+tls "failed to read request header > stream error: stream ID xxx; CANCEL"

提交 Issue 之前请先阅读 Issue 指引，然后回答下面的问题，谢谢。
除非特殊情况，请完整填写所有问题。不按模板发的 issue 将直接被关闭。
如果你遇到的问题不是 V2Ray 的 bug，比如你不清楚要如何配置，请使用Discussion进行讨论。

你正在使用哪个版本的 V2Ray？（如果服务器和客户端使用了不同版本，请注明）
4.21.3
你的使用场景是什么？
网页浏览、观看 YouTube 视频等
你看到的不正常的现象是什么？（请描述具体现象，比如访问超时，TLS 证书错误等）
V2Ray 服务启动一段时间后，客户端出现无法连接的情况，重启 V2Ray 后连接恢复正常
你期待看到的正确表现是怎样的？
V2Ray 启动后能持续正常工作
请附上你的配置（提交 Issue 前请隐藏服务器端IP地址）。

服务器端配置:
    // 在这里附上服务器端配置文件
{
  "log": {
    "loglevel": "info",
    "access": "/var/log/v2ray/access.log",
    "error": "/var/log/v2ray/error.log"
  },
  "inbounds": [{
    "port": 20190,
    "listen": "<IP_ADDRESS>",
    "protocol": "vmess",
    "settings": {
      "clients": [
        {
          "id": "some uuid",
          "level": 1,
          "alterId": 64
        }
      ]
    },
    "streamSettings": {
      "network": "h2",
      "security": "tls",
      "httpSettings": {
        "path": "/bucket",
	"host": ["xxx.yyy.zzz"]
      },
      "tlsSettings": {
	"serverName": "xxx.yyy.zzz",
	"certificates": [
	{
	  "certificateFile": "/etc/v2ray/cert.crt",
	  "keyFile": "/etc/v2ray/cert.key"
	}
	]
      }
    }
  }],
  "outbounds": [{
    "protocol": "freedom",
    "settings": {}
  },{
    "protocol": "blackhole",
    "settings": {},
    "tag": "blocked"
  }],
  "routing": {
    "rules": [
      {
        "type": "field",
        "ip": ["geoip:private"],
        "outboundTag": "blocked"
      }
    ]
  }
}

客户端配置:
{
  "log": {
    "error": "",
    "loglevel": "info",
    "access": ""
  },
  "outbounds": [
    {
      "protocol": "vmess",
      "streamSettings": {
        "tlsSettings": {
          "serverName": "xxx.yyy.zzz",
          "allowInsecure": false
        },
        "security": "tls",
        "httpSettings": {
          "path": "/bucket",
          "host": [
            "xxx.yyy.zzz"
          ]
        },
        "network": "h2"
      },
      "tag": "agentout",
      "settings": {
        "vnext": [
          {
            "address": "xxx.yyy.zzz",
            "users": [
              {
                "id": "some uuid",
                "alterId": 64,
                "level": 1,
                "security": "none"
              }
            ],
            "port": 443
          }
        ]
      }
    },
    {
      "tag": "direct",
      "protocol": "freedom",
      "settings": {
        "domainStrategy": "AsIs",
        "redirect": "",
        "userLevel": 0
      }
    },
    {
      "tag": "blockout",
      "protocol": "blackhole",
      "settings": {
        "response": {
          "type": "none"
        }
      }
    }
  ],
  "dns": {
    "servers": [
      ""
    ]
  },
  "routing": {
    "strategy": "rules",
    "settings": {
      "domainStrategy": "IPIfNonMatch",
      "rules": [
        {
          "outboundTag": "direct",
          "type": "field",
          "ip": [
            "geoip:cn",
            "geoip:private"
          ],
          "domain": [
            "geosite:cn",
            "geosite:speedtest"
          ]
        }
      ]
    }
  },
  "transport": {}
}

请附上出错时软件输出的错误日志。在 Linux 中，日志通常在 /var/log/v2ray/error.log 文件中。

服务器端错误日志:
2019/12/02 08:55:01 [Info] [3838754925] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 389; CANCEL
2019/12/02 08:55:07 [Info] [3912041362] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 391; CANCEL
2019/12/02 08:55:11 [Info] [3770826762] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 393; CANCEL
2019/12/02 08:55:16 [Info] [1308767177] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 399; CANCEL
2019/12/02 08:55:16 [Info] [3995426864] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 397; CANCEL
2019/12/02 08:55:16 [Info] [3991594457] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 395; CANCEL
2019/12/02 08:55:21 [Info] [2455374023] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 369; CANCEL
2019/12/02 08:55:30 [Info] [3612578077] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 401; CANCEL
2019/12/02 08:55:30 [Info] [4280515873] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 403; CANCEL
2019/12/02 08:55:30 [Info] [1846036703] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 405; CANCEL
2019/12/02 08:55:31 [Info] [1588946313] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 407; CANCEL
2019/12/02 08:55:37 [Info] [3774176444] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 411; CANCEL
2019/12/02 08:56:11 [Info] [1913081805] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 413; CANCEL
2019/12/02 08:56:16 [Info] [1809757778] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 415; CANCEL
2019/12/02 08:56:26 [Info] [2333996337] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 417; CANCEL
2019/12/02 08:56:39 [Info] [4171362482] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 419; CANCEL
2019/12/02 08:56:39 [Info] [1146838814] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 423; CANCEL
2019/12/02 08:56:39 [Info] [625695323] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 421; CANCEL
2019/12/02 08:56:39 [Info] [2739784565] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 425; CANCEL
2019/12/02 08:56:39 [Info] [558061020] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 409; CANCEL
2019/12/02 09:05:31 [Info] [1226193380] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 311; CANCEL
2019/12/02 09:05:31 [Info] [2526464214] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vmess/inbound: invalid request from <IP_ADDRESS>:50220 > v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 171; CANCEL

客户端错误日志:
2019/12/02 22:11:33 [Info] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe
2019/12/02 22:11:46 [Info] [888748416] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/12/02 22:11:46 [Info] [3280895938] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/12/02 22:11:46 [Info] [2052814815] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/12/02 22:11:47 [Info] [1767668478] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/12/02 22:11:48 [Info] [2968754233] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/12/02 22:11:49 [Info] [3623113930] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/12/02 22:11:57 [Info] [3622868858] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/12/02 22:11:58 [Info] [4161351635] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/12/02 22:11:59 [Info] [3665410282] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/12/02 22:12:12 [Info] [2147131559] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/12/02 22:12:13 [Info] [1380429388] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/12/02 22:12:17 [Info] [110920364] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/12/02 22:12:22 [Info] [2242320780] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/12/02 22:12:32 [Info] [1470336529] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/12/02 22:12:34 [Info] [960041049] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/12/02 22:12:34 [Info] [2344660237] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled
2019/12/02 22:12:35 [Info] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/vmess/outbound: connection ends > context canceled

请附上访问日志。在 Linux 中，日志通常在 /var/log/v2ray/access.log 文件中。

2019/12/02 09:15:10 <IP_ADDRESS>:50220 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 521; CANCEL
2019/12/02 09:15:13 <IP_ADDRESS>:50220 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 545; CANCEL
2019/12/02 09:15:14 <IP_ADDRESS>:50220 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 473; CANCEL
2019/12/02 09:15:14 <IP_ADDRESS>:50220 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 553; CANCEL
2019/12/02 09:15:14 <IP_ADDRESS>:50220 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 547; CANCEL
2019/12/02 09:15:14 <IP_ADDRESS>:50220 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 465; CANCEL
2019/12/02 09:15:14 <IP_ADDRESS>:50220 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 501; CANCEL
2019/12/02 09:15:14 <IP_ADDRESS>:50220 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 511; CANCEL
2019/12/02 09:15:14 <IP_ADDRESS>:50220 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 537; CANCEL
2019/12/02 09:15:14 <IP_ADDRESS>:50220 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 535; CANCEL
2019/12/02 09:15:14 <IP_ADDRESS>:50220 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 471; CANCEL
2019/12/02 09:15:14 <IP_ADDRESS>:50220 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 449; CANCEL
2019/12/02 09:15:14 <IP_ADDRESS>:50220 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 503; CANCEL
2019/12/02 09:15:14 <IP_ADDRESS>:50220 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 531; CANCEL
2019/12/02 09:15:14 <IP_ADDRESS>:50220 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 549; CANCEL
2019/12/02 09:15:14 <IP_ADDRESS>:50220 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 461; CANCEL
2019/12/02 09:15:14 <IP_ADDRESS>:50220 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 489; CANCEL
2019/12/02 09:15:14 <IP_ADDRESS>:50220 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 469; CANCEL
2019/12/02 09:15:14 <IP_ADDRESS>:50220 rejected  v2ray.com/core/proxy/vmess/encoding: failed to read request header > stream error: stream ID 481; CANCEL

其它相关的配置文件（Caddy 配置文件）

xxx.yyy.zzz
{
  log ./caddy.log

  proxy /bucket https://localhost:20190 {
    insecure_skip_verify
    header_upstream X-Forwarded-Proto "https"
    header_upstream Host "xxx.yyy.zzz"
  }
}

设置加密停止h2再测试

更改为 (caddy+tls) + ws，不加密，可以稳定使用。
考虑到在之前的配置下，V2Ray 刚启动时总是可用，过一段时间（比如半小时）后无法连接，重启 V2Ray 后（不重启前置 Web 服务器）又恢复正常。也许和 V2Ray 的 h2 实现有关？条件允许的情况下，建议尝试复现一下。

您的caddy是否欠了电子证书?

您的caddy是否欠了电子证书?

感谢回复。Caddy 集成了 ACME，在默认的配置下会自动申请 SSL 证书并应用。我在 V2Ray 服务端配置文件中设定的证书是这一证书的软链接。

Caddy设置了证书，V2Ray的server就不用设置证书了吧？不然岂不是要加密两次？


Unit tests

Ideally this project should have unit tests so we can avoid regressions. I could work on setting this up if that's helpful. I have one bugfix PR open that really feels like it should have a unit test covering it.
Any testing framework preferences?

I don't have a preference for frameworks. You can use the one you prefer and send a PR. Thanks!


Paper properties colourDescriptions: and recycled: in version 2.0.0

Why are Paper properties colourDescriptions: and recycled: in version 2.0.0 defined as arrays?
Is it an error?
All other Paper properties are defined as single values.
   colourDescriptions:
      type: array
      minItems: 1
      items:
        type: string
        minLength: 1
    recycled:
      type: array
      minItems: 1
      items:
        type: object
        required:
          - value
          - UOM
        properties:
          value:
            type: number
          UOM:
            type: string
            enum:
              - Percentage

This looks like a mistake, even before from when we move out of multiple-values-property for the 2.0.0, colourDescription (singular) was missing, as well as for recycled.
colourDescription:
  type: string
  minLength: 1
recycled:
  type: object
  required:
    - value
    - UOM
  properties:
    value:
      type: number
    UOM:
      type: string
      enum:
        - Percentage

It is also weird/annoying that the recycled property is not a noun, maybe it is the right time to change it to something like recycledContent, so we can have a clear singular and plural forms that can be used in the future. Let's discuss the best name:

OPTION 1: recycledContent
OPTION 2: recycledProprotion
...

We decided to go with:
colourDescription:
  type: string
  minLength: 1
recycledContent:
  type: object
  required:
    - value
    - UOM
  properties:
    value:
      type: number
    UOM:
      type: string
      enum:
        - Percentage

I have updated both papiNet-API.PROPOSAL.yaml and papiNet-API.yaml, see commit 45c57ec, so we close the issue.


Fix #701 allow quoted values for IN operator and refactor

While working on the where param I noticed that it may suffer from this lacking #701 as well, for example in people?where=and{name=in.Thompson, Larry,or{age=gte.18,height=lte.180}} or even ..eq.Thompson, Larry,or{age.. I'll have to consider that later.
Because of that I thought on working this first and also do some refactoring, the where param may combine different parsers so I'm trying to be cautious and not make my implementation a source of bugs or maintainability problems.

Very nice refactoring.
Only thing that seems repetitive is the operator related stuff types.
I see basically 3 forms to represent an operator
like / Like / LIKE and the definitions and transitions between them are spread between a few places.
Would it be possible to have the definition somehow only in a single place
with an array of (Like, "like", "LIKE") and then have a function that that translates form one representation to another and use that function in the definition of the Read/Show instances and the other function that does some translation for the parsers?
Having it this way, will make adding new operators easier if the need arises.
@begriffs what do you think?

@ruslantalpa By defining the Operator type and its constructors I meant to make the Like constructor in your example the only representation of the querystring operator like that postgREST sees. The Read/Show instances are just for obtaining that representation in the Parsers, and the only transition I saw was from that querystring Operator to his SQL operator. I could make this clear maybe by renaming Operator to QSOperator and adding comments.
I get that there are 3 functions now to handle that instead of the operators tuples but my main motivation for converting this to types was to avoid having the pgFmtOperator that lookups the operators and instead just pattern match to convert the Operator to SQL like in opToSqlFragment, I thought it was better to have that transition closer to the types.
if I where to do the (Like, "like", "LIKE") array I think the Like constructor wouldn't add any value and maybe it'll be better to just delete it and go back to the operators tuples.

I merged Ruslan's PR because I'd like to begin some work on top of it. Could you rebase please?

Done.

Looks good. Adding a note for myself to update the docs to mention quoting the IN values.


Error when coloring using command

I dont usually recolor using the context menu or command.
But I just tried the command and it does not work:

thanks for reporting this. This issue has been fixed in v 0.2.6


use switch-case in Dart

Switch case

I want to handle objects with a switch case. Just like Kotlin, why not increase this ability? Currently it can only handle constants...
Sincerely
A flutter fans😋

@Maskedheroe you should ask / request here https://github.com/dart-lang/language/issues/27

Please request this feature here https://github.com/dart-lang/language


Custom config.php?

Check if there is an easy way to allow users to use custom config.php files.

Users will have to provide their custom.php using an external volume.


EnumRequest - Table 110 Sales Shipment Header - Field - Bal. Account Type

EnumRequest - Table 110 Sales Shipment Header - Field - Bal. Account Type

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


used trivy version 0.37.1, that enabled also downloading the java db.

implements issue #12

hey @kforner thanks for the PR! we'll be testing it and see to merge it asap 👍

thanks @kforner for the contribution!


can't login with microsoft account

When I put the email and password login information in the file and then start it, it say that credentials are not correct.
Why it doesn't work

Did you enabled microsoft auth in type field?


documentation and examples on accessible routing patterns

Hi, is there anything that i can do?
I am new to open source and nuxt but i would love to contribute.

That would be fantastic! I think a page of advice on accessibility patterns for Nuxt would be great. (I think generic accessibility content could be simply signposted to other websites, but things specific to Nuxt could have examples or a list of best practices.)

That's great, I'll try to look into it.


RemoveUntraceableBlocks and NEP-17 tracking

We never ever touch NEP-17 transfers, so they'll keep adding up even with RemoveUntraceableBlocks set to true. I'd expect this data to be deleted at the same time with blocks, but it's not trivial to do that with current DB scheme.

We also need to remove outdated NEP-17 transfers during state exchange process after state sync is completed when state jump is performing. The only outdated NEP-17 transfers we have by this moment is genesis-related transfers (for height 0). Ref. #2019.

If we're to have #2263 implemented it'll be possible to drop old entries by iterating over batch keys, but they start with account hash, so while we can skip some records based on the time data we can't avoid going through all accounts (and we'll have many of them). Reversing the key into "date + account" from "account + date" is problematic wrt batching scheme and RPC.
Maybe we can store all accounts touched by a block in the block data itself? We remove transactions in a similar way, so if we're to store accounts we might also drop stale transfer data by iterating over just the accounts we need?

Current storage scheme seems to be sufficient, we can handle stale entries in GC routine of #2095.


2-make-the-payment-system-work

Last think from functionality is the payment. Need to think of some sort of payment system.
1) Could try to use third-party app to accept payment.
2) We could send email with confirmation, that order is processed and person will pay with cash.

Scrap for now. Need input


Lokalise: Translations update

This pull request was initiated by Lokalise (user Peter Murray) at 2021-12-20 16:06:56

Test errors found for formatjs-compile. See https://jenkins-aws.indexdata.com/job/folio-org/job/ui-bulk-edit/job/PR-36/1/


chore: create Pull Request Template

A basic PR template for this repo.

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

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


Rename DevFile to Devfile inside alizer code

Which area this feature is related to?
/area alizer
Which functionality do you think we should add?
Inside the project we are mentioning the term DevFile instead of Devfile in various variables and functions.
This will improve the consistency between the different places that this term is found inside this project, but also on other devfiles projects.

We can use deprecation to ensure no breaking changes, e.g. keep both DevFile and Devfile

Regarding the scope of the issue: The main reason that we need to be cautious about this update is the usage of recognizer.SelectDevFilesFromTypes func. This function is replaced by the recognizer.MatchDevfiles, but it is used from external users already.
As a result, we need to add a deprecation warning to our documentation for this specific function and we can keep it as is. In the future it can be removed in favor of recognizer.MatchDevfiles which has a new feature of filters (passing filters to the devfile API)


Refactor PatrolBoatView to reduce size

The code for this view has grown to large, and some of the functionality should be moved to new sub-views (e.g., to handle the changes to duty state

 Raise new issues resulting from using/testing the apps


Fix taking out long samples

Removing long samples from list samples in the for loop will change the length and the indices of samples. This will cause problems when there are more than one items in to_single_batch.
#8 tries to handle the same issue, but it's wrong too, and cannot handle to_single_batch longer than 2 items. My fix is to remove long samples after saving all the long samples in list_samples_batches list. With this fix, #8 is not necessary.

Thanks for the fix!

@shirley-wu
I don't understand why the fix in #8 is WRONG and cannot handle to_single_batch longer than 2 items.
Notice that how the batchify function get the list to_single_batch, it designed to be sorted:
to_single_batch = []
for i in range(0, len(samples)):  # the pivot i here is in a ascending sequence
    if len(samples[i]['tokens']) > 350:
        to_single_batch.append(i)

The remove operation for a list lst results in a new list with lst[:target] + lst[target+1:]，when we remove indexes in a reverse order, the next remove operation must be in lst[:target], which is proved to be stable:
samples = ['1', '2', '3', '4', '5']
to_single_batch = [1, 4]
for i in to_single_batch[::-1]:
    samples.remove(samples[i])
print(samples) # => ['1', '3', '4']

At last, with the fix in #12 the complexity improves from O(len(samples)*len(to_single_batch)) to O(len(samples)*log(len(to_single_batch))), I missed this, nice work.

@shirley-wu
I don't understand why the fix in #8 is WRONG and cannot handle to_single_batch longer than 2 items.
Notice that how the batchify function get the list to_single_batch, it designed to be sorted:
to_single_batch = []
for i in range(0, len(samples)):  # the pivot i here is in a ascending sequence
    if len(samples[i]['tokens']) > 350:
        to_single_batch.append(i)

The remove operation for a list lst results in a new list with lst[:target] + lst[target+1:]，when we remove indexes in a reverse order, the next remove operation must be in lst[:target], which is proved to be stable:
samples = ['1', '2', '3', '4', '5']
to_single_batch = [1, 4]
for i in to_single_batch[::-1]:
    samples.remove(samples[i])
print(samples) # => ['1', '3', '4']

At last, with the fix in #12 the complexity improves from O(len(samples)*len(to_single_batch)) to O(len(samples)*log(len(to_single_batch))), I missed this, nice work.

Sorry I didn't think it thoroughly. Your code is correct. Previously I ran the code on my own dataset and it couldn't remove the right samples, so I assumed there is a problem in the index operations. I rechecked and the real problem is that there are some duplicate samples in my dataset. An example is like this:
``python
samples = ['1', '2', '3', '4', '1']
to_single_batch = [0, 1, 4]
for i in to_single_batch[::-1]:
samples.remove(samples[i])
print(samples) # => ['4', '1'], but expect to have ['3', '4']

But the problem is more about my data preprocessing rather than the codes, because ideally `doc_key` and `sentence_ix` should be unique for each sample. Thanks for pointing it out!


Atom v1.7.2 Crashes Very Frequently on Windows 10 x64

Prerequisites

[ ] Can you reproduce the problem in safe mode?
[x] Are you running the latest version of Atom?
[x] Did you check the debugging guide?
[x] Did you check the FAQs on Discuss?
[x] Are you reporting to the correct repository?
[x] Did you perform a cursory search to see if your bug or enhancement is already reported?

Description
Windows 10 x64, Atom v1.7.2 (installed with the Windows installer)
Atom started to crash VERY frequently for me, almost every hour, when I'm regularly typing in the editor. It started to happen recently, either 1.7.2 or 1.7.1 version. I use Atom for at least 5 hours a day so I'm seeing this 4-5 times a day.
I have two different Windows 10 x64 machines and this started to happen simultaneously in both machines. Both have 16GB memory and I never use more than 50% of it. Intel i5-3340M & i7-2600 processors. I tried uninstalling & re-installing several times which didn't fix this issue (cleaned .atom folder too, except for the config.cson and packages folder).
See crash logs from AppData\Local\Temp\Atom Crashes\operation_log.txt here: https://gist.github.com/tedyun/2525fbefcdf1f68e82594d419ca37554
Steps to Reproduce

Use Atom v1.7.2 for a while on Windows 10 x64.
Editor crashes almost every hour when I'm regularly typing in the editor.

Expected behavior: Should not crash that often.
Actual behavior: Crashes frequently.
Versions
atom --version
Atom    : 1.7.2
Electron: 0.36.8
Chrome  : 47.0.2526.110
Node    : 5.1.1
apm --version
apm  1.9.2
npm  2.13.3
node 0.10.40
python 2.7.10
git 2.8.0.windows.1
visual studio
Windows 10 x64

@tedyun Part of the reason for you to file a new issue is to ensure that you've followed all the preliminary steps. Please include all the information from the ISSUE_TEMPLATE.md.

@lee-dohm Report updated.

Have you tried safe mode? Try --safe and see if the issue stops.

No I couldn't reproduce the issue in the safe mode from a quick testing I did. I do need several packages for my day-to-day tasks so I had to temporarily switch to a different text editor.
Even if the issue is caused by some package, I still think the text editor base should not crash without any debugging/error message.
I use five popular packages, all of which has > 200,000 users (highlight-selected, linter, linter-jshint, merge-conflicts, project-manager).

Hi @tedyun, you can try using the package-cop package to try to determine which package is crashing Atom for you.

I'm seeing this issue very often on both of my machines, one running v1.7.2 the other v1.8.0-beta2. The crash logs don't have anything in them unfortunately and I can't pin what causes the crash as I've seen it happen when typing as well as coming back to the editor after about 10 minutes.

@HaykoKoryun can you reproduce the problem using Safe Mode? To launch Safe Mode:

Completely exit all instances of Atom
Launch Atom with the command atom --safe

@tedyun Have you had any luck figuring out which package is causing the issue?

No I haven't.. package-cop didn't really help in my case so I'm trying disabling one package at a time. Not even sure if it is caused by a package yet.
@HaykoKoryun Do you use any of these packages? -- highlight-selected, linter, linter-jshint, project-manager

@tedyun Yeah package-cop won't help I don't think since Atom completely crashes; tried opening dev tools to see if there's anything interesting in the console.log but there's nada, and when Atom crashes dev tools goes along with it.
The only package in common with you by the looks of it is project-manager.
By the way, when the editor crashes are you editing a git project by any chance?

When Atom crashes, it should send information to the OS crash reporting system (Console.app on OS X, Event Log on Windows, etc). Have you checked there?

Just checked and nada, there's nothing there related to Atom. I guess that might be because whilst Atom does crash, the Electron shell intercepts it so it's not a complete crash per se.

@HaykoKoryun Yep I'm always editing a git project :)

@tedyun the weird thing is I have an instance open with about 9 git projects in the projects pane which never crashes, and another window with 1 new-ish git project and it crashes all the time.

Just checked my Atom Crashes folder and it looks like one the crashes has a dump file with the exception:

The thread tried to read from or write to a virtual address for which it does not have the appropriate access.

Here's the dump file:
4f6dbb8b-deda-4c4b-9210-55d5705a7d6c.dmp.zip

@damieng Can you take a quick look at this and see if you can tell what's going wrong?

Unhandled exception at 0x776AC244 (ntdll.dll) in 4f6dbb8b-deda-4c4b-9210-55d5705a7d6c.dmp: 0xC0000005: Access violation reading location 0x00000100.
Specifically this is happening inside ntdll.dll where it is being told to free the heap. I don't have the symbols available and can't see a stack trace to figure out where this might be coming from.

After updating Atom to v1.7.3 and disabling the project-manager package, it's crashing much less frequently than before. I've experienced only one crash in the last three days.
Not completely sure those changes are directly related to the crash though.. as I've been trying to use Atom more "gently" too (not open too many files simultaneously, always close/restart when switching git branches, etc.) Will post an update when I have more info.

Hi, I am experiencing this as well on 1.7.3 on windows 10 64bit.
There is nothing in the "Atom Crashes" folder, and it seems that the crashes also appear in safe mode. I have disabled all community packages, but for now left the core packages.
It seems atom crashes while typing, and it may have something to do with the autocomplete.
I cannot find anything in the windows logs either. I am editing a git folder.
I will gladly help with more information:-)

Same here with the latest version (1.7.3)

On Atom 1.7.3 I seem to be getting crashes when in the left side bar when going through the folders. I checked my windows event log and I get nothing in terms of reporting the crash on windows.

This time round just as Atom crashed I think I may have captured a ghost that's in cahoots with the culprit.
Take a look at the screenshot and you can see a few things which were trying to rerender as it crashed (the black bars where the code was supposed to be and the mini-map) (I have blurred out the code as I am working on an as of yet unreleased code).

@HaykoKoryun So does disabling minimap and restarting solve the problem for you?

I have Atom 1.7.3 on Windows 10 x64, working on a git project with many changes to be committed.
Atom keeps crashing once a minute and keeps getting faster and faster the more I write!
It just started happening few days ago and the span of time from one crash to another is getting smaller as my project's uncommitted changes get bigger.

Yeah I've noticed that too; the more uncommited changes you the larger the
probability of a crash.
On 6 May 2016 15:24, "Ramtin Soltani"<EMAIL_ADDRESS>wrote:
I have Atom 1.7.3 on Windows 10 x64, working on a git project with many
changes to be committed.
Atom keeps crashing once a minute and keeps getting faster and faster the
more I write!
It just started happening few days ago and the span of time from one crash
to another is getting smaller as my project's uncommitted changes get
bigger.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/atom/atom/issues/11590#issuecomment-217415588

yes i faced the same problem ATOM Crashes frequently every minute while typing
under this requirement   ATOM 1.7.3  WIN 10 (64)
I my case i solved problem with toggle minimap modul  (defintife a minimap problem)

My experience was similar to @morbidgames and @HaykoKoryun . The editor crashed more frequently when it had more uncommitted changes.
It was definitely not a minimap issue in my case. I don't use the minimap package.

I use minimap but disabling it didn't help. Atom's crashing very often now
as I committed all those files.
On Monday, May 9, 2016, Ted<EMAIL_ADDRESS>wrote:

My experience was similar to @morbidgames https://github.com/morbidgames
and @HaykoKoryun https://github.com/HaykoKoryun . The editor crashed
more frequently when it had more uncommitted changes.
It was definitely not a minimap issue in my case. I don't use the minimap
package.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/atom/atom/issues/11590#issuecomment-217863333

As above minimap is not causing the issue for me. I disabled and kept crashing even after committing as well. However I was using the linter and after disabling it caused a less frequent crash.

I had linter installed but disabled, turns out committing those files
helped Atom. Since then, Atom hasn't crashed at all (I misspoke earlier).
On Monday, May 9, 2016, Dustin Hershman<EMAIL_ADDRESS>wrote:

As above minimap is not causing the issue for me. I disabled and kept
crashing even after committing as well. However I was using the linter and
after disabling it caused a less frequent crash.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/atom/atom/issues/11590#issuecomment-217902695

Ok.  So it looks like the general consensus here is that the probability of a crash increases the more modified VCS files are present.
If you are experiencing a crash on Windows that can not be explained by the above, please create a new issue.

Just disabled the core package git-diff on a whim and everything was fine for ~30 mins, then I re-enabled it and it crashed soon afterwards.

Interesting, I could have seen my cursor turning into hourglass (loading)
when I hovered over the left folder view pane before the crashes. So maybe
too much diff on uncommited data causes the core package to break Atom?
On Monday, May 9, 2016, Hayko Koryun<EMAIL_ADDRESS>wrote:

Just disabled the core package git-diff on a whim and everything was fine
for ~30 mins, then I re-enabled it and it crashed soon afterwards.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/atom/atom/issues/11590#issuecomment-218044986

Been using 1.7.3/Win10 this morning after against the atom repo after a git reset HEAD~5000 to cause some serious git churn but hasn't yet crashed.  There was very little activity in git-diff recently although it could still be some other interaction with it that changed in core atom if that's what it is.

did you try editing code whilst traipsing down memory lane :P? Atom seems
to become more unstable whilst typing...
On 10 May 2016 21:21, "Damien Guard"<EMAIL_ADDRESS>wrote:

Been using 1.7.3/Win10 this morning after against the atom repo after a git
reset HEAD~5000 to cause some serious git churn but hasn't yet crashed.
There was very little activity in git-diff recently although it could still
be some other interaction with it that changed in core atom if that's what
it is.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/atom/atom/issues/11590#issuecomment-218228304

I can confirm that I had a lot of crashes recently while having a lot of uncommitted stuff open. After a commit, Atom hasn't crashed anymore. All my projects are hosted on a network share by the way, I run Windows 7 with Atom 1.7.3 on my dev machine.

Hmm, there are some known issues with network shares - is anyone else on this thread using a network share or can you confirm it's local?

Every file I edit is local in my case.

I've had crashes on both local and network but noticed the problem on the
networked project as it happened a lot more often. Now though on the latest
version it seems a lot worse.
On 10 May 2016 22:47, "Damien Guard"<EMAIL_ADDRESS>wrote:
Hmm, there are some known issues with network shares - is anyone else on
this thread using a network share or can you confirm it's local?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/issues/11590#issuecomment-218252495, or mute
the thread
https://github.com/notifications/unsubscribe/ACddNNlDEgzFgfUlR3DTG_a3e4igmz5fks5qANK7gaJpZM4IOSAd
.

All my files are local as well. I have disabled the gif diff package and
have not experienced crashes since.
On 10 May 2016 at 22:10, Hayko Koryun<EMAIL_ADDRESS>wrote:

I've had crashes on both local and network but noticed the problem on the
networked project as it happened a lot more often. Now though on the latest
version it seems a lot worse.
On 10 May 2016 22:47, "Damien Guard"<EMAIL_ADDRESS>wrote:
Hmm, there are some known issues with network shares - is anyone else on
this thread using a network share or can you confirm it's local?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/issues/11590#issuecomment-218252495, or
mute
the thread
<
https://github.com/notifications/unsubscribe/ACddNNlDEgzFgfUlR3DTG_a3e4igmz5fks5qANK7gaJpZM4IOSAd

.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/atom/atom/issues/11590#issuecomment-218292106

--
Mads Kessel
All2day.dk
Tlf.:31319531
I øvrigt vil jeg blive rigtig glad, hvis du vil fortælle din mening om os
på:
http://www.trustpilot.dk/review/all2day.dk

Managed to get all the symbols lined up on my dev box so that I could make some sense of that dump. It basically appears to be a heap corruption within the Skia layers of Chromium that we picked up in a newer version of Electron for 1.7.3.  I wonder if it is also causing problems on the other platforms as we have crash reports in many places.
ntdll!RtlpFreeHeap+0x244
ntdll!RtlFreeHeap+0x268
msvcr120!free+0x1a
atom!SkTDArray<SkRTree::Branch>::{dtor}+0x6
atom!SkRTree::insert+0x1fb
atom!SkRecords::FillBounds::cleanUp+0x58
atom!SkRecordFillBounds+0xa0
atom!SkPictureRecorder::endRecordingAsPicture+0xbe
atom!cc::DisplayItemList::Finalize+0x26
atom!cc_blink::WebContentLayerImpl::PaintContentsToDisplayList+0x9e
atom!cc::DisplayListRecordingSource::UpdateAndExpandInvalidation+0x314
atom!cc::PictureLayer::Update+0x20d
atom!cc::LayerTreeHost::DoUpdateLayers+0x369
atom!cc::LayerTreeHost::UpdateLayers+0x23
atom!cc::ThreadProxy::BeginMainFrame+0x387

Just had a crash with the core package minimap-git-diff disabled. Haven't had a crash in a while with it disabled; the file I was editing had a lot of uncommited changes as usual.

Same as before with me, after committing my files Atom was stable for a few days but as my uncommitted files piled up, Atom started crashing. After committing those files Atom is stable again. I should start doing checkpoints to avoid this!

Can't even write my code, atom keeps crashing looks like something with the autocomplete?
Windows 10
64bit
Atom 1.7.3

@venomlust %TEMP%\Atom Crashes.  Please upload the latest .dmp files here.

@50Wliu i have operation_log.txt should i reproduce the error?

0bab1c02-45a5-4a84-9afe-e59694ab60f3.txt
48b5a1c5-953a-4cb1-abb7-5a6a6b9dec40.txt
73549bf5-8fb3-4075-9fb9-a772cc7bb389.txt
a040231d-48fc-498f-803e-a3329b1505ad.txt
cc507905-5b48-4dd2-9a67-196e82e32308.txt
cf05ecb8-b549-413f-b1fe-926edbfd1119.txt
d4928496-3f9f-417a-a7a4-35abd71bb7a3.txt
Does these files help figure out what's happening (couldn't upload .dmp files)?

Atom should automatically generate .dmp files when it crashes - I don't know what to tell you if it isn't.

Github doesn't allow .dmp files to be uploaded on their server.
On Saturday, May 14, 2016, Wliu<EMAIL_ADDRESS>wrote:

Atom should automatically generate .dmp files when it crashes - I don't
know what to tell you if it isn't.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/atom/atom/issues/11590#issuecomment-219262877

@50Wliu Just installed atom 1.8.0 beta 3 seems fixed

Github doesn't allow .dmp files to be uploaded on their server.

You can add them to a .zip file and upload them here - that's generally what I do.
@venomlust Awesome, glad to hear it!  Can anyone else confirm that?

I started using 1.8.0 Beta 3 and have a lot of uncommitted files, still haven't experienced any crashes. Seems fixed.

:sparkles: I'm closing this as the crash appears to be resolved on Atom 1.8.0 and above.  If someone is still experiencing this exact issue on 1.8.0 or above, please comment here!

I've solved this by commiting the git, it really works guys !

Crashed several time for me in 1.8.0 version as well.
Atom Crashes.zip
Where I can find PDB for it ?

Nothing changed for me (Atom 1.8.0 win10 x64): Atom still crashes about every 20-30 minutes.

+1

I am, too, having this issue with Atom v1.10.2 and Windows 10 x64.
This is the dump from operation_log.txt
[2304:7260:0914/124030:VERBOSE1:crash_service.cc(394)] dump for pid = 5916 is C:\Users\nicol\AppData\Local\Temp\Atom Crashes\adc6964d-443f-466c-9ab1-f9c1692de148.dmp [2304:17696:0914/124030:VERBOSE1:crash_service.cc(442)] trying to send report for pid = 5916 [2304:15108:0914/124030:VERBOSE1:crash_service.cc(331)] client end. pid = 5916 [2304:7260:0914/124032:VERBOSE1:crash_service.cc(323)] client start. pid = 17124 [15296:19216:0914/124032:VERBOSE1:crash_service_main.cc(68)] Session start. cmdline is [--reporter-url=https://crashreporter.atom.io --application-name=Atom --v=1] [15296:19216:0914/124032:VERBOSE1:crash_service.cc(142)] window handle is 0098117C [15296:19216:0914/124032:VERBOSE1:crash_service.cc(290)] pipe name is \\.\pipe\Atom Crash Service dumps at C:\Users\nicol\AppData\Local\Temp\Atom Crashes [15296:19216:0914/124032:VERBOSE1:crash_service.cc(294)] checkpoint is C:\Users\nicol\AppData\Local\Temp\Atom Crashes\crash_checkpoint.txt server is https://crashreporter.atom.io maximum 128 reports/day reporter is electron-crash-service [15296:19216:0914/124032:ERROR:crash_service.cc(301)] could not start dumper
And I've uploaded my .dmp file.
adc6964d-443f-466c-9ab1-f9c1692de148.zip
This happens when I try to add a repo to Atom using "Add Project Folder" - but with certain folders only. For these certain folders, I cannot add them to Atom - it crashes every single time. For other folders, I can add them with no issues at all. I cannot find anything in common between the folders that cause Atom to crash when adding.

+1 I've a lot of crash in Windows with Atom :/

Atom crashes for me about once every couple of hours. I am not using it as frequently as maybe others, but it is still quite annoying. I used to use notepadd++ but was talked into installing Atom. Whilst I am impressed with the software, the constant crashes are putting me off using it. Does anyone know if there is a fix imminent?

@markymark292 (and everyone else still experiencing crashes) please open a new issue so that we can better troubleshoot what's causing your crashes.  Thanks!

I am having the same issues as others. Constant crashing if I have uncommited changes on Win10 x64. I have already tried disabling git diff, but crashes are still occuring.

I'm windows 7. It is very bad now. I just open a file and it crashes now. And the fan gets louder.

Atom no long works on Windows 7 x64

@c-w-m Can you please file a new bug and provide sufficient details that we can investigate? Thanks.

OK, here is what I went through:

Atom 1.14.0-beta2 was installed on Win7 x64 along with multiple packages, everything worked after initial installation (~1/19/17), I have not been using it for the last month
there has been new software installed on the system but they were not related to Atom (? interaction)
today, I tried to open Atom and it immediately failed
I uninstalled all the packages I had added but it still failed
I uninstalled Atom and deleted the install directory
I've just now installed the new beta (1.15.0-beta4) and it appears to be working

I won't be able to duplicate the old installation to see if the bug can be reproduced, so this is more of a footnote than a bug report.  Thanks for motivating me to test the new installation, I do really enjoy using Atom and want to see the Electron framework mature as a cross platform architecture.

I added some notes, bottom line, the new 1.15.0-beta4 seems to be working.
I didn't go back to the failing installation config so - no bug report
details other than my notes.
Hope that helps.
cm
On Wed, Mar 8, 2017 at 10:20 AM, Damien Guard<EMAIL_ADDRESS>wrote:

@c-w-m https://github.com/c-w-m Can you please file a new bug and
provide sufficient details that we can investigate? Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/issues/11590#issuecomment-285106247, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AXUASFVUnzAUKuYmZpUXpmvteoHjwUSjks5rjuNpgaJpZM4IOSAd
.

I created a new issue that may be related: #14049.

I had the same problem in Windows 10 and I disabled git-diff and github package. Seems to be working fine now.

Lost half a day worth of work due to Atom crashing.

Still crashing. Happened 4 times today.

This closed issue has become a dumping ground for vaguely related issues.  If you are experiencing crashes please try atom --safe to see if it is Atom itself or a third party package. If it still happens in safe mode please open a new issue with a completed issue template.
I am now locking this issue as there are 26 people the majority of who no longer are having issues.


error on last level

An error occurs if

the player has completed the last level
and then uses "resume"

This will try to load level N+1 which doesn't exist.

Solution could be:

remember last level completed
remember whether "in" or "between" levels. When "in" level, propose RESUME button. Otherwise, make it "LEVEL %d"

resolved in 1.12


Iteration Plan for January 2019 [DRAFT]

This plan captures our work in late December and January. Although longer, we treat this iteration as a 4-week iteration because most of us will have time off over the holidays, and it will take us a little bit to get going again once we are back. We will ship our January Update in in early Feburary.

Note: We don't publish any insider builds between December 22nd and January 2nd. Also, we'll be slow in responding to issues.

Endgame

January 28, 2019: Code freeze for the endgame
February 1, 2019: Endgame done

The endgame details for this iteration are tracked in TBD
Plan Items
Below is a summary of the top level plan items.
Legend of annotations:

Mark
Description

:runner:
work in progress

:hand:
blocked task

:muscle:
stretch goal for this iteration

:red_circle:
missing issue reference

:large_blue_circle:
more investigation required to remove uncertainty

:black_circle:
under discussion within the team

Roadmap

[ ] Publish the 2019 roadmap @egamma @kieferrm

Workbench

[ ] :runner: Provide preview of flexible panel/sidebar layout https://github.com/Microsoft/vscode/issues/50853 @sbatten @joaomoreno
[x] :red_circle: :runner: Support multi-line diagnostics messages in the Problems panel @sandy081
[ ] Revisit the explorer context menu (cut, duplicate, open folder) https://github.com/Microsoft/vscode/issues/61110 @isidorn @bpasero
[ ] :muscle: Explore flatting folder hierarchies in the explorer https://github.com/Microsoft/vscode/issues/41627 @isidorn @joaomoreno

UX

[ ] :runner: Update Octicons https://github.com/Microsoft/vscode/issues/65508 @misolori
[ ] Iconography re-design https://github.com/Microsoft/vscode/issues/8017 @misolori
[ ] :runner: Welcome page improvements https://github.com/Microsoft/vscode/issues/63152 @chrmarti @misolori

Terminal

[x] :runner: Support conpty on Windows https://github.com/Microsoft/vscode/issues/45693 @tyriar
[ ] :red_circle: :runner: Improve accessibility of the terminal @tyriar

Tasks

[ ] :red_circle: Add support for custom execution in addition to ShellExecution and ProcessExecution @alexr00

Languages

[ ] :runner: Support semantic selections https://github.com/Microsoft/vscode/issues/4795 @jrieken
[ ] Support semantic selections in LSP https://github.com/Microsoft/language-server-protocol/issues/613 @dbaeumer
[ ] Provide feedback on LSP tutorial @dbaeumer @octref

JavaScript/TypeScript

[ ] :red_circle: Adopt TypeScript 3.3 @mjbvz

JSON

[ ] :red_circle: Support semantic selections in JSON @aeschli

CSS/HTML

[ ] :runner: Improve custom tags and properties in HTML https://github.com/Microsoft/vscode/issues/62976 @octref
[ ] :red_circle: :runner: Provide custom properties in CSS @octref
[ ] :red_circle:Support semantic selections in CSS and HTML @octref

Debug

[ ] Explore Debug API: Debug Config Provider to return launch configurations dynamically https://github.com/Microsoft/vscode/issues/54212 @weinand
Fully support input arguments for command variables in launch configs https://github.com/Microsoft/vscode/issues/64362 @weinand

Install

[x] :runner: Linux: Provide daily insider snaps @joaomoreno

Extension Contributions

[ ] :runner: Migrate vscode-tslint to use tslint as a TS server plugin https://github.com/Microsoft/typescript-tslint-plugin/issues/1 @mjbvz
[ ] GitHub PR extension https://github.com/Microsoft/vscode-pull-request-github/issues/762 @rmacfarlane @rebornix
[ ] Improve Vetur roadmap @octref

Extensions

[ ] :runner: Explore impact of Webview changes in electron 3.0 on extensions @mjbvz https://github.com/Microsoft/vscode/issues/63180
[ ] :red_circle: Investigate to activate extensions after install without window reload @alexandrudima @sandy081
[ ] :runner: Support to install native dependencies when an extension is installed https://github.com/Microsoft/vscode/issues/23251 @sandy081
[ ] :red_circle: vsce should block publishing extensions that use vscode as a dependency (should always be a devDependency) @joaomoreno

API

[ ] Address "DefinitionLink:targetSelectionRange not working as expected" https://github.com/Microsoft/vscode/issues/58649 @jrieken
[ ] :red_circle: Investigate generalized support for 'Fix All' @mjbvz

Exploration

[ ] :runner: Explore support for developing on WSL https://github.com/Microsoft/vscode/issues/63155 @alexandrudima team

Engineering

[ ] :runner: Electron 3.0 upgrade @bpasero
[ ] :red_circle: Explore Electron 4.0 upgrade @bpasero
[ ] :runner: Strict null checking VS Code https://github.com/Microsoft/vscode/issues/60565 @mjbvz team
[x] :red_circle: :runner: Show startup performance times inside an editor @jrieken
Support the adoption of the new Tree widget @joaomoreno

[ ] :runner: Adopt new tree widget in the Explorer @isidorn
[x] :runner: Adopt new tree widget in the Peek widget @jrieken
[x] :runner: Adopt new tree widget in Search @roblourens
[ ] :runner: Adopt new tree widget in Settings @roblourens

Documentation

[x] :runner: Publish new extensibility documentation https://github.com/Microsoft/vscode-docs/issues/2199 @octref team
[ ] Revisit Javascript end user documentation https://github.com/Microsoft/vscode-docs/issues/2190 @mjbvz @gregvanl

Deferred Items

:hand: Support a post install/update hook for extensions https://github.com/Microsoft/vscode/issues/23251 @sandy081 @joaomoreno
:muscle: Use browser logic for improved word navigation in CJK https://github.com/Microsoft/vscode/issues/50045 @rebornix

Explore upgrade to Electron 4 is #61787 ?

happy new year .


Update conditions to include live-tests stage to internal pipelines

The current condition requires LiveTestCtestRegex to be set, however, we can now remove the test regex concept to separate the live and non-live test and use the regex from CtestRegex for public and internal pipelines

Not sure what's being asked for.  Possible it's already been dealt with.  The EngSys team won't be getting to this any time soon.  If this is a priority for the language team, please go ahead and fix/address this.


Fix USDC Earn staked amount

Problem
get_staked_assets endpoint should return USDC staked balance but instead it’s returning always 0. The goal of this task is to get that number back.
This solution
When we try to get the staked balance using querier.get_staked_balance, it fetches the balance using entry.denom from the assets profile which is ibc/2180E84E20F5679FCC760D8C165B60F42065DEF7F46A72B447CFF1B7DC6C0A65 for USDC.
However, this function expects the input to be entry.base_denom (uusdc ) to correctly retrieve the staked amount. (confirmed)
In the case of other assets (elys and eden) base_denom is equals to denom. That’s why it works for the rest.

@cosmic-vagabond Even though this works, we might need to make querier.get_staked_balance(addr.clone(), usdc_base_denom.clone())?; more consistent in the Golang repo. That might be a better solution.

@cosmic-vagabond Even though this works, we might need to make querier.get_staked_balance(addr.clone(), usdc_base_denom.clone())?; more consistent in the Golang repo. That might be a better solution.

sounds good, the changes looks good to me lets figure out with @jelysn what are the changes we need to do in the native code


v2.4.5 release to PyPI

Hey maintainers, firstly thanks for making & maintaining this project we've used it with great success here at Zillow :D
One problem we're hitting though is a number of packages (mostly in the scientific computing community, ie pandas & jupyter) now require python-dateutil>=2.8.1. The good news is blocking issue is resolved (see this PR), thanks for handling this!
The bad news is that change is still lingering in master, I'd like to request a release with the patches included since the v2.4.4. release back in Feb (see the delta here). We'd love to rely on an official release if possible!
Many thanks!

@epierce Would it be possible to cut a new release?

Bump this

I'm planning on releasing a new version the first week in January


LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20210716153712583 to main

LEGO: Pull request from lego/hb_04604851-bac4-4681-9f74-73de611d6e48_20210716153712583 to main with localized lcls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.002%) to 42.75%

Totals

Change from base Build<PHONE_NUMBER>:
-0.002%

Covered Lines:
26253

Relevant Lines:
55746

💛  - Coveralls


gptp: fix endianness of correction field in sync follow up message

#42799
When gptp prepare sync follow up message, endianness of correction does not get converted to network endianness
Signed-off-by: Lu Ding<EMAIL_ADDRESS>

@bibibibi89
You need to add an empty line between the commit title and body:
net: gptp: fix endianness of correction field in sync follow up message
<add an empty line here please>
correction field in sync follow up message must be converted from host
endianness to network endianness.

Passed all checks. May I get some reviews? Thanks.


[Bug] Unable to properly deselect features

Description
When a feature is selected, there is no way to deselect feature, except for refreshing the website.  Clicking at a blank spot only close the inspector panel, not de-highlight the selected features
What browser are you seeing the problem on? What version are you running?
Chrome
The OS you're using
MacOS
Steps to reproduce

Click on any type features to select
Click on a blank spot to deselect

GERS ID of the entity in question (if applicable)
089194ad306fffff047ffe22cd897271
The browser URL at the time you encountered the bug
https://explore.overturemaps.org/#18.15/51.505082/-0.08924

This feature was added as a part of PR #87


Menu colour grading breaks upon leaving main menu

Title, any selected colour grading will revert back to default once you enter any menu's like the inventory or crime.net

Fixed in r21.


Publish package on PyPI

We need the DCSO Portal Python SDK available through PyPI (Python Package Index) so that people can install it using pip.

SDK is now available through PyPI: $ pip install -U dcso-portal-python-sdk


Perhaps make the save image button more conspicuous

Made the button yellow and changed to "export image". What do you think @Munfred ?


expose message item clicked

It was great if it was possible to subscribe for message click events.
Very useful for implement a delete/edit functionality by showing a context menu in the clicked message item.

It will be possible with slots for messages 😉
I want that will be added to customize the view of messages. Did a PR #https://github.com/mattmezza/vue-beautiful-chat/pull/96, waiting 🤔

Here is message click event 😊
#100

Hello! 👋
By expose, do you mean to expose this to library users so that they can subscribe to message clicked event and do some actions upon clicking on a chat message?
Or do you mean internally expose this event such that editing and deleting would be much easier to implement?
@HotspurHN already implemented the editing :)

Closing as we won't expose click event to library users :) 👍


FancyZones Right Shift + Right Ctrl + Left Click drag no longer works for spanning zones

Microsoft PowerToys version
0.72.0
Installation method
PowerToys auto-update
Running as admin
No
Area(s) with issue?
FancyZones
Steps to reproduce
RShift+LClick (hold) to highlight a zone.
Also press RCtrl and drag into another zone.
Instead of adding the second zone to be highlighted, the second zone is highlighted by itself.
I've found that LShift+LCtrl and RShift+LCtrl work.
LShift+LClick(drag)+RCtrl fails to span multiple zones.
RShift+LClick(drag)+RCtrl fails to span multiple zones.
Only LCtrl works for spanning zones.
It was working fine before the update.
✔ Expected Behavior
I was expecting for RShift+LClick(drag)+RCtrl to be able to span multiple zones.
The issue seems to be with RCtrl specifically for spanning.
❌ Actual Behavior
LShift+LClick(drag)+RCtrl fails to span multiple zones.
RShift+LClick(drag)+RCtrl fails to span multiple zones.
Other Software
No response

/bugreport

I'm sorry for the delay, thank you.
PowerToysReport_2023-09-24-06-39-29.zip


Remove IJ1 dependency

During kymograph creation I use the following code :
currentLine = new Line(new_xStart, new_yStart, new_xEnd, new_yEnd);
 currentLine.setStrokeWidth(1);
imp.setRoi(currentLine);

xpoints = currentLine.getInterpolatedPolygon().xpoints;
 ypoints = currentLine.getInterpolatedPolygon().ypoints;
npoints = currentLine.getInterpolatedPolygon().npoints;

I am pretty sure it makes things slower...

See https://github.com/fiji/KymographBuilder/blob/master/src/main/java/fiji/plugin/kymographbuilder/KymographCreator.java#L169
I am looking for help here. I don't know how to do that.

I found an IJ2 algorithm that could do the job here : https://github.com/imglib/imglib2-roi/blob/master/src/main/java/net/imglib2/roi/util/ROIUtils.java#L126
The thing is for now  bresenham() is guessing a closed loop. So I need to adapt it to my needs (and maybe submit a PR to imglib2-roi ?).

ROIUtils.bresenham() is not exactly the same as Line.getInterpolatedPolygon(). For example it does take into account the interval = 1 seen in Line.getInterpolatedPolygon().

Line.getInterpolatedPolygon() : https://github.com/imagej/ImageJA/blob/master/src/main/java/ij/gui/Roi.java#L439

ROIUtils.bresenham() : https://github.com/imglib/imglib2-roi/blob/master/src/main/java/net/imglib2/roi/util/ROIUtils.java#L126

So for now I don't plan to remove the IJ1 deps.

See https://github.com/imglib/imglib2-roi/issues/27


Parallax background Ignore Camera Zoom doesn't work if the ParallaxLayer's motion_offset is modified from script.

Godot version
v4.0.3.stable.mono.official [5222a99f5]
System information
Windows 10
Issue description
Parallax background Ignore Camera Zoom doesn't work if the ParallaxLayer's motion_offset is modified from script.
If camera zoom is (2,2), that layer would be zoomed in, even though it shouldn't be.
I'm guessing ParallaxBackground::get_scroll_scale needs to account for ignore_camera_zoom and return 1 (like it does in _update_scroll)? This gets used by ParallaxLayer::set_motion_offset.
Steps to reproduce
Have camera at some zoom (ex. 2), ParallaxBackground with IgnoreCameraZoom=True. Add below script to a ParallaxLayer.
func _process(delta):
self.motion_offset.x -= 1
Minimal reproduction project
NA

I have something similar happening in my project. Setting the ignores camera zoom doesn't prevent the layer from being misplaced.