Multi mode gateway(ZNDMWG03LM) BLE device disconnected

The thing is like this
After updating approximately 3.2.0 to 3.2.1, the BLE devices on the gateway will gradually become "unavailable" every two days or so, but they can be operated on the Mijia APP. After clicking "reload" on the config/integrations page, these BLE devices will resume working
I have tried removing the gateway from the Mi Home app, then removing XiaomiGateway3 from the hassle and re adding and initializing it, but still cannot solve the problem;
I have also tried selecting [DANGER] Use storage in memory, but still cannot solve the problem;
Before making the above attempt, I ensured that the router settings had never changed and the gateway location had not changed. However, during this period, I added several BLE devices. I wonder if it was due to the addition of devices? Currently, XiaomiGateway3 controls 24 devices (4 zigbee, 20 BLE)
I'm not sure if it's related to the latest version update of XiaomiGateway3, so I'm trying to provide feedback

Same problem.

Same problem.

Same problem.

Looks like the same to me. Gateway - ZNDMWG03LM / FW - 1.5.4_0090
HA - 2023.05.02.
None off BLE devices working from 12.05. Including door lock, mesh spot lights, kettle and other devices.
"Cloud link" entity not available. Zigbee devices working.

Same problem, BLE devices works well but mesh devices become unavailable every serveral days.

Same problem, BLE devices works well but mesh devices become unavailable every serveral days.

咱们遇到的问题可能不一样...

Emmm yes, your problem is with BLE devices but mine is with mesh devices 😂

me to！

所有蓝牙mesh设备变成不可用了 ，重载也没有用 ， 卸载重装后可以用几个小时，然后又不可用。

Looks like discribed problem is gone after 2023.05.03 HA update. Right now all BLE devices available in HA.

I was running into the same issue, however, I can't clearly identify the reason.
Possible reasons are:

HA update
Gateway firmware update: mgl03_1.5.1_0032_mod20211108 -> mgl03_1.5.4_0090_mod20220510
3 days ago I installed mgl03_1.5.5_0006_mod20230517 - still working. Will see.

2.4gwifi   40MHz to 20MHz

I have recently switched to version 3.1.0 and it seems that the problem has been alleviated. At least there have been no issues in the past 4 days

Same here. 3.1.0 solved my issue. I have two gateway setup and I think this issue is related to multiple gateway support features introduced in 3.2.0.

@isdebug there is no info about your gateway firmware.
Are you sure we talking about BLE devices and not Mesh devices?
@micturkey I can confirm a situation where Mesh devices stop working and BLE devices continue. I'm trying to figure out why.

@isdebug you still haven't provided the firmware of your gateway

@isdebug there is no info about your gateway firmware. Are you sure we talking about BLE devices and not Mesh devices?
@micturkey I can confirm a situation where Mesh devices stop working and BLE devices continue. I'm trying to figure out why.

Thanks, waiting for update :).
Now I use an automation to reboot every gateways every 2 days, and mesh devices wouldn't stop working again.

https://github.com/AlexxIT/XiaomiGateway3/releases/tag/v3.3.0

