Marathon is Crashing Often

Hello,
We run a clustered marathon cluster of 5 machines. We've been noticing the marathon leader "switching" every 15m to an hour. This is causing serious problems such as orphaned containers (containers that mesos knows about but marathon does not).
Looking closer into the issue, we've noticed that our marathon masters are crashing in a few different ways
The first way is a segmentation fault. The gist below is the full hs_xxxx.pid segmentation fault log.
segfault log
The second way it is crashing seems to be related to libmesos
F1128 08:41:20.672775  9158 check.hpp:79] Check failed: f.isReady()
*** Check failure stack trace: ***
    @     0x7fcd9e73c4bd  google::LogMessage::Fail()
    @     0x7fcd9e73e2fd  google::LogMessage::SendToLog()
    @     0x7fcd9e73c0ac  google::LogMessage::Flush()
    @     0x7fcd9e73ebf9  google::LogMessageFatal::~LogMessageFatal()
    @     0x7fcd9e7324e4  _checkReady<>()
    @     0x7fcd9e72ff24  Java_org_apache_mesos_state_AbstractState__1_1fetch_1get
    @     0x7fcdb49aef88  (unknown)

More log context is available here
The third crash also seems related to libmesos
F1128 16:28:24.845263 28864 org_apache_mesos_state_AbstractState.cpp:145] CHECK_READY(*future): is PENDING
*** Check failure stack trace: ***
    @     0x7f1ccb1664bd  google::LogMessage::Fail()
    @     0x7f1ccb1682fd  google::LogMessage::SendToLog()
    @     0x7f1ccb1660ac  google::LogMessage::Flush()
    @     0x7f1ccb168bf9  google::LogMessageFatal::~LogMessageFatal()
    @     0x7f1ccb159ff7  Java_org_apache_mesos_state_AbstractState__1_1fetch_1get
    @     0x7f1ce167ea88  (unknown)

More log context is available here
We are running
Zookeeper 3.4.6, 7 nodes
Marathon 0.7.5, 5 nodes
Mesos 0.20.0, 5 nodes
we have somewhere around 60-100 mesos slaves in an autoscaling group connecting to the mesos masters
Java version 6
# java -version
java version "1.6.0_31"
OpenJDK Runtime Environment (IcedTea6 1.13.3) (6b31-1.13.3-1ubuntu1)
OpenJDK 64-Bit Server VM (build 23.25-b01, mixed mode)

Hello,
I encountered a similar problem. It was encountered when are running about 3000 tasks.
We are running:
Zookeeper 3.4.6, 7 nodes
Marathon 0.7.7-SNAPSHOT, 7 nodes
Mesos 0.21.1, 7 nodes
and, around 25 mesos slaves
java version "1.7.0_65"
A problem could be avoided by adding a JVM option.
-d64
-server
-Xms
-Xms
-XX:NewSize
-XX:MaxNewSize
-XX:PermSize
-XX:MaxPermSize
-XX:+UseConcMarkSweepGC
-XX:+CMSParallelRemarkEnabled
-XX:+UseParNewGC
-XX:SurvivorRatio
-XX:MaxTenuringThreshold
-XX:TargetSurvivorRatio

If running about 5000 tasks:
-d64 -server -Xms8g -Xmx8g -XX:NewSize=6g -XX:MaxNewSize=6g -XX:PermSize=512m -XX:MaxPermSize=512m -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:+UseParNewGC -XX:SurvivorRatio=8 -XX:MaxTenuringThreshold=32 -XX:TargetSurvivorRatio=80
If running about 10000 tasks:
-d64 -server -Xms16g -Xmx16g -XX:NewSize=12g -XX:MaxNewSize=12g -XX:PermSize=512m -XX:MaxPermSize=512m -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:+UseParNewGC -XX:SurvivorRatio=8 -XX:MaxTenuringThreshold=32 -XX:TargetSurvivorRatio=80
and, adjustment of --reconciliation_interval also need.  I'm successful in running about 13000 tasks at present.
I think GC and state.fetch(id).get(timeout.duration.length, timeout.duration.unit) has caused problems.
https://github.com/mesosphere/marathon/blob/0.7.7-SNAPSHOT/src/main/scala/mesosphere/marathon/tasks/TaskTracker.scala#L40

Here's what we know:

org.apache.mesos.state.AbstractState.fetch returns a Java Future backed by a C++ (libprocess) future.  That Future's get method dispatches back into native code, where we see the three failure modes (two kinds of assertion failure, or a segmentation fault.)  See https://github.com/apache/mesos/blob/0.21.1/src/java/src/org/apache/mesos/state/AbstractState.java#L63

The Java Futures returned from the Mesos state API define finalizer methods.  These finalizers free the underlying C++ future.  These finalizers should probably be removed.  See https://github.com/apache/mesos/blob/0.21.1/src/java/jni/org_apache_mesos_state_AbstractState.cpp#L226

The crashes seem correlated with GC events.  The periodicity of crashes under high load with large heaps seems to correspond with the sawtooth heap allocation graph typical of long-lived JVM processes.

@uzyexe, do you know if the problem is any better or worse with the changes introduced in PR #881?  Based on our current understanding of this problem, we had hoped that it could help.

@ConnorDoyle, thank you.
I was running marathon v0.7.5, v0.7.6, v0.7.7-SNAPSHOT(Is now v0.8.0-RC1?).
and I also know PR #881. but, It in particular there was no impact in my environment.

Just ran straight into this issue with 0.7.6 - we plan on upgrading to 0.8.0 this weekend. Happened when we increased our task count significantly. Are there any new updates or workarounds available?
Thanks

This should be fixed with Marathon 0.8.2-RC3 and Mesos 0.22.1 libraries and master.
Please reopen if that doesn't fix your problem.


Add "find assignment references"

Search Terms
find usage reference as LVALUE langauge services assignment read write
Suggestion
Add a language feature that will find a variable/property "x" when assigned a value in the code (or otherwise is used as an LVALUE).
Use Cases
Allows a user to find where a variable/property is set as opposed to defined or read.
Examples
When searching in VSCode, and my cursor is on "name" in
x = myPerson.name
a "find LVAUE references" call would return...
myPerson.name = "Jim";
or
this.name = "Ann";
or
myOtherPerson.name = "Arlo";
but not
class person { name: string; }
or
print(myPerson.name);
or
x = myPerson.name

3 years counting and I also think this would be a pretty nice addition to the development utilities Typescript can provide.
I guess this would not even be difficult as it can probably be based on the existing find-references feature and would only need some kind of filter on which references to return?
Would be interested in working on this myself 🤔

It seems we would need https://github.com/microsoft/vscode/issues/167187 on the editor side of things to allow users to filter the references to just the write ones.
TypeScript's find all references already sends reference entries with a isWriteAccess boolean property that says whether that's a write/assignment reference or not.


chore(*) update Cargo structure for Dependabot

Split the single Cargo workspace we had in two: lib/ and t/lib. This helps separating production vs. development crates for Dependabot.
Minor updates to auto/cargo to force it to use the same lib/ngx-wasm-rs/target/ directory as before instead of lib/target/ with the new workspace change.
Update dependabot.yml to configure several jobs for automated version bumps (distinct from security bumps).
Clean work/lib/wasm on make cleanup.
Always copy SDK example filters to work/lib/wasm due to cleanup change.
Rename the ngx-wasm-rs crate purely for consistency.
New make update target for quick cargo update in all workspaces.

Ping @hishamhm @casimiro for ack of operational changes in this PR.
Ping @locao and @flrgh because I believe this may break the Gateway bazel builds of the Rust modules but I have not tried it yet.

Building Kong Gateway with Wasmer or V8 is already broken as of today, so we will merge this without further consideration for the Bazel build system.


[FEATURE] Add support for Null Safety

Add support for Null Safety

Added support for null safety
https://pub.dev/packages/dialog_flowtter/versions/0.3.0-nullsafety.0


Fixed Team Page Bug

Closes #48

Can you please share the screenshot @ShahzaibJutt

@ShahzaibJutt  we want to review first please provide screenshot  .

@ShahzaibJutt we want to review first please provide screenshot .

Yeah Sure.


Fix mdadm monitor service

Motivation for this change
In #72394 we see a situation where enabling the built-in systemd units for mdadm caused issues for users. I have reviewed the discussion in the thread and am providing a fix that
a) works out of the box without failing units
b) allows to explicitly enable the mdadm monitor service, and
c) takes care to remind the admin to provide an email address.
This can likely be improved further inthe future but should be sufficient to mitigate #72394 and work as a reliable starting point.
Things done

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

[X] NixOS
[] macOS
[] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Nice fixup, seems reasonable to me. Thanks @ctheune

This looks awesome, can't wait for it to be merged. Thank you for the hard work @ctheune!

I just stumbled over this again on my personal server and wondered whether we should reactivate this as it was so close to being merged anyway? I'd be happy update the PR.

Il 18 settembre 2022 19:40:33 CEST, Christian Theune @.***> ha scritto:

I just stumbled over this again on my personal server and wondered whether we should reactivate this as it was so close to being merged anyway? I'd be happy update the PR.

I would be nice to have this closed!
Inviato dal mio dispositivo Android con K-9 Mail. Perdonate la brevità.

@GrahamcOfBorg test systemd-initrd-swraid

I don't knowingly use mdadm on my system (default desktop). Eval started failing on master as:
$ nix build --no-link -f nixos system --keep-going
trace: warning: mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the `mdmon` service to crash.
error:
       … while calling the 'derivationStrict' builtin

         at /builtin/derivation.nix:9:12: (source not available)

       … while evaluating derivation 'nixos-system-nz-23.11pre-git'
         whose name attribute is located at /mnt/archive/big/git/nixpkgs-master/pkgs/stdenv/generic/make-derivation.nix:300:7

       … while evaluating attribute 'buildCommand' of derivation 'nixos-system-nz-23.11pre-git'

         at /mnt/archive/big/git/nixpkgs-master/nixos/modules/system/activation/top-level.nix:53:5:

           52|     passAsFile = [ "extraDependencies" ];
           53|     buildCommand = systemBuilder;
             |     ^
           54|

       (stack trace truncated; use '--show-trace' to show the full trace)

       error: The option `boot.initrd.extraFiles."/etc/mdadm.conf".enable' does not exist. Definition values:
       - In `/mnt/archive/big/git/nixpkgs-master/nixos/modules/tasks/swraid.nix': true

see  #254429 @trofi

see #254429 @trofi

This fixes the eval for me. Thank you!
The only annoyance is that I'm still getting the following warning at eval time: "trace: warning: mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the mdmon service to crash."

It's interesting that you're getting this, with your normal system config.
That means something sets boot.swraid.enable = true;, in your config. e.g. if I'm evaluating nixosTests.simple it doesn't print the warning.
There's only one file in nixpkgs that I can find that would do that, which is modules/profiles/installation-device.nix.

