Runtime terminal setup for stdin

This issue should have a priority of something like "lower than very low."
If stdin is a terminal, the runtime currently puts the terminal into a pseudo-raw mode. See lang/stdfd.c:stdin_tty(). (It's not quite full raw mode since ISIG is still on; that would be very painful. :-)) In this mode, input characters are not automatically echoed, they're read one-at-a-time, and some special characters like ctrl-d are passed through the input rather than being interpreted, as an end of file for ctrl-d.
Is there a specific reason for doing this? There's nothing obvious in the git logs; it just appears fully formed.
Raw mode is needed for ANSITerm/Readline, and cooked mode is inappropriate if you're doing something involving a binary stream over a pseudo-tty or something (expect-like, maybe?). But it's a bit confusing if you just want to write a simple filter program.
Some discussion from irc:
(04:59:45 PM) mcguire: When it shows up:
(04:59:45 PM) mcguire: commit 416376cc10338ffc2b84a16ff4fb7c349c53aa50
(04:59:45 PM) mcguire: Author: sylvanc<EMAIL_ADDRESS>(04:59:45 PM) mcguire: Date:   Mon Feb 2 12:34:14 2015 +0000
(05:00:13 PM) mcguire: "stdin support"
(05:30:23 AM) sylvanc: mcguire: that's to handle individual keypresses
(05:30:29 AM) sylvanc: rather than line-by-line input

Options are:

Keep it the way it is and document it somewhere fairly visible. New users (Yo!) are going to be confused.

Wait until the program uses ANSITerm/Readline to put the terminal into raw mode.

There's nothing pressing about this issue; I have a work-around (and the very tiny beginings of a Unix systems library).
While I am here, though, I did notice that the runtime is not restoring the terminal mode to raw after a suspend/resume. I'm not sure if that can be done in a SIGCONT handler (I've managed to avoid knowing that so far and might want to preserve my record.) or if it needs something more complex.

via @sylvanc stdfd.c code should probably be moved out of the runtime to pony userland.

via @jemc this functionality should be moved created as an option to turn on and off requiring ambient authority to change the TTY.

That is, it makes sense to require an authority token primitive derived from AmbientAuth (see NetAuth token for an example of this).


Optimisation of ConvertByteStreamToNaluSample()

Good day!
This PR introduce optimisations in algorithm of NALU start codes searching.
This approach is inspired by ffmpeg code. Byte slice is presented as array of uint numbers, this lead to 4/8 times (for 32 and 64bit systems accordingly) less iteration over slice. ((x - 0x0101010101010101) & (^x) & 0x8080808080808080) construction check every byte of uint on zero at once. If zero byte is found we iterating over every odd byte of uint and searching for NALU start code. Last uint and reminder of streamLen % uintSize is iterated with old approach.
FFmpeg code contains one more loop to ensure correct alignment of data. I benchmark it on my machine (arm64 arch) but didn't get any performance benefits.
This optimisation gave us x4 boost on conversion operation (i will provide you with profiling data if needed).
PS Unfortunately i can't test and benchmark this code on 32bit system.

@k-danil Thanks for your PR.
Searching for start codes is a heavy process, so a big efficiency improvement is an indeed a good thing.
I made a small benchmark
func BenchmarkByteStreamToNaluSample(b *testing.B) {
	l := 1024 * 1024
	data := make([]byte, l)
	s := rand.NewSource(42)
	r := rand.New(s)
	for i := 0; i < l; i++ {
		data[i] = byte(r.Intn(256))
	}
	for j := 0; j < b.N; j++ {
		_ = ConvertByteStreamToNaluSample(data)
	}
}

and found an improvement in speed by a factor 6-7 so this PR really provides a big gain.
That said, I think a few things I'd propose to improve

I'm confident that the code won't compile on 32-bit architectures. The reason is that there are 64-bit unsigned
constants in the line if ((x - 0x0101010101010101) & (^x) & 0x8080808080808080) != 0. I therefore think
there should be separate code for the 32-bit case. Either with 32-bit unsigned constants or with the old algorithm.
It would then be nice to have some test for the 32-bit part as well, even though the don't have a 32-bit architecture
to run it on,
The new code is much less readable than the old. I therefore think that the algorithm should be commented,
and one could possibly extract the "zero-byte-check" expression into a separate function (the compiler should inline it).
You have a quite good explanation in the PR text, so copying that into the function would be a great improvement.

For science sake i find working solution:
const (
	magicLeft  uint = 0x0101010101010101 >> (64 - bits.UintSize)
	magicRight uint = 0x8080808080808080 >> (64 - bits.UintSize)
)

func hasZeroByte(x uint) bool {
	return ((x - magicLeft) & (^x) & magicRight) != 0
}

Tested on Debian 5.10.162-1 (2023-01-21) i686 GNU/Linux .

There may be something to learn from https://github.com/golang/go/issues/33388

It's very strange, but it builds fine on my machine.
Befor changes:
% GOOS=linux GOARCH=arm go build .
# github.com/Eyevinn/mp4ff/avc
./annexb.go:91:15: 0x0101010101010101 (untyped int constant<PHONE_NUMBER>8076673) overflows uint
% GOOS=linux GOARCH=386 go build .
# github.com/Eyevinn/mp4ff/avc
./annexb.go:91:15: 0x0101010101010101 (untyped int constant<PHONE_NUMBER>8076673) overflows uint

After:
% GOOS=linux GOARCH=386 go build .
% GOOS=linux GOARCH=arm go build .

OK. Then it's probably something on my side, like that I didn't get latest commit checked out. Sorry for that, but good that we have a way of testing it now.

I'am not a slight against your approach with separate per arch implemention it's just pure interest.
Also i rebased my branch on current master, so you can check is it ok.

I didn't put mentioned solution to PR, you can copy/paste and test it locally. If you think that it's good enought, i will add it.

Hmm.
To me, the commit history looks strange. After rebase your commits should have the "origin/master" commit b281a9f as an ancestor, but that commit (with hash c9e877c) is instead after two commits of yours, and I don't see your latest one with the 32-bit fix (which is the reason my build failed). Can you sync the "upstream remote" on your side, redo the rebase, and make sure that your 32-bit constant fix is included?

All done!


Update cats-effect, cats-effect-laws, ... to 3.3.2

Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-laws
org.typelevel:cats-effect-testkit

from 3.3.1 to 3.3.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #129.

Superseded by #129.


feat: Use Compose V2 to run test

Add compose v2 command docker compose, it is required by image docker:20.10.18
Assign valid CONF_DIR value which is required by compose v2

Fix #702
Signed-off-by: Cherry Wang<EMAIL_ADDRESS>

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[ ] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[X] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

New Dependency Instructions (If applicable)

@cherrycl , with this TAF is always using docker compose (aka V2) to run the compose files, correct?
Compose builder can generate the compose files with V2, but the files it generates don't run using docker-compose (aka V1). So this PR opens up the ability next release to switch to V2 to generate the compose files. I will create a test PR with V2 generated composes files once you verify my assumption. THX!

