Add arguments to cli to disabling copying image data in share

When importing data into CVAT from the share mount the user can uncheck copy_data and check use_cache to avoid creating multiple copies of the data on the server, this functionality wasn't available in the cli.  So I added it.  It was previously proposed in #2862 and is under the backlog of the project planning as work to be completed here
Motivation and context

When a user downloads images to their CVAT server, then imports into the CVAT application, it is not memory efficient to make 3 copies of the image (raw, original, and compressed) - this functionality allows the user to disable creating these copies.
How has this been tested?

I imported images with the code changes and verified that by default it does not cause the images to be duplicated and the hard drive space does not fill up nearly as rapidly.  Issue #3542 goes into greater detail of copied file location as seen during testing.
Checklist

[x] I submit my changes into the develop branch
[x] I have added description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[x] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[x] I have updated the license header for each file (see an example below)

# Copyright (C) 2021 Intel Corporation
#
# SPDX-License-Identifier: MIT

@shortcipher3 , thanks for the contribution!


Weeds3D - retake video button not working

User in Vermont had an issue where whenever they tried to retake a video (using the retake video button), the weeds3D app would start taking a new video but then say "this video already exists". The previously existing video would then not show up in the weeds3D app. This occurred in the on-farm protocol. I will test to see if this is persistent in other tabs in the weeds3D app.

Any fixes for this yet?

@mikahpinegar @mikahpinegar1 does any of the recent updates fix this?

yes this is fixed in the new version. not sure where it's at with being released

@saseehav kinda. I've told some teams to put their tablets online so the update can be pushed to them, but I've definitely missed a number of them. I can send reminder emails to each project this week and do a big app update push

@saseehav will work with on-farm and ce2 to deploy the newest app

Will work on next deployment of app version this week. Issue with naming 1.6.4 versus 1.7 for example

1.7-field
1 device
7
0
7.14 MB
Min sdk 27
05/24/2023 01:39 PM
5/18/23
Actions

1.6.4-field
4 devices
10
0
7.15 MB
Min sdk 27
06/13/2023 02:05 PM
5/24/23
Actions


Add some more TFVC samples

Address #53, #80, and #82 with additional samples.

@willsmythe could you review or delegate to someone to review? Thanks.


Error: boot.cpp

Describe your bug here.
Error: boot.cpp
C:/HaxeToolkit/haxe/lib/discord_rpc/git/linc/linc_discord_rpc.h(7): fatal error C1083: No se puede abrir el archivo incluir: '../lib/discord-rpc/include/discord-rpc.h': No such file or directory
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build?


Why is C# referred to as 'CSharp'?

All other languages containing the symbol '#' are represented correctly (e.g. F#).
The name "CSharp" is not a correct way of referring to the language. The specification (ECMA-334) states the following at the bottom of page 27:

The name C# is written as the LATIN CAPITAL LETTER C (U+0043) followed by the NUMBER SIGN #
(U+0023).

Is there a specific reason it was decided to use "CSharp" instead of "C#"? Because to me it doesn't make sense considering "special characters" are used all over in file names in this repository.

Well, apparently there are three other languages using "Sharp" (TSharp, ZSharp, QSharp). Still, F# and J# are correctly using '#'.


StackState/StackReducer related leak

Description
For the last 2 days I'v been trying to understand a leak & I have been able to reproduce it in this sample project : NavigationStackLeak.zip
The issue occurs when creating a StoreOf<FlowCore> from scratch, where FlowCore is a Reducer wrapping a StackState / StackAction combined using forEach operator.
It seems like pushing a node in StackState causes effects to be added by _StackReducer that will cause Store & all its properties to not being deallocated once the NavigationStack gets dismissed causing a leak
Thanks in advance for looking into this :)
Checklist

[X] I have determined whether this bug is also reproducible in a vanilla SwiftUI project.
[X] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior
I would expect Store to be removed from memory once the view/controller using them has been dismissed
Actual behavior
Stores are stacking up after each present/dismiss of FlowView
Steps to reproduce

Launch attached project app : NavigationStackLeak.zip
Tap "present stack" button
Tap "go to next screen"
Dismiss modal using cross or swipe down gesture
Repeat 2 or 3 times previous steps
Open memory inspector & filter with FlowCore : you will see as many instance of StoreOf<FlowCore> as modal opened

It's important to note that the issue is not there when FlowCore is embedded in another Reducer like MainCore in example project (try same scenario using "present stack using TCA" button instead). probably because effects built in _StackReducer get properly cancelled in that case.
A quick fix on my side would be to send action to pop all nodes of StackState when receiving dismiss action. However a fix on the lib would be preferable as others could stumble upon this issue & like me waste hours trying to figure out what is happening ;)
The Composable Architecture version information
0.59.0 / 1.2.0 / main branch
Destination operating system
iOS 16.2
Xcode version information
XCode 14.2
Swift Compiler version information
swift-driver version: 1.62.15 Apple Swift version 5.7.2 (swiftlang-<IP_ADDRESS>.5 clang-14<IP_ADDRESS>)
Target: arm64-apple-macosx13.0

Hi @bioche, are you certain it is an issue in TCA and not that SwiftUI is holding onto the Store even after the view has been dismissed? We have seen that many times in the past.
I ran your sample project in Xcode 15 with the iOS 17 simulator and I do not see any leaks in the memory graph debugger. Perhaps it was fixed in iOS 17?

I'm not sure it's SwiftUI as when using the "present stack using TCA" that uses the same views but with a MainCore that has a ifLet reducer it works with no leak.
Also I forgot to mention in the bug report that if I comment those 2 effects in the _StackReducer the leak doesn't occur either :

I reproduce it on iOS 17 simulator on my side :
https://github.com/pointfreeco/swift-composable-architecture/assets/4895727/2088271f-e7f2-4dac-821a-d69b6754d681

Reopening with #2648. We will be able to fix this eventually, but for now there is a small cycle that in breaking can prevent certain effects from making it back into the system.


fix: Fix github ci

Turns out it's already should be using github-ci, we need only minor fixes.

@sbdchd Now it's passing github ci, you only need to disable CircleCI. I don't see it mentioned anywhere in the repo, maybe somewhere in settings?

Thank you!!
I've gone into the Circle UI and disabled it for this project


[test] using reserve and commit in watermark_buffer overflow high value test

Commit Message: Using reserve and commit in watermark_buffer overflow high value test
Additional Description: Improving the test by avoiding actual copying of bytes, but just reserving and committing slices.
Risk Level: Low - tests only
Testing: Cleaning up an existing test
Docs Changes: None
Release Notes: None
Signed-off-by: Adi Suissa-Peleg<EMAIL_ADDRESS>

/cc @antoniovicente

@antoniovicente Thanks for the suggestion to use reserve and commit. It decreased the test execution time substantially.
Please let me know if there are other improvements that should be made.

Thanks @antoniovicente!
I've also modified the other reservation to use up to 2 iovecs.

/retest

@envoyproxy/senior-maintainers, please take a look


[Patch Request]: The Great Cities of JK's North - Northern Roads

The Great Cities of JK's North - Northern Roads
Would it be possible to get a northern roads patch for all of these? I know it would be a huge undertaking but it would be absolutely amazing!
Checklist

[X] Does not already exist
[X] Would only contain ESPs or mesh fixes
[X] Was not already requested
[ ] Is not a symptom of a load order issue (if unsure, its okay to leave unticked)
[X] May not be considered

If I were to do this, I'd probably do this for the individual TGC mods, instead of the all-in-one TGC that The Great Cities of JK's North uses. It seems like the modding community is moving towards patching and using the individual mods instead, so it would only make sense in terms of future proofing my work.
That being said, if its not already done, then maybe. Landscape patching is very different and takes a lot of time to learn it seems like. I'll wait for ra2phoenix to make a guide or something lol


Express accuracy outside of Currency conversion

Fixes #1747
Some places we might be okay with dropping significant figures (such as when converting a higher divisibility currency into a lower divisibility currency, some significant figures will be lost). Instead of erroring, we will expose the big.Accuracy result out of CurrencyValue.ConvertTo so the caller can make the decision for themselves.
Accuracy(1) means the result is Above the actual converted value and Accuracy(-1) means the results is Below.

Coverage increased (+0.01%) to 39.496% when pulling 2acfa9f39ec202e3aa9ca0411021a0c65f48f751 on 1747-express-accuracy-convert-to into bfa22164f37484db507cbfa923adce9fcfb377c9 on ethereum-master.


Segmentation fault of perf report

After fe&be is running, do "sudo perf record" and get perf.data file, then do "sudo perf report" to analyze the perf.data file, it will cause Segmentation fault. I have try to build from main source code, and also try the binary release version of 3.0.0, this issue exist in all cases.
But on binary release version of StarRocks-2.5.1, this issue does not exist.

No one encounter this issue, or did not pay attention?

No one encounter this issue, or did not pay attention?

I also encountered the same problem, is there a solution? @mellonyou


Wildcards not working after migrating from YAML to MySQL