Ah, that's probably because I'm using system with an old state version: system.stateVersion = "21.11"; which defaults to swraid.enable in a roundabout way:
# nixos/modules/tasks/swraid.nix
  options.boot.swraid = {
    enable = lib.mkEnableOption (lib.mdDoc "swraid support using mdadm") // {
      default = lib.versionOlder config.system.stateVersion "23.11";
# ...

Good point… maybe printing this warning (by default) on every system with a stateVersion < 23.11 isn't that great :grimacing:

Oh,

Ah, that's probably because I'm using system with an old state version: system.stateVersion = "21.11"; which defaults to swraid.enable in a roundabout way:
# nixos/modules/tasks/swraid.nix
  options.boot.swraid = {
    enable = lib.mkEnableOption (lib.mdDoc "swraid support using mdadm") // {
      default = lib.versionOlder config.system.stateVersion "23.11";
# ...

Wow, thanks. I ran into this today, too.
warning: Git tree '/home/john/code/repos/mine/JohnOS' is dirty
building the system configuration...
warning: Git tree '/home/john/code/repos/mine/JohnOS' is dirty
trace: warning: mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the `mdmon` service to crash.
error:
       … while calling the 'derivationStrict' builtin

         at //builtin/derivation.nix:9:12: (source not available)

       … while evaluating derivation 'nixos-system-framie-23.11.20230911.ca40349'
         whose name attribute is located at /nix/store/j6d62blp6npckwcj6cjxf0hyga4w94c1-source/pkgs/stdenv/generic/make-derivation.nix:300:7

       … while evaluating attribute 'buildCommand' of derivation 'nixos-system-framie-23.11.20230911.ca40349'

         at /nix/store/j6d62blp6npckwcj6cjxf0hyga4w94c1-source/nixos/modules/system/activation/top-level.nix:53:5:

           52|     passAsFile = [ "extraDependencies" ];
           53|     buildCommand = systemBuilder;
             |     ^
           54|

       … while calling 'g'

         at /nix/store/j6d62blp6npckwcj6cjxf0hyga4w94c1-source/lib/attrsets.nix:599:19:

          598|           g =
          599|             name: value:
             |                   ^
          600|             if isAttrs value && cond value

       … from call site

         at /nix/store/j6d62blp6npckwcj6cjxf0hyga4w94c1-source/lib/attrsets.nix:602:20:

          601|               then recurse (path ++ [name]) value
          602|               else f (path ++ [name]) value;
             |                    ^
          603|         in mapAttrs g;

       … while calling anonymous lambda

         at /nix/store/j6d62blp6npckwcj6cjxf0hyga4w94c1-source/lib/modules.nix:242:72:

          241|           # For definitions that have an associated option
          242|           declaredConfig = mapAttrsRecursiveCond (v: ! isOption v) (_: v: v.value) options;
             |                                                                        ^
          243|

       … while evaluating the option `system.systemBuilderCommands':

       … while calling anonymous lambda

         at /nix/store/j6d62blp6npckwcj6cjxf0hyga4w94c1-source/lib/modules.nix:815:28:

          814|         # Process mkMerge and mkIf properties.
          815|         defs' = concatMap (m:
             |                            ^
          816|           map (value: { inherit (m) file; inherit value; }) (builtins.addErrorContext "while evaluating definitions from `${m.file}':" (dischargeProperties m.value))

       … while evaluating definitions from `/nix/store/j6d62blp6npckwcj6cjxf0hyga4w94c1-source/nixos/modules/system/boot/kernel.nix':

       … from call site

         at /nix/store/j6d62blp6npckwcj6cjxf0hyga4w94c1-source/lib/modules.nix:816:137:

          815|         defs' = concatMap (m:
          816|           map (value: { inherit (m) file; inherit value; }) (builtins.addErrorContext "while evaluating definitions from `${m.file}':" (dischargeProperties m.value))
             |                                                                                ^
          817|         ) defs;

       … while calling 'dischargeProperties'

         at /nix/store/j6d62blp6npckwcj6cjxf0hyga4w94c1-source/lib/modules.nix:887:25:

          886|   */
          887|   dischargeProperties = def:
             |                         ^
          888|     if def._type or "" == "merge" then

       … from call site

         at /nix/store/j6d62blp6npckwcj6cjxf0hyga4w94c1-source/lib/modules.nix:893:11:

          892|         if def.condition then
          893|           dischargeProperties def.content
             |           ^
          894|         else

       … while calling 'dischargeProperties'

         at /nix/store/j6d62blp6npckwcj6cjxf0hyga4w94c1-source/lib/modules.nix:887:25:

          886|   */
          887|   dischargeProperties = def:
             |                         ^
          888|     if def._type or "" == "merge" then

       … while evaluating derivation 'initrd-linux-6.5.2'
         whose name attribute is located at /nix/store/j6d62blp6npckwcj6cjxf0hyga4w94c1-source/pkgs/stdenv/generic/make-derivation.nix:300:7

       … while evaluating attribute 'exportReferencesGraph' of derivation 'initrd-linux-6.5.2'

         at /nix/store/j6d62blp6npckwcj6cjxf0hyga4w94c1-source/pkgs/build-support/kernel/make-initrd.nix:107:3:

          106|   # See #36268.
          107|   exportReferencesGraph =
             |   ^
          108|     lib.zipListsWith

       … while calling anonymous lambda

         at /nix/store/j6d62blp6npckwcj6cjxf0hyga4w94c1-source/lib/types.nix:541:22:

          540|       merge = loc: defs:
          541|         mapAttrs (n: v: v.value) (filterAttrs (n: v: v ? value) (zipAttrsWith (name: defs:
             |                      ^
          542|             (mergeDefinitions (loc ++ [name]) elemType defs).optionalValue

       … from call site

         at /nix/store/j6d62blp6npckwcj6cjxf0hyga4w94c1-source/lib/modules.nix:837:59:

          836|       if isDefined then
          837|         if all (def: type.check def.value) defsFinal then type.merge loc defsFinal
             |                                                           ^
          838|         else let allInvalid = filter (def: ! type.check def.value) defsFinal;

       … while calling 'merge'

         at /nix/store/j6d62blp6npckwcj6cjxf0hyga4w94c1-source/lib/types.nix:762:22:

          761|         check = x: isAttrs x || isFunction x || path.check x;
          762|         merge = loc: defs:
             |                      ^
          763|           (base.extendModules {

       error: The option `boot.initrd.extraFiles."/etc/mdadm.conf".enable' does not exist. Definition values:
       - In `/nix/store/j6d62blp6npckwcj6cjxf0hyga4w94c1-source/nixos/modules/tasks/swraid.nix': true

Manually editing system.stateVersion to be 23.11 (so, ignoring the scary "Did you read the comment?" message) removed the warning and fixed my build.

nixpkgs-unstable channel seems to be blocked on this, BTW.
https://hydra.nixos.org/build/234796902/nixlog/1/tail

@vcunat yeah, I've already prepare #254429 that fixes this and it's waiting to be merged.

The default ISO image configuration now raises a warning.

Maybe we should add an option to disable the mon service sending mail for the iso.

Maybe we should add an option to disable the mon service sending mail for the iso.

The ISO can simply set a non-sensical e-mail-adress like<EMAIL_ADDRESS>Disabling individual services is really a fight against windmills - we'd have to talk to upstream about that as they enable/disable services automatically depending on various udev events...


Update generation of refID for documenting purpose

update generation of refID for documenting purpose according to convention provided by PS

category code (from category table)
date (ddmmYY)
sequence number (which restarts on each day)


RDS migration type file only generated when using mysql engine

If you create a new project with the graphql/rds template
npx create-sst@latest --template=graphql/rds

And use engine: "postgresql10.14" or engine: "postgresql11.13" in the RDS config, sql.generated.ts will not be generated upon migration, however using engine: "mysql5.7" seems to not cause any issues.
This is what I get in debug.log when running a migration with one of the postgresql engine
[debug] [kysely-codegen] {"name":"BadRequestException","$fault":"client","$metadata":{"httpStatusCode":400,

Not sure if related but I am currently battling a similar error.
export const DB = new Kysely<Database>({
  plugins: [new CamelCasePlugin()],
  log: JSON.parse(Config.SQL_LOGGING_LEVELS),
  // 👇👇👇 Triggers the TS error, below
  dialect: new DataApiDialect({
    mode: "postgres",
    driver: {
      secretArn: RDS.db.secretArn,
      resourceArn: RDS.db.clusterArn,
      database: RDS.db.defaultDatabaseName,
      client: new RDSData({ region: Config.REGION }),
    },
  }),
});

Of particular interest could be Types of property 'acquireMigrationLock' are incompatible.. Will let you know @geauser if I find out what's causing this. Next thing I'll try is to downgrade Kysely and see if that helps.
No overload matches this call.
  Overload 1 of 2, '(args: KyselyConfig): Kysely<Database>', gave the following error.
    Type 'DataApiDialect' is not assignable to type 'Dialect'.
      The types returned by 'createAdapter()' are incompatible between these types.
        Type 'PostgresAdapter | MysqlAdapter' is not assignable to type 'DialectAdapter'.
          Type 'PostgresAdapter' is not assignable to type 'DialectAdapter'.
            Types of property 'acquireMigrationLock' are incompatible.
              Type '(db: Kysely<any>) => Promise<void>' is not assignable to type '(db: Kysely<any>, options: MigrationLockOptions) => Promise<void>'.
                Types of parameters 'db' and 'db' are incompatible.
                  Type 'import("/Users/bjorn/Projects/seaboard/seaboard-backend-v2/services/node_modules/kysely/dist/cjs/kysely").Kysely<any>' is not assignable to type 'import("/Users/bjorn/Projects/seaboard/seaboard-backend-v2/node_modules/kysely/dist/cjs/kysely").Kysely<any>'.
                    Property '#private' in type 'Kysely' refers to a different member that cannot be accessed from within type 'Kysely'.
  Overload 2 of 2, '(args: KyselyProps): Kysely<Database>', gave the following error.
    Type 'DataApiDialect' is not assignable to type 'Dialect'.ts(2769)
kysely.d.ts(371, 14): The expected type comes from property 'dialect' which is declared here on type 'KyselyConfig'
kysely.d.ts(367, 14): The expected type comes from property 'dialect' which is declared here on type 'KyselyProps

It looks like koskimas added an argument to acquireMigrationLock() 3 months ago: https://github.com/kysely-org/kysely/commit/fbcf3e3853e6e466fc7e93ce0294d6da32554a14
What's really bizarre is that kysely is a peer dep in kysely-data-api. The PostgresAdapter and MySQLAdapter used, that have the interface responsible for my type error, is taken directly from Kysely. So it's basically complaining that a class/interface in its own package isn't satisfying an interface. Confusing.
I'm probably completely on the wrong track here. Just sharing what I've observed. Tried downgrading kysely - didn't help.

A function property with less arguments than the interface has does implement the interface in typescript. It's the same as not using the last argument.
https://www.typescriptlang.org/play?#code/JYOwLgpgTgZghgYwgAgJLIN4FgBQzkwAUcAXMgM5hSgDmANMgEZmMD2rANhHCAJRkA3VsAAmuAL65cCViErIAHmXQBeTLnxFSFKrV7q8+ZDLmcIAOg6saxXhuSSc4oA

Please open a new thread in #help on Discord.

Thank you @koskimas ❤ that's super helpful.
@jayair - will open a new thread. First, will add some context below that could help tracking down the conflicting versions/installs of kysely.
I have a monorepo setup with two packages:

/package.json
/services/package.json (includes kysely 0.24.2 and kysely-data-api 0.2.0)

Within kysely-data-api, kysely 0.x is listed as a peer dependency. I'm not super familiar with how NPM works, but to my understanding that means that kysely-data-api will not install its own version but rely and demand on one provided by the package.
If kysely-data-api is not the culprit responsible for the 2 parallel versions, the other packages I'd turn my attention to would be kysely-codegen (which is, I assume, used within SST) and sst (that may have some kysely dep somewhere).


It is unclear what extra.top does

I read the theme source for this but it was still a bit abstract. It would be nice to have this documented in the top-level docs in a way that shows what the theme designer intended.

The 'extra.top' option is to set the navigation of the section's pages. Because  the default navigation config of the Zola cannot find the previous or the next page in the nested section, the 'extra.top' is added to mark the page is the super page that has no parent pages.
You can read the related code in the file templates/macros/docs-navigation.html：
{% macro docs_navigation(page, current_section) %}

  {# Find lighter navigation. There are three types: #}
  {# 1. directly find the lighter if exists, #}
  {# 2. find the last page in the previous sibling section, and #}
  {# 3. find the last page in the parent section. #}
  {% if page.lighter %}

        ← {{ page.lighter.title }}

  {% elif not page.extra.top %}
    {% set index = get_section(path=page.ancestors | reverse | first) %}
    {% set parent = get_section(path=index.ancestors | reverse | first)%}
    {% set first_subsection = get_section(path=parent.subsections | first) %}
    {% if index == first_subsection %}
      {% if parent.pages %}
        {% set last_page = parent.pages | last %}

              ← {{ last_page.title }}

      {% endif %}
...
{% endmacro %}


GraphBulkExecutor.InitializeAsync breaks creating new DocumentClients

Describe the bug
After calling graphBulkImporter.InitializeAsync, future attempts to create DocumentClient constructors throw System.FormatException with the message:

The format of value '.NET/BulkExecutorLibrary/' is invalid.

To Reproduce
        var docClient = new DocumentClient(new Uri($"https://{accountName}.documents.azure.com/"), cloudStorageKey);
        Database database = await docClient.CreateDatabaseIfNotExistsAsync(new Database { Id = databaseId });
        var graph = await docClient.CreateDocumentCollectionIfNotExistsAsync(
            UriFactory.CreateDatabaseUri(databaseId),
            new DocumentCollection
            {
                Id = "somegraph",
            });
        var graphBulkImporter = new GraphBulkExecutor(docClient, graph);

        await graphBulkImporter.InitializeAsync(); // REMOVE this line to eliminate the repro

        docClient.Dispose();

        docClient = new DocumentClient(new Uri($"https://{accountName}.documents.azure.com/"), cloudStorageKey);

Expected behavior
I expect that running GraphBulkImporter.InitializeAsync makes no changes to static state that would break creating future objects (that may even be completely unrelated to the GraphBulkImporter).
Actual behavior
I can only create DocumentClient objects until the first initialization of GraphBulkImporter. After that, creating these objects is broken for the life of the AppDomain. This breaks unit tests that include bulk uploading, as well as applications that use the bulk importer.
Environment summary
SDK Version: Microsoft.Azure.CosmosDB.BulkExecutor 1.0.2
Additional context
Result StackTrace:
at System.Net.Http.Headers.HttpHeaderParser.ParseValue(String value, Object storeValue, Int32& index)
   at System.Net.Http.Headers.HttpHeaders.ParseAndAddValue(String name, HeaderStoreItemInfo info, String value)
   at Microsoft.Azure.Documents.HttpClientExtension.AddUserAgentHeader(HttpClient httpClient, UserAgentContainer userAgent)
   at Microsoft.Azure.Documents.Client.DocumentClient.Initialize(Uri serviceEndpoint, ConnectionPolicy connectionPolicy, Nullable`1 desiredConsistencyLevel)
   at Microsoft.Azure.Documents.Client.DocumentClient..ctor(Uri serviceEndpoint, String authKeyOrResourceToken, EventHandler`1 sendingRequestEventArgs, ConnectionPolicy connectionPolicy, Nullable`1 desiredConsistencyLevel)
   at Microsoft.Azure.Documents.Client.DocumentClient..ctor(Uri serviceEndpoint, String authKeyOrResourceToken, ConnectionPolicy connectionPolicy, Nullable`1 desiredConsistencyLevel)
   at GremlinExportTests.<Foo1>d__7.MoveNext() in D:\git\Tests\GremlinExportTests.cs:line 84
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
Result Message:	System.FormatException : The format of value '.NET/BulkExecutorLibrary/' is invalid.

This repros with Microsoft.Azure.CosmosDB.BulkExecutor 1.1.1 as well.

@AArnott - Can you please share the rest of the code after you dispose the DocumentClient and recreate a new one. The BulkExecutor instance would be holding a reference to the disposed client - so I want to know what you attempt to do after what you shared in the code snippet

This is the entire code snippet. The last line is the one to throw the exception.

We need a fix or a workaround to this ASAP. We are running a single unit test at a time because any more than that hits this bug. This is an unacceptable way for us to check in our feature work.


webworker problem react / vite

I cannot get pdf-to-img working, I get the following error
The file does not exist at "/node_modules/.vite/deps/build/pdf.worker.mjs?worker_file&type=module" which is in the optimize deps directory. The dependency might be incompatible with the dep optimizer. Try adding it to optimizeDeps.exclude.
In another project I solved it by importing
import * as pdfjsLib from "pdfjs-dist/webpack";
Would that be an option?

This is a NodeJS package, it's not meant to work in the browser.
In a browser, we can access the native <canvas /> element, so most of the logic in this library is not required

I'm having a similar issue - I'm not using it on the frontend, but instead in a Next.js / Webpack backend. I still get the same error:
Failed to parse document: Atel letter.pdf Error: Setting up fake worker failed: "Cannot find module '/sites/web/.next/server/vendor-chunks/pdf.worker.mjs' imported from /sites/web/.next/server/vendor-chunks/pdfjs-dist.js".
    at eval (webpack-internal:///(rsc)/../node_modules/pdfjs-dist/legacy/build/pdf.mjs:8581:36)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Any advice would be appreciated, thanks!


330db build failure "GpuArrowPythonRunner.scala:80: not found: type WriterThread"

It looks like a recent Databricks 11.3 update pulled in
[SPARK-44705][PYTHON] Make PythonRunner single-threaded
[ERROR] /home/ubuntu/spark-rapids/sql-plugin/src/main/spark311/scala/org/apache/spark/sql/rapids/execution/python/shims/GpuArrowPythonRunner.scala:80: not found: type WriterThread
[ERROR]       context: TaskContext): WriterThread = {
[ERROR]                              ^
[ERROR] /home/ubuntu/spark-rapids/sql-plugin/src/main/spark311/scala/org/apache/spark/sql/rapids/execution/python/shims/GpuArrowPythonRunner.scala:81: not found: type WriterThread
[ERROR]     new WriterThread(env, worker, inputIterator, partitionIndex, context) {
[ERROR]         ^
[ERROR] /home/ubuntu/spark-rapids/sql-plugin/src/main/spark311/scala/org/apache/spark/sql/rapids/execution/python/shims/GpuCoGroupedArrowPythonRunner.scala:84: not found: type WriterThread
[ERROR]       context: TaskContext): WriterThread = {
[ERROR]                              ^
[ERROR] /home/ubuntu/spark-rapids/sql-plugin/src/main/spark311/scala/org/apache/spark/sql/rapids/execution/python/shims/GpuCoGroupedArrowPythonRunner.scala:85: not found: type WriterThread
[ERROR]     new WriterThread(env, worker, inputIterator, partitionIndex, context) {
[ERROR]         ^
[ERROR] /home/ubuntu/spark-rapids/sql-plugin/src/main/spark320/scala/org/apache/spark/sql/rapids/execution/python/shims/GpuArrowPythonOutput.scala:60: not found: type WriterThread
[ERROR]       writerThread: WriterThread,
[ERROR]                     ^
[ERROR] /home/ubuntu/spark-rapids/sql-plugin/src/main/spark320/scala/org/apache/spark/sql/rapids/execution/python/shims/GpuArrowPythonOutput.scala:68: type mismatch;
 found   : java.net.Socket
 required: org.apache.spark.api.python.PythonWorker
[ERROR]     new ReaderIterator(stream, writerThread, startTime, env, worker, pid, releasedOrClosed,
[ERROR]                                                              ^
[INFO] java.net.Socket <: org.apache.spark.api.python.PythonWorker?
[INFO] false
[ERROR] /home/ubuntu/spark-rapids/sql-plugin/src/main/spark321db/scala/org/apache/spark/sql/rapids/execution/python/shims/GpuGroupUDFArrowPythonRunner.scala:71: not found: type WriterThread
[ERROR]       context: TaskContext): WriterThread = {
[ERROR]                              ^
[ERROR] /home/ubuntu/spark-rapids/sql-plugin/src/main/spark321db/scala/org/apache/spark/sql/rapids/execution/python/shims/GpuGroupUDFArrowPythonRunner.scala:72: not found: type WriterThread
[ERROR]     new WriterThread(env, worker, inputIterator, partitionIndex, context) {
[ERROR]         ^
[ERROR] 8 errors found

presumably all spark-rapids Plugin releases (23.02+) supporting DBR 11.3 are affected
Originally posted by @gerashegalov in https://github.com/NVIDIA/spark-rapids/issues/10225#issuecomment-1900886056

we have made changes similar to this in our 341db shim. I think this is the PR they were introduced: https://github.com/NVIDIA/spark-rapids/commit/54145c445dc537cccade45dc1e477bd088707a7d


This is bubble sort

Read up on Squash Commits and read on How to sync a fork using Terminal and then re-send your Pull Request!


BUG: interpolate.AAA: improve dtype consistency and test integer type promotion

Motivated by this example where there is no need to store support points as complex
In [1]: import numpy as np

In [2]: from scipy.interpolate import AAA

In [3]: z = np.linspace(-10,10,num=1000)

In [4]: r = AAA(z, z + 1j)

In [5]: r.support_points
Out[5]: array([-10.+0.j,  10.+0.j])

Also greatly strengthens tests by not assuming z, f and z2 to have the same type
Secondly, adds tests defining integer type promotion as requested in https://github.com/scipy/scipy/pull/21497/files#r1741158461

Hmm not sure if I understand why some tests fail catastrophically and others are completely fine

Motivated by this example where there is no need to store support points as complex

I'm not convinced by the example that a change is needed. There is some interaction between these attributes, e.g.
A[:, m] = (f - fj[m]) * C[:, m]

Then one of the two may need to be promoted each iteration before the operation is performed, right?

Ah yes that's fair point, let's not overcomplicate things then


Move to multi-version model, with separate Dockerfiles for each version

This is how I envisioned supporting multiple versions of a database in a GitHub repo, to simplify supporting multiple (incompatible) versions in perpetuity.
The idea is that the database repo would have one subdirectory, corresponding to one Docker repo tag, for each "compatibility equivalence class," usually a major or minor version of a database. Different revisions within each subdirectory/tag must be compatible with each other for all database operations, in particular --client, --dump, and --restore. Also, a data volume taken from a container running one revision of a tag must be usable in a container running a different revision of the same tag. For PostgreSQL on Aptible, these subdirectories are 9.3 and 9.4.
To simplify and reduce errors in the process of backporting common security fixes and enhancements to all versions of a database, I've added a shared directory in addition to the versioned directories, for common Bats tests and configuration files. run-database.sh is also shared between both versions (I added a new PG_VERSION environment variable to help enable the common script.)
@aaw and @jbergknoff : Thoughts on this format?
PS: Unfortunately, Quay doesn't support building to this format currently (for one, it's not possible to build a Dockerfile not exactly named Dockerfile, or to build a Dockerfile ). That said, I expect they will support it at some point in the near future. So I'm opening this PR to evaluate the general repo layout, and will merge a separate change which, by removing the shared directory and duplicating its contents across 9.3 and 9.4, will build on Quay today.

The diff is tricky to interpret as is. It may be easier to check out this branch locally:
git fetch git@github.com:fancyremarker/docker-postgresql.git version-tags
git checkout FETCH_HEAD

Looks good, I really like the single repo with multiple Dockerfiles. I also like splitting the bats tests into shared/version-specific.

Looks good to me, as well. Official docker images are structured similarly, e.g. https://github.com/docker-library/postgres .


Enhancement: is it possible to avoid a mutex for read-only dbs?

In other words, can readings be parallelized?

Not a good idea. First, the author of the library we use warns that SQL_BUSY errors may always appear; second, there would be nothing to avoid nidified transactions, which are not supported by sqlite. An implementation breaks the tests for this very reason:
=== RUN   TestTwoServesOneDb
    ws4sqlite_test.go:968: SELECT failed {"reqIdx":-1,"error":"SQL logic error: cannot start a transaction within a transaction (1)"}


Brazil passport number

Sources: passports regex, examples

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.33%. Comparing base (fde98f0) to head (3475cf5).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff              @@
##               main    #1437      +/-   ##
============================================
+ Coverage     92.23%   92.33%   +0.09%
- Complexity     3164     3167       +3
============================================
  Files           320      320
  Lines          6182     6182
  Branches        593      593
============================================
+ Hits           5702     5708       +6
+ Misses          338      335       -3
+ Partials        142      139       -3

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


Walking

Looking around is already cool, but even more cool would being able to walk on this terrain.
Depends on https://github.com/Ralith/hypermine/issues/34 I guess.

The issue with walking is gravity. Hyperblock recently decided to use a very Escher-like gravity: https://www.youtube.com/watch?v=NzK0MCwgLE8 but other solutions would be possible; nothing is perfectly intuitive.

To the contrary, the issue is collision detection. It's easy enough to come up with a consistent rule for gravity, but that's no use if you just fall forever.


Sending context from recently accessed buffers

From what I've read online (note: not from GitHub docs directly), the vscode copilot plugin sends the last several accessed files to copilot as additional context to provide better suggestions. This seems particularly useful when classes/types are defined in other files, as without this extra context copilot just guesses at what functions/members/properties exist on the given object.
It would be nice if this package could offer something similar, e.g. sending the buffer contents from the N most recently opened buffers (up to copilot-max-char characters). For safety, likely would only want to include buffers that are also in copilot-mode minor mode.

I have experienced the same behavior on CLion, where it suggests function definitions from other files while completing the current file.
The main challenge is that VSCode's Copilot API is not public. Therefore, copilot.el and other unofficial Copilot plugins rely on copilot.vim. If copilot.vim adds this functionality, copilot.el can also take advantage of it.
https://github.com/github/copilot.vim

https://thakkarparth007.github.io/copilot-explorer/posts/copilot-internals provides some very detailed (but speculative) reverse engineering of how Copilot works. The way it works is somewhat sophisticated:

Gather the last 20 accessed files for the same language as the current file.
Find "similar snippets" from those 20 files, which is done by slicing up the files into windows and calculating the "similarity" of the slices with the file you have open (using Jaccard similarity).
Use a gazillion heuristics to construct a fancy prompt which uses those snippets. Like, a lot of heuristics.

There's a ton of secret sauce in there and my guess is it won't make it to the Vim plugin any time soon. I think you'd need a pretty totally different approach from the one in this project to replicate the behavior of VSCode Copilot, unfortunately - like, you'd probably end up building a prompt engineering pipeline and communicating directly with the OpenAI Codex APIs... which were deprecated last month and partially removed from public access :(

@spenczar Thanks for sharing this excellent article.
All the sophisticated work can be done in the binary (agent.js) file, which is transparent to plugin developer. What I can do is follow the logic in copilot.vim precisely and hope the functionality will be added to the agent.js file from copilot.vim soon.

I've been working on repeating the work from that article, but on the current agent.js in copilot.vim. So far, it looks like it does all the same stuff. It computes Jaccard similarity for sliding windows, does tree-sitter parsing - the whole deal. So a good question is why it seems to feel like it's less clever.
I think that, as it currently stands,agent.js builds its knowledge about other files exclusively via calls to its textDocument/didChange and textDocument/didOpen. Those are only called by copilot--sync-doc, which is only called as part of copilot-complete. So if you haven't tried a code completion in another file in the same agent server session, it won't be available to Copilot as context.
I haven't really been able to make sure of this, but it seems like the agent can alternatively use workspaces. One little piece of evidence of this is if I manually initialize and tell the agent that we can describe workspace folders, it responds saying it wants to use those capabilities.
The current initialization in copilot.el specifies no client capabilities at all:
(copilot--request 'initialize '(:capabilities 'nil))
;; evals to this response from the agent:
(:capabilities
  (:textDocumentSync (:openClose t :change 2)
   :workspace (:workspaceFolders (:supported :json-false :changeNotifications :json-false))))

But if I tell it "We can apply edits to workspaces, and we can tell you the folders that make up a workspace if you ask," we get a different answer from the agent:
(copilot--request 'initialize
  '(:capabilities (:workspace (:applyEdit t :workspaceFolders t :configuration t))))
;; response:
(:capabilities
  (:textDocumentSync (:openClose t :change 2)
   :workspace (:workspaceFolders (:supported t :changeNotifications t))))

I don't actually know how it uses this workspace information; the code is pretty obfuscated. It could be worth experimentation.
But a certain thing to work is to be a little more aggressive with calling copilot--sync-doc. I'm thinking about adding hooks to send it waaaaay more often and seeing how my suggestions change.

@spenczar The workspace option is in LSP standard.
See https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#serverCapabilities and https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspaceFeatures
For copilot--sync-doc, I followed the logic from copilot.vim, which invokes the sync each time before requesting a completion.

@spenczar The workspace option is in LSP standard.
See https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#serverCapabilities and https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspaceFeatures

Yep. I was just saying that the agent supports some workspace capabilities. An LSP server can respond that it doesn't support workspace edits or folders. There is some explicit logic for this in agent.js.

For copilot--sync-doc, I followed the logic from copilot.vim, which invokes the sync each time before requesting a completion.

Yeah, this is reasonable if you want to keep copilot.el as a straight port of copilot.vim. If you're willing to diverge a bit though, you I think sending files more often would be helpful.


ARCHIE-210: Add support for mode GPT-4 plus some other odds and ends

https://cipherhealth.atlassian.net/browse/ARCHIE-210
https://cipherhealth.atlassian.net/browse/ARCHIE-211
https://cipherhealth.atlassian.net/browse/ARCHIE-212
https://cipherhealth.atlassian.net/browse/ARCHIE-177

@markusos @chuchothecat Thanks for the feedback - I'll create stories and address in the next revision


Added Yellowblue theme

Great theme. Thanks for adding Yellowblue. Cheers.

You are welcome. Thank you!


having issue to run overall code in colab and also in jupyter notebook?

having issue to run overall code in colab and also in jupyter notebook? how can i solve this issue ? is python version matter? can anybody tell how can i solve this issue?

Hi @zubairshahg,
thanks for using pyHRV! pyHRV should be able to run with any Python 3.X compatible framework. However, it's difficult to tell what the issue might be here based on the information you provided so far.
Could you provide a few more details about your current setup and what issue you are exactly experiencing? Thanks!


CodeArkive - Puzzle 2

Link to the milestone and objectives table.

Detailed log of all completed objectives including valid proof of work.
https://codearkive.pythonanywhere.com/puzzle-two/
Project Wallet
18c07b4227cb0993fa7a1db834834e42461a0d9f61b2b157dfbfee625bbf3de6

@Niekon01, we are unable to find a project proposal this. Please create a proposal prior to the payout request.

Hey @tspearing, here is the project proposal: https://github.com/thenewboston-developers/Projects/issues/377

Approved for 45000 TNBC.
@Niekon01, when the puzzle is solved, please submit a bounty request for the 10000 TNBC.
https://github.com/thenewboston-developers/Contributor-Payments/issues/new?assignees=&labels=Bounty+Payment&template=bounty-account-refill-request.md&title=Bounty+Payment+Request+-+DD%2FMM%2FYYYY+-+TEAM_NAME


[BUG]: Unknown argument chatProvider when changing Workspace LLM Provider

How are you running AnythingLLM?
AnythingLLM desktop app
What happened?
System: Linux Ubuntu using AppImage
AythingLLM Version: 1.4.4
When attempting to change the "Workspace LLM Provider" in "Chat Settings" I get the error below.
Seems to be the same error for both anthropic and openai. It's possible to change the LLM at the instance level by changing "LLM Provider" just not at Workspace level
Error:
Invalid `prisma.workspaces.update()` invocation:

{
where: {
id: 3
},
data: {
chatProvider: "anthropic",
~~~~~~~~~~~~
chatModel: "claude-instant-1.2",
chatMode: "chat",
openAiHistory: 20,
openAiPrompt: "Given the following conversation, relevant context, and a follow up question, reply with an answer to the current question the user is asking. Return only your response to the question given the above information following the users instructions as needed.",
openAiTemp: 0.7,
? name?: String | StringFieldUpdateOperationsInput,
? slug?: String | StringFieldUpdateOperationsInput,
? vectorTag?: String | NullableStringFieldUpdateOperationsInput | Null,
? createdAt?: DateTime | DateTimeFieldUpdateOperationsInput,
? lastUpdatedAt?: DateTime | DateTimeFieldUpdateOperationsInput,
? similarityThreshold?: Float | NullableFloatFieldUpdateOperationsInput | Null,
? topN?: Int | NullableIntFieldUpdateOperationsInput | Null,
? workspace_users?: workspace_usersUpdateManyWithoutWorkspacesNestedInput,
? documents?: workspace_documentsUpdateManyWithoutWorkspaceNestedInput,
? workspace_suggested_messages?: workspace_suggested_messagesUpdateManyWithoutWorkspaceNestedInput,
? embed_configs?: embed_configsUpdateManyWithoutWorkspaceNestedInput,
? threads?: workspace_threadsUpdateManyWithoutWorkspaceNestedInput
}
}

Unknown argument `chatProvider`. Available options are listed in green.

I get an error when starting the AppImage:
EROFS: read-only file system, unlink '/tmp/.mount_Anythib4quPA/resources/backend/node_modules/.prisma/client/index.js'
Not sure if this is related or not.
Are there known steps to reproduce?
After clicking "Update Workspace" the following error should appear if a value different from "System Default" is selected for "Workspace LLM Provider"

I've tried opening and closing the application several times yet the issue persists.
I only downloaded the AppImage today (version 1.4.4)

Just modified the Linux version to help debug this issue. Can you see if this error reproduces with this app image?
https://s3.us-west-1.amazonaws.com/public.useanything.com/latest/AnythingLLMDesktop.AppImage
Let's see if this boots on your distro + allows you to update that workspace config. Definitely prisma related, but local to on the AppImage

Okay, that was expected to be seen honestly. That was the previous issue. Just reverted to the prior image which was causing the original issue.
While the provider per workspace functionality is not available in 1.4.2, are you able to even set the model per workspace in this version (1.4.2)
https://s3.us-west-1.amazonaws.com/public.useanything.com/legacy/1.4.2/AnythingLLMDesktop.AppImage

It looks like here, for some reason, the Prisma client is failing to generate after migration, this blocks the client from being able to use any updated schema and then fails to update workspaces who use the new fields from the updated schema

That likely could be the fix. Asking people to unzip the AppImage is a bit crazy so I wanted to hold off on recommending that, but it looks like patching the app post-install seems to be the most continuously reliable solution. :/
The main issue is that whatever CI we use to build the image we will have the same issue since Openssl binary native likely wont match what is used on the user OS and will instead come with whatever the CI was using.
Thinking we might just make the app a shell script at this point that can make the appimage on-machine to avoid all of these compatibility quirks. Docker just works for Linux on all distro but nobody wants to use that solution, which is why AppImage even exists

I asked ChatGPT lol and it came back with the following:

Prisma provides a feature to generate a static binary that includes all its dependencies. This can help ensure that the Prisma Client does not depend on the system's OpenSSL version. To generate a static binary for Prisma, you can configure your schema.prisma file with an appropriate binaryTargets option:

generator client {
  provider = "prisma-client-js"
  binaryTargets = ["native", "debian-openssl-1.1.x"]
}

This configuration tells Prisma to generate a client that is compatible with both the native platform it's generated on and specifically for debian-openssl-1.1.x. Adjust the binaryTargets as needed for your deployment target.

Maybe it's possible to just put in a few different openssl versions for the moment for the most popular distributions?

@renegadephysicist you may have just solved a big headache. Will see if we can wrap a new Linux version and test to see if this resolves everyone's issues. If this does, would be happy to mark you as a contributor
Related: https://github.com/prisma/prisma/issues/8112

Even i got the same issue. Looks like prisma is causing the issue.

For now. The solution to simply this for all distros is the run the AppImage in the following way:
./AnythingLLMDesktop.AppImage --appimage-extract && \
cd squashfs-root && \
./AppRun

This will ensure on run that the prisma binaries for your system are installed automatically. Since AppImages mount to /tmp/ and this in not writeable this is the current solution for Linux while we work on a workaround or comprehensive solution..

目前。对于所有发行版本来说，简单的解决方案是按以下方式运行AppImage：
./AnythingLLMDesktop.AppImage --appimage-extract && \
cd squashfs-root && \
./AppRun

这将保证在运行时prisma自动安装系统的二进制文件。由于AppImages挂载到/tmp/并且是不可写的，因此这是Linux的当前解决方案，同时我们正在研究解决方法或综合解决方案。

原来如此!!

For now. The solution to simply this for all distros is the run the AppImage in the following way:
./AnythingLLMDesktop.AppImage --appimage-extract && \
cd squashfs-root && \
./AppRun

This will ensure on run that the prisma binaries for your system are installed automatically. Since AppImages mount to /tmp/ and this in not writeable this is the current solution for Linux while we work on a workaround or comprehensive solution..

it works,thank you very much！

my system is windows, is there any sulution for this issue?

我的系統是Windows，這個問題有什麼解決辦法嗎？

Me too,Encountered the same problem in windows system

我的系統是Windows，這個問題有什麼解決辦法嗎？

Me too,Encountered the same problem in windows system

我也遇到了，解决了吗


useResizeObserver fails to unobserve due to ref being null

🐛 Bug Report
The cleanup function of the useEffect in useResizeObserver can in some cases call unobserve with an empty ref, which will throw a TypeError (Failed to execute 'unobserve' on 'ResizeObserver': parameter 1 is not of type 'Element'.).
https://github.com/adobe/react-spectrum/blob/6e9f55a7cebf5f61cdd89057f7cc8b00d021d4d7/packages/%40react-aria/utils/src/useResizeObserver.ts#L36-L38
At least, this is what I think happens. If I add a check for ref.current existing, it works fine.
This seems like it happens when for example rendering a ScrollView inside a modal/popover that unmounts before the cleanup effect is called, in my case I was trying to use a Virtualizer inside a Popover (see code example). For some reason that I can't figure out, this doesn't happen for the react-spectrum Picker component, although it uses a Virtualizer in this same sense.
Here's a codesandbox where this issue is present. Opening then closing the Select throws the mentioned error. https://codesandbox.io/s/affectionate-vaughan-bcy0f?file=/src/App.tsx

🤔 Expected Behavior

😯 Current Behavior

💁 Possible Solution
I think changing the cleanup function in the useEffect in useResizeObserver to something like this could suffice:
  return () => {
    if (ref.current !== null) {
      resizeObserverInstance.unobserve(ref.current)
    }
  };

🔦 Context
I am building a custom Select component using the react-aria hooks as well as the Virtualizer component.

💻 Code Sample
https://codesandbox.io/s/affectionate-vaughan-bcy0f?file=/src/App.tsx

🌍 Your Environment

Software
Version(s)

react-spectrum

Browser

Operating System

🧢 Your Company/Team
Visly

🕷 Tracking Issue (optional)

@karlpetersson Thanks for reporting this, I think your solution is reasonable. My guess would be that it works for Picker due to the transition the overlay wrapping the popover has.

I think we actually need to just store the ref.current that we use in the setup so that we can re-use it for the tear down
following the pattern described here
https://reactjs.org/blog/2020/08/10/react-v17-rc.html#effect-cleanup-timing

Looks like @LFDanLu has it in his PR already https://github.com/adobe/react-spectrum/pull/1145/files#diff-fa757bcd677038369ad3ed26cca2ff8d645c63dc009266f3d1aeb0e7bdca8a0dR16

The PR has been merged, can you verify that it fixed your issue?


Clone feature

It wourld be nice to be able of cloning the items.
If you disable the sorting with accepts, and you can clone the items, you transform the list in a draggable one very quickly.

+1 Have used the copy-workaround mentioned above, but the dragged item still disappears from the original zone when it's dragged on top of another zone. Any hints to prevent this?

+1

+1 I would also love to have the cloning option.  Otherwise great work!

Along with the solution provided here (https://github.com/MrMDavidson/ng-sortable/commit/cdfd6dc3eed3916638b86012e9a266b167b0d7b4), I have edited the ng-sortable.js for cloning the elements. I don't see any issues. Please let me know if you guys face anything.
I have replaced the apply function of dragItem (Line no: 293) with the below code:
apply: function () {

    // If clone is not set, set it to false
    if (typeof (this.sourceInfo.sortableScope.options.clone) === 'undefined') {
        this.sourceInfo.sortableScope.options.clone = false;
    }

    // If clone is not set to true, remove the item from the source model.
    if (this.sourceInfo.sortableScope.options.clone == false) {
        this.sourceInfo.sortableScope.removeItem(this.sourceInfo.index);
    }

    // If the dragged item is not already there, insert the item. This avoids ng-repeat dupes error
    if(this.parent.modelValue.indexOf(this.source.modelValue) < 0) {
        this.parent.insertItem(this.index, this.source.modelValue);
    }

}

excelente work karthickannan !

Thank you @sbaglieri
Please let me know if you face any issues after changing the code

Documentation would be nice for this.

@a5hik is there a plan to merge this soon?

@amcdnl will do is soon after some testing, I was busy for a while.

Thank you for the patch, AxxlForce. I tried this out, and I'm noticing when I drag an element from a source list, the item is still removed, and it's added back when I drop the item in the target list. So in reality it's not actually cloning.
Your patch does this: http://jsfiddle.net/v265q/
In my opinion, it would be better for it to work like this: http://jsfiddle.net/vaibviad/njYqA/214/

@a5hik and everyone, I've provided an alternative solution for the clone option. Just provide clone: true as an option, and this should work. This solution prevents items from being removed from the source list at all. Documentation will need to be updated.
I've created a pull request.

@chaddjohnson did u get a chance to look at the pull request for #175 also It would be good If you demonstrate the changes with a plunker along with readme changes?

Crap, didn't realize that existed. I'll have to look at that soon.

@a5hik  Have you merged my code with your code??
@chaddjohnson Is this code working fine or is there any issues ??

My code seems to work fine without issues.
I have not had time to look at the other code or test it.

@wonskarol yes will be doing it. in max 2 days. extremely busy with other things. will update you.

Thank you @a5hik

There's one more thing ... as @juusopimia noticed (https://github.com/a5hik/ng-sortable/issues/3#issuecomment-69013948), the dragged element at first disappears from source container and when dropped in destination container, appears again. I mean, this same happens in @karthickannan solution. Is it possible to prevent this behavior?

@wonskarol sure will check this as well.

@wonskarol Thank you for pointing out that issue. I'll work on this and provide the solution within the end of this week.

@wonskarol and all I had tested the patch #204 from @chaddjohnson and @karthickannan and it works fine and merged the same, please take the latest from the master, and let me know If you see any issues.

Ashik

Hi @a5hik,
great job! I don't see any issues, everything works fine :)

Ok Great, let me close this issue.

Awesome!

Any docs?

Is already on main page:
$scope.dragControlListeners = {
    accept: function (sourceItemHandleScope, destSortableScope) {return boolean}//override to determine drag is allowed or not. default is true.
    itemMoved: function (event) {//Do what you want},
    orderChanged: function(event) {//Do what you want},
    containment: '#board'//optional param.
    clone: true //optional param for clone feature.
};

@a5hik: are you going to tag a new version 1.3.1?

Yeah, I will be tagging a new version soon.

With clone option set to true, the list is not sortable anymore.
Anybody got this problem? How to solve?

hi @tbthiago, i'm facing the same issue: "with clone set to true, the list is not sortable anymore".
Did you find a solution to solve it?
Thanks


fix clean sched cache

这个 PR 实现什么功能/修复什么问题:
fix clean sched cache
是否需要 backport 到之前的 release 分支:
release/2.10.0

/cc @swordqiu

/lgtm
/approve

Codecov Report

Merging #1244 into master will increase coverage by 0.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #1244      +/-   ##
=========================================
+ Coverage    7.87%   7.89%   +0.01%
=========================================
  Files         370     370
  Lines       58030   58032       +2
=========================================
+ Hits         4570    4581      +11
+ Misses      53060   53052       -8
+ Partials      400     399       -1

Flag
Coverage Δ

#aFlag
7.89% <0%> (+0.01%)
:arrow_up:

Impacted Files
Coverage Δ

pkg/cloudcommon/db/sharablevirtual.go
0% <0%> (ø)
:arrow_up:

pkg/util/rbacutils/rbac.go
74.76% <0%> (+3.47%)
:arrow_up:

Continue to review full report at Codecov.

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


clean adminBlazorWebsite look

Remove the pages that are not mandatory

The first draft is done in the branch interface/adminBlazorWebsite

Fixed with PR #25


Async Java client for Azure Table Storage

Is there an async Netty based Java client for azure table storage? Just browsing through the repo, it seems like azure-sdk-for-java/sdk/tables might be what I'm looking for but it hasn't been published yet it looks like. Can someone confirm or point me in the right direction. Thanks!

Hey there, thanks for the question. We're working on a new library that will provide both sync and async client options (with either Netty or OkHttp as the backend) and will interoperate with both the traditional Azure Table Storage service, and the Azure Table Storage APIs exposed by CosmosDB. Stay tuned for an announcement soon. You can track our work towards our first preview release in issue #13730. Going to mark this issue as resolved, feel free to re-open if you need further assistance on this topic.
Related-to: #7361


Unable to rename the property of destructuring assignment

From https://github.com/Microsoft/TypeScript/issues/6312#issuecomment-278974537
const x = 1;
const o = { x };
{
    const { x } = o;
    x;
}

Renaming any x will result in broken code.

Option 1
The safe route would be to always leave local variables alone:

If I rename const x = 1; to y, I get const o = { x: y }.
If I rename x the property, I get const o = { y: x } and const { y: x } = o.

Option 2
Whenever we are renaming a property, we might recursively rename any locals that are used in a shorthand property declaration with it.
This would be doable; we handle imports in a similar way. But it could result in incorrect code if there is shadowing involved.
In the case of renaming a local that happens to be used in a shorthand declaration, you probably want option 1 anyway.

Related to #19173 and #15787

Renaming any x will result in broken code.

I can't reproduce this now on 3.4.1. Renaming x to f produces valid code:
const x = 1;
const o = { x };
{
    const { x: f } = o;
    f;
}

const f = 1;
const o = { x: f };
{
    const { x } = o;
    x;
}

@OliverJAsh is this a VS code thing? I also see that behaviour in VS code, but not in the TypeScript playground.
When calling findRenameLocations on the language service in 3.6.0-dev.20190530 however, I get the following objects (with no prefixText or suffixText):
[ { textSpan: { start: 6, length: 1 }, fileName: '/testFile.ts' },
  { textSpan: { start: 25, length: 1 }, fileName: '/testFile.ts' } ]

So I'm not sure this is actually fixed in TypeScript's language service.

Hmm, what behaviour do you see in the playground?
VS Code does have an option to control this behaviour (typescript.preferences.renameShorthandProperties), which they pass through to TS, but AFAIK they don't change the default value.

@OliverJAsh my bad. I didn't realize this was configurable. Probably the playground is not using this.
There is a new providePrefixAndSuffixTextForRename parameter on findRenameLocations:
findRenameLocations(fileName: string, position: number, findInStrings: boolean, findInComments: boolean, providePrefixAndSuffixTextForRename?: boolean): ReadonlyArray<RenameLocation> | undefined;

Once I provided true for that I got the expected results:
[ { textSpan: { start: 6, length: 1 }, fileName: '/testFile.ts' },
  { textSpan: { start: 25, length: 1 },
    fileName: '/testFile.ts',
    prefixText: 'x: ' } ]

Thanks for the help!

From what I can tell the Playground doesn’t actually have a Rename function in the same capacity as VS Code’s - it’s “Change All Occurrences” which is a dumb find-and-replace utilizing multiple cursors:
function f() { let f = 0; }

Right click one of the fs, hit Change All Occurrences and type g.  For your trouble, you end up with a gunction. :smile:


Restructure html report

Proposed Changes
This PR is an overhaul of the AIP html report. An example of the new format can be seen here: https://test-web.populationgenomics.org.au/acute-care/reanalysis/no_private/draft-restructured-report.html
Changes include:

Moving to a tabbed interface allowing the summary stats and run metadata to be moved to their own space
Changing to a single large table containing all variants for all samples. This has some tradeoffs but on balance I think is more usible than one splitting the table per sample.
Simplified data presented in the main result fields of the table.
Added expanding child-row (draw) that includes additional variant and transcript details.
Swapped to the tablesorter js library. Compared to datatables, tablesorter has better support for child rows and better out-of-the-box type-aware advanced filtering.

Things for discussion:

I made many judgement calls on what detail to show where. Overall, I think this is a better balance but we will need to discuss/test with users and revise as needed.
Now we can display additional detail, should we pass more info into the AIP results json? For example, it would be great to have individual genotype data available. Displaying patient HPO terms would also be super useful.
Where do the "support" only variants go that are supporting a CH? As far as I can see the test json I have been using does not actually contain them as "variants"?
I have included single-line descriptions of each category. These probably need wordsmithing. Might also be nice if we can link to full technical description of each category in the docs?
It would be great to include the date variant 1st reported in the top-level variant info if it is available. This way we can highlight and/or dynamically filter to just recent variants.

I love the tabbed interface, it makes the whole view much cleaner (not having to scroll past a bunch of waffle to get to actual variants...)
The one thing I have concerns about it the single-table interface is knowing when all variants/samples have been reviewed. that might be as simple as making the Individual column filter box a drop-down list of available values in that row instead of free text, so an analyst can track through each participant one at a time (if they want).
Adding a top-line annotation on the variants to capture the number of times this variant appears in this cohort could be a useful prompt for users to drop back to a per-variant search, if they want to look for common features/HPO between multiple families with the same variant.
From the discussion points:

Nothing to add about user feedback, interested in seeing how they feel

HPO terms are a simple add, there's some redundancy in adding them per-variant instead of per-individual, but we aren't expecting large variant numbers per family so probably not worth getting hung up over that.

2a. Genotypes are an interesting one. With this more fully-featured display that's probably the main thing completely missing. Given the arbitrary family sizes, it probably makes sense to do that either though a list of inferred relationships rather than sample ID (Proband: 1/1, Father: 0/1), or by embedding a mini-image of the pedigree structure like Seqr has.

The variants in the table are only the ones which qualify as a primary variant. 17:1736124 is an example from that test report - it doesn't appear as its own row because it only qualified as supporting, so the MOI logic skips evaluating it as a primary variant. When two eligible variants (e.g. a Cat 2 and a Cat 4) are in a compound-het, both would appear as a separate row, with reciprocal links to the other as a support.

I can't see where the single-line category description is? The revised README.md will have link-able sections to the individual categories and reasoning for each one. I saw that the inheritance patterns have been added much more concisely under the symbol which is a much better use of space.

This logic doesn't exist yet - I think we discussed it a while back but I've only just added it to the backlog board. The current logic just filters out against prior results, instead of tagging with first date seen - that should be a simple mod, and I've added it to the backlog board.

Couple of touch-ups:
There's a few typos dotted around
The support variants don't render as hyperlinks
The family/individual links don't work (that's on me, the default config file contains the wrong project ID, so the links are invalid. R0039_acute_care ->  R0011_acute_care in the config should fix it)
MutationTaster appears twice in the in silico list, probably something I messed up in the result JSON

The one thing I have concerns about it the single-table interface is knowing when all variants/samples have been reviewed. that might be as simple as making the Individual column filter box a drop-down list of available values in that row instead of free text, so an analyst can track through each participant one at a time (if they want).

Yea, I went back an forth on this. When I have done similar things in the past I have always found the drop-down selectors to be a pain once you have more than a handful of things to select from. I get frustrated hunting for the right one and the string-based filter is much faster. I hear what you mean about not knowing when you are done. In reality I am not sure how we solve this correctly without moving to a more full-featured web app where we can track review state (which I do not think we want to do at this point). I can try adding the drop down and we can try it out.

HPO terms can just be attached to the samples in the results.json. This would be all HPO for that sample and is useful for the analysis to glance at to see what the patient had without the need to look it up. If we wanted to get fancy, we could also annotate the pannel matches with the HPO term that triggered each specific panel match (ie which of the patient HPO terms were the ones that triggered a panel to be flagged). This would require you to do some lifting, but I think we probably need to separate the panels from the flags in the report in any case.

2a. genotypes. My thought would be to keep this simple, remember it is intended to be short cut to clicking through to seqer et al, not a replacement. My thought would be just to present similar to what you see in a seqr variant row: each individual has and ID, sex, affected status and the genotype (so no pedigree/relationship etc). This conveys most of the info without us needing to us to parse the relationships which gets ugly.

Ok I see the logic. I will add a hyperlink to these.

You can find them all here. They appear in the right-hand side of each child row.

There's a few typos dotted around
Yea that is a cost of letting me have commit access to anything... Can you just fix these as you see them please (or send me a specific list). I will never see them 🤦♂

The support variants don't render as hyperlinks
I will fix this

I added in grouping the table by individual. I think this is ready to go?


Added some details and changed scripting into programming

I have added an extra link for people who do not understand frameworks, also I have been more consistent with describing JS as a programming language.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@JMVL64 thanx for the pr :balloon:


support for version 100+ browsers

for some reason my chrome (version 102) wasnt able to connect to gateways but stuff like insomnia and firefox(98) was able to.

Hi @Grayson-code sorry you are having trouble. Express works just fine with 100+ web browsers.
Unfortunately your issue to to vague and not enough information to debug. If you are looking for a general support channel, please check out our Gitter chat.
If you believe it is an issue in Express, but are not sure where the issue is, please provide detailed reproduction steps so we can help diagnose and can reopen the issue.


Update install.rst: needs libprotobuf-dev and libpython3-dev for building from source

Thanks!

I think protobuf-compiler was also needed??


Could not find plugin descriptor 'plugin-descriptor.properties' in plugin zip

elasticsearch/bin/plugin install jprante/elasticsearch-index-termlist
-> Installing jprante/elasticsearch-index-termlist...
Trying https://github.com/jprante/elasticsearch-index-termlist/archive/master.zip ...
Downloading ............................................................................................................................................DONE
Verifying https://github.com/jprante/elasticsearch-index-termlist/archive/master.zip checksums if available ...
NOTE: Unable to verify checksum for downloaded plugin (unable to find .sha1 or .md5 file to verify)
ERROR: Could not find plugin descriptor 'plugin-descriptor.properties' in plugin zip

You have to use the URL
./bin/plugin -install index-termlist -url http://xbib.org/repository/org/xbib/elasticsearch/plugin/elasticsearch-index-termlist/...

Please see README https://github.com/jprante/elasticsearch-index-termlist/blob/master/README.md

@jprante this doesn't work with 2.4.1 (see https://www.elastic.co/guide/en/elasticsearch/plugins/2.4/installation.html)
anyway, I was able to locally compile and make the zip from https://github.com/jilen/elasticsearch-index-termlist, which I could install successfully ;)


Add breadcrumb styles

The breadcrumb styles should usable with elements other than native lists, such as div elements.

Added new breadcrumb styles.


init.d Script

Hey Guys,
currently I start splash with the following command /usr/bin/nohup python3 -m splash.server -v0 &
Is there a way to start splash with an init.d script?
Best Regards
Micha

There must be a way; the way to go is to consult with init.d documentation :) You need to figure out how to run a non-daemon script in background (maybe nohup or a similar utility could help). Adding a watchdog is a good idea because Splash process could exit. There are other options like supervisord, upstart or systemd. Example upstart script is available here: https://github.com/scrapinghub/splash/blob/master/debian/upstart. If you have Docker installed you can also use daemonize Splash using Docker, as described in http://splash.readthedocs.io/en/stable/faq.html#hard-way.
I'm not sure maintaining init.d script in the Splash repo is a good idea, so I'm closing this ticket. For development daemonizing is not needed, and for production using load-balanced instances with a proxy and request queue in front of Splash (as described in docs) is a better idea; single-process Splash without a request queue in front of it could cause issues in practice ( http://splash.readthedocs.io/en/stable/faq.html#splash-instance-is-overloaded). See also: https://github.com/TeamHG-Memex/aquarium.


Documentation is not specific on what permissions are required for personal tokens

When setting up GitHub OAuth, the documentation does not list the permissions required for the authentication process to work.
I've set up a token with just:

user:email
read:org
user

Though I'm not sure if it works, as there's no indication it is (no interstitial page to log in), per #8

user should be enough. its just to provide ability to search users & add them.

Cool, I'll update my permissions.


Configure apache modules in apache role

Currently this is configured in each role based on what those apps need.
This should be configured in apache based on what sites it will host.

Fixed with ea37354


Notes on updating to 0.11.1

Here's the procedure I followed to update to 0.11.1.  Hope it helps update the documentation. There is a recent vulnerability which suggests upgrading to this new version. https://groups.google.com/a/lightning.engineering/g/lnd/c/NtG33wYrHdo/m/fWam0XbLAQAJ
$ cd /tmp
$ wget https://github.com/lightningnetwork/lnd/releases/download/v0.11.1-beta/lnd-linux-armv7-v0.11.1-beta.tar.gz
$ wget https://github.com/lightningnetwork/lnd/releases/download/v0.11.1-beta/manifest-v0.11.1-beta.txt
$ wget https://github.com/lightningnetwork/lnd/releases/download/v0.11.1-beta/manifest-v0.11.1-beta.txt.sig
$ wget https://keybase.io/bitconner/pgp_keys.asc

$ sha256sum --check manifest-v0.11.1-beta.txt --ignore-missing
lnd-linux-armv7-v0.11.1-beta.tar.gz: OK

$ gpg ./pgp_keys.asc
> gpg: WARNING: no command supplied.  Trying to guess what you mean ...
> pub   rsa4096 2018-03-06 [SC] [expires: 2021-03-06]
>      9C8D61868A7C492003B2744EE7D737B67FA592C7
> uid           Conner Fromknecht<EMAIL_ADDRESS>> sub   rsa4096 2018-03-06 [E] [expires: 2021-03-06]

$ gpg --import ./pgp_keys.asc
$ gpg --verify manifest-v0.11.1-beta.txt.sig
> gpg: assuming signed data in 'manifest-v0.11.1-beta.txt'
> gpg: Signature made Fri 02 Oct 2020 00:38:32 BST
> gpg:                using RSA key 9C8D61868A7C492003B2744EE7D737B67FA592C7
> gpg: Good signature from "Conner Fromknecht<EMAIL_ADDRESS>[unknown]
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:          There is no indication that the signature belongs to the owner.
> Primary key fingerprint: 9C8D 6186 8A7C 4920 03B2  744E E7D7 37B6 7FA5 92C7

$ tar -xzf lnd-linux-armv7-v0.11.1-beta.tar.gz
$ sudo install -m 0755 -o root -g root -t /usr/local/bin lnd-linux-armv7-v0.11.1-beta/*
$ lnd --version
> lnd version 0.11.1-beta commit=v0.11.1-beta

Thanks!
This is helpful, especially because the instructions at https://stadicus.github.io/RaspiBolt/raspibolt_40_lnd.html#download refer to the pgp_keys.asc of roasbeef, which just expired last week on 10/2/2020.

Good catch. Can you open a PR with that update?

I opened #657, which fixes some typos introduced in the previous commit and gets roasbeef's old key from a key server.

I think the original topic of this issue has been taken care of with the recent update to RaspiBolt v3. I'm closing this issue, but feel free to reopen it if you think it's still unsolved.


Component - Basic form input

[x] Text
[x] Password
[ ] Number
[ ] Text area

Design review: 4.5-Input
Please check:

[ ] Format when the placeholder is long

[ ] Textarea:
UI bug when have scroll and use shape = "Round"

UI bug in case no label


Precompile fails on Windows 10

Thank you for the great tool, I've used it on Mac for the last 6 months and it's been a big help. Trying to install on Windows now, and can't precompile.
Installed everything fresh on July 15, 2020. Running in VS Code stable on Windows 10. Following these instructions: Build-and-Run-(In-VSCode)
Everything appears to work until the precompile task, which generates the following error:
Active code page: 65001
**********************************************************************
** Visual Studio 2017 Developer Command Prompt v15.9.7
** Copyright (c) 2017 Microsoft Corporation
**********************************************************************

C:\Users\username\Desktop\username\0_Resources\Sumneko\vscode-lua\server\3rd\luamake>tools\ninja.exe -f ninja\msvc.ninja
[0/5] cmd.exe /C cd tools\msvc && lua.exe init.lua ..\..\3rd\bee.lua\build\msvc\msvc-init.ninja
[1/5] cmd.exe /C cd 3rd/bee.lua && ..\..\tools\ninja.exe -f build\msvc\msvc-init.ninja
[4/17] cmd.exe /C project\copy.bat bootstrap\main.lua build\msvc\bin
        1 file(s) copied.
[9/17] Compile C++ build/msvc/obj/bee/endpoint.obj
FAILED: build/msvc/obj/bee/endpoint.obj
cl /nologo /showIncludes -c bee/net/endpoint.cpp /Fobuild/msvc/obj/bee/endpoint.obj /EHsc /Zc:__cplusplus /O2 /GL /Zc:inline /W3 /permissive- /MD /I3rd/lua /I3rd/lua-seri /I. /D_WIN32_WINNT=0x0601 /DBEE_EXPORTS /D_CRT_SECURE_NO_WARNINGS /DNDEBUG /I3rd/lua /std:c++17
bee/net/endpoint.cpp(86): error C2065: 'UNIX_PATH_MAX': undeclared identifier
bee/net/endpoint.cpp(89): error C2132: syntax error: unexpected identifier
bee/net/endpoint.cpp(89): note: offsetof has a builtin meaning; use /Zc:offsetof- to revert to old, non-conforming definition
bee/net/endpoint.cpp(91): error C2027: use of undefined type 'bee::net::endpoint::from_unixpath::sockaddr_un'
bee/net/endpoint.cpp(90): note: see declaration of 'bee::net::endpoint::from_unixpath::sockaddr_un'
bee/net/endpoint.cpp(92): error C2027: use of undefined type 'bee::net::endpoint::from_unixpath::sockaddr_un'
bee/net/endpoint.cpp(90): note: see declaration of 'bee::net::endpoint::from_unixpath::sockaddr_un'
bee/net/endpoint.cpp(93): error C2027: use of undefined type 'bee::net::endpoint::from_unixpath::sockaddr_un'
bee/net/endpoint.cpp(90): note: see declaration of 'bee::net::endpoint::from_unixpath::sockaddr_un'
bee/net/endpoint.cpp(175): error C2027: use of undefined type 'bee::net::endpoint::info::sockaddr_un'
bee/net/endpoint.cpp(175): note: see declaration of 'bee::net::endpoint::info::sockaddr_un'
bee/net/endpoint.cpp(176): error C2079: '$S2' uses undefined struct 'bee::net::endpoint::info::sockaddr_un'
bee/net/endpoint.cpp(176): error C2618: illegal member designator in offsetof
bee/net/endpoint.cpp(176): note: offsetof has a builtin meaning; use /Zc:offsetof- to revert to old, non-conforming definition
[13/17] Link    Dll build/msvc/bin/lua54.dll
   Creating library build/msvc/bin/lua54.lib and object build/msvc/bin/lua54.exp
Generating code
Finished generating code
ninja: build stopped: subcommand failed.
FAILED: build/msvc/_/bee
cmd.exe /C cd 3rd/bee.lua && ..\..\tools\ninja.exe -f build\msvc\msvc-init.ninja
ninja: build stopped: subcommand failed.
The terminal process "C:\Windows\System32\cmd.exe /c chcp 65001 && msvc_build.bat" terminated with exit code: 1.

Any help would be appreciated!

You need to update the Windows SDK.

Just to clarify, which SDK? Do you mean Visual Studio? If we’re using 2017, do I need to install 2019?
Thanks for your help!

On Jul 17, 2020, at 4:43 AM, actboy168<EMAIL_ADDRESS>wrote:

You need to update the Windows SDK.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

https://developer.microsoft.com/en-us/windows/downloads/sdk-archive/


Error on page of route 28-40 (relation 6395727)

The page of relation 6395727 gives an error while it seems to be a correct route relation in Openstreetmap.

@A67-A67 Thanks for reporting this issue.
The first way in the route relation contains only one node. This is unexpected for the logic that analyzes the change in route geometry for the route history.
This is fixed in v2.0.11: ways with just one node are now ignored when analyzing route geometry changes.


docker run command

Hi Daniel,
I face this error using docker on Centos 6.9
docker run -v /data/software/cocoTeam/demo2/models_with_properties/lustre_files/src_tcm_with_properties_PP:/lus kind2/kind2:dev -xml --timeout 60.0  --lus_main tcm_with_properties_PP_TCM_Longitudinal_Guide_130  /lus/tcm_with_properties_PP.lus

kind2 v1.1.0

Error opening input file "/lus/tcm_with_properties_PP.lus":
Sys_error("/lus/tcm_with_properties_PP.lus: No such file or directory")

Normally the file tcm_with_properties_PP.lus does exist in /data/software/cocoTeam/demo2/models_with_properties/lustre_files/src_tcm_with_properties_PP repo
Do you have any idea?
Thanks
Hamza

Hi Hamza,
I cannot reproduce the issue. The command should work.
Best,
Daniel

Hi Daniel,
Could you tell me how to run the bash on your image?
doing this docker run -t -i kind2/kind2:dev /bin/sh
is not working, it runs kind2 on /bin/sh :)
Thanks
Hamza

Hi Hamza,
The Kind2 image uses an ENTRYPOINT instruction to set the main command. You can override it using the docker run --entrypoint flag.
docker run --entrypoint /bin/sh -t -i kind2/kind2:dev
Best,
Daniel

Nice Thanks


EncoderException hidden when sending

I used the marshalling serialization tool, but because the class UserInfo did not implements Serializable, the client threw an exception when sending data. However, the exception was hidden, and there was no exception on the console. As a result, I did not know the cause of any exception
The second:
according to my understanding, any exception should be handled by io.netty.channel.ChannelInboundHandler#exceptionCaught(ChannelHandlerContext ctx, Throwable cause)
demo
https://github.com/brucelwl/demo/tree/netty-marshalling

This is only true for inbound exceptions. Outbound bound operations (like write) will fail the promise only by default.

This is only true for inbound exceptions. Outbound bound operations (like write) will fail the promise only by default.

OK, we don't discuss inbound exceptions, but please run my demo. The client sends data to the server, but the service can't receive it. It doesn't prompt any exceptions, which is very unfriendly。
In fact, the client has already had a serialization exception。
It is hoped that netty can output the exception stack information when the listener is not registered


Should NOTE.EXID be handled by extension instead of by SNOTE?

Issue #64 observed that NOTE cannot have an identifier structure, but SNOTE can.
PR #72 added permission for SNOTE to be used when not shared to obtain access to identifiers.
I think PR #72 is confusing the distinction between NOTE and SNOTE and should be rolled back before we release 7.0.6. Instead, I propose adding a non-normative note like

Note — SNOTE allows an IDENTIFIER_STRUCTURE substructure, but NOTE does not. Conversations are ongoing about changing this in a future version of the specification. Using the current specification, identifiers can be added to NOTEs (and other structures) using a documented extension tag by including the following in the header:
1 SCHEMA
2 TAG _EXID https://gedcom.io/terms/v7/EXID
2 TAG _REFN https://gedcom.io/terms/v7/REFN
2 TAG _UID https://gedcom.io/terms/v7/UID

and using the extension tags like so:
1 NOTE Example
2 _EXID external identifier
3 TYPE http://example.com/note/identifiers
2 _REFN Example note 1
2 _UID 7913f642-c2ff-4371-ab3d-1c8d3ffe6663

FWIW, I like this approach.

As with all extensions: Only some of the applications will support them. By this the danger of losses of data increases when exchanging GEDCOM, whenever we use extensions.
In this case I prefer to use SNOTE record, as this is the way in GEDCOM 7.0 to transfer the identifiers by standard tags.

Discussed 2021-11-30 without resolution. Major points mentioned:

Extension means fewer SNOTEs, and we know many applications do not handle shared NOTE semantics correctly in 5.5.1
Standard means more applications keep the IDs
Standard means 7.0 would allow SNOTE in more places than 7.1 (i.e. SNOTE for shared or identifier in 7.0, only for shared in 7.1). This is just a recommendation, not a requirement, so it's not technically against the rules to remove it in a minor release, but I'd rather not do so.

Discussed 2021-12-07
Many current tools discard extensions they don't understand. Will leave current text; issue closed


filter_stream: provide io.Reader implementation

This pull-request provides an implementation of the io.Reader interface that can read data encoded with the protocol used for filter process communication.
This provides a huge savings on memory usage when cleaning files, as the shasum of the contents can be calculated as data is streamed in, and then discarded.
This pull request is implemented in three parts:

https://github.com/github/git-lfs/commit/4524d1221efc54d82f4a409208e0d83a56a1c78e: Implement the underlying PacketReader.
https://github.com/github/git-lfs/commit/d23c0445f4580d6b82345ae3613bf47ecaff482a: Make the WriteStatus method public since reading packets no longer reports success/error statuses, and this responsibility will be delegated to the caller in the following commit...
https://github.com/github/git-lfs/commit/2db63047c028811deeab1b8462e44251304164ca: use an io.Reader as the Payload field of a request, instead of buffering the data upfront.

Some notes on the implementation:

There is no "offset" encoded into where the reader starts and stops. This means that a given packet run must be completely consumed before the next one is read. The code as it currently stands within this branch, does obey that rule as the synchronization is done with the loop condition, scanner.Scan().
The implementation is safe to call with buffers shorter or longer than the packet that is being read. Any data that wont fit into the current given buffer will be sent to an internal buffer, and subsequent calls to Read(p []byte) will read first from the internal buffer until the internal buffer is drained.
An io.EOF is returned on the first call to Read() after all of the data has been consumed. This is done to avoid a complicated implementation dealing with peeking bytes to see if more data is incoming. Luckily, the Go documentation allows for this (meaning things like io.Copy, etc will respect it):

An instance of this general case is that a Reader returning a non-zero number of bytes at the end of the input stream may return either err == EOF or err == nil. The next Read should return 0, EOF.

(See: https://golang.org/pkg/io#Reader).

/cc @larsxschneider @technoweenie @sinbad @rubyist @sschuberth

I fixed the hang in the integration test from yesterday, but there's a new open question that I'd love some feedback on. The test that is currently broken (and what is causing CI to go 🔴 ) is the pull zero len file test.
This test is broken because LFS tries to write the zero-len file out to the filter protocol, but the protocol code rejects it because packets with no body are invalid (according to: https://github.com/github/git-lfs/pull/1619#issuecomment-258039097 and https://github.com/github/git-lfs/pull/1619#issuecomment-258039532).
So long as that assumption is correct, I think we have two options:

Fall back to the legacy clean/smudge process instead of the filter protocol, which would allow users to track empty files with LFS (not sure if this is useful), but binds us to use legacy APIs which may not be supported in all versions of Git going forward.
We could also just specify that tracking empty files is not allowed and just enforce that requirement earlier on in LFS, so that this situation doesn't happen. I think this course of action makes more sense.

In the case that I misread @larsxschneider's comment and my previous assumptions about lengths were incorrect, then I'll have to re-do some work as described in https://github.com/github/git-lfs/pull/1619#discussion_r86431429, which will propagate its way back to this PR and make this a non-issue.
Curious as to your thoughts.

We could also just specify that tracking empty files is not allowed and just enforce that requirement earlier on in LFS

I agree here. LFS is for large files after all, and zero is not large ;-)

Your assumption was indeed correct and pktline shouldn't send 0004. I was wrong and I am sorry that I confused you. That also explains why my demo code considers 0004 invalid. I just wrote that too long ago to remember correctly.

Re: 1.
I think the new protocol should be able to handle everything. If we would need the legacy protocol in any way then there would be something wrong with the new protocol.
I actually test the case of an empty file in the protocol and therefore it should work:
https://github.com/git/git/blob/be5a750939c212bc0781ffa04fabcfd2b2bd744e/t/t0021-conversion.sh#L375
One trick to see what is going on is to run the tests with GIT_TRACE=1 GIT_TRACE_PACKET=1.
This is how an empty file is processed:
packet:          git> command=clean            # Git wants to clean
packet:          git> pathname=test4-empty.r   # ... a file with this name
packet:          git> 0000                     # end of request header
packet:          git> 0000                     # end of content (= no content!)
packet:          git< status=success           # filter sets status success
packet:          git< 0000                     # end of status
packet:          git< 0000                     # end of cleaned content (= no content!)
packet:          git< 0000                     # end of status (no status change)

Would that work for you?
Re: 2.
An empty file is certainly not large. However, people use the *.bin pattern and this can easily catch empty files (I saw this many times already @Autodesk).

On Nov 6, 2016 5:27 PM, "Lars Schneider"<EMAIL_ADDRESS>wrote:

Your assumption was indeed correct and pktline shouldn't send 0004. I was
wrong and I am sorry that I confused you. That also explains why my demo
code considers 0004 invalid. I just wrote that too long ago to remember
correctly.

Re: 1.
I think the new protocol should be able to handle everything. If we would
need the legacy protocol in any way then there would be something wrong
with the new protocol.
I actually test the case of an empty file in the protocol and therefore
it should work:

https://github.com/git/git/blob/be5a750939c212bc0781ffa04fabcfd2b2bd744e/t/t0021-conversion.sh#L375

One trick to see what is going on is to run the tests with GIT_TRACE=1
GIT_TRACE_PACKET=1.
This is how an empty file is processed:
packet: git> command=clean # Git wants to clean packet: git>
pathname=test4-empty.r # ... a file with this name packet: git> 0000 # end
of request header packet: git> 0000 # end of content (= no content!)
packet: git< status=success # filter sets status success packet: git< 0000

end of status packet: git< 0000 # end of cleaned content (= no content!)
packet: git< 0000 # end of status (no status change)

Would that work for you?
Re: 2.
An empty file is certainly not large. However, people use the *.bin
pattern and this can easily catch empty files (I saw this many times
already @Autodesk).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

One trick to see what is going on is to run the tests with GIT_TRACE=1 GIT_TRACE_PACKET=1.

This is awesome, thanks for letting me know it exists.

packet:          git< 0000                     # end of cleaned content (= no content!)

Makes sense to me, I can make this work! Thanks for the info 🤘


App stops working when the phone goes in standby

While using my phone, I've SoulissApp open in foreground with Music Synch and a Cloud Music Player running. After a while from the standby, SoulissApp goes in OFFLINE and stops sending data to my lights, while the music player in the foreground is playing music.
WiFi is active and the music is streamed from a cloud server, so I've full network connectivity at time of this issue.
Let me know if I have to provide more info, running the 1.5.3-testing release of SoulissApp.

I can't reproduce this, if SoulissApp is foreground it won't stop reproducing because of an OFFLINE state...Even after an hour
Anyone else on this?

I suggest to decouple the OFFLINE from the data send method, this out of
Scenario and Programs that should wait ONLINE before proceed.
Dario.
From Mobile.

apart from the check 'Souliss online' made at the start of nodesDetail activity (to show buttons or not), there is no other reference to the fact Souliss is offline, ie changing this won't solve your issue.


[Minor change] Interpretable models update

Description of changes:
Minor updates to the interpretable preset:

bumping the imodels version (to support better model visualization)
updating the preset model names to work with the new version
minor update to the tutorial

Hopefully should be able to merge in without any issue!
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-1823-3 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-1823/3/index.html


ci: log previous instance of the container in a pod

if the pod is crashed and restarted the current logs are not helpful. Logging with -p might help us to log the previous container.
Signed-off-by: Madhu Rajanna<EMAIL_ADDRESS>

Locally it seems to be misbehaving with error:
[ygupta@localhost ceph-csi]$ kuberc logs csi-cephfsplugin-provisioner-56d8446896-fk24p --all-containers  --previous
Error from server (BadRequest): previous terminated container "liveness-prometheus" in pod "csi-cephfsplugin-provisioner-56d8446896-fk24p" not found

It will help sometimes to debug if the container crashed. or else it will fail with above error.


bump browserify-zlib to 0.2.0

This includes all the fixes mentioned in #51 and #52.

anyone? @sokra @jhnns

Thanks 👍
Shipped with 2.1.0 (should land in current webpack 3 installations)
In alignment with browserify, this has been shipped as non-breaking change (although I couldn't check it for myself since the source code has been changed significantly).