``Viomi Kettle V-SK152 sensors info seems to be still unavailable.
gateway: Xiaomi ZNDMWG03LM
FW: 1.5.4_0090 (Custom)
Integration: 3.3.4
2023-10-31 07:36:48 [D] <IP_ADDRESS> [MQTT] miio/report_ack b'{"error":{"code":-7,"message":{"operation":"query_prod","pdid":1116}},"id":1518051946}'
2023-10-31 07:34:59 [D] <IP_ADDRESS> [BASE] b87c6fae0830 (1116) setup ble V-SK152: power, temperature, ble
2023-10-31 07:40:09 [D] <IP_ADDRESS> [MQTT] miio/report_ack b'{"id":2096716974,"result":{"operation":"keep_alive","intvl":1200,"delta":300,"filter":[{"mac":"B8:7C:6F:AE:08:30","pdid":1116,"ttl":7200,"desc":"has no permit"}]}}'
2023-10-31 07:41:52 [D] <IP_ADDRESS> [MQTT] miio/report b'{"id":1259895991,"method":"_sync.ble_query_prod","params":{"pdid":1116}}'
2023-10-31 07:41:52 [D] <IP_ADDRESS> [MQTT] miio/report_ack b'{"error":{"code":-7,"message":{"operation":"query_prod","pdid":1116}},"id":1259895991}'```


PERF-#6388: avoid masking in getitem when the number of rows to be taken > 90%

What do these changes do?

This change speeds up the workload I work on. I'll add a couple of synthetic examples a little later, but the pull request is ready for review.
Benchmark's result (best time): 5.4 sec (PR) vs 7.2 sec (master). Boost: ~25%.

 Benchmark
from time import time

import os

os.environ["MODIN_ENGINE"] = "Ray"
os.environ["MODIN_CPUS"] = "44"
os.environ["MODIN_BENCHMARK_MODE"] = "True"

import numpy as np
import modin.pandas as pd

random_state = np.random.RandomState(seed=42)

df = pd.DataFrame(random_state.randint(0, 10**6, size=(5 * 10**6, 64)))

new_index = df.index.values[:int(len(df.index)*0.9) + 1]
random_state.shuffle(new_index)

for _ in range(10):
    start = time()
    new_df = df.iloc[new_index]
    print(f"time: {time()-start}")

[x] first commit message and PR title follow format outlined here

NOTE:  If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

[x] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] signed commit with git commit -s
[x] Resolves #6388
[x] tests added and passing
[x] module layout described at docs/development/architecture.rst is up-to-date

Also I wonder if the threshold should be tuned - did you try different coefficients?

@vnlitvinov I believe that the coefficient can be further reduced, for this it is necessary to conduct more perf. experiments.

Blocked by https://github.com/modin-project/modin/pull/6457


alvisnlp-rest: PubAnnotation endpoint

We need an empty end-point for AlvisNLP--PubAnnotation:

One URL for each plan?
Accept the text parameter for direct input
Accept the sourcedb and sourceid parameters, should download the text by calling back pubannotation.org

Done with 96f67963aedc5d267282ed95c1a96e1e81cd7b97.
At the moment the PubAnnotation endpoint assumes the plan has a parameter named text that represents the input of a TextFileReader.


Refactor storeObject process

Refactor storeObject so that it can be called without supplying a pid, and revise the respective processes for finding, tagging and deleting objects.

The respective issue in HashStore (python) can be found here: Revise HashStore storeObject process
The corresponding pull request for the changes described can be found here: Feature-73: store_object Refactor (with References)

Issue Upgrade Java version from 1.8 to 17 has also been addressed in this branch.

Issue Review HashStore interface is also beeing addressed in this branch.

This has been completed via: Feature-55: storeObject and Reference Files Refactor


Added information about the enabled, visible, and checked properties

...when they can be set and what they mean.
Also tidied up the grammar and clarified wording.
Fix for doc issue https://github.com/atom/electron/issues/4884 .

Thanks for this :+1:


Randomized p0

Need a method to initialize UKF p0 according to a probability distribution.

Need to refactor SSASchedulerParams to work with new feature


Don't create log file if --log-http is not specified

Fix to --log-http behaviour; log file (http-requests.log) was always created, even if the option was not specified. This was due to the use of the default= argument to argparse. Default removed, gives expected behaviour - i.e. no log created if --log-http is not specified.

Maybe it would be better to allow --log-http to have a default filename, but not log a file if it is not specified. i.e.
[nothing] writes to no file
--log-http writes to http-requests.log
--log-http foo.log writes to foo.log
I think you can do this with nargs='?' as suggested at https://stackoverflow.com/questions/21997933/how-to-make-an-optional-value-for-argument-using-argparse

I tried the nargs='?' approach but it seems to cause problems in this particular case due to the required positional argument (the release tag). i.e.
python -m mrtarget.CommandLine --rea --log-http 18.08
is interpreted as using 18.08 for the log file name and thus there is an error about a missing release tag.


Evaluate generating BaselineTitles.json directly from the Baseline Markdown documents

This is the manually created JSON that maps the Rego JSON output to the HTML Report.
Every change to the titles/policy numbers in the Baseline docs we have to manually modify this JSON to reflect the changes in the Report.
This issue is for exploring generating this JSON dynamically from the Baseline Markdown docs.
Current markdown docx branch

Will track this issue in https://github.com/cisagov/ScubaGear/issues/228.


[Question] How do I get the recipes I added to the custom recipe gui?

Issue Description:
I notice when I add in the scripts, none of the recipes appear in the recipe book that's in the crafting table gui nor in the knowledge book
What happens:
After I remove the old recipes and add in new ones (replacing them basically), the new recipes do not appear in the recipe book
What you expected to happen:
The new recipes to appear in the recipe book and the knowledge book
Script used:
All scripts: https://hastebin.com/cagixuneru.scala
CraftTweaker Log: https://hastebin.com/korijetuvo.md

Affected Versions (Do not use "latest"):

Minecraft: 1.12
Forge: 1.12-<IP_ADDRESS>3
Crafttweaker: 1.12-4.0.2

Your most recent log file where the issue was present:
Forge Log: https://gist.github.com/NovaViper/149b5f863a2329e1b3925810e26c5afd

Did you restart your game?
On Aug 10, 2017 02:49, "Nova Leary"<EMAIL_ADDRESS>wrote:
Issue Description:
I notice when I add in the scripts, none of the recipes appear in the
recipe book that's in the crafting table gui nor in the knowledge book
What happens:
After I remove the old recipes and add in new ones (replacing them
basically), the new recipes do not appear in the recipe book
What you expected to happen:
The new recipes to appear in the recipe book and the knowledge book
Script used:
All scripts: https://hastebin.com/cagixuneru.scala
CraftTweaker Log: https://hastebin.com/korijetuvo.md
Affected Versions (Do not use "latest"):

Minecraft: 1.12
Forge: 1.12-<IP_ADDRESS>3
Crafttweaker: 1.12-4.0.2

Your most recent log file where the issue was present:
Forge Log: https://gist.github.com/NovaViper/149b5f863a2329e1b3925810e26c5a
fd
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jaredlll08/CraftTweaker/issues/293, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFS9xQsidkLIBIMhY2iGKPLixXePCiH3ks5sWlOygaJpZM4Oy0BO
.

@jaredlll08 I did

Update Crt?
On Aug 10, 2017 2:53 AM, "Nova Leary"<EMAIL_ADDRESS>wrote:

@jaredlll08 https://github.com/jaredlll08 I did
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jaredlll08/CraftTweaker/issues/293#issuecomment-321420458,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFS9xaAob4YiVH2MRhsp0wMYUVTm-FxCks5sWlR_gaJpZM4Oy0BO
.

Update Crafttweaker? I have the latest version of the mod

you sure?

I just noticed that there was an update, 4.0.3, <_> I must've not seen it yesterday. The recipes appear now, thanks!


Legend colors/values not working properly

I appear to have an issue where data values of 1 are sometimes colored properly, and sometimes colored as "less than 1" per the legend.  See attached image with a tooltip for the day, the first legend entry, and the second legend entry.  This is the legend code I'm using:
legend: [1,4,8,12,20]}
Not sure why days with a value of 1 are randomly showing gray.

I'm having the same problem.
Agree with @jamesburke-examtime that it looks like it's the legend title text that is wrong, with less than actually being less than or equal to etc... This (<=) is actually the behaviour I want (although perhaps it should be optional?), so it's just the title text that's wrong from my perspective.
Another thing with the legend is that if you're only using integers and have the legend set to single values (so [1, 2, 3, 4, 5]) then it'd be good to have the option to just show the actual numbers in the key, rather than "Less than 1", "Less than 2" etc...

Having this same issue. I think you can fix this by treating the legend values as the upper bound (inclusive).
So let's say a setting of [10, 20, 30, 40] would be interpreted as:
Legend 1: <= 10
Legend 2: 11-20
Legend 3: 21-30
Legend 4: 31-40
Legend 5: >= 40
I would personally include: Legend 0: empty - but that's for another discussion.

Comment above is right, the legend array values are threshold
Next v4 legend is rewritten from the ground up, and will allow more flexibility


Self-documenting settings template

Description

There is new helper to be used from Gradle task. It converts UtSettings.kt to resource file settings.properties.
So, actual state of UtSettings.kt (properties, defauls, relevant documentation comments) will allways be converted to bundled resource file we publish along with the plugin as top-level entry inside utbot-intellij-{version}.jar file.
Note, the template contains commented lines only so we free to change our hardcoded defaults later and re-write outdated template with new one until it's customized by user.

Just after IDE start (namely when plugin loads its settings) we check if settings.properties is presented in user's local file system as {home}/.utbot/settings.properties:

If not we create it from the resource template together with the folder is need.
If file already exists we copy resource template only if there are no custom (provided by user) values inside to persist existing users' configuration "as is".

Fixes #1412
Type of Change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Manual Scenarios
Scenario 1

Delete {home}/.utbot folder if exists.
Start IDE, wait for project loading.
The folder {home}/.utbot should be created automatically, for Windows it also should be marked as "hidden file".
There should be template file settings.properties inside.
If you delete the file it should appear again after IDE restart.

Scenario 2

Clear the file {home}/.utbot/settings.properties, leave just one line inside: disableCoroutinesDebug=true
Start IDE, wait for project loading.
As soon as property file contains defaults, it should be re-writen with template.

Scenario 3

Clear the file {home}/.utbot/settings.properties, leave just one line inside: disableCoroutinesDebug=false
Start IDE, wait for project loading.
As soon as property file contains custom value, it should stay as is.

Checklist (remove irrelevant options):

[x] The change followed the style guidelines of the UTBot project
[x] Self-review of the code is passed
[x] The change contains enough commentaries, particularly in hard-to-understand areas
[x] New documentation is provided or existed one is altered
[x] No new warnings

Some ideas from our discussion with @Vassiliy-Kudryashov and @olganaumenko:

Create settings.properties.template near to settings.properties - and recreate it every time the plugin is installed.
That can be useful to have the template with the current version of settings.

Select the most important settings. Which can be suggested first to the user.
They can be listed above all others. And described separately in docs.

@Vassiliy-Kudryashov Please check:
the changed settings are not applied (or may be not parsed)
To reproduce

Removed existing settings.properties file
Installed build from this branch
Restarted IDE
Opened generated settings.properties file
Uncommented the line with utBotGenerationTimeoutInMillis and changed value to 1000
Restarted IDE once more
Open UnitTestBot dialog

Expected behavior
Test generation timeout should be 1 sec
Actual behavior
Default test generation timeout is applied - 60 sec
Additional context
The same issue is when executing runIde task.
The issue is not reproducing in main - the change of this setting is applied.

@Vassiliy-Kudryashov
Also the usability question:

after UnitTestBot plugin installation there are 2 IDE restarts needed to apply new settings:

To generate settings.properties template
To apply changes in properties-file
Could we consider some improvements for this? Probably a discussion would help?

@Vassiliy-Kudryashov @Domonion
Could you please advise if we can log the settings that differ from default ones?
One the step of IDE start or when the test run is performed.
That can explain some issues and help with reproducing customer's bugs.


Continue/maintaining django-background-task

Hi @lilspikey
Based on #12, It seems that you stopped maintaining this project. Is this right?
If so, we https://github.com/arteria, would like to continue django-background-task. We use this app in production in various project and we would also invest in it by adding more useful feature, for example #6.
What do you think about that?

Hi Philippe,
I've not deliberately stopped maintaining this.  Real life has just got in
the way.  Issue #12 arrived after my daughter (2nd child) was only a few
weeks old.  I've been playing catchup with sleep and work ever since.
Hopefully I'll get some time and motivation to pick things back up, but as
issue #12 and #6 haven't been relevant to my work needs I've not got around
to doing them.
Obviously the beauty of github means you could fork this project if you
need to, but I do intend to maintain this going forward.
cheers,
John
On 4 March 2015 at 19:51, Philippe O. Wagner<EMAIL_ADDRESS>wrote:

Hi @lilspikey https://github.com/lilspikey
Based on #12 https://github.com/lilspikey/django-background-task/pull/12,
It seems that you stopped maintaining this project. Is this right?
If so, we https://github.com/arteria, would like to continue
django-background-task. We use this app in production in various project
and we would also invest in it by adding more useful feature, for example
#6 https://github.com/lilspikey/django-background-task/issues/6.
What do you think about that?
—
Reply to this email directly or view it on GitHub
https://github.com/lilspikey/django-background-task/issues/13.

--
http://psychicorigami.com/

Too many forks let the project dilute. Many great features are distributed over forks.
They should be combined again and an up-to-date release should then be placed on PyPI to allow others to use this great app in production.
Together we are stronger: what do you @lilspikey  think about creating an Github organisation (you could still be the owner!) and you will grant commit right to the arteria team. We chould handle the releasing and maintenance stuff. Here a reference of one of our own open sourced projects.
We could then continue the development and evolve django-background-task together.

Right so I see you have forked this.  I had kind of hoped that you'd have just submitted a pull request or something.
Still I guess that's the way things go.  Good luck.


#630 add mean func

Codecov Report

Merging #631 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #631   +/-   ##
=======================================
  Coverage   94.32%   94.32%
=======================================
  Files          60       60
  Lines        2169     2169
=======================================
  Hits         2046     2046
  Misses        123      123

Impacted Files
Coverage Δ

matchzoo/engine/base_model.py
93.1% <ø> (ø)
: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 0ec2a25...7547556. Read the comment docs.

#630

but why do you think it's a bug?

@bwanglzu It appears in classification task. In classification, we use categorical to compute both binary and categorical loss and metrics, which leads to


Category Filters for Wheel Spins

will be covered by #45, the user settings of filters will be pulled into the get random quest call


add ssl ca certificate settings

Added SSL CA certificate settings to ensure secure connections during HTTPS requests.

Thanks for PR


fix #12 Async all the way is still acceptable in console main method …

…since c# 7.1

Thank you for your correction 👍


API keys in querystrings?

The docs currently say:
apikeystring | API Key (can be submitted as query string)

Is that really true?

This is true.
For example following query works:
# as query string
curl https://author-tools.ietf.org/api/render/text?apikey=foobar -F<EMAIL_ADDRESS># as form parameter
curl https://author-tools.ietf.org/api/render/text -F 'apikey=foobar' -F<EMAIL_ADDRESS>

Does it need to be true? That will cause keys to end up in httpd logs.

Good point. This doesn't have to be this way. API keys were allowed in query strings to mimic how datatracker API handle requests.
I'll change Author Tools API to not to accept API key as query string.


Removed defercheck

Fixes #66
This removes defercheck from gometalinter, given that it is no longer available.

Thanks!


add support for other models

Is there a plan for supporting other models?
currently the library supports gpt 3.5 turbo and gpt 4.
The first model is fast enough, but not so precisly.
In addition, in case of a complex situation, the option that I followed is to have different schemas and make parallel calls, managing the results once they come back.
The second model is more accurate but very very slow.
In addition, in case of a complex situation, it's possible to manage the complexity also with a single schema. The problem is that almost always a timeout occurs (15 seconds not changeable).
Thank you,
Antonio

+1 - add support for other models: Phi-3, LLAMA, ...


Upload G-Code file programatically

Is it currently possible to upload G-Codes through the API? I see there's the command 'copyModel' but that just adds and already uploaded G-Code to the print queue. Also, manually adding the G-Code file to ProgramData\Repetier-Server\printer\MCF_Printer\models doesn't seems to work as Repetier doesn't detects it.

Sure it is. The frontend does so it must be possible:-)
Here a matching curl command
curl -i -X POST -H 'Content-Type: multipart/form-data' -F 'filename=@" & realFile & "' -F 'a=upload' -F 'apikey=11111111-8393-11e4-a892-00224d7b76cb' 'http://<IP_ADDRESS>:3344/printer/model/Eusthatios'
/printer/model = upload
/printer/job = print
next release also has a parameter "group" that defaults to "#" = Default. Has to do with the folders we added in 0.75.

PS: You can also use "sess" from websocket instead of api-key!

Thank you! Working great! Is it possible to contribute to the API docs? More examples with more details would be really helpful :)

You know docs are always the latest thing programmers do :-)
We will update the docs soon to contain some missing or new api calls for 0.75 which hopefully comes in april. I doubt I find the time to make more examples from our side. If you have some great examples we could include I would check them and try to find a good place for them. Eventually even a single example webpage we would link to from main docs.

Haha yeah it's ok :) Great! Looking forward for the new features! :)


Move repository to Git LFS

As the repository contains (and contained) a bunch of large files, the repository has grown to over 500MB in size. We should migrate the Repository to Git LFS to avoid users downloading the whole large history. Unfortunately, the git history needs to be rewritten.

Repository moved to Git LFS.


sc-8415 fix broken link on review page link

Scope of changes
sc-8415 fix broken link on review page link
Type of change

[x] bug fix
[ ] new feature
[ ] documentation
[ ] other (describe)

Acceptance criteria
The links in the text, "return to the Review Page" send the user to the Overview rather than the review page.
Author checklist

[x] I have manually tested the change and/or added automation in the form of unit tests or integration tests
[ ]  I have updated the dependencies list
[ ]  I have recompiled and included new protocol buffers to reflect changes I made
[ ]  I have added new test fixtures as needed to support added tests
[x]   Check this box if a reviewer can merge this pull request after approval (leave it unchecked if you want to do it yourself)
[x]  I have moved the associated Shortcut story to "Ready for Review"

Reviewer(s) checklist

[ ] Any new user-facing content that has been added for this PR has been QA'ed to ensure correct grammar, spelling, and understandability.

Codecov Report

Merging #733 (ff91adc) into main (a747591) will decrease coverage by 11.98%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main     #733       +/-   ##
===========================================
- Coverage   43.41%   31.42%   -11.99%
===========================================
  Files         583      478      -105
  Lines       17498     5406    -12092
  Branches     1311     1311
===========================================
- Hits         7597     1699     -5898
+ Misses       8714     3519     -5195
+ Partials     1187      188      -999

Impacted Files
Coverage Δ

...s/CertificateReview/LegalPersonReviewDataTable.tsx
30.00% <ø> (-3.34%)
:arrow_down:

.../gds-user-ui/src/components/ReviewSubmit/index.tsx
78.57% <ø> (+5.23%)
:arrow_up:

.../trisacrypto/directory/pkg/bff/db/organizations.go

...om/trisacrypto/directory/pkg/bff/api/v1/options.go

...m/trisacrypto/directory/pkg/gds/store/trtl/mock.go

...github.com/trisacrypto/directory/pkg/trtl/peers.go

...com/trisacrypto/directory/pkg/gds/config/config.go

...risacrypto/directory/pkg/gds/models/v1/contacts.go

...om/trisacrypto/directory/pkg/gds/client/profile.go

...ithub.com/trisacrypto/directory/pkg/bff/members.go

... and 97 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Building on 7.10 gives linker error

Trying to build hashable-<IP_ADDRESS> with GHC 7.10.3 results in the following error for me:
/usr/bin/ld: -r and -pie may not be used together
collect2: error: ld returned 1 exit status

System
I'm running Manjaro (Linux) on x86_64.
Additional information
I installed GHC via ghcup. My cabal version is 3.4 and the ld version is 2.36.1.
I noticed this while trying to test GHC 7.10 in the CI of primitive: https://github.com/haskell/primitive/pull/322.

This seems related to https://gitlab.haskell.org/haskell/ghcup-hs/-/issues/123. See the suggested workaround in https://gitlab.haskell.org/haskell/ghcup-hs/-/issues/123#note_346066.


Client-specific settings

Description
Ability to change client-specific settings, configure new clients, and enable/disable blocked services.
Screenshots

Version where feature was introduced
At least since v1.107.7

Hi. That feature is already available in the app. Go to Clients > Added and there you will see your added clients.


Customize the 'Submit a Report'/'Submit Entry' dialogue

I have been getting pinged that people want to have a more 'custom' look in the viewer mode.  One thing that would go a long way is just providing a dialogue to allow someone to customize this button.
It would be good to have it consistent across both pages as well, currently, the GeoForm submission area says "Submit Entry /  View Submissions" while the Viewer has "Submit a Report"

You can change these buttons by editing the js/nls/resources.js file.
line 64 changes the "Submit Entry" text
line 124 changes the "View Submissions" text
line 276 changes the "Submit a Report" text
There is also a "View Submissions" on line 261 but have not found it in the application
Not a fix for changing these while configuring the app but can do this as a workaround for now.
Hope this helps
Ray


Synthesis failed for nodejs-local-auth

Hello! Autosynth couldn't regenerate nodejs-local-auth. :broken_heart:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the nodejs-local-auth API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
2021-03-19 04:21:35,858 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/nodejs-local-auth
2021-03-19 04:21:36,428 synthtool [ERROR] > Failed executing git reset --hard master:

fatal: ambiguous argument 'master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 254, in _inner_main
    working_repo_path = synthtool_git.clone(f"https://github.com/{args.repository}.git")
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 90, in clone
    shell.run(["git", "reset", "--hard", committish], cwd=str(dest))
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'reset', '--hard', 'master']' returned non-zero exit status 128.

Google internal developers can see the full log here.

Autosynth is still having trouble generating nodejs-local-auth. :sob:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the nodejs-local-auth API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
2021-03-20 04:20:58,974 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/nodejs-local-auth
2021-03-20 04:20:59,565 synthtool [ERROR] > Failed executing git reset --hard master:

fatal: ambiguous argument 'master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 254, in _inner_main
    working_repo_path = synthtool_git.clone(f"https://github.com/{args.repository}.git")
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 90, in clone
    shell.run(["git", "reset", "--hard", committish], cwd=str(dest))
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'reset', '--hard', 'master']' returned non-zero exit status 128.

Google internal developers can see the full log here.

Autosynth is still having trouble generating nodejs-local-auth. :sob:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the nodejs-local-auth API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
2021-03-21 04:21:42,839 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/nodejs-local-auth
2021-03-21 04:21:43,311 synthtool [ERROR] > Failed executing git reset --hard master:

fatal: ambiguous argument 'master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 254, in _inner_main
    working_repo_path = synthtool_git.clone(f"https://github.com/{args.repository}.git")
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 90, in clone
    shell.run(["git", "reset", "--hard", committish], cwd=str(dest))
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'reset', '--hard', 'master']' returned non-zero exit status 128.

Google internal developers can see the full log here.

Autosynth is still having trouble generating nodejs-local-auth. :sob:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the nodejs-local-auth API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
2021-03-22 04:22:14,277 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/nodejs-local-auth
2021-03-22 04:22:14,777 synthtool [ERROR] > Failed executing git reset --hard master:

fatal: ambiguous argument 'master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 254, in _inner_main
    working_repo_path = synthtool_git.clone(f"https://github.com/{args.repository}.git")
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 90, in clone
    shell.run(["git", "reset", "--hard", committish], cwd=str(dest))
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'reset', '--hard', 'master']' returned non-zero exit status 128.

Google internal developers can see the full log here.

This is an issue because we've renamed master branch to main. I've reached out to @SurferJeffAtGoogle to migrate this to owl bot.

Autosynth is still having trouble generating nodejs-local-auth. :sob:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the nodejs-local-auth API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
2021-03-24 04:21:33,933 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/nodejs-local-auth
2021-03-24 04:21:34,411 synthtool [ERROR] > Failed executing git reset --hard master:

fatal: ambiguous argument 'master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 254, in _inner_main
    working_repo_path = synthtool_git.clone(f"https://github.com/{args.repository}.git")
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 90, in clone
    shell.run(["git", "reset", "--hard", committish], cwd=str(dest))
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'reset', '--hard', 'master']' returned non-zero exit status 128.

Google internal developers can see the full log here.

Autosynth is still having trouble generating nodejs-local-auth. :sob:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the nodejs-local-auth API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
2021-03-25 04:20:55,401 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/nodejs-local-auth
2021-03-25 04:20:55,922 synthtool [ERROR] > Failed executing git reset --hard master:

fatal: ambiguous argument 'master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 254, in _inner_main
    working_repo_path = synthtool_git.clone(f"https://github.com/{args.repository}.git")
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 90, in clone
    shell.run(["git", "reset", "--hard", committish], cwd=str(dest))
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'reset', '--hard', 'master']' returned non-zero exit status 128.

Google internal developers can see the full log here.

Autosynth is still having trouble generating nodejs-local-auth. :sob:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the nodejs-local-auth API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
2021-03-26 04:21:47,225 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/nodejs-local-auth
2021-03-26 04:21:47,709 synthtool [ERROR] > Failed executing git reset --hard master:

fatal: ambiguous argument 'master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 254, in _inner_main
    working_repo_path = synthtool_git.clone(f"https://github.com/{args.repository}.git")
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 90, in clone
    shell.run(["git", "reset", "--hard", committish], cwd=str(dest))
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'reset', '--hard', 'master']' returned non-zero exit status 128.

Google internal developers can see the full log here.

Autosynth is still having trouble generating nodejs-local-auth. :sob:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the nodejs-local-auth API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
2021-03-27 04:22:44,203 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/nodejs-local-auth
2021-03-27 04:22:44,711 synthtool [ERROR] > Failed executing git reset --hard master:

fatal: ambiguous argument 'master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 254, in _inner_main
    working_repo_path = synthtool_git.clone(f"https://github.com/{args.repository}.git")
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 90, in clone
    shell.run(["git", "reset", "--hard", committish], cwd=str(dest))
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'reset', '--hard', 'master']' returned non-zero exit status 128.

Google internal developers can see the full log here.

Autosynth is still having trouble generating nodejs-local-auth. :sob:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the nodejs-local-auth API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
2021-03-28 04:22:56,226 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/nodejs-local-auth
2021-03-28 04:22:56,714 synthtool [ERROR] > Failed executing git reset --hard master:

fatal: ambiguous argument 'master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 254, in _inner_main
    working_repo_path = synthtool_git.clone(f"https://github.com/{args.repository}.git")
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 90, in clone
    shell.run(["git", "reset", "--hard", committish], cwd=str(dest))
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'reset', '--hard', 'master']' returned non-zero exit status 128.

Google internal developers can see the full log here.

Autosynth is still having trouble generating nodejs-local-auth. :sob:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the nodejs-local-auth API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
2021-03-29 04:21:36,696 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/nodejs-local-auth
2021-03-29 04:21:37,252 synthtool [ERROR] > Failed executing git reset --hard master:

fatal: ambiguous argument 'master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 254, in _inner_main
    working_repo_path = synthtool_git.clone(f"https://github.com/{args.repository}.git")
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 90, in clone
    shell.run(["git", "reset", "--hard", committish], cwd=str(dest))
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'reset', '--hard', 'master']' returned non-zero exit status 128.

Google internal developers can see the full log here.


Cannot create schema_migrations

Describe the bug
I added the exandra to the deps {:exandra, "~> 0.6"}
Then I made a repo with config
defmodule Chats.XandraRepo do
  use Ecto.Repo,
    otp_app: :chats,
    adapter: Exandra
end

And generated a migration.
But when I run mix ecto.migrate I get the following error
[error] Could not create schema migrations table. This error usually happens due to the following:

  * The database does not exist
  * The "schema_migrations" table, which Ecto uses for managing
    migrations, was defined by another library
  * There is a deadlock while migrating (such as using concurrent
    indexes with a migration_lock)

To fix the first issue, run "mix ecto.create" for the desired MIX_ENV.

To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create", both for the desired MIX_ENV. Alternatively you may
configure Ecto to use another table and/or repository for managing
migrations:

I see my keyspace in cqlsh so the database definitely exists
What can I do to fix it?

What version of Exandra are you using? You specified ~> 0.6 on the issue, but the latest version is 0.7.5. What's the version in your mix.lock?
Also, is that the only error you get? IIRC there's more context to this.

"exandra": {:hex, :exandra, "0.6.5", "bb13655271cf28bdff1daa9f7516c57f20fd5c8d08c44c058eb28cb3bbb867ce", [:mix], [{:decimal, "~> 1.6 or ~> 2.0", [hex: :decimal, repo: "hexpm", optional: false]}
I'll try to upgrade exandra

Unfortunately upgrade did not help
15:36:48.383 [error] Could not create schema migrations table. This error usually happens due to the following:

  * The database does not exist
  * The "schema_migrations" table, which Ecto uses for managing
    migrations, was defined by another library
  * There is a deadlock while migrating (such as using concurrent
    indexes with a migration_lock)

To fix the first issue, run "mix ecto.create" for the desired MIX_ENV.

To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create", both for the desired MIX_ENV. Alternatively you may
configure Ecto to use another table and/or repository for managing
migrations:

    config :chats, Chats.XandraRepo,
      migration_source: "some_other_table_for_schema_migrations",
      migration_repo: AnotherRepoForSchemaMigrations

The full error report is shown below.

** (Xandra.ConnectionError) action "checkout from cluster #PID<0.212.0>" failed with reason: not connected to any of the nodes
    (ecto_sql 3.10.2) lib/ecto/adapters/sql.ex:1047: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.15.4) lib/enum.ex:1693: Enum."-map/2-lists^map/1-1-"/2
    (ecto_sql 3.10.2) lib/ecto/adapters/sql.ex:1154: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.10.2) lib/ecto/migrator.ex:756: Ecto.Migrator.verbose_schema_migration/3
    (ecto_sql 3.10.2) lib/ecto/migrator.ex:564: Ecto.Migrator.lock_for_migrations/4
    (ecto_sql 3.10.2) lib/ecto/migrator.ex:433: Ecto.Migrator.run/4
    (ecto_sql 3.10.2) lib/ecto/migrator.ex:170: Ecto.Migrator.with_repo/3
    (ecto_sql 3.10.2) lib/mix/tasks/ecto.migrate.ex:141: anonymous fn/5 in Mix.Tasks.Ecto.Migrate.run/2
    ```

    Looks like there is no connection, but `mix ecto.create` creates keyspace correctly 🤷

