Feeder.js

Hey i have a problem..
https://gyazo.com/315ee940d4cc3dae5ba15573f665b1f9
Any one can help me?

tutorial for a new version will be available soon under wiki: https://github.com/davidmann4/agario-feeder-bot/wiki


fix: added owner to transactions

Hey,
I was working with ArDB and noticed, that the owner on transactions is missing

Thank you so much @fabianriewe !


Progress: indicating progressbar does not change its color

Steps to Reproduce

visit the react.semantic-ui/modules/progress website
checkout the indicating example
compare it with the original semantic-ui example

Expected
The Progress should change its color with increasing value
Result
The Progress does not do this

SUI uses CSS selector based on data-percent attribute:

We should add data-percent attribute there.


is it possible  permission checking outside the startScanning function?

i am using startScanning function in worker
But it gives following error in Worker thread
JS: Error in Bluetooth.startScanning: Error: java.lang.NullPointerException: Attempt to invoke virtual method 'int android.content.Context.checkPermission(java.lang.String, int, int)' on a null object reference
JS:     android.support.v4.content.ContextCompat.checkSelfPermission(ContextCompat.java:453)
JS:     com.tns.Runtime.WorkerGlobalOnMessageCallback(Native Method)
JS:     com.tns.Runtime.access$400(Runtime.java:33)
JS:     com.tns.Runtime$WorkerThreadHandler.handleMessage(Runtime.java:233)
JS:     android.os.Handler.dispatchMessage(Handler.java:102)
JS:     android.os.Looper.loop(Looper.java:158)
JS:     android.os.HandlerThread.run(HandlerThread.java:61)

On Android you cannot ask for permission on a non-UI thread, therefore, it will be best if a permission is checked and granted before delegating work to the worker thread.
is it possible  permission checking outside the startScanning function?

Didn't the has.. and request.. functions here work for you?

yes i am use has.. and request... function in main thread
but  i have to use startScanning function in worker
so i just want that can you please stop checking permission in startScanning function in nativescript-bluetooth module

Ah, ok, so even if the user has granted persmission, the check in startScanning will fail because it's not on the main thread? Even when there's no need for a permission dialog in that case? Then I guess I can add an option to the startScanning method to have it not check permissions, but the default will be what it has always been of course.

ok, great
if you can add option for not check permissions to startScanning method
Thanks in advance :)

OK, you can pass a new property to this function (see the readme and update to 1.3.1).

Hello,
Thank you so much............:) for add option for not check permissions
but i face other issue in new version ..i never get call back to onConnected function
my code is:
console.log('beforeConnect....')
bluetooth.connect({
  UUID: '04343-23445-45243-423434',
  onConnected: function (peripheral) {
  	console.log("onConnected........... ");

  	// the peripheral object now has a list of available services:
  	peripheral.services.forEach(function(service) {
  	  console.log("service found: " + JSON.stringify(service));
   });
  },
  onDisconnected: function (peripheral) {
  	console.log("Periperhal disconnected with UUID: " + peripheral.UUID);
  }
});

success fully print ''beforeConnect....'' log but never print 'onConnected........... ' means never get call back to onConnected function After update it with 1.3.1 ...
so can you please help me out .
thanks once again..:)


Login breaks without email set

Description
The user is unable to login to jellyseerr with their jellyfin account if the email has been removed from the account page.
Version
1.9.0
Steps to Reproduce

Go to profile
Click edit settings
empty the email field
logout
attempt to login using jellyfin

Screenshots
No response
Logs
No response
Platform
desktop
Device
pc
Operating System
windows 10
Browser
chrome
Additional Context
Setting the email is forced during the setup process of jellyfin, this oculd explain why the login breaks if it suddenly isn't set. For clarity the email should not be able to be unset, or not be mandatory during the setup.
Code of Conduct

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

