CosmosDB extension - failed to install

Failed to install the CosmosDB extension for Python 3.6.6 running Windows10
(I managed to repo this on two seperate machines)
(env) PS <C:\Users\zivr\OneDrive - Microsoft\LocalGit\Functions-Python\ServerlessAzureMgmt>> func extensions install --package Microsoft.Azure.WebJobs.Extensions.CosmosDB --version 3.0.0-beta7
Please specify one package reference to add.
Usage: dotnet add  package [options] <PACKAGE_NAME>
Python 3.6.6
Functions App core v2
Any thoughts ?

@zivraf can you share your function.json file?
What happens when you run func extensions install ?
/cc @soninaren

This issue was moved to Azure/azure-functions-host#3312


Remove link check for changes section

This removes the link checking for the Changes and Releases sections, as it's not realistic that we maintain outgoing links in changelogs.

Obsolete


p5.SoundRecorder example broken

Running the example here https://p5js.org/reference/#/p5.SoundRecorder gives me this error in the console:
arraySequence[channel] is undefined

...which later causes it to try to create a sound file with buffer length 0, which throws a different error.

The recording of the audio and the wav download works well for me, I tried in firefox and chrome, but it logs this warning:
p5.min.js?v=9299cb:2 textAlign(*, CENTER) requires x, y, width and height

and the 'Done! Tap to play and download' text does not appear.

Thanks for helping narrow this down! What OS do you use? in Chrome I get the same result as you, but get errors in Firefox 108 on MacOS 12.5.1.
For the text issue, it seems like that was added as a result of the fix for this issue https://github.com/processing/p5.js/issues/5785. If we want to fix it now, we can change these examples to text('something', 0, 0, width, height), but I'll also mention in the p5 repo that it seems to be causing existing examples to stop working.

There's now an issue here https://github.com/processing/p5.js/issues/5933 to track that text issue!

I am using windows 10

Ok, looks like it might just be a Firefox Mac issue then, which might not be p5.sound's doing. We can keep track of this and check back in the next version in case this is a Firefox Mac regression that gets fixed.

@davepagurek  I am getting this while using it on Firefox Mac

Thanks @tuminzee, looks like it is indeed a Firefox for Mac issue and not just for me! I haven't yet looked into what part is going wrong here, but let me know in the mean time if anyone feels like taking a look and gets any insight.

sure thing @davepagurek  I would love to give it a try, although I am not familiar with the whole codebase but this could be a good opportunity of learning for me, as in future I want to contribute more to this community

Sounds good! I'll assign this issue to you, let me know if I can give any pointers.

Thank you @davepagurek
I'll keep you updated

I found this https://github.com/processing/p5.js-sound/issues/499#issuecomment-994308373
I will go in this direction

good catch! that seems like the underlying cause, hopefully fixing that will fix this too!

@davepagurek I'll dig up the cause.
I'll keep you updated.


Added a new file

Hi @Kashishgoyal6300 Can you please sign CLA. Thank you!

This is spam, hence closing this PR.


Elasticsearch batch indexing fails without error

Using the NameUsageIndexServiceEs to index a dataset sometimes does not index all records.
There are no exceptions and the counter reports all records just fine. But the ES index does not contain all rows.
Digging into ES logs reveals there are indeed ES exceptions occurring (see below for larger stacktrace).

StrictDynamicMappingException: mapping set to strict, dynamic introduction of [nameIndexId] within [_doc] is not allowed

This one is based on an outdated index definition that can be fixed by creating a new index.
@ayco-at-naturalis Is there an option for the batch client to be aware of these errors and report them back, i.e. throw an indexing exception?
[2020-10-02T11:28:33,577][DEBUG][o.e.a.b.TransportShardBulkAction] [node-coldev] [dev-nu][0] failed to execute bulk item (index) index {[dev-nu][_doc][M7MS6XQBfBi8UciVIHg6], source[{"usageId":"757842","datasetKey":1106,"scientificName":"Goniocidaris (Cyrtocidaris) tenuispina var. tuberculata","nameStrings":{"sciNameLetter":"g","genusLetter":"g","genusOrMonomial":["goniocidaris"],"specificEpithet":["tenuispina"],"infraspecificEpithet":["tuberculata"]},"authorship":["Mortensen"],"authorshipYear":["1927"],"authorshipComplete":"Mortensen, 1927","nameId":"757842","nameIndexId":1672787,"rank":74,"type":0,"nomCode":5,"nameFields":[1,2,3,4,11,13,15],"status":2,"issues":[36],"classificationIds":["x4","x6","x8","xA","x5G","x5J","x3KC","x3KL","513291","513658","757842"],"classification":[{"rank":4,"name":"Animalia"},{"rank":8,"name":"Echinodermata"},{"rank":12,"name":"Echinoidea"},{"rank":33,"name":"Cidaroida"},{"rank":42,"name":"Cidaroidea"},{"rank":44,"name":"Cidaridae"},{"rank":52,"name":"Goniocidaris"},{"rank":53,"name":"Cyrtocidaris"},{"rank":63,"name":"Goniocidaris (Cyrtocidaris) tenuispina"},{"rank":64,"name":"Goniocidaris (Cyrtocidaris) tenuispina tuberculata"},{"rank":74,"name":"Goniocidaris (Cyrtocidaris) tenuispina var. tuberculata"}],"acceptedName":"Goniocidaris (Cyrtocidaris) tenuispina tuberculata","payload":"eJzlkktv2zAQhP9KwENPjC3KetgCgjZ9oAiC9JLcihxoam0tapEEScV2Df/3LpXYsZumTVGgPfQo6ltyZnY2DGtWsTIvx1nKOOu8nAOrNuwNnV7TgXIgAxDzOU3ShIuEpzzjWc4FT5OxKESSJLd77O2aVYSw1tQ4w1+P7bjd3B24qQzYXkJ/kBU5Z1q2vaJnlGQ8n/Ayz4rx5LekPJl7iZbGtCasLapPJOriKLko80LXsLqSQTU3a0uiR5zJLjTG+QYtwVfGBdAeND8Rk7SkKSf1F1aVGWdz0J0n5qPRaBTW0qEnAPXM0Uo0OFQfLIYGAkHv1i4cQN6CIu0HAD3Tobeo5e6OHzDdFJzqFjJESJl2SnhAo88PNG92Dii/R/2M8lqDdHTLgxFobaCcZnLhYRtvq8k/JWYczlGzigK10vm4h+C6iPggQ3Scfg+BDn20uRgV+ZjulkqB7Vd/38ubv95LPNJz1IyyHCf/rqQ1Lc9DuO+oSIoXSH3a4T2973A8FkU5ESL7s2YX/0WzQ5/J8xVPflLxdCLokQXGtFgTgq2Gw+VyOWgpAQ29N/AD4+ZDUA1qgzXIobQNyoFt7Gt7FuSqhiBx4V9hfbbfpYMZ0DuKVtw7HImyiOa8cl1AjV8herx0puEn57qmPvZ5P/59TwUlIk1EdpoUp+koZrGinyo8pEHf+g6d0S35iY+kt9uDfu0y234DGj76Sw=="}]}
org.elasticsearch.index.mapper.StrictDynamicMappingException: mapping set to strict, dynamic introduction of [nameIndexId] within [_doc] is not allowed
	at org.elasticsearch.index.mapper.DocumentParser.parseDynamicValue(DocumentParser.java:815) ~[elasticsearch-7.4.2.jar:7.4.2]
	at org.elasticsearch.index.mapper.DocumentParser.parseValue(DocumentParser.java:619) ~[elasticsearch-7.4.2.jar:7.4.2]
	at org.elasticsearch.index.mapper.DocumentParser.innerParseObject(DocumentParser.java:427) ~[elasticsearch-7.4.2.jar:7.4.2]
	at org.elasticsearch.index.mapper.DocumentParser.parseObjectOrNested(DocumentParser.java:395) ~[elasticsearch-7.4.2.jar:7.4.2]
	at org.elasticsearch.index.mapper.DocumentParser.internalParseDocument(DocumentParser.java:112) ~[elasticsearch-7.4.2.jar:7.4.2]
	at org.elasticsearch.index.mapper.DocumentParser.parseDocument(DocumentParser.java:71) ~[elasticsearch-7.4.2.jar:7.4.2]

That shouldn't be too hard ... in other words you want to map any exception occuring while indexing to a single, custom IndexingException?

Hmmmm ... client.performRequest is in itself not async. I think client.performRequest under the hood still spawns an asynchronous request, and then waits. But you would expect the es client to handle any http response appropriately. I anyhow do (indeed) not understand how this exception bubbles up. Do we have a full stack trace? Or is this message from the es server log? Otherwise I can put some log statements in executeRequest. Will think about it some more.

The problem is exactly that is does not bubble up. It is silently swallowed and I only found it in the ES logs (see above).
As it is a batch update I bet ES does an async update and the http request itself is probably only transmitting the data and returns before it is actually fully processed. So the request comes in fine, is checked that it is semantically correct and gets pushed to some internal ES "queue" for updating which at some point fails after the http response was already sent. But thats just my unproven theory. If true it would mean we have no chance to catch this...

Yes, I have one been digging in the source code of performRequest (I guess when we got the timeouts :-)) and it didn't seem ultra-solid, so what you describe seems a likely explanation. Certainly about the async update, because its non-asynchronous methods just wrap the asynchronous methods. Perhaps upgrading to ES 7.5.6 would solve it, but I don't know if this issue was explicitly mentioned in the version history.

Yes, I have once been digging in the source code of performRequest (I guess when we got the timeouts :-)) and it didn't seem ultra-solid, so what you describe seems a likely explanation. Certainly about the async update, because its non-asynchronous methods just wrap the asynchronous methods. Perhaps upgrading to ES 7.5.6 would solve it, but I don't know if this issue was explicitly mentioned in the version history.

we just upgraded to postgres 13 before we go live with the code in a few weeks.
Is it worthwhile upgrading ES to the latest before that too?

we just upgraded to postgres 13 before we go live with the code in a few weeks.
Is it worthwhile upgrading ES to the latest before that too?

Hmmm, that makes me think, maybe we should after all do asynchronous, so we have better control over what happens. We could, just like ES it self block until the request comes back to mimick non-asynchronicity.

but that would slow down our indexing if we block?
It takes up already most of the import and sync time and is the bottleneck. Mostly due to very expensive recursive reads in postgres though.

I wouldn't just update to 8 until you or I have ample time to test it. But upgrading to the latest 7.x version should be innocuous (although with ES you never quite know for sure)

but that would slow down our indexing if we block?
It takes up already most of the import and sync time and is the bottleneck. Mostly due to very expensive recursive reads in postgres though.

