12 Volt Deep cycle value

Hello,
Will this code and resistor set up work for a 12 volt Deep cycle battery
Looking to do something for a battery that is on a battery backup sump pump to alert via Email when it a start to see a change in the voltage that the battery is going bad.
I have the code and everything else for sending out email.
Just need  a way to read the battery once a week to check the status.
THanks!

Hi, yes this will with 12v battery however I'd rather pick different pair of resistors, let's say 4k and 1k so we will get 3.3v at ADC pin with 16v source connected, this way your readings will be more accurate, also you should add 3.3v zener diode (in parallel between ADC pin and GND) for extra protection in case of voltage spikes. Getting voltage readings using rpi pico may be good for low risk projects (due to adc spikes and possible interference from connected battery load), but if you care most about accuracy, better alternative might be to use dedicated digital voltmeter like DFRobot I2C Digital Wattmeter.

Thank you for the info
Really do not need 100% accurate.
The battery just sits on a trickle charger hooked up to a secondary sup pump. Almost never goes on unless we lose power for an extented period of time.
Just want to check the state of the battery once a day or ever other day a nd if a see a downward trend I know it is time to replace
Was going to add code so when it reads the battery if it gets a weird reading or a reading that the battery is a bad state it would read it again 2-3 times to check before it sends me an email that I need to inspect the battery
I will look into the DFRobot I2C Digital Wattmeter as well
Thanks for the information

You can always test Pico ADC before getting into i2c wattmeters, and if the results are ok there is no need to buy or search for driver to use separated device. Also your approach with performing many readings before making decision if battery is in bad condition might be enough to solve problems I mentioned previously.


Headless Mode: Java Versions.

I am having a problem loading a configuration in headless mode that works fine when running under micromanager.
I am running on MacOS and want to load the adapter for the Basler camera.  It wasn't provided with the release, so I downloaded, configured and compiled the module and placed in the latest micromanager release directory. Fired up micromanager with the configuration and all is fine.
Tried using the same configuration in headless mode and I get an error:
hs_err_pid77161.log
Note that I am using V8 as the JRE in headless startup to get the class load to work, but it seems that micromanager is running V9.  Not sure if this is the issue, but its one difference that I see between the two setups.

Thats pretty clearly an error coming from the device adapter itself, so its not clear to me why running headless or through micromanager would make a difference. Does the same thing happen when you swap in the demo camera for the basler camera? If so than I'd suspect there is an issue in the device adapter.
It does seem from that file that you're actually using JRE 9 to run the headless, not JRE8:
# JRE version: Java(TM) SE Runtime Environment (9.0+11) (build 9.0.4+11)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (9.0.4+11, mixed mode, tiered, compressed oops, g1 gc, bsd-amd64)

So perhaps that has something to do with it?

Everything works fine with demo camera.
Not sure why it's jre9.  That is not the path I am using in the arg to headless start.  If you recall I had to specify jre8 to get the class load to work.  Let me see if something funny is goning on with the path.
Sent from my iPhone
On Jul 4, 2021, at 10:59 AM, Henry Pinkard @.***> wrote:

Thats pretty clearly an error coming from the device adapter itself, so its not clear to me why running headless or through micromanager would make a difference. Does the same thing happen when you swap in the demo camera for the basler camera? If so than I'd suspect there is an issue in the device adapter.
It does seem from that file that you're actually using JRE 9 to run the headless, not JRE8:
JRE version: Java(TM) SE Runtime Environment (9.0+11) (build 9.0.4+11)
Java VM: Java HotSpot(TM) 64-Bit Server VM (9.0.4+11, mixed mode, tiered, compressed oops, g1 gc, bsd-amd64)
So perhaps that has something to do with it?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/micro-manager/pycro-manager/issues/302#issuecomment-873634006, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA3OGXUYSHSNSOXWZDO3RYLTWCOO3ANCNFSM47YO3ULQ.

hmm... jre9 might have been something funny.  Its showing the correct JRE version after clean restart... still seeing same error and different behavior between headless start and using the GUI for the same config file.
One thing I did notice from the stack trace is that the core seems to be trying to unload all of the drivers as part of loading the config file and the error occurs when the driver is unloaded.  Is is possible that this is causing the difference between the two scenarios?
hs_err_pid50381.log

It would make sense to me that the basler adapter has some error that only comes up when it is unloaded.
But I don't know why this would only get triggered with headless start. The calls made as headless start are directly copied from those that launch micro-manager in Java. You can see them here:
https://github.com/micro-manager/pycro-manager/blob/49b68607cc04d4405bf9b1f7cde74f6559ca1cf7/pycromanager/acquire.py#L77
I don't see any reason why this would be different from the source it was copied from:
https://github.com/micro-manager/micro-manager/blob/fe1a3b72f3a6fd36b717789ccb76c4c185b66298/mmstudio/src/main/java/org/micromanager/internal/MMStudio.java#L797

As a test, I tried to just load the module, and I also get an error.  While I'm willing to believe I did something wrong building the module, the difference in behavior between headless start and regular start is concerning.  Is it possible there is something in my setup that would make the two behave differently?  The micro-manager download is just a nightly build, right out of the box.
Traceback (most recent call last):
  File "/Users/carl/opt/anaconda3/envs/spim-data/lib/python3.9/site-packages/IPython/core/interactiveshell.py", line 3441, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-8-4d0ec9da58eb>", line 1, in <module>
    b.get_core().load_device("BaslerCamera")
  File "/Users/carl/Repos/Projects/pycro-manager/pycromanager/core.py", line 426, in <lambda>
    ): instance._translate_call(signatures_list, args)
  File "/Users/carl/Repos/Projects/pycro-manager/pycromanager/core.py", line 534, in _translate_call
    valid_method_spec, deserialize_types = _check_method_args(method_specs, fn_args)
  File "/Users/carl/Repos/Projects/pycro-manager/pycromanager/core.py", line 698, in _check_method_args
    raise Exception(
Exception: Incorrect arguments.
Expected java.lang.String, java.lang.String, java.lang.String
Got <class 'str'>
b.get_core().load_device("Camera","BaslerCamera","FooBar")
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.micromanager.internal.zmq.ZMQServer.runMethod(ZMQServer.java:346)
	at org.micromanager.internal.zmq.ZMQServer.parseAndExecuteCommand(ZMQServer.java:401)
	at org.micromanager.internal.zmq.ZMQServer.lambda$initialize$1(ZMQServer.java:108)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.Exception: Failed to load device "FooBar" from adapter module "BaslerCamera" [ Device adapter "BaslerCamera" failed to instantiate device "FooBar" ]
	at mmcorej.MMCoreJJNI.CMMCore_loadDevice(Native Method)
	at mmcorej.CMMCore.loadDevice(CMMCore.java:312)
	... 11 more
Traceback (most recent call last):
  File "/Users/carl/opt/anaconda3/envs/spim-data/lib/python3.9/site-packages/IPython/core/interactiveshell.py", line 3441, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-9-0b57b264d972>", line 1, in <module>
    b.get_core().load_device("Camera","BaslerCamera","FooBar")
  File "/Users/carl/Repos/Projects/pycro-manager/pycromanager/core.py", line 426, in <lambda>
    ): instance._translate_call(signatures_list, args)
  File "/Users/carl/Repos/Projects/pycro-manager/pycromanager/core.py", line 548, in _translate_call
    return self._deserialize(self._socket.receive())
  File "/Users/carl/Repos/Projects/pycro-manager/pycromanager/core.py", line 167, in receive
    self._check_exception(message)
  File "/Users/carl/Repos/Projects/pycro-manager/pycromanager/core.py", line 172, in _check_exception
    raise Exception(response["value"])
Exception: java.lang.Exception: Failed to load device "FooBar" from adapter module "BaslerCamera" [ Device adapter "BaslerCamera" failed to instantiate device "FooBar" ]
mmcorej.MMCoreJJNI.CMMCore_loadDevice(Native Method)
mmcorej.CMMCore.loadDevice(CMMCore.java:312)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:498)
org.micromanager.internal.zmq.ZMQServer.runMethod(ZMQServer.java:346)
org.micromanager.internal.zmq.ZMQServer.parseAndExecuteCommand(ZMQServer.java:401)
org.micromanager.internal.zmq.ZMQServer.lambda$initialize$1(ZMQServer.java:108)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)

As a test, I tried to just load the module, and I also get an error.

Unclear on what exactly you did. Can you post code?

I'm willing to believe I did something wrong building the module, the difference in behavior between headless start and regular start is concerning. Is it possible there is something in my setup that would make the two behave differently? The micro-manager download is just a nightly build, right out of the box.

I agree. But there's nothing obvious to me as to what would be causing that. Maybe there is something weird with your string formatting + passing from java to python such that config_file in core.load_system_configuration(config_file) is incorrect?

sorry, I led you astray... I didn't check carefully enough.  It turns out that the first start_headless works fine.  I then do a second on a different port and this is the one that fails with the java error message.  I wonder if there is some shared state that is messing up the second instance... perhaps in the USB driver iteself.  I will play around some more.

yep, that seems to be it.  It would seem that micromanager is not happy when you try to load the same adapter twice, even though it is on a different port.

Sounds like it is an adapter-specific bug then. Worth opening an issue on main micro-manager repo


Feature request:- Loan Repayment Prediction

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.
To predict if a person is able to repay his loan or not
Describe the solution you'd like
A clear and concise description of what you want to happen.
Create a Machine Learning Model to predict if a person would be able to repay his loan or not.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
N/A
Approach to be followed (optional)
A clear and concise description of the approach to be followed.
Data Collection, EDA, Preprocessing and Training, Testing
Additional context
Add any other context or screenshots about the feature request here.
I am a GSSOC'24 Extended and Hacktoberfest Contributor

@SaiNivedh26 @UppuluriKalyani @Neilblaze  I couldn't find a similar issue or work that exists. Kindly check and assign manually.


Setup e2e tests with cypress

Hey @yubathom,
Your changes look good to me!
View build log
TravisBuddy Request Identifier: 92377440-e60a-11e9-82e3-2501c7641175


Removed the text footer from the footer tag

Pull Request Template

Please provide all of the details below. Pull requests missing any of the information below will be closed!

Sumarise what this PR fixes: < Just removes a text from the footer tag in index.html >
Fixes #: < Enter Issue ID/URL >
Checklist:
(Add an x between the brackets to check the items)

[ x] I have sumarised what this PR fixes above
[x] I have provided the issue ID/URL above
[x] This PR fixes only the issue mentioned above (create seperate PRs for seperate issues)
[x] I was the first one to claim the issue or I created the issue

This pr does not resolve a current issue and has nothing added to the project. Marking as invalid.


