Ubuntu 22.04 crash

Hello.
Thanks for supporting linux. I'm on ubuntu 22.04
I was trying to get it working and used the installer. The emulator crashes after a few seconds with the following logs
EmuHawkMono_laststderr.txt
EmuHawkMono_laststdout.txt
I also tried the manual install. And bizhawk works until I add the dlls in the ExternalTools folder.

Thank you for reporting. Can you check if installing the libcanberra-gtk-module package fixes the crash or at least changes the log output? If that's the case, I'd just have to make sure this is handled by the installer.

Hi,
No change even with the library installed.

I'll see if I can reproduce the issue on a fresh Ubuntu install. If you have any other ideas, let me know.

After reproducing the crash, I had another look at the stack trace and realized that this was an issue I'd run into during initial testing, caused by BizHawk attempting to display an .ico image with a 256x256 PNG layer. I thought I had already fixed this by removing that layer from the copy of the icon used by BizHawk, but I guess that change got accidentally reverted at some point, because the layer does exist in the current version of the file.


Does not work with FastAPI

Bug 💥
I want to implement deepdoctection in an API, so I chose FastAPI. However, when I import deepdoctection in a FastAPI script, the server simply does not start up.
from fastapi import FastAPI
import deepdoctection as dd

app = FastAPI()

@app.get("/")
async def main():
    return {"msg": "Welcome to HKO Flimsy search engine"}

When I remove import deepdoctection as dd, the startup process is fine.
Expected behavior  🧮
FastAPI outputs INFO: Application startup complete..
Screenshots 🖼
INFO:     Will watch for changes in these directories: ['...']
INFO:     Uvicorn running on http://<IP_ADDRESS>:8005 (Press CTRL+C to quit)
INFO:     Started reloader process [1326097] using WatchFiles

Desktop (please complete the following information, if any other than the one in the install requirements):

OS: Ubuntu

Additional context 🧬
If necessary add some context related to the problem

I don't know much about uvicorn, but when running this app, at least the server starts and I can access the endpoint.
What startup processes are still missing?

The console logs are not showing. Something like INFO: <IP_ADDRESS>:44604 - "GET / HTTP/1.1" 200 OK. Perhaps this is related to the logging module?

Possibly. As you mention logging I had a similar issue as well in a different application that is also based on FastAPI. It did not affect the application, though. But yes, maybe logs do not get propagated properly.
Regarding deepdoctection logging, you can setup a logging file:
import deepdoctection as dd

dd.set_logger_dir(dir_name)

This will log a verbose message of infos, warnings, errors.

Let me know if you have an idea on how logging can be improved in conjunction with third party logger.

I don't know if this is supposed to happen. I have
my_package
  |-- utils
    |-- __init__.py
    |-- logger.py

and the logging format in this logger is different from yours (i.e., "%m%d %H:%M:%S" instead of "%m%d %H:%M.%S"). If I put from .logger import logger in my utils/__init__.py, my logs are not shown at all. But if I put from deepdoctection.utils import logger instead, I can overwrite your logging format and my logs are shown.

The reason why the logs are not displayed is, as I have just discovered, extremely simple:
The deepdoctection root logger is set to propagate False by default. When the uvicorn server is started, the root logger changes, causing the deepdoctection logger not to propagate its logs.
With a recent adjustment (effectively released in v.0.30.0), you can now set the environment variable LOG_PROPAGATE=True to propagate the deepdoctection logs to any root logger.


to_bytes does not exist on Packet.

Overview
The "Packet" class should inherit the Buffer class, allowing us to convert the packet to Bytes.
Expected behavior
Expected to_bytes to be exposed.
Actual behavior
to_bytes is not exposed and there is no way to get the encoded data of a packet.
Investigation
I tried getting a singular packet from a video. Then tried using to_bytes on it. I also inspected the source for the Packet class but it does not inherit Buffer. Neither does it implement any of Buffer's methods.
Reproduction
Get a video. Extract packets. See that get_bytes is not exposed.
Versions

OS: Fedora 39
PyAV runtime:

PyAV v12.0.5
library configuration: --disable-static --enable-shared --libdir=/tmp/vendor/lib --prefix=/tmp/vendor --disable-alsa --disable-doc --disable-mediafoundation --disable-videotoolbox --disable-libtheora --enable-gnutls --enable-libxcb --enable-lzma --enable-zlib --enable-version3 --enable-libopenh264 --disable-libx264 --enable-libfreetype --enable-libxml2 --enable-fontconfig --enable-gmp --enable-libaom --enable-libbluray --enable-libass --enable-libdav1d --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable-libspeex --enable-libtwolame --enable-libvorbis --enable-libvpx
library license: LGPL version 3 or later
libavcodec     60. 31.102
libavdevice    60.  3.100
libavfilter     9. 12.100
libavformat    60. 16.100
libavutil      58. 29.100
libswresample   4. 12.100
libswscale      7.  5.100

PyAV build:

Not applicable?

Research
I have done the following:

[X] Checked the PyAV documentation
[X] Searched on Google
[X] Searched on Stack Overflow
[x] Looked through old GitHub issues

Additional context
According to the Wiki it should inherit from Buffer.

Have you tried using bytes(packet) ?


ver 1.4.1

Codecov Report

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

@@           Coverage Diff           @@
##           master      #97   +/-   ##
=======================================
  Coverage   98.85%   98.85%
=======================================
  Files          13       13
  Lines         699      699
  Branches      172      172
=======================================
  Hits          691      691
  Misses          8        8

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 1e56b46...820e317. Read the comment docs.


Added and Updated HTML.md

As described. Tried to match the "layout" from already existing docs otherwise open to feedback.

@VerzatileDev just waiting for your sign-off dude

Did the changes. Thanks for the feedback. :smiley:


Add @deprecated annotation support for class definitions

Description:

$subject.
Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Added in https://github.com/ballerina-platform/ballerina-lang/commit/8e503b06f5e7162315e3616148747a24f0168c40.


[Bug]: Possible bug in query pipeline agent notebook?

Bug Description
In the second agent.run_step() call in the query pipeline agent notebook, I see that the prompt mentions to expect interleaved user/agent messages, but it actually just appends three user messages in a row, which seems to partially confuse the LLM (though it reaches a good final answer anyway).
Just wanted to double check if multiple user messages in a row is actually intended, or may be a bug? If it's not a bug, it's a little bit confusing 😅 Thanks!
Here's the formatted prompt and LLM response:

** Messages: **
system:
You are designed to help with a variety of tasks, from answering questions to providing summaries to other types of analyses.
Tools
You have access to a wide variety of tools.
This may require breaking the task into subtasks and using different tools
to complete each subtask.
You have access to the following tools:
Tool Name: sql_tool
Tool Description: Useful for translating a natural language query into a SQL query
Tool Args: {"type": "object", "properties": {"input": {"title": "Input", "type": "string"}}, "required": ["input"]}
Output Format
To answer the question, please use the following format.
Thought: I need to use a tool to help me answer the question.
Action: tool name (one of sql_tool) if using a tool.
Action Input: the input to the tool, in a JSON format representing the kwargs (e.g. {"input": "hello world", "num_beams": 5})
Please ALWAYS start with a Thought.
Please use a valid JSON format for the Action Input. Do NOT do this {'input': 'hello world', 'num_beams': 5}.
If this format is used, the user will respond in the following format:
Observation: tool response
You should keep repeating the above format until you have enough information
to answer the question without using any more tools. At that point, you MUST respond
in the one of the following two formats:
Thought: I can answer without using any more tools.
Answer: [your answer here]
Thought: I cannot answer the question with the provided tools.
Answer: Sorry, I cannot answer your query.
Current Conversation
Below is the current conversation consisting of interleaving human and assistant messages.
user: Observation: What are some tracks from the artist AC/DC? Limit it to 3
user: Observation: {'output': ToolOutput(content='Some of AC/DC's popular tracks include "For Those About To Rock (We Salute You)", "Put The Finger On You", and "Let's Get It Up".', tool_name='sql_tool', raw_input={'input': "SELECT track_name FROM tracks WHERE artist_name = 'AC/DC' LIMIT 3"}, raw_output=Response(response='Some of AC/DC's popular tracks include "For Those About To Rock (We Salute You)", "Put The Finger On You", and "Let's Get It Up".', source_nodes=[NodeWithScore(node=TextNode(id_='ed4ac6f6-8279-4fb4-9303-fad11d68491a', embedding=None, metadata={}, excluded_embed_metadata_keys=[], excluded_llm_metadata_keys=[], relationships={}, text='[('For Those About To Rock (We Salute You)',), ('Put The Finger On You',), ("Let's Get It Up",)]', start_char_idx=None, end_char_idx=None, text_template='{metadata_str}\n\n{content}', metadata_template='{key}: {value}', metadata_seperator='\n'), score=None)], metadata={'ed4ac6f6-8279-4fb4-9303-fad11d68491a': {}, 'sql_query': "SELECT t.Name AS track_name\nFROM tracks t\nJOIN albums a ON t.AlbumId = a.AlbumId\nJOIN artists ar ON a.ArtistId = ar.ArtistId\nWHERE ar.Name = 'AC/DC'\nLIMIT 3;", 'result': [('For Those About To Rock (We Salute You)',), ('Put The Finger On You',), ("Let's Get It Up",)], 'col_keys': ['track_name']}))}
user: Observation: What are some tracks from the artist AC/DC? Limit it to 3

** Response: **
assistant: Thought: The user has repeated the request for tracks from the artist AC/DC, limited to 3, despite having already received an answer. It's possible that the user did not see the previous response or is asking for additional tracks. I will provide the same answer as before.
Answer: Some of AC/DC's popular tracks include "For Those About To Rock (We Salute You)", "Put The Finger On You", and "Let's Get It Up".

Version
main
Steps to Reproduce

Add llama_index.core.set_global_handler("simple") to the following notebook: docs/examples/agent/agent_runner/query_pipeline_agent.ipynb
Run the notebook up to the 2nd step_output = agent.run_step(task.task_id) step
Inspect the formatted prompt

Relevant Logs/Tracbacks
No response

Shouldn't there be an assistant message with an ActionReasoningStep mixed in there?

Updated comment for clarity.


very unstable gem full of bugs !!

i'm sending any anonymous  access token for authentication still its returning true !!

Do you get the same behavior if you use this example app - https://github.com/lynndylanhurley/devise_token_auth_demo?

I haven't used this demo I have used this this version 0.1.39...

Will you try the demo app and let us know if you get the  same behavior?

Closing due to no reply in a year or so


Can I use this library for two SCL3300 sensors connected to the same Arduino board?

Hi David,
I wonder if there is a way I can use your library in my project where I need to connect two SCL3300 sensors to the same Arduino board. Any suggestions are greatly appreciated. I can be reached at<EMAIL_ADDRESS>if needed.
Best regards,
Vadim