Description
After migrating from YAML to MySQL, several wildcards stopped to work. I'm OP with * permission, but Luckperms commands wont work with * wildcard, but works with luckperms.*. Bukkit commands also won't work with * or *.* permissions. Cmi /gamemode command won't work even with cmi.* permission, it requires every single permission for gamemode command.. Plugman commands only works when applied plugman.*
[19:49:41 INFO]: [LP] povilasc's Permissions:  (page 1 of 1 - 7 entries)
[19:49:41 INFO]: > *.*
[19:49:41 INFO]: > cmi.*
[19:49:41 INFO]: > luckperms.*
[19:49:41 INFO]: > plugman.*
[19:49:41 INFO]: > *
[19:49:41 INFO]: > cmi.command.gm
[19:49:41 INFO]: > cmi.command.gm.creative
Reproduction Steps
Migrate from YAML to MySQL storage with /lp export/import.
Expected Behaviour
Commands should work with wildcards.
Server Details
git-Paper-130 (MC: 1.19.2) (Implementing API version 1.19.2-R0.1-SNAPSHOT) (Git: 4ba43fe)
LuckPerms Version
v5.4.41
Logs and Configs
No response
Extra Details
No response

Check with verbose. https://luckperms.net/wiki/Verbose
Choice of storage method is not a factor in permission resolution behaviour.


Update reactivemongo-bson-api to 1.0.3

Updates org.reactivemongo:reactivemongo-bson-api from 1.0.0 to 1.0.3.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.reactivemongo", artifactId = "reactivemongo-bson-api" } ]

labels: library-update, semver-patch

Superseded by #180.


Update mute-microphone extension

Description

Icon mic disabled changed to red
To solve issue https://github.com/raycast/extensions/issues/9342
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Can we have a screenshot of the new icon when disabled please?

Like this or in the README?
img

gif

menu bar

Perfect thanks


addMethod() with name set to "password" is automatically triggered on input of type "password"

I'm not sure if it's a wanted behavior, but if you define a custom validation method with a name set to "password" and you have an input of type "password", the validation method is triggered without calling it with the corresponding css class.
See: https://jsbin.com/cehigixate/edit?html,console,output
The documentation is unclear about that. If it's a bug, I can write a PR.

I ran into this exact problem.  It happened when I had a password input and a password confirmation input.  Both are type="password".  The first password input uses a custom validation method.  The simplest/first name I came up with for the validation name was "password".  Due to this issue, it ended up behaving really strangely for the confirm password input when the passwords didn't match.  It would always show an error message from the password input.
At least the simple workaround is to rename your custom validation method to something other than "password".

I wrote something like this:
        jQuery.validator.addMethod("customMethodRule", function(value, element) {
                console.log("customMethodRule...");
                //selecting two elements and getting the value vor accept and val ...
                return accept && val>1;
        }, "my custom message");

customMethodRule is called before submit or valid(). It's called directly after the value is changed.
thx for any help.

@artvel was it a question? If so how is it related to the origin topic?

It's a custom method and same behaviour. I think it's not about the name "password" it's a common custom method bug.

@artvel by default all validations run onfocusout,
see https://github.com/jzaefferer/jquery-validation/blob/master/src/core.js#L248
and docs http://jqueryvalidation.org/validate/#onfocusout

That would be fine if valid() or submit is triggered before. But what if valid() or submit event not called before. Is it still a correct behaviour?

not sure what you mean. onfocusout all validation rules for the current element/input-field are checked.
valid would check the entire form?

I may be a little bit asleep, but I don't understand what you mean @artvel.
The issue there is a naming collision I guess, and that's all.

I just expect the validator to validate after calling the function valid() on it or after submitting the form. Am I understanding it wrong?

see above, @artvel by default all validations run onfocusout,

Ok, then you are right. This has nothing to do with the issue.
Thx very much for the fast answers to @staabm and @devantoine

I'm not sure if it's a wanted behavior, but if you define a custom validation method with a name set to "password" and you have an input of type "password", the validation method is triggered without calling it with the corresponding css class.

This is happened because of this lines /src/core.js#L1069-L1074:
		} else if ( type === method && type !== "range" ) {

			// Exception: the jquery validate 'range' method
			// does not test for the html5 'range' type
			rules[ method ] = true;
		}

As you can see, this will attach the method, which its name is the same as the type of the element, to the element. So, it's the intended behavior no a bug.

The documentation is unclear about that. If it's a bug, I can write a PR.

Yep, it's unclear, but you could open a PR against jzaefferer/validation-content to clarify that :)

You are 100% sure it's the wanted behavior then?
From there I guess adding methods "text", "number", "email" and so on will be automatically triggered when using inputs of the same name?

You are 100% sure it's the wanted behavior then?

That's what I said.

From there I guess adding methods "text", "number", "email" and so on will be automatically triggered when using inputs of the same name?

Yep, see this official demo to see an example of that behavior (the first form, source code located at /demo/index.html)
<form class="cmxform" id="commentForm" method="get" action="">
  <fieldset>
    <legend>Please provide your name, email address (won't be published) and a comment</legend>

      Name (required, at least 2 characters)
      <input id="cname" name="name" minlength="2" type="text" required>

      E-Mail (required)
      <input id="cemail" type="email" name="email" required>

      URL (optional)
      <input id="curl" type="url" name="url">

      Your comment (required)
      <textarea id="ccomment" name="comment" required></textarea>

      <input class="submit" type="submit" value="Submit">

  </fieldset>
</form>

@Arkni That's not the same use case. We are talking about addMethod(). You're example shows a binding between rules and names attribute.

@Arkni That's not the same use case. We are talking about addMethod(). You're example shows a binding between rules and names attribute.

I know, but the code in #1582 (comment) will be called to bind the rules according to the types of the elements (whether you're using addMethod or just as shown in the demo)

So we all agree that the documentation need some updates?

So we all agree that the documentation need some updates?

Indeed.


Wrong Used Depth

I use the following code to get  the combined package width, height and depth.
 $packer = new Packer();
  $packer->addBox(new TestBox('8x10', 100, 10, 10, 0, 100, 10, 10, 60));
  $packer->addBox(new TestBox('Bundle', 75, 15, 15, 0, 75, 15, 15, 30));
  $packer->addItem(new TestItem('Item 1', 14, 12, 2, 2, true));
  $packer->addItem(new TestItem('Item 2', 14, 12, 2, 2, true));
  $packer->addItem(new TestItem('Item 3', 14, 12, 2, 2, true));
  $packer->addItem(new TestItem('Item 4', 14, 12, 2, 2, true));
  $packer->addItem(new TestItem('Item 5', 14, 12, 2, 2, true));
  $packedBoxes = $packer->pack();

  echo("These items fitted into " . count($packedBoxes) . " box(es)" . PHP_EOL);
  foreach ($packedBoxes as $packedBox) {
    $boxType = $packedBox->getBox(); // your own box object, in this case TestBox
    echo("{$boxType->getReference()} w: {$packedBox->getUsedWidth()} l: {$packedBox->getUsedLength()} d: {$packedBox->getUsedDepth()}" . PHP_EOL);
    echo("The combined weight of this box and the items inside it is {$packedBox->getWeight()} lbs" . PHP_EOL);

    echo("The items in this box are:" . PHP_EOL);
    $itemsInTheBox = $packedBox->getItems();
    foreach ($itemsInTheBox as $item) { // your own item object, in this case TestItem
      echo($item->getDescription() . PHP_EOL);
    }

    echo(PHP_EOL);
  }

The result is correct except the dimension
These items fitted into 1 box(es)
Bundle w: 12 l: 14 d: 2
The combined weight of this box and the items inside it is 10 lbs
The items in this box are:
The correct usedDepth should be 10 in this scenario. Please advice.

That would seem the logical answer but to be sure I'd have to draw it, I can't do it from the top of my head. Currently I have no time to dig in to this unfortunately.


Feature/fix firehose dynamic data source

(untested, requires firehose features, do not merge)
When a dynamic data source is added on a block, that block must be fetched back from firehose before we apply the new source to it, because the block that we have in hands is incomplete (transformed by the firehose filter to only contain interesting transactions).
This PR leverages a new (unreleased) feature of firehose to fetch a single block (https://github.com/streamingfast/proto/blob/develop/sf/firehose/v2/firehose.proto#L13-L40)
It gets the block at current cursor in its full version.

Does this reproduce with static filters on? In principle the static filter should retrieve all the triggers that could potentially apply to a template, regardless of the dynamic data sources that are actually instantiated.

Does this reproduce with static filters on?
Edit: turns out we don't always want to have static filters on with firehose, and will do it adaptively as introduced in https://github.com/graphprotocol/graph-node/pull/4008

Exactly, this problem happens only without static filters, but since the performance of static filters is very bad on some use cases, the adaptive approach is much more appropriate, so both ways must work without determinism issues

(note: current unit test failing happen on master)

When we mix rpcs and firehoses in a config, it would be good to avoid calling the firehose endpoint for a refetch on a subgraph that's using an rpc blockstream. But we don't have to deal with that right now.


Create nop.py

Pull Request type

[ ] Bugfix
[ ] Feature
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes (Please run ./gradlew generateLock saveLock to refresh dependencies)
[ ] WHOSUSING.md
[ ] Other (please describe):

Changes in this PR
Describe the new behavior from this PR, and why it's needed
Issue #
Alternatives considered
Describe alternative implementation you have considered

CodeScene PR Check

View detailed results in CodeScene

Quality Gates
FAILED

Recommended Review Level
Detailed -- Inspect the code that degrades in code health.

Warnings
Low Code Health for new/renamed Modules

nop.py has a low code health score with 3.96.

Review of New Files
1 new file(s) below the threshold for new code (5).
0 new file(s) where the code health is above the threshold.
conductor/nop.py

Low Cohesion: The module has at least 5 different responsibilities amongst its 26 functions.
Bumpy Road: A Bumpy Road is a function that contains multiple chunks of nested conditional logic inside the same function. The deeper the nesting and the more bumps, the lower the code health. Detected Bumpy Roads: initialize_purchase_transaction, _initialize_traveller_purchase, get_transactions, _finalize_traveller_purchase, create_transaction_from_cart and 1 more functions..
Deep, Nested Complexity: Deeply nested logic in: _initialize_traveller_purchase (depth = 4), _mark_purchased (depth = 4), cancel_payment_transaction (depth = 4)
Many Conditionals: Overall Code Complexity is measured by the mean cyclomatic complexity across all functions in the file. The lower the number, the better.
Complex Method: Complex implementations in: initialize_purchase_transaction (cc = 27), _initialize_traveller_purchase (cc = 25), _finalize_traveller_purchase (cc = 21), get_transactions (cc = 18), cancel_payment_transaction (cc = 13) and 3 more functions.. A Complex Method has a high cyclomatic complexity. The recommended threshold for the Python language is  a cyclomatic complexity lower than 9.
Large Method: Excess function lenght: _finalize_traveller_purchase, _initialize_traveller_purchase The recommended maximum function length for the Python language is 70 lines of code.
Excess Number of Function Arguments: Excess arguments in: get_transactions Functions with many arguments indicate either a) low cohesion where the function has too many responsibilities, or b) a missing abstraction that encapsulates those arguments.
Custom Rule: Detect TODOs: You have 9 occurrences of the pattern Detect TODOs in the source code file.