Add a warning for ARMv8.2-A

See #485, especially https://github.com/docker-library/mongo/issues/485#issuecomment-970864306.
This is a follow-up to / enhancement of #491.

(This is [marginally] easier to review without whitespace: https://github.com/docker-library/mongo/pull/511/files?w=1)


Perfomance issue with forked branch

There is a performance issues with with this version of the fork. I have made two builds one with the original project and the other with forked branch and found the following average results using the same chip. Is there a place in the code where this is configured the discrepancy is too much.
Original:

Forked:

There are a few things that can affect performance.
First, check your link speed after connecting to the ESP32. If it's around 150 Mbps, that's a good sign. Also, make sure your power source is providing enough current, as this can impact performance, especially with extra features enabled.
Try out this firmware to see if it improves things or if you still face the same issue. Let me know how it goes.
esp32.zip

This ZIP file is not working, can you provide the address information for uploading the separate files or just a single bin file


⚠ Samsung has degraded performance

In e938b1e, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2827 ms

Resolved: Samsung performance has improved in e569b26.


Add setting for AMP Google Analytics tracking

AMP does not include any scripts, or any code injection, so it does not get reported in Google Analytics. Making it work is relatively simple : https://www.pixelite.co.nz/article/adding-google-analytics-to-amp-posts-in-ghost/ - but it would be nice if this wasn't required.
Could we allow AMP to have a single setting, a text field, for

Google Analytics Tracking ID
Tracks AMP traffic in Google Analytics, find your ID here
<input type="text" placeholder="UA-XXXXXXX-X" />

If set, then it should output:
Inside <head> right here (or inside {{amp_components}}?)
<script async custom-element="amp-analytics" src="https://cdn.ampproject.org/v0/amp-analytics-0.1.js"></script>

Right before </body>
<amp-analytics type="gtag" data-credentials="include">
    <script type="application/json">
        {
            "vars" : {
                "gtag_id": "UA-XXXXXXX-X",
                "config" : {
                    "UA-XXXXXXX-X": { "groups": "default" }
                }
            }
        }
    </script>
</amp-analytics>

Working URL example:
https://ghost.org/blog/how-to-create-a-newsletter/amp/
Validator:
https://search.google.com/test/amp
I don't think we need to do detailed validation / try to prevent broken inputs. If people do something wrong, Google will send them 1 million emails about it anyway.
Appetite: 1 day

This will require a new setting amp_gtag_id added in group amp, configured via the existing AMP integration configuration page in Admin (at #/settings/integrations/amp). Text input should follow the UI conventions used in the equivalent Slack integration config screen (exact copy TBD).

@matthanley Is there any update on the exact copy wanted to the screen?

https://github.com/TryGhost/Ghost-Admin/pull/1638 I've added the initial UI work here

Exact copy is in first comment of this issue - between the two <hr> lines - should be safe to use that
This can go straight out and be reviewed alongside release or whatever, should be small enough to not need any formal review or anything

This is now in master!
https://github.com/TryGhost/Ghost/pull/12039 - Migrations, database & template updates
https://github.com/TryGhost/Ghost-Admin/pull/1638 - UI updates


Handle brackets in page title

A country has it's legacy name in brackets.
That makes it an invalid XML ID, which we need to fix.
Mock content here

Fixed in #489


Timer based example on docu using nrf52-dk compile error.

Hi I'm new with using zephyr  and maybe a noob question. I'm using nrf52-dk via platformio. Been scratching and googling but can't find answer. I just copied the example timer expiry on zephyr documentation but this shows up and I can't fix it. I need the timer to work every 50ms. It says declaration incompatible pointing to the kernel.h file.
TIA

kernel.h file

Closing this. Solved it by moving it to main.


Pomodoro clock GUI

Is your feature request related to a problem? Please describe.
We often find it difficult for us to stay productive and manage time to complete our tasks without getting distracted.
Describe the solution you'd like
The Pomodoro technique uses a timer to break down work into intervals, traditionally 25 minutes in length, separated by 5 -15 min breaks. I will be implementing this in a GUI based form along with an extra functionality of website blocking to prevent distractions.

@rmoyano updates on this?

@RohiniRG updates on this?

@RohiniRG updates on this?

Yes, I am working on it, I'll put up the PR within a day.


udpate to 2.3.0

based on api list changes 776c317c6300303428d9a8fe30936d17550aec00

there should be 43 new APIs to be added

Any update for 2019 year?

mmmm, this repo is maintained by handwriting or packet capture something?

It's handwriting based on the WAService.js file extracted from the Wechat Web DevTool

Inspired by your awesome work, I fetch the API and generate the typing file in here, hoping to help you.

changes updated https://github.com/Emeryao/typed-we-app/commit/e040462190f28f1ec287d64fa9161740602d8280#diff-d47f3321f5ef1d278505699055b34112


Bug? Killer Joe doesnt use XP it collect to repair tools with mending

Mending is a new enchantment and it uses xp to repair itself. Unfortunately, the killer joe does not repair the weapon using the xp it collects when it should which makes the enchantment meaningless.

enable it in the config

Why is this disabled by default?


update dynamiclyrics url

Thank you for the contribution. It needed some fixes, so they were made in 6d10aa1911cc6edb9629a601106e740c65f92789. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


GibsonEnv for robot manipulation

Hi,
GibsonEnv looks cool. Does it work for robot manipulation, like grasping? Has anyone tested it on manipulation yet? Thanks.

GibsonEnv for manipulation is being actively developed and will be released soon.


Add prefilter, final filter and bolster filter definition

Addressing discussion in https://github.com/BrickSchema/Brick/issues/152

Seems reasonable to me :) 👍


Support awscli configuration files in '.aws' folder

Proposal
The awscli uses the ~/.aws folder to store configuration files. One of those being a credentials file that can have default and profiles sections. The file follows an ini type format:
[default]
aws_access_key_id = <access_key>
aws_secret_access_key = <super_secret_thing>

[bob]
aws_access_key_id = <access_key>
aws_secret_access_key = <super_secret_thing>

To support this in ExAws we could introduce a new config tuple similar to the {:system, "KEY"} that is currently supported. This could support the default or named profiles. Something like the following could be supported:
#loads config values from the "default" section
config :ex_aws,
  access_key_id: [{:shared, "aws_access_key_id"}, :instance_role],
  secret_access_key: [{:shared, "aws_secret_access_key"}, :instance_role]

and
#loads from the named section
config :ex_aws,
  access_key_id: [{:shared, "bob", "aws_access_key_id"}, :instance_role],
  secret_access_key: [{:shared, "bob", "aws_secret_access_key"}, :instance_role]

Implementation Details

To read the config file we would add an optional dependency on ConfigParser and return nil if the module is not loaded at runtime.
We would also need to load the path to the file in a cross-platform friendly way. Check for ~/.aws/credentials on OSX, Linux, Unix and C:\Users\<USERNAME>\.aws\credentials on Windows
use System.user_home |> Path.join(".aws") |> Path.join("credentials") and check File.exists?

Questions

What should the atom be for this type? :shared, :awscli or something else?
What should the format of the config object be? .aws has credentials and config files. So it could be something like: {:awscli, <file>, <section>, <key>} where file and section both have defaults?

Thoughts, comments, concerns?

Apologies for the delay. My primary concern here is the need to add an extra dependency. I wonder if there's a way to make the dependency nicely optional so that it's only used if you specify {:shared or something. I suppose if I simply marked it as an optional dependency, and then had just remote function calls to those modules inside my Config stuff I would be good to go.

The way I tested it, was with an optional dependency. Then I did a
Code.ensure_loaded? call before using it. If it's not loaded give a
warning and return nil.
I have a rough implementation put together that works. And it's pretty
simple.
On Tue, Apr 12, 2016, 2:40 PM Ben Wilson<EMAIL_ADDRESS>wrote:

Apologies for the delay. My primary concern here is the need to add an
extra dependency. I wonder if there's a way to make the dependency nicely
optional so that it's only used if you specify {:shared or something. I
suppose if I simply marked it as an optional dependency, and then had just
remote function calls to those modules inside my Config stuff I would be
good to go.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/CargoSense/ex_aws/issues/132#issuecomment-209072565

This can be done with a separate module, going to go that route instead. It will allow the functionality to exists, but not add the complexity to ExAws directly.


[WIP] extends agreement

Extends Agreement contracts according to legal guidelines. Please check Agreement contract header for details.
If this direction is approved I will continue with code cleanup and proper test update/coverage

Followup

cancellation removed
signatories storied in a mapping to easily check who signed agreement, also prevents log pollution
only legally binding acceptAgreement left in Neumark and LockedAccount
I leave the riddle of signing up investor in Commitment contract to Neumark Token Holder Agreement to @Recmo There is already such provision in legal contract and we should follow:

Neumark Token Holder Agreement. By concluding this Agreement and triggering acquisition (‘transfer’) of the Neumark Tokens to the Neumark Holder’s Ethereum Address, the Neumark Holder enters into the Neumark Token Holder Agreement (the “NTHA”), on the terms and conditions specified therein. Acceptance of the terms and conditions of the NTHA is required in order to conclude this Agreement.

I dropped Agreement inheritance from LockedAccount. We'll add it to new Commitment contract when it is ready.


Flaming helment ?

Ive been looking for it but cant find it

The flaming helmet can be used without any mods.
There's a chest piece you can equip which has the effect.

It's the Bungie chestpiece


senders: Mitigate issue with GCP logging quota

https://cloud.google.com/logging/docs/reference/v2/rest/v2/entries/write
https://cloud.google.com/logging/quotas
WHAT
This PR is doing two things:

Not retrying to send logs that return with HTTP status code 4xx. Instead those logs are simply skipped.
Filtering out any LogEntry that is bigger than 256K

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 63.47%. Comparing base (a71f5aa) to head (95d94d7).
Report is 5 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #171      +/-   ##
==========================================
+ Coverage   63.32%   63.47%   +0.15%
==========================================
  Files          19       19
  Lines        2094     2100       +6
==========================================
+ Hits         1326     1333       +7
+ Misses        768      767       -1

Files
Coverage Δ

journalpump/senders/base.py
80.44% <ø> (+0.10%)
:arrow_up:

journalpump/senders/google_cloud_logging.py
91.66% <100.00%> (+1.34%)
:arrow_up:

... and 2 files with indirect coverage changes


Initialize basic development framework for TrafficManager

Pull Request Template
Description
To initialize basic development framework for TrafficManager
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
TODO
Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have checked my code and corrected any misspellings

@LinkinPF 也看一看


fix: thorchain LP token withdraws

Description

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #
Risk

High Risk PRs Require 2 approvals

What protocols, transaction types or contract interactions might be affected by this PR?

Testing

Engineering

Operations

Screenshots (if applicable)

#6374  👈
develop

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

Join @gomesalexandre and the rest of your teammates on  Graphite

Good catch on the depositWithExpiry amount!


Update: phase ID (codename) retrieval updated

Description
Update: new method to obtain the challenge phase codename
Fixes #
Where has this been tested?

Platform(s): Ubuntu 16.04
Python version(s): 3.5.5
Unreal Engine version(s): NA
CARLA version: carla-overnight 2019-03-29

Possible Drawbacks

This change is


Not working value change

My initial value<EMAIL_ADDRESS><EMAIL_ADDRESS>I get emails from excel file...
Result<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>But don't work re-render getLabel function. Still showing old value<EMAIL_ADDRESS><EMAIL_ADDRESS>My state value changed<EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>It was working fine two days ago.

Hello. Please show me the reaction-multi-email usage code. Thanks

MyState structure:
const [participants, setParticipants] = useState({
participant1<EMAIL_ADDRESS>participant2: null
})
It's my code setting code:
const setImportedEmailToParticipants = (importedEmails) => {
let newParts = {
...participants,
[${importParticipantKey}]: importedEmails,
};
setParticipants(newParts);
};
<ReactMultiEmail
emails={participants?.[key] || []}
onChange={(_emails) => {
setParticipantErrors(null);
handleEmailChange(_emails, key);
}}
allowDuplicate={true}
autoFocus={true}
getLabel={(email, index, removeEmail) => {
return (

{email}
{key !== "participant1" && (
<span
data-tag-handle
onClick={() => removeEmail(index)}
>
×

)}

);
}}
/>

setParticipants({...newParts});

If the key value in the object is changed, JS does not recognize it as a new value.
I think it will probably work if I use it as above.
If possible, I think it's better not to use the email value as an object key.

It's not working. I aspirant this way.
it's my state...
const [changedEmails, setChangedEmails] = useState([]);
setChangedEmails([...importedEmails]); or setChangedEmails(importedEmails);
config:
emails={changedEmails}
It's my result. But still re-render not working.

Do you have any ideas?

Hi @Bttlg , your intent is not working because react-multi-email is just using emails props with useState which only initializing the values.
If you want to change emails, you should re-render the react-multi-email now.
@thomasJang I think we can support dynamic props changing with useEffect hook. How do you think about this?

// propsEmails: string[] | undefined
const [emails, setEmails] = React.useState<string[]>(() => initialEmailAddress(propsEmails));

// Add hook
useEffect(() => {
  setEmails(propsEmails || []);
}, [propsEmails]);

Thank you very much, @134130
And @Bttlg  I'm sorry I didn't check the problem exactly.
There is a problem with the code, so it is being modified. It will be fixed soon.

@Bttlg is the issue has been resolved ?


Opportunity to Improve Conversion of Validation.Invalid<? extends Throwable,T> to Try

I have a Validation and I'd like it to cause an exception carrying the Validation.Error.error content, somehow.
My first thought was to invoke mapError() on my Validation to roll the error content into a Throwable, then simply to invoke toTry() on the new Validation. Unfortunately that invokes Value.toTry() which attempts a get() even if the Validation is an Error. There is no specialized behavior that somehow notices that the Error is actually carrying a Throwable, so the error could be used to initialize the cause in a new Try.Failure.
My second thought was to invoke getOrElseThrow() directly on my original Validation. Unfortunately, that method does not provide visibility to the Validation.Error.error content. That method takes a Supplier<X>.
As a workaround, I mapError() on my Validation to transform my (String) error content into a Throwable (carrying the String in the message). Then I wrote my own method to convert such a Validation into a Try:
    private static <T> Try<T> toTry(final Validation<? extends Throwable,T> v) {
        // avoid calling v.toTry() if v.isInvalid()
        return v.isValid() ? v.toTry() : Try.failure(v.getError());
    }

I see various possible solutions that would obviate my approach (calling mapError() followed by my toTry() method above). :

Make Validation.Invalid.toTry() construct a Try.Failure:
a. …by making Value.toTry() aware of the possibility that the "alternative" (in this case Validation.Invalid.error) might be a valid argument to the Try.failure() constructor. In that case, instead of calling get(), it could call Try.failure().
b. …or by defining a Validation.Invalid.toTry() that constructs the Try.Failure if the cause is Throwable.
Overload (or redefine) Validation.getOrElseThrow() to take a Function1<? extends Throwable,T>. Then getOrElseThrow could pass the Validation.Error.content (in this case, a Throwable) to the fn.

Update: as I learned later (see my next message) (2) would bring Validation.getOrElseThrow() into alignment with Either.getOrElseThrow() and so it might be a minimally-disruptive change. That being said, it seems to me that if (1) could be made to work, the approach should be applied to Either as well as Validation. If toTry() on a thing carrying a Throwable in its "alternative" created a Try with that Throwable as the error, toTry() would be less surprising to my way of thinking.
Here's a test (vavr 0.9.2, junit 4.12):
import org.junit.Before;
import org.junit.Ignore;
import org.junit.Rule;
import org.junit.Test;
import org.junit.rules.ErrorCollector;

import io.vavr.control.Try;
import io.vavr.control.Validation;

import static org.junit.Assert.*;
import static org.hamcrest.CoreMatchers.*;

public class ValidationToTryTest {

    private final Validation<String,String> invalid =
            Validation.invalid("a problem");

    private final Validation<? extends Throwable,String> invalidWithThrowable =
            invalid.mapError(IllegalArgumentException::new);

    @Rule
    public ErrorCollector collector = new ErrorCollector();

    @Test
    public void testConversionViaMapErrorThenToTry() {
        final Try<String> tryGet = Try.of(()-> invalidWithThrowable.toTry().get());
        collector.checkThat(tryGet.isFailure(), is(true)); // ok
        /*
         fails:
         Expected: is an instance of java.lang.IllegalArgumentException
         but: <java.util.NoSuchElementException: get of 'invalid' Validation> is a java.util.NoSuchElementException
         */
        collector.checkThat("Validation.toTry() doesn't have a specialization for Validation<? extends Throwable,T>",
                            tryGet.getCause(),is(instanceOf(IllegalArgumentException.class)));
    }

    @Test
    public void testConversionViaGetOrElseThrow() {
        final Try<String> tryGet = Try.of(()-> invalid.getOrElseThrow(IllegalArgumentException::new));
        collector.checkThat(tryGet.getCause(),is(instanceOf(IllegalArgumentException.class))); // ok
        /*
         fails:
         Expected: is "a problem"
         but: was null
         */
        collector.checkThat("getOrElseThrow() doesn't have visibility to the Invalid's error",
                            tryGet.getCause().getMessage(),is("a problem"));
    }

    @Test
    public void testConversionViaMapErrorThenUserDefinedToTry() {
        final Try<String> tryGet = Try.of(()-> toTry(invalidWithThrowable).get());
        collector.checkThat(tryGet.isFailure(), is(true)); // ok
        collector.checkThat(tryGet.getCause(),is(instanceOf(IllegalArgumentException.class))); // ok
    }

    private static <T> Try<T> toTry(final Validation<? extends Throwable,T> v) {
        // avoid calling v.toTry() if v.isInvalid()
        return v.isValid() ? v.toTry() : Try.failure(v.getError());
    }

}

Back in January (above) I came to the conclusion that, it seemed like an oversight, that there was no getOrElseThrow(Function<? super L, X>) on Validation.Valid/Validation.Invalid to match the corresponding methods on Either.Left/Either.Right that take Functions.
Yesterday I ran into an analogous problem trying to convert a Try to a Validation:
Validation<String,Apple> doSomeValidation(final String name) {
    return Try.withResources(() -> new AppleReader(name)).of(reader->{
      // do things with the reader. some things cause exceptions
      return reader.read();
    }).toValidation( /* I'd like to convert the Throwable into a Validation error here! */ );
}

But the Try does not send its error (Throwable) to the function supplied by the caller. Try has:
    default <L> Validation<L, T> toValidation(L invalid)
    default <L> Validation<L, T> toValidation(Supplier<? extends L> invalidSupplier)

Both inherited from Value. But there is no conversion to Validation that has access to the error if the Validation isInvalid(). That is, there is no variant of this function that takes a Function/Function1.
So we have a bunch of types that model "alternatives". All but one (Option) carry important information in the "left"/"error" part:
Either
Try
Validation

For each of those, there are various higher-order functions that should, in general, pass the "left"/"error" to the caller-supplied function, but do not.
Searching through Value, Either, Try, and Validation for "supplier" I gathered the full list of functions of interest. On each of Either, Try, and Validation I think these functions should be overloaded to take a Function/Function1:
// unless otherwise noted, "left"/"cause"/"error" value is passed to fn

Try.       toEither(fn)
Validation.toEither(fn)
Either.    toTry(fn)
Validation.toTry(fn)
Either.    toValidation(fn)
Try.       toValidation(fn)

// each of the following should be defined on each of Try, Validation, and Either:

getOrElse(fn)
getOrElseThrow(fn)
getOrElseTry(fn)

orElse(fn)

toInvalid(fn)    // pass "right"/"value" value to fn
toValid(fn)      // pass "left"/"cause"/"error" value to fn
toLeft(fn)       // pass "right"/"value" value to fn
toRight(fn)      // pass "left"/"cause"/"error" value to fn

With that done, my validation method could look something like this:
Validation<String,Apple> doSomeValidation(final String name) {
    return Try.withResources(() -> new AppleReader(name)).of(reader->{
      // do things with the reader. some things cause exceptions
      return reader.read();
    }).toValidation( throwable->throwable.toString() );
}

Hi @Bill, thank you for putting so much effort into this issue!
I fully agree with your suggested list of overloads! We should definitely add those.

Generally, since Java methods can be overloaded on argument type but not on return type, fromXXX() methods don't seem to make much sense in a Java library.
Is that what you are getting at @CauchyPeano?

@CauchyPeano I don't think I can say it any more clearly than I did on March 8.

Sadly, I have to admit that lately I have been a little careless in the care of the issues. With Vavr 1.0.0, we align more tightly to Scala. I've finished a first alpha version of the vavr-control module, which will contain Option, Either and Try. Especially, Validtation will reside outside of that module.
The conversion methods of the vavr-control module have (more or less) a final state now. So this issue is obsolete. I will close it.

@CauchyPeano this also has an impact on your PR #2304. I really appreciate your effort, sorry for discarding your work.


Can't attach file in android

When trying to attach file with paths which are in private storage of app i get exception
What I am trying to do
var emailTask = CrossMessaging.Current.EmailMessenger;                 if (emailTask.CanSendEmail)                 {                     var email =  new EmailMessageBuilder()                     .To("")                     .Body(AppResources.EmailBodyText)                     .Subject(AppResources.EmailBodySubject)                     .WithAttachment("/data/user/0/DMD.Client.Android/files/textfile", ".txt")                     .WithAttachment("/data/user/0/DMD.Client.Android/files/imagefile", ".png").Build();                     emailTask.SendEmail(email);                 }
What exception i get
{Java.Lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.XmlResourceParser android.content.pm.ProviderInfo.loadXmlMetaData(android.content.pm.PackageManager, java.lang.String)' on a null object reference   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in /Users/builder/jenkins/workspace/xamarin-android-d15-5/xamarin-android/external/mono/mcs/class/referencesource/mscorlib/system/runtime/exceptionservices/exceptionservicescommon.cs:152    at Java.Interop.JniEnvironment+StaticMethods.CallStaticObjectMethod (Java.Interop.JniObjectReference type, Java.Interop.JniMethodInfo method, Java.Interop.JniArgumentValue* args) [0x00069] in <54816278eed9488eb28d3597fecd78f8>:0    at Android.Runtime.JNIEnv.CallStaticObjectMethod (System.IntPtr jclass, System.IntPtr jmethod, Android.Runtime.JValue* parms) [0x00000] in /Users/builder/data/lanes/5749/d8c6e504/source/xamarin-android/src/Mono.Android/Android.Runtime/JNIEnv.g.cs:562    at Android.Support.V4.Content.FileProvider.GetUriForFile (Android.Content.Context context, System.String authority, Java.IO.File file) [0x00077] in <dc495abdac154ae3bea326f4da3a4ec0>:0    at Plugin.Messaging.EmailTask.SendEmail (Plugin.Messaging.IEmailMessage email) [0x00191] in C:\PragmaDev\OKSource\Git\Xamarin.Plugins\Messaging\Plugin.Messaging.Android\EmailTask.cs:102

I'm seeing this as well.

@hanzala-abbass Just looking at your code snippet again, the second parameter for the WithAttachment call should be the contentType for the kind of file you are attaching, i.e. something like image/jpeg for a jpeg file.  The extension for the file should be included as part of first parameter.

closing issue as no more feedback has been provided.

Hi,
Could you please confirm that the second parameter of .WithAttachment for a .txt file = text/txt
I am getting an error message reading "Unable to attach file due to IO error"

try text/plain

Thanks for the quick reply @cjlotz My error was due to the file I was trying to attach was not in a publicly accessible storage location. I've since implemented a line of code which copies the text file from the original location to a temporary public one, then use that to attach before removing it.
Oh, and text\txt works fine for me :)
Thanks again


Typo

The linguists asked to have this changed.
Description of proposed changes
What is the goal of this pull request? What does this pull request change?
Related issue(s)

Fixes #
Related to #
Testing
What steps should be taken to test the changes you've proposed?
If you added or changed behavior in the codebase, did you update the tests, or do you need help with this?
Thank you for contributing to Nextstrain!

Thanks for the typo fixes @VengaLing . However, the update to "authors:" in the header section will screw up formatting. Do you mind eliminating that?

Sorry about that. Removed


How to insert texts or pics into markdown?

I want to implement a feature where, once a button is pushed, the editor automatically inserts a picture or a text, which may be generated by AI. However, I'm still not sure how to achieve this

This is too broad of a question, to be honest. The short answer is that you need to use the Lexical API for content manipulation - node insertion, node removal, etc.

Thank you for your answer. If possible, could you provide a demo?


missed dates added on Bulgaria

I tried to added missied dates to bulgaria.py as noted in https://github.com/dr-prodigy/python-holidays/issues/507
I hope it will work.

I tried to added missied dates to bulgaria.py as noted in https://github.com/dr-prodigy/python-holidays/issues/507
I hope it will work.

#507

Thank you very much! 👍


Can't get metrics working

Describe the bug
Whatever settings I use for promql backend, metrics are failed to read.
Grafana reads well at the same time.
Perhaps the problem is that I use prometheus-in-place replacement VictoriaMetrics, and it can't be detected through expected services or whatever.
Please, give us an opportunity to specify just url to promql-endpoint, without autodetect-magic.
like https://mydomain.tld/path/to/api
Screenshots

Environment (please complete the following information):

Lens Version: 4.0.6
OS: Debian linux
Installation method (e.g. snap or AppImage in Linux): AppImage

At this moment Lens can fetch metrics only via service running inside the cluster. Is VictoriaMetrics running inside the cluster? If yes then you can point to fetch metrics by setting /:/path/to/api

At this moment Lens can fetch metrics only via service running inside the cluster. Is VictoriaMetrics running inside the cluster? If yes then you can point to fetch metrics by setting /:/path/to/api

Yes. it works inside the cluster, and i tried to provide /:/path/to/api but still something is wrong.
Can't get it working and don't understand how to debug/log it.

Yes. it works inside the cluster, and i tried to provide /:/path/to/api but still something is wrong.
Can't get it working and don't understand how to debug/log it.

# curl -X POST <IP_ADDRESS>:8481/select/0/prometheus/api/v1/query?query=up

works perfectly.

# curl -X POST <IP_ADDRESS>:8481/select/0/prometheus/api/v1/query?query=up

works perfectly.

what does, for example, curl -X POST <IP_ADDRESS>:8481/select/0/prometheus/api/v1/query?query=container_cpu_usage_seconds_total return? Just thinking if the metrics do not contain all the labels Lens is expecting.

what does, for example, curl -X POST <IP_ADDRESS>:8481/select/0/prometheus/api/v1/query?query=container_cpu_usage_seconds_total return? Just thinking if the metrics do not contain all the labels Lens is expecting.

Perhaps you are right.
So, it could be  kube-state-metrics daemon then ?

Perhaps you are right.
So, it could be  kube-state-metrics daemon then ?

Seems so. I think I have to close this one.

Seems so. I think I have to close this one.

@korjavin did you manage to solve this issue ? and if so, how ?
I installed kube-state-metrics from the lens manifests alongside victoriametrics but I don't have these metrics

Nope, I couldn't. This part seems broken.

after digging a bit more I found how to solve it, the issue is that you need a specific config to instruct vmagent to read metrics from kubernetes (these come from cadvisor which is inside the kubelet process served by kubernetes service api), I found it here: https://github.com/VictoriaMetrics/operator/blob/185e3d1c5b47215606ac24b966d09740685f6439/docs/quick-start.MD#vmnodescrape
After adding this entity (I am using the operator) I now have the metrics !

after digging a bit more I found how to solve it, the issue is that you need a specific config to instruct vmagent to read metrics from kubernetes (these come from cadvisor which is inside the kubelet process served by kubernetes service api), I found it here: https://github.com/VictoriaMetrics/operator/blob/185e3d1c5b47215606ac24b966d09740685f6439/docs/quick-start.MD#vmnodescrape
After adding this entity (I am using the operator) I now have the metrics !
Edit: switching from prometheus to VictoriaMetrics feels a bit like assembling a puzzle, you need to find every pieces and how they fit until you got everything back... At least now I understand each part of my monitoring.

Can you describe in more detail how did you fix it?
I can see the code you've referenced in the current version of VM helm chart https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-k8s-stack/values.yaml#L651 but Lens is not showing anything.

@vainkop do you see some metrics or none ?
In my case I had all pod metrics and cluster metrics but was missing only the node metrics

@vainkop do you see some metrics or none ?
In my case I had all pod metrics and cluster metrics but was missing only the node metrics

I see no metrics on the main cluster page, which usually shows requests/limits. Only a standard error is shows which I usually see when smth is wrong with Prometheus stack.

check that your prometheus install is fine, port forward the prometheus port and query the  /metrics endpoints

check that your prometheus install is fine, port forward the prometheus port and query the /metrics endpoints

Well it is kind of fine since I can see all metrics inside grana dashboards which come with VM helm chart.
I'm trying to use VM helm chart & subcharts without any modifications so I'm using this one for VM stack installation:
https://github.com/VictoriaMetrics/helm-charts/tree/master/charts/victoria-metrics-k8s-stack
I've changed only this part https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-k8s-stack/values.yaml#L564-L597
Enabled ingress, adjusted urls, enabled tls & it works ok.
The rest I've left unchanged.
Here's how I ran it:
kubectl config set-context --current --namespace=monitoring
helm repo add grafana https://grafana.github.io/helm-charts
helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
helm repo add vm https://victoriametrics.github.io/helm-charts/
helm repo update
helm install vm vm/victoria-metrics-k8s-stack -f=helm-values.yml

Probably many things changed in this chart since you tried did. Do you have a chance to use up to date version & share which parameters you're using?

For me, VM stack and lens don't work together.
Whatever I put as metric url, it works for curl, but not for lens.
On Tue, Aug 10, 2021 at 3:20 PM vainkop @.***> wrote:

check that your prometheus install is fine, port forward the prometheus
port and query the /metrics endpoints
Well it is kind of fine since I can see all metrics inside grana
dashboards which come with VM helm chart.
I'm trying to use VM helm chart & subcharts without any modifications so
I'm using this one for VM stack installation:
https://github.com/VictoriaMetrics/helm-charts/tree/master/charts/victoria-metrics-k8s-stack
I've changed only this part
https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-k8s-stack/values.yaml#L564-L597
Enabled ingress, adjusted urls, enabled tls & it works ok.
The rest I've left unchanged.
Here's how I ran it:
kubectl config set-context --current --namespace=monitoring
helm repo add grafana https://grafana.github.io/helm-charts
helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
helm repo add vm https://victoriametrics.github.io/helm-charts/
helm repo update
helm install vm vm/victoria-metrics-k8s-stack -f=helm-values.yml
Probably many things changed in this chart since you tried did. Do you
have a chance to use up to date version & share which parameters you're
using?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lensapp/lens/issues/1942#issuecomment-895981535, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABEKHOCQAUJEYXQIUCAZXLT4EKPNANCNFSM4V6D3PVQ
.

I am using the victoriametrics operator with node-exporter and kube-state-metrics installed directly from yaml manifests so it will be hard to compare our setups xD
What I did is look at lens source code for the exact metrics queried on prometheus, port forward your prometheus/victoriametrics port, query /metrics (or look in grafana in explore) and make sure they are available.
Once you do that check that your cluster monitoring configuration in Lens is correct, I had to set it to Helm and provide the service by hand which in my case is: monitoring-system/vmsingle-vmsingle:8429
Once that was done I disconnected and connected back to the cluster and I had my graphs (Lens does not use the new metrics config until your restart or reconnect to the cluster).

I am using the victoriametrics operator with node-exporter and kube-state-metrics installed directly from yaml manifests so it will be hard to compare our setups xD
What I did is look at lens source code for the exact metrics queried on prometheus, port forward your prometheus/victoriametrics port, query /metrics (or look in grafana in explore) and make sure they are available.
Once you do that check that your cluster monitoring configuration in Lens is correct, I had to set it to Helm and provide the service by hand which in my case is: monitoring-system/vmsingle-vmsingle:8429
Once that was done I disconnected and connected back to the cluster and I had my graphs (Lens does not use the new metrics config until your restart or reconnect to the cluster).

Sounds like switching to helm & pointing to the vm service should work. I'll try & report.

Perhaps it works for vm-single.
For my cluster-version of VM  I tried everything.

I know that it's a correct service in settings, but it still doesn't work.

I am using the victoriametrics operator with node-exporter and kube-state-metrics installed directly from yaml manifests so it will be hard to compare our setups xD
What I did is look at lens source code for the exact metrics queried on prometheus, port forward your prometheus/victoriametrics port, query /metrics (or look in grafana in explore) and make sure they are available.
Once you do that check that your cluster monitoring configuration in Lens is correct, I had to set it to Helm and provide the service by hand which in my case is: monitoring-system/vmsingle-vmsingle:8429
Once that was done I disconnected and connected back to the cluster and I had my graphs (Lens does not use the new metrics config until your restart or reconnect to the cluster).

Sounds like switching to helm & pointing to the vm service should work. I'll try & report.

I am using the victoriametrics operator with node-exporter and kube-state-metrics installed directly from yaml manifests so it will be hard to compare our setups xD
What I did is look at lens source code for the exact metrics queried on prometheus, port forward your prometheus/victoriametrics port, query /metrics (or look in grafana in explore) and make sure they are available.
Once you do that check that your cluster monitoring configuration in Lens is correct, I had to set it to Helm and provide the service by hand which in my case is: monitoring-system/vmsingle-vmsingle:8429
Once that was done I disconnected and connected back to the cluster and I had my graphs (Lens does not use the new metrics config until your restart or reconnect to the cluster).

Switching Lens > Setting > Prometheus > Use pre-installed Prometheus service for metrics. Please refer to the guide for possible configuration changes. Prometheus installation method. > Helm + monitoring/vmsingle-vm-victoria-metrics-k8s-stack:8429 worked for me but only partly: I can see requests/limits & capacity now but not the Usage & the main Metrics windows is saying Metrics not available at the moment

It's because requests/limits don't depend on prometheus/VM. Part of k8s
describe.
On Tue, Aug 10, 2021 at 8:29 PM vainkop @.***> wrote:

I am using the victoriametrics operator with node-exporter and
kube-state-metrics installed directly from yaml manifests so it will be
hard to compare our setups xD
What I did is look at lens source code for the exact metrics queried on
prometheus, port forward your prometheus/victoriametrics port, query
/metrics (or look in grafana in explore) and make sure they are available.
Once you do that check that your cluster monitoring configuration in Lens
is correct, I had to set it to Helm and provide the service by hand which
in my case is: monitoring-system/vmsingle-vmsingle:8429
Once that was done I disconnected and connected back to the cluster and I
had my graphs (Lens does not use the new metrics config until your restart
or reconnect to the cluster).
Sounds like switching to helm & pointing to the vm service should work.
I'll try & report.
I am using the victoriametrics operator with node-exporter and
kube-state-metrics installed directly from yaml manifests so it will be
hard to compare our setups xD
What I did is look at lens source code for the exact metrics queried on
prometheus, port forward your prometheus/victoriametrics port, query
/metrics (or look in grafana in explore) and make sure they are available.
Once you do that check that your cluster monitoring configuration in Lens
is correct, I had to set it to Helm and provide the service by hand which
in my case is: monitoring-system/vmsingle-vmsingle:8429
Once that was done I disconnected and connected back to the cluster and I
had my graphs (Lens does not use the new metrics config until your restart
or reconnect to the cluster).
Switching Lens > Setting > Prometheus > Use pre-installed Prometheus
service for metrics. Please refer to the guide for possible configuration
changes. Prometheus installation method. > Helm +
monitoring/vmsingle-vm-victoria-metrics-k8s-stack:8429 worked for me but
only partly: I can see requests/limits & capacity now but not the Usage &
the main Metrics windows is saying Metrics not available at the moment
[image: image]
https://user-images.githubusercontent.com/28118190/128906319-178367fe-d0b3-4688-96db-54edfddb9334.png
[image: image]
https://user-images.githubusercontent.com/28118190/128906371-aa0ea776-7db4-4586-adb4-884ea0083ceb.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lensapp/lens/issues/1942#issuecomment-896176336, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABEKHP7TCVNGRBTFS75W2DT4FOYJANCNFSM4V6D3PVQ
.

It's because requests/limits don't depend on prometheus/VM. Part of k8s describe.
…
On Tue, Aug 10, 2021 at 8:29 PM vainkop @.***> wrote: I am using the victoriametrics operator with node-exporter and kube-state-metrics installed directly from yaml manifests so it will be hard to compare our setups xD What I did is look at lens source code for the exact metrics queried on prometheus, port forward your prometheus/victoriametrics port, query /metrics (or look in grafana in explore) and make sure they are available. Once you do that check that your cluster monitoring configuration in Lens is correct, I had to set it to Helm and provide the service by hand which in my case is: monitoring-system/vmsingle-vmsingle:8429 Once that was done I disconnected and connected back to the cluster and I had my graphs (Lens does not use the new metrics config until your restart or reconnect to the cluster). Sounds like switching to helm & pointing to the vm service should work. I'll try & report. I am using the victoriametrics operator with node-exporter and kube-state-metrics installed directly from yaml manifests so it will be hard to compare our setups xD What I did is look at lens source code for the exact metrics queried on prometheus, port forward your prometheus/victoriametrics port, query /metrics (or look in grafana in explore) and make sure they are available. Once you do that check that your cluster monitoring configuration in Lens is correct, I had to set it to Helm and provide the service by hand which in my case is: monitoring-system/vmsingle-vmsingle:8429 Once that was done I disconnected and connected back to the cluster and I had my graphs (Lens does not use the new metrics config until your restart or reconnect to the cluster). Switching Lens > Setting > Prometheus > Use pre-installed Prometheus service for metrics. Please refer to the guide for possible configuration changes. Prometheus installation method. > Helm + monitoring/vmsingle-vm-victoria-metrics-k8s-stack:8429 worked for me but only partly: I can see requests/limits & capacity now but not the Usage & the main Metrics windows is saying Metrics not available at the moment [image: image] https://user-images.githubusercontent.com/28118190/128906319-178367fe-d0b3-4688-96db-54edfddb9334.png [image: image] https://user-images.githubusercontent.com/28118190/128906371-aa0ea776-7db4-4586-adb4-884ea0083ceb.png — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1942 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABEKHP7TCVNGRBTFS75W2DT4FOYJANCNFSM4V6D3PVQ .

It depends on metrics server which I have installed & it worked until I removed community kube-prometheus-stack & installed VM.
One thing I've noticed is that smth similar to original metrics server was installed with VM helm chart called vm-kube-state-metrics so maybe they're in conflict?
That's how I've installed the metrics-server initially:
kubectl config set-context --current --namespace=kube-system
helm repo add bitnami https://charts.bitnami.com/bitnami
helm repo update
helm upgrade -i metrics-server bitnami/metrics-server --set apiService.create=true

I've scaled down the original metric-server to 0 & reinstalled VM but it didn't help to bring back the main window metrics.
But I can see those metrics if I open any individual deployment or a node including Usage.

And that's what I see in kubernetes-compute-resources-cluster Grafana dashboard which came with VM & I didn't configure

Here's the gist with my helm-values.yml in case someone needs it: https://gist.github.com/vainkop/d8ed28f85f3b87fa53ec4269ad13b460#file-victoriametrics-helm-values-yml


use custom formatter  formating gorm log

when I define my formatter for gorm log , the entry.Message field's value like the following. It contains sql, file, line, used time, query statement, [] 16.
Now I still try to find out why it like this.
version info

go: version go1.13.4 darwin/amd64
logrus: 1.4.2
gorm: 1.9.11

sql{YourCallerFilePath}:{Line}{usedTime}ms{Query}[] 16

// exampe
sql/Users/A/B/C/D.go:34580.463646msSELECT * FROM YOUR_TABLE_NAME[] 16

after I use debug, i find the following information:
entry.go:266-268
func (entry *Entry) Log(level Level, args ...interface{}) {
	if entry.Logger.IsLevelEnabled(level) {
		entry.log(level, fmt.Sprint(args...))
	}
}

the args: type: []interface{}
0: "sql"
1: "/Users/xxxx/xxx.go:100"
2: 78950332  (used time the same to 80.463646ms )
3: SELECT DISTINCT A AS a,B AS b FROM `t`   ORDER BY b DESC
4: nil
5: 16

after call "entry.log(level, fmt.Sprint(args...))"  the Message field the same to above

in the gorm , i find the following code
func (s *DB) slog(sql string, t time.Time, vars ...interface{}) {
   if s.logMode == detailedLogMode {
   	s.print("sql", fileWithLineNum(), NowFunc().Sub(t), sql, vars, s.RowsAffected)
   }
}

so,  gorm passing an array with type []interface{}, and logrus calling fmt.Sprint(args...), then the message output like above.

hello @Turing-Chu.
It's not quite clear from your issue, what are you trying to do ?

If you want to have each paramater of the gorm print in a dedicated field, I guess you need to write a wrapping function/struct somehow

thanks for your answer.


If there is no url secret, ignore the test

https://github.com/scottrobertson/fintech-to-ynab/issues/30#issuecomment-311615181

This seems risky. Should we not be testing both cases explicitly?

I've added more tests. Now, if there is no secret, then any call should succeed, if there is, then calls succeed ony when the valid secret is passed in the url query string


Nice :)

Nice one @pyloque :)
captain will be featured in our next RedisWeekly!