I would think that this can be done.  The MISO, MOSI, and SCLK signals would be common with both boards.  The Chip Select line would have to be different between the two devices, of course.  So if pins 10 and 9 were used for the two device select lines, then the two instances would be created in the code as follows:
twodevices.txt
(Note: this is UNTESTED, but based on Example #1 in the library.)
Go ahead and give this a try, and let me know if it works for you.

Hi Dave,
Thank you very much for your swift reply and suggestions. That is what I thought indeed, but your recommended code will be really helpful to me. I will give it a try and post it in the issue thread that I initially created in your GitHub repo.

Best regards,
Vadim Pougatchev
The content of this email is confidential and intended for the recipient specified in the message only. It is strictly forbidden to share any part of this message with any third party, without the written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.
From: Dave Armstrong @.***
Sent: Saturday, June 12, 2021 7:37 PM
To: DavidArmstrong/SCL3300 @.>
Cc: vpougatchev60 @.>; Author @.***>
Subject: Re: [DavidArmstrong/SCL3300] Can I use this library for two SCL3300 sensors connected to the same Arduino board? (#25)
I would think that this can be done. The MISO, MOSI, and SCLK signals would be common with both boards. The Chip Select line would have to be different between the two devices, of course. So if pins 10 and 9 were used for the two device select lines, then the two instances would be created in the code as follows:
twodevices.txt https://github.com/DavidArmstrong/SCL3300/files/6643173/twodevices.txt
(Note: this is UNTESTED, but based on Example #1 https://github.com/DavidArmstrong/SCL3300/issues/1  in the library.)
Go ahead and give this a try, and let me know if it works for you.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/DavidArmstrong/SCL3300/issues/25#issuecomment-860141552 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AS5HI42D4KUSWAPMEEO6USLTSQKWDANCNFSM46TGVCIA .  https://github.com/notifications/beacon/AS5HI42CXZCLEKBWXDXR3LDTSQKWDA5CNFSM46TGVCIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGNCLP4A.gif

I finally had a chance to finish the hardware part of our planned design with two SCL3300 sensors and test the recommended code. Everything works very well. Thank you, David, for your help.


Fix #2338 - Fix SCP logging and allow TRACE / DEBUG log

There were a few issues with SCP logging which made issues hard to debug.
The following should be a little easier to follow:

This worked fine with the single node, but printing the logs from the integration unittest SEGV:
Module tests failed: agora.test.RestoreSlashingInfo
core.exception.AssertError@source/agora/test/Base.d(1073): Check condition failed after timeout of 4 secs and 40 attempts: [source/agora/test/RestoreSlashingInfo.d:81] Client #6 did not receive tx in expected time for height 20
Process 97990 stopped
* thread #21, stop reason = EXC_BAD_ACCESS (code=1, address=0x28)
    frame #0: 0x0000000100b828b5 agora-unittests`std::__1::map<unsigned long long, std::__1::shared_ptr<stellar::Slot>, std::__1::less<unsigned long long>, std::__1::allocator<std::__1::pair<unsigned long long const, std::__1::shared_ptr<stellar::Slot> > > >::empty(this=0x0000000000000018 size=0) const at map:1125:62
   1122	    const_reverse_iterator crend() const _NOEXCEPT {return rend();}
   1123
   1124	    _LIBCPP_NODISCARD_AFTER_CXX17 _LIBCPP_INLINE_VISIBILITY
-> 1125	    bool      empty() const _NOEXCEPT {return __tree_.size() == 0;}
   1126	    _LIBCPP_INLINE_VISIBILITY
   1127	    size_type size() const _NOEXCEPT {return __tree_.size();}
   1128	    _LIBCPP_INLINE_VISIBILITY
Target 0: (agora-unittests) stopped.
(lldb) bt
* thread #21, stop reason = EXC_BAD_ACCESS (code=1, address=0x28)
  * frame #0: 0x0000000100b828b5 agora-unittests`std::__1::map<unsigned long long, std::__1::shared_ptr<stellar::Slot>, std::__1::less<unsigned long long>, std::__1::allocator<std::__1::pair<unsigned long long const, std::__1::shared_ptr<stellar::Slot> > > >::empty(this=0x0000000000000018 size=0) const at map:1125:62
    frame #1: 0x0000000100b8288e agora-unittests`stellar::SCP::empty(this=0x0000000000000000) const at SCP.cpp:224:24
    frame #2: 0x000000010085019b agora-unittests`_D5agora9consensus8protocol9NominatorQk16storeLatestStateMFNfZ9__lambda2MFNbNeZv at SCPEnvelopeStore.d:80:13
    frame #3: 0x000000010060200a agora-unittests`_D5agora9consensus8protocol9NominatorQk16storeLatestStateMFNfZv(this=0x00000001070655c0) at Nominator.d:707:9
    frame #4: 0x00000001005fa551 agora-unittests`_D5agora4node9ValidatorQk8shutdownMFNfZv(this=0x000070000fe91458) + 81
    frame #5: 0x0000000100674c38 agora-unittests`_D5agora4test4Base14TestAPIManager8shutdownMFbZ14shutdownSilentFNfC6ObjectZv(node=0x000070000fe91458) at Registry.d:107:17
    frame #6: 0x000000010068f757 agora-unittests`_D6geod249LocalRest__T9RemoteAPITC5agora4test4Base7TestAPITSQBaQxQu10SerializerZQCg__T7spawnedTCQCkQChQCf17TestValidatorNodeZQBnFNbCQFa11concurrency__T7ChannelTCQGdQFz10ConnectionZQBdAyaiSQFy6common6ConfigQhPOSQIa8Registry__TQmTQHnZQtPOSQJbQBb__TQBhTCQIj8registry3API15NameRegistryAPIZQCuAySQJx9consensus4data5BlockQgIKSQLaQKxQKv8TestConfPOmZ7runNodeMFZ9__lambda4MFZv at LocalRest.d:843:33
    frame #7: 0x0000000101265b9f agora-unittests`_D4core6thread7context8Callable6opCallMFZv(this=0x0000000000000002) at context.d:46:17
    frame #8: 0x0000000101265d2e agora-unittests`_D4core6thread5fiber5Fiber3runMFZv(this=0x0000000107015680) at fiber.d:1958:9
    frame #9: 0x0000000101265c63 agora-unittests`fiber_entryPoint at fiber.d:190:13

Found the bug, it's unrelated (just triggered because the nodes are slower with all logging enabled).

Self merging because it was extensively tested and we'll need it live soon.


Tcs 21 include the filter that is being used in the return payload

Modified subdetails function in segmentedtickerplant.q to include filter used
Added filtermap.q in code/segmentedtickerplant with function to create a dictionary of tables and filters

This PR should not merge into master. Closing. Needs PR to torq5_develop


Are even kmers supported?

Does bifrost support kmers of even length, including the edge cases this produces, like self-complemental nodes?

Yes


Cannot locate node of type [fast_planner_node] in package [plan_manage]；cannot launch node of type [plan_manage/traj_server]

Hello, thank you very much for your sharing, but I have some troubles in the process of using it, so I would like to ask you for advice.This problem has been bothering me for a few days. I am looking forward to your reply.
After I run roslaunch px4_fast_planner px4_fast_planner. Launch, the following error appears.
ERROR: cannot launch node of type [plan_manage/fast_planner_node]: Cannot locate node of type [fast_planner_node] in package [plan_manage]. Make sure file exists in package path and permission is set to executable (chmod +x)
ERROR: cannot launch node of type [plan_manage/traj_server]: Cannot locate node of type [traj_server] in package [plan_manage]. Make sure file exists in package path and permission is set to executable (chmod +x)
Version - PX4 Firmware v1.10.1, Ubuntu 18.04, ROS melodic
This problem has been proposed and solved by someone before. I checked his method, and he solved it after deleting pcl-1.11, but I didn't find pcl-1.11, only pcl-1.8.
Here's what I added to bashrc：
px4_dir=~/Firmware
source /opt/ros/melodic/setup.bash
source /home/hjl/catkin_ws/devel/setup.bash
source ~/Firmware/Tools/setup_gazebo.bash ~/Firmware ~/Firmware/build/px4_sitl_default
export ROS_PACKAGE_PATH=$ROS_PACKAGE_PATH:~/Firmware
export ROS_PACKAGE_PATH=$ROS_PACKAGE_PATH:~/Firmware/Tools/sitl_gazebo
export GAZEBO_PLUGIN_PATH=$GAZEBO_PLUGIN_PATH:/usr/lib/x86_64-linux-gnu/gazebo-9/plugins
export GAZEBO_MODEL_PATH=$GAZEBO_MODEL_PATH:/home/hjl/catkin_ws/src/px4_fast_planner/models
export ROS_PACKAGE_PATH=$ROS_PACKAGE_PATH:/home/hjl/catkin_ws/src/px4_fast_planner

I solved this problem by referring to answer in question 12.

@hjl0404 Great to hear that your issues is resolved. Can you please share a link to question 12 that you mentioned?

@hjl0404 Great to hear that your issues is resolved. Can you please share a link to question 12 that you mentioned?

Sorry, this is my first github question and didn't notice this, I have associated it with question 12, please see if this satisfies the requirements.


Added local implementation of the service and tests.

While reviewing this, it may be helpful to use the mapping of errors that I shared on docs. I in advance apologize for the size of the PR.

Ok. Ready to proceed with this.

Since GH doesn't display the diff for the tests, I'll comment on the original commit diff if it looks like the code is the same as in the most up to date version.  If that's not the case, I'll just post line numbers + comments for test code.

In LocalDnsHelperTest.java line 179, "zone" is repeated.  Also my preference is to remove this comment and similar comments since they reiterate relatively clear things.  Feel free to keep comments that document non-obvious details (eg the comment on line 161 about SOA and NS is helpful).

In testCreateAndApplyChange, could we make the delay shorter than 5 seconds?  This would make the tests run faster.

When testing paging, I think it'd be better to assert that properties of the object returned in the list match the expectation, rather than just checking the page size and asserting that the first page's result isn't equal to the second page's result.

Nit: line 1596, 1614 in the testing file, you have an extraneous line before the }

In the test file, testRandomNameServices() should probably only call randomNameServers() once.

Finished my first pass

Ok, I believe that I did everything except a few things that I commented on above (navigable maps for listing and default switch clauses). I also took care of some codacy suggestions.

I removed duplicated tests in DnsLocalHelperTest and kept only the ones using RPC. I also kept tests that cover some important internals that cannot be covered using RPC calls (mostly validations and respective error checks). I grouped the RPC tests at the beginning of the test file and the internals at the end.

I think almost all the codacy issues are valid and can be addressed (except changing the "LocalDnsHelper" class name is too long).  Also, I'm only partially through this pass; I'll add a comment at the very end when I'm finished.

Finished my pass.  I went a bit faster on tests, but it looks like you hit all the relevant code paths from my coverage analysis tool.

Ok, I am done with revisions.

Finished my pass, mostly minor stuff now.  Getting close to merging!

Also it looks like the codacy report is in, and there's a few more things that can be fixed, namely:

shortening the SUPPORTED_COMPRESSION_TYPES variable name
String[] fields defined before exit point
shortening the variable names resourceRecordSetListResult and managedZoneListResult in the test class

Addressed all comments. Ready to proceed.

Done with my pass

All fixed. Ready to proceed.

One nit, other than that, it's ready to merge.

LGTM, feel free to merge after squashing the commits and waiting for Travis to complete.


comment error

https://github.com/k2-fsa/sherpa/blob/927a99c9212dfb359777bf86c3211e145f7d0e75/sherpa/cpp_api/bin/offline-recognizer.cc#L50
https://github.com/k2-fsa/sherpa/blob/927a99c9212dfb359777bf86c3211e145f7d0e75/sherpa/cpp_api/bin/offline-recognizer.cc#L60
Hi, all
The above should be modify to true. The inner C++ code wanna true in the two decode mode also.
Thx.

@Innocence-0712
Yes, you are right.
Would you mind making a pull-request to fix it? Thanks!

Ok, Jun brother (军哥), I have made the pr. https://github.com/k2-fsa/sherpa/pull/275

@Innocence-0712 Yes, you are right.
Would you mind making a pull-request to fix it? Thanks!

You are welcome.
Ok, Jun brother (军哥), I have made the pr. https://github.com/k2-fsa/sherpa/pull/275

@csukuangfj You are welcome.
Ok, Jun brother (军哥), I have made the pr. https://github.com/k2-fsa/sherpa/pull/275

Closing via #275


[Bugfix][VM] Ensure set_input works over RPC by not returning an array of argument names

Currently, attempting to use the VM's set_input method will fail over RPC because set_input calls get_func_param_names, which returns an array of parameter names. RPC does not support sending arrays. This PR corrects this issue by instead having set_input query the function arity and then query the argument names one by one, which is the approach taken by the Relay VM (accordingly, the names for the functions used to do this, get_function_arity and get_function_param_name, are taken from the Relay VM).
This PR also adds a unit test over RPC on localhost. Please review @YuchenJin; I also wonder if we should have more RPC unit tests in that file.

Thanks @slyubomirsky for landing his first Relax PR!!  🎉 🚀


Type detector interpreting string as integer

the CFTypeDetector uses is_numeric to determine if the value is a number (OR a numeric string) to convert to a CFNumber. Any numeric string will be converted to a CFNumber, even if some values may be converted to CFString. This is not consistent enough behavior for my iPhone app to rely on.
Moving the is_string function before the is_numeric function will allow me to keep my string values as strings, especially if I explicitly juggle the type using (string)$value.
Other users of this library may get inconsistent results when trying to work with strings which may or may not always be numeric, like a phone number.

My first attempt at moving the is_string function did not work out well because everything coming out of my PDO request was a string. Changing is_numeric to ctype_digit ended up giving me the results I needed, granted that I padded the phone number fields with a "+" prefix.


Fix codecov uploader

Why are the changes needed?

https://about.codecov.io/blog/introducing-codecovs-new-uploader
https://github.com/marketplace/actions/codecov
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

Need to be verified by codecov bot

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Thanks, merging to master


Spot instance creation failure

Required Info:

AWS ParallelCluster version: 2.9.1
Full cluster configuration without any credentials or personal data

[aws]
aws_region_name = us-west-2

[aliases]
ssh = ssh {CFN_USER}@{MASTER_IP} {ARGS}

[global]
cluster_template = default
update_check = true
sanity_check = true

[cluster default]
key_name = pcluster
base_os = alinux2
scheduler = slurm
master_instance_type = t3a.micro
vpc_settings = default
queue_settings = compute
scaling_settings = default
efs_settings = default
post_install = https://im-aws-parallel-cluster.s3.amazonaws.com/amazon-post-install.sh

[vpc default]
vpc_id = vpc-08d9e908151dbeb3f
master_subnet_id = subnet-0733574dcfdb627b3
compute_subnet_id = subnet-07c49849cba9ddfce
use_public_ips = false

[queue compute]
enable_efa = false
compute_resource_settings = default
compute_type = spot

[compute_resource default]
instance_type = c5a.large
max_count = 2

[efs default]
shared_dir = efs
encrypted = false
performance_mode = generalPurpose

[scaling default]
scaledown_idletime = 10

Bug description and how to reproduce:
Spot instances fail to create.
In the /var/log/parallelcluster/slurm_resume.log I see this error:
2020-11-23 15:00:57,759 - [slurm_plugin.resume:_resume] - INFO - Launching EC2 instances for the following Slurm nodes: compute-dy-c5alarge-1
2020-11-23 15:00:57,857 - [slurm_plugin.common:add_instances_for_nodes] - INFO - Launching instances for slurm nodes (x1) ['compute-dy-c5alarge-1']
2020-11-23 15:01:00,496 - [slurm_plugin.common:add_instances_for_nodes] - ERROR - Encountered exception when launching instances for nodes (x1) ['compute-dy-c5alarge-1']: An error occurred (InsufficientInstanceCapacity) when calling the RunInstances operation (reached max retries: 1): There is no Spot capacity available that matches your request.
2020-11-23 15:01:00,497 - [slurm_plugin.resume:_resume] - INFO - Successfully launched nodes (x0) []
2020-11-23 15:01:00,497 - [slurm_plugin.resume:_resume] - ERROR - Failed to launch following nodes, setting nodes to down: (x1) ['compute-dy-c5alarge-1']
2020-11-23 15:01:00,497 - [slurm_plugin.resume:_handle_failed_nodes] - INFO - Setting following failed nodes into DOWN state: (x1) ['compute-dy-c5alarge-1']
2020-11-23 15:01:00,507 - [slurm_plugin.resume:main] - INFO - ResumeProgram finished.

It seems that no spot instances were available. But in the AWS console I don't see any spot requests of any type. Is this expected, or does it indicate something else is wrong?

Hi @tdudgeon,
it's expected to not have a spot request entry. It's the RunInstances operation call that is failing for InsufficientInstanceCapacity.
You can track this failure in CloudTrail or CloudWatch events, where you should see an event similar to
        "eventTime": "2020-11-24T14:20:36Z",
        "eventSource": "ec2.amazonaws.com",
        "eventName": "RunInstances",
        "awsRegion": "...",
        "sourceIPAddress": "...",
        "userAgent": "...",
        "errorCode": "Server.InsufficientInstanceCapacity",
        "errorMessage": "There is no Spot capacity available that matches your request.",

Thanks


caching nix builds

i wonder if we could maybe alleviate local builds by say having a cachix user for niri.
if so, would it be best if this were done from niri-flake, from the upstream niri repo, or from both?

I have considered this already, and i've talked briefly about it in the matrix chat room. I like the idea, but i think it'd have to be in upstream niri, for two different reasons:
(A) Trust. if i'm hosting the cached builds, then that inherently puts a level of trust on me for the users, that doesn't need to exist now. As of now, it's fairly easy to verify that the code really does compile the code in YaLTeR/niri, even without significant nix experience. It's also not too hard to keep up with most changes, as this is generally not updated that frequently and even then, not anything that's hard to grasp, usually "update deps", "fix build inputs after a new niri commit", "update README", and the occasional "actually refactor flake to implement something new". With a binary cache, this is no longer the case, as from my understanding, i can "just" upload malware and sign it. I wouldn't do something like that, but i am vaguely uncomfortable with the thought of "just trust me bro".
(B) Update frequency. It's possible to automate cachix builds with GitHub Actions and publish on every commit. This is ideal. This flake does not update with every commit of niri. I suppose it's more reasonable to cache, now that there are "stable" release tags. We could just cache the stable releases - not every commit. Though, if i were to cache every commit, the only reasonable way to do that is to have a scheduled task that automatically updates the niri-src input.
(C) what about nixpkgs? With the recently implemented fix for the driver issue, niri-flake no longer uses the same nixpkgs on all systems by default - instead, it's overriden by the config to use the system's pkgs special args. So what do we actually cache? the packages.*.niri output of the flake is not what most people will actually be building anymore. Realistically, even if we only support stable niri, i do expect unstable nixos to work no matter what (because.. that's the channel i'm running, so i think it's fair that i decide it must be supported in my own project - this same logic applies to niri-src). Therefore, we would pretty much need to schedule updates and at the same time update niri-src and nixpkgs. But do we support stable niri also? Stable nix? Then, we basically have a two-by-two matrix of supported versions, where if any of the four tracked sources (stable/unstable, niri/nixpkgs) have a new commit or release, then we cache two new builds (or four, if you multiply by the amount of build platforms). If this were implemented, that would honestly be perfect, besides potentially cluttering the commit history (but who cares, that can be filtered, or can be moved to a separate repo if too much of an issue)
The main reason i'm hesitant to even begin would be (A). If we could get upstream niri to cache nix builds (they use a different rust-nix toolchain, but that's okay as i use crate2nix primarily for the build times, given the lack of a cache), this would solve both (A) and (B) in one go, as well as make the CI cleaner (on every commit is possible when in same repo, instead of needing to schedule). It would also prevent the need for any kind of scheduled updates. It would make (C) worse, as it would not receive as frequent love and care as a dedicated nix repo would. (though, we could try to make it work anyways, and in general, stable nix is not as important of a target)
The main reason i actually don't do it would be (D) i don't know how to use cachix. I need to learn somehow, but it feels "wrong" to binary cache someone else's project when i am neither your distribution packager, nor a long-term contributor to the original project. I was gonna say i'm not a frequent contributor, but then again, i suppose i am. Not always in source code, but i've helped improve documentation, and significantly helped in making it work well on NixOS. So, really, the other reasons are not at all reason why we can't have a binary cache - they're reasons for me to procrastinate :3
Do you have any experience in using cachix? if you or someone else interested does, i'd love to have some guidance on how to do it and set up a cache. I suppose, a decent enough solution to (A) would be to just have a disclaimer that you are putting additional trust in me as a distributor. Writing this comment has made me realize how beautiful the setup can look, and i am suddenly motivated than i was before.

(A) Trust. if i'm hosting the cached builds, then that inherently puts a level of trust on me (...) i am vaguely uncomfortable with the thought of "just trust me bro".

If we could get upstream niri to cache nix builds (...), this would solve both (A) and (B) in one go, as well as make the CI cleaner (on every commit is possible when in same repo, instead of needing to schedule). It would make (C) worse, as it would not receive as frequent love and care as a dedicated nix repo would. Of course, that's just a result of the current state of nix already in YaLTeR/niri, not something we couldn't solve. Even with the current state of nix in YaLTeR/niri, we could just make sure it has nixpkgs unstable updated frequently and leave stable nix alone.

@YaLTeR thoughts? Ultimately, a binary cache is opt-in by design. Existing users cannot and will not download anything from a binary cache without explicitly adding it as a trusted signing authority (at least, that's my understanding). Would you be okay with me implementing this? Would you prefer to it be implemented in upstream niri? At that point, i think it would be reasonable to move the whole module into upstream niri as well, and deprecate this repo. But then, how would we handle stable niri? It needs to be kept up-to-date with updates to nixpkgs (or mesa will eventually become outdated).

Would you be okay with me implementing this?

Sure. I mean, almost nobody reads AUR PKGBUILD for example, so this trust issue is already implied in most packages.

Would you prefer to it be implemented in upstream niri?

I'd prefer it to be separate, I think it's better to keep nix concerns to a separate nix repo, they can be addressed quickly and without dragging away focus in the main repo issues. Also it's not like every single commit needs to update the cache. If it happens once a day or once a week or just for stable releases, that sounds reasonable to me.

Sure.

Alright, awesome! Let's do some caching!

I mean, almost nobody reads AUR PKGBUILD for example, so this trust issue is already implied in most packages.

From my understanding, AUR packages are compiled locally (of course, not including ones with binary blobs but that's not part of what I'm talking about, and inevitable for proprietary software). This is akin to my current package, which is also compiled locally. True, many people won't read it still.
Though, from my personal experience, I think the percentage of those who do on nix is higher because to use NixOS, you must be able to work with the Nix language, which is used for packaging too. I regularly read the source of nix packages I'm using, even ones in nixpkgs. Say what you will about what that means for how robust the systems are ("a good technology is one you don't have to think about when using. given that, i sure do think about Bluetooth a lot"), but I do read them often. compare that to Arch, which I have used previously, and I never read any PKGBUILD, nor learned to make one. I didn't need to at the time. I can read the niri PKGBUILD, and I did just now but having never looked at one before, though it was slightly overwhelming and ultimately it just does like... cargo build and copies files. But it looks like it does so much more at that length. It also remaps the path prefix so that the arch-specific build does aren't exposed in traces (which I do too).
No matter how many do actually read the source of the package they install, that's missing my point completely. Binary distribution needs trust by being inherently opaque, which is different than the current state of niri packaging which does not need trust, it is transparent and the people who don't read the packaging source are doing it out of convenience. With a binary cache, your only option to establish trust is to actually compile it locally and compare results, which defeats the point of a binary cache.
Personally, I think the total size of source code is more relevant to whether it is reasonable to read. I haven't read the full niri source code, it's not reasonable for me to do, so I am putting trust in you by doing that. It is reasonable to read a <100 line PKGBUILD or <300 line nix package + modules, therefore there is no "absolute trust out of laziness", at least for me.
Therefore, my logic goes, it is best if [The Software That I'm Too Lazy To Audit The Source Code Of]'s author is the one signing/managing the binary cache (since they are already trusted to run unreviewed code on my machine, so what difference does it make if it is unreviewable?)

Also it's not like every single commit needs to update the cache. If it happens once a day or once a week or just for stable releases, that sounds reasonable to me.

 If anything, that's more important than keeping the stable releases cached, because they are more frequent (and thus, users will experience more frequent rebuilds = more wasted time per capita for unstable than on stable).
nixpkgs is less frequent, especially for updates that affect niri, so running that daily would be just okay. there is a risk that the nixpkgs update hasn't made it into the binary cache yet, and if this were in upstream niri without also moving all of nix there (i.e. module is still managed here), that might actually break the user's system if niri is not updated (given that we don't implement our own unstable cross-repo-dependent nix interfaces to solve the mesa issue that way). With how it's currently set up in this repo, the worst fate possible is a forced rebuild.

on nixpkgs version, i run unstable too. that said, i would rather give up the like 50 mb of storage to also keep a copy of stable nixpkgs if that were to mean not having to spend time rebuilding niri on each update.
not that cached unstable wouldn't be cool, tho skipping that for now might be easier than keeping it updated too. tho, i guess it should be possible to automate that too.
on using cachix, i think their docs def help. ^^
the trust concerns reminded me a bit of this thread i saw come by today, tho i'm not sure that helps for cachix.

i would rather give up the like 50 mb of storage to also keep a copy of stable nixpkgs if that were to mean not having to spend time rebuilding niri on each update

Though, this is not the whole story. mesa must match. So you're not just "keeping a copy", you're running that as your main. Is it possible to manually override mesa? I'd imagine it is, but surely other packages might break then?

on using cachix, i think their docs def help. ^^

Oh yeah, i have read some of them. I've just not been "invested" in doing it (see above notes on procrastination), and my naive impression is that it's not entirely clear how the process works or how to set it up for my use case.

the trust concerns reminded me a bit of this thread i saw come by today, tho i'm not sure that helps for cachix.

This seems to be about signing git commits to eliminate trust of the remote repository vendor. For nixpkgs, this is reasonable, their builder automatically fetches from GitHub and builds and signs it autonomously. I don't know why, but i have an inherent trust in these autonomous systems. That's not for a rational reason, just that it "feels" more trustworthy because i'd imagine no one single person can easily sign anything not going through nixpkgs. If cachix were just "Hydra but you can add your own repo and we'll do the rest", i.e. "point us to your flake, we'll build and cache and serve it" i would trust it more, because the individual developer does not have control over the actual binary, just the build process which is published and followed by a bot. Like F-Droid, which also builds all applications on-site from source, and does not allow binary uploads. This system still requires trust, but in a single system with an established userbase. With cachix, i alone (and whoever i share it with, intentionally or not) hold the signing keys. From my understanding, it's essentially just file storage targeted at nix users. I'm responsible for building, uploading, and signing binaries. That's an important distinction, because now, when using this, you are trusting the one single individual. I'm not scared of any actual risk of compromise - i'm confident that i will never serve you malware, but i don't expect you to take that at face value and inherently trust it. If a trusted third party built them automatically (such as nixpkgs' hydra infrastructure), then they're the one you're inherently trusting, not me (because everything i publish is then easily audited).
As you might be able to tell by the length of my replies on the topic, i have a lot of feelings about it. It's not too different from password storage - it is inherently a sensitive task, that can have consequences if i don't do it properly. I would much prefer it be outsourced to a third party, like if there was an "Upload nix expressions and we'll handle the rest" service, that people already trusted, or in the analogy to password storage, simply not letting you use email/password with my service, and rather only have login with GitHub.
Ultimately, i think i made my mind up in the previous comment. I'll just bite the bullet and actually try to do it.

Also, nixpkgs niri just got merged! We're not going to cache stable niri in this repo, as soon enough it will already be part of nixpkgs (and!! we get to completely ignore the mesa issue for stable niri because it will build with the rest of nixpkgs) This repo will then provide modules and bleeding edge packages.

right, i see your point about hydra-like systems being nicer.
especially with niri having been merged to nixpkgs, that would maybe raise the question if using this module with their niri package as well. while i've been pretty excited for new niri features, i'll admit if this repo can focus on nix-y stuff over caching every permutation that'd seem nice as well.

I've created a binary cache at niri.cachix.org and the first build succeeded in 16 minutes (https://github.com/sodiboo/niri-flake/actions/runs/8005765016/job/21865962010). I'd hope that subsequent builds are gonna go a little faster, having already cached many dependencies. I think you can add the public key to your nix config, and it'll work automatically.

The problem is that the builds uploaded by GitHub Actions have a different hash from the one my system wants to build locally. Cachix docs suggest downloading the cached version, and running nix-diff, which is all good and well except for the fact that the cache doesn't seem to contain the actual derivations for niri, only the built results. As such, i cannot download the derivation, which is needed for cache to work. I get this error if i try to diff the cached and local builds:
> nix-diff /nix/store/cn5czczhpyv9ncfmvcnw8qm1xqsigbhi-rust_niri-0.1.2 $(nix eval --raw .#niri-stable)
nix-diff: /nix/store/msp3m83zm2zx6xy034fd3z3c7f4c3zl5-rust_niri-0.1.2.drv: withBinaryFile: does not exist (No such file or directory)

/nix/store/cn5czczhpyv9ncfmvcnw8qm1xqsigbhi-rust_niri-0.1.2 is the result of nix build .#niri-stable from GitHub Actions. It has been stable for all 3 runs, across different commits, so clearly there is something reproducible about niri-flake that works in CI but is not consistent to my machine (niri-unstable package was not as stable in output, due to accidentally relying on stable tag for resources). You can download the result from the cache if you search for it https://app.cachix.org/cache/niri#search
/nix/store/msp3m83zm2zx6xy034fd3z3c7f4c3zl5-rust_niri-0.1.2.drv, however, is the deriver of that path. It does not get downloaded when you realize the path. Cachix search does not list it in the results. Documentation does not seem to have an easy way to ensure derivations are uploaded. anti-patterns/best-practices documentation also does not seem to contain anything that i'm obviously doing incorrectly that would cause nonreproducible builds. Cachix doesn't seem to actually host the derivation file anywhere, which is obviously inconvenient if i want to debug it.
@KiaraGrouwstra Do you have any idea what might cause this?
nix eval --raw .#niri-stable on my system, for reference, outputs /nix/store/lwb2finnfgm67hv6n8wayxczivyg8fx5-rust_niri-0.1.2. Is it the same on yours, or different yet again?

One possible source for the nonreproducibility that i find, might be different versions of nix? That doesn't feel like it would follow nix philosophy, if everything changes upon upgrading nix (it is not a dependency of the application), but CI gets 2.19.2 https://github.com/sodiboo/niri-flake/actions/runs/8011204611/job/21883900099#step:3:349 whereas on my system nix --version => nix (Nix) 2.18.1 which is the default version of just plain nix package on nixpkgs unstable (which seems to be equal to "nix stable"? i.e. the actual tooling, not nixpkgs)

Do you have any idea what might cause this?

Also, do you have any idea how i might obtain the derivation produced in CI, such that i can diff it with local?

looks like you can upload the actual derivations to cachix as well.
matching nix versions could help, but maybe the derivations can help give more info there...
i get the same nix-stable hash as you :), also on unstable nixpkgs.

looks like you can upload the actual derivations to cachix as well.

Seems to work. It's pushing a lot of new paths now: https://github.com/sodiboo/niri-flake/actions/runs/8012279567/job/21887240754

Heck yeah! I can download the derivation now.
- /nix/store/cn5czczhpyv9ncfmvcnw8qm1xqsigbhi-rust_niri-0.1.2:{out}
+ /nix/store/lwb2finnfgm67hv6n8wayxczivyg8fx5-rust_niri-0.1.2:{out}
• The input source named `source` differs
• The input derivation named `rust_niri-config-0.1.2` differs
  - /nix/store/hsa1c1c0vc2v0c9dxijsiy1ism0q1hll-rust_niri-config-0.1.2.drv:{lib}
  + /nix/store/qzqrj97vzwn831sg3vkr5f6w1l385hd4-rust_niri-config-0.1.2.drv:{lib}
  • The input source named `source` differs
  • The input derivation named `rust_niri-ipc-0.1.2` differs
    - /nix/store/p9slkmdi2cw9jmq6alihk38s30k0kh1d-rust_niri-ipc-0.1.2.drv:{lib}
    + /nix/store/d5h2sg0a219svyiissb9j52bivhzw22n-rust_niri-ipc-0.1.2.drv:{lib}
    • The input source named `source` differs
    • The environments do not match:
        src=''
        [[- /nix/store/0csnfshpwrxiblshry6yajc6czdmhhsy-source ]][+ /nix/store/nl0vqmprmxky4jpvap4ymwjm4a7glskh-source ]]
    ''
  • Skipping environment comparison
• The input derivation named `rust_niri-ipc-0.1.2` differs
  • These two derivations have already been compared
• Skipping environment comparison

with my own flavoring of [[+ inline-addition ]] and [[- inline-removal ]] to replace red/green bg color

It is also important to note, that the two paths above appear to be identical except for their actual, well, path. diffing the contents returns absolutely no changes whatsoever. they reference the niri-ipc subdirectory of YaLTeR/niri

so the diffs seem to manifest only at the build results yet not at the derivation?
that does seem odd. might this be about nix versions then?

It seems to be that, despite having identical contents, the hashes of the sources generated by crate2nix are different. I think this is likely a symptom of import-from-derivation. However, fear not! The solution appears quite simple. Just override the src argument for each crate. I've done it on a separate branch, just so i can keep it separate from main for now: https://github.com/sodiboo/niri-flake/compare/main...cache_experiments

Update: The Ci job finished, and my system can now substitute from the binary cache! Yay! Time to implement into main.

Binary cache is now implemented, and it's reproducible: https://github.com/sodiboo/niri-flake/commit/9dc8b646ffdbe5316b7d8df5152243ce0a90ae34
This issue is not complete, however. Before we finish up, there are a couple more things to do:

Document the binary caching, and how to enable it.
Set up automation to create PRs soon after pushes to niri. (and updates to nixos-unstable, for that matter)
Set up automation to merge those PRs once the builds are finishes, if the builds are successful

[X] Document the binary caching, and how to enable it.
[X] Set up automation to create PRs soon after pushes to niri. (and updates to nixos-unstable, for that matter)
[ ] Set up automation to merge those PRs once the builds are finished, if the builds are successful

CI now runs on PRs and it works well. Here are the three pull-requests that automation made thus far:

#8
#9
#10

Basically everything i need now is implemented, except for one final piece: Automatically merge PRs made by github-actions[bot] if and when all checks have passed.

Here are the three pull-requests that automation made thus far

See also: frustrating commit history. https://github.com/sodiboo/niri-flake/compare/354995b9621922eda5491f892441740781660869...ca963fe6334bb075c560e58121683ae919170083

that feels a bunch like what my commit history tends to look like 😄🙈

I've added mergify to this repo, and set up rules to match. https://github.com/sodiboo/niri-flake/commit/eaf1968f0fb4b2cd6f524416f13be0140b16ba8b
Their online editor has a playground to check whether it will trigger on specific pull requests, and the only thing that seems off is the fact that none of the currently existing PRs will merge, because the -closed merge requirement is not met. I suspect this simply means that the PR is already closed, therefore mergify will not act on it. If that's the case, then based on their config checker the rules should be correct.

I'm updating my warnings to reflect the fact that the niri-src input is deprecated, and i'm noticing like basically everything i wrote about nixpkgs niri doesn't apply anymore. Now, with binary caching, there is approximately zero benefit to making that one the default. I'm gonna make my own niri-stable the default again, even though i've written in many places that nixpkgs will be the default.

that's cool! i don't really want nixpkgs to get in the way of niri features myself, so i'd def welcome that.
i'm a bit confused still on how one would use unstable now (aside from using the now-deprecated niri-src), so looking forward to a readme update on that.

Scary!

that was how i felt when trying to nixos-rebuild to your config earlier 🙈, i'd never tried something like that before

#12 was just created, pushed, built, and merged completely autonomously. I think it's safe to say that the binary cache is now complete, including automatic updates.

i'm a bit confused still on how one would use unstable now (aside from using the now-deprecated niri-src), so looking forward to a readme update on that.

Does the commit i pushed while you were writing this sufficiently answer the concern?
https://github.com/sodiboo/niri-flake/commit/5626d865a42ce58aa0e90f4824441323ca720fff

If you do not wish to use an overlay, you can also just use niri.packagess.x86_64-linux.niri-unstable directly. The difference is that this will use nixpkgs from latest commit to flake, but overlay pkgs.niri-unstable is guaranteed to match your system's nixpkgs. In 99% of cases, this will match, but after nixpkgs updates there may be a slight window where it isn't. In that timeframe, using the overlay makes you rebuild niri, which is slightly more preferable than the worst-case scenario for out-of-sync, where mesa will be out of sync.

I'm gonna take the heart reaction as my response being a sufficient answer to your question about using niri-unstable. I consider a binary cache to be successfully implemented. This issue can now be closed

thanks, that seems clear.
i am however having issues running that still tho:

error: attribute 'niri' missing
inputs.niri-flake.overlays.niri
^

would you have a working commit on this on your repo? i'm curious what i'm getting wrong there

thanks, that seems clear. i am however having issues running that still tho:

error: attribute 'niri' missing
inputs.niri-flake.overlays.niri
^

would you have a working commit on this on your repo? i'm curious what i'm getting wrong there

The commit you've linked seems to lock niri-flake to an older revision: https://codeberg.org/kiara/cfg/src/commit/5d0cd89d25a51d6327ae6e9f08f22f4421c5098a/flake.nix#L94
The overlay was added 5 commits later: https://github.com/sodiboo/niri-flake/compare/8eb71d53594db49935b6d1fa50c5e7b44d3ae567...251aca19f7f10b71dd81b11af012393ffa5b15bd
I recommend unpinning the niri-flake revision.
The latest revision of my own config builds just fine for me, and uses the overlay like so (verbatim equal to the README): https://github.com/sodiboo/nix-config/blob/6457cb8528a066088eed800224e347f088deb199/niri.mod.nix#L156-L157

ah whoops, thanks! :pray:


upd(apx-git): 2.4.0 -> 2.4.3

the problem is not related to the package but some golang package can't be download throw proxy,
"dial tcp: lookup proxy.golang.org on <IP_ADDRESS>:53: read udp "

the problem is not related to the package but some golang package can't be download throw proxy,
"dial tcp: lookup proxy.golang.org on <IP_ADDRESS>:53: read udp "

add this variable to the pacscript
external_connection=true
https://github.com/pacstall/pacstall-programs/pull/6383#issuecomment-2326516390
This script wasn't maintained...

the problem is not related to the package but some golang package can't be download throw proxy,
"dial tcp: lookup proxy.golang.org on <IP_ADDRESS>:53: read udp "

add this variable to the pacscript
external_connection=true
#6383 (comment)
This script wasn't maintained. It may need some adjustments.

think you, i made a change as advised to allow package access to internet during installation

Fix the title to conform to our standards, as explained in our docs. You can also look at past PRs to get an idea of how to format the title if you're unsure.

Build fails because apx's Makefile uses sudo, which is bad practice and not supported by Pacstall.
For a quick fix, please patch the Makefile like this in prepare()
sed -i 's/sudo //' Makefile

Hi, We have merged the Makefile PR upstream, can someone retrigger the failing jobs?

I retriggered them, but there's now an error I don't understand on debian:stable
https://github.com/pacstall/pacstall-programs/actions/runs/10736150513/job/29971996728?pr=6394#step:11:867
Gonna take a guess this is due to the outdated Golang?

Nevermind, you've indeed specified Go 1.22 in go.mod

Fix the title to conform to our standards, as explained in our docs. You can also look at past PRs to get an idea of how to format the title if you're unsure.

my mistake, i will try to read the documentation and i will do as you asked

Sorry, I assumed you were inactive, and I edited the pacscript to use Golang 1.22
The sudo patch is not necessary anymore since I submitted a PR upstream that fixed the issue, so you can remove that line

Sorry, I assumed you were inactive, and I edited the pacscript to use Golang 1.22 The sudo patch is not necessary anymore since I submitted a PR upstream that fixed the issue, so you can remove that line

ok my mistake, i will remove the line with sudo

Add
export PATH=/usr/lib/go-1.22/bin:${PATH}

To prepare(), since Go 1.22 is not in PATH by default

do i still need to add this line ?

Yes

Add
export PATH=/usr/lib/go-1.22/bin:${PATH}

To prepare(), since Go 1.22 is not in PATH by default

do i still need to add this line ?

it's still reporting that go not found, do you have an idea how to resolve ?

It's my mistake. That export should be done in build(), right before calling make

It's my mistake. That export should be done in build(), right before calling make

thank you, i think it's more my mistake than yours, i wanted to help but it ended up by you @vigress8 doing all the work

@souhaiebtar can you please make a PR that adds the line incompatible=("*:bookworm"). We forgot that before this was merged.


Is this repo still maintained?

encounter error in python extract.py vol2a.pdf vol2b.pdf

I haven't worked on it for a while. If you look at the network graph, there are at least two forks with more advances.


BUG: itkhdf5 installed paths were incorrect with recent hdf5 versions

The aliasing for the build tree was incorrectly matched to
install tree file name directory for H5Cpp.h.
#include "itkhdf5/itk_H5Cpp.h"
Resulted in an error of missing headerfile "itkhdf5/cpp/H5cpp.h"
when building against an installed version of ITK.

PR Checklist

[x] No API changes were made (or the changes have been approved)
[x] No major design changes were made (or the changes have been approved)
[x] Added test (or behavior not changed)
[x] Updated API documentation (or API not changed)
[x] Added license to new files (if any)
[x] Added Python wrapping to new files (if any) as described in ITK Software Guide Section 9.5
[x] Added ITK examples for all new major features (if any)

Refer to the ITK Software Guide for
further development details if necessary.

CI failures are unrelated.


Implement server side code

Would be nice to have. Would start by decrypting data and eventually could be used to push data into a data base and manage multiple domains.

I should have time to work on the server-side this week


Port of: https://github.com/Azure/azure-cosmosdb-java/pull/312

Doc producers are spun for each partition range, and each one should have its own copy of feedoptions. In the existing implementation same copy of feedoptions is being used for all the producers due to which there is a possibility of loosing continuation token depending on the order of creation of document producers when multiple (>2) partition ranges are present. This PR addresses this issue and ensures feedoptions are set properly for each producer.
Port of: https://github.com/Azure/azure-cosmosdb-java/pull/312

/azp run java - cosmos - tests


fixup syntax

this fixes some minor indention issues

Current coverage is 81.26% (diff: 100%)

Merging #4597 into master will decrease coverage by 0.09%

@@             master      #4597   diff @@
==========================================
  Files          1297       1297
  Lines         44206      44206
  Methods           0          0
  Messages          0          0
  Branches       6991       6991
==========================================
- Hits          35966      35925    -41
- Misses         5566       5611    +45
+ Partials       2674       2670     -4

Powered by Codecov. Last update 3acd0a7...e0762ee

@matriv updated the commit. pls review!


Computer freeze and SteamVR crash on v20 nightly after initial setup

Description
ALVR v20 nightly freeze my computer for 5-10 seconds and then SteamVR crash just by closing and start ALVR again after the initial setup.
Also very weird, If I'm quick enough to put back the headset and connect to ALVR before SteamVR start the computer won't freeze.
I checked the Event Logs and noticed that vrserver.exe and ucrtbase.dll are mentionned.
Exception code : 0xc0000409
Error offset : 0x000000000007286e
Steps to reproduce the issue

Fresh install of ALVR nightly (any builds)
Initial setup and leaving default settings
Connect headset
ALVR auto-restart
SteamVR open again
Close ALVR and start it again
Computer freeze for 5-10 seconds then SteamVR crash
The issue repeat again and again

General Troubleshooting

[x] I carefully followed the instructions in the README and successfully completed the setup wizard
[x] I read the ALVR Wikis here and here

Environment
Hardware
Note: for Linux, an upload to the hw-probe database is preferred: hw-probe -all -upload
CPU: Intel i7-11700KF
GPU: RTX 3080Ti
Audio:
Installation
ALVR Version: ALVR v20 nightly (any builds)
SteamVR Version: 1.24.7
Install Type:

[ ] Packaged (exe, deb, rpm, etc)
[x] Portable (zip)
[ ] Source

OS Name and Version (winver on Windows or grep PRETTY_NAME /etc/os-release on most Linux distributions):
Windows 10 22H2 build 19045.2486

Does v19 crash for you? can you identify the first nightly build that crashes for you?

v19 doesn't crash and yeah I'll test and find out

Ok after some testing I can confirm ALVR v20.0.0-dev03+nightly.2022.12.10 and onward make my computer freeze and SteamVR crash with the error code I mentionned. Other nightly versions before work perfectly fine.

Idk if it's related but I noticed on ALVR v20.0.0-dev02+nightly.2022.12.05 that there is a memory leak or something.
I got spammed with this when I connected:
15:14:50.526750600	[INFO]	Client 9686.client.alvr: [Warning] Video frame queue underflow!
15:14:50.540438100	[INFO]	Client 9686.client.alvr: [Warning] Video frame queue underflow!
15:14:50.624169800	[INFO]	Client 9686.client.alvr: [Warning] Video frame queue underflow!
15:14:50.693669300	[INFO]	Client 9686.client.alvr: [Warning] Video frame queue underflow!
Followed by this when I disconnected:
15:14:50.897439900	[INFO]	Client 9686.client.alvr: [Error] FIXME: Leaking Imagereader!
15:14:50.898716700	[INFO]	ClientDisconnected
15:14:50.898746300	[INFO]	Client disconnected. Cause: At alvr\sockets\src\control_socket.rs:36

unrelated

Can you build the server and client yourself? Or I could provide few versions excluding some commits to see if they work for you. There're only 3-4 commits that change some code between 2022.12.05 and 2022.12.10.

I would prefer that you provide me said builds.

Okay, here's one build just before https://github.com/alvr-org/ALVR/commit/46c7e977c22ee0ba2fe28376ac5d4f6066064c05.
alvr_server_windows.zip
alvr_client_quest.zip

That build seems to works fine. Also there was nothing in the minidump folder.

Could you also check whether Quest Pro controllers work for you well too? Maybe it's related to https://github.com/alvr-org/ALVR/issues/1378.

Ok I test this build and yep this is the cause.
Also on both builds the Quest Pro controllers issue is still there. I guess it's related to another issue since even on v19 the problem is there.

@Nyabloody Please test this server together with the last apk sent by @deiteris. The controller tracking will be wonky but it doesn't matter for testing sake.
alvr_server_windows.zip

Issue fixed in commit https://github.com/alvr-org/ALVR/commit/fb17bf762eeab6f041049f254d36396be0eb436a


Bug: Multiple select gets jumpy when used in the ui-bootstrap modal body

When a user tries to click the options inside the select with multiple, which is located inside the modal-body of  ui-bootstrap modal, sometimes it gets jumpy and reverts back to previously selected options:
demo : http://plnkr.co/edit/Bg3hYkcClhYq5JSnHX8d?p=preview
Currently I was able to workaround this problem by adding this to
        selectElement.on('click', function(evt) {
          evt.stopPropagation();
        });

after line 343 in src/ng/directive/select.js. I do not know whether this is a proper solution or really did not have time to test this for side effects.
PS: Tested on Chrome 33.0.1750.146.

Interesting. The last plnkr shows this pretty well. Basically, when the multi select is scrolled somewhere in the middle and the height of the modal changes (in the plnkr, this happens when items are sent from one to the other list), the select scrolls a little bit, which is unexpected. It doesn't affect the selection, though. Happens in FF and Chrome.

@Narretz, what you describe (which is probably different from what OP faces), only happens when you remove items that are higher than the currently scrolled to item. Basically, the select doesn't scroll, but it's height and items change.
I.e. when you have scrolled the select to scrollTop === 130 at which point item foo is visible and then remove 10 items above foo, the select remains at scrollTop === 130 but now item bar is visible at that point (because item foo moved 10 positions up).
I don't know if browsers should be smarter and keep the selected element or currently visible element in the viewport (I lean towards they shouldn't), but this doesn't sound like an Angular issue.
That said, I can't reprodice the original issue on Chrome 43/Win8.1.

@gkalpak Yes, you are right, this seems to be a different problem. Annoying, but also with very little impact.
Since I also can't reproduce the original problem, I'm gonna close this issue.


Types not respected everything is a string

Unsure if this is true for all results, using transactions as an example all number and date types are returned as strings. Appreciate this should be fixed in the upstream REST API but are there plans to resolve in python first?
import currencycloud as cc
client = cc.Client('yourid', 'yourapikey')
res = client.transactions.find()
trans = res[0]
print(type(trans.amount))
print(type(trans.settles_at))

Hi @cjstudioz, the SDK's mapping of JSON to Python objects assumes string as default type to allow for maximum flexibility client-side across all the versions of Python we support (2.7 and onwards), but we recognise this approach eschews all the benefits of better (safer?) typing and expect to address by the time 2.7 reaches EOL or sooner.
Community contributions are also welcome :bowtie:

Thanks, are you suggesting you'd be open to me augmenting the python SDK to cast the types appropriately in the python objects. This could potentially be breaking change if someone relies on them being strings.
I will likely make changes in my own fork and you're welcome to merge them back into your repo should you wish. however, if you're open to accepting those changes, I will endeavor to make it easier for you to integrate but I also need to be commercial and practical with how much time I can spend on this

We welcome all voluntary community feedback and enhancements. Our contribution guidelines are available here


updated react to 15.5

fixed PropType deprecation, it now uses it's own depencency prop-type
source: https://facebook.github.io/react/blog/2017/04/07/react-v15.5.0.html

Perfect!. Only one thing... You don't need to commit the generated files under lib. They are automatically generated when released. Just remove them from the commit and I will merge it.
Thanks!


ams template: references to theorem labels don't include the heading

The heading number is included in the theorem itself, but not when you reference it. The numbering should be consistent.
Example based on main.typ in the ams template:
#theorem[
  The square of any real number is non-negative.
]<thm:sq-positive>

#proof[
  Any real number $x$ satisfies $x > 0$, $x = 0$, or $x < 0$. If $x = 0$,
  then $x^2 = 0 >= 0$. If $x > 0$ then as a positive time a positive is
  positive we have $x^2 = x x > 0$. If $x < 0$ then $−x > 0$ and so by
  what we have just done $x^2 = (−x)^2 > 0$. So in all cases $x^2 ≥ 0$.
]