@pustserg what does your config look like? What env are you getting that error in?

action "checkout from cluster #PID<0.212.0>" failed with reason: not connected to any of the nodes

@pustserg also, this points you to the fact that the issue is that you cannot connect to the database, not that there is an actual issue creating the schema_migrations table.

@vinniefranco it's development env
dev.exs
config :chats, Chats.XandraRepo,
  hostname: "<IP_ADDRESS>",
  port: "9042",
  keyspace: "chats_dev",
  stacktrace: true,
  show_sensitive_data_on_connection_error: true,
  pool_size: 10

I tried with a localhost and without port option, result is the same
xandra_repo.ex
defmodule Chats.XandraRepo do
  use Ecto.Repo,
    otp_app: :chats,
    adapter: Exandra
end

action "checkout from cluster #PID<0.212.0>" failed with reason: not connected to any of the nodes

@pustserg also, this points you to the fact that the issue is that you cannot connect to the database, not that there is an actual issue creating the schema_migrations table.

I see it, but I'm wondered that mix ecto.create creates keyspace in the cassandra

@pustserg can you try to pass sync_connect: timeout to the config? Something like:
config :chats, Chats.XandraRepo,
  # ...,
  sync_connect: 5000 # Or any timeout you prefer

@whatyouhide checked. Error is the same :(

Can you run this and paste all the output (using the config above + sync_connect:
mix ecto.drop
mix ecto.create
mix ecto.migrate

@whatyouhide
➜  chats git:(main) ✗ mix ecto.drop
The database for Chats.XandraRepo has been dropped
The database for Chats.PostgresRepo has been dropped
➜  chats git:(main) ✗ mix ecto.create
The database for Chats.XandraRepo has been created
The database for Chats.PostgresRepo has been created

➜  chats git:(main) ✗ mix ecto.migrate

10:26:03.016 [error] Could not create schema migrations table. This error usually happens due to the following:

  * The database does not exist
  * The "schema_migrations" table, which Ecto uses for managing
    migrations, was defined by another library
  * There is a deadlock while migrating (such as using concurrent
    indexes with a migration_lock)

To fix the first issue, run "mix ecto.create" for the desired MIX_ENV.

To address the second, you can run "mix ecto.drop" followed by
"mix ecto.create", both for the desired MIX_ENV. Alternatively you may
configure Ecto to use another table and/or repository for managing
migrations:

    config :chats, Chats.XandraRepo,
      migration_source: "some_other_table_for_schema_migrations",
      migration_repo: AnotherRepoForSchemaMigrations

The full error report is shown below.

** (Xandra.ConnectionError) action "checkout from cluster #PID<0.212.0>" failed with reason: not connected to any of the nodes
    (ecto_sql 3.10.2) lib/ecto/adapters/sql.ex:1047: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.15.4) lib/enum.ex:1693: Enum."-map/2-lists^map/1-1-"/2
    (ecto_sql 3.10.2) lib/ecto/adapters/sql.ex:1154: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.10.2) lib/ecto/migrator.ex:756: Ecto.Migrator.verbose_schema_migration/3
    (ecto_sql 3.10.2) lib/ecto/migrator.ex:564: Ecto.Migrator.lock_for_migrations/4
    (ecto_sql 3.10.2) lib/ecto/migrator.ex:433: Ecto.Migrator.run/4
    (ecto_sql 3.10.2) lib/ecto/migrator.ex:170: Ecto.Migrator.with_repo/3
    (ecto_sql 3.10.2) lib/mix/tasks/ecto.migrate.ex:141: anonymous fn/5 in Mix.Tasks.Ecto.Migrate.run/2