Wow, so surprised!  Thanks!


merge package template from Kronos-Tools/npm-package-template

Updated standard to latest version

Codecov Report

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

@@           Coverage Diff           @@
##           master     #128   +/-   ##
=======================================
  Coverage   83.33%   83.33%
=======================================
  Files           1        1
  Lines          54       54
=======================================
  Hits           45       45
  Misses          9        9

Continue to review full report at Codecov.

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


Web3Auth Package Signer BigInt Problems

Summary
In the web3auth extension directory the hashObject Signing a transaction errors when a message contains bigIntValues because they cannot be serialized.
Error
Failed to broadcast: TypeError: BigInt value can't be serialized in JSON
    hashObject utils.js:67
    signDirect signer.js:68
    signDirect signingstargateclient.js:282
    sign signingstargateclient.js:230
    tx useTx.tsx:84
    handleConfirm ConfirmationForm.tsx:89

Reproduce

install and run dev

git clone https://github.com/chalabi2/manifest-app
cd manifest-app
git checkout main
yarn install
yarn run dev

connect via web3auth social wallet option

visit /factory/create

attempt to create a token

Working solution
Simply check if there are any bigInt values in the hashObject
export const hashObject = (object) => {
    const replacer = (_, value) => {
      if (typeof value === 'bigint') {
        return value.toString();
      }
      return value;
    };

    return Buffer.from(sha256(toUtf8(JSON.stringify(object, replacer))));
  };

