S3 presigned urls expire before requested ExpireIn parameter

Describe the bug
Presigned URLs expire either when your credentials do or when ExpiresIn passes. However, it's impossible via the public API to refresh credentials such that their expiry is greater than or equal to a passed in ExpiresIn value.
Steps to reproduce
I've included code here which reproduces the issue: https://gist.github.com/DrewBarclay/98535af9a6a444d0c4b317e344f88e55
When ran on an EC2 instance with appropriate signing permissions, it shows that presigned URLs will all expire in a batch at the end when the instance's temporary credentials expire.
Expected behavior
I expect botocore to, if I try to sign a URL with an expiry past when temporary credentials expire, to refresh the credentials before signing. So, if I ask for a presigned URL lasting 3 hours, and if there's 1 hour left on my current credentials, I expect botocore to refresh to 6 hours and then sign so it can actually create an URL which lasts as long as I requested.
If that would be a lot of effort, I'd hope for at least a public and stable API for me to manually check the expiry time of my current credentials (if applicable) and for me to handle refreshing the boto3 credentials manually.
Another possible mitigation would be to at least generate a warning if you try to generate a presigned URL that botocore knows will expire before the requested expiry.
I also think the docs should at least be modified to clarify this corner case, as it's easy to misunderstand and think all presigned URLs will last 6 hours when generated on an EC2 instance. The current wording at each of these pages does not mention anything about this issue:
https://boto3.amazonaws.com/v1/documentation/api/latest/guide/s3-presigned-urls.html
https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/s3.html#S3.Client.generate_presigned_url
The actual AWS page (https://docs.aws.amazon.com/AmazonS3/latest/userguide/ShareObjectPreSignedURL.html) on this is also not clear enough, in my opinion, because while it says credentials last 'up to' 6 hours, it should explicitly clarify that because instance credentials are not refreshed until 10-15 minutes before expiry in some AWS libraries, presigned url expiry may be as low as 10 minutes, regardless of what you request.

Hi @DrewBarclay thanks for the feedback. I think this premium support article gives a more thorough explanation: https://aws.amazon.com/premiumsupport/knowledge-center/presigned-url-s3-bucket-expiration/
I’m not sure if any change in the behavior would be considered but maybe the documentation could be improved for this.

Thanks @tim-finnigan - documentation being improved in the Python docs to help avoid this would be very appreciated.
I do feel the API could be very improved here, though, or perhaps some kind of additional presigning URL module be made on top of this one.
It's not very useful to have presigned URLs which last 10 minutes to 6 hours - typically you have to design for the worst case, so essentially you cannot safely build any system which relies on presigned URLs lasting longer than 10 minutes when generated on an EC2 instance. There's no real point to allowing them to be generated for 6 hours or whatever, it just lets you shoot yourself in the foot.
You can get around this by building a much more complex system with assumed user roles and all that, but as far as I can tell there's no clean example code to work off of that properly handles auto-refreshing - if I'm missing anything already made for that, please correct me though!


fix: Correctly handle arrays in terraform_docs.sh

@antonbabenko A serious regression has been introduced in v1.34.0 in the process of factoring out getopt. Starting with that version, terraform_docs pre-commit hook would only process one terraform module, ignoring any other modules that are part of the commit.
This PR attempts to fix the regression. I have tested it on Ubuntu Focal (GNU bash, version 5.0.17), but I would appreciate if anyone could also test it on Bash 4.x and on MacOS.
Please note that args are still passed around in the script as a single argument (just as it was), and I have also successfully verified the correct operation with multiple --args= in the pre-commit YAML configuration (fixed earlier in #98).
Side note: other hooks may also be affected in a similar way, but I haven't tested them because we are not using them.

Thanks a lot, @sergei-ivanov !
I have verified it by running on terraform-aws-security-group on Mac and it works as expected.
@robinbowes Could you please verify the code and maybe update other hooks also?

v1.38.0 has been just released.

@robinbowes Could you please verify the code and maybe update other hooks also?

Looks good to me. I shall investigate the other hooks.

v1.38.0 has been just released.

Did you push it? I don't see it on github?

Pushed now.

@antonbabenko https://github.com/antonbabenko/pre-commit-terraform/pull/142 - needs regression testing before merging, I have requested that @sergei-ivanov takes a look.


Customizable flash settings

As requested by @alarkbentley on behalf of an OpenCities Planner user, the flash behavior can now be customized for a Viewport.
The duration and maximum intensity can be configured. Lit geometry can also be forced to flash with the hilite color like unlit geometry does, instead of brightening.
Viewport.setFlashed used to take a duration specified by the caller, which was weird and was always hard-coded to 0.25 by each caller (there are only two). Now that duration is optional and ignored in favor of FlashSettings.duration.

@markschlosseratbentley @bbastings please review.

Just curious what settings OpenCities Planner will use...should we consider changing our default flash?

Just curious what settings OpenCities Planner will use...should we consider changing our default flash?

They want lit geometry to flash with the hilite color, like it would in an unlit view, but with a ratio < 1 so some of the element color is preserved.
I don't think we should change our default - using hilite color for flash doesn't work well when the element color is approximately the same as the hilite color.


Added file_monitoring.py

Hi, I have added file_monitoring.py which is a python script to continuously monitor any changes to a given file or directory at a given frequency in windows os . It also records the changes to a log.txt file

Great work! @bvks2020sameer


Added a new organisation to line 100

https://www.gov.uk/legalisation-document-checker/y/educational-certificate-uk
Line 100 - added a new organisation to Educational certificate list
Name of organisation: Accreditation Service for International Colleges
https://trello.com/c/ls0eGFwz/434-update-to-check-if-documents-can-be-legalised
https://govuk.zendesk.com/agent/tickets/1415134

Update no longer needed on the page. Cancelling this pull request.


minSdkVersion is not the same among the modules

@dmfs Is this on purpose?
calendarpal 14
contactspal 11
contentpal 11
(testing module will have 11)

ContentPal and ContactsPal can work from SDK level 11+, but CalendarPal doesn't work with SDK Level <14 because the CalendarContract is not public in earlier SDK versions.
So yes, this is on purpose.

I see, thanks.


Driver/znb dev

Fixes #issuenumber.
Changes proposed in this pull request:

@mention one core developer

replaced by #834


Multiple clients - multiple drones communicate through nodejs server

Hello,
I want to make a web application which manages AR drones. I want to have multiple clients which can make an account and get data from their drones in browser. Is this posible? Can I identify each drone unique or can i make an array of ardrone clients  ( var client = arDrone.createClient(); ) ?
I tried to put ar-drone files on client side( with browserify) but it ended with "dgram.createSocket is not a function" .
I need some opinions. Thank you !!

Hi. In theory you can have an application that talks to multiple drones. That being said, they will all have to be on the same network in order for the application to be able to talk to them. Depending on your use cases for the application, that might be a problem.
You won't be able to use this library on the client side. The error message you got is because Browsers don't allow JS to do UDP networking, which is needed for talking to AR Drones.

I see.Thanks. Maybe I'll make something like : clients have the whole app (server(+db) + client) on their PCs ( like local server). Sounds it weird ?


Weekly 7-day Calendar; integration myBB etc

How do i display the current weekly 7 day calendar or any period? as a slider on top?
rather than have the usual, 30 day box?

#13

No need to refer to #13, a feature was added in the spring that allows you to do this. See the lengthOfTime option in the Usage section of the docs.
$('#my-calendar').clndr({
  lengthOfTime: {
    days: 7,
    interval: 7
  }
});

Now in your template you will have a days array of length 7 and all clndr controls (next, previous, today, next year, previous year, etc) will work as usual.


Add Oracle Binary download step if the RPM isn't present

Since no more click is needed, automatic download of the binary RPM file could be added to the buildContainerImage.sh script.

Unfortunately, that is not a solution that will work forever, as older RPM installer files are being removed from Oracle.
For example, there is no 11g R2 RPM file available anymore (despite it not being click-through free).
However, if the checksum calculation fails, either because the file is not present or the checksum is invalid, buildContainerImage.sh could prompt the user whether an automatic download should be attempted. If that fails, it would still be up to the user to provide the installer RPM file.

I needed to build the image for myself and these are the steps I used...

From https://docs.oracle.com/en/database/oracle/oracle-database/18/xeinl/procedure-installing-oracle-database-xe.html I found https://docs.oracle.com/en/database/oracle/oracle-database/18/xeinl/procedure-installing-oracle-database-xe.html
curl -L https://download.oracle.com/otn-pub/otn_software/db-express/oracle-database-xe-21c-1.0-1.ol8.x86_64.rpm -O to grab the rpm
I got an error about buildah and I was running Ubuntu 20.04 - I found https://gist.github.com/sebastianwebber/2c1e9c7df97e05479f22a0d13c00aeca from Google which directed me to https://fabianlee.org/2022/08/02/buildah-installing-buildah-and-podman-on-ubuntu-20-04/ to get buildah
I had to add a trusted CA since I'm working inside a corporate network, so I added a couple lines:
COPY Issuing-CA.crt /etc/pki/ca-trust/source/anchors/
RUN update-ca-trust

Currently running it and seems to be taking a while, I'll update this when it is done...

So it ran successfully - it was WSL and using too much memory; I added a .wslconfig file to limit memory and avoid going to swap which eliminated the errors.
Still not accessing EM manager tho, even tho I did add a SID_LIST_listener

Hey @jcrben, which flavor did you build? You need to have SHARED_SERVERS > 0 if you want access to the DB Console.

@gvenzl  I ended up having to execute the command suggested at https://github.com/oracle/docker-images/issues/1419#issuecomment-689305485 to see the EM
docker exec -it racnode1 /bin/bash
su - oracle
setfacl -R -m u:grid:rwx <XDB wallet location>
eg. setfacl -R -m u:grid:rwx /u01/app/oracle/product/19.3.0/dbhome_1/admin/ORCLCDB/xdb_wallet

I think it might have been slightly different from that - I have access to the Oracle Support Center via my employer and reviewed doc ID 2680248.1 on Oracle support
I also mentioned that over at https://github.com/gvenzl/oci-oracle-xe/issues/166

Cool, thanks a lot for sharing, @jcrben!

I'm closing this PR as it seems no longer relevant.
Downloading the RPM before the build may adds a nice little touch but ultimately Oracle decides for how long and where to publish these RPMs to, making this proposed mechanism unreliable.


Missing C++ API to set IP_TOS (DSCP) on a gRPC server stream

I need a C++ API to set IP_TOS (DSCP) on gRPC server stream. How can this be done? I could not find a C++ API for this.
There are many use cases where marking the IP frames with DSCP is important. Notably, googles own gNMI spec is one of them requiring the gRPC stream to have DSCP marking!

I think this may be achieved by implementing a grpc_socket_mutator and set the appropriate option in the mutate callback.
@apolcyn Could you please confirm?

We acknowledge this to be a valid feature request but since no one has come forward to implement this, we are going to close it for now while maintaining the label/Help wanted to indicate that this can be picked up as future work

@jtattermusch Hi! We need an API like this and I will look into how it can be implemented, to prepare a PR. Since this issue was closed more then a year ago I would like to first check if the conditions have changed. Do you know if there are any new thoughts in this area?


Add new exercise: zebra-puzzle

problem specification | description | canonical data
You may find it helpful to follow this checklist from the CONTRIBUTING.md resource.

Hi! Can I try to implement this?

Sure!

@SleeplessByte Where did this issue originate from, did you just decide JS should have this problem and therefore create it?  I was looking for a similar issue in Ruby but see nothing...

Yep. I manually created an issue per missing exercise.


Remove circe-streaming module

circe-streaming was extracted.
I have put it here for now: https://github.com/aeons/circe-streaming
I just did git filter-branch with a subdirectory, so commits touching circe-streaming in other files, like build.sbt are not captured.

The "missing" parts were basically copied from circe-fs2

Excellent, thanks, @aeons! Will merge when green, then #773 should pass and we can publish 0.9.0-M2. I'll follow up on getting the new repo moved to the circe org after all the other dust settles.

(And right, I've never bothered with a better way to do this than filter-branching with a subdirectory, so your approach looks reasonable to me.)

Codecov Report

Merging #774 into master will decrease coverage by 0.09%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master     #774     +/-   ##
=========================================
- Coverage   86.55%   86.45%   -0.1%
=========================================
  Files          73       71      -2
  Lines        2305     2282     -23
  Branches       93       90      -3
=========================================
- Hits         1995     1973     -22
+ Misses        310      309      -1

Impacted Files
Coverage Δ

...o/circe/generic/util/macros/DerivationMacros.scala
76.47% <0%> (-9.81%)
:arrow_down:

.../core/shared/src/main/scala/io/circe/Decoder.scala
89.89% <0%> (-0.34%)
:arrow_down:

...re/shared/src/main/scala/io/circe/JsonNumber.scala
97.02% <0%> (+0.99%)
:arrow_up:

...re/shared/src/main/scala/io/circe/KeyDecoder.scala
100% <0%> (+2.7%)
:arrow_up:

...rc/main/scala/io/circe/shapes/SizedInstances.scala
92.85% <0%> (+14.28%)
:arrow_up:

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 4f10855...903b4e2. Read the comment docs.

The failure for that one job looked spurious so I restarted it.


Update completion-list help string

Follow on to #8045 to make the completion-list tool use the CaseIterable support in swift-argument-parser to automatically enumerate the options.
list-snippets was missing from the list, and is now added.

cc @cmcgee1024

@swift-ci test


fix(docs): demo's broken link

Fix of a link that goes to the theme's demo.
Before: https://mattgraham.github.com/midnight
After: https://madebygraham.com/midnight

I now wonder how long thats been like that. Thanks!


Use VimTeXs lua parser?

I'm curious if it may make more sense to utilize the new VimTeX lua parser for bib files directly. It has now become quite fast. And after parsing a large file it can be kept in memory.
Thus, even if there would be a delay while parsing for the completion, the delay would be 1) very small, and 2) should only appear once for each session.
I believe this would simplify the cmp-vimtex plugin. Simpler is often better. :)