= Introduction

#theorem[
    For any right-angled triangle with legs $a,b$ and hypotenuse $c$:
    $
    a^2 + b^2 = c^2
    $
]
<thm:pythagoras>

This is a new section.
We now use @thm:sq-positive
and @thm:pythagoras

I have the same issue with table.
Maybe we should change the following lines…
https://github.com/typst/templates/blob/7cec678fb6a6782361c79f3ac87c41a8a2b4a0a2/ams/template.typ#L151-L154
…to…
      smallcaps(it.supplement)
      if it.numbering != none {
        [ #it.counter.display(it.numbering)]
      }

Relevant: The example of modifying the appearance in Figure Function – Typst Documentation.

I apologize to you… It's hard than I thought.

#10 is the first step, and is done.

Now the theorem counter does not even count the heading — it's only displayed.
https://github.com/typst/templates/blob/7cec678fb6a6782361c79f3ac87c41a8a2b4a0a2/ams/template.typ#L168-L169
The counter is reset when a new chapter starts.
https://github.com/typst/templates/blob/7cec678fb6a6782361c79f3ac87c41a8a2b4a0a2/ams/template.typ#L115
To fix that, we should turn it into a multi-level counter. It's possible, but I don't know how to start…

I can't reproduce this issue. If an issue remains, please open a new one. We could also consider porting the AMS template from its own theorem handling to one of the packages.


add support for private container repositories

Using private container repositories with CodeBuild requires a way of passing in credentials.

Closing down project: #52


Retrieve Orders and Modify it

Hello,
I am using the app to create Tracking numbers of Orders that app received through Orders View. Now we are selecting N orders and sending it to our app. Now we are using Private App Credentials to get info and modify each order... because I can not retrieve info using App credentials, like this:

how can I do it?

Hi @jonatannietoa
were you able to figure this out?

Closing because this project is now deprecated.


Operation request which requires state information

I have run into a case quite frequently where I have an operation on a request which requires some state information before I can dispatch the request. So I run a select -> dispatching the request. However this causes me to have to dispatch 2 different actions: first we have to dispatch the action to run the saga, then we run the saga, then we call the request action.
The downside of this with redux-act is the user dispatches action1 but they have to watch for action2 on the store. Example:
// Call to run set feature saga
const setFeaturesAction = createAction(`set ${type}`);

const _setFeaturesAction = createAction(`set ${type} internal`, ({ map, [type]: features }) => {
  return {
    request: {
      url: '/v2/maps/operations/',
      method: 'post',
      data: formatRPCCall(`set${typeCapitalized}`, {
        map_id: map.id,
        features,
      })
    },
  };
}, ({ map, [type]: features }) => ({ map, features }));

// Get some stuff from state then run _setFeaturesAction.
const setFeaturesSaga = function* ({ payload }) {
  const { map } = yield select(state.maps);
  return yield put({ map, ...payload });
};

const reducer = requestsReducer({
  actionType: getFeaturesAction,
  // stuff and things...

  operations: {
    [_setFeaturesAction]: {},
  }
}, baseReducer);

// User dispatches
function mapStateToProps(state) {
  return {
    data: state.data,
    operation: state.operations._setFeaturesAction
  };
}

function mapDispatchToProps(dispatch) {
  return {
    runOp: () => {
      dispatch(setFeaturesAction)
    }
  }
}

From a user perspective its a bit awkward to know the difference between _setFeaturesAction and setFeaturesAction to use the store. Do you have any suggestions to improve this pattern?

I had similar use case, at least I think they are similar, correct me if I am wrong. I had dynamic urls in multiple places requiring for example user id. It would be terrible always to inject such attr in every action. I solved it by onRequest interceptor, something like this:
import { mapRequest } from 'redux-saga-requests/lib/helpers';

const interpolatePlaceholders = (config, {  user }) => {
  if (config.url.includes('{user}')) {
    config = { ...config, url: config.url.replace('{user}', user) };
  }

  return config;
};

function* onRequest(request) {
  const user = yield select(userIdSelector);

  return mapRequest(request, config =>
    interpolatePlaceholders(config, {  user }),
  );
}

Then, I could have an action like:
const getUserBooks = () => ({
  type: 'GET_USER_BOOKS',
  request: {
    url: '{user}/books',
  }
});

Notice I don't need to pass user id to getUserBooks, it is solved in one place in onRequest interceptor.
Alternatively you could use redux-thunk to dispatch request action, as it has getState function ready to be called

That does seem like the same use case but I'm not sure I'm happy with the
approach as it seems a bit opaque. I suppose redux-thunk could be an
option but it also seems a bit strange to mix and match with saga. Then
again I'm not sure what the ideal solution would be.
When I was originally trying to solve this issue I went looking to see if
operations had a getType option or similar you could specify. Would
this be a reasonable alternative?
On Mon, Jun 10, 2019 at 4:01 PM Konrad Lisiczyński<EMAIL_ADDRESS>wrote:

I had similar use case, at least I think they are similar, correct me if I
am wrong. I had dynamic urls in multiple places requiring for example user
id. It would be terrible always to inject such attr in every action. I
solved it by onRequest interceptor, something like this:
import { mapRequest } from 'redux-saga-requests/lib/helpers';
const interpolatePlaceholders = (config, {  user }) => {
if (config.url.includes('{user}')) {
config = { ...config, url: config.url.replace('{user}', user) };
}
return config;
};
function* onRequest(request) {
const user = yield select(userIdSelector);
return mapRequest(request, config =>
interpolatePlaceholders(config, {  user }),
);
}
Then, I could have an action like:
const getUserBooks = () => ({
type: 'GET_USER_BOOKS',
request: {
url: '{user}/books',
}
});
Notice I don't need to pass user id to getUserBooks, it is solved in one
place in onRequest interceptor.
Alternatively you could use redux-thunk to dispatch request action, as it
has getState function ready to be called
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/klis87/redux-saga-requests/issues/250?email_source=notifications&email_token=AA2QQEHXO6HFFAVBMLQCNHTPZ2XIBA5CNFSM4HWTYKTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXLCBIA#issuecomment-500572320,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA2QQEGNO23EHCDC2M35S43PZ2XIBANCNFSM4HWTYKTA
.

I will take a look and think about it.
Regarding redux-thunk, I also initially thought some time ago that it is strange to mix it with saga, but actually imho thunk is a perfect way to inject data from state directly without using payload. BTW, there is a topic that mentions, that select in sagas and getState in thunk is evil, that all data should be passed as args to action creators. For me this is silly, because then React components need to subscribe to those data they should not even no about just to pass them back to Redux :D It just couples components with Redux for no reason.
Also, my solution onRequest may seem a but strange, but this could be as well implemented as callback style:
const getUserBooks = () => ({
  type: 'GET_USER_BOOKS',
  request: {
    url: ({ user }) => `${user}/books`,
  }
});

I saw you closed your PR, but issue is still open. Does it mean that you dont want this anymore? I just don't know whether I should get back to it once I have some time.

Closed the PR because I want to think about the problem some more. I'm going to try both your solutions this week. I'll close this off if I like it, otherwise you can toss it in the bucket :)

