Error in Tensorflow_MNIST Tutorial numpy version 1.24.1

Describe the bug
While running Director Workflow Tensorflow_MNIST Tutorial on WSL (Ubuntu 20.04) it gives an error
Experiment "mnist_experiment" failed with error: module 'numpy' has no attribute 'int'.
To Reproduce
Steps to reproduce the behavior:

python -m venv venv
source venv/bin/activate
python -m pip install -U pip setuptools wheel
git clone https://github.com/intel/openfl.git
cd openfl/
pip install .
cd openfl/openfl-tutorials/interactive_api/Tensorflow_MNIST
cd director
./start_director.sh
cd envoy
./start_envoy.sh env_one envoy_config_one.yaml
cd workspace
code .
Run the experiment in Visual Studio code Remotely

Expected behavior
Experiment should run successfully without any error
Error logs
Error message while running the experiment
INFO     🧿 Created an Aggregator Server for mnist_experiment experiment.                                                           experiment.py:131
INFO     Building 🡆  Object CloudpickleSerializer from openfl.plugins.interface_serializer.cloudpickle_serializer Module.                  plan.py:171
INFO     Building 🡆  Object KCPipeline from openfl.pipelines Module.                                                                       plan.py:171
INFO     Building 🡆  Object CutoffTimeBasedStragglerHandling from openfl.component.straggler_handling_functions Module.                    plan.py:171
INFO     Building 🡆  Object Aggregator from openfl.component Module.                                                                       plan.py:171
ERROR    Experiment "mnist_experiment" failed with error: module 'numpy' has no attribute 'int'.                                     experiment.py:94
Traceback (most recent call last):
File "/home/ithakarx/newEnv/lib/python3.8/site-packages/openfl/component/director/experiment.py", line 76, in start
aggregator_grpc_server = self._create_aggregator_grpc_server(
File "/home/ithakarx/newEnv/lib/python3.8/site-packages/openfl/component/director/experiment.py", line 132, in
create_aggregator_grpc_server
aggregator_grpc_server = plan.interactive_api_get_server(
File "/home/ithakarx/newEnv/lib/python3.8/site-packages/openfl/federated/plan/plan.py", line 559, in
interactive_api_get_server
server_args['aggregator'] = self.get_aggregator(tensor_dict)
File "/home/ithakarx/newEnv/lib/python3.8/site-packages/openfl/federated/plan/plan.py", line 338, in get_aggregator
self.aggregator = Plan.build(**defaults, initial_tensor_dict=tensor_dict)
File "/home/ithakarx/newEnv/lib/python3.8/site-packages/openfl/federated/plan/plan.py", line 182, in build
instance = getattr(module, class_name)(**settings)
File "/home/ithakarx/newEnv/lib/python3.8/site-packages/openfl/component/aggregator/aggregator.py", line 114, in init
self.model = utils.construct_model_proto(
File "/home/ithakarx/newEnv/lib/python3.8/site-packages/openfl/protocols/utils.py", line 137, in construct_model_proto
bytes_data, transformer_metadata = tensor_pipe.forward(data=nparray)
File "/home/ithakarx/newEnv/lib/python3.8/site-packages/openfl/pipelines/pipeline.py", line 134, in forward
data, metadata = transformer.forward(data=data, **kwargs)
File "/home/ithakarx/newEnv/lib/python3.8/site-packages/openfl/pipelines/kc_pipeline.py", line 52, in forward
int_array, int2float_map = self._float_to_int(quant_array)
File "/home/ithakarx/newEnv/lib/python3.8/site-packages/openfl/pipelines/kc_pipeline.py", line 91, in _float_to_int
int_array = np.zeros(flatten_array.shape, dtype=np.int)
File "/home/ithakarx/newEnv/lib/python3.8/site-packages/numpy/init.py", line 284, in getattr
raise AttributeError("module {!r} has no attribute "
AttributeError: module 'numpy' has no attribute 'int'
Desktop (please complete the following information):

OS: Windows 11 (WSL2 Ubuntu 20.04)
Python 3.8.15

Additional context
All the Requirements and Packages which are installed by default
Building wheels for collected packages: openfl
Building wheel for openfl (setup.py) ... done
Created wheel for openfl: filename=openfl-1.4-py3-none-any.whl size=4509686 sha256=8e3daff1638d5c6bb04aa2edc5d90555230d4537ca7277c289b4c51176690641
Stored in directory: /tmp/pip-ephem-wheel-cache-715cmxmu/wheels/fc/db/71/bf72d95009ad0434707fc5ba52b00d079e8e9bc867da4dc724
Successfully built openfl
Installing collected packages: webencodings, wcwidth, tensorboard-plugin-wit, send2trash, pytz, pyasn1, pure-eval, ptyprocess, pickleshare, mistune, json5, ipython-genutils, fastjsonschema, executing, commonmark, charset-normalizer, backcall, zipp, websocket-client, webcolors, urllib3, uri-template, typing-extensions, traitlets, tqdm, tornado, tomli, tinycss2, threadpoolctl, tensorboard-data-server, soupsieve, sniffio, six, rsa, rfc3986-validator, pyzmq, PyYAML, python-json-logger, pyrsistent, pygments, pycparser, pyasn1-modules, psutil, protobuf, prompt-toolkit, prometheus-client, platformdirs, pkgutil-resolve-name, pexpect, parso, pandocfilters, packaging, oauthlib, numpy, nest-asyncio, MarkupSafe, jupyterlab-pygments, jsonpointer, joblib, idna, fqdn, entrypoints, dynaconf, defusedxml, decorator, debugpy, cloudpickle, Click, certifi, cachetools, babel, attrs, absl-py, werkzeug, terminado, tensorboardX, scipy, rich, rfc3339-validator, requests, python-dateutil, matplotlib-inline, jupyter-core, jinja2, jedi, importlib-resources, importlib-metadata, grpcio, google-auth, flatten_json, comm, cffi, bleach, beautifulsoup4, asttokens, anyio, stack-data, scikit-learn, requests-oauthlib, pandas, markdown, jupyter-server-terminals, jupyter-client, jsonschema, docker, cryptography, arrow, argon2-cffi-bindings, nbformat, isoduration, ipython, google-auth-oauthlib, argon2-cffi, tensorboard, nbclient, ipykernel, nbconvert, jupyter-events, jupyter-server, notebook-shim, jupyterlab-server, nbclassic, notebook, jupyterlab, openfl
Successfully installed Click-8.0.1 MarkupSafe-2.1.1 PyYAML-6.0 absl-py-1.4.0 anyio-3.6.2 argon2-cffi-21.3.0 argon2-cffi-bindings-21.2.0 arrow-1.2.3 asttokens-2.2.1 attrs-22.2.0 babel-2.11.0 backcall-0.2.0 beautifulsoup4-4.11.1 bleach-5.0.1 cachetools-5.2.1 certifi-2022.12.7 cffi-1.15.1 charset-normalizer-3.0.1 cloudpickle-2.2.0 comm-0.1.2 commonmark-0.9.1 cryptography-39.0.0 debugpy-1.6.5 decorator-5.1.1 defusedxml-0.7.1 docker-6.0.1 dynaconf-3.1.7 entrypoints-0.4 executing-1.2.0 fastjsonschema-2.16.2 flatten_json-0.1.13 fqdn-1.5.1 google-auth-2.16.0 google-auth-oauthlib-0.4.6 grpcio-1.48.2 idna-3.4 importlib-metadata-6.0.0 importlib-resources-5.10.2 ipykernel-6.20.1 ipython-8.8.0 ipython-genutils-0.2.0 isoduration-20.11.0 jedi-0.18.2 jinja2-3.1.2 joblib-1.2.0 json5-0.9.11 jsonpointer-2.3 jsonschema-4.17.3 jupyter-client-7.4.9 jupyter-core-5.1.3 jupyter-events-0.6.3 jupyter-server-2.1.0 jupyter-server-terminals-0.4.4 jupyterlab-3.5.2 jupyterlab-pygments-0.2.2 jupyterlab-server-2.18.0 markdown-3.4.1 matplotlib-inline-0.1.6 mistune-2.0.4 nbclassic-0.4.8 nbclient-0.7.2 nbconvert-7.2.7 nbformat-5.7.3 nest-asyncio-1.5.6 notebook-6.5.2 notebook-shim-0.2.2 numpy-1.24.1 oauthlib-3.2.2 openfl-1.4 packaging-23.0 pandas-1.5.2 pandocfilters-1.5.0 parso-0.8.3 pexpect-4.8.0 pickleshare-0.7.5 pkgutil-resolve-name-1.3.10 platformdirs-2.6.2 prometheus-client-0.15.0 prompt-toolkit-3.0.36 protobuf-3.19.6 psutil-5.9.4 ptyprocess-0.7.0 pure-eval-0.2.2 pyasn1-0.4.8 pyasn1-modules-0.2.8 pycparser-2.21 pygments-2.14.0 pyrsistent-0.19.3 python-dateutil-2.8.2 python-json-logger-2.0.4 pytz-2022.7 pyzmq-25.0.0 requests-2.28.2 requests-oauthlib-1.3.1 rfc3339-validator-0.1.4 rfc3986-validator-0.1.1 rich-13.0.1 rsa-4.9 scikit-learn-1.2.0 scipy-1.10.0 send2trash-1.8.0 six-1.16.0 sniffio-1.3.0 soupsieve-2.3.2.post1 stack-data-0.6.2 tensorboard-2.11.1 tensorboard-data-server-0.6.1 tensorboard-plugin-wit-1.8.1 tensorboardX-2.5.1 terminado-0.17.1 threadpoolctl-3.1.0 tinycss2-1.2.1 tomli-2.0.1 tornado-6.2 tqdm-4.64.1 traitlets-5.8.1 typing-extensions-4.4.0 uri-template-1.2.0 urllib3-1.26.14 wcwidth-0.2.5 webcolors-1.12 webencodings-0.5.1 websocket-client-1.4.2 werkzeug-2.2.2 zipp-3.11.0
(newEnv) (base) ithakarx@ithakarx-mobl:~/testDir/openfl$

numpy version is not pinned in OpenFL and, unfortunately, starting from numpy 1.24.x backward compatibility is broken. I checked versions 1.22.2 and 1.23.5, it works. As temporary workaround, you can manually install numpy==1.23.5 or earlier version in your virtual environment.

Hi @aleksandr-mokrov
Thanks for your feedback. My understanding is as follows:

As mentioned since numpy version is not pinned, by default latest numpy version is installed (refer log snippets above)
Numpy versions 1.22.2 and 1.23.5 raises a warning when we use dtype=np.int due to which the workaround suggested works
Numpy versions following 1.24.0 will give an error and tutorial fails

Summary: Issue seems very similar to PR #683. I have created PR #694 to handle this error. Request to please review if it is suitable

Closed with #694


After upgrading to version 5 downloadTraceFile() expects JSON

It's a plain text content type API, it shouldn't try parsing it as JSON

wrong project :)


Rendering on Smartphone

Super nice work, it renders super smooth on my Macbook pro :)
I "optimized "the ply to splat with your function but it still doens't render on my android phone (not super fast but not slow Pixel 7)
Any ideas of optimization? I tested the 3 examples too, it doesn"t work.
Thanks!

Tested on my side using a P30 Pro, on firefox mobile :
https://github.com/mkkellogg/GaussianSplats3D/assets/13988751/be01c034-fcd5-4beb-8537-019a9bb5f0c4
Exactly same behavior on chrome mobile.

For what it's worth, I have had trouble running on mobile as well. I'm pretty sure it has to do with the large amount of memory used by the viewer. There's currently no quick fix, I just need to work on making the viewer more efficient with memory usage.

@mkkellogg There's two issues from my experience so far of this issue.
The first one I encountered was that safari doesn't support importmap. This one I solved by bundling with Vite instead. This seems to be one recommended way according to mrDoob (Author of Three.js). Surely though this can be handled in another way.
Additionally as you say, there seems to be an issue with memory usage.
I managed to get the truck scene running on a iPhone 14 pro with splatAlphaRemovalThreshold set to 30.

I made some tweaks to how the data textures are populated and reduced their size. I can now load all the demo scenes on my samsung galaxy s9... but it's very, very sloooooow. Pretty much unusable, but at least it loads now :) I will continue working on that. @MarcusAndreasSvensson As for the import map issue, it looks like Safari supports them as of version 16.4?

I'm having trouble running in Safari on my iPhone (latest OS version). It seems that the error is related to this line in the sort worker. I'm happy to provide more info if needed.

@mkkellogg  Hmm, interesting. Yet I'm getting

On Safari both on iPhone and Macbook.

Closing this issue for now, please let me know if these issues come up again. I know mobile performance is still not great, I will try to work on that :)


Improved Color Combination & Navbar font-size

Fixes Issue🛠

Closes #
Description👨💻

Type of change📄

[x] New feature (non-breaking change which adds functionality)

How this has been tested✅

Checklist✅

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added demonstration in the form of GIF/video file
[x] I am an Open Source Contributor

Screenshots/GIF📷

"Could you kindly assign me this issue to GSSOC 2024? I would greatly appreciate it."

Please do not create a PR until you have been assigned to an issue @AshaSatpathy08


ng add @angular/material

Moved from https://github.com/angular/angular-cli/issues/10627

Versions
Angular CLI: 6.0.0
Node: 8.9.3
OS: win32 x64
Angular: 6.0.0
... animations, cli, common, compiler, compiler-cli, core, forms
... http, language-service, material, platform-browser
... platform-browser-dynamic, router

Repro steps

Step 1: ng add @angular/material
Step 2 It will update multiple files and add @angular/material and @angular/cdk to package.json

Observed behavior
It will install @angular/material but won't install @angular/cdk

Desired behavior
It should either install both or none.

@clydin looked into it and it seems like the CDK is being added but the npm install task is not.

another problem with ng add @angular/material is here
#https://github.com/angular/angular-cli/issues/10640


⚠ Samsung has degraded performance

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

HTTP code: 200
Response time: 2380 ms

Resolved: Samsung performance has improved in 8f4f5c7.


Fix beautify

Codecov Report

Merging #19 (21e6a24) into main (1d1b3f7) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #19   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           11        11
  Lines          328       328
=========================================
  Hits           328       328

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 1d1b3f7...21e6a24. Read the comment docs.


Blocking child Touchable on iPhone 6s and 6s Plus

There seems to be an issue with PanResponder and 3D touch on new iPhone devices. A TouchableHighlight inside a Swipeout component does not respond to its onPress handler. This issue has been raised in the react-native project (https://github.com/facebook/react-native/issues/3082) but could also be handled in react-native-swipeout by looking at the position of the child component (see https://github.com/facebook/react-native/issues/3082#issuecomment-144689910).

+1

+1

Hi all,
Thanks for reporting this. I'll be working on a major update this weekend, and I'll check out this issue and try implementing the fix described by @alexrabarts.

Just merged PR #47 which should fix this issue. Thanks @mhollweck!


Improve the exercise!

Really cool job @leireriel  !!!
Here you have some tips to improve the exercise:

[x] Remember to convert input value string to a number
[x] You are writing many times "trackEl.innerHTML = 'something';", what about making a function that accepts a string as param and paints it into 'trackEl'?
[x] Use === instead of == for comparisons
[x] Add HTML elements for the game: title, label and input, button, space for feedback (div, p) and number of trials
[x] Use a label to define the content of the input
[x] Connect the label to the input using the for attribute of the label and the id of the input
[x] Inputs must have a type attribute set to a valid value (text, number, mail, button..)

Then you can improve the game as you please, here you have some ideas:

Add new feedback when the number is bigger than 100 or smaller than 0.
Manage when the user hits the button and the input is empty.
Make the input work when hitting enter key.
Add a reset button that cleans the input, the counter, writes the initial feedback and generates a new random number to play again!
Whatever you want!

Let me know if you have any doubts ;)
Go for it!!

done! :)

