Prompt for remote url in CLI

The user experience should be something like this:
PROMPT FOR: (New) Backup path?
PROMPT FOR: Remote git backup? (Y/N)
      If yes, PROMPT FOR: Remote URL.
      Create `public` and `private` folders and do something with that.
PROMPT FOR: What to back up?

I'd like to take this one.

Migrating to a new issue for the idea of separating public and private backups.


when use dbname has "gis*" string, docker can not restart container

user postgresql v9.6
when i create db name "gis-server" and config with docker-compose volumes /data/gisdata:/var/lib/postgressql ,exec docker restart the container, some problems in logs
ERROR: databases "gis" already exists
i can not restart the docker container
when i rename db "gis-server" to "dbserver" ,it's restart fine.

Going to close assuming you fixed the issue. You could also try asking over at the Docker Community Forums, Docker Community Slack, or Stack Overflow. Since these repos aren't really a user-help forum


[BUG] kong proxy externalTrafficPolicy from Cluster to Local cause dramatic random latencies

Summary
We have been running kong in production  over the last month in a K8s cluster (gcp) and it was working great.
We recently change our kong config to be able to use ip-restriction this topics
basicely we change the external traffic policy so that the user IP is forwaded to the services, according to this k8s docs
However, this change caused dramatic random latencies on all our endpoints. To be more precise some of our APIs took more than 5 to 10 seconds to respond whereas other were working perfectly. few minutes later all was okay and then the issues reapered randomly ( but frequently). It came to the point that some of our services were totaly unusable.
However we check and :

The traffic was totaly normal on our APIs (less than 1 rps overall)
All of our pods were in good health (no resheduling nor atteint limits)
Kong proxy was using few ressources :
they were no warning nor debug in the logs

Finaly we rollback the modification and recame to proxy.externalTrafficPolicy: CLuster and all immediately was back to normal.
Steps To Reproduce

install kong with ingress controller via helm chart with the normal values.
only add proxy.externalTrafficPolicy: Local

create an ingress that uses kong proxy and that reach a basic api

navigate on this api and wait for excessive time response

Additional Details & Logs

Kong version (1.3)
Kong ingress controller (0.6.0)

Can you please upgrade Kong to 1.4.2 as it contains a few important fixes?
Which cloud provider are you using?

@samsja any update?

Nop, however we are still using kong 1.3 , it may helped to upgrade as suggested by @hbagdi

@samsja, when you have time to upgrade and try this, and still find the issue, can you please reopen this ticket so that we can investigate it further. For now we feel it is fixed on a more recent release already, and thus closing this.


Upon redirect to the note symbol, Apache will say "Not Found"

Upon placing the repo into Apache and setting it up, attempting to browse to the root, it will redirect to the music symbol like it's supposed to, but Apache won't display the music browser.

yup. i encounter the same problem: The requested URL /â™« was not found on this server.

Try setting a virtual host for it, or modify .htaccess
RewriteBase / to the correct path e.g. RewriteBase /koel/ however you will notice an empty page since the project's views need to be modified too, because there is no relative url for css or js scripts, e.g. resources/views/index.blade.php file you can clearly notice it is not compatible with subdirectories in url path.

That was indeed the problem. I didn't have AllowOverride All in my virtual host config so the .htaccess file was not parsed.
Thanks!

What would I need to do to fix this problem?

Try to put something like this in /etc/apache2/sites-enabled
<VirtualHost *:80>
        ServerName koel.local

        XSendFilePath /data/Music        # Change to your music folder
        DocumentRoot /var/www/koel    # Change to the folder you installed koel in
        <Directory /var/www/koel>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride All
                Require all granted
        </Directory>
</VirtualHost>

@vhanla Hi, I was edited the resources/view/index.blade.php and resources/view/auth/login.blade.php with URL of app folder from <form method="post" action="/login"  to <form method="post" action="koel/login"  , the login page show up with informations fully (logo, form) but when I click to login button, the console log show errors, something like that:
http://mywebsite/public/build/css/vendors-f9a37709f1.css
http://mywebsite/public/build/css/app-b9d02655ca.css
http://mywebsite/public/build/js/vendors-99cbf2751a.js
http://mywebsite/public/build/js/main-e6326a8774.js

check #134 and help me


Improve some aspects of WillRenameFile experiences

Pylance recently implemented WilRenameFile handler and noticed 2 things.

Will Rename Dialogbox will pop up even if empty edit (no changes or documentchanges) is returned. It would be nice if vscode check not only whether edits is null but check edits is empty. Provider can do the check but that means all provider needs to do the check when vscode can do it for all providers.
If user selects "don't show again" in the dialogbox, it is not saved to settings so user can't reverse the decision they made for the workspace. It would be nice if users have a way to change the option they selected later on.
cancellation token created for progress bar is not propagated to WillRenameFile event handlers. so a handler once started can't be cancelled even if vscode file operation got cancelled due to either user clicking cancel on progress bar or timed out.

Pushed changes for the first two issues, closing with the option to continue the discussion

@jrieken how would I access the cancellation token in the extension API. I couldn't find a way to get access to it. Anything I am missing?

To verify

create an extension that uses the onWillRenameFiles event
provide an empty WorkspaceEdit to the waitUntil-function
ensure that no dialog showsn


The choice to output null values during binary tree traversal should be provided.

Describe the solution you'd like
The choice to output null values during binary tree traversal should be provided. Like bfs, dfs

In version 1.42.0, we added this feature


Add info on converting to an annual plan

Add instructions on how to convert a monthly team plan to an annual plan.

The team-specific change looks good. We should also add a docs update for switching from a monthly Pro plan to an annual plan.

LGTM


Error upload file with FormData

I try upload file:
const data = new FormData()
data.append('file', file)
useHttp(url, {
        method: 'POST',
        headers: {
          'Content-Type': 'multipart/form-data'
        },
        body: data
      })

but get error:
Uncaught (in promise) Error: Unknown object type "formdata"
    at Object._object (index.mjs?v=ec9512e1:57:17)
    at Object.dispatch (index.mjs?v=ec9512e1:34:30)
    at Object._object (index.mjs?v=ec9512e1:77:18)
    at Object.dispatch (index.mjs?v=ec9512e1:34:30)
    at Object._array (index.mjs?v=ec9512e1:88:16)
    at Object._object (index.mjs?v=ec9512e1:53:30)
    at Object.dispatch (index.mjs?v=ec9512e1:34:30)
    at objectHash (index.mjs?v=ec9512e1:13:10)
    at hash (index.mjs?v=ec9512e1:481:56)
    at useHttp (composables.mjs?v=ec9512e1:8:1)

update the module and try again


Carousel - empty slide list

When slides list is cleared and filled with new slides Carousel stops working.
Here is reproducer.
Scenario:

Load 4 images - works fine
After 5 seconds clear slides list and fill with new images - carousel stops working

Plunker: http://plnkr.co/edit/u6inF6vMIzdSVplgkJBr?p=preview
AngularJS: 1.4.5
UI Bootstrap: 0.13.4

I'm experiencing the same.
My case: Clear and recompose the slide list when the window is resized past a media breakpoint. Active and next()/prev() fall apart, so the slides are no longer shown. Explicitly setting the first slide to active shows the first slide, but next/prev no longer function. <- verified as not an issue in 0.13.0. Verified as not functional in 0.13.4.
Bootstrap: 3.3.4
Other things tried:

Keep the same array for $scope.slides and just clear it out/push. <- still an issue.
Use a directive to totally nuke/repop the carousel in the page <- still an issue (this is wonky and could be an invalid case)

Verified as an issue in 0.13.1, 0.13.2, and 0.13.3 as well. NOTE: In my case, there's something funky around when/how the script is included. When I use the direct include, it appears to work in all versions, but after production-ification, 0.13.0 works and 0.13.1+ doesn't (likely my app/grunt setup).
Bower include: "angular-bootstrap": "0.13.0", <- works
Thanks!

There is a bug present in UI Bootstrap, but there are two things being done wrong here - one should not break the reference in $scope.slides here, and one should defer adding slides until the carousel is complete handling the garbage collection of listeners on the slide $scopes.
I will file a PR with the bug fix shortly, as well as link a Plunker that handles this correctly.

Hi!
I've updated Plunker and it seems that nothing has changed.
Can you check it?
http://plnkr.co/edit/HNakbA6GkNNcy3VZmoaF


Added get_by_id since there is no way to get current version of page…

since there is no way to get a current version of page otherwise, so actually no way to do 'update' the page.

Is there any chance of this merge happening in the near future?
We'd love to stop using our custom version and switch to the official gem.

@pegasd I'm sorry, I'm completely missed your message. Il


Adding reply callback to deployFeed and adding using it for canary failures

Adding a new callback to the deployFeed which enables returning slack blocks to be sent as a reply to a sent message as a follow up. The first usage of this is sending a reply following a canary failure explaining that the pipeline is paused and tagging the people involved (those who have commits in the failing deploy).

LGTM


Extension Request: Dendron

[X] Extension name: Dendron
[X] Extension GitHub or homepage: https://github.com/dendronhq/dendron
[X] Extension Visual Studio Link: https://marketplace.visualstudio.com/items?itemName=dendron.dendron

Note: After setting up /etc/systemd/user/code-server.service.d/override.conf with:
[Service]
Environment=SERVICE_URL=https://open-vsx.org/vscode/gallery ITEM_URL=https://open-vsx.org/vscode/item

so that I could hit https://open-vsx.org/, I got the following error:

I'm not sure what VScode version code-server uses under the hood.

Thanks for bringing this to our attention. Unfortunately, we do not have the ability to update extensions posted to the open-vsx registry.
To view the VSCode version used in your current version of code-server, navigate to the Help -> About menu.

Regarding including the extension in the default code-server marketplace, the best course of action is to request that the publisher include bundled .vsix artifacts in their Github Releases.

have updated dendron to be compatible with code server in the latest release (0.10.5). this issue should be safe to close


Update maps-api.md

I think that, since is the first step "initial" opposed to final is better.

my pleasure @conceptdev


chore(GitHub): add repository-settings app configuration

What
add .github/settings.yml file with basic configuration, primary to

