after some layers the image given as output by render.render_vis become grey

When i try to use lucid on my own network the output of a lot of filters is just gray (there are some pixels that vary however the returned image is gray for a human. The deeper the layer the more filters are grey (in the highest layers everything returned is completely grey). Is there something I am doing wrong?

Are you optimizing after a ReLU by any chance?

at some places however not everywhere. I am trying to make spritemaps for every layer and at the moment I am doing it for every layer which does not give an error (no gradient) this includes the ones behind a ReLU. However these are not the only ones. But is it not possible to optimise behind a Relu when you get deeper in a network? At the starting layers it does give correct outputs.

ah I found this:

One isse you will run into is that certain neurons you want to inspect won't activate from just the random noise you feed them, and if they don't activate then a ReLU non-linearity will block all the gradient, so you won't be able to optimize your input.
There are two ways around this: override non-linearity gradients to the identity op for the first couple optimization steps, or create new tensors in your graph that correspond to the tensors you want to optimize, but before their ReLU non-linearity.
We don't have either of those options automated so far. Look at lucid's googlenet/inception class to see how we "crawl" the graph and add _pre_relu nodes for tensors we're interested in.

I tried to see how you added pre_relu nodes which I think you do here. However this does not seem to work for mobilenets. It is mainly because of this  tower = tower.op.inputs[0], I am not sure what inputs[0] should be as the only place that includes op.type==Relu is inputs[0] in mobilenet v1.

I also wondered for how many iteration do you run the render_vis in order to create the spritemaps you have? Becaues the default is 512 which seems to few.

I just realized you're likely on the most current version, which does try its best to automatically override ReLU gradients during model import anyway—so that shouldn't even be the problem. (For reference: it's the relu_gradient_override=True parameter on render_vis.)
Number of iterations is just a hyperparameter—in Feature Visualization we reported 2048 steps, but this will depend on your architecture, optimizer, step size, parameterization, etc. Feel free to tune it.
On a more general level note that interpretability techniques atm have a big uncertainty around them when they don't work as expected: is the technique not working, or is the model truly behaving in weird ways? Progress on this is an open research problem and feels outside the scope of a Github issue. I'd always be happy to take a look at an easy reproduction in (e.g.) a colab notebook. :-)

an example can be found in: https://colab.research.google.com/drive/1OFesr3ceAaPGmU_gNtDy1djn_9GZgI81

These are some images from the layers, As can be seen they become more and more grey and more iterations or other variables don't seem te work for me.

Hey @JaspervDalen I took a long look—I could not find anything obviously wrong in your approach.
Our code has not been (extensively) tested on models with BatchNorm layers, and we haven't tested if graphs imported from keras may behave subtly differently. We will follow-up on both, but I unfortunately can't guarantee a timeline.
If you want to debug more yourself, you may find it useful to start by finding out why so little gradient reaches the input during optimization. Sorry I can't be of more help atm!
(I am skeptical of your image_value_range; it looks to me like Keras preprocesses it to (-1, 1) for tf models. This does not seem to solve your problem, though.)

Ok thank you, the image_value_range is an artifact from my trying different ways of using lucid as I at the start when playing a bit with your library managed to get outputs in these layers. However since then I updated every lib (keras,tf, lucid, np) so it can be a number of things. I tried going back but it doesn't seem to work.

just for extra information:
I also tried to visualize the network using this method: https://blog.keras.io/how-convolutional-neural-networks-see-the-world.html
The same problem is true for higher layers.

@JaspervDalen  Did you manage to solve this problem ? I am facing the same one by importing a graph from Keras to Lucid.

When you visualize a ReLU neuron, it's possible that your initial image causes the neuron to take a zero value. When ReLU neurons are zero, no gradient flows through them, and so they never start to optimize.
The solution is to use a gradient override for the first few steps:
https://github.com/tensorflow/lucid/blob/master/lucid/misc/redirected_relu_grad.py
There are some ways this could still fail to work, including:

Your neuron uses a non-standard implementation of relu (ie. not tf.nn.relu) and so doesn't get overriden
You are visualizing a non-relu neuron that can also have zero gradients (like a saturated sigmoid neuron)
The gradient override was only applied for a few steps, and not long enough to escape

Thanks for your answer. The problem doesn't seem to be related to the no gradient flows in my case but maybe to the fact I convert a keras model to a tensorflow graph and then to a lucid Model in order to run the render function.
Because, the problem est more that the filter doesn't respond as I expected it. I try to get the same results with Inception_v1 as in the original paper Feature Visualization.


Putting Conversations Back

I noticed that when I continued the conversation for roughly more than 3 turns, Sydney forgets the context of the discussion and begins with the introduction again. I suspect this is because the conversation is put in the document summary, resulting Sydney not recognizing it as previous conversation

I can't say I'm experiencing the same thing, at least consistently. I've only had Sydney randomly say Hi once on the 3rd turn, but I've tried it several times and haven't reencountered it.

I have encountered several times. Maybe because I'm using a different system prompt. It may be more obvious and frequent if you give Sydney more rules and different identities. I'll leave this open to see if anyone else meet the same problem.

try this: https://github.com/waylaidwanderer/node-chatgpt-api/commit/f685de75d84f86f38d608a0c939757a09d339bf6

The same problem. Sydney starts to repeat introduction of herself after few conversions and forgets the context of converstion. I'm also using more rules and different system prompt.

OK I've reproduced the issue. This may work InterestingDarkness@bef4c97

Hello I tried this, I don't know if this is only on my side but it often cuts off the answer/response.

OK I've reproduced the issue. This may work InterestingDarkness@bef4c97

Hello I tried this, I don't know if this is only on my side but it often cuts off the answer/response.

Works well on my side. AI generated context will still be moderated.


Remove rioxarray optional import logic now that it is a main dependency

This was forgotten!

And did we actually need to make it a main dependency? It is only used in one function, would it not make more sense to keep it as optional?
Or will you need it more in ongoing/future PRs?

Yes that's why, it has to be a main dependency for the Xarray accessor in the works :wink:


Tensorflow2 implementation

Hello, thank you for this great paper and great implementation! As Tensorflow has upgraded to version 2, I was wondering if you by any chance changed this model to Tensorflow2 as well?

Hi,
Thanks for your interest. However, this repo is not actively maintained anymore. It is better to use the older version of tensorflow. Otherwise, some functions may be broken.

Hello, I have some questions to ask. I noticed in your paper you said that the model only considers undirected graphs, is it possible to extend it to directed graphs? The current model is used for molecular graph generation, so the node features and edge features are only onehot, is it possible to extend other numerical features? Looking forward to your reply, Thanks a lot!

Hi,
Yeah.
Extending to directed graphs is easy. Need to maintain the direction of edges during expansion.
Using numerical features and edge features is not a problem. But I think it requires a network to output continuous values instead of performing a classification in the code


ensemble model parallelism

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
Closes  #1341
What are the significant changes in functionality due to this change request?
Changed the parallelism strategy in case of ensemble model.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).  (No changes to input syntax)
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details. (Yes)
[x] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass. (yes)
[x] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True. (no significant functionality added)
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.  (needs second)
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done. (done)
[x] 8. If an analytic test is changed/added is the the analytic documentation updated/added? (no change)
[x] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example. (no change)

Job Mingw Test on 32960e5 : invalidated by @joshua-cogliati-inl
test civet

Job Mingw Test on 32960e5 : invalidated by @joshua-cogliati-inl
test civet

@joshua-cogliati-inl ready to review

@joshua-cogliati-inl Josh I addressed your comments

Job Test Ubuntu 18-2 Python 3 on da1cd4f : invalidated by @joshua-cogliati-inl
failed tests/framework/Optimizers/SimulatedAnnealing/ExponentialEggHolder

Any hope for a end-of-week miracle merge on this?

@PaulTalbot-INL looks like Josh is on it...so you called the miracle ehhehe

I approve, but this changes a requirements test so needs a second approval from the CCB chair or designee.

@PaulTalbot-INL @alfoa This changes a requirements test, so it needs a second approver.

As chair of COB I approve the requirement test modifications.

@PaulTalbot-INL  can you also approve the PR?


Notifications system

Description:
Build a notification system that does the following:

Add Notification if post is liked by other user
Add Notification if post is commented by other user
Read receipts. When user clicks on notification, redirect to the post and mark notification as read.

Reference:
Use this video for reference.
https://youtu.be/DrCQeI3WqF0?si=LWVXABplhB8tFAu8

@aadeshkulkarni I can take this.


Support Tombstones

To complete this, we need to:

Add StructureType::Tombstone variant
Add look::TOMBSTONE constant
Add find::TOMBSTONE constant
Add Tombstone structure implementing RoomObjectProperties
Add objects/impls/tombstone.rs file implementing tombstone properties/methods

Nevermind, this exists.


from_address is none

