GEOS aborting with "Assertion failed" on OS X, discussion and work around

I've spent a bit of free time looking more deeply into the reports of GEOS aborting in the AbstractSTRtree.cpp module (either in query() or itemsTree()) on OS X when fiona is imported before shapely in a Python script.
Here are the conditions for a program that will unexpectedly abort:

Any version of Python on OS X.
Fiona and Shapely binary wheels for macosx downloaded from PyPI. These wheels include libgeos_c.dylib and libgeos-3.6.2.dylib files.
A script that imports fiona before shapely and which triggers the creation of a GEOS STR R-tree. Calling ops.unary_union with a number of lines or polygons will suffice.

Here's an example program:
import fiona

from shapely.geometry import Point
from shapely.geos import geos_version
from shapely.ops import unary_union

print(geos_version)

SHAPES = [Point(i, i).buffer(1.5) for i in range(20)]
for i, s in enumerate(SHAPES):
    print(i, s.is_valid)
    print(i, s.wkt)
    print(i, s.area, s.length)
    print(i, s.intersects(Point(10, 10).buffer(8.0)))

union = unary_union(SHAPES)
print(union)

I've run the script under lldb with a modified version of GEOS 3.6.2 that prints some debugging output before calling assert().
...
19 7.057234103728362 9.420993470864257
19 False
Assertion failed: (!static_cast<bool>("should never be reached")), function itemsTree, file AbstractSTRtree.cpp, line 379.
dynamic_cast<AbstractNode*>: 0x0dynamic_cast<ItemBoundable*>: 0x0childBoundable: 0x100498510Process 17968 stopped
* thread #1: tid = 0x606ba9, 0x00007fff8d415f06 libsystem_kernel.dylib`__pthread_kill + 10, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
    frame #0: 0x00007fff8d415f06 libsystem_kernel.dylib`__pthread_kill + 10
libsystem_kernel.dylib`__pthread_kill:
->  0x7fff8d415f06 <+10>: jae    0x7fff8d415f10            ; <+20>
    0x7fff8d415f08 <+12>: movq   %rax, %rdi
    0x7fff8d415f0b <+15>: jmp    0x7fff8d4107cd            ; cerror_nocancel
    0x7fff8d415f10 <+20>: retq

I've failed to get access to variables in the frame where assert() is called. I am frankly over my head in trying to debug a dlopen'ed C++ library.
Changing the intersects() call in the script to intersection() leads to another failed assertion and an aborted program the first time there is a non-empty intersection.
...
4 7.057234103728363 9.42099347086426
Assertion failed: (0), function query, file AbstractSTRtree.cpp, line 288.
Process 18002 stopped
* thread #1: tid = 0x6074fe, 0x00007fff8d415f06 libsystem_kernel.dylib`__pthread_kill + 10, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
    frame #0: 0x00007fff8d415f06 libsystem_kernel.dylib`__pthread_kill + 10