#489 is a potential fix


#[near_bindgen] macro is not able to detect that func is public when implemented for a trait on the contract for simulation testing

I found this "issue" while trying to integrate simulation tests ... my contract implements traits, which means that the funcs are implied to be public, however the #[near_bindgen] macro is not able to detect that the func are public, e.g.,
 pub trait ContractOwner

 { fn owner_id(&self) -> AccountId; }

#[near_bindgen]
 impl ContractOwner for StakeTokenContract {
 fn owner_id(&self) -> AccountId

 { self.owner_id.clone() }

 ...

 }

// sim test code

let res = view!(contract.owner_id());

let res = view!(contract.owner_id());

| ^^^^^^^^^^^^^ method not found in StakeTokenContractContract

I can get it to work if the contract does not implement the trait:

#[near_bindgen]

StakeTokenContract {

pub fn owner_id(&self) -> AccountId { self.owner_id.clone() }

...
}

The near_bindgen does not appear to be aware that the contract is implementing a trait.
I am using:
[dependencies]
near-sdk =

{ git = "https://github.com/near/near-sdk-rs", tag = "2.3.0" }

[dev-dependencies]
near-sdk-sim =

{ git = "https://github.com/near/near-sdk-rs", tag = "2.3.0" }

I'm a little confused with your example.  The method in question is owner_id, but then in your view call you call owner_balance.  Is this a typo?