add the list of allowed teams/collaborators
enable "delete branch on PR merge" feature

Release checklist

[x] assign this PR to yourself
[ ] add meaningful labels
[x] add at least 2 reviewers

closes #72

let's wait for @pietrograndi to have a look also


valueTransformer does not work even being called

Hi
I'm trying to transform the value into double. But when the button tapped, the value is still the String type.
This is the print output
I/flutter (19930): valueTransformer
I/flutter (19930): String

And the code
class EmployeeFormScreen extends StatelessWidget {
  final _formKey = GlobalKey<FormBuilderState>();

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(),
      body: FormBuilder(
        key: _formKey,
        child: Column(
          children: [
            FormBuilderTextField(
              name: 'salary',
              initialValue: '5000',
              keyboardType: TextInputType.number,
              valueTransformer: (value) {
                print('valueTransformer');
                return double.tryParse(value);
              },
            ),
            ElevatedButton(
              child: Text('Submit'),
              onPressed: () {
                _formKey.currentState.save();

                print(_formKey.currentState.fields['salary'].value.runtimeType);
              },
            )
          ],
        ),
      ),
    );
  }
}

Version Log
flutter_form_builder: 4.2.0

$ flutter doctor -v
[✓] Flutter (Channel stable, 1.22.4, on Linux, locale en_US.UTF-8)
    • Flutter version 1.22.4 at /home/bolt/dev/data/flutter
    • Framework revision 1aafb3a8b9 (2 months ago), 2020-11-13 09:59:28 -0800
    • Engine revision 2c956a31c0
    • Dart version 2.10.4

I don't know if this is a bug or I'm using it in the wrong way.
Thanks

Your data is processing just fine. You're just looking at the field's value (what has been entered into the text field, which is a string).
Instead you want to check the value after it has been transformed, which you can retrieve with _formKey.currentState.value['salary']

Your data is processing just fine. You're just looking at the field's value (what has been entered into the text field, which is a string).
Instead you want to check the value after it has been transformed, which you can retrieve with _formKey.currentState.value['salary']

Awesome!
Thanks it's working now :+1:

Awesome!
Thanks it's working now :+1:


(EMAIL) EGA - to be sent 26.11

Subject:
EN: E-commerce Germany Awards are open for submissions!
DE: E-Commerce Germany Awards ist offen für Bewerbungen!
File:
EN: ebe9-ega-intro-en.blade.php
DE: ebe9-ega-intro-de.blade.php

@az today's mailing & PRs:

EGA: https://github.com/ecommerceberlin/ecommercegermanyawards.com/pull/208
exhibitor panel: https://github.com/ecommerceberlin/exhibitors/pull/218


Sync multiple tabs opening the same page

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
When working on an application, it's possible to open two tabs for the same app. However, changes done to one tab are not kept in sync with the other. We take the risk to lose previous work if saving changes from a tab that is behind.
Examples 🌈
Codesandbox keeps two tabs in sync. This feature request might be part of a collaboration feature, but it might also be different here, it's about a single user with multiple tabs.
As a quick workaround, we could imagine only accepting the save events that are coming on top of the latest version that is stored in the DB, if the app detects an outdated save attempt, he could then reload the tab.
Motivation 🔦
No response

@Janpot Can this be closed now? It works now.


Adding support for Focal Loss?

Hi,
Thanks for the amazing repo. I have been using it for performing experiments focusing mostly on computer vision tasks.
I currently use focal_loss in my work. I was wondering if adding the loss to this repo would be something useful.
I currently use it in the following manner
def focal_loss(
    logits: chex.Array,
    labels: chex.Array,
    alpha: chex.Array,
    gamma: float = 2.0,
) -> chex.Array:
  """Computes the focal loss between sets of logits and labels.

  Computes the focal loss

  References:
    [Lin et al, 2017](https://arxiv.org/abs/1708.02002)

  Args:
    logits: Unnormalized log probabilities, with shape `[..., num_classes]`.
    labels: Valid probability distributions (non-negative, sum to 1), e.g a
      one hot encoding specifying the correct class for each input;
      must have a shape broadcastable to `[..., num_classes]`.
    alpha: Weighting factor, with shape `[num_classes]` and values in the range `[0, 1]`.
    gamma: Focusing parameter `>=0`. It controls the contribution of higher confidence predictions.
      Defaults to 2.

  Returns:
    focal loss between each prediction and the corresponding target
    distributions, with shape `[...]`.
  """
  chex.assert_type([logits], float)
  focus = jnp.power(-jax.nn.softmax(logits, axis=-1) + 1.0, gamma)
  loss = -labels * alpha * focus * jax.nn.log_softmax(logits, axis=-1)
  return jnp.sum(loss, axis=-1)

Apologies for the delay, this is a great suggestion, can you put together a PR?

I played with this a little the alpha-parameter has a problem in the current version. If it indeed has the shape [num_classes] the function crashes.
The current implementation also differs from the implementation in:
https://github.com/facebookresearch/fvcore/blob/0f2b23b6f93e36041d9a74764ee824541cf0a0e5/fvcore/nn/focal_loss.py#L41
I suggest to change the function as follows:
def focal_loss(
    logits: jnp.ndarray,
    labels: jnp.ndarray,
    alpha: float = 0.25,
    gamma: float = 2.0,
) -> jnp.ndarray:
    """Compute the focal loss between sets of logits and labels.

    Computes the focal loss

    References:
      [Lin et al, 2017](https://arxiv.org/abs/1708.02002)

    Args:
      logits: Unnormalized log probabilities, with shape `[..., num_classes]`.
      labels: Valid probability distributions (non-negative, sum to 1), e.g a
        one hot encoding specifying the correct class for each input;
        must have a shape broadcastable to `[..., num_classes]`.
      alpha (float): Weighting factor in range (0,1) to balance
          positive vs negative examples or -1 for ignore. Default: ``0.25``
      gamma: Focusing parameter `>=0`. It controls the contribution of higher confidence predictions.
        Defaults to 2.

    Returns:
      focal loss between each prediction and the corresponding target
      distributions, with shape `[...]`.
    """
    focus = jnp.power(-jax.nn.softmax(logits, axis=-1) + 1.0, gamma)
    loss = -labels * focus * jax.nn.log_softmax(logits, axis=-1)

    if alpha >= 0:
        alpha_t = alpha * labels + (1 - alpha) * (1 - labels)
        loss = alpha_t * loss
    return jnp.sum(loss, axis=-1)

Which mirrors the original authors' implementation.

The original code does not use a softmax, I think this might be confusing. Perhaps this can be reflected in the name somehow?

See https://github.com/deepmind/optax/pull/574 for a sigmoid version.

I am not sure the computation of the focus term is currently correct. See i.e. https://github.com/artemmavrin/focal-loss/blob/7a1810a968051b6acfedf2052123eb76ba3128c4/src/focal_loss/_binary_focal_loss.py#L512  .
I think the key idea is to expand equation two from https://arxiv.org/pdf/1708.02002v2.pdf . I think the repository link above does something similar since the softmax gives us probabilities that sum to one.

Hi @v0lta
Can you share the reason for the crash? There is a unit test  that I have added in the PR, are you using as described there?
We can use scalar/vector for alpha, but, I have to emphasize that this is a multi-class focal loss and not a binary one. That is why it utilises softmax instead of sigmoid.
As mentioned in the documentation string, it takes as input a [..., num_classes] object. It could be that you tried for num_classes=1 and it didn't work.

You are right. Something like equation two from Lin et al., 2017, does not exist in the multi-class version. Bishops equation (5.24) confirms this [1].
Regarding the error, I think I had a shape that was unequal to [num_classes] it first. So that is a problem on my end. I will remove the comment from the pull request.

[1]  Pattern Recognition and Machine Learning, Christopher M. Bishop .

Current pull request: https://github.com/google-deepmind/optax/pull/599

Closing this issue since we merged #599 . Please don't hesitate to open a new issue if you have further comments on this implementation


Update to D3.js version 4

I updated the event drops to d3 version 4 .
I sticked to the code architecture as much as I could.
I mostly modified the zoom action . the axis action, changed the time parser according to the d3 upgrade reference .

the tests is passing in my enviornment

I committed all the changes .

