Double clicking on a word can select prior not character symbol

Godot version
4.0-beta6
System information
Windows 10
Issue description
Word selection is not stopping to some symbols on left of word (tested +=>$) if prior symbol of this character is not a word or spacing character which is not very practical for most of them ; no problem with ,!-<%;* however.
It seems to be right too in Label and RichTextLabel text edit box... but there rules could be different ?
I tested too €uro, ₩on, ¥en as examples, but those characters arez similar to letters and I am less anoyed to see them selected...
Steps to reproduce
Just open any script, exit any Label or RichTextLabel text and type examples below,
then double-click on word in order to select it :

"var1==var2" : if I double-click on var2, =var2 is selected
"func myFunc()->int:" : if I double-click on int, >int is selected
"this is test for ++tag" : if I double-click on tag, +tag is selected

Minimal reproduction project
Any project, in any script or Label text edit box, or RighTextLabel text edit box

Search for similar issue with :
is:issue is:open label:bug label:topic:editor  word selection
And only one related I found was a graphical issue :
#55588

Found #56402 which is similar but restricted to $

I found that putting space before things is an acceptable workaround ;
what bothered me was difference of behavior for different symbols...

In fact I was chocked because Godot 3.5.x do not behave like that... it feels like some regression to me.

You can change the list of non-word characters for the purpose of text navigation/selection in the Editor Settings, but I agree the default value should be changed to get the 3.x behavior back. Feel free to open a pull request for this :slightly_smiling_face:

You can change the list of non-word characters for the purpose of text navigation/selection in the Editor Settings, but I agree the default value should be changed to get the 3.x behavior back. Feel free to open a pull request for this 🙂

I can't find any setting.
This seems to be caused by TextServerAdvanced's u_ispunct() which doesn't consider certain characters as punctuation. Using TextServerFallback matches the 3.x behavior because it uses Godot's is_punct().
A way to solve this would be to add custom_punctuation to CodeEdit.
Also, we should maybe match is_punct()'s behavior with u_ispunct().
Differences between the two functions:

Code
Char
u_ispunct()
is_punct()
Diff

32

0
1
*

33
!
1
1

34
"
1
1

35
#
1
1

36
$
0
1
*

37
%
1
1

38
&
1
1

39
'
1
1

40
(
1
1

41
)
1
1

42
*
1
1

43
+
0
1
*

44
,
1
1

45
-
1
1

46
.
1
1

47
/
1
1

48
0
0
0

49
1
0
0

50
2
0
0

51
3
0
0

52
4
0
0

53
5
0
0

54
6
0
0

55
7
0
0

56
8
0
0

57
9
0
0

58
:
1
1

59
;
1
1

60
<
0
1
*

61
=
0
1
*

62
>
0
1
*

63
?
1
1

64
@
1
1

65
A
0
0

66
B
0
0

67
C
0
0

68
D
0
0

69
E
0
0

70
F
0
0

71
G
0
0

72
H
0
0

73
I
0
0

74
J
0
0

75
K
0
0

76
L
0
0

77
M
0
0

78
N
0
0

79
O
0
0

80
P
0
0

81
Q
0
0

82
R
0
0

83
S
0
0

84
T
0
0

85
U
0
0

86
V
0
0

87
W
0
0

88
X
0
0

89
Y
0
0

90
Z
0
0

91
[
1
1

92
\
1
1

93
]
1
1

94
^
0
1
*

95
_
1
0
*