Well - I mean we could mimick doing a non-asynchronous request (but just be more in control), as have done until now.
We could of course also go "full-throttle" asynchronous, but then we have to be even more alert on the HTTP 429 (Too Many Requests) and similar consequences.
If the indexing happens in the blink of an eye compared to all the ploughing of postgres, it might not gain us much. Otherwise yes, letting go of synchronous requests is a good idea.

Unfortunately I don't have much time the coming 2/3 weeks ... can it wait that long?

yes. Let's first get things public before we do this step.
But first Naturalis needs to hand over the CoL DNS entry to GBIF ;)

Ah .. maybe you should know we've suffered a sudden drain of infrastructure guys (e.g. Hugo no longer works for us). If Olaf didn't tell you, it's probably best to now contact<EMAIL_ADDRESS>

thanks, I'll give David a try


VS Code not recognizing the Anaconda packages installed.

Environment data

VS Code version: 1.24.1
Extension version (available under the Extensions sidebar): XXX
OS and version: Win 10
Python version (& distribution if applicable, e.g. Anaconda): 3.6.5
Type of virtual environment used (N/A | venv | virtualenv | conda | ...):  conda root
Relevant/affected Python packages and their versions: XXX

Actual behavior
Traceback (most recent call last):
File "test.py", line 1, in
import numpy as np
ImportError: No module named numpy
Expected  behavior
Import numpy from Anaconda environment and run the desired code.
Steps to reproduce:

Installed Anaconda
Open Anaconda Navigator
Install VS Code from Navigator
Install necessary extensions (Anaconda, Python 3.6, C/C++)
ctrl + shift + p and select anaconda environment
Install numpy via Conda prompt into root env
save all, close & reopen VS Code
Double check path in python.pythonPath is in the Anaconda directory
run a sample numpy code.

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)

Doesn't look like you are you are debugging.
If you want to run a file then select the command it menu item Run Python file in terminal.
It you could create a terminal activated with that coma environment, using Pythin : Create Terminal, then extras the command ptython test.py


NetJavaImpl$HttpClientResponse.getResultAsStream shouldn't return silently an error stream

Hi,
The implementation of NetJavaImpl$HttpClientResponse.getResultAsStream is as follow:
public InputStream getResultAsStream () {
    return getInputStream();
}
...
private InputStream getInputStream () {
    try {
        return connection.getInputStream();
    } catch (IOException e) {
        return connection.getErrorStream();
    }
}

I don't see any - good, reliable - way to figure out if the returned stream is the expected one or not... Is there any rational behind this?
Thanks,
Franck.

honestly, all the suppressing going in in NetJavaImpl (and related HTTP classes) is IMO a very bad thing... it made the debugging of https://github.com/libgdx/libgdx/issues/3226 and couple of other HTTP issues I encountered a real PITA; if it was my decision, I'd add a boolean flag, allowing toggling the exception suppression off if needed; for the time being, I just forked the code and added the exception propagation by hand.
If somebody decides it's worth it and does a PR - he gets my most sincere thumb up for it.

Yeah, that's no good. We should fix it proper and get rid of the old behavior.

Duplicate of #4700


Maintainers list cleanup process

Today all the packages in opensearch-project such as common-utils have the list of maintainers which is controlled by the MAINTAINERS.md file. We do have process defined by how we add people to the maintainers list depending upon their contributions and engagement in reviewing PRs, triaging issues etc.
However, this doesn’t necessarily imply that MAINTAINERS.md becomes the ever growing list of maintainers. We should come  up with some unified process around cleaning up the list, based on the recency of the activities of the maintainers. Such as inactivity for 60 days.
Opening up this issue to collect more feedback/thoughts. Also to know, if we have already given some thought to it previously.

Is 60 days sufficient or should we possibly consider 90 days for repos like this as typically there are not many changes going in. Also I think inactivity should mean they do not push commits, review PRs, add github issues, or coment on github issues.

This has been later discussed broadly as part of https://github.com/opensearch-project/.github/pull/59.
The new proposal should apply to all the OpenSearch Repositories.


Improve the cron display

Coverage remained the same at 27.714% when pulling 9cbc6ca3914a4795bd2ad04703cd8cec8c8b1053 on sylvestre-patch-6 into 884b88cf18b3b964307201ad1da28ae054061b0a on master.


add integrity checks to TreeMap

And remove some cruft.
cc #85

I will be moving check_{left,right} into is_valid and adding some tests. Don't merge yet.

Under what contexts will ndebug be set for downstream dependencies? This is pretty epic bloat if you don't have that set.

Per crates.io:

Cargo supports custom configuration of how rustc is invoked through profiles at the top level. Any manifest may declare a profile, but only the top level project's profiles are actually read. All dependencies' profiles will be overridden. This is done so the top-level project has control over how its dependencies are compiled.

https://github.com/rust-lang/rfcs/pull/563 is relevant, but doesn't appear to affect the usage of debug_assert.

Could we perhaps roll our own cfg for integrity checks, so that these only run in true testing?

Could certainly use an explicit #[cfg(test)], but if this isn't the use
case for debug_assert, what is?
On Tuesday, January 13, 2015, Alexis Beingessner<EMAIL_ADDRESS>wrote:

Could we perhaps roll our own cfg for integrity checks, so that these only
run in true testing?
—
Reply to this email directly or view it on GitHub
https://github.com/Gankro/collect-rs/pull/91#issuecomment-69835097.

The problem is that this is insanely expensive. I think debug_asserts are generally for cheap-but-not-free things. Like optional bounds checks.

In that case, I can add a macro like test_assert that requires cfg(test) and use it instead of debug_assert. If that sounds good to you, I can update IntervalHeap to do the same thing.

If we migrate to cfg(test)-only, then we might not want this after all. The tests can just perform the integrity checks directly, as they were doing previously.


⚠ GitLab Server has degraded performance

In 5edbd10, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 9582 ms

Resolved: GitLab Server performance has improved in f3af1dd.


Bugfix/#487

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

37 of 37 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.05%) to 90.126%

Totals

Change from base Build<PHONE_NUMBER>5:
0.05%

Covered Lines:
6316

Relevant Lines:
6907

💛  - Coveralls


Please update plugin to compatable with flutter 3.0.4

We are facing issue to run app on flutter 3.0.4 sdk.This plugin unable to maintain compatabilty with other firebase plugin .

We will update soon

Also please check Android 12 compatabilty

@parmeetmaster We couldn't reproduce your issue with flutter 3.3.2 and and firebase_core 1.23.0 on Android 12 and 13 .
Which versions of our package and firebase plugin  are you using?
And send your stacktrace, please.

@parmeetmaster
This package cannot have issues related to 3rd party Firebase plugins as there are no transitive dependencies.
Can you attach the stack trace containing the error?


Add ban/unban/kick directly to Member

Summary
Provides convenience methods for banning/unbanning/kicking Members directly instead of having to go through Server.
Resolves #45
Current:
member.server.ban(member, reason: 'bonk')

New:
member.ban(reason: 'bonk')

Added
Member#ban
Member#unban
Member#kick

Thank you!


Blacklist copy and url updates

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

Two changes:

updates URL for installing pip
updates blacklist message for macruby since the project has been abandoned

Merged in 3e309d4643ab52ce823b8733d72f8665133dbf5e. Thank you for this contribution to Homebrew, @tonyta! You rock! :tada:


Hide window on ESC key

Alternative shortcut to hide the window. It is not practical every time to use the mouse to hide. Using the ESC key is a fast and intuitive way to hide the window quickly.

this only works with focus on the input area. while focus is there most of the time the shortcut shold be associated to the entire app
on mac you can do cmd + h or cmd + w. Other OS may altread have their own shortcuts i think, isn't it ?

On Windows/Linux you can use ctrl+h to hide the window

@bryanzw15  -  CTRL+H does nothing on Linux (LXDE at least)

@ctcpip I just tested on Windows 10 and Ubuntu 16.04 and it works, maybe you're not fully updated? Otherwise it's just a weird issue with LXDE

More likely just the difference in desktop environment than anything else.

I'm not sure if this ESC key is a good idea. I merge it for the moment


ostree: 2022.1 -> 2022.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ostreedev/ostree/releases.
meta.description for ostree is: "Git for operating system binaries"
meta.homepage for ostree is: "https://ostree.readthedocs.io/en/latest/"
meta.changelog for ostree is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
Warning: no invocation of /nix/store/dsd60r2m9ispfldih7snibf4q9srg3dz-ostree-2022.2/bin/ostree had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/dsd60r2m9ispfldih7snibf4q9srg3dz-ostree-2022.2/bin/.ostree-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/dsd60r2m9ispfldih7snibf4q9srg3dz-ostree-2022.2/bin/.rofiles-fuse-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/dsd60r2m9ispfldih7snibf4q9srg3dz-ostree-2022.2/bin/rofiles-fuse had a zero exit code or showed the expected version
0 of 4 passed binary check by having a zero exit code.
0 of 4 passed binary check by having the new version present in output.
found 2022.2 with grep in /nix/store/dsd60r2m9ispfldih7snibf4q9srg3dz-ostree-2022.2
found 2022.2 in filename of file in /nix/store/dsd60r2m9ispfldih7snibf4q9srg3dz-ostree-2022.2

Rebuild report (if merged into master) (click to expand)

27 total rebuild path(s)

26 package rebuild(s)

26 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
flatpak
flatpak-builder
gnome-builder
gnome.gnome-software
haskellPackages.gi-ostree
libsForQt5.discover
libsForQt512.discover
libsForQt514.discover
libsForQt515.discover
malcontent-ui
minishift
ostree
pantheon.appcenter
pantheon.elementary-greeter
pantheon.elementary-onboarding
pantheon.sideload
pantheon.switchboard-plug-applications
pantheon.switchboard-with-plugs
pantheon.wingpanel-applications-menu
pantheon.wingpanel-with-indicators
plasma5Packages.discover
rpm-ostree
vala-language-server
xdg-desktop-portal
xdg-desktop-portal-gnome
xdg-desktop-portal-gtk

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/dsd60r2m9ispfldih7snibf4q9srg3dz-ostree-2022.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ostree https://github.com/r-ryantm/nixpkgs/archive/5e483c35dd1dd205254ee3e56f1f57bfa64d6e2b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/dsd60r2m9ispfldih7snibf4q9srg3dz-ostree-2022.2
ls -la /nix/store/dsd60r2m9ispfldih7snibf4q9srg3dz-ostree-2022.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages marked as broken and skipped:

libsForQt512.discover
libsForQt514.discover

21 packages built:

flatpak
flatpak-builder
gnome-builder
gnome.gnome-software
libsForQt5.discover
malcontent-ui
minishift
ostree
pantheon.appcenter
pantheon.elementary-greeter
pantheon.elementary-onboarding
pantheon.sideload
pantheon.switchboard-plug-applications
pantheon.switchboard-with-plugs
pantheon.wingpanel-applications-menu
pantheon.wingpanel-with-indicators
rpm-ostree
vala-language-server
xdg-desktop-portal
xdg-desktop-portal-gnome
xdg-desktop-portal-gtk

