VQC works with COBYLA but not ADAM

Environment

Qiskit Machine Learning version: 0.4.0
Python version: 3.7.13
Operating system:  Executed on Google Colab

What is happening?
I've tried to implement a classification problem on Iris dataset using the VQC function which works perfectly well when I set the optimizer to COBYLA but when I change it to ADAM keeping everything else the same, the program doesn't doesn't end when I run fit.
How can we reproduce the issue?
from sklearn.datasets import load_iris
from sklearn.model_selection import train_test_split
from sklearn.preprocessing import StandardScaler,MinMaxScaler
from keras.utils.np_utils import to_categorical

import qiskit
from qiskit import QuantumCircuit
from qiskit.circuit import ParameterVector
from qiskit.circuit.library import  ZZFeatureMap, TwoLocal
from qiskit.algorithms.optimizers import COBYLA, L_BFGS_B, ADAM
from qiskit.utils import QuantumInstance, algorithm_globals

iris = load_iris()
X = iris['data']
y = iris['target']
names = iris['target_names']
feature_names = iris['feature_names']

scaler = MinMaxScaler((-3.142, 3.142))
X_scaled = scaler.fit_transform(X)

X_train, X_test, y_train, y_test = train_test_split(
X_scaled, y, test_size=0.2, random_state=2)
y_train = to_categorical(y_train, num_classes=3)
y_test = to_categorical(y_test, num_classes = 3)

backend = Aer.get_backend('qasm_simulator')
backend_options = {"method": "statevector"}
seed = 88
quantum_instance = QuantumInstance(backend, shots=1024,seed_simulator = seed, seed_transpiler = seed,
                                   backend_options=backend_options)

vqc = VQC(
    feature_map=ZZFeatureMap(4),
    ansatz=TwoLocal(4, ['rx', 'ry','rz'], 'cx', entanglement = 'circular', reps = 1, insert_barriers = True),
    loss="cross_entropy",
    #optimizer= COBYLA(maxiter=30),
    optimizer = ADAM(maxiter=30, lr=1e-3, tol = 1e-6),
    quantum_instance=quantum_instance
)

vqc.fit(X_train, y_train)

What should happen?
Program works fine when the optimizer is set to COBYLA but doesn't doesn't end when it's set to ADAM
Any suggestions?
No response

The script works, but unfortunately slow. The problem is that ADAM is a gradient based optimizer, while COBYLA is gradient free. That means, ADAM estimates gradient with respect to ansatz parameters. For each sample in the dataset, for each parameter there are two additional circuits are executed. In your case it is 120 * 24 * 2 = 5760 circuits. And the gradient is estimated on each iteration. COBYLA does not do that, it just evaluates an objective function defined by VQC one time per iteration, thus one circuit per iteration. See the numbers.

The script works, but unfortunately slow. The problem is that ADAM is a gradient based optimizer, while COBYLA is gradient free. That means, ADAM estimates gradient with respect to ansatz parameters. For each sample in the dataset, for each parameter there are two additional circuits are executed. In your case it is 120 * 24 * 2 = 5760 circuits. And the gradient is estimated on each iteration. COBYLA does not do that, it just evaluates an objective function defined by VQC one time per iteration, thus one circuit per iteration. See the numbers.

That makes sense, thank you. If the gradients are being computed using the parameter shift rule, the runtime could probably be improved by computing the gradients parallelly.

@DPeddireddy The problem is more generic, the runtimes may help, but not that much. Here is the cause of this issue: https://github.com/Qiskit/qiskit-terra/issues/7676.


Downloads client

Clients are no longer under downloads.o.org
This PR updates the links
The version and the size will have to be modified when ready for release
Further changes will be required to the "downloads" section. The proposed changes are the minimal ones that will not affect the layout of the page
Note: the link to the .exe does not work. The .exe was not attached to the m3 tag
cc @pwalczysko

The built version https://snoopycrimecop.github.io/www.openmicroscopy.org/omero/downloads/ looks good.
I suppose there will have to be another PR which will replace the m3 with 5.5.0-true-release-version-number  ?

So we will not publicize the insight, insight-ij on https://downloads.openmicroscopy.org/omero/5.5.0-rc1/artifacts/ anymore, right ?

@pwalczysko correct they will not be under downloads

@pwalczysko Links will be updated when we are ready

See the header of the page (5.4 downloads) as found on the https://snoopycrimecop.github.io/www.openmicroscopy.org/omero/downloads/  (version built by snoopy).
If this is as expected, then the PR here is still working fine.

It is expected.  We discussed dropping the minor version to avoid confusion since "openmicroscopy" could be at 5.5.0 and insight for example at 5.5.2

@pwalczysko I have linked the .exe to the m3 tag. Could you test it on Windows?

@pwalczysko I have linked the .exe to the m3 tag. Could you test it on Windows?

@jburel  tested (including import to eel) and works as expected.
But, as already discussed with @rgozim , it would be good if there would be a shortcut created on the installation step - the other programmes ask about this when I am trying to install them on Windows (something like : should a shortcut be created on Desktop and or in Start menu ?). Otherwise it is a challenge to find where insight was installed.

@pwalczysko Having a short cut will be useful. But we can do that in a follow-up release. Could you create an issue on https://github.com/ome/omero-insight?


SchemaConfig To Define Table Schema Is Ignored When Used With Annotations To Set Custom Table Name

My sch.post table is in different schema thus i had to use --feature sql/schemaconfig
dbc, err := codegen.Open(
	"postgres",
	<conn-string>,
	codegen.AlternateSchema(codegen.SchemaConfig{
		Post: "sch",
	}))

On generation, ent opted to generate a plural (can this be disabled?) form name of the table. My table name becomes sch.posts thus I get  pq: relation \"sch.posts\" does not exist error
Now I had to use Annotations to specify the original table name.
func (Post) Annotations() []schema.Annotation {
	return []schema.Annotation{
		entsql.Annotation{Table: "post"}, // fails to generate if sch.post
	}
}

But by doing so, SchemaConfig seems to be ignored? Now i get the error codegen: post not found

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
SchemaConfig defined is ignored when used with Annotations. Table access is now post
Expected Behavior 🤔
SchemaConfig + Annotations should result to sch.post
Steps to Reproduce 🕹
Steps:

Create a table with a singular name (ex. post) in a different schema.
Use SchemaConfig to configure the table schema (ex. sch). Results to sch.posts. You'll  get does not exist error.
Use Annotations to configure custom table name. Results to post. You'll get not found error.

Your Environment 🌎

Tech
Version

Go
1.17

Ent
v0.9.1

Database
Postgres (postgres:13.3-alpine)

Driver
github.com/lib/pq

Hey @qgervacio and thanks for opening this issue.
I'm not able to reproduce this issue. Can you please create an example repository (with docker-compose) that reproduces this bug and post it here? Thanks 🙏

Closing as I'm not able to reproduce this issue and it looks like things work as expected.
@qgervacio, please reopen this issue if you still have troubles with the SchemaConfig feature 🙏


Shared files are moved to trash when changed locally

I share a KeePass 2 (*.kdbx) database with my wife since we have some shared accounts. We have been using Google Drive to sync the database to our Android phones using the Keepass2Android app and Grive-Tools on Ubuntu, until that recently stopped working with the Drive API changes.
Since then, I've noticed that things aren't syncing correctly on our phones when I make a change on Ubuntu and expect it to sync up via google-drive-ocamlfuse. Tonight I realized that the issue relates to the fact that when I save the Keepass2 database, the old kdbx file is moved to the trash in Google Drive.
This wouldn't be an issue, but it means that every time I make a change, I have to go back into Google Drive and share the file with my wife again. If it were just me, it would only mean that I have to re-locate the file and re-open the database in Keepass2Android. The big problem comes in with shared files.
I imagine this will also be an issue other shared files, and whether or not keep_duplicates is set to true or false.

I checked the source code of KeePass 2 and I think that what you have experienced is the default behavior when saving the kdbx file. The DB is saved to a new temporary file, then renamed to match your original filename. There should be an option to turn off this behavior: in Tools -> Options -> Advanced there is a checkbox labeled Use file transactions for writing databases. You should try unchecking this option.

Thanks for the help! Changing that option worked. I never changed it when switching from grive to ocamlfuse. Weird, but glad it's working now.


Register GPU RefExit kernel

It looks like the code was all set up to support a GPU kernel for RefExit (as was done for similar kernels, e.g. RefEnter), but RefExit was never actually registered for the GPU.  I'm not sure if it was intentionally left out for some reason, or if this was just an oversight.  All I did was add the registration calls and it appears to work.

Can one of the admins verify this patch?

The more general motivation for this change is that currently all loop Variables are pinned to the CPU, because they are colocated with the CPU-only RefExit.  This means that the Variables need to be transferred on and off the GPU every loop iteration.  Adding a GPU kernel for RefExit allows the whole loop to run on the GPU, which significantly improves performance.

Any updates on the review?  Normally I wouldn't push, but it'd be really nice to get this into the 1.2 release if possible, since it's a pretty significant performance bottleneck.  @ebrevdo might be able to quickly comment, since he wrote the GPU RefExit code.

I believe the GPU_HOST_REF_KERNEL is already being registered here

Are there any other changes you'd suggest @ebrevdo?

No, I'm away this week so will ask someone else to review.
On Jun 13, 2017 7:29 AM, "Daniel Rasmussen"<EMAIL_ADDRESS>wrote:
Are there any other changes you'd suggest @ebrevdo
https://github.com/ebrevdo?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/pull/10174#issuecomment-308134751,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABtim-skvKejOuztUaxgo_AJ5IQE4UiOks5sDpzigaJpZM4NlpiR
.

@keveman can you take a look?

@tensorflow-jenkins test this please

I have just ran all internal tests, and looks like this change does not cause any breakages internally.
It is safe to merge this PR.


Draggable.handle dont work

Its not possbile to resign draggable handle class, the whole widget is always draggable form everywhere and if I set draggeble:{
handle: 'h3'
}
should only make the H3 draggable but nothing happens, I can drag the widget from everywhere

Found the problem myself, was using a ng-include for rendering my widgets and ng-include does not replace the html so my draggable class could not be found and angular-gridsters fallback when not finding the handle class is to set the whole element.
Work around if any others may have the same problem is to create a custom directive like so:
app.directive('customWidget', function () {
return {
restrict: 'E',
templateUrl: './views/partials/widget.html',
replace: true //Very important
}
});

I think there is a root problem relating to this because of templateUrl being fetched async. I'll open another issue to track it. Also, the replace property is being deprecated so it doesn't make sense to use it for a solution. Although, it didn't work for me anyways.