Super good job, @leireriel !
If you are up to a challenge check out these exercises from previous Adalabers:

http://beta.adalab.es/dorcas-s2-evaluacion-intermedia-mariavioleta1417/
http://beta.adalab.es/e-s2-evaluacion-intermedia-maria-badanina/
http://beta.adalab.es/dorcar-s2-evaluacion-intermedia-annabranco/
http://beta.adalab.es/e-s2-evaluacion-intermedia-beatrizAdalab/

;)
Here you have a cool gif:


@IBOutlet weak var error

Am not able to use IBOutlet, is this an Xcode issue?
Regards.

@pixelbendr can you provide more details? Which element did you try to use, AnimatableView, AnimatableButton or others?
Can you specify the step you try to use IBOutlet? Ctrl+Drag?
Can you specify the Xcode version?
Can you tell us the IBAnimatable version?
Can you tell us how do you use it, CocoaPods, Carthage?

Which element did you try to use, AnimatableView, AnimatableButton or others?
AnimatableView
Can you specify the step you try to use IBOutlet? Ctrl+Drag?
Dragging
Can you specify the Xcode version?
7.3
Can you tell us the IBAnimatable version?
1.2
Can you tell us how do you use it, CocoaPods, Carthage?
CocoaPods

Did you import IBAnimatable in your file as well?
What is the exact error did you get?