Maintainer pings
cc @copumpkin for testing.

Test failures -2+1 compared to previous update:
SUMMARY: total=123; passed=121; skipped=0; failed=2; user=573.9s; system=224.6s; maxrss=108556
FAIL: libostree/test-cli-extensions.sh.test (Child process exited with code 1)
FAIL: libostree/test-basic-bare-split-xattrs.sh.test (Child process exited with code 2)

basic-bare-split-xattrs is a new test.


the netatmo thermostat does not appear

Home Assistant release with the issue:

Home Assistant 0.91.3
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

Component/platform:

Description of problem:
104/5000
Netatmo thermostat not showing.
Works properly with your application.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
netatmo:
   api_key: 5xxxxxxxxxxxxxxxxxxxxxxxxxxa
   secret_key: uxxxxxxxxxxxxxxxxxxxxxxxxxx8
   username<EMAIL_ADDRESS>   password: fxxxxxxxxP

climate:
   platform: netatmo

Traceback (if applicable):

Additional information:
From Log File:
2019-04-13 16:09:02 WARNING (MainThread) [homeassistant.components.http] Configuring api_password via the http component has been deprecated. Use the legacy api password auth provider instead. For instructions, see https://www.home-assistant.io/docs/authentication/providers/#legacy-api-password
2019-04-13 16:09:02 WARNING (MainThread) [homeassistant.components.http.auth] legacy_api_password support has been enabled.
2019-04-13 16:09:07 ERROR (MainThread) [homeassistant.components.device_tracker] Unable to load /config/known_devices.yaml: Config file not found: /config/known_devices.yaml
2019-04-13 16:09:10 ERROR (MainThread) [homeassistant.components.climate] Error while setting up platform netatmo
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=hass.loop)
  File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 96, in setup_platform
    for room_id in room_data.get_room_ids():
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 344, in get_room_ids
    if not self.setup():
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 355, in setup
    self.homestatus = pyatmo.HomeStatus(self.auth, home=self.home)
  File "/usr/local/lib/python3.7/site-packages/smart_home/Thermostat.py", line 130, in __init__
    raise NoDevice("No device found, errors in response")
smart_home.NoDevice: No device found, errors in response

+1
Seeing the same issue. Often it can be resolved by rebooting my Hass.IO server completely (not just by restarting Home Assistant)

Same issue here:
2019-04-15 21:59:18 ERROR (MainThread) [homeassistant.components.climate] Error while setting up platform netatmo Traceback (most recent call last):   File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform     SLOW_SETUP_MAX_WAIT, loop=hass.loop)   File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for     return fut.result()   File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run     result = self.fn(*self.args, **self.kwargs)   File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 96, in setup_platform     for room_id in room_data.get_room_ids():   File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 344, in get_room_ids     if not self.setup():   File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 355, in setup     self.homestatus = pyatmo.HomeStatus(self.auth, home=self.home)   File "/usr/local/lib/python3.7/site-packages/smart_home/Thermostat.py", line 130, in __init__     raise NoDevice("No device found, errors in response") smart_home.NoDevice: No device found, errors in response
I have the netatmo Thermostat, the Welcome camera and the Weather Station. All works fine in previous versions (0.89), but now the thermostat don't show up and report this error :/

Might be related to #23380 and fixed with #23429.

Waiting for the next hassio release :)

Is this still an issue?

I haven't seen any issues for the last 2 versions (.92 and .92.1)

@fviscon How about you?

Same issue with the last hassio version (.92.1) :(

i still have the same problem, also with 92.1.
I try to use a fresh new netatmo api/secret, but the problem is still here :/

2019-05-01 06:11:00 ERROR (MainThread) [homeassistant.components.climate] Error while setting up platform netatmo
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
SLOW_SETUP_MAX_WAIT, loop=hass.loop)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
return fut.result()
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 97, in setup_platform
for room_id in room_data.get_room_ids():
File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 345, in get_room_ids
if not self.setup():
File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 356, in setup
self.homestatus = pyatmo.HomeStatus(self.auth, home=self.home)
File "/usr/local/lib/python3.7/site-packages/smart_home/Thermostat.py", line 130, in init
raise NoDevice("No device found, errors in response")
smart_home.NoDevice: No device found, errors in response

Home Assistant 92.1 on Synology Docker, same issue.

I take my comment back - today I have the issue again, on HA .92.1

@MTrab If you're currently experiencing this can you please check your app page in the dev section over at Netatmo if your app is banned? If so, unban it and try again after after a while. I noticed this error (No device found, errors in response) yesterday evening I unbaned it and when I tried to investigate this morning it worked fine.

If I restart my HA, when experiencing this issue, then all is back to normal again - so I'd recon that it have nothing to do with the app in netatmo dev.

It was with a shot. This is really difficult to debug as I cannot reproduce it.

2019-05-19 15:31:44 ERROR (MainThread) [homeassistant.components.climate] Error while setting up platform netatmo
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=hass.loop)
  File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 97, in setup_platform
    for room_id in room_data.get_room_ids():
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 345, in get_room_ids
    if not self.setup():
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 358, in setup
    self.update()
  File "/usr/local/lib/python3.7/site-packages/homeassistant/util/__init__.py", line 224, in wrapper
    result = method(*args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/netatmo/climate.py", line 382, in update
    homestatus_room['therm_setpoint_temperature']
KeyError: 'therm_setpoint_temperature'

This is what I get in the log. After upgrade to 0.93.1 it will not connect, no matter how many times I reboot/restart HA :(

Screenshot from the app:

Just realised that this is not the same error as the initial issue.
Creating a new issue report with this issue.

@fviscon is this still an issue in 0.95.4?

@fviscon is this still an issue in 0.95.4?

Yes:
Tue Jul 09 2019 08:57:58 GMT+0200 (hora de verano de Europa central) Error while setting up platform netatmo Traceback (most recent call last):   File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 126, in _async_setup_platform     SLOW_SETUP_MAX_WAIT)   File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for     return fut.result()   File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run     result = self.fn(*self.args, **self.kwargs)   File "/usr/src/homeassistant/homeassistant/components/netatmo/climate.py", line 98, in setup_platform     for room_id in room_data.get_room_ids():   File "/usr/src/homeassistant/homeassistant/components/netatmo/climate.py", line 346, in get_room_ids     if not self.setup():   File "/usr/src/homeassistant/homeassistant/components/netatmo/climate.py", line 357, in setup     self.homestatus = pyatmo.HomeStatus(self.auth, home=self.home)   File "/usr/local/lib/python3.7/site-packages/smart_home/Thermostat.py", line 156, in __init__     raise NoDevice("No device found, errors in response") smart_home.NoDevice: No device found, errors in response

@JesCR could you please provide your Netatmo related config?

@JesCR could you please provide your Netatmo related config?

Sure!, here it's:
netatmo:
  api_key: !secret netatmo_apikey
  secret_key: !secret netatmo_secretkey
  username: !secret netatmo_username
  password: !secret netatmo_password
  webhooks: true
  discovery: true

I also try with
discovery: false
and
_climate:

platform: netatmo

And i use a new netatmo app and check that the App State is ACTIVATE.
But always get the same error

@JesCR Could you run this script and check what it returns for python gen_test_data.py --USERNAME <your_username> --PASSWORD <your_password> --CLIENT_ID <your_client_id> --CLIENT_SECRET <your_client_secret> --modules Thermostat?

python gen_test_data.py --USERNAME <your_username> --PASSWORD <your_password> --CLIENT_ID <your_client_id> --CLIENT_SECRET <your_client_secret> --modules Thermostat

Done!
result:
Traceback (most recent call last):   File "gen_test_data.py", line 3, in <module>     import pyatmo ImportError: No module named pyatmo
BTW i'm running hassio in a nuc (but i had the problem in a pi too)

after
➜  /workspace pip install pyatmo   Collecting pyatmo   Downloading https://files.pythonhosted.org/packages/e8/e1/41bcecaabb49f774986af755c884a3473f7ecb60ef76782bb18213542e02/pyatmo-2.1.1.tar.gz Installing collected packages: pyatmo   Running setup.py install for pyatmo ... done Successfully installed pyatmo-2.1.1
still get:
Traceback (most recent call last):   File "gen_test_data.py", line 3, in <module>     import pyatmo   File "/usr/lib/python2.7/site-packages/pyatmo.py", line 14, in <module>     from smart_home import _BASE_URL, NoDevice, postRequest   File "/usr/lib/python2.7/site-packages/smart_home/__init__.py", line 4, in <module>     import requests

Oops, you've been installing with python 2.7. You probably need pip3 install pyatmo. Feel free to ping me on Discord (might be quicker).

@cgtobi sorry but i don't use Discord :/
So i need to install python 3.7.4 first. After that pip3 and then pyatmo?
In my ubuntu host?
So my hassio docker can use the pyatmo and netatmo thermostat will work?

I don't want you to fiddle with your live environment too much. But you should be able to run this anywhere where you have python 3.6+, which includes your HA docker container. But I have hardly any docker experience so I can't help you much with this.

I will try when i get home and will ping back with the results!

@cgtobi i was able to run the script (after install python3, pip3 and request)
A lot of info printed, the last lines:
INFO:smart_home:Response: INFO:smart_home:{"status": "ok", "time_server":<PHONE_NUMBER>} ERROR:__main__:warning, no thermostat available for testing

@JesCR are you on the HA forum, so we can discuss this via PM?

@cgtobi , you have a PM in the HA forum ;)


Big Integers are being round

Big integers are being round up in js
here is my code
let bigint=<PHONE_NUMBER>0324999
console.log(bigint);
output is<PHONE_NUMBER>0325000
https://jsfiddle.net/uk26sywg/

Thanks, but this is an issue with Javascript itself, not Express.


Discussion: Async assertions

I want to make it easier to write and use assertions that need to do async work before they can figure out whether to fail. Examples include:
unexpected-express
The to yield exchange assertion runs the supplied middleware, which can be async, so the assertion itself needs to take a callback, so it ends up looking like this:
it('should DTRT', function (done) {
    expect(myMiddleware, 'to yield exchange', {request: 'GET /', response: 200}, done);
});

image metadata/resemblance analysis
I have some not-yet-open sourced custom assertions that use exif-parser, resemble.js and other image libraries to implement things like these on buffers, filenames -- or even http resources:
expect('foo.png', 'to be an image resembling', 'bar.png', {
    isSameDimensions: true,
    mismatchPercentage: expect.it('to be less than', 1)
}, done);

expect(myBuffer, 'to be an image whose exif data satisfies', {
    tags: {LensModel: /^iPhone 6/ }}
}, done);