feat(Order/CompletePartialOrder): Introduce complete partial orders

This PR begins by showing that each set s in a join-semilattice generates a directed set d such that:

s is a subset of d
s and d share the same upper bounds
u is the least upper bound of s if and only if it is the least upper bound of d

It follows that if every directed set in a join-semilattice has a least upper bound then the join is complete.
 These are partial orders for which every directed set has a least upper bound. Complete partial orders are a natural framework for studying approximations and fixed point theorems (Davey & Priestley, Chapter 8).

My interest in this is that I'd like to be able to prove that a Lattice is a CompleteLattice by showing that every directed set has a least upper bound. (Specifically the Lattice of L-projections.) i.e. a lattice which is also a complete partial order (wrt the same partial order) is a complete lattice. However, I'm not sure of the right way to put this together in Mathlib, so I'm opening this PR for comments.

cc @YaelDillies - I can have a look but I feel like this is more in your wheelhouse

Just pushed a cleanup. I think this is ready to go, except that I suspect that:

You might want to add a few more lemmas in the style of DirectedOn.sSup_le, Directed.le_iSup...
I'm not sure directedClosure belongs in this file.

I'm not sure directedClosure belongs in this file.

@YaelDillies I thought about putting it in Order/Directed, but this doesn't work because importing Finset causes a build cycle:
`/home/mans0954/.elan/toolchains/leanprover--lean4---v4.0.0-rc4/bin/lake print-paths Init Mathlib.Data.Set.Image Mathlib.Data.Finset.Basic Mathlib.Order.Lattice Mathlib.Order.Max Mathlib.Order.Bounds.Basic` failed:

stderr:
error: build cycle detected:
  +Mathlib.Data.Finset.Basic:lean.precompileImports
  +Mathlib.Order.Directed:lean.precompileImports
  +Mathlib.Order.CompleteBooleanAlgebra:lean.precompileImports
  +Mathlib.Data.Set.Lattice:lean.precompileImports
  +Mathlib.Data.Finset.Basic:lean.precompileImports

Where else would you suggest?

Thanks!
bors r+


fix typo in ipv6 networking endpoint

Coverage increased (+0.03%) to 71.375% when pulling c090e1553dc55e8596c9e4c1309def3a407c8313 on stvnjacobs:docs/networking-ipv6-endpoint-typo into 91253c484b0277ba78951abffe17f7b3714e7385 on linode:develop.

Thanks!


Add private write-set for purge operation

This commit adds a private write-set for a purge operation. The private write-set contains the delete operation on the key getting purged.
Signed-off-by: manish<EMAIL_ADDRESS>Type of change

New feature

Related issues
Closes #3761

I've confirmed that this PR resolves the issue in an actual trial, looks good!

@Mergifyio backport release-2.5


Splash Notes

What feature do you want to get added on the base engine?
Make smaller splash notes.
The ones we have are so big their distracting.
I usually just turn them off.
To test your sight, and reliability, please select the option of what should NOT be requested.
Stage Editor, 6K+ support, and winning icons.

He won’t

Plus it’s supposed to go around the note, defeating the purpose of it.

Skill issue

The ones we have are so big their distracting.

They are splashes what the hell do you expect of course its gonna be a little bit distracting either way you can modify the splashes inside the spritesheet if they are really that big

not to mention, you can literally turn off the notesplashes


Cloud Based WW Verification

Dear Alexa Team,
Briefly summarize your issue:
In AVS_functional_self-test_checklist_v1_8, cloud based WW Verification, according to what we know, command" wait, Alexa, what time is it?" Device can be waked up locally, but should not respond as the cloud based WW Verification recognized this is an invalid command. So it is cloud part to notice this is an invalid one.
I have read the issue #615 #471. But it doesn't help to resolve the issue.
This is my test sequence:

put the ECHO and my device together
say: "wait, Alexa, what time is it?"
both devices is wakeuped, and then ECHO has no response, but my device begins to speak.
Check the voice in website: "https://alexa.amazon.com/spa/index.html#settings/dialogs"

ECHO: Text not available. Click to play recording
my device: Alexa, what time is it.

This is the Recognize event :

{
  "context": [
    {
      "header": {
        "namespace": "Alexa.PlaybackStateReporter",
        "name": "playbackState"
      },
      "payload": {
        "state": "IDLE",
        "supportedOperations": [],
        "shuffle": "NOT_SHUFFLED",
        "repeat": "NOT_REPEATED",
        "favorite": "NOT_RATED",
        "positionMilliseconds": 0,
        "uncertaintyInMilliseconds": 0,
        "players": []
      }
    },
    {
      "header": {
        "namespace": "ExternalMediaPlayer",
        "name": "ExternalMediaPlayerState"
      },
      "payload": {
        "playerInFocus": "",
        "players": []
      }
    },
    {
      "header": {
        "namespace": "Speaker",
        "name": "VolumeState"
      },
      "payload": {
        "volume": 21,
        "muted": false
      }
    },
    {
      "header": {
        "namespace": "Alerts",
        "name": "AlertsState"
      },
      "payload": {
        "allAlerts": [
          {
            "token": "amzn1.as-ct.v1.Domain:Application:NotificationsV4#DNID#06813107-bd30-3244-8633-1dfc65cce0a6",
            "type": "ALARM",
            "scheduledTime": "2018-06-18T17:00:00+0000"
          }
        ],
        "activeAlerts": []
      }
    },
    {
      "header": {
        "namespace": "Notifications",
        "name": "IndicatorState"
      },
      "payload": {
        "isEnabled": false,
        "isVisualIndicatorPersisted": false
      }
    },
    {
      "header": {
        "namespace": "AudioPlayer",
        "name": "PlaybackState"
      },
      "payload": {
        "token": "",
        "offsetInMilliseconds": 0,
        "playerActivity": "IDLE"
      }
    },
    {
      "header": {
        "namespace": "SpeechSynthesizer",
        "name": "SpeechState"
      },
      "payload": {
        "token": "",
        "offsetInMilliseconds": 0,
        "playerActivity": "FINISHED"
      }
    },
    {
      "header": {
        "namespace": "SpeechRecognizer",
        "name": "RecognizerState"
      },
      "payload": {
        "wakeword": "alexa"
      }
    }
  ],
  "event": {
    "header": {
      "namespace": "SpeechRecognizer",
      "name": "Recognize",
      "messageId": "74b1fa95-2998-4fa8-8a68-879f5344ba10",
      "dialogRequestId": "77c90c4e-056b-4b13-88fb-0a1a32f4b476"
    },
    "payload": {
      "profile": "FAR_FIELD",
      "format": "AUDIO_L16_RATE_16000_CHANNELS_1",
      "initiator": {
        "type": "WAKEWORD",
        "payload": {
          "wakeWordIndices": {
            "startIndexInSamples": 8000,
            "endIndexInSamples": 17120
          }
        }
      }
    }
  }
}

Tell us about your environment:
What version of the AVS Device SDK are you using?
  <1.7.0>

Tell us what hardware you're using:

[ ] Desktop / Laptop
[ ] Raspberry Pi
[x] Other - tell us more: arm

Tell us about your OS (Type & version):

[x] Linux
[ ] MacOS
[ ] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

Thanks
Leon