thats the problem, the import. Thank you. Regards.

You're welcome :tada:


Interested?

We're trying to figure out the level of interest for this project. Do you think this datagrid is something you might want to use? What changes / features would you like to see?

Just getting started with it with a high level of interest. I'll report back once I've had some time to experiment

Very interesting.  It looks to be quite useful.  Would it contain the ability to edit values inside the grid?

No, but what you could do is implement your own editable value component and then render that inside the datagrid. E.g.:
<require from="src/components/myinlineeditor"></require>

<datagrid rows.bind="myData">
    <column header="My Editable Field">
        <my-inline-editor value.bind="row.myValue" onSave.bind="parent.saveCallback">
        </my-inline-editor>
    </column>
</datagrid>

I use aurelia extensively and have had to build my own custom datagrids from scratch for each project. I haven't had the time to make it modular. It would be of very great value.

I am looking for a new platform for our apps ( old one is becoming legacy ) and the ability to drop in well documented components like these really does make a difference in our ranking of Aurelia.

This would be great!


New tables added to Indexed db using dexie not getting reflected

Hi,
As of last week I had created tables in my Indexed db like this -
this.version(1).stores({
Person1Data: '++id,personName'
Person2Data: '++id,personName'
Person3Data: '++id,personName'
});
This was the same that was released to the QA instance last week and so then the QA Indexed db instance for me had these 3 tables which is correct.
As of yesterday I modified my Indexed db like this -
this.version(1).stores({
Person1Data: '++id,personName'
Person2Data: '++id,personName'
Person3Data: '++id,personName',
Person4Data: '++id,personName',
Person5Data: '++id,personName',
});
After that this was released to QA again yesterday and when I checked, the QA Indexed db instance still had 3 tables instead of 5 tables. Thinking that it was a cache issue, I cleared my cache and then when I logged in to QA instance, the Indexed db started showing 5 tables.
However, two other people from my team tried to fix the same issue in QA by clearing cache but for them there were still 3 tables, instead of 5 tables. For one person, clearing the %temp data%  solved the issue and for the other deleting the indexed database and then going to QA instance again(database got created newly with 5 tables) solved the issue and they both were finally able to see the 5 tables.
Now, coming to my actual question -
I am unable to join the dots between these solutions and find the actual cause of the issue. Is it because of cache that the two new tables weren't getting created or we cannot add new tables to a database version that has been released(deleting the database and allowing the database to create again adds the new tables though).
It will be really helpful if someone can provide me some direction so that if there is any issue in my code or my concept, I can rectify it. Thank you in advance.