Can you try using :nodes in the config?
config :chats, Chats.XandraRepo,
  nodes: ["<IP_ADDRESS>:9042"],
  keyspace: "chats_dev",
  stacktrace: true,
  show_sensitive_data_on_connection_error: true,
  pool_size: 10,
  sync_connect: 5000

and make sure you're on Exandra 0.8.1?


gcp deleting printers and re-adding them on transient errors from cups

Hi all,
We are investigating an issue where gcp receives an inconsistent error from cups when syncing, deletes the printer, and then re-adds it on next sync.
Example of errors from cups:
[Printer HCCI01AAMBGM03] Failed to call cupsGetPPD3(): 1282 Bad file descriptor
(this happens when we use sockets, cups seems to close it after 5 min and gcp does not handle it properly),  or
[Printer CCSI00ACEXGM07] Failed to call cupsGetPPD3(): 1280 No printer-uri found
(still no clue why this happens from time to time)
This is a problem for us because the printer gets re-added as "other printers" and users cannot use them for printing anymore.
Although the ideal fix would be to fix these bugs on cups, my sugestion is that gcp should only delete the printer if cups says explicitly that the printer does not exist, and not on any error.
I did a quick and dirty hack, but I believe the issue should be addressed properly by someone who knows the code.
I added:
# define HTTP_STATUS_NOT_FOUND        HTTP_NOT_FOUND