I'm a little confused with your example.  The method in question is owner_id, but then in your view call you call owner_balance.  Is this a typo?

I'm a little confused with your example. The method in question is owner_id, but then in your view call you call owner_balance. Is this a typo?

correct - I fixed the example

I'm a little confused with your example. The method in question is owner_id, but then in your view call you call owner_balance. Is this a typo?

correct - I fixed the example

Hmm, well if you cargo install wasm-nm and then do wasm-nm -e path/to/file.wasm do you see owner_id listed?
Do you have branch where I can see this in action?

Hmm, well if you cargo install wasm-nm and then do wasm-nm -e path/to/file.wasm do you see owner_id listed?
Do you have branch where I can see this in action?

The problem is not in the wasm file. When I deploy the contract, it works just fine. The problem is with code generated by wasm_bindgen does not pick up the method visibility:
https://github.com/oysterpack/oysterpack-near-stake-token/blob/main/contract/tests/account_management.rs
#[test]
fn near_sdk_issue_262_near_bindgen_does_not_detect_pub_visibility_from_trait() {
    let ctx = test_utils::create_context();
    let contract = ctx.contract;

    // works because public method is defined directly on the contract
    let res = view!(contract.get_staking_pool_id());
    assert!(res.is_ok());

    // `staking_pool_id` is defined on the `StakingService` trait which the contract implements
    // but the method is not publicly visible on `StakeTokenContractContract`
    // let res = view!(contract.staking_pool_id());  // will not compile

    // but it is there if onvoked with the "low level" approach:
    let res = ctx.contract_operator.view(PendingContractTx::new(
        &contract.user_account.account_id,
        "staking_pool_id",
        json!({}),
        true,
    ));

    assert!(res.is_ok());
    let staking_pool_id: String = res.unwrap_json();
    assert_eq!(staking_pool_id, "astro-stakers.poolv1.near");
}