I committed all the desired changes.
One think is that when we install event drops(npm install) it automatically run's make build.
1.how do you achieve that I didn't saw that anywhere in the code or in the package.json scripts.
2.can we disable that . this is very annoying for windows users that does not have make (I don't think that this is required process since windows users can run this with webpack

Thanks for your PR! :)
The make build is done as a prepublish npm hook (see https://github.com/marmelab/EventDrops/blob/master/package.json#L56). Indeed, that's quite annoying, even for Linux users, as it adds a lot of time to wait.
We should indeed, remove this hook and instead use a make publish target. I added an issue for that (https://github.com/marmelab/EventDrops/issues/123).

Wow outstanding work @osadan and @jpetitcolas !!!!


Add content/en/database as a service

Added a new term: Database as a Service (DBaaS)
Fixes: #340

Oh, and spellcheck is failing. Can you please make sure that's fixed as well? Thank you!

Oh, and spellcheck is failing. Can you please make sure that's fixed as well? Thank you!

What do I correct in words like DBaaS/DBA?

Edited the first sentence of how it helps


[SPARK-5182] [SPARK-5528] [SQL] WIP: Parquet data source improvements

This PR adds three major improvements to Parquet data source:

Partition discovery
While reading Parquet files resides in Hive style partition directories, ParquetRelation2 automatically discovers partitioning information and infers partition column types.
This is also a partial work for [SPARK-5182] 1, which aims to provide first class partitioning support for the data source API.  Related code in this PR can be easily extracted to the data source API level in future versions.

Schema merging
When enabled, Parquet data source collects schema information from all Parquet part-files and tries to merge them.  Exceptions are thrown when incompatible schemas are detected.  This feature is controlled by data source option parquet.mergeSchema, and is enabled by default.

Metastore Parquet table conversion moved to analysis phase
This greatly simplifies the conversion logic.  ParquetConversion strategy can be removed once the old Parquet implementation is removed in the future.

This version of Parquet data source aims to entirely replace the old Parquet implementation.  However, the old version hasn't been removed yet.  Users can fall back to the old version by turning off SQL configuration spark.sql.parquet.useDataSourceApi.
Other JIRA tickets fixed as side effects in this PR:

[SPARK-5509] 3: EqualTo now uses a proper Ordering to compare binary types.

[SPARK-3575] 4: Metastore schema is now preserved and passed to ParquetRelation2 via data source option parquet.metastoreSchema.

TODO:

[ ] More test cases for partition discovery

[ ] Fix write path after data source write support (#4294) is merged
It turned out to be non-trivial to fall back to old Parquet implementation on the write path when Parquet data source is enabled.  Since we're planning to include data source write support in 1.3.0, I simply ignored two test cases involving Parquet insertion for now.

[ ] Fix outdated comments and documentations

PS: This PR looks big, but more than a half of the changed lines in this PR are trivial changes to test cases. To test Parquet with and without the new data source, almost all Parquet test cases are moved into wrapper driver functions. This introduces hundreds of lines of changes.

Test build #26514 has started for   PR 4308 at commit af3683e.

This patch merges cleanly.

Test build #26514 has finished for   PR 4308 at commit af3683e.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class DefaultSource extends RelationProvider with SchemaRelationProvider

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26514/
Test FAILed.

Test build #26537 has started for   PR 4308 at commit 0277e47.

This patch merges cleanly.

Test build #26562 has started for   PR 4308 at commit 87689d5.

This patch merges cleanly.

Test build #26572 has started for   PR 4308 at commit 170a0f8.

This patch merges cleanly.

Test build #26562 has finished for   PR 4308 at commit 87689d5.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class DefaultSource extends RelationProvider with SchemaRelationProvider

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26562/
Test FAILed.

Test build #26572 has finished for   PR 4308 at commit 170a0f8.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class DefaultSource extends RelationProvider with SchemaRelationProvider

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26572/
Test FAILed.

Test build #26591 has started for   PR 4308 at commit a760555.

This patch does not merge cleanly.

Test build #26595 has started for   PR 4308 at commit 1b11851.

This patch does not merge cleanly.

Test build #26595 has finished for   PR 4308 at commit 1b11851.

This patch fails to build.
This patch does not merge cleanly.
This patch adds the following public classes (experimental):
class KafkaUtils(object):
trait Column extends DataFrame with ExpressionApi
class ColumnName(name: String) extends IncomputableColumn(name)
trait DataFrame extends DataFrameSpecificApi with RDDApi[Row]
class GroupedDataFrame protected[sql](df: DataFrameImpl, groupingExprs: Seq[Expression])
 protected[sql] class QueryExecution(val logical: LogicalPlan)
class DefaultSource extends RelationProvider with SchemaRelationProvider

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26595/
Test FAILed.

Test build #26596 has started for   PR 4308 at commit 07599a7.

This patch merges cleanly.

Test build #26596 has finished for   PR 4308 at commit 07599a7.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KafkaUtils(object):
public class JDBCUtils
trait Column extends DataFrame with ExpressionApi
class ColumnName(name: String) extends IncomputableColumn(name)
trait DataFrame extends DataFrameSpecificApi with RDDApi[Row]
class GroupedDataFrame protected[sql](df: DataFrameImpl, groupingExprs: Seq[Expression])
 protected[sql] class QueryExecution(val logical: LogicalPlan)
          logWarning(s"Couldn't find class $driver", e);
 implicit class JDBCDataFrame(rdd: DataFrame)
class DefaultSource extends RelationProvider with SchemaRelationProvider

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26596/
Test FAILed.

Test build #26601 has started for   PR 4308 at commit bcb3ad6.

This patch merges cleanly.

Test build #26591 has finished for   PR 4308 at commit a760555.

This patch fails PySpark unit tests.
This patch does not merge cleanly.
This patch adds the following public classes (experimental):
class DefaultSource extends RelationProvider with SchemaRelationProvider

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26591/
Test FAILed.

Test build #26601 has finished for   PR 4308 at commit bcb3ad6.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class KafkaUtils(object):
public class JDBCUtils
trait Column extends DataFrame with ExpressionApi
class ColumnName(name: String) extends IncomputableColumn(name)
trait DataFrame extends DataFrameSpecificApi with RDDApi[Row]
class GroupedDataFrame protected[sql](df: DataFrameImpl, groupingExprs: Seq[Expression])
 protected[sql] class QueryExecution(val logical: LogicalPlan)
          logWarning(s"Couldn't find class $driver", e);
 implicit class JDBCDataFrame(rdd: DataFrame)
class DefaultSource extends RelationProvider with SchemaRelationProvider

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26601/
Test FAILed.

Test build #26667 has started for   PR 4308 at commit 5584e24.

This patch merges cleanly.

Test build #26667 has finished for   PR 4308 at commit 5584e24.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class DefaultSource extends RelationProvider with SchemaRelationProvider

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26667/
Test FAILed.

Test build #26734 has started for   PR 4308 at commit ae1ee78.

This patch merges cleanly.

Test build #26734 has finished for   PR 4308 at commit ae1ee78.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26734/
Test FAILed.

retest this please

Test build #26769 has started for   PR 4308 at commit ae1ee78.

This patch merges cleanly.

The last build failure was caused by a flaky ML test case, which is now fixed in master.

Test build #26769 has finished for   PR 4308 at commit ae1ee78.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
protected class CaseInsensitiveMap(map: Map[String, String]) extends Map[String, String]
trait CreatableRelationProvider

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26769/
Test FAILed.

retest this please.
The last build failure reports that isFile and isRoot are not member of org.apache.hadoop.fs.FileStatus, which doesn't make sense (the pull request builder uses Hadoop 2.3.0, and these methods are definitely defined in FileStatus).

retest this please.

Test build #26780 has started for   PR 4308 at commit ae1ee78.

This patch merges cleanly.

Test build #26780 has finished for   PR 4308 at commit ae1ee78.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
protected class CaseInsensitiveMap(map: Map[String, String]) extends Map[String, String]
trait CreatableRelationProvider

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26780/
Test FAILed.

Test build #26797 has started for   PR 4308 at commit 209f324.

This patch merges cleanly.

Test build #26797 has finished for   PR 4308 at commit 209f324.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
protected class CaseInsensitiveMap(map: Map[String, String]) extends Map[String, String]
trait CreatableRelationProvider

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26797/
Test PASSed.

Rebased (for the 8th time during the last 72 hours), should be ready to go once Jenkins nods. Will address comments in follow-up PRs.

Test build #26856 has started for   PR 4308 at commit 1ad361e.

This patch merges cleanly.

OK, rebased for the 9th time... Addressed all comments except for adding option to disable metadata caching, which I'd like to include in another PR.

Test build #26858 has started for   PR 4308 at commit b6946e6.

This patch merges cleanly.

Test build #26856 has finished for   PR 4308 at commit 1ad361e.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
protected class CaseInsensitiveMap(map: Map[String, String]) extends Map[String, String]
trait CreatableRelationProvider

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26856/
Test PASSed.

Test build #26858 has finished for   PR 4308 at commit b6946e6.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
protected class CaseInsensitiveMap(map: Map[String, String]) extends Map[String, String]
trait CreatableRelationProvider

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/26858/
Test PASSed.


Support for battery level

Hi,
I can see from your readme and comment on intructables.com that you found a way to retrieve the battery level.
Can you please detail which bytes are the ones to get data from?

@doktoil-makresh I didn't ever get around to trying to add the battery level to the script, and don't have a device with me to test it on, but here's an attempt if you want to try it: https://github.com/sighmon/raspberry-pi-bluetooth-temperature/pull/2

Hi Simon, thank you for answering quickly!
It seems to work. I guess I'm receiving battery level for the main station.
Do you have any idea or documentation that may help retrieving sensors batteries ?
I was expecting to find sensors batteries in other indexes, but there are no other indexes.

@doktoil-makresh Unfortunately I don't have any documentation... and just out of interest, was your reading 64% by any chance? I couldn't get it to return anything other than that when I was using sudo gatttool -b <BLE ADDRESS> -t random --char-read --uuid=0x2A19 to read it. So I wonder if they haven't implemented it for this device?
I also wonder if we haven't signed up for notifications from the battery uuid, and if we have whether the readings are in the bytes we're not handling. e.g. this line in the output: handle 1d = 11120b11112927ff00800080ffffffffffffffff

gatttool outputs 64 indeed, but not your piece of script.
I tried extracting data from the different handlers, but I don't know what too expect: percentage, quarters (the app shows from 0 to 3 bars), voltage, etc
Without any documentation it is a bit difficult. I'll work on it as soon as one of my sensor battery is not shown as full in the app, and I hope finding something...
Thanks again for your help.


Package not found

Expected behavior
godep save identifies all dependencies in a new project and saves the json in the GoDeps folder to be created
Actual behavior
Fails with error -
$godep save ./... godep: Package (github.com/kr/logfmt) not found
Steps to reproduce behavior

New Project
Take dependency on go-kit packages
Run GoDep
godep version output
$godep version
godep v74 (darwin/amd64/go1.7)
go version output
$godep version
godep v74 (darwin/amd64/go1.7)
Contents of Godeps.json file

None available - it is a brand new run for a new go-kit microservice

if I manually do, go get:
go get github.com/kr/logfmt
and then do, a
godep save
it works! - Is this still a bug or an operator error on my part?

Hey @ajayamohan, how did you install godep? Did you compile it yourself?
This looks like you are missing a dependency for godep itself, and the go get workaround you submitted seems to be pulling the dependency and dropping it in your $GOPATH. Which will of course allow godep to build properly.

Hi @kris-nova,
I installed godep through the recommended install option:
 go get github.com/tools/godep
Ajith

Okay thanks - will re-create today and get back to you.
Cheers

Hey @ajayamohan,
This looks like you ran into the problem while installing go-kit? Is that right?

Take dependency on go-kit packages

If so can we open up a new bug in go-kit for this? I think I see the problem, but I want to make sure it gets tracked correctly. Also, if that is the case can we get detailed step-by-step reproduction steps on the go-kit issue?
Thanks :)

Getting a similar error here:
godep: Package (golang.org/x/sys/unix) not found

I'm new to go, not sure if related.

@PandaWhisperer - These are all go dependency errors - how did you install your application, and what are your replication steps?

@kris-nova just like the documentation said – go get github.com/tools/godep. Is there anything else to do?

This happened to me recently because the version of godep was mismatched with my go version. This was a problem for me because Homebrew versions GOROOT (e.g. GOROOT="/usr/local/Cellar/go/1.7.3/libexec").
$ go version
go version go1.7.3 darwin/amd64
$ godep version
godep v74 (darwin/amd64/go1.7.1)

I had it installed via Homebrew. Solution was to brew remove godep && go get github.com/tools/godep. Hope this helps someone else!

@kris-nova Figured it out! I cloned a repo using 'go get' and then did 'godep save'
I got an error that godep could not find a dependency. I got the missing dependency with 'go get' and ran 'godep save' again. Again I got the missing dependency with 'go get'. Eventually, 'godep save' worked. The reason appears to be that go is trying to be efficient: It only imports packages that are appropriate for my OS (ubuntu). godep, on the other hand, is looking for all dependencies, regardless of the value of GOOS. Solution: 'go get' missing dependencies until 'godep save' works.

I tried that, and eventually ran into this roadblock:
mjs10:tpr-example mspreitz$ godep save
godep: Package (github.com/docker/distribution/digest) not found
mjs10:tpr-example mspreitz$ go get github.com/docker/distribution/digest
package github.com/docker/distribution/digest: cannot find package "github.com/docker/distribution/digest" in any of:
    /usr/local/go/src/github.com/docker/distribution/digest (from $GOROOT)
    /Users/mspreitz/Documents/go/src/github.com/docker/distribution/digest (from $GOPATH)

It's probably looking at the master branch which no longer has a digest directory (blame docker), maybe try manually checking out https://github.com/docker/distribution/tree/release/2.6 in your $GOPATH and then running godep save in your project.

  That got me past that difficulty.

Next up:
mjs10:tpr-example mspreitz$ godep save
godep: Package (github.com/emicklei/go-restful/swagger) not found
mjs10:tpr-example mspreitz$
mjs10:tpr-example mspreitz$ go get github.com/emicklei/go-restful/swagger
package github.com/emicklei/go-restful/swagger: cannot find package "github.com/emicklei/go-restful/swagger" in any of:
	/usr/local/go/src/github.com/emicklei/go-restful/swagger (from $GOROOT)
	/Users/mspreitz/Documents/go2/src/github.com/emicklei/go-restful/swagger (from $GOPATH)

Found that referenced in client-go's Godeps, with a commit ID.  Checking out that commit got me past that one.

I wrote a small bash script to automate this for those interested:
missing_package="start"
while [ "$missing_package" != "" ]
do
  missing_package=$(godep save 2>&1 | \
    egrep '^godep: Package (.*) not found' | \
    sed 's/.*(\(.*\)).*/\1/');
 [ "$missing_package" != "" ] && {
   echo "Installing missing package: ${missing_package}" ;
   go get -u "${missing_package}"
  }
done

@carlosonunez , thank you. That script worked for me. Although I had to add ./... to godep save:
godep_save() {
  missing_package="start"
  while [ "$missing_package" != "" ]
   do
    missing_package=$(godep save $@ 2>&1 | \
      egrep '^godep: Package (.*) not found' | \
      sed 's/.*(\(.*\)).*/\1/');
   [ "$missing_package" != "" ] && {
     echo "Installing missing package: ${missing_package}" ;
     go get -u "${missing_package}"
    }
  done
  godep save $@
}

No problem! I'm glad I could help.
Sent from my iPhone

On Jun 20, 2017, at 20:10, 1138-4EB<EMAIL_ADDRESS>wrote:
@carlosonunez , thank you. That script worked for me. Although I had to add ./... to godep save:
godep_save() {
missing_package="start"
while [ "$missing_package" != "" ]
do
missing_package=$(godep save $@ 2>&1 |
egrep '^godep: Package (.) not found' |
sed 's/.((.))./\1/');
[ "$missing_package" != "" ] && {
echo "Installing missing package: ${missing_package}" ;
go get -u "${missing_package}"
}
done
godep save $@
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

$ ll
total 8601
drwxr-xr-x 1 jockc 197609       0 7月   8 00:08 conf/
-rwxr-xr-x 1 jockc<PHONE_NUMBER>600 7月   8 06:02 contentlibs.exe*
drwxr-xr-x 1 jockc 197609       0 7月   7 23:09 doc/
drwxr-xr-x 1 jockc 197609       0 7月   8 06:03 Godeps/
-rw-r--r-- 1 jockc 197609    1065 7月   6 04:59 LICENSE
-rw-r--r-- 1 jockc 197609     345 7月   8 05:30 main.go
drwxr-xr-x 1 jockc 197609       0 7月   8 05:32 module/
-rw-r--r-- 1 jockc 197609      70 7月   6 04:59 README.md
drwxr-xr-x 1 jockc 197609       0 7月   8 05:33 utils/
drwxr-xr-x 1 jockc 197609       0 7月   8 06:03 vendor/

jockc@DESKTOP-MDSE3EM MINGW64 ~/go/src/contentlibs (master)
$ pwd
/c/Users/jockc/go/src/contentlibs

$ godep go build
main.go:4:2: cannot find package "contentlibs/module" in any of:
        D:\Go\src\contentlibs\module (from $GOROOT)
        C:\Users\jockc\go\src\contentlibs\Godeps\_workspace\src\contentlibs\module (from $GOPATH)
main.go:6:2: cannot find package "github.com/go-martini/martini" in any of:
        D:\Go\src\github.com\go-martini\martini (from $GOROOT)
        C:\Users\jockc\go\src\contentlibs\Godeps\_workspace\src\github.com\go-martini\martini (from $GOPATH)
main.go:7:2: cannot find package "github.com/martini-contrib/render" in any of:
        D:\Go\src\github.com\martini-contrib\render (from $GOROOT)
        C:\Users\jockc\go\src\contentlibs\Godeps\_workspace\src\github.com\martini-contrib\render (from $GOPATH)
godep: go exit status 1

I am getting this error. How can I proceed to solve this now ?
go get github.com/tools/godep
package github.com/tools/godep: cannot download, ### $GOPATH not set. For more details see: go help gopath

@Sikandarkhan: that is a basic issue about using the go tools. See https://golang.org/doc/code.html

Any workaround to allow me to do "godep save ./..."? I hit the error
"godep: package (github.com/docker/distribution/digest) not found"
I build alright but just failed at "godep save ./..."

@PandaWhisperer do you solve the problem,  i have a same one

I am closing this issue because the repo is going to be archived.

It worked again for me after removing and reinstalling godep. Likely a mismatch of verions of go and godep after my MacOS upgrade.


App attribute missing

Click to expand!
Issue Type
Build/Install
Source
source
Tensorflow Version
2.9.1
Custom Code
Yes
OS Platform and Distribution
Linux Ubuntu 20.04
Mobile device
No response
Python version
3.7.6
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
File "resnet_main.py", line 18, in <module>
    FLAGS = tf.app.flags.FLAGSAttributeError: module 'tensorflow' has no attribute 'app'

Standalone code to reproduce the issue
File "resnet_main.py", line 18, in <module>
    FLAGS = tf.app.flags.FLAGSAttributeError: module 'tensorflow' has no attribute 'app'

Relevant log output
No response

Hi @ShubhAgarwal-dev !
You can use Flags using compat.v1 mode using below command.
tf.compat.v1.flags.FLAGS
Reference
Thank you!


commands: fix a bug where docker-machine env -u fails

resolve #2204
Signed-off-by: Soshi Katsuta<EMAIL_ADDRESS>

Thank you for the PR. It's fixed with https://github.com/docker/machine/pull/2250


Permissions in Azure DevOps to execute

I'm running the command via PS console, but result the error:
Get-AzSKADOSecurityStatus -OrganizationName "........." -ProjectNames "......" -ScanAllResources -DetailedScan -ResetCredentials
Using '*' can take a long time for the scan to complete in larger projects.
You may want to provide a comma-separated list of projects, builds, releases, service connections, agent pools and variable groups.

Organization not found: Incorrect organization name or '............' account does not have necessary permission to access the organization. Use -ResetCredentials parameter in command to login with another account.
InvalidOperation: Invalid JSON primitive: .

What permissions does the user need to have in Azure DevOps?
Thank you
Leandro Prado

Hi @leandromsft, you need to be a valid user in the given ADO org to scan it. If you can access the org on ADO, you should be able to scan via ADO scanner as well. Please check if you are giving the correct organization name in -OrganizationName parameter. Also check if the account being used to scan is the same as the one having access. You can also try logging in again by using the switch -ResetCredentials as the end of your command. If you are still facing issues, please let us know.

Hi @juhi037, I'm part of the Team Project Contributor group, but when I try to run the Get-AzSKADOSecurityStatus command, the error below
Organization not found: Incorrect organization name or<EMAIL_ADDRESS>account does not have necessary permission to access the organization. Use -ResetCredentials parameter in command to login with another account.
I execute the command using the -ResetCredentials, but result the same error
I try to use the -PATToken parameter, and result the same error
Thank you for help

Hi @leandromsft. Can you please validate if you are running the latest version i.e. 1.17.0? Also can you try if you can use the ADO Scanner from an extension. You can find the steps here: https://github.com/azsk/ADOScanner-docs/tree/master/05-Running ADOScanner as pipeline extension. If this does not work as well, we can get on a call to better understand the issue. We work in IST hours from 9 AM - 6 PM.

Hi @juhi037 , thank you for help.
I was using an old version
I upgraded to version 1.17.9 and now it worked
Thank you


Conversation command shows old transcripts

Clicking right and left goes through the history of logs.

One thing: I was going to put this in a separate command or behind arguments to not slow down the current use case but it ended up being fast enough I thought it was better to keep it simple. I think I'll make it accept an optional argument that can be a log a json or jsonl and have it display those as well in a future pr

LGTM


 Is the docker daemon running on this host?
  └ UpdatedAt: 2016-05-06T15:35:45Z
  └ ServerVersion:
 (unknown): <IP_ADDRESS>:2375
  └ ID:
  └ Status: Pending
  └ Containers: 0
  └ Reserved CPUs: 0 / 0
  └ Reserved Memory: 0 B / 0 B
  └ Labels:
  └ Error: Cannot connect to the Docker daemon. Is the docker daemon running on this host?
  └ UpdatedAt: 2016-05-06T15:35:25Z
  └ ServerVersion:
 (unknown): <IP_ADDRESS>:2375
  └ ID:
  └ Status: Pending
  └ Containers: 0
  └ Reserved CPUs: 0 / 0
  └ Reserved Memory: 0 B / 0 B
  └ Labels:
  └ Error: Cannot connect to the Docker daemon. Is the docker daemon running on this host?
  └ UpdatedAt: 2016-05-06T15:35:15Z
  └ ServerVersion:
Plugins:
 Volume:
 Network:
Kernel Version: 4.4.8-boot2docker
Operating System: linux
Architecture: amd64
CPUs: 0
Total Memory: 0 B
Name: 8c6604b3d48e

I expose few ports, as I thought it may be a network issue, but it did not help that is why:
-P -p <IP_ADDRESS>:8500:8500 \
    -p <IP_ADDRESS>:4000:4000 \
    -p <IP_ADDRESS>:2375:2375 \

is present, without it, same result

There might be some problems in your setup. This doc should be good to follow https://docs.docker.com/swarm/install-w-machine/.
First you want to validate docker port and TLS. Use docker-machine ls to validate which port docker uses (in the following case it's 2376). Managers should be able to reach nodes, i.e., command docker -H node_ip:port info is successful from manager. TLS is likely open so you need to include TLS settings.
$ docker-machine ls
NAME         ACTIVE   DRIVER       STATE     URL                         SWARM
default    *        virtualbox   Running   tcp://<IP_ADDRESS>:2376

Swarm join doesn't need to expose any service port. join registers node (specified by --advertise) to consul and keeps it updated. It shouldn't expose any port.
eval $(docker-machine env node0)
docker run -d \
    -P -p <IP_ADDRESS>:8500:8500 \
    -p <IP_ADDRESS>:4000:4000 \
    -p <IP_ADDRESS>:2375:2375 \
    swarm join --advertise=$(docker-machine ip node0):2375 consul://$(docker-machine ip consul0):8500

Thanks for your reply, can the TLS config be the only reason ? (I do not need tls for now, it just for some internal test environment)
The link you provide adds a token in the example, but I am following https://docs.docker.com/swarm/multi-manager-setup/ and no token is provided.
Can the configuration work with consul without token?

Using TLS did not help, node are still in Pending status, regarding https://docs.docker.com/swarm/multi-manager-setup/, I cannot use token as I am using consul.
What am I missing?

Ok got it: --advertise has to take the tcp port of docker service


missing_formula: fix cask installation advice on tap migration

When an installed formula is missing and its source has migrated
to a new tap, Homebrew warns the user about this, saying:
You can access it again by running:
  brew tap new-name
And then you can install it by running:
  brew cask install new-name

Unfortunately, the "brew cask install" incantation is deprecated
and the advice won't work:
Error: Calling brew cask install is disabled! Use brew install [--cask] instead.

This alters the advice to use the new "brew install --cask" notation,
fixing the advice presented to the user.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?
[ ] Have you successfully run brew man locally and committed any changes?

Thanks!

Thanks!


test: enable --throw-deprecation for tests

Enabling --throw-deprecation for the tests ensures that no deprecated methods are being used in nodejs.  I'm trying to track down a node.js 12 property deprecation, and figured I may as well do this while I was in here :)

Thx, will merge this on next release.


Use prob more strictly inside SSD and Faster R-CNN

We should use prob whenever possible.

We cannot assume that all models return a value in [0, 1] as a confidential score.

None of them return probs. The internal naming is changed to be more explicit.

None of them return probs.

Sorry, it's my misunderstanding.

The internal naming is changed to be more explicit.
Using both score and prob is confusing. I don't think this modification improves readability.

Using both score and prob is confusing. I don't think this modification improves readability.

I agree. It is not necessary to enforce this rule.


Loop not working (DeadlineExceeded desc = context deadline exceeded)

Hi when I try to do "Loop In" I and up with this error:
Error: Error: cannot initiate swap: rpc error: code = DeadlineExceeded desc = context deadline exceeded

Retrying does not help (same error)
Version:

RaspiBlitz v1.6.3

Bug to be researched/fixed for next release.

Bug to be researched/fixed for next release.

Same error here.
Environment
Version of RTL - v0.10.1-boltz-integration-release
Version of lnd - 0.11.1-beta
Version of btcd, bitcoind, - v0.20.0
Browser & browser version - 88.0.4324.190 (Official Build) (64-bit)
Host Operating system - Linux raspberrypi 4.19.118-v7l+ #1311 SMP Mon Apr 27 14:26:42 BST 2020 armv7l GNU/Linux
Go Version - go1.16 linux/arm
RaspiBlitz - v1.6.3
loopd.log
2021-03-04 22:35:13.122 [INF] LOOPD: Loop in terms request received
2021-03-04 22:35:13.215 [INF] LOOPD: Loop in quote request received
2021-03-04 22:35:13.217 [INF] LOOPD: Loop in quote request received
2021-03-04 22:35:28.354 [INF] LOOPD: Loop in quote request received
2021-03-04 22:35:33.288 [INF] LOOPD: Loop in request received
2021-03-04 22:35:33.288 [INF] LOOP: Loop in 0.0025 BTC (last hop: )
2021-03-04 22:35:33.401 [INF] LOOP: Creating probe invoice 19aa2aa8447a7f69c56bf52007483706dd37dc7598ae046739fd1d777210612b
2021-03-04 22:35:33.422 [INF] LOOP: Initiating swap request at height 673172
2021-03-04 22:36:03.448 [ERR] LOOPD: Loop in: cannot initiate swap: rpc error: code = DeadlineExceeded desc = context deadline exceeded

With v1.7RC1 we will have loop now as part of the "Lightning Terminal" that offers also cli .. @ShahanaFarooqui is it still possible to integrate?

@ph-legacy @brandonshope Can you guys test the v1.7RC2 on the dev branch. There is the image to download and build_sdcard.sh if wanted. Also, RC3 coming probably this week.

Running Loop solo is deprecated ... RTL will now use the the LIT cli. First test looked good - marking for final v1.7.1 testing.


Add simulated nominal type for COM SAFEARRAY and VarDate to lib.scripthost.d.ts

TypeScript Version:  nightly (2.5.0-dev.20170725)
When running Javascript under an Automation context (Windows Script Host, or HTML Applications), there are two types exposed by various APIs: VarDate and SafeArray. These types have no shape  from Javascript's perspective:

they cannot be constructed using new, and
they have no  members that can be consumed from Javascript

However, other methods/constructors/properties expect these types and will fail if an incorrect type is passed in:
var rst = new ActiveXObject('ADODB.Recordset');
// open the connection and recordset here
var fields = ['firstname', 'lastname'];
var values = ['Plony', 'Almony'];

// Will fail at runtime, since two SafeArrays are expected, and not two Javascript arrays
rst.Update(fields, values);

Currently, VarDate is typed in lib.scripthost.d.ts as an empty interface; while SafeArray has no defined type, and methods that expect a SafeArray are typed with any (example).
I propose adding a representation of these types to lib.scripthost.d.ts:
declare class VarDate {
    private VarDate_typekey: VarDate;
    private constructor();
}

declare class SafeArray<T = any> {
    private SafeArray_typekey: SafeArray<T>;
    private constructor():
}

An interface couldn't be used here, because there is no shape from Javascript, and an empty interface is equivalent to any

The private constructor prevents new VarDate();

The other private member prevents assigning an arbitrary object to a variable/parameter of this type:
  //compiler error -- Property 'VarDate_typekey' is missing in type '{}'
 let x: VarDate = {};

Note that this is actually simulating nominal typing (thanks @aleksey-bykov for the suggestion). If some form of nominal typing is introduced to TypeScript, the definitions for VarDate and SafeArray could be rewritten accordingly.

The previous definition for Update could then be written as follows:
declare namespace ADODB {
    interface Recordset {
        Update(Fields: SafeArray<string>, Values: SafeArray): void;
    }
}

that article is a bit outdated, here is the latest workaround: https://github.com/Microsoft/TypeScript/issues/202#issuecomment-302402671

@aleksey-bykov Fixed, thanks.

@DanielRosenwasser Any news? Could you describe some of the discussion relating to this?


Release bundle distribution for commercial

@spencergibb @marcingrzejszczak @OlgaMaciaszek obviously the number of files changed here is ridiculous.  Most of them are files in git repos for tests.  If you ignore that stuff its much more manageable.  I did test this stuff releasing 2022.0.7, 2022.0.6, and Spring Cloud Contract 4.0.8.  I will go over these changes on Thursday so everyone is on the same page.


non-fragment lexer rule BYTES can match the empty string

https://github.com/jcabi/jcabi-parent/issues/131
 [INFO] Processing grammar: org/eolang/parser/Program.g4
Warning:  warning(146): org/eolang/parser/Program.g4:286:0: non-fragment lexer rule BYTES can match the empty string
Warning:  /home/runner/work/eo/eo/org/eolang/parser/Program.g4 [286:0]: non-fragment lexer rule BYTES can match the empty string
[INFO]

@yegor256 Done in #542


Prevent large number of dictionary resizes

Summary of the changes
GCPauseWatson reports high GC pressure caused by frequent dictionary resizes in this code:
https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1824275
We attempt to reduce these by giving the dictionary a reasonable size to start with.
Fixes:

Preallocate a dictionary large enough for all the likely additions we'll make.

@dotnet/razor-compiler for a second review.


KOGITO-6962: DSL reorganization for flexibility

https://issues.redhat.com/browse/KOGITO-6962
Depends on https://github.com/kiegroup/kogito-pipelines/pull/416

Hi @radtriste! Thanks for the PR. Can you please give us a little bit more context on what you're working on?

jenkins retest this

jenkins retest this

The (build) kie-tools-stunner-editors check has failed. Please check the logs.

jenkins retest this

@tiagobento why CodeQL / Analyze (java) is failing ?

btw @tiagobento could you approve this one ?

Hi @radtriste! We're already investigating why CodeQL / Analyze (java) is failing. For now, let's ignore it.
Regarding CI :: Monorepo (full), you have formatting issues. This can be easily solved by running yarn format at the root of the repository.

The (build) kie-tools-stunner-editors check has failed. Please check the logs.

jenkins failure is expected

jenkins retest this


Unable to run example

Getting the dreaded Couldn't find any pixel format that matches the criterias error when running the example.
Hardware: Dell XPS 9650
OS: Linux 4.13.3-1-ARCH
Window Manager: xmonad 0.13-9
Backtrace
% RUST_BACKTRACE=1 cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.0 secs
     Running `target/debug/spinning-square`
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: "Couldn\'t find any pixel format that matches the criterias."', /checkout/src/libcore/result.rs:860:4
stack backtrace:
   0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace
             at /checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::_print
             at /checkout/src/libstd/sys_common/backtrace.rs:71
   2: std::panicking::default_hook::{{closure}}
             at /checkout/src/libstd/sys_common/backtrace.rs:60
             at /checkout/src/libstd/panicking.rs:380
   3: std::panicking::default_hook
             at /checkout/src/libstd/panicking.rs:396
   4: std::panicking::rust_panic_with_hook
             at /checkout/src/libstd/panicking.rs:611
   5: std::panicking::begin_panic_new
             at /checkout/src/libstd/panicking.rs:553
   6: std::panicking::begin_panic_fmt
             at /checkout/src/libstd/panicking.rs:521
   7: rust_begin_unwind
             at /checkout/src/libstd/panicking.rs:497
   8: core::panicking::panic_fmt
             at /checkout/src/libcore/panicking.rs:92
   9: core::result::unwrap_failed
             at /checkout/src/libcore/macros.rs:41
  10: <core::result::Result<T, E>>::unwrap
             at /checkout/src/libcore/result.rs:738
  11: spinning_square::main
             at src/main.rs:56
  12: __rust_maybe_catch_panic
             at /checkout/src/libpanic_unwind/lib.rs:98
  13: std::rt::lang_start
             at /checkout/src/libstd/panicking.rs:458
             at /checkout/src/libstd/panic.rs:361
             at /checkout/src/libstd/rt.rs:59
  14: main
  15: __libc_start_main
  16: _start

Cargo.toml
[package]
name = "spinning-square"
version = "0.1.0"
authors = []

[[bin]]
name = "spinning-square"

[dependencies]
piston = "0.34.0"
piston2d-graphics = "0.22.0"
pistoncore-glutin_window= "0.40.0"
piston2d-opengl_graphics = "0.47.0"

src/main.rs
extern crate piston;
extern crate graphics;
extern crate glutin_window;
extern crate opengl_graphics;

use piston::window::WindowSettings;
use piston::event_loop::*;
use piston::input::*;
use glutin_window::GlutinWindow as Window;
use opengl_graphics::{ GlGraphics, OpenGL };

pub struct App {
    gl: GlGraphics, // OpenGL drawing backend.
    rotation: f64   // Rotation for the square.
}

impl App {
    fn render(&mut self, args: &RenderArgs) {
        use graphics::*;

        const GREEN: [f32; 4] = [0.0, 1.0, 0.0, 1.0];
        const RED:   [f32; 4] = [1.0, 0.0, 0.0, 1.0];

        let square = rectangle::square(0.0, 0.0, 50.0);
        let rotation = self.rotation;
        let (x, y) = (
            (args.width / 2) as f64,
            (args.height / 2) as f64
        );
        self.gl.draw(args.viewport(), |c, gl| {
            // Clear the screen.
            clear(GREEN, gl);

            let transform =
                c.transform
                    .trans(x, y)
                    .rot_rad(rotation)
                    .trans(-25.0, -25.0);

            // Draw a box rotating around the middle of the screen.
            rectangle(RED, square, transform, gl);
        });
    }

    fn update(&mut self, args: &UpdateArgs) {
        // Rotate 2 radians per second.
        self.rotation += 2.0 * args.dt;
    }
}

fn main() {
    let opengl = OpenGL::V4_5;

    // Create a Glutin window.
    let mut window: Window =
        WindowSettings::new("spinning-square", [200, 200])
            .exit_on_esc(true)
            .samples(4)
            .opengl(opengl)
            .build()
            .unwrap();

    // Create a new game and run it.
    let mut app = App {
        gl: GlGraphics::new(opengl),
        rotation: 0.0
    };

    let mut events = Events::new(EventSettings::new());
    while let Some(e) = events.next(&mut window) {
        if let Some(r) = e.render_args() {
            app.render(&r);
        }

        if let Some(u) = e.update_args() {
            app.update(&u);
        }
    }
}

I can confirm this issue, was about to post it and I have had this error for a month or so on two different machines
Hardware: T440p with dedicated GPU
OS:  Linux 4.13.7-1-ARCH
Window Manager: i3-wm 4.14.1-1
and
Hardware: T450s with Intel GPU
OS:  some lts kernel, has been a while since I checked
Window Manager: i3-wm 4.14.1-1
I did test it on the laptop of a friend though where it worked, waiting for him to give me the specs

Can also confirm.
Kernel: LTS Kernel (4.9)
Window Manager: KWin
Seems to be an issue with Arch Linux in general?

Friend confirmed his specs he is also running Arch with a NVidia GPU and the nouveau drivers (like me) but it works for him. This issue has also been discussed in #1202 the .srgb(false) does not work for me though

Does an older version of OpenGL work on your machine?

Note that I had this same issue with Amethyst; however, the problem has been fixed in master. Maybe there could be some coordination to figure out what causes this issue.

Downgrading mesa to 17.1.X fixed it for me, as was suggested somewhere but I cant find that again :/
There was also some thread about this being a bug in mesa, will try to find it again

This is a clear dupe of #1202.

This seems to have been fixed with the latest mesa 18.*. See https://github.com/PistonDevelopers/piston/issues/1202 for more information.

Closing.


KEP 262: Configurable Failure Policy API

Fixes #262

Chatting with @danielvegamyhre in slack - I want to share our discussion here (and perhaps move up a level to a higher level picture):
When thinking about success/failure of JobSet, we have several levels that this might operate on:

lowest level only we have the failure / success policy defined on the level of Job (and indexed job, for example) so then that is honored, and replicatedJob is just a shell to put that in (and honor those policies), and that trickles up to replicatedJob->JobSet.
"global": if something in the JobSet fails, we have to start everything again (this doesn't seem ideal to me) but certainly was an OK starting approach, before the full set of use cases was known for JobSet.
"middle level": if something fails in a replicatedJob, take this action.
"multiple level": any of the above, with needing to resolve conflicting preferences (probably not ideal)

I do agree that just the global level is not ideal (I think this is a main thrust of this KEP) Likely the original implication of JobSet was to make it easy to wrap jobs together, and assume they fail together, but the use case has expanded beyond that to not want that anymore. As an example, I often use JobSet to run an indexedJob (some HPC app running in parallel) and then I have services that run alongside it, nicely on the same headless service provided by JobSet. If the service fails, I would just want the service to restart, and I wouldn't want my main compute/simulation/ML job to be failed. Within that, I might have logic on the indexed job that says something about what happens if a single index fails.
So the "fail the entire JobSet if one component fails" design is not good for that use case. Then the question becomes where to add the logic - does it belong with Job or replicatedJob? I'm assuming we don't want to manage conflicts (the last case) for now.
For having the logic on replicatedJob, that is theoretically adding additional context to a Job, so I kind of like that, but if we want the failure/success to work for Job outside of JobSet, then the first bullet makes most sense (and then replicated Job inherits) but that might be a harder change if it needs to go into Kubernetes proper. If we aren't able to OR it's much harder to make a change to there, then likely you'd put this logic on replicatedJob for now.
So TLDR: we definitely have use cases for this. The challenging part, for me, is in terms of design - where to allow representing the policies, and how that is managed given conflict.

Also just a high level observation - I understand ML (and ML jobs) are leading the industry space now, but I think it's dangerous to develop Kubernetes components that are optimized primarily for that. I think the vision here needs to be flexible that the future could (likely will be) different.

Thanks @vsoch, I see in https://github.com/kubernetes-sigs/jobset/pull/381#discussion_r1465571802 that HPC were discussed, do you have feedback on whether or not the current proposal addresses them? Can you help suggest user stories to add to the KEP to evaluate if the proposed approach handles them and if not, discuss how to adjust it to accommodate them?

Chatting with @danielvegamyhre in slack - I want to share our discussion here (and perhaps move up a level to a higher level picture):
When thinking about success/failure of JobSet, we have several levels that this might operate on:

lowest level only we have the failure / success policy defined on the level of Job (and indexed job, for example) so then that is honored, and replicatedJob is just a shell to put that in (and honor those policies), and that trickles up to replicatedJob->JobSet.
"global": if something in the JobSet fails, we have to start everything again (this doesn't seem ideal to me) but certainly was an OK starting approach, before the full set of use cases was known for JobSet.
"middle level": if something fails in a replicatedJob, take this action.
"multiple level": any of the above, with needing to resolve conflicting preferences (probably not ideal)

I do agree that just the global level is not ideal (I think this is a main thrust of this KEP) Likely the original implication of JobSet was to make it easy to wrap jobs together, and assume they fail together, but the use case has expanded beyond that to not want that anymore. As an example, I often use JobSet to run an indexedJob (some HPC app running in parallel) and then I have services that run alongside it, nicely on the same headless service provided by JobSet. If the service fails, I would just want the service to restart, and I wouldn't want my main compute/simulation/ML job to be failed. Within that, I might have logic on the indexed job that says something about what happens if a single index fails.
So the "fail the entire JobSet if one component fails" design is not good for that use case. Then the question becomes where to add the logic - does it belong with Job or replicatedJob? I'm assuming we don't want to manage conflicts (the last case) for now.
For having the logic on replicatedJob, that is theoretically adding additional context to a Job, so I kind of like that, but if we want the failure/success to work for Job outside of JobSet, then the first bullet makes most sense (and then replicated Job inherits) but that might be a harder change if it needs to go into Kubernetes proper. If we aren't able to OR it's much harder to make a change to there, then likely you'd put this logic on replicatedJob for now.
So TLDR: we definitely have use cases for this. The challenging part, for me, is in terms of design - where to allow representing the policies, and how that is managed given conflict.

I think it is better to handle concrete use cases than discussing hypothetical or abstract scenarios, so lets list the user stories that you would like to be taken into account.

I think it is better to handle concrete use cases than discussing hypothetical or abstract scenarios, so lets list the user stories that you would like to be taken into account.

Sure, the concrete use case is an indexed job running a simulation (wrapped in a replicatedJob) an then having several services on the same headless service (other replicatedJob) and then not wanting the entire JobSet to fail when one of the services needs to restart.

I think it is better to handle concrete use cases than discussing hypothetical or abstract scenarios, so lets list the user stories that you would like to be taken into account.

Sure, the concrete use case is an indexed job running a simulation (wrapped in a replicatedJob) an then having several services on the same headless service (other replicatedJob) and then not wanting the entire JobSet to fail when one of the services needs to restart.

For this use case, I think the RestartReplicatedJob action in the current API would work. If a job running one of the services fails, only the ReplicatedJob for the services will be recreated, not the ReplicatedJob for the main workload.

For this use case, I think the RestartReplicatedJob action in the proposed API would work. If a job running one of the services fails, only the ReplicatedJob for the services will be recreated, not the ReplicatedJob for the main workload.

And I think as long as we had some kind of policy for within the indexed job (e.g., don't restart failed workers) then it would cover the set of (near term) foreseeable cases.

For this use case, I think the RestartReplicatedJob action in the proposed API would work. If a job running one of the services fails, only the ReplicatedJob for the services will be recreated, not the ReplicatedJob for the main workload.

And I think as long as we had some kind of policy for within the indexed job (e.g., don't restart failed workers) then it would cover the set of (near term) foreseeable cases.

To clarify, do you mean within a single indexed job, don't restart a pod that has failed?

Yes, we have an example of downsizing a Flux MiniCluster and this means:

A sidecar that is monitoring the main queue notices (via an algorithm) that we have too many pods, we can downsize
We have a nice way to kill that worker
With this setting the pod is allowed to exit with code 0 instead of trying to reconnect
The pod completes and does not restart

To be clear, this isn't a failure policy that is supported natively, we had to come up with that solution via the return code - a 0 allows completion, and anything else will have the worker try to reconnect. Then the "restart" case is having completions == parallelism so we can enable scaling up/down of the actual cluster. It would create a new pod, with (unfortunately) a higher index, but we can keep track of that within the sidecar that is monitoring things.

Yes, we have an example of downsizing a Flux MiniCluster and this means:

A sidecar that is monitoring the main queue notices (via an algorithm) that we have too many pods, we can downsize
We have a nice way to kill that worker
With this setting the pod is allowed to exit with code 0 instead of trying to reconnect
The pod completes and does not restart

To be clear, this isn't a failure policy that is supported natively, we had to come up with that solution via the return code - a 0 allows completion, and anything else will have the worker try to reconnect. Then the "restart" case is having completions == parallelism so we can enable scaling up/down of the actual cluster. It would create a new pod, with (unfortunately) a higher index, but we can keep track of that within the sidecar that is monitoring things.

Ok I see, yeah this proposal wouldn't interfere with the behavior you have implemented there. As long as the Job itself is not marked as failed, the JobSet controller will do nothing here, regardless of the internal state of the indexed job. It only looks at failed jobs.

Thanks @vsoch, I see in https://github.com/kubernetes-sigs/jobset/pull/381#discussion_r1465571802 that HPC were discussed, do you have feedback on whether or not the current proposal addresses them? Can you help suggest user stories to add to the KEP to evaluate if the proposed approach handles them and if not, discuss adjustments to the API?

See https://github.com/kubernetes-sigs/jobset/pull/381#discussion_r1465826615
That's a dummy example from a real workflow I'm implementing in Kubernetes now - not using jobset (yet) but could eventually get there.

One additional idea I have is to add a DefaultAction field to the failure policy, in case the user doesn't want RestartJobSet to be the behavior for any failure not matching a failure policy rule. I think it would make the default restart/failure recovery behavior more explicitly clear in the API, rather than the user needing to read the docs/comments to understand what happens if they don't set one.
If unset, it would default to RestartJobSet so our current default behavior is preserved.
type FailurePolicy struct {
  // MaxRestarts defines the limit on the number of JobSet restarts.
  // A restart is achieved by recreating all active child jobs.
  MaxRestarts int32 `json:"maxRestarts,omitempty"`
  // List of failure policy rules for this JobSet.
  // For a given Job failure, the rules will be evaluated in order,
  // and only the first matching rule will be executed.
  Rules []FailurePolicyRule `json:"rules,omitempty"`
  // The default action that is executed for any Job failure that does
  // not match any of the failure policy rules.
  // If unset, this defaults to "RestartJobSet"
  DefaultAction FailurePolicyAction `json:"defaultAction,omitempty"`
}

What do you think?

I wouldn't add such thing.
It might make more sense for the user to add a Rule at the end that kind of matches anything

I wouldn't add such thing. It might make more sense for the user to add a Rule at the end that kind of matches anything

Hmm, can you elaborate on this a bit? That seems like a more complicated way of achieving the same thing.

Perhaps the last rule has empty OnConditionReason, so it matches any Failed condition.
It's easier to document because rules apply in order.

Re DefaultAction: I would keep the api simple. The default action is RestartJobSet, and if the user wants to change that, they can add a catch all rule at the end.

/label tide/merge-method-squash

/lgtm
/hold
holding just in case, feel free to remove the hold
Thanks Daniel!

/hold cancel
Thanks for the feedback everyone!


CSharpWorker always invoked with [-m pyspark.worker]

I noticed that Spark launches a CSharpWorker process for every task with [-m pyspark.worker] args. This cause the worker to always run in "SimpleWorker" mode and it looks like it's spawning multiple process for every Spark partition. Needless to say it wastes an awful amount of time (about 30% overall my job) just forking processes.
I'm running this in local mode on my Windows machine. I followed the instructions in the samples page, but maybe I'm missing something? I'm using the Mobius v2.0.000-PREVIEW-2 with Spark 2.0.1 release. I tried several configuration line options, but running out of ideas. Here's conf output of the driver:
16/10/26 09:59:09 INFO CSharpRunner: Starting CSharpBackend!
16/10/26 09:59:09 INFO CSharpRunner: Port number used by CSharpBackend is 4216
16/10/26 09:59:09 INFO CSharpRunner: Adding key=spark.history.fs.logDirectory and value=file:///c:/logs/spark/ to environment
16/10/26 09:59:09 INFO CSharpRunner: Adding key=spark.eventLog.enabled and value=true to environment
16/10/26 09:59:09 INFO CSharpRunner: Adding key=spark.jars and value=file:/C:/Hadoop/spark-clr_2.11-2.0.000-PREVIEW-2/runtime/lib/spark-clr_2.11-2.0.000-PREVIEW-2.jar to environment
16/10/26 09:59:09 INFO CSharpRunner: Adding key=spark.app.name and value=SparkParsingTest to environment
16/10/26 09:59:09 INFO CSharpRunner: Adding key=spark.python.worker.memory and value=1g to environment
16/10/26 09:59:09 INFO CSharpRunner: Adding key=spark.driver.memory and value=5g to environment
16/10/26 09:59:09 INFO CSharpRunner: Adding key=spark.logConf and value=true to environment
16/10/26 09:59:09 INFO CSharpRunner: Adding key=spark.python.worker.reuse and value=true to environment
16/10/26 09:59:09 INFO CSharpRunner: Adding key=spark.submit.deployMode and value=client to environment
16/10/26 09:59:09 INFO CSharpRunner: Adding key=spark.master and value=local[8] to environment
16/10/26 09:59:09 INFO CSharpRunner: Adding key=spark.eventLog.dir and value=file:///c:/logs/spark/ to environment
16/10/26 09:59:09 INFO SparkContext: Running Spark version 2.0.1
16/10/26 09:59:10 WARN NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
16/10/26 09:59:10 INFO SparkContext: Spark configuration:
spark.app.name=SparkParsingTest-C#
spark.driver.memory=5g
spark.eventLog.dir=file:///c:/logs/spark/
spark.eventLog.enabled=true
spark.history.fs.logDirectory=file:///c:/logs/spark/
spark.jars=file:/C:/Hadoop/spark-clr_2.11-2.0.000-PREVIEW-2/runtime/lib/spark-clr_2.11-2.0.000-PREVIEW-2.jar
spark.logConf=true
spark.master=local[8]
spark.python.worker.memory=1g
spark.python.worker.reuse=true
spark.submit.deployMode=client

@qintao1976 can you confirm that this behavior is expected in Windows due to the constraint in Spark code on Windows? (https://github.com/apache/spark/blob/branch-2.0/core/src/main/scala/org/apache/spark/api/python/PythonWorkerFactory.scala#L41). I think "spark.mobius.CSharpWorker.maxProcessCount" setting will not also help. Please confirm that as well.
@karvin89  it may not be practical for your situation, but one option is to set val useDaemon = true and compile Spark code for your use to get this to work.

@karvin89 - closing this issue due to inactivity. Feel free to reopen if needed.


[local_auth] localizations are incorrect for Face authentication on pixel 4 [0.6.0]

Using flutter 1.9.1 and local_auth 0.6.0 the localized strings for face authentication are not correct, as demonstrated in the screenshot.

@bbedward by localization you mean fingerprint text instead of face authentication text?

@BondarenkoStas yes that's correct, both the "Fingerprint authentication" and the "touch sensor" strings don't apply when using face authentication. It would be the same for Iris authentication on devices that support that.

@bbedward i wanted to reproduce your problem but i did not even manage to get the screen to pop up – my available biometrics are empty on the pixel 4 :/ I have enabled face unlock on the device. Is there anything else i need to consider? I have face unlock in other apps like lockwise from mozilla, so i think its basically enabled on the device itself to be used.

This was fixed in https://github.com/flutter/plugins/pull/2489


Delay transitions or scroll before animations begin?

Hi there, I absolutely love Swup!  Very easy to use, and everything seems to work great right out of the box.
The only thing I'm noticing is that the transitions I'm creating with CSS can look a little odd when used in conjunction with the page scroll.  I've tried using the doScrollingRightAway: true setting assuming it would scroll, then start the animations, but it seems like the page loads so fast that it doesn't really change anything.
So, the question is: Is there a way to scroll to the top, then start all the animations?
I've also noticed that, even when not scrolling, occasionally the "out" transitions don't seem to have enough time to complete before the page loads.  (I've got the cache disabled as well, because certain parts of the site are dynamic — not sure if that contributes to the issue or not.)
Thanks!

I see that my bottom comments about the "out transitions" were addressed by you in issue #11 .  It might not hurt to make a note about that in the documentation. Your example of using multiple classes on one item was helpful. Thanks!

Hi, glad you like it and thanks for checking the solved issues.
doScrollingRightAway option determines whether swup waits for the page to animate OUT or not to start the scroll, but will still continue with the IN animation in any way. swup doesn't have the option to animate out > scroll > animate in simply for the reason of being a bad approach, as you probably don't want a user to wait longer than needed. After all, the content of the next page is why user clicked the link.
Your best option would be to set animateScroll: false, so you animate the page out, jump to the top without the animation, and animate in. Of course, that assumes that your contents are hidden and no elements would be jumping around. Another option is to change the animation to look different or make it more optimized if that's the issue you are facing.


MudRating: make HandleKeyDown async Task

Description
Follow up for https://github.com/MudBlazor/MudBlazor/pull/8877
I missed it since I thought the HandleKeyDown is done via key interceptor therefore it cannot be a Task for now, but it's coming from onkeydown.
How Has This Been Tested?
Visually
Type of Changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (fix or improvement to the website or code docs)

Checklist

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant tests.

Will fix some stale comp.FindAll I see in tests and open it back

ready


How to increate upload size?

Is your feature request related to a problem? Please describe.
Upload failed due to max upload size
Describe the solution you'd like
In advanced config, ability to set max upload size value
Describe alternatives you've considered
Tried custom nginx.conf file in advanced config but didn't work.

This turned out to not be an issue with nginx-proxy-manager but the php side of things behind the nginx proxy manager. A fairly large file was able to be uploaded, so I think nginx allows large files through it.

Sorry to necro up an old post but I'm trying to find the php.ini file to make modifications or work around this same problem but struggling to find the file, can  you point me in the right direction please?


⚠ Bofrost.at has degraded performance

In 258bfee, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2050 ms

Resolved: Bofrost.at performance has improved in 36d6f17.


add browsing context storage docs and unit tests

See commit message for changes.

It's quite hard to add more unit tests at the moment because the classes are quite coupled with each other, i.e. it's hard to define a browser context storage instance because it requires us to instantiate pretty much every other class in the codebase. In the future we should try to decouple the classes from each other with builder pattern and dependency injection.


What kind of versioning system are you using?

Are you following the rules of semver or are you using something else for your version numbers?

Yes semver but use release as version until we get to 1.0.0
On 28 Aug 2015 15:48, "Lars-Magnus Skog"<EMAIL_ADDRESS>wrote:

Are you following the rules of semver http://semver.org/ or are you
using something else for your version numbers?
—
Reply to this email directly or view it on GitHub
https://github.com/maidsafe/crust/issues/284.

Ok. Thanks!


"Received malformed payload" on match_data_send when upgrading to V3

Hello, I followed the Defold+Nakama tutorial and created a similar game, then tried to upgrade the libraries to V3 and started getting errors on the server with "Received malformed payload".
I had some differences in code and setup so I continued my testing on the xoxo sample project branch and got the same results. Tried with multiple versions of the Nakama server and same thing.
Here's the decoded payload the server was complaining about:
{"match_data_send":{"op_code":1,"data":"{\"row\":1,\"col\":1}","match_id":"1325d106-4ea1-495f-be90-f0d33d73777c.nakama1"},"cid":"3"}

When going back to main and enabling debug level on the server but I could only find this message:
{"level":"debug","ts":"2022-10-26T19:35:35.207Z","caller":"server/pipeline.go:66","msg":"Received *rtapi.Envelope_MatchDataSend message","uid":"3a59222c-9749-4100-869f-0fe975a72be0","sid":"4cb4ce7b-5565-11ed-9018-7106fdcb5b46","cid":"3","message":{"MatchDataSend":{"match_id":"da0d6d5e-9665-4943-90af-785050561cdd.nakama1","op_code":1,"data":"eyJyb3ciOjEsImNvbCI6M30="}}}

There are some visible differences:

the key of the message: match_data_send vsMatchDataSend
data: it's a json string on V3 and it's base64 in the older version

Not sure if they should match one to one though, could be a red herring.

Are you testing with the code on main or are you using the latest release?
The 3.0.3 version does not contain the fix for this issue

I'm testing the latest release, that explains it then, thanks.

That's great, thank you! I can confirm both my project and the example project work by using the master branch.

I also had such a problem on the release, now I have a message sent on the master, but it does not go further
function M.sendMessage() 	nakama.sync(function() 		local data = json.encode({ 			row = 11, 			col = 22, 		}) 		--data=base64.encode(data) 		local op_code = 1 		local result = nakama_socket.match_data_send(socket, matchID, op_code, data) 		print("sended") 		if result.error then 			print(result.error.message) 			pprint(result) 		else 			print("ok!!!") 		end 	end) end
print("sended") - is not running

@ufgo which version of the Nakama client are you using? The fact that you don't see the print() indicates that something crashes in the coroutine, but for some reason the error is not shown (I'll look into this)-

but for some reason the error is not shown (I'll look into this)

Ah, logging is silent by default. Enable logging by doing this:
local log = require "nakama.util.log"
log.print()

nothing print
only log in docker:
nakama-nakama-1 | {"level":"debug","ts":"2022-10-30T08:44:37.293Z","caller":"server/pipeline.go:65","msg":"Received *rtapi.Envelope_MatchDataSend message","uid":"f590a664-17b8-436c-8b57-037106dd7f93","sid":"e65afced-582e-11ed-9223-7106fdcb5b46","cid":"3","message":{"MatchDataSend":{"match_id":"3cc2b731-0cc6-496d-b957-6468de15b112.","op_code":1,"data":"eyJjb2wiOjIyLCJyb3ciOjExfQ=="}}}

Can you share a minimal repro case so that I can take a look?

Closing due to inactivity. I was also not able to repro any problem myself.

I seem to have this problem as well. tho. I raised my own issue #80


Feat(web): Introduce Breadcrumbs component (refs #DS-302)

@vmilersky Please run yarn format:fix to reformat your code.

Not pixel perfect :D Please, look at the icon near Back. It is by 1px up.


Merge duplicate CI workflows

This PR merges the files ci.yml and ci-pr.yml as they completed the same jobs  but had different triggers.
The requirement for CI to only be triggered on push to the master branch was also removed as there is no branch with that name in this repo.

Coverage report failing due to it comparing the current branch to commit fff0a74d92b93946e57df32640fd8ed28ff4469a. The changes that occurred between that commit and the current v1 branch can be seen here: https://github.com/pozil/auto-assign-issue/compare/fff0a74d92b93946e57df32640fd8ed28ff4469a...v1


npm in Docker, Redis Insight, redismod

adding Dockerfile and changing docker compose to run npm in Docker instead of local machine
minor edit to node.js to then link to redis (docker) instead of localhost
now can run simply with docker compose up
also added Redis Insight and changed Redis to standard image redismod

@alexvasseur, Thank you for the PR. I will take a look and test the proposed changes.

@alexvasseur, thank you for the proposed changes.
I did some updates and removed RedisInsight v1. as I consider it EOL.


fix(connectors): fixes MGDCTRS-1755, added migration to add annotations for existing clusters and connectors

Description
Added migration to add annotations for existing clusters and connectors
Verification Steps
CI including migration tests should pass.
Checklist (Definition of Done)

[X] All acceptance criteria specified in JIRA have been completed
- [ ] Unit and integration tests added that prove the fix is effective or the feature works (tested against emulated and non-emulated OCM environment)
- [ ] Documentation added for the feature
[ ] CI and all relevant tests are passing
[ ] Code Review completed
- [ ] Verified independently by reviewer
[ ] All PR comments are resolved either by addressing them or creating follow up tasks
- [ ] Required metrics/dashboards/alerts have been added (or PR created).
- [ ] Required Standard Operating Procedure (SOP) is added.
- [ ] JIRA has been created for changes required on the client side

@valdar this PR adds missing annotations for existing clusters and annotations.


Video playback test/QA list

Embed, different browsers, scenarios, desktop, etc.

Came up with a few: https://docs.google.com/spreadsheets/d/13jhyOLPQ3xsNXpKN4wkf5FS2ia75Bc9_AOsp3cBcTIQ/edit?usp=sharing
Also added an advanced tab for some related calls that should happen.


Changing the Collider of a chunk, while running the Game....[UNITY]

Hello guys,
I bought the FastNoise Library inside the Asset Store of Unity, means I'm writing the Code in C#. Now I added the supported mesh Collider Generation to my Terrain. The Problem is, I want something like the Render Distance in the examples. So he's rendering like 10 Chunks in every x, y, z direction, but I want just like 5 Chunks Render Distance of The Colliders, so that a chunk being away like 7 chunks doesnt have the MeshCollider enabled to save processing Power. How can I do it??
Thanks.
Fable67

Hi Fable,
You should add and additional check when chunk distances are checked for unloading, and if they within a certain distance generate collider meshes for them.


Change the log dir when the directory creation fail

Thank you a lot for the contribution @karronoli!

You're wellcome!

:+1:

Thank you a lot for the contribution @karronoli as always!