For some reason many of the underlying libraries only support working asynchronously, even when consuming buffers.
streaming
Almost all assertions that work on streams need to wait for the stream to end, and thus need to be async. I'd like to write a plugin that provides a set of composable middle-of-the-rocket assertions, which will each need to be async:
expect(myStream, 'to be a readable stream whose output satisfies', 'when gunzipped', /foo bar/, done);

As far as I can tell, the above will be almost impossible to achieve as things are now, even with the done callback. It'll require each assertion to make assumptions about whether the next assertion in the argument list will need to take a callback.
Adding it all together
When combining multiple of the above I've ended up needing to provide multiple callbacks to the different assertions, so I've had to introduce a makeMakeCallback construct that issues one or more callbacks within a single tick, then calls done when all of them have completed:
it('should auto-orient an image with an EXIF orient if told to', function (done) {
    var makeCallback = makeMakeCallback(done);
    expect('GET /exifOriented.jpg?rotate', 'to yield a response of', {
        headers: {
            'Content-Type': 'image/jpeg'
        },
        statusCode: 200,
        body: expect.it('to be an image whose metadata satisfies', {
            contentType: 'image/jpeg',
            width: 2448,
            height: 3264
        }).and('to be an image whose exif data satisfies', {
            tags: {Orientation: undefined}
        }, makeCallback()).and('to be an image resembling', 'foo.jpg', makeCallback())
    }, makeCallback());
});

In short, I would like to write the above without the having to worry so much about the callbacks. That will require some extra complexity in unexpected itself.
One idea, which @sunesimonsen and I explored a bit, is to make the switch into async mode explicit by letting expect know that you want it to call done after all the assertions have completed. IIRC:
it('should DTRT', function (done) {
    expect.async(done);
    expect(myStream, 'to be a readable stream whose output satisfies', 'when base64 decoded', 'to be an image resembling', 'foo.jpg');
    // The following line will run regardless of the outcome of the previous assertion,
    // which is counter-intuitive when the callback is not directly visible:
    expect(myStream.readable, 'to be true');
});

I stumbled upon domenic's "mocha as promised" fork, which actually landed in the official mocha as of 1.18.0. If the async assertions could somehow be orchestrated using promises, we might even be able to get rid of the done function altogether by returning the result of expect from the it function:
it('should DTRT', function () {
    return expect(myStream, 'to be a readable stream whose output satisfies', 'when base64 decoded', 'to be an image resembling', 'foo.jpg');
});

The return would also solve the problem with the following line being executed. But I don't know enough about promises to really understand whether that's realistic. I guess it would require expect to always return something that's promise compatible.