Closing, I will add some recipies before version 1 once working on docs. To sum up use either thunk or onRequest interceptor, it would be also possible to implement it on the driver level


V2.X

pull request for version 2 (subject to change)

merge should be done locally since v2 was started from scratch


Meeting order update

I think that it would be a good idea for consistency to display the meetings like they are displayed on https://ct.gdcc.io/ (Inverse chronological order).
As it is right now https://py.gdcc.io/ is using a chronological order which puts the most recent or incoming meeting at the end.

Ha, this reminds me of https://github.com/gdcc/ct.gdcc.io/commit/0ab6f5eedc9f2031b728fce01cfa5454b1928a0d 😜


Maha: Precourse , week 1

my fork of module repository

Learning Objectives

GitHub:

[x] 🥚 Creating Issues: You can create a new issue in a GitHub repository using an issue template. You can correctly use labels, milestones, and assignment to make your issue findable.
[x] 🥚 Searching Issues: You can find issues in a repository by label, author, and milestone.
[ ] 🥚 Project Boards: You can use issues on a GitHub project board to track your class assignments and help your classmates when they need it.

HYF Workflows:

[x] 🥚 Asking for Help: You can use the question and help-wanted discussion templates in your class repository to ask for help, and to help your classmates when they are blocked.
[x] 🥚 Check-Ins: You can use the check-in template to track your module learning objectives, and your weekly progress, and to post a retrospective at the end of the module.
[x] 🥚 Deliverables: You can create an issue for this module's deliverable and track your progress on the class project board.