@lenny-intel Correct, the TAF is always using docker compose command to run tests after this PR was merged.


Doesn't work for link:// protocol addresses

Please can you extend this capability to work with the link:// protocol.
Right now excel isn't practical on AAS with MFA as it prevents users sharing their workbooks due to having to set the username limitation.
https://docs.microsoft.com/en-us/azure/analysis-services/analysis-services-server-alias
If I use the asazure:// protocol the odc works but if I switch it to the link:// protocol I get the error "Initialization of the data source failed..."
I guess it is some limitation of the javascript but I don't really know what it is doing to adapt it

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

ID: 11836a84-4c56-a746-064f-8415bbc37cd6
Version Independent ID: eed232c4-f215-7417-851b-2793276cc056
Content: Create an .odc file to connect to an Azure Analysis Services server
Content Source: articles/analysis-services/analysis-services-odc.md
Service: azure-analysis-services
GitHub Login: @Minewiskan
Microsoft Alias: owend

@o-o00o-o Thanks for the feedback and bringing this to our notice. At this time we are reviewing the feedback and will provide an update as appropriate.

@o-o00o-o Thanks for the feedback. Please feel free to submit your idea, in the user voice forum. All the feedback you share in this forum will be monitored and reviewed by the Analysis Services engineering team.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.
Thank you.


Fix highlighting interferences

Changelog
Highlighting
Fix issue where spellcheck highlighting would remove other highlightings. The highlight marker nodes now have different attribute values.
New marker node attributes:

Comment and whitespace highlights:
Other highlights:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Mod actions do not show who did them after you disconnect and reconnect

If you are mod in a channel and go to maybe an alt account for example and disconnect from chatterino, if you go back to the account you have mod in it will not show mod actions. To be more specific, instead of saying which mod timed someone out it will treat you like you are a normal viewer and not mod.

#1022


Normalisation of the output "per inner loop iteration” by default

It is very nice to be able to do it via --scale command line option, but seems it is more intuitive to have it ON by default, otherwise you get confused due some test written with scalingFactor=.one and some with scalingFactor=.kilo

Fixed with 1.14.0


Suggestion: a more robust implementation for the AUTOCOMMIT option & make it the default on Django ≥ 1.9

Django's on_commit hook seems perfectly appropriate for delaying enqueue() until the database transaction commits.
Django 1.9+ maintains its own per-database-connection (database connections are thread-local) queue of functions to run when the current database transaction commits. You don't have to roll your own.
This is better than hooking to request-related signals because it deals properly with partial rollbacks in case of nested atomic blocks, etc. It works regardless of whether the project uses ATOMIC_REQUESTS and also outside of the request-response cycle.
I think it would be good to make it the default. This would be technically backwards-incompatible but it's likely a better default in the long run, given that many web developers are uncomfortable with database transactions.
The only difficulty is the interaction with multi-database setups. You might have to add a kwarg to tell which database this task depends on. Setting that kwarg to None would enqueue the task immediately. The kwarg would default to 'default'.
Please let me know if you'd like me to elaborate on why I think this is the best way to hook with Django's transaction management.
(Although I'm not the author of on_commit — that's @carljm — I'm responsible for most of the current transaction management features in Django and I'm interested in helping third party projects make the best use of them.)

Here's a custom Queue class that implements the approach I described above.
from django.db import transaction
from rq.queue import Queue

DEFAULT = object()

class OnCommitQueue(Queue):
    """
    RQ Queue that enqueues jobs only after the database transaction commits.

    """
    def __init__(self, *args, **kwargs):
        # Drop autocommit parameter -- this class takes a different approach
        # to the same issue.
        kwargs.pop('autocommit', None)
        return super().__init__(*args, **kwargs)

    def enqueue(self, *args, **kwargs):
        on_commit = kwargs.pop('on_commit', DEFAULT)

        # Explicitly passing on_commit=None forces enqueuing the task
        # immediately. This escape hatch should be rarely needed.
        if on_commit is None:
            super().enqueue(*args, **kwargs)

        # Not passing on_commit enqueues the task after the current
        # transaction on the default database commits.
        if on_commit is DEFAULT:
            on_commit = None

        transaction.on_commit(
            lambda: super().enqueue(*args, **kwargs), using=on_commit)

Note that this approach makes it impossible to return the job synchronously, since it isn't created until the database transaction commits.

I built a test case to show what @aaugustin described. I hope the comments in the code make it explicative so that the test cases can be used as a base for a correct on_commit hook implementation.
Let me recall the @aaugustin worlds:

This is better than hooking to request-related signals because it deals properly with partial rollbacks in case of nested atomic blocks, etc. It works regardless of whether the project uses ATOMIC_REQUESTS and also outside of the request-response cycle.

Sorry for the late response. I think this is a good idea, though I'm unlikely to have any time to work on this anytime soon. I've been super busy since my daughter was born a few weeks ago.
If someone wants to work on this, I'll be more than happy to review and merge the resulting PR.
P.S: thanks for overhauling Django's transaction management features a few releases ago @aaugustin 😃

Congratulations :-)
The custom Queue class works just fine for now, no hurry!

Congratulations :-)

Thanks 😁
Sent from my phone

On Sep 12, 2016, at 9:14 PM, Marco De Paoli<EMAIL_ADDRESS>wrote:
Congratulations :-)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Feat. extend hostPaths to include suffix dir

Addresses #7757

Added fn to extract suffix from a host string
Added tests for hostPaths

/retest

Thanks for the change! Could you squash all the commits?
Also seems like the linter error isn't a fault of your own.. Error: Failed to run: Error: Unexpected HTTP response: 403, Error: Unexpected HTTP response: 403. Pushing will re-kick off the CI so two birds with one stone.


reduce horizontal space in table columns

@scottdraves
Isn't that a space reserved for the hamburger menu? The hamburger menu is shown on cell hover so if i reduce the space the menu icon will overlap the header text.

good point i forgot that.  but i think some overlap will be a smaller bug than this space,
can you give it a try?

there seems to be too much space even accounting for the menu.

Ok, i'll fix this one.


Added ecommerce tracking

Hi there! Thanks for the PR, I've been itching to get started on this feature. Glad to see someone beat me to it.
There are two points which I think is important when considering Ecommerce tracking;

It should work for both iOS/Android (relevant for any new functionality really).
For Android, the standard Ecommerce tracking has been deprecated in the latest SDK.

What I've been thinking of is implementing Enhanced Ecommerce transaction tracking for both platforms. Then we bypass the whole deprecation business, and it's possible to build upon it with more features as far as ecommerce tracking goes.
I have not tested the differences between the standard and enhanced tracking mechanisms for Ecommerce though. Maybe you are more familiar with it than me?

Nope I just started playing with ecommerce tracking today. I haven't dived into React Native for Android yet, so I don't know much about that either. Let me know how I can help!