expand docu for undocumented docker behavior

Hmm I don't think that this is accurate, though I understand the confusion. Gitea uses GITEA_WORK_DIR/custom if GITEA_CUSTOM has not been set, but the docker build provided by gitea does set GITEA_CUSTOM.
Gitea itself doesn't know if it is being run inside docker or not, and wouldn't use /data/gitea if somebody else made a docker build -- so it isn't accurate to say that it uses a different value if inside docker.
This is also explained on the docker page here in the "Customization" section:
https://docs.gitea.io/en-us/install-with-docker/
So it isn't undocumented (and working as documented -- though confusing if you don't look at the docker page). I believe as of 1.9 it will also list the value of GITEA_CUSTOM in the admin section as well.
Maybe it would be better to have a section for docker users here that says if using the official Docker image to instead look at the "Environments variables" and "Customization" section on the Docker page (linked above)

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@a25b3d4). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #7272   +/-   ##
=========================================
  Coverage          ?   40.98%
=========================================
  Files             ?      462
  Lines             ?    62584
  Branches          ?        0
=========================================
  Hits              ?    25652
  Misses            ?    33569
  Partials          ?     3363

Continue to review full report at Codecov.

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


Add the "remote_source.packages" key to the JSON schema

This is to support forwarding new parameters to Cachito to
support multiple packages in a single source repository.
Relates to CLOUDBLD-1598
Signed-off-by: mprahl<EMAIL_ADDRESS>Maintainers will complete the following section

[ ] Commit messages are descriptive enough
[ ] Code coverage from testing does not decrease and new code is covered
[ ] JSON/YAML configuration changes are updated in the relevant schema
[ ] Changes to metadata also update the documentation for the metadata
[ ] Pull request has a link to an osbs-docs PR for user documentation updates

/packit copr-build

rn upated: - Add the "remote_source.packages" key to schema for container.yaml


thread 'Block data compression' panicked at 'called `Option::unwrap()

I've installed ordhook on my local computer and i'm trying to run this as a service. On the beginning everything was looking fine, but further i was i've encountered more errors. Currently im +- 190k block and my console looks like on screen.

My config:
[storage]
working_dir = "ordhook"

# The Http Api allows you to register / deregister
# dynamically predicates.
# Disable by default.
#
# [http_api]
# http_port = 20456
# database_uri = "redis://localhost:6379/"

[network]
mode = "mainnet"
bitcoind_rpc_url = "xxx"
bitcoind_rpc_username = "xxx"
bitcoind_rpc_password = "xxx"
# Bitcoin block events can be received by Chainhook
# either through a Bitcoin node's ZeroMQ interface,
# or through the Stacks node. Zmq is being
# used by default:
bitcoind_zmq_url = "tcp://xxx:29000"
# but stacks can also be used:
# stacks_node_rpc_url = "http://<IP_ADDRESS>:20443"

[limits]
max_number_of_bitcoin_predicates = 100
max_number_of_concurrent_bitcoin_scans = 100
max_number_of_processing_threads = 2000
bitcoin_concurrent_http_requests_max = 64
max_caching_memory_size_mb = 8000

Disable the following section if the state
must be built locally
[bootstrap]
download_url = "https://archive.hiro.so/mainnet/ordhook/mainnet-ordhook-sqlite-latest"
[logs]
ordinals_internals = true
chainhook_internals = true
Tried this on 2 machines and both have similar issues - did i missed something?

Please see: this tip for a solution.


Refactored ReviewStore, Characteristics form, implemented add review button corresponding form

Good Job Danny, I will approve.


(maint) Logger bug fix

This PR is about the fix for the bug found within clean.rb when the Logger is called and received a :debug message.  The fix is to create a debug function within the LoggerIO class in the file clean.rb.

🙈 sorry for more back and forth @Tu2607 but would you mind updating the commit message to mention that this bug arose from adding debug logging to the puppetserver-ca gem?

🙈 sorry for more back and forth @Tu2607 but would you mind updating the commit message to mention that this bug arose from adding debug logging to the puppetserver-ca gem?

Yeah for sure. Btw, one the tests for windows failed because of some reason that I don't think is related to the logger.


phpExtensions.openswoole: init at 4.11.0

Description of changes
Request to add openswoole: https://pecl.php.net/package/openswoole
Open Swoole is a fork of Swoole. It is actively maintained by some of the original developers and has growing community.

https://github.com/openswoole
https://openswoole.com/
https://openswoole.com/community

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

You need to rebase your commits :)

Commits have been rebased as requested. If there is anything else please let me know.

@ofborg build php81.extensions.openswoole php80.extensions.openswoole php74.extensions.openswoole

So... this extension doesn't actually build on any of the supported PHP versions. I see no reason to merge a broken package.
Has this been tested without sandboxing or something like that?

@etu Happy to clarify. Openswoole works on PHP7.4, 8.0 and 8.1. It's direct fork of https://github.com/NixOS/nixpkgs/tree/master/pkgs/development/php-packages/swoole which is already included in Nix.
I'm new to Nix, how can I help you with your question/concern?

Openswoole works on PHP7.4, 8.0 and 8.1. It's direct fork of https://github.com/NixOS/nixpkgs/tree/master/pkgs/development/php-packages/swoole which is already included in Nix.

I'm well aware of this bit, it was part of the description of the package. I see the point of having this package, I'm not against it. I just don't see the point of merging a package that doesn't build and won't work :wink:

It seems the build is failing due to an issue with the test scripts, not familiar with these. I have informed the Openswoole dev team, and will get back to you asap.

It may be that something is using network in the tests, those tests would have to be skipped since they can never work inside of the sandbox. This is why I asked if it had been tested without sandboxing enabled.

Running the tests assumes you have a MySQL and Redis instance running: https://github.com/openswoole/swoole-src/blob/master/tests/README.md. In the log it looks like all tests are skipped except one which fails instead. You need to either provide an environment where the tests can run, i.e. launch MySQL and Redis in the test phase, or just disable the tests, since they're useless otherwise.

Thanks @etu and @talyz. The developers are going to fix this for the next point release. Will inform you once this release it out. Thanks for your patience.

Thanks a lot!

Thank you for your contribution!


Replace Lua with Jazz / Mun interpreter

Mun-Lang
Jazz + Programming language design Discord.
related: https://github.com/foundpatterns/torchbear/issues/233
upstream: https://github.com/poga/actix-lua/issues/25

nushell/crates at 55eafadf025fb8737ed922b2f471137e0cdfe1f9 · nushell/nushell
nushell/crates/nu-parser/src at 55eafadf025fb8737ed922b2f471137e0cdfe1f9 · nushell/nushell
nushell/Cargo.toml at 55eafadf025fb8737ed922b2f471137e0cdfe1f9 · nushell/nushell
nushell scripts - Google Search
nu_scripts/netstat.nu at main · nushell/nu_scripts


Activity Id displayed in emulator doesn't match activity id from code

Version
4.4.2
Describe the bug
I am creating an activity the posting it into my bot. Unfortunately it looks like the ID that I provide the activity does not match the ID displayed in the JSON inspector.
The JSON is:
{
  "attachments": [
    {
      "content": {
        "buttons": [
          {
            "text": "PositiveFeedback|question:what is a skill|answer:A broad set of common capabilities exist which today, which require each developer to build themselves. Our Virtual Assistant solution includes a new Skill capability enabling new capabilities to be plugged into an Virtual Assistant through configuration only and provide an authentication mechanism for Skills to request tokens for down-stream activities.\nFind out more [here](https://github.com/Microsoft/AI/blob/master/solutions/Virtual-Assistant/docs/virtualassistant-skills.md).|activityid:f371dc50-8318-11e9-a9a4-4fbd3b8d2732|channelid:emulator",
            "title": "Yes",
            "type": "imBack",
            "value": "PositiveFeedback|question:what is a skill|answer:A broad set of common capabilities exist which today, which require each developer to build themselves. Our Virtual Assistant solution includes a new Skill capability enabling new capabilities to be plugged into an Virtual Assistant through configuration only and provide an authentication mechanism for Skills to request tokens for down-stream activities.\nFind out more [here](https://github.com/Microsoft/AI/blob/master/solutions/Virtual-Assistant/docs/virtualassistant-skills.md).|activityid:f371dc50-8318-11e9-a9a4-4fbd3b8d2732|channelid:emulator"
          },
          {
            "text": "NegativeFeedback|question:what is a skill|answer:A broad set of common capabilities exist which today, which require each developer to build themselves. Our Virtual Assistant solution includes a new Skill capability enabling new capabilities to be plugged into an Virtual Assistant through configuration only and provide an authentication mechanism for Skills to request tokens for down-stream activities.\nFind out more [here](https://github.com/Microsoft/AI/blob/master/solutions/Virtual-Assistant/docs/virtualassistant-skills.md).|activityid:f371dc50-8318-11e9-a9a4-4fbd3b8d2732|channelid:emulator",
            "title": "No",
            "type": "imBack",
            "value": "NegativeFeedback|question:what is a skill|answer:A broad set of common capabilities exist which today, which require each developer to build themselves. Our Virtual Assistant solution includes a new Skill capability enabling new capabilities to be plugged into an Virtual Assistant through configuration only and provide an authentication mechanism for Skills to request tokens for down-stream activities.\nFind out more [here](https://github.com/Microsoft/AI/blob/master/solutions/Virtual-Assistant/docs/virtualassistant-skills.md).|activityid:f371dc50-8318-11e9-a9a4-4fbd3b8d2732|channelid:emulator"
          }
        ],
        "subtitle": "",
        "title": "Click on the icons below to rate this answer"
      },
      "contentType": "application/vnd.microsoft.card.hero"
    }
  ],
  "channelId": "emulator",
  "conversation": {
    "id": "74aa38f1-8317-11e9-996c-452966995099|livechat"
  },
  "entities": [],
  "from": {
    "id": "67a0a4f0-8295-11e9-996c-452966995099",
    "name": "Bot",
    "role": "bot"
  },
  "id": "ef945e90-8319-11e9-a9a4-4fbd3b8d2732",
  "localTimestamp": "2019-05-31T08:31:42+12:00",
  "locale": "en-US",
  "recipient": {
    "id": "9c25fbce-849f-41e7-adf8-218bc84d1925",
    "role": "user"
  },
  "replyToId": "f371dc50-8318-11e9-a9a4-4fbd3b8d2732",
  "serviceUrl": "http://localhost:62661",
  "timestamp": "2019-05-30T20:31:42.841Z",
  "type": "message"
}