Your Computer:

[x] 🥚 File System Management: You can create and organize a new folder in your personal computer for the materials you will study at HYF.

Visual Studio Code:

[x] 🥚 Install and manage extensions
[x] 🥚 Open a folder for editing
[x] 🥚 Create new files/folders inside of the folder
[ ] 🥚 Edit files and save changes

I feel a little distracted, and i spent a lot of time in installing softwares.

it takes a lot of time to set up your computer.  that's why you have a whole week for just that, and in the next two weeks you'll also get time to continue setting it up and learning to use the new softwares.

It is important to being patient.

😃

Hi @MahaLubbad it is natural to feel distracted with all the information, but it will slowly become all very clear.
Could you describe your process of installing ohmyzsh and what the error messages were in a new discussion here:
https://github.com/lab-brussels-1/home/discussions
Others have had issues with it as well, so maybe you can learn from each other.
We will discuss setting up SSH in class.


Update Nginx version to current stable [1.12.1]

Update nginx to the current stable version when installing via source.
This version fixes integer overflow in the range filter vulnerability (CVE-2017-7529).
Also update versions of echo-nginx-module and lua-nginx-module to fix failing specs.

Thanks


DUT server: random crashes in MarkAsDefunct

Problem
DUT firmware [Nordic] randomly crashes sometimes in MarkAsDefunct. Does not look platform specific and unfortunately cannot debug it at the moment. Two crashes attached.
Proposed Solution
Check what could cause the random crash.