When I run get start script,I get error:
Traceback (most recent call last):
File "Code/python/Blockchain/eth_trans_decode.py", line 23, in
transaction: DecodedTransaction = ethtx.decoders.decode_transaction(
File "/opt/anaconda3/envs/py3.8/lib/python3.8/site-packages/ethtx/ethtx.py", line 67, in decode_transaction
return self._decoder_service.decode_transaction(chain_id, tx_hash)
File "/opt/anaconda3/envs/py3.8/lib/python3.8/site-packages/ethtx/decoders/decoder_service.py", line 47, in decode_transaction
transaction = self.web3provider.get_full_transaction(
File "/opt/anaconda3/envs/py3.8/lib/python3.8/site-packages/ethtx/providers/web3_provider.py", line 466, in get_full_transaction
w3calltree = self.get_calls(tx_hash, chain_id)
File "/opt/anaconda3/envs/py3.8/lib/python3.8/site-packages/ethtx/providers/web3_provider.py", line 255, in get_calls
return self._create_call_from_debug_trace_tx(
File "/opt/anaconda3/envs/py3.8/lib/python3.8/site-packages/ethtx/providers/web3_provider.py", line 490, in _create_call_from_debug_trace_tx
main_parent = W3CallTree(tx_hash=tx_hash, chain_id=chain_id, **w3input)
File "pydantic/main.py", line 406, in pydantic.main.BaseModel.init
pydantic.error_wrappers.ValidationError: 2 validation errors for W3CallTree
type
field required (type=value_error.missing)
from_address
none is not an allowed value (type=type_error.none.not_allowed)
When debug, I found from_address is set to none in ethtx/providers/web3_provider.py , 479 line.
I have no idea why?  And I print the debug_transaction response , it dose not contain from_address , either.

I had this same issue originally when using a hardhat fork from mainnet, are you possibly doing that? I did not resolve the issue just went on to using alchemy with polygon instead as I had trouble running a node (always get close but then I run out of some sort of capacity RAM or HDD space) but even then ran into a few issues with rate limiting and ens which is not on polygon but got it working in the end with the pull request I have submitted.

Could you provide more debug information for this issue? Info about which chain do you use, tx hash and node type should be sufficient for now. We are using pydantic to make sure data in models is in correct types, and this validation is causing the problem. For a quick fix, you could try making this field optional by changing fields type in file ethtx/models/w3_model.py in class 'W3CallTree' from str to Optional[str]
From this:
class W3CallTree(BaseModel):
    ...
    from_address: str

to this:
class W3CallTree(BaseModel):
    ...
    from_address: Optional[str]

and change to_object method from this:
    def to_object(self) -> Call:
        from_address = self.from_address

to this:
    def to_object(self) -> Call:
        from_address = self.from_address if self.from_address else "" ""

but I can't guarantee this will work, but it's worth a shot if you really need this tx decoded. I can't really make a PR with this without testing and making sure it's a valid solution, so again, if you could get me more info about transaction you are trying to decode and/or results of this hacked fix, we could work out something better.

Can someone please tell me how many requests per decode sent to a full archive node ?

@enmohsinali  It's a bit of out the line from original question, but it could be from 1 to multiple hundreds of requests depending on transaction and how complicated it is.

Sorry I couldn't find a better place for the question.
If there is any discord related to this repo please mention it.
By they way thanks alot.

Sorry I couldn't find a better place for the question.
If there is any discord related to this repo please mention it.
By they way thanks alot.

Hey, we have Discord. You can find a link to it on our website, in the footer: https://tokenflow.live/

I think the problem is my request node is not a full archive node.

by the way, I think the ens function can be optional , it is not work on bsc

@kchojn Yeah Found it now.
Thanks

@wulasite, we was thinking about optional ens and we will implement this in the future releases, for sure. Thanks for the idea!


Visual bugs

https://i.imgur.com/ygFW3cF.png
https://i.imgur.com/aYqdQo0.png
https://i.imgur.com/kAeySdM.png
device backup view:
https://i.imgur.com/QFqC2uK.png

(1) and (3) should be fixed. I'll get to (2) when I have time.
Unfortunately, I've never used the device backup feature before so I'll have to look into that one.


Lunarfusion/css 114 migrate tooltip core tokens

Description
BREAKING CHANGE: This migrates the Tooltip component to core tokens.

Jira issue CSS-114 https://jira.corp.adobe.com/browse/CSS-114

Note that the tip triangle has been changed to use clip-path rather than the older border corner "hack" method for creating triangles.
How and where has this been tested?

Chrome 105 for macOS
Firefox 105 for macOS
Safari 15.5 for macOS
How this was tested: comparing local build of http://localhost:3000/docs/tooltip.html with XD redline for Tooltip and with https://spectrum.adobe.com/page/tooltip/

Screenshots
There are now 22 positions, 10 of which are logical and must be tested in both LTR and RTL.

To-do list

[ ] If my change impacts other components, I have tested to make sure they don't break.
[x] If my change impacts documentation, I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have tested these changes in Windows High Contrast mode.

[ ] This pull request is ready to merge.

Newly published beta<EMAIL_ADDRESS>


paypal error fixed #1640

error is raised because xml tag value is 'SOAP_ENV:Envelope' and not 'Envelope'.
Due to this, cc payment always fails.

We have a fairly large number of credit card payments going through PayPal that are successful - do you have a test case that can reproduce this?

Going to close this out for now - feel free to reopen when this has a test. :)


K3S Breaks after a firewalld reload

Environmental Info:
K3s Version:

k3s version v1.26.4+k3s1 (8d0255af)
go version go1.19.8
Node(s) CPU architecture, OS, and Version:

Linux HOSTNAME 4.18.0-489.el8.x86_64 #1 SMP Thu Apr 27 17:02:11 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:

Single node configuration, CIDR - <IP_ADDRESS>/16
Describe the bug:

Opening the K3S ports using firewalld as explained here and then installing the application works fine and any app deployed in K3S is accessible.
However, reloading firewalld afterwards (for example, to set up a non Kubernetes service) flushes all iptables rules. This breaks any deployment in K3S, making then not accessible anymore.
I tried restarting the K3S service without any success, the K3S iptables rules are not added back.
I have found that rebooting the whole physical server gets it back to to work again. So, there is a step there I have not been able to reproduce manually.
Uninstalling and re-installing K3S again works as well, although this is not very handy.
Steps To Reproduce:

Set up firewalld as instructed here: https://docs.k3s.io/advanced#red-hat-enterprise-linux--centos

Allowed <IP_ADDRESS> instead of <IP_ADDRESS>  (<IP_ADDRESS> is already in use)

Install K3S

Beware that the provided script runs the K3S uninstallation script
--write-kubeconfig-mode 644
--cluster-cidr "<IP_ADDRESS>/16"

Deploy whoami service for testing
Check that  the whoami service works
Reload firewalld
Check that the whoami service doesn't work anymore
Check the before.txt and after.txt file from differences in iptables

Provided script to reproduce the steps above
#!/bin/bash

set -e
current_dir=$(dirname -- $0)

# Clean up current K3S installation
if [ -f /usr/local/bin/k3s-uninstall.sh ]
then
    /usr/local/bin/k3s-uninstall.sh
fi

# Open firewall for K3S
# https://docs.k3s.io/advanced#red-hat-enterprise-linux--centos
echo "Setting up firewall"
firewall-cmd --permanent --add-port=6443/tcp # apiserver
firewall-cmd --permanent --add-port=10250/tcp # metrics
firewall-cmd --permanent --zone=trusted --add-source=<IP_ADDRESS>/16 # pods
firewall-cmd --permanent --zone=trusted --add-source=<IP_ADDRESS>/16 # services
firewall-cmd --reload

# Install K3S
# https://docs.k3s.io/quick-start
# https://docs.k3s.io/cli/server
curl -sfL https://get.k3s.io | sh -s - --write-kubeconfig-mode 644 --cluster-cidr "<IP_ADDRESS>/16"

# Wait for K3S to be ready
while
    PODS=$(/usr/local/bin/kubectl get pods --namespace kube-system 2>&1)
    [ "$PODS" = "No resources found in kube-system namespace." ]
do
    sleep 3
done
/usr/local/bin/kubectl wait jobs --namespace kube-system --all --for condition=complete --timeout 300s
/usr/local/bin/kubectl wait pods --namespace kube-system --selector='!job-name' --for condition=ready --timeout 300s
/usr/local/bin/kubectl get pods -A

# Test deployment
/usr/local/bin/kubectl apply -f $current_dir/whoami.yml

# Wait for deployment to finish
/usr/local/bin/kubectl wait pods --namespace whoami-example --all --for condition=ready --timeout 120s

# Test
curl --fail http://whoami.localhost

# Log iptables before reloading firewalld
iptables -L -v -n --line-numbers > $current_dir/before_reload.txt

# Reload firewall
firewall-cmd --reload
sleep 10

# Log iptables after reloading firewalld
iptables -L -v -n --line-numbers > $current_dir/after_reload.txt

sleep 30

# Log iptables after reloading firewalld
iptables -L -v -n --line-numbers > $current_dir/after_reload_and_30_secs.txt

# Test
curl --fail http://whoami.localhost

apiVersion: v1
kind: Namespace
metadata:
  name: whoami-example
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: whoami-deploy
  namespace: whoami-example
  labels:
    app: whoami
spec:
  replicas: 2
  selector:
    matchLabels:
      app: whoami
  template:
    metadata:
      labels:
        app: whoami
    spec:
      containers:
        - name: whoami
          image: traefik/whoami:latest
          ports:
            - name: whoami
              containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: whoami-service
  namespace: whoami-example
  labels:
    service: whoami
spec:
  type: ClusterIP
  ports:
    - name: http
      port: 80
      protocol: TCP
  selector:
    app: whoami
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: whoami-ingress
  namespace: whoami-example
  annotations:
    traefik.ingress.kubernetes.io/router.entrypoints: web
spec:
  rules:
    - host: whoami.localhost
      http:
        paths:
          - path: /
            pathType: Exact
            backend:
              service:
                name: whoami-service
                port:
                  number: 80

Expected behavior:

K3S adds back all its iptables rules after a firewalld reload. Not sure if there is any option for this that I have missed.
As mentioned above, it all goes back to normal after a system reboot.
Knowing the command to manually reload K3S iptables rules could be a temporal solution to be executed after every reload. Not ideal, but would be helpful
Actual behavior:

All K3S-related iptables rules are flushed after firewalld reloads
All K3S deployments are inaccesible
PS: While writing creating this issue I noticed that ~30 seconds after reloading firewalld, a few rules are added back.
This means that K3S is indeed reactive to firewalld reloads, but fore some reason not all the rules are restored and the services remain inaccessible
Additional context / logs:

It looks like other similar technologies have had similar issues. Although I lack the expertise to know whether this specific cases could be relevant for K3S.
https://github.com/weaveworks/weave/issues/3586
https://github.com/moby/moby/pull/9397/files
iptables output:
1_iptables_before_firewalld_reload.txt
2_iptables_after_firewalld_reload.txt
3_iptables_after_firewalld_reload_and_30_secs.txt
4_iptables_after_system_reboot.txt

Bonus question:
Is there some way to make my system aware of the ports being used by K3S?
The devices I am working on are multi-user and not exclusive to K3S. So I am afraid that, at some point, somebody will end trying to bind their own service to one this ports

However, reloading firewalld afterwards (for example, to set up a non Kubernetes service) flushes all iptables rules. This breaks any deployment in K3S, making then not accessible anymore.

Don't do that. We don't recommend using self-managed iptables-based firewalls alongside k3s. If you must, make sure that they don't attempt to exclusively manage the iptables ruleset, and make sure that you've allowed access to/from the cluster CIDRs. See the examples at https://docs.k3s.io/advanced#red-hat-enterprise-linux--centos


how to find what tensorflow/keras release contains a specific bug fix

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
This is related to a known bug (see below in italics), but I'm trying to figure out how to install a version of tf/keras which has the fix.
System information

OS Platform and Distribution -> Ubuntu 20.0.4
TensorFlow installed from -> docker tensorflow-gpu
TensorFlow version: 2.5.0-dev20210204 from docker tensorflow/tensorflow:nightly-gpu
Python version: 3.6.9 (default, Oct  8 2020, 12:12:24) \n[GCC 8.4.0]
Installed usinga  Dockerfile to add some required Python libraries to tensorflow-gpu image
CUDA/cuDNN version:Cuda compilation tools, release 11.0, V11.0.221
Build cuda_11.0_bu.TC445_37.28845127_0
GPU model and memory: Nvidia RTX 2080 Ti

I'm training a large (millions of parameters) NN to analyze audio files (speech vs. music).  After 28/50 epochs I hit a known bug which is (to my knowledge) fixed already.  I'm not sure how to find out what tf/keras release the fix is in or if my docker image has the fix.  I'm using a docker image since it was recommended as the easiest way to get version compatibility between tf/keras and CUDA.
This is the bug description and reference to the fix:
_Tensorflow 2.1 Error “when finalizing GeneratorDataset iterator” - a memory leak? #37515
URL: https://github.com/tensorflow/tensorflow/commit/e918c6e6fab5d0005fcde83d57e92b70343d3553
Fixing a memory leak in Keras.
Fixes: #37515
PiperOrigin-RevId: 302568217
Change-Id: I28d0eaf3602fea0461901680df24899f135ce649_

@jmm5491,
The error mentioned in #37515 seems to have been fixed in TensorFlow v2.2, so TensorFlow v2.5 should also work in this case.
In order to expedite the trouble-shooting process, could you please provide a minimal code snippet to reproduce the issue reported here and the dataset you are using. Thanks!

I hit this problem when running someone else's github project, so I'm not very familiar with the code.  I'll look into it some more and see what I can do.  It uses a large dataset. FYI, it is this project: https://github.com/qlemaire22/speech-music-detection.

I can provide a tgz file including the project code and one dataset with which what I run to reproduce the problem.  It's 4Gb compressed.  With slightly more steps (using sox app to convert mp3 files to a series of .wav files, plus .npy files), I can reduce the file size quite a bit.  I'm not sure the best way to get it to you.  I  could upload it to my Google Drive and make it available that way, for example.

I could upload it to my Google Drive and make it available that way, for example.

@jmm5491,
Yes please, you can share the code and the dataset from your Google Drive.
Alternatively, you can also run your code on Google Colab and share the notebook with us. Thanks!

I tried to reproduce this on Colab using the complete 4Gb dataset, but rather than seeing the symptom described in my original post, the python process hung.  Because of this and the fact that other users don't seem to have this problem, I'm going to assume the problem is in the code I'm using.  This issue can be closed now.  Thanks.


Intensity not taken into account in pwm_set_gpio_level

When setting the level of the LED in pwm_set_gpio_level, it always goes to the maximum intensity (duty cycle at 100%). I suspect that pwm_set_gpio_level should receive (char*) instead of (uint8_t) because changing the type in main.c on the RP2040 fixes the issue for me.
For example, I use the command:
i2cset -y 1 0x30 0 0xC0
It's the same behavior using the "pio run led_intensity --A 75" command.
Let me know if I'm doing something wrong.
Thanks!

Hi @lorenpelli, I totally missed this! Sorry about that!
Are you still seeing this issue? I'll investigate asap too.


Correctly parse HTML in the Speaker Detail Activity #1185

#1185
Changes: In SessionDetailActivity summary is not correctly parsed. Also the link is not clickable.
Screenshots for the change:
## Before

# After

Please review this PR.

Hi, Please review this PR.

@harshitagupta30 is this working for you too?

@the-dagger Yeah its working fine! :+1: I was making changes in SpeakerDetailsActivity :P

@mohitmanuja Can you please squash the commits? :+1:

@mohitmanuja  Can you please update your commit message according to guidelines :+1:

@harshitagupta30 @the-dagger yeah sure.

@the-dagger please review this so that I can close this PR.

Looks good.
Let the travis build complete and I'll merge it.

@the-dagger please merge it.

@mohitmanuja Make sure to squash all the commits into one :+1:

@the-dagger Please review it.

LGTM merging


Q1: Question on Redis

Redis is an in-memory database instead of on disk. Doesn't this change everything?

@cristiprg Redis is an in-memory but persistent on disk database. Even this is not the case, why would being in-memory change everything?

@jeyhunkarimov Because of two reasons:

multiple processes should have access to the same data. Like if computer1 (or JVM1) creates a model, then computer2 should also have access to that model. This is not easily possible with in-memory (only with tricky shared memory at OS-level or JVM-level)
if the process dies, everything that is in its memory is deleted, so the model is lost. I'm not sure, but maybe it can be recovered from the checkpoints that Spark makes, but I don't think is trivial.

@cristiprg let Redis handle this and you focus on the solution. Redis handles those issues because it is supports concurrent updates. It uses cache and persistent storage on disk and synchronises them. Moreover, to gain the speedup, we are ready to sacrifice some accuracy due to  possible issues you listed above.


BUG: New Github Login Error - No Account Found

Note - this is high priority as it is blocking a business line from onboarding
Describe the bug
Shankara Subramanian<EMAIL_ADDRESS>attempted to login to staging with his github account. This was a new login. He received the following error message upon authenticating successfully and being redirected:

To Reproduce
Steps to reproduce the behavior:

Go to https://staging.notification.va.gov while on the VA Network
Click on Sign in with Github
Log in with an account that has not yet logged into Staging
See error: Your account was not found.

Expected behavior
You should see the message: You are not assigned to any services (paraphrasing) and the new account should be created in the database.
Screenshots
See above
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

@ianperera Future PeriOptimization user was unable to login to Staging with Github. @jessecanderson took a quick look and thinks it may be related to the recent changes made for having users assigned to > 10 services. Can you please focus on this with urgency? If you're working on anything else for Strike or Notify that you feel is urgent or could block others let me know and I'll coordinate. FYI @zlaw

Does this only occur with people that havent logged in using github before?

When I tried on local with a new github user, it worked well.  Not sure how to replicate the issue

From the codebase, the issue raised when user has already registered with an email and then trying to sign up with github user which is authorized with same email.

@mjones-oddball Only github account who are a member  of department-of-veterans-affairs can signup using the github

Root cause analysis: A new user without access to department-of-veterans-affairs org in github attempted to log into staging. The user was authorized, but failed that additional check and thus was redirected to the error page. Since github won't be used after PIV is fully implemented we will not pursue enhancements to the error page for this specific case. However, in the future we will need to provide this guidance during onboarding and if the error recurs, ask this before escalating.

This has been deemed, working as expected, and has been closed. The user was sent instructions to gain access to the va org.


Documentation search is pointing to incorrect path

Describe the bug
Documentation search feature is able to find the proper documentation topic but points to an incorrect path which always goes to a 404 page.
To Reproduce
Steps to reproduce the behavior:

Go to https://pioneer.dexclaimation.com
Click on 'Search documentation'
Scroll down to any option there (i.e. 'GraphQL IDE')
Navigate to that page
Should be redirected to a 404 page

Expected behavior
Search should points to an actual page, most of the documentation is under the /docs route.
Desktop (please complete the following information):

OS: macOS

Additional context
Seemed like the path is partially correct just missing the  /docs route, must investigate why and how to fix it.

Update (Dec 21st):

The search functionality works as intended, the search functionally does show the correct links, but it seemed to also have incorrect (outdated) links as well.
There are always duplicate search result, one pointing incorrectly, the other is correct. Sadly, the first happen to be the incorrect path
It could have been due to caching issues or incorrect build output.

Also maybe fix typo in the docs since I rewrite a handful of things but haven't really double check them


Merge viewer and editor into a single project

See https://github.com/renatopp/behavior3js/issues/10

Changes:

Old folders app, b3view and b3editor are now all inside app;
The old View and Editor class were merged to a Editor class;
Build process is now simplified, use grunt <option> with css, libs, html, app and build options. Use build to build everything;


Convert PolicyDiff to Python 3

basestring and unicode were remove from Python 3 because all str are Unicode so this PR created equivalents.

@mikegrima Please review.

Coverage decreased (-0.01%) to 71.974% when pulling a7a14c8368c266e44b78c4d956bdc5a60ecf35c1 on cclauss:PolicyDiff-for-Python-3 into a6bf3b0cea5b21d3c675b19715d725b6a428e96f on Netflix:develop.

LGTM. Thanks again for working on this! 🍻


Revert changes made to getUnusedSlug in #2075

In #2075 I made the mistake of thinking that onCreate functions were always exectued in async, which is not the case for the Users collection. Thus, the slugs would be [ Object object ] because getUnusedSlug returned a pending promise.
So I reverted to the previous way we did things, using collection.findOne. I don't really understand why this is fine in terms of async, but at least it works. I let the version I implemented but it's commented, this way it's not lost and can be reused when we refactor or move out of meteor for example.

I don't really understand why this is fine in terms of async

Because of Meteor magic (Fibers) ;)


feat: add setCustomTransformer. Customize parsing!

add n2m.setCustomTransformer(string, function)
short-cut parsing when a custom transformer is set

Hello @souvikinator !
Thanks for this repo, it's really helpful. While developing scripts to transform notion pages to Docusaurus markdown, I've stumbled on a specific need that may help other: I want to be able to change some parsing in a very "docusaurus" way, like handling the embed betters.
So here what I've done:
n2m.setCustomTransformer('embed', async (block) => {
  const {embed} = block as any;
  if (!embed?.url) return '';
  return `

${await n2m.blockToMarkdown(embed?.caption)}

`;
});

This way, when the parser have a "embed" type, it executes this function and not the default one. It can fits any other type.
Tradeoffs: The types for ListBlockChildrenResponseResult have not all the notion types, so it may be needed to do a any type-casting.

Hello there,
Thanks for the contribution. That definitely is a useful feature.
I'll test it locally and create a new release shortly.

Wow that's a pretty awesome feature. Just love it 💯.
It's live in v2.5.0.

Hi again! Your past feedback on notion-to-md has been valuable.
We're now working on v4 with major improvements to address various use cases better.  V4 extends on this and takes it way beyond Markdown.
I'd love your insights on this. Please checkout the GitHub discussion #112   to discuss or share your feedback? Your feedback would be really valuable in shaping v4's development.


Thanks for this, but could have been a PR

Bar code scanning support now available here - might have been nice to submit a PR: https://github.com/lwansbrough/react-native-camera

Did not realize that, anyway, glad to know you made it.


New device creation - returns forbidden

In GitLab by @jasonpagetas on Jul 11, 2024, 08:43
When creating a new device I have filled out the name, added a serial number and assigned the organization perseus. When I click submit I am present with the 403 Forbidden page.

added 1m of time spent

mentioned in commit a62a36ba82252257646325679180c68632971c52


operators t8c (42.1.0)

Signed-off-by: esara<EMAIL_ADDRESS>

@camilamacedo86 of course, I am stuck with this being merged
so that I can create the pr to upgrade it to the 4.9 supported version
like we already did in community https://github.com/k8s-operatorhub/community-operators/pull/276
can you help me get this merged, so I can create pr for the 4.9 friendly version?

/merge possible


Release 100.10 AppStore

The PR will merge the latest U10 sample updates to master branch.
We'll merge this PR on Wednesday March 31st, as well as publish the release build on AppStore.

The new release note
The following samples have been added:

• Augmented reality > View hidden infrastructure in AR
• Display information > Create symbol styles from web styles
• Geometry > Buffer list
• Layers > Add ENC exchange set
• Maps > Display device location with NMEA data sources
• Route and directions > Navigate route with rerouting
• Utility network > Create load report

The following samples have been updated:

• Augmented reality > Flyover AR
• Display information > Custom dictionary style
• Geometry > Spatial operations
• Layers > Edit KML ground overlay
• Layers > Export tiles
• Layers > ArcGIS vector tiled layer (custom style)
• Layers > Group layers
• Layers > Apply mosaic rule to rasters
• Layers > Identify KML features
• Maps > Change basemap
• Scenes > Create terrain from local tile package
• Scenes > Add integrated mesh layer

In addition, this update includes the following changes:

• Added Dark Mode support
• Slightly improved coding style
• Updated build phases and path to the new ArcGIS Framework
• Incorporated API key and new basemap initializers
• Replaced pixelated Brest basemap
• Fixed the build error that occurs in the first clean build
• Updated the demo Sample Server used in utility network samples

@yo1995 i don’t seem many of the new samples in the test flight (load report, nmea, web styles)

I don’t seem many of the new samples in the test flight submission(load report, nmea, web styles).

I didn't create a separate TestFlight Samples Beta app, but only upload a build to the formal Samples app. That is to say, once you install it from TestFlight, it will overwrite the 100.9 app.
I know we decided in U9 to use the separate Samples Beta for comparison and internal testing, but since we are on a tight schedule (try to make the release public before this Friday), I skipped this step this time.

Also, didn’t we have dark mode already before this update?

Nope. In U9 the app changed from blue to purple, but the Dark Mode changes are merged during U10 (Jan 27th).

Ah, I see them now

Two more fixes to do before the release

Address the issue in Edit and sync feature from #750
Update the URL for Create load report sample for SS7

I've addressed the 2 issues from AppStore review and merged them into v.next.
Now the 100.10.0 release has been approved, and you'll see the update on AppStore soon! 🎉


Absolute paths used on Windows

I think I'm seeing this bug in my jsdoc output from Grunt:
https://github.com/terryweiss/docstrap/issues/44
I'm using DocStrap. I think you include DocStrap with the grunt plugin right? Can it be you are still on an older version that has this bug?
Sorry if it's user error, i'm pretty new to Grunt, JsDoc and this plugin  :)