This activity is being created by the following code:
public static Activity GetHeroCardWithButtons(string cardTitle, List<HeroCardButton> buttons)
		{
			var chatActivity = Activity.CreateMessageActivity();
			var cardButtons = new List<CardAction>();

			foreach (HeroCardButton button in buttons)
			{
				cardButtons.Add(
					new CardAction()
					{
						Text = button.Value,
						Type = ActionTypes.ImBack,
						Title = button.Label,
						Value = button.Value
						//Value = " " // Thank you for your feedback here?
					});
				;
			}

			var plCard = new HeroCard()
			{
				Title = cardTitle,
				Subtitle = string.Empty,
				Buttons = cardButtons
			};

			var attachment = plCard.ToAttachment();

			chatActivity.Id = Guid.NewGuid().ToString();
			chatActivity.Attachments.Add(attachment);

			return (Activity)chatActivity;
		}

Evidence of the ID being created in code for the activity:

Checking the activity in the emulator:

Am I doing something wrong here when trying to find the activity ID?
Thanks.
Additional context
I am trying to use the activity id to Call the DeleteActivityAsync function but since the IDs don't match it fails.

I've found the code responsible for this issue, and it appears that the Emulator is in fact overwriting the id field on the incoming activity.
I don't think this is necessary because if you look at that same code path, we call postActivityToUser which then calls postage on the activity, which tries to use the existing id on the activity, otherwise it generates a new one. In the case of this code path, we are wiping the incoming id field every time, so a new GUID is always generated.
@justinwilaby or @compulim do either of you happen to have more context on this, or any idea on if this is necessary? If not, it should be an easy fix of just reusing the incoming activity's id or defaulting to null if the id field is missing.

I discussed this change with @compulim offline, and we have decided that there shouldn't be any adverse side effects to this change as long as you -- the user -- ensure that the activity ids are unique.
At that point the burden is on the user when modifying the activity id directly.


Safes 0.1.0 Show no owners when loaded

Env: mainnet https://gnosis-safe.io/app/#/load
version: 3.9.0
Issue: Loading a safe 0.1.0 is possible with our current app, but the safe is shown with 0 owners.
A 0.1.0 safe: 0x5f2b85618d790e7ba4328c19628c8587cc3d9645

0.1.0 Safes aren't critical for us, however it seems like they are allowed in the Safe address input step.
So I think the solution should be one of
(1) Display the owners properly
Or if that tedious, (2) prevent users from adding 0.1.0 Safes in the first place.

This will be solved in #2608 adding a minimum compatibility with legacy safes

Tried this in the PR2608 in the mainnet build with the safe address given in the description, but it is treated as a "unprocessable entity"
safe: 0x5f2b85618d790e7ba4328c19628c8587cc3d9645
https://pr2608--safereact.review.gnosisdev.com/mainnet/app/#/load

@francovenica could you test again today? Maybe it was a backend issue. I can load that safe perfectly in #2608

@dasanra I still have issues, even in prod mainnet. I'll check later today

0x5f2b85618d790e7ba4328c19628c8587cc3d9645 throws "not checksummed" 🤔

0x5F2b85618D790e7Ba4328c19628c8587cC3D9645
if I use this address it loads fine to me

We might need a bug report for that input not checksumming the value.

yep, it was about the checksum. I checked again and it worked.
Regarding checksum, is something we fixed last year and it worked so well during so many regressions that I just stop checking since it was time consuming just to check the checksum in all addresses inputs throughout the site. I'll Check those again and if they are not working I'll fill a ticket and add the test to the regression again

Made a ticket https://github.com/gnosis/safe-react/issues/2620 for the checksum thing

Checksumming has been fixed, and this Safe address can be loaded fine now. With owners.


Hello!

Hello!
Thank you for reaching out. I didn't see any text/comments in the issue you created. If there is something you'd like help with, please reopen this issue and add in any comments or questions. I'd be happy to help out :)
Originally posted by @ncalteen in https://github.com/google-pay/wallet-samples/issues/27#issuecomment-1238138981

Hello again, apologies, it looks like this is just a copy of my comment on the previous issue you opened. If you'd like to ask a question, please add a new comment to this issue and I will reply as soon as I can.
I will leave this issue open for a few days :)


[Bug] Can't access the xCloud menu within the game

Describe the bug
When I activate fullscreen mode, I can't access the Xcloud menu within the game
Platform (please complete the following information):

OS: [e.g. Android]
Browser: [Kiwi Browser]
Browser Version: [<IP_ADDRESS>]
Better xCloud Version: [1.6]

Please add a screenshot or a screen recording. I still don't know what the problem is.

Hi, I'm using kiwi browser through sideload on android TV, I can't register

Basically when I'm in fullscreen mode, I can't access the Xcloud menu. In non-full screen mode it opens normally

If you have hidden the 3 dots as part of the better xcloud settings, you can still press it whilst full screen, use your mouse to point to the top corner and press it.
If your mouse won't appear, double click and it will then show up.

Have you tried switching User-Agent profile to Edge?

Pretty sure this can be closed off


WRQ-22937: Updated storybook to version 8

Checklist

[x] I have read and understand the contribution guide
[x] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[x] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
Storybook needed to be updated to the latest version
Resolution
Updated list of storybook dependencies and their version to v8.x based on the migration guide https://github.com/storybookjs/storybook/blob/next/MIGRATION.md
Changed configuration based on the storybook v7 and v8 requirements

main.js: core.builder information replaced by framework.name.
Addon '@enact/storybook-utils/addons/docs' replaced by '@storybook/addon-docs' because storybook addon for docs does not support customization anymore https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#dropped-addon-docs-manual-configuration
story filenames different than xxx.stories.js need an indexer https://github.com/storybookjs/storybook/pull/20700/files#diff-ea5ebe92abd71b6467c58252b92c04b8d49cc140e8a94f9cf5bb7a76bf2256a4 experimental_indexers information was added in main.js
preview.js: docs.inlineStories has been renamed docs.story.inline; docs.iframeHeight has been renamed  docs.story.iframeHeight
manager.js changed configuration based on https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#ui-layout-state-has-changed-shape
package.json storybook dev and build commands adapted to v8 naming.
new root container id used by storybook is called "storybook-root". This change breaks enact's logic to apply spotlight related styling in SpotlightRootDecorator https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#change-of-root-html-ids ThemeDecorator already has a rootId prop and can be set from the sampler app to storybook-root, but it was not passed to SpotlightRootDecorator. A PR in enact repo is needed also and is attached to the user story
manager.js: The state and API for the UI layout has changed https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#ui-layout-state-has-changed-shape

Additional Considerations
Note: although docs is disabled, I left the docs configuration intact in preview.js. It will be needed when we activate docs and does not affect current configuration
Links
WRQ-22937
Comments
Enact-DCO-1.0-Signed-off-by: Daniel Stoian<EMAIL_ADDRESS>

Overall looks good to me.
There is one issue on window resize. A native HTML scrollbar is applied to globals controls.  This seems to be a Storybook bug.
On develop branch, a os-scrollbar is applied to globals list

on feature/storybook8 branch, this class does not appear

A discussion is needed on whether to override this class or to open a Storybook issue.

Could you please rebase your branch with the latest feature/enact_v5?

@daniel-stoian-lgp , Have you tested storybook version 8.1.6 with this branch?
I manually updated the storybook-related modules to 8.1.6 and symlinked @enact/storybook-utils to feature/storybook8.
I got an error like below. 🤔 Do you get this error too?
Error: Cannot find module '@storybook/csf-tools'
Require stack:
- /.storybook/main.js
- /node_modules/<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>- /node_modules/storybook/index.js

@storybook/csf-tools

Hello Mikyung. I do not face these issue. I removed node_modules and npm-shinkwrap.
Them npm i && npm shrinkwrap && enact link

Hm.. I guess symlinking made some problem. If I don't symlink the error is not reproducing. Thanks.


[FR] Compatibility with Obsidian "Extract this heading.." feature

My testing so far shows this plugin reliably updates links to headings, when headings are are cut/pasted.
But I wonder if it's possible to hook this up to Obsidian's built-in "Extract this heading..." feature, which is functionally equivalent to cutting/pasting a heading and its content to another note?

Would love this feature as well. Vote + 100%
I use the "Extract this heading" feature all the time. Although there is the "repair links within the file" option I find the links often break. For instance if my Header had a $ followed by a numeric value it often does not include the 1st 2 characters & thus the link is broken
Either way would love the suggested feature/ ability

I support this request! Having links remain consistent through renames or moves would be incredibly helpful, especially for larger projects where references are key. Persistent links would save a lot of time and hassle compared to manually fixing broken links each time a file is adjusted. It’d really help keep the workflow smooth.


Intersection Observer - thresholds param bug

Hi,
Thank you for these handy hooks !
I think there is a problem with thresolds param.
It only works if I use threshold, not thresholds as explained in the documentation.

Oh whoops, sorry about that! threshold is correct. I will update the docs today.

Fixed, thanks for reporting!


Added button to table to add default columns

Features

Added button to table to add default columns - id, created_at and updated_at - #214

It only shows when table is empty to make UI simple

Diff is shown next to table as a small circle if columns were changed

Fix

When opening tree of tables, it is automatically refreshed if no tables were previously found


Tarpaulin removed -v shorthand for --verbose in 0.27

Describe the bug
I used to use -v flag for tarpaulin. It stopped working on the latest version.
To Reproduce
Install version 0.27 of tarpaulin and try running tarpaulin with the -v flag:

sudo pacman -Sy cargo-tarpaulin=0.27.0-2

cargo tarpaulin -v

Expected behaviour
Tarpaulin runs with verbose logging.
Actual behaviour
error: unexpected argument '-v' found

  tip: to pass '-v' as a value, use '-- -v'

Usage: cargo tarpaulin [OPTIONS] [-- <ARGS>...]

For more information, try '--help'.

@MiniaczQ do you mind having a look at this if you have time as it's related to the clap 2 -> 4 migration. If not I can try and find some time after work some day this week

This turned out to be pretty easy to fix

Sorry for that 😅