Hi @prichakraborty09
I think you must increment your db version number, it will update the your db schema automatically.
please see this doc for further info
https://dexie.org/docs/Tutorial/Design#database-versioning

Thank you @rianonehub. I went through the documentation, so what's clear to me is that one cannot add tables to an existing version if it has been published. If we do need to add tables to an existing version, we would have to delete the indexed db and allow it to re-create again.


Add vscode instructions to tools_editors

On https://lectures.quantecon.org/jl/tools_editors.html

[ ] We need to find a consistent way to have a julia startup file that works for both Atom, the REPL, the Debugger, and vscode.  Might need to ask around
[ ] Add installation instructions for vscode and setting up julia support
[ ] Add similar sorts of quick walkthrough of editing code/ ctrl-enter to execute tests, etc.
[ ] A little text about reasons Juno is superior for certain things.

Issue is obsolete.

Why is it obsolete?

I thought we decided not to put in VS Code instructions. Maybe I'm hallucinating, though.

This is a 1.2 issue, not a 1.03 or even 1.1


⚠ Bofrost.fr has degraded performance

In 1ea37ea, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1358 ms

Resolved: Bofrost.fr performance has improved in ba933e1 after 33 minutes.


Include info on whether WiMi signed time sheet on time_sheet#show

When status is accepted

Should be the same design as #512

Should mention WHO signed the document, as every WiMi from the chair can accept timesheets

It is currently impossible to accept a time sheet as a WiMi without adding a signature. As such, the accepting WiMi is always the signer.


The cli command to create cosmos db table account is failing

[Enter feedback here]
I followed this document and when trying to create an account with table api it is failing.Please find the screenshot for the same

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 5c8143f6-c64f-408b-15b1-e259fd03e6c2
Version Independent ID: 630ff8c7-1288-cc6f-e1b8-b1c19a64f64c
Content: Create a API for Table table for Azure Cosmos DB
Content Source: articles/cosmos-db/scripts/cli/table/create.md
Service: cosmos-db
Sub-service: table
GitHub Login: @seesharprun
Microsoft Alias: sidandrews

Hi @aparna198809 ,
Thanks for sharing this feedback. We will look into this and update as appropriate.
Hi @seesharprun,
Could you please look into this request, thanks.

The sample code for this page is sourced from: https://github.com/Azure-Samples/azure-cli-samples/blob/master/cosmosdb/table/create.sh
I tried to reproduce this issue multiple times but the command works as expected.
When digging into the error message that you received, I noticed that the error code is related to an issue with your user principal for Azure CLI. As this is support for Azure Cosmos DB documentation, I won't be able to reproduce your issue or help you further.
You can post an issue in the official GitHub repo for Azure CLI and they may be able to help you further: https://github.com/Azure/azure-cli/issues. You can also open an Azure support ticket.
#please-close


CFP: Hubble DNS config option for response IPs

Cilium Feature Proposal
Is your proposed feature related to a problem?
No
Describe the feature you'd like
Proposing the option to configure Hubble to include metadata for DNS response IPs, e.g.:
hubble_dns_responses_total{response="<IP_ADDRESS>,<IP_ADDRESS>", ...}

With a Hubble configuration option for DNS like:
hubble-metrics: dns:response_ips

The DNS response IPs are already being sent to Hubble (see "Existing Code" section below).
(Optional) Describe your proposed solution

Create Hubble DNS config option.
Add label to hubble_dns_responses_total Prometheus metric.

Set label using data already present in Flow.

Existing Code: Response IPs sent to Hubble
The response IPs are part of the Flow proto used in Hubble:
https://github.com/cilium/cilium/blob/302a8b12fb6e05d505d79de1aac9c7141f055324/api/v1/flow/flow.proto#L593-L598
which is mapped from LogRecordDNS:
https://github.com/cilium/cilium/blob/302a8b12fb6e05d505d79de1aac9c7141f055324/pkg/hubble/parser/seven/dns.go#L16
DNS response IPs are included in the LogRecordDNS for the MessageTypeAccessLog payload sent as an AgentEvent to Hubble's parser. The code flow is:
https://github.com/cilium/cilium/blob/302a8b12fb6e05d505d79de1aac9c7141f055324/daemon/cmd/fqdn.go#L459-L474
https://github.com/cilium/cilium/blob/302a8b12fb6e05d505d79de1aac9c7141f055324/pkg/proxy/logger/logger.go#L221-L233
https://github.com/cilium/cilium/blob/302a8b12fb6e05d505d79de1aac9c7141f055324/pkg/proxy/logger/monitoragent_lognotifier.go#L21-L22
https://github.com/cilium/cilium/blob/302a8b12fb6e05d505d79de1aac9c7141f055324/pkg/hubble/parser/parser.go#L144-L152

Hi :wave:
This could easily be implemented but I'm worried about metrics cardinality. At the very least, it'll need to be opt-in and not a default option when enabling Hubble metrics.

Hi 👋 This could easily be implemented but I'm worried about metrics cardinality. At the very least, it'll need to be opt-in and not a default option when enabling Hubble metrics.

Thanks for taking a look! I agree, this should be optional and off by default


Get through 3 to 5 more Learn JavaScript Modules

Saeed: 1 additional lesson completed

Saeed has now completed the minimum requirement for this task


Missing inference in $Call

('abc': $Call<<E>(E) => $PropertyType<E, 'foo'>, { foo: number }>); // Error, ok

(['abc']: $Call<<E>(E) => [$PropertyType<E, 'foo'>], { foo: number }>); // No error. Why?