to cups/cups.h and:
      case C.HTTP_STATUS_NOT_FOUND:
               // printer does not exist @ cups
               if len(C.GoString(buffer)) > 0 {
                       os.Remove(C.GoString(buffer))
              	}
               C.free(unsafe.Pointer(buffer))
               return nil, fmt.Errorf("printer does not exist: %d", 404)

       default:
               //ignore all other errors, may be temporary
               if len(C.GoString(buffer)) > 0 {
                      	os.Remove(C.GoString(buffer))
               }
              	C.free(unsafe.Pointer(buffer))
              	return nil,nil
       }

to cups/core.go
Best Regards,
Bruno Silva

Had the same issue today on a newer CUPS installation. Had a large amount of Max Clients errors in cups, and right after we had 1 printer delete then re-add. Has not reproduced since a reboot. If anyone wants specific logs let me know and I will pull them.
Ubuntu 16.04
cups 2.1.3
GCP-Connector

Hi Avlis,
Please which function in cups.go do I add this code
case C.HTTP_STATUS_NOT_FOUND:
// printer does not exist @ cups
if len(C.GoString(buffer)) > 0 {
os.Remove(C.GoString(buffer))
}
C.free(unsafe.Pointer(buffer))
return nil, fmt.Errorf("printer does not exist: %d", 404)
   default:
           //ignore all other errors, may be temporary
           if len(C.GoString(buffer)) > 0 {
                  	os.Remove(C.GoString(buffer))
           }
          	C.free(unsafe.Pointer(buffer))
          	return nil,nil
   }

Hi Alvis,
Please may you help me know where to put the code that solves the issue?
Thank you.
Best Regards,
Prince Steven Annor
New York University Abu Dhabi - Class of 2020
Student Life Facilities Assistant
Mobile: +971 54 304 2559
http://nyuad.nyu.edu/
On Wed, Sep 27, 2017 at 8:05 PM, avlis<EMAIL_ADDRESS>wrote:

Reopened #366 https://github.com/google/cloud-print-connector/issues/366
.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/cloud-print-connector/issues/366#event-1268109737,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYqn-15ZciyWNqxRK3E0VgY37kDcA6I1ks5smnJOgaJpZM4OSgRB
.

Hi Steven,
it depends on your $GOPATH.
in my case, I have $GOPATH set to ~/gcp.compile, so the files cups.h and core.go are in:
~/gcp.compile/src/github.com/google/cloud-print-connector/cups/
Note: I have edited the original comment so it's clearer. I also replaced the hardcoded 404 by httpStatus.

Hi Avlis,
I found the two files, cups.h and core.go but I am not sure which function
in core.go your case and default blocks below go into. The code snippet has
a closing curly bracket at the end so I am confused about where in the
core.go file I should put your code below.
case C.HTTP_STATUS_NOT_FOUND:
// printer does not exist @ cups
if len(C.GoString(buffer)) > 0 {
os.Remove(C.GoString(buffer))
}
C.free(unsafe.Pointer(buffer))
return nil, fmt.Errorf("printer does not exist: %d", httpStatus)
   default:
           //ignore all other errors, may be temporary
           if len(C.GoString(buffer)) > 0 {
                  	os.Remove(C.GoString(buffer))
           }
          	C.free(unsafe.Pointer(buffer))
          	return nil,nil
   }

Thank you.
Best Regards,
Prince Steven Annor
On Thu, Sep 28, 2017 at 12:08 AM, avlis<EMAIL_ADDRESS>wrote:

Hi Steven,
it depends on your $GOPATH.
in my case, I have $GOPATH set to ~/gcp.compile, so the files cups.h and
core.go are in:
~/gcp.compile/src/github.com/google/cloud-print-connector/cups/
Note: I have edited the original comment so it's clearer. I also replaced
the hardcoded 404 by httpStatus.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/cloud-print-connector/issues/366#issuecomment-332640254,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYqn-8A7zCfzqE4_xXv1parB6fd7jFfLks5smqs3gaJpZM4OSgRB
.