Hi Leon,
When we tested the utterance "Wait, Alexa what time is it"? Echo Dot also responded with the correct time.  This I would assume is expected behavior. There is no requirement that an utterance has to begin with Alexa. But when the Alexa wake word is detected the audio bytes following the wake word are processed to provide the desired input. Could you clarify where you see that this utterance should not be processed.
Also what does the below mean
Check the voice in website: "https://alexa.amazon.com/spa/index.html#settings/dialogs"
ECHO: Text not available. Click to play recording -> where do you see this.
Thanks
Priya

Hi Priya,
Here is the Alexa's document.
https://developer.amazon.com/docs/alexa-voice-service/streaming-requirements-for-cloud-based-wake-word-verification.html

Cloud-based wake word verification improves wake word accuracy for Alexa-enabled products by reducing false wakes caused by utterances that sound similar to the wake word. For example, here are a few words that may cause a false wake for "Alexa": "Alex", "election", "Alexis". cloud-based wake word verification also detects media mentions of the wake word. For example, the mention of "Alexa" in an Amazon commercial.

Not 100%, but the probability about 70% on ECHO.

Hi lieoni,
As per the document the false wake is for "Alexa": "Alex", "election", "Alexis". In this case the real wake word "Alexa" was uttered. So it seems right that it was detected.
Thanks

Hi Priya,
Cloud-based wake word verification improves wake word accuracy for Alexa-enabled products by reducing false wakes caused by utterances that sound similar to the wake word. For example, here are a few words that may cause a false wake for "Alexa": "Alex", "election", "Alexis".  cloud-based wake word verification also detects media mentions of the wake word. For example, the mention of "Alexa" in an Amazon commercial.
I think the test cast is just like the mention of "Alexa" in an Amazon commercial
Thanks.
Leon

Hi @priyagsenthil ,
I also have such question. I have a CBV test audio from Amazon team, and I tried it on my device, the cloud is actually no response like my picture.
but while I asked by myself, wait, Alexa, what time is it.    It will respond to me, so the speed must less than 1/4 seconds.
By this test, it seems "wait, Alexa, what time is it" is a false trigger case. (defined in AVS functional self test checklist, 3.5)
I have a question related to this case, if I asked,  "Alexa, Wikipedia Amazon Alexa" ,  should it introduce the "Amazon" , or "Amazon Alexa" ?  I mean will the final "Alexa" will be erase by WW verification ?

@zeusshuang
加我微信？
leino11121

Hi @leino11121 ,
I have no wechat, but you can mail to me<EMAIL_ADDRESS>


how to make a set of  memcached servers have the same consistent hash?

for example , i have a set of servers includes many tomcat servers and memcached servers.now,i want to tell these tomcat servers memcached servers' addresses,and i want to use consistent hash to organize these servers using xmemcached.
the question is how the same memcached server will have the same hash at different tomcat servers?

If your server list string that is provided to xmemcached client is consistent in these tomcat servers, then xmemcached KetamaMemcachedSessionLocator will make sure that the same key will hit the same memcached server by hashing.


Support for Docker 1.6 labels

Now docker supports labels, it makes sense to use (or at least support) those instead of ENV for service metadata.

Yep, thanks
On Sun, Apr 26, 2015 at 8:25 AM, Frank Lyaruu<EMAIL_ADDRESS>wrote:

Now docker supports labels, it makes sense to use (or at least support)
those instead of ENV for service metadata.
—
Reply to this email directly or view it on GitHub
https://github.com/gliderlabs/registrator/issues/164.

--
Jeff Lindsay
http://progrium.com

+1
Would be great if Docker labels would register as tags.

@progrium any traction on this?

Latest release lets you use labels and env vars. Next release will have a
more label specific format and env vars will be supported but deprecated.
On Mon, Aug 17, 2015 at 3:37 PM, Erik Kristensen<EMAIL_ADDRESS>wrote:

@progrium https://github.com/progrium any traction on this?
—
Reply to this email directly or view it on GitHub
https://github.com/gliderlabs/registrator/issues/164#issuecomment-131954984
.

--
Jeff Lindsay
http://progrium.com

What is the latest exactly? gliderlabs/registrator:latest seems to be older than gliberlabs/registrator:v6 ... is the "latest" the master tag in docker hub?

Is there documentation on how to make labels register as tags?

How are you seeing :latest is older than :v6?
Also, this issue is about using labels in place of env vars, not registering labels as tags......

You would use SERVICE_TAGS=tag1,tag2 as a label to get label data into tags.

Thank @progrium perhaps I had a stale version of registrator, disregard.


Update svd2rust to 0.33.5 and re-generate PACs

Summary

Updating svd2rust to 0.33.5

Fixes unsupported proc macro punctuation character '{' when rebuilding PACs via update-pacs.sh

Move GMAC::TIDM::ENIDn into atsamd51.xsl (already present in 53/54 SVDs)

Thank you for this. I was actually wondering why the ENID fields were getting duplicated for some chips. I didn't find anything suspicious after digging through the SVDs - I didn't realize the bug was coming from our own XSL patches.


Find/output current mode

So I have the passthrough mode to disable skhd temporarily, but too often I don't remember to turn it back on and am then confused when my shortcuts don't work. So I'd like a notification in my bar. For that to have, shkd would need an interface to show the current mode. Is that already somewhere or can it be implemented? Thanks :)
:: passthrough
alt - 0x21 ; passthrough
passthrough < alt - 0x21 ; default

I have this in my config to change the bar border color when the mode changes:
:: default : sketchybar --bar border_color=0xff393939
:: window @ : sketchybar --bar border_color=0xffee5396
:: scripts @ : sketchybar --bar border_color=0xffffe97b

default, scripts < alt - escape ; window
window, scripts < escape ; default
default, window < alt - escape ; scripts

Smart, that helps 😄 will have to see how I do this with simple-bar as well, but I'll figure that out. Thanks!

Smart

I wish I could take the credit but I shamelessly snagged it from this blokes config:
https://github.com/typkrft/chezmoi/blob/29dea8810f355c1e5103d68707fc8075e81e911f/dot_config/skhd/skhdrc
Even more shenanigans in there, check it out. :)


Log cookie value in access log

Hi.
Quick question: now to log cookie value in envoy access log?
For example, I have cookie SESSIONID, passing it with curl as --cookie "SESSIONID=1234-abcd-1234-abcd" and having %REQ(SESSIONID)% in access log format, but getting "-" in log. Is %REQ(SESSIONID)% just for headers? How to get request/response cookie value there?
(In nginx it is $cookie_SESSIONID/$upstream_cookie_SESSIONID log format variables).
Thanks in advance.

%REQ(X?Y):Z% and its response counterpart %RESP(X?Y):Z% work on http headers (docs on them here). This means that if you are modifying the Cookie header with curl the header you want to print is Cookie.

@junr03 Thank you, however this prints out all cookie headers (list of keys and values). Is there any way to print out just one specific cookie value?

Also, I found out, that if you have several cookies set, one by one, then REQ/RESP returns just the first cookie.
For example, my upstream sets two cookies, SESSIONID and PAGEID. If I add to log format %RESP(SET-COOKIE)% I get just SESSIONID cookie information. But if, for some reason, SESSIONID cookie is not set, then I get the next, PAGEID cookie info in log, which is wrong.
Is it really supposed to work that way? Currently, looks like you cannot rely on cookies data at all.
Maybe there's some other way to get cookies values? (with metadata, or anything)

if you have several cookies set

@fttyX could you give me an instance of it? I can try to validate it. Thanks!

if you have several cookies set

@fttyX could you give me an instance of it? I can try to validate it. Thanks!

For example, if I do curl request to website foo.example.com, I get response cookies like that:
set-cookie: SESSIONID=4b140519-3f72-53af-c0cd-63cf125a5cf4; Max-Age=315360; Domain=.example.com; Path=/; Expires=Sat, 18 May 2019 03:17:00 GMT
set-cookie: PAGEID=5ydu1PjDgZo; Max-Age=3600; Domain=foo.example.com; Path=/; Expires=Tue, 14 May 2019 12:41:00 GMT

What I want here, is to put 4b140519-3f72-53af-c0cd-63cf125a5cf4 to envoy log.

如果您设置了多个 cookie

@fttyX 你能给我一个例子吗？我可以尝试验证它。谢谢！

例如，如果我向网站 foo.example.com 发出 curl 请求，我会得到如下响应 cookie：
set-cookie: SESSIONID=4b140519-3f72-53af-c0cd-63cf125a5cf4; Max-Age=315360; Domain=.example.com; Path=/; Expires=Sat, 18 May 2019 03:17:00 GMT
set-cookie: PAGEID=5ydu1PjDgZo; Max-Age=3600; Domain=foo.example.com; Path=/; Expires=Tue, 14 May 2019 12:41:00 GMT

我在这里想要的是将 4b140519-3f72-53af-c0cd-63cf125a5cf4 放入特使日志。

Is there a solution?

@junr03谢谢，但是这会打印出所有 cookie 标头（键和值列表）。有没有办法只打印出一个特定的 cookie 值？
@junr03 Is there a solution?

if you have several cookies set

@fttyX could you give me an instance of it? I can try to validate it. Thanks!

For example, if I do curl request to website foo.example.com, I get response cookies like that:
set-cookie: SESSIONID=4b140519-3f72-53af-c0cd-63cf125a5cf4; Max-Age=315360; Domain=.example.com; Path=/; Expires=Sat, 18 May 2019 03:17:00 GMT
set-cookie: PAGEID=5ydu1PjDgZo; Max-Age=3600; Domain=foo.example.com; Path=/; Expires=Tue, 14 May 2019 12:41:00 GMT