The intended behavior is email shouldn't be removed. Email is a must (even if it's just nonesense). Thank you for reporting that it can be set as empty (that's not intended)

:tada: This issue has been resolved in version 1.9.1 :tada:
The release is available on:

v1.9.1
GitHub release

Your semantic-release bot :package::rocket:


[maven-release-plugin] prepare release rocketmq-all-5.1.3

Which Issue(s) This PR Fixes

prepare release rocketmq-all-5.1.3
Brief Description

[maven-release-plugin] prepare release rocketmq-all-5.1.3
How Did You Test This Change?

Codecov Report

Merging #6938 (03c408f) into develop (3358592) will increase coverage by 0.02%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #6938      +/-   ##
=============================================
+ Coverage      42.64%   42.67%   +0.02%
- Complexity      9206     9213       +7
=============================================
  Files           1131     1131
  Lines          80421    80421
  Branches       10511    10511
=============================================
+ Hits           34299    34319      +20
+ Misses         41832    41819      -13
+ Partials        4290     4283       -7

see 16 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add Prometheus endpoints to retrieve data

Hi,
This looks like a really useful project, but I'm already doing all of my monitoring with Grafana, and I'd really like to keep it that way instead of having multiple dashboards spread across different tools, and I'm sure I'm not the only one.
Do you think it would be a good idea to add some configurable Prometheus/VictoriaMetrics endpoints that could be used to pull all that useful data into Grafana ?

This is not something we are looking at adding.
the data is available in the applications data base and could be manually access to expose to a public API.

the data is available in the applications data base and could be manually access to expose to a public API.

All right thanks, I'll try to play with this over the week-end.


removed batch_size field from GRU and LSTM

Pull Request Template
Checklist

I've run all std checks and all tests pass except for 8 tests in record that require the static file path /tmp/burn_test_file_recorder, which is not valid on Windows.

Related Issues/PRs
I haven't seen any related issues so I decided to do this pull request directly, since there are barely any changes.
Changes
I have removed the batch_size  field from both GRU and LSTM, because they limit flexibility in exchange for nothing really.
This change increases compatibility with the Pytorch API (not necessary but nice).
If you run a RL workload and algorithm like PPO, during the rollout phase (data generation) you run with batch 1 but then during training phase you switch to whatever batch size you deem correct. Eliminating the field increases the flexibility for these kinds of situations and it doesn't impact saving and loading weights or performance (from what I have observed so far).
Testing
I have ran the tests provided in the library and have not seen any performance differences for my workloads. May require further testing but the changes are very minor so I expect everything to work fine, once people adjust to the breaking changes.

This is more concise, but I'm not sure I understand how including the batch_size in the config limits flexibility- it doesn't impose any constraints that aren't already present. Both LSTM's and GRU's are stateless, so a single config was never really intended to be re-used since you'd need to extract hidden/cell states regardless and pass them to another layer, and I find it helpful to be explicit with all the parameters tying a model together in those cases. If this is a matter of preference, maybe make it an option?

Also, instead of assigning batch_size and seq_length separately maybe it's better to do array unpacking as follows:
let [batch_size, seq_length, _] = batched_input.shape().dims;
Just a minor detail.


docs: update contributing guidelines for required org membership

Which problem is this PR solving?
It should be easier to auto-assign issues and PRs and grant more authority to codeowners on specific packages.
This came up while reviewing the react-native instrumentation, which is currently the top requested feature in the repo. We want to delegate responsibly, while still keeping a high bar for adding instrumentations.
Short description of the changes
Update contributing guidelines to

require membership in the OpenTelemetry org
add owners to js-contrib-triagers role (role request in community repo)

Isn't https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/.github/workflows/component-owners.yml already meant to be handling assigning PRs to and/or request reviews from component owners?
From https://github.com/dyladan/component-owners#readme

Automatically add component owners as assignees and approvers to pull requests.
This works very similarly to CODEOWNERS, however with CODEOWNERS all owners must have write access to the repository. ...

This works very similarly to CODEOWNERS, however with CODEOWNERS all owners must have write access to the repository. ...

Aah, yes I completely forgot about this 🤦 CODEOWNERS does not work with non-write permission owners. 😞
Anyway I think we can still do something similar with component-owners.yaml and since we will give owners triage permissions they can then apply a label that a PR is ready to merge. Then approvers/maintainers can just swoop in and merge the PR. 🙂

@trentm @pichlermarc I removed the references to CODEOWNERS and just kept in the triagers role and the requirement of being in otel org.


unsupported query: ALTER SEQUENCE ... OWNED BY ...

Django 3.0 includes a bug fix to preserve the sequence owner when altering an AutoField/BigAutoField on PostgreSQL.
However, this SQL isn't supported by cockroachdb...
======================================================================
ERROR: test_alter_autofield_pk_to_bigautofield_pk_sequence_owner (schema.tests.SchemaTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/tim/code/django/django/db/backends/utils.py", line 86, in _execute
    return self.cursor.execute(sql, params)
psycopg2.errors.FeatureNotSupported: at or near "EOF": syntax error: unimplemented: this syntax
DETAIL:  source SQL:
ALTER SEQUENCE "schema_author_id_seq" OWNED BY "schema_author"."id"
                                                                   ^
HINT:  You have attempted to use a feature that is not yet implemented.
See: https://github.com/cockroachdb/cockroach/issues/26382

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/tim/code/django/tests/schema/tests.py", line 1194, in test_alter_autofield_pk_to_bigautofield_pk_sequence_owner
    editor.alter_field(Author, old_field, new_field, strict=True)
  File "/home/tim/code/django/django/db/backends/base/schema.py", line 565, in alter_field
    old_db_params, new_db_params, strict)
  File "/home/tim/code/cockroach-django/cockroach/django/schema.py", line 37, in _alter_field
    new_db_params, strict,
  File "/home/tim/code/django/django/db/backends/base/schema.py", line 739, in _alter_field
    self.execute(sql, params)
  File "/home/tim/code/django/django/db/backends/base/schema.py", line 142, in execute
    cursor.execute(sql, params)
  File "/home/tim/code/django/django/db/backends/utils.py", line 68, in execute
    return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
  File "/home/tim/code/django/django/db/backends/utils.py", line 77, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "/home/tim/code/django/django/db/backends/utils.py", line 86, in _execute
    return self.cursor.execute(sql, params)
  File "/home/tim/code/django/django/db/utils.py", line 90, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/home/tim/code/django/django/db/backends/utils.py", line 86, in _execute
    return self.cursor.execute(sql, params)
django.db.utils.NotSupportedError: at or near "EOF": syntax error: unimplemented: this syntax
DETAIL:  source SQL:
ALTER SEQUENCE "schema_author_id_seq" OWNED BY "schema_author"."id"
                                                                   ^
HINT:  You have attempted to use a feature that is not yet implemented.
See: https://github.com/cockroachdb/cockroach/issues/26382

That said, I don't think Django needs to manage any sequences because unique_rowid() is used for AutoField. Is that correct?

Link to cockroachdb issue: https://github.com/cockroachdb/cockroach/issues/26382
It does seem that unique_rowid() should be used for AutoField, but I haven't confirmed this yet.


About image format and "memorized" images

Hello!
I think that this tool is very useful, but I would like to see in the README some info about the image format it recognizes. I tried using .jpeg and it didn't recognize them, but, when I changed to .jpg, it did. So know it beforehand might help new users.
Also, I have been choosing  different folders with images until I targeted the .jpeg problem and, now, if there are 6 photos in the folder I am opening, the program chooses that those 6 photos are not the ones in the folder but part of the photos I chose in older selections. If the number of photos in the current folder is bigger than the number of different photos seen before, then, after showing older photos, it starts showing the new ones. Is there any way to restart this "memory" of older photos?
Thank you very much

Which version of the tool are you using? Django, Flask or Qt?

Which version of the tool are you using? Django, Flask or Qt?

The Qt desktop one (the one that is explained in the readme example part)

The Qt desktop one (the one that is explained in the readme example part)

Hmmm... Oh dear.
Which OS are you using?
I think I have an idea what is going on. It starts a web server in a separate process in the background. It should terminate it when you close the application. I've got a feeling that the web server from old instances of the application is still running, hence your problem.

Hmmm... Oh dear.
Which OS are you using?
I think I have an idea what is going on. It starts a web server in a separate process in the background. It should terminate it when you close the application. I've got a feeling that the web server from old instances of the application is still running, hence your problem.

I am using Ubuntu 18.04.
I tried rebooting my computer to kill the process but I still get old images. I can just ignore them right now, as they are not too many.
Thank you very much!

I am using Ubuntu 18.04.
I tried rebooting my computer to kill the process but I still get old images. I can just ignore them right now, as they are not too many.
Thank you very much!


Typing issue: 圃場

Category of the typing issue
Choose one of them (delete rest of them)

Out-of-vocabulary (e.g. "夕日" is not in the candidate list at all).

Issues
Write issues to the following table. (It's in the markdown format)

input [e.g.ゆうひ]
expected [e.g. 夕日]
actual [e.g. ユウヒ]

ほじょう
圃場
ほ場

"ほ場" だけでなく漢字のみでの表記も加えていただきたいです。
Version or commit-id
Mozc-2.28.5029.101+24.11.oss
Additional context
Add any other context about the problem here.

PR#703 added this entry.
Thank you!


Add support for testmode

This is wonderful. Can you add test coverage and I will gladly merge.

Will do

Is it ok to do like this @kayladnls?
Else I can change it back to protected and hardcode the urls in the test

I was thinking more along the lines of this: https://github.com/thephpleague/omnipay-common/blob/e8cdb1b7e3779bf945a3573803358d902db3267c/tests/Omnipay/Common/Message/AbstractRequestTest.php#L259-L268
Just to test that test mode is getting set correctly.
And then you can hardcode the URLs to ensure that when test mode is set, the right endpoint is called. I'd prefer those endpoints to be protected so they can't be changed.

Its what it did, but dynamically? Well I changed to protected and hardcoded urls now.

@kayladnls ping...


Dev

publish to pypi so that we could easily install
modify README.rst
did some integration tests(utilize aiographite lib to send to data to our graphite test instance)

lgtm


[Bug]: Getting error on npm run deploy

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[x] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
App, Extension
Expected behavior
It should have deployed extension to app
Actual behavior
request to https://partners.shopify.com/api/cli/graphql failed, reason:     │
│  802071FE01000000:error:0A0003FC:SSL routines:ssl3_read_bytes:sslv3 alert    │
│  bad record mac:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1605:SSL   │
│  alert number 20
Reproduction steps

Create New app from CLI
Create new theme extension
Then try deploy

Operating System
MacBook Pro
Shopify CLI version (check your project's package.json if you're not sure)
3.48.1
Shell
iTerm2
Node version (run node -v if you're not sure)
18.16.0
What language and version are you using in your application?
ruby 2.7.8p225

Hi! I can't reproduce it, but it looks like an SSL issue on your side.
Could you please share the output of these commands?

which openssl
openssl version -a
npm run deploy -- --verbose

Outputs:

which openssl
/opt/homebrew/bin/openssl

openssl version -a

OpenSSL 3.1.1 30 May 2023 (Library: OpenSSL 3.1.1 30 May 2023)
built on: Tue May 30 12:13:24 2023 UTC
platform: darwin64-arm64-cc
options:  bn(64,64)
compiler: clang -fPIC -arch arm64 -O3 -Wall -DL_ENDIAN -DOPENSSL_PIC -D_REENTRANT -DOPENSSL_BUILDING_OPENSSL -DNDEBUG
OPENSSLDIR: "/opt/homebrew/etc/openssl@3"
ENGINESDIR<EMAIL_ADDRESS>MODULESDIR<EMAIL_ADDRESS>Seeding source: os-specific
CPUINFO: OPENSSL_armcap=0x87d

npm run deploy -- --verbose

> deploy
> shopify app deploy --verbose

2023-08-09T14:17:41.949Z: Running command app deploy
2023-08-09T14:17:41.973Z: Reading cached app information for directory /Users/abuhasan/shopify-apps/adaptive-supply-app...
2023-08-09T14:17:41.973Z: Reading the content of file at shopify.app.toml...
2023-08-09T14:17:41.974Z: Reading the content of file at shopify.app.toml...
2023-08-09T14:17:41.976Z: Reading the content of file at shopify.app.adaptive-supply-app.toml...
2023-08-09T14:17:41.976Z: Reading the content of file at shopify.app.toml...
2023-08-09T14:17:42.043Z: Reading the .env file at .env
2023-08-09T14:17:42.044Z: Reading the content of file at .env...
2023-08-09T14:17:42.045Z: Reading the content of file at extensions/theme-extension/shopify.extension.toml...
2023-08-09T14:17:42.046Z: Reading the content of file at package.json...
2023-08-09T14:17:42.047Z: Reading the content of file at package.json...
2023-08-09T14:17:42.047Z: Obtaining the dependency manager in directory /Users/abuhasan/shopify-apps/adaptive-supply-app...
2023-08-09T14:17:42.050Z: Reading the content of file at shopify.web.toml...
2023-08-09T14:17:42.051Z: Reading the content of file at package.json...
2023-08-09T14:17:42.053Z: Ensuring that the user is authenticated with the Partners API with the following scopes:
[]

2023-08-09T14:17:42.053Z: Getting session store...
2023-08-09T14:17:42.054Z: Validating existing session against the scopes:
[
  "openid",
  "https://api.shopify.com/auth/shop.admin.graphql",
  "https://api.shopify.com/auth/shop.admin.themes",
  "https://api.shopify.com/auth/partners.collaborator-relationships.readonly",
  "https://api.shopify.com/auth/shop.storefront-renderer.devtools",
  "https://api.shopify.com/auth/partners.app.cli.access",
  "https://api.shopify.com/auth/destinations.readonly"
]
For applications:
{
  "partnersApi": {
    "scopes": []
  }
}

2023-08-09T14:17:42.054Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2023-08-09T14:17:42.054Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:
 - User-Agent: Shopify CLI; v=3.48.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2023-08-09T14:17:42.425Z: Request to https://accounts.shopify.com/oauth/introspection completed in 366 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"bd2ac7e226025c232dccc9d0bffa7355"
 - x-request-id: 6cea9ff9-0b35-4488-a055-db962dfb1654

2023-08-09T14:17:42.429Z: The identity token is valid: true
2023-08-09T14:17:42.430Z:
The validation of the token for application/identity completed with the following results:
- It's expired: false
- It's invalid in identity: false

2023-08-09T14:17:42.430Z: Verifying that the user has a Partner organization
2023-08-09T14:17:42.430Z: Sending "Partners" GraphQL request:
  {
    organizations(first: 1) {
      nodes {
        id
      }
    }
  }

With request headers:
 - User-Agent: Shopify CLI; v=3.48.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2023-08-09T14:17:42.844Z: Request to https://partners.shopify.com/api/cli/graphql completed in 400 ms
With response headers:
 - cache-control: max-age=0, private, must-revalidate
 - content-type: application/json; charset=utf-8
 - etag: W/"7bf30bcca7e5463db2cefb197f7bf447"
 - x-request-id: 27b27921-b5cc-4c4a-a15c-33b11106afbf

2023-08-09T14:17:42.846Z: Sending "Partners" GraphQL request:
  query FindApp($apiKey: String!) {
    app(apiKey: $apiKey) {
      id
      title
      apiKey
      organizationId
      apiSecretKeys {
        secret
      }
      appType
      grantedScopes
      betas {
        unifiedAppDeployment
        unifiedAppDeploymentOptIn
      }
      applicationUrl
      redirectUrlWhitelist
      requestedAccessScopes
      webhookApiVersion
      embedded
      posEmbedded
      preferencesUrl
      gdprWebhooks {
        customerDeletionUrl
        customerDataRequestUrl
        shopDeletionUrl
      }
      appProxy {
        subPath
        subPathPrefix
        url
      }
    }
  }

With variables:
{
  "apiKey": "c7353d54cad9749f94619f35b9fe0063"
}

With request headers:
 - User-Agent: Shopify CLI; v=3.48.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2023-08-09T14:17:44.008Z: Request to https://partners.shopify.com/api/cli/graphql completed in 1158 ms
With response headers:
 - cache-control: max-age=0, private, must-revalidate
 - content-type: application/json; charset=utf-8
 - etag: W/"61cbf690daeec7ef925efab8346af17c"
 - x-request-id: a58f34ae-1ff1-4af1-93c1-73e31735b851

2023-08-09T14:17:44.008Z: Sending "Partners" GraphQL request:
  query FindOrganization($id: ID!) {
    organizations(id: $id, first: 1) {
      nodes {
        id
        businessName
        website
      }
    }
  }

With variables:
{
  "id": "1007279"
}

With request headers:
 - User-Agent: Shopify CLI; v=3.48.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2023-08-09T14:17:44.978Z: Request to https://partners.shopify.com/api/cli/graphql completed in 966 ms
With response headers:
 - cache-control: max-age=0, private, must-revalidate
 - content-type: application/json; charset=utf-8
 - etag: W/"7232cf25e79c61c9bdeb7f284590b702"
 - x-request-id: 39a65be2-e102-473c-893c-ed9c0db3376b

╭─ info ───────────────────────────────────────────────────────────────────────╮
│                                                                              │
│  Using .env:                                                                 │
│                                                                              │
│    • Org:          Apper                                                     │
│    • App:          adaptive-supply-app                                       │
│                                                                              │
│   You can pass `--reset` to your command to reset your app configuration.    │
│                                                                              │
╰──────────────────────────────────────────────────────────────────────────────╯

╭─ warning ────────────────────────────────────────────────────────────────────╮
│                                                                              │
│  `npm run deploy` now releases changes to users.                             │
│                                                                              │
│  All your extensions will be released to users, unless you add the           │
│  `--no-release` flag.                                                        │
│                                                                              │
│  Reference                                                                   │
│    • Simplified extension deployment                                         │
│                                                                              │
╰──────────────────────────────────────────────────────────────────────────────╯

2023-08-09T14:17:45.016Z: Sending "Partners" GraphQL request:
  query allAppExtensionRegistrations($apiKey: String!) {
    app(apiKey: $apiKey) {
      extensionRegistrations {
        id
        uuid
        title
        type
        draftVersion {
          config
        }
        activeVersion {
          config
        }
      }
      dashboardManagedExtensionRegistrations {
        id
        uuid
        title
        type
        activeVersion {
          config
        }
        draftVersion {
          config
        }
      }
      functions {
        id
        uuid
        title
        type: apiType
      }
    }
  }

With variables:
{
  "apiKey": "c7353d54cad9749f94619f35b9fe0063"
}

With request headers:
 - User-Agent: Shopify CLI; v=3.48.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2023-08-09T14:17:46.102Z: Request to https://partners.shopify.com/api/cli/graphql completed in 1084 ms
With response headers:
 - cache-control: max-age=0, private, must-revalidate
 - content-type: application/json; charset=utf-8
 - etag: W/"abe70acda8e35b09e589f833b3b78664"
 - x-request-id: 1ae711d7-c5e8-4676-bf20-22c7899c828b

2023-08-09T14:17:46.125Z: Sending "Partners" GraphQL request:
  query activeAppVersion($apiKey: String!) {
    app(apiKey: $apiKey) {
      activeAppVersion {
        appModuleVersions {
          registrationId
          registrationUuid
          registrationTitle
          type
          specification {
            identifier
            name
            options {
              managementExperience
            }
          }
        }
      }
    }
  }

With variables:
{
  "apiKey": "c7353d54cad9749f94619f35b9fe0063"
}

With request headers:
 - User-Agent: Shopify CLI; v=3.48.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2023-08-09T14:17:46.924Z: Request to https://partners.shopify.com/api/cli/graphql completed in 797 ms
With response headers:
 - cache-control: max-age=0, private, must-revalidate
 - content-type: application/json; charset=utf-8
 - etag: W/"d5ea70ae5a5479d76b7523f6ab1ad796"
 - x-request-id: 8cb4db4c-0163-492e-a364-d8c421e14e87

?  Release a new version of adaptive-supply-app?
✔  Yes, release this new version

2023-08-09T14:17:48.593Z: Writing some content to file at .env...

Releasing a new app version as part of adaptive-supply-app

2023-08-09T14:17:48.596Z: Creating directory at /private/var/folders/jm/880h30n945x28pt2yk_mgjgh0000gn/T/8afd58ab56358ad97dde498c338c7dd0...
2023-08-09T14:17:48.597Z: Sync-creating directory at /private/var/folders/jm/880h30n945x28pt2yk_mgjgh0000gn/T/c4f966df40970446cc20faefcef9329a/bundle...
2023-08-09T14:17:48.597Z: Creating an empty file at /private/var/folders/jm/880h30n945x28pt2yk_mgjgh0000gn/T/c4f966df40970446cc20faefcef9329a/bundle/.shopify...
theme-extension │ Running theme check on your Theme app extension...
2023-08-09T14:17:48.606Z:
Running system process:
  · Command: ruby -v
  · Working directory: /Users/abuhasan/shopify-apps/adaptive-supply-app

2023-08-09T14:17:48.620Z:
Running system process:
  · Command: bundle -v
  · Working directory: /Users/abuhasan/shopify-apps/adaptive-supply-app

2023-08-09T14:17:48.704Z: Creating directory at ../../Library/Caches/shopify-cli-nodejs/vendor/theme-check/1.15.0...
2023-08-09T14:17:48.705Z: Writing some content to file at ../../Library/Caches/shopify-cli-nodejs/vendor/theme-check/1.15.0/Gemfile...
2023-08-09T14:17:48.706Z:
Running system process:
  · Command: bundle config set --local path /Users/abuhasan/Library/Caches/shopify-gems-nodejs
  · Working directory: /Users/abuhasan/Library/Caches/shopify-cli-nodejs/vendor/theme-check/1.15.0

2023-08-09T14:17:48.777Z:
Running system process:
  · Command: bundle config set --local without development:test
  · Working directory: /Users/abuhasan/Library/Caches/shopify-cli-nodejs/vendor/theme-check/1.15.0

2023-08-09T14:17:48.848Z:
Running system process:
  · Command: bundle install
  · Working directory: /Users/abuhasan/Library/Caches/shopify-cli-nodejs/vendor/theme-check/1.15.0

2023-08-09T14:17:48.980Z:
Running system process:
  · Command: bundle exec theme-check /Users/abuhasan/shopify-apps/adaptive-supply-app/extensions/theme-extension -C :theme_app_extension
  · Working directory: /Users/abuhasan/Library/Caches/shopify-cli-nodejs/vendor/theme-check/1.15.0

theme-extension │ Checking
/Users/abuhasan/shopify-apps/adaptive-supply-app/extensions/theme-extension ...
theme-extension │ 4 files inspected, 0 offenses detected, 0 offenses
auto-correctable
theme-extension │ Bundling theme extension theme-extension...
2023-08-09T14:17:49.217Z: Copying file from extensions/theme-extension/assets/thumbs-up.png to /private/var/folders/jm/880h30n945x28pt2yk_mgjgh0000gn/T/c4f966df40970446cc20faefcef9329a/bundle/820f3c84-c84f-4c89-96e2-56b120b1c025/assets/thumbs-up.png...
2023-08-09T14:17:49.218Z: Copying file from extensions/theme-extension/blocks/star_rating.liquid to /private/var/folders/jm/880h30n945x28pt2yk_mgjgh0000gn/T/c4f966df40970446cc20faefcef9329a/bundle/820f3c84-c84f-4c89-96e2-56b120b1c025/blocks/star_rating.liquid...
2023-08-09T14:17:49.218Z: Copying file from extensions/theme-extension/locales/en.default.json to /private/var/folders/jm/880h30n945x28pt2yk_mgjgh0000gn/T/c4f966df40970446cc20faefcef9329a/bundle/820f3c84-c84f-4c89-96e2-56b120b1c025/locales/en.default.json...
2023-08-09T14:17:49.218Z: Copying file from extensions/theme-extension/snippets/stars.liquid to /private/var/folders/jm/880h30n945x28pt2yk_mgjgh0000gn/T/c4f966df40970446cc20faefcef9329a/bundle/820f3c84-c84f-4c89-96e2-56b120b1c025/snippets/stars.liquid...

2023-08-09T14:17:49.220Z: Zipping /private/var/folders/jm/880h30n945x28pt2yk_mgjgh0000gn/T/c4f966df40970446cc20faefcef9329a/bundle into /private/var/folders/jm/880h30n945x28pt2yk_mgjgh0000gn/T/8afd58ab56358ad97dde498c338c7dd0/bundle.zip
2023-08-09T14:17:49.238Z: Ensuring that the user is authenticated with the Partners API with the following scopes:
[]

2023-08-09T14:17:49.238Z: Getting session store...
2023-08-09T14:17:49.239Z: Validating existing session against the scopes:
[
  "openid",
  "https://api.shopify.com/auth/shop.admin.graphql",
  "https://api.shopify.com/auth/shop.admin.themes",
  "https://api.shopify.com/auth/partners.collaborator-relationships.readonly",
  "https://api.shopify.com/auth/shop.storefront-renderer.devtools",
  "https://api.shopify.com/auth/partners.app.cli.access",
  "https://api.shopify.com/auth/destinations.readonly"
]
For applications:
{
  "partnersApi": {
    "scopes": []
  }
}

2023-08-09T14:17:49.239Z: Sending Identity Introspection request to URL: https://accounts.shopify.com/oauth/introspection
2023-08-09T14:17:49.239Z: Sending POST request to URL https://accounts.shopify.com/oauth/introspection
With request headers:
 - User-Agent: Shopify CLI; v=3.48.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2023-08-09T14:17:49.240Z: Getting the size of file file at extensions/theme-extension/assets/thumbs-up.png...
2023-08-09T14:17:49.240Z: Getting the size of file file at extensions/theme-extension/blocks/star_rating.liquid...
2023-08-09T14:17:49.241Z: Getting the size of file file at extensions/theme-extension/locales/en.default.json...
2023-08-09T14:17:49.241Z: Getting the size of file file at extensions/theme-extension/snippets/stars.liquid...
2023-08-09T14:17:49.575Z: Request to https://accounts.shopify.com/oauth/introspection completed in 335 ms
With response headers:
 - cache-control: no-cache, no-store, private, must-revalidate, max-age=0
 - content-type: application/json; charset=utf-8
 - etag: W/"bd2ac7e226025c232dccc9d0bffa7355"
 - x-request-id: 1629e10c-051d-438f-829d-8ff53e36315b

2023-08-09T14:17:49.576Z: The identity token is valid: true
2023-08-09T14:17:49.578Z:
The validation of the token for application/identity completed with the following results:
- It's expired: false
- It's invalid in identity: false

2023-08-09T14:17:49.578Z: Verifying that the user has a Partner organization
2023-08-09T14:17:49.579Z: Sending "Partners" GraphQL request:
  {
    organizations(first: 1) {
      nodes {
        id
      }
    }
  }

With request headers:
 - User-Agent: Shopify CLI; v=3.48.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2023-08-09T14:17:49.961Z: Request to https://partners.shopify.com/api/cli/graphql completed in 380 ms
With response headers:
 - cache-control: max-age=0, private, must-revalidate
 - content-type: application/json; charset=utf-8
 - etag: W/"7bf30bcca7e5463db2cefb197f7bf447"
 - x-request-id: db863263-fad9-4565-88cf-952ca3994c8a

2023-08-09T14:17:49.962Z: Sending "Partners" GraphQL request:
  mutation GenerateSignedUploadUrl($apiKey: String!, $appVersionUuid: String!, $bundleFormat: Int!) {
    deploymentGenerateSignedUploadUrl(
      input: {apiKey: $apiKey, appVersionUuid: $appVersionUuid, bundleFormat: $bundleFormat}
    ) {
      signedUploadUrl
      userErrors {
        field
        message
      }
    }
  }

With variables:
{
  "apiKey": "c7353d54cad9749f94619f35b9fe0063",
  "appVersionUuid": "9275b1c0-0c65-465e-9ecd-bc2d58c19fde",
  "bundleFormat": 1
}

With request headers:
 - User-Agent: Shopify CLI; v=3.48.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2023-08-09T14:17:50.654Z: Request to https://partners.shopify.com/api/cli/graphql completed in 690 ms
With response headers:
 - cache-control: max-age=0, private, must-revalidate
 - content-type: application/json; charset=utf-8
 - etag: W/"ae43d0d251b580e8492139720c957f43"
 - x-request-id: faf6d9a7-63bb-4306-9200-6b5623435c3e

2023-08-09T14:17:50.655Z: Sync-reading the content of file at /private/var/folders/jm/880h30n945x28pt2yk_mgjgh0000gn/T/8afd58ab56358ad97dde498c338c7dd0/bundle.zip...
2023-08-09T14:17:51.096Z: Request to https://partners-extensions-scripts-bucket.storage.googleapis.com/deployments/54785900545/9275b1c0-0c65-465e-9ecd-bc2d58c19fde/bundle.zip?X-Goog-Algorithm=GOOG4-RSA-SHA256&X-Goog-Credential=argo-project-sa%40shopify-tiers.iam.gserviceaccount.com%2F20230809%2Fauto%2Fstorage%2Fgoog4_request&X-Goog-Date=20230809T141750Z&X-Goog-Expires=300&X-Goog-SignedHeaders=host&X-Goog-Signature=7d3c1c663371872387bb74b07fff92c790e4bd3224a3d641a98dd9385546e94186b003c751a6d736b836c5d893c8c409d1817b436a14b37415571652d9c9f0651aab0924785517ab314c93540a960d6275122c49c5fbe32f2234667d61059a9acea45574372b3b7f2605147e524e5b11a104a2566a2ba5190c11409ae063c442ee5bfe63c600fe41c4c023726ad3b933d126ca90678d9307d26942aaca73c40afcd1321a0cc9aa63779213c3ae0e7c2ddcdbeba481cd9f80c5d25fa14302406c8bba2f618e18ac8395bbfdb1815220bdad9fb1c186c9f519e40f46273e9318725eb188266b9dc5b2f83a5499c654549e6530014b54892d16e899e08bfb41464b completed in 438 ms
With response headers:
 - content-type: text/html; charset=UTF-8
 - etag: "fc9e667715b90352d1da324a1058bcbd"

2023-08-09T14:17:51.097Z: Sending "Partners" GraphQL request:
  mutation AppDeploy(
    $apiKey: String!
    $uuid: String!
    $bundleUrl: String
    $appModules: [AppModuleSettings!]
    $skipPublish: Boolean
    $message: String
    $versionTag: String
    $commitReference: String
  ) {
    appDeploy(
      input: {
        apiKey: $apiKey
        uuid: $uuid
        bundleUrl: $bundleUrl
        appModules: $appModules
        skipPublish: $skipPublish
        message: $message
        versionTag: $versionTag
        commitReference: $commitReference
      }
    ) {
      appVersion {
        uuid
        id
        message
        versionTag
        location
        appModuleVersions {
          uuid
          registrationUuid
          validationErrors {
            message
            field
          }
        }
      }
      userErrors {
        message
        field
        category
        details
      }
    }
  }

With variables:
{
  "apiKey": "c7353d54cad9749f94619f35b9fe0063",
  "uuid": "9275b1c0-0c65-465e-9ecd-bc2d58c19fde",
  "skipPublish": false,
  "bundleUrl": "https://partners-extensions-scripts-bucket.storage.googleapis.com/deployments/54785900545/9275b1c0-0c65-465e-9ecd-bc2d58c19fde/bundle.zip?X-Goog-Algorithm=GOOG4-RSA-SHA256&X-Goog-Credential=argo-project-sa%40shopify-tiers.iam.gserviceaccount.com%2F20230809%2Fauto%2Fstorage%2Fgoog4_request&X-Goog-Date=20230809T141750Z&X-Goog-Expires=300&X-Goog-SignedHeaders=host&X-Goog-Signature=7d3c1c663371872387bb74b07fff92c790e4bd3224a3d641a98dd9385546e94186b003c751a6d736b836c5d893c8c409d1817b436a14b37415571652d9c9f0651aab0924785517ab314c93540a960d6275122c49c5fbe32f2234667d61059a9acea45574372b3b7f2605147e524e5b11a104a2566a2ba5190c11409ae063c442ee5bfe63c600fe41c4c023726ad3b933d126ca90678d9307d26942aaca73c40afcd1321a0cc9aa63779213c3ae0e7c2ddcdbeba481cd9f80c5d25fa14302406c8bba2f618e18ac8395bbfdb1815220bdad9fb1c186c9f519e40f46273e9318725eb188266b9dc5b2f83a5499c654549e6530014b54892d16e899e08bfb41464b",
  "appModules": [
    {
      "uuid": "820f3c84-c84f-4c89-96e2-56b120b1c025",
      "config": "{\"theme_extension\":{\"files\":{}}}",
      "context": ""
    }
  ]
}

With request headers:
 - User-Agent: Shopify CLI; v=3.48.0
 - Keep-Alive: timeout=30
 - Sec-CH-UA-PLATFORM: darwin
 - Content-Type: application/json

2023-08-09T14:17:51.128Z: Request to https://partners.shopify.com/api/cli/graphql completed in 26 ms
With response headers:

╭─ error ──────────────────────────────────────────────────────────────────────╮
│                                                                              │
│  request to https://partners.shopify.com/api/cli/graphql failed, reason:     │
│  80205FF001000000:error:0A0003FC:SSL routines:ssl3_read_bytes:sslv3 alert    │
│  bad record mac:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1605:SSL   │
│  alert number 20                                                             │
│                                                                              │
│                                                                              │
╰──────────────────────────────────────────────────────────────────────────────╯

2023-08-09T14:17:51.142Z: Obtaining the dependency manager in directory /Users/abuhasan/shopify-apps/adaptive-supply-app...
2023-08-09T14:17:51.144Z:
Running system process:
  · Command: ruby -v
  · Working directory: /Users/abuhasan/shopify-apps/adaptive-supply-app

2023-08-09T14:17:51.147Z: Obtaining the dependency manager in directory /Users/abuhasan/shopify-apps/adaptive-supply-app...
2023-08-09T14:17:51.148Z:
Running system process:
  · Command: ruby -v
  · Working directory: /Users/abuhasan/shopify-apps/adaptive-supply-app

2023-08-09T14:17:51.440Z: Request to https://monorail-edge.shopifysvc.com/v1/produce completed in 282 ms
With response headers:
 - x-request-id: 54904d6b-65c1-4fa0-b34b-8bfc22bb59e8

2023-08-09T14:17:51.442Z: Analytics event sent: {
  "command": "app deploy",
  "time_start":<PHONE_NUMBER>950,
  "time_end":<PHONE_NUMBER>145,
  "total_time": 9195,
  "success": true,
  "cli_version": "3.48.0",
  "ruby_version": "2.7.8",
  "node_version": "18.16.0",
  "is_employee": false,
  "uname": "darwin arm64",
  "env_ci": false,
  "env_plugin_installed_any_custom": false,
  "env_plugin_installed_shopify": "[\"@shopify/app\",\"@shopify/cli\",\"@shopify/plugin-cloudflare\",\"@shopify/plugin-did-you-mean\"]",
  "env_shell": "zsh",
  "env_device_id": "f7f338ceb56dc46287e750baf84b09c8a08d6872",
  "env_cloud": "localhost",
  "env_package_manager": "npm",
  "cmd_app_warning_api_key_deprecation_displayed": false,
  "cmd_deploy_flag_message_used": false,
  "cmd_deploy_flag_version_used": false,
  "cmd_deploy_flag_source_url_used": false,
  "project_type": "node",
  "app_extensions_any": true,
  "app_extensions_breakdown": "{\"theme\":1}",
  "app_extensions_count": 1,
  "app_extensions_custom_layout": false,
  "app_extensions_function_any": false,
  "app_extensions_function_count": 0,
  "app_extensions_theme_any": true,
  "app_extensions_theme_count": 1,
  "app_extensions_ui_any": false,
  "app_extensions_ui_count": 0,
  "app_name_hash": "741399306f1abf395ddff7774bad9f5727c358f5",
  "app_path_hash": "7c147e6db22f272ba7afcb369178554b987d9605",
  "app_scopes": "[\"write_products\"]",
  "app_web_backend_any": true,
  "app_web_backend_count": 1,
  "app_web_custom_layout": true,
  "app_web_framework": "remix",
  "app_web_frontend_any": true,
  "app_web_frontend_count": 1,
  "env_package_manager_workspaces": true,
  "cmd_app_all_configs_any": true,
  "cmd_app_all_configs_clients": "{\"shopify.app.adaptive-supply-app.toml\":\"7a186158d2311eba4455bfee070a1b05\",\"shopify.app.toml\":\"c7353d54cad9749f94619f35b9fe0063\"}",
  "cmd_app_linked_config_used": true,
  "cmd_app_linked_config_name": "shopify.app.toml",
  "cmd_app_linked_config_git_tracked": true,
  "cmd_app_linked_config_source": "cached",
  "cmd_app_deployment_mode": "unified",
  "cmd_deploy_confirm_new_registrations": 1,
  "cmd_deploy_confirm_updated_registrations": 0,
  "cmd_deploy_confirm_removed_registrations": 0,
  "cmd_deploy_confirm_cancelled": false,
  "cmd_deploy_confirm_time_to_complete_ms":<PHONE_NUMBER>925,
  "partner_id": 1007279,
  "api_key": "c7353d54cad9749f94619f35b9fe0063",
  "cmd_all_launcher": "npm",
  "cmd_all_topic": "app",
  "cmd_all_plugin": "@shopify/app",
  "cmd_all_verbose": true,
  "cmd_all_path_override": true,
  "cmd_all_path_override_hash": "7c147e6db22f272ba7afcb369178554b987d9605",
  "cmd_app_reset_used": false,
  "args": "--verbose",
  "app_name": "adaptive-supply-app",
  "env_plugin_installed_all": "[\"@shopify/app\",\"@shopify/cli\",\"@shopify/plugin-cloudflare\",\"@shopify/plugin-did-you-mean\"]",
  "metadata": "{\"extraPublic\":{},\"extraSensitive\":{}}"
}
2023-08-09T14:17:51.443Z: Completed command app deploy
2023-08-09T14:17:51.448Z: Request to https://monorail-edge.shopifysvc.com/v1/produce completed in 291 ms
With response headers:
 - x-request-id: bae870e3-65b4-4058-854c-f742757219d6

2023-08-09T14:17:51.449Z: Analytics event sent: {
  "command": "app deploy",
  "time_start":<PHONE_NUMBER>950,
  "time_end":<PHONE_NUMBER>136,
  "total_time": 9186,
  "success": false,
  "cli_version": "3.48.0",
  "ruby_version": "2.7.8",
  "node_version": "18.16.0",
  "is_employee": false,
  "uname": "darwin arm64",
  "env_ci": false,
  "env_plugin_installed_any_custom": false,
  "env_plugin_installed_shopify": "[\"@shopify/app\",\"@shopify/cli\",\"@shopify/plugin-cloudflare\",\"@shopify/plugin-did-you-mean\"]",
  "env_shell": "zsh",
  "env_device_id": "f7f338ceb56dc46287e750baf84b09c8a08d6872",
  "env_cloud": "localhost",
  "env_package_manager": "npm",
  "cmd_app_warning_api_key_deprecation_displayed": false,
  "cmd_deploy_flag_message_used": false,
  "cmd_deploy_flag_version_used": false,
  "cmd_deploy_flag_source_url_used": false,
  "project_type": "node",
  "app_extensions_any": true,
  "app_extensions_breakdown": "{\"theme\":1}",
  "app_extensions_count": 1,
  "app_extensions_custom_layout": false,
  "app_extensions_function_any": false,
  "app_extensions_function_count": 0,
  "app_extensions_theme_any": true,
  "app_extensions_theme_count": 1,
  "app_extensions_ui_any": false,
  "app_extensions_ui_count": 0,
  "app_name_hash": "741399306f1abf395ddff7774bad9f5727c358f5",
  "app_path_hash": "7c147e6db22f272ba7afcb369178554b987d9605",
  "app_scopes": "[\"write_products\"]",
  "app_web_backend_any": true,
  "app_web_backend_count": 1,
  "app_web_custom_layout": true,
  "app_web_framework": "remix",
  "app_web_frontend_any": true,
  "app_web_frontend_count": 1,
  "env_package_manager_workspaces": true,
  "cmd_app_all_configs_any": true,
  "cmd_app_all_configs_clients": "{\"shopify.app.adaptive-supply-app.toml\":\"7a186158d2311eba4455bfee070a1b05\",\"shopify.app.toml\":\"c7353d54cad9749f94619f35b9fe0063\"}",
  "cmd_app_linked_config_used": true,
  "cmd_app_linked_config_name": "shopify.app.toml",
  "cmd_app_linked_config_git_tracked": true,
  "cmd_app_linked_config_source": "cached",
  "cmd_app_deployment_mode": "unified",
  "cmd_deploy_confirm_new_registrations": 1,
  "cmd_deploy_confirm_updated_registrations": 0,
  "cmd_deploy_confirm_removed_registrations": 0,
  "cmd_deploy_confirm_cancelled": false,
  "cmd_deploy_confirm_time_to_complete_ms":<PHONE_NUMBER>925,
  "partner_id": 1007279,
  "api_key": "c7353d54cad9749f94619f35b9fe0063",
  "cmd_all_launcher": "npm",
  "cmd_all_topic": "app",
  "cmd_all_plugin": "@shopify/app",
  "cmd_all_verbose": true,
  "cmd_all_path_override": true,
  "cmd_all_path_override_hash": "7c147e6db22f272ba7afcb369178554b987d9605",
  "cmd_app_reset_used": false,
  "args": "--verbose",
  "error_message": "request to https://partners.shopify.com/api/cli/graphql failed, reason: 80205FF001000000:error:0A0003FC:SSL routines:ssl3_read_bytes:sslv3 alert bad record mac:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1605:SSL alert number 20\n",
  "app_name": "adaptive-supply-app",
  "env_plugin_installed_all": "[\"@shopify/app\",\"@shopify/cli\",\"@shopify/plugin-cloudflare\",\"@shopify/plugin-did-you-mean\"]",
  "metadata": "{\"extraPublic\":{},\"extraSensitive\":{}}"
}

I have the exact same brew openssl version, so maybe it's related to the downloaded certificates. If you open the Keychain app and search for "Shopify" certificates, can you see anything expired?
Another thing you could check is your current system time. I think incorrect values can cause SSL errors.

I don't have any certificate for "Shopify". Can you guide me to create/get certificate?

Hmm I've tried deleting my certificates and the deploy command still works for me, so I guess it has nothing to do here.
It's also weird that all your previous requests to Partners do work, but it only fails with the last one (the deploy itself)... Let me ask internally about this.

I'm a bit lost. They say here that it's likely to be a network problem on your end. Could you try with a different connection, proxy, firewall, antivirus, computer...?

@hasanm95 what was the solution? We are encountering the same issue


[Feature] add ability to set docker labels on worker nodes

Some service discovery systems are using docker labels to configure DNS, load-balancing, monitoring, metering ... (ie. dalidock , traefik ...).
This PR introduce ability to set arbitrary docker labels for worker nodes using a new --label argument to k3s create and k3d add-node.

Hi @lionelnicolas , thank you for contributing!
This seems to be a fairly small change compared to the value it adds when combined with services like the two you mentioned :+1:
Just one small note: I think that the flag name --label could be misunderstood in a way that people think it can be used to add Kubernetes node labels. Not sure if we should account for this :thinking:

@iwilltry42 That's a good point.
I put "docker labels to every node container" in the help message for that reason, but it may not be sufficient.
We could use --docker-label instead (and drop the -l short flag).
My initial thought was that the existing --volume and --env arguments were not including docker, so I did the same for consistency.
Other suggestion, the docker-run manpage shows:
       -l, --label key=value
          Set metadata on the container (for example, --label com.example.key=value).

So maybe we could use --metadata instead of --label ?
Please tell me what you prefer, and I'll make the changes :wink:

@lionelnicolas , nah, let's stick with --label, it makes more sense in the k3d context, you're right there :+1: We won't set Kubernetes node labels anyway :+1:


Milestone 1 - Implement all  "Group tasks"

In this branch we implement:

We create an Item class in a separate .rb file.
All Item class properties visible in the diagram should be defined and set up in the constructor method. Exception: properties for the 1-to-many relationships should NOT be set in the constructor method. Instead, they should have a custom setter method created.
We add all methods visible in the diagram.
We implement methods:

can_be_archived?() in the Item class

should return true if published_date is older than 10 years
otherwise, it should return false

move_to_archive() in the Item class

should reuse can_be_archived?() method
should change the archived property to true if the result of the can_be_archived?() method is true
should do nothing if the result of the can_be_archived?() method is false

We create a main.rb file that will serve as your console app entry-point.
We implement startup actions:

Present the user with a list of options to perform.
Let users choose an option.
If needed, ask for parameters for the option.
Have a way to quit the app.

Hi @mukhammadrizooff @sumairq  ,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉

Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.


fails when running npm test

Hi
I'm using nyc with mocha and coveralls
I've setup my .travis.yml and package.json as specified on the readme
The test is passing on travis and test coverage are send to coveralls.
But when I do npm test on my computer, it fails
><EMAIL_ADDRESS>test C:\perso\node-annotation-parser
> nyc mocha

events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: spawn mocha ENOENT
    at exports._errnoException (util.js:746:11)
    at Process.ChildProcess._handle.onexit (child_process.js:1053:32)
    at child_process.js:1144:20
    at process._tickCallback (node.js:355:11)
    at Function.Module.runMain (module.js:503:11)
    at startup (node.js:129:16)
    at node.js:814:3
npm ERR! Test failed.  See above for more details.

The repo: https://github.com/mastilver/node-annotation-parser

CC: @isaacs seems like our shebang logic is having trouble with Windows.
You might try explicitly specifying the path to the mocha bin:
./node_modules/.bin/nyc ./node_modules/.bin/mocha test

I've set test by ./node_modules/.bin/nyc.cmd ./node_modules/.bin/mocha.cmd
It's now outputting:
><EMAIL_ADDRESS>test C:\perso\sails-hook-annotation-router
> nyc.cmd ./node_modules/.bin/mocha.cmd

'.' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! Test failed.  See above for more details.

I've tested the same on linux, it does work.
Unfortunately I need to stick with windows for my job. :/

Interesting!
I'm not super surprised that it doesn't work on Windows.  There's some deep and strange unixy stuff going on.  But I wonder where the error actually lies.
I'll try to spin up a VM soon.  Either spawn-wrap is just busted on Windows (my guess), or it's something specific to do with how nyc is invoking it.

I'm getting a failure on my Windows CI machines that might be related to this. The stack trace might be slightly more useful than the above:
child_process.js:1162
    throw errnoException(err, 'spawn');
          ^
Error: spawn UNKNOWN
    at exports._errnoException (util.js:746:11)
    at ChildProcess.spawn (child_process.js:1162:11)
    at ChildProcess.spawn (D:\workspace\strongloop-license.pr\412f199f\node_modules\tap\node_modules\nyc\node_modules\spawn-wrap\index.js:143:18)
    at exports.spawn (child_process.js:995:9)
    at module.exports (D:\workspace\strongloop-license.pr\412f199f\node_modules\tap\node_modules\foreground-child\index.js:12:15)
    at Object.<anonymous> (D:\workspace\strongloop-license.pr\412f199f\node_modules\tap\node_modules\nyc\bin\nyc.js:54:5)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)

That is the result of running tap --bail --save fails.txt --coverage test/test-*.js in a subshell that has $(pwd)/node_modules/.bin injected into the PATH.

@rmg @mastilver I don't currently have a Windows testing environment, but I will try to get one up and running soon. It would be nice to try to get things at least partially working with Windows.

For me, nyc npm test still fails on Windows, but now, I get another error.
I suspect it's because the argv variable is wrong, but I'm not sure...

@motapc97 :-(
What about nyc ./test/mota-test.js or nyc ./node_modules/.bin/grunt buildTest?

As you can see, the first command doesn't fail, but I find no coverage output :(

Sorry, but I keep getting errors...


Feature request: Consistent hashing on value other than address

Given a config similar to this:
static_resources:
  listeners:
  - address:
      socket_address:
        address: <IP_ADDRESS>
        port_value: 80
    filter_chains:
    - filters:
      - name: envoy.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          codec_type: auto
          stat_prefix: thing
          route_config:
            name: local
            virtual_hosts:
            - name: service
              domains:
              - "*"
              routes:
              - match:
                  prefix: /
                route:
                  cluster: peers
                  hash_policy:
                    header:
                      header_name: some-header
          http_filters:
          - name: envoy.router
  clusters:
  - name: peers
    type: STRICT_DNS
    dns_lookup_family: V4_ONLY
    dns_refresh_rate: 5s
    lb_policy: MAGLEV
    connect_timeout: 0.5s
    load_assignment:
      cluster_name: peers
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: foo.default.svc.cluster.local
                port_value: 8080

It's impossible to actually achieve consistent hashing around the peers cluster with the defined hash_policy as instances come and go. This specific example is using pointing at a StatefulSet in Kubernetes.
What that means, is we have a DNS record of foo.default.svc.cluster.local which is a CNAME for foo-{0..N}.foo.default.svc.cluster.local.
In Kubernetes, a StatefulSet is guaranteed to have the same hostnames, but they'll obviously get different IP addresses for each Pod.
Routing and hashing within the cluster is determined by the ultimate address of the server (the ip:port) pairs.
Even if we didn't use DNS for discovery, and we introduce a hardcoded list of endpoint records that point the individual hostnames, hashing is still broken as soon as the IP changes.
I'm not sure exactly how we can work around this in envoy infrastructure, but ideally, there'd be some option to choose how to determine the hash. In my case, ideally I'd use the hostname, not the IP:port. Alternately, adding a name field to each endpoint would be useful if you spell out exactly what the hosts are. This obviously breaks the ability to do service discovery.
Through every measure I can find, there's no way to accomplish consistent hashing while leveraging any form of service discovery, unfortunately.
Am I missing something, or does the feature request make sense?

cc @HenryYYang

I think this is a dup of https://github.com/envoyproxy/envoy/issues/9074. See also partial PR https://github.com/envoyproxy/envoy/pull/9433. If you agree can we close this and track in the other issue?

Ah yes, that sounds identical to what I'm looking for as well. Thank you! <3


trying to style custom elements but not seeming to work...

trying to style the 'carousel' and 'slide' custom elements that vue-carousel exposes but it does not seem to be working very well...dunno what I'm doing wrong here... I imported the component globally then added it to my app component, then in the styles section of the app component i added carousel and slide selectors and gave them bg colors to test, but the colors are not showing up at all...not sure what to do next at this point.
Please help, if possible, thank you :-)

Hey @rchrdnsh if you don't mind posting some code + steps to reproduce the issue, I bet I, or some of the contributors here, could help you out 😄

@rchrdnsh Found the solution on issue https://github.com/SSENSE/vue-carousel/issues/14 to be working.


SW-6179 Added None category for internal interest

The requirement has updated to be not notifying unless a category is selected. Terraware will now expect Global users to opt-into every category if they expect to receive every notificaiton

#2615  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Nov 20, 6:05 PM EST: A user merged this pull request with Graphite.


Asset migration guide

Hi,
First off, thank you for making this public, i have managed to get it working using this project however i have tried migrating the webview to a different project but without success. I have seen you have some videos on youtube can you create a quick video about how to properly migrate the webview and keyboard to a different project, pretty please? Thank you!

👍I'll make it after the current work settles down. Just a moment, please.

you are a god, thank you very much

Sorry for the delay. please refer to this video.
https://youtu.be/_Tj6pHsAz6M

Sorry for 6M
the delay. please refer to this video.
https://youtu.be/_Tj6pHsAz6M
Bless you soul :D

Coffe on it's way


fix typo in catalog type data source error message

👋 This fixes a typos incorrectly referring to the "User" data source in a catalog type data source error message.
Thanks!

Thanks for finding this!


Named DataFrame indices shouldn't introduce an empty row between header and data

When showing Values of a DataFrame with a named index, it introduces an empty row between header and data. There's no reason for it though, and pd.to_excel() doesn't do it either (even if there's additionally a df.columns.name!). So currently, you'd have to do df.reset_index() to format it correctly.

If you try the same example on standard jupyter environment, you will see the exact same space allocated. I do not see this as an issue.

That's right, because Jupyter notebooks leave space for a potential columns name, but that concept doesn't really translate to Excel (see e.g., Excel tables).


[WIP] Skip tile instead of zone in quantization

The current code skips an entire zone if turf.intersect fails for a single tile within that zone.
For America/Chicago zone, turf.intersect with 53/104/8 fails with the following error:
unable to assign hole to a shell [ (-105.22637, 30.79939) ]

The remaining tiles that hasn't been processed are therefore skipped over, as a result some tiles in that zone are missing.
This PR fixes this by catching the problematic tile rather than an entire zone.
cc @tcql

I generated a new timezones.json lookup table in https://github.com/mapbox/timespace/pull/7/commits/3ff68e0501053bb614bbff2928e45670f4a5ba38. This lookup table is still missing tile 53/104/8 because of the turf.intersect problem. Debugging/fixing this will take a bit more time. I'm going to merge this PR and publish a patch so that at least the good costal tiles are in the lookup table, and circle back to this problematic tile later.


Implement LUMIGO_SWITCH_OFF support

If LUMIGO_SWITCH_OFF env var is set to true, no instrumentation is installed, no exporters, tracer providers, resource detectors are registered.

We need to add logging for the switch-off, like in https://github.com/lumigo-io/opentelemetry-python-distro/blob/943847ffac919f7fe3a60adce90b3640a151786e/src/lumigo_opentelemetry/init.py#L74, and test for it.
Also, we need to log like https://github.com/lumigo-io/opentelemetry-python-distro/blob/943847ffac919f7fe3a60adce90b3640a151786e/src/lumigo_opentelemetry/init.py#L85 (including Lumigo distro version) if the tracer does get activated.


D3D11 Incorrect depth in example 22

Steps to reproduce:

reposition the cubes in example 22 xz plane like this
	mtx[12] = -15.0f + float(xx)*3.0f;
	mtx[13] = 0.0f;
	mtx[14] = -15.0f + float(yy)*3.0f;

start example 22

press c to create a new window

observe that you can see through the cubes in the new window

Note: Win7, D3D11

Should be fixed, try latest.

Thank you, it works.


ollama documentation is unclear

Is there support for local ollama models? It seems so from the home page, but it's unclear what config to use. This does not work for example:
clients:
  - type: ollama
    api_base: http://localhost:11434/api
    models:
      - name: codellama
      - name: llava

If you've used aichat before and checked its generated config.yaml, you'll never say it unclear.
Initialize with ollama when you first run aichat
> No config file, create a new one? Yes
> Platform: ollama
> API Base: http://localhost:11434
> API Key:
> Model Name: codellama
> Max Tokens: 4096
✨ Saved config file to <CONFIG_DIR>/aichat/config.yaml

NOTE: The #276 will be available in the next release. It is not included in the current latest version v0.11.0. To try out the ollama early, you need to manually compile the project.


Hiden icon

Description of the new feature / enhancement
perfect multipurpose application, but it bothers the icon, there is a way to keep it active, but with the hidden icon, I don't want to see it even in the hidden icons by displaying the arrow next to the clock.
thank you
Scenario when this would be used?
takes up space from my other icons
Supporting information
there are applications that allow you to hide their icons and continue working with them

/dup https://github.com/microsoft/PowerToys/issues/9526


4.24 -> 4.25 Error Fixes

Please change: Developer to DeveloperTool in your .uplugin file.

Done for all versions above 4.23.


[Fix #36] Rake/Desc should not generate offense for prerequisite declarations

Closes #36

CI should be fixed in https://github.com/rubocop/rubocop-rake/pull/38
I'll rebase this branch once #38 is merged.

@koic Rebased.


Draft: Optimize csrsv

Summary of proposed changes:

"Optimize csrsv: scalarize wid" helps the compiler generate faster code. When wid is a scalar value (and pointers are const and restricted), it is possible to use scalar loads instead of vector loads for row, row_begin, row_end.
(Perhaps it's better to wrap it as a template function).
With this change we observe -5% of csrsv_kernel's duration in one application.
"Optimize csrsv: pack "done" flags (32 per uint)" reduces the amount of memory to load when some lanes depend on neighboring rows so they can load one common uint instead of unique uints. Also less memory (32x) is need to be cleared.
About -15% of csrsv_kernel's duration in one application.

All changes are independent, I can split them into separate PR if you want.

Hello and thanks for the PR! I ran some performance benchmarks using this PR and got the following results:
dcsrsv_MI100_bandwidth_asic2.pdf
dcsrsv_MI100_msec_log_asic2.pdf
dcsrsv_MI200_bandwidth.pdf
dcsrsv_MI200_msec_log.pdf
scsrsv_NAVI21_bandwidth.pdf
scsrsv_NAVI21_msec_log.pdf
What this seems to indicate is that while for some matrices a speed-up can be seen, for many the proposed changes seem to result in a slow down. I think the reason for this might be that because atomics operate on bytes and not bits, then any row/columns in the done array that happen to land in the same int32 end up competing when calling the atomicOr. With this in mind I tried changing your lines:
constexpr unsigned int done_bits = CHAR_BIT * sizeof(unsigned int);
to
constexpr unsigned int done_bits = CHAR_BIT * sizeof(uint8_t);
which at least then gives each row/column in the done array its own byte (rather than bit). This seems to help, but still is often slower then the original code. Given this, do you mind splitting up the PR into three? I think we want the log changes and probably the loading of wid into scalar registers but the changes to the done array may require some more investigation and/or tweeking to see if we can improve the performance more consistently. By having the loading of wid into scalar registers isolated to its own PR, I can also more easily benchmark that change in isolation.

Extracted an independent change: https://github.com/ROCmSoftwarePlatform/rocSPARSE/pull/268

I spent some time trying to understand why some cases become faster, others - slower.
Atomic conflicts can't be the cause because atomicOr(..., 0) is optimized to globally coherent load (global_load_dword ... glc,). And atomics that set the done flag called very rarely compared to reading done flags.
I took 3 different cases from rocSPARSE test matrices (ASIC_320k, rma10, bmw3_2) and 2 cases from PETSc.

One of big differences is that PETSc cases are more "uniform": each row has at most 27 values, there are no "bottleneck"-rows (when multiple rows depend on one row, or vice versa, a row depends on multiple rows). As a result, most lanes don't wait for other rows to finish for thousands of iterations.
The most interesting case is rma10: it is almost 3 times slower with my changes!
Here are omniperf results for this case.
Original code:

My changes:

Th number of L1-L2 reads ("Rd:" between "Vector L1 Cache" and "L2 Cache") becomes 3.3x smaller but L2 latency ("L2 Cache: Latency") is 8x higher! It seems that are more channel conflicts. At least that's how I understand why latency is so high and "Stalled on L2 Data" is >90%.
As an experiment, I checked how atomicOr(&done_array[local_col / done_bits * 32], 0) would perform (https://github.com/StreamHPC/rocSPARSE/tree/opt_csrsv_mul32):

It's interesting that this change returns the original performance (see the table, column opt_csrsv_mul32). Though it also mostly cancels improvements for PETSc cases.
ASIC_320k, on the other hand, has non-uniform numbers of request per channel and very high latency for both branches (develop and mine). It may be explained by a row which is a dependency of many other rows, but I'm not sure:

If you want to check omniperf results for other cases, I'm attaching screenshots: omniperf-screenshots.zip
Another observation: csrsv_analysis_lower_kernel seems significantly faster than csrsv_kernel for rma10 and ASIC_320k. I wonder why. csrsv_kernel should process rows in a more optimal order that the original order used by csrsv_analysis_lower_kernel. Could it be that with the original order there are less channel conflicts? Or is it something else?
I don't know if my observation have any use. Please share your ideas why it works this way.
It doesn't seem that there is a solid condition for choosing one approach or another for any matrix. Now I understand what you have to deal with: it's really difficult to cover all possible cases with the best performance :)
Also, I've pushed wid "scalarization" commit here: https://github.com/StreamHPC/rocSPARSE/tree/scalar_wid
If you have time it would be great to benchmark it.

Does it make a difference when swapping atomicOr() with __hip_atomic_load() and __hip_atomic_store()?
We have checked the wid scalarization. If you can file a PR with it, I will merge it. You can skip the if condition btw, logical and hardware wavefront size will always match in this case.

Performance for scalar_wid (not I removed the if statement when measuring as per Nico's comment)
scsrsv_MI100_bandwidth_asic2.pdf

Does it make a difference when swapping atomicOr() with __hip_atomic_load() and __hip_atomic_store()?

__hip_atomic_load(&done_array[local_col], __ATOMIC_RELAXED, __HIP_MEMORY_SCOPE_AGENT) produces exactly the same ISA as atomicOr(&done_array[local_col], 0):
global_load_dword v16, v[6:7], off glc

(as I expected).
__hip_atomic_store(&done_array[row], 1, __ATOMIC_RELAXED, __HIP_MEMORY_SCOPE_AGENT) leads to
global_store_dword v[2:3], v0, off

compared to atomicOr(&done_array[row], 1)'s:
global_atomic_or v[2:3], v0, off

global_store_dword seems just a bit faster but I can't say for sure if it is not a fluctuation.
The same instruction can be produced with atomicOr(&done_array[row], -1) (all bits are set, any_value | -1 == -1 , so the compiler optimizes atomic min as store).

We have checked the wid scalarization. If you can file a PR with it, I will merge it. You can skip the if condition btw, logical and hardware wavefront size will always match in this case.

Done.


Filter specific entity requests by tag

A request /mdq/aaf-edugain-export/entities will return every entity we're exporting to eduGAIN. That's great! What's not so great is that a request for /mdq/aaf-edugain-export/{sha256}xyzabc will return the xyzabc entity regardless of whether we're exporting it to eduGAIN or not. SAML service just ignores the prefix and returns any entity in it's database.
This commit changes the behaviour so that it only returns an entity under a specific tag if the entity actually has that tag.
This is useful for the FR -> FM migration so we can confirm whether SAML service is aware of FM's copy of the data.

Great work @matthew-puku !
I've already noticed this issue before - great to see it fixed!


PHPORM-180 Keep createOrFirst in 2 commands to simplify implementation

Fix PHPORM-180
Alternative to #2980
Revert optimisation from #2742 in order to keep all the processes from Eloquent and simplify maintenance.
The main feature difference is that it's requiring a unique index whereas my previous implementation was only using the filter "attributes". This new implementation is closer to Laravel's implementation, it only remove the nested transaction and catch the MongoDB exception instead of the PDO exception.
Checklist

[ ] Add tests and ensure they pass
[ ] Add an entry to the CHANGELOG.md file
[ ] Update documentation for new features

Unfortunately, that doesn't solve the nested transaction issue reported initially #2720.
MongoDB\Driver\Exception\CommandException: Transaction with { txnNumber: 1 } has been aborted.


Using WinRT using plain C

Hey there!
I am working on a small library , which is similar to GLFW, for myself. It is also written in C. I am looking to extend its capabilities to create WinRT windows.
My question is naturally: can WinRT application be developed using plain C (perhaps using COM)?
If so, where could I start? Can anyone point me to some examples?

It's certainly possible, but highly impractical. API calls are really COM interface calls that are just collections of virtual functions. You could create a struct in C with a bunch of function pointers or simply offset the address of the function pointers, but it is very tedious. A simpler approach might be to use C++/WinRT to make the API calls and then wrap that behind a C-style API that you can call from your C code.


404 error

"Installing Visual Studio for Mac" on left menu returns 404 error
href link : https://docs.microsoft.com/it-it/visualstudio/mac/installation/)%20(Installazione%20di%20Visual%20Studio%20per%20Mac
In the same menu there is a problem with "Istruzioni di configurazione del firewall" link

Dettagli del documento
⚠ Non modificare questa sezione. È necessaria per i collegamenti relativi ai problemi tra docs.microsoft.com ➟ GitHub.

ID: 802a751e-ac74-cb5b-3a40-33044df2c46e
Version Independent ID: e27cba22-ffae-dd13-3556-ab39fe41213c
Content: Installazione - Xamarin
Content Source: docs/cross-platform/get-started/installation/index.md
Service: unspecified
GitHub Login: @asb3993
Microsoft Alias: amburns

Hey @EnricoTirotta, thanks for your report! We're working on fixing this. In the meantime, if you need to install (or know more about) Visual Studio for Mac you can find the information here: https://docs.microsoft.com/en-us/visualstudio/mac/installation

Thank you @EnricoTirotta for reporting. I am International PM and have requested the fix. This should be fixed in few days.

This has now been fixed - thanks for your feedback!


Better dbump_pg

Codecov Report
Patch and project coverage have no change.

Comparison is base (74ab126) 85.99% compared to head (02dee8a) 85.99%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #10   +/-   ##
=======================================
  Coverage   85.99%   85.99%
=======================================
  Files           2        2
  Lines         257      257
=======================================
  Hits          221      221
  Misses         25       25
  Partials       11       11

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


[BUG] org.opensearch.repositories.s3.RepositoryS3ClientYamlTestSuiteIT/test {yaml=repository_s3/20_repository_permanent_credentials/Snapshot and Restore with repository-s3 using permanent credentials} flaky: randomizing basePath

Signed-off-by: Andriy Redko<EMAIL_ADDRESS>
Description
Fixing org.opensearch.repositories.s3.RepositoryS3ClientYamlTestSuiteIT/test {yaml=repository_s3/20_repository_permanent_credentials/Snapshot and Restore with repository-s3 using permanent credentials} flaky by randomizing basePath
Issues Resolved
Closes https://github.com/opensearch-project/OpenSearch/issues/5219
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[X] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@reta FYI, I have seen failures in use-cases other than Snapshot and Restore... inside  20_repository_permanent_credentials.yml in case you want to update the title.

@reta FYI, I have seen failures in use-cases other than Snapshot and Restore... inside 20_repository_permanent_credentials.yml in case you want to update the title.

Thanks @dreamer-89 , I think we could keep it like that (just to not push another commit if you don't mind), the related issue has a number of failure patterns.


[IQE] : [Ctrl/Cmd +(Shift) + Tab] for file traversing doesn't work on MAC

Steps To Reproduce:

Launch Brackets
Open and edit some files in the Working set
Use [Ctrl/Cmd +(Shift) + Tab] Shortcut to traverse files

Result: Doesn't work on MAC
ENV : Release 1.4 build 1.4.0-16190 (master e35f2a4)
OS- MAC 10.10.02

@rawat11 This works for me. Try resetting the preferences and see if that fixes the issue.

@nethip but this worked on windows without setting any prefernces. Do we have to set preferences for MAC

Yes it worked with (Cmd+shft+])


Update using_directives to 1.1.4

About this PR
📦 Updates org.virtuslab:using_directives from 1.1.3 to 1.1.4
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (1.1.3).
You might want to review and update them manually.
modules/core/src/main/scala/scala/build/internals/Licenses.scala
website/docs/guides/advanced/internals.md
website/docs/reference/scala-versions.md
website/docs/release_notes.md
website/static/img/complete-install.svg
website/static/img/dark/complete-install.svg
website/yarn.lock

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.virtuslab", artifactId = "using_directives" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.virtuslab", artifactId = "using_directives" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

Superseded by https://github.com/VirtusLab/scala-cli/pull/3381


Upgrade to webpack v5

The update of ts-loader #13  (which is needed for other deps) requires webpack v5. Apart from this its a good idea to upgrade anyway
https://webpack.js.org/migrate/5/

Probably fixes https://github.com/JabRef/JabRef-Word-Addin/issues/461


Add Xcode 14.3 / Swift 5.8

Update PackageList project

[ ] ci.yml

[ ] issues.yml
[ ] nightly.yml

example: https://github.com/SwiftPackageIndex/PackageList/pull/2717/files

Update PackageList-Validator (optional)

[ ] bump Swift version

Update build machines

[ ] Install latest Xcode version

[ ] mb3
[ ] mb4
[ ] mb5

Linux builders don't require updates because they pull docker images. However, the release tag must be available before deploying a new builder referencing it.

Update SPIManifest project

[ ] New major or minor Swift versions must be defined in SPIManifest's SwiftVersion enum before they can be used in the builder or server.
example: https://github.com/SwiftPackageIndex/SPIManifest/pull/5/files

Update builder binary

[ ] Update SPIManifest dependency
[ ] Update SwiftVersion.xcodeVersion
[ ] Update SwiftVersion.dockerImage
example: https://gitlab.com/finestructure/swiftpackageindex-builder/-/merge_requests/100/diffs

Update Server

[ ] Update SPIManifest dependency
[ ] Update SwiftVersion+Build.swift
[ ] Update PackageShow.Model.SwiftVersionResults

[ ] new property
[ ] update init
[ ] update cells
[ ] fix compiler errors
[ ] update tests

[ ] Remove builds for old Swift versions (if applicable)
https://github.com/SwiftPackageIndex/SwiftPackageIndex-Server/pull/1646/files

Update spi-images

[ ] Add or remove the Swift version from the image build matrix

Either as part of this or as a separate stage afterwards, we can remove Swift 5.4, which would free up mb3 to become a Ventura build machine and mean we only have to maintain two different macOS versions rather than three.

We should do this while adding 5.8. It makes adjusting all the test expectations easier when we're just shuffling them around. Otherwise we'll have to do considerable structural changes twice.

@finestructure Can I work on that?

Thanks for your offer to help out with this one, @ahmdyasser!
This is probably one of the fiddliest things we do twice a year and it has to be me who does it, I'm afraid 😅
However, we do still have a couple of good first issues that might be a great way to contribute. Would one of those interest you?

Swift 5.8 processing is under way. Remaining todos tracked here: https://github.com/SwiftPackageIndex/SwiftPackageIndex-Server/issues/2323


[FEATURE] ADD BETTER FRONTEND AND FAST API

Feature description

please consisely describe the feature that you'd like to see here.
it will be better for and better api and forntend for netblox

Argumentation

why does this feature have to exist in the first place?
it helps other players to play games and be happy

Additional context

what do you think can be helpful for us when implementing this feature?
making it esay to start and make game in netblox

if you mean the public service, then its not the priority. current thing is want to implement normally is physics, and maybe then i will start working on the PS. everything will come, please wait

@AsertCreator ok but how long will it take will it take a year or so

can u add /user/id and /register when not login in and /create/game/id


Deployment documentation needs to show Seamless mode first, rather then classic "simple"

https://6.dev-docs.plone.org/volto/deploying/simple.html

That link goes to Simple deployment. The word "seamless" does not appear on that page.
Do you mean to reorder the items in the navigation under Deploying instead?

yes this link goes to Simple deployment. the Word does not appear in that page
@tiberiuichim

@stevepiercy yes, it should not be first in the navigation, and it should clearly state that is "install Volto on older Plone without access to plone.rest 2.0".

@tiberiuichim would you prefer this order?

Seamless mode
Simple deployment
Deployment using a node process manager (PM2)
Apache
Integration with Sentry
critical.css (above the fold) optimizations

Should Simple deployment have a deprecation warning at the top, like so? Please provide specific details as needed.

Deprecated
This installation method requires plone.restapi < 2.0.
It is recommended only for Plone 5.2 and older.
For Plone 6 and later, use Seamless mode.

The whole thing has to be refactored. "Simple deployment" information is relevant, but the https://6.dev-docs.plone.org/volto/deploying/simple.html#reverse-proxies needs to be updated, it should be just a "hey, this is also how you can do it", just a note in the new docs.
I'll try to refactor this today, I may find 30 minutes to do so.

hi @tiberiuichim, I want to work on this issue if the changes are still required, if you can kindly help me what do I need to amend in reverse-proxies section under "hey, this is also how you can do it" I am happy to contribute.

@aniasusual thank you for your interest. But, sorry, this issue was incorrectly tagged as 41 level: easy (probably at first thought) and is actually 41 level: complex (now that @tiberiuichim explained the complexity), and requires someone deeply familiar with Volto to refactor the entire section.


Improvements to linear models

The current techniques used in the linear models are sub-par and numerically unstable. There are better techniques available that we should use. This is most notably an issue for the GLM module - but improvements can be made in the linear model and logistic model as well (which are of course special cases).
The current implementations are as follows:

Linear regression : compute (X.t * X)^-1 * X.t * y
Logistic regression : we use gradient descent in the logistic_reg module
General Linear Models : we use a naive IRLS implementation which again computes inverses directly.

We should focus on improving GLM's as the issues crop up very often here. The GLMs, abridged article provides a great overview of GLMs in R - we can make good use of this as a resource for rusty-machine. Rulinalg provides all the techniques we need - though of course without the performance given by BLAS/LAPACK.
For linear regression we can also make use of better techniques to solve the least squares problem. More research needed here.
Finally we should add Regularization to the linear models. The learning::toolkit::regularization model should do most of the work for us - though this was designed for neural nets and may need some changes.

I'd like to help!
I'm quite new to ML, but would like to have a stab at Levenberg-Marquardt optimisation (or similar). At a glance, the maths doesn't seem too difficult, so if this sounds like a useful contribution I'll get started on it. From what I understand, this could significantly outperform vanilla GD on linear and logistic regression (and neural net).

Thank you for your comment! I hadn't heard of the Levenberg-Marquardt algorithm before you suggested it here. It looks like it could be a valuable addition to the linear and logistic regression models. However from my own reading I'm not sure whether this would be a stable alternative in some of the more tricky GLMs (as described in the aforementioned article). That said - if you're happy to try and get this implemented I would be glad to review it!
As a final thought. It might be worth trying to be generic over the underlying algorithm. This would make it easy for us to compare them across different models and provide options to our users for those cases where different algorithms are needed. This is probably quite a big task which we can put off for now.

I'm pretty new to Rust, but would be interested in contributing if I'm able. For linear regression, one option is using one of the orthogonal decomposition-based methods, as described here or here, with a bit on performance and numerical stability for QR and Cholesky methods here here.
So, if that's an option of interest, I'd be interested in at least trying to implement something.

Hey @phasedchirp !
I think this sounds like a promising approach. If you have the time it would be great to see an implementation of this (alongside some benchmarks and accuracy comparisons, where possible). I'm fairly busy over the next few weeks but I'll do my best to be available for any questions you might have. The gitter channel is probably the best place but feel free to comment here too.

@AtheMathmo Cool. I've got a rough first pass using the QR method, which seems to be working not terribly (passes test_regression, fails test_regression_datasets_trees, but with differences on the scale of less than 1e-11 for parameters and predictions), but it will need a lot of cleaning up, so I'll work on that/putting together appropriate tests/comparisons.

As with @phasedchirp, I'm new to Rust (cloned some repos and that's about it :)) .  But anxious to contribute and I think a statistics / machine learning library might be my best bet.
For linear regression using least-squares, QR and Cholesky is usually the way to go with some special cases for certain matrix structures.  I believe this is what the \ operator does in Julia.

How much worse in accuracy do you think the current implementation of logistic regression should be vs. R's glm()?
I just trained a model with 7 features and 20 million samples, and the calibration of the results seems to be far worse than R.  Is that to be expected for now or should I investigate further?


Seleno - TypeInitializationException

Hello All,
I've run across an odd exception in working with TestStack.Seleno. Full disclosure, this is my first real run using the utility. I'm working on a functional acceptance test using Seleno, and the application configuration in SelenoHost.Run() is failing with a System.TypeInitializationException, not the DirectoryNotFound exception I'm expecting.
Before I get too far ahead of myself. I'm using Seleno in an xUnit.NET test project targeting .Net 4.5, and using the latest releases of Seleno, the Selenium helper libraries, and xUnit.NET from NuGet.
Here's the host configuration, it's essentially borrowed from the getting started documentation.
public static class Host
    {
        public static readonly SelenoHost Instance = new SelenoHost();

        static Host()
        {
            Instance.Run("GroundControl.Mvc.AcceptanceTests", 12346, c => c
                .WithRouteConfig(RouteConfig.RegisterRoutes)
                );
       }
}

I call Host() from a NavigateToInitialPage() call, shown below
var experimentIndex = Host.Instance
                .NavigateToInitialPage<ExperimentIndexPage>();

And receive the following exception
System.TypeInitializationException was unhandled by user code
HResult=-2146233036
Message=The type initializer for 'GroundControl.Mvc.AcceptanceTests.Host' threw an exception.
Source=GroundControl.Mvc.AcceptanceTests
TypeName=GroundControl.Mvc.AcceptanceTests.Host
StackTrace:
at GroundControl.Mvc.AcceptanceTests.UserCreatesSimpleExperiment.ShouldCreateExperimentAndShowStatus() in C:\Users\Steven\Workbench\BCSL Ground Control Service\Tests\GroundControl.Mvc.AcceptanceTests\UserCreatesSimpleExperiment.cs:line 23
InnerException:
HResult=-2147467261
Message=Object reference not set to an instance of an object.
Source=TestStack.Seleno
StackTrace:
at TestStack.Seleno.Configuration.WebServers.ProjectLocation.GetSolutionFolderPath() in c:\ConsoleBuildAgent\work\6625a30e8ee728ba\src\TestStack.Seleno\Configuration\WebServers\ProjectLocation.cs:line 42
at TestStack.Seleno.Configuration.WebServers.ProjectLocation.FromFolder(String webProjectFolderName) in c:\ConsoleBuildAgent\work\6625a30e8ee728ba\src\TestStack.Seleno\Configuration\WebServers\ProjectLocation.cs:line 33
at TestStack.Seleno.Configuration.SelenoHost.Run(String webProjectFolder, Int32 portNumber, Action`1 configure) in c:\ConsoleBuildAgent\work\6625a30e8ee728ba\src\TestStack.Seleno\Configuration\SelenoHost.cs:line 51
at GroundControl.Mvc.AcceptanceTests.Host..cctor() in C:\Users\Steven\Workbench\BCSL Ground Control Service\Tests\GroundControl.Mvc.AcceptanceTests\Host.cs:line 12
InnerException:
I'm a bit at a loss for how to resolve this issue, or even really where the problem is. Any help you can offer would be appreciated.
Thanks,

I think there is two things happening here.
First one is some poor error handling in Seleno that bubbles up a null reference exception when it fails to find a website to spin up in IIS Express. We should out in a fix for that (although feel free to submit a PR for it yourself too :)). Based on the stack trace its on line 42 of ProjectLocation.cs.
The second problem is I suspect you are putting the wrong project name in your host configuration, you had:
Instance.Run("GroundControl.Mvc.AcceptanceTests", ...)
That doesn't look like the name of a web project to me?

Rob,
Thanks for getting back so quickly.
Yes, I'm using an intentionally bad project name to throw the expected DirectoryNotFound exception. I was getting the same error using the web project in my solution: GroundControl.Mvc.
The solution is laid out as shown below:
Service\
     GroundControl.sln
     GroundControl.Mvc\

When calling the run method, I used this host configuration
 public static class Host
    {
        public static readonly SelenoHost Instance = new SelenoHost();

        static Host()
        {
            Instance.Run("GroundControl.Mvc", 12346, c => c
                .WithRouteConfig(RouteConfig.RegisterRoutes)
                );

        }
    }

I'm experiencing, essentially, the same System.TypeInitializationException here. My assumption is that I'm pointing Seleno at the wrong directory, but shouldn't I be getting the DirectoryNotFound exception, rather than the stacktrace I provided earlier?
Thank you so much for the help.

Rob,
I'm doing some digging on my own, and forcing creation of the web application using the instructions TestStack provides here: http://seleno.teststack.net/docs/configuring-the-web-application. This forces the directory location before acting on .Run().
I'm finding a null reference exception here, and I believe it's triggering in the GetSolutionFolderPath method in ProjectLocation.cs.
private static string GetSolutionFolderPath()
39         {
40             var directory = new DirectoryInfo(Environment.CurrentDirectory);
41

42             while (directory.GetFiles("*.sln").Length == 0)
43             {
44                 directory = directory.Parent;
45             }
46             return directory.FullName;
47         }

This path doesn't return a DirectoryNotFound exception, so it would make sense to get a null reference exception here.
The previous question, I guess, still stands. If the solution is laid out in a fairly typical way, what is causing Seleno to throw an exception?

Rob,
Figured it out. It turns out, my solution structure broke the method used to locate the solution directory. If you have a solution structured like:
Service
     MySolution.sln
     MyWebProject
Test
     MyTestProject

And you run SelenoHost.Run() from inside the TestProject, it will iterate backward up through parent directories until the directory.Parent variable is null..
To fix this, move the solution file to
MySolution.sln
     Service\
      Test\

After doing that, Seleno is functioning as expected. Consider this issue resolved.

Cool. Thanks for reporting back.
I'll leave the issue open so we can make the error a bit more obvious

(Again - if you have time feel free to submit a PR for it :))


Add x-ms-enum.modelAsString=false to single value enums in Azure.Search.Documents

seal-single-value-enum-by-default in autorest.md is a temporary flag. When it stops working, enums with single value will no longer be treated as constants. To avoid this, add x-ms-enum.modelAsString=false to all enums that should remain constants, e.g.: e.g.:
https://github.com/Azure/autorest.csharp/blob/25d9b624ae1e6c5faf65fbb8176e718f85c6b4c8/test/TestProjects/BodyAndPath-LowLevel/BodyAndPath-LowLevel.json#L106 (in this example, however, parameter is still created cause EnumName2 has 2 values).

/cc: @ShivangiReja please check if the search swagger has any single enums and whether this flag needs to be added as perhaps a transformation to keep the current behavior.


Remove variables that are not used

This PR removes two variables nh_iceload and nh_bedrock that got carried over from the older version of the SLM when it was coupled to the PSU model to run over the Northern Hemispheric Ice Sheet during the Last glacial cycle. These variables are no longer used in the MALI-SLM coupling framework.

@matthewhoffman , here's another straightforward PR that removes some unnecessary variables in MALI-SLM coupling framework.


Some ideas, to be expanded

Saw your talk today, here's a couple more, I'll add some more details to these. Great project!

Don't know why this created a PR against the fork. Weird.

@kopasetik: I'll work on this branch a bit more later, and open a real PR against upstream. (I'll add those to the list, too, heh!)


lorri shell error message says to use a --show-trace option that does not exist

Describe the bug

When running lorri shell, if the evaluation fails due to an EvalError, the underlying nix-shell error message is returned which encourages the user to "use '--show-trace' to show detailed location information". However, lorri shell does not have a --show-trace flag, so the error message is confusing.
While usually, lorri daemon builds (and fails) silently in the backround, I find myself invoking the lorri shell directly in order to see the error message if lorri has failed. When I first encountered the message to use --show-trace and tried to heed the advice only to find that the flag did not exist, I found it frustrating, so it could be a source of frustration to new users.
To Reproduce
Steps to reproduce the behavior:

Create a shell.nix with a build input that does not exit:

{ pkgs ? import <nixpkgs> {} }:

pkgs.mkShell {
  buildInputs = [
    pkgs.hellohello

    # keep this line if you use bash
    pkgs.bashInteractive
  ];
}

Run lorri shell. Output is:

lorri: building environment.. done
Aug 27 10:42:55.877 ERRO Build failed. No cached environment available.
Build error: Nix process returned exit code 1.
$ "nix-instantiate" "-vv" "--add-root" "/tmp/.tmpzAvNks/result" "--indirect" "--argstr" "runTimeClosure" "/nix/store/sf8qqzxmxx2k2h7vmr0h3k7nk4sfw9sj-runtime-closure.nix" "--argstr" "src" "/home/myuser/Documents/Programming/Learning/fail/shell.nix" "--" "/home/myuser/.cache/lorri/cas/3a83fbad2f114b4f4f431db2014c985c"
trace: using storePath
error: --- EvalError --- nix-instantiate
at: (5:5) in file: /home/myuser/Documents/Programming/Learning/fail/shell.nix

     4|   buildInputs = [
     5|     pkgs.hellohello
      |     ^
     6|

attribute 'hellohello' missing
(use '--show-trace' to show detailed location information)

Run lorri shell --show-trace

error: Found argument '--show-trace' which wasn't expected, or isn't valid in this context

Expected behavior

Either:

a lorri shell --show-trace option should exist, which passes the --show-trace flag to nix-shell

Or

the "(use '--show-trace' to show detailed location information)" line is not included in the lorri shell error message

(I prefer the first option, and I would be happy to implement it, if you think it makes sense!)
Metadata

$ lorri info --shell-file shell.nix

lorri version: 1.1
GC roots exist, shell_gc_root: "/home/myuser/.cache/lorri/gc_roots/28cfd13fd135690f7734c7c5adf99eb7/gc_root/shell_gc_root"

$ uname -a

Linux myhostname 5.4.57 #1-NixOS SMP Fri Aug 7 07:34:02 UTC 2020 x86_64 GNU/Linux

Additional context

Thanks!

Makes a lot of sense to me. :+1:


Not authorized - solved

Hi everybody
Today I couldn't connect to WhatsApp, so I changed my local file WhatsConstants as following:
// Previous value: 2.12.96
public const string WhatsAppVer = "2.13.9";
// Previous value: WhatsApp/2.12.96 S40Version/14.26 Device/Nokia302
public const string UserAgent = "WhatsApp/2.13.9 S40Version/14.26 Device/Nokia302";
I tried to connect using the same password, but I got: not authorized.
Then I tryied to register again using voice option. Instead of making the call, it answered me with a new password.  Now everything is working.
Is anybody else facing the same problem?
Sorry for any English grammar mistakes...

It was the same with me!
When I'd Request Register showed " {"status":"fail","reason":"old_version"} "
I changed the const "WhatsAppVer and UserAgent " and it worked.
Hugs

ButI m not able to come out from this problem.
Since morning login not authorized.  before that I used everything to send
image,  video, audio.
Now I have problem from whatsappApi
On 04-Dec-2015 5:03 PM, "rflsouza"<EMAIL_ADDRESS>wrote:

It was the same with me!
When I'd Request Register showed "
{"status":"fail","reason":"old_version"} "
I changed the const "WhatsAppVer and UserAgent " and it worked.
Hugs
—
Reply to this email directly or view it on GitHub
https://github.com/mgp25/Chat-API-NET/issues/108#issuecomment-161945610.

hi guys. It happened to me too last night! It seems that the solution of @danielst83  is right. I will have to check my app on Saturday though. Will keep you all informed then.

Where are whatsAppver and UserAgent values? I´m having this problem since morning and got no idea how you fixed it.

Found it :P

Big Big Big thank you it works!! :D:D


feat: matic mainnet and mumbai testnet (polygon)

This is very much needed as currently Onboard displays  "you need to switch your wallet's network from mainnet to unknown" for Matic (& some other chains).
Is anything missing @aaronbarnardsound?

is there any updates?
really need polygon support here
thx!

@harry830622 @yomarion I merged these in but it won't be included in the next release. For now we only want to include networks that are officially supported. We have an option that will allow you to override the unknown field with your desired networkName. Please let me know if this resolves your issue. 👍🏾