its part of the switch httpStatus {, on func getPPD.

Found it!
Thanks Alvis!

I got bit by this today, having five printers deleted then readded. I've created a PR with a similar fix to @avlis.

I've closed my PR (#417) because it didn't actually prevent the printer from being deleted. To copy my findings from there, I only got the 1280 No printer-uri found issue when using CUPS_SERVER to point the connector to a CUPS server on another host. When I ran the connector on the same host as the CUPS server, the issue went away.


Qiskit’s OpenQASM 3 exporter:s not correctly escaping the names of custom gates it’s defining

Environment

Qiskit version:
Python version:
Operating system:

What is happening?
I submit a job to the IBM Platform, a max cut using QAOA, for very simple circuits (less than 10 nodes, few edges). This will produce a parameterized circuit.
The OpenQASM 3 string created cannot be drawn - there's something wrong with the string, likely not correctly escaping the names of custom gates it's defining.
Jake Lishman has requested I submit this bug report.
Here's an example of a string it produces:
"""
OPENQASM 3;
include "stdgates.inc";
input float[64] β_0;
input float[64] γ_0;
gate exp(it IZ)(γ_0) _gate_q_0, _gate_q_1 {
rz(5.0*γ_0) _gate_q_0;
}
gate rzz_140434630696240(γ_0) _gate_q_0, _gate_q_1 {
cx _gate_q_0, _gate_q_1;
rz(1.0*γ_0) _gate_q_1;
cx _gate_q_0, _gate_q_1;
}
gate exp(it ZZ)(γ_0) _gate_q_0, _gate_q_1 {
rzz_140434630696240(1.0*γ_0) _gate_q_0, _gate_q_1;
}
gate PauliEvolution(γ_0) _gate_q_0, _gate_q_1 {
exp(it IZ)(γ_0) _gate_q_0, _gate_q_1;
exp(it ZZ)(γ_0) _gate_q_0, _gate_q_1;
}
bit[2] meas;
qubit[2] q;
h q[0];
h q[1];
PauliEvolution(γ_0) q[0], q[1];
PauliEvolution(β_0) q[0], q[1];
barrier q[0], q[1];
meas[0] = measure q[0];
meas[1] = measure q[1];
"""
How can we reproduce the issue?
This code will not run for you as it depends on some custom functions and config files.
However, the problem should be reproducible from the concept - we are creating a really straightforward QAOA / maxcut problem.
from docplex.mp.model import Model
from qiskit_optimization.algorithms import MinimumEigenOptimizer
from qiskit_optimization.translators import from_docplex_mp
from qiskit_ibm_runtime import QiskitRuntimeService, Session, Sampler, Options
from qiskit_algorithms import QAOA
from qiskit_algorithms.optimizers import COBYLA, SPSA
from qiskit_aer.noise import NoiseModel

from quantum_computing_for_energy_sector.settings import load_config
from quantum_computing_for_energy_sector.utils import root_path, read_args, show_graph
from quantum_computing_for_energy_sector.logging_config import logger

token = load_config(root_path(".venv", "IBMQ-API-token.yml"))
args = read_args()

device_config = load_config(args.device_conf_file)
logger.info(f"Device config: {device_config}")

service = QiskitRuntimeService(
    channel = "ibm_quantum",
    token = token["IBM_Quantum_API_key"]
)

if device_config["device"] == "Simulator":
    backend = service.backend(device_config["simulator"])

backend = service.least_busy(operational=True, simulator=False)
graph_config = load_config(args.graph_conf_file)

number_of_nodes = len(graph_config["nodes"])
edges = [(edge['first_node'], edge['second_node'], edge['weight']) for edge in graph_config["edges"]]

model = Model()

x = model.binary_var_list(number_of_nodes)
model.maximize(model.sum(w * x[i] * (1 - x[j]) + w * (1 - x[i]) * x[j] for i, j, w in edges))

model.add(x[0] == 1)

problem = from_docplex_mp(model)

optimizer = COBYLA(maxiter = device_config["maxiter"])

session = Session(backend = backend)
options = Options()

sampler = Sampler(session = session, options = options)

qaoa = QAOA(sampler=sampler, optimizer=optimizer)
algorithm = MinimumEigenOptimizer(qaoa)
result = algorithm.solve(problem)

What should happen?
The code above will run - that is not the problem.
The problem is the OpenQASM 3 string that qiskit generates on the IBM Quantum Platform - this string has a bug in it. A circuit cannot be drawn from that string.
Any suggestions?
No response

Thanks for the report.  We have logic that does this in the OpenQASM 2 exporter, so I think we must have forgotten to port over similar behaviour to the OpenQASM 3 exporter.

I believe this should be fixed by #12776, but since I can't generate the exact initial circuit to check, I'm not absolutely 100% sure.  I'll mark it as "being fixed", and if I'm wrong, feel free to re-open (if it closes).


Feature Request: display free disk space on host page

Rancher Version: v1.1.0-dev1
It would be useful to be able to see the used / free disk space for a given host in the UI. It currently displays the sizes of the any attached storage, but not how full they are. I can currently see how much space CPU and memory I have, but not storage.

It'd be good to get a warning as well if the host is close to having its docker root volume full.

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


Update Composer dependencies (2021-12-02-00-11)

Visual regression test passed!
View the visual regression test report


Fixed roc format --stdin --stdout to format output

fixes #6088

Awesome, thanks!
I have this in draft because I think I technically need an approval from my
company (Google) to make this kind of open-source contribution. I’m not
sure about the legal specifics but I don’t want to have any issues after
merging in to main, and then having to surgically remove it from the repo
because “no that’s our code”. Just trying to be safe out of an abundance of
caution because big tech is big and sometimes scary.
I should get an approval this coming week, I’ll change this to a normal PR
once that happens.
Thanks again!
Crepe
On Sun, Nov 26, 2023 at 14:27 Richard Feldman @.***>
wrote:

@.**** approved this pull request.
@CrepeGoat https://github.com/CrepeGoat This looks ready to merge to me!
I've approved it, but since it's still in Draft, I wasn't sure if you
wanted to make any other changes before merging. 😄
—
Reply to this email directly, view it on GitHub
https://github.com/roc-lang/roc/pull/6095#pullrequestreview-1749418725,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABMXLE5XG7UGNKELTHNA5L3YGOX4PAVCNFSM6AAAAAA72V3BR2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTONBZGQYTQNZSGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Got the OK -> should be good to merge! Thanks again @rtfeldman  🙂

Don't worry about the test failures - something made it into main somehow. https://github.com/roc-lang/roc/pull/6117 should fix that, then this will be ready to merge! 🎉


Added set [{+|-}{e|x|xe|ex}] [ ]  to nsh

@LorenzMeier
I know you asked for a -e  option for nsh - I have added that and -x
Set the 'exit on error control' and/or 'print a trace' of
commands when parsing scripts in NSH.
Use 'set -e' to enable and 'set +e' to disable (ignore) the exit
condition on commands. The default is -e. Errors cause script to
exit.
Use 'set -x' to enable and 'set +x' to disable (silence) printing
a trace of the script commands as they are executed. The default
is +x. No printing of a trace of script commands as they are
executed.
Print expanded variables if -x
The settings are in effect from the point of execution,
until they are changed again, or in the case of the init
script, the settings are returned to the default settings
when it exits.
Included child scripts will run with the parents settings
and changes made in the child script will effect the parent
on return.

Addresses https://github.com/PX4/Firmware/issues/2639


Fixes #232 - Don't warn when mixing border and borderRadius + test

Can you please rebase and update the test to work with chai? Thanks!

Done, +1 switch to karma.


Make logging less verbose

Overview Of PR
This PR updates the log.rs file, changing the tracing format from pretty to compact. It also updates the if statement, adding the lines and source of the error when verbose is true, making it more verbose.

Ensuring less verbosity during logging.
Only verbose when the -v,  --verbose flag or RUST_LOG env variable is present.
Adds a filter layer to disable the spans while --verbose  or RUST_LOG is not enabled

References:
See improve logging - 1739

Thanks! Now this is an example output:
2024-11-19T06:47:52.864365Z  INFO release_plz::args: using release-plz config file release-plz.toml
2024-11-19T06:47:52.938231Z  INFO update:next_versions:download{self=PackageDownloader { packages: ["cargo_utils", "git_cmd", "test_logs", "next_version", "release-plz", "release_plz_core"], directory: "/var/folders/cf/zcqg_ct53g3dj0dy81063x500000gn/T/.tmpAy2i9x", registry: None, cargo_cwd: None }}: release_plz_core::download: downloading packages from cargo registry crates.io

What I would like instead is something even simpler:
2024-11-19T06:47:52.864365Z  INFO using release-plz config file release-plz.toml
2024-11-19T06:47:52.938231Z  INFO downloading packages from cargo registry crates.io

Thanks! Now this is an example output:
2024-11-19T06:47:52.864365Z  INFO release_plz::args: using release-plz config file release-plz.toml
2024-11-19T06:47:52.938231Z  INFO update:next_versions:download{self=PackageDownloader { packages: ["cargo_utils", "git_cmd", "test_logs", "next_version", "release-plz", "release_plz_core"], directory: "/var/folders/cf/zcqg_ct53g3dj0dy81063x500000gn/T/.tmpAy2i9x", registry: None, cargo_cwd: None }}: release_plz_core::download: downloading packages from cargo registry crates.io

What I would like instead is something even simpler:
2024-11-19T06:47:52.864365Z  INFO using release-plz config file release-plz.toml
2024-11-19T06:47:52.938231Z  INFO downloading packages from cargo registry crates.io

Done @MarcoIeni

Hey @MarcoIeni, wondering if you are aware of the Clippy error "elided lifetime has a name"? If it's okay with you, I can look into it.

Go for it! Please open a separate pr

thanks! I'm won't close the issue because I want to review log messages

I appreciate this was a pretty insightful task.

I want to review log messages and I want to think more about logging in general

No problem! I understand that logging can be tedious, especially with customizations. Let me know if I can help simplify this process for you. I would love to learn how you go about this

Let me know if I can help simplify this process for you.

Thanks, but first I need to understand what I want 😂
If you want to keep contributing I'm sure you can find other interesting issues. 👍
Thanks again!


fix alphabetical order

This minor fix to better handle alphabetical order.
The "#" character has a lower ASCII code then ".", ":" or other special character, so the dependencies are actually listed in a more natural order, based first on group and then on artifact id.
For instance, before:
and
group: a.b
artifactId: z
group: a.b.c
artifactId: a
where ordered in this way:

a.b.c:a
a.b:z

now instead they are ordered in this way:

a.b#z
a.b.c#a

thanks a lot @massimeddu-sj


Cesium no longer working with Webpack [Outdated Approach]

This blog  was very helpful to setup what we needed from Cesium on a Nuxt/Vue project using copy-webpack-plugin

Browser:
Chrome 113.0.5672.127 | 64 bit
Operating System:
Windows 10 Version 21H2 (OS Build 19044.2965)

https://github.com/CesiumGS/cesium/issues/11306#issuecomment-1561310854

Thanks @oussamabonnor1. More recently, we've been "maintaining" cesium-webpack-example, but it can certainly use a refresh.

Also, based on your title, can you provide more information on what makes this an outdated approach? Is it just that it's not working as-is, or does it go deeper?

Also, based on your title, can you provide more information on what makes this an outdated approach? Is it just that it's not working as-is, or does it go deeper?

Sorry @ggetz , I meant it's not working as-is. Using copy-webpack-plugin (or a similar approach) would be great if it's still an option on the table.

Also, based on your title, can you provide more information on what makes this an outdated approach? Is it just that it's not working as-is, or does it go deeper?

Sorry @ggetz , I meant it's not working as-is. Using copy-webpack-plugin (or a similar approach) would be great if it's still an option on the table.

How should nuxt2 use cesium? I urgently need this feature.

Also, based on your title, can you provide more information on what makes this an outdated approach? Is it just that it's not working as-is, or does it go deeper?

Sorry @ggetz , I meant it's not working as-is. Using copy-webpack-plugin (or a similar approach) would be great if it's still an option on the table.

How should nuxt2 use cesium? I urgently need this feature.

@bbhxwl Nuxt2 will only work with Cesium 1.92 and older using this approach https://cesium.com/learn/cesiumjs-learn/cesiumjs-webpack/#manage-cesiumjs-static-files
Anything newer than the 1.92 version will have to use a different approach (Nuxt3 or Webpack5 or...).
My package.json's dependencies section has these:
"cesium": "1.92",
"copy-webpack-plugin": "6",

Good luck! 💪

Also, based on your title, can you provide more information on what makes this an outdated approach? Is it just that it's not working as-is, or does it go deeper?

Sorry @ggetz , I meant it's not working as-is. Using copy-webpack-plugin (or a similar approach) would be great if it's still an option on the table.

How should nuxt2 use cesium? I urgently need this feature.

@bbhxwl Nuxt2 will only work with Cesium 1.92 and older using this approach https://cesium.com/learn/cesiumjs-learn/cesiumjs-webpack/#manage-cesiumjs-static-files Anything newer than the 1.92 version will have to use a different approach (Nuxt3 or Webpack5 or...).
My package.json's dependencies section has these:
"cesium": "1.92",
"copy-webpack-plugin": "6",

Good luck! 💪

Is there any bug in 1.92? My project currently does not support upgrading to nuxt3, so can't I have a better experience with cesium?

Also, based on your title, can you provide more information on what makes this an outdated approach? Is it just that it's not working as-is, or does it go deeper?

Sorry @ggetz , I meant it's not working as-is. Using copy-webpack-plugin (or a similar approach) would be great if it's still an option on the table.

How should nuxt2 use cesium? I urgently need this feature.

@bbhxwl Nuxt2 will only work with Cesium 1.92 and older using this approach https://cesium.com/learn/cesiumjs-learn/cesiumjs-webpack/#manage-cesiumjs-static-files Anything newer than the 1.92 version will have to use a different approach (Nuxt3 or Webpack5 or...).
My package.json's dependencies section has these:
"cesium": "1.92",
"copy-webpack-plugin": "6",

Good luck! 💪

Is there any bug in 1.92? My project currently does not support upgrading to nuxt3, so can't I have a better experience with cesium?

1.92 works fine! It just has less features than the newest available version. You can use it with Nuxt2.

Also, based on your title, can you provide more information on what makes this an outdated approach? Is it just that it's not working as-is, or does it go deeper?

Sorry @ggetz , I meant it's not working as-is. Using copy-webpack-plugin (or a similar approach) would be great if it's still an option on the table.

How should nuxt2 use cesium? I urgently need this feature.

@bbhxwl Nuxt2 will only work with Cesium 1.92 and older using this approach https://cesium.com/learn/cesiumjs-learn/cesiumjs-webpack/#manage-cesiumjs-static-files Anything newer than the 1.92 version will have to use a different approach (Nuxt3 or Webpack5 or...).
My package.json's dependencies section has these:
"cesium": "1.92",
"copy-webpack-plugin": "6",

Good luck! 💪

Is there any bug in 1.92? My project currently does not support upgrading to nuxt3, so can't I have a better experience with cesium?

1.92 works fine! It just has less features than the newest available version. You can use it with Nuxt2.

What features are missing? I want to see if I need them and if there are any explanations? If using CDN references, you can use the latest version, right?

Also, based on your title, can you provide more information on what makes this an outdated approach? Is it just that it's not working as-is, or does it go deeper?

Sorry @ggetz , I meant it's not working as-is. Using copy-webpack-plugin (or a similar approach) would be great if it's still an option on the table.

How should nuxt2 use cesium? I urgently need this feature.

@bbhxwl Nuxt2 will only work with Cesium 1.92 and older using this approach https://cesium.com/learn/cesiumjs-learn/cesiumjs-webpack/#manage-cesiumjs-static-files Anything newer than the 1.92 version will have to use a different approach (Nuxt3 or Webpack5 or...).
My package.json's dependencies section has these:
"cesium": "1.92",
"copy-webpack-plugin": "6",

Good luck! 💪

Is there any bug in 1.92? My project currently does not support upgrading to nuxt3, so can't I have a better experience with cesium?

1.92 works fine! It just has less features than the newest available version. You can use it with Nuxt2.

What features are missing? I want to see if I need them and if there are any explanations? If using CDN references, you can use the latest version, right?

What features are missing => check the change.log for a complete list. Can a CDN approach work => I never tested it but it sounds like it wont since the compilation/imports will just be replaced from being fetched locally to being fetched via a request. I recommend you test it and see :)
Good luck!