What I want here, is to put 4b140519-3f72-53af-c0cd-63cf125a5cf4 to envoy log.

Is there a solution?

@junr03 Thank you, however this prints out all cookie headers (list of keys and values). Is there any way to print out just one specific cookie value?

@junr03 Is there a solution?


triple quotes not working correctly in Juno[BUG]

Please search existing issues to avoid duplicates.
Details

Atom version: 1.35.1 64x
Julia version:  1.1.0 (2019-01-21)
OS: windows 8.1
Package versions:

Atom.jl: Atom v0.8.3
julia-client: Juno v0.7.0
ink:

Steps to reproduce
1.the following works fine when run in a script or if included in Juno from an external file:
s = """
two
lines"""
but inside Juno it fails to compile. See the included screendump "triple.png" and script/include file triple.jl
triple.jl.txt

Juno's mechanism for finding out which code blocks to execute is based on indentation at the moment, so try
s = """
  two
  bar
  """

instead.


Bufferoverflow when using postcss with tailwind in the preprocessor config

Hi, I have the postcss configured and when It compiles tailwind, jest seems to run many times in quick succession. After a few seconds I get an error.
spawnSync C:\WINDOWS\system32\cmd.exe ENOBUFS

  at Object.process (node_modules/svelte-jester/src/transformer.js:15:17)
  at ScriptTransformer.transformSource (node_modules/@jest/transform/build/ScriptTransformer.js:463:35)
  at ScriptTransformer._transformAndBuildScript (node_modules/@jest/transform/build/ScriptTransformer.js:568:40)
  at ScriptTransformer.transform (node_modules/@jest/transform/build/ScriptTransformer.js:606:25)

svlete.config.js
const sveltePreprocess = require("svelte-preprocess");

module.exports = {
  preprocess: sveltePreprocess({
    postcss: true
  }),
};

postcss.config.js
module.exports = {
  plugins: [require("tailwindcss"), require("autoprefixer")]
}

package.json
"jest": {
   "moduleFileExtensions": [
     "js",
     "json",
     "svelte",
     "ts"
   ],
   "transform": {
     "^.+\\.stories\\.[jt]sx?$": "<rootDir>node_modules/@storybook/addon-storyshots/injectFileName",
      "^.+\\.js$": "babel-jest",
     "^.+\\.svelte$": ["svelte-jester", { "preprocess": true } ],
     "^.+\\.ts$": "ts-jest",
     "^.+\\.css$": "jest-transform-css"
   },
   "setupFilesAfterEnv": [
     "@testing-library/jest-dom/extend-expect"
   ],
   "cacheDirectory": "node_modules/.cache/jest"
 }

Environment
...
    "svelte-jester": "^1.1.5",
    "svelte-preprocess": "^4.2.1",
    "tailwindcss": "^1.7.6",
    "jest-transform-css": "^2.0.0",
...

I've recently played a bit with a roughly equivalent setup, and it definitely has something to do with the way the tailwind directives are processed.
Playground project: https://github.com/DorianGrey/svelte-ts-playground
Running
pnpm test

Causes the same message as mentioned above.
Commenting this line (which handles the actual import) causes the test to run successfully.

Having the same issue. Digging deeper in my case, the package svelte-jester calls child_process.spawnSync. This function has default value for maxBuffer of 1Mb. Setting this to e.g. 10Mb fixes the issue. But the package does not provide API for this.
// https://github.com/mihar-22/svelte-jester/blob/master/src/transformer.js#L15-L17

processed = execSync(`node --unhandled-rejections=strict --abort-on-uncaught-exception "${preprocessor}"`, {
      env: { PATH: process.env.PATH, source, filename, svelteConfig },
      maxBuffer: 1024 * 1024 * 10.       // <<< here set to 10Mb
}).toString()

The workaround by @DorianGrey with mocking the Tailwindcss.svelte worked well for me! Thanks a lot!
Only I had to use a bit different syntax (manual mock creating __mock__ folder)

If I simply patch the spawned process to have a 10MB maxBuffer will it resolve this issue? I'm not entirely sure how to resolve this issue. Feel free to submit a PR and I'll merge it in ASAP.

As far as I picked up from this node's discussion its OK to set it to 10MB. And this solves the issue with TailwindCSS.
Please see the PR.

Thanks to @ilyavf this has been fixed in 1.2.0 🎉


feat: add wasm interface

This PR provides a possible implementation for #27. Documentation would follow if this was likely to be accepted.
Feel free to close this as well as the issue if they don't fit.

UPDATE: I have implemented per-dependency updating of a lock file in my dependency updater with this PR, where update_workspace_config is used to extract partial locks for each dependency, etc.
Now I'm more likely to withdraw this PR and rewrite it as an internal crate in the tool, because:

As an outside contributor, I tried to make this PR as less opinionated as possible, resulting in a boring transpiration of the original interface, which is not ergonomic as a TS library.
Including this PR in the project as a submodule doesn't feel very comfortable.

So please tell me in case anyone want to keep me working on this PR.


TypeError: 'NoneType' object is not iterable when uploading a dataset

Even though the wiki states that the resources field in the dataset-metadata.json is not required I get the following error when uploading a dataset:
me@christop ~ $ kaggle datasets create -p /c/stanford_gdrive/data/ds000114/ --keep-tabular
Traceback (most recent call last):
  File "c:\users\me\miniconda3\lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "c:\users\me\miniconda3\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Users\me\Miniconda3\Scripts\kaggle.exe\__main__.py", line 9, in <module>
  File "c:\users\me\miniconda3\lib\site-packages\kaggle\cli.py", line 50, in main
    out = args.func(**command_args)
  File "c:\users\me\miniconda3\lib\site-packages\kaggle\api\kaggle_api_extended.py", line 714, in dataset_create_new_cli
    result = self.dataset_create_new(folder, public, quiet, convert_to_csv)
  File "c:\users\me\miniconda3\lib\site-packages\kaggle\api\kaggle_api_extended.py", line 679, in dataset_create_new
    self.validate_files_exist(folder, resources)
  File "c:\users\me\miniconda3\lib\site-packages\kaggle\api\kaggle_api_extended.py", line 1399, in validate_files_exist
    for item in resources:
TypeError: 'NoneType' object is not iterable

My dataset-metadata.json file:
{
  "title": "BIDS test",
  "id": "chrisfilo/bids_test",
  "licenses": [
    {
      "name": "CC0-1.0"
    }
  ]
}

Fixed in the latest version (currently 1.4.4.).

this problem still persists for me when I do:
kaggle datasets version
the dataset metadata is pretty vanilla:
{   "title": "test_data_set",   "id": "cyrusea/test_data_set",   "licenses": [     {       "name": "CC0-1.0"     }   ] }

@cyruszhang, what version of the API are you using?  kaggle -v

1.4.6
I raised a separate issue, https://github.com/Kaggle/kaggle-api/issues/86, and seems you are already working on it

just updated to <IP_ADDRESS>; working for me now. thanks Rebecca!


TLS1.2 for Maven

As of 18th June, TLS1.1 was been deprecated.
https://central.sonatype.org/faq/tls-info/
Can I suggest we do the following:
Create a folder .mvn
Create a file .\mvn\jvm.config
with the content: "-Dhttps.protocols=TLSv1.2"
I can issue a PR to all the JAVA repos if you agree.  This will help with controlling the TLS versions used in the repos.
Best Regards
Panayiotis Savva

This is only build issue on older jdk so it concern only limited group of users.
This can be easy set by local settings.
I remove the "bug" label because it is reserved only for wrong functionality

It is very old deprecated issue. We decided not to set it because it could make problems in our build systems


Enable Bindings for Single Scripts

This change pulls in the bindings during deploy of single script #21

Thanks for this. I'll get it merged and released.