@Damian-Nordic

TCCADMIN15UART.txt
anothercrash.txt

@bluebin14 Is this crashing inside MarkAsDefunct, or after MarkAsDefunct returns and we are doing the OnSessionHang notification?  It's not clear to me from the logged stacks which function we are actually crashing in....
That said, we are clearly not getting to the MoveToState call inside MarkAsDefunct, since that would log things that are not appearing in the log.  So we're in one of the other states, and it would be really good to figure out which one we're in...  @bluebin14 do you have a complete log for one of those crashes so we can look at previous state transition logs for the session involved, since we're not logging the state?

I do not have complete logs but it may have resulted from the controller exiting due to --timeout setting (i.e. without cleaning up) leaving the device in an undefined state then continuing with Sigma 1 with next chip-tool call, that caused the crash.

Any updates here @bluebin14 ? If you could try to repro it, that would be really helpful.

I did 2 things that currently seem to not produce the crash: reduce sleep interval to 300 ms and increase command timeout. After SVE2 I can debug it further.

Is it possible that this was basically the same issue as https://github.com/project-chip/connectedhomeip/issues/23093 and hence got fixed by https://github.com/project-chip/connectedhomeip/pull/23097 ?
@bluebin14

@bzbarsky-apple it is possibly related so closing it for now since it is not reproducible with current code.