The problem is not in the wasm file. When I deploy the contract, it works just fine. The problem is with code generated by wasm_bindgen does not pick up the method visibility:
https://github.com/oysterpack/oysterpack-near-stake-token/blob/main/contract/tests/account_management.rs
#[test]
fn near_sdk_issue_262_near_bindgen_does_not_detect_pub_visibility_from_trait() {
    let ctx = test_utils::create_context();
    let contract = ctx.contract;

    // works because public method is defined directly on the contract
    let res = view!(contract.get_staking_pool_id());
    assert!(res.is_ok());

    // `staking_pool_id` is defined on the `StakingService` trait which the contract implements
    // but the method is not publicly visible on `StakeTokenContractContract`
    // let res = view!(contract.staking_pool_id());  // will not compile

    // but it is there if onvoked with the "low level" approach:
    let res = ctx.contract_operator.view(PendingContractTx::new(
        &contract.user_account.account_id,
        "staking_pool_id",
        json!({}),
        true,
    ));

    assert!(res.is_ok());
    let staking_pool_id: String = res.unwrap_json();
    assert_eq!(staking_pool_id, "astro-stakers.poolv1.near");
}

I moved the sample code to a separate file: https://github.com/oysterpack/oysterpack-near-stake-token/blob/main/contract/tests/near_sdk_rs_issue_262.rs

I moved the sample code to a separate file: https://github.com/oysterpack/oysterpack-near-stake-token/blob/main/contract/tests/near_sdk_rs_issue_262.rs

sim tests deprecated and no longer need to use those types for workspaces


Heap and Stack Memory Errors in Java

Proposed title of the article
Heap and Stack Memory Errors in Java
Introduction paragraph (2-3 paragraphs):
Java's virtual machine oversees memory allocation. It separates the memory into heap and stack portions. Stack is only used for the method or methods presently running, however, Java Heap Space is used throughout the application. All items are produced in the Heap Space, but only references to those things are stored in the Stack. A LIFO (last-in, first-out) memory allocation system is used to access the Stack.
Every time we call a method, the stack memory is freed. In the event that your methods continue to stay in the stack, the stack will be full, and we will be unable to push because we will receive the java.lang.StackOverflowError error from the JVM. java.lang.OutOfMemoryError will be thrown by the JVM if there is not enough heap memory to accommodate the number of new objects being created. This tutorial will go into great detail about all of that.
Key takeaways:

Stack and Heap memory.
Stack memory in Java.
Heap Memory Error.

References:
N/A

Hello @AshaIha  and thank you for submitting your topic suggestion.
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

Thank you for submitting your topic.
After some careful consideration, it struck us that this topic may be a bit over-saturated throughout other blog sites and official documentation.
We believe this is the best way for students to build a great portfolio (for potential employers) is by building what does not exist and what can provide the most value.
Please feel free to suggest an alternate topic to explore. 🚀


Added fallbackLocale

[x] $localesUC/LC duplicity bugfix
[x] Added UC/LC locale tests
[x] Added feature logic
[x] Added feature tests
[x] Added feature docs
[x] Added feature examples

How do we use this? I also need fallbackLocale

@ralyodio https://github.com/sveltekit-i18n/lib/tree/master/examples/fallback-locale


site column empty in workqueue link

https://github.com/CMSCompOps/WmAgentScripts/issues/400
https://cmsweb.cern.ch/couchdb/workqueue/_design/WorkQueue/_rewrite/elementsInfo?request=vlimant_task_HIG-RunIIFall17wmLHEGS-01995__v1_T_181030_224109_3526
https://cmsweb.cern.ch/couchdb/workqueue/_design/WorkQueue/_rewrite/elementsInfo?request=vlimant_task_HIG-RunIIFall17wmLHEGS-02954__v1_T_181015_122154_4974
These two requests were in the system for a long time. I had a look at these links and they had no site under the site column. @amaltaro as you said, if the column is empty, then it means there is no common site between sitewhitelist and data location and in case there is no input data for MC, it should be full of sites. Can you please correct me if I understood something wrong.
@vlimant @thongonary FYI

the WQE are gone, since the requests are rejected now : please update if you find any other such workflow in such situation

They are gone because we rejected them but the cloned workflows should help.
http://dmytro.web.cern.ch/dmytro/cmsprodmon/workflows.php?prep_id=task_HIG-RunIIFall17wmLHEGS-01995
http://dmytro.web.cern.ch/dmytro/cmsprodmon/workflows.php?prep_id=task_HIG-RunIIFall17wmLHEGS-02954

the empty "Sites" in the WQE table is normal
see https://cmsweb.cern.ch/couchdb/workqueue/_design/WorkQueue/_rewrite/elementsInfo?request=pdmvserv_task_HIG-RunIIFall17wmLHEGS-02380__v1_T_190216_082922_9801 running just fine.
the others are not being picked up because of priority

@amaltaro please close if you agree

Yes, that's correct.
It looks like Sites column shows where your Inputs data is located, and in the case where there is not input dataset (empty dict for Inputs), then nothing is shown:
https://github.com/dmwm/WMCore/blob/master/src/couchapps/WorkQueue/_attachments/js/ElementInfoByWorkflow.js#L52
When the element has input dataset but it's not available anywhere, then Sites would show No sites.
I'm closing this issue since there is nothing wrong.


fix: support reading type arrow

Addresses #135

Based on this comment https://github.com/rstudio/pins-python/issues/135#issuecomment-1161854818 switching "arrow" to be the go-to type, deprecating "feather".

@juliasilge do you mind double checking this (either the code or sanity checking it does what we discussed!)?
I set pins to...

pin_write and pin_read type "arrow"
pin_read type "feather"
pin_write "feather", but only after ...

printing a deprecation warning
switching the type to "arrow" (so the pin is technically saved as an arrow pin type)


config function misbehaving

Calling ox.config() lets you set the values of the global settings package-wide and resets any un-passed settings to their original default values. Per its docstring:
Configure OSMnx by setting the default global settings' values.

Any parameters not passed by the caller are set to their default values.

But I noticed there is one odd exception to this for the useful_tags_node and useful_tags_path settings, which determine the OSM tags to add as graph node/edge attributes respectively. These settings are initially set the same way as the others, but then immediately overwritten with a superset of values:
https://github.com/gboeing/osmnx/blob/59f6a8d61e69cda6e5d9112fbdbaf3d4648e7b23/osmnx/utils.py#L182-L185
This results in weird behavior like this:
import osmnx as ox
print(ox.settings.useful_tags_node)
# ['ref', 'highway']

ox.config(use_cache=True)
print(ox.settings.useful_tags_node)
# ['version', 'timestamp', 'uid', 'id', 'changeset', 'lon', 'user', 'highway', 'ref', 'lat']