So it seems like I should upgrade my project. I'll try using nuxt3, can I use the latest one?

So it seems like I should upgrade my project. I'll try using nuxt3, can I use the latest one?

With Nuxt3. Yes!

So it seems like I should upgrade my project. I'll try using nuxt3, can I use the latest one?

With Nuxt3. Yes!

Do you have the correct method for loading maps with nuxt3? Ts
https://github.com/CesiumGS/cesium/issues/11586

Thanks @oussamabonnor1. More recently, we've been "maintaining" cesium-webpack-example, but it can certainly use a refresh.

Is it possible to use the latest version of cesium with nuxt2+webpack4?

Also, based on your title, can you provide more information on what makes this an outdated approach? Is it just that it's not working as-is, or does it go deeper?

Sorry @ggetz , I meant it's not working as-is. Using copy-webpack-plugin (or a similar approach) would be great if it's still an option on the table.

How should nuxt2 use cesium? I urgently need this feature.

@bbhxwl Nuxt2 will only work with Cesium 1.92 and older using this approach https://cesium.com/learn/cesiumjs-learn/cesiumjs-webpack/#manage-cesiumjs-static-files Anything newer than the 1.92 version will have to use a different approach (Nuxt3 or Webpack5 or...).
My package.json's dependencies section has these:
"cesium": "1.92",
"copy-webpack-plugin": "6",

Good luck! 💪

Is there any bug in 1.92? My project currently does not support upgrading to nuxt3, so can't I have a better experience with cesium?

1.92 works fine! It just has less features than the newest available version. You can use it with Nuxt2.

Can we consider how to be compatible with the latest version? Because upgrading to nuxt3 is too challenging for me.

Also, based on your title, can you provide more information on what makes this an outdated approach? Is it just that it's not working as-is, or does it go deeper?

Sorry @ggetz , I meant it's not working as-is. Using copy-webpack-plugin (or a similar approach) would be great if it's still an option on the table.

How should nuxt2 use cesium? I urgently need this feature.

@bbhxwl Nuxt2 will only work with Cesium 1.92 and older using this approach https://cesium.com/learn/cesiumjs-learn/cesiumjs-webpack/#manage-cesiumjs-static-files Anything newer than the 1.92 version will have to use a different approach (Nuxt3 or Webpack5 or...).
My package.json's dependencies section has these:
"cesium": "1.92",
"copy-webpack-plugin": "6",

Good luck! 💪

So it seems like I should upgrade my project. I'll try using nuxt3, can I use the latest one?

With Nuxt3. Yes!

I have a question to consult here.
https://community.cesium.com/t/cesium-ion-1-110-webpack-problem/27351

I'm going to close this as https://github.com/CesiumGS/cesium-webpack-example has been updated and is working with Webpack 5.
We are investigating wether we should provide an example of Webpack 4, specifically for use with Nuxt 2. However, given that Nuxt 2 will soon be end of life in June.

Also see https://github.com/CesiumGS/cesium/issues/11306


[docker] update debian base images

Motivation
Update debian base images.
Have you read the [Contributing Guidelines on pull requests]
Y
Test Plan
CI
Related PRs
None
If targeting a release branch, please fill the below out as well

Justification and breaking nature (who does it affect? validators, full nodes, tooling, operators, AOS, etc.)
Comprehensive test results that demonstrate the fix working and not breaking existing workflows.
Why we must have it for V1 launch.
What workarounds and alternative we have if we do not push the PR.

/land


Added automatic downloading of PrimateReaching