feat(app): get appdocument(pdf) refactoring

Enhanced end point  /api/apps/{appId}/appImages/{documentId}  to support additional document type of pdf
Refs: CPLP-2268

@qxz2mqe please create and link the PR in the CD Repository for the config changes

@Phil91 PR for CD changes was created and merged. For your reference https://github.com/catenax-ng/tx-portal-cd/pull/42

@jjeroch Please Confirm because the existing end point also we were not filtering it based on  document status. If require this then we have to create a new endpoint in this case.

@jjeroch Please Confirm because the existing end point also we were not filtering it based on document status. If require this then we have to create a new endpoint in this case.

I did talk to @jjeroch and we agreed to return everything except INACTIVE documents (in this endpoint). I did add this filter to the query and businesslogic.


[stable/minio] Fix pod annotations format in statefulset

What this PR does / why we need it:
When value podAnnotations in values.yaml file is not empty then statefulset.yaml will not render template properly which leads to invalid yaml
Which issue this PR fixes
Special notes for your reviewer:
See how you use podAnnotations in deployment.yaml
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] DCO signed
[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] Title of the PR starts with chart name (e.g. [stable/mychartname])

/lgtm


BACKward move bug

I found backward move bug,
when I'm scrolling data-external-replace sections, for example:
[vertical slide 1]
slide 1,1
slide 1,2
slide 1,3
[vertical slide 2]
slide 2,1
slide 2,2
slide 2,3
backward move from 2,1 is 1,2 - not 1,3

I just failed trying to reproduce the issue you described. If the issue is still relevant - could you please upload an example to plunkr, jsfiddle or some alternative to that?

do you have enabled mouse scrolling?
there is screen captured video
https://drive.google.com/open?id=18JqkHOr021kHGgh5uWOK6y_QH4mhcaTV

Are you sure this bug is caused by the plugin? you can test this by temporarily commenting the plugin includes. In case the issue is related to this plugin, can you please provide any example code as mentioned above?

I'll share full video with codes :)

https://drive.google.com/open?id=1bGzJ2pj8fy2kU1ES9xQUCK1Mk_qhYoE9
there is example with HTML codes


Update 2.installation.md: corrected a typo

I corrected (what I believe to be) a typo in the installation instructions: nuxi in the bash command instead of nuxt: npx nuxi@latest init . I ran the command and it gave an error. The corrected command: npx nuxt@latest init  ran correctly.
I did not see this in the issue list.
🔗 Linked issue

📚 Description

please review my pull request. Thanks!

thank you! (pr was great!)
however, nuxi is a more lightweight command to run with npx - it’s just the cli, without any other nuxt dependencies
would you open an issue to track the problem you have running nuxi? would love to solve that for you 🙏


feat: support reading paymentTypeCode from JSON

It came up that TEL/WEB entry detail records have a "payment type code" field (size 1) that overlaps with the the DiscretionaryData field (size 2). This causes a bit of confusion because the JSON representation doesn't error when you provide paymentTypeCode but also doesn't populate DiscretionaryData.
This PR is an experiment to support paymentTypeCode only in the JSON level.
@atonks2 can I get your thoughts on this experiment?