libsystem_kernel.dylib`__pthread_kill:
->  0x7fff8d415f06 <+10>: jae    0x7fff8d415f10            ; <+20>
    0x7fff8d415f08 <+12>: movq   %rax, %rdi
    0x7fff8d415f0b <+15>: jmp    0x7fff8d4107cd            ; cerror_nocancel
    0x7fff8d415f10 <+20>: retq

The problem in query() appears to be the same as in itemsTree(): the dynamic casts return null pointers and the library fails by calling assert(0).
https://github.com/OSGeo/geos/blob/master/src/index/strtree/AbstractSTRtree.cpp#L277-L287
If fiona is imported after shapely, the programs (either with intersects() or intersection()) run without problems.
My hypothesis is that there is a race condition in initialization of the libgeos-3.6.2 library that leaves some objects in the AbstractSTRtree.cpp module in a partly or improperly initialized state when we dlopen the GEOS lib after it has already been loaded in the process via import of fiona. Use of GEOS as both a dependent library of fiona modules and as a library we dynamically load during import of shapely is a little weird, I grant, but doesn't necessarily have to trigger crashing bugs. There's no problem on Linux. I see some hints that the difference between ELF and Mach-O might be important.
Workaround 1
Install the GEOS library to one standard location on your macosx system using homebrew, fink, macports, or from source, do the same for GDAL, and then install fiona and shapely like so:
pip install --no-binary shapely,fiona shapely fiona
You can import fiona and shapely in any order if you do this.
Workaround 2
On OS X, if you're using fiona and shapely wheels together, import shapely first. It's annoying to have to do this, I know. Abstracting away the C/C++ details of GEOS and GDAL has been one of my main design principles for fiona and shapely, and I'm falling short.
Solution
I think there's a race condition bug to be fixed in the GEOS library. You can see some indication of that at https://lists.osgeo.org/pipermail/geos-devel/2017-November/008157.html. Because this doesn't affect Linux and PostGIS, it's a very low-flying bug.
Fixing it will require more knowledge and experience with C++ and dynamic library building and loading on Mac OS X than I currently have, and so the fix isn't going to be coming soon unless we can get some help.
I'm somewhat content to at least have a master ticket that I can point users at. It's a start.
/cc @snorfalorpagus @perrygeo

Hi, I am not using Fiona, only shapely. I was trying to use Shapely's parallel_offset(). Building the program in the terminal is fine but when I tend to check my browser, it crashes with the alert that  "Python quit unexpectedly." In my python console, the error says
Assertion failed: (0), function query, file AbstractSTRtree.cpp, line 287.
Process finished with exit code 134 (interrupted by signal 6: SIGABRT)

I do not use fiona, but was still experiencing this issue. I first attributed it to spatialite, since I am attempting to get Python 2.7.15 running on OS X and rebuilding libspatialite. Using the --no-binary flag in pip solved my issue it appears.
I didn't suspect shapely since all I am doing is using a Polygon and the wkb_hex value in a Spatialite query that uses an Intersection(). I wasn't using one of the Shapely functions above, strictly Spatialite functions.

Still encountering this issue without Fiona (only shapely and GEOS on a mixed Python/C++ library) on OSX and python 3.7.
Using pip install --no-binary shapely, shapely fixed it.

Yes, acknowledged. The problem is between GEOS and dlopen (ctypes) and it remains.

Using the geometry.split method I am getting the same error.  I tried installing shapely with the following and still getting the error.   Can I not specify a version in this no-binary approach?  the reason i have to use --ignore-installed is because I already have a version of Shapely installed that i cannot remove because it's a 'distutils installed project' which I don't quite grok yet.
pip install --ignore-installed --trusted-host pypi.org --trusted-host files.pythonhosted.org  --no-binary shapely==1.6.4.post2,fiona shapely==1.6.4.post2 fiona

@CordThomas pip install --no-binary shapely,fiona shapely==1.6.4 fiona is the correct usage.

Just to add to this thread, I'm seeing the same behavior in a virtualenv that meets the above descriptions.
Re-installing from source for Fiona and Shapely did not fix the problem.
I did some digging in my virtualenv and found the geos binary installed by rasterio:
.../lib/python3.5/site-packages/rasterio/.dylibs/libgeos-3.6.2.dylib
.../lib/python3.5/site-packages/rasterio/.dylibs/libgeos_c.1.dylib

This appears to have fixed it:
pip uninstall -y rasterio && pip install rasterio==1.0.11 --no-binary rasterio

Update: in my experience, shapely 1.7a2 (released yesterday) solves this on OS X. The example program runs with no errors and no crashes. If you'd like to confirm, try pip install -U --pre shapely and let me know how it goes.

I am getting this error as well. Using dissolve method on geopandas geometry series to group shapely polygons together based on some shared metadata attribute (datetime).
I'm working in a conda env but have tried both updating to new shapely version 1.7a2 and many of the other hints in the thread. Still crashing my notebook.
Any other tips for conda users?

shapely 1.7a2 solved this issue for me. I had to reinstall fiona as well. Now I can run the initial example regardless of the import order (fiona vs shapely). Thank you @sgillies

Upgrading to shapely 1.7a2 solved the GEOS assertion error for me, but then I quickly ran into issues when reading polygon data from a file geodatabase. Any polygon files would be read in without geometry and I'd get a Shell is not a LinearRing error when attempting any operation on them.
I read up on solutions for the second issue and they all seemed to point to making sure that conda is being used correctly. I have everything installed into an independent environment using only pip and haven't ran into problems like this before.
Is there a stable pathway for installing shapely, fiona, and geopandas through pip or do we have to move to using conda for installs only?
My current environment file (before upgrading to shapely 1.7a2) is below
requirements.txt

affine==2.2.1
appnope==0.1.0
area==1.1.0
asn1crypto==0.24.0
astroid==2.2.5
attrs==18.2.0
azure-common==1.1.16
azure-nspkg==2.0.0
azure-storage==0.36.0
backcall==0.1.0
bleach==3.0.2
boto3==1.7.4
botocore==1.10.84
certifi==2018.11.29
cffi==1.11.5
chardet==3.0.4
Click==7.0
click-plugins==1.0.4
cligj==0.5.0
cryptography==2.4.2
cycler==0.10.0
Cython==0.29.5
decorator==4.3.0
defusedxml==0.5.0
descartes==1.1.0
docutils==0.14
entrypoints==0.3
Fiona==1.8.3
flake8==3.7.5
future==0.17.1
geojson==2.3.0
geopandas==0.4.0
greenlet==0.4.15
idna==2.7
ijson==2.3
ipykernel==5.1.0
ipython==7.2.0
ipython-genutils==0.2.0
ipywidgets==7.4.2
isort==4.3.21
jedi==0.13.1
Jinja2==2.10
jmespath==0.9.3
joblib==0.13.1
jsonschema==2.6.0
jupyter==1.0.0
jupyter-client==5.2.3
jupyter-console==6.0.0
jupyter-core==4.4.0
jupyterlab==0.35.4
jupyterlab-server==0.2.0
keyring==17.0.0
kiwisolver==1.0.1
lazy-object-proxy==1.4.2
MarkupSafe==1.1.0
matplotlib==3.0.2
mccabe==0.6.1
mercantile==1.0.4
mgrs==1.3.5
mistune==0.8.4
msgpack==0.6.1
munch==2.3.2
nbconvert==5.4.0
nbformat==4.4.0
neovim==0.3.1
notebook==5.7.2
numpy==1.15.4
pandas==0.23.4
pandocfilters==1.4.2
parso==0.3.1
pdfkit==0.6.1
PDPbox==0.2.0
pexpect==4.6.0
pickleshare==0.7.5
Pillow==5.4.1
plotly==3.4.2
prometheus-client==0.4.2
prompt-toolkit==2.0.7
psutil==5.5.0
ptyprocess==0.6.0
pyarrow==0.8.0
pyasn1==0.4.4
pyasn1-modules==0.2.2
pycodestyle==2.5.0
pycparser==2.19
pycryptodomex==3.7.2
pyflakes==2.1.0
pyGeoTile==1.0.6
Pygments==2.3.0
PyJWT==1.7.0
pylint==2.3.1
pynvim==0.3.2
pyOpenSSL==18.0.0
pyparsing==2.3.0
pyproj==<IP_ADDRESS>
pyshp==2.0.1
python-dateutil==2.7.5
python-dotenv==0.10.1
pytz==2018.4
PyYAML==3.12
pyzmq==17.1.2
qtconsole==4.4.3
rasterio==1.0.12
requests==2.20.1
retrying==1.3.3
Rtree==0.8.3
s3transfer==0.1.13
scikit-learn==0.20.2
scipy==1.1.0
seaborn==0.9.0
Send2Trash==1.5.0
sentinelhub==2.5.0
Shapely==1.6.2.post1
six==1.11.0
sklearn==0.0
snowflake-connector-python==1.6.10
snuggs==1.4.2
SQLAlchemy==1.2.15
supermercado==0.0.5
terminado==0.8.1
testpath==0.4.2
tifffile==2019.1.30
tornado==5.1.1
traitlets==4.3.2
typed-ast==1.4.0
urllib3==1.24.1
utm==0.4.2
wcwidth==0.1.7
webencodings==0.5.1
widgetsnbextension==3.4.2
wrapt==1.11.2
xmltodict==0.11.0

@jcusick13 I'm closing this issue because it has been resolved. The Shell is not a LinearRing message has been reported a few times: https://github.com/Toblerity/Shapely/search?q="shell+is+not+a+linearring"&type=Issues. It's a symptom of a shared library incompatibility. Using conda is a good choice because, if your environment is in good shape, you only have one GEOS shared library between all of the geopandas dependencies.


Segmentation fault on Ubuntu 20.04

Describe what happened:
I just installed the extension and it is not working at all, I get a segmentation fault activating the extension. I read elsewhere that it may depend by Mono raising errors when multiple libssl versions, but I have only one:
> ls /usr/lib/x86_64-linux-gnu/libssl.so.*
/usr/lib/x86_64-linux-gnu/libssl.so.1.1

What was your system configuration?
Product and Version [VS/VSCode]: 1.62.2
OS Version[macOS/Windows]: Linux
Live Share Extension Version: v1.0.5090
Target Platform or Language [e.g. Node.js]:

Steps to Reproduce / Scenario:

Install Live Share extension
Install Live Share dependencies

Please attach logs to this issue: live-share-logs.log
You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue
Screenshots:

Solved it launching Live Share: Repair.


Add SITL target for simulating catapult / handlaunching fixed wing

Describe problem solved by this pull request
This PR implements a SITL target for a plane_catapult model which includes a catapult plugin implemented in https://github.com/PX4/sitl_gazebo/pull/393
This simulates fixed wing being launched by a catapult or being hand launched. This is required to test the takeoff mode of the fixed wing, which has been largely untested in simulation until now.
Describe your solution
The plugin ca be launched with the following command
make px4_sitl gazebo_plane_catapult

Test data / coverage

Additional context
This was brought up from a discussion with @dagar
Might be of interest to @Antiheavy

That was fast! Nice work.

Will you point the nose along the launch vector?

@mhkabir I am currently just applying force for a fixed duration. Does this mean that I should constrain the motion while the vehicle is being launched?
My thought process was that hand launching would be a more general case which would include the catapult launch, and constraining the attitude or line of motion wouldn't make much sense.

I think what is here is perfectly fine. If someone wants a simulated catapult they can contribute it - that's the great thing about open source. We shouldn't be in the business of doing the work for people on features - we have our hands full maintaining the core.

@Jaeyoung-Lim This is very cool. Can you add a heading and very brief explanation of the option under here: http://dev.px4.io/master/en/simulation/gazebo.html#running-the-simulation ?


Prevent zooming on mobile

Hopefully this prevents iOS safari zooming into text fields

@aapeliv how's this

https://www.30secondsofcode.org/blog/s/zooming-accessibility-tips
Especially:

while others such as iOS 10 ignore the suggestion entirely, so you should be aware that you might not be delivering a consistent user experience for all of your users.

I don't have an iPhone to test but not sure if this would work? And it seems anti-accessibility to disable zooming for other browsers/Android that may not be affected by this...
This might be a better solution instead? https://stackoverflow.com/questions/2989263/disable-auto-zoom-in-input-text-tag-safari-on-iphone

It did work but you're right, it's bad accessibility. Trying this.

@aapeliv should probably check this? I don't have a physical iPhone 😅


TSelect is working with WARNING when I bind it with v-model

Hi @alfonsobries,
It was working fine in v2.0.0 but since 2.0.1 t-select does not seem to work properly with v-model.
[Vue warn]: Invalid prop: type check failed for prop "value". Expected Array, String, Number, got Event
Thank you!

Hey thanks for the report @zhang9553 ill take care tomorrow

Hey thanks for the report @zhang9553 ill take care tomorrow

Hi Alfonso Bribiesca,
Thank you for your response.
I appreciated to your great work!
Have a great weekend.
Best Regards,
Zhang He
From: Alfonso<EMAIL_ADDRESS>Sent: Monday, January 25, 2021 12:01 AM
To<EMAIL_ADDRESS>Cc: Zhang He<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [alfonsobries/vue-tailwind] TSelect is working with WARNING when I bind it with v-model (#135)
Hey thanks for the report @zhang9553https://github.com/zhang9553 ill take care tomorrow
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/alfonsobries/vue-tailwind/issues/135#issuecomment-766394605, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APBFGE3BRVQNZLTV74S6SJTS3RG7RANCNFSM4WQQMXOQ.

Hi Alfonso Bribiesca,
Thank you for your response.
I appreciated to your great work!
Have a great weekend.
Best Regards,
Zhang He
From: Alfonso<EMAIL_ADDRESS>Sent: Monday, January 25, 2021 12:01 AM
To<EMAIL_ADDRESS>Cc: Zhang He<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [alfonsobries/vue-tailwind] TSelect is working with WARNING when I bind it with v-model (#135)
Hey thanks for the report @zhang9553https://github.com/zhang9553 ill take care tomorrow
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/alfonsobries/vue-tailwind/issues/135#issuecomment-766394605, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APBFGE3BRVQNZLTV74S6SJTS3RG7RANCNFSM4WQQMXOQ.

@zhang9553 should be fixed on 2.1.1

@zhang9553 should be fixed on 2.1.1

It works great!
Thank you
From: Alfonso<EMAIL_ADDRESS>Sent: Monday, January 25, 2021 10:30 PM
To<EMAIL_ADDRESS>Cc: Zhang He<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [alfonsobries/vue-tailwind] TSelect is working with WARNING when I bind it with v-model (#135)
@zhang9553https://github.com/zhang9553 should be fixed on 2.1.1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/alfonsobries/vue-tailwind/issues/135#issuecomment-766897507, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APBFGE3XLYBSY6ETTMTUWHTS3WFCRANCNFSM4WQQMXOQ.

It works great!
Thank you
From: Alfonso<EMAIL_ADDRESS>Sent: Monday, January 25, 2021 10:30 PM
To<EMAIL_ADDRESS>Cc: Zhang He<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [alfonsobries/vue-tailwind] TSelect is working with WARNING when I bind it with v-model (#135)
@zhang9553https://github.com/zhang9553 should be fixed on 2.1.1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/alfonsobries/vue-tailwind/issues/135#issuecomment-766897507, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APBFGE3XLYBSY6ETTMTUWHTS3WFCRANCNFSM4WQQMXOQ.


OperationApi: If getting and executing operations with address and/or descriptor check full address

Currently getting descriptor by address will be split in a search for path and version. But if there are additional informations (parts) it will be ignored and the wrong operation are addressed.
The same situation for calling operations with descriptor.
e.g. If the same operation in different jms sources exists, this can cause the system to use the wrong operation.

done


Fix Availability Status Warn condition

Saw this while testing - we were getting a warn for 204 and I realized I used % instead of /. This will eliminate the warn message since anything 2xx is not a problem.

I like size of this PR :)

+1/-1 are the best kind!


fix: hide scrolls in all browsers

add class to hide scroll bars

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


[MFB] Icons doesn't work well on Hexo

I use MFB to build my own site based on Hexo, It works well in localhost, but after I publish my site, I notice that the icons do not appear at all.(Git Page + Hexo)
localhost:

web:

Please help me! Thanks a lot!
Greetings!

OK, I found a solution, now I'm using fontisto icons, works well.


Modelix.core 9.1.0

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


Add cellType property to the matrix dropdown/dynamic

I have got a survey with a dropdown matrix question that has a lot of checkbox columns. Actually all columns are checkbox. Since the default editor is dropdown, all columns have cellType: "checkbox" attribute. It would be nice to have the cellType on the question/matrix level to change the default editor type.

Implemented: additionally added columnColCount and columnMinWidth properties to avoid duplication in survey JSON, matrix columns

Used in this example


Update README.md to use Membrane.Opus.Parser

Replaces references to the removed Membrane.Opus.Serializer
Adds a reference to the (currently not published to Hex) Membrane
Ogg Plugin to guide people to a potential solution for containerization.

Addresses #29.

Thanks ;)


Move FunctionWrapper to triad

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (a05e763) 100.00% compared to head (7140c12) 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##            master      #100    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files           22        23     +1
  Lines         1755      1884   +129
==========================================
+ Hits          1755      1884   +129

Impacted Files
Coverage Δ

triad/collections/function_wrapper.py
100.00% <100.00%> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Validate print template when allowing on survey

Motivation and Context
When we create print templates, we have no list of columns to validate against, so anything is allowed. We should instead validate at the point when we attempt to allow a print template on a particular survey.
What has changed
Added validation at the point print templates are allowed on surveys.
How to test?
Create a print template with crazy columns, then try to associate it to a survey... it should complain about the crazy columns.
Links
Trello: https://trello.com/c/rUBC4RJt
Screenshots (if appropriate):

 Validation on print template association to a survey should check columns - action rule only (8)


[py2py3] Migration at level scr/python/A/B/C - slice 23

Fixes #10147
Status
In development
Related PRs

Previous migration PR: #10362  (slice22, issue #10146 )
Next migration PR: #10371 (slice24, issue #10148 )

Description
Run futurize and some manual changes on the first batch of src/python/A/B/C.
"Native String" approach (use str in both py2 and py3, hoping that it stays consistent within the same runtime):

src/python/WMCore/BossAir/Plugins/MockPlugin.py: using jobid = str(jj['id']) to append a str to tmpname = report.cmsRun1.output.output.files.file0.lfn.split('.root')[0]. Not a problem if it is kept as a str in both py2 and py3
src/python/WMCore/BossAir/Plugins/SimpleCondorPlugin.py:

format input of classad.quote(input), which should accept a str input in py3 as well as they claim, but better be safe than sorry and check this.
format a ton of keys of a dict that is appended to JobParameters, such as ad['My.OriginalCpus'] = str(origCores). If this is used only by us in SimpleCondorPlugin.createSubmitRequest and not by WMCore clients, we may be in a good spot.
tracked in #10378

Is it backward compatible (if not, which system it affects?)
It should be. (Any possible cause for errors will we reported here)
External dependencies / deployment changes
Requires python-future in both py2 and py3 environments.

Tracking the investigations about SimpleCondorPlugin in #10378


Delegate v1

Overview
To keep the v1 delegation flow simple, we can use a similar flow to /send-money.
The validator whitelist can send users to /staking/stake/<validator_name>/, and we'll prepopulate the validator.
We should also display the users current delegated balance, the validator(s) they've delegated to, and their unclaimed rewards on /staking.
Acceptance Criteria
On /staking

[ ] If there is no validator name in the /staking/stake URL, the user can enter the validator name
[ ] A link with the validator name in it /staking/stake/<validator_name> prepopulates the validator name
[ ] Users can enter the relevant details to initiate a delegation TX to the chosen validator

[ ] Amount of NEAR to delegate

[ ] Users can view their total delegated balance
[ ] Users can view their unclaimed rewards
[ ] Users can view each validator they've delegated to

[ ] Validator name
[ ] Amount delegated
[ ] Unclaimed rewards

For v1, I think the two actions for users should be just "delegate" and "undelegate". "Delegate" should call both deposit and stake on the staking pool contract. “Undelegate” should call “unstake” and “withdraw”.
Should we allow users to specify the amount to undelegate in v1? Or just undelegate all?
Also, should we allow users to delegate to more than one validator in v1?
cc @mattlockyer @vgrichina @Patrick1904 @corwinharrell @jimmy3dita

@jimmy3dita Do you think we can get Figment/Hubble to maintain which validators support delegation, and link to the appropriate delegation page for each of them?

For v1, I think the two actions for users should be just "delegate" and "undelegate". "Delegate" should call both deposit and stake on the staking pool contract. “Undelegate” should call “unstake” and “withdraw”.

Be careful that unstake and withdraw cannot happen at the same time, there's a three epoch-long lock period for the funds. So a user that unstaked funds will have to wait until he can withdraw the funds.

Should we allow users to specify the amount to undelegate in v1? Or just undelegate all?

The protocol automatically re-stakes all the funds, so it could be possible that users would like to withdraw only the rewards without "killing" their favorite validator. I suppose that we have to leave them free to set the amount (even in chunks of 0.1 Near or similar).

Also, should we allow users to delegate to more than one validator in v1?

Depends on the amounts we plan to store in the wallet. Whales might be interested to use more than one validator - but at that point they might use a different tool such as near-shell.

@jimmy3dita Do you think we can get Figment/Hubble to maintain which validators support delegation, and link to the appropriate delegation page for each of them?

for an updated list (maintained by validators themselves) we can use this section of the Stake Wars repo: https://github.com/nearprotocol/stakewars/blob/master/VALIDATORS.md#testnet-validators

Be careful that unstake and withdraw cannot happen at the same time, there's a three epoch-long lock period for the funds. So a user that unstaked funds will have to wait until he can withdraw the funds.

Good point. Breaking out the "Undelegate" functionality into a separate issue, as there is a bit more complexity than I realized: https://github.com/near/near-wallet/issues/755

Wanted to share the WIP UI for Delegation. In an attempt to design/build this in an iterative fashion, the UI and prototype currently focus on the primary stake flow. The following is missing at the time of this post but is soon to follow:

Total delegated balance
Unclaimed rewards

Some things to note:

This UI leverages the current "Send" flow, but with a facelift. We have the option of using the updated version, which would result in an update to Send as well, or we can fall back on the current send flow and use it unchanged. The core elements between them are consistent, there are simply some improvements I made to the form.

As mentioned above, there will be some changes happening to the validator list and li design to include some additional metadata. Just wanted to mention this so we can anticipate those things changing to reflect things link rewards and additional actions. Right now they just contain the bare-minimum to facilitate the primary flow.

Please leave feedback and comments in Figma regarding any specific UI decisions or language used. cc @jimmy3dita
Figma Doc: https://www.figma.com/file/q4OnMvaPpwowEZ9kCSOk2w/753-Delegate-v1?node-id=1101%3A1153
Interactive Prototype: https://www.figma.com/proto/q4OnMvaPpwowEZ9kCSOk2w/753-Delegate-v1?node-id=1101%3A1153&scaling=scale-down

As we discussed at the end of last week, I'm going to scope the UI down for each individual issue within the delegation epic, so that we can build this out in an iterative fashion. I'll be moving the resources provided in my last comment to #722, where a "complete" version of the UI will live, representative of the Epic in its final state.
The following UI is limited to this issue, and only allows the user to enter a known validator, and stake with that validator:
https://www.figma.com/file/oy0wBFxW5H8nTFZtFaMZpK/753-Delegate-v1?node-id=1162%3A795

@kcole16 With the re-introduction of the stripped down validator profile where the user will manage their stake and rewards, I'm wandering if we want to create an additional issue for "Manage my stake" that includes:

View my amount that is pending release from my validator
View my list of validators with unclaimed rewards
View my list of validators with funds available for withdrawal
Claim rewards from a validator
Withdraw my funds from a validator/delegation contract

Maybe it makes sense to roll these up into #755? Thoughts @mattlockyer @Patrick1904?
The way I'm thinking about the iterations of this project are as follows, which is slightly different than how the Epic is split up right now:

Stake with Known Validator
Find a validator (whitelist)
Manage my stake (unstake, claim rewards, withdraw balance)

@kcole16 @corwinharrell can you please provide copy/explanations for the following staking concepts:

Total amount staked
Unclaimed rewards
Available for withdrawal
Pending release
Staking fee

Staking fee

This name feels a bit confusing to me. People could interpret it as the transaction fee associated with sending the staking transaction.

@bowenwang1996 How about "Validator Fee"?

Yeah that sounds better

@kcole16 @bowenwang1996 updating the copy to 'Validator Fee'.

@Patrick1904
Total amount staked

NEAR tokens currently staked with validators. These tokens are accumulating rewards. To access these tokens, you must first unstake and then withdraw them.

Unclaimed rewards

Rewards that have been earned, but not withdrawn. Unclaimed rewards are automatically restaked, which means your "Total Amount Staked" automatically increases over time, and your rewards are compounding.

Available for withdrawal

These tokens have been unstaked, and are ready to be withdrawn.

Pending release

These tokens have been unstaked, but are not yet ready to withdraw. Tokens are ready to withdraw 36 hours after unstaking.

Validator fee

This is the fee paid to the validator to stake on your behalf. This fee is only charged on your rewards.


No 'Next X Tide' info usign public API

[### System Health details
System Information

version
core-2024.2.0

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.12.1

os_name
Linux

os_version
6.1.74-haos

arch
x86_64

timezone
Pacific/Auckland

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
5000

Installed Version
1.34.0

Stage
running

Available Repositories
1385

Downloaded Repositories
19

Home Assistant Cloud

logged_in
true

subscription_expiration
February 4, 2025 at 1:00 PM

relayer_connected
true

relayer_region
ap-southeast-1

remote_enabled
true

remote_connected
true

alexa_enabled
true

google_enabled
false

remote_server
ap-southeast-1-2.ui.nabu.casa

certificate_status
ready

instance_id
e38287e14dd74dc3aa3d5d2e86273523

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 11.5

update_channel
stable

supervisor_version
supervisor-2024.01.1

agent_version
1.6.0

docker_version
24.0.7

disk_total
116.7 GB

disk_used
16.4 GB

healthy
true

supported
true

board
generic-x86-64

supervisor_api
ok

version_api
ok

installed_addons
Samba share (12.2.0), File editor (5.7.0), AirCast (4.2.0), Advanced SSH & Web Terminal (17.1.0), TasmoAdmin (0.29.1), Mosquitto broker (6.4.0), OneDrive Backup (2.3), Zigbee2MQTT (1.35.3-1), chrony (3.0.1), ESPHome (2023.12.9), Whisper (1.0.2), Piper (1.4.0), openWakeWord (1.8.2), Run On Startup.d (0.11a)

Dashboards

dashboards
5

resources
9

views
7

mode
storage

Recorder

oldest_recorder_run
January 29, 2024 at 4:17 AM

current_recorder_run
February 8, 2024 at 10:36 AM

estimated_db_size
681.98 MiB

database_engine
sqlite

database_version
3.44.2

](url)
Checklist

[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of any previous issues..

Describe the issue
I have selected Auckland as my city,.
There is no tide information showing up:

Is that a bug, or am I missing some configuration?
Reproduction steps

...
Debug logs
No response
Diagnostics dump
No response

It is the same for me using Public location of Nelson.

Evening @clowgg and

Yes that would be useful. Thanks.

Updated in v0.6.0 - please update and let me know what you think @Tarawera @clowgg
Note - this is a breaking change; you'll need to reconfigure the integration to choose your tide locations.

Thanks ChrisAll is working fine in Nelson now. I did have to delete and reinstall the integration to get it to ask about the tide city.RegardsDavid (Tarawera)On 17/02/2024, at 2:33 PM, Chris Jenkins @.***> wrote:
Updated in v0.6.0 - please update and let me know what you think @Tarawera @clowgg
Note - this is a breaking change; you'll need to reconfigure the integration to choose your tide locations.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Deleted and re-added integration in HA [Settings/Integrations] (http://ha/config/integrations/integration/metservice_weather).
Choose Onehunga as tide locale. All working fine :)  Thank you @ciejer !!!


fix: drop invalid discovered environment(#8075)

Summary
Fix #8075.
Invalid discovered environments in the working directory should be filtered out.
Test Plan

Test python_find

This commit will also affect pip subcommand.
$ RUST_LOG=debug /tmp/uv pip install idna
DEBUG uv 0.4.20
DEBUG Searching for default Python interpreter in system path
DEBUG Found `cpython-3.12.6-linux-x86_64-gnu` at `/usr/bin/python` (search path)
DEBUG Ignoring Python interpreter at `/usr/bin/python`: system interpreter not explicitly requested
DEBUG Found `cpython-3.12.6-linux-x86_64-gnu` at `/usr/bin/python3` (search path)
DEBUG Ignoring Python interpreter at `/usr/bin/python3`: system interpreter not explicitly requested
DEBUG Found `cpython-3.12.6-linux-x86_64-gnu` at `/usr/bin/python3.12` (search path)
DEBUG Ignoring Python interpreter at `/usr/bin/python3.12`: system interpreter not explicitly requested
error: No virtual environment found; run `uv venv` to create an environment, or pass `--system` to install into a non-virtual environment

$ RUST_LOG=debug uv pip install idna
DEBUG uv 0.4.20
DEBUG Searching for default Python interpreter in system path
error: Broken virtualenv `/home/code/.venv`: `pyvenv.cfg` is missing

$ RUST_LOG=debug uv pip list
DEBUG uv 0.4.20
DEBUG Searching for default Python interpreter in system path
error: Broken virtualenv `/home/code/.venv`: `pyvenv.cfg` is missing

$ RUST_LOG=debug /tmp/uv pip list
DEBUG uv 0.4.20
DEBUG Searching for default Python interpreter in system path
DEBUG Found `cpython-3.12.6-linux-x86_64-gnu` at `/usr/bin/python` (search path)
Using Python 3.12.6 environment at /usr
Package            Version
------------------ ---------
autocommand        2.2.2
fail2ban           1.1.0

Ah we can't just filter there — that will change behavior too much.
Perhaps at https://github.com/astral-sh/uv/blob/715f28fd398aae1a6347deb312e3d0a27161696b/crates/uv-python/src/discovery.rs#L677 instead? I don't think this change is valid for other operations though.

@zanieb
Maybe I'm using it incorrectly, I previously created virtual nesting under the .venv folder.
uv venv .venv/jupyter

tree -L 1 .venv
# .venv
# ├── huggingface
# ├── jupyter
# └── nogil


switch host verify to on host

Signed-off-by: brmclaren<EMAIL_ADDRESS>

/retest

/override pr-test-infra-validate-host-verify-debug


Segment Wiki

We may want to start putting segment information on the wiki and indicate when they are available only for a certain OS. As far as I can see, the dropbox-cli is only available on Linux.

This works on OSX...
mkdir -p ~/bin
wget -O ~/bin/dropbox.py "https://www.dropbox.com/download?dl=packages/dropbox.py"
chmod +x ~/bin/dropbox.py
# alias to the pyton script
printf "\nalias dropbox-cli='~/bin/dropbox.py'\n" | tee -a ~/.zshrc

Right now, we actually don't have any OS-specific segments, that I'm aware of, and generally I refuse to merge segments unless they work cleanly on all supported OSes. If there are segments you find that don't work in some OS, be sure to file a bug!
It sounds like this Dropbox issue was settled, though? If not, feel free to re-open!

It doesn't work for me. dropbox-cli start -i opens a python download window to download the daemon, but it doesn't even progress from 0. When run in root, it halts with Error: Platform not supported so it's not supported on macOS High Sierra 10.13.3


latest libsharp

We should try and move to the latest version of libsharp, which is currently hosted in gitlab (https://gitlab.mpcdf.mpg.de/mtr/libsharp). I just found out about this now

Kudos to @gfabbian for bringing this up

Solved by #71

The main change is that ntrans is no longer a parameter for sharp_execute.  You'll have to transform the 0 and 2 maps with two calls to sharp_execute, I think. I also had some trouble getting the sharp_Ylmgen_destroy function from configure.ac to be found.

It's slightly more complicated than that as also the FFT library and linking changed. I got it running at NERSC with the lib sharp version distributed in Healpix 3.5 and with the version checked out from the repo. Any preference how to solve this? In order to keep the support for all library version then some preprocessing statements in the code to be specified when compiling should be enough.

Hey @gfabbian . Did you have to modify NaMaster itself (including the configure scripts)? If so, a PR form a fork would be ideal (as would any instructions to reproduce what you had to do).

Yes, slightly. I am working for a proper modification of the config file and then do the PR. I also need edto to port the c_libs from the old libsharp version as it is no longer distributed with the new version. I think the licence allows that.

It's done and I've submitted a PR. If  @xzackli or others want to check can also pull from my fork. Let me know if edits to the doc are needed or something is not clear or, worse, not working!

I'm gonna close this for the time being, since the gitlab version seems to still be under development (or at least it's been changing significantly lately). I'll get back to this once things are stable.


Gliblastoma Multiforme

http://tcga-data.nci.nih.gov/docs/publications/gbm_2008/
GBM.zip

Thanks Michela, you're the first one to choose a cancer type!


4th, and 5th order XC derivatives

Add a patch to xcfun to compute up to 5th order XC derivatives
Update xcfun_itrf for up to 5th order derviatives
Update libxc_itrf to support 4th order XC derivatives
Add the transform_xc function to support arbitrary order XC derivatives
Update conda build script

What do you need 5th order derivatives for, should we also generate these in libxc in a later release...?

What do you need 5th order derivatives for, should we also generate these in libxc in a later release...?

It is mainly for the non-collinear/multi-collinear functional methods. The multi-collinear functional requires a higher order derivative than the regular xc functional derivatives. Constructing the 4th order multi-collinear derivative requires 5th order XC derivative. TDDFT gradients  with multi-collinear functional are under development. It requires the 4th order XC derivative. I just add an additional feature in case developing TDDFT hessian in the future. I guess 5th order in libxc is not needed for the moment.


Prepare API for getting reserved ports on peer

To enable Hub to see what ports are in use on peer, we need to implement relevant API
https://github.com/optdyn/hub/wiki/Port-Mapping-Requirements
https://github.com/optdyn/hub/issues/2891

Added ResourceHost.getReservedPorts() method


services.mysql: properly quote database.name

Motivation for this change
Address the quoting issues discussed on #5227.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
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)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review 33821"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Can someone please merge?

Thanks.

Thank you!


Expose logs of machine-controller-manager to end users

How to categorize this issue?

/area logging
/kind enhancement
/kind discussion
/priority 3
What would you like to be added:
As far as I see currently the machine-controller-manager logs are not exposed to the end users. Exposing them to the end users can make sense.
Why is this needed:
In multiple cases we see that end users cannot complete RCA on their side because they don't have access to the MCM logs. We see that in such cases, the MCM logs actually can reveal the root cause. End users often ask questions like "Why Node foo was replaced?", "Why a new Node was not able to join the cluster during given period of time?", etc. If end users have access to the MCM logs, then they will be able to answer such type of questions on their own.
Currently we also expose cloud-controller-manager logs and logs from CSI components - they are also components that interact with the cloud provider APIs.
/cc @vpnachev @prashanth26 @Kristian-ZH @vlvasilev
/cc @vlerenc I recall we were discussing this topic in the past. Any opinion from your side?

@ialidzhikov Indeed, it would be great to give the people access to the MCM and CA logs as they often raise questions like why a node was replaced or why scale-out/-in didn't happen, etc.
See also https://github.com/gardener/machine-controller-manager/issues/140.
So yes, ideally the Grafana dashboards should expose those logs (that we anyway have).

@ialidzhikov Indeed, it would be great to give the people access to the MCM and CA logs as they often raise questions like why a node was replaced or why scale-out/-in didn't happen, etc.
See also gardener/machine-controller-manager#140.
So yes, ideally the Grafana dashboards should expose those logs (that we anyway have).

I agree with this. I think CA logs are already exposed. However, yes exposing MCM logs also makes sense.

Yes, CA logs are already exposed.
About the MCM: @vlvasilev can you please do this?

I also suggest to add it only in Controlplane Logs Dashboard because the separated dashboards by container will be deleted soon.

I will do it tomorrow

Almost all provider extensions are now exposing the MCM logs.
Once https://github.com/gardener/gardener/pull/4387 is also merged, we can close this issue.

This task is now completed and I am closing this issue as all required PRs are merged.


lxml.etree.XMLSyntaxError

Hi,
I got an syntax error when I try to run the script the first time:
Traceback (most recent call last):
  File "./ews-fetch-calendar.py", line 163, in <module>
    root = etree.fromstring(data)
  File "src/lxml/lxml.etree.pyx", line 3213, in lxml.etree.fromstring (src/lxml/lxml.etree.c:79003)
  File "src/lxml/parser.pxi", line 1848, in lxml.etree._parseMemoryDocument (src/lxml/lxml.etree.c:118334)
  File "src/lxml/parser.pxi", line 1736, in lxml.etree._parseDoc (src/lxml/lxml.etree.c:117014)
  File "src/lxml/parser.pxi", line 1102, in lxml.etree._BaseParser._parseDoc (src/lxml/lxml.etree.c:111258)
  File "src/lxml/parser.pxi", line 595, in lxml.etree._ParserContext._handleParseResultDoc (src/lxml/lxml.etree.c:105102)
  File "src/lxml/parser.pxi", line 706, in lxml.etree._handleParseResult (src/lxml/lxml.etree.c:106810)
  File "src/lxml/parser.pxi", line 646, in lxml.etree._raiseParseError (src/lxml/lxml.etree.c:105956)
  File "<string>", line 0
lxml.etree.XMLSyntaxError

Can you provide the exact version numbers of the libraries used on your side so that I might come up with a virtualenv that uses your setup?
Thanks!

Hi,
are you sure you configured the host, path, etc. correctly? You get an XMLSyntaxError, which means the result from the webservice call cannot be processed.
There is a debug line in the script, which allows you to dump the response to the console, just uncomment line 2 and 3 and re-execute.
# Debug code
# print data
# exit(0)

You should then see the xml returned by the webservice. If you see e.g html or similar, you're talking to the wrong endpoint.
In case this really is a dependency issue:
I merged #2 yesterday. The  author claimed to have started with a clean virtualenv, so please check if requirements.txt does the trick for you.

I configured my settings in the config.cfg.
Before root = etree.fromstring(data) I get something in body but data is empty.
However, I have no clue, what I should put in path. So I took the default. Using an empty path leads to the same error. Maybe I need a config file with some more detailed example values?

Just check config.cfg.sample, for office 365 i used:
host=outlook.office365.com
path=/ews/Exchange.asmx

Turns out: when testing i saw the same stack trace you described, when an authentication error happens. In case you're using office356 you have to provide your email address as username (including the domain part).

Closed, because of missing feedback.

Sorry for the late feedback.
Error persists when changing username to: DOMAIN\\first.last or<EMAIL_ADDRESS>or<EMAIL_ADDRESS>or same without the DOMAIN.
We do have a bit of a chaos in our company. Sometimes usernames are first.last, sometimes f.last, sometimes with domain, sometimes without. Therefore, I have no clue what to use in the config file.
Never mind, I found a different library (exchangelib) which worked for me: https://github.com/novoid/exchange2org


[ERROR]  socket-mode:SocketModeClient:0 unable to parse incoming websocket message: Unexpected token U in JSON at position 0

Description
When using the bolt-js app in socketMode, I think the WS sometimes receives an undefined message, causing the app to crash.
What type of issue is this? (place an x in one of the [ ])

[x] bug
[ ] enhancement (feature request)
[ ] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Reproducible in:
package version: 3.11.2
node version: 16.13.0
OS version(s): Alpine Linux and MacOS Monterey (possible others)
Steps to reproduce:

Run the app with socketMode: true
Sometimes it crashes with the following error:
[ERROR]  socket-mode:SocketModeClient:0 unable to parse incoming websocket message: Unexpected token U in JSON at position 0

Expected result:
It does not crash
Actual result:
It crashed with
[ERROR]  socket-mode:SocketModeClient:0 unable to parse incoming websocket message: Unexpected token U in JSON at position 0
Attachments:

Hi @robinclaes, thanks for sharing this. Since this is an issue related to the underlying Socket Mode library side, let me transfer this issue to https://github.com/slackapi/node-slack-sdk before starting a discussion.


Indexing into arrays hoists empty array constants out of Jaxprs

Repro:
def test_fun(x):
  return x[0] + x[1] + x[2] + x[3]

Jaxpr:
{ lambda a b c d ; e.
  let f = lt 0 0
      g = add 0 4
      h = select f g 0
      i = convert_element_type[ new_dtype=int32
                                weak_type=False ] h
      j = broadcast_in_dim[ broadcast_dimensions=(  )
                            shape=(1,) ] i
      k = concatenate[ dimension=0 ] a j
      l = gather[ dimension_numbers=GatherDimensionNumbers(offset_dims=(), collapsed_slice_dims=(0,), start_index_map=(0,))
                  slice_sizes=(1,) ] e k
  [...]
}

where a, b, c, and d are empty int32 arrays - one per indexing operation: [array([], dtype=int32), array([], dtype=int32), array([], dtype=int32), array([], dtype=int32)]
In severe cases, thousands of these constants inflate the size of the unoptimized HLO and result in slow compilation. In code with higher-order functions, there is evidence that these constants and the associated lt,add, and select operations do not get optimized away.
Workarounds: jnp.take does not create empty constants and lax.slice results in even more compact code in situations where its semantics are applicable.

With #6416
In [1]: import jax

In [2]: jax.make_jaxpr(lambda x: x[2])(jax.numpy.arange(5))
WARNING:absl:No GPU/TPU found, falling back to CPU. (Set TF_CPP_MIN_LOG_LEVEL=0 and rerun for more info.)
Out[2]:
{ lambda  ; a.
  let b = lt 2 0
      c = add 2 5
      d = select b c 2
      e = broadcast_in_dim[ broadcast_dimensions=(  )
                            shape=(1,) ] d
      f = gather[ dimension_numbers=GatherDimensionNumbers(offset_dims=(), collapsed_slice_dims=(0,), start_index_map=(0,))
                  slice_sizes=(1,) ] a e
  in (f,) }

I am not completely confident this will fix your original problem, but I'm hopeful that it will. Please let me know!

This looks a lot better, thanks! We are now lowering directly to lax.index_in_dim to take advantage of the Slice XLA op.

That's an optimization we can make also, but I am yet to see evidence that it helps. Do you have an example where it matters?


Mutex token aware sharding initializer

Prevents data race when/if a schema update happens during an initialization.

I believe this addresses #94.

@mmatczuk  - One for you, It seems pretty safe to call the mutex here, and it stops the issues fine in my CI runs locally. I've got a lot of tests where I set up keyspaces, do a bunch of operations then blow away the keyspace so each test is idempotent. I doubt this will happen to anyone in the wild, and will have been an issue for a long while I suspect. If I re-run CI enough, tests will pass.


Fix delete count bug; add deleted files to stats; correct typos

Hi,
Thank you for this fantastic script. I was about to write something similar for my photo tagging app, but stumbled upon this and integrated it instead, saving me a lot of time.
I noticed a couple of issues while I was playing about with it and reviewing the code, which I fixed, namely: 1) the deleted image count was erroneously incremented and 2) a few typos.
I also added the deleted file information to the stats output - either just a count, or also with a list of the files deleted, depending upon whether the user had requested verbose logging. Tried to integrate that in the same way that the invalid files are reported, to preserve consistency.

Hi @UplandsDynamic,
Thanks a lot for opening the pull request and for your effort in making difPy better! These adjustments are very valuable. I'll include them in the next difPy release.
Again, thanks and all the best,
Elise

My pleasure, @elisemercury. The effort in making those small changes was as nothing compared to the time this script saved me in not having to code something similar from scratch. All hail open source!
Let me know if you'd like me to update the README to include a bit about the deletion information in the stats output (I didn't do it before in case you decided against merging that part).
Cheers,
Dan

Hi @UplandsDynamic,
Your pull request and adjustments have been merged and added to the new v3.0.9 release. I also updated the README. Thanks again for your contributions!
Cheers,
Elise

Hi @elisemercury,
That's great! Thank you for merging to main so quickly. I noticed your release of the associated web app too - very slick.
I'm just now having a look at that remaining outstanding issue on your repo, regarding implementation of a preliminary file check, for common image file formats based on file extensions. I'll try to get that done.
Cheers,
Dan

Hi @UplandsDynamic,
Thank you so much - that is great! Let's move the conversation to the open issue #60 and I'll share my thoughts around it with you there!
All the best,
Elise


Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[ ] iOS
[*] Android
[ ] UWP
[ ] .NET Standard

Version of Library
6.2.6
Version of OS(s) listed above with issue
Android 6.0.1
Steps to Reproduce
Unfortunately is a bug I cannot reproduce, but I have a full stacktrace at least.
Expected Behavior
No crash
Actual Behavior
Library crash on StopScan
I attach the full stacktrace I receveid from my crash reporting system.
In my app the user can launch a scan and i put this three line of code before launch it:
if (CrossBleAdapter.Current.IsScanning) //maybe the user already launch a scan
            {
                CrossBleAdapter.Current.StopScan();
            }

Then I launch a scan (I use scanextra)
Sometimes, but I cannot reproduce the bug on my devices, this exception is raised:
Java.Lang.IllegalArgumentException: callback cannot be null
The full stacktrace:
Stacktrace.txt
Is it a bug in a "old" version of Android?
P.S. I have more info about #359 can you unlock it? I understand what is the problem, it's not a library bug, but rather a not-so-well documented behavior of Android with not paired bluetooth devices.

Feel free to send a PR with a fix if you want.  All of my efforts have moved to the other repo as listed in the readme.

Hi,
Unfortunately I do not have the knowledge about bluetooth to create a proper fix and, as I said, I cannot re-create the problem.
P.S.
Can you re-open #359 ? I will put the info I got and close the issue.

This isn't something I can look into without a proper test case.  I would suggest wrapping a try/catch around the StopScan for now.
The other issue is unlocked


Translate Class and Style

Translate Class and Style

@matrunchyk I can't assign this task to me. Maybe you should add me as a member in project settings?


Implement the input side of the Lincoln Writer

Unit 66, the Lincoln Writer output, is implemented.  But we also need to implement unit 65, the input side.

PR #105 implements the display of a keyboard in the web simulator, but pressing the keys on it doesn't generate input to the simulated machine yet.


Fixes broken help menu.  Addresses #2081.

Addresses #2081.
Currently if one pip installs toil and runs the command toil --help, toil breaks.  This PR fixes this.

Jenkins, test this please.

Flaky test:

src.toil.test.provisioners.aws.awsProvisionerTest.AWSAutoscaleTestMultipleNodeTypes.testAutoScale
http://jenkins.cgcloud.info/job/toil-pull-request-integration-tests/2010

m.doc searches through all of the files in the directory for their docstrings.  It returns a string or None.  The method always uses .strip() so if it returns None, you get a type error.  This fix added the missing docstring, and also forced m.doc as a string, even if it is None, so that the help menu will show up even if there's no docstring in place for that file (just showing the string 'None' instead on the help menu).


Merge pull request #795 from TantoluwaHeritageA/main

added right links to my profile

updated profile with right links


[Bug]: Some tabs of the debugger pane not present in split mode

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Tabs such as Errors, Logs of the debugger are not present in split mode.
Steps To Reproduce

Go to an app.
Create a query/JS Object.
Switch between split mode & normal mode.

Expected: All tabs in the debugger should be present in both split & normal mode.
Public Sample App
No response
Environment
Production
Severity
Medium (Frustrating UX)
Issue video log
https://jam.dev/c/e798eea9-bb27-4607-9b1c-6a6befa9aecc
Version
Cloud

The other tabs are available when you click the error count debugger CTA on the bottom right.

@hetunandu it sometimes gets confusing as to why we see only two tabs in split mode & four in normal. Also if you do not have any widget on the canvas, the errors that pop up when you click the error count debugger CTA seem out of place.

Also for some operations we see duplicate logs


Tests fixed

There were errors in the imports of the tests, which are independent from the ones in app.module.ts. They are now fixed and passing.

I do not see any problem, but I'd wait for the reviews of the other members before merging it, just in case. Good work.

Pa alante 💃🏼


Missing fault and fan-level for jsq2w in HA ui

Device model / 设备型号
humidifier.deerma_jsq2w_42c5_humidifier
Component version / 插件版本
0.7.13
HA core version / HA版本
2023.11.2
Integrated mode / 集成方式
Token
The problem / 问题详情
Missing fault and fan-level for jsq2w in HA ui (only modes)
Fan on/off — but it's wrong, fan have 4 modes

Entity attributes / 实体属性
preset_modes
Home Assistant Logs / 系统日志
No response

Also would be great to have empty water tank sensor as was in the previous model.

Please see:

water shortage fault issue https://github.com/al-one/hass-xiaomi-miot/issues/1021
available modes issue https://github.com/al-one/hass-xiaomi-miot/issues/1421


Hcap 66 update api to postgres

So much clean up in this PR! The pg lib being used looks really slick.


add unique creation_id for the 4M variant of the T-Display ESP32

It is needed for the unique version of CircuitPython for this variant of this board. The "regular" 16M variant already supported by CircuitPython has ID 0x0032_0002 so the smaller 4M flash chip could use 0x0032_0004.

The related pull request on CircuitPython is https://github.com/adafruit/circuitpython/pull/8787


FIX: SET Command Inconsistency

The above was not same in the Current Dice db implementation , i have fixed it, kindly verify once and let me know if there is something that is need to be change and updated too.
It makes it consistent with current DOCs and Redis Implementation.
#786
cc @apoorvyadav1111

Please add testsbto validate these changes

Sure will do....

@lucifercr07 added tests that were missing and now it is consistent with the DICE DB Sets docs too and Also with redis.


cv2 error

Hello again, I've updated to the latest ALAuto version with SED removed. When trying to run the script with the latest ADB platform-tools 1.0.41 version 29.0.4. I get this output.
[2019-09-29 17:26:21] Initializing config module
[2019-09-29 17:26:21] Validating config
[2019-09-29 17:26:21] Starting ALAuto!
* daemon not running; starting now at tcp:5037
* daemon started successfully
[2019-09-29 17:26:36] Sucessfully connected to the service.
error: more than one device/emulator
Traceback (most recent call last):
  File "ALAuto.py", line 143, in <module>
    Utils.update_screen()
  File "G:\AzurLane\ALAuto-master\util\utils.py", line 79, in update_screen
    screen = cv2.imdecode(numpy.fromstring(Adb.exec_out('screencap -p'), dtype=numpy.uint8), 0)
cv2.error: OpenCV(3.4.4) C:\projects\opencv-python\opencv\modules\imgcodecs\src\loadsave.cpp:750: error: (-215:Assertion failed) !buf.empty() && buf.isContinuous() in function 'cv::imdecode_'```