Using ox.config to turn on caching shouldn't change other settings from their default values. We need to prevent this, while offering a straightforward way for users looking to export to XML (who want to add those additional OSM tags/attributes during graph creation).
@mxndrwgrdnr this is likely relevant to your interests.

See the fix in #490 (which also renames the confusingly-named setting useful_tags_path to the more appropriate useful_tags_way) for suggested configuration if you're creating a graph to save to .osm XML file later.


Fix typo isIquals to isEquals

Fixed #228

I think it's perfect, I'm going to review it and update, thank you very much

Thanks.
Since the key name has changed, please be careful about versioning.


Fixed long long support

This is the fix for #12.  A separate real and integer variables were added. First prv_parse_number assumes the value to be an integer until it finds a decimal point, at which point the value is casted into a real and processed from there.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Calc 99.99% vs 99.999999%

Just curious. I know the almost 100% value is to handle cross-browser sub-pixel rounding inconsistencies, but I'm not sure why you use 99.99% when there is no gutter and 99.999999% when there is. Why not use one or the other for both?

These numbers are the result of having various versions of all the browsers open and trying out variations of 99.xxxxxxxxxxxxxxxxx%. Some browsers would kick blocks down into the next row when these numbers were set to anything else. Are they causing you any problems?

Nope. Just wondering. Thanks!


agent stops without apparent cause

I am having issues with a bosh-lite deployed to a vsphere bosh environment (that is, it was created with bosh deploy using -o misc/bosh-dev.yml). I'm trying to debug it.
I redeployed the VM and tailed the /var/vcap/bosh/log/current and eventually it just stops with this last line:
2017-10-29_22:38:19.80190 [main] 2017/10/29 22:38:19 ERROR - Agent exited with error: received signal (terminated): stopping now

There is nothing preceding this line that indicates why the agent stopped. The agent never restarts (shouldn't the local process monitoring software restart the agent?)
Eventually the parent BOSH gets cranky that the bosh-agent stopped (and never restarted) and resurrects the bosh-lite vm (which means it stops being useful for 7 minutes).
$ bosh tasks --all
Using environment 'https://<IP_ADDRESS>:25555' as user 'admin' (openid, bosh.admin)

ID       State       Started At                    Last Activity At              User  Deployment    Description   Result
4567676  processing  Sun Oct 29 23:05:07 UTC 2017  Sun Oct 29 23:05:07 UTC 2017  hm    bosh-lite-10  scan and fix  -

1 tasks

$ bosh task 4567676
Task 4567676 | 23:06:15 | Applying problem resolutions: VM for 'bosh/83887585-6b46-468f-b913-26434a36ce23 (0)' with cloud ID 'vm-9f994659-4a27-4e43-a177-358c1c4f1b98' is not responding. (unresponsive_agent 2308): Recreate VM and wait for processes to start

Task 4567676 Started  Sun Oct 29 23:05:07 UTC 2017
Task 4567676 Finished Sun Oct 29 23:12:11 UTC 2017
Task 4567676 Duration 00:07:04

There is about 7:20 between scan and fix task below, and given that it takes 7:04 minutes to resurrect the VM, the agent is surviving only 15 seconds after it finishes deploying all the BOSH/bosh-lite jobs.
$ bosh tasks --recent -a | grep done | grep scan
4567689 done      	Sun Oct 29 23:12:28 UTC 2017	Sun Oct 29 23:12:34 UTC 2017	hm   	bosh-lite-10	scan and fix                           	scan and fix complete
4567676 done      	Sun Oct 29 23:05:07 UTC 2017	Sun Oct 29 23:12:11 UTC 2017	hm   	bosh-lite-10	scan and fix                           	scan and fix complete
4567660 done      	Sun Oct 29 22:56:07 UTC 2017	Sun Oct 29 23:02:39 UTC 2017	hm   	bosh-lite-10	scan and fix                           	scan and fix complete

How can I debug this issue? It's very consistent - even though using fresh vms each time.  I am waiting patiently for the agent to die again.
Update: I'm also trying bosh cloud-check (after turning off resurrector) with "recreate vm without waiting for processes". Agent doesn't seem to to die after bosh cloud-check recreation.

By default, bosh-lite will disable the agent since they're typically used as throwaway environments. The bosh-lite.yml ops file configures the disable_agent job from os-conf release. If you're managing these with another directory and not create-env, you may want to remove it.

@dpb587-pivotal thanks very much for pointing that out.
Does this mean that I'm the only one running bosh-lites for CI? Or am I the only one using bosh deploy to run bosh-lites (so they are resurrected, etc)? How is everyone else doing CI with BOSH - just provisioning lots of VMs and paying the cost to AWS/Google?

Can we add the following to misc/bosh-dev.yml?
- type: delete
  path: /instance_groups/name=bosh/jobs/name=disable_agent

Sounds like a good idea to me. Perhaps name=disable_agent? in case it's already removed.


Implementing counting method for LSTM

Hi
currently no counting method for LSTM layer! Please put it on road map.
thanks

Pull #78 supports it. Please have a check.


Endpoint list needs updating or Maybe separate page for GCC

The GCC Power Platform Endpoints/URLs are not included in this document, even though it states it is for Worldwide and GCC.  Maybe since GCC uses different URLs for the Power Platform it should be on a separate page from https://docs.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide&source=docs#feedback.
Or other option is to add the GCC PowerPlatform URLs to the current page..
The GCC Endpoints can be found https://docs.microsoft.com/en-us/power-platform/admin/powerapps-us-government#power-apps-us-government-service-urls

@JoeDavies-MSFT Please help us in resolving this issue as it is a Highly Structured document. Thanks

@Matt-Mueller-MSFT Starting an internal email thread to discuss this issue. Thanks for letting us know.


contrib.rnn.ConvLSTMCell: zero_state has wrong size if cell has skip connections

There seems to be a bug in how ConvLSTMCell handles its states:
When calculating the output size, ConvLSTMCell has one more channel dimension (in general, as many more channels as there are input channels) than what was given as output_channels.
This is only if skip_connection was True at initialization, and makes sense (the input is concatenated to the output --> n_channels_out = n_channels_in + original_n_channels_out).
Also, when creating a cell and applying it to inputs and a state:
Minimal reproducible example
cell = tf.contrib.rnn.ConvLSTMCell(conv_ndims=2, input_shape=[80,80,1], output_channels=2,
                                               kernel_shape=[5,5], skip_connection=True)
state= cell.zero_state(10, dtype=tf.float32)
output, next_state = cell(last_outputs, states)

--> next_state is an LSTMStateTuple with shapes (?, 80, 80, 2) and (?, 80, 80, 3). Still makes sense since it stores its hidden state as well as outputs and re-uses them in the next timestep, and the outputs gained an additional channel. But cell.zero_state() will have other shapes ( (?, 80, 80, 2) and (?, 80, 80, 2).)
The zero_state() calculation seems wrong; the code reads (in contrib/rnn/python/ops/rnn_cell.py):
    self._total_output_channels = output_channels
    if self._skip_connection:
      self._total_output_channels += self._input_shape[-1]

    state_size = tensor_shape.TensorShape(
        self._input_shape[:-1] + [self._output_channels])
    self._state_size = rnn_cell_impl.LSTMStateTuple(state_size, state_size)
    self._output_size = tensor_shape.TensorShape(
        self._input_shape[:-1] + [self._total_output_channels])

Shouldn't it be not rnn_cell_impl.LSTMStateTuple(state_size, state_size), but rnn_cell_impl.LSTMStateTuple(state_size, self._output_size) ?
Funnily, it does not disturb the cell to be called with a state of size (80, 80, 2)   - but for me it raised an error when called again with its next state which has size (80, 80, 3). For completeness, this error was (and this error is not my problem, my problem was inconsistency of shapes of the cell states):

Traceback (most recent call last):
File "/home/me/programs/pycharm-community-2016.1.1/helpers/pydev/_pydevd_bundle/pydevd_comm.py", line 1079, in do_it
result = pydevd_vars.evaluate_expression(self.thread_id, self.frame_id, self.expression, self.doExec)
File "/home/me/programs/pycharm-community-2016.1.1/helpers/pydev/_pydevd_bundle/pydevd_vars.py", line 352, in evaluate_expression
Exec(expression, updated_globals, frame.f_locals)
File "/home/me/programs/pycharm-community-2016.1.1/helpers/pydev/_pydevd_bundle/pydevd_exec2.py", line 3, in Exec
exec(exp, global_vars, local_vars)
File "", line 1, in
File "/home/me/miniconda3/envs/tf36/lib/python3.6/site-packages/tensorflow/python/ops/rnn_cell_impl.py", line 232, in call
return super(RNNCell, self).call(inputs, state)
File "/home/me/miniconda3/envs/tf36/lib/python3.6/site-packages/tensorflow/python/layers/base.py", line 717, in call
outputs = self.call(inputs, *args, **kwargs)
File "/home/me/miniconda3/envs/tf36/lib/python3.6/site-packages/tensorflow/contrib/rnn/python/ops/rnn_cell.py", line 2113, in call
4 * self._output_channels, self._use_bias)
File "/home/me/miniconda3/envs/tf36/lib/python3.6/site-packages/tensorflow/contrib/rnn/python/ops/rnn_cell.py", line 2207, in _conv
"kernel", filter_size + [total_arg_size_depth, num_features], dtype=dtype)
File "/home/me/miniconda3/envs/tf36/lib/python3.6/site-packages/tensorflow/python/ops/variable_scope.py", line 1317, in get_variable
constraint=constraint)
File "/home/me/miniconda3/envs/tf36/lib/python3.6/site-packages/tensorflow/python/ops/variable_scope.py", line 1079, in get_variable
constraint=constraint)
File "/home/me/miniconda3/envs/tf36/lib/python3.6/site-packages/tensorflow/python/ops/variable_scope.py", line 417, in get_variable
return custom_getter(**custom_getter_kwargs)
File "/home/me/miniconda3/envs/tf36/lib/python3.6/site-packages/tensorflow/python/ops/rnn_cell_impl.py", line 235, in _rnn_get_variable
variable = getter(*args, **kwargs)
File "/home/me/miniconda3/envs/tf36/lib/python3.6/site-packages/tensorflow/python/ops/variable_scope.py", line 394, in _true_getter
use_resource=use_resource, constraint=constraint)
File "/home/me/miniconda3/envs/tf36/lib/python3.6/site-packages/tensorflow/python/ops/variable_scope.py", line 738, in _get_single_variable
found_var.get_shape()))
ValueError: Trying to share variable conv_lstm_cell/kernel, but specified shape (5, 5, 4, 8) and found shape (5, 5, 3, 8).

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
Yes.
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Linux Ubuntu 14.04
TensorFlow installed from (source or binary):
binary
TensorFlow version (use command below):
1.8.0
Python version:
3.6
Bazel version (if compiling from source):