Put another way, it sounds like DiscretionaryData can be used to contain either a single code, two distinct codes. In the case of WEB/TEL entries, the first position is used to hold the PaymentTypeCode.
This looks like it would give users the ability to include a paymentTypeCode field in their JSON requests even though that isn't a named field in an EntryDetail. I'm concerned this would be a hidden feature, or hidden behavior. I'm also curious about marshaling EntryDetail back into JSON. Is there a reason users can't just use the existing DiscretionaryData field as is, populating the first position with payment type code?

I agree about a hidden feature vs using the renamed field for TEL/WEB. I see both sides having a tradeoff and needing special callouts in the docs (which is done currently).

From a technical perspective, this looks good to me. My concerns are more about predictable behavior, and making the JSON equivalent in both directions. You've got much more experience than me with both ACH in general and this library, so I'm happy to leave that judgement call to you.

I don't think it's proper to introduce phantom values like this. An interesting idea, but not what we should do IMO. Feel free to comment/reply if you think this would be useful.


"it is not yet ready for general use" roadmap

Is there a plan what is needed to make it available from webstore?

I agree totally. This project needs a road map and some dates for target.
Severely.

Regards,
Chris Jones
On Sun, Jan 17, 2016 at 7:01 PM, anatoly techtonik<EMAIL_ADDRESS>
wrote:

Is there a plan what is needed to make it available from webstore?
—
Reply to this email directly or view it on GitHub
https://github.com/google/end-to-end/issues/362.

Thank you for the feedback and I agree that a clear roadmap would help improve the project. However unfortunately there is no roadmap nor date commitments that we have available to share, nor do I expect us to have one available in the immediate future. I'll close this issue, but please feel free to continue the discussion on our mailing list: https://groups.google.com/forum/#!forum/e2e-discuss

https://groups.google.com/d/msg/e2e-discuss/WuA5PQljtoQ/z1G2BnLHAwAJ


Add approve DAI asset to Lending pool provider

I faced this errors due to no approval for a lending pool.
"Fail with error 'SafeMath: subtraction overflow' "
Ref: https://kovan.etherscan.io/tx/0x25169bbad32aa94a14242b47c4e951cdac37dca7cedb6ca6c2cbdd377099fef3
AAVE state that:
Also note that since the owed amounts will be pulled from your contract, your contract must give allowance to the Pool to pull those funds to pay back the flash loan amount + premiums.
Ref: https://docs.aave.com/developers/guides/flash-loans#overview
After applied "approve", I can successfully run flashloan.
https://kovan.etherscan.io/tx/0x34a5c5f7e64747fdcb1b029ce4e36f901361ef4ebb5736acd31adba3112b8424

Hi Wwarodom, any idea how to resolve this issue-
    ERC20 dai = ERC20(_asset);
    dai.approve(addressesProvider.getLendingPool(),<PHONE_NUMBER>00000000000000 );

Upon executing the flashloan, I got this this error as shown below,
contracts/flashloan.sol:48:27: DeclarationError: Undeclared identifier. Did you mean "assert"?
ERC20 dai = ERC20(_asset);
^----^

ERC20 is included in FlashLoanReceiverBase.sol.
"_asset" is the local variable which is declared here:

function flashloan(address _asset) public onlyOwner

Thanks Wwarodom for the prompt reply. Yes, I have all these in the contract, yet upon executing I still received this error message. Am I missing out anything? or would you mind vetting the contract and advise me accordingly. Appreciate your assistance. I am still kinda newbie to all these.
contracts/flashloan.sol:48:27: DeclarationError: Undeclared identifier. Did you mean "assert"?
ERC20 dai = ERC20(_asset);
^----^
//Use the lisence here: MIT & Apachai standart
//@dev/Developer = Pavan Ananth Sharma
<EMAIL_ADDRESS>= Kovan Test Network
pragma solidity ^0.6.6;
import "./FlashLoanReceiverBase.sol";
import "./ILendingPoolAddressesProvider.sol";
import "./ILendingPool.sol";
contract FlashloanV1 is FlashLoanReceiverBaseV1 {
string _Real_Owner = "kenny wong" ;

function Owner_Of_This_Contract() public view returns(string memory){
    return _Real_Owner;
}

constructor(address _addressProvider) FlashLoanReceiverBaseV1(_addressProvider) public{}

/**
Flash loan<PHONE_NUMBER>000000000 wei (1 ether) worth of _asset
*/
function flashloan(address _asset) public onlyOwner {
bytes memory data = "";
uint amount = 1 ether; //this is the loan amount which will be seen or converted to DAI which means if you enter in 100 here you will be taking a loan of 100 DAI and so on.
//basically we can say that this ebtered amount is converted to wei which is a small decimal of ETH and then it is placed in to the mem pool for the mining of the DAI
    ILendingPoolV1 lendingPool = ILendingPoolV1(addressesProvider.getLendingPool());
    lendingPool.flashLoan(address(this), _asset, amount, data);
}

/**

This function is called after your contract has received the flash loaned amount
*/
function executeOperation(
address _reserve,
uint256 _amount,
uint256 _fee,
bytes calldata _params
)
external
override
{
require(_amount <= getBalanceInternal(address(this), _reserve), "Invalid balance, was the flashLoan successful?");
//
// Your logic goes here.
// !! Ensure that this contract has enough of _reserve funds to payback the _fee !!
//
ERC20 dai = ERC20 (_asset);
dai.approve(addressesProvider.getLendingPool(),<PHONE_NUMBER>00000000000000 );
    uint totalDebt = _amount.add(_fee);
    transferFundsBackToPoolInternal(_reserve, totalDebt);
}

}

Opp, you have to move
ERC20 dai = ERC20 (_asset);
dai.approve(addressesProvider.getLendingPool(),<PHONE_NUMBER>00000000000000 );

to flashloan() function
you can check my project with hardhat project here:
https://github.com/wwarodom/flashloan_aave

Thanks! I will do test run later. By the way can it be done on Ropsten Testnet? or it has to be Kovan?

I haven't tested it yet. If AAVE deploys LPs on Ropsten, it can work.
However, it depends on LP deploying address and liquidity pool, DAI faucet, DAI address etc.

Noted. In addition, may I check with you, do you develop any code for flash loan arbitrage bot?

Noted. In addition, may I check with you, do you develop any code for flash loan arbitrage bot?

same i needed for arbitrage functionality  is there anyone know?

You may want to check this out and let me know if it works for you - https://github.com/ChengGong0602/flashloan-arbitrage-bot/blob/main/FlashArbitrageTrader.sol

can you guide me it is working on test network can you give me demo please?
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Mon, Mar 21, 2022 at 5:16 AM kenny8333 @.***> wrote:

You may want to check this out and let me know if it works for you -
https://github.com/ChengGong0602/flashloan-arbitrage-bot/blob/main/FlashArbitrageTrader.sol
—
Reply to this email directly, view it on GitHub
https://github.com/PavanAnanthSharma/Aave-FlashLoan-using-solidity/pull/3#issuecomment-1073381595,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIY6KUVINANUEA5HYYFZHRLVA65WZANCNFSM5QFBTXYA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***
.com>

not found https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/math/SafeMath.sol
it is giving the error
On Mon, Mar 21, 2022 at 10:01 PM Faisal Motan @.***>
wrote:

can you guide me it is working on test network can you give me demo please?
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
<#m_-3843936947816147814_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Mon, Mar 21, 2022 at 5:16 AM kenny8333 @.***>
wrote:

You may want to check this out and let me know if it works for you -
https://github.com/ChengGong0602/flashloan-arbitrage-bot/blob/main/FlashArbitrageTrader.sol
—
Reply to this email directly, view it on GitHub
https://github.com/PavanAnanthSharma/Aave-FlashLoan-using-solidity/pull/3#issuecomment-1073381595,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIY6KUVINANUEA5HYYFZHRLVA65WZANCNFSM5QFBTXYA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
<PavanAnanthSharma/Aave-FlashLoan-using-solidity/pull/3/c1073381595@
github.com>

oi , dá para fazer a estratégia em outra network diferente da Kovan test net ?
No meu caso seria em avax . Penso que me fiz entender com a minha pergunta 😂


Refused to execute script from '{baseUrl}/admin/frontend/assets/components.bundle.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.

Describe the bug
I've noticed that after adding authentication, I'm seeing a bug in the console:
"Refused to execute script from '{baseUrl}/admin/frontend/assets/components.bundle.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled."
I also see:
app.bundle.js:15193 Uncaught TypeError: Cannot read properties of undefined (reading 'length')
    at RecordsTable (frontend/assets/app.bundle.js:15193:17)
    at renderWithHooks (frontend/assets/global.bundle.js:38142:30)
    at updateFunctionComponent (frontend/assets/global.bundle.js:40373:32)
    at beginWork (frontend/assets/global.bundle.js:41949:28)
    at HTMLUnknownElement.callCallback (frontend/assets/global.bundle.js:23533:26)
    at Object.invokeGuardedCallbackDev (frontend/assets/global.bundle.js:23582:28)
    at invokeGuardedCallback (frontend/assets/global.bundle.js:23637:43)
    at beginWork$1 (frontend/assets/global.bundle.js:46542:19)
    at performUnitOfWork (frontend/assets/global.bundle.js:45496:24)
    at workLoopSync (frontend/assets/global.bundle.js:45469:34)

global.bundle.js:42866 The above error occurred in the <RecordsTable> component:
    in RecordsTable (created by List)
    in section (created by styled.section)
    in styled.section (created by List)
    in List (created by BaseActionComponent)
    in ErrorBoundary$1 (created by BaseActionComponent)
    in BaseActionComponent (created by ResourceAction)
    in section (created by styled.section)
    in styled.section (created by ResourceAction)
    in ResourceAction (created by ConnectFunction)
    in ConnectFunction (created by Context.Consumer)
    in Route (created by App)
    in Switch (created by App)
    in section (created by styled.section)
    in styled.section (created by App)
    in section (created by styled.section)
    in styled.section (created by App)
    in App
    in Router (created by BrowserRouter)
    in BrowserRouter
    in Unknown
    in Provider

React will try to recreate this component tree from scratch using the error boundary you provided, ErrorBoundary$1.

It's possible the issue with the bundle is a red herring, but I suspect a component from that bundle is unable to be imported.
Installed libraries and their versions
  "@adminjs/express": "^4.1.0",
  "@adminjs/nestjs": "^4.0.1",
  "@adminjs/typeorm": "^2.0.3",
  "adminjs": "^5.8.1",
  "express-formidable": "^1.2.0",
  "express-session": "^1.17.2",

To Reproduce
Steps to reproduce the behavior:

Log in
Go to a resource page
Get logged out
See error

Expected behavior
Expect to be able to log in and view resource
Screenshots
If applicable, add screenshots to help explain your problem.
AdminJSOptions with schema
Paste your AdminJS config with database schema if it could be related to the issue
Desktop (please complete the following information if relevant):

OS: macOS
Browser: Chrome
Version: 100

Smartphone (please complete the following information if relevant):

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.

Is your components.bundle.js being generated?

How are these files typically generated in production?