Try
I expected both of these examples to throw an error that string is incompatible with number but the second example seems to infer $PropertyType<E, 'foo'> as any. Can you please explain why?

Just found out that adding $NonMaybeType fixes this issue:
(['abc']: $Call<<E>(E) => [$PropertyType<$NonMaybeType<E>, 'foo'>], { foo: number }>); // Error!

Why? 😨

but the second example seems to infer $PropertyType<E, 'foo'> as any

No.
type A = $Call<<E>(E) =>
	[$PropertyType<E, 'foo'>], { foo: number }>;
;(['abc']: A)

Here A is [(string | number)]

You can also use this:
type A = [$Call<<E>(E) =>
	$PropertyType<E, 'foo'>, { foo: number }>];
;(['abc']: A) // error.

These both errors under inference_mode=lti


Review workshop material

Especially with respect to 1.x compability
The data in question is this.
Some stuff is pretty old and may not be updated. It would also make sense to spilt it more into what is useful for beginners and what is more of interest for more experienced programmers.

Thanks @BeastyBlacksmith. Will we have time to do this together tomorrow? I'm sick today.
From my point of view, there are three tasks

Content for beginners (to programming)
Content for experienced programmers
Make it all 1.x compatible

Lets but it at the end tomorrow. We should at least mark stuff that is outdated.

done with @pfitzseb


Remove unused thread_pool

When in commit ea3c5ef0f1 march_hare's thread pools were deprecated in favor of RMQ's thread pools, one thread pool was left behind, but it is/was no longer used, and can be safely removed.
Fixes #96

Thanks!


pkgx --sync on main takes around 1 minute while in v1.1.6 takes 1 second