I'm linking to docstrap version 0.5.2, could you reinstall the plugin ?

I will try... Could you give me a tip how to do it?
Some npm commands I presume?

just remove the node_modules folder and run again npm install

Did as you asked and I see (among lots of other output):
<EMAIL_ADDRESS>node_modules\grunt-jsdoc
├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS>
I will try out if it worked and let you know

Running "jsdoc:dist" (jsdoc) task
Documentation generated to C:\Users\Stijn\Documents\GitHub\suid\doc

I still see the issue. It generates a file called C__Users_Stijn_Documents_GitHub_suid_src_suid.js.html and 'absolute' path links to it.
My grunt file contains this:
jsdoc : {
	dist : {
		src: ['src/*.js', 'test/*.js'],
		options: {
			destination: 'doc',
			template : "node_modules/grunt-jsdoc/node_modules/ink-docstrap/template",
			configure: "node_modules/grunt-jsdoc/node_modules/ink-docstrap/template/jsdoc.conf.json"
		}
	}
},

I will try with ./src/*.js instead of src/*.js and see if that makes a difference.

Nope it made no difference.
Am I doing something wrong? I notice that jsdoc logs an absolute path in it's output:
Documentation generated to C:\Users\Stijn\Documents\GitHub\suid\doc

Is it supposed to? I'm new to JSDoc and Grunt both so I really don't know what to expect.
I also saw that the bug on JSDoc was reopened at some point because the bug came back. Maybe it came back again?

As docstrap isn't in the plugin anymore, I'm closing the issue.

I gave up on JSDoc as keep editing the file to fix the absolute path was a pain.


Prevent multiple instances using QtSingleApplication rather than QSharedMutex

This does add https://github.com/itay-grudev/SingleApplication as a submodule dependency. I'm not sure if this is desirable, as I'm not used to working with C++ projects.
This was my workaround to resolve https://github.com/macdems/yet-another-spotify-tray/issues/1

I think that using QSingleApplication library is an overkill. I have resolved #1 using a simple solution from https://stackoverflow.com/questions/42549904/qsharedmemory-is-not-getting-deleted-on-application-crash

Great, thanks a lot!


Changed file exporter, improve significantly scraping time and get new metrics kafka's version 2.5

Description
Changed yaml file with regex to get jmx metrics that improve significantly scraping time. The image above show the improvement:

Type of change

[ ] 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?
I ran the tests with molecule.
Checklist:

[x] 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
[ ] Any dependent changes have been merged and published in downstream modules
[ ] Any variable changes have been validated to be backwards compatible

@alvarobacelar Thanks for this contribution. Please review our Branching Model and update the target branch to either 6.1.x or 6.2.x. I'd say this is a good idea to get into the subsequent 6.1 releases.


[Mod]Less Simple Isru

Mod info

Mod name: Less Simple Isru
Author(s): juanml82
License: GNU LESSER GENERAL PUBLIC LICENSE
Version 3GPLv3
Homepage: https://forum.kerbalspaceprogram.com/index.php?/topic/192738-18-110less-simple-isru-for-modded-fuels-v03-electrolysis-sabatier-and-more-added-rss-and-nfc-integration/
Download: https://spacedock.info/mod/2378/Less Simple ISRU

Already indexed in #7802.

https://github.com/KSP-CKAN/NetKAN/blob/master/NetKAN/LessSimpleISRU.netkan
https://github.com/KSP-CKAN/CKAN-meta/tree/master/LessSimpleISRU

(Presumably this is harder to find now thanks to BobPalmer/CommunityResourcePack#249. Pray for BobPalmer/CommunityResourcePack#252 to get re-opened and merged.)


Create task by torrent file

Hi!
Do you plan to add a create method with file location (on the pc or on nas)
I tried to implement this in c#, but never got any results.
There is similar logic in this repository, but I'm not that good at power shell scripts: https://github.com/xaozai/ds-cli

I've updated the script to support this.
Note: it does not check to see if it's a valid download folder, or create it if it does not exist. That is outside of the API. If it's not a valid destination, it will give an error (403).
The best way to understand what it needs to be supplied is to:

go to your download station web page
look at a currently running download
look under 'General' at the 'Destination' info
copy that format to supply to the script!

Thank you for answer!
Can you show example string to create task with torrent file?

adrian@DiskStation:~$ ls /volume1/DiskStation/Downloads/Linux/
adrian@DiskStation:~$ ./bin/download-station.sh add "https://releases.ubuntu.com/22.10/ubuntu-22.10-desktop-amd64.iso.torrent" DiskStation/Downloads/Linux
Initialising environment... OK!
Checking API on Synology... OK!
=> Auth_URL: /webapi/entry.cgi
=> DS_URL:   /webapi/DownloadStation/task.cgi
{
  "data": {
    "SYNO.API.Auth": {
      "maxVersion": 7,
      "minVersion": 1,
      "path": "entry.cgi"
    },
    "SYNO.DownloadStation.Task": {
      "maxVersion": 3,
      "minVersion": 1,
      "path": "DownloadStation/task.cgi"
    }
  },
  "success": true
}
Getting authentication token... OK!
=> SID: x3nF6Ef7oWdRgYSREGcNPZ4C9gXSFegb8QMiLDraim4uZrl53fZP0Ys-s2Ukl3hIaE03BZcrwHw_qwCWejOTBQ
{
  "data": {
    "did": "sYt45wcK-V1uJaM4MpaEb-4PktzoD6m_n8xLHVOqCzll8NzwD641DhVqNzXnunpKsbpB1nyFGufRsVIQP5acXg",
    "sid": "x3nF6Ef7oWdRgYSREGcNPZ4C9gXSFegb8QMiLDraim4uZrl53fZP0Ys-s2Ukl3hIaE03BZcrwHw_qwCWejOTBQ"
  },
  "success": true
}
Adding URL... OK!
{
  "success": true
}
Cleaning up... OK!
{
  "success": true
}
adrian@DiskStation:~$ ./bin/download-station.sh list
Initialising environment... OK!
Checking API on Synology... OK!
=> Auth_URL: /webapi/entry.cgi
=> DS_URL:   /webapi/DownloadStation/task.cgi
{
  "data": {
    "SYNO.API.Auth": {
      "maxVersion": 7,
      "minVersion": 1,
      "path": "entry.cgi"
    },
    "SYNO.DownloadStation.Task": {
      "maxVersion": 3,
      "minVersion": 1,
      "path": "DownloadStation/task.cgi"
    }
  },
  "success": true
}
Getting authentication token... OK!
=> SID: wchMJBohboQWnTflpJhUgZRtjLY0pfQm0GqHPVHxsrEpMEYSAGbhP7dcwa1lnRqxDM7SVO0qI3Sce8UcvH7xfs
{
  "data": {
    "did": "Ivqva_mTeCu7OuRDcNRCKgmn4qeVvxLO41b9zqwDajzZ-a9ixLPcXrJf8933nNuKKlmCtbB2aaxmHmKTFo-ixA",
    "sid": "wchMJBohboQWnTflpJhUgZRtjLY0pfQm0GqHPVHxsrEpMEYSAGbhP7dcwa1lnRqxDM7SVO0qI3Sce8UcvH7xfs"
  },
  "success": true
}
Getting download tasks... OK!
=> Number of downloads: 1
=> Format: id,"title",status,download speed,downloaded,size,percentage complete
=> dbid_376,"ubuntu-22.10-desktop-amd64.iso",downloading,0B/s,0B,3.8GB,0.0%
{
  "data": {
    "offset": 0,
    "tasks": [
      {
        "additional": {
          "transfer": {
            "downloaded_pieces": 0,
            "size_downloaded": 0,
            "size_uploaded": 0,
            "speed_download": 0,
            "speed_upload": 0
          }
        },
        "id": "dbid_376",
        "size":<PHONE_NUMBER>,
        "status": "downloading",
        "title": "ubuntu-22.10-desktop-amd64.iso",
        "type": "bt",
        "username": "adrian"
      }
    ],
    "total": 1
  },
  "success": true
}
Cleaning up... OK!
{
  "success": true
}

So I created Linux folder under the DiskStation share Downloads folder.
Then added the torrent file:
download-station.sh add "https://releases.ubuntu.com/22.10/ubuntu-22.10-desktop-amd64.iso.torrent" DiskStation/Downloads/Linux
You’ll need to check your paths etc.
This is why I didn’t want to implement it - just use the default downloads folder and move it afterwards. If adding on iOS, I’ve included a sample shortcut which works over SSH

Thank you! Perfect answer
But, some torrent files do not have a link like https://...
So I wondered what to do if I have a downloaded file on my device (pc or phone) or if the file is already on NAS

The API does not support this - only links which are accessible via the internet.
You’d need to upload it to the NAS another way (scp or smb for example), and possibly drop it into a watch folder.

It's so sad(
But if create task from UI (choose file from pc) i can intercept request and see another API (download station 2)
I'm just talking for information
For example: https://www.reddit.com/r/synology/comments/110mobb/what_is_current_api_version_for_downloadstation/
I have asked support, but they are silent

FYI: Syno DS API Does mention sending a file across. It's outside my use-case and scope of this simple script. Happy for you to fork the script and add support...
A solution that would be easier would be to use secure copy a .torrent into the watched folder scp -O your.torrent user@synology.local:/path/to/watched/folder


enhancement: Added firewall rules for the HA cluster on azure #118

Sure will review once you have changed stuff
Also if you could create another pr for civo provider as well still it's your call


Update the docstr for use_docker in execute_code

          Do we want to update the docstr? Like line 245?

Originally posted by @sonichi in https://github.com/microsoft/autogen/pull/200#pullrequestreview-1672687913

Please assign this to me @sonichi

Assigned. Thanks.

Thanks @sonichi

Hello @sonichi ... Please review the PR #233  ....do i need to changes something

Thanks @sonichi @qingyun-wu  for merging my PR ... can u please add hacktoberfest-accepted tag ....or  else no problem

Thanks. Added.


btf: print original error returned by ebpf btf.TypeByName()

btf.TypeByName() could return ErrMultipleMatches if btf includes multiple matches.

looks good, could you please put example of the new log message into the changelog? thanks

Thanks just did and pushed

Merging as CI error is not related


Sanity Check- quality-grades/gmp-source-grade

Hi Team,
I have noticed a few observations which are given below. Please look into the below and do the needful.
Reference Links:-
Main:- https://main--aldevron--hlxsites.hlx.page/quality-grades/gmp-source-grade
Source:- Refer the document.

Image quality issue

The text in Italic,

Image quality issue, The quality of the image is fine now but we need to replace the graphic with the latest one(if the customer provides it)
Italic text issue, this is a minor issue, and I will take it in the next phase.


typo: Double word "size"

@nschonni : Thanks for your contribution! The author, @, has been notified to review your proposed change.

Reviewed editorial correction.


feat: initial commit for spaces best practices

This is a concept that Chris D and I came up with, we've noticed theres a very heavy usage of warning and info callouts scattered through our documentation. This can be very distracting to our users. A lot of these callouts, we believe, are better suited for a "best practices" type page where we can bring all these important callouts under one roof and make our documentation flow a little better. This is not to say we cannot use warning or info callouts in the docs - we think we should just use them sparingly and centralize the important callouts in one place while also being a little more opinionated on how to set things up.
I went through the spaces documentation with this PR and put together a best practices and cleaned up some of those callouts. The idea is that most sections of our documentation would have this best practices page at the bottom of their navigation.

Heres an example page that could use this type of setup, our login policy page has like 5 callouts right at the top: https://docs.spacelift.io/concepts/policy/login-policy


affected/package: SAST coverity scan [security] - Crypto -  Risky cryptographic function

What version of Go are you using (go version)?

$ go version
1.17

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
Linux
go env Output
$ go env

What did you do?

What did you expect to see?
What did you see instead?
A use of a weak cryptographic method was detected. There exist known ways to compromise the security of the encrypted data.
In golang.org/x/crypto/ssh.newRC4([]byte, []byte): A risky cryptographic function was used. This may allow an attacker to decrypt encrypted data as the quality of the cryptographic protection is suspect.

// Ciphers from RFC4345, which introduces security-improved arcfour ciphers.
// They are defined in the order specified in the RFC.
"arcfour128": {16, 0, streamCipherMode(1536, newRC4)},
"arcfour256": {32, 0, streamCipherMode(1536, newRC4)},

// Cipher defined in RFC 4253, which describes SSH Transport Layer Protocol.
// Note that this cipher is not safe, as stated in RFC 4253: "Arcfour (and
// RC4) has problems with weak keys, and should be used with caution."
// RFC4345 introduces improved versions of Arcfour.
"arcfour": {16, 0, streamCipherMode(0, newRC4)},

Working as intended.


Feature Request 1

Please add a placeholder which returns The color of the players vault prefix when unnicked and the eazynick prefix-color when nicked.
Same goes to suffixes tooo.
Would be good for more customizatoins.

Please add a placeholder which returns The color of the players vault prefix when unnicked and the eazynick prefix-color when nicked.
Same goes to suffixes tooo.
Would be good for more customizatoins.

Already included. Enable ServerIsUsingVaultPrefixesAndSuffixes anf use %eazynick_chat_prefix% and %eazynick_chat_suffix%

I mean It Return the Color Codes instead of prefix


switch to tower-abci branch with patched rx selection

The patch applied is https://github.com/heliaxdev/tower-abci/commit/8a88c53ef45b55bc4967e93b2f79460eb9414575. It fixes the panics seen in the public testnet and occasionally on a local dev node:
Location: /usr/local/rust/cargo/git/checkouts/tower-abci-0d01b039e0b7a0c9/d63c0d0/src/buffer4/worker.rs:156
Message: called `Option::unwrap()` on a `None` value
The application panicked (crashed).

merged to next, later to master, maint-0.2?

pls also rebase onto f837d9f87faa39d098ba1b3a1443a81b0fd20c7f if it depends on query_with_proof otherwise v0.2.0

@juped I have 2 more commits for this. I'll rebase it

@juped I rebased on v0.2.0 and added 2 more commits

rebasing and merging to master

pls update wasm

Cannot access 'prInfo' before initialization

pls update wasm

Cannot access 'prInfo' before initialization

pls update wasm


IndexError: list index out of range

What orders caused the problem

Please take a screenshot of the complete stack error screenshot thanks

python3 main.py -f aliyun url.txt

Fix: https://github.com/UzJu/Cloud-Bucket-Leak-Detection-Tools/commit/1445d0b44598ead99ef01b4bce6394585b9f1a30


[web applications] mailhog/MailHog

A web and API based SMTP testing tool.

Can you rebase this onto master?

Rebased.

but this is really a php project ?

Heh you're right. Closing.


"Could not find" module error in test file

I'm getting an error that the editor cannot find the lib when in the test file, but prove6 runs correctly.
Here is the folder structure:
├── HELP.md
├── README.md
├── lib
│   └── Pangram.rakumod
└── t
    └── pangram.rakutest

And here's the top of the test file:
use Test;
use lib $?FILE.IO.parent(2).add('lib');
use Pangram;

This is the full error:
    /Users/italo/.vscode/extensions/bscan.raku-navigator-0.3.2/server/src/lib
    /Users/italo/.raku
    /opt/homebrew/Cellar/rakudo-star/2024.02/share/perl6/site
    /opt/homebrew/Cellar/rakudo-star/2024.02/share/perl6/vendor
    /opt/homebrew/Cellar/rakudo-star/2024.02/share/perl6/core
    CompUnit::Repository::AbsolutePath<6136726709184>
    CompUnit::Repository::NQP<6136721594120>
    CompUnit::Repository::Perl5<6136721594160>
raku navigator

This is from Exercism's Pangram exercise: https://exercism.org/tracks/raku/exercises/pangram
I'm running the Raku VS Code extension v0.3.2, Rakudo v2024.02 on macOS 14.2.1 (M1 Pro).

Hi @oyarsa, thanks for filing the issue. This is a limitation because the Raku Navigator is not taking file locations into account while compiling, so any relative pathing (e.g. $?FILE) is not going to work correctly. The file does not compile in place because a user may be editing the file, so we need to compile the unsaved version that does not exist on disk.
Currently, the code and file-path are both passed into navigator.raku, but file-path is not currently utilized. This would be a great improvement, but I'm not currently sure how to do it. If anyone has any suggestions, or would like to make a pull request, that would be great.
https://github.com/bscan/RakuNavigator/blob/master/server/src/raku/navigator.raku

Another option available is using the setting raku.includePaths. This is an array that lets you add things to the search path and you could add "raku.includePaths": ["/path/to/folder/lib"]
I should probably also start adding "./lib" by default. In the Perl version, when you have a folder or workspace open, it will automatically add the ./lib folder as an include path.
https://github.com/bscan/PerlNavigator/blob/1f3e38e74277f1f95b6a4a10012a71eb9826b109/server/src/utils.ts#L31


unable to run the project on aws ec2

Do you want to request a feature or report a bug?
unable to run the project
What is the current behavior?
unable to run the project
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
i am trying to run the graph node , in aws ec2 (ubuntu 18.04.6 LTS 4 GB RAM, GNU/Linux 5.4.0-1060-aws x86_64 ) with aws rds postgres sql db (without using ssl/tls)

In ec2, install IPFS and run ipfs init followed by ipfs daemon.

Create PostgreSQL DB in aws rds
In ec2 , clone https://github.com/graphprotocol/graph-node did,  cargo build

cargo run -p graph-node --release --
--postgres-url postgresql://SUPER_USER:SUPER_USER_PW@DBURL....rds.amazonaws.com:5432/graphdb
--ethereum-rpc mainnet:https://mainnet.infura.io/v3/INFURA_ID
--ipfs <IP_ADDRESS>:5001

In ec2 , clone https://github.com/graphprotocol/example-subgraph , then did
yarn
yarn codegen
yarn create-local
yarn deploy-local

the i notice that in the db some tables has created.But as soon as i hit "yarn deploy-local", it give me error
✖ Failed to deploy to Graph node http://<IP_ADDRESS>:8020/: subgraph resolve error: resolve error: No IPFS clients were supplied to handle the call to object.stat. File: QmXfCx2FYrBhbm7WP8Mn5N
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

and the logs from the graph-node says.
warning: graph-node (lib) generated 4 warnings
Finished release [optimized] target(s) in 0.31s
Running target/release/graph-node --postgres-url 'postgresql://postgres:abcd1234@database-2.cyf4genvizjn.us-east-1.rds.amazonaws.com:5432/graphdb' --ethereum-rpc 'mainnet:https://main9'
Dec 10 11:22:43.942 INFO Graph Node version: v0.25.0 (4bdb0640b 2021-12-01)
Dec 10 11:22:43.942 INFO Generating configuration from command line arguments
Dec 10 11:22:43.942 INFO Starting up
Dec 10 11:22:43.942 INFO Creating transport, capabilities: archive, traces, url: https://mainnet.infura.io/v3/6e7e3dc04b744e2f8ab3c4e965eb0839, provider: mainnet-rpc-0
Dec 10 11:22:44.025 INFO Connecting to Postgres, weight: 1, conn_pool_size: 10, url: postgresql://postgres:HIDDEN_PASSWORD@database-2.cyf4genvizjn.us-east-1.rds.amazonaws.com:5432/graphdb,
Dec 10 11:22:44.026 INFO Pool successfully connected to Postgres, pool: main, shard: primary, component: Store
Dec 10 11:22:44.081 INFO Setting up fdw, pool: main, shard: primary, component: ConnectionPool
Dec 10 11:22:44.097 INFO Running migrations, pool: main, shard: primary, component: ConnectionPool
Dec 10 11:22:44.103 INFO Migrations finished, pool: main, shard: primary, component: ConnectionPool
Dec 10 11:22:44.103 INFO Mapping primary, pool: main, shard: primary, component: ConnectionPool
Dec 10 11:22:44.135 INFO Connecting to Ethereum to get network identifier, capabilities: archive, traces, provider: mainnet-rpc-0
Dec 10 11:22:44.145 INFO Connected to Ethereum, capabilities: archive, traces, network_version: 1, provider: mainnet-rpc-0
Dec 10 11:22:44.151 INFO Creating LoadManager in disabled mode, component: LoadManager
Dec 10 11:22:44.152 INFO Starting block ingestors with 1 chains [mainnet]
Dec 10 11:22:44.152 INFO Starting block ingestor for network, network_name: mainnet
Dec 10 11:22:44.152 INFO Starting job runner with 3 jobs, component: JobRunner
Dec 10 11:22:44.155 INFO Starting JSON-RPC admin server at: http://localhost:8020, component: JsonRpcServer
Dec 10 11:22:44.155 INFO Starting GraphQL HTTP server at: http://localhost:8000, component: GraphQLServer
Dec 10 11:22:44.155 INFO Starting index node server at: http://localhost:8030, component: IndexNodeServer
Dec 10 11:22:44.155 INFO Starting metrics server at: http://localhost:8040, component: MetricsServer
Dec 10 11:22:44.155 INFO Started all assigned subgraphs, node_id: default, count: 0, component: SubgraphRegistrar
Dec 10 11:22:44.156 INFO Starting GraphQL WebSocket server at: ws://localhost:8001, component: SubscriptionServer
Dec 10 11:22:57.343 INFO Syncing 1 blocks from Ethereum., code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 13777094, current_block_head: 13777093, provider
Dec 10 11:23:33.068 INFO Syncing 1 blocks from Ethereum., code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 13777095, current_block_head: 13777094, provider
Dec 10 11:23:42.772 INFO Syncing 2 blocks from Ethereum., code: BlockIngestionStatus, blocks_needed: 2, blocks_behind: 2, latest_block_head: 13777097, current_block_head: 13777095, provider
Dec 10 11:24:00.514 INFO Syncing 1 blocks from Ethereum., code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 13777098, current_block_head: 13777097, provider
Dec 10 11:24:02.056 INFO Received subgraph_deploy request, params: SubgraphDeployParams { name: SubgraphName("example"), ipfs_hash: DeploymentHash("QmXfCx2FYrBhbm7WP8Mn5N6ERbY3jfKVqjntZZYmyer
Dec 10 11:24:02.056 ERRO subgraph_deploy failed, params: SubgraphDeployParams { name: SubgraphName("example"), ipfs_hash: DeploymentHash("QmXfCx2FYrBhbm7WP8Mn5N6ERbY3jfKVqjntZZYmyNhPRy"), n(No IPFS clients were supplied to handle the call to object.stat. File: QmXfCx2FYrBhbm7WP8Mn5N6ERbY3jfKVqjntZZYmyNhPRy)), component: JsonRpcServer
Dec 10 11:24:28.220 INFO Syncing 1 blocks from Ethereum., code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 13777099, current_block_head: 13777098, provider: mainnet-rpc-0, component: BlockIngestor
Dec 10 11:24:34.981 INFO Syncing 1 blocks from Ethereum., code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 13777100, current_block_head: 13777099, provider: mainnet-rpc-0, component: BlockIngestor
Dec 10 11:24:54.956 INFO Syncing 1 blocks from Ethereum., code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 13777101, current_block_head: 13777100, provider: mainnet-rpc-0, component: BlockIngestor
Dec 10 11:25:11.082 INFO Syncing 1 blocks from Ethereum., code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 13777102, current_block_head: 13777101, provider: mainnet-rpc-0, component: BlockIngestor
Dec 10 11:25:19.226 INFO Syncing 1 blocks from Ethereum., code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 13777103, current_block_head: 13777102, provider: mainnet-rpc-0, component: BlockIngestor
Dec 10 11:25:23.014 INFO Syncing 1 blocks from Ethereum., code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 13777104, current_block_head: 13777103, provider: mainnet-rpc-0, component: BlockIngestor
Dec 10 11:25:38.103 INFO Syncing 1 blocks from Ethereum., code: BlockIngestionStatus, blocks_needed: 1, blocks_behind: 1, latest_block_head: 13777105, current_block_head: 13777104, provider: mainnet-rpc-0, component: BlockIngestor

for the testing i allowed all the inbound/outbound ports in aws ec2

What is the expected behavior?
should run without any issue.
Can some one help me on this matter ? I am unable to fix the issue and get it to run.

At glance can't provide much help other than it looks like an issue in the connection between graph node and the ipfs node.

@leoyvens thank you very much for the reply.
The graph node communicate  with ipfs via port 5001.Both are in the same ec2 and port 5001 is running.Is their can way i can trouble shoot the problem ?

I'm getting the exact same error, using e2-micro (gcp), yet I'm running postgres locally (localhost:5432) and using the --ethereum-ws parameter.
The instance of the node had following to say about it (which is essentially the same as the result of yarn deploy-local):
Note: my "deployment hash" happens to be the same as for OP. I didn't go through the source yet, probably that's intended, as we probably both used the example subgraph(?)
ERRO subgraph_deploy failed, params: SubgraphDeployParams { name: SubgraphName("example"), ipfs_hash: DeploymentHash("QmXfCx2FYrBhbm7WP8Mn5N6ERbY3jfKVqjntZZYmyNhPRy"), node_id: None }, error: ResolveError(ResolveError(No IPFS clients were supplied to handle the call to object.stat. File: QmXfCx2FYrBhbm7WP8Mn5N6ERbY3jfKVqjntZZYmyNhPRy)), component: JsonRpcServer.

@ronidee.
After the above issue,
I tried with https://hub.docker.com/r/graphprotocol/graph-node. And it worked.
the only difference i did was , run the ipfs daemon  with screen (https://linuxize.com/post/how-to-use-linux-screen/).(you can run it as a service).
After this i did not run the original code and run it. But the docker works.Data saved in PostgreSQL.
I added a version number and keep on increasing with every deployment.

i checked, with the graph-node (not the docker), it is not working, but the docker is working.
can some one help me one this?

@tharinduk90 did you build the docker image yourself or used the one you linked?
I am having issues building it myself (the "extra step for linux users").
And how did you connect the graph-node inside the docker container to your local ethereum node?
If this is too off-topic I apologize. Please delete my comment then, I'll create a separate issue for it then.

I used the docker that has been published.Did not try to build the docker image.Fo ubuntu I did not able to run the project, the mentioned error occurs.
I connected the the graph-node inside the docker container to local(host) ipfs node like below, hope this will help.
sudo docker run -it --network="host"
-e postgres_host=DATABASE_URL
-e postgres_port=5432
-e postgres_user=POSTGRES_USER
-e postgres_pass= POSTGRES_PW
-e postgres_db=graph-node
-e ipfs=http://<IP_ADDRESS>:5001
-e ethereum=mainnet:https://mainnet.infura.io/v3/INFURA_ID
graphprotocol/graph-node:latest
http://<IP_ADDRESS>:5001 => this is running in host
https://docs.docker.com/network/host/

hi @tharinduk90 - to confirm, the issue you are having is still when you yarn deploy-local?
Does it work if you use
-e ipfs=http://host.docker.internal:5001

@tharinduk90 @ronidee hey guys, did you solve the issue? if so, can you tell us how? I'm having the same problem locally. Thanks!


Error compiling on armhf platform

Hi everyone,
I am getting an error when compiling the library as part of hyperledger fabric (fabric-amcl) on a raspberry pi 4 (raspbian, armhf architecture). As far as I can tell it is due to the int representation on 32-bit platforms which could be easily fixed.  Or am I the only crazy person trying to compile the hyperledger fabric images on 32-bit architecture? :) I am trying to do this in order to lower the hurdles in deploying hyperledger fabric on standard raspberry pis for people who are not well versed with blockchain and/or uncommon cpu architectures.

Hello,
The AMCL library supports both 32 and 64-bit versions. Here it would appear
that a 64-bit build is being used on a 32-bit architecture.
So solution is to use a 32-bit build of the library. See
https://github.com/miracl/amcl/blob/master/version3/go/readme.txt
Mike
On Wed, Jan 13, 2021 at 8:26 AM Razvan Hrestic<EMAIL_ADDRESS>wrote:

Hi everyone,
I am getting an error when compiling the library as part of hyperledger
fabric (fabric-amcl) on a raspberry pi 4 (raspbian, armhf architecture). As
far as I can tell it is due to the int representation on 32-bit platforms
which could be easily fixed.  Or am I the only crazy person trying to compile the
hyperledger fabric images on 32-bit architecture? :) I am trying to do this
in order to lower the hurdles in deploying hyperledger fabric on standard
raspberry pis for people who are not well versed with blockchain and/or
uncommon cpu architectures.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/miracl/amcl/issues/56, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAU3ZDQNYPT4I42Y4HTK6W3SZVKNFANCNFSM4WANUXRQ
.

Hello,
The AMCL library supports both 32 and 64-bit versions. Here it would appear
that a 64-bit build is being used on a 32-bit architecture.
So solution is to use a 32-bit build of the library. See
https://github.com/miracl/amcl/blob/master/version3/go/readme.txt
Mike
On Wed, Jan 13, 2021 at 8:26 AM Razvan Hrestic<EMAIL_ADDRESS>wrote:

Hi everyone,
I am getting an error when compiling the library as part of hyperledger
fabric (fabric-amcl) on a raspberry pi 4 (raspbian, armhf architecture). As
far as I can tell it is due to the int representation on 32-bit platforms
which could be easily fixed.  Or am I the only crazy person trying to compile the
hyperledger fabric images on 32-bit architecture? :) I am trying to do this
in order to lower the hurdles in deploying hyperledger fabric on standard
raspberry pis for people who are not well versed with blockchain and/or
uncommon cpu architectures.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/miracl/amcl/issues/56, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAU3ZDQNYPT4I42Y4HTK6W3SZVKNFANCNFSM4WANUXRQ
.

Hello Mike,
thanks for the tip, I will try this and post the result here.
Best regards,
Razvan

Hello Mike,
thanks for the tip, I will try this and post the result here.
Best regards,
Razvan

Hi again, I have tried the steps and the TL;DR; of it is: it worked :) so many thanks with that!
The long version of it is that I had to do a bit more work to integrate the 32-bit-version back into the fabric-amcl repository:

Used the python-script to change to 32-bit as in the amcl-readme file
Selected only FP265BN (the only one in fabric-amcl) when prompted by the script (option 22 I believe)
Copied the generated amcl folder over the old repo (locally inside the vendor folder structure, I did not push the changes)
Changed the import directives for some of the files so that the do not point to the miracl-repository but rather to the fabric-amcl repo, so that the import looked like this: import "github.com/hyperledger/fabric-amcl/amcl"

Build process for hyperledger fabric then worked without any errors.

Hi again, I have tried the steps and the TL;DR; of it is: it worked :) so many thanks with that!
The long version of it is that I had to do a bit more work to integrate the 32-bit-version back into the fabric-amcl repository:

Used the python-script to change to 32-bit as in the amcl-readme file
Selected only FP265BN (the only one in fabric-amcl) when prompted by the script (option 22 I believe)
Copied the generated amcl folder over the old repo (locally inside the vendor folder structure, I did not push the changes)
Changed the import directives for some of the files so that the do not point to the miracl-repository but rather to the fabric-amcl repo, so that the import looked like this: import "github.com/hyperledger/fabric-amcl/amcl"

Build process for hyperledger fabric then worked without any errors.

Nice one! Glad it worked out..
Mike
On Sun, Jan 24, 2021 at 9:54 PM Razvan Hrestic<EMAIL_ADDRESS>wrote:

Hi again, I have tried the steps and the TL;DR; of it is: it worked :) so
many thanks with that!
The long version of it is that I had to do a bit more work to integrate
the 32-bit-version back into the fabric-amcl repository:

Used the python-script to change to 32-bit as in the amcl-readme
file
Selected only FP265BN (the only one in fabric-amcl) when prompted
by the script (option 22 I believe)
Copied the generated amcl folder over the old repo (locally inside
the vendor folder structure, I did not push the changes)
Changed the import directives for some of the files so that the do
not point to the miracl-repository but rather to the fabric-amcl repo, so
that the import looked like this: import "
github.com/hyperledger/fabric-amcl/amcl"

Build process for hyperledger fabric then worked without any errors.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/miracl/amcl/issues/56#issuecomment-766438744, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAU3ZDSI665PMETCHVZXTN3S3SJI7ANCNFSM4WANUXRQ
.

Nice one! Glad it worked out..
Mike
On Sun, Jan 24, 2021 at 9:54 PM Razvan Hrestic<EMAIL_ADDRESS>wrote:

Hi again, I have tried the steps and the TL;DR; of it is: it worked :) so
many thanks with that!
The long version of it is that I had to do a bit more work to integrate
the 32-bit-version back into the fabric-amcl repository:

Used the python-script to change to 32-bit as in the amcl-readme
file
Selected only FP265BN (the only one in fabric-amcl) when prompted
by the script (option 22 I believe)
Copied the generated amcl folder over the old repo (locally inside
the vendor folder structure, I did not push the changes)
Changed the import directives for some of the files so that the do
not point to the miracl-repository but rather to the fabric-amcl repo, so
that the import looked like this: import "
github.com/hyperledger/fabric-amcl/amcl"

Build process for hyperledger fabric then worked without any errors.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/miracl/amcl/issues/56#issuecomment-766438744, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAU3ZDSI665PMETCHVZXTN3S3SJI7ANCNFSM4WANUXRQ
.


HX711: unstable readings and reading before data is ready

Describe the bug
The included HX711 driver does not respect the timing specifications described in the datasheet, and generates mostly false readings.
To Reproduce
Steps to reproduce the behavior:

Run program

package main

import (
	"fmt"
	"os"
	"periph.io/x/periph/experimental/devices/hx711"
	"periph.io/x/periph/host"
	"periph.io/x/periph/host/rpi"
	"time"
)

func main() {
	host.Init()
	if err := mainE(); err != nil {
		fmt.Fprintln(os.Stderr, "error:", err)
		os.Exit(1)
	}
}

func mainE() error {
	// HX711 board configured with CLK @ P1_31 and DOUT @ P1_29
	hx, err := hx711.New(rpi.P1_31, rpi.P1_29)
	if err != nil {
		return err
	}

	time.AfterFunc(10*time.Second, func() { hx.Halt() })

	sampleCh := hx.ReadContinuous()
	for s := range sampleCh {
		// observe that many samples are garbage
		fmt.Printf("%8d\n", s.Raw)
	}
	return nil
}

Run it.
See that many samples are garbage. For me, half of all samples is -1; and many samples are suspiciously 2^n - 1.

Expected behavior
The driver should ideally read data when data is ready. In this case we see that samples are occasionally read out as garbage because data isn't ready or DOUT isn't stable.
Platform (please complete the following information):

OS: Raspbian buster
Board: Raspberry Pi 2 Model B v1.1
Peripheral: Cheapo oem HX711 (https://www.amazon.com/gp/product/B00XRRNCOO/ref=ppx_yo_dt_b_asin_title_o04_s00?ie=UTF8&psc=1)

Additional context
The AviaSC datasheet (https://components101.com/sites/default/files/component_datasheet/HX711 Datasheet.pdf) provides a timing specification for the HX711. Note that it specifies a minimum of .1us after a falling edge on DOUT before data is ready to be read, and that it additionally specifies that DOUT is not stable until .1us after the rising edge on CLK. Additionally, it expects pulse width on CLK to be at least 1us.
I checked out the driver and first tried to fix this by adding sleeps, but interrupts are too coarse-grained to make .1-100us sleeps meaningful. I replaced sleeps with fine-grained busy waits, and eliminated the readings of -1.
I continued to get odd 2^n - 1 readings, so I replaced the WaitForEdge call in ReadTimeout with a busy wait (for !d.IsReady() {}), and this seems to have eliminated all or almost all of the garbage readings I was getting. I think that this could be evidence of false GPIO edge detection as described in this thread: https://www.raspberrypi.org/forums/viewtopic.php?t=134394.
I have only tested this with one board. I intend to see if I can get better readings the other HX711 boards I have, and potentially with one of those fancy $15 HX711s they sell at Sparkfun if issues persist.

At worst maybe use https://periph.io/x/periph/host/cpu#Nanospin ?

If you still face issues, Please file a bug at https://github.com/periph/devices. Will close for now as there's no AI.


Sample for report_tensor_allocations_upon_oom and RunOptions

This is a feature request.
Please add some example to the docs describing how to use report_tensor_allocations_upon_oom and other options of RunOptions
All I could find is this file:
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/profiler/model_analyzer_test.py
But it is not obvious. For example, it contains:
from tensorflow.core.protobuf import config_pb2

and then
with session.Session() as sess:
    sess.run(c, options=config_pb2.RunOptions(
        report_tensor_allocations_upon_oom=True))

And more questions arise like: "What is config_pb2?" etc.
Thanks.

@Yagun Do you care about CPU, GPU, or both?

I got it work like this:
run_options = tf.RunOptions(report_tensor_allocations_upon_oom = True)
sess.run(op, feed_dict=fdict, options=run_options)

This will produce messages like this :
tensorflow.python.framework.errors_impl.ResourceExhaustedError: OOM when allocating tensor with shape[100000,60,190] and type double on /job:localhost/replica:0/task:0/device:GPU:0 by allocator GPU_0_bfc
         [[Node: Tile = Tile[T=DT_DOUBLE, Tmultiples=DT_INT32, _device="/job:localhost/replica:0/task:0/device:GPU:0"](ExpandDims, Tile/multiples)]]

Current usage from device: /job:localhost/replica:0/task:0/device:GPU:0, allocator: GPU_0_bfc
  144.96MiB from cKR/sub

         [[Node: concat/_11 = _Recv[client_terminated=false, recv_device="/job:localhost/replica:0/task:0/device:CPU:0", send_device="/job:localhost/replica:0/task:0/device:GPU:0", send_device_incarnation=1, tensor_name="edge_8207_concat", tensor_type=DT_DOUBLE, _device="/job:localhost/replica:0/task:0/device:CPU:0"]()]]

Current usage from device: /job:localhost/replica:0/task:0/device:GPU:0, allocator: GPU_0_bfc
  144.96MiB from cKR/sub

But it seems like, it does not contain all allocation therefore rendering it a bit pointless :/
The Error message above is for a 15GB p100 gpu and it says it only allcoated 145 MB, but fails on allocating  a tesnor of shape [100000,60,190] -> around 9GB.
@cy89 is there a way to get even more details?

@cy89, I care about GPU more, because it usually has 2 to 4 GB RAM.
@georgh, thank you very much for this example.

@zheng-xq can you please point @georgh at tools he can use to better inspect GPU memory allocation? Or is there a docs page we can point him at, or build for him?

@cy89 @zheng-xq
The main problem I encountered was the missing allocation information for placeholders. My findings regarding the problem are summarized in #17092 (would be great if a tensorflower would take a look at this)
I think doc pages for inspecting GPU allocation would be great. But I just found
https://www.tensorflow.org/programmers_guide/debugger and https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/profiler/README.md
so this might be the tool / docs I didn't find before. (Side has changed quite a bit since the last time I had a look) Maybe they even display placeholder memory usage. Have to test them now.

Nagging Awaiting TensorFlower: It has been 14 days with no activity and the awaiting tensorflower label was assigned. Please update the label and/or status accordingly.

Nagging TensorFlower: It has been 14 days with no activity and the awaiting tensorflower label was assigned. Please update the label and/or status accordingly.

I agree that this is a good feature request, i.e. there should be a guide to memory use debugging in TF, especially GPU memory use since there are some non-obvious tricks going on.   Eventually someone from TF will probably get around to doing it, but probably not soon, so I'm going to mark it contributions welcome.  @geogh I see that you made some progress in the other thread, using @yaroslavvb 's tool.  It would be great if either of you want to contribute some notes on this topic.

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

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

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

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

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

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

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

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

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

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

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

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

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

Kindly requesting what is the status of this ticket?

I would like to know most recent status of this ticket.

Also pinging in here. TF reports

Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info

But there doesn't seem to be a way to do that in TF 2.x

Also pinging in here. TF reports

Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info

But there doesn't seem to be a way to do that in TF 2.x

My previous comment seems to have been missed: There still doesn't seem to be a way to get the OOM info in TF 2 as indicated by the error message shown by TF 2. See also https://github.com/tensorflow/tensorflow/issues/37556 and https://github.com/tensorflow/tensorflow/blob/78d7f8b2ef12509d5f47f16ccf242f861f222636/tensorflow/core/common_runtime/executor.cc#L989-L991

@Flamefire,
Did you try Profiler Tool, mentioned in this comment?

Not yet as it involves some setup and usage of a notebook which is a bit involved when running on HPC nodes. Adding some option to have some output on the stdout/stderr in case of failure would have been much more usable in that context.
And if  that is not possible, then TF should not tell you so in its error message. I spend quite some time looking how to follow the advice of "add report_tensor_allocations_upon_oom to RunOptions".
In the end this is what this issue is about: Either there is a way to do that in TF2, then some documentation is needed, or there is not, then it should be added (preferably) or the error message changed.

What's wrong with the bot? There has been activity here since its last comment, so why close it?

@Flamefire,
Sorry for the inconvenience. Reopened the issue.

amazing. this bug is 4 years old and still open

.

5 yrs...

Today was the day that I learned that Tensorflow has been generating this incorrect output message FOR SIX YEARS, while multiple people have asked about it.  Wow.
Hint: If you want to see a list of allocated tensors when OOM happens, add report_tensor_allocations_upon_oom to RunOptions for current allocation info. This isn't available when running in Eager mode.

Using the profiler is not an option for me because it simply doesn't work.  "The profile plugin has moved."  Regardless of all attempts to get it working.
If there is no way to,"add report_tensor_allocations_upon_oom to RunOptions for current allocation info", then someone really needs to remove that message.


Draft: Emit type stubs

Basically this needs to handle a few things to work:

Create a virtual output module which is to be stubbed.
Add actual python entities (functions, classes, module variables) to be type stubbed in this module's namespace (could often just be the vars of the module, minus any imports)
Traverse all the types used in annotations and make sure the required imports are added to the emitted type stub
Generate source code with annotations and empty bodies

For this to work with synchronicity, we also need to make sure that synchronicity's emitted classes translate things properly with annotations (and some function name translation like __aenter__ -> __enter__). This is handled in the base PR #84
TODOs:

[x] Functions
[x] Classes
[x] classmethod/staticmethod/properties
[x] Class annotations
[x] Module vars
[x] Test with mypy
[x] e2e tests with synchronicity + annotations
[x] Fix regression: *args and **kwargs are now emitted as arguments to wrapped functions... Probably need to skip using inspect.Signature() altogether for function signatures...
[x] Base classes
[x] TypeVars
[x] Forward/Self references ("str" annotations)
[x] cli util for emitting type stub for an input python file

Future improvements:

[ ] Include docstrings
[ ] Include argument comments (this would let us generate even better reference docs for our generated classes too!)
[ ] Generate actual source code and not just type stubs, using the synchronicity base classes as implementation (!)

Nice!  Feels like those assertions will have a high maintenance cost. Is it possible to check for equality in a more fuzzy way, like can you get the AST and make sure it's equal?

This only returns the current interface right? It doesn't translate it to a blocking interface yet right?

This only returns the current interface right? It doesn't translate it to a blocking interface yet right?

Yes, the translation happens in #84 before this code gets the interface handed to it. I intentionally separated the two processes (and PR:s).

In #84 we translate all of the annotations from async to the blocking interface, such that the generated classes have the correct annotations for their "blockyness"
In this PR, we take runtime annotations of any class and output them as source stubs. As it stands this is entirely decoupled from the rest of synchronicity, but works on the generated classes that synchronicity emits. It could be a separate project/package/repo entirely, but I think we'll eventually want to get synchronicity specific stuff in here as well (for example actual source generation based on the annotations...)

Now successfully generates a valid stub for the modal root package: https://gist.github.com/freider/04dd81718dad5fb05c9a982bba082182


Develop

Codecov Report

Merging #207 (836b8fd) into master (709e178) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master     #207   +/-   ##
=======================================
  Coverage   85.68%   85.68%
=======================================
  Files          17       17
  Lines         517      517
  Branches      132      132
=======================================
  Hits          443      443
  Misses         17       17
  Partials       57       57

Impacted Files
Coverage Δ

src/lib/task.ts
83.15% <0.00%> (ø)

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 709e178...836b8fd. Read the comment docs.

:tada: This PR is included in version 3.2.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Proposal] Add boolean function 'has_item' to Inventory class

Could you add a boolean function to the Inventory class which allows to check whether an item is currently in the inventory.
func has_item(item: InventoryItem) -> bool:
This would reduce the need to keep an additional status variable for every item taken.
Thanks,  Thomas

Done. Thanks for the suggestion.


Nested Body Blocks

So far only a method has a block, but to be correct, Plume lacks the following blocks:

A block for an IF and ELSE body
A block for SWITCH statement bodies

Plume cannot yet determine a while/do-while/for-loop (and using bytecode, that is challenging to do accurately) so these two are fine to cover now. This is more of an AST problem as UnitGraphs are CFGs so perhaps a different representation is required for this.

Does this problem make some confliction on query?

Not that I'm aware of. CONTROL_STRUCTURE and BLOCK vertices are only really a thing on the source-code frontends anyway since it's more to do with the AST. Most of the AST info is lost in bytecode anyway so the only important stuff is that the CFG and data dependencies are correct.
That's why I've marked this as low priority.

JVM bytecode and Jimple have flat ASTs - so no need to worry about this issue


Export military graphics to KML

Is there a property exposed that would give us the complete graphic points for drawing these symbols in Google Earth? We would like to be able to retrieve this information from the Graphic or the Message so that we can export it in a KML and it would look correct in Google Earth.
For example, a FLOT may have only two control points but could potentially have hundreds of drawn points to get it to look like it should. This is a request from our military customer.

Currently the message layer abstracts a lot of the layers and graphics properties that one might need to get at. Given the map is at a current scale how can we get the individual geometries for the stylized military symbology?


Android tab shifiting on Target version 28 and Xamarin.Android support nugets 28.0

when I upgrade android target to 28.
and update android support NuGet packages to 28.0.
tabShifting no longer works.
Severity	Code	Description	Project	File	Line	Suppression State Error	CS1061	'BottomNavigationItemView' does not contain a definition for 'SetShiftingMode' and no accessible extension method 'SetShiftingMode' accepting a first argument of type 'BottomNavigationItemView' could be found (are you missing a using directive or an assembly reference?)	CustomTabbedPage.Android	[***ProjectPath***]\ExtendedTabbedPageSample-master\CustomTabbedPage.Android\ExtendedTabbedPageRenderer.cs	193	Active
looks like  item.SetShiftingMode(enableItemShiftMode); is not available anymore.

@prasadsunny1 any solution? please update here?


Multiple matches from a single rule query

I'm trying flatline especially with threshold setting to 1, hoping to have an alert with no events for the query.
By the way, with 0 hits it sometimes reports more than 1 matches and alerts (with a repeating pattern) .  I tried many different combinations of all the time-related settings; run_every, buffer_time, timeframe as well as data-arrival interval, but still cannot understand why it could generate multiple matches/alerts from 0 hits.
My question is general. Can elastalert make multiple matches/alerts with a single query result (from a single rule execution), and how?
Thanks.

This is a known issue. Basically, it will sometimes split up a time period into two queries.
For example, run_every is 1 minute, but it tries to query 12:00 to 12:01:01, which is very slightly longer than a minute. Elastalert will then segment that into 1 minute pieces, with the second one consisting of only 1 second. Each query generates an alert because there are still no documents.
The default realert should prevent these extra matches from every being alerts.

Yeah we noticed the query window is slightly longer just like you mentioned. Okay fair enough. We will handle this in the enhancement.
Thanks!

This is on my list of things to fix.


Complete Math Magician Website

Set up a complete app with routes

Add home and quotes page components
Style components
Connect components using routers

Oh dang! I added a CSS style that overrode the previous ones, totally forget to check the whole thing before pushing 🤦🏾♂


Add geant-val fataset 1.3_1

Changes needed to create and upload to geant-val results with v1.3 and G4-11.2.p01:

Add script for lxplus usage with G4-11.2.p01 and el9 lxplus machines (0a5e70fba8c22b9ba3d773578b4b6872d47b720d c2ac79cdb257502859adf10b97edbdf32f2ad6c3)
Fix bug in gval config script used with G4-11.1.p01 (4c6b3a9bb57001ecb9fa507238a83d5da0bcf626)
Add gval config file for G4-11.2.p01 (54a40fcb53d5cba30fee93b5b604f9cc65b571e0)
Remove spaces in analysis.root graph names called by parser.py (2926aae5754eed2fd2ee19211f012ac0c99ebfce)
Add 1.3_1 dataset in geant-val results table (513b89e41245d4ca66833bd3cf53046682fa8268)

Accepting PR #58.


[release-1.3] fix(gateway template): patch gateway to include same env var as sidecar

This is an automated cherry-pick of #16463

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-presubmit-tests-release-1.3
780799bcbad19fee87f84421285218913810b17c
link
/test integ-new-install-k8s-presubmit-tests-release-1.3

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

This is a follow up of https://github.com/istio/istio/pull/16462 which is already merged into 1.3. This is to make gateway has the same node metadata as proxy.

@rlenglet this is a low risk PR that adds 3 env vars to gateways to bring it in compliance with new metadata set , just like sidecar.


fix: update gatsby to v3

I have tested this locally and gatsby builds as expected.
fixes: #4

@jamaljeantobias Thanks for getting this merged so quickly! 👍🏻

Thank you.