Any insights on what I may have setup incorrectly?

error: more than one device/emulator
Unlike Nox, most other emulators get automatically connected to the adb server, therefore making the connection made by the bot redundant.
My guess is that after updating to the latest platform-tools your emulator started doing that.
Try commenting this line and let me know if it works as intended.

That was it! It was definitely related to the ADB version change but I didn't understand the reason. Thank you for the response, I'm back in business!

Oops it threw a similar error after combat victory.
error: more than one device/emulator
[2019-09-29 23:20:06] Moving towards objective.
[2019-09-29 23:20:16] Starting combat.
error: more than one device/emulator
Traceback (most recent call last):
  File "ALAuto.py", line 156, in <module>
    script.run_combat_cycle()
  File "ALAuto.py", line 56, in run_combat_cycle
    result = self.modules['combat'].combat_logic_wrapper()
  File "G:\AzurLane\ALAuto-master\modules\combat.py", line 74, in combat_logic_wrapper
    if not self.clear_map():
  File "G:\AzurLane\ALAuto-master\modules\combat.py", line 281, in clear_map
    self.battle_handler()
  File "G:\AzurLane\ALAuto-master\modules\combat.py", line 105, in battle_handler
    Utils.update_screen()
  File "G:\AzurLane\ALAuto-master\util\utils.py", line 79, in update_screen
    screen = cv2.imdecode(numpy.fromstring(Adb.exec_out('screencap -p'), dtype=numpy.uint8), 0)