Awesome! Well code-wise it seems really quite similar to your implementation, other than the fact that the product (equivalent to "item" in the standard tracking), and the ProductAction (equivalent to "transaction") needs to accompany an event or screenView hit.
For that event we'd probably want to let people define their own eventCategory and eventAction (even though they will likely name it something like the example, "Ecommerce" and "Purchase").
So I envision something like this for the JS API:
trackPurchaseEvent(product = {}, transaction = {}, eventCategory = "Ecommerce", eventAction = "Purchase"). In other words category/action are optional params with defaults.
The product object should have the following defintion;
{ productId, name, category, brand, variant, price, couponCode, quantity }
The transaction object should have the following definition;
{ transactionId, affiliation, revenue, tax, shipping, couponCode }
By the way, in your implementation I see you have included default values in the index.js for the objects, this should probably be avoided since they will vary depending on the country.
If you can do the iOS implementation, I can add onto that with an Android implementation. What do you think?

Sure why not? I just finished adding exception, social interaction, user ID, and iOS install tracking (you can see the branches: https://github.com/gnestor/react-native-google-analytics-bridge).

Ok I pushed to https://github.com/gnestor/react-native-google-analytics-bridge/tree/feature/enhanced-ecommerce
You will need to implement Android methods for trackException, trackSocialInteraction, setUser, and allowIDFA if you want to merge this branch into master. Otherwise, you can just take the trackPurchaseEnhanced method.

This is great work, thanks! I'll look into it this evening.
Looks like dependencies will have to be updated for allowIDFA, it requires libAdIdAccess.a. Also it might affect lead to app rejections in App Store. Have you looked into this?

Thanks for the great work! Since the work has diverged so much I made a new pull request.


igh-1423 - updated rest api readme

Added documentation on how to modify the rest api for your project

Codecov Report

Merging #1482 into develop will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop    #1482   +/-   ##
==========================================
  Coverage      66.68%   66.68%
  Complexity      1744     1744
==========================================
  Files            723      723
  Lines          23669    23669
  Branches        2993     2993
==========================================
  Hits           15783    15783
  Misses          6676     6676
  Partials        1210     1210

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 269f4cc...1af6452. Read the comment docs.


Could not build shaders :   cmake missing

On ubuntu, cloned devel and ran 'cargo build'. Got this :
The following warnings were emitted during compilation:
warning: Checking for system installed libraries.  Use --features = build-from-source to disable this behavior
warning: System installed library not found.  Falling back to build from source
error: failed to run custom build command for shaderc-sys v0.6.3
Caused by:
process didn't exit successfully: /home/andy/rust/richter/target/debug/build/shaderc-sys-f89ed4c0ddc2d59e/build-script-build (exit status: 101)
--- stdout
cargo:warning=Checking for system installed libraries.  Use --features = build-from-source to disable this behavior
cargo:warning=System installed library not found.  Falling back to build from source
--- stderr
thread 'main' panicked at '
couldn't find required command: "cmake"

Strangely, i seem to have cmake.   'apt show cmake' returns this
Package: cmake
Version: 3.16.3-1ubuntu1
Priority: optional
Section: devel
Origin: Ubuntu

sudo apt install cmake
worked!
However i wish this wasnt a dependency.  seems like python is a dependency too. ugh


fix: prevent select component to open on scroll for mobile deveices

On mobile devices when the user wants to scroll if touches a select component it opens and prevents the scroll. This is fix that prevents opening if select options on mobile while scrolling and opens only if the user clicks on the select component. The issue is reported here as well https://github.com/shadcn-ui/ui/issues/2654

On mobile devices when the user wants to scroll if touches a select component it opens and prevents the scroll. This is fix that prevents opening if select options on mobile while scrolling and opens only if the user clicks on the select component. The issue is reported here as well #2654

its broken on web better is this:
onPointerDown={(e) => {
         if (e.pointerType === 'touch')
            e.preventDefault()
      }}
     ```


Cargo linter runs correctly, but I see no errors

Information
VIM version
VIM - Vi IMproved 8.1 (2018 May 18, compiled Apr 29 2019 04:53:42)
Included patches: 1-1234
Operating System: Windows 10 version 1703
What went wrong

This appears to be similar to #2488, but I am unsure.
Whenever I lint a project made with cargo new, ALEInfo shows that the cargo check ran, and gave the expected output, but I see nothing in the location list, and in fact, no indication of any errors at all.
Reproducing the bug

cargo new experiment
cd experiment
vim src/main.rs
Make some obvious error, then save.
Observe that you're seeing no indication of anything being amiss.
:ALEInfo and scroll to the bottom.
Observe the results you wished you could have seen.

:ALEInfo
 Current Filetype: rust
Available Linters: ['cargo', 'rls', 'rustc']
  Enabled Linters: ['cargo']
 Suggested Fixers:
  'remove_trailing_lines' - Remove all blank lines at the end of a file.
  'rustfmt' - Fix Rust files with Rustfmt.
  'trim_whitespace' - Remove all trailing whitespace characters at the end of every line.
 Linter Variables:

let g:ale_rust_cargo_avoid_whole_workspace = 1
let g:ale_rust_cargo_check_all_targets = 0
let g:ale_rust_cargo_check_examples = 0
let g:ale_rust_cargo_check_tests = 0
let g:ale_rust_cargo_clippy_options = ''
let g:ale_rust_cargo_default_feature_behavior = 'default'
let g:ale_rust_cargo_include_features = ''
let g:ale_rust_cargo_use_check = 1
let g:ale_rust_cargo_use_clippy = 0
 Global Variables:

let g:ale_cache_executable_check_failures = v:null
let g:ale_change_sign_column_color = 0
let g:ale_command_wrapper = ''
let g:ale_completion_delay = v:null
let g:ale_completion_enabled = 0
let g:ale_completion_max_suggestions = v:null
let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = 'Error'
let g:ale_echo_msg_format = '%code: %%s'
let g:ale_echo_msg_info_str = 'Info'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_enabled = 1
let g:ale_fix_on_save = 0
let g:ale_fixers = {}
let g:ale_history_enabled = 1
let g:ale_history_log_output = 1
let g:ale_keep_list_window_open = 0
let g:ale_lint_delay = 200
let g:ale_lint_on_enter = 'never'
let g:ale_lint_on_filetype_changed = 1
let g:ale_lint_on_insert_leave = 0
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'never'
let g:ale_linter_aliases = {}
let g:ale_linters = {'rust': ['cargo']}
let g:ale_linters_explicit = 1
let g:ale_list_vertical = 0
let g:ale_list_window_size = 10
let g:ale_loclist_msg_format = '%code: %%s'
let g:ale_lsp_root = {}
let g:ale_max_buffer_history_size = 20
let g:ale_max_signs = -1
let g:ale_maximum_file_size = v:null
let g:ale_open_list = 0
let g:ale_pattern_options = v:null
let g:ale_pattern_options_enabled = v:null
let g:ale_set_balloons = 0
let g:ale_set_highlights = 1
let g:ale_set_loclist = 1
let g:ale_set_quickfix = 0
let g:ale_set_signs = 1
let g:ale_sign_column_always = 0
let g:ale_sign_error = '>>'
let g:ale_sign_info = '--'
let g:ale_sign_offset = 1000000
let g:ale_sign_style_error = '>>'
let g:ale_sign_style_warning = '--'
let g:ale_sign_warning = '--'
let g:ale_statusline_format = v:null
let g:ale_type_map = {}
let g:ale_use_global_executables = v:null
let g:ale_virtualtext_cursor = 0
let g:ale_warn_about_trailing_blank_lines = 1
let g:ale_warn_about_trailing_whitespace = 1
  Command History:

(executable check - success) cargo
(finished - exit code 0) ['/usr/bin/bash', '-c', '''cargo'' --version']

<<<OUTPUT STARTS>>>
cargo 1.34.0 (6789d8a0a 2019-04-01)
<<<OUTPUT ENDS>>>

(finished - exit code 101) ['/usr/bin/bash', '-c', 'cd ''/home/em162098/experiment'' && cargo check --frozen --message-format=json -q']

<<<OUTPUT STARTS>>>
{"reason":"compiler-message","package_id":"experiment 0.1.0 (path+file:///C:/msys64/home/em162098/experiment)","target":{"kind":["bin"],"crate_types":["bin"],"name":"experiment","src_path":"C:\\msys64\\home\\em162098\\experiment\\src\\main.rs","edition":"2018"},"message":{"message":"cannot find macro `pintln!` in this scope","code":null,"level":"error","spans":[{"file_name":"src\\main.rs","byte_start":16,"byte_end":22,"line_start":2,"line_end":2,"column_start":5,"column_end":11,"is_primary":true,"text":[{"text":"    pintln!(\"Hello, world!\");","highlight_start":5,"highlight_end":11}],"label":null,"suggested_replacement":null,"suggestion_applicability":null,"expansion":null}],"children":[{"message":"you could try the macro","code":null,"level":"help","spans":[{"file_name":"src\\main.rs","byte_start":16,"byte_end":22,"line_start":2,"line_end":2,"column_start":5,"column_end":11,"is_primary":true,"text":[{"text":"    pintln!(\"Hello, world!\");","highlight_start":5,"highlight_end":11}],"label":null,"suggested_replacement":"println","suggestion_applicability":"MaybeIncorrect","expansion":null}],"children":[],"rendered":null}],"rendered":"error: cannot find macro `pintln!` in this scope\n --> src\\main.rs:2:5\n  |\n2 |     pintln!(\"Hello, world!\");\n  |     ^^^^^^ help: you could try the macro: `println`\n\n"}}
{"reason":"compiler-message","package_id":"experiment 0.1.0 (path+file:///C:/msys64/home/em162098/experiment)","target":{"kind":["bin"],"crate_types":["bin"],"name":"experiment","src_path":"C:\\msys64\\home\\em162098\\experiment\\src\\main.rs","edition":"2018"},"message":{"message":"aborting due to previous error","code":null,"level":"error","spans":[],"children":[],"rendered":"error: aborting due to previous error\n\n"}}

To learn more, run the command again with --verbose.
<<<OUTPUT ENDS>>>

$ rustup component add rls
source

rls has nothing to do with Cargo.
The problem here is that Cargo is being run from Bash, returning Windows with backslashes, when the editor has forward slashes. What's the output of :echo has('win32') and :echo has('unix'). If both are somehow true, that might make this hard to fix. Which environment is Vim being run in?

echo has('win32') gives 0, while echo has('unix') gives 1. The environment is an MSYS2 shell, with vim installed from pacman.

I'm guessing you can't install cargo from pacman? The issue here being Cargo knows it's on Windows and produces output for that environment, but Vim thinks it's on a UNIX compatible, and detects input for that.

@RyanSquared I tried that too. I get a very similar result from following all these steps.

 Current Filetype: rust
Available Linters: ['cargo', 'rls', 'rustc']
  Enabled Linters: ['cargo']
 Suggested Fixers:
  'remove_trailing_lines' - Remove all blank lines at the end of a file.
  'rustfmt' - Fix Rust files with Rustfmt.
  'trim_whitespace' - Remove all trailing whitespace characters at the end of every line.
 Linter Variables:

let g:ale_rust_cargo_avoid_whole_workspace = 1
let g:ale_rust_cargo_check_all_targets = 0
let g:ale_rust_cargo_check_examples = 0
let g:ale_rust_cargo_check_tests = 0
let g:ale_rust_cargo_clippy_options = ''
let g:ale_rust_cargo_default_feature_behavior = 'default'
let g:ale_rust_cargo_include_features = ''
let g:ale_rust_cargo_use_check = 1
let g:ale_rust_cargo_use_clippy = 0
 Global Variables:

let g:ale_cache_executable_check_failures = v:null
let g:ale_change_sign_column_color = 0
let g:ale_command_wrapper = ''
let g:ale_completion_delay = v:null
let g:ale_completion_enabled = 0
let g:ale_completion_max_suggestions = v:null
let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = 'Error'
let g:ale_echo_msg_format = '%code: %%s'
let g:ale_echo_msg_info_str = 'Info'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_enabled = 1
let g:ale_fix_on_save = 0
let g:ale_fixers = {}
let g:ale_history_enabled = 1
let g:ale_history_log_output = 1
let g:ale_keep_list_window_open = 0
let g:ale_lint_delay = 200
let g:ale_lint_on_enter = 1
let g:ale_lint_on_filetype_changed = 1
let g:ale_lint_on_insert_leave = 0
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'always'
let g:ale_linter_aliases = {}
let g:ale_linters = {}
let g:ale_linters_explicit = 0
let g:ale_list_vertical = 0
let g:ale_list_window_size = 10
let g:ale_loclist_msg_format = '%code: %%s'
let g:ale_lsp_root = {}
let g:ale_max_buffer_history_size = 20
let g:ale_max_signs = -1
let g:ale_maximum_file_size = v:null
let g:ale_open_list = 0
let g:ale_pattern_options = v:null
let g:ale_pattern_options_enabled = v:null
let g:ale_set_balloons = 0
let g:ale_set_highlights = 1
let g:ale_set_loclist = 1
let g:ale_set_quickfix = 0
let g:ale_set_signs = 1
let g:ale_sign_column_always = 0
let g:ale_sign_error = '>>'
let g:ale_sign_info = '--'
let g:ale_sign_offset = 1000000
let g:ale_sign_style_error = '>>'
let g:ale_sign_style_warning = '--'
let g:ale_sign_warning = '--'
let g:ale_statusline_format = v:null
let g:ale_type_map = {}
let g:ale_use_global_executables = v:null
let g:ale_virtualtext_cursor = 0
let g:ale_warn_about_trailing_blank_lines = 1
let g:ale_warn_about_trailing_whitespace = 1
  Command History:

(executable check - success) cargo
(finished - exit code 0) ['/usr/bin/bash', '-c', '''cargo'' --version']

<<<OUTPUT STARTS>>>
cargo 1.35.0
<<<OUTPUT ENDS>>>

(finished - exit code 101) ['/usr/bin/bash', '-c', 'cd ''/home/em162098/experiment'' && cargo check --frozen --message-format=json -q']

<<<OUTPUT STARTS>>>
{"reason":"compiler-message","package_id":"experiment 0.1.0 (path+file:///C:/msys64/home/em162098/experiment)","target":{"kind":["bin"],"crate_types":["bin"],"name":"experiment","src_path":"C:\\msys64\\home\\em162098\\experiment\\src\\main.rs","edition":"2018"},"message":{"message":"cannot find macro `priiintln!` in this scope","code":null,"level":"error","spans":[{"file_name":"src\\main.rs","byte_start":16,"byte_end":25,"line_start":2,"line_end":2,"column_start":5,"column_end":14,"is_primary":true,"text":[{"text":"    priiintln!(\"Hello, world!\");","highlight_start":5,"highlight_end":14}],"label":null,"suggested_replacement":null,"suggestion_applicability":null,"expansion":null}],"children":[{"message":"you could try the macro","code":null,"level":"help","spans":[{"file_name":"src\\main.rs","byte_start":16,"byte_end":25,"line_start":2,"line_end":2,"column_start":5,"column_end":14,"is_primary":true,"text":[{"text":"    priiintln!(\"Hello, world!\");","highlight_start":5,"highlight_end":14}],"label":null,"suggested_replacement":"println","suggestion_applicability":"MaybeIncorrect","expansion":null}],"children":[],"rendered":null}],"rendered":"error: cannot find macro `priiintln!` in this scope\n --> src\\main.rs:2:5\n  |\n2 |     priiintln!(\"Hello, world!\");\n  |     ^^^^^^^^^ help: you could try the macro: `println`\n\n"}}
{"reason":"compiler-message","package_id":"experiment 0.1.0 (path+file:///C:/msys64/home/em162098/experiment)","target":{"kind":["bin"],"crate_types":["bin"],"name":"experiment","src_path":"C:\\msys64\\home\\em162098\\experiment\\src\\main.rs","edition":"2018"},"message":{"message":"aborting due to previous error","code":null,"level":"error","spans":[],"children":[],"rendered":"error: aborting due to previous error\n\n"}}

To learn more, run the command again with --verbose.
<<<OUTPUT ENDS>>>

(finished - exit code 101) ['/usr/bin/bash', '-c', 'cd ''/home/em162098/experiment'' && cargo check --frozen --message-format=json -q']

<<<OUTPUT STARTS>>>
{"reason":"compiler-message","package_id":"experiment 0.1.0 (path+file:///C:/msys64/home/em162098/experiment)","target":{"kind":["bin"],"crate_types":["bin"],"name":"experiment","src_path":"C:\\msys64\\home\\em162098\\experiment\\src\\main.rs","edition":"2018"},"message":{"message":"cannot find macro `priiintln!` in this scope","code":null,"level":"error","spans":[{"file_name":"src\\main.rs","byte_start":16,"byte_end":25,"line_start":2,"line_end":2,"column_start":5,"column_end":14,"is_primary":true,"text":[{"text":"    priiintln!(\"Hello, world!\");","highlight_start":5,"highlight_end":14}],"label":null,"suggested_replacement":null,"suggestion_applicability":null,"expansion":null}],"children":[{"message":"you could try the macro","code":null,"level":"help","spans":[{"file_name":"src\\main.rs","byte_start":16,"byte_end":25,"line_start":2,"line_end":2,"column_start":5,"column_end":14,"is_primary":true,"text":[{"text":"    priiintln!(\"Hello, world!\");","highlight_start":5,"highlight_end":14}],"label":null,"suggested_replacement":"println","suggestion_applicability":"MaybeIncorrect","expansion":null}],"children":[],"rendered":null}],"rendered":"error: cannot find macro `priiintln!` in this scope\n --> src\\main.rs:2:5\n  |\n2 |     priiintln!(\"Hello, world!\");\n  |     ^^^^^^^^^ help: you could try the macro: `println`\n\n"}}
{"reason":"compiler-message","package_id":"experiment 0.1.0 (path+file:///C:/msys64/home/em162098/experiment)","target":{"kind":["bin"],"crate_types":["bin"],"name":"experiment","src_path":"C:\\msys64\\home\\em162098\\experiment\\src\\main.rs","edition":"2018"},"message":{"message":"aborting due to previous error","code":null,"level":"error","spans":[],"children":[],"rendered":"error: aborting due to previous error\n\n"}}

To learn more, run the command again with --verbose.
<<<OUTPUT ENDS>>>

Right, so it's still giving out a filename with backslashes - src\main.rs and I'm not sure how to - or whether it would even be appropriate to - handle those kinds of things. I think you'd need Vim installed specifically for Windows (rather than a UNIX-like environment) for this to work properly.

@RyanSquared So you're basically saying that vim on MSYS2 shell is unusable with ALE? I'm not saying it's anyone's fault, but that seems kinda painful.

I'm saying that Vim thinks you're in UNIX. Cargo thinks you're in Windows. I'm not sure who would be appropriate to blame given both are partially correct. I'd look into why Cargo thinks you're in a Windows environment and see if that can be changed.

I think I'll just have to make ALE replace backslashes in filenames on Unix with forward slashes. I doubt anyone actually puts backslashes in their filenames for source files, so I don't expect it to be an issue.

I've pushed a commit now to handle convert back slashes to forward slashes in a Unix environment, even though back slashes are actually valid characters in Unix. That should fix your issue. Let me know if you still have problems.
Later on, we might want to handle paths like C:\foo\bar as something like /drive/c/foo/bar, depending on the environment and where the drives are mounted.

If I may, it's a bad decision. Even if very few users use backslash in the name of their files, this may happen for some reasons.  All this on behalf of this particular issue (one user that is in Windows 10, under a "MSYS2 shell"..). It's not logic at all.

I'm okay with breaking support for all Linux paths containing a backslash. I sincerely doubt anyone seriously commits code with backslashes in their filenames.


Invalid URLs in notification emails sent by Amplify Console

AWS notifications send incorrect URL for build URLs.
I have a branch named feature/my_CoolBranch, the build URL for in Amplify Console is therefore:
https://feature-my-coolbranch.<id_generated_by_amplify>.amplifyapp.com.
However, the URL in the email notification is corrupt and the same branch reads
https://feature/my_CoolBranch.<id_generated_by_amplify>.amplifyapp.com
I'd expect the URL in the email to match the valid URL as shown in the Console UI.
This can be consistently replicated with any branch name containing underscore _, slash /. In addition the case should be normalised, i. e. lowercased.

Okay looks, like notification service needs to catch nonalpha/numerical characters and replace them with -, it should also convert all characters to lowercase. I will work on submitting a fix for this.

Hi, we found the same problem. Is there any progress on this issue?

+1 since #739 got closed, even though this isn't fixed.


Add logging and permissions to core modules

Basic logging and file permission scripts are in the utils directory of the repo. Need to add these to calib_prep.py, mkref.py and mkrefs.py.

@arminrest, how should we set up logging? A single log file for each run of mkrefs.py? Break it up into separate log files for each module (e.g. mkrefs, calib_prep, rdnoise_nircam, gain_armin, etc)?


chore: revert "chore: Add kafkaPagev3 to index.ts file"

Reverts redhat-developer/app-services-ui-components#485

:tada: This PR is included in version 2.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Wait for powershell script to finish, callback not working?

Hello,
Great plugin, thanks!. Maybe I'm trying something impossible here, but let's give it a go. I'm using gulp-run to start up a powershell script that executes in a separate powershell window. I thought I could use the callback function to be able to have gulp-run to finish the task, after the powershell script has done it's job.. but can 't get it to work. I'm loading powershell with the 'Start-Process' command.
function deploy(done) {
 // some variable definitly left out (argumentlist)
  return run('Start-Process powershell.exe -ArgumentList ' + argumentList, { usePowerShell: true }).exec(function () {
    done();
  });
}
gulp.task('deploy', deploy);

This is the output, you can see it doesn't wait for completion:
[16:40:18] Starting 'deploy'...
[16:40:18] Finished 'deploy' after 543 ms
$ Start-Process powershell.exe -ArgumentList etc....

Any thoughts on this? Thanks!

Let me know do you have any updates on this ?


Is there a way to go to a specific date?

let's say I click on some button on my website and the <DatePicker /> (or <Calendar />) goes on 2007-12-15 and picks that date, is this possible?

Currently it is not possible

I guess one good workaround is to just re-render the datepicker on specific date, but I don't think it will work when we want to pick range of days.

My foolish mistake, it can go to a specific date with just setValue function of the useState, it just needs to be a new reference of object {year: 2020, month: 10, day: 28} in order to force rerender.
I changed the day, but forgot that the object reference stays the same, so it was not re-rendering.

I thought you only needed going to specific date without selecting it.

yeah, I wanted to go to specific date programmatically (without mouse/keyboard interaction), for example 3 seconds after mounting.


Loose version requirements

Codecov Report

Merging #820 (f9a0a9c) into main (4a5ecec) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #820   +/-   ##
=======================================
  Coverage   85.43%   85.43%
=======================================
  Files         319      319
  Lines       29713    29713
=======================================
  Hits        25386    25386
  Misses       4327     4327

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 4a5ecec...f9a0a9c. Read the comment docs.


Unavailable entity climate.smoker

Synology 918+:
https://imgur.com/G14OJzo
https://imgur.com/Btwsa4h
https://imgur.com/Fu6DBjF
Verified tuya keys, uninstalled / reinstalled several times.
Logger: custom_components.recteq.device
Source: custom_components/recteq/device.py:127
Integration: Recteq (documentation, issues)
First occurred: 10:11:50 PM (7 occurrences)
Last logged: 10:12:50 PM
Unexpected error fetching Smoker data: Expecting value: line 1 column 1 (char 0)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 144, in async_refresh
self.data = await self._async_update_data()
File "/config/custom_components/recteq/device.py", line 145, in _async_update_data
await self.async_update()
File "/config/custom_components/recteq/device.py", line 140, in async_update
await self.hass.async_add_executor_job(self.update)
File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/recteq/device.py", line 127, in update
self._cached_status = self._pytuya.status()['dps']
File "/usr/local/lib/python3.8/site-packages/pytuya/init.py", line 311, in status
result = json.loads(result)
File "/usr/local/lib/python3.8/json/init.py", line 357, in loads
return _default_decoder.decode(s)
File "/usr/local/lib/python3.8/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/local/lib/python3.8/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
Supervisor Core Logs
self._cached_status = self._pytuya.status()['dps']
File "/usr/local/lib/python3.8/site-packages/pytuya/init.py", line 311, in status
result = json.loads(result)
File "/usr/local/lib/python3.8/json/init.py", line 357, in loads
return _default_decoder.decode(s)
File "/usr/local/lib/python3.8/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/local/lib/python3.8/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
2020-12-23 22:26:41 DEBUG (MainThread) [custom_components.recteq.device] Finished fetching Smoker data in 0.025 seconds
2020-12-23 22:26:41 INFO (SyncWorker_16) [somecomfort] Session refreshed
2020-12-23 22:26:51 DEBUG (SyncWorker_2) [pytuya] status() entry
2020-12-23 22:26:51 DEBUG (SyncWorker_2) [pytuya] json_payload=b'{"gwId":"18345033bcddc296d94f","devId":"18345033bcddc296d94f"}'
2020-12-23 22:26:51 DEBUG (SyncWorker_2) [pytuya] status received data=b'\x00\x00U\xaa\x00\x00\x00\x00\x00\x00\x00\n\x00\x00\x00,\x00\x00\x00\x01\x19G\x99\x06\x88\x0b\xec\xd9\xf9w\x0e\x02\x13b\xd4\xef\xd4\xb7>\xff\xe9V\xb1\xc7Jo\xe4+\xd5\x8czk\xd2\t\xe7S\x00\x00\xaaU'
2020-12-23 22:26:51 DEBUG (SyncWorker_2) [pytuya] result=b'\x19G\x99\x06\x88\x0b\xec\xd9\xf9w\x0e\x02\x13b\xd4\xef\xd4\xb7>\xff\xe9V\xb1\xc7Jo\xe4+\xd5\x8czk'
2020-12-23 22:26:51 DEBUG (SyncWorker_2) [pytuya] decrypted result=''
2020-12-23 22:26:51 ERROR (MainThread) [custom_components.recteq.device] Unexpected error fetching Smoker data: Expecting value: line 1 column 1 (char 0)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 144, in async_refresh
self.data = await self._async_update_data()
File "/config/custom_components/recteq/device.py", line 145, in _async_update_data
await self.async_update()
File "/config/custom_components/recteq/device.py", line 140, in async_update
await self.hass.async_add_executor_job(self.update)
File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/recteq/device.py", line 127, in update
self._cached_status = self._pytuya.status()['dps']
File "/usr/local/lib/python3.8/site-packages/pytuya/init.py", line 311, in status
result = json.loads(result)
File "/usr/local/lib/python3.8/json/init.py", line 357, in loads
return _default_decoder.decode(s)
File "/usr/local/lib/python3.8/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/local/lib/python3.8/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
2020-12-23 22:26:51 DEBUG (MainThread) [custom_components.recteq.device] Finished fetching Smoker data in 0.028 seconds
2020-12-23 22:27:01 DEBUG (SyncWorker_3) [pytuya] status() entry
2020-12-23 22:27:01 DEBUG (SyncWorker_3) [pytuya] json_payload=b'{"gwId":"18345033bcddc296d94f","devId":"18345033bcddc296d94f"}'
2020-12-23 22:27:01 DEBUG (SyncWorker_3) [pytuya] status received data=b'\x00\x00U\xaa\x00\x00\x00\x00\x00\x00\x00\n\x00\x00\x00,\x00\x00\x00\x01\x19G\x99\x06\x88\x0b\xec\xd9\xf9w\x0e\x02\x13b\xd4\xef\xd4\xb7>\xff\xe9V\xb1\xc7Jo\xe4+\xd5\x8czk\xd2\t\xe7S\x00\x00\xaaU'
2020-12-23 22:27:01 DEBUG (SyncWorker_3) [pytuya] result=b'\x19G\x99\x06\x88\x0b\xec\xd9\xf9w\x0e\x02\x13b\xd4\xef\xd4\xb7>\xff\xe9V\xb1\xc7Jo\xe4+\xd5\x8czk'
2020-12-23 22:27:01 DEBUG (SyncWorker_3) [pytuya] decrypted result=''
2020-12-23 22:27:01 ERROR (MainThread) [custom_components.recteq.device] Unexpected error fetching Smoker data: Expecting value: line 1 column 1 (char 0)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 144, in async_refresh
self.data = await self._async_update_data()
File "/config/custom_components/recteq/device.py", line 145, in _async_update_data
await self.async_update()
File "/config/custom_components/recteq/device.py", line 140, in async_update
await self.hass.async_add_executor_job(self.update)
File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/recteq/device.py", line 127, in update
self._cached_status = self._pytuya.status()['dps']
File "/usr/local/lib/python3.8/site-packages/pytuya/init.py", line 311, in status
result = json.loads(result)
File "/usr/local/lib/python3.8/json/init.py", line 357, in loads
return _default_decoder.decode(s)
File "/usr/local/lib/python3.8/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/local/lib/python3.8/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
2020-12-23 22:27:01 DEBUG (MainThread) [custom_components.recteq.device] Finished fetching Smoker data in 0.029 seconds
2020-12-23 22:27:06 ERROR (MainThread) [custom_components.hacs] Error trying to serve custom_components/spotcast/
Traceback (most recent call last):
File "/config/custom_components/hacs/webresponses/category.py", line 22, in async_serve_category_file
response = await async_serve_static_file_with_etag(
File "/config/custom_components/hacs/webresponses/category.py", line 52, in async_serve_static_file_with_etag
etag = await async_get_etag(servefile)
File "/config/custom_components/hacs/helpers/functions/file_etag.py", line 18, in async_get_etag
fnv = await hass.async_add_executor_job(get_etag, path)
File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/hacs/helpers/functions/file_etag.py", line 13, in get_etag
return fnv1a_32(file_path.read_bytes())
File "/usr/local/lib/python3.8/pathlib.py", line 1228, in read_bytes
with self.open(mode='rb') as f:
File "/usr/local/lib/python3.8/pathlib.py", line 1221, in open
return io.open(self, mode, buffering, encoding, errors, newline,
IsADirectoryError: [Errno 21] Is a directory: '/config/www/community/custom_components/spotcast'
2020-12-23 22:27:06 ERROR (MainThread) [custom_components.hacs] Error trying to serve custom_components/unifigateway/
Traceback (most recent call last):
File "/config/custom_components/hacs/webresponses/category.py", line 22, in async_serve_category_file
response = await async_serve_static_file_with_etag(
File "/config/custom_components/hacs/webresponses/category.py", line 52, in async_serve_static_file_with_etag
etag = await async_get_etag(servefile)
File "/config/custom_components/hacs/helpers/functions/file_etag.py", line 18, in async_get_etag
fnv = await hass.async_add_executor_job(get_etag, path)
File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/hacs/helpers/functions/file_etag.py", line 13, in get_etag
return fnv1a_32(file_path.read_bytes())
File "/usr/local/lib/python3.8/pathlib.py", line 1228, in read_bytes
with self.open(mode='rb') as f:
File "/usr/local/lib/python3.8/pathlib.py", line 1221, in open
return io.open(self, mode, buffering, encoding, errors, newline,

Will look at this soon.  Sorry for the delay.

No worries, thanks for the update and the time u  and others spent getting
this to work!!
Jim Davis
Davis MWD Field Services
<EMAIL_ADDRESS>(817) 584-7474
On Tue, Dec 29, 2020 at 12:26 PM Paul Dugas<EMAIL_ADDRESS>wrote:

Will look at this soon. Sorry for the delay.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pdugas/recteq/issues/12#issuecomment-752194556, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ3HRW3EWO56VIZ7GTRV5LTSXINMJANCNFSM4VHYU4HA
.

I'm not sure what's going on to generate that error. Gotta admit I'm no expert on HA's inner workings. I have a fully current instance of HA with this plugin installed and it's not producing that error. Maybe I'll try using incorrect configs and see if that causes this.

Don't put much time into it, I often have more issues with using the
synology in docker, sometimes, not always someone with a Synology has the
same issue and I can follow what they did to get it to work.
Thanks, again
Jim Davis
Davis MWD Field Services
<EMAIL_ADDRESS>(817) 584-7474
On Wed, Dec 30, 2020 at 4:51 PM Paul Dugas<EMAIL_ADDRESS>wrote:

I'm not sure what's going on to generate that error. Gotta admit I'm no
expert on HA's inner workings. I have a fully current instance of HA with
this plugin installed and it's not producing that error. Maybe I'll try
using incorrect configs and see if that causes this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pdugas/recteq/issues/12#issuecomment-752781868, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ3HRW6HHZO3ARNDWPM26BDSXOVFJANCNFSM4VHYU4HA
.

I had this integration working but recently had to reinstall Ubuntu on the computer that I use for my home assistant server which is installed as a virtual machine. On the previous setup home assistant was humming as a VM using Oracle's virtual machine, but this time I am using the virtual machine software that comes with Ubuntu and setup my home assistant using the KVM file. Cannot get my recteq smoker to work now, just shows as unavailable no matter how many ways I have tried to install/re-install this integration.
Below is the info from the log:
2021-06-22 17:20:12 ERROR (MainThread) [custom_components.recteq.device] Unexpected error fetching Smoker data: Expecting value: line 1 column 1 (char 0)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 187, in _async_refresh
self.data = await self._async_update_data()
File "/config/custom_components/recteq/device.py", line 135, in _async_update_data
await self.async_update()
File "/config/custom_components/recteq/device.py", line 130, in async_update
await self.hass.async_add_executor_job(self.update)
File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/recteq/device.py", line 117, in update
self._cached_status = self._pytuya.status()['dps']
File "/usr/local/lib/python3.8/site-packages/pytuya/init.py", line 311, in status
result = json.loads(result)
File "/usr/local/lib/python3.8/json/init.py", line 357, in loads
return _default_decoder.decode(s)
File "/usr/local/lib/python3.8/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/local/lib/python3.8/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Just got home assistant blue odroid n2+ and am having the same issue as above. Wish I had tried to install before installing most of my setup from scratch to see if something else was interfering with install. trplowman, please let us know if you were able to resolve. Thanks

Nope, unable to get it working.
Sent from my iPhone
On Jun 29, 2021, at 2:39 PM, Jackald1918 @.***> wrote:

Just got home assistant blue odroid n2+ and am having the same issue as above. Wish I had tried to install before installing most of my setup from scratch to see if something else was interfering with install. trplowman, please let us know if you were able to resolve. Thanks
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/pdugas/recteq/issues/12#issuecomment-870863591, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AR7WAPL734ZZCD2YW245HNLTVIOQFANCNFSM4VHYU4HA.


HM Big drop area

Optional file select form + optional Drag'n'Drop + File upload looks like a nice can of worm, bit should still be achievable.


Webhooks docs update

When working on my bot, I noticed the webhooks docs were a little outdated.
I updated the example jsons to include new fields that they now have, fixed their indentation, and included a new VISIBILITY-UPDATE example since the json is now completely different from the old docs.
I also did some updates on the wording on the page -- tried to fix capitalization/punctuation mistakes, and then update the sentences to be more readable. I'm not 100% happy with all the changes I made, so they don't need to be included if you don't like them. (Or if anyone has an idea on how to further improve them...)

Yeah, it looks good aside from the rogue capitals in the JSON examples.
I find the changes to be completely readable, thank you for taking some time to polish it up! This kind of stuff really makes a difference when people are trying to implement APIs, as I'm sure you discovered when doing it yourself :)

good catch with the capitalization, fixed it.

Thank you so much! 🥇


optimist ddl: fix safe redirect after gtid event

What problem does this PR solve?

Issue Number: close #6691
What is changed and how it works?

redirect after receive rows event/ query event

Check List
Tests
Original test
Release note
None

/run-all-tests

/run-all-tests

/run-dm-integration-test

/merge

/run-all-tests

/run-dm-integration-test

/run-dm-integration-test

/run-dm-integration-test


forkproxy: Retry epoll on EINTR

Proxy processes currently exit when epoll_wait is interrupted, leaving a broken connection that (I think) can only be fixed by restarting the container or removing and re-adding the device. This just handles EINTR so the proxy keeps listening.
I reused the body of the lxc_read_nointr function in main_forkproxy.go, which did basically the same thing for read(2) but didn't seem to be used anywhere (it was introduced in 45be3534).

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

jenkins: test this please

@brauner can you review this one?

Looks solid.

jenkins: test this please


Upgrade jenkins and plugins versions

It was getting the error. So I upgraded the Jenkins and plugin versions.

Jenkins image upgraded to v2.126
Kubernetes plugin upgraded to v1.7.1
Workflow-job plugin upgraded to v2.21
Credentials-binding plugin upgraded to v1.16
Git plugin upgraded to v3.9.1

Cool, thanks for the PR. I'll verify tonight and merge after it :+1:


sparse data frame value_counts not working

Based on a suggestion from an user at stackoverflow.com, I am reporting a bug / enhancement request for sparse data frames. Please let me know if you need any more information.
Thanks in advance.
I am encountering a TypeError with a pandas sparse data frame when I use the value_counts method. I have listed the versions of the packages that I am using.
Python 2.7.6 |Anaconda 1.9.1 (x86_64)| (default, Jan 10 2014, 11:23:15)
[GCC 4.0.1 (Apple Inc. build 5493)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

import pandas
print pandas.version
0.13.1
import numpy
print numpy.version
1.8.0

dense_df = pandas.DataFrame(numpy.zeros((10, 10))
,columns=['x%d' % ix for ix in range(10)])
dense_df['x5'] = [1.0, 0.0, 0.0, 1.0, 2.1, 3.0, 0.0, 0.0, 0.0, 0.0]
print dense_df['x5'].value_counts()
0.0    6
1.0    2
3.0    1
2.1    1
dtype: int64

sparse_df = dense_df.to_sparse(fill_value=0) # Tried fill_value=0.0 also
print sparse_df.density
0.04

print sparse_df['x5'].value_counts()
Traceback (most recent call last):
File "", line 1, in
File "//anaconda/lib/python2.7/site-packages/pandas/core/series.py", line 1156, in     value_counts
normalize=normalize, bins=bins)
File "//anaconda/lib/python2.7/site-packages/pandas/core/algorithms.py", line 231, in value_counts
values = com._ensure_object(values)
File "generated.pyx", line 112, in pandas.algos.ensure_object (pandas/algos.c:38788)
File "generated.pyx", line 117, in pandas.algos.ensure_object (pandas/algos.c:38695)
File "//anaconda/lib/python2.7/site-packages/pandas/sparse/array.py", line 377, in astype
raise TypeError('Can only support floating point data for now')
TypeError: Can only support floating point data for now

In current master, fill_value is not included result without TypeError. Changing the title.
pd.SparseSeries([1, 2, 0, 0], fill_value=0).value_counts()
# 2    1
# 1    1
# dtype: int64


Rohit

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
hGnhn
Error Message and Stack Trace (if applicable)
Ghgh
Description
Yhtuyhy
System Info
Yhguyuujhgghyhu

Dedooo bro

Hghhhjuu

Please 🥺

Iiii

Ji

Jsjhsajhana

Bnsnsnshsuzgz

Hsjshnsuabans

Bnahajahajas

Nbanajaha

Hahhahahaa

Babahahhaa

H

@ccurme this is some spam issue we can close it i think


[FEATURE] Utilize uvloop in batches to avoid using threads for domain name resolution

Is your feature request related to a problem? Please describe.

Currently, all batches are written in async way but some web3 call uses multi thread because aiohttp depended by web3 resolves domain name using getaddrinfo which calls Thread.run.
To reduce thread overhead, we want to introduce uvloop, which allows getaddrinfo to be executed without threading.

https://github.com/MagicStack/uvloop/blob/v0.19.0/uvloop/loop.pyx#L892-L932

Describe the solution you'd like

Utilize uvloop in batches to avoid using threads for domain name resolution.

In order to make aiohttp Session cache thread-safe, web3 uses exclusion control on a single separate thread. This cannot be removed.
https://github.com/ethereum/web3.py/blob/v6/web3/_utils/request.py#L129-L141
https://github.com/ethereum/web3.py/blob/v6/web3/_utils/async_caching.py#L13


Python 2.7+ requirement should be documented in Readme.

Will not work w/ Python 2.6.

maybe. It's already documented in tox.ini and setup.py so I'm not motivated to do the work myself. hint hint.