I noticed this so I just wanted to make you aware (in case you aren't already).
This is because the addition of the cache using sqlite, which didn't exist on 1.1.6.

@dosubot is probs right. The cache takes time to build, though for me it is only a few seconds or I wouldn't be about to publish v1.2 that contains it…
I guess we'll find out if this still occurs for you on release and if so fix that straight away.

Note that sync is slower but running executables has way, way less overhead. I did the testing months ago but it was 50x or something

That is understandable, but I was wondering if something could be done to improve it. I use pkgx very often in ephemeral environments (containers, CI/CD), and taking 1 minute for the sync (which must be done in fresh environments) is kind of big deal.
$ git pull
$ dev
$ deno task run --sync  6.76s user 8.04s system 21% cpu 1:08.82 total

yeah this is not ok for sure.
The code I wrote is not optimized, but I also don’t know where the slowness is specficially:
https://github.com/pkgxdev/libpkgx/blob/main/src/hooks/useSyncCache.ts

Potentially the ffi interface to sqlite is slow
Potentially the sqlite queries are slow
Potentially the slowdown is entirely in the YAML parsing

I will aim to investigate but not today (likely).

I did intend to bundle the pre-cached DB with the pantry.tgz that pkgx downloads, but we should aim to make the cache-step fast as first as reasonably possible anyway.
sqlite is potentially not the right solution, though it's accessible and simple.

just realized that the installation of the sqlite pkg will add seconds for sure. That is step one in caching.

Moving the .cache/pkgx folder into a memory based filesystem (like /dev/shm or /tmp if on memory) makes the sync process instant, while on my ssd disk sqlite stays writing 120mb/s during several seconds the pantry.db file.

Thanks for the hint, @amospalla.
@mxcl, https://github.com/pkgxdev/libpkgx/pull/78 fixes it.

A new pkgx release coming soon.


data preparation

Hi, Thanks for sharing these code. It would have been great to get the step how to prepare data for training as well as for query. Possible to share the same?
Thanks

I already addressed this in #1 and #3.


CI Github Workflow

@muskie9 any idea what's going on with the tests? Works on local running PHP8, SS 4.11 and PHPUNIT 9

@jsirish I was able to track it down. It was aspects of the composer file that snuck in with the work that converted locations to pages: https://github.com/dynamic/silverstripe-locator/pull/231/commits/14ead804ee96e16f301b934d791e107332bcbdbf


RATEINF/CPI_CAN does not exists anymroe... what is the replacement name ?!!!

RATEINF/CPI_CAN does not exists anymroe... what is the replacement name ?!!!

-- Please reply above this line --
        Hi there,

Thanks for reaching out.
Unfortunately the RATEINF database has been deprecated and is no
longer updating on Nasdaq Data Link. At this time, we do not currently
have an alternate data feed.
_We apologize for the inconvenience caused by the deprecation of the
RATEINF data feed. Kindly note _that free data feeds may get
deprecated at any time for various reasons eg. they may no longer meet
our quality standards, technical issues prevent us from obtaining the
data, etc. Please feel free to check out our data offerings in the
future to see if there's anything of interest.
Best regards,
Kim
KIM LIRA
Nasdaq Data Client Success
How would you rate my reply?
Great [1]    Okay [2]    Not Good [3]
Links:
[1]
https://secure.helpscout.net/satisfaction/657776831/record/7194983590/1/
[2]
https://secure.helpscout.net/satisfaction/657776831/record/7194983590/2/
[3]
https://secure.helpscout.net/satisfaction/657776831/record/7194983590/3/
    > On Thu, Oct 26, 2023 at 11:46 AM EDT, Nasdaq/data-Link-Python<EMAIL_ADDRESS>wrote:

WARNING - EXTERNAL EMAIL; EXERCISE CAUTION.
RATEINF/CPI_CAN does not exists anymroe... what is the replacement
name ?!!!

Reply to this email directly, view it on GitHub [1], or unsubscribe
[2].
You are receiving this because you are subscribed to this
thread.Message ID:
@.***>
Links:
[1] https://github.com/Nasdaq/data-link-python/issues/43
[2]
https://github.com/notifications/unsubscribe-auth/AWYQ64YGQBYZMUEIDL6XOS3YBKATXAVCNFSM6AAAAAA6RN7PDWVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE3DGOBVHA4DCOA


Bootstrap agent

Commit Message: allow user_agent fields to be overridden from bootstrap config
Additional Description: user_agent_name, user_agent_version and user_agent_build_version all look like they're settable from the docs, but the server just sets these values from the internals.  This allows the users to override them if desired, but falls back to the default behavior.
Risk Level: low
Testing: Added integration tests for using the values from the fields.  But to test manually: update any of those 3 fields in the bootstrap node config to whatever valid values you want, then verify that they show up in the /config_dump output.  If you omit them, the current defaults will still be populated.
Docs Changes:
Release Notes:
Platform Specific Features:
Fixes #16471

Please tell me how to generate this setup? Mozilla/5.0 (Linux; Android 7.0; PRA-LA1 Build/HUAWEIPRA-LA1; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/77.0.3865.116 Mobile Safari/537.36 binu/1078 (1ceb656684e4cf54)

It's not clear to me what to fix on these failing builds, or if they're intermittent failures.  @yanavlasov just LMK if there's something I should do at this point

thanks, I thought trailing whitespace removal was on for all, turns out I didn't have it set editor wide but rather for a couple specific languages.

I'm using this adress as remote proxy myassupol.datafree.co then I'm
getting 407 Proxy-Authenticate. How can I fix it?
On Tue, May 25, 2021, 6:32 PM Justin Ely @.***> wrote:

It's not clear to me what to fix on these failing builds, or if they're
intermittent failures. @yanavlasov https://github.com/yanavlasov just
LMK if there's something I should do at this point
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/envoyproxy/envoy/pull/16646#issuecomment-848027665,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHDVRRI6COSBZLIOGSYSLRDTPPGIXANCNFSM45N4UF2Q
.

@prosper86 please open issues in the main issue tracker or ask questions in the envoy slack channel.  This pull request isn't the correct place for these discussions.

@yanavlasov do you know if/how I can run the failing test locally? I'm trying to fix the null pointer error it raises

nvm, think i found it with
./ci/run_envoy_docker.sh './ci/do_ci.sh bazel.dev'
ci/run_envoy_docker.sh 'ci/do_ci.sh bazel.clang_tidy'

Thanks


x:import and x:description/attribute()

https://github.com/xspec/xspec/pull/1397#pullrequestreview-622778963

If I have timing in an XSpec file, and that file imports another XSpec file with the opposite timing value, then only the parent file's attribute takes effect. I think this behavior is fine, but I don't know what users' expectations would be. Is it worth documenting, or too obscure?

Related to #1497 is a similar behavior: If you set @threads on x:description and then use x:import to run a suite of tests, the @threads values in the imported files have no effect. That might surprise some users and make them wish they had organized their code differently from the start.

Will plan to add information to this page, where x:import is documented: https://github.com/xspec/xspec/wiki/Focusing-Your-Efforts

I updated the page Focusing Your Efforts.
Here is an earlier draft that I didn't use, but I'm including it here in case a reviewer likes this approach better.

The following attributes of x:description take effect across all imported XSpec description documents. Make sure the main XSpec description document has your desired value.

measure-time
result-file-threshold
run-as
threads

The following attributes of x:description, take effect in each individual XSpec description document. Make sure each individual XSpec description document has your desired value.

expand-text
preserve-space

Closing based on change in "Focusing Your Efforts".


EspLogger is not extensible

I would like to be able to extend the functionality of EspLogger for my own custom purposes like so
struct MyLogger<L>(L);

impl<L> ::log::Log for MyLogger<L>
where
    L: ::log::Log,
{
    fn enabled(&self, metadata: &log::Metadata) -> bool {
        self.0.enabled(metadata)
    }

    fn flush(&self) {
        self.0.flush()
    }

    fn log(&self, record: &log::Record) {
        if self.enabled(record.metadata()) {
            self.0.log(record);
            <do other things with the record...>
        }
    }
}

However as of this commit, I'm no longer able to do so because the public struct now has a private constructor.

Help me understand how a pub EspLogger::new would help. It is not like Rust is an OOP language, whgere you can "inherit" from EspLogger, so not sure how that would be useful?
(And btw the new is private because the logger is supposed to be a singleton.)

Help me understand how a pub EspLogger::new would help. It is not like Rust is an OOP language, where you can "inherit" from EspLogger, so not sure how that would be useful?
(And btw the new is private because the logger is supposed to be a singleton.)

Rust is not OOP, but composition is still possible. In the example I put above, let's suppose that the <do other things with the record> involves uploading the log to some cloud storage. I could call log::set_boxed_logger(MyLogger(EspLogger::new())) at the start of my code and then all Rust logs would be efficiently redirected to UART as EspLogger is implemented to do and then MyLogger could redirect that log over the internet with its own logic.
I understand the pattern of desiring a singleton, but enforcing that pattern is already handled by the log crate.

Help me understand how a pub EspLogger::new would help. It is not like Rust is an OOP language, where you can "inherit" from EspLogger, so not sure how that would be useful?
(And btw the new is private because the logger is supposed to be a singleton.)

Rust is not OOP, but composition is still possible. In the example I put above, let's suppose that the <do other things with the record> involves uploading the log to some cloud storage. I could call log::set_boxed_logger(MyLogger(EspLogger::new())) at the start of my code and then all Rust logs would be efficiently redirected to UART as EspLogger is implemented to do and then MyLogger could redirect that log over the internet with its own logic.
I understand the pattern of desiring a singleton, but enforcing that pattern is already handled by the log crate.

OK, so your idea would be:

Wrap the esp logger in your own stuff
Do NOT call EspLogger::initialize_default, and instead do your own ::log::set_logger(...) dance with the log crate

BTW: You do realize this way you can only grab the logs originating from rust code. Logs originating from the C code you need to grab with a different facility, which is much more hairy (vsprintf and stuff like that)
:

Yes that's exactly what my plan is. I am aware about those other logs, I have a separate additional use of the esp_log_set_vprintf that handles those statements

Yes that's exactly what my plan is. I am aware about those other logs, I have a separate additional use of the esp_log_set_vprintf that handles those statements

Would be great if you could share your code that deals with the vprintf blackmagic from Rust (if you do it from Rust and with pure rust (i.e. no C stubs and such)). I remember a user was fighting this for a long time without declaring success. We might include such an utility in esp-idf-svc::log as that might be useful to many folks.

Closing as fixed by https://github.com/esp-rs/esp-idf-svc/commit/11d9d0a417335f6e1fb596f03bf53dc4050862f1
But if you could really share the vsprintf stuff, that would be helpful.

Thank you for hearing me out @ivmarkov! I have an example I wrote for my work here


[red-knot] remove TODO catch-all case in infer_unary_expression

Currently, the method TypeInferenceBuilder::infer_unary_expression handles some common cases, and has a catch-all arm that simply infers a "todo" type.
This issue is to remove that todo catch-all case, and replace it with correct handling of all missing cases.
For many of the unhandled types (e.g. Type::FunctionLiteral, Type::ClassLiteral, Type::SubclassOf) the correct handling will simply be an unsupported-operator diagnostic. But for each missing type, we should confirm the runtime behavior and handle it accordingly.
Even for the various types that should just result in an error, it would be better to list all the Type variants explicitly rather than using a catch-all arm, so that in future when we add a new Type variant, we are forced to consider how it should behave in a unary expression.

For many of the unhandled types (e.g. Type::FunctionLiteral, Type::ClassLiteral, Type::SubclassOf) the correct handling will simply be an unsupported-operator diagnostic.

Hmm, I don't think that's correct when it comes to Type::ClassLiteral and Type::SubclassOf. We need to treat a class as an instance of its metaclass when determining if a unary operation is supported on that class or not.

Yes, good point! I looked at functions and then thoughtlessly lumped classes in with them.
Even for functions, we should probably treat them as an instance of types.FunctionType and defer to typeshed, rather than hardcoding the unsupported-operator diagnostic.

Closed by #15045


chafa image not displaying

Hello. I came across your tool yesterday and really like it so far. I did come across an issue where when selecting 'View Info', it did not show the image. Everything else displayed just fine. I am still learning git and not sure how to setup a pull request, so thought to open an issue ticket as it is a easy fix.
File with issue: fastanime/cli/utils/print_img.py
Current line 27:
subprocess.run([EXECUTABLE, url, "--size=15x15"], input=img_bytes)

Suggested fix for line 27:
subprocess.run([EXECUTABLE, "--size=15x15"], input=img_bytes)

Yeah, all that seems to need to be done is to remove url from the command.
I reached out to the chafa dev after test the chafa command on my sytem. Link to issue ticket with explanation: https://github.com/hpjansson/chafa/issues/233
System Info:
Xubuntu 24
kitty 0.37.0

Never touched that file (2mnths ago) in a while :laughing: . Thanks, will update it later. Though i think if you try doing it yourself it would not be as hard as you imagine. So give it a try before saying you can't do it.

I'have written more than enough (13k+) solo. Its time for the community to step up.  So, I'll will be waiting for your pr :laughing:

Sure!! At the gym and just found a vid that made it 100x more clear on how to do it then the docs do. Will make it when I get home.

PR put in https://github.com/Benex254/FastAnime/pull/24

Merged, told you could do it


Add Discord links to documentation and README

Pull Request Test Coverage Report for Build 481349764

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 481241998:
0.0%

Covered Lines:
644

Relevant Lines:
644

💛  - Coveralls

Pull Request Test Coverage Report for Build 481349764

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 481241998:
0.0%

Covered Lines:
644

Relevant Lines:
644

💛  - Coveralls

Pull Request Test Coverage Report for Build 481349764

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 481241998:
0.0%

Covered Lines:
644

Relevant Lines:
644

💛  - Coveralls

Pull Request Test Coverage Report for Build 481349764

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 481241998:
0.0%

Covered Lines:
644

Relevant Lines:
644

💛  - Coveralls

Pull Request Test Coverage Report for Build 481349764
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 481241998:
0.0%

Covered Lines:
644

Relevant Lines:
644

💛  - Coveralls

Pull Request Test Coverage Report for Build 481349764
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 481241998:
0.0%

Covered Lines:
644

Relevant Lines:
644

💛  - Coveralls


feat(storage): add git configuration and integration tests

Signed-off-by: Eric Stroczynski<EMAIL_ADDRESS>

Closing this PR. We decided to move away from git-based backends.


[FEATURE] Feature command: noon humanize option

Describe the solution you'd like
Add an option to the noon feature command to send a simple text message explaining how the feature is configured.
This message should also be visible when using the help command.

This flag is about sending a text message explaining how the noon feature is configured.
This text message should be visible as well when sending the help message since it is pretty useful.

Decided to not include the content of the humanize flag with the help option.
The humanize is an embed message and even the description can be used from the outside I think that the goal of a help flag is to be close to a CLI experience so no need to add extra confusing text when you just need to list the flags.


Modify installation instructions for Ubuntu

Changes to use apt, not snap. Fixes https://github.com/github/hub/issues/2695

Ubuntu has currently hub in 2.7.0 (https://packages.ubuntu.com/source/groovy/hub)
side note: did you guys thinking of bumping it (or asking maintainers to do so) soon, to some more recent version?

Ubuntu has currently hub in 2.7.0 (https://packages.ubuntu.com/source/groovy/hub)
side note: did you guys thinking of bumping it (or asking maintainers to do so) soon, to some more recent version?

Thank you! Looks great

Which version of hub does this install on Ubuntu?

2.7.0 is the latest I've found. It's not likely to be the latest version unless it is extremely actively maintained or automated. Most apt dependencies will install a slightly older version which has been tested by the Canonical team or contributors.

If Ubuntu 18 isn't supported by this, should we add a notice?

People should be able to reasonably expect installation instructions on the latest LTS and newer, after all - that's why it's called an LTS. Whether you want to support distributions that are now no longer supported (older than the 2 year long term support lifecycle) is up to you, but to keep things simple and clean, I would suggest not doing so.

Thank you! Looks great

Which version of hub does this install on Ubuntu?

2.7.0 is the latest I've found. It's not likely to be the latest version unless it is extremely actively maintained or automated. Most apt dependencies will install a slightly older version which has been tested by the Canonical team or contributors.

If Ubuntu 18 isn't supported by this, should we add a notice?

People should be able to reasonably expect installation instructions on the latest LTS and newer, after all - that's why it's called an LTS. Whether you want to support distributions that are now no longer supported (older than the 2 year long term support lifecycle) is up to you, but to keep things simple and clean, I would suggest not doing so.

Which version of hub does this install on Ubuntu?

2.7.0 is the latest I've found.

This may be too ancient version that perhaps does not work well with latest Git credential helpers what may cause authentication problems, see https://github.com/github/hub/issues/2701

Which version of hub does this install on Ubuntu?

2.7.0 is the latest I've found.

This may be too ancient version that perhaps does not work well with latest Git credential helpers what may cause authentication problems, see https://github.com/github/hub/issues/2701

Not only WSL is affected: I just had the same issue with the ubuntu:latest Docker container (which is 20.04 focal) where apt install hub installed version 2.7.0 which didn't work due to Unauthorized (HTTP 401) Bad credentials. (I posted on Stack Overflow at first because I didn't expect the outdated version to be the issue, but something with my GitHub Actions workflow.) The solution was to install the latest hub binary, manually, via wget. So, unfortunately, it seems like installing via apt can't be recommended at the moment.

Not only WSL is affected: I just had the same issue with the ubuntu:latest Docker container (which is 20.04 focal) where apt install hub installed version 2.7.0 which didn't work due to Unauthorized (HTTP 401) Bad credentials. (I posted on Stack Overflow at first because I didn't expect the outdated version to be the issue, but something with my GitHub Actions workflow.) The solution was to install the latest hub binary, manually, via wget. So, unfortunately, it seems like installing via apt can't be recommended at the moment.


code about a cvpr 19 paper

Hi, Justin, thanks for the wonderful work on pinocchio. Not sure if it is the correct place to ask my question, but I noticed that the CVPR 19 paper "Estimating 3D Motion and Forces of Person-Object Interactions from Monocular Video" is implemented based on pinocchio. I am wondering if there is a rough timeline for releasing the code. If it still needs time, is there any simple tutorial on inverse dynamics with contacts (for humanoid) to get started? In addition, is it possible to release the urdf file used in the paper for modeling the human?

Hi @timothy233,
Thanks for your interest in our work. Parts of the CVPR project’s code and data are already online but lack documentation and clear instructions. Therefore, we are preparing an official release using Docker for the project. The code release will go with an extended journal version of the paper which should be available around the end of May.

Is it possible to release the urdf file used in the paper for modeling the human?

Our human model is the same used in HMR but adopted to Pinocchio. The model was not saved in URDF so I would suggest you to wait a few days for the official release.
Thanks again for your interest, and I am sorry for the delays!

Thanks @zongmianli for this nice and useful feedback.
@timothy233 Thanks for your interest in our software and research activities.
I will close this issue and we will try to come back to it when the docker image is released.


📖 Modify the text to acknowledge GitHub != universe

There are many source repository hosting services (forges),
not just GitHub. This generalizes the requirements, e.g., from:

Determines if the project's GitHub workflows follow the principle of least privilege.

to:

Determines if the project's workflows follow the principle of least privilege.

Scorecard doesn't currently implement checks in most cases for
systems other than GitHub, so acknowledge that as a limitation, instead
of implying that it's the one true way to implement secure software.
Signed-off-by: David A. Wheeler<EMAIL_ADDRESS>

Run make generate-docs?

Some past commits didn't run make generate-docs. I'm afraid that if I run make generate-docs within this commit, it'll appear to add unrelated changes, possibly even leading to merge conflicts.
So I propose accepting this commit & other recent commits on the docs, then run a separate commit to make generate-docs. That'll have the same result with less intermediate pain.

Run make generate-docs?

Some past commits didn't run make generate-docs. I'm afraid that if I run make generate-docs within this commit, it'll appear to add unrelated changes, possibly even leading to merge conflicts.
So I propose accepting this commit & other recent commits on the docs, then run a separate commit to make generate-docs. That'll have the same result with less intermediate pain.

That sounds good to me. @azeemshaikh38 WDYT?

Run make generate-docs?

Some past commits didn't run make generate-docs. I'm afraid that if I run make generate-docs within this commit, it'll appear to add unrelated changes, possibly even leading to merge conflicts.
So I propose accepting this commit & other recent commits on the docs, then run a separate commit to make generate-docs. That'll have the same result with less intermediate pain.

That sounds good to me. @azeemshaikh38 WDYT?

@azeemshaikh38 Ping

Run make generate-docs?

Some past commits didn't run make generate-docs. I'm afraid that if I run make generate-docs within this commit, it'll appear to add unrelated changes, possibly even leading to merge conflicts.
So I propose accepting this commit & other recent commits on the docs, then run a separate commit to make generate-docs. That'll have the same result with less intermediate pain.

That sounds good to me. @azeemshaikh38 WDYT?

@azeemshaikh38 Ping

SGTM.


Add Functionality to Fetch QR Hash Codes for a Specific Event

Description
The POAP.js library currently offers various SDKs and utilities for interacting with the POAP ecosystem, including moments creation and management, TypeScript support, and easy integration with the ecosystem. To further enhance this library, we propose to add the functionality to fetch QR hash codes for a specific event using the POAP API endpoint /event/{id}/qr-codes.
This endpoint returns the list of qr_hash codes for a particular event, along with the claim status of each code for whether it has been claimed yet.
Proposed Feature

Create a new function, getEventQrCodes(eventId), that will hit the POST endpoint https://api.poap.tech/event/{id}/qr-codes, where {id} is the event's ID.
The function should return a list of qr_hash codes for the given event, along with the claim status of each code.

Why This Feature?
This feature would allow users of the library to easily fetch QR hash codes for specific events, which would be particularly useful for organizers and developers who need to manage or interact with these events.
Next Steps

Fork the repository.
Create a new branch with a descriptive name.
Implement the feature and commit the changes with a clear and concise commit message.
Create a pull request, describing the changes made and why.

Is the function supposed to go here?
Are there any more details about /qr-codes route?
https://github.com/poap-xyz/poap.js/blob/main/packages/providers/src/core/PoapDropApi/PoapDropApi.ts

Is the function supposed to go here?
Are there any more details about /qr-codes route?
https://github.com/poap-xyz/poap.js/blob/main/packages/providers/src/core/PoapDropApi/PoapDropApi.ts

To integrate the endpoint into PoapDropApi.ts, you'd define a new function using an HTTP POST request to https://api.poap.tech/event/{id}/qr-codes. This function should send a Bearer token for authorization. When called, it should return a list of qr_hash codes for a specified event alongside the claim status of each code. You can follow the structure of existing functions in PoapDropApi.ts for guidance, adapting as necessary for the specifics of thisendpoint.
For working with Bearer tokens, you can refer to examples in PoapTokenApi.ts and apply the same principles in PoapDropApi.ts.
Do you want to be assigned to this issue?


Direct consumption of Siebel notifications rather than via the PM

[Kunal] – as explained above, it may not be required (even though it is allowed) as for some cases PR’s BindData API should be sufficient to handle the change of model.

closed

mentioned in issue #12


Outdated cask: table-tool

Outdated cask: table-tool.
Info:

version: 1.1.1.
appcast url: https://github.com/jakob/TableTool/releases.atom.

Please do not run find_outdated_appcasts unless you are a maintainer.