undefined local variable or method `current_user' for #Admin::DashboardController:0xade7434

NameError in Admin/dashboard#index
Showing /home/ruanxx/.rvm/gems/ruby-1.9.2-p180/gems/activeadmin-0.3.1/app/views/active_admin/dashboard/index.html.arb where line #1 raised:
undefined local variable or method `current_user' for #Admin::DashboardController:0xade7434
Extracted source (around line #1):
1: render view_factory.dashboard_page
app/models/admin_user.rb:18:in `block (2 levels) in class:AdminUser'

Not that I'm sure this will help, but have you tried using the ActiveAdmin user helper?  Appears from your dump <Admin::DashboardController> that you do have a name pace setup (:admin), so the helper current_user will be of no use to you, while current_admin_user might do the trick.  Didn't verify any of that.


Yel 12365 simplified agent registration

I think this is ready go once the fixed/updated debs and rpms have been generated.


refactor Pages#goto() to make it easier to profile

clearly separates the initialize+render phase from the remove phase
over 10 runs, this neither improves nor worsens performance

lgtm :+1:


De-normalise snippets database

Right now we only have one snippets list which contains not only the metadata but the complete snippet listing.  This should be split out into meta-data only list for simple quick access and the complete list for full operations.

going to push this back from milestone 0.2.0 as it's not really necessary at this point


Outdated minimum Android version for Survey in docs

https://github.com/odk-x/docs/blame/master/odkx-src/survey-using.rst#L15 should be updated to Android version 4.4.

@linl33 Please can I work on this?

@chinenyelilian I have assigned the issue to you.


Add spanish language

Add spanish language

Hey @fmaso04, Thank you!! This code will be published next release.


[FEATURE] Changed prop

We can try to provided changed prop to each FormField

Working started. branch

Also need:

update docs
add test for changed props. Create new folder for test. Move utils to unit-test


Support for OpenSearch protocol

With how often I look up applications on Flathub, I'd like to be able to right-click the URL bar on Firefox and add Flathub as a search engine. Flathub could do this by supporting the OpenSearch protocol. Thank you for your hard work!

I've looked at this from time to time, first failing to understand how to handle it and now it seems like the protocol is pretty much on it's way out.
So I'll close this, as it's probably not worth allocating any more time.


Lookup browserslist config

This is a 🙋 feature
Though browsers may be configured using .babelrc there's no way of sharing a browserslist config with e.g. autoprefixer or cssnext without duplicating the list. This makes it easier to consolidate which browsers to support.
The tests aren't very future proof as they'd yield false positives once all major browsers catch up with the specific features used in the test.
Checklist

[x] tests pass
[x] tests and/or benchmarks are included
[x] documentation is changed or added

Semver Changes
Minor

Sweeeet :star2:


Three cameras, only one showing preview

Hello,
I have three cameras, but only one is showing preview; the others does not work.
Using component version 1.0.15.
Here attached the debug log. What configuration file do you need?
Thank you.
home-assistant_imou_life_2024-02-29T10-34-55.635Z.log

Hi, I see the error message "NotAuthorized: OP1009: No right, cannot operate" as if your credentials do not have permissions to operate the device. Is the device a shared device?

Hi,
Yes, it's a shared device, but in the app it works well.

Ok than is related to what we discussed in #88, looks like for some devices there is a different set of API for shared devices we have been not able to identified yet. Adding to the "blocked" queue unless this new api is found. Thanks

The question is: why with one camera it works?
All the three cameras are shared...

First time I see this situation, usually users reported a all-or-nothing with shared devices. No idea, unfortunately unless Imou will update the documentation of the API, emulating what the app does is really hard (#63)

Added to https://github.com/user2684/imou_life/wiki/Known-Issues


Convert Bin + Rel/Close/Punct to Ord + Rel/Close/Punct

6. If the current item is a Rel or Close or Punct atom, and if the most recent previous atom was Bin, change that previous Bin to Ord.

(Also bins at the end of an expression, see #355.)

Copying the table I posted there for reference (TeXbook, Chapter 18):

I felt like it's worth clarifying the explanation of * since it certainly is possible to write ++, +. etc...

@cbreeden: Right; this conversion process is the topic of this issue :)

@WChargin: Right, sorry :confused: I was just slightly confused for the deduction of converting bin to ords if they are last in the list (#355), until I was able to find this between rules 18 and 19.  Knuth tricked me! :blush:

I did take a look at this issue a few days ago, however, and my conclusion was that given the current model we would probably just need to implement a next for the next token here.  But I'm sure this was already known.

@cbreeden It seems like pass the next group to all the groupTypes handlers would get you what you need.

I did that 😊


I have to click undo five times to actually undo the action

Describe the bug:

When creating a data flow by double clicking a process, I have to execute undo five times in order to actually undo the action.
Expected behaviour:

Only clicking once should be enough.
Environment:

Version: 2.2
Platform: Desktop App
OS: Windows 11

To Reproduce:

Create Process Element.
Double click on it.
Click on undo five times.

Any additional context, screenshots, etc:

wow, that it not a good look, I agree @srcnuzn and thanks again for the bug report, much appreciated
There is work to be done for redo/undo functionality, along with #972 , planning this for version 2.4 due in Q4 2024

This is fixed in pull request 'Migrate to version 2.x antv/x6' #1099, where the undo functions as expected and the double click to add a dataflow has been removed - it was too counter intuitive


feat: update golang-github-benbjohnson-clock to 1.3.0

library for mocking time in Go
Issue: https://github.com/linuxdeepin/developer-center/issues/3965
Log: update repo

/test github-trigger-obs-ci


ref(release): Include CRD upgrade info in Release Notes

Signed-off-by: Kalya Subramanian<EMAIL_ADDRESS>
Description:
Fixes #2314
The release notes will now clearly indicate if a given release includes CRD upgrades from the one before it. Users will be able to use this field to see if they should manually delete the old versions of the CRDs first.

Affected area:

New Functionality      [ ]
Documentation          [ ]
Install                [ ]
Control Plane          [ ]
CLI Tool               [ ]
Certificate Management [ ]
Networking             [ ]
Metrics                [ ]
SMI Policy             [ ]
Security               [ ]
Tests                  [ ]
CI System              [ ]
Performance            [ ]
Other                  [X]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution?
No

Codecov Report

Merging #2323 (fdb1c50) into main (0011cf9) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2323   +/-   ##
=======================================
  Coverage   57.21%   57.21%
=======================================
  Files         149      149
  Lines        6689     6689
=======================================
  Hits         3827     3827
  Misses       2857     2857
  Partials        5        5

Continue to review full report at Codecov.

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

Codecov Report

Merging #2323 (fdb1c50) into main (0011cf9) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2323   +/-   ##
=======================================
  Coverage   57.21%   57.21%
=======================================
  Files         149      149
  Lines        6689     6689
=======================================
  Hits         3827     3827
  Misses       2857     2857
  Partials        5        5

Continue to review full report at Codecov.

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


I have a question about parameter number.

after pruning, I count the parameter of the network resnet34.
well... I found the number of parameters to be 4.2 * 10e7
I know parameter number of resnet34 is about 2 * 10e7
I think it's because of the mask of layer that the difference is about  double, right?
then how to remove the mask layer after prunning?
Thanks you.

Sorry for the slow response.
The easiest way to do this would be to create a normal resnet34 (without masks), and then copy across the weights.
You'll want to do something like:
net = NormalResNet34()
masked_net = MaskedResNet34()

for normal, masked in zip([net.layer1, net.layer2, net.layer3, net.layer4], [masked_net.layer1, masked_net.layer2, masked_net.layer3, masked_net.layer4]):
    normal.conv1.weight = masked.conv1.weight
    normal.bn1.weight = masked.bn1.weight
    normal.conv2.weight  = masked.conv2.weight
    # etc.

Note that you're probably going to have to copy some biases as well (you can just do normal.bn1.bias).
It would be cool to have this as a feature in the code. If you figure it out, please feel free to open a pull request 😊
If not I'll get to implementing it soon.

Sorry for the slow response.
The easiest way to do this would be to create a normal resnet34 (without masks), and then copy across the weights.
You'll want to do something like:
net = NormalResNet34()
masked_net = MaskedResNet34()

for normal, masked in zip([net.layer1, net.layer2, net.layer3, net.layer4], [masked_net.layer1, masked_net.layer2, masked_net.layer3, masked_net.layer4]):
    normal.conv1.weight = masked.conv1.weight
    normal.bn1.weight = masked.bn1.weight
    normal.conv2.weight  = masked.conv2.weight
    # etc.

Note that you're probably going to have to copy some biases as well (you can just do normal.bn1.bias).
It would be cool to have this as a feature in the code. If you figure it out, please feel free to open a pull request
If not I'll get to implementing it soon.

Good idea, thank you. @jack-willturner
Using mask for pruning training is a very common way in pruning algorithm. I didn't want to extract effective parameters after mask training before. Your description gives me a specific implementation path (Although using this scheme needs to reimplement a model definition that can customize the number of parameters of each layer)


Maptiles Invalid Key

Today:

Thanks in advance for support and for this awesome tool!

Here are the debug file: https://drive.google.com/open?id=1_mXwV8al4XZMkk_Jd0TgBwpZmn77BanO&authuser=jfbuendia%40gmail.com&usp=drive_fs

Thanks for the bug report. It is a know issue. For the secondary base map, I am using a paid service that provides a free tier, but there are too many users that use it and we reach the limit every month: it will work again in a few days. In the meantime, you have to use the default base map.
Unfortunately, there is not many providers that offer map tiles for free, and it quickly become very expensive with paid service :( I am looking into an alternative (generate and host my own map tiles), but it is a rather complex thing to set up.

Fixed in #104, available in next release.


Usage via command line

python main.py --cmd true
it will not open the gui just simply run the script and activating all bots with the settings from config.json

Theres already a CLI but its outdated, ill update it after Im done with gui

can you do so you can run it without opening the gui just using the config.json? i need it for my server, keep up the good work!


DARK MODE

Describe the feature
can add darkmode option in right most corner .
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a SWOC24 contributor
[X] I want to work on this issue

allow  me to contribute @student-aditipaliwal

allow me to contribute @student-aditipaliwal


Add links to uploads to Audit Report

Fixes #330

rather than setting a few more env vars, we can probably just pull the domain out of the req variable used to kick off the audit report gen process. we might not have the website url available in the API, but we do have it available on the client-side when the request is made, maybe it could be part of the request parameters?

Yeah, there are definitely a few approaches here.  I don't have a clear preference.
(a) As noted, we can't use the default properties on the express request, because the API host isn't necessarily the same as the website host.
(b) We can declare the website host in an environment variable, but this an extra point of configuration to remember.
(c) We can derive the host from window.location in the client and pass it to the server in a request parameter.  The issue here is that we have to trust the client, and something like a browser extension could hijack either window.location or issue requests with an alternative parameter.
🤷

(a) As noted, we can't use the default properties on the express request, because the API host isn't necessarily the same as the website host.
only in dev, in prod they're the same

(c) We can derive the host from window.location in the client and pass it to the server in a request parameter. The issue here is that we have to trust the client, and something like a browser extension could hijack either window.location or issue requests with an alternative parameter.
i don't think browser extensions hijack window.location, that's a pretty core security feature of browsers. i would prefer this approach, but i can unblock this approach also if you think it's much better, esp. if you also clean up the existing BASE_URL config.

Okay, I learned a few more things
First, BASE_URL is actually an env variable auto-generated by Vue.
https://cli.vuejs.org/guide/mode-and-env.html#using-env-variables-in-client-side-code
Bizarrely, it doesn't seem like variables we declare in .env are actually available to the Vue HTML processory, so I don't think we can remove BASE_URL.  Note that the GOST repo also uses BASE_URL for the same purposes.  (I'm pretty certain this is part of the boilerplate generated when you bootstrap a new Vue app.
https://github.com/usdigitalresponse/usdr-gost/search?q=BASE_URL
Of course, since this env variable is provided by vue-cli-service, we can't access it from express — especially in production.  I can't see a way around keeping both values.  😧

Second, I'm pretty sure you're correct: modern browsers do a good job of protecting window.location, so that particular concern probably isn't a real problem.
I admit I might be a little paranoid, but this is still a service that we are deploying into government agencies, and I just don't like the idea of passing around URLs in query parameters where they can be accessed or spoofed.  If an attacker did manage to get an arbitrary value into that domain, it could take the user literally anywhere.

path forward: lets set an env var. looks like api_host is not used, just website_host. lets have a function that gets it out of the request host header, and then falls back to the env var if it's not set. we don't have to set it in prod -- the host header always matches for us.

@igor47 Sorry, I don't think I quite follow you actually.
Are you suggesting that we read the default Host header from the request and only falling back to the env variable if that isn't present?  I think that header should always be present, it's just incorrect in our dev configuration.

i suggest we try the env var and fall back to the Host header if that's not present. we'll only have to configure the Host header in dev.

Ohh, reversing the direction of the fallback.  Sure, that makes more sense.  👍


WebviewCookieManagerPlugin.java uses or overrides a deprecated API.

I am getting this error WebviewCookieManagerPlugin.java uses or overrides a deprecated API.
my config
minSdkVersion 19

As I already wrote on #60 (which is a duplicate with a bad title):
Just general speaking without checking the actual code: There is nothing bad using deprecated APIs on legacy platforms. If you want to support all versions, you sometimes need to make such calls, since on those platforms those APIs are not deprecated and there is no alternative.


Alsa driver initialization fails on Arch Linux

Godot version:
Godot v3.0.6
OS/device including version:
Arch Linux 4.20.0-arch1-1-ARCH
Issue description:
Distored and scratchy sound when running a project file. Error message:

ERROR: init_device: Condition ' status < 0 ' is true. returned: ERR_CANT_OPEN
At: drivers/alsa/audio_driver_alsa.cpp:80.
ERROR: initialize: AudioDriverManager: all drivers failed, falling back to dummy driver
At: servers/audio_server.cpp:165.

Steps to reproduce:
Created a normal project following a tutorial (no longer available)
Minimal reproduction project:
Project link
Just open and run.
Recording while the game is running.
Recording when played from another media player.

I'm getting the exact same error too. There is no sound when playing the game, everything else works fine.
I'm on Windows and exported to Linux.
Where do I change this setting "pulseaudio"?

I'm getting the exact same error too. There is no sound when playing the game, everything else works fine.
I'm on Windows and exported to Linux. I'm using 3.3.1 stable.
Where do I change this setting "pulseaudio"?

Which Linux distribution are you using? Do you use a PulseAudio or ALSA setup on your machine? (PipeWire supports PulseAudio natively, so you don't need to do anything specific if using PipeWire.)
You can override the audio driver used by passing the --audio-driver PulseAudio/--audio-driver ALSA command line argument to the exported project. Try both and see if either of those work.

Which Linux distribution are you using? Do you use a PulseAudio or ALSA setup on your machine? (PipeWire supports PulseAudio natively, so you don't need to do anything specific if using PipeWire.)
You can override the audio driver used by passing the --audio-driver PulseAudio/--audio-driver ALSA command line argument to the exported project. Try both and see if either of those work. Official export templates contain both the PulseAudio and ALSA drivers, with PulseAudio used by default unless the audio driver is set to ALSA in the Project Settings.

I'm not using Linux, I'm on Windows, exporting to Linux via official export templates. A friend of mine is testing the game on Linux. He sent me the debug console with the following errors:
https://i.ibb.co/Hh8G2Yq/ndice.jpg
I'll try exporting with those arguments tho.

They're running the game with sudo, i.e. as super user / administrator. The administrator typically doesn't have an audio system set up.
They should just run the game as their normal user which has a working audio setup.

They're running the game with sudo, i.e. as super user / administrator. The administrator typically doesn't have an audio system set up.

I'd probably print a warning message if a Godot project/editor was started with sudo.

They're running the game with sudo, i.e. as super user / administrator. The administrator typically doesn't have an audio system set up.
They should just run the game as their normal user which has a working audio setup.

That was exactly the cause of the problem. When running as a normal user, the audio worked normally. Thanks!


The streaming action example in the readme isn't correct

It doesn't include the stream port flag

Completed in ca8cf23


Gadgetbridge support

Gadgetbridge is a oss companion app for all sorts of wearables. Among a lot of other features, it is able to provide weather data to devices. It does this by implementing recievers and relying on weather apps to send weather data. See https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki/Weather#weather-app-development for details.
Is this a feature you would be willing to consider or do you think it is out of scope for this project?
If there is an interest i'd offer myself to work on this feature. Only problem is, I have never worked with NativeScript before so a short how to build (Is it just as simple as ns run android?) and maybe a pointer where to best implement this would be amazing.
King regards

@baltevl I am not against anything. How would my app  communicate with yours? Is there an API ? Is it using intents ?
As for Nativescript, it is indeed easy to run with ns run android though I would add --no-hmr.
As for where to do it it depends mostly on how the communication would work. But I guess a new file in app/services.

Hey, while working on this I thought this would be easier to implement using a few oop principles. So I started a small refactor. Before continuing like this, I'd like to hear your opinion about 9e59888.

@baltevl awesome I really like it. Wanted to do something like thus at one point . you can create a PR and I LL merge it right away

#59 done. I might do something similar for other modules when I find the time :)


Update discord.py dependancy ref to allow IDs in role related checks.

The discord.py library has had a few new commits, but the primary benefit is that they added support for IDs in has_role and has_any_roles, which allows us to remove the custom decorator with_role.
While none of the other changes should be breaking for anything we use, it'll still be good to test things to make sure before we update the Pipfile's ref for this dependency.
Click here to see the full diff between the dependent rewrite version and the up to date one.
The noticeable changes include:

Add channel category cooldown buckets
Support IDs in role related checks
Add support for referencing and editing Guild default notification levels
Support discordapp.com invites
Spoiler attachment support
Add support for mobile indicators and per-client statuses
Support editing explicit_content_filter
Rate limit logs are WARN level instead of INFO

Related: #217

Given #217 was closed, is there anything else to do on this issue?

it was closed and then reopened again.

Oh, I did not scroll down enough. Anyway, I've actually been using cog_check to check for roles and that uses the check function we have instead of the decorator. Can these decorators from d.py be used as functions inside cog_check?

Also, if there's nothing else from here then we can close this and focus on #217.

I think everything that's still relevant can go in #217.


How does cylon differ from Vaex?

Vaex also leverages C++ and Apache Arrow. I wonder how does cylon compare to Vaex?

I'm not an expert in Vaex. From the documentation, it seems Vaex is designed to run on a single machine. Cylon can run on multiple machines and even scale to thousands of CPU cores. Vaex seems to be an older project so it should be more mature than Cylon.

Hope this answers the question. Feel free to reopen if need more details.


Add the ahoy build version based on the latest tag used.

Create a ahoy "build" command which builds the ahoy binaries and displays
the version created

Please remove all the version items from all ahoy.yml files so that it's more clear that that isn't used anymore.


Find some problem about the autofuzz in Jazzer

I find that there are many recursive parameter processes, which cause a loop operation such as ConsumeArguments(data, method, visitor)-> ConsumeArguments(data, constructor, visitor); Consume(data, type, visitor) -> Consume(data, type ,visitor).
These operation may cause some fuzz cannot further forward. For example, when the parameter in the method and the parameter in the constructor invokes the loop dependency, Jazzer will be stuck in the loop that consumes cpu and memory continuously and cannot perform effective autofuzz action.

Hi @SSWena! It's not completely clear to me what the issue is. Could you maybe create a small example (project) that I can try out to see the issue?

While it's possible that the situation could be improved, this is a fundamental limitation of the approach used in Autofuzz. We are actively working on a new mutation engine for Java types that has proper support for recursive data types.
In the meantime, if you happen to achieve "quick wins" by tweaking the heuristics used in Meta#consume or Meta#consumeArguments, please let us know or submit a PR.

Ok, thanks!
At 2023-07-05 20:15:20, "Fabian Meumertzheim" @.***> wrote:
While it's possible that the situation could be improved, this is a fundamental limitation of the approach used in Autofuzz. We are actively working on a new mutation engine for Java types that has proper support for recursive data types.
In the meantime, if you happen to achieve "quick wins" by tweaking the heuristics used in Meta#consume or Meta#consumeArguments, please let us know or submit a PR.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


[BUG] After about 8-10 commands, game stops running.

Describe the bug
Every time I play the game, no matter what type of story I choose, after about 8-10 commands, the game stops responding.
To Reproduce
Play the game and type about 8-10 responses.
Expected behavior
Should be able to continue indefinitely, or at least until the end of the story.
Additional context
I've tried in both Google Chrome and Firefox, with the same results.

Are your responses long?

I'm seeing this happen mostly when using dialogue. Something like typing: "Where are we?" instead of: ask where we are
I'm gonna try playing without ANY dialogue in quotes and see if that helps.

I'm seeing this happen mostly when using dialogue. Something like typing: "Where are we?" instead of: ask where we are
I'm gonna try playing without ANY dialogue in quotes and see if that helps.

Try not to use direct speech very often and if you have to, then save right before it

I tried to play without direct speech, but after ten requests game just stopped.

I tried again without 'ask'. All works normally.

Seems like this is resolved. Please close @AlSovPich

I've tried playing without typing dialogue in quotation marks, I've tried without using 'ask', and the same thing seems to happen, sometimes now with a lengthy error message.

Seems like this is resolved. Please close
Vortexx opened this issue, not me

And it still crash after using direct speech

The only way that I have found to resolve this is to reduce the size of the context being passed to the model.   This has a side-effect of the model forgetting things.    There's an internal history limit of 20 story items.   To keep it relatively infinite, I'd suggest keeping the whole context at a maximum of 4000 characters.   I used this to keep the model alive for many hours on Twitch.

This could be a code correctness problem (buffer overflow or improper bounds checking), not an out-of-memory problem. See bug #251.

If quotes or apostrophes seem to be related to the problem, please see my comments near the end of bug #55 .


Dispatching submit after initialize yields wrong form values

Type
Probably a bug.
Process

Set onSubmit to handleSubmit(data => ...).
Dispatch an initialize(FORM_NAME, {}) action to clear initialValues.
Dispatch a reset(FORM_NAME) action to revert to the previously initialized values.
Dispatch a submit(FORM_NAME) action to submit empty values.

Current behavior

Parameter data is a string and equals the FORM_NAME value.

Expected behavior

Parameter data is an empty object.

Environment
<EMAIL_ADDRESS>

I think you might be forgetting to include some step here.
I recreated them, and it works: https://codesandbox.io/s/ElLmqED3N

Closing as probable duplicate of #2818, @gustavohenke when all these actions are called in one synchronous block, the reproduction is achievable. See the extra two buttons at https://codesandbox.io/s/N9D0R2L0K.

This is happening to me on 7.0.3. My scenario is not in one synchronous block.

User taps submit button
This gets triggered

onClick={props.handleSubmit(vals => {
                  // onSubmit is defined in a wrapper component
                  props.onSubmit(vals, CONTENT_FORM_ACTIONS.PUBLISH);
                })}

Redux action uses the values to submit to api
on return of that api call, an initialize is called

dispatch(initialize('content', {
  id: savedItem.id,
  ...vals
}, false);

At this point, the 'content' redux-form has the correct state. initial is updated and so is values.
User types something in the form fields
User presses submit again. initial is correct and values are correct, BUT, the values sent to the handleSubmit method are still the initial. They never get set to values. The reducer is correctly updating, but handleSubmit does not. It's also worth mentioning that the dirty flag is correctly reset from the initialize, but any field modifications after that do not set the dirty flag to true.

It's like the react component is partially disconnected from redux-form after the initialize. By not doing an initialize, everything stays in sync.

I'm experiencing exactly the same behavior as @duhseekoh described with 7.2.0: the first submit works correctly, all subsequent ones receive the same stale values.

@urzhumskov - Since i commented on a closed issue, it probably isn't getting attention. Want to open a new issue? Feel free to copy any of my comments.


Error at installing

using :- pip install local-llm-function-calling[llama-cpp]
got following error:-
ERROR: Failed building wheel for llama-cpp-python
ERROR: Could not build wheels for llama-cpp-python, which is required to install pyproject.toml-based projects

This seems to be an issue with llama-cpp-python. Could not replicate. Closing for now.


Support of compressed files

Hello, I have the same problem described here: https://github.com/uni-halle/gerbil/issues/22
I tried to run Gerbil on different compressed fastq data and it systematically output the following error (sometimes with thread[1] and sometimes with thread[0]):
 〉gerbil -k 28 -l 2 -t 2 -i -e 4G fv.txt tmp_bins tmp_gres
______________________________________________
Gerbil version 1.12
================= PARAMETERS =================
size of k-mers          :    28
size of minimizers      :     7
threshold min           :     2
normalized kmers        :  true
number of temp-files    :   512
total number of threads :     4
number of splitters     :     2
number of hashers       :     2
input                   :       fv.txt
temp                    :       tmp_bins
output                  :       tmp_gres
size of memory          :  4096 MB
number of gpu's         :     0
---------------------------------------------
Thread[0]: read file 'SRR072013.fastq.gz' ( 587 MB)...
Thread[1]: read file 'SRR072029.fastq.gz' ( 553 MB)...
ERROR: unexpected end of stream (thread[1])! Archive corrupt?!

Any idea ?
Just in case, when I installed the tool, the cmake command output this (I have CMake 3.22 and I don't have CUDA):
CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- The C compiler identification is GNU 11.4.0
-- The CXX compiler identification is GNU 11.4.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.74.0/BoostConfig.cmake (found version "1.74.0") found components: system thread filesystem regex
-- Found BZip2: /usr/lib/x86_64-linux-gnu/libbz2.so (found version "1.0.8")
-- Looking for BZ2_bzCompressInit
-- Looking for BZ2_bzCompressInit - found
-- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.11")
-- Found Threads: TRUE
CUDA_TOOLKIT_ROOT_DIR not found or specified
-- Could NOT find CUDA (missing: CUDA_TOOLKIT_ROOT_DIR CUDA_NVCC_EXECUTABLE CUDA_INCLUDE_DIRS CUDA_CUDART_LIBRARY)
-- Build type: Release
-- Configuring done
-- Generating done
-- Build files have been written to: /home/paul/Travail/gerbil/build

make output:
[  5%] Building CXX object CMakeFiles/gerbil.dir/src/gerbil/Application.cpp.o
[ 11%] Building CXX object CMakeFiles/gerbil.dir/src/gerbil/Bundle.cpp.o
[ 17%] Building CXX object CMakeFiles/gerbil.dir/src/gerbil/FastFile.cpp.o
[ 23%] Building CXX object CMakeFiles/gerbil.dir/src/gerbil/FastParser.cpp.o
[ 29%] Building CXX object CMakeFiles/gerbil.dir/src/gerbil/FastReader.cpp.o
[ 35%] Building CXX object CMakeFiles/gerbil.dir/src/gerbil/KmcWriter.cpp.o
[ 41%] Building CXX object CMakeFiles/gerbil.dir/src/gerbil/KmerDistributor.cpp.o
[ 47%] Building CXX object CMakeFiles/gerbil.dir/src/gerbil/SequenceSplitter.cpp.o
[ 52%] Building CXX object CMakeFiles/gerbil.dir/src/gerbil/SuperReader.cpp.o
[ 58%] Building CXX object CMakeFiles/gerbil.dir/src/gerbil/SuperWriter.cpp.o
[ 64%] Building CXX object CMakeFiles/gerbil.dir/src/gerbil/TempFile.cpp.o
[ 70%] Building CXX object CMakeFiles/gerbil.dir/src/gerbil/debug.cpp.o
[ 76%] Building CXX object CMakeFiles/gerbil.dir/src/gerbil/gerbil.cpp.o
[ 82%] Building CXX object CMakeFiles/gerbil.dir/src/gerbil/global.cpp.o
[ 88%] Linking CXX executable gerbil
[ 88%] Built target gerbil
[ 94%] Building CXX object CMakeFiles/toFasta.dir/src/gerbil/toFasta.cpp.o
[100%] Linking CXX executable toFasta
[100%] Built target toFasta

UPDATE:
It might have something to do with the gz file, since it worked with another fastq.gz file from another source. But what's strange is that the tool kmc works fine with the original gz file, while gerbil doesn't.

FINAL UPDATE:
It seems the probleme comes from the fact that I used the tool parallel-fastq-dump to retrieve the fastq.gz files. The files are good, since they produce the exact same uncompressed file that we get with others method to retrieve the fastq.gz, and since kmc works well with them. However, gerbil seems to not be able to handle those files.
What I did is uncompress the "corrupted" fastq.gz files, and then re-compressed them with gzip, and now gerbil works.


Fix validation of empty/missing phone_number field in PhoneNumberMixin.

If a phone_number field is missing or empty, then PhoneNumberMixin.clean() fails with a key error because the field does not exist in cleaned_data. This patch fixes the clean_phone_number_field() method to only attempt to clean a field if it exists in cleaned_data.
Also added more comprehensive tests for the validation logic in the mixin, to ensure that required/optional phone number fields are correctly handled.

Shall we mention this in release notes?

Yeah, sorry, I forgot earlier. Have added a note to the release notes.


"unknown error" when user cancels technology request on iOS

Hello,
When I begin a technology request and press the Cancel button in the popup i get a "unknown error" string error.
I expected to get the error code 200 as defined in https://developer.apple.com/documentation/corenfc/nfcreadererror/code/readersessioninvalidationerrorusercanceled
When looking at the code I saw that this library tends to return localised string errors which is not a great idea if i want to handle the error cases in code. I really want the error code.
Thanks

I patched it locally using patch-package with this patch:
% cat patches/react-native-nfc-manager+2.1.1.patch
diff --git a/node_modules/react-native-nfc-manager/ios/NfcManager.m b/node_modules/react-native-nfc-manager/ios/NfcManager.m
index ad0d73e..40105ed 100755
--- a/node_modules/react-native-nfc-manager/ios/NfcManager.m
+++ b/node_modules/react-native-nfc-manager/ios/NfcManager.m
@@ -18,11 +18,13 @@
 NSString* getErrorMessage(NSError *error) {
     NSDictionary *userInfo = [error userInfo];
     NSError *underlyingError = [userInfo objectForKey:NSUnderlyingErrorKey];
-    NSString* result = [underlyingError localizedDescription];
-    if (result == nil) {
-        return @"unknown error";
+    if (underlyingError != nil) {
+        return [NSString stringWithFormat:@"%@:%ld,%@:%ld",
+                [error domain], (long)[error code],
+                [underlyingError domain], (long)[underlyingError code]];
     }
-    return result;
+    return [NSString stringWithFormat:@"%@:%ld",
+            [error domain], (long)[error code]];
 }

 @implementation NfcManager {

Hi @plol , that looks great! If you can make a PR for this, I will be happy to accept it and other users can definitely benefit from it.

Hi @plol , I have merged the patch and release 2.1.4. Thanks for the contribution!


[+] add commands config [init|upgrade], closes #514

[] reorganize config sources for better modularity
[] rename config package to cmdopts
[+] introduced new config commands for initializing and upgrading
[*] rename packages config types to CmdOpts
[+] add NewPostgresMetricReaderWriterConn()
[+] add NewPostgresSourceReaderWriterConn()

Pull Request Test Coverage Report for Build<PHONE_NUMBER>1
Details

29 of 148 (19.59%)  changed or added relevant lines in 10 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.4%) to 28.399%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sinks/postgres.go
1
2
50.0%

src/reaper/reaper.go
0
3
0.0%

src/metrics/postgres.go
1
7
14.29%

src/sources/postgres.go
1
7
14.29%

src/main.go
0
13
0.0%

src/cmdopts/cmdoptions.go
14
31
45.16%

src/cmdopts/cmdconfig.go
7
80
8.75%

Files with Coverage Reduction
New Missed Lines
%

src/main.go
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>0:
-0.4%

Covered Lines:
1339

Relevant Lines:
4715

💛  - Coveralls


Update 5.0.0 failed

Hi guys,
I just updated to 5.0.0 and I face this issues:
Ambiguous reference to member 'observe(_:options:handler:)'
I can't observer change of a key path.

Hey @vienvu89, I understand that you resolved your issue?

Yes, I resolve. It is my fault.
Thanks.

@vienvu89 Hey. I am facing this issue. How do I fix this?

@kaunteya I face it when I use it to observer update of key. So I fix it by:
example:  I change  let nameKey = DefaultsKey<String>.imageQuality to let nameKey = DefaultsKey<String?>("imageQuality")
and Defaults.observe(key: nameKey) { to  Defaults.observe(nameKey) {

I have added a variable in DefaultsKeys
extension DefaultsKeys {
    var showLineNumbers: DefaultsKey<Bool> { .init("showLineNumbers", defaultValue: false) }
}

And trying to add an observer in viewDidLoad
Defaults.observe(Defaults.showLineNumbers) { a in

}

I am getting the Ambiguous reference error here

@kaunteya You can consider changing Defaults.showLineNumbers to DefaultsKey<Bool?>("showLineNumbers"). It's a workaround to make it work.

hmm this is strange, wonder why it happens? @vienvu89 do you mean that only optional types can be observed? Did you try using Defaults.observe(\.showLineNumbers)?

@sunshinejr It works. Maybe it's better than my workaround.

Ah I see what you guys are trying to do. Defaults.showLineNumbers is not a key, it's a value! The key is showLineNumbers, which is in DefaultsKeys. So You could also fix this by using Defaults.observe(DefaultsKeys.showLineNumbers), but yeah the keypath syntax should be a lot nicer to use: Defaults.observe(\.showLineNumbers).
Let me know if it helps @vienvu89 @kaunteya.


Example XML/JSON Fragments

Can we make sure that any payload examples have

been validated
includes the meta.profile element

Done sprint 4


Add ssl certificate using DNS-01 via duckdns

Hi
Could you add the possibility to get ssl certificate using DNS-01 via duckdns  as with this docker
https://hub.docker.com/r/wuodan/docker-dehydrated-duckdns-cron
Thanks
Philippe

Hi,
I also would appreciate this solution.
Thanks and best regards

Hi
Very good news
Is it operational with the « latest » suffix ?
Philippe
Envoyé depuis mon IPhone SE 2020

Le 29 avr. 2021 à 13:38, jc21 @.***> a écrit :

Closed #969 via #1042.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi @pbranly ,
If I'm not wrong, a new version should be released to get it with the "latest" tag.
At this moment, you can test it with the "github-develop" tag.


Upgrade kaleido 0.2.1 -> 0.4.1 is causing errors in CI

Hi, first of all, thank you for this project. Really appreciate the work! After as of the 0.4.1 release several of our unit tests started failing here. In the meantime I've pinned our version to 0.2.1 and all is well but not sure if there's something deprecated that I didn't see before as our code hasn't changed in ages. Let me know if there's more information you need. Thank you.
         self._plotlyfier = os.path.join(
         os.path.dirname(os.path.dirname(os.path.abspath(__file__))),
         'vendor',
         'kaleido_scopes.js'
         )
         path = os.environ.get("BROWSER_PATH", which_browser())
         if tmp_path:
         temp_args = dict(dir=self.tmp_path)
         >       elif "snap" in path:
         E       TypeError: argument of type 'NoneType' is not iterable

         /usr/local/bin/python-3.12.0-1/lib/python3.12/site-packages/kaleido/scopes/plotly.py:64: TypeError

and also seeing this traceback as well with the only change being Kaleido 0.4.1
        # force a single process to manage the trace rendering
>       pio.kaleido.scope.chromium_args += (
            "--single-process",
            "--disable-gpu",
        )
E       AttributeError: 'PlotlyScope' object has no attribute 'chromium_args'

This might be the same as #223 but im not entirely sure

I have also just bit bitten by this issue.
My current workaround is to set BROWSER_PATH='None' in CI.
A possible solution to this is to change the following line
https://github.com/plotly/Kaleido/blob/245963391a86fdfa70bb6b96d853fbb30a3b388d/src/py/kaleido/scopes/plotly.py#L64
to:
-elif "snap" in path:
+elif path is not None and "snap" in path:

Happy to open a PR for this if you agree 👍

Opened a draft PR just in case you think this is a viable solution: https://github.com/plotly/Kaleido/pull/227

Had the same issue today and 0.2.1 saved me in jupyterlabs, you beat me by an hour or so :) I can now write images again, I was confused as it worked fine two days ago and figured it was something to with how I original installed things the first time.

+1 to fixing this issue.

+1 to fixing this issue - downgrading to 0.2.1 did NOT work within Azure Databricks
Attempted on

DBR: 12.2 LTS, 13.3LTS, 14.3LTS, 15.4LTS

After several hours of trying different DBR configs/Plotly versions/Kaleido versions, I've finally gotten it to work on
DBR: 15.4LTS
Plotly 5.1.0
Kaleido 0.1.0

just to help discoverability of this thread, another error you hit when you manually fix the elif "snap" in path: issue and then try to write a figure in binary format (PDF, PNG, ...)
-> 1035 view = memoryview(data)
   1036 with self.open(mode='wb') as f:
   1037     return f.write(view)

TypeError: memoryview: a bytes-like object is required, not 'NoneType'

Hi @janosh,
My suggestion is to pin the old version of kaleido <0.4.0 or use the new version of kaleido >=0.4.2 (v1.0.0rc) (you need to pin these as well or set --pre). This is very likely stems from a) using the new version of kaleido w/o downloading the dependency.
Plotly decided to yank the new version release so as not to force-update every given the dependency change:
One must now have chrome or chromium (or edge- wait) installed to use kaleido. We packaged it internally before but now it is too big for pypi's rules- we're looking at other methods.

A bug like "snap" in None could never happen if you were developing with a type checker...

A bug like "snap" in None could never happen if you were developing with a type checker...

While type annotation do make codebases more resistant to these sorts of bugs, in this specific instance since choreographer isn't annotated itself mypy would not catch this bug.
@s-banach I'm sure the maintainers would welcome a PR from you!


ProbCover

Hi! Can I expect ProbCover implementation in this repo? 👀

Hi Liangyu,
Thanks for your interest in our work!
I'll try push an implementation for ProbCover in the next week.
I'll update when it's ready.

Hi Liangyu,
I uploaded a ProbCover implementation.
Check out the changes here.
Usage example:
python train_al.py --cfg ../configs/cifar100/al/RESNET18.yaml --al probcover --exp-name auto --initial_size 0 --budget 100 --delta 0.6

I'm closing this issue for now, feel free to reopen it.


reset build-number to zero

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_22pvmuhagu/clone/recipe/meta.yaml:12: http_url: http://ftp.gnome.org/pub/GNOME/sources/msitools/0.100/msitools-0.100.tar.xz is not https
ERROR: /tmp/abs_22pvmuhagu/clone/recipe/meta.yaml:17: patch_must_be_in_build: patch must be in build when source/patches is set.
WARNING: /tmp/abs_22pvmuhagu/clone/recipe/meta.yaml:51: missing_description: The recipe is missing a description
WARNING: /tmp/abs_22pvmuhagu/clone/recipe/meta.yaml:51: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_22pvmuhagu/clone/recipe/meta.yaml:51: missing_license_url: The recipe is missing a license_url
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_09bog5hbaq/clone/recipe/meta.yaml:12: http_url: http://ftp.gnome.org/pub/GNOME/sources/msitools/0.100/msitools-0.100.tar.xz is not https
ERROR: /tmp/abs_09bog5hbaq/clone/recipe/meta.yaml:17: patch_must_be_in_build: patch must be in build when source/patches is set.
WARNING: /tmp/abs_09bog5hbaq/clone/recipe/meta.yaml:51: missing_description: The recipe is missing a description
WARNING: /tmp/abs_09bog5hbaq/clone/recipe/meta.yaml:51: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_09bog5hbaq/clone/recipe/meta.yaml:51: missing_license_url: The recipe is missing a license_url
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_f9oc_frrf1/clone/recipe/meta.yaml:12: http_url: http://ftp.gnome.org/pub/GNOME/sources/msitools/0.100/msitools-0.100.tar.xz is not https
WARNING: /tmp/abs_f9oc_frrf1/clone/recipe/meta.yaml:52: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_f9oc_frrf1/clone/recipe/meta.yaml:52: missing_description: The recipe is missing a description
WARNING: /tmp/abs_f9oc_frrf1/clone/recipe/meta.yaml:52: missing_license_url: The recipe is missing a license_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_d8wp64ge0j/clone/recipe/meta.yaml:12: http_url: http://ftp.gnome.org/pub/GNOME/sources/msitools/0.100/msitools-0.100.tar.xz is not https
WARNING: /tmp/abs_d8wp64ge0j/clone/recipe/meta.yaml:57: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_d8wp64ge0j/clone/recipe/meta.yaml:57: missing_license_url: The recipe is missing a license_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_9b_o7i689g/clone/recipe/meta.yaml:12: http_url: http://ftp.gnome.org/pub/GNOME/sources/msitools/0.100/msitools-0.100.tar.xz is not https
WARNING: /tmp/abs_9b_o7i689g/clone/recipe/meta.yaml:57: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_9b_o7i689g/clone/recipe/meta.yaml:57: missing_doc_source_url: The recipe is missing a doc_source_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_acp1lhkhu4/clone/recipe/meta.yaml:12: http_url: http://ftp.gnome.org/pub/GNOME/sources/msitools/0.100/msitools-0.100.tar.xz is not https
WARNING: /tmp/abs_acp1lhkhu4/clone/recipe/meta.yaml:58: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_acp1lhkhu4/clone/recipe/meta.yaml:58: missing_license_url: The recipe is missing a license_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_13udn3_acr/clone/recipe/meta.yaml:12: http_url: http://ftp.gnome.org/pub/GNOME/sources/msitools/0.100/msitools-0.100.tar.xz is not https
WARNING: /tmp/abs_13udn3_acr/clone/recipe/meta.yaml:58: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_13udn3_acr/clone/recipe/meta.yaml:58: missing_doc_source_url: The recipe is missing a doc_source_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_73mc7mmdxf/clone/recipe/meta.yaml:12: http_url: http://ftp.gnome.org/pub/GNOME/sources/msitools/0.100/msitools-0.100.tar.xz is not https
WARNING: /tmp/abs_73mc7mmdxf/clone/recipe/meta.yaml:61: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_73mc7mmdxf/clone/recipe/meta.yaml:61: missing_doc_source_url: The recipe is missing a doc_source_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_1bdgfjqy6v/clone/recipe/meta.yaml:12: http_url: http://ftp.gnome.org/pub/GNOME/sources/msitools/0.100/msitools-0.100.tar.xz is not https
WARNING: /tmp/abs_1bdgfjqy6v/clone/recipe/meta.yaml:61: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_1bdgfjqy6v/clone/recipe/meta.yaml:61: missing_license_url: The recipe is missing a license_url
Warnings were found

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_5ahoy71gdv/clone/recipe/meta.yaml:12: http_url: http://ftp.gnome.org/pub/GNOME/sources/msitools/0.100/msitools-0.100.tar.xz is not https
WARNING: /tmp/abs_5ahoy71gdv/clone/recipe/meta.yaml:61: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_5ahoy71gdv/clone/recipe/meta.yaml:61: missing_license_url: The recipe is missing a license_url
Warnings were found


Add 'contents' to TaskParameter

Allow for small scripts to be injected into the system, without having to go through the object store, using a 'contents' field in the TaskParameter (and leaving the location field blank)
Example:
{
   "inputs" : [
       { "path" : "/tmp/runtime.sh",
          "contents" : "#!/bin/bash\necho \"What up dog?\"\n"
       }
    ],
    "docker" : [
        {
            "imageName" : "ubuntu",
        "cmd" : ["/bin/bash", "/tmp/runtime.sh"]
        }
    ]
}

-1 I don't think I'd use this... I'm most concerned about large file inputs which I have to upload to an object store.  So I can't really avoid using an object store and would just bake in scripts into my docker image.

I'm 50/50 on this.
I feel like client libraries will already have code to support communication with a filesystem (e.g. object storage), so this probably isn't absolutely necessary and would add one more item to the list of things needed to implement a TES server.
Also, sometimes it's nice for debugging when files like this are written to an accessible filesystem, so that you can go hunting around afterwards to understand what happened. If they are written only to the worker node, you might have less/no access to those files for debugging.
Possibly this adds security risk as well, since we're talking about writing a file that's going to get executed and we need to apply limits to the size.
But, on the other hand, it would possibly be easy to implement and might be handy for keeping temporary files out of the object store. And, you might need just as much logic to figure out how/where/when you're going to store/cleanup run scripts in the object store.

This made me think of extensions:
Some APIs allow for extensions (I think Kubernetes does this) which is often a useful way to (dis)prove the utility of features before accepting into the core. Might be something keep in mind for the longer future of TES.

I wouldn't object to this but I also feel it's necessary either. Call that less "50/50" and more "I don't care enough to argue either way" :)

I've been chewing on a related idea, which is to give TES a limited storage API which would include get, put, and stat operations. TES already has a concept of storage backends, configuration, and URLs such as file:///path/to/foo and s3://bucket/path/to/foo.
get and put are obvious, I presume. stat would return metadata about the file.
Exposing that storage as a simple service could remove another chunk of commonly duplicated code from workflow engines and task submitters, which seems to fit the mission well. Most engines will need to write and upload a wrapper shell script, and I think they need to check for output files as well. Could a simple storage API enable both of those cases?
The API would have conservative size limits. I have thought of an exact number, but less than 32KB seems fine.
I envision that as a separate concern from a task execution schema. Perhaps that's a minor organizational detail, but I think it would be good for specs to have a separate experimental or incubation phase before they get merged into the core.

@buchanae I mentioned this on a previous GA4GH call but I'd love to see a standardized GA4GH storage API built around the S3 schema like you propose. By that I mean how to interact, put, get files and not storing arbitrary info/metadata/etc. Would such a thing cover what you're looking for?

That sounds pretty similar.
Could you clarify "and not storing arbitrary info/metadata/etc"?

@buchanae What I mean is I basically want it to operate like a filesystem/object store and nothing more. When I brought it up on the call the convo quickly devolved (from my perspective) into people talking about storing all kinds of information along with the files.

Makes sense. Yes, I agree it should be a simple as possible, and storing arbitrary metadata is more complex than I was envisioning.
One consideration is that if it's not useful enough and every client ends up needing a direct communication channel to do what they need, such as S3 metadata access, then the usefulness of a storage proxy API is gone.

@buchanae Right. My thought is just that if it's not something which would fit in what the world already pictures as an object store, then that concept should be something else instead of trying to jam the two concepts together

By the way, on Funnel at least, scripts can be easily packed into the cmd field
{
    "name": "Hello world",
    "projectId": "Funnel",
    "description": "Simple Echo Command",
    "resources": {},
    "docker": [
        {
            "imageName": "ubuntu",
            "cmd": ["/bin/bash", "-c", "#!/bin/bash\necho \"What up dog?\"\n"],
            "stdout": "stdout"
        }
    ]
}

If that fulfills the need, I'm not sure it's worth adding something new to the spec.

To argue with myself... :)
One place where contents might be useful is in the rabix/bunny TES backend, where they need to transmit a JSON file describing the CWL job. This is about 3-10KB in my experience, and might not fit well into the cmd field.

Fixed in #34


system_tests_tcp_adaptor TcpLiteCutthroughAbortTest failing

 =================================== FAILURES ===================================
____________ TcpLiteCutthroughAbortTest.test_aborted_streaming_link ____________

self = <tests.system_tests_tcp_adaptor.TcpLiteCutthroughAbortTest testMethod=test_aborted_streaming_link>

    def test_aborted_streaming_link(self):
        test = FakeClientStreamAborter(self.e_address, self.van_address, self.logger)
        test.run()
>       self.assertIsNone(test.error)
E       AssertionError: 'Timeout Expired' is not None

/home/gmurthy/actions-runner/_work/skupper-router/skupper-router/skupper-router/tests/system_tests_tcp_adaptor.py:2898: AssertionError

https://github.com/skupperproject/skupper-router/actions/runs/8392267222/job/22984523824#step:18:16160

@ganeshmurthy could this be a duplicate of #1293

Actually I retract the last comment - on further examination I think this is a flakey test. Looks like the test messaging handler state machine can miss the abort state.


[WIP] Upgrade Android Studio + 3rd parties libraries

Description
LEARNER-8243

Upgrade the Android Studio
Upgrade the 3rd parties libraries

Please Clean project after upgrade the libraries

close in support of PR#1791.


Update content of Terms of use and SLA to cover 2-factor authentication

Terms of use
EN: https://docs.google.com/document/d/1ThGNKO_oyKBSgm7R5Smi8goBIphCV-VTa3249J5sdDc/edit#heading=h.fmwmhh1x2vjv
FR: https://docs.google.com/document/d/1FcAIY3zbIykFu0vuEAgEYR6efJJboOBsE5sQ3P_IU9Y/edit#
Service-level agreement
EN: https://docs.google.com/document/d/16Wi9ySVvY6oTA9kGIL-fRRPswSmHbgnMToXOzj5Tz2c/edit#heading=h.56slma2l0sqo
FR: https://docs.google.com/document/d/1scIg3wPHHz2gZe2VUm_dRXolxtPR7Bti8XXwN-wE-28/edit#

Exploration of what Notify does in relation to 2FA

Bilingual changes for 2FA drafted for now. To be reviewed.
On hold to implement until feature is closer to being ready.


Disable use of GP-relative addressing

https://github.com/pspdev/psptoolchain-allegrex/issues/24

Hello, could you make a PR to platform_agnostic branch too, that's the default branch we use

Hello, could you make a PR to platform_agnostic branch too, that's the default branch we use

Hello, ok
https://github.com/pspdev/pthread-embedded/pull/2


Upgrade to PostgreSQL 11.x in local dev VM

Description
#955 tracks progress on upgrading PostgreSQL to 11.x in our AWS environments.  This task makes a similar upgrade to PostgreSQL in our local dev VM.
Acceptance Criteria

[x] check out bento/amazonlinux-2 box locally;
[x] install the following, and update scripts/dev/packer/provision-vm-packer.sh accordingly:

[x] PostgreSQL 11.11 (through postgresql11 in amazon-linux-extras);
[x] pgcrypto 1.3;
[x] postgis 2.5.2 with libprotobuf-c support for ST_AsMVT (see #981 );
[x] fuzzystrmatch 1.1;
[x] pg_trgm 1.4;
[x] pgrouting 2.6.1;

[x] generate a new box using packer;
[x] upload new box version to cot-move/cot-move-dev on Vagrant Cloud;
[x] test that running through the directions in MOVE developer onboarding using this box results in a working version of MOVE.

Additional Notes
From past updates here, it can take a couple of iterations to get the box right, and it might also be necessary to update documentation.

Finished this before my leave - marking closed.


Add message logger

Codecov Report

Merging #4 (afec2f5) into main (6c70111) will decrease coverage by 3.24%.
The diff coverage is 56.75%.

@@            Coverage Diff             @@
##             main       #4      +/-   ##
==========================================
- Coverage   76.05%   72.81%   -3.25%
==========================================
  Files           4        8       +4
  Lines         213      309      +96
==========================================
+ Hits          162      225      +63
- Misses         42       61      +19
- Partials        9       23      +14

Impacted Files
Coverage Δ

app/bot/bot.go
91.37% <ø> (ø)

app/events/superuser.go
0.00% <0.00%> (ø)

app/reporter/reporter.go
52.72% <52.72%> (ø)

app/events/mock_message_logger.go
100.00% <100.00%> (ø)

app/events/mock_tg_bot_api.go
66.66% <100.00%> (ø)

app/events/telegram.go
80.28% <100.00%> (+14.12%)
:arrow_up:

Continue to review full report at Codecov.

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


Rancher generated kubeconfig has same user id but different token

Currently running Rancher 2.2.8 and using the kubeconfig generated by it, I am able to individually authenticate to the respective clusters via kubectl. However, I want to merge the kubeconfig so I can use kubectl config use-context. In attempt to merge the kubeconfig, I encountered issue where the latter clusters could not be authenticated into.
> kubectl get nodes
error: You must be logged in to the server (the server has asked for the client to provide credentials)

Looking deeper into the merged kubeconfig, the problem appears to be that the user id used is shared for all clusters, however the authentication token is different for each. The resultant kubeconfig only keeps the token of the user for the first cluster, since it's all the same id.
...
current-context: my-cluster1
kind: Config
preferences: {}
users:
- name: user-d5dvk
  user:
    token: kubeconfig-user-d5dvk.c-6x2sn:sfs7fkdj5d89gbx8p9jsnf8jxlx8ljwdw8r2rwmsp444hq7qx7dsv8

See https://github.com/rancher/rancher/issues/19342