96
`
0
1
*

97
a
0
0

98
b
0
0

99
c
0
0

100
d
0
0

101
e
0
0

102
f
0
0

103
g
0
0

104
h
0
0

105
i
0
0

106
j
0
0

107
k
0
0

108
l
0
0

109
m
0
0

110
n
0
0

111
o
0
0

112
p
0
0

113
q
0
0

114
r
0
0

115
s
0
0

116
t
0
0

117
u
0
0

118
v
0
0

119
w
0
0

120
x
0
0

121
y
0
0

122
z
0
0

123
{
1
1

124
|
0
1
*

125
}
1
1

126
~
0
1
*

127
⌂
0
0

This also affects using ctrl+left/ctrl+shift+left/ctrl+backspace to move/select/delete the word to the left.
On more than one occasion, this has introduced a bug: an inadvertent change of a foo>=bar comparison into foo>qux when I edited the variable name on the right hand side.
(And on many occasions it has caused a foo==bar to be inadvertently changed to foo=qux, but at least this one is caught by assignment being disallowed in expressions in GDScript.)
In addition, presumably due the same cause, there is a discrepancy when editing GDScript code between $Node, where the caret/selection is placed before the $ versus %Node, where the caret/selection is placed after the %.

CC @bruvzg

As I can see, most work properly but when there is several ponctuation characters before selection ; exemples :
a==b   =>  (same if first = is + or - instead) double-clicking a willl select =b, a=b is fine though as it select only b then
func(arg)->void;   => double-clicking void willl select >void, func(arg) -> void is fine though as it select only void then
print("test >>word") => (notice the space) double-clicking word willl select >>word ; but should select only word
print("test>>word") => (notice no space) double-clicking word willl select >word ; but should select only word


Removing unused mock-fs library which caused tests to fail

mock-fs will override node's core fs calls which mess up the tests.

Node v6 and v7 pass all tests.
versions 4 and 5 fail due to protractor issues which I'll check in another PR.


feat(sort-objects): add custom-ignore to enable customizable ignore rule

Description
fixes #126
Additional context
Because json-schema does not support function type, it is converted through object.

What is the purpose of this pull request?

[ ] Bug fix
[x] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.
[x] Read contribution guidelines.

The idea for such an option is a good one. But don't you think the customization is overly complicated? Perhaps it would be better to use just variable names instead of functions?

I don't quite understand what you mean. How do variable names solve the problem?

@KID-joker does it allow to exclude the files with specific name? can u prodive an example for it?


Small fix for BLC_07

#212
#288

The idea here was that the button should be smaller on mobile devices

Got it, then need to do it in another way. I will do it on monday.

Updated.


Inlay hints acquire font styling from the character that follows them

I have VSCode theme that puts operators in bold. A closure in my code written as |chunk| has an inferred argument type of Result<Bytes, Error>, rendered in my editor as an inlay hint. Correct behavior would be to render the |'s in bold but not anything in between them. Instead, I get a (correctly) regularly-styled chunk but a  bold : Result<Bytes, Error>| following it.
The type renders correctly (i.e. not in bold) if I write it out explicitly rather than having it filled in as an inlay hint. So this seems to be an issue particular to inlays, and not a problem with any of the patterns in rust.tmGrammar.json.

This is a limitation of the lsp/vscode Inlay hints can only be attaches before or after a character, not in between two characters.

@dfoxfranke does #6382 do anything for you?

@lnicola Confirmed, this fixes it for me. You probably also want textDecoration: "none", to remove underlines.

@dfoxfranke what theme are you using? I'd like to be able to reproduce this to make sure that #6394 didn't regress.

@kjeremy It's a theme I'm developing and it's not released yet, but it will be soon, probably this weekend; after then look for "Lunaria" on the extension marketplace. By the looks of the diff, it won't regress on my theme (which puts operators in bold) but will regress on any theme that underlines operator (I don't know of any that do this).
Regardless, I have to say I really dislike this change. I designed the theme I'm working on specifically with rust-analyzer inlay hints in mind, and it arranges colors in such a way that the inlay hints are already readable and clearly distinct from the surrounding text. Varying the font size will make them less legible and distracting, and if you're going to do this I wish you'd provide a toggle for it.

Thanks for the response.
Please file an issue if you want the size change to be customizable so we
don't lose track of it.
On Wed, Oct 28, 2020, 3:17 PM Daniel Fox Franke<EMAIL_ADDRESS>wrote:

@kjeremy https://github.com/kjeremy It's a theme I'm developing and
it's not released yet, but it will be soon, probably this weekend; after
then look for "Lunaria" on the extension marketplace. By the looks of the
diff, it won't regress on my theme (which puts operators in bold) but will
regress on any theme that underlines operator (I don't know of any that do
this).
Regardless, I have to say I really dislike this change. I designed the
theme I'm working on specifically with rust-analyzer inlay hints in mind,
and it arranges colors in such a way that the inlay hints are already
readable and clearly distinct from the surrounding text. Varying the font
size will make them less legible and distracting, and if you're going to do
this I wish you'd provide a toggle for it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rust-analyzer/rust-analyzer/issues/6380#issuecomment-718152813,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABBACRHGJ2YVM7JBOA6JWU3SNBU4HANCNFSM4TAD6UFA
.


fastapi 内部如何获取uvicorn的端口

Get the port of the service in FastAPI. I expect FastAPI to get its own port, and then periodically update the IP and port of the machine to the database to prevent the service of one machine from being suspended

Please re-ask the question in English.

Thanks for the help @ycd! 🍰
@xujiang1 that would then be outside of FastAPI, if you are running the Uvicorn command from outside, you would have to stop it and start it again with the new host and port. If you run Uvicorn from inside Python, you would also have to, in some way, stop the process and restart it with the new host and port. But in both cases it would really be outside of FastAPI.

Sorry for the long delay! 🙈  I wanted to personally address each issue/PR and they piled up through time, but now I'm checking each one in order.


Cache sharing between instances of ApolloStore

Version
3.8.3
Summary
I have multiple implementations of ApolloClients where I want to share in-memory cache data with. However even after injecting the same NormalizedCacheFactory the entries are not same between the 2 instances.
Steps to reproduce the behavior
A minimalist repro
    val cacheKey = CacheKey("TypeName", "CacheId")
    val reviewFragment = ReviewFragmentImpl()

    val cacheFactory = MemoryCacheFactory(expireAfterMillis = 100000)

    val client1 = ApolloClient.Builder().normalizedCache(cacheFactory)
        .serverUrl("test")
        .build()

    val client2 = ApolloClient.Builder().normalizedCache(cacheFactory)
        .serverUrl("test")
        .build()

    client1.apolloStore.writeFragment(
        reviewFragment,
        cacheKey,
        ReviewFragmentImpl.Data(
            id = "test",
            rating = 3,
            review = "test",
        )
    )

    println(client1.apolloStore.dump())
    println(client2.apolloStore.dump())

Logs
{class com.apollographql.apollo3.cache.normalized.api.internal.OptimisticCache={}, class com.apollographql.apollo3.cache.normalized.api.MemoryCache={TypeName:CacheId=com.apollographql.apollo3.cache.normalized.api.Record@4e2ad3f2}}

{class com.apollographql.apollo3.cache.normalized.api.internal.OptimisticCache={}, class com.apollographql.apollo3.cache.normalized.api.MemoryCache={}}

I was expecting both dumps to be exact same.

Hi!
The reason is you are sharing a cache factory, which will be called to produce a cache instance twice - resulting in 2 separate instances. Instead you can share the ApolloStore which will have a reference to the cache, like so:
  val store = ApolloStore(cacheFactory)

  val client1 = ApolloClient.Builder().store(store)
    .serverUrl("test")
    .build()

  val client2 =ApolloClient.Builder().store(store)
    .serverUrl("test")
    .build()

Verified that the above works for me.


Gem Version Bump?

The version of queue_classic on RubyGems is a little dated, any chance of getting it updated?  Two issues in that version that have bit me are SQL escape problems and calling "SET application_name" by default. Obviously, I can use the Github version, but I prefer the stability of an official release when possible.
Thanks!

Thanks for calling me out on this.
I am working on a 1.X fix release now.
Also, I have a 2.0 release in the works as well. Of course the 1.X fix will be my first priority for release.

version 1.0.1 has been pushed to gemcutter.

Thanks, I know what it's like to keep after a gem. 1.0.1 officially solved my escape issue. Thanks again.


feat(CMSIS,PeriphDrivers): Update SMON Libraries with latest naming convention and design implementation

Description

Update SMON library to use latest naming convention
Adds latest SMON design implementation for MAX32572 and future parts going forward.
Removes repetitive and unnecessary typecasts (and to match type definitions and usage of other libraries).

Checklist Before Requesting Review

[x] PR Title follows correct guidelines.
[x] Description of changes and all other relevant information.
[ ] (Optional) Link any related GitHub issues using a keyword
[ ] (Optional) Provide info on any relevant functional testing/validation.  For API changes or significant features, this is not optional.

/clang-format-run

/clang-format-run

/clang-format-run

/clang-format-run


Data Quality Issues

This epic is for data quality issues with missing data points or data not making it to expected receivers.

Duplicate


SMTC-48: Extracting the semantic type definitions into their own file.

We need to start structuring our semantic definitions a little better and be a bit more formal about the meaning of the various portions of our JSON Schema. The theory behind this can be found in: https://docs.google.com/document/d/1dSgEMsCAV6PnNwRT5SRUEvUJz4rSyNDZ7PkbuYPQvXw/edit#heading=h.e47r8vm6ehr4
This PR refactors the semantic definitions so that we have all types defined in their own file to promote reusability after we break up the models into dedicated files as well.

Dropping this PR in lieu of https://github.com/DataDog/schema/pull/46


137 peer review updates

Updating comments for apply_cut.R, drop_temp_vars.R & process_cut.R as per #137.
Thanks @alanaharris22 for reviewing!

@reesnj - updates all look good to me - thanks Nathan!


Update Modal.js

Change default background color (when transparent prop is set to false) from white to semitransparent black.
#18398 - https://github.com/facebook/react-native/issues/18398

Summary

Changelog

[CATEGORY] [TYPE] - Message
Test Plan

When the transparent prop is off, then the color used shouldn't be using transparency so I'm not sure whether the motivation for this change makes sense. If you'd like us to consider this, could you go into more detail about what prompted this change and what this looks like before/after on devices?

This PR was made in too much hast - sorry about that.
Yours Sincerely
Lasse Nørfeldt
On Mon, May 20, 2019 at 9:44 AM Christoph Nakazawa<EMAIL_ADDRESS>wrote:

When the transparent prop is off, then the color used shouldn't be using
transparency so I'm not sure whether the motivation for this change makes
sense. If you'd like us to consider this, could you go into more detail
about what prompted this change and what this looks like before/after on
devices?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/pull/24949?email_source=notifications&email_token=AAFFXFUYL5TKB5GGMT473B3PWJJENA5CNFSM4HN4QCE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVX6RHQ#issuecomment-493873310,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFFXFWEO2JMDT2YMXRUOOTPWJJENANCNFSM4HN4QCEQ
.


Fixed error 422 on commit. Fixes #128

Would love to merge this, @benweet! Mind rebasing so I can do so? Thanks!

This has been fixed elsewhere. Closing as duplicate.


Add rule for skip_ansible_lint

Add rule for skip_ansible_lint

Not possible according to lint design. And not necessary with our processes.


ENH: Warning when trying to open in Python an image file that doesn't…

… exist
When opening an image file in Python through the itkTemplate class (i.e.
itk.ImageFileReader.New(FileName="my_file.png"), the error message
warns the user that the file does not exist. The error message matches
the error message printed in C++ or when using directly the ImageFileReader
class (i.e. itk.ImageFileReader[ImageType].New(FileName="my_file.png")).

Matches C++ error message.

@cdeepakroy


Add typescript eslitn plugin.

Changes

fixes no unused vars inTS type declarations

Codecov Report

Merging #25 into main will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #25   +/-   ##
=======================================
  Coverage   57.60%   57.60%
=======================================
  Files           5        5
  Lines          92       92
  Branches       13       13
=======================================
  Hits           53       53
  Misses         39       39

Impacted Files
Coverage Δ

packages/core/src/index.ts
84.84% <100.00%> (ø)

packages/core/src/inject-script.ts
6.66% <100.00%> (ø)

packages/react-core/src/scalprum-link.tsx
33.33% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8b8835f...7c5779d. Read the comment docs.


Added the js-display-webpart sample

Q
A

Bug fix?
no

New feature?
no

New sample?
yes

Related issues?
N/A

What's in this Pull Request?
Added a new sample web part that uses JavaScript to display the contents of a list. The web part properties pane provides a DropDown list that displays the lists in the current web. The user can then choose which list to display using this DropDown list.

Hi @nalaswad, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Sorry for the delay, we'll start processing these more detailed next week (24th of Oct forward)

thx nalaswad, we would like to give you credits on this work, so would appreciate if you'd reply on this message after you've updated your name for the GitHub profile. If you want to remain anonymous, that's fine as well. We can also add your company logo on the monthly announcement - See example from October 2016 here - http://dev.office.com/blogs/PnP-October-2016-Release.
Please reply to this discussion your thoughts. Thx.

Hi Vesa,
Thank you for merging my pull request. I have updated my user profile on Github and I would appreciate getting the credit for my work.
Thanks,
Naamat Al-Aswad, P.Eng.
Principal SharePoint Consultant and Architect
Grace Software Consulting


Find a dataset for survival analysis

I got one dataset from Kaggle - https://www.kaggle.com/gilsousa/habermans-survival-data-set
Please check if it is one of the suitable datasets for survival analysis?

Hey @Abhijit2505 the two datasets are perfect, before moving on two the EDA , first point is to check censoring of data. As you had read about how right censored data plays an important role. For survival regression , the two important factors are observation and duration, if you have thses parameters you are good to go.

https://data.world/makeovermonday/2018w40-five-year-cancer-survival-rates-in-america
https://lifelines.readthedocs.io/en/latest/lifelines.datasets.html?highlight=datasets#module-lifelines.datasets

Datasets.zip
This is a good find. Need to review.

https://github.com/vincentarelbundock/Rdatasets/tree/master/csv/survival

https://github.com/CamDavidsonPilon/lifelines/blob/master/lifelines/datasets/dd.csv

I got this awesome Clinical Trial Dataset for the same breast cancer after 10 hours of searching 😪.
I think it is one of the best datasets for survival analysis. Please review it and let me know.

https://github.com/vfa-phuclkh/online_retail_survival_analysis
Another dataset. Case study related.

https://github.com/square/pysurvival/blob/master/pysurvival/datasets/churn.csv


v0.5.1

Trying again; something about the UDST account seems to block "edits by maintainers".
@conda-forge-admin, please rerender

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.


Use static Boost and OpenCV libraries

Can have Two builds, one which uses static libraries and one-click install. One can have a shared library.

I ended up only getting Boost, but that's okay I can switch OpenCV for libpng


vcl: load OpenCL using DL

By default VCL uses OpenCL loading the library statically. If you want to use OpenCL
dynamicly, you can use the -d dlopencl flag.
<!--

Please title your PR as follows: `time: fix foo bar`.
Always start with the thing you are fixing, then describe the fix.
Don't use past tense (e.g. "fixed foo bar").

Explain what your PR does and why.

If you are adding a new function, please document it and add tests:

```
// foo does foo and bar
fn foo() {

// file_test.v
fn test_foo() {
    assert foo() == ...
    ...
}
```

If you are fixing a bug, please add a test that covers it.

Before submitting a PR, please:
  - run the tests with `./bin/test`

I try to process PRs as soon as possible. They should be handled within 24 hours.

Applying labels to PRs is not needed.

Thanks a lot for your contribution!

->

CI is not passing yet, but it is because of an issue with the dependencies, not related with this PR


updated mpg123 to 1.29.3 + rerendered

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

This PR is in response to another package update https://github.com/conda-forge/libsndfile-feedstock/pull/25

This looks to me like it's working now.  It would be great to have a windows build as well, but I have zero experience in that and don't feel sufficiently adventurous to try setting it up right now.
Side question: the license.txt included in the feedstock (BSD3) did not match the package's license (LGPL).  I have left it as is for now, but should these be rectified?  Or is the feedstock license independent of the package license (which is correctly specified in meta.yml)?

Yes, the feedstock license (of this recipe) is always BSD3.
The meta.yaml and license_file specify the license of the package contents.

Would you mind adding your github username to the list of maintainers in extras?

For Windows -- I'd love to have it but I think we can try that in a dedicated follow-up PR.

Agreed.  I brought it up because this update PR is intended to support an update to another package https://github.com/conda-forge/libsndfile-feedstock/pull/25 which does have windows builds, and it would be nice if we could get that all squared away in one shot.  But I agree that this is better done in two steps.
Otherwise, thanks for the comments - I've updated accordingly and this should be ready to go when CI finishes.

Side note: this obviates #20 (I didn't realize it was open when I started this PR).  Not sure if anyone feels like back-filling prior releases #19 #18.

@thomasfillon can you give this a peep when you have a chance?  I think it's ready to go, and it's holding up some other packages.

Checking back on this one - I think it's good to go?

@hbredin @thomasfillon - checking in again, since I think this is merge-able and it's holding up some downstream updates.

Thanks!


[BUG] Thank you bot stopped working

We have a "Thank you  BOT" setup on this repository as a workflow action, but it has stopped working.
The problem seems to be the auth token that expires as it is hardcoded as an environment variable. This ticket should investigate a better way to gather this information and solve this issue without the need to issue a new token.
https://github.com/thisdot/framework.dev/actions/runs/6002702021

This has been fixed now


Add progress bar when updating scene groups

Fixes first part of https://github.com/godotengine/godot/issues/89516

Thanks!


Certificate signed by unknown authority when trying to download dependency using go get

Using go get in my repo produces this error message
package code.cloudfoundry.org/lager: unrecognized import path "code.cloudfoundry.org/lager": https fetch: Get "https://code.cloudfoundry.org/lager?go-get=1": x509: certificate signed by unknown authority

needed to update machine certs

Sorry, user error, still seeing the same issue.

Are you still seeing this issue? I know that there was an error with the cert that was fixed a few weeks back.

I just ran go get again on my repo and I don't see the issue anymore


clean up the database

hey mohamed,
can you check out the merge conflicts in models/topics.js
it won't let me merge it
thanks bro!


Use print() function in both Python 2 and Python 3

Legacy print statements are syntax errors in Python 3 but print() function works as expected in both Python 2 and Python 3.
As discussed at https://github.com/nodejs/build/pull/1836#issuecomment-502066381

LGTM, thanks.


Just open with a blank windows in windows 7

Describe the bug
After install requisites (NET Framework 4.5) and install insomnia. When open it, just has a blank window.
To Reproduce
Steps to reproduce the behavior:

Install it in Windows 7
If you don't have NET Framework 4.5 installed, will ask to install first. So install it
After install insomnia, Open it

Expected behavior
Expect open insomina with its features.
Screenshots

Desktop (please complete the following information):

OS: Windows 7 64 Bits
Installation Method: Last Windows installable binaries
App Version: Insomnia.Core-2021.3.0

Additional context
Nothing more.

Windows 7 reached end of life a year and a half ago (January 14, 2020).
We're looking into this, regardless, but I'd love to have more context on whether there's some use case (perhaps, "enterprise use case") that we should know about.

ng into this, regardless, but I'd love to have more context on whether there's some use case (perhaps, "enterp

Hello, Greetins from Brazil.
Yes it's true, Windows 7 is no longer supported by Microsoft. However there are a lot of computers using the SO yet.
Here on Brazil we have a lot gov agencies that still using it. Brazil has a vast territorial extension with many states, cities and counties. So we have government agencies at county, state and federal levels.
Many of them still use Windows 7, which is my case here at the City Council in my city. And adding up these agencies there are a lot of computers using them.
If this is still the case in Brazil, it will certainly be in other countries with different intensity, and even cases of companies that have not yet migrated due to support for legacy software, etc.

Closing this issue due to lack of activity and age.  IF this is still a problem in the latest Insomnia, feel free to make a new issue.  However, due to the end of life status of windows and the necessity of keeping dependencies in the Insomnia App up to date, I'm not sure there's a safe fix for this problem should it still exist.


Log to console that the server has started

Just curious, would it be a breach of the "only one line" rule if I formatted it like the code below instead? Because it is going to become one long line if we can't insert line breaks :D
var server = app.listen(process.env.PORT || 3000, function () {
console.log("Server started");
}); // now we can close it if needed

haha no I think that's fine! I was wondering the same thing but I think one "line" can be formatted however you'd like!


Minor typo corrections

@lrakai : Thanks for your contribution! The author(s) have been notified to review your proposed change.

verified corrections

#sign-off


Universe levels [WIP]

[x] annotate type codes with levels
[ ] add lvl type (not in any universe)
[ ] get rid of ULvl.magic

(Don't worry about merge conflicts, I'm just playing around and we don't have to merge this right away.)

Once you are done I am interested in treating level parameters as streams.

Once you are done I am interested in trying out "level parameters as monotone streams."

To clarify, this is actually Jon's idea, but I have done the Visualization.

Once you are done I am interested in trying out "level parameters as monotone streams."

To clarify, this is actually @jonsterling's idea, but I have done the Visualization.

to be fair, I had no idea how to execute it or even make it precise ;-)

Once you are done I am interested in trying out "level parameters as monotone streams."

To clarify, this is actually @jonsterling's idea, but I have done the Visualization.

to be fair, I had no idea how to execute it or even make it precise ;-)

If you are not in a hurry to merge this PR, I can temporarily overtake it and unleash the Thought. I guess you can assign this PR to me when you are ready. LOL


Character controlling Water Level

Have a character who can manipulate the water with a fall off strength that depends on the distance from the character and have then fight some fire based enemies

needs #59


Remove poetry from runtime requirements

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

In the accidental-simultaneous PR for simpleconf, we realised that grayskull was being a bit over-eager and poetry wasn't needed as a runtime requirement.

@conda-forge-admin, please rerender


[d3d11] Fix min luminance of HDR Metadata

This should be a multiply instead of a divide. Values are 1/10000th of a nit (0.0001 nit).


⚠ Bofrost.nl has degraded performance

In 670cbed, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 1125 ms

Resolved: Bofrost.nl performance has improved in 62e7aaa.


SentinelOne Phantom app enhancement v2.2.0

Please ensure your pull request (PR) adheres to the following guidelines:

Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

Pull Request Checklist
Please check if your PR fulfills the following requirements:

[x] Testing of all the changes has been performed (for bug fixes / features)
[X] The readme.html has been reviewed and added / updated if needed (for bug fixes / features)
[X] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
[X] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
[X] Verify all checks are passing.
[X] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
[X] Do NOT submit updates to dependencies unless it fixes an issue.
[X] Limit your pull request to one application and submit multiple pull requests if necessary.

Pull Request Type
Please check the type of change your PR introduces:

[X] New App
[X] Bugfix
[X] Feature
[X] Code style update (formatting, renaming)
[X] Refactoring (no functional changes, no api changes)
[X] Documentation
[X] Other (please describe):

Release Notes (REQUIRED)

Provide release notes as part of the PR submission which describes high-level points about the changes for the upcoming GA release.
The following actions are modified so that they work with IP addresses too:

Quarantine device: This command isolate (quarantine) endpoints from the network.
Unquarantine device: This command reconnects to the network at all endpoints.
Scan endpoint: This command runs a Full Disk Scan on Agents that match the filter.

Modified command to support new SentinelOne API:

Block hash: Add a file hash to the global blocklist.

The following new actions are implemented:

AGENT ACTIONS

Abort Scan: Stop a Full Disk Scan on endpoint/agent.
Broadcast Message: Send a message through the Agents that users can see.
Fetch Files (P1): Fetch files from endpoints to analyze the root of threats.
Fetch Firewall Logs: Get Firewall Control events in the local log file.
Fetch Firewall Rules: Fetch firewall rules.
Shutdown: Shutdown endpoint.

DEVICE CONTROL

Get Device Control Events (given a hostname or IP): Get the data of Device Control events on Windows and macOS
endpoints.

Create Firewall Rule: Create a Firewall Control rule.

HASHES

Hash Reputation: Get the reputation of a hash, given the required SHA1.

THREAT NOTES:

Add Note to Multiple: Add a threat note to multiple threats.

THREATS:

Download from cloud: Download threat file from cloud.
Export Mitigation Report: Export the mitigation report of threat.
Export Threat Timeline: Export a threat's timeline.
Export Threats: Export data of threats.
Fetch Threat File: Fetch a file associated with the threat.
Update Threat Analyst Verdict: Change the verdict of a threat, as determined by a Console user.

Update Threat Incident: Update the incident details of a threat.

What is the current behavior? (OPTIONAL)

Describe the current behavior that you are modifying.

What is the new behavior? (OPTIONAL)

Describe the behavior or changes that are being added by this PR.

Other information (OPTIONAL)

Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

Pay close attention to (OPTIONAL)

Any specific code change or test case points which must be addressed/reviewed at the time of GA release.

Screenshots (if relevant)

Thanks for contributing!

Need clarification for the "Static Tests" error.

Looks like the final piece of the puzzle revolves around the actions names (seen in the static test and pasted below). We try to maintain the same action names between all the apps as much as we can, but sometimes it's not entirely possible. Can you please review the names of the actions and let us know if it's possible to change any of them to something that already exists?
"Action abort scan not known. Would url scan be better?",
"Action shutdown endpoint not known.",
"Action broadcast message not known.",
"Action fetch files not known. Would get file be better?",
"Action fetch firewall rules not known.",
"Action fetch firewall logs not known.",
"Action get applications not known. Would list applications be better?",
"Action get cves not known. Would get acls be better?",
"Action get devicecontrol events not known.",
"Action get firewall rules not known. Would list firewall rules be better?",
"Action create firewall rule not known. Would delete firewall rule be better?",
"Action hash reputation not known. Would host reputation be better?",
"Action get threat notes not known.",
"Action add threat note not known.",
"Action export threat timeline not known.",
"Action export mitigation report not known.",
"Action export threats not known.",
"Action fetch threat file not known.",
"Action update threat analystverdict not known.",
"Action get threat timeline not known.",
"Action update threat incident not known.",
"Action download from cloud not known."

@mattsayar-splunk we are getting one error on FIPS compliance. The app does not store any credentials, can we mark it as fips_compliant = true? We don't see the key in any of the other apps.

@abhijeeta-metron The FIPS check is a new feature flag. If you aren't sure of your code's FIPS compliance, it's safe to just declare it "false" and ignore the error. We'll remove this check in the near future

@mattsayar-splunk We have resolved all the errors except these static tests errors we cant resolve.

Hi @abhijeeta-metron, can you please provide me the access to the repo(metron-labs:sentinelone-phantom-2.2.0)?

@haritas-crest we have sent an invite for repo access.

Hi @abhijeeta-metron
While testing for the negative scenarios, we observed that the 'export threats' action was passing with invalid parameter values. To handle this case, we have added a check for the ‘-1’ string value after the get_agent_id method call. Similarly, we have added the check for '-1' string in other actions as well.

Action result status before adding -1 check:

Action result status after adding -1 check:

Please let us know if you have any queries regarding this change.

@haritas-crest Sure, I will check. Thanks

@haritas-crest we are ok with the changes


Add waitfor RPC methods

This PR is just in case you @nopara73 decide to go with this approach. I added the methods here because NBitcoin won't accept this methods in its codebase.

Helping review and testing of https://github.com/bitcoin/bitcoin/pull/7949 would be useful.


UI improvements 2

Proposals:

[x] remove background behind the table
[x] remove links to the same page
[ ] sum of capacities is little bit misleading since we fetch only upcoming n days
[x] format date
[x] add link to reservatic watchdogs
[x] replace Úvodní strana by the web name
[ ] merge both pages to have the table on the main page?
[x] use table-condensed

See my PR

See my PR


Add an initial benchmark for the tx-parser crate. (#406) r=nalexander

This is an example first benchmark for the tx-parser.  It can be run with:
cargo bench --package mentat_tx_parser
To take measurements and print it in a nicer format I used this command:
for i in `seq 1 5`; do echo '---'; cargo bench --package mentat_tx_parser 2> /dev/null | sed -n -e 's/test \(.*\)\( ... bench: \)/\1/p'; done;
Here are my results for that locally:
bench_parse1      7,462 ns/iter (+/- 7,514)
bench_parse2    384,068 ns/iter (+/- 48,037)
---
bench_parse1      7,171 ns/iter (+/- 1,431)
bench_parse2    381,971 ns/iter (+/- 59,735)
---
bench_parse1      6,860 ns/iter (+/- 1,742)
bench_parse2    352,454 ns/iter (+/- 177,286)
---
bench_parse1      6,787 ns/iter (+/- 3,107)
bench_parse2    348,041 ns/iter (+/- 146,625)
---
bench_parse1      7,113 ns/iter (+/- 961)
bench_parse2    376,373 ns/iter (+/- 52,412)

lol, I think that script doesn't like zsh:
$ for i in `seq 1 5`; do echo '---'; cargo bench --package mentat_tx_parser 2> /dev/null | sed -n -e 's/test \(.*\)\( ... bench: \)/\1/p'; done;
---
---
---
---
---

Oh, it fails 'cos I'm not using Nightly.

Older dual-core 13" rMBP:
test bench_parse1 ... bench:       8,959 ns/iter (+/- 1,450)
test bench_parse2 ... bench:     594,676 ns/iter (+/- 66,751)
---
test bench_parse1 ... bench:       8,634 ns/iter (+/- 4,373)
test bench_parse2 ... bench:     575,320 ns/iter (+/- 71,528)


Iss169

gm1.conf .... gm7.conf

This issue is for user guide changes. Please open up new issue and new branch for .cpp changes.


http response from mongodb2 node not working

I assume that you closed the issue because you found a solution - right?
On 14 May 2016 at 12:54, guitar-hero<EMAIL_ADDRESS>wrote:

Closed #6 https://github.com/ozomer/node-red-contrib-mongodb2/issues/6.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/ozomer/node-red-contrib-mongodb2/issues/6#event-660678433

Yes thats right. Is there a way to delete it?
The problem was me doing something minor different...
Von meinem Windows Phone gesendet

Von: Oren<EMAIL_ADDRESS>Gesendet: 14.05.2016 11:56
An<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS>State<EMAIL_ADDRESS>Betreff: Re: [ozomer/node-red-contrib-mongodb2] http response from mongodb2 node not working (#6)
I assume that you closed the issue because you found a solution - right?
On 14 May 2016 at 12:54, guitar-hero<EMAIL_ADDRESS>wrote:

Closed #6 https://github.com/ozomer/node-red-contrib-mongodb2/issues/6.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/ozomer/node-red-contrib-mongodb2/issues/6#event-660678433

You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub:
https://github.com/ozomer/node-red-contrib-mongodb2/issues/6#issuecomment-219211686

I don't know if you can delete it. Don't worry, closing the issue is fine.
On May 14, 2016 1:05 PM, "guitar-hero"<EMAIL_ADDRESS>wrote:
Yes thats right. Is there a way to delete it?
The problem was me doing something minor different...
Von meinem Windows Phone gesendet

Von: Oren<EMAIL_ADDRESS>Gesendet: 14.05.2016 11:56
An: ozomer/node-red-contrib-mongodb2<mailto:
<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS>State change<mailto:
<EMAIL_ADDRESS>Betreff: Re: [ozomer/node-red-contrib-mongodb2] http response from mongodb2
node not working (#6)
I assume that you closed the issue because you found a solution - right?
On 14 May 2016 at 12:54, guitar-hero<EMAIL_ADDRESS>wrote:

Closed #6 https://github.com/ozomer/node-red-contrib-mongodb2/issues/6.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
<
https://github.com/ozomer/node-red-contrib-mongodb2/issues/6#event-660678433

You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub:
https://github.com/ozomer/node-red-contrib-mongodb2/issues/6#issuecomment-219211686
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/ozomer/node-red-contrib-mongodb2/issues/6#issuecomment-219212038


[Windows] Rename PKEY_Device_FriendlyName to avoid duplicate symbols with newer MinGW SDKs.

Renames CLSID constant to avoid conflicts, since it is defined only in some SDK versions (same way we handle CLSID for DX12).
Fixes https://github.com/godotengine/godot/issues/97882

Also affected here.
Can we please get this merged since it is approved?

Should fix https://github.com/godotengine/godot/issues/98822 as well. Waiting for it to compile fork with double precision.


dependency old?

When I build my flutter app, I got this error.

What went wrong:
Execution failed for task ':flutter_logs:generateReleaseRFile'.

Could not resolve all files for configuration ':flutter_logs:releaseCompileClasspath'.
Could not find com.github.umair13adil:RxLogs:1.0.18.
Required by:
project :flutter_logs

I can confirm the com.github.umair13adil:RxLogs has v1.0.18, as you know. ref) https://github.com/umair13adil/RxLogs/tree/v1.0.18
Could you take a look of this build.gradle? https://github.com/umair13adil/flutter_logs/blob/master/android/build.gradle#L50
Wonder if 1.0.18 fine or not, is it v1.0.18?

Started to get this issue as well in my github actions pipeline for api level 31

same issue here, any work around?

same here gitlab ci/cd pipeline, also even weirder (to me) it seems intermittent

flutter_logs in my app still try to resolve 1.0.18... Need a version update to 2.1.11?
I think your fix(https://github.com/neiljaywarner/flutter_logs/commit/c7c69f10829558e9baa2f723597cc9b304746b2b) is fine, but it doesn't fix my app... Hmm

Does pubspeck.lock say the new version number?
I had a bit of that at first which is why I bumped the version but yeah a
full release would be great
....sent from my phone
On Thu, Sep 7, 2023, 11:58 PM leejonggun @.***> wrote:

flutter_logs in my app still try to resolve 1.0.18... Need a version
update to 2.1.11?
I think your @.***
https://github.com/neiljaywarner/flutter_logs/commit/c7c69f10829558e9baa2f723597cc9b304746b2b)
is fine, but it doesn't fix my app... Hmm
—
Reply to this email directly, view it on GitHub
https://github.com/umair13adil/flutter_logs/issues/55#issuecomment-1711075093,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXBGYPEFAF2RO3ZVXXAZC3XZKQVTANCNFSM6AAAAAA4OSG5AA
.
You are receiving this because you commented.Message ID:
@.***>

PR57(https://github.com/umair13adil/flutter_logs/pull/57) is merged. my app build success! :) Thank you.


RocksDB Options are not changing

I am trying out different options for RocksDB in the configuration file. For example:
write_buffer_size=128MB;max_write_buffer_number=19;min_write_buffer_number_to_merge=1;compression=kSnappyCompression;bloom_locality=1;
but I do not see them getting passed to RocksDB. For example max_write_buffer_number remains 6 whatever the value I choose. It seems it always defaults to the same values. Same for min_write_buffer_number_to_merge which always defaults to 2.
[11795] 03-02 21:58:51,218 INFO [RocksDB]       Options.write_buffer_size: 134217728 [11795] 03-02 21:58:51,218 INFO [RocksDB] Options.max_write_buffer_number: 6 [11795] 03-02 21:58:51,218 INFO [RocksDB]       Options.compression[0]: NoCompression [11795] 03-02 21:58:51,218 INFO [RocksDB]       Options.compression[1]: NoCompression [11795] 03-02 21:58:51,218 INFO [RocksDB]       Options.compression[2]: Snappy [11795] 03-02 21:58:51,218 INFO [RocksDB]       Options.compression[3]: Snappy [11795] 03-02 21:58:51,218 INFO [RocksDB]       Options.compression[4]: Snappy [11795] 03-02 21:58:51,218 INFO [RocksDB]       Options.compression[5]: Snappy [11795] 03-02 21:58:51,218 INFO [RocksDB]       Options.compression[6]: Snappy [11795] 03-02 21:58:51,218 INFO [RocksDB]                 Options.bottommost_compression: Disabled [11795] 03-02 21:58:51,218 INFO [RocksDB]      Options.prefix_extractor: ardb.prefix_extractor [11795] 03-02 21:58:51,218 INFO [RocksDB]  Options.memtable_insert_with_hint_prefix_extractor: nullptr [11795] 03-02 21:58:51,218 INFO [RocksDB]            Options.num_levels: 7 [11795] 03-02 21:58:51,218 INFO [RocksDB]       Options.min_write_buffer_number_to_merge: 2 [11795] 03-02 21:58:51,218 INFO [RocksDB]    Options.max_write_buffer_number_to_maintain: 0 [11795] 03-02 21:58:51,218 INFO [RocksDB]           Options.compression_opts.window_bits: -14 [11795] 03-02 21:58:51,218 INFO [RocksDB]                 Options.compression_opts.level: -1 [11795] 03-02 21:58:51,218 INFO [RocksDB]              Options.compression_opts.strategy: 0 [11795] 03-02 21:58:51,218 INFO [RocksDB]        Options.compression_opts.max_dict_bytes: 0 [11795] 03-02 21:58:51,218 INFO [RocksDB]     Options.level0_file_num_compaction_trigger: 2 [11795] 03-02 21:58:51,218 INFO [RocksDB]         Options.level0_slowdown_writes_trigger: 20 [11795] 03-02 21:58:51,218 INFO [RocksDB]             Options.level0_stop_writes_trigger: 40 [11795] 03-02 21:58:51,218 INFO [RocksDB]                  Options.target_file_size_base: 67108864 [11795] 03-02 21:58:51,218 INFO [RocksDB]            Options.target_file_size_multiplier: 1 [11795] 03-02 21:58:51,218 INFO [RocksDB]               Options.max_bytes_for_level_base: 536870912 [11795] 03-02 21:58:51,218 INFO [RocksDB]Options.level_compaction_dynamic_level_bytes: 0 [11795] 03-02 21:58:51,218 INFO [RocksDB]         Options.max_bytes_for_level_multiplier: 10.000000 [11795] 03-02 21:58:51,218 INFO [RocksDB]Options.max_bytes_for_level_multiplier_addtl[0]: 1 [11795] 03-02 21:58:51,218 INFO [RocksDB]Options.max_bytes_for_level_multiplier_addtl[1]: 1 [11795] 03-02 21:58:51,218 INFO [RocksDB]Options.max_bytes_for_level_multiplier_addtl[2]: 1
Am I doing something wrong?

ColumnFamilyOptions::OptimizeLevelStyleCompaction is called after creating options  from string, which would modify max_write_buffer_number to 6.
https://github.com/facebook/rocksdb/blob/master/util/options.cc#L501

Does this mean that we cannot modify the max_write_buffer_number parameter at all (?) because this is the behavior I am seeing...

@ipapapa  maybe we can add another option  to enable/disable the optimize operations.

@yinqiwen RocksDB allows for different optimized configurations based on the compaction strategy.
ColumnFamilyOptions::OptimizeForPointLookup
ColumnFamilyOptions::OptimizeLevelStyleCompaction
ColumnFamilyOptions::OptimizeUniversalStyleCompaction

I assume these could be exposed in the ardb.conf and bypass the default ones.

@yinqiwen can you make the changes to accept the options from the config file?

@yinqiwen is this issue fixed? I'm having the same problem: I pass an ardb.conf file, which has rocksdb.options, and the ardb-server ignore the rocksdb options. It works, for example, to change the ardb's port. I have tried both with your sample file and with other values, but they are always ignored. If that config does not do nothing, which is its purpose?

Ok, I have found the problem: https://github.com/yinqiwen/ardb/blob/master/ardb.conf#L43-L50

What do you suggest to solve this pb?
Thanks


Minify dist file

Is there any specific reason not to minify dist/datime.js?
If you guys want it, I can send a PR to do it.
Great module, by the way.

I think it's not that necessary to minify them because most of the developers have their own build tool, which not only minify js but concat each modules into one js file.

Well, we could have both files, actually. A minified and a not minified one - which is pretty common.
But that's up to you.

It is good to have both :+1:

I'll send a PR soon.

Fixed in 5.2.0.


[placeholder] Display ownership info in task-group "Info"

We are currently not showing any kind of single-user-ownership information about task groups, see e.g.

The only information we have is about user-group ownership, as in

Is this OK?
Or should we move to "every user has a unique username attribute and when we show info about a task group we also mention who owns it"?

This is great and the amount of detail is totally sufficient for the beta launch! Very nice to make the task list more compact & structured this way.

Or should we move to "every user has a unique username attribute and when we show info about a task group we also mention who owns it"?

In the context of "should we use usernames more broadly across the interface, sure, why not, we can also add them here. I don't see as something critical we need to have right now though.
Instead, I think the next step will need to be more novice-user focused work on deciding which of the current information they care about most, how we improve on that metadata, how we display it in an accessible manner etc.
Some of the things I'd be thinking about here:

Regular users will not care about the command strings, the task meta, the arg schema version, but they will care about the Docs info (especially if we make them more user-facing) & the docs link
Additionally, users will care to see some of the new metadata that now gets added to tasks
If we have some top-level package description, that would be useful to have & show

Most of those thoughts should be tackled later. One quick fix we could add: Can we make Command non parallel & Command non parallel expandable like Initialisation Meta and others?

In that context: If the task list becomes something more useful to regular users, which is more browsable and useful in discovery, as well as more compact thanks to the grouping by packages, we may consider putting it on top of the page and adding the task collection below (/ accessible via button or so). Most users won't collect new packages after all


[Feedback 0.35.0-RC]: Connecting after rebooting of the device produces a java.lang.IllegalStateException: Scope is not active

We have the following connect code in our codebase:
suspend fun connectToPeripheral(): Either<Failure, Unit> {
        return try {
            Timber.d("[BLE Communication]: Connecting to peripheral...")
            peripheral.connect()
            Either.Right(Unit)
        } catch (e: IllegalStateException) {
            ...
            Either.Left(BluetoothError.IllegalStateError())
        }
        ...
        ...
}

And the following flow:

Connect to a device
Write something to that device
Reboot the device and disconnect from it
Reconnect to the device after it has booted again
Get some information from that device

This flow works correctly with 0.34.0. The problem is that with 0.35.0-RC the connect() function throws an IllegalStateException:
java.lang.IllegalStateException: Scope is not active
I'm not sure what "Scope is not active" means here but ideally we would like for it to work as it did with 0.34.0 without having to re-write our codebase.

Thank you. Please ping me here when it's ready to test it again.

@PavlosTze The "scope is not active" exception message occurs when the peripheral's scope is no longer active but an operation was attempted using the scope (in this case, connect) — providing a better failure message will be tracked via #798.
This can happen if the call to connect was preceded by a call to peripheral.cancel().
Being that the peripheral's coroutine scope is a supervisor scope, it shouldn't shutdown unless explicitly instructed to do so, but there may be a bug.
I've added logging for when the peripheral's scope shuts down, so that we can try and find the cause; please try the following snapshot:
repositories {
    maven("https://oss.sonatype.org/content/repositories/snapshots")
}

dependencies {
    implementation("com.juul.kable:core:0.35.0-rc+logging-SNAPSHOT")
}

When reproducing, be sure that the peripheral is configured with logging enabled.
Then look for the following log messages (and associated stacktraces):

"Supervisor job ended"
"Supervisor job received exception"

I just did that, you can find the logs below. Also, based on your message, I removed the peripheral.cancel() from my disconnection code, and it worked perfectly, just like before. So I guess this might be an issue on my side, when I would expect a new automatic re-connection immediately after disconnecting, I should handle it in a better way and not call the cancel() function?
2024-11-26 10:04:01.236 25745-26018 BluetoothC...ionManager com.weatherxm.app                    D  [BLE Communication]: AT+BAND=5
2024-11-26 10:04:01.239 25745-26018 Kable/Peripheral        com.weatherxm.app                    D  XX:XX:XX:XX:36:7A write
                                                                                service: 49535354-fe7d-4ae5-8fa9-9fafd205e455
                                                                                characteristic: 49535354-8841-43f4-a8d4-ecbe34729bb3
                                                                                writeType: WithoutResponse
                                                                                data: 41 54 2B 42 41 4E 44 3D 35 0D 0A
2024-11-26 10:04:01.249 25745-26560 Kable/Callback          com.weatherxm.app                    D  F9:F8:40:77:36:7A onCharacteristicWrite
                                                                                service: 49535354-fe7d-4ae5-8fa9-9fafd205e455
                                                                                characteristic: 49535354-8841-43f4-a8d4-ecbe34729bb3
                                                                                status: GATT_SUCCESS(0)
2024-11-26 10:04:01.251 25745-26026 Kable/Peripheral        com.weatherxm.app                    D  XX:XX:XX:XX:36:7A Starting observation
                                                                                service: 49535354-fe7d-4ae5-8fa9-9fafd205e455
                                                                                characteristic: 49535354-1e4d-4bd9-ba61-23c647249616
2024-11-26 10:04:01.251 25745-26026 Kable/Peripheral        com.weatherxm.app                    V  XX:XX:XX:XX:36:7A setCharacteristicNotification
                                                                                service: 49535354-fe7d-4ae5-8fa9-9fafd205e455
                                                                                characteristic: 49535354-1e4d-4bd9-ba61-23c647249616
                                                                                value: true
2024-11-26 10:04:01.252 25745-26026 BluetoothGatt           com.weatherxm.app                    D  setCharacteristicNotification() - uuid: 49535354-1e4d-4bd9-ba61-23c647249616 enable: true
2024-11-26 10:04:01.253 25745-26026 Kable/Peripheral        com.weatherxm.app                    V  XX:XX:XX:XX:36:7A Writing ENABLE_NOTIFICATION_VALUE to CCCD
                                                                                service: 49535354-fe7d-4ae5-8fa9-9fafd205e455
                                                                                characteristic: 49535354-1e4d-4bd9-ba61-23c647249616
                                                                                descriptor: 00002902-0000-1000-8000-00805f9b34fb
2024-11-26 10:04:01.254 25745-26026 Kable/Peripheral        com.weatherxm.app                    D  XX:XX:XX:XX:36:7A write
                                                                                service: 49535354-fe7d-4ae5-8fa9-9fafd205e455
                                                                                characteristic: 49535354-1e4d-4bd9-ba61-23c647249616
                                                                                descriptor: 00002902-0000-1000-8000-00805f9b34fb
                                                                                data: 01 00
2024-11-26 10:04:01.384 25745-26560 Kable/Callback          com.weatherxm.app                    D  F9:F8:40:77:36:7A onCharacteristicChanged
                                                                                service: 49535354-fe7d-4ae5-8fa9-9fafd205e455
                                                                                characteristic: 49535354-1e4d-4bd9-ba61-23c647249616
                                                                                data: 0D 0A 4F 4B 0D 0A
2024-11-26 10:04:01.385 25745-26560 Kable/Callback          com.weatherxm.app                    D  F9:F8:40:77:36:7A onDescriptorWrite
                                                                                service: 49535354-fe7d-4ae5-8fa9-9fafd205e455
                                                                                characteristic: 49535354-1e4d-4bd9-ba61-23c647249616
                                                                                descriptor: 00002902-0000-1000-8000-00805f9b34fb
                                                                                status: GATT_SUCCESS(0)
2024-11-26 10:04:01.388 25745-26026 Kable/Peripheral        com.weatherxm.app                    D  XX:XX:XX:XX:36:7A Stopping observation
                                                                                service: 49535354-fe7d-4ae5-8fa9-9fafd205e455
                                                                                characteristic: 49535354-1e4d-4bd9-ba61-23c647249616
2024-11-26 10:04:01.389 25745-26026 Kable/Peripheral        com.weatherxm.app                    V  XX:XX:XX:XX:36:7A Writing DISABLE_NOTIFICATION_VALUE to CCCD
                                                                                service: 49535354-fe7d-4ae5-8fa9-9fafd205e455
                                                                                characteristic: 49535354-1e4d-4bd9-ba61-23c647249616
                                                                                descriptor: 00002902-0000-1000-8000-00805f9b34fb
2024-11-26 10:04:01.389 25745-26026 Kable/Peripheral        com.weatherxm.app                    D  XX:XX:XX:XX:36:7A write
                                                                                service: 49535354-fe7d-4ae5-8fa9-9fafd205e455
                                                                                characteristic: 49535354-1e4d-4bd9-ba61-23c647249616
                                                                                descriptor: 00002902-0000-1000-8000-00805f9b34fb
                                                                                data: 00 00
2024-11-26 10:04:01.629 25745-26560 Kable/Callback          com.weatherxm.app                    D  F9:F8:40:77:36:7A onDescriptorWrite
                                                                                service: 49535354-fe7d-4ae5-8fa9-9fafd205e455
                                                                                characteristic: 49535354-1e4d-4bd9-ba61-23c647249616
                                                                                descriptor: 00002902-0000-1000-8000-00805f9b34fb
                                                                                status: GATT_SUCCESS(0)
2024-11-26 10:04:01.633 25745-26023 Kable/Peripheral        com.weatherxm.app                    V  XX:XX:XX:XX:36:7A setCharacteristicNotification
                                                                                service: 49535354-fe7d-4ae5-8fa9-9fafd205e455
                                                                                characteristic: 49535354-1e4d-4bd9-ba61-23c647249616
                                                                                value: false
2024-11-26 10:04:01.634 25745-26023 BluetoothGatt           com.weatherxm.app                    D  setCharacteristicNotification() - uuid: 49535354-1e4d-4bd9-ba61-23c647249616 enable: false
2024-11-26 10:04:01.637 25745-26023 BluetoothC...tATCommand com.weatherxm.app                    D  [BLE Communication]: Success: true
2024-11-26 10:04:01.643 25745-26026 BluetoothC...ionManager com.weatherxm.app                    D  [BLE Communication]: ATZ
2024-11-26 10:04:01.644 25745-26026 Kable/Peripheral        com.weatherxm.app                    D  XX:XX:XX:XX:36:7A write
                                                                                service: 49535354-fe7d-4ae5-8fa9-9fafd205e455
                                                                                characteristic: 49535354-8841-43f4-a8d4-ecbe34729bb3
                                                                                writeType: WithoutResponse
                                                                                data: 41 54 5A 0D 0A
2024-11-26 10:04:01.649 25745-26560 Kable/Callback          com.weatherxm.app                    D  F9:F8:40:77:36:7A onCharacteristicWrite
                                                                                service: 49535354-fe7d-4ae5-8fa9-9fafd205e455
                                                                                characteristic: 49535354-8841-43f4-a8d4-ecbe34729bb3
                                                                                status: GATT_SUCCESS(0)
2024-11-26 10:04:01.653 25745-26022 Kable/Peripheral        com.weatherxm.app                    D  XX:XX:XX:XX:36:7A Starting observation
                                                                                service: 49535354-fe7d-4ae5-8fa9-9fafd205e455
                                                                                characteristic: 49535354-1e4d-4bd9-ba61-23c647249616
2024-11-26 10:04:01.654 25745-26026 BluetoothC...ionManager com.weatherxm.app                    D  [BLE Communication]: Disconnecting from peripheral...
2024-11-26 10:04:01.654 25745-26022 Kable/Peripheral        com.weatherxm.app                    V  XX:XX:XX:XX:36:7A setCharacteristicNotification
                                                                                service: 49535354-fe7d-4ae5-8fa9-9fafd205e455
                                                                                characteristic: 49535354-1e4d-4bd9-ba61-23c647249616
                                                                                value: true
2024-11-26 10:04:01.655 25745-26022 BluetoothGatt           com.weatherxm.app                    D  setCharacteristicNotification() - uuid: 49535354-1e4d-4bd9-ba61-23c647249616 enable: true
2024-11-26 10:04:01.658 25745-26022 Kable/Peripheral        com.weatherxm.app                    V  XX:XX:XX:XX:36:7A Writing ENABLE_NOTIFICATION_VALUE to CCCD
                                                                                service: 49535354-fe7d-4ae5-8fa9-9fafd205e455
                                                                                characteristic: 49535354-1e4d-4bd9-ba61-23c647249616
                                                                                descriptor: 00002902-0000-1000-8000-00805f9b34fb
2024-11-26 10:04:01.658 25745-26022 Kable/Peripheral        com.weatherxm.app                    D  XX:XX:XX:XX:36:7A write
                                                                                service: 49535354-fe7d-4ae5-8fa9-9fafd205e455
                                                                                characteristic: 49535354-1e4d-4bd9-ba61-23c647249616
                                                                                descriptor: 00002902-0000-1000-8000-00805f9b34fb
                                                                                data: 01 00
2024-11-26 10:04:01.662 25745-26023 Kable/Connection        com.weatherxm.app                    V  XX:XX:XX:XX:36:7A Waiting for connection tasks to complete
2024-11-26 10:04:01.662 25745-26023 Kable/Connection        com.weatherxm.app                    D  XX:XX:XX:XX:36:7A Disconnecting
2024-11-26 10:04:01.662 25745-26023 BluetoothGatt           com.weatherxm.app                    D  cancelOpen() - device: XX:XX:XX:XX:36:7A
2024-11-26 10:04:01.685 25745-26453 BluetoothGatt           com.weatherxm.app                    D  onClientConnectionState() - status=0 clientIf=6 device=XX:XX:XX:XX:36:7A
2024-11-26 10:04:01.690 25745-26560 Kable/Callback          com.weatherxm.app                    D  F9:F8:40:77:36:7A onConnectionStateChange
                                                                                status: Success
                                                                                newState: Disconnected
2024-11-26 10:04:01.692 25745-26023 Kable/Connection        com.weatherxm.app                    I  XX:XX:XX:XX:36:7A Disconnected
2024-11-26 10:04:01.694 25745-26023 Kable/Connection        com.weatherxm.app                    D  XX:XX:XX:XX:36:7A Closing (Ask Gemini)
                                                                                java.util.concurrent.CancellationException: com.juul.kable.NotConnectedException: Disconnect requested
                                                                                at com.juul.kable.BluetoothDeviceAndroidPeripheral.disconnect(BluetoothDeviceAndroidPeripheral.kt:152)
                                                                                at com.weatherxm.data.bluetooth.BluetoothConnectionManager.disconnectFromPeripheral(BluetoothConnectionManager.kt:176)
                                                                                at com.weatherxm.data.datasource.bluetooth.BluetoothConnectionDataSourceImpl.disconnectFromPeripheral(BluetoothConnectionDataSourceImpl.kt:57)
                                                                                at com.weatherxm.data.repository.bluetooth.BluetoothConnectionRepositoryImpl.reboot(BluetoothConnectionRepositoryImpl.kt:57)
                                                                                at com.weatherxm.data.repository.bluetooth.BluetoothConnectionRepositoryImpl$reboot$1.invokeSuspend(Unknown Source:20)
                                                                                at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
                                                                                at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:101)
                                                                                at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:113)
                                                                                at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89)
                                                                                at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:589)
                                                                                at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:823)
                                                                                at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:720)
                                                                                at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:707)
                                                                                Caused by: com.juul.kable.NotConnectedException: Disconnect requested
                                                                                at com.juul.kable.BluetoothDeviceAndroidPeripheral.disconnect(BluetoothDeviceAndroidPeripheral.kt:152)
                                                                                at com.weatherxm.data.bluetooth.BluetoothConnectionManager.disconnectFromPeripheral(BluetoothConnectionManager.kt:176)
                                                                                at com.weatherxm.data.datasource.bluetooth.BluetoothConnectionDataSourceImpl.disconnectFromPeripheral(BluetoothConnectionDataSourceImpl.kt:57)
                                                                                at com.weatherxm.data.repository.bluetooth.BluetoothConnectionRepositoryImpl.reboot(BluetoothConnectionRepositoryImpl.kt:57)
                                                                                at com.weatherxm.data.repository.bluetooth.BluetoothConnectionRepositoryImpl$reboot$1.invokeSuspend(Unknown Source:20)
                                                                                at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
                                                                                at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:101)
                                                                                at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:113)
                                                                                at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89)
                                                                                at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:589)
                                                                                at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:823)
                                                                                at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:720)
                                                                                at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:707)
2024-11-26 10:04:01.694 25745-26023 BluetoothGatt           com.weatherxm.app                    D  close()
2024-11-26 10:04:01.697 25745-26023 BluetoothGatt           com.weatherxm.app                    D  unregisterApp() - mClientIf=6
2024-11-26 10:04:01.700 25745-26023 Kable/Connection        com.weatherxm.app                    I  XX:XX:XX:XX:36:7A Closed
2024-11-26 10:04:01.704 25745-26026 Kable/Peripheral        com.weatherxm.app                    D  XX:XX:XX:XX:36:7A Supervisor job ended
                                                                                kotlinx.coroutines.JobCancellationException: Job was cancelled; job=SupervisorJobImpl{Cancelled}@23149ef
2024-11-26 10:04:11.739 25745-26018 BluetoothC...ionManager com.weatherxm.app                    D  [BLE Communication]: Connecting to peripheral...
2024-11-26 10:04:11.747 25745-26018 BluetoothC...ionManager com.weatherxm.app                    E  Connection to peripheral failed with IllegalStateException (Ask Gemini)
                                                                                java.lang.IllegalStateException: Scope is not active
                                                                                at com.juul.kable.SharedRepeatableAction.create(SharedRepeatableAction.kt:80)
                                                                                at com.juul.kable.SharedRepeatableAction.getOrCreate(SharedRepeatableAction.kt:76)
                                                                                at com.juul.kable.SharedRepeatableAction.await(SharedRepeatableAction.kt:89)
                                                                                at com.juul.kable.BluetoothDeviceAndroidPeripheral.connect(BluetoothDeviceAndroidPeripheral.kt:148)
                                                                                at com.weatherxm.data.bluetooth.BluetoothConnectionManager.connectToPeripheral(BluetoothConnectionManager.kt:207)
                                                                                at com.weatherxm.data.datasource.bluetooth.BluetoothConnectionDataSourceImpl.connectToPeripheral(BluetoothConnectionDataSourceImpl.kt:44)
                                                                                at com.weatherxm.data.datasource.bluetooth.BluetoothConnectionDataSource$DefaultImpls.connectToPeripheral$default(BluetoothConnectionDataSource.kt:16)
                                                                                at com.weatherxm.data.repository.bluetooth.BluetoothConnectionRepositoryImpl.connectToPeripheral(BluetoothConnectionRepositoryImpl.kt:27)
                                                                                at com.weatherxm.usecases.BluetoothConnectionUseCaseImpl.connectToPeripheral(BluetoothConnectionUseCaseImpl.kt:27)
                                                                                at com.weatherxm.ui.components.BluetoothHeliumViewModel.connect(BluetoothHeliumViewModel.kt:105)
                                                                                at com.weatherxm.ui.claimdevice.helium.result.ClaimHeliumResultViewModel.access$connect$s-1739547676(ClaimHeliumResultViewModel.kt:23)
                                                                                at com.weatherxm.ui.claimdevice.helium.result.ClaimHeliumResultViewModel$connectToPeripheral$1.invokeSuspend(ClaimHeliumResultViewModel.kt:111)
                                                                                at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
                                                                                at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:101)
                                                                                at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:113)
                                                                                at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89)
                                                                                at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:589)
                                                                                at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:823)
                                                                                at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:720)
                                                                                at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:707)
2024-11-26 10:04:22.432 25745-25745 ViewRootIm...mActivity] com.weatherxm.app

when I would expect a new automatic re-connection immediately after disconnecting, I should handle it in a better way and not call the cancel() function?

Is it possible to share a snippet of your reconnection code, and I can give you feedback on it.
Feel free to DM me on kotlinlang Slack (@travis) if you'd prefer to share the code there.

when I would expect a new automatic re-connection immediately after disconnecting, I should handle it in a better way and not call the cancel() function?

Is it possible to share a snippet of your reconnection code, and I can give you feedback on it. Feel free to DM me on kotlinlang Slack (@travis) if you'd prefer to share the code there.

Hey, sorry for the late reply. Our codebase is open source @ WeatherXM/wxm-android so I've no issues sharing it here.
Regarding the flow:
Disconnection Code
It starts in the ViewModel at function reboot ➡➡ UseCase ➡➡ Repository (if you check the code here you will see that we need a custom fix of disconnecting from the peripheral also at this point) ➡➡ DataSource (Reboot & Disconnect) ➡➡ Bluetooth Connection Manager (the problem is here at the disconnectFromPeripheral() where we do peripheral.cancel())
Reconnection Code
It starts in the ViewModel at function connectToPeripheral ➡➡ UseCase ➡➡ Repository➡➡ DataSource ➡➡ Bluetooth Connection Manager (the problem is here at the connectToPeripheral() which throws the above IllegalStateException: java.lang.IllegalStateException: Scope is not active exception)

Looking through the WeatherXM/wxm-android code (if I'm understanding correctly), you only manage a single peripheral at a time (i.e. you can't connect to multiple weather stations concurrently)? If that is the case, then I would recommend only calling Peripheral.cancel() when the "managed" peripheral is changing. Essentially, just adding peripheral?.cancel() to the beginning of your BluetoothConnectionManager.setPeripheral function and removing your peripheral.cancel() call from your BluetoothConnectionManager.disconnectFromPeripheral function.
Basically, you should only cancel a peripheral when you are done using it. Peripheral.cancel is synonymous with disposing it.
Let me know if that seems feasible / works.

Yup you are 100% correct. I just tested it and it worked like a charm. Therefore I'm considering this issue as a bug in our side, so I'm closing it. Thank you very much for your help!


How to display tags in lithium theme ?

Hi, I am unable to display the tags using lithium theme. Could you please give some guidance on displaying the tags and then eventually displaying all the posts based on tags ? Is this possible on hugo-lithium-theme ?

@janeshdev Sorry for the delay. Hugo theme currently doesn't support taxonomies and I don't have a plan to add them at this point in time.


Can gaia version in tutorial be updated?

Context
I'm going through https://hermes.informal.systems/tutorials/pre-requisites/gaia.html
Problem
I have Golang 1.21.1 installed locally. The docs explain using Gaia v9.0.3 which fails to install locally because it depends on Golang 1.18.
HEAD is now at 05b6b87d3 update changelog for rc 2 (backport #2421) (#2422)
$ make install
ERROR: Go version 1.18 is required for HEAD-05b6b87d3c9121e933eab437772ea56f33ae268f of Gaia.
exit 1
make: *** [check_version] Error 1

Proposal
Increase the version of Gaia used in the tutorial. Gaia v12.0.0 exists.

Alternatively, one can bypass the check by commenting these lines out but that may break other things.


Add multiple Spanish words for the emojis

Hi!
I added multiple Spanish words for the emojis, even for the new one  🕸
😉

I'm going to wait before merging this PR, I need to fix issue #9 and #10 first

LGTM 👍🏻

Thank you very much!


Can't use proxy user:password with percent encoded characters

RFC 3986 defines a set of reserved characters that can't appear directly in URL components like the userinfo. It also defines the percent encoding mechanism to escape them when needed. That means that an URI containing characters like $ or ? in the userinfo need to be encoded. For example, if the user is myuser and the password is $?xxxx then the proxy URI should be like this:
http://myuser:%24%3Fxxxx@myproxy.example.com:3128

The Ruby URI.parse methods accepts this syntax, but it doesn't do the corresponding decoding. The program that uses this URI needs to do the decoding explicitly before using it:
require 'cgi'
require 'uri'

uri = URI.parse('http://myuser:%24%3Fxxxx@myproxy.example.com:3128')
password = CGI.unescape(uri.password)
...

But apparently, for proxy URIs, rest-client uses directly the value returned by the password method. See rest-client/rest-client#661 for details.
In addition this gem also does the same itself:
https://github.com/abonas/kubeclient/blob/359e8c167c3f4356504c133160ed52aa4b4b8131/lib/kubeclient/watch_stream.rb#L59-L60
As a result when the password contain percent encoded characters this gem uses a wrong proxy password, and the proxy authentication fails.

I believe the same also applies to percent-encoded username.
RFC doesn't talk of password specifically; AFAICT it says percent encoding applies to any component, and syntax for whole whole userinfo field clearly shows percent encoding is applicable:
userinfo    = *( unreserved / pct-encoded / sub-delims / ":" )

username encoding does happen in the wild for example when using email as username https://stackoverflow.com/questions/10050877/url-username-with.

I think if we agree on this fix, we will have to do it in kubeclient anyway, because getting it into rest-client stable version will take time. I think we should, @cben WDYT?
Can such a fix introduce a problem? i.e someone has a proxy with this password "%". he previously could construct a client with proxy<EMAIL_ADDRESS>The user could still make it work by using escaped %<EMAIL_ADDRESS>but he would have to change code. Is this scenario real? should we take it into consideration? I think not but still sharing.
rest-client seems to escape the url user and password but not the proxy user and password.

I don't think backward compatibility is a blocker.  That's the beauty of RFCs :-)  If we're confident we understood the RFC right (I'm satisfied), then<EMAIL_ADDRESS>is simply wrong URL for the password %ab.  It's just a bug, we fix it and document the change.
Do you see any sane way for kubeclient to fix non-watch methods before rest-client itself is fixed?
Looks like we can easily fix watch methods (based on http gem), but I'm not sure we should until we fix the rest — different methods using different proxy settings for same URL would be very confusing...

See: https://github.com/rest-client/rest-client/pull/665


Missing breadcrumbs on Groups pages

The two pages under Users and Groups on the admin dashboard -- Manage Users and Manage Groups -- do not show the breadcrumbs. This is not consistent with the other pages on the admin dashboard, and I would expect to find them for a better navigation experience.

I've added it to my new users page that is in the works. From our discussions last week, I am under the assumption that the existing users page is most likely not going to remain, so I would assume it doesn't need to be retrofitted with breadcrumbs. If I'm wrong on this, please let me know.
Manage groups page is in hyku rather than hyrax, so that would be a separate issue from manage users, and would need to be covered by this issue.

Thanks, @laritakr. You are correct: no need to add breadcrumbs to the existing page. Let's wait for the page that you are working on in https://github.com/projecthydra-labs/hyrax/issues/247.
I'm editing the title of this issue so it just concerns the Groups pages.


Event Timestamp

I'm not sure if road/city decks save the date they were used but we'd love to know the dates the cards were played.
If a scenario log were to be added, we'd love to have dates on that too.

Won't be added because it would take too much time.


Windows Compatibility

Coverage decreased (-2.4%) to 82.576% when pulling 907aaa74d3765b367bf814f8bdff472823d5df90 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-2.0%) to 83.009% when pulling e88c7b7ddcab4336751dc9636c2fc078f3183a07 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-2.07%) to 82.937% when pulling fe181b7311aba3e75a4680058d64767c16e42325 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-2.0%) to 83.027% when pulling c04b3d652549653867df37e1dbf49433e67f28c6 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-2.0%) to 83.027% when pulling b018b53ea644c8980e1650dbfe658e33dc16af5e on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-2.4%) to 82.595% when pulling a36860a76347089fb7e714fe3b045830639a18cc on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-2.0%) to 83.027% when pulling ec38df003faa3438b6a4d33b128b9191803f026d on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-2.0%) to 83.027% when pulling 0eb17063b20fdbb916d7aaaa058b0412066d53c3 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-2.0%) to 83.027% when pulling c2363ac5a648af61e9be219d74e3407b54eec79f on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-2.0%) to 83.027% when pulling 9a31dc4cddbe9c449d6d13f479935ff96505e007 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-2.0%) to 83.027% when pulling 05c1f51567bc2fd5f9801273dcec728f4fc2ef5d on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-2.0%) to 83.027% when pulling b46196c0f2cb5c9b8bcf4966c84e4785040348ec on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-2.0%) to 83.027% when pulling 57b6c3c31a531ef211e4765a6b07a0ec394953c8 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-2.4%) to 82.595% when pulling 713776ac8d2a195732b481c7b4559345ff3f08e3 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-2.4%) to 82.595% when pulling 713776ac8d2a195732b481c7b4559345ff3f08e3 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-2.0%) to 83.027% when pulling e8cd9a7491aa41e93db906a2ae7479a38d8eb6d6 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-2.0%) to 83.027% when pulling 8cb9fe9f8531473d9455d99c55ab8379e6ea9235 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-2.0%) to 83.027% when pulling 2dc9dd4cdebbdaea7db3cf10f180f65cc3aeb29d on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-1.9%) to 83.082% when pulling a18b7a979438e291cd6a4a8b7089c7f380219f1b on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-0.8%) to 84.159% when pulling 33b6a32982aad3030c6dc83f1e8973f4d1a07916 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-1.9%) to 83.082% when pulling 1e96215d0d916a8524e82949859f9ccdce0df6e1 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-1.9%) to 83.082% when pulling e63fde8a1fcda1c7eff03f7e218477922acae655 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-1.9%) to 83.082% when pulling 0b922a1fd256b3618df360bbbde8727050d0ff22 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-1.9%) to 83.082% when pulling 1a1f228ca20080db829ac392949b6a20417c583d on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-1.9%) to 83.082% when pulling 161f06bedd6cf6f1adc2deb2461a295046370832 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-1.9%) to 83.082% when pulling 8be9559753700d173cca84887ebf669713e2d578 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-1.9%) to 83.082% when pulling 18ba969ea2b6c93048dce9e9b03b8aa76290dce8 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-1.9%) to 83.082% when pulling d732e0bc44819a6ce0b9bf4558de1e98bcf23eec on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-1.9%) to 83.082% when pulling 9e053460d1a6f31d4adfacb5d58a1634b2f9a39f on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-1.9%) to 83.082% when pulling c9e89ea7beaa82fad6bcf3e50c312382f31344b6 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

Coverage decreased (-1.9%) to 83.082% when pulling c9e89ea7beaa82fad6bcf3e50c312382f31344b6 on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

@datarobot/predictions  Please review and feel free to ping me if you have any questions since there is a lot going on here.
Here is a high level overview of the changes:

There is no fork on Windows, so when using multiprocessing state needs to be passed in explicitly. Any objects passed into the new proc need to be pickleable.
Locks and queues cannot be shared so it's necessary to use a manager process. The manager creates proxies for locks and queues which can be shared across processes.
A file or file handle cannot be opened by more than one proc so it's necessary to send logs from a sibling process, like the shoveler, to a different file.

I gave up on the Python3 tests on Windows because I had trouble recreating the issues on either my Windows 7 laptop or VM. As far as I can tell, the issue is caused by a socket being close prematurely by Windows on the Appveyor CI machine.
2016-07-06 23:38:01,251 [DEBUG] authorization has succeeded
2016-07-06 23:38:01,267 [INFO] Shovel go...
2016-07-06 23:38:01,892 [DEBUG] batch 0 transmitting 93 bytes
2016-07-06 23:38:01,892 [INFO] Starting new HTTP connection (1): localhost
2016-07-06 23:38:01,892 [DEBUG] batch 10 transmitting 103 bytes
...
2016-07-06 23:38:01,907 [DEBUG] batch 90 transmitting 103 bytes
2016-07-06 23:38:01,907 [DEBUG] Exception <class 'requests.exceptions.ConnectionError'>: ('Connection aborted.', ConnectionAbortedError(10053, 'An established connection was aborted by the software in your host machine', None, 10053, None))
2016-07-06 23:38:01,938 [DEBUG] Skipping processing response because of FakeResponse
2016-07-06 23:38:01,954 [INFO] Starting new HTTP connection (2): localhost
2016-07-06 23:38:01,954 [INFO] 1 responses sent | time elapsed 0.6875612735748291s
2016-07-06 23:38:01,954 [DEBUG] "POST /api/v1/56dd9570018e213242dfa93c/56dd9570018e213242dfa93d/predict HTTP/1.1" 200 2032

This causes the first batch to be lost and the tests fail. I added a note to Windows users encouraging them to stick with 2.7 for now.

Coverage decreased (-1.9%) to 83.082% when pulling 6aea116635cf2ce6392709b8425d6fe7020b414c on matt/windows_tests into d5bca37bd42d6a265c316a02a2e4609c0f3a03d2 on master.

LGTM


[BUG] cant install mubeng from github

Describe the bug
I cant install mubeng from github
To Reproduce
Steps to reproduce the behavior:
go install github.com/kitabisa/mubeng/cmd/mubeng@latest

Expected behavior
Install mubeng from github
Environment (please complete the following information):

OS: Ubuntu 20.04
OS version: Linux nanopineo3 5.10.63-rockchip64 aarch64 GNU/Linux

Yep, currently the package URL is down. You should try building from source.

it is necessary to change line 1 https://github.com/kitabisa/mubeng/blob/master/go.mod#L1 by github.com/kitabisa/mubeng


Update for 0.9

0.9 split the sub_printer() method up into components. How would you draws columns now? Can you update this code to work with 0.9?

I think I have this working. There's an issue in cursive 0.9 I'm still tracking down with BoxView::with_full_screen(). Once I'm convinced it doesn't impact this, I'll give you a PR.

Fix is now in master (1784fefd8089f436e1411de728b2eb53d27bd49b).


Difficulty with Sync to Azure Mobile Apps using Starter App

Hi there! 👋
First off, my apologies if this is better suited for Xamarin.Forms directly – I'm new to the Azure/Xamarin space and not sure where I'd get the best feedback.
Getting my feet wet with Xamarin, and doing some feasibility testing/research. I've downloaded the starter app to test out syncing Xamarin.Forms with Azure Mobile Apps. I've done practically no customization from the starter app generated from Azure – except for adding a few extra fields to my table, just to simulate a little larger dataset. I'm encountering four issues, which I'll detail here – but first, my environment:
Environment

Visual Studio for Mac (Community), v7.4 build 1033
Microsoft.Azure.Mobile.Client v4.0.1
Microsoft.Azure.Mobile.Client.SQLiteStore v4.0.1
NETStandard.Library v1.6.1
Xamarin.Forms v<IP_ADDRESS>

1. Duplicate items (Screencast)
Adding items can sometimes result in duplicate records being added to the database. These duplicate records sometimes clear out over time, but sometimes they don't.
2. If there are duplicate items, only one is updated  (Screencast)
If there are duplicate items in the database as a result of the above point, and that item is updated within the app, only the one record in the database is updated – not both. So in addition to data duplication, we also don't seem to have a way of knowing which record is authoritative.
3. Deleting items in database doesn't delete in app (Screencast)
If records are deleted from the database, they seem to get "stuck" in the app. In fact, force-closing and re-launching the app does not regenerate the local database. It takes a full re-install before these "stuck" items are removed/database is synced.
4. Items can reappear after deletion (Screencast)
If I delete records from the database, we already know from 3 above that they're not removed from the app. But I found that if I add a new item within the app, they're added back to the database. In this example video, it's also worth noting that the record for "Newmont Mining Corporation" is not re-added to the database, and the "App 2" item I added in the app was not synced to the database either.

These issues are obviously a bit concerning, and would be challenging to work with in a production environment. I just want to make sure I'm not missing anything obvious in my initial testing. 🙂
Note that in all of the above examples, the app is connected to the database the whole time. These problems seem to be made worse when the device is offline, especially items getting "stuck" in their old state – but I'm more concerned about the core functionality of syncing with Azure.
Any insight you can provide here would be fantastic. I'm not sure how stable this syncing functionality is "out in the wild", so I'm be curious about that as well, or if we should investigate alternative solutions.
Thanks so much!

Hi!
Many thanks for SO detailed description. It's awesome!
1 and 2
I've managed to reproduce it and it looks like just a visual bug in portal web UI caused by fast multi-clicking refresh button. Full reload the page should help.
3 and 4
This is expected behavior. To support that case you should use a soft delete (column deleted) or don't use incremental sync on the client.
Check out these articles to find out how it works and why it happens:

Offline Data Sync in Azure Mobile Apps
Understanding Offline Sync

I hope this helps you. Feel free to contact us if you have additional questions or something still goes wrong.
Best,
Ivan

@tgmcguire Thanks for using Azure Mobiel Apps and reporting this issue. I hope answers shared by @MatkovIvan has helped you resolve your issues. I will close this for now but feel free to contact us if you have more questions. Thanks!


purification chamber induces lag spike when turning on/off

If the purification chamber isn't being fed as fast as it processes, it flips on and off as input comes in.  This transition always induces a lag spike.  In my survival world, this is on the order of hundreds of milliseconds during which the game freezes.
In a new creative flatworld with nothing but a simple tier 2 chain and a timer set up to turn the chamber on and off via redstone every second, I still see this spike, although much less severe.  The game visually stutters whenever the machine changes state, and the F3 graph shows a clear lag spike.
I haven't tested whether other machines have this problem.
This seems to occur with the default config, and also after disabling these:
B:CTMRenderer=false
B:EnableAmbientLighting=false
B:EnableMachineSounds=false
B:EnablePlayerSounds=false
B:MachineEffects=false
B:OpaqueTransmitterRender=false

Interestingly, at a distance of about 30-35 blocks, the stutter disappears.

Try and increase the value of UpdateDelay. It will determine how quickly a machine can transition from its on to off state and vice versa.