GCC/Compiler version (if compiling from source):

CUDA/cuDNN version:
(using CPU version)
GPU model and memory:
(using CPU version)
Exact command to reproduce:
See description above
Mobile device:
N/A

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Mobile device

Sure...

Thank you for the detailed report. That seems reasonable! Feel free to contribute a PR.

Hi, @su-si .
I want to know if the tf.nn.dynamic did not suport the ConvLSTMCell ?

Hi @songzenghui ,
In my case I couldn't use a dynamic_rnn, so I don't know. (I had a problem with changing state sizes using ConvLSTMCell in a tf.while loop.) So just give it a try :) dynamic_rnn is probably the most frequent use case, so it will probably work.
The code to dynamic_rnn looks a bit complicated, I don't see right away whether they circumvent the changing state size within a while loop. It might be they do the first step outside of the loop, then both old and 'fixed' versions should work fine with dynamic_rnn.
Could still be that my suggested fix destroys compatibility with dynamic_rnn.


Parsing fails for some Int64 values

Parsing seems to fail for all Int64 values x where MaxInt < x <= 2*MaxInt + 1. Other values work fine. The problem seems to be that FLook.HI = 0 and therefore FLook.I is used instead of FLook.L. Unfortunately I don't know how to fix it so I can't provide you with a pull request.
var
  lInput: String;
  lInt64: Int64;
  lJsonObject: TJsonObject;
begin
  lInt64 := 2 * Int64(MaxInt);
  lInput := Format('{ "num": %d }', [lInt64]);

  lJsonObject := TJsonObject.Parse(lInput) as TJsonObject;
  try
    Writeln(lInput); // { "num":<PHONE_NUMBER> }
    Writeln(lInt64); //<PHONE_NUMBER>
    Writeln(lJsonObject.L['num']); // -2
  finally
    lJsonObject.Free;
  end;
end;

This is Delphi XE5.

Thanks for the bug report. This is fixed in 6796437dcbfdb227b1b40e04b1161499cb239953

Thank you for the very quick fix :+1:


Changes made by rounak

Checklist
Required changes:

[done] Center the description (Line 17 in HTML file) using a single change in CSS
[done] Fix JS so that when the search is executed, the search engine is not present in query
[done] Add Google Drive, Google Slides and Google Sheets as a provider

Optional changes:

[ ] Add other search providers (GitHub, Spotify, etc)
[ ] Additional CSS styling (as you like)

Link to hosted site: multisearch

Good work, however in the markdown when you want to select a checkbox all you have to do is put an x inside the square brackets. Minor unrelated issue tho, overall executed well


Strengthen SystemRandomNumberGenerator docs.

SE-0202 claimed that it would add a secure RNG for all platforms, but
the documentation for SystemRandomNumberGenerator contains a few weasel
phrases that imply that the strength may not meet cryptographic
requirements on all platforms.
This language makes the tool worse than useless, as any unexpected
future platform may implement a weak random number generator. We should
make the documentation reflect the spirit of SE-0202 and have it clearly
state that all implementations will be suitable for cryptographic
applications.
While we're here, I added some documentation to cover the Windows
implementation, which was missed previously.

@swift-ci Please smoke test

@Lukasa @natecook1000 What do y'all want to do with this?

I believe the forum consensus was not to move forward on this.

Alright.  Thank you for taking the time to clarify this.  I’m going to close this out.


Fix E/AudioRecord: start() status -1 by starting the recorder immediately

By moving recorder.startRecording(); outside of the Thread this prevents the recorder from going stale and crashing the app randomly. Why exactly the recorder will just crash if you wait to long to connect is unknown to me but when you immediately start it the app is much more reliable (to the point it has not crash yet under my tests)
I replaced the "exit the app" on disconnect with a restart of the socket to allow for the service to handle disconnects and not require the entire restart procedure just to reopen the socket
And added logging so its possible to monitor if the socket is ready to prevent connecting to early for applications that are sensitive to expecting the connection to be ready immediately (cough ffmpeg)
My revision is mainly to help with my automated recording software that I use to record XM radio but i think it could help the project in general

I'm sorry for late to checking your pull request.
Thanks for contributing!
Java is not my forte, so I am very happy to have better suggestions from others who are more familiar with Java.
Thank you.


[tests-only][full-ci] test: Test coverage for bug #7060

Description

This PR covers the test for the bug report #7060
Related Issue

Related to: https://github.com/owncloud/ocis/issues/9948
Coverage for: https://github.com/owncloud/ocis/issues/7060

Motivation and Context

How Has This Been Tested?

Locally
CI

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[x] Tests only (no source changes)

Checklist:

[ ] Code changes
[ ] Unit tests added
[ ] Acceptance tests added
[ ] Documentation ticket raised:

Sorry, I will close this one.
this will be done in PR https://github.com/owncloud/ocis/pull/10078


Myelin oligodendrocyte glycoprotein (MOG) antibody-associated disease (MOGAD)

Label
Myelin oligodendrocyte glycoprotein (MOG) antibody-associated disease (MOGAD)
Synonyms
MOGAD
Synonym type
exact
Definition
Request to add a new disease:
Myelin oligodendrocyte glycoprotein (MOG) antibody-associated disease (MOGAD) is an inflammatory demyelinating disease of the central nervous system (CNS) with the presence of conformation-sensitive antibodies against MOG. The spectrum of MOGAD includes monophasic/relapsing optic neuritis, myelitis, neuromyelitis optica spectrum disorder (NMOSD) phenotype without aquaporin 4 (AQP4) antibodies, acute/multiphasic demyelinating encephalomyelitis (ADEM/MDEM)-like presentation, and brainstem and cerebral cortical encephalitis. The prevalence of MOGAD is approximately 1.3–2.5/100,000.  https://www.ncbi.nlm.nih.gov/pmc/articles/PMC10542411/
NOTE:  I noticed that MONDO list the following that are included in MOGAD:

isolated optic neuritis with anti-MOG antibodies (MONDO:0035668)
acute transverse myelitis with anti-MOG antibodies (MONDO:0035666)
acute disseminated encephalomyelitis with anti-MOG antibodies (MONDO:0035669)  and also
neuromyelitis optica spectrum disorder with anti-MOG antibodies (MONDO:0035664)

From the same source: "The MOG antibodies were initially detected primarily in a subgroup of patients with acute/multiphasic demyelinating encephalomyelitis (ADEM/MDEM) (2, 3). Subsequent studies showed that MOG antibodies were also present in patients with optic neuritis, myelitis, neuromyelitis optica spectrum disorder (NMOSD) phenotype without aquaporin 4 (AQP4) antibodies, and brainstem and cerebral cortical encephalitis; Recently, the international diagnostic criteria for MOGAD were published (12), and the diagnosis of MOGAD is now made based on the presence of at least one of the core clinical demyelinating events (optic neuritis, myelitis, ADEM, cerebral monofocal or polyfocal deficits, brainstem or cerebellar deficits, and cerebral cortical encephalitis often with seizures), a positive MOG-IgG test, and the exclusion of alternative diagnoses including MS."
See also: MOGAD is now recognized as an autonomous, antibody-mediated inflammatory demyelinating disorder, most frequently with relapsing course and a variety of clinical manifestations. As it is a rare condition, researchers should still focus on the different aspects of the disease: its pathophysiological mechanisms, the identification of markers of the disease status and outcome, the incidence in various regions and patients populations. All of the above should form the basis for development and elaboration of the MOGAD diagnosis criteria to be ultimately approved by experts. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7795410/
We have a NORD report.
Thank you, Gioconda Alyea
Parent term
inflammatory demyelinating disease of the central nervous system
Children term(s)
No response
ORCID Identifier
0000-001-9310-0163
Website URL
No response
Additional comments
No response

Dear @galyea123,
Thank you for reaching out to the Mondo Disease Ontology, part of the Monarch Initiative!
We have received your ticket and will review it as soon as possible.
If you have any additional information or updates relevant to your inquiry, please add them in a comment on this ticket. Your input is valuable in helping us understand and resolve the issue effectively.
Thank you for your patience and for your contributions to Mondo!
Sincerely,
The Mondo Team

Hi!  Any updates in this request?  Thank you! Gioconda Alyea

Hi Sabrina!  Just wanted to clarify if this term was added (I saw the GitHub ticket but I could not tell...).  I apologize for bothering you!
Thank you!! Gioconda

From: Sabrina Toro @.>
Sent: Wednesday, July 31, 2024 3:19 PM
To: monarch-initiative/mondo @.>
Cc: Gioconda Alyea @.>; Mention @.>
Subject: Re: [monarch-initiative/mondo] Myelin oligodendrocyte glycoprotein (MOG) antibody-associated disease (MOGAD) (Issue #7776)
Closed #7776https://github.com/monarch-initiative/mondo/issues/7776 as completed via 01e178chttps://github.com/monarch-initiative/mondo/commit/01e178ce4420e52827bc71863b9ddfeef852b3c5.
—
Reply to this email directly, view it on GitHubhttps://github.com/monarch-initiative/mondo/issues/7776#event-13714976071, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A4QAWD3TYTNBZC5GHEQU7WDZPE2DNAVCNFSM6AAAAABIXLP2RKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTG4YTIOJXGYYDOMI.
You are receiving this because you were mentioned.Message ID: @.***>
Any review, use, distribution or disclosure by others is strictly prohibited.

No bothering at all @galyea123. :-)
Yes, this term has been added: the PR was merged earlier today. It will be available in our next release (scheduled on August 6)
Best, Sabrina

[heart]         Gioconda Alyea reacted to your message:

From: Sabrina Toro @.>
Sent: Wednesday, July 31, 2024 8:20:12 PM
To: monarch-initiative/mondo @.>
Cc: Gioconda Alyea @.>; Mention @.>
Subject: Re: [monarch-initiative/mondo] Myelin oligodendrocyte glycoprotein (MOG) antibody-associated disease (MOGAD) (Issue #7776)
No bothering at all @galyea123https://github.com/galyea123. :-)
Yes, this term has been added: the PR was merged earlier today. It will be available in our next release (scheduled on August 6)
Best, Sabrina
—
Reply to this email directly, view it on GitHubhttps://github.com/monarch-initiative/mondo/issues/7776#issuecomment-2261381164, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A4QAWD4SYBZ37UAIKL5T6O3ZPFBHZAVCNFSM6AAAAABIXLP2RKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRRGM4DCMJWGQ.
You are receiving this because you were mentioned.Message ID: @.***>
Any review, use, distribution or disclosure by others is strictly prohibited.