Automatic downloading of PrimateReaching added. Please have. a review.

We have changed one of the files from loco_20170217_02.mat to loco_20170215_02.mat to upgrade data quality

@jasonlyik have you figured out whether we can. use Pytorch code?

Yes, I believe this is not an issue.
Can you refer to the following example from speech2spikes: https://github.com/NeuroBench/neurobench/blob/main/neurobench/preprocessing/speech2spikes.py
https://github.com/NeuroBench/neurobench/blob/main/NOTICE
Please add a header to the file where you have copied code and copy in the pytorch LICENSE to that header and point to the repo. Also add a short statement to the neurobench NOTICE file.

Yes, I believe this is not an issue.
Can you refer to the following example from speech2spikes: https://github.com/NeuroBench/neurobench/blob/main/neurobench/preprocessing/speech2spikes.py https://github.com/NeuroBench/neurobench/blob/main/NOTICE
Please add a header to the file where you have copied code and copy in the pytorch LICENSE to that header and point to the repo. Also add a short statement to the neurobench NOTICE file.

The legal texts were added and please have a review.

Tao, there is a small typo in the dataset file which I commented on.
Otherwise everything looks good, once it is fixed we can pull this in!


Set global.platform when not set by the user

This change ensures that the openshift platform is set correctly even when the openshift profile isn't selected via spec.profile.
Users can now select a profile (e.g. remote) and still have the correct platform selected automatically.

@luksa: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_sail-operator_main
14e5a41f57893f59590342b117bd82295ca97e05
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@luksa: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_sail-operator_main
14e5a41f57893f59590342b117bd82295ca97e05
link
true
/test lint

integ-tests_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test integ-tests

integ-tests-arm64_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test integ-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@luksa: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_sail-operator_main
14e5a41f57893f59590342b117bd82295ca97e05
link
true
/test lint

integ-tests_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test integ-tests

integ-tests-arm64_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test integ-tests-arm64

unit-tests-arm64_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@luksa: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_sail-operator_main
14e5a41f57893f59590342b117bd82295ca97e05
link
true
/test lint

integ-tests_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test integ-tests

integ-tests-arm64_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test integ-tests-arm64

unit-tests-arm64_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test unit-tests-arm64

gencheck_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@luksa: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_sail-operator_main
14e5a41f57893f59590342b117bd82295ca97e05
link
true
/test lint

integ-tests_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test integ-tests

integ-tests-arm64_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test integ-tests-arm64

unit-tests-arm64_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test unit-tests-arm64

gencheck_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test gencheck

unit-tests_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@luksa: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-tests_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test integ-tests

integ-tests-arm64_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test integ-tests-arm64

unit-tests-arm64_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test unit-tests-arm64

gencheck_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test gencheck

unit-tests_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test unit-tests

lint_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@luksa: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-tests_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test integ-tests

integ-tests-arm64_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test integ-tests-arm64

unit-tests-arm64_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test unit-tests-arm64

gencheck_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test gencheck

unit-tests_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test unit-tests

lint_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test lint

e2e-kind-dualstack_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test e2e-kind-dualstack

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@luksa: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-tests_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test integ-tests

integ-tests-arm64_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test integ-tests-arm64

unit-tests-arm64_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test unit-tests-arm64

gencheck_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test gencheck

unit-tests_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test unit-tests

lint_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test lint

e2e-kind-dualstack_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test e2e-kind-dualstack

e2e-kind-multicluster_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test e2e-kind-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@luksa: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-tests_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test integ-tests

integ-tests-arm64_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test integ-tests-arm64

unit-tests-arm64_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test unit-tests-arm64

gencheck_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test gencheck

unit-tests_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test unit-tests

lint_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test lint

e2e-kind-dualstack_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test e2e-kind-dualstack

e2e-kind-multicluster_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test e2e-kind-multicluster

e2e-kind_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test e2e-kind

e2e-kind-olm_sail-operator_main
98c718cd99ca3d0cf69aac008a7a1a9552f14b82
link
true
/test e2e-kind-olm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.


Add SMTP writer

FEATURE REQUEST

Is there an open issue addressing this request? If it does, please add a "+1" reaction to the
existing issue, otherwise proceed to step 2.
No.

Describe the feature you are requesting, as well as the possible use case(s) for it.
I want to create a Mainflux Writer that can send me an email when a message to some topic (channel + subtopic) is received. In the ideal case, these messages are processed using some sort of rules engine so that I can specify rules when receiving emails to avoid spam messages and unnecessary traffic, but creating an SMTP writer is the first step in that direction. Potential,  use cases are limitless, but most of them are related to notifications and alarms.

Indicate the importance of this feature to you (must-have, should-have, nice-to-have).
This is a should-have.

@dusanb94 IMHO, this should not be a part of Core. Especially Core writers. Without knowing background of idea, I would put my two cents in different direction.
A good first step would be to work on data processing (e.g., new custom reader), which will outgrow the rules engine (still without notifications). The last part should be notifications/alarms or even better notification events (there is an ES in core) which would be collected and fireered via such Writters as SMTP.
It would be nice to have such an add-on (not as a Core service).

Since writers are primarily meant for message persistence, it makes sense not to put this in the writers. This can be extracted as a separate Notification service. Whether its place is in the core or not, I'm not sure at the moment. Let's leave it out for the time being. We can easily move it around later. The idea behind this service is rather simple: it consumes events/messages and sends notifications to the preconfigured email addresses. These messages/events will eventually come from the rules engine. Of course, later we can add more complex logic such as filtering notification receiver depending on some criteria and support for multiple protocols (push notifications, SMS).

I like the idea of extracting as separate service and domain naming "Notification service". The thing I don't get is  These messages/events will eventually come from the rules engine, which rules engine?
Maybe you think as service will listen to a specific topic/es and will do its job (send all messages from this channel as notifications) without taking care of rules or message source? This sounds good and usable. I really like the first step to a full-blown Rules engine with Notifications/Alarms, etc...
This is also very interesting  support for multiple protocols (push notifications, SMS). We can do like writers, for example, satisfying Pusher interface you will be able to implement different notifications email, push like firebase, SMS, etc.

@nmarcetic  Maybe you think as service will listen to a specific topic/es and will do its job (send all messages from this channel as notifications) without taking care of rules or message source? Exactly. The rules engine is yet to be made (or integrated using existing solutions), but the Notifications service will not care for the source. We can even attach it to send an email for every message on some Channel (or subtopic), for example, in cases that messages are not sent frequently.

@dusanb94 Got it!
This will be awesome!
Just to clarify when I sad "not be part of Core" I mean, it's probably best to be an add-on (in the same mono repo, as other add-ons).


It's doesn't work on Multi-Target in Cocoapod

Xcode version:  9.1
Firebase SDK version: Firebase/Core (4.4.0)
Firebase Component: Core

I try to adopt Firebase into my project that has multi-targets in 1 project.
The target that I created is Cocoa Touch Framework
This is my podfile
platform :ios, '9.0'
use_frameworks!

workspace 'FirebaseProve.xcworkspace'

target 'FirebaseProve' do

end

target 'SomeTarget' do
    pod 'Firebase/Core'
end

Next, I run my project and It show out the log
objc[39848]: Class FIRAIdentifiers is implemented in both xxx/FirebaseProve-gnlkwtltwmkpqgdfrahtyedtphzu/Build/Products/Debug-iphonesimulator/SomeTarget.framework/SomeTarget (0x10a645498)
and xxx/FirebaseProve.app/FirebaseProve (0x1098a6640).
One of the two will be used. Which one is undefined.
...

It's not only FIRAIdentifiers class but show many class from Firebase.
After that the application is crash.
I'm not sure that is a bug from Firebase or Cocoapod but It's work with other lib in Cocoapod. So I try to reported here.

The Firebase CocoaPods are static frameworks and cannot be linked into app libraries.

Firebase will continue to not support being embedded in dylibs for the time being, since shipping Firebase as a dynamic library has app launch time tradeoffs for all of our users.


Generalize the "Edit me (on Github)" button

We should come up with a solution that allows for other repo hosters as well.

Right now, docs.typo3.org allows GitHub, GitLab and Bitbucket Cloud and Server via Webhook.
In theory further systems should be allowed, if Webhook is triggered as expected. But those are the official supported hosters that we should support.


Routes generated by artisan not works

Routes generated by
php artisan ziggy:generate
not works because there's no
defaultParameters attribute
please fix it.

I'm gonna need a little more to work with. Can you provide:
Expected Behavior
If this is a new feature, give a usage example.
Current Behavior
If this is a new feature, is it a modification of an existing feature? Otherwise – none
For bug reports only please provide
Currently installed Laravel version:
5.5.28
Currently installed Ziggy version
0.6.0
Example route from your Laravel Routes file.
i.e. -
Route::get('/venues/{venue}', 'VenuesController@show')->name('venues.show');

Contents of Ziggy.namedRoutes
In dev tools type Ziggy.namedRoutes and copy the result here.
Ziggy call in context
i.e. –
// Api client is a wrapper around Axios
ApiClient.get(route('venues.show', {venue: 1}));