cv2.error: OpenCV(3.4.4) C:\projects\opencv-python\opencv\modules\imgcodecs\src\loadsave.cpp:750: error: (-215:Assertion failed) !buf.empty() && buf.isContinuous() in function 'cv::imdecode_'```

It is really weird, I'd suggest you sticking to the old adb and sed. It should work just as good.
I added an argument to enable sed on this https://github.com/Egoistically/ALAuto/commit/b36c24964269b09f9ab6d9f19fdfbdc2b6aef284 commit.

No problem at all, sleep definitely comes first. I will try the commit and can easily revert back to the old ADB and SED version which works just as well. Thank you!

-l is working great with the latest commit and SED. Thanks again!


Question about the new changes

Hello, I have a question, if anyone can help me I will be very happy. I have an application on zephyr, that downloads an image and saves it in flash area 1, and before the last modifications I just rebooted the board and it already comes out running the downloaded image. Now, when I rebooted happens that error bellow:
[00:00:00.004,948] <inf> mcuboot: Starting bootloader
[00:00:00.010,967] <inf> mcuboot: Image 0: magic=good, copy_done=0x3, image_ok=0x1
[00:00:00.018,793] <inf> mcuboot: Scratch: magic=unset, copy_done=0x5b, image_ok=0x3
[00:00:00.016,952] <inf> mcuboot: Boot source: slot 0
[00:00:00.014,445] <inf> mcuboot: Swap type: test
***** BUS FAULT *****
  Imprecise data bus error
***** Hardware exception *****
Current thread ID = 0x00000000
Faulting instruction address = 0x3ebe

What change should I make so that the board keeps restarting in flash area 1 ??? Thank you

Are you running zephyr and mcuboot master? (you should probably sync both together). In case you are, is it possible to find out what change started causing this? (git bisectmight be useful). And check what's located at 0x3ebe...

Hello, I found where started the error on mcuboot. The error started here on Zephyr:
commit dc0713a706e7e2898c172c6c0965b1b784859841
Author: Andy Ross<EMAIL_ADDRESS>Date:   Thu Jul 5 12:50:41 2018 -0700

    kernel: Cleanup. Remove redundant test when calling _Swap()

    _Swap() must already handle the case where _get_next_ready_thread() is
    the same as _current.

    Signed-off-by: Andy Ross<EMAIL_ADDRESS>

Unfortunately, I don't know how to solve it.

This looks like a recently merged change in the scheduler; mcuboot runs with multithreading disabled, so could be a side-effect. @nvlsianpu any ideas?

No Idea - unfortunately I don't have time to investigate this now.
cc @carlescufi

I'll investigate. The zip of Zephyr isn't booting into MCUboot at all for me, although I'm not sure if that is a logging change or this problem.

The tip of Zephyr isn't booting into MCUboot at all for me

For me neither, I believe this is https://github.com/zephyrproject-rtos/zephyr/issues/13249


Bump numpy to 1.23.4

Previously, NumPy was pinned to an old version on Windows to avoid a bug in a Windows update.  However, that bug has now been fixed and that old NumPy version is now incompatible with the version of Python now in the Windows store (Python 3.10).  The old version also has known security vulnerabilities, giving one final reason to update.
NumPy 1.20 dropped support for Python 3.6, and NumPy 1.22 dropped support for Python 3.7.  So, we use NumPy 1.19.5 for Python < 3.8 and latest NumPy for everything else.

Finally the tests are green.

The build here is 3.6 and 3.9, is it worth adding 3.10 or 3.11?

Seems like a good shout.  We should probably also add 3.7 and 3.8 because they're the boundary at which the numpy version changes and they're what'll break if I've got the versions wrong.
I would prefer to avoid testing tons of different Python versions; it seems inefficient and clutters up the merge box.  Can you remember the rationale of choosing 3.6 and 3.9?  I think 3.9 was the latest version at the time, so possibly 3.6 was the version that RR uses and 3.9 (i.e. latest) was what CLI users would probably have installed?  By that logic, we should do something like 3.6, 3.8 and 3.11... what do you reckon?

Yes I think it was a balance of the number of jobs with coverage of versions.
3.6, 3.8 and 3.11 sounds fine to me.


[DEV-2413] adapt mails

Release Checklist
Pre-Release

[ ] Check migrations

No database related infos (sqldb-xxx)
Impact on GS (new/removed columns)

[ ] Check for linter errors (in PR)
[ ] Test basic user operations (on DFX services)

Login/logout
Buy/sell payment request
KYC page

Post-Release

Test basic user operations
Monitor application insights log

Add migration
Wait for DEV-2459 and change url

add buyCrypto/bankTx missing Route Mail


Transform Error

import React from 'react';
import { StyleSheet, Text, View, Dimensions } from 'react-native';
import SearchHeader from 'react-native-search-header';
const DEVICE_WIDTH = Dimensions.get(window).width;
export default class App extends React.Component {
render() {
return (

Open up App.js to start working on your app!

);
}
}
const styles = StyleSheet.create({
container: {
flex: 1,
justifyContent: 'flex-start',
alignItems: 'center',
backgroundColor: '#f5fcff'
},
status: {
zIndex: 10,
elevation: 2,
width: DEVICE_WIDTH,
height: 21,
backgroundColor: '#0097a7'
},
header: {
justifyContent: 'center',
alignItems: 'center',
width: DEVICE_WIDTH,
height: 56,
marginBottom: 6,
backgroundColor: '#00bcd4'
},
label: {
flexGrow: 1,
fontSize: 20,
fontWeight: 600,
textAlign: left,
marginVertical: 8,
paddingVertical: 3,
color: #f5fcff,
backgroundColor: transparent
},
button: {
justifyContent: 'center',
alignItems: 'center',
width: 130,
height: 40,
marginTop: 40,
borderRadius: 2,
backgroundColor: #ff5722
}
});

Are you using this package with the latest react native version 0.50.3?  Looks like a babelrc issue.

I'm facing this issue as well while my dependencies are perfectly aligned. Only way I could solve it is by adding babel-preset-react and babel-preset-env to the main project which should of course not be necessary.

I'll take a look and fix this issue in the next update. Thanks.

@tuantle thanks for the changes, I can confirm that the transform error is gone..... BUT... your deep merge introduction is failing! You cannot override the styles at the moment.

Thanks @tuantle you can close this issue in my opinion.


Issue while compiling the application

I am getting the following error when I run "mvn clean install -X"
[INFO] Axon Bank .......................................... SUCCESS [  0.270 s]
[INFO] Axon Bank - Core API ............................... FAILURE [  1.596 s]
[INFO] Axon Bank - Core ................................... SKIPPED
[INFO] Axon Bank - Query .................................. SKIPPED
[INFO] Axon Bank - Web .................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  2.212 s
[INFO] Finished at: 2020-09-09T14:25:11Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project axon-bank-core-api: Fatal error compiling: java.lang.ExceptionInInitializerError: com.sun.tools.javac.code.TypeTags -> [Help 1]
[ERROR]

Thanks for filing this concern with us @nikhilgoenkatech. Without knowing your specific set up, I want to state that this project has not been updated for over three years now. This makes it a project against Axon Framework 3.x (whilst we're currently on Axon Framework 4.4.2) and a Java 8 workable project only too.
So from your end, you can verify you are using Java 8 when building the project (hoping that solves the problem of course).
From our end, I want to state chances are high this project will be moved to a different repository prior to receiving an update here, if it isn't already superseded by other sample projects out there. As such, there is currently no priority on fixing this sample. To reflect this I've put your issue on under discussion with priority 4, noting we will eventually discuss this and pick this up.

Closing this issue due to inactivity.
Furthermore, this sample project this being archived, so we're not planning any active development on this anymore.
If you're looking for a sample project, I recommend the GiftCard or Hotel applications.


24h statistics using webSocket?

Is there any way to get the 24Statistics using a websocket? I don't want to use Candlestick.Interval_DAILY because that returns the statistics from 3:00 a.m. I wan't the statistics of the last 24 hours as they are shown on the binance website.

client.getAll24HrPriceStatistics();

No, you need to use the REST API (client.getAll24HrPriceStatistics();).


horizontal thumb appear when there is no need

If clientWidth and scrollWidth are 0, then width is calculated as NaN, which will break next condition and thumb will appear for full width

Great PR Mahesh! Hope it gets approved soon.

Waiting for this! Can this be included into a release?


last execution problem

Hello, I am a beginner, where is the last EXE and how is it executed, can you tell me

你好我是学生，打钱！

check the demo is self-explanatory , the cipher,key of the EXE (created by aes.py script ) is hosted on web server, run the exe to get the cipher,key and everything willl work fine

hello @TheD1rkMtr ,
Can you check if the script is still working.
i am getting this error.

no sessions is created on kali after this


cmd/verify: allow pass by url for signature flag

Description
Currently, -signature flag only supports filepath. Would it be good practice to pass a URL for this flag? i.e., GitHub download link:
$ cosign verify-blob -key https://raw.githubusercontent.com/foo/bar/master/cosign.key -signature https://github.com/foo/bar/releases/download/v0.1.0/bar_0.1.0_Darwin-x86_64.sig

SGTM


Add CI

Enable travis-ci for continuous integration.
This requires adding a .travis.yml file, and including all the necessary local-build scripts (e.g. locally-building xtt).
The main blocker for this, currently, is getting a working version of Boost on travis.

We are trying to enable testing for xtt-cpp which uses Boost 1.66.0 which requires clang >=5 or gcc >=6 and uses C++14 with CMake 3.11.4 or greater. This is proving to be a difficult task because Travis has very little or extremely outdated support for C and C++ and their libraries.
Things we fixed and issues we ran into when attempting to fix:
-Changed language to C++ not C
-Added NIST256 to the AMCL curves used to account for ECDSA changes
-Installed CMake 3.11.4 since the version already downloaded on Travis CI is very old and does not support Boost 1.66.0 which we need. Also appended the /.travis directory to the CMAKE_MODULE_PATH so that FindBoost.cmake could be found by find_package().
-Tried to add Boost with libboost-all-dev
--> Travis continued to use boost 1.54
-Tried to use conan to install Boost
--> Used clang 5.0 and setting for C++14 to be used
---->Tried to update clang but later realized that should not be necessary for C++14 support. Build 73 is able to do everything except use the standard library for experimental/optional, signaling that Travis or conan is not properly using C++14.
--> Used and updated gcc to 6.4 within Travis CI using C++14
---->When we run conan install boost/1.66.0@conan/stable there are 2 dependencies: bzip2 and zlib. We encounter errors trying to build zlib from source (which is necessary because zlib does not exist for a compiler.version of 6.4).
---->Build 113 is able to execute conan install properly, but does not update both gcc and g++ versions therefore receiving a mismatch error in the cmake command. Tried to fix this mismatch with an update of both gcc and g++ which asks us to build zlib from source.
---->Attempted to separate zlib and install before gcc was updated, and while Travis showed that zlib was already in the cache it would assert that zlib was missing for the new compiler.version and asked to install zlib from source.
Error produced by zlib built from source: ERROR: Error downloading file https://zlib.net/zlib-1.2.11.tar.gz: 'HTTPSConnectionPool(host='zlib.net', port=443): Max retries exceeded with url: /zlib-1.2.11.tar.gz (Caused by SSLError(CertificateError("hostname 'zlib.net' doesn't match either of 'adler.madler.net', 'adler.me', 'autodiscover.adler.me', 'autodiscover.saintj.net', 'cpanel.adler.me', 'cpanel.saintj.net', 'mail.adler.me', 'mail.saintj.net', 'saintj.madler.net', 'saintj.net', 'webdisk.adler.me', 'webdisk.saintj.net', 'webmail.adler.me', 'webmail.saintj.net', 'www.adler.madler.net', 'www.adler.me', 'www.saintj.madler.net', 'www.saintj.net'",),))'
-Tried to use other conan packages besides Conan-center as to avoid zlib
-->When trying to conan install from anywhere but conan-center (adding remote and adjusting settings correctly), we received: ERROR: Failed requirement 'boost_asio/1.66.0@bincrafters/stable' from 'PROJECT'
We are shelving this issue for the moment and moving forward may try to use with another CI that has better support for C and C++.

Just FYI, you can run your builds in a docker container on Travis and avoid all these issues.On Aug 3, 2018 12:35, kathrynfejer<EMAIL_ADDRESS>wrote:We are trying to enable testing for xtt-cpp which uses Boost 1.66.0 which requires clang >=5 or gcc >=6 and uses C++14 with CMake 3.11.4 or greater. This is proving to be a difficult task because Travis has very little or extremely outdated support for C and C++ and their libraries.
Things we fixed and issues we ran into when attempting to fix:
-Changed language to C++ not C
-Added NIST256 to the AMCL curves used to account for ECDSA changes
-Installed CMake 3.11.4 since the version already downloaded on Travis CI is very old and does not support Boost 1.66.0 which we need. Also appended the /.travis directory to the CMAKE_MODULE_PATH so that FindBoost.cmake could be found by find_package().
-Tried to add Boost with libboost-all-dev
--> Travis continued to use boost 1.54
-Tried to use conan to install Boost
--> Used clang 5.0 and setting for C++14 to be used
---->Tried to update clang but later realized that should not be necessary for C++14 support. Build 73 is able to do everything except use the standard library for experimental/optional, signaling that Travis or conan is not properly using C++14.
--> Used and updated gcc to 6.4 within Travis CI using C++14
---->When we run conan install boost/1.66.0@conan/stable there are 2 dependencies: bzip2 and zlib. We encounter errors trying to build zlib from source (which is necessary because zlib does not exist for a compiler.version of 6.4).
---->Build 113 is able to execute conan install properly, but does not update both gcc and g++ versions therefore receiving a mismatch error in the cmake command. Tried to fix this mismatch with an update of both gcc and g++ which asks us to build zlib from source.
---->Attempted to separate zlib and install before gcc was updated, and while Travis showed that zlib was already in the cache it would assert that zlib was missing for the new compiler.version and asked to install zlib from source.
Error produced by zlib built from source: ERROR: Error downloading file https://zlib.net/zlib-1.2.11.tar.gz: 'HTTPSConnectionPool(host='zlib.net', port=443): Max retries exceeded with url: /zlib-1.2.11.tar.gz (Caused by SSLError(CertificateError("hostname 'zlib.net' doesn't match either of 'adler.madler.net', 'adler.me', 'autodiscover.adler.me', 'autodiscover.saintj.net', 'cpanel.adler.me', 'cpanel.saintj.net', 'mail.adler.me', 'mail.saintj.net', 'saintj.madler.net', 'saintj.net', 'webdisk.adler.me', 'webdisk.saintj.net', 'webmail.adler.me', 'webmail.saintj.net', 'www.adler.madler.net', 'www.adler.me', 'www.saintj.madler.net', 'www.saintj.net'",),))'
-Tried to use other conan packages besides Conan-center as to avoid zlib
-->When trying to conan install from anywhere but conan-center (adding remote and adjusting settings correctly), we received: ERROR: Failed requirement 'boost_asio/1.66.0@bincrafters/stable' from 'PROJECT'
We are shelving this issue for the moment and moving forward may try to use with another CI that has better support for C and C++.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

Ha, well, that's a mentoring failure on my part. Sorry, Kathryn, that I led you down the wrong path.


docs：update the card title and website logo

@ChenlingLu Use this new png for favicon, ref https://github.com/pingcap/ossinsight/issues/406


update ImportC introduction

As ImportC has evolved, so should the documentation. This also adds "Associated C Compiler" to the glossary where it can be linked to.

Isn't it great that CyberShadow/DAutoTest fails with no clue in the voluminous log file. I suppose I should just submit documentation PRs that are no longer than one line.

Isn't it great that CyberShadow/DAutoTest fails with no clue in the voluminous log file. I suppose I should just submit documentation PRs that are no longer than one line.

Searching for trailing whitespace
Searching for tabs
./glossary.dd:10:	command line switch $(DDSUBLINK dmd, switch-m32mscoff, $(TT -m32mscoff)).

Because DAutoTest doesn't say where the error is, I split off the changes to glossary.dd to https://github.com/dlang/dlang.org/pull/3329

@maxhaton thank you. I tried grepping the log file for glossary but did not see that line. I don't know why.

Here is the run: https://dtest.dlang.io/results/d7d2242f78254a8427c43eaffc60c1c4cd91c131/2662cc8b8a32eb393ca13912dc78b78a112803e3/
The problem here is that the style checker doesn't actually produce any error messages. The relevant log lines are:
Searching for tabs
./glossary.dd:10:	command line switch $(DDSUBLINK dmd, switch-m32mscoff, $(TT -m32mscoff)).
posix.mak:812: recipe for target 'test' failed

You have to deduce that the problem is a stray tab character from the Searching for tabs line yourself, and is easy to miss if you're looking for the word "Error" or such.

@CyberShadow thanks for your help!


☂ linter: eslint-plugin-unicorn  (recommended)

https://github.com/sindresorhus/eslint-plugin-unicorn (recommended)
Recommended rules

[ ] better-regex
[x] catch-error-name https://github.com/web-infra-dev/oxc/pull/984
[ ] consistent-destructuring
[ ] consistent-function-scoping
[ ] empty-brace-spaces
[x] error-message https://github.com/web-infra-dev/oxc/pull/992
[ ] escape-case
[ ] expiring-todo-comments
[ ] explicit-length-check
[x] filename-case https://github.com/web-infra-dev/oxc/pull/978
[ ] import-style
[ ] new-for-builtins
[ ] no-abusive-eslint-disable
[ ] no-array-callback-reference
[ ] no-array-for-each
[ ] no-array-method-this-argument
[ ] no-array-push-push
[ ] no-array-reduce
[ ] no-await-expression-member
[x] no-console-spaces https://github.com/web-infra-dev/oxc/pull/991
[ ] no-document-cookie
[ ] no-empty-file
[ ] no-for-loop
[ ] no-hex-escape
[x] no-instanceof-array
[ ] no-invalid-remove-event-listener
[ ] no-lonely-if
[ ] no-negated-condition
[ ] no-nested-ternary
[ ] no-new-array
[ ] no-new-buffer
[ ] no-null
[ ] no-object-as-default-parameter
[ ] no-process-exit
[ ] no-static-only-class
[ ] no-thenable
[ ] no-this-assignment
[ ] no-typeof-undefined
[x] no-unnecessary-await
[ ] no-unreadable-array-destructuring
[ ] no-unreadable-iife
[ ] no-useless-fallback-in-spread
[ ] no-useless-length-check
[ ] no-useless-promise-resolve-reject
[ ] no-useless-spread
[ ] no-useless-switch-case
[ ] no-useless-undefined
[ ] no-zero-fractions
[ ] number-literal-case
[ ] numeric-separators-style
[ ] prefer-add-event-listener
[ ] prefer-array-find
[ ] prefer-array-flat
[x] prefer-array-flat-map https://github.com/web-infra-dev/oxc/pull/997
[ ] prefer-array-index-of
[ ] prefer-array-some
[ ] prefer-at
[ ] prefer-blob-reading-methods
[ ] prefer-code-point
[ ] prefer-date-now
[ ] prefer-default-parameters
[ ] prefer-dom-node-append
[ ] prefer-dom-node-dataset
[ ] prefer-dom-node-remove
[ ] prefer-dom-node-text-content
[ ] prefer-event-target
[ ] prefer-export-from
[ ] prefer-includes
[ ] prefer-keyboard-event-key
[ ] prefer-logical-operator-over-ternary
[ ] prefer-math-trunc
[ ] prefer-modern-dom-apis
[ ] prefer-modern-math-apis
[ ] prefer-module
[ ] prefer-native-coercion-functions
[ ] prefer-negative-index
[ ] prefer-node-protocol
[ ] prefer-number-properties
[ ] prefer-object-from-entries
[ ] prefer-optional-catch-binding
[ ] prefer-prototype-methods
[ ] prefer-query-selector
[ ] prefer-reflect-apply
[ ] prefer-regexp-test
[ ] prefer-set-has
[ ] prefer-set-size
[ ] prefer-spread
[ ] prefer-string-replace-all
[ ] prefer-string-slice
[ ] prefer-string-starts-ends-with
[ ] prefer-string-trim-start-end
[ ] prefer-switch
[ ] prefer-ternary
[ ] prefer-top-level-await
[ ] prefer-type-error
[ ] prevent-abbreviations
[ ] relative-url-style
[ ] require-array-join-separator
[ ] require-number-to-fixed-digits-argument
[ ] switch-case-braces
[ ] template-indent
[ ] text-encoding-identifier-case
[x] throw-new-error https://github.com/web-infra-dev/oxc/pull/1005

I need https://github.com/sindresorhus/eslint-plugin-unicorn/blob/main/docs/rules/filename-case.md for Rspack.

Recommended rules

[ ] better-regex
[ ] catch-error-name
[ ] consistent-destructuring
[ ] consistent-function-scoping
[ ] empty-brace-spaces
[ ] error-message
[ ] escape-case
[ ] expiring-todo-comments
[ ] explicit-length-check
[ ] filename-case
[ ] import-style
[ ] new-for-builtins
[ ] no-abusive-eslint-disable
[ ] no-array-callback-reference
[ ] no-array-for-each
[ ] no-array-method-this-argument
[ ] no-array-push-push
[ ] no-array-reduce
[ ] no-await-expression-member
[ ] no-console-spaces
[ ] no-document-cookie
[ ] no-empty-file
[ ] no-for-loop
[ ] no-hex-escape
[x] no-instanceof-array
[ ] no-invalid-remove-event-listener
[ ] no-lonely-if
[ ] no-negated-condition
[ ] no-nested-ternary
[ ] no-new-array
[ ] no-new-buffer
[ ] no-null
[ ] no-object-as-default-parameter
[ ] no-process-exit
[ ] no-static-only-class
[ ] no-thenable
[ ] no-this-assignment
[ ] no-typeof-undefined
[ ] no-unnecessary-await
[ ] no-unreadable-array-destructuring
[ ] no-unreadable-iife
[ ] no-useless-fallback-in-spread
[ ] no-useless-length-check
[ ] no-useless-promise-resolve-reject
[ ] no-useless-spread
[ ] no-useless-switch-case
[ ] no-useless-undefined
[ ] no-zero-fractions
[ ] number-literal-case
[ ] numeric-separators-style
[ ] prefer-add-event-listener
[ ] prefer-array-find
[ ] prefer-array-flat
[ ] prefer-array-flat-map
[ ] prefer-array-index-of
[ ] prefer-array-some
[ ] prefer-at
[ ] prefer-blob-reading-methods
[ ] prefer-code-point
[ ] prefer-date-now
[ ] prefer-default-parameters
[ ] prefer-dom-node-append
[ ] prefer-dom-node-dataset
[ ] prefer-dom-node-remove
[ ] prefer-dom-node-text-content
[ ] prefer-event-target
[ ] prefer-export-from
[ ] prefer-includes
[ ] prefer-keyboard-event-key
[ ] prefer-logical-operator-over-ternary
[ ] prefer-math-trunc
[ ] prefer-modern-dom-apis
[ ] prefer-modern-math-apis
[ ] prefer-module
[ ] prefer-native-coercion-functions
[ ] prefer-negative-index
[ ] prefer-node-protocol
[ ] prefer-number-properties
[ ] prefer-object-from-entries
[ ] prefer-optional-catch-binding
[ ] prefer-prototype-methods
[ ] prefer-query-selector
[ ] prefer-reflect-apply
[ ] prefer-regexp-test
[ ] prefer-set-has
[ ] prefer-set-size
[ ] prefer-spread
[ ] prefer-string-replace-all
[ ] prefer-string-slice
[ ] prefer-string-starts-ends-with
[ ] prefer-string-trim-start-end
[ ] prefer-switch
[ ] prefer-ternary
[ ] prefer-top-level-await
[ ] prefer-type-error
[ ] prevent-abbreviations
[ ] relative-url-style
[ ] require-array-join-separator
[ ] require-number-to-fixed-digits-argument
[ ] switch-case-braces
[ ] template-indent
[ ] text-encoding-identifier-case
[ ] throw-new-error

There are some convention / style rules, which should be omitted from the list. We should aim for correctness rules.

@Boshen
we can check off
catch-error-name #984
error-message #992
filename-case #978
no-console-spaces #991
prefer-array-flat-map #997
throw-new-error #1005

@camc314 You are free to edit it, unless your triage permission disallows.

@camc314 You are free to edit it, unless your triage permission disallows.

yeah i can't edit unfortunatly

@Boshen
Those are now done :)
text-encoding-identifier-case https://github.com/web-infra-dev/oxc/pull/1051
switch-case-braces https://github.com/web-infra-dev/oxc/pull/1054
require-number-to-fixed-digits-argument https://github.com/web-infra-dev/oxc/pull/1073

FYI I'm working on numeric-separators-style in #1490

eslint-plugin-unicorn(explicit-length-check): Use .size > 0

@NikitaIT Can you create an separate issue and provide more context?

@Boshen
In this PR, unicorn/prefer-spread rule was migrated to eslint:prefer-spread.
So should we update status of unicorn/prefer-spread? (It seems to be not implemented status)


Bump version

Hi!
Can you please bump version of the library, in order to have this functionality from npm package.
Thank you

@aksonov ?

Sorry, didn't wrote, but i've done it at that day :)

@aksonov thx!
I will close the issue


lsc -n produces deprecation warning

The option customFds used by child_process.spawn is deprecated.
$ ./bin/lsc -e "0" -n [node-args...]

There is also a follow-up issue because everything after -n is parsed as node-args, you can't pass a file name to lsc when using -n. One of these should be possible:
$ ./bin/lsc -n="--harmony" test/generators.ls
$ ./bin/lsc -n --harmony -- test/generators.ls

Closed as original issue was fixed, follow-up should be new issue.


TensorFlow.TFException: 'Invalid GraphDef'

Describe the bug
I took your example from README.MD and pasted it in and got a few errors and made a few modifications to make it go away. I can't seem to get it to work so here is the code. This is the image I am trying to feed it https://www.google.com/search?q=dogs&newwindow=1&source=lnms&tbm=isch&sa=X&ved=0ahUKEwjp2YCZzeThAhXnk4sKHa_cB2oQ_AUIDigB&biw=1284&bih=699#imgrc=GK40Gyy6hLCFvM:
Link to project https://mega.nz/#!66J0yYAQ!kYW2z2-hQS-ym3nynQ9xMM_rr40tqNym6YOH3y5zwSI
using System;
using System.IO;
using System.Windows.Forms;
using TensorFlow;

namespace SharpNeatTest
{
    public partial class FormMain : Form
    {
        public FormMain()
        {
            InitializeComponent();
        }

        private void Button1_Click(object sender, EventArgs e)
        {
            using (var graph = new TFGraph())
            {
                graph.Import(File.ReadAllBytes("test.jpg")); // TensorFlow.TFException: 'Invalid GraphDef'
                var session = new TFSession(graph);
                var runner = session.GetRunner();
                TFTensor tensor = null;
                runner.AddInput(graph["input"][0], tensor);
                runner.Fetch(graph["output"][0]);

                var output = runner.Run();

                // Fetch the results from output:
                TFTensor result = output[0];
            }
        }
    }
}

To Reproduce
Use the Debug mode on x64 CPU.
Load the code.
Debug. Done.
That was all I did.
Expected behavior
To run without errors?
Screenshots
I don't think screenshots are required here.
Desktop (please complete the following information):

OS: Windows 10 Version 1809 (OS Build 17763.437)
Browser: Firefox Quantum 66.0.3

Smartphone (please complete the following information):
Noy using a phone for this
Additional context
Not that I can think of

Replace .jpg with your ML Model (.pb file). Remember that you are using frozen weights for that model.
I also had the same problem. I followed https://github.com/migueldeicaza/TensorFlowSharp/issues/374#issuecomment-496353019 and this resolved my problem.

Hi there,
I have the same issue, here is my code:
tf.compat.v1.disable_eager_execution();  var modelPath = "emotion_detection_model.pb";  var buffer = System.IO.File.ReadAllBytes(modelPath);  var graph = tf.Graph().as_default();  graph.Import(buffer);
I get TensorFlow.TFException: 'Invalid GraphDef'. I tested emotion_detection_model.pb in Python app and it's fine so the prooblem is not in model.


package: Add --exclude option to exclude components from being started.

Description

When developing / testing certain components which provide a live reload debug server, other CLP components also need to be started for functionality verifications. Previously, developers have been starting the whole CLP package and later stopping the component(s) to be debugged, to avoid resource (e.g. TCP host + port) conflicts. The approach works but has proven to be inconvenience and prone to manual errors. This PR:

Add --exclude option to exclude components from being started.

Validation performed

Built the package.cd <clp-root>
task

Started the package, excluding components webui and log_viewer_webui.cd build/clp-package/sbin
./start-clp.sh --exclude webui log_viewer_webui

Observed all components started except webui and log_viewer_webui.

Thanks for making the change, it now makes much more sense to me

Trying to think about this from another perspective, what if we rearrange the code, such that we have a function, takes in the target, the exclude, and generates a List: components_to_run. in that case, for each if statement, we simply need to write something like if DB_COMPONENT in components_to_run.
A trade off is that now for targets correspond to mulitple component, we would need to have some good way to define them.
Like
"ALL_TARGET": [
"comp1",
"comp2",
"comp3,
...
]
"CONTROLLER_TARGET": [
"comp1",
...
]

What's the status of this PR?

Let's close this for now. We will refactor the WebUI components and the mechanism proposed in this PR may no longer apply.


CustomStatement does not fire watch event.

Hi, I am implementing CRDTs for my app and therefore I got the following table:
CREATE TABLE crdt (
    collection TEXT NOT NULL,
    id TEXT NOT NULL,
    field TEXT NOT NULL,
    value BLOB,
    hlc TEXT NOT NULL,
    modified TEXT NOT NULL,
    PRIMARY KEY (collection, id, field)
);

Since value has to be dynamic (it could be any sql data type), I use Blob for it. However, the typed table generated by Drift uses Uint8List as the type for the value column. Since type serialisation to and from Uint8List is difficult, I take advantage of the fact that sql3 stores the value dynamically, so I can write and read dynamic types without having to serialise them. Of course, this means that I cannot use the typed table (with the Uint8List value) provided by Drift, but have to use custom queries instead.
Now to the actual problem I have:
I have a simple query to determine the maximum modified value:
getMaxModified: SELECT MAX(modified) FROM crdt;

(Side Question: This query is not achievable as Drift query, since the max expression is not available for String/Text, am I correct?)
And I am watching this query:
Stream<Hlc> get canonicalTimeStream {
  return getMaxModified()
      .map((modified) =>
          modified?.asHlc ?? Hlc.zero(nodeId: const Uuid().v4()))
      .watchSingle();
}

When I subscribe to the stream and print the output, I do not get new results when I insert new values using custom statements.
So when I insert some new value e.g. with this:
  Future<void> saveCrdt(CrdtTableModel r) async {
    final crdtTbl = crdt.actualTableName;
    final query = """
      INSERT INTO $crdtTbl
      (collection, id, field, value, hlc, modified)
      VALUES (?1, ?2, ?3, ?4, ?5, ?6)
      ON CONFLICT (collection, id, field) DO UPDATE
      SET value = excluded.value, hlc = excluded.hlc, modified = excluded.modified
      """;
    final vars = [
      r.collection,
      r.id,
      r.field,
      _encodeValue(r.value),
      r.hlc,
      r.modified.toString()
    ];
    await customStatement(query, vars);
  }

the subscriber does not receive a new value.
However, when I use Drift's insertOnConflictUpdate the trigger works fine...
into(crdt).insertOnConflictUpdate(CrdtData(
        collection: "test",
        id: "test",
        field: "test",
        value: Uint8List.fromList([1]),
        hlc: "2022-12-12T06:18:49.417Z#0000#0f04f467-78f0-4fb8-9151-26e5927ddef6",
        modified: "2022-12-12T06:18:49.417Z#0000#0f04f467-78f0-4fb8-9151-26e5927ddef6"
));

Unfortunatly this is not an option for me since I don't want to use Uint8List, as described above.
Thanks for your great work!

@simolus3 Thanks for the fast answer! Does something similar like customInsert() exist for batches?

It should! I've added this method in 5f887b8d2a5fe8be0e16cefa371ac9384e3578e3, so it will be available in the next drift release.


Fixing hx-disabled-elt attribute.

Description.
Fixing typo on hx-disabled-elt. According to docs it has to end with "d".

Hi there, and thank you for the pull request!
Thanks for spotting this; Definitely the small issues that are hard to catch, and I haven't been using HTMX much this part week so it hasn't been on my radar. The changes all look good to me, so I'm happy to merge in for the next release :)


WFCORE-5808 NonResolvingResourceDescriptionResolver.INSTANCE should b…

…e used instead of creating new instances
Issue: https://issues.redhat.com/browse/WFCORE-5808
Upstream: https://github.com/wildfly/wildfly-core/pull/4969

Core - Full Integration Build 10999 outcome was UNKNOWN using a merge of e5bfe6a96fddb96df4173a976c84d935fc7fa446
Summary: Canceled (Error while applying patch; cannot find commit 1ccef0eb3c839c84aa76870f91d73dfd8f50fb11 in the https://github.com/wildfly/wildfly-core.git repository, possible reason: refs/pull/5023/merge branch was updated and the commit selected for the ... Build time: 00:00:15


Add support for Greek

Leaving this as a placeholder.
It would be great if the README listed the procedure in order to request/support new languages.

https://github.com/argosopentech/argos-translate/discussions/91#discussioncomment-644475
https://github.com/argosopentech/onmt-models#making-an-argospm-package


VEML6075 Datapoints

Describe the bug
As far as I understand should mqtt messages ariving at the sonoff adapter be able to make datapoints in iobroker. I have this mqtt message coming from an ESP8266 with Tasmota installed:
 MQT: tele/Hof/Lager/Tasmota/Relais/RFresv/Beleuchtung/UV/Beleuchtungsstaerke/Außenlampe/SENSOR = {"Time":"2021-05-28T14:30:44","BH1750":{"Illuminance":27550},"VEML6075":{"UvaIntensity":1710,"UvbIntensity":890,"UvIndex":2.4}}
I got a datapoint for UvIndex:
sonoff.0.Hof Lager.VEML6075_UvIndex
Missing are the points for UvaIntensity and UvbIntensity.
I have data points from a formerly used VEML6050. I don't know if this might influence the creation:
sonoff.0.Hof Lager.VEML6070_UvIndex
sonoff.0.Hof Lager.VEML6070_UvIndexText
sonoff.0.Hof Lager.VEML6070_UvLevel
sonoff.0.Hof Lager.VEML6070_UvPower
The data point BH1750 is old and still there.
Steps to reproduce the behavior:

restart iobroker - no change
restart the RPi2 - no change

Expected behavior
The data points should all be established
Screenshots & Logfiles

Versions:

Adapter version: 2.4.0
JS-Controller version: 3.2.16
Node version: v12.20.0
Operating system: Raspian

Please test 2.4.1

I tested 2.4.1 and 2.4.3 without success. For the test with 2.4.3 I renamed the mqtt object in Tasmota and the adapter found it immedeatly - but without the UVA and UVB data, which is included in the mqtt message (08:11:43.400 MQT: tele/Hof/Lager/Tasmota/Relais/RFresv/Beleuchtung/UV/Beleuchtungsstaerke/Außenlampe/SENSOR = {"Time":"2021-07-19T08:11:43","BH1750":{"Illuminance":7006},"VEML6075":{"UvaIntensity":728,"UvbIntensity":444,"UvIndex":1.1}}).
.
Please see attached screenshots of the admin/objects interface.
Both times after installing I restarted the Pi 2B running iobroker.
Any idea whats the problem?
Thank you!

please try 2.4.4

2.4.4 work's for me. Thank you very much!


add .swiftpm/ to gitignore

When opening Package.swift with Xcode, it will create a .swiftpm directory, this should be in the gitignore

thanks


Missing SOVERSION bump

As we are needing to include aws-c-common in Amazon Linux in order to package AWS CLI v2, we need to ensure that the SOVERSION is being updated appropriately to avoid nasty build and runtime surprises.
When looking at the diff between v0.6.14 and v0.7.4, I noticed a couple of changes that should have come with an SOVERSION major or minor bump.
It looks like https://github.com/awslabs/aws-c-common/commit/ee859bf31f2d840c25a1b7cb7d4624aa31b77905 should have introduced a minor bump as it added functionality.
The changes in https://github.com/awslabs/aws-c-common/commit/3eb38301aaca6dd454828a006315c706e5ce3bf8#diff-e4e7fa2904589ee122e13b9546e13b80ef35e509aaa26fa8967ef3238d5533c9L119 appear to also indicate an ABI change, which would mean a major SOVERSION bump would be needed as well.
Am I misunderstanding these changes and their impact to shared library ABI?

Sorry for the late reply. We have since bumped the version to v0.9.23. So I don't think this is a concern anymore. Please let me know if you have any questions about versioning with this sdk