Thus, even if there would be a delay while parsing for the completion, the delay would be 1) very small, and 2) should only appear once for each session.

Whilst this is true, I'd like to avoid the slightest hint of freezing. The benchmark result was about half a second which, while an excellent time for the parsed-file size, is, I feel, already too much.
The parser is not excessively big and, apart from applying your recent enhancements, I think it's safe to say that it won't have to be altered in the foreseeable future (since it's practically complete). Whilst it would be simpler to use Vimtex's parser, it's a compromise I'd like to avoid.

Thus, even if there would be a delay while parsing for the completion, the delay would be 1) very small, and 2) should only appear once for each session.

Whilst this is true, I'd like to avoid the slightest hint of freezing. The benchmark result was about half a second which, while an excellent time for the parsed-file size, is, I feel, already too much.

That's fair; cmp-vimtex is your plugin and you are perfectly free to develop it as you see fit. In that case, I would strongly suggest that you rewrite your parser similar to the updated VimTeX parser. There are two reasons:

I found and fixed several bugs(!).
My update has a performance improvement of about 1.5-2.

@lervag Sorry for coming back to this issue after more than a month. I still haven't gotten around to making all the changes to the parser, as I haven't found the time.

I found and fixed several bugs(!).

By chance, do you remember what problems this bugs caused? I'm not noticing much, on my part.

@lervag Sorry for coming back to this issue after more than a month. I still haven't gotten around to making all the changes to the parser, as I haven't found the time.

No problem!

I found and fixed several bugs(!).

By chance, do you remember what problems this bugs caused? I'm not noticing much, on my part.

No, sorry. I don't think it was any major bug, e.g. nothing that was catched by the existing test cases. And since I catched them while implementing the Lua version I forgot to create new test cases.
I still think it would not be too much work for you to update your parser based on my updates, and I think it should be both faster and slightly less buggy.

On a separate note, I may have found the reason why you weren't able to display correctly the bibliographic information in the menu. Check out this issue and, especially, the pull request I've linked at the bottom.

I don't use lspkind.nvim, but perhaps I use something else that does something similar? Not sure. Things work well enough for me right now, though.

I still think it would not be too much work for you to update your parser based on my updates, and I think it should be both faster and slightly less buggy.

Then I'll start to work on it.

I don't use lspkind.nvim, but perhaps I use something else that does something similar? Not sure. Things work well enough for me right now, though.

Good to hear!
I've implemented the bibliographic databases search functionality in the database_search branch. When a cite completion item is selected, by calling the search_menu function, a menu will appear to select a search engine.
    vim.keymap.set("i", "<C-s>", function() require('cmp_vimtex.search').search_menu() end)

If you have time and would like to try it, let me know if you have any suggestions.
As soon as I find the time, I'll also write up the tutorial.

@lervag I've also written the tutorial.
Since @ejmastnak said he would wait for a tutorial in an old thread, I'll point out that the search functionality has been implemented on the database_search branch (it will be merged into masters in the future).
@benbrastmckie might be interested too.
All the plugin functionality has been thoroughly explained in the tutorial linked above. So, you have the time to check it out, I'd be glad to accept suggestions; both on new features, and the state of the currently available ones.

The search feature is quite nice, thanks! The tutorial looks good as well. Well done!
I understand it is a nontrivial amount of work to update the parser code as per the original comment in this thread. However, I've noticed that your parser has a bug that I've fixed that you can find quite easily reproduced. I'm opening an issue for that now - but I think the best fix for that would be to update the parser as requested here.


zklogin: always use PublicKey to derive SuiAddress

Description
Describe the changes or additions included in this PR.
Test Plan
How did you test the new or updated feature?

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

To confirm: padded is the legacy way and unpadded is the accepted way?

mapping.insert(SuiAddress::try_from_padded(&z.inputs)?, sig);

yes

Are we ever going to disable verify_legacy_zklogin_address? if not, should we assume from now on that it's true and simplify the authentication code (since we already updated all validators with verify_legacy_zklogin_address=true)

iiuc protocol config cannot be removed or deprecated because of tx replay.


dead links in the documents

Are you aware that all links in the top two sections of the document are dead?

Yes I saw it recently.  The html and css renders and links fine in the browser locally - not sure what’s up...


Error when using SoftDTW

Hi,
Thank you for releasing the code. I'm having trouble using it though. When using the simple l2_distance I get the following error

And when changing the dist_func for l2_exact I get another error :

Any idea why ?
Pytorch 1.8.2+cu111
numba 0.56.4

Hi,
I am facing a same issue. Had you resolved it. Thanks.


Emoji reactions in accountability station

Is your feature request related to a problem? Please describe.
When people write a message in #accountability-station, he no longer reacts with a random encouraging emoji, I'd love for this feature to return!
Describe the solution you'd like
I want Horace to react with emojis to all tasks containing a sort of checkmark in the accountability channel, to help encourage people to finish more tasks.
Describe alternatives you've considered
No alternatives.
Additional context