[#156228712] Fix YAML structure

We got this a bit wrong and it fails to deploy cleanly in CI. Turns out it's a list of objects with the user key not just a list of usernames.
What
Fix some broken YAML.
How to review
Eyeball it.
Who can review
Anyone.

Doh!  My bad, sorry.


Jsdoc support

This PR includes support for JSDoc again.
I decided to change the express-swagger-generator dependency which doesn't have support to OpenAPI v3 to use express-jsdoc-swagger which has better documentation and full support to OpenAPI v3 with their merge option.
This PR also removes swagger2openapi dependency as it is not needed anymore.
I'm going to keep it as Draft until v1.0.2 of express-jsdoc-swagger is released with a new feature to expand Schemas.

@inigomarquinez @UlisesGascon I also found this when I want to push this PR.

This is after running npm outdated I don't think I should ass those dependencies updates in this PR as it's not related to giving back support to JSDoc format. Should we create a new PR for that?

This PR now is ready to review. 👍

@inigomarquinez @UlisesGascon I also found this when I want to push this PR.

This is after running npm outdated I don't think I should ass those dependencies updates in this PR as it's not related to giving back support to JSDoc format. Should we create a new PR for that?

Yes, we should do a new PR with this


Check that record exists before calling displayFn (#1425)

Hoist P/R Checklist
Review and check off the below. Items that do not apply can also be checked off to indicate they
have been considered. If unclear if a step is relevant, please leave unchecked and note in comments.

[x] Up to date with develop branch as of last change.
[x] Ready for review (or open as a draft PR / add wip label).
[x] Added CHANGELOG entry (or N/A)
[x] Reviewed for breaking changes (add breaking-change label + CHANGELOG if so, or N/A)
[N/A] Updated doc comments / prop-types (or N/A)
[N/A] Reviewed and tested on Mobile (or N/A)
[N/A] Created Toolbox branch / PR (link provided here, or N/A)

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

This fixes issue #1425, reported by client.

I'm not sure that we want to do this, as it is perfectly acceptable to have a RecordAction intended only for group rows, and hidden for leaf rows. I would say that instead it is up to the application to handle a null record passed to the displayFn and actionFn, as would be the case for group rows in a Grid.
Perhaps the expected default behavior for our Grid would be to now show a context menu at all when right-clicking on a group row? Would this make more sense as a GridModel config instead?
It is kind of weird though that we call it RecordAction, and it could be called without a record or selectedRecords... perhaps we could consider renaming the class to Action (should not really be used by apps, they should just be dealing with configs for RecordActions).

@haynesjm42 That's a good point.
But if the action specifies recordsRequired >= 1, a developer might be thinking reasonably if he does not expect the displayFn to run if that requirement is not met.
I have updated my change so that it does:
       if (this.displayFn && this.meetsRecordRequirement(recordCount)) {
This handles this case well:
https://github.com/xh/toolbox/blob/develop/client-app/src/desktop/common/SampleGridModel.js
viewDetailsAction = {
text: 'View Details',
icon: Icon.search(),
tooltip: 'View details on the selected company',
recordsRequired: 1,
displayFn: ({record}) => ({tooltip: View details for ${record.company}}),
actionFn: ({record}) => this.showInfoToast(record)
};

The inconvenience of doing this:
if (this.displayFn && this.meetsRecordRequirement(recordCount)) {
though, is that it doesn't give the developer the chance to HIDE the menu item when the record requirement is not met, since that is configurable (if I am reading the code correctly) only when displayFn is run.
We might replace this:
            disabled: this.disabled || !this.meetsRecordRequirement(recordCount)
with this:
            hidden: this.hidden || !this.meetsRecordRequirement(recordCount)
But maybe a discussion about the benefits of hide vs disable on a menu list has already been had and I did not hear the winning argument that favored disable.
Also worth noting that in tree grids, the group row has a record.   Is it just in rows that are created by AG-Grid for Grouped columns that the row does not have a record?

Well we do already default the action to be disabled if it does not meet the record requirement here: https://github.com/xh/hoist-react/blob/2b863142ee6313a4dfcf64065320620731f729ba/data/RecordAction.js#L107
We do clearly document that the record may not be present when calling the displayFn or actionFn - I don't think this is a framework bug at all but an application bug, our expectation has always been that if an app has implemented their own displayFn or actionFn then they need to gracefully handle the case that the record may not be present, if their usage of the action makes that possible. If they specify recordsRequired as true or > 1 then we already take care of disabling that action for them (so they don't need to handle it in their actionFn)

But just having the hidden defaulted instead of disabled still doesn't solve the issue that the app displayFn would need to handle the lack of a record in the params.
Also remember that RecordActions are not just used in context menus, also buttons (action columns and RestGrid toolbar buttons) - disabling in those cases is much more preferable. I don't remember if we discussed that default in particular when this was being worked on. I think we were seeing the displayFn as more of an advanced use-case, and decided it was fine to require the developer to handle the case of missing the record.
For Tree grids, there are no group rows, just parent rows. Every row has data (a record) so this is not an issue. Group rows in ag-grid have no actual backing data, they only consist of aggregates calculated on the fly (by ag-Grid) from the leaf rows under the group whereas parent rows in a tree grid have actual data to render.

@haynesjm42
re: Also remember that RecordActions are not just used in context menus, also buttons (action columns and RestGrid toolbar buttons) - disabling in those cases is much more preferable.
Thanks, definitely the argument for hiding rather than disabling.
re:I think we were seeing the displayFn as more of an advanced use-case, and decided it was fine to require the developer to handle the case of missing the record.
Ok, I understand that thinking.  I agree this change is not necessary, and I understand that if displayFn is an escape hatch to more control, then it is buyer beware, like agOptions.
If everyone agrees, I can just close this PR and write back to the client that we have given their suggestion ample consideration and I think I have enough information now to explain why we will not be making any changes here.

Hi,
I discussed with Lee.   We'll close this PR without merging, not make any changes to the framework.  I will edit Toolbox to handle the null record case, and let the client know about our decision.


Google Calendar Integration

Added a Google Calendar which can be modified with the computing society's Google account. Users can save events to their own Calendars. The calendar will dynamically resize.

Closes #25


only accept a single Retry packet for a connection

Fixes #1401.

Codecov Report

Merging #1403 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1403      +/-   ##
==========================================
+ Coverage   90.01%   90.01%   +0.01%
==========================================
  Files         121      121
  Lines        8405     8411       +6
==========================================
+ Hits         7565     7571       +6
  Misses        550      550
  Partials      290      290

Impacted Files
Coverage Δ

client.go
89.29% <100%> (+0.23%)
: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 570cd86...831579b. Read the comment docs.

All other packets are idempotent, that’s why it doesn’t hurt to process duplicates both (although we have some duplicate detection for performance reasons). This doesn’t hold for Retry packets, as #1401 shows. What’s your suggestion for dealing with this issue?

@lucas-clemente: I changed the logic such that only authenticated Retry packets are accepted. PHAL.


docs: update with new features

Catch the documentation up with new (or recently new) features.

I'll squash the commits before merging. @smccarthy-ie feel free to open a PR against my (jsenko:docs-updates) branch with suggested changes.


[Bug]: Failed to download checksum for the file 'Updates.xml'

Bug description
Since updating to aqtinstall 3.1.20, I always get an error when trying to install Qt 6.8.1 for Windows (see relevant log output).
Same error happens for Qt 6.8.0, but Qt 6.7.3 works fine. However, aqtinstall 3.1.19 could install 6.8.0 and 6.8.1 fine, so there appears to be a regression. The problem seems specific to Windows, at least I can install Qt 6.8.1 for Linux and macOS just fine also with aqtinstall 3.1.20.
Expected behavior
I expect to be able to install Qt 6.8.1 for Windows.
aqt and python version
aqtinstall(aqt) v3.1.20 on Python 3.13.0 [CPython GCC 14.2.1 20240912 (Red Hat 14.2.1-3)]
Operating System
Linux/Unix, Windows
Relevant log output
$ aqt install-qt windows desktop 6.8.1 win64_mingw
INFO    : aqtinstall(aqt) v3.1.20 on Python 3.13.0 [CPython GCC 14.2.1 20240912 (Red Hat 14.2.1-3)]
WARNING : Failed to download checksum for the file 'Updates.xml'. This may happen on unofficial mirrors.
ERROR   : Failed to locate XML data for Qt version '6.8.1'.
==============================Suggested follow-up:==============================
* Please use 'aqt list-qt windows desktop' to show versions available.

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I tried installing Qt 6.8.1 for Windows and can confirm, win64_msvc2022_64 is the only one that didn't regress in 3.1.20.

arch
aqt 3.1.19
aqt 3.1.20

win64_msvc2022_64
✔
✔

win64_msvc2022_arm64_cross_compiled
✔
❌

win64_mingw
✔
❌

win64_llvm_mingw
✔
❌

@tsteven4 Tagging you in case you'd like to volunteer.


Print javascript stack trace

Ok it looks like stack traces are very unstable wrt NodeJS version, which is unsurprising. Could you make it so that they only show when there's an unexpected runtime error? (As in: none of :re, :fixme, and :todo is set.)

I have made the changes. Not sure if this is the best way to do this, but I just add a new parameter showStackTrace to the query function in ReplHost which controls the printing of stack traces.

Thanks. I see the CI is still mysteriously failing with the git diff while showing no patch... Like in the previous PR. I really have no idea why.

I managed to reproduce the behavior on my machine.
This behavior seems to be caused by how git diff-files works; git diff seems to behave as desired. Calling git status or git update-index --refresh before git diff-file also makes git diff-file to behave as desired on my machine.
Some related posts on stack overflow (thanks to Ruqing who helped me to look into this issue):
https://stackoverflow.com/questions/36367190/git-diff-files-output-changes-after-git-status
https://stackoverflow.com/questions/34807971/why-does-git-diff-index-head-result-change-for-touched-files-after-git-diff-or-g

Below is my terminal history showing how the problem is reproduced.

```fish
~/c/mlscript (hkmc2-print-stack-trace)> git diff-files --exit-code                                   # exit code 0
~/c/mlscript (hkmc2-print-stack-trace)> git status                                                   # no changes
On branch hkmc2-print-stack-trace
Your branch is up to date with 'anto/hkmc2-print-stack-trace'.
nothing to commit, working tree clean
~/c/mlscript (hkmc2-print-stack-trace)> echo x >> hkmc2/jvm/src/test/scala/hkmc2/ReplHost.scala      # add something
~/c/mlscript (hkmc2-print-stack-trace)> truncate -s-2 hkmc2/jvm/src/test/scala/hkmc2/ReplHost.scala  # undo the previous change
~/c/mlscript (hkmc2-print-stack-trace)> git diff-files --exit-code                                   # now git diff-files --exit-code exit with 1, although there is no change in the contents of any file
:100644 100644 d9ccf26c987c5e29e8cda92004077828c62d064e<PHONE_NUMBER>000000000000000000000000000000 M      hkmc2/jvm/src/test/scala/hkmc2/ReplHost.scala
~/c/mlscript (hkmc2-print-stack-trace) [1]> git diff-files --exit-code -p                            # git diff-files --exit-code -p exit with 1, but do not show any diff
~/c/mlscript (hkmc2-print-stack-trace) [1]> git diff --exit-code -p                                  # git diff --exit-code -p exit with 0
~/c/mlscript (hkmc2-print-stack-trace)> git diff-files --exit-code -p                                # git diff-files --exit-code -p now also exit with 0
~/c/mlscript (hkmc2-print-stack-trace)> git status                                                   # git status shows no changes
On branch hkmc2-print-stack-trace
Your branch is up to date with 'anto/hkmc2-print-stack-trace'.
nothing to commit, working tree clean
~/c/mlscript (hkmc2-print-stack-trace)> echo x >> hkmc2/jvm/src/test/scala/hkmc2/ReplHost.scala      # add something
~/c/mlscript (hkmc2-print-stack-trace)> truncate -s-2 hkmc2/jvm/src/test/scala/hkmc2/ReplHost.scala  # and undo the change again
~/c/mlscript (hkmc2-print-stack-trace)> git status                                                   # execute git status first
On branch hkmc2-print-stack-trace
Your branch is up to date with 'anto/hkmc2-print-stack-trace'.
nothing to commit, working tree clean
~/c/mlscript (hkmc2-print-stack-trace)> git diff-files --exit-code -p                                # after git status, git diff-files --exit-code -p exit with 0
~/c/mlscript (hkmc2-print-stack-trace)> git --version
git version 2.39.5 (Apple Git-154)
</details>

Wow, thanks for looking into this! I wonder why this was never a problem before. I suppose the new diff-tests is overriding some files even though there are no actual changes.
So what do you suggest to fix it? Fixing the root issue could actually make more sense. Could you commit the fix in this PR?

Indeed I guess this was not a problem before because previous diff-tests will run git status at the directory containing test files so that git diff-files, which is executed after git status, can work as expected. The new test CompileTestRunner does not run git status, so git diff-files report spurious file changes.
For the fix I think although git diff works as expected on my machine, I cannot find clear documentation saying that it will never report spurious changes. So maybe it's better to run git update-index -q --really-refresh before git diff-files.

Thanks for the fixes!


After reload state form local storage, state$.subscribe() give back an empty state

I use the NgxsLocalStoragePluginModule. After reload the app, the state will load from local storage correctly (state show correctly on dev tools), but the subscribe give me an null value.
@Select(TmpState) tmpState$: Observable<any>;

constructor() {
  this.tmpState$.subscribe((state) => {
    console.log(state); // null
  });
}

Any idea what I'm doing wrong?

@labs-scnm what version are you using?

I tested with 2.0.0-rc.10 and 2.0.0-rc.12.

@labs-scnm could you try not in the constructor? (different lifecycle hook or in the template) and see what that result is?

I tested it before on ngOnInit(), same result.

@labs-scnm what about spitting it out in the template? I am only asking because our integration app isn't having this problem

@labs-scnm can you provide a repo or stackblitz that reproduces the issue?

On the template is the same result, it's empty.
It seems, the store init will dispatch before restore the state.
Ok, I will try to provide an example.

Ok, I found the problem. The restore dosen't work with lazy loading!
Here are an working example: https://stackblitz.com/edit/ngxs-localstorage

@labs-scnm excellent thank you!

Welcome! Hope you find a solution. ☺

ha me too :)

@labs-scnm we just pushed an update to lazy loading and feature modules. could you give it a shot?

Sry, but still same result. Empty result after reload. 😔
I updated also the example app, so you can verify the result: https://stackblitz.com/edit/ngxs-localstorage

I tested some possible scenarios, it seams the lazy state is loading to early from the local storage, also if I'm not running the lazy module.
Some Details
If I have an lazy module with own (lazy) state, normally the state will be loaded first with the module. I can see an empty state on the DevTools, before I load the lazy module.
But if the state restored from the local storage, the state is still exist, also before the the lazy module loaded.
I update my example app, to run and test this scenario.
Hope this will help to find the issue! 🙏

@labs-scnm thanks for the info (and patience) I still haven't figured this one out and im burned out for the weekend. Ill try to get back to it something this week. could also use some help if you have any ideas


Add vcfanno to the annotation workflow

Is your feature request related to a problem? Please describe

Describe the solution you'd like

Describe alternatives you've considered

Additional context

note to self: https://github.com/projectoriented/rucksack/tree/main/rucksack


Bug: when creating an event always the same time is sent although user puts different input

https://github.com/sopra-fs23-group-07/sopra-fs23-group-07-client/commit/c82330e66c72a1837c526f271c363a9fb2af2c8f


Load test the bot for capacity

should be able to handle upto 1000 facebook conversations

Tools

[ ] tsung
[ ] artillery


msgflo-foreign-participant MQTT timeout

After a while of running the coordinator, seeing one of these per each foreign participant (started with --forever=true):
1485432445: Client mqttjs_aa005680 has exceeded timeout, disconnecting.
1485432445: Socket error on client mqttjs_aa005680, disconnecting.

#30 would probably help?

Yes, we must send regularly to not be disconnected on MQTT. One can bump keepalive, but its only delaying the inevitable.

Considering we don't actually send anything after the initial message this doesn't really result in any observable issues, apart from that covered in #30

@bergie this should be fixed now in 0.10.0. Can you re-rest?

Please re-open if not fixed.


RFC: include distance with "{devcommit}"

Ref: https://github.com/zsimic/setupmeta/issues/33

Let's do this, a bit of extra info on devcommit (when not on tag) sounds fine


fix connection and notebook icons not highlighting

This PR fixes https://github.com/microsoft/azuredatastudio/issues/13312

Pull Request Test Coverage Report for Build 354718224

0 of 0   changed or added relevant lines in 0 files are covered.
8 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.02%) to 40.284%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/common/ports.ts
4
74.14%

extensions/notebook/src/jupyter/serverInstance.ts
4
73.81%

Totals

Change from base Build 354583404:
-0.02%

Covered Lines:
21149

Relevant Lines:
48264

💛  - Coveralls


Adding Dropdown in sidenav

I am not able to add drop down to the sidenav. I tried this from the documentation {   type: "collapse",   name: "Dashboards",   key: "dashboards",   icon: <Shop size="12px" />,   collapse: [     {       name: "Analytics",       key: "analytics",       route: "/dashboards/analytics",       component: <Analytics />,     },     {       name: "Sales",       key: "sales",       route: "/dashboards/sales",       component: <Sales />,     },   ], } I am getting the following error: TypeError: Cannot read properties of undefined (reading 'pathname')

**Hi @Shazil1 **
Thanks for using our product unfortunately the collapse is only available for the PRO version of the product.
All the best
Sajad


Report an issue points to 404

Using the 'Report Issue' menu option brings a pop up window with a GitHub 404.
It seems to direct to https://github.com/into-cps/INTO-CPS_Application/issues/new

Duplicate of #124. Already fixed.


Update to inaccurate footer text

Have you checked if this is correct for tictactoe?

TicTacToe doesn't have the Type /tictactoe to play or something along those lines. It doesn't even have a footer.

Should we add a footer while already working on the footers then?

also, codecov isn't running on this PR, which is normally a blocking issue

Should we add a footer while already working on the footers then?

I wouldn't know where to add embed.set_footer(text="Start playing by typing /programs tictactoe")

also, codecov isn't running on this PR, which is normally a blocking issue

How do I enable it / is really needed?

Should we add a footer while already working on the footers then?

I wouldn't know where to add embed.set_footer(text="Start playing by typing /programs tictactoe")

I'd have to check, but I think it would be in the view.py for that sub module, there should be a central callback iirc where the embed is handled, and in programs.py where the initial embed is made. You probably could find all spots by looking for where .set_image(url="attachment://tictactoe.png") is.

also, codecov isn't running on this PR, which is normally a blocking issue

How do I enable it / is really needed?

It isn't needed yet because i'm still building test coverage, but i would like to know why it isn't running.
Also, I do want to add the footer text to checks for corresponding tests so if i change the layout of command structure later, there's a higher chance of this being caught by the continuous integration


Add correct Anaconda badge

Hi @RileyWilliams this corrects the Anaconda badge. Trivial fix.

Oops my bad, forgot to change the project name!


listPublicIpAddresses API lists the (unallocated) reserved public IPs of other account, and resulting in UI to show other account's public IPs while acquire new IPs in the network

listPublicIpAddresses API lists the (unallocated ) reserved public IPs of other account (when allocatedonly=false and account is passed in the API), and it is resulting in UI to show other account's public IPs while acquire new IPs in the network.
ISSUE TYPE

Bug Report

COMPONENT NAME

Network

CLOUDSTACK VERSION

4.14.0

CONFIGURATION

OS / ENVIRONMENT

SUMMARY

UI show the list of reserved public IPs of other account while acquire new IPs in the network
STEPS TO REPRODUCE

Create a zone with advanced network
Add two different public IP ranges in the Public Network and reserve them to two different accounts, say account01 and account02.
Login with account01, and create a network, say network01
Try to acquire new IP in the network01, which lists the reserved IPs for account02.
(or) Call listPublicIpAddresses API with account=account01 and allocatedonly=false.

EXPECTED RESULTS

The reserved public IPs of other account shouldn't be listed while acquiring new IP.

ACTUAL RESULTS

The reserved public IPs of other account are listed while acquiring new IP.

@sureshanaparti if the UI shows that the API must return those as well, which seems the real issue, did you check that?

, did you check th

yes @DaanHoogland , API is ignoring account when listing unallocated IPs (allocatedonly=false)

@sureshanaparti if the UI shows that the API must return those as well, which seems the real issue, did you check that?

yes @DaanHoogland , API is ignoring account when listing unallocated IPs (allocatedonly=false)

@sureshanaparti this might be fixed by #4675
@ravening could you confirm ?

@sureshanaparti this might be fixed by #4675
@ravening could you confirm ?

Yes that pr fixes the issue

thanks for the confirmation @ravening

@shwstppr can you test if PR #4675 fixes the issue for this bug?

tested listpublicipaddresses API and Acquire New IP UI with #4675. IPs assigned to different account were not listed.
And not able assign ip from another account.
(local) 🐱 > list publicipaddresses id=1404f2a2-1c30-49a5-8aea-6da8cfa3295e
{
  "count": 1,
  "publicipaddress": [
    {
      "fordisplay": true,
      "forvirtualnetwork": true,
      "id": "1404f2a2-1c30-49a5-8aea-6da8cfa3295e",
      "ipaddress": "<IP_ADDRESS>",
      "isportable": false,
      "issourcenat": false,
      "isstaticnat": false,
      "issystem": false,
      "networkid": "c8822cbc-1fd7-4a76-b6fd-04db5c103806",
      "physicalnetworkid": "2282fc1e-02f9-4b99-bc65-9c3c606b1b40",
      "state": "Free",
      "tags": [],
      "vlanid": "eac3ddb5-4635-445f-b727-8b4eed2ace08",
      "vlanname": "vlan://53",
      "zoneid": "6d560900-b905-4f31-af04-c2e3f947e9c6",
      "zonename": "Sandbox-simulator"
    }
  ]
}

(local) 🐱 > list networks id=b0a7048b-2dfc-4dbf-bd2e-cf5bbd4e7692 filter=id,name,account
{
  "count": 1,
  "network": [
    {
      "account": "account1",
      "id": "b0a7048b-2dfc-4dbf-bd2e-cf5bbd4e7692",
      "name": "iso"
    }
  ]
}

(local) 🐱 > associate ipaddress networkid=b0a7048b-2dfc-4dbf-bd2e-cf5bbd4e7692 ipaddress=<IP_ADDRESS>
🙈 Error: (HTTP 533, error code 9999) Insufficient address capacity

Fixed in https://github.com/apache/cloudstack/pull/4675


[Suggestion] - add support for annotations on Grafana dashboard ConfigMap

Suggestion
Hi,
Thanks for maintaining Grafana dashboards as part of the charts, it is a great added value!
It would however be very convenient if one could add annotations to the Grafana dashboard's ConfigMaps, so the dashboards can be stored under a folder structure within Grafana.
apiVersion: v1
kind: ConfigMap

data:
  example-dashboard.json: |-
    {
      ...
    }
metadata:
  annotations:
    k8s-sidecar-target-directory: /tmp/dashboards/example-folder
  labels:
    grafana_dashboard: example-tag
  name: example-name
  namespace: example-namespace

Product
Jira, Confluence
Code of Conduct

[X] I agree to follow this project's Code of Conduct

hi @sleterrier thanks for this suggestion. It definitely makes sense to add annotations. I'll make sure this feature makes it to 1.14.2 release

@sleterrier https://github.com/atlassian/data-center-helm-charts/pull/637 this will make it to the next release. Thanks for your suggestion 👍


502 Bad Gateway

Hello i am facing an issues Ubuntu 22.04 Docker 4gb ram. docker crash everyday.
Any idea
[0] <--- Last few GCs --->  [0]   [0] [14:0x7f3784903280]  2191032 ms: Scavenge (reduce) 924.2 (998.2) -> 924.1 (999.2) MB, 8.1 / 0.0 ms  (average mu = 0.985, current mu = 0.969) allocation failure;   [0] [14:0x7f3784903280]  2191155 ms: Mark-sweep (reduce) 925.1 (999.2) -> 924.6 (1000.2) MB, 120.3 / 0.0 ms  (average mu = 0.957, current mu = 0.482) allocation failure; scavenge might not succeed  [0]   [0]   [0] <--- JS stacktrace --->  [0]   [0] FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory  [0] node server.js exited with code SIGABRT  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  [1] ERROR Making Cron Request..  [1] SyntaxError: Unexpected token < in JSON at position 0  [1]     at JSON.parse (<anonymous>)  [1]     at Response.json (node:internal/deps/undici/undici:6160:23)  [1]     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

In the issue title you wrote 502 Bad Gateway, but I am not seeing that in the error log you posted. Can you please let me know where you are seeing the 502 error?

Every 50 min i have to restart docker container
https://serp.vivacoda.com/

Can you please answer my question? It will help me pinpoint the issue.
And also, try login to your docker container with ssh, and open the cron.js file and replace it with the code found here https://haste.zneix.eu/raw/mosydadoby and then restart the container and see if the issue still occurs or not.

Thanks any idea where i can find it? Ubuntu latest docker. I am unable  to find the file

first run docker ps -a to get all the running docker containers.
Then notice the name of the serpbear docker container. Suppose its xxx, in that case, run the following to ssh into it.
sudo docker exec –it xxx /bin/bash
Once you are logged in, cd into app directory, and the cron.js file should be inside it.

I got this
OCI runtime exec failed: exec failed: unable to start container process: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown

In that case, try this: sudo docker attach xxx

Nothing happend really strange i wait like 5 min

Please try the methods described here to ssh into the container: https://stackoverflow.com/a/48835704/391955


Reducing distribution size RFC

Since we are in RFC creation mode for deck.gl, did a write-up on current thoughts around reducing distribution size.
#621
@georgios-uber  @romaxa

Landed so that RFC is available on master. It links to this PR where reviews can be added.


I've added my Address

Please don't submit spam like this. If you're coming from hacktoberfest be aware that submitting two spam PR's will disqualify you.


[Setup wizzard] support setup for an already registered GitHub App

Feature request / idea:
User flow: as a brand new Probot user, with some experience developing github apps, I've created/registered the app before starting the creation of the (Probot) app itself.
When starting the app for the first time (using npm run dev), the resulting page while fetching localhost:3000 offers a button to register the app.
Here, the user could be offered an alternate path to input the settings and keys of their already registered Github app. Instead of following the automated wizard to register a new one, the settings are added to the .env file, while it downloads the private key, etc.
Thoughts?

done 👍

Would still love this to be implemented :)


AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?

Exception when trying to run.
user@machine:~$ ds4drv
Traceback (most recent call last):
  File "/usr/local/bin/ds4drv", line 5, in <module>
    from ds4drv.__main__ import main
  File "/usr/local/lib/python3.12/site-packages/ds4drv/__main__.py", line 5, in <module>
    from .actions import ActionRegistry
  File "/usr/local/lib/python3.12/site-packages/ds4drv/actions/__init__.py", line 1, in <module>
    from ..action import ActionRegistry
  File "/usr/local/lib/python3.12/site-packages/ds4drv/action.py", line 1, in <module>
    from .config import add_controller_option
  File "/usr/local/lib/python3.12/site-packages/ds4drv/config.py", line 72, in <module>
    class Config(configparser.SafeConfigParser):
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?

Installed using sudo pip install ds4drv.
Fedora Workstation 39. Python Python 3.12.2.

The solution to this is to navigate to /usr/local/lib/python3.12/site-packages/ds4drv/config.pyand modify lines 72 and 99 from SafeConfigParser to ConfigParser
Save and run again.
Also, on Fedora, you may run into an error regarding hcitools. If that's the case, then you need to install bluez-deprecated off the rpm, which includes hcitools.


Add payment processing

paddle added in https://github.com/jayfk/launchr/commit/05fd84f81c7c135d77036955924f35f4f5c3da25


comparing joint vs pooled calling

I took a quick look at the vcf and there seems to be 2x variants in the joint vs pooled analysis runs (freebayes, n=143 exomes). Does that seem expected?
I'm tempted to try a hybrid approach. Something that calls small batches of samples via the pooled approach before doing the joint aggregation. The batches could be seeded with a set of common reference samples.

Daryl;
There are 2x more total variant positions when you run samples joint versus fully pooled (all 143 together)? That doesn't seem right, I'd expect them to be closer than that. The joint approach shouldn't be tons more sensitive than a pooled approach. If you can isolate and provide some differences happy to offer suggestions.
The pooled, then joint approach is what we've done previously for large samples. We called families in batches, then combined and re-called together for the final squared off joint set.
Hope this helps.