Another way to avoid looking at done could be to issue an it-compatible function:
it('should DTRT', expect.async(function (expect) {
    expect(myStream, 'to be a readable stream whose output satisfies', 'when base64 decoded', 'to be an image resembling', 'foo.jpg');
});

That is a very interesting idea - it looks nice.

var Promise = require('bluebird');

describe('foo', function () {
    it('should bar', expect.async(function () {
        expect(middleware, 'to be an object');

        return expect(middleware, 'to yield exchange', {
            ...
        })
    }));
});

expect.async = function (cb) {
    var that = this;
    if (cb.length !== 0) {
        throw 'idiot';
    }
    if (that._isAsync) {
        throw 'idiot2';
    }
    that._isAsync = true;
    return function (done) {
        if (typeof done !== 'function') {
            throw 'idiot3';
        }
        var result = cb();
        that._isAsync = false;
        if (!result || typeof result.then !== 'function') {
            throw 'idiot4';
        }
        result.then(function () {
            done();
        }).catch(done);
    };
};

Another thing we have to keep in mind is the ability of an "adverbial" assertion to clean up and make additional assertions after the actual test. For example, with http mocked out needs to unhijack the http module and assert that all the mocked out HTTP exchanges were actually exercised.
This is really awkward with the current async assertions (has to assume that the last argument is a callback), but would work really well with promises, as far as I can tell.

Yes that would probably be really easy to orchestrate with promises.

In case anyone else is watching, we're currently exploring this here: https://github.com/unexpectedjs/unexpected/tree/feature/it-looks-even-more-promising
As the branch name indicates, it's looking good :)

I think we have settled on a solution and it will ship as part of v7. Everything is almost ready on the v7 branch, so I'll just close this issue as I don't think there is need for anymore discussion on the subject for now.


[dev-ops] - Create first working CI/CD pipeline

Intro
We need a robust CI/CD pipeline. This is the start to building such devOps workflows.
Note: The Argo Suite of applications mentioned below in the Tasks are already running and are behind SSO auth with m8a Teams (Keycloak).

Argo Workflow = https://workflows.m8a.io (the version error goes away after login)
Argo CD = https://deploy.m8a.io
Kargo - https://kargo.m8a.io

Tasks:
Continuous Integration

[ ] - Create a workspace entry point, which creates a branch of the dev( soon to be staging) branch, so that when a workspace is started, a new branch is always being worked on. No branch, no workspace.
Note: when the core app is (at some point) controlling the workspace service, it will also control the creation and deletion of the workspaces.
[ ] TO BE CARRIED OVER TO THAT PROCESS: Make sure at the time of destruction of the workspace, that any uncommitted changes are confirmed can be deleted. This is to avoid inadvertent loss of work in the workspace.
[x] - Create a webhook event source in Argo Events to catch changes to the repository.

[x] - Create a prototype webhook and test it
[ ] - Set up the connectivity for the webhook to the outside world (i.e. https://webhooks.m8a.dev)
[ ] - Figure out authorization scheme (only data sent from a trusted source can be accepted)
[ ] - Make sure the hook is called for PR creations and commits to branches with PRs.

[ ] - Create a workflow in Argo Workflows to run the necessary checks (tests, linting, etc.) before a package can be promoted between environments i.e. before the PR is merged.

[ ] - fire on PR creation
[ ] - fire on additional commits to the PR

[ ] - On approval (PR approval) of a new version, create artifacts

[ ] - Container(s) can be built
[ ] - Container(s) can be stored in registry

Continuous Deployment

[x] - Create a pipeline in Kargo to install container(s) of an app via ArgoCD.

[x] - Repository is updated with the new version(s) of the container image(s)
[x] - Create an application watcher (Argo CD) to pole the repository for version changes to roll-out the new version

Scott

Added some points and notes above.
Scott


clearMediaBlob function

when i use the use-media-recorder i will need to clear my recorded media, and i don't see anything for it !!
i added this function and update the tests, interface and readme file
check it, if need more thing ... add to it
and add this feature for this library

Looks good @Amir-Alipour 🤝
Apologies for the delay
Is it cool if we adjust the description in the readme file to "Resets the media blob to null"?

Looks good @Amir-Alipour 🤝 Apologies for the delay Is it cool if we adjust the description in the readme file to "Resets the media blob to null"?

hi, thanks ❤
yes it can be better, because it shorten


Bring ServiceX Frontend inline with ServiceX 1.0 RC2

RC2 of ServiceX released a bunch of features. This PR adds features to make them accessible to the user:

#79 - Fetches the /transformation endpoint data
#80 - Uses minio auth information from the /transformation endpoint data
#82 - When a file fails to transform, dump transform logs of failed pods to the logger.warning.
#30 - If the DID look up fails (or simlar error), report error message to use from /transform status
ServiceX_App/34 - The ServiceX app now uses email/password to authenticate.

Goal would be to merge this along with other changes into master as version 1.1 once approved.

Sorry - this is a big PR - has a bunch of new features and code changes in it!

Would prefer multiple PRs, but here goes...

Comment on versioning - does this need to be version 1.1? Can we align the version numbers between the backend and the frontend?

Looks good apart from the hardcoded docker image tag in servicex.py

If ypu know how that should be handled, i would be up for that!

Comment on versioning - does this need to be version 1.1? Can we align the version numbers between the backend and the frontend?

Ideally. We will try to get there.

Would prefer multiple PRs, but here goes...

Yeah
I am up for that in the future, but that means more for you to review!

Would prefer multiple PRs, but here goes...

Yeah
I am up for that in the future, but that means more for you to review!

This shouldn't be a problem with our new branching strategy. Each PR should be merged directly into develop, and reviewed by anyone necessary at that time. I don't think we'll need any more aggregate PRs like this.

This shouldn't be a problem with our new branching strategy. Each PR should be merged
directly into master (or whatever we call the trunk branch), and reviewed by anyone
necessary at that time. I don't think we'll need any more aggregate PRs like this.

This won't change the fundamental - the issue is that if there are too many PR's then it takes too much of other people's time.

This will get fixed as soon as there is a working tag of that name! So not in time for this PR, but shortly after that, I hope!

The new version was released, so this has been updated to the v1.0.0-rc.2 tag.


Obsidian setting using  HTML tags instead of # markdown syntax

In order for the app to work more seamlessly with Obsidian, it should copy headers using markdown syntax #, instead of
 tags when using the Obsidian setting.
Steps to reproduce

Open the extension and select the Obsidian preset
Enter a website and copy a couple of headers

Expected result
# Header 1
## Header 2
### Header 3

Actual result

Header 1

Header 2

Header 3

While Obsidian recognizes HTML tags, this is not ideal, since Obsidian is markdown-oriented and it it will only render HTML headers in preview mode, and not in edit mode.

The best way to indicate something is a header is using #. That way, it will render as a header in edit mode too.

@ayrtonoropeza good idea and point of feedback. I have it on my list to do but I haven't been able to spend much time developing in the last couple months due to work being busy.

@ayrtonoropeza sorry just getting around to development again on my highlighter. I saw your post in obsidian forums as I never got notified via email about new posts for some reason and now am going back through them all. I will keep you posted!
https://forum.obsidian.md/t/web-clipper-highlighter-and-kindle-highlights-notes-extraction-extension/852/44?u=smurfman111

I just wanted to make a suggestion: in order for this to work more seamlessly with Obsidian, the extension’s clipboard should convert html header tags into markdown syntax when using the Obsidian preset. Right now, it is copying headers as
Header
, but Obsidian works better when you use the markdown syntax, which is # Header 1. That way, the title will render in both edit and preview mode. I left a feature request in GitHub with screenshots and more details.

I’ve never used Roam, but I’m guessing there’s a reason to use the html syntax there. I just hope you can include this html-to-markdown conversion for Obsidian without messing with the default Roam mode. Thanks a lot in advance!


Update Remote Manager Sample

The remote manager sample is actually supposed to upload datapoints using the method upload_datapoint in the while loop. Instead, while loop is creating datastreams. A small fix.

@sai-ydev, thank you so much for the fix. Please reword a little bit the title of the commit message before merging it, something similar to:
samples: fix the datapoints upload in the DRM HTTP Requests sample
Thanks.

@rubenmoral Thanks for the review. I updated the title of the commit per your request.


docs: update FUNDING.yml

You probably want to merge this and set up GitHub Sponsors :)

Oh yes, I still haven't dwelled on all the boilerplate config that comes with electron-react-boilerplate, thanks for the heads up!


Admin - view client details

As the admin I should be able to view client details

Acceptance Criteria:

through the database a list of client details will be generated to which admin will be able to access.


added missed constraint changes in thermostat cluster

update to missed changes in https://github.com/project-chip/connectedhomeip/pull/34474
follow-up to https://github.com/project-chip/connectedhomeip/pull/34511

Closing this in favor of https://github.com/project-chip/connectedhomeip/pull/36023


Added build and coverage status images to README

Changes Unknown when pulling 13517245fe7175f56dd002ba8330f7acda2229c8 on feature/status-images into ** on master**.


Cross Review

Topic or purpose in relation to helping Teacher.
Visual designs of what your topic will look like.  Using design or drawing tool.
Description of data that you will capture.  Using table or UML tool.
Coding work you have done on spring_2025.  Live designs using markdown on frontend.
Evidence of research.
Here are grading guidelines in  individual group and cross over.  For perspective, this should look like a minimum of 8 hours of work.
.55 no work
.60 simple, topic and outline #1 only
.75 some descriptions and designs #1-#3
.85 meeting the majority of #1 through #5
.90 something that should be shared with other classes

Topic or purpose in relation to helping Teacher.
Bathroom pass for all teachers would be very useful. making the bathroom process much more sanitary.
Visual designs of what your topic will look like. Using design or drawing tool.
Made a basic backend ready for use with columns for login, issues, and queuing.
Description of data that you will capture. Using table or UML tool.
Sqlite databases are gonna be used. a few basics are made.
Coding work you have done on spring_2025. Live designs using markdown on frontend.
Aashray has done login and error handling for that as well. Actively works.
Evidence of research.
Made a flowchart and had thorough conversations with chat gpt.


OS icons cached in local storage are not updated if the icon changes on the server

Even after the "Other OS" icon was updated on the ovirt-engine (see https://gerrit.ovirt.org/#/c/93007/), web-ui keeps using its cached copy of the image.  The icons need to be purged from the browser "Local Storage" to force the new icon to be reloaded.
web-ui makes an assumption that the data-url of any given icon id will not change.  Once it is loaded in Local Storage it stays there.
There are 2 things that can be done:

On the ovirt-engine, when an icon is updated, change it's id
On the web-ui, add cache invalidation to the icons stored in browser local storage

Related to but different from #606

Since no user complained and the issue is opened for more than 2 years then closing it.
Please re-open if you think it's still important to handle.


OS X version auto-corrupts translations

Translations get auto-corrected and modified without the user's request or consent, nor attention. Version 1.6.5.
Take for example this minimal .po file (the mandatory msgid "" header can be copied from de.po):
msgid "Please log in, ok?"
msgstr "Bitte einloggen, ok?"

msgid "About..."
msgstr "Über..."

Just opening this in Poedit modifies the first message. The word einloggen gets replaced with einlochen -- a completely different word. When moving to the second message using the arrow keys, the three dots get replaced by the Unicode ellipsis.
If autocorrect is disabled in settings, the first message doesn't get modified, but the ellipsis still does.
With this minimal sample the behavior is quite deterministic and reproducable, but in a big real-life PO file modifications appear to happen at random.
IMHO this is pretty bad, as random words in translations may get replaced with some unrelated words, and the only indication of this happening is the little star icon appearing on the row.

I'm having the issue with version 3.5.1 on OSX 15.0.1 (Apple MacBook Pro M3)


Skip duplicate vertices in ETL

Hi,
I would like to propose an extension to the vertex component in ETL. Currently if you try to create a vertex that would violate the unique constraint of a corresponding index, you get an exception that stops the complete ETL processing. My proposal is that there should be a configuration parameter for this transformation that gives the option not to stop the whole ETL process but rather skip the current record. I made an exemplary implementation as change to the OVertexTransformer class. Here are the changes:
public ODocument getConfiguration() {
    return new ODocument().fromJSON("{parameters:[" + getCommonConfigurationParameters() + ","
            + "{class:{optional:true,description:'Vertex class name to assign. Default is V'}}]"
            + ",input:['OrientVertex','ODocument'],output:'OrientVertex'"
            + ",skipDuplicates:{optional:true,description:'Vertices with duplicate keys are skipped', default:false}}");

public Object executeTransform(final Object input) {
...
if (vertexClass != null && !vertexClass.equals(v.getRecord().getClassName())) {
  try {
    v.setProperty("@class", vertexClass);
  } catch (ORecordDuplicatedException e) {
    if (skipDuplicates) {
      return null;
    } else {
      throw e;
    }
  }
}

Hey @gfinger, I like your implementation. Could you send us a Pull Request for ETL project? In this way you figure as contributor and author of this fix. WDYT?

Hi Luca, it looks like there is no develop branch existing in the orientdb-etl repository.

Thanks for this contribution. I'm going to update the docs :-)


Indexing 0-D dask array handling raises exceptions

What happened:
The following code raises an exception:
>>> import numpy
>>> import dask.array
>>> dask.array.from_array(numpy.zeros((3, 0)))[[0]]
---------------------------------------------------------------------------
OverflowError                             Traceback (most recent call last)
    ...
OverflowError: cannot convert float infinity to integer

What you expected to happen:
I would expect this to match numpy behavior:
>>> import numpy
>>> numpy.zeros((3, 0))[[0]]
array([], shape=(1, 0), dtype=float64)

Minimal Complete Verifiable Example:
>>> import numpy
>>> import dask.array
>>> dask.array.from_array(numpy.zeros((3, 0)))[[0]]
---------------------------------------------------------------------------
OverflowError                             Traceback (most recent call last)
    ...
OverflowError: cannot convert float infinity to integer

Anything else we need to know?: nope
Environment: linux

Dask version: 2022.01.0
Python version: 3.9
Operating System: linux
Install method (conda, pip, source): pip

Thanks for including the minimal reproducer! It looks like the raise is coming from a divide by zero in the array slicing logic, I'll dig a bit more.
Full traceback for reference
In [19]: x = da.from_array(np.zeros((3, 0)))

In [20]: x[[0]]
/Users/ddavis/.pyenv/versions/3.10.2/envs/dask-awkward/lib/python3.10/site-packages/dask/array/slicing.py:647: RuntimeWarning: divide by zero encountered in long_scalars
  maxsize = math.ceil(nbytes / (other_numel * itemsize))
---------------------------------------------------------------------------
OverflowError                             Traceback (most recent call last)
Input In [20], in <module>
----> 1 x[[0]]

File ~/.pyenv/versions/3.10.2/envs/dask-awkward/lib/python3.10/site-packages/dask/array/core.py:1847, in Array.__getitem__(self, index)
   1844     return self
   1846 out = "getitem-" + tokenize(self, index2)
-> 1847 dsk, chunks = slice_array(out, self.name, self.chunks, index2, self.itemsize)
   1849 graph = HighLevelGraph.from_collections(out, dsk, dependencies=[self])
   1851 meta = meta_from_array(self._meta, ndim=len(chunks))

File ~/.pyenv/versions/3.10.2/envs/dask-awkward/lib/python3.10/site-packages/dask/array/slicing.py:174, in slice_array(out_name, in_name, blockdims, index, itemsize)
    171 index += (slice(None, None, None),) * missing
    173 # Pass down to next function
--> 174 dsk_out, bd_out = slice_with_newaxes(out_name, in_name, blockdims, index, itemsize)
    176 bd_out = tuple(map(tuple, bd_out))
    177 return dsk_out, bd_out

File ~/.pyenv/versions/3.10.2/envs/dask-awkward/lib/python3.10/site-packages/dask/array/slicing.py:196, in slice_with_newaxes(out_name, in_name, blockdims, index, itemsize)
    193         where_none[i] -= n
    195 # Pass down and do work
--> 196 dsk, blockdims2 = slice_wrap_lists(out_name, in_name, blockdims, index2, itemsize)
    198 if where_none:
    199     expand = expander(where_none)

File ~/.pyenv/versions/3.10.2/envs/dask-awkward/lib/python3.10/site-packages/dask/array/slicing.py:262, in slice_wrap_lists(out_name, in_name, blockdims, index, itemsize)
    260 if all(is_arraylike(i) or i == slice(None, None, None) for i in index):
    261     axis = where_list[0]
--> 262     blockdims2, dsk3 = take(
    263         out_name, in_name, blockdims, index[where_list[0]], itemsize, axis=axis
    264     )
    265 # Mixed case. Both slices/integers and lists. slice/integer then take
    266 else:
    267     # Do first pass without lists
    268     tmp = "slice-" + tokenize((out_name, in_name, blockdims, index))

File ~/.pyenv/versions/3.10.2/envs/dask-awkward/lib/python3.10/site-packages/dask/array/slicing.py:647, in take(outname, inname, chunks, index, itemsize, axis)
    645     warnsize = maxsize = math.inf
    646 else:
--> 647     maxsize = math.ceil(nbytes / (other_numel * itemsize))
    648     warnsize = maxsize * 5
    650 split = config.get("array.slicing.split-large-chunks", None)

OverflowError: cannot convert float infinity to integer

@douglasdavis if this is a regression, just wanted to make sure you are aware that there were recent changes in https://github.com/dask/dask/pull/8538

Doesn't appear to be a regression: it has existed since at least 2021.11.2


Extension won't install in OpenLens

Describe the bug
Installed OpenLens from https://github.com/MuhammedKalkan/OpenLens
But it cannot install extensions
To Reproduce
Steps to reproduce the behavior:

Go to extensions view
Paste this @alebcay/openlens-node-pod-menu
Click install
Installs forever

Expected behavior
Should finish install and add features from plugin
Screenshots

Environment (please complete the following information):

Lens Version: v6.5.2-366 Latest
OS: Windows 11
Installation method (e.g. snap or AppImage in Linux): MSI and EXE package from https://github.com/MuhammedKalkan/OpenLens/releases

Thanks for reaching out. However, it appears that the issue you're experiencing is related to OpenLens, which is a separate project and not maintained by our team. Our repository is dedicated to Lens Desktop product.
For issues specific to Lens, we encourage you to check out our latest release here. If your issue persists with the official version of Lens, please let us know, and we'll be more than happy to assist.


instance check: region for image and cloud service must be the same

The location of the image must be the same region as the cloud service

working on this Issue

done


Crash on Result.setValue()

Hi, after upgrading realm to the latest version v0.97.0 my code crash:
let remove = db.objects(VODBrand.self)
    .filter("topBrand = %@", RealmOptional<Bool>(true))
if remove.count > 0 {
    remove.setValue(RealmOptional<Bool>(false), forKeyPath: "topBrand")
}

remove.count have a value of 1, but RLMCollectionSetValueForKey() methods is looping 3 objects:

Here the crash:
Terminating app due to uncaught exception 'RLMException', reason: 'Index 2 is out of bounds (must be less than 1)'

What's up?

RLMCollectionSetValueForKey is mutating objects so that they no longer match the predicate. This causes the length of the collection to change on each iteration, which makes it unsafe to iterate the collection by index as RLMCollectionSetValueForKey is doing.
To work around this you can write the mutation explicitly as:
for brand in remove {
    brand.topBrand.value = false
}

Please also verify that your topBrand property is declared using let rather than dynamic var. RealmOptional properties must be mutated by changing their value property, not by assigning to the property itself as your snippet shows you doing.


Create single fcl config for reco of all coldbox CRP top-readout data

As I discussed at today's VD analysis meeting, we would like to have a single fcl config to cover reco of all run periods for the vertical-drift top-readout CRP coldbox data. To merge the two top-level configs we have now, we need context-dependent channel status and field strength. Context means run period, run, event, etc., with run most important here. A service for the former is in place --see duneprototypes issue 20.
We need to add context-dependent field strength and the top-level fcl configuration. The field strength has to be delivered through the detector properties service interface to work with existing code.

I did a dump of the two existing top-level reco configs for VD top coldbox data:

crp2cb_data_jul2022_reco.fcl
crp3cb_data_oct2022_reco.fcl

The only differ by channel status. The field strength (DetectorProperties.Efield) is the same for both. This is consistent with what appears to be config data in those dumps:

data: {
  crp2cb_july22_Efield: [0.411, 1, 1]
  crp3cb_oct22_Efield: [0.411, 1, 1]

So there is no difference in field strength in v09_65_03.

Froam laura Zambelli:

Hi David,

As I presented in a previous meeting, here are my estimate of the Efield :
CRP2 July : 0.447
CRP3 October : 0.441
CRP2 Nov : 0.444

Laura

Tingjun explains how the E-field is set in protoDUNE:

Hi David,

For ProtoDUNE-SP we use the following DetectorProperties service:
https://github.com/DUNE/duneprototypes/blob/develop/duneprototypes/Protodune/singlephase/DetectorServices/Providers/DetectorPropertiesProtoDUNEsp.cxx

The HV value is saved in metadata so the service sets the E-field using metadata. See function UpdateHV. We also set run dependent temperatures. See function UpdateTemp.

Tingjun

However, Wenqiang reports that we do not have such metadata in the vertical-drift coldbox data:

Do we have and use this metadata for the vertical-drift top-readout coldbox data? Thanks.

da
.
.
.
Hi David,

It seems not. Here is an example:

```
[dunegpvm07] $ samweb get-metadata 1727_66_b_cb.test
      File Name: 1727_66_b_cb.test
        File Id: 75949408
    Create Date: 2022-10-19T14:27:07+00:00
           User: timm
      File Size:<PHONE_NUMBER>
       Checksum: adler32:7f8267b2
 Content Status: good
      File Type: detector
    File Format: binary
      Data Tier: raw
    Event Count: 60
     Start Time: 2022-10-12T09:58:27+00:00
    Data Stream: study
DUNE.datataking: COLDBOX_run2022_CRP3
           Runs: 1727.0066 (vd-coldbox-top)
```

Best,
Wenqiang

In dunesw/fcl/vdcoldbox/reco, I created crpcb_data_reco.fcl which uses the context-dependent channel status service ans so should produce the same results as crp2cb_data_jul2022_reco.fcl or crp3cb_data_oct2022_reco.fcl applied to appropriate runs.
Wenqiang, could you check that the new config file produces the same results as the old ones? Thank you.

We can close this as soon as Wenqiang confirms that next release (presumably the next after v09_68_00d00) with these changes is OK. We can also close dunedataprep issue 22 at that time.

Presumably thi is OK.


change private ip to list, add key_name to instances, add user_data

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Jon Baker seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


LLM installation issue

Hi,
Project is absolutely awesome. However, am running into some issues (probably between the ears) trying to install Vicuna. I downloaded the 3 .bin files from here:
https://huggingface.co/lmsys/vicuna-13b-delta-v1.1
And put them in ./chatbots
Then I tried to follow the written instructions:
./utils shell (I assume ./utils.sh shell). This puts me in the docker container.
Then I run:
cd chatbot
This puts me in ./chatbot in the docker container.
Then I run:
./utils.sh install 13B - this actually fails with the following error:
You need to run this command from the host - you are in the container
If I exit the container and try, it fails again because utils.sh is a directory higher. If I run ../utils.sh install 13B from outside the container, it installs everything as normal, and seems to just ignore Vicuna. There's no log output related to Vicuna or an LLM, and from what I can tell when I start it, there's no way to use Vicuna.
Was just hoping to get some clarification here on the installation procedure. Thanks.

Thanks!
Unfortunately when we merged the most recent WIS changes I forgot to update the LLM documentation in the README (facepalm). Now that there are plenty of models on Hugging Face that don't require obtaining the LLaMA weights separately you can load them directly.
I've updated the README for the new (much easier) process.

Thanks for the quick response!
Few follow up questions:

When starting with TheBloke/vicuna-7B-v1.3-GPTQ, I get a handful of errors:

willow-inference-server-wis-1    | The model weights are not tied. Please use the `tie_weights` method before using the `infer_auto_device` function. willow-inference-server-wis-1    | The safetensors archive passed at /root/.cache/huggingface/hub/models--TheBloke--vicuna-7B-v1.3-GPTQ/snapshots/e7466408ac3d7d3534097dcd431799c603a52be7/vicuna-7b-v1.3-GPTQ-4bit-128g.no-act.order.safetensors does not contain metadata. Make sure to save your model with the `save_pretrained` method. Defaulting to 'pt' metadata.
and also:
willow-inference-server-wis-1    | Xformers is not installed correctly. If you want to use memory_efficient_attention to accelerate training use the following command to install Xformers willow-inference-server-wis-1    | pip install xformers. willow-inference-server-wis-1    | The model 'LlamaGPTQForCausalLM' is not supported for text-generation.
Are these normal?

It's possible I misunderstood what the LLM is doing here. If I go to https://<IP_ADDRESS>:19000/api/docs#/, I see the nice UI and can submit text questions and watch those pop up in the stdout on the server. But if I say something to my Espressif, it simply submits it as a TTS request to the server, but the LLM doesn't pick it up, and nothing happens. Similarly, there's no audio playback from the Espressif box. My impression was that it would go Espressif --> STT --> Text input to LLM --> Inference --> TTS --> Espressif

but perhaps I assumed that?
Thanks again!

Presently the LLM chatbot is exposed only through API, there doesn't appear to be any hook from willow into the chatbot yet. Not sure what the future plan is, but I Imagine once 1.0 is released and the team starts looking into things like Rasa for routing to skills or apps, LLM could be one of the things requests could be routed to if it is determined they are not destined for HA (IE there could be some sort of system where if it sees there's no intent match at HA it would then fall back to passing the spoken text to the LLM if desired).


Method to remove applied filters.

Hey Team,
let test = new searchQuery();
test.applyFilter({ filter values});

is there any specific method to remove the applied filter  or empty the array later.
Thanks,

Hello. Not really.
The whole use-case of storefront-query-builder was to build query from scratch in abstract way but only once. If you need this method you could add it in your own fork. You would need to make changes inside SearchQuery.ts file. Just add method with logic opposite to applyFilter.

Thanks


Crashes after upgrade from 1.08 to 1.11

https://ghostbin.co/paste/sps3c

Same issue for me unfortunately. I'm sorry I know how much you've worked on this lol
https://ghostbin.com/paste/IoEWc

Hey! Thanks for proving the logs.
I switched the code from MRYIPC over to rocketbootstrap and it seems to have resolved the crashing. Would you be willing to try it out? If so, please shoot me an email (mail icon on my repo https://usrlightmann.github.io). Thanks in advance!

Crashing fixed in v1.1.1. Thanks again for your help testing!

Works like a charm! Kudos, and thank you for all your hard work. Cheers
On Friday, February 12, 2021, 01:18:47 PM EST, Lightmann<EMAIL_ADDRESS>wrote:
Crashing fixed in v1.1.1. Thanks again for your help testing!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


embed_sequence and embedding_lookup behave differently on CPU vs. GPU

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 1.6
Python version: 3.6.3
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:
Exact command to reproduce:

Describe the problem
When using tf.nn.embedding_lookup or tf.contrib.layers.embed_sequence with -1 in the indexes the corresponding embeddings should be 0 vectors, in the same way that tf.feature_column.categorical_column_with_identity ignores negative values. This works correctly when trying on Colaboratory but fails on my Windows installation using the same Tensorflow version v1.6.
Source code / logs
Both ways of initializing the embeddings produce the same error, only on Windows, may it be related to the version of the gather function being used from python\ops\array_ops.py?
tf.reset_default_graph()
a = tf.constant(np.array([[0, 1, 2, -1, 4]]))
# b = tf.contrib.layers.embed_sequence(a, 5, 3, initializer=tf.random_uniform_initializer(-1.0, 1.0))
b = tf.nn.embedding_lookup(tf.get_variable('embeddings', [5, 3], initializer=tf.random_uniform_initializer(-1.0, 1.0)), a)
with tf.Session() as sess:
    sess.run(tf.global_variables_initializer())
    print(sess.run(b))

The error goes like this

InvalidArgumentError: indices[..] = -1 is not in [0, ..)

@ilblackdragon can you please take a look?

Actually, I have some more insight to add, since by trying something else I have discovered that the issue is not with the OS, but it has to do with whether you are using a GPU or not. Running the same code on Linux (for instance in Colaboratory) will throw the same error about -1 values if you disable GPU support.
Hope this further helps to nail down the issue.

embedding_lookup doesn't support invalid ids. InvalidArgumentError is the right behavior.  FeatureColumns are handling them. We implemented _safe_embedding_lookup_sparse. Making those functions public make sense. I added contributions welcome to make them public.

Please remove the assignee, as this issue is inviting external contributions. Otherwise, remove the contributions welcome label. Thank you.

the difference seems related to tf.gather. @alextp do you know who can give us some background info here?

Is this related to GPU gather setting out-of-range indices to zero ( https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/kernels/gather_functor_gpu.cu.h#L58 ) ?

Please remove the assignee, as this issue is inviting external contributions. Otherwise, remove the contributions welcome label. Thank you.

Hi @eisenjulian !
It seems you are using older versions(1.x versions) of Tensorflow which is not supported any more. Could you confirm whether issue is replicating after migrating to 2.8 or not ? Thanks!

Hello,
I'm excited about contributing to this issue and believe it aligns well with my skills and interests. Could you please assign me to work on this? I'm ready to dive in, discuss the details, and start contributing.
Thank you!
Harshavardhan Bellamkonda

Hi, thanks for offering to help out.
This is an ancient issue. It you want to help with it the first step would be to check the current behavior. But given @mohantym 's comment above this is likely still the case.
It looks like the safe function never made it to TF2.
It also looks like the underlying gather OP's docs now mention the difference between CPU and GPU behavior, in a red warning box:
https://www.tensorflow.org/api_docs/python/tf/gather_nd
Since it's too late in the game to change the behavior of these functions, if you want to help out you could copy that the nodice to the embedding_lookup docs to close this as fixed.

Hi there! I'm trying to locate the documentation file for the tf.nn.embedding_lookup function. Can anyone point me in the right direction? Thanks!

Hi @eisenjulian ,

Could you go through this documentation once. It is clearly showing in red box like this "  On CPU, if an out of bound index is found, an error is returned. On GPU, if an out of bound index is found, a 0 is stored in the corresponding output value". If it is not resolved for you please let us know.

Thank you!


README.md on the main page lists v1.0.0 as the latest release

I think I'd just remove it from the README.md, but if you want to keep it, it probably ought to be updated.

I think github tags are already listed, following section just adds a maintenance overhead and other projects in github.com/containers also don't list their latest version in README.md so I think we should just remove it. https://github.com/containers/netavark/pull/442


Failure:  Transport has closed

I'm running the minidsp-rs server and I received the following error after starting the service.  Is this something I need to address, if so how?
Feb 02 05:22:20 raspberrypi systemd[1]: Started minidsp. Feb 02 06:00:04 raspberrypi minidsp[978]: [2021-02-02T11:00:04Z ERROR minidsp::server] stream rx: Err(Lagged(1)) Feb 02 06:00:04 raspberrypi minidsp[978]: Error: Transport has closed Feb 02 06:00:04 raspberrypi systemd[1]: minidsp.service: Main process exited, code=exited, status=1/FAILURE Feb 02 06:00:04 raspberrypi systemd[1]: minidsp.service: Failed with result 'exit-code'.

Does the service restart afterwards? You definitely seem to have hit a bug but it looks like something that wouldn't happen every time (and the service is configured to auto-restart)

It did a couple of times last night and this morning but seems to be ok today.

This is largely fixed in the current 0.1.0 pre-releases.


Window props Blob and URL do not exist in v3.6 beta/dev

TypeScript Version:  3.6.0-dev.20190807

Search Terms: window url, window blob, window property, window properties
Code
// A *self-contained* demonstration of the problem follows...
// Test this by running `tsc` on the command-line, rather than through another build tool such as Gulp, Webpack, etc.
declare global {
    const win: Window;
}
if (win.Blob && win.URL) {
    console.log(':)');
}
export {};

Expected behavior:
Compiles without a problem.
Actual behavior:
Errors:

Property 'Blob' does not exist on type 'Window'.
Property 'URL' does not exist on type 'Window'.

Playground Link:
3.6 is not available in playground.
Related Issues:
Nope.

Removed by https://github.com/microsoft/TSJS-lib-generator/pull/715. The removal was intentional, but I'll revisit the decision. @saschanaz do you have an opinion on this?

Never mind, I mis-remembered the change. Blob and URL are available globally, and can be referenced on window. However, in 3.6, window: Window & typeof globalThis. You'll need to update your declaration of win for 3.6 to match it.


Do we have a timeline of when this will be implemented? Will we have enterprise control over this setting? Will it be turned on by default with an opt out?

Do we have a timeline of when this will be implemented?

I believe your questions are mostly answered in https://github.com/GoogleChrome/ip-protection/issues/8 and https://github.com/GoogleChrome/ip-protection/issues/16.


We're removing the salesforcedx aggregator plug-in soon

We plan to remove the salesforcedx plug-in from Salesforce CLI in the coming months. Don’t worry, we’re not removing any functionality! The salesforcedx plug-in doesn’t do much; it simply aggregates other ones that contain the commands for creating scratch orgs, deploying source, and so on. The CLI itself is already an aggregator plug-in. So in the spirit of simplicity, we’re removing the unnecessary salesforcedx plug-in.
To prepare for this change:

If you previously installed a tagged version of salesforcedx in your CLI, such as with the sfdx plugins:install salesforcedx@latest-rc command, remove that version with this command:
sfdx plugins:uninstall salesforcedx
If you want to install and test the release candidate, run this command instead:
sfdx update stable-rc

Remove the sfdx plugins:install salesforcedx command from your scripts.

Until we completely remove salesforcedx from Salesforce CLI, you'll still see it in your list of plug-ins, such as in the sfdx plugins --core output. We'll announce the exact date we plan to remove it, after which you'll no longer see it listed.
We're also updating the Salesforce CLI Setup Guide to no longer mention the salesforcedx plug-in.

In the new install method, how do I install a specific version?
In CI we do sdfx plugins:install<EMAIL_ADDRESS>to ensure a stable would the syntax just be sfdx update 51.1.1 ?

@yippie
npm-based installs have it easy npm install -g<EMAIL_ADDRESS>and that's what I'd recommend for CI.  Those numbers are on the weekly release notes.
We're working on a way to make it simpler to find older versions of the CLI installers/tarballs so you can install exactly what you want that way, too.

We don't use non install because we have been burned by it badly in the past. Typically it is behind, which for this use case isn't a big deal. But more importantly it did not properly pin its dependencies causing ALL versions to break in out CI, with no work around, when a dependency published a breaking version update.
Pinning the tar to a specific version of both the cli and salesforcedx plugin set would be ideal because we have also had issues where the latest cli version had issues that installing a version of salesforcedx plugin did not work around

@yippie and others...please see this week's release notes for details about using older versions.  Those files are live now, and we'll get them added to the dev guide soon.
https://github.com/forcedotcom/cli/tree/main/releasenotes#51140-may-27-2021---cli-71030


Lift http handler type discovery up a layer

This commit lifts the discovery of what type of handler a component is, for example spin-vs-wasi-vs-wasi-snapshot, up one layer from where it currently resides. Previously this determination was made on each request and now it's made when a component first loaded and pre-instantiated instead. This would shift possible errors earlier in the system, for example.
This removes a bit of per-request work and makes the creation of the handler in execute_wasi a bit more straightforward with less guessing of exports for something that was already probed.

I lost this a bit in the shuffle of things, but @lann or others mind if I ask for a re-review on this?


Icons missing

I reverted back to the original sublime theme and now the icons are missing

fixed it by adding
"theme": "Default.sublime-theme" to the Preferences file and removing the package st-primer
I had to also restart sublime text a few times


Datepicker inconsistent time between text input or dialog click

Environment

Tech
Version

@material-ui/pickers
3.2.6

material-ui
4.4.3

React
16.10.1

Browser
firefox

@date-io/dayjs
1.3.11

Steps to reproduce

Configure KeyboardDatePicker with

format 'dd/MM/yyyy'
initialFocusedDate: today - 12:00 UTC
onChange: (date: Date, value: string) => console.log('[onDateChange]', date, value)

enter '01/01/2000' on text input using keyboard
refresh page (to reset component)
select date '01/01/2000' using datepicker dialog

Expected behavior
Step 2 log:
>  [onDateChange] Date 2000-01-01T12:00:00.000Z 01/01/2000

Step 4 log:
>  [onDateChange] Date 2000-01-01T12:00:00.000Z 01/01/2000

Actual behavior
Keyboard parsed date is localized (my local timezone is GMT+3), so selected date is wrong
Step 2 log:
>  [onDateChange] Date 2000-01-01T12:00:00.000Z 01/01/2000

Step 4 log:
>  [onDateChange] Date 1999-12-31T21:00:00.000Z 01/01/2000

Suggestion
If it is too hard to fix, please provide one of the following:

a way to provide the parse method to KeyboardDatePicker
a 3rd parameter in onChange to know if date come from  text input or datepicker dialog

Live example
Note: open the console to see the logs.
https://codesandbox.io/s/material-ui-pickers-usage-demo-bopjp?fontsize=14
Related issues
https://github.com/mui-org/material-ui-pickers/issues/1310

Just added a live example.

Just had the same issue. I think parsing should not be that hard, because we need to provide format - in this case each keyboard input can manipulate date object.
E.g we compare 10/10/2019 to 10/10/2018 and we know that diff is in yyyy segment.
I will take a look at this, maybe I can figure this out

@DonkeyAfterDark me too man, if you figure it out please tell me...

I actually figure out, but I don't know if is the best solution:
`class UTCUtils extends DateFnsUtils {
date(d) {
d = moment(d);
var year = d.format('YYYY');
var month = d.format('M');
var day = d.format('D');
var hours = d.format('HH');
var minutes = d.format('mm');
    return new Date(year, month, day, hours, minutes);
}

}`
<MuiPickersUtilsProvider utils={UTCUtils}>


ruamel: moved from bitbucket to sourceforge

Motivation for this change
This is a backport of https://github.com/NixOS/nixpkgs/pull/80400.
Original text:

It looks like the ruamel python packages have moved from bitbucket to sourceforge. See for example https://bitbucket.org/ruamel/yaml.clib
This mainly affects ruamel.yaml.clib which was getting source from bitbucket, which now 404s.

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build pythonPackages.ruamel_base pythonPackages.ruamel_ordereddict pythonPackages.ruamel_yaml pythonPackages.ruamel_yaml_clib


Problem whit % format

Greetings I am trying to calculate a progress or a ratio.
I don't know why, but as much as I've tried I can't make a field formatted to % it only shows it from 1 to 0 but it doesn't make the change to % I tried to put the field as a percentage but this damages the metric that becomes 1 and multiplying by 100 does not adjust it either. Here is an example using the example index delivered by kibana kibana_sample_data_ecommerce
Kibana 7.1.1

export (12).zip

Hi,
no easy way here. You can properly render formula results in a table using numeral.js formatting option, but the graph axis deals only with the raw data (so 0.5 vs 50%). You can trick it like this agg1/agg2*100, but you cannot get the axis to show the unit.


Fatal error: Class 'Google\Auth\Cache\MemoryCacheItemPool' not found in

Hi I'm having an issue on the Fatal error: Class 'Google\Auth\Cache\MemoryCacheItemPool' not found in C:\xampp\htdocs\googleapi\src\Google\Client.php on line 1010
i'm using the latest version my code is like this
setClientId('[app client id].apps.googleusercontent.com');
$client->setClientSecret('[app client secret]');
$client->refreshToken('[your refresh token]');
*/

$client->setClientId('xxx');
$client->setClientSecret('xxx');

echo $client->getLibraryVersion()."version";

$service = new Google_Service_Books($client);

$optParams = array('filter' => 'free-ebooks');
$results = $service->volumes->listVolumes('Henry David Thoreau', $optParams);

print_r($results);

I'm not sure why is causes like this i've check that line and it seems its just a

 protected function createDefaultCache()
  {
    // use filesystem cache by default if tedivm/stash exists
    if (class_exists('Stash\Pool')) {
      $cache = new Stash\Pool(new Stash\Driver\FileSystem);
    } else {
      $cache = new MemoryCacheItemPool; // <-------------- on this line
    }

    return $cache;
  }

I updated your code snippet and removed your credentials, but you must change them immediately since you posted them publicly.

Run composer update and make sure you have the latest version. It's possible you updated just the code for this library and not the corresponding updates to the vendored libraries.


Ensure wallet calculates max amount for sends accurately

There is a report on Discord for wallet v3.3 seeing an "Insufficient funds" message which might be a bug in the way the wallet auto-calculates max amount

I've just bought BNS name and I'm sending funds from that wallet to another address and I'm getting an 'Insufficient funds' message however there are no transactions that have gone out/in the process of going out of this wallet (I've double checked the address on Stacks Explorer too in case there was a lag).

They also mention this bug: https://github.com/hirosystems/stacks-wallet-web/issues/2176

I also had a 'fee too low' message too on a few of the attempts, which was auto calculated - changed it to 'High' but no difference & unable to send the funds.

@andresgalante have you seen this issue recently?

@markmhx I have not seen this issue recently personally from my end

I'll close it, thanks Mark


Wrong variable type in ForInitStmt

TEST:
module dut ();
function automatic integer _clog2(integer value);
  integer result;
  value = value - 1;
  for (result = 0; value > 0; result = result + 1) begin
    value = value >> 1;
  end
  return result;
endfunction
endmodule

UHDM:
|vpiForInitStmt:
         \_assign_stmt<EMAIL_ADDRESS>           |vpiRhs:
           \_constant: , line:5
             |vpiConstType:9
             |vpiDecompile:0
             |vpiSize:64
           |vpiLhs:
           \_chandle_var: (work@dut._clog2.result), line:5
             |vpiName:result
<EMAIL_ADDRESS>
Surelog reports wrong variable type for ForInitStmt, result was declared as integer, but it is reported as chandle

Fixed by #1459, check the vpiActual of the chandle_var

It still doesn't work when the for loop is inside the package.
package prim_util_pkg;
   function automatic integer _clog2(integer value);
      integer result;

      for (result = 0; value > 1; result++) begin
	 value = value >> 1;
      end
      return result;
   endfunction
endpackage

module top(output integer o);
   assign o = prim_util_pkg::_clog2(15);
endmodule // top

Fixed by #1501


Add ability to pass offset and URL

I'm not 100% sure this is possible, but it is in theory. We should be able to pass an offset and URL to a binary that allows somebody to just program that binary onto their board. This can make it much easier than it already is.

@lorennorman this was done in #8 I believe, correct?

@makermelissa I'm not sure the exact idea of this Issue, but I think the answer is yes, I did toss all the local files and now have the tool fetch the bins from our server, which mirrors files from GitHub Release Assets with CORS headers applied.

Sounds good to me.


Upgrade Fedora e2e tests with OAI to run on 41

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test

/kind feature

/kind flake

What this PR does / why we need it:
Upgrade Fedora e2e tests with OAI to run on 41
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

@efiacor There is Fedora 41
NAME: fedora-coreos-41-20241109-3-0-gcp-aarch64
PROJECT: fedora-coreos-cloud
FAMILY: fedora-coreos-stable-arm64
NAME: fedora-coreos-41-20241109-3-0-gcp-x86-64
PROJECT: fedora-coreos-cloud
FAMILY: fedora-coreos-stable
NAME: fedora-coreos-41-20241122-1-0-gcp-aarch64
PROJECT: fedora-coreos-cloud
FAMILY: fedora-coreos-next-arm64
NAME: fedora-coreos-41-20241122-1-0-gcp-x86-64
PROJECT: fedora-coreos-cloud
FAMILY: fedora-coreos-next
NAME: fedora-coreos-41-20241122-2-0-gcp-aarch64
PROJECT: fedora-coreos-cloud
FAMILY: fedora-coreos-testing-arm64
NAME: fedora-coreos-41-20241122-2-0-gcp-x86-64
PROJECT: fedora-coreos-cloud
FAMILY: fedora-coreos-testing

Fedora CoreOS fails with below error:
 Failed to import public key "file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-41-x86_64" to rpmdb: can't create transaction lock on /usr/share/rpm/.rpm.lock (Read-only file system)

I'll run the rest of it manually on GCP to avoid mess here.


new MODE LEVELS:open_ended

Reported by Ansley B Manke on 23 Apr 2007 16:01 UTC
When setting levels, the (-inf) (inf) makes life easier, but a further
improvement would be a MODE which lets us turn this on in general.
If no levels are specified then of course Ferret just uses the data range, but
if the user says (0,30,2) and MODE open_ended is turned on then that would
correspond to (-inf)(0,30,2)(inf)
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1502

Comment by ansley.b.manke on 1 Jul 2009 21:22 UTC
Closing this -- will write a new ticket with our current thinking.


Failed assertion with DropdownMenu

There should be exactly one item with [DropdownButtonFormField]'s value: Simba SC.
Either zero or 2 or more [DropdownMenuItem]s were detected with the same value
'package:flutter/src/material/dropdown.dart':
Failed assertion: line 933 pos 15: 'items == null || items.isEmpty || value == null ||
items.where((DropdownMenuItem item) {
return item.value == value;
}).length == 1'
I am using a Riverpod and a function to generate a list of items in dropdownmenu

Hi @Ridhiwan. Thanks for filing this. From the error log

Either zero or 2 or more [DropdownMenuItem]s were detected with the same value

This is an issue with the item values you are passing to your DropdownButtonFormField, kindly check this.
This issue isn't a bug or a feature request. Please see https://flutter.dev/community for resources and ask questions like this, you may also get some help if you post it on Stack Overflow
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you

My code was working completely fine and it was showing the dropdown Items correctly but when I launched it now the error keeps reappearing. I have even stopped using the provider and straight to hard coded values the error persists

I have gone through the error and it might not be a framework error.
Might have to do with state management of the values available in the DropdownButtonField


Fix style bug on problem shares

Fixes #4899
I updated the share bar function to not take in an analytics class parameter anymore, but I was still passing it when generating the problem share bar. The function was then not applying share bar classes I passed to it, because the ordering was off.

:+1:
the js-class gets added elsewhere now?

@angaither we use a generic ga-click tracking class that the js binds to. Then, use data attributes to pass in the custom stuff we want to track.


dashboard: fragment graph loads slowly when there's limited bandwidth and too many actors

It's possible that we need to access the web dashboard on a remote cluster with port-forwarding. In this case, the bandwidth between the local machine and the server could be quite limited. If there're too many actors, it could take a quite long time for the browser to fetch the graph JSON and the experience is not good.
Furthermore, @KeXiangWang reported that this procedure would fail under Kubernetes port-forwarding, with an error of broken pipe. This appears to be a known issue of Kubernetes (https://github.com/kubernetes/kubernetes/issues/74551) but not been resolved yet.
I believe what we can do is reduce the amount of data fetched from the meta service. Possible approaches:

Enable HTTP compression.
Manually reduce the data amount somehow like #13598, as in most cases except for the dispatcher, we do not care about the difference between the node bodies from different actors in the same fragment.
Improve the logic and shift more operations to the server side.

This should have already been resolved by https://github.com/risingwavelabs/risingwave/pull/15558.


Plugin System

It would be really great if people could register plugins that create their own view or just run some helper utilities. I'm imagining we would hand them either a reference to the subject or some Object that had subject and database.

Should this include adding own tabs?

Yeah, I'm kind of thinking that we assume a plugin author will provide us a React.Component and that the name we display is some class property (e.g. using displayName).

@rgbkrk I think that's a good idea. A system that allows the author to tap into the connection all the time is probably a lot more powerful though. We have to come up with something different for that I guess.

Maybe we should think about what plugins do, what are they supposed to do.
Do they enhance the UI by something clickable?
Do they automate tasks with the pipboy?
Do the need settings?
Example ideas:
Some non-gui mod could be an autoinject steampak mod.
(I saw this somewhere here)
Some gui thing might be for example an radar for your quests.

@luckydonald Yea, definitely make sense to list these requirements. Imho, plugins should be able to:

Access the connection subject (receive and send payloads)
Add one or more new panes
Add settings to a kind of plugin page

I think all of these requirements can be easily fulfilled. I think an easy solution would be:
A plugin is an npm (like) package. The package's main file is imported inside the pipboy app. Now either the pipboy app injects a module / dependency that exposes our plugin API (quite complex) or it just imports a function that each plugin exports.
The API might expose certain methods that can add components as panes, or add settings. All background logic then actually doesn't have to be implemented explicitly, but would be just a side effect


feat: clap v4

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Breadcrumbs Updated design

Successfully resolve the issue #674.
Please check the and my first pull request.

You need to make a design system for the bread crumb not a new design system for breadcrumb. Please refer to the issue description. @Kumar-Ankit56

You need to make a design system for the bread crumb not a new design system for breadcrumb. Please refer to the issue description. @Kumar-Ankit56

@Rajdip019 Yes
By mistake I designed this but currently I have open new pull request for design system as well.
I just want to say can't you take this design as it is different version with skew property because I worked it be no use if it will stay with me because I will be only able to use this.
Thanks


Name of the backend in MNE-Python

To make use of this amazing package, I have to refer to it as pyqtgraph backend in MNE-Python. This is super technical and its name has nothing to do with the name of this package (well, of course, except for the qt bit)
Any chance we could simply name the backend qt or so? At least in the public API?
cc @larsoner

Yes, I would also like "qt" much better :thumbsup:


Media Manager Not Working

Images not uploading - I found some errors on the console
also, it does not show the Preview and previously uploaded images
I am using Gitlab (Private Respo) & Hugo
backend Method  - git-gateway
Uncaught (in promise) TypeError: Cannot read property 'find' of undefined
    at M (mediaLibrary.js:84)
    at index.js:9
    at bindActionCreators.js:3
    at ae (MediaLibrary.js:125)
    at Object.<anonymous> (react-dom.production.min.js:15)
    at Object.invokeGuardedCallback (react-dom.production.min.js:16)
    at Object.invokeGuardedCallbackAndCatchFirstError (react-dom.production.min.js:16)
    at C (react-dom.production.min.js:20)
    at N (react-dom.production.min.js:22)
    at I (react-dom.production.min.js:22)

Rest Features are Working fine

This looks like a duplicate of #1608, let's discuss there. Thanks for reporting!