Will tackle this one next, but if anyone gets to it before me, some ideas:
✅ or :yes2: if it contains one of the checkmark effects
💯 👍 🔥 and 2 or 3 others selected at random for completed tasks
🎏 Corresponding flags if a language is mentioned, common ones are french, spanish, italian (from what I've seen)
🍅 If it contains 'pom'

Forgot this was a separate issue- just wanted to confirm that I'm on it!
:rocket:
Le ven. 18 oct. 2019 à 01:45, Daniel Moesgaard Andersen <
<EMAIL_ADDRESS>a écrit :

Assigned #26 https://github.com/Knights-Of-Academia/horace/issues/26 to
@Dendrobyte https://github.com/Dendrobyte.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/Knights-Of-Academia/horace/issues/26?email_source=notifications&email_token=ADATWBRSKD2ITR43FF5AWMLQPFEQXA5CNFSM4I62MAKKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOUJLN35Y#event-2723601911,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADATWBT63QDKOZX6LVGC4DTQPFEQXANCNFSM4I62MAKA
.

More recs on random reacts:
🙌 👏 👌 💪 :1000: :muscle_reverse: :LETSGO:


"Unknown error occurred"

I installed this on my HAOS install via HACS, and when I "ADD INTEGRATION" and choose NAD, and select my serial port and "SUBMIT", it just says "Unknown error occurred".
I tried every serial port option, just in case my USB->RS232 breakout box was mislabeled.
I've got a T747, and I also tried connecting to my T535, with identical results.  I looked in all their on-screen menus and didn't see anything related to RS232 control which needed enabling.
On the HA page, Settings -> Devices & services -> HACS -> 2 services -> NAD page, under Logbook, it says "No logbook events found".  That's the only logging/NAD-related page I've found.
I'm new to HA -- how does one troubleshoot this?  Thanks!

I connected my USB->RS232 breakout to my Linux workstation (stock Debian, not HAOS), and downloaded the joopert/nad_receiver Python library.  I tried connecting that way, and it works:
>>> from nad_receiver import *
>>> r = NADReceiver("/dev/ttyUSB0")
>>> r.main_volume('?')
-27.0
>>> r.main_volume('=', -24)
-24.0

(Pretty cool!)  So the hardware, cables, and low-level library all seem to be working.  The issue must be in HA, HAOS, the integration, or my config (user error).

Hi! I developed this integration for my T755 and also use it for a T757, I have not tested it with other devices.
To give me a better understanding what's going on could you enable debugging for the NAD integration, try adding the integration again and report back to me the logging.
You can go to http://homeassistant.local:8123/config/integrations/integration/nad and click Enable debug logging to enable logging

Sure, I’ll do that when I get the chance.
BTW, while power works fine with nad_receiver, mute and some other features have issues with that underlying library, so depending on what exactly this integration does on startup, that could be related:
joopert/nad_receiver#60
(I hope I’m remembering the correct syntax for cross-repo bug reports!)

You can go to http://homeassistant.local:8123/config/integrations/integration/nad and click Enable debug logging to enable logging

I don't see any "Enable debug logging" on that page.  Where exactly should I look?

Maybe you need to enable Advanced mode in your user profile

I enabled Advanced mode (and even logged out and logged in again), but no change here.  Possibly relevant: "Enable debug logging" in the same relative place was already visible for "HACS" before making this change.
Anyway, this is getting off-track for a bug report, and I'm clearly out of my depths with HA in general.  I'll find the HA chat/forums and see if I can get some remedial help there.

Ok, so maybe the debug option is only there when you have a device added, which you don't because adding your device fails.
You can always add debugging to your configuration.yaml:
logger:
  default: info
  logs:
    custom_components.nad: debug
    nad_receiver: debug

OK, I added that to my configuration.yaml and rebooted.  When I try to add my device in the NAD integration page and click "Submit", I see this item in the main logs:
Traceback (most recent call last):
  File "/config/custom_components/nad/config_flow.py", line 194, in validate_input_setup_serial
    model = self.exec_command("Main.Model", "?")
            ^^^^^^^^^^^^^^^^^
AttributeError: 'NADReceiverConfigFlow' object has no attribute 'exec_command'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 477, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 559, in _handle
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 83, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 85, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware
    response = await handler(request)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 81, in with_admin
    return await func(self, request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 222, in post
    return await super().post(request, flow_id)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 74, in wrapper
    return await method(view, request, data, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 122, in post
    result = await self._flow_mgr.async_configure(flow_id, data)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 370, in async_configure
    result = await self._async_configure(flow_id, user_input)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 417, in _async_configure
    result = await self._async_handle_step(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 520, in _async_handle_step
    result: _FlowResultT = await getattr(flow, method)(user_input)
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/nad/config_flow.py", line 120, in async_step_setup_serial
    title, data, options = await self.validate_input_setup_serial(
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/nad/config_flow.py", line 195, in validate_input_setup_serial
    except (serial.SerialException, CommandNotSupportedError):
                                    ^^^^^^^^^^^^^^^^^^^^^^^^
NameError: name 'CommandNotSupportedError' is not defined

I need to wait for a new "release" (after 0.0.2) to get this on HACS, right?
The exec_command issue still needs to be fixed, too, and it's less obvious to me how to fix that.  Suggestions welcome.


Update INSTALL # Add Manual building to gst-plugin

Clarified purpose of option "make -j #"
Added manual building of gst-plugin because it wasn't getting build with kaldi's Makefile
cd directly to "src" in gst-kaldi-nnet2-online, and ready to build
Added dependency libjansson-dev

You're brave to try building this from source, although I appreciate the updates :)
P.S. I just added an archive to the silvius website, you can download a compiled version here, you can also look around to see how it was set up in this case: http://voxhub.io/static/archive/silvius-server.tar.gz


Experiment/wallet rpc method migration 40026600

PR Checklist
Please check if this PR show the following integrations:

[ ] List addresses
[ ] List transactions
[x] Display balances
[x] Save address alias(label)

Note: following still in progress.

Filter transactions (in progress)
PDF download address keys (in progess, investigating the blank page issue)

I think this warning message should be disappeared after clicking cross button. Could you please check this?

Fixed.


proto_sync can fail creating diff

Not sure exactly the cause but it seems proto_sync is failing creating a diff

INFO: Streaming build results to: https://source.cloud.google.com/results/invocations/fc4663a5-dc44-4373-a52c-954ca0a9f9ab
Traceback (most recent call last):
  File "/build/bazel_root/base/execroot/envoy/bazel-out/k8-fastbuild/bin/tools/proto_format/proto_sync.runfiles/envoy/tools/proto_format/proto_sync.py", line 149, in <module>
    sync(
  File "/build/bazel_root/base/execroot/envoy/bazel-out/k8-fastbuild/bin/tools/proto_format/proto_sync.runfiles/envoy/tools/proto_format/proto_sync.py", line 100, in sync
    _diff += git.diff(
  File "/build/bazel_root/base/execroot/envoy/bazel-out/k8-fastbuild/bin/tools/proto_format/proto_sync.runfiles/envoy/tools/proto_format/proto_sync.py", line 45, in diff
    fhash = self.string_hash(t1)
  File "/build/bazel_root/base/execroot/envoy/bazel-out/k8-fastbuild/bin/tools/proto_format/proto_sync.runfiles/envoy/tools/proto_format/proto_sync.py", line 42, in string_hash
    return self.blob_hash(io.BytesIO(text.encode("utf-8")), len(text))
  File "/build/bazel_root/base/execroot/envoy/bazel-out/k8-fastbuild/bin/tools/proto_format/proto_sync.runfiles/envoy/tools/proto_format/proto_sync.py", line 38, in blob_hash
    raise ValueError('%s: expected %u bytes, found %u bytes' % (stream.name, size, nread))
AttributeError: '_io.BytesIO' object has no attribute 'name'
Format check failed, try apply following patch to fix:

there have been a lot of changes recently to related code so im guessing this should be fairly easy to resolve

https://dev.azure.com/cncf/envoy/_build/results?buildId=135983&view=logs&j=c95d62a5-6bb9-58f0-2a02-7575fd482a15&t=cbf2fcae-fb78-5fe6-095d-49113b477432&l=70

Thank you @phlax for investigating this!
I tried to run proto sync under different scenarios:

It worked on the main branch without any changes.
It did not work on my PR with changed proto.
It also did not work on my PR after I reverted all proto changes. Not sure whether there are some issues in my PR though.
When I removed the output of stream.name and ran the tool against my PR, it said that the bytes did not match, has 4 bytes differences IIRC.

It also did not work on my PR after I reverted all proto changes. Not sure whether there are some issues in my PR though.

iiuc the reason for this, you should either do ...
export BAZEL_VOLATILE_DIRTY=1

or make a commit
the test checks for changes in your repo, and this flag makes it at least more reactive if not totally reactive to every change

hmm, actually that is set in the tools/proto_format/proto_format.sh so maybe i dont uc

ill test against your PR/commit and see if i can figure out what is going wrong


Terraform should tag resources

All three terraform modules should tag resources with an 'owner' tag based either on their username/iam name, or based on something that can be configured.
We do this for AWS today: https://github.com/redpanda-data/deployment-automation/blob/main/aws/cluster.tf#L14 but not for Azure or GCP.

https://github.com/redpanda-data/deployment-automation/pull/127
added support for custom tagging for gcp here, I guess I could also add in an object merge or something to include the id of the creator alongside any custom tags.

Done


[13pt] Test new floor for Manning's slope

Our current minimum slope value of 0.001 may be too high for some locations, e.g. Illinois River. Let's make sure to test FIM in these lower slope areas as well as the effect it may have on other areas that don't have that low of a slope.

Matt, I think you're already testing this new slope for low low-relief inland areas, but can you also do a test on a coastal area which might also have low relief? I'm specifically thinking of the Brazoria, TX region that Derek called out yesterday. This area is overpredicting pretty terribly, and I'm curious to see what kind of effect your tests might show here. The HUC is 12070104. Even a 2-yr flow is inundating the floodplain and town pretty badly.

The slope for this area is very low, even below the new floor of 0.000001. However, reducing the slope from the original slope_min of 0.001 only exacerbates the inundation overprediction problem as it decreases the discharge in the Manning's equation. The crosswalking error identified in #1194 is likely responsible for this overprediction.

Here are some results from HUC 10240011. Lowering the minimum slope threshold to slope_min=0.000001 decreases discharge and increases stage and thus inundation. However, the effect on evaluation metrics was inconsistent.

Here's a few images of where the slopes are being set to 0.001 (red lines)


Hotfix/5.4.2

close #1384

Was this hotfix abandoned or merged? In the latter case, why was it necessary to close it manually?

I must have closed it before using git-flow to handle merging, which wasn't necessary.


[Relay][ONNX] fix the wrong default value about dtype in Multinomial converter

Fix the bug: https://github.com/apache/tvm/issues/16623
the default type of attribute 'dtype' is int32 rather than int64

The bug can not produce a significant wrong result. Thus, I didn't add the unit test.

cc @echuraev @Hzfengsy


[Bugfix] Allow user to pick local mode only so huggingface does not do a network call and timeout

Linked issue: https://github.com/qdrant/fastembed/issues/218
This allows the user to select local_files_only and bypass network calls, allowing it to be used behind firewalls.

@Anush008 I'll run with your judgement on this, I don't have enough context on the Huggingface API other than what is mentioned in the linked issue

Thanks @Waffleboy.

Thank you for the review and the changes @joein !

@Waffleboy thank you for the contribution!


Code modernising

These changes should improve the readability and stability of the code base, also when moving / modifying. Especially not using hard-coded strings.
As the project was already at C# 7.3, I modified some of the code to use more of the features, but only if these improve readability. I could have been a lot more aggressive, but assume that would be to much.
Removed the "this." references where possible, as it's unneeded from my standpoint.
Moved 2 classes in their own files, it's a common convention not to have multiple classes in one file.
In TaskbarIcon there was a lot of lock(this), which is bad practice (but most likely not an issue here), I replaced this with a lock on a separate object. This might increase the memory usage with a few bytes, but I would advice to do it anyway.
Also fixed some typos in documentation.
What is missing, are some code / naming conventions (like are private fields prefixed with an _ or not etc)
Just look if you like these changes

@hardcodet LGTM 👍 @Lakritzator

BTW: I was "struggling" with applying "var", and didn't, I'm not a fan of var everywhere but it has it usages... And it's already used in some places...

BTW: I was "struggling" with applying "var", and didn't, I'm not a fan of var everywhere but it has it usages... And it's already used in some places...

@Lakritzator  ACK, I use var if I can infer the type from looking at the code, otherwise I don't:
var user = new User("john");
User user = await GetUser("john");

Some other things I noticed:
Currently the solution is targeting many framework versions, are these needed? I guess you can reduce it on the essence, like 4.5 & 4.7.1 or so...
I found some sub-optimal interop calls, from a performance & memory perspective, but I think this doesn't need to be changed as it's not a critical path. I will check this another time.

As @punker76 is involved, I would expect him to work on Azure Pipeline support too, for making automatic builds & publishing to nuget (if approved), if not I can help.
AppVeyor would be an alternative, but due to the gigantic forward momentum which Microsoft has, my advice would be to use Azure Pipelines.
Your organisation will need an "account" though, but it's free for open source and solves many issues with building locally.

Yes, this code has been unchanged for years now, it can most certainly use some brushing up with regards to targets. Where possible (and easy!), I'd like to support older framework versions, but given it's been mostly stable, I'm not against cutting off some old version at all.

Actually you don't seem to be using any >.NET 4.5 features... it might be okay to leave that in for now and loose all the rest. Why build a library for many different frameworks when there is no difference?
Anyway, that would be something which @punker76 can decide on.
The only part I found which has any different "framework" code is this:
https://github.com/hardcodet/wpf-notifyicon/blob/master/Hardcodet.NotifyIcon.Wpf/Source/NotifyIconWpf/Interop/WindowMessageSink.cs#L188
I actually would remove this, okay? Silverlight :laughing:

@Lakritzator I'm sure Silverlight will have a massive comeback one day. Not :)
Feel free to kill that code 👍 👍 👍

@Lakritzator - @punker76 I created an Azure pipeline, feel free to take over (Azure created a PR on the fly here, I'll add you guys as reviewers).
Jan, I saw that you already added a NuGet issue here, so I guess you'll know what to do there? @Lakritzator, if you'd like, I'll gladly add you to Azure as well, I'd need an email address though to send you an invite.

Actually you don't seem to be using any >.NET 4.5 features... it might be okay to leave that in for now and loose all the rest. Why build a library for many different frameworks when there is no difference?
Anyway, that would be something which @punker76 can decide on.
The only part I found which has any different "framework" code is this:
https://github.com/hardcodet/wpf-notifyicon/blob/master/Hardcodet.NotifyIcon.Wpf/Source/NotifyIconWpf/Interop/WindowMessageSink.cs#L188
I actually would remove this, okay? Silverlight 😆

Maybe net40;net45;net462 and later netcoreapp3.0 could be enough (net462 has some fixed DPI chamges inside).

Actually you don't seem to be using any >.NET 4.5 features... it might be okay to leave that in for now and loose all the rest. Why build a library for many different frameworks when there is no difference?
Anyway, that would be something which @punker76 can decide on.
The only part I found which has any different "framework" code is this:
https://github.com/hardcodet/wpf-notifyicon/blob/master/Hardcodet.NotifyIcon.Wpf/Source/NotifyIconWpf/Interop/WindowMessageSink.cs#L188
I actually would remove this, okay? Silverlight 😆

Maybe net40;net45;net462 and later netcoreapp3.0 could be enough (net462 has some fixed DPI chamges inside).

Sounds good! I don't see a compelling reason to continue supporting CLR 2. Unless Silverlight vnext will support it, of course :p

Thanks, it has been fun! :smiley:


Simplified (object_name#) objects complex again after converting to GLB

Checklist:

[ ] I updated to the latest version available
[ ] I cleared the cache of my browser

Release with the issue:
Last working release (if known):
Browser and Operating System:

I have my OBJ file with objects such as MALE_MANAQUIN; however, when I convert the OBJ file to GLB using the instructions in this repo it goes back to MALE_MANAQUIN_1, _2, _3, etc.

Javascript errors shown in the web inspector (if applicable):

Additional information:

This happens to me as well with the OBJ MTL JSON files. Any solutions so as to be able to assign the corect entity?

In obj and mtl it should not happen if you use the sharp sign (#) at the end of the object name in sweethome3d (ex. John#).
In GBL unfortunately I have not find a way to export in a way to preserve the same object structure I manage to export in .obj


ColMarTech automated marine  equipment rack

I’ll take this issue.

I’m probably just going to add the weapon and armor vendors, and the fills for them too. IIRC those just dispensed onto the floor.

If we have a system for the point-buy vendors, I could probably add a few of those too.

I’m probably just going to add the weapon and armor vendors, and the fills for them too. IIRC those just dispensed onto the floor.

feel free to add anything that can be done, systems can be done later as long as the fills are ready anyways


Improve :ObsidianBacklinks command

Closes #5

CI currently broken due to https://github.com/neovim/neovim/issues/20623


Crashes during parsing of malformed XML files (SDF format)

Hi,
Cross-posting this issue as it affects sdformat and tinyxml2.
https://github.com/leethomason/tinyxml2/issues/878
Thanks!

Thanks for reporting this. We'll keep an eye on the tinyxml issue.


WIP: Config validation script

Description:
This is a early prototype of a script to validate hass configuration. The idea behind the script is to quickly be able to validate a configuration file without starting hass, and ultimately use its output as data-source for hass-config-plugins for text editors.
What I would like to solve:

[ ] yaml validation
[ ] platform validation (vol)
[ ] component validation (vol)
[ ] parsable output
[ ] configuration file line number references from vol

I would appreciate input and opinions about the concept, if this is worth spending time on before I continue.
There in no need for code review yet, most of it is unpolished copy paste.
Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Except for parsable output, check_config currently does most of this.
check_config consists of two parts checking, and printing
A suggestion would be to rather modify the printing based on a cmdline parameter to achieve your desired output.

Ah, I search for a script like that but didn't manage to find it (somehow I didn't know about the homeassistant/scripts folder). That's good news!
I will close this PR and add a new one with with the changes I need in check_config.
thanks @kellerza

I was thinking it would be great to have a commandline option to --output html and then we can add a custom panel in the HA frontend to show the output of the script checking. It should be fairly easy with the way color is implemented. Otherwise passing a json struct to the frontend it can possibly handle its own output
Some users get stuck with ssh and activating correct user and venv and this will help greatly.
Maybe @justweb01 can assist with the panel?

Sound like a good idea. Should be quite easy to add a few different outputs json/html/flat. For my vim-plugin I think flat is easiest to work with, so I might start with that. For the front end, is json or html preferred? If the answer is html I might need some help creating a template to work with.

Json would allow for editing the output in the frontend code. If you output
html the display would have to be edited on the backend. Json is probably
best.
On Tue, Oct 18, 2016, 1:25 AM Per Sandström<EMAIL_ADDRESS>wrote:

Sound like a good idea. Should be quite easy to add a few different
outputs json/html/flat. For my vim-plugin I think flat is easiest to work
with, so I might start with that. For the front end, is json or html
preferred? If the answer is html I might need some help creating a template
to work with.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/3924#issuecomment-254418046,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKvitfvJckZrrJxCRgzKQqa-GUXxFvIUks5q1GZzgaJpZM4KZEii
.


--query.auto-downsampling doesn`t seem to have any effect

Setup containing Thanos+Prometheus+Minio+Grafana running as docker containers.
Relevant configuration for Thanos Querier:
thanos_querier:
    image: thanosio/thanos:v0.20.1
    container_name: thanos_querier
    command:
      - "query"
      - "--log.level=debug"
      - "--log.format=logfmt"
      - "--store=thanos_sidecar:10901"
      - "--store=thanos_store:10901"
      - "--store.sd-interval=5m"
      - "--query.replica-label=monitor"
      - "--query.auto-downsampling"
    restart: unless-stopped
    expose:
      - 10902
      - 10901
    ports:
      - "10902:10902"
    depends_on:
      - minio
      - thanos_sidecar
      - thanos_store

When querying data from Thanos Frontend through Grafana, I only get raw data where I have a 14 days retention time.
Downsampled data with 1H resolution is not shown. Following the PromQL query from Grafana, shows the same
problem in Thanos Frontend.
Example of PromQL query from Grafana:
http://prom:19090/graph?g0.expr=expression%7Bapn%3D%22parameter%22%7D&g0.range_input=2592000s&g0.end_input=2021-06-28%2020%3A49&g0.step_input=1800&g0.tab=0
If add g0.max_source_resolution=auto to the PromQL query, I can see the expected historical downsampled data.
So it seems like the parameter --query.auto-downsampling doesn`t have effect, and the default returned data is only the raw-data.

This was solved with the --query-range.request-downsampled flag in Thanos Query Frontend. According to:
https://github.com/thanos-io/thanos/pull/3723


Fix deserialization of activity exceptions

We were serializing activity exception messages as arrays of a string rather than a string.
Test Plan
GitHub/temporal-ruby/examples $ bundle exec rspec spec/integration/call_failing_activity_workflow_spec.rb

@robholland thoughts?

@antstorm , Rob already looked at this in a previous revision.


Build process is slow

Purpose:

The build process is currently running in series and for the number of tasks it is doing that could otherwise be run independently there is no need for them to run in a specific order.

Description:

There is currently a make build/list command that appears to be outdated, if updated to return the proper images we should get a good list of commands that could be run in parallel

PR:

#982

This has been improved since


Super cool. Will it add privacy feature?

Nice to meet u!
Your project is very cool, I think the proof of humanity is the beginning of democratic application on the chain, and the beginning of blockchain becoming mainstream.
I use the v1 contract, and I found a significant problem, the videos uploaded by users are transparent (e.g. I can sew vitalik's verification video), is it possible to support privacy features? Given the maturity of zkp technology, what are your concerns?
Thank you so much for your ideas, looking forward to seeing more progress! willing to communicate at any time!~

Hey Luozhu, thanks for the feedback!
The video cannot be made private because it would prevent the decentralized curation of the PoH registry by the community, which looks for sybils. The trade-off is that a video is less intrusive than biometrics for example, and PoH does not require any real name, but indeed it does leak the photo, video and audio of the applicants.
I could see ZK being used as an extra layer on top of the current PoH registry and let the other apps integrate with that privacy layer instead of PoH directly. That would be really cool!
Also Sismo has launched a ZK badge for PoH: https://app.sismo.io/proof-of-humanity


Crash on classification with config file

✅ Inferring train table columns. 2s
✅ Loading train table. 2s
✅ Loading test table. 5s
✅ Shuffling. 0s 628ms
✅ Computing train stats. 9s
✅ Computing test stats. 27s
✅ Finalizing stats. 16s
🏁 Computing baseline metrics. 212389 / 230150 92% 0s 15ms elapsed 0ms remaining
[=======================================================================>      ]
[Thread 0x7ffff7c7e640 (LWP 419555) exited]
thread panicked while panicking. aborting.

Thread 1 "tangram" received signal SIGILL, Illegal instruction.

#0  std::panicking::rust_panic_with_hook () at library/std/src/panicking.rs:621
#1  0x00005555572d34a0 in std::panicking::begin_panic_handler::{closure#0} () at library/std/src/panicking.rs:502
#2  0x00005555572d1944 in std::sys_common::backtrace::__rust_end_short_backtrace<std::panicking::begin_panic_handler::{closure#0}, !> () at library/std/src/sys_common/backtrace.rs:139
#3  0x00005555572d3409 in std::panicking::begin_panic_handler () at library/std/src/panicking.rs:498
#4  0x0000555555893a51 in core::panicking::panic_fmt () at library/core/src/panicking.rs:107
#5  0x0000555555893b43 in core::result::unwrap_failed () at library/core/src/result.rs:1613
#6  0x00005555558d6764 in core::result::Result::unwrap<(), std::sync::mpsc::SendError<core::option::Option<tangram_core::progress::ProgressEvent>>> () at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/core/src/result.rs:1295
#7  tangram::train::{impl#1}::drop () at crates/cli/train.rs:169
#8  0x00005555559319a9 in core::ptr::drop_in_place<tangram::train::ProgressThread> () at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/core/src/ptr/mod.rs:188
#9  core::ptr::drop_in_place<core::option::Option<tangram::train::ProgressThread>> () at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/core/src/ptr/mod.rs:188
#10 0x000055555593a651 in tangram::train::train::{closure#1} () at crates/cli/train.rs:117
#11 0x00005555558d5c27 in std::panicking::try::do_call<tangram::train::train::{closure#1}, core::result::Result<(tangram_core::model::Model, std::path::PathBuf), anyhow::Error>> () at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/std/src/panicking.rs:406
#12 std::panicking::try<core::result::Result<(tangram_core::model::Model, std::path::PathBuf), anyhow::Error>, tangram::train::train::{closure#1}> () at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/std/src/panicking.rs:370
#13 std::panic::catch_unwind<tangram::train::train::{closure#1}, core::result::Result<(tangram_core::model::Model, std::path::PathBuf), anyhow::Error>> () at /rustc/db9d1b20bba1968c1ec1fc49616d4742c1725b4b/library/std/src/panic.rs:133
#14 tangram::train::train () at crates/cli/train.rs:37
#15 0x000055555590c001 in tangram::main () at crates/cli/main.rs:170

At a first look, I don't see how the sender can be None on drop, but I'm probably missing something. Anyway, this happens on one dataset I have, if I specify both --file-train and --file-test and a config file.

And it is not happening when you just pass a --file-train and --file-test without a config file?

Yeah, but then it trains the wrong thing (as per my previous question from today). I suppose there's something wrong with my config file. I have the same classes in both the training and validation file, at least.

It's just bizarre that its a SIGILL. What is the version of tangram that you are using?

Both the latest release and a git build fail in the same way. SIGILL is an abort, because a thread panicked while panicking (I updated my original comment).

I meant the format of your config file shouldnt cause it.  We can try and debug this over a video call. Can you join our discord  https://discord.gg/fqyvVMsJ

I've attached a subset of the data, unpack it and run tangram train --file-train training_ss.csv --file-test validation_ss.csv -t CTnumL4A -o t.tangram --config config.json .
The values themselves should be mostly meaningless, but if you don't mind I'll remove the file after we figure it out.
repro.zip

No problem, I am able to reproduce this on my end. I'll start digging in and let you know what I find.

There is definitely an issue with the progress bar. I'm looking into this more. in the meantime, you can train a model by passing the flag --no-progress

Hi @lnicola I fixed the issue. The problem was that we were using the train_row_count as the total for the progress bar when it was in fact the test_row_count that was the total which caused a value that we assumed to be positive to be negative. The eta was negative and the following line caused the panic https://github.com/tangramdotdev/tangram/blob/47340b8de905399912dfb4d181e9a45025c403c8/crates/cli/train.rs#L605
The issue is fixed on the main branch. The same bug should have been hit with regression but because progress draws on a timer and the regression code path was faster, the progress bar didn't get a chance to draw and so that code path was not hit.

Thanks, it's working now. I just had to make a small change for it to build:
diff --git i/crates/cli/train.rs w/crates/cli/train.rs
index 874d77c..cc7836b 100644
--- i/crates/cli/train.rs
+++ w/crates/cli/train.rs
@@ -97,8 +97,7 @@ pub fn train(args: TrainArgs) -> Result<()> {
                        }
                };
                let kill_chip = unsafe { ctrl_c::register_ctrl_c_handler()? };
-               let train_grid_item_outputs =
-                       trainer.train_grid(Some(kill_chip), &mut handle_progress_event)?;
+               let train_grid_item_outputs = trainer.train_grid(kill_chip, &mut handle_progress_event)?;
                unsafe { ctrl_c::unregister_ctrl_c_handler()? };
                if kill_chip.is_activated() {
                        if let Some(progress_thread) = progress_thread.as_mut() {

yes, my bad! Thank you :)


ghc-prim-<IP_ADDRESS> can not be found in indices

I'm using Stackage version nightly-2017-12-16 and want to download the package source for ghc-prim-<IP_ADDRESS> but getting this error:
stack unpack ghc-prim-<IP_ADDRESS>
Selected mirror https://s3.amazonaws.com/hackage.fpcomplete.com/
Downloading root
Selected mirror https://s3.amazonaws.com/hackage.fpcomplete.com/
Downloading timestamp
Downloading snapshot
Downloading mirrors
Cannot update index (no local copy)
Downloading index
Updated package index downloaded
Update complete
Populated index cache.
Selected mirror https://s3.amazonaws.com/hackage.fpcomplete.com/
Downloading timestamp
No updates to your package index were found
Update complete
The following package identifiers were not found in your indices: ghc-prim-<IP_ADDRESS>

I have tried to get it working by deleting ~/.stack/indices but it did not help.

Reproduced

Hmm, I also notice now that this version is not on hackage. Can someone explain this?

Huh!? It says https://www.stackage.org/nightly-2017-12-19/package/ghc-prim-<IP_ADDRESS> but then actually, the latest version listed in the change log is <IP_ADDRESS>. And yes, only that version is on Hackage - https://hackage.haskell.org/package/ghc-prim-<IP_ADDRESS>. Confused.

This is one of those packages that is shipped with ghc so it gets corner case treatment.
See this section of the nightly snapshot file
system-info:
  core-packages:
    ghc: '8.2.2'
    hoopl: '<IP_ADDRESS>'
    bytestring: '<IP_ADDRESS>'
    unix: '<IP_ADDRESS>'
    base: '<IP_ADDRESS>'
    time: '<IP_ADDRESS>'
    hpc: '<IP_ADDRESS>'
    filepath: '<IP_ADDRESS>'
    process: '<IP_ADDRESS>'
    array: '<IP_ADDRESS>'
    integer-gmp: '<IP_ADDRESS>'
    containers: '<IP_ADDRESS>'
    ghc-boot: '8.2.2'
    binary: '<IP_ADDRESS>'
    ghc-prim: '<IP_ADDRESS>'
    ghci: '8.2.2'
    rts: '1.0'
    terminfo: '<IP_ADDRESS>'
    transformers: '<IP_ADDRESS>'
    deepseq: '<IP_ADDRESS>'
    ghc-boot-th: '8.2.2'
    pretty: '<IP_ADDRESS>'
    template-haskell: '<IP_ADDRESS>'
    directory: '<IP_ADDRESS>'

@DanBurton okay but where does version <IP_ADDRESS> comes from?

Since ghc-prim ships with GHC itself, you never need to install it, it's already there when you download GHC. It looks like this is a bug in the GHC upload process, in that this package wasn't released along with other packages like base.

@snoyberg According the release notes https://downloads.haskell.org/~ghc/8.2.2/docs/html/users_guide/8.2.2-notes.html ghc-prim version <IP_ADDRESS> was shipped with GHC.

Then the release notes are wrong too:
$ stack exec --resolver ghc-8.2.2 -- ghc-pkg list ghc-prim
/Users/michael/.stack/programs/x86_64-osx/ghc-8.2.2/lib/ghc-8.2.2/package.conf.d
    ghc-prim-<IP_ADDRESS>

You can find the source files bundled with ghc source. e.g. at my mac terminal:
$ wget https://downloads.haskell.org/~ghc/8.2.2/ghc-8.2.2-src.tar.xz
$ tar -xf ghc-8.2.2-src.tar.xz
$ grep version ghc-8.2.2/libraries/ghc-prim/ghc-prim.cabal
version:        <IP_ADDRESS>

Thanks all for your help!


(proposal) feat: add zerolog library for logging with levels, context and colors

Zerolog[1] is a library that extends the basic log functionality adding log levels, format, colors and context.
[1] https://github.com/rs/zerolog

Signed-off-by: João Vanzuita<EMAIL_ADDRESS>

implemented https://github.com/kubefirst/kubefirst/pull/830 \o/


(3.0.50) very long delay when clicking around after commit (before it finished?)

Jadeite appeared to be frozen in this state for  a few minutes:

It would beep when I clicked but otherwise was not responding and the executing expression dialog remained transparent for the duration ... not long after I made the screenshot (after I figured the display was frozen) and while I was copying the snapshot ... the executing expression dialog disappeared and I was back in business ...
I have a feeling that a second commit click while the first commit click was still running caused the freeze either that or the commit/update was taking an inordinate amount of time ...

Closing this as stale; Dale, reopen if you see it again.


Standard Project Proposal template for GSOC

As the deadline for submitting the project proposal is getting nearer, by adding a standard template would help us in making proposals.
@ivantha @root5533 @SamTube405

Should I add the google guidelines as mentioned in Google Summer of Code Guidelines as PROPOSAL.md file

SCoRe Lab has a proposal template in the GSoC 2019 section http://www.scorelab.org/gsoc-2019/,
https://docs.google.com/document/d/1be2y09Z51yB9X69A04O1rsD9XQXTVLJtu9mvxZdbNpM/edit
maybe it can be added as proposal.md

@Kanishka5 Thanks for sharing :slightly_smiling_face:

Should I add the google guidelines as mentioned in Google Summer of Code Guidelines as PROPOSAL.md file ?

@ivantha?

@ivantha
Should the Proposal.md file added to the project ?

GSoC project guidelines are not needed to be included in the repository.

GSoC project guidelines are not needed to be included in the repository.

:+1: Thanks


[11.0e] GraphQL / Odoo Bi-Directional Connector to Realm (Realm.io)

Hi,
First of all, great initiative on this, this will be incredible useful for integrations.
I'd like to check, what version of Odoo is this targeting, and is it ready for testing (even in an alpha state)?
I'm currently developing something based on the Realm database (realm.io), for an eventual ReactNative + Realm DB App with an Odoo backend.
I'll need this for an 11.0 project, and would like to discuss whether this version is targeted with this repo, as well as whether you are available for custom projects.
The architecture will be as follows:
[Mobile Device]
ReactNative
Realm Mobile DB *Developer Edition (will handle offline use with mobile, and will sync back with Realm Object Server *Developer Edition, on the server)
[Server]
Odoo 11.0e
Realm Object Server (This will poll for changes from Odoo and sync to the Realm Mobile DB, this is where your GraphQL connector comes in)

We would push changes from Realm Object Server to Odoo once changes are detected in Odoo and vice-versa when changes are detected in Realm Object server.
This approach will allow us to avoid the common REST API issues in terms of mobile internet connection reliability, etc. as Realm will handle the logic here.

Is this something you'd be interested in working on?
Here's some information on Realm/GraphQL implementations:
https://github.com/realm/realm-graphql
https://github.com/realm/realm-graphql-service

Hi Luke,
This is something I plan to continue working on very soon. This is however for odooku based odoo versions only. And I will most likely only target 11.0 from now on.
I want full read / write / search support for every Odoo model. So far it looks like this is achievable.

HI Raymond,
Thanks for the reply, it looks like you've already done significant work towards this.
Please let me know if you're interested in working on an Odoo 11.0 implementation of this.


Issue 37867: Row creation in Exp.Data in Panorama folder

Looks good. Ready to commit pending testing from Vagisha on her dev machine.

Meant to say Sweta, not Vagisha. Sorry for the confusion.


Re-structure rollovers test setup for configurability

Split into prepare_rollover and rollover.
prepare_rollover prepares maker, taker and fee_structure to be used for the rollover; it prepares the open cfd and asserts on the initial fees.
rollover performs one rollover and can be parametrized.

One thing that is a bit unfortunate is that we now need access to the previously private aggregated in the projection::Cfd - but I think this is an acceptable change given that we can write better tests!
Potentially this could be configured with only being public in cfg(test) but I did not invest time into this.

This is for preparing more elaborate tests for #2272
I thought it's better to keep the changeset smaller so I opened a separate PR with these improvements against master :)

a bit more about the motivation for the direction of the cleanup commit:

cfg(test) wouldn't work, as it's only useful for unit tests (inside the same file)
pub(crate) would work for integration tests, but only within a crate; daemon-tests are in a separate crate unfortunately :(

we could consider using doc(hidden) for these functions, but I'm not sure about that.

bors r+


Pylance shoud use a sub-level logger of logging

Currently, I noticed that PyLance directly uses logging to record logs. So, when we need to modify the log level, we have to do it in the following way:
logging.basicConfig(level=logging.DEBUG)

The intention behind this is to achieve the goal by modifying the root logger of logging. However, this doesn't seem to be an optimal practice. The optimal practice should be to use the sublevel of logging to prevent changes to the log level from having out-of-scope impacts, like the fsspec's practice. Generally, in a typical Python project, multiple frameworks are usually used, and they may all use the logging modules. If we modify the log level of the root logger, the impact scope of this change may exceed expectations (or there may be side effects).
Therefore, my suggestion is to use the sub-logger and make the following changes:

Use logging.getLogger() to obtain pylance's logger;
Use APIs or environment variables to control the log level of the PyLance logger.

@westonpace @wjones127 WDYT?

This makes sense to me. Would you have bandwidth to make a PR to migrate the logging?
Also is it better to do getLogger() or getLogger(name)?
(Cc
@wjones127 @westonpace if you guys have thoughts)

Would you have bandwidth to make a PR to migrate the logging?

Yes, I will submit a PR to do this.

Also is it better to do getLogger() or getLogger(name)?

IMO, getLogger(name) is better


Merge the PR

Hey guys!
Is anybody having a look at the PR?
There are some that are still waiting and the changes are not that complex... :)

@Mr0grog, @VictorBjelkholm Is help needed?
I could help managing this repository if it is hard!

So, there are two reasons why PRs are pending. First reason is that the changes are small, but they need to be reviewed to make sure the thing is actually "awesome" by some definition. So we can't just merge stuff, has to actually review them.
Second reason is that we're currently working on reorganizing the information in this repository, to have some better discoverability, but that's more minor.

Awesome! Thank you!


About the loss in the training process.

I have trained the model in VOC2007+2012 and also adapted it to other datasets. I've try 300, and 640, and some different settings as well. However, the final loss is always around 2.x or 3.x and keep in this level. What is your final loss when training? I am confused with this problem for several days and didn't found the reason. Plz give me some hints!

I just followed the original training steps and got the results. Maybe it was caused by different initialization?

Thanks!I solved it, mistaking to init the 'lr '=1e-4,so got a worse result！

@OxInsky @IssacCyj
when I set the original lr=1e-3, after 50-100 iterations, it will get NaN loss; while setting 'lr'=1e-4, it will get the decreasing loss.
are looking forward 7fdcf168f8f2ef4aca47cb4f69757ac1ce05700e8814e098


Docs re-structure for Clarinet, Stacks-blockchain-api, Stacks.js, Stacks-explorer products

Re-structured left nav for 4 products.
Updated Sidebar.js to include nav for all 4 products.
Updated content based on the latest feature upgrades.

Explorer docs are very minimal; let's follow-up with the product team to assemble some content

Pinged: https://hiropbc.slack.com/archives/C03TU42NL05/p1665079443535109?thread_ts=1664488674.033069&cid=C03TU42NL05


Adapter gives no status TCP connection

As syslog protocol does not provide any acknowledgement mechanism there should be an option to configure TCP keepalive for syslog endpoint to help ensure message delivery.
/cc @giner

Here is how to reproduce the issue considering you have a load balancer in front of your syslog server which silently cuts TCP connection after 2 minutes of inactivity.

Push a log generator

cf push --no-route -u process -c 'counter=0; rnd=$RANDOM; echo "splunk_test_$rnd - $counter"; sleep 180; while sleep 0.1; do let counter++; echo "splunk_test_$rnd - $counter"; done'

Check logs on syslog server in a few minutes

152 <14>1 2017-11-21T01:17:06.522815+00:00 stas-org.stas-space.hello-go-app 42b9b1ee-97eb-4838-b817-aff1df08ab6f [APP/PROC/WEB/0] - - splunk_test_32595 - 0
155 <14>1 2017-11-21T01:22:08.590296+00:00 stas-org.stas-space.hello-go-app 42b9b1ee-97eb-4838-b817-aff1df08ab6f [APP/PROC/WEB/0] - - splunk_test_32595 - 1202
155 <14>1 2017-11-21T01:22:08.691728+00:00 stas-org.stas-space.hello-go-app 42b9b1ee-97eb-4838-b817-aff1df08ab6f [APP/PROC/WEB/0] - - splunk_test_32595 - 1203
155 <14>1 2017-11-21T01:22:08.792966+00:00 stas-org.stas-space.hello-go-app 42b9b1ee-97eb-4838-b817-aff1df08ab6f [APP/PROC/WEB/0] - - splunk_test_32595 - 1204
155 <14>1 2017-11-21T01:22:08.995555+00:00 stas-org.stas-space.hello-go-app 42b9b1ee-97eb-4838-b817-aff1df08ab6f [APP/PROC/WEB/0] - - splunk_test_32595 - 1206
155 <14>1 2017-11-21T01:22:09.198152+00:00 stas-org.stas-space.hello-go-app 42b9b1ee-97eb-4838-b817-aff1df08ab6f [APP/PROC/WEB/0] - - splunk_test_32595 - 1208
155 <14>1 2017-11-21T01:22:09.299996+00:00 stas-org.stas-space.hello-go-app 42b9b1ee-97eb-4838-b817-aff1df08ab6f [APP/PROC/WEB/0] - - splunk_test_32595 - 1209
...

1200 lines of logs are lost

need to test if this new comment will add the label 'new-activity' sorry for doing this on an open issue. this is for testing gitbot.

This is not really about getting acknowledgements for messages. Syslog messages are ACKed on the TCP level. Adding TCP keep alive allows:

the connection to not get killed by the load balancer in the first place since the connection will stay "active" because of the keep alive packets
if the connection is killed by other means this will be detected early

Adding the keep alive packets will likely help the former situation. If the latter happens I suspect you will still see message loss. Detecting the disconnect takes time. A keep alive timer has
to expire and then the connection needs to be re-established. If the peer is not ready to accept the new connection I believe the adapter goes into a falloff strategy waiting for the peer. These will contribute to message loss.
Also, It would be a good idea for your load balancer that is killing the connections to send a FIN packet to the adapter to let it know the connection was killed for inactivity.

Also, It would be a good idea for your load balancer that is killing the connections to send a FIN packet to the adapter to let it know the connection was killed for inactivity.

We are working on this too. The problem is that remotes are not always under our direct control.

If the latter happens I suspect you will still see message loss.
This should be fine as long as keep-alive is tunable. It is not possible get 100% reliability with syslog protocol anyway.

@ginger This has been added and released with CF Syslog Drain Release v5


client and server don't have same version

Any idea what this means?
Error response from daemon: client and server don't have same version (client : 1.17, server: 1.15)Error response from daemon: client and server don't have same version (client : 1.17, server: 1.15)docker: "run" requires a minimum of 1 argument. See 'docker run --help'.

I get it when I use the "check-cmd {container_name}".

I'm getting the same issue.  Basically, seems the host is running a version of docker older than the docker binary included in the container...
In my case, with CoreOS:
Container:
docker version
Client version: 1.5.0
Client API version: 1.17
Go version (client): go1.4.1
Git commit (client): a8a31ef
OS/Arch (client): linux/amd64
Host:
$ docker version
Client version: 1.4.1
Client API version: 1.16
Go version (client): go1.3.3
Git commit (client): 5bc2ff8-dirty
OS/Arch (client): linux/amd64
Server version: 1.4.1
Server API version: 1.16
Go version (server): go1.3.3
Git commit (server): 5bc2ff8-dirty

Similar (same?) problem on Debian with backports:
sudo docker images
FATA[0000] Error response from daemon: client and server don't have same version (client : 1.17, server: 1.16)
Any suggestions how to update server please?

installed kitematics, and it brought in the latest version of docker I suspect. anyways getting this error after this.

I ran into the same issue, because I did not install correctly docker. I fixed my problem, I re-installed docker by this way:
sudo wget -qO- https://get.docker.com/ | sh
Hope it help someone.

We dropped support for builtin Docker, however you can still bind mount your host docker binary in if you need it in shell scripts.


Associate optional mask to each ROI (in tables), and use it for I/O selection

(branching from https://github.com/fractal-analytics-platform/fractal-tasks-core/issues/45)
This requires #194

Just to make sure we don't duplicate work here: The optional mask would be the label image. And the association should be possible via the metadata of the ROI table & the obs dataframe of AnnData.
See the proposed OME-Zarr table spec: https://github.com/ome/ngff/pull/64
My understanding is that we'd use the region_key in .zattrs to specify which column in the obs dataframe contains the relative path to the label image. For our use case here and the current implementation, each row of the dataframe would point to the same label image (but one could eventually also store e.g. a combined ROI table, where they point to the different label images in the different wells)

Close in favor of #333.


[TOMEE-2060] Make app naming context read only (switched on/off with property)

Initial proposal (there are things to be clarified)

applied, build in progress on https://ci.apache.org/builders/tomee-trunk-ubuntu/builds/778

Thank you for reviewing this. Three more questions/comments from my side:

Is there Tomee code convention documented somewhere? I tried to stick to the original format but obviously the IDE has applied some own preferences and I saw check-formatting step is failing.
About the arquillian tests - I have added a test to check only the default behavior since this is a config change and is applied on container start. (I didn't manage to change it via the test framework) How do you test different behavior that depends on a system property for example?  I was thinking of adding new container for each config set but it would require specifying different mvn profile on build and someone has to invoke these which could be seen as overhead. Do I need to add more arquillian tests for read-only context?
About logging (on your request: if there is a one time - 10 calls will log a single time - log line (warning?)) It would need to propagate and synchronize a counter among nested contexts and it would be unnecessary overhead in my opinion. But if you think this would be hepful, I can add it.

not that much, we are not that strong about it cause we all have different habits and thinking about it
you can create a new surefire execution for this test with another arquillian container config, that said the embedded testing in openejb-core (which forks by test) should be enough probably
you logged it was read only in the assembler, this is enough for now probably

@katya-stoycheva can you please close this - it was applied. Thank you very much for your contribution :-)


README.md indentation issue on terraform_tflint hooks multiple arguments

In order to pass multiple args, try the following:
```yaml
 - id: terraform_tflint
    args:
      - 'args=--deep'
      - 'args=--enable-rule=terraform_documented_variables'
```

should be
In order to pass multiple args, try the following:
```yaml
 - id: terraform_tflint
   args:
      - 'args=--deep'
      - 'args=--enable-rule=terraform_documented_variables'
```

there is one more space with args: so it fails. it needs to be aligned with previous line

Thanks for opening this issue, Omer!
v1.31.0 has been just released.

Making whitespace relevant again. Sigh!


There should probably be less in the base Page class and a little more duplication between Page and ArchivedPage

It will be more code, but it will be easier to keep straight in ya brain.

wontfix


[Packaging][Release] Use Debian/RPM type Artifactory repositories instead of General type Artifactory repository

Describe the enhancement requested
Background
We're using a "General" type Artifactory repository to provide APT/Yum repositories. We generate metadata for APT/Yum repositories' by ourself. Recently, we sometimes get 403 Forbidden errors when we use APT repository in the "general" type Artifactory repository. See also #35292.
INFRA asked JFrog this. See also https://issues.apache.org/jira/browse/INFRA-24569 .
JFrog recommended to migrate to a "Debian" type Artifactory repository. INFRA (not JFrog) also said that "Generic" type Artifactory repository isn't suitable for APT repository.
Compatibility
I already created https://apache.jfrog.io/ui/repos/tree/General/arrow-debian?projectKey=arrow and https://apache.jfrog.io/ui/repos/tree/General/arrow-rpm?projectKey=arrow repositories but I don't do anything yet.
If we use "Debian"/"RPM" type repositories instead of the current "General" type repository, users need to change their configuration. I want to avoid it as much as possible. We're providing apache-arrow-apt-source package for APT repository and apache-arrow-release package for Yum repository. I hope that we can implement a safe migration (users don't need to change anything. users just need to run apt update/dnf update as usual.) by using them.
See also

Debian type repository's document: https://jfrog.com/help/r/jfrog-artifactory-documentation/debian-repositories
RPM type repository's document: https://jfrog.com/help/r/jfrog-artifactory-documentation/rpm-repositories

Component(s)
Packaging, Release

The automated release signing guideline: https://infra.apache.org/release-signing.html#automated-release-signing

Can we use the default signing key for Debian/RPM Package Type repositories to release "official" artifacts?
https://issues.apache.org/jira/browse/INFRA-25217

Our build process must be reproducible build. It must be verified by the Apache Security Team.
We need to contact to<EMAIL_ADDRESS>what we need to do for it.


Add encoder

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

Project coverage is 93.36%. Comparing base (4595264) to head (f2227f0).
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #121      +/-   ##
==========================================
- Coverage   96.68%   93.36%   -3.32%
==========================================
  Files          13       13
  Lines        1268     1312      +44
==========================================
- Hits         1226     1225       -1
- Misses         42       87      +45

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


recvfrom A2S_INFO: Resource temporarily unavailable

How to fix?
./SteamQueryProxy ... 27015
recvfrom A2S_INFO: Resource temporarily unavailable
recvfrom A2S_INFO: Resource temporarily unavailable
recvfrom A2S_INFO: Resource temporarily unavailable
recvfrom A2S_INFO: Resource temporarily unavailable
recvfrom A2S_INFO: Resource temporarily unavailable
recvfrom A2S_INFO: Resource temporarily unavailable
recvfrom A2S_INFO: Resource temporarily unavailable
recvfrom A2S_INFO: Resource temporarily unavailable
recvfrom A2S_INFO: Resource temporarily unavailable
recvfrom A2S_INFO: Resource temporarily unavailable
./SteamQueryProxy 0 27015 It also gives the same error

No idea, you have provided exactly zero information.

Thanks a lot for the quick response. What other information is needed? I run SteamQueryProxy and get this log. Here is more information:

OS Linux Debian 11
Game Counter-Strike Source v92
SteamQueryProxy compiled successfully

make
Scanning dependencies of target SteamQueryProxy
[ 50%] Building C object CMakeFiles/SteamQueryProxy.dir/src/main.c.o
[100%] Linking C executable SteamQueryProxy
[100%] Built target SteamQueryProxy

This has not been tested with CS, see #1
Please provide your firewall rules
Resource temporarily unavailable indicates there was no data to read from the socket.

I use a clean OS, there are no rules. iptables -nvL
-bash: iptables: command not found
There is no security in front of the server either. Checked on different nodes and hosting

Please read the instructions in README.md, you MUST setup firewall rules for this to operate.

Sorry for the inattention. I checked on the node with the rules, there was the same error. That's the only reason I decided to test it on another clean node. Now I installed iptables and added the rules:
root@dimkazai4enko96:~/SteamQueryProxy/build# iptables -nvL
-bash: iptables: command not found
root@dimkazai4enko96:~/SteamQueryProxy/build# apt install iptables
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
libip6tc2 libnetfilter-conntrack3
Suggested packages:
firewalld
The following NEW packages will be installed:
iptables libip6tc2 libnetfilter-conntrack3
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 458 kB of archives.
After this operation, 2,808 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://mirror.docker.ru/debian bullseye/main amd64 libip6tc2 amd64 1.8.7-1 [35.0 kB]
Get:2 http://mirror.docker.ru/debian bullseye/main amd64 libnetfilter-conntrack3 amd64 1.0.8-3 [40.6 kB]
Get:3 http://mirror.docker.ru/debian bullseye/main amd64 iptables amd64 1.8.7-1 [382 kB]
Fetched 458 kB in 0s (5,352 kB/s)
Selecting previously unselected package libip6tc2:amd64.
(Reading database ... 45418 files and directories currently installed.)
Preparing to unpack .../libip6tc2_1.8.7-1_amd64.deb ...
Unpacking libip6tc2:amd64 (1.8.7-1) ......................................................................................................................................................................................................................................]
Selecting previously unselected package libnetfilter-conntrack3:amd64.....................................................................................................................................................................................................]
Preparing to unpack .../libnetfilter-conntrack3_1.0.8-3_amd64.deb ...
Unpacking libnetfilter-conntrack3:amd64 (1.0.8-3) ...######################...............................................................................................................................................................................................]
Selecting previously unselected package iptables.#############################################............................................................................................................................................................................]
Preparing to unpack .../iptables_1.8.7-1_amd64.deb ...
Unpacking iptables (1.8.7-1) ...#################################################################################.........................................................................................................................................................]
Setting up libip6tc2:amd64 (1.8.7-1) ...############################################################################################......................................................................................................................................]
Setting up libnetfilter-conntrack3:amd64 (1.0.8-3) ...####################################################################################################################................................................................................................]
Setting up iptables (1.8.7-1) ...###############################################################################################################################################################################..........................................................]
update-alternatives: using /usr/sbin/iptables-legacy to provide /usr/sbin/iptables (iptables) in auto mode#########################################################################################################################.......................................]
update-alternatives: using /usr/sbin/ip6tables-legacy to provide /usr/sbin/ip6tables (ip6tables) in auto mode
update-alternatives: using /usr/sbin/iptables-nft to provide /usr/sbin/iptables (iptables) in auto mode
update-alternatives: using /usr/sbin/ip6tables-nft to provide /usr/sbin/ip6tables (ip6tables) in auto mode
update-alternatives: using /usr/sbin/arptables-nft to provide /usr/sbin/arptables (arptables) in auto mode
update-alternatives: using /usr/sbin/ebtables-nft to provide /usr/sbin/ebtables (ebtables) in auto mode
Processing triggers for man-db (2.9.4-2) ...##########################################################################################################################################################################################################....................]
Processing triggers for libc-bin (2.31-13+deb11u6) ...
root@dimkazai4enko96:~/SteamQueryProxy/build# ^C
root@dimkazai4enko96:~/SteamQueryProxy/build# iptables -A INPUT -i lo -j ACCEPT
root@dimkazai4enko96:~/SteamQueryProxy/build# iptables -A INPUT -p udp -m udp --dport 27015 -m length --length 33:57 -j NFQUEUE --queue-num 0 --queue-bypass
root@dimkazai4enko96:~/SteamQueryProxy/build# ./SteamQueryProxy 0 27015
recvfrom A2S_INFO: Resource temporarily unavailable
recvfrom A2S_INFO: Resource temporarily unavailable
recvfrom A2S_INFO: Resource temporarily unavailable
root@dimkazai4enko96:~/SteamQueryProxy/build# ^C
root@dimkazai4enko96:~/SteamQueryProxy/build# iptables -nvL
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target     prot opt in     out     source               destination
1    53 ACCEPT     all  --  lo     *       <IP_ADDRESS>/0            <IP_ADDRESS>/0
13   561 NFQUEUE    udp  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            udp dpt:27015 length 33:57 NFQUEUE num 0 bypass
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target     prot opt in     out     source               destination
Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target     prot opt in     out     source               destination
root@dimkazai4enko96:~/SteamQueryProxy/build# ./SteamQueryProxy ...* 27015
recvfrom A2S_INFO: Resource temporarily unavailable
recvfrom A2S_INFO: Resource temporarily unavailable
recvfrom A2S_INFO: Resource temporarily unavailable
recvfrom A2S_INFO: Resource temporarily unavailable
recvfrom A2S_INFO: Resource temporarily unavailable
recvfrom A2S_INFO: Resource temporarily unavailable
recvfrom A2S_INFO: Resource temporarily unavailable
recvfrom A2S_INFO: Resource temporarily unavailabl

I also tried to run ./SteamQueryProxy 0 27015, still getting the error recvfrom A2S_INFO: Resource temporarily unavailable. I'm trying to use your development to protect DDoS attacks by Valve Source Engine (VSE DDoS Method). Recently, css servers have been heavily attacked, no protection helps. We look forward to your development.

This has nothing to do with protecting the server, this is not the tool you're looking for.

Hello there, apologies for piggybacking on this issue thread, but i'm having the same recvfrom A2S_INFO: Resource temporarily unavailable issue for my Rust server
The command im trying to run is ./SteamQueryProxy 0 28016
My port settings
DESCRIPTION  PORT   PROTOCOL  LISTEN
Game         28015  udp       1
Query        28016  udp       1
RCON         28017  tcp       1
App          28018  tcp       1

iptables have been configured using your suggested settings
iptables -A INPUT -i lo -j ACCEPT
iptables -A INPUT -p udp -m udp --dport 27015 -m length --length 33:57 -j NFQUEUE --queue-num 0 --queue-bypass

Current iptables -nvL:
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination
 335K   64M ACCEPT     all  --  lo     *       <IP_ADDRESS>/0            <IP_ADDRESS>/0
44023 2394K NFQUEUE    udp  --  *      *       <IP_ADDRESS>/0            <IP_ADDRESS>/0            udp dpt:28016 length 33:57 NFQUEUE num 0 bypass

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Library versions:
cmake version 3.20.0
gcc version 11.3.0 (Ubuntu 22.04.1)
libnetfilter-queue-dev version 1.0.5-2
libmnl-dev version 1.0.4-3build2

@gnif

Can you please provide a sample tcpdump of the traffic?
tcpdump -i eth0 -s0 -X udp and port 28016
Feel free to censor the IPs, but please do not change anything else.

Sorry, a correction here, I need the loopback traffic
tcpdump -i lo -s0 udp and port 28016 -w capture.pcap

Sorry for the late reply, just woke up, here is the netstat -nvlp | grep 28016:
netstat: no support for `AF INET (sctp)' on this system.
netstat: no support for `AF INET (sctp)' on this system.
udp        0      0 <IP_ADDRESS>:28016    <IP_ADDRESS>:*                           154057/./RustDedica
netstat: no support for `AF IPX' on this system.
netstat: no support for `AF AX25' on this system.
netstat: no support for `AF X25' on this system.
netstat: no support for `AF NETROM' on this system.
netstat: no support for `AF ROSE' on this system.

I ran the tcpdump -i lo -s0 udp and port 28016 -w capture.pcap command and left it running for 2 minutes, while at the same time ./SteamQueryProxy 0 28016 was running (let me know if you need a longer than 2 minute log of tcpdump)
Since github doesn't support .pcap file type upload to the message, here is a download link

I can already see the issue, Rust has bound to <IP_ADDRESS>, however SteamQueryProxy needs to connect to it on <IP_ADDRESS> (Loopback). Because it's bound to only <IP_ADDRESS> it will not be able to communicate. You need to adjust rust to instead bind to <IP_ADDRESS> which will allow both to work.

Thank you, already restarted my server using +app.listenip <IP_ADDRESS> it should be up in 2-3 minutes and i will test it afterwards and let you know how it works out, thank you once again for your help!

IIRC app.listenip is for the Rust companion App, not the rust server itself. You need to set +server.ip <IP_ADDRESS>

Works like a charm now, already receiving query requests:
Got A2S_PLAYER_REPLY: 6 bytes
Got A2S_RULES_REPLY: 1400 bytes
A2S_INFO 0x8e89f97d
A2S_INFO 0x8624849b
A2S_INFO 0x733fb69a
A2S_RULES 0x733fb69a

Awesome
@dimkazai4enko96, even though I do not believe this will help with your DDoS issue, this might be the same reason it is not working for you. I would be curious to know if it does actually help in your situation.

@Saadar just note that this application has a 1400 byte limit for the rules packet, you are already either at the limit or exceeding it which may cause issues. I have never tested this

It is probably because of server description being too long, I will try to compact it to only state most important things

Yes, after shortening it, I'm already only at 1063 bytes on the rules packet, thanks for letting me know about the limit.
Would it be possible to increase the byte limit if for some reason I might need the longer description again?
And if its possible, would i only need to edit Line 84: static char g_datagram[1400] and Line 485: uint8_t buffer[1400] to a higher number on the main.c and compile the build again? (Apologies if i'm completely off about this, never had to deal with C language)
If it might cause any issues to increase the limit, that's okay too, I will keep everything as is, was just confirming.

No, this will not work, 1400 is the maximum reliable payload size for a UDP datagram, to allow for larger payloads the application complexity increases as it needs to then identify the subsequent packet and re-assemble the original payload.

@Saadar & @dimkazai4enko96  I will be pushing in a substantial refactor/redesign which not only will fix the 1400 byte packet size limitation, but also affords some performance improvements and some basic filtering of invalid IPs. This should help with VSE Flood issues.
Testing locally I am able to handle up to 400,000 packets per second before packet loss starts to occur.

Amazing, love your work, I will be definitely testing it.
I already saw a massive change since I started using your Query Proxy and before, with just using default setup on OVH

Changes pushed. Please note that the launch arguments have changed, see the output of --help for all options and some useful information.
I am going to close this issue as resolved, if you encounter any problems please feel free to open a new issue with the details.

Thank you very much. I'm trying to start a game server with the +ip and -ip options (game Game: Counter-Strike Source v92), I still have <IP_ADDRESS>:* it in the netstat -nvlp | grep 27015
netstat -nvlp | grep 22022
tcp        0      0 my_game_server_ip:27015    <IP_ADDRESS>:*               LISTEN      133787/./srcds_linu
udp     9216      0 my_game_server_ip:27015    <IP_ADDRESS>:*                           133787/./srcds_linu
I have several IP addresses on my machine, each game server uses a dedicated one. Ports can be the same. Can you add a variable so that you can specify the ip address of the game server? For example ./SteamQueryProxy -s my_game_server_ip -p 27015 -n 0 -t 2

It's not as simple as adding a parameter, we need to use the loop-back address to avoid getting into a network routing loop in netfilter itself. There might be a way to make this work by marking packets to avoid the loop, but it's not something I have yet looked into.
I will look into if it's possible.

Hrmm, it seems this isn't actually an issue anymore since the redesign of the application. I will add the parameter but please note that it might cause a loop when used. Feedback on how successful it is would be greatly appreciated.

This has been done. Please note that while you could point this to an IP on a different system, it is useless to do so. The new argument is -i or --query-ip.
The only issue with the DoS side of things is that I do not have any game servers that are being attacked, would you be willing to collaborate by allowing me access to one of these targeted systems so I can improve this software? I understand there may be a trust issue here as such I encourage you to see my other repository "Looking Glass" and the associated website. I am a very well known and trusted figure in the FOSS development community.

Yes, sure. I trust you and am very grateful. I got it right, I see:
./SteamQueryProxy -i my_ip -p 27015 -n 0 -s 100000000
Upstream: my_ip:27015 (Protocol: Source)
Got A2S_INFO_REPLY: 267 bytes
Got S2C_CHALLENGE: 0x9f349e1a
Got A2S_PLAYER_REPLY: 6 bytes
It remains to check everything in a real situation. My telegram: @buddy1337

Sorry I do not use telegram, but I am on discord. You can contact me there in the Looking Glass server
https://looking-glass.io/discord


12 Hours format support in datetime picker

Please add support for 12 hours format in the DateTimePicker

+1, please add support for 12 hours format. dateFormat: 'hh:mm a' will throw exception.


Add emsg data to timeline regions.

Closes #1268

Sorry for not looking at this sooner.  Please rebase on the latest master since there have been some large-scale style changes that will cause merge conflicts.  Also you'll need to verify you meet the new style requirements like using let instead of var.  Otherwise looks good to me.  Thanks.

@chrisfillmore Are you still interested in this PR?  You'll need to rebase and make some style changes for the new style requirements.

Yes I'm still interested in this PR, though it's not a high priority. If you'd like to decline for housekeeping purposes, feel free, I can reopen later if I have the time to work on it.

I'm going to go ahead and close this for inactivity.  We would be happen to reopen if/when you're ready to resume.  Thanks for your contributions!


My first pull request

Pull Request
Title

Type of Change

[ ] New feature
[ ] Bug fix
[ ] Documentation Update
[ ] Refactoring
[ ] Hotfix
[ ] Security patch
[ ] UI/UX improvement

Description

Testing

Impact

Issue related to PR

Resolves #

Additional Information

Checklist

[ ] My code adheres to the coding and style guidelines of the project.
[ ] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ ] My changes generate no errors/warnings/merge conflicts.

Sorry, this was a mistake. Please delete this pull request.