How to make the ListView stop there when pull down , and restore it after refresh completed.

Just like the classical ios pull down refresh

Duping into #11661. Support will likely be added in about a week on the master branch.


Added new enrolment states and updated 'Get my applied mentors' endpoint

Purpose
Adding new enrolment states, updating 'Get my applied mentors' endpoint, and updating corresponding unit tests.
The purpose of this PR is to fix #246 and #229
Goals
Adding enrolment states and adjusting endpoint for February release.
Checklist

[x] This PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
[x] I have read and understood the development best practices guidelines ( http://bit.ly/sef-best-practices )
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

Yep, checking right now

I think I forgot to commit some changes, give me one second

Yep, checking right now

Nice. I added a few more comments. Update those as well.

Made the changes, can you retry the build?


Battery alarm level adjustment

The battery alarm sets in to early according to this post by awap at RCGroups:
"Hi, I'm very happy with version 1.4 and the Eachine DVR installed. One whish however: I'm on a 3S battery and the beeper starts at 11.4V (3.8V per cel) and the second level beep starts at 11,2V (3,73V per cel). This is too soon. Is there a way to start the beeper at 3x3.65= 10.95 -11.0 V?"
The behavior is not really a bug, the level was set unnecessarily low.

duplicate


Domain expired

The link http://box-project.org/installer.php is down :anguished:

$ curl -LSs https://box-project.github.io/box2/installer.php | php

Done.

Awesome thanks - merged!


[18.03] libxml2: fix CVE-2018-14567 & CVE-2018-14404 & CVE-2018-9251

Motivation for this change
backport of 06e7a48f458164ae012bc82337f7ef88579cafc8
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Fits CONTRIBUTING.md.

@GrahamcOfBorg build libxml2

Success on x86_64-linux (full log)
Attempted: libxml2
Partial log (click to expand)
strip is /nix/store/k8b9hqv58dd1z0j4ikak24ykndcm91s6-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/rlpri2hv9lbpmb28qkl6im4yv3si5gvf-libxml2-2.9.7-py/lib
patching script interpreter paths in /nix/store/rlpri2hv9lbpmb28qkl6im4yv3si5gvf-libxml2-2.9.7-py
checking for references to /build in /nix/store/rlpri2hv9lbpmb28qkl6im4yv3si5gvf-libxml2-2.9.7-py...
Moving /nix/store/vywwsqjz3gpdrqc3hpilw8s043xzmmwc-libxml2-2.9.7-bin/bin/xml2-config to /nix/store/s9gimgx6aqkj4y4hah0b9ggvyc4iabhr-libxml2-2.9.7-dev/bin/xml2-config
rmdir: failed to remove '/nix/store/vywwsqjz3gpdrqc3hpilw8s043xzmmwc-libxml2-2.9.7-bin/bin': Directory not empty
Moving /nix/store/mzpcmn5hggx412gq8zfbwrcbnx8p9rdy-libxml2-2.9.7/lib/xml2Conf.sh to /nix/store/s9gimgx6aqkj4y4hah0b9ggvyc4iabhr-libxml2-2.9.7-dev/lib/xml2Conf.sh
rmdir: failed to remove '/nix/store/mzpcmn5hggx412gq8zfbwrcbnx8p9rdy-libxml2-2.9.7/lib': Directory not empty
Moving /nix/store/sq0d65ld1j8x23clcgg0hq3mbda597lk-libxml2-2.9.7-man/share/man/man1 to /nix/store/vywwsqjz3gpdrqc3hpilw8s043xzmmwc-libxml2-2.9.7-bin/share/man/man1
rmdir: failed to remove '/nix/store/sq0d65ld1j8x23clcgg0hq3mbda597lk-libxml2-2.9.7-man/share/man': Directory not empty

The changes clearly seem platform-neutral.

@andir: more of mass rebuilds coming now to 18.03, or can Hydra start rebuilding?

Success on aarch64-linux (full log)
Attempted: libxml2
Partial log (click to expand)
stripping (with command strip and flags -S) in /nix/store/4wvxwfkhp1nrvq8jhl5pdd49xzvmwlna-libxml2-2.9.7-py/lib
patching script interpreter paths in /nix/store/4wvxwfkhp1nrvq8jhl5pdd49xzvmwlna-libxml2-2.9.7-py
checking for references to /build in /nix/store/4wvxwfkhp1nrvq8jhl5pdd49xzvmwlna-libxml2-2.9.7-py...
Moving /nix/store/njmdbayzviqglax2hlxhfnfdr065ggi2-libxml2-2.9.7-bin/bin/xml2-config to /nix/store/yl5pnzjh8naajr7z99jq75msnmg26b3g-libxml2-2.9.7-dev/bin/xml2-config
rmdir: failed to remove '/nix/store/njmdbayzviqglax2hlxhfnfdr065ggi2-libxml2-2.9.7-bin/bin': Directory not empty
Moving /nix/store/k1zlikjjd5cbgdrx04fighq03lb0jha8-libxml2-2.9.7/lib/xml2Conf.sh to /nix/store/yl5pnzjh8naajr7z99jq75msnmg26b3g-libxml2-2.9.7-dev/lib/xml2Conf.sh
rmdir: failed to remove '/nix/store/k1zlikjjd5cbgdrx04fighq03lb0jha8-libxml2-2.9.7/lib': Directory not empty
Moving /nix/store/iyacj90j8akwnxbrxv9yil1ryw9am3ba-libxml2-2.9.7-man/share/man/man1 to /nix/store/njmdbayzviqglax2hlxhfnfdr065ggi2-libxml2-2.9.7-bin/share/man/man1
rmdir: failed to remove '/nix/store/iyacj90j8akwnxbrxv9yil1ryw9am3ba-libxml2-2.9.7-man/share/man': Directory not empty
/nix/store/njmdbayzviqglax2hlxhfnfdr065ggi2-libxml2-2.9.7-bin

Success on aarch64-linux (full log)
Attempted: libxml2
Partial log (click to expand)
these derivations will be built:
  /nix/store/rmnk0xglasylx4irliar9shhds4myg8i-libxml2-2.9.7.drv
waiting for locks or build slots...
/nix/store/njmdbayzviqglax2hlxhfnfdr065ggi2-libxml2-2.9.7-bin

@vcunat My time for today is almost over. There are no more mass-rebuilds on my list for today :)
Thanks for picking them up!

Right, today ends in half an hour in my timezone (and yours as well, I think).

Timed out, unknown build status on x86_64-darwin (full log)
Attempted: libxml2
Partial log (click to expand)
cannot build derivation '/nix/store/q36b107h0956d82arshlddjv29qi3y7l-flex-2.6.4.drv': 7 dependencies couldn't be built
cannot build derivation '/nix/store/0adi003cdg6pwk6qgpqf3w7gikh38m25-CF-osx-10.10.5.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/qshxipi8y3h1248qdk5al26bc57zbhvd-bootstrap_cmds-dev-tools-7.0.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/k139s3nmp7qakwr3bq1nvdz9hbwk0d7j-python-2.7.15.drv': 14 dependencies couldn't be built
cannot build derivation '/nix/store/254444qf23aa26sb1h7myfl4kjdzy7x7-xnu-osx-10.11.6.drv': 9 dependencies couldn't be built
cannot build derivation '/nix/store/l0wnmbhzdbcac6m0aq7415h7l0xgdp59-IOKit-osx-10.11.6.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/4051r8yv9vlck076nrnf90s6z5zz06v3-configd-osx-10.8.5.drv': 9 dependencies couldn't be built
cannot build derivation '/nix/store/lz9zs2py1vwwaah14s0zpys3iik7mclg-python-2.7.15.drv': 15 dependencies couldn't be built
cannot build derivation '/nix/store/x2nh0x7sw12dr0p4fv9vhjxqsi2ngd03-libxml2-2.9.7.drv': 7 dependencies couldn't be built
error: build of '/nix/store/x2nh0x7sw12dr0p4fv9vhjxqsi2ngd03-libxml2-2.9.7.drv' failed

Timed out, unknown build status on x86_64-darwin (full log)
Attempted: libxml2
Partial log (click to expand)
cannot build derivation '/nix/store/q36b107h0956d82arshlddjv29qi3y7l-flex-2.6.4.drv': 6 dependencies couldn't be built
cannot build derivation '/nix/store/0adi003cdg6pwk6qgpqf3w7gikh38m25-CF-osx-10.10.5.drv': 7 dependencies couldn't be built
cannot build derivation '/nix/store/qshxipi8y3h1248qdk5al26bc57zbhvd-bootstrap_cmds-dev-tools-7.0.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/k139s3nmp7qakwr3bq1nvdz9hbwk0d7j-python-2.7.15.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/254444qf23aa26sb1h7myfl4kjdzy7x7-xnu-osx-10.11.6.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/l0wnmbhzdbcac6m0aq7415h7l0xgdp59-IOKit-osx-10.11.6.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/4051r8yv9vlck076nrnf90s6z5zz06v3-configd-osx-10.8.5.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/lz9zs2py1vwwaah14s0zpys3iik7mclg-python-2.7.15.drv': 9 dependencies couldn't be built
cannot build derivation '/nix/store/x2nh0x7sw12dr0p4fv9vhjxqsi2ngd03-libxml2-2.9.7.drv': 3 dependencies couldn't be built
error: build of '/nix/store/x2nh0x7sw12dr0p4fv9vhjxqsi2ngd03-libxml2-2.9.7.drv' failed


FIX: Version of recipe for 4.2

The version of recipe-cms effectively pinned this repo to 4.1 when I tried to upgrade.  Not sure if this is the best way to fix it, and it will need a major version bump in packagist as it's not backwards compatible to 4.1.

Change made as requested, I've force pushed so only one commit in the history.  Seems to work running composer update and version control pointing at this PR in composer.json.
Thanks for educating me on the use of || in version control restraints, that is useful :)

Thanks for making the update. We brushed up on the options a while back when we noticed the version change for the recipe.


int with warp: log not working again

@cxhernandez, cf. #109
With the latest version of osprey, when passing something like this:
  cluster__n_clusters:
     min: 10
     max: 100
     type: int
     warp: log

I get an error (see below). This is the case for both random and gp search, with or without jump. cc: @hannahw1
------------------------------------------------------------------------------
Exception encountered while fitting model
------------------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/bhusic/source/osprey/osprey/execute_worker.py", line 136, in run_single_trial
    estimator, params, cv=cv, scoring=scoring, X=X, y=y, verbose=1)
  File "/home/bhusic/source/osprey/osprey/fit_estimator.py", line 61, in fit_and_score_estimator
    for train, test in cv.split(X, y))
  File "/home/bhusic/miniconda3/lib/python3.5/site-packages/sklearn/externals/joblib/parallel.py", line 758, in __call__
    while self.dispatch_one_batch(iterator):
  File "/home/bhusic/miniconda3/lib/python3.5/site-packages/sklearn/externals/joblib/parallel.py", line 608, in dispatch_one_batch
    self._dispatch(tasks)
  File "/home/bhusic/miniconda3/lib/python3.5/site-packages/sklearn/externals/joblib/parallel.py", line 571, in _dispatch
    job = self._backend.apply_async(batch, callback=cb)
  File "/home/bhusic/miniconda3/lib/python3.5/site-packages/sklearn/externals/joblib/_parallel_backends.py", line 109, in apply_async
    result = ImmediateResult(func)
  File "/home/bhusic/miniconda3/lib/python3.5/site-packages/sklearn/externals/joblib/_parallel_backends.py", line 326, in __init__
    self.results = batch()
  File "/home/bhusic/miniconda3/lib/python3.5/site-packages/sklearn/externals/joblib/parallel.py", line 131, in __call__
    return [func(*args, **kwargs) for func, args, kwargs in self.items]
  File "/home/bhusic/miniconda3/lib/python3.5/site-packages/sklearn/externals/joblib/parallel.py", line 131, in <listcomp>
    return [func(*args, **kwargs) for func, args, kwargs in self.items]
  File "/home/bhusic/source/osprey/osprey/fit_estimator.py", line 131, in _fit_and_score
    estimator.fit(X_train, **fit_params)
  File "/home/bhusic/miniconda3/lib/python3.5/site-packages/sklearn/pipeline.py", line 268, in fit
    Xt, fit_params = self._fit(X, y, **fit_params)
  File "/home/bhusic/miniconda3/lib/python3.5/site-packages/sklearn/pipeline.py", line 234, in _fit
    Xt = transform.fit_transform(Xt, y, **fit_params_steps[name])
  File "/home/bhusic/source/msmbuilder/msmbuilder/cluster/base.py", line 173, in fit_transform
    return self.fit_predict(sequences, y)
  File "/home/bhusic/source/msmbuilder/msmbuilder/cluster/base.py", line 154, in fit_predict
    labels = super(MultiSequenceClusterMixin, self).fit_predict(sequences)
  File "/home/bhusic/miniconda3/lib/python3.5/site-packages/sklearn/cluster/k_means_.py", line 898, in fit_predict
    return self.fit(X).labels_
  File "/home/bhusic/source/msmbuilder/msmbuilder/cluster/base.py", line 48, in fit
    super(MultiSequenceClusterMixin, self).fit(self._concat(sequences))
  File "/home/bhusic/miniconda3/lib/python3.5/site-packages/sklearn/cluster/k_means_.py", line 1381, in fit
    init_size=init_size)
  File "/home/bhusic/miniconda3/lib/python3.5/site-packages/sklearn/cluster/k_means_.py", line 681, in _init_centroids
    x_squared_norms=x_squared_norms)
  File "/home/bhusic/miniconda3/lib/python3.5/site-packages/sklearn/cluster/k_means_.py", line 106, in _k_init
    for c in range(1, n_clusters):
TypeError: 'numpy.float64' object cannot be interpreted as an integer
------------------------------------------------------------------------------

Done in #210


[ENHANCEMENT] Only pull image if the image is not found

I merged this into my local branch, accepting all of your incoming changes.
When I start a new cluster, I receive the following error messages:
2019/05/03 09:00:11 ERROR: failed to create cluster
ERROR: couldn't create container k3d-test1-server
Error response from daemon: page not found

Updated

LGTM, thank you :+1:


allow to include enum

this code not work
enum Errors
  ERROR1 = 1
  ERROR2 = 2
end

include Errors

p ERROR1

need to change enum to module, after that it works, may be allow to include enum also?

I've thought about this many times, and it's a really nice feature. Maybe we should include this in the standard library:
macro include_constants(type)
  {% for constant in type.resolve.constants %}
    {{constant}} = {{type}}::{{constant}}
  {% end %}
end

enum Errors
  ERROR1 = 1
  ERROR2 = 2
end

include_constants Errors

p ERROR1

:-)

I've [also] (https://github.com/BlaXpirit/crsfml/blob/v2.4.1/src/common.cr#L13) been keeping one of these.

It's interesting to consider whether the "included" constants should be documented (in my case they aren't). Maybe a configurable argument?
And now that I think about it, maybe instead it makes more sense to just allow enums to expose their constants unqualified  as a language feature, so there's a proper way to indicate that they're available outside without annoying lists of placeholders in documentation.

I'll just throw in a few more or less daunting ideas here:
It could be preferable if we had some "reverse inference" (I know I abuse that term ;-) ) matching literals, as has been discussed earlier, and for this case also unqualified enum-constants, which match towards Enums in ivars type declarations or a parameter's restriction, when explicitly an Enum.
This is harder to do, but cause less name pollution and thus avoids possible conflicts, while still allowing much more clearly readable code.
First, a Naive Suggestion
It can of course never be "fool proof" (just like with freevars contra types) and introduces further rules for order of matching methods:
enum MyEnum
   Red
   Green
   Purple
end

Green = 47

# To show of one problematic
def my-fun(x, y)
  p "my-fun 1: #{x}, #{y}"
end

def my-fun(x, y : MyEnum)
  p "my-fun 2: #{x}, #{y}"
end

my-fun 1, 2  # business as usual
my-fun 1, Red  # Red not found, but a signature exists with enum, try matching in that. Match! Expand.
my-fun 1, Green  # matches the const. Problematic Gotcha!!!

The gotcha alone, is a strong argument against.
So How About Something Similar to Swift?
Indicating a non qualified enum const explicitly:
my-fun 1, 2  # business as usual
my-fun 1, .Red  # Signature exists with enum, try matching them. Match! Expand to qualified.
my-fun 1, .Green  # Of course also gives the expected result.

The dot-const notation could of course prove problematic, unless parenthesis call is demanded when it's used as first arg (that's true already for some literals). However, do we ever access a const-like identifier like that?:
some-fun .Red  # how will the parser take this?
some-fun(.Red)  # this is sure to be ok at least.

And, the ivars of course:
class Foo
  @val : MyEnum = .None
  def do_stuff
    @val = .Purple
  end
end

Another option, is a using declaration which can be used to expose constants in a specific scope only. But using has much more uses [no pun..] so I put it in its' own issue: #3319.

@ozra, I had this idea but with the syntax... :SomeItem. I don't think the dot is viable.

But then it's a symbol!?

We actually looked at how this works in Swift and like it, and thought about doing something similar in Crystal :-)
Our main issue is that Swift requires type declarations everywhere, while we don't, so in their case if you have a = .Purple they already know what the type of a is, so they can deduce what .Purple means. That, coupled with overloads and other things makes it a bit hard to do, but it's something that we'll try to tackle once we tackle things with more priority.
And like @BlaXpirit says, for enums we though about using symbol literals, as this is also closer to Ruby, though a downside of that is that it adds more magic to the language (and we have to solve the conflict between symbol and enum).

@ozra, it would normally be a symbol. I'm suggesting it only for the contexts where it couldn't possibly be a symbol and it's clear what enum is being referred to.

for enums we though about using symbol literals

:+1: I can't wait for something like this. Compare:
case opcode
when StandardOpcode::NegateStmt
when StandardOpcode::FixedAdvancedPc
end

vs
case opcode
when :negate_stmt
when :fixed_advance_pc
end

Or logger.level = :debug vs logger.level = Logger::Severity::DEBUG
In places where the type is known to be an enum, this would really help increase readability, without sacrificing type safety.

@asterite I suspected you'd already thought about it XD
I think it should try all overloads that match with an Enum in the position, and then try them to see which includes the const.
Of course the problem is that several enums can have the same const. And then a rule is needed for signature precedence. Perhaps whichever enum is declared first or last in the program?

with symbols you can typo and program compiled, with enums not.

@kostya I assume the symbols would be transformed to their enums at compile time, and thus validated.

@ysbaddaden you can do https://play.crystal-lang.org/#/r/19y4 since #285 in order to short case opcode scenario
enum Color
  Red
  Green
  Blue
end

color = Color::Red
a = case color
    when .red?
      1
    when .green?
      2
    when .blue?
      3
    end

pp color
pp a

How about not making them symbols? It seems confusing and magic to me. There should be some nonambiguous syntax, or no syntax.

Agree with @RX14 fully. Symbols are symbols. Unqualified Enum consts another.

We got :symbol shorthand syntax for enum members in calls now. This seems to cover most usecases people had for this. Is there still strong desire for this? Otherwise I'd reject this to keep the language more simple for now.


feat: parallel beatree branch updater

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#423  👈
#422
#421
#420
#419
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @gabriele-0201 and the rest of your teammates on  Graphite


Document hive.allow-drop-table and hive.allow-rename-table and defaults

Testing: mvn install -pl presto-docs

The commit message title is a bit long. It should be ~50 characters. Will update.

Merged, thanks!

OK, sorry that the title was too long. thanks for the review & merge!


[Feature request] TLSConfiguration.trustRoots is not flexible enough

TLSConfiguration.trustRoots is defined as enum NIOSSLTrustRoots. That enum can be .file(String), certificates([NIOSSLCertificate]) or .default. Default here means using roots provided by the platform (e.g "/etc/ssl/certs/ca-certificates.crt" on Linux).
Now the problem is that I cannot use combination of these mechanisms: for example if I want to trust all root certificates provided by the platform, but also some custom ones that I have in my app.

This seems like a reasonable request!

I believe this is fixed by #284.

Agreed.


NOT ABLE TO SIGN IN USING GITHUB OAUTH

Type: Bug
no able to sign in with github. The process ends up with a faliure saying to retry everytime I disabled firewall and things that were related to git signin in vscode but nothing worked
VS Code version: Code 1.75.1 (441438abd1ac652551dbe4d408dfcec8a499b8bf, 2023-02-08T21:32:34.589Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-1005G1 CPU @ 1.20GHz (4 x 1190)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
19.67GB (11.51GB free)

Process Argv
--crash-reporter-id ae6dca54-b42f-4fe9-bdd5-841ea3777e8a

Screen Reader
no

VM
0%

Extensions: none
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyonecf:30548226
vscccc:30610679
pyindex848:30662994
nodejswelcome1:30587005
3biah626:30602489
pyind779cf:30662993
f6dab269:30613381
pythonsymbol12cf:30657549
vscodedisable:30660115

@TylerLeonhardt, could you please take a look at this one? Thank you!

Can you follow these steps so that we can get more information on what's going on?

Open the Output pane (ctrl+shift+u I think on Windows)
drop in this issue he contents of the following:

GitHub Authentication Output channel

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


cmake CONFIGURE_DEPENDS (IDFGH-14190)

Is your feature request related to a problem?
When I add a new file, I have to clean the project manually and then build it again because the build system doesn't recognize the new file automatically.
Describe the solution you'd like.
I want to use GLOB to include all my source files. ESP-IDF provides the SRC_DIRS argument for idf_component_register, but it doesn't detect new files added to the source directories.
CMake has an option called CONFIGURE_DEPENDS  to re-run the GLOB operation during every build and trigger a clean build if the GLOB output changes. However, I haven't figured out how to make this work with ESP-IDF.
Is this feature already supported, or can it be implemented?
Describe alternatives you've considered.
No response
Additional context.
No response

I'm using CMakeLists.txt like this.
file(GLOB srcs *.c)
message(STATUS ${srcs})
idf_component_register(SRCS "${srcs}" INCLUDE_DIRS ".")

I think this is probably caused by CMakeLists.txt not being updated.
Please try updating the timestamp in CMakeLists.txt.


null uriToProblem in validation issue #196

Adds uri to problem if missing. Normally happens when syntactic error occurs outside a semantic object.

I see similar test errors as in


Conversational learning page #10

Description

Created the conversational learning page HTML file.

Placed it in the src/features/pages directory of the project as directed.

Added content for the head element of the file.
Added content for the body element of the file, including sections and dummy content.

Fixes #10
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

closing this pr as the issue is already done. Good attempt


docker client can't read from both "docker private registry" and "online docker registry" if custom ssl certificate are used

Docker version 1.2.0, build 2a2f26c/1.2.0
docker registry 0.8.1
i setup docker private registry on cenots7 and created my custom ssl cert. when I try to access my docker registry using https I get x509: certificate signed by unknown authority. i found a solution for this by placing the cert file under "/etc/pki/tls/certs" then do "update-ca-trust" and "service docker restart" now it started to read my certificate.i can login and pull and push to docker private registry.
now when i tries to read from online docker registry(https://index.docker.io/v1/search?q=centos) i get "Error response from daemon: Get https://index.docker.io/v1/search?q=centos: x509: certificate signed by unknown authority". i exported docker.io cert from firefox brower and put it under "/etc/pki/tls/certs" then do "update-ca-trust" and "service docker restart" but same error. it looks like docker client cant decide which cert to use for which repository.
Any ideas how we can fix x509: certificate signed by unknown authority for online docker registry while using your own docker private registry.

ping @dmp42 @dmcgowan @jlhawn

Private registries with self-signed certificates configuration is described here: https://docs.docker.com/reference/commandline/cli/#insecure-registries
I'm closing this for now - let me know if the provided instructions work, or if you still have an issue there.


chore(main): release 2.5.11

:robot: I have created a release beep boop
2.5.11 (2024-12-28)
Bug Fixes

fix:  (a061d20)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/rainbowwarmth/KazuhaBot/releases/tag/v2.5.11 :sunflower:


Vulnerability Import Should Support Risk Threshold

As a user I would like for the vulnerability importer to only create findings above a user specified risk level. For example, a risk level of informational does not get imported while moderate and high risk findings do.
Originally from https://github.com/MooseDojo/Serpico/issues/88

To set the risk threshold modify config.json to the desired value, 0 is the lowest:
"threshold":"2"


copy edits and update to install dialog

This makes several copy edits and a slightly bigger revision to to the install dialog:
This makes the introduction paragraph and closing paragraphs into specific instructions.

original:

The recovery has a similar update and additional details about which apps to use thereafter:

original:

It would probably be better to make the numbers consecutive. We can make some efforts to make the number of steps consistent across hubs or we add some tricks to make the start steps correct.

It would probably be better to make the numbers consecutive.

The <ol> element has a start attribute. So we would just need a variable to count each enabled step to set that number.

The  element has a start attribute. So we would just need a variable to count each enabled step to set that number.

I started using that in https://github.com/pybricks/pybricks-code/blob/3f6317a118f6f6b32612e0f118138ed901d339fc/src/firmware/bootloaderInstructions/BootloaderInstructions.tsx#L226 but it got a bit messy. I'll try the variable approach.
Firefox has a simple CSS solution though Chrome doesn't support it:

Maybe a way to do it with counter() in css? https://developer.mozilla.org/en-US/docs/Web/CSS/counter

Maybe a way to do it with counter() in css? https://developer.mozilla.org/en-US/docs/Web/CSS/counter

Seems like counter-reset: none does not work, but everything else does, so we can achieve it another way indeed :+1:

Updated with the comments so far.

Codecov Report
Base: 69.51% // Head: 69.60% // Increases project coverage by +0.09% :tada:

Coverage data is based on head (96188f4) compared to base (6e8e597).
Patch coverage: 100.00% of modified lines in pull request are covered.

:exclamation: Current head 96188f4 differs from pull request most recent head 3cc94ea. Consider uploading reports for the commit 3cc94ea to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1374      +/-   ##
==========================================
+ Coverage   69.51%   69.60%   +0.09%
==========================================
  Files         189      189
  Lines        4678     4689      +11
  Branches      959      967       +8
==========================================
+ Hits         3252     3264      +12
+ Misses       1407     1406       -1
  Partials       19       19

Impacted Files
Coverage Δ

src/ble/alerts/NoHub.tsx
33.33% <ø> (ø)

...re/installPybricksDialog/InstallPybricksDialog.tsx
17.64% <ø> (ø)

src/tour/Tour.tsx
68.91% <ø> (ø)

src/app/constants.ts
100.00% <100.00%> (ø)

.../bootloaderInstructions/BootloaderInstructions.tsx
72.72% <100.00%> (+2.88%)
:arrow_up:

...re/restoreOfficialDialog/RestoreOfficialDialog.tsx
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Updated with fixes for comments so far.

Can be merged if satisfactory. I'll make a separate PR for the next round.

Updated.

Added a few more commits. I think this completes the first pass.

Need to update the tests to match the button text rename.

Fixed

Thanks!


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 --temp-directory build/coverage ava && c8 report -r lcov --temp-directory build/coverage
chore(package): add xo from template
chore(package): add nyc from template
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/-test.js,tests/-test.mjs' as in template
chore(package): set $.ava.extensions='js,mjs' as in template

Codecov Report

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

@@          Coverage Diff           @@
##           master    #417   +/-   ##
======================================
  Coverage    75.8%   75.8%
======================================
  Files           5       5
  Lines         434     434
======================================
  Hits          329     329
  Misses        105     105

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 b57253d...8f78a1e. Read the comment docs.

Coverage remained the same at 77.075% when pulling 8f78a1e4b3cac089350cc0d9a8adb5b6549a1195 on template-sync-1 into b57253d4d5ad23c47f740769f255301f4c1c4fea on master.


Stats: Community package lists can collapse package groups to provide better visibility for projects

Issue
The package stats page https://www.nuget.org/stats/packages attempts to show the top 100 community packages. However many packages are distributed in groups, where if one of the popular packages at the root is installed it will bring the rest of the group with it. This creates a bias in the list towards popular packages that are broken down into individual components.
See this thread for more details: https://twitter.com/socketnorm/status/1203480289076375552
To Reproduce
Browse to: https://www.nuget.org/stats/packages
Expected behavior
I expect packages like xunit, serilog, swashbuckle, mongodb, and google.api to show up once per root package. So as Brad Wilson says, likely more than just one for xunit. Then I expect to be able to see a little more stats about other packages in that group and the ability to expand the entry to see all of its dependencies from the same group.
Why?
Because the current stat is both unfair, a single popular package takes a % space in the top 100 list based on how granularly it was broken down. Bringing other similarly popular package far down the list and stunting their exposure. I'm aware of my own bias as an AWS person, but note that that specific package is in the top 10 already, but packages like automapper, swashbuckle, are pushed below and so are a few others than would move above the fold.
Screenshots
Current

What it should look like
Excuse my possible mistakes in grouping some of the packages, I'm making an assumption, but the idea should come through regardless of mistakes

Current
New
Name
Count

1
1
newtonsoft.json
29,148,117

2
2
serilog
7,984,291

3
3
castle.core
7,886,842

4
4
moq
6,175,176

5
5
xunit xunit.extensibility.core
5,245,389

6
X
xunit.abstractions
5,208,127

7
X
xunit.extensibility.execution
4,956,922

8
X
xunit.core
4,850,106

9
6
awssdk.core
4,844,711

10
X
xunit.assert
4,800,113

11
7
automapper
4,791,484

12
X
xunit
4,717,355

13
X
xunit.runner.visualstudio
4,529,696

14
X
xunit.analyzers
4,106,426

15
8
swashbuckle swashbuckle.aspnetcore.swagger
3,896,177

16
X
swashbuckle.aspnetcore.swaggergen
3,840,631

17
9
nunit
3,775,539

18
X
swashbuckle.aspnetcore.swaggerui
3,686,688

19
X
swashbuckle.aspnetcore
3,390,697

20
10
polly
3,169,254

21
X
serilog.sinks.file
3,109,215

22
11
fluentassertions
3,060,040

23
12
nlog
3,059,236

How can it be done
I have some ideas about how to curate it, but I think the NuGet team is best equipped to come up with the best strategy in this case. You guys rock!

Thanks for the detailed write-up @yishaigalatzer! I agree with the sentiment here.
Trying to think of a possible quick-win here...
We already have a Dimension_PackageSet construct in the stats database. We mainly use it to apply the reverse filter: filter out non-community packages.
I'm wondering if we could use the same construct to group other packages into 'known sets' and enhance the DownloadReportRecentCommunityPopularity sproc that way...
Downside is that this grouping would also be manually curated (though only applies to the most popular packages), just like we do for the non-community packages that would otherwise appear in the list.
If we can build a query that generates the desired resultset, we'd need to update the report's JSON format, and the gallery's view that consumes this JSON.
Longer term, I think we should definitely take this feedback into account in a future redesign of the stats pipeline. Big question there would be: what data points are we missing (if any) to automate the grouping of these package sets? (thinking about telemetry difference between downloads and installs, direct installs versus transitive, and the like)


Searching errors through the dashboard using SQLite results in Ecto.QueryError

Searching through the web dashboard doesn't work because SQLite (and other DBs) doesn't support Postgres' ILIKE:
ilike is not supported by SQLite3 in query:

from e0 in ErrorTracker.Error,
  where: ilike(e0.reason, ^...),
  select: count()

A possible solution would be to change the private filter function lib/error_tracker/web/live/dashboard.ex depending on the DB. ILIKE for Postgres and LIKE for other DBs (which search case-insensitive by default).
  defp do_filter({field, value}, query) do
    # conditional filter based on DB?
    where(query, [error], ilike(field(error, ^field), ^"%#{value}%"))
  end

Thanks for the detailed report @toberoni. This should be fixed in #51. We will push a new release once the fix is merged. In the meanwhile you can point your application dependency directly to the branch.
mix deps do
  [
    {:error_tracker, "~> 0.2", github: "elixir-error-tracker/error-tracker", branch: "fix-sqlite-search"}
  ]
end


refactor: remove unnecessary index k

note that previously, the expression
(indices.length == 0) || ((k < indices.length) && (indices[k] == i))
would always evaluate to true. This meant that i == k was always true.
This refactor removes the unnecessary index k.

This change causes 2 of the test cases in claim.test.ts to fail.

closing, as this is a mistake!


Fails to compile as a dependency

Looks like the dependency async_io_utilities was yanked from crates.io, resulting in this crate no longer compiling as a dependency in other crates.
error: no matching package named `async_io_utilities` found
location searched: registry `crates-io`
required by package `async_zip v0.0.9`
    ... which satisfies dependency `async_zip = "^0.0.9"` of package ...

Thanks for letting me know - I've restored the latest version of async_io_utilities so that 0.0.9 compiles at the very least. 👍

@Majored is it also possible to restore the deleted https://github.com/Majored/rs-async-zip GitHub repo, to make older versions & forks like https://github.com/dignifiedquire/rs-async-zip compile?

@Majored is it also possible to restore the deleted https://github.com/Majored/rs-async-io-utilities GitHub repo, to make older versions & forks like https://github.com/dignifiedquire/rs-async-zip compile?

Idk what you're trying to do, and why you would like to compile old forks of rs-async-zip, but you can use my fork of rs-async-io-utilities instead, I cannot guarantee I will not delete it someday, but I may achieve it at some point and delete later, it doesn't make sense to keep it, but I may do for some time. There are also other forks as well.

@JonathanxD that's very nice; we fixed the problem in the meantime, so for us, you won't need to keep it.


[WIP] add basic plugin panic handlers

Fixes #521
@carlisia @nrb this is a basic fix for #521.  It captures any info about the panic and returns it as a normal error.  Stack traces (per Andy's WIP #1119) to be added in subsequent PR(s).
If this looks reasonable for block_store.go then i'll add it to the other 3 plugins as well.

LGTM!

👍 will proceed with the rest.

Updated the rest. Will squash before merge, and would like to do a quick manual test.

Squashed, test looks fine.

Updated all, try out squash & merge when ready


KAFKA-16056: Revoking connectors and tasks upon worker poll timeout expiry to prevent duplicate task assignments

Please refer to KAFKA-16056 for a details description of the problem.

@C0urante , @gharris1727 , I wanted to bring this issue to your attention which I had filed a while back. Essentially, the fix is similar to what was done for KAFKA-9184 i.e to revoke assignments upon poll timeout expiry now to avoid duplicate tasks running. To
Note that testing this was quite tricky using IT and I have written a test which seems to indicate that w/o this fix, we would have duplicate tasks running. Let me know what you both think!

hmm I see this

[2024-07-18T17:56:40.951Z] FAILURE: Build failed with an exception.

[2024-07-18T17:56:40.951Z]

[2024-07-18T17:56:40.951Z] * What went wrong:

[2024-07-18T17:56:40.951Z] Execution failed for task ':connect:runtime:spotlessJavaCheck'.

[2024-07-18T17:56:40.951Z] > The following files had format violations:

[2024-07-18T17:56:40.951Z]       src/test/java/org/apache/kafka/connect/integration/ConnectWorkerIntegrationTest.java

[2024-07-18T17:56:40.951Z]           @@ -59,6 +59,7 @@

[2024-07-18T17:56:40.951Z]            import·java.io.FileOutputStream;

[2024-07-18T17:56:40.951Z]            import·java.nio.file.Path;

[2024-07-18T17:56:40.951Z]            import·java.time.Duration;

[2024-07-18T17:56:40.951Z]           +import·java.util.ArrayList;

[2024-07-18T17:56:40.951Z]            import·java.util.Collection;

[2024-07-18T17:56:40.951Z]            import·java.util.Collections;

[2024-07-18T17:56:40.951Z]            import·java.util.HashMap;

[2024-07-18T17:56:40.951Z]           @@ -67,7 +68,6 @@

[2024-07-18T17:56:40.951Z]            import·java.util.Objects;

[2024-07-18T17:56:40.951Z]            import·java.util.Properties;

[2024-07-18T17:56:40.951Z]            import·java.util.Set;

[2024-07-18T17:56:40.951Z]           -import·java.util.ArrayList;

[2024-07-18T17:56:40.951Z]            import·java.util.concurrent.TimeUnit;

[2024-07-18T17:56:40.951Z]            import·java.util.concurrent.atomic.AtomicReference;

[2024-07-18T17:56:40.951Z]            import·java.util.stream.Collectors;

[2024-07-18T17:56:40.951Z]           @@ -100,8 +100,8 @@

[2024-07-18T17:56:40.951Z]            import·static·org.apache.kafka.connect.runtime.distributed.DistributedConfig.CONFIG_TOPIC_CONFIG;

[2024-07-18T17:56:40.951Z]            import·static·org.apache.kafka.connect.runtime.distributed.DistributedConfig.REBALANCE_TIMEOUT_MS_CONFIG;

[2024-07-18T17:56:40.951Z]            import·static·org.apache.kafka.connect.runtime.distributed.DistributedConfig.SCHEDULED_REBALANCE_MAX_DELAY_MS_CONFIG;

[2024-07-18T17:56:40.951Z]           +import·static·org.apache.kafka.connect.runtime.distributed.DistributedConfig.STATUS_STORAGE_PARTITIONS_CONFIG;

[2024-07-18T17:56:40.951Z]            import·static·org.apache.kafka.connect.runtime.distributed.DistributedConfig.STATUS_STORAGE_TOPIC_CONFIG;

[2024-07-18T17:56:40.951Z]           -import·static·org.apache.kafka.connect.runtime.distributed.DistributedConfig.STATUS_STORAGE_PARTITIONS_CONFIG;

[2024-07-18T17:56:40.951Z]            import·static·org.apache.kafka.connect.util.clusters.ConnectAssertions.CONNECTOR_SETUP_DURATION_MS;

[2024-07-18T17:56:40.951Z]            import·static·org.apache.kafka.test.TestUtils.waitForCondition;

[2024-07-18T17:56:40.951Z]            import·static·org.hamcrest.CoreMatchers.containsString;

[2024-07-18T17:56:40.951Z]   Run './gradlew :connect:runtime:spotlessApply' to fix these violations.

Can't seem to run ./gradlew :connect:runtime:spotlessApply locally. Let me check this and update

Can't seem to run ./gradlew :connect:runtime:spotlessApply locally. Let me check this and updatez
spotless behavior is jre-version-dependent, you can run with JDK11 and it should work.

Can't seem to run ./gradlew :connect:runtime:spotlessApply locally. Let me check this and updatez

spotless behavior is jre-version-dependent, you can run with JDK11 and it should work.

Aah ok, thanks for the info. I was able to run it now and updated the PR.

Build got aborted. Closing and reopening the PR to let the build getting triggered again.

hmm the build got aborted again. I see `org.apache.kafka.connect.integration.ConnectWorkerIntegrationTest.testPollTimeoutExpiry() failed as well which I haven't seen in the past.
org.apache.kafka.connect.runtime.rest.errors.ConnectRestException: Could not execute POST request. Error response: {"error_code":500,"message":"Failed to start task: simple-connector-0"}

Closing and opening again to see if it helps (one last try).

@gharris1727 , I have fixed the IT and the spotless issue. I think it's ready for a round of review. When you have some time, can you plz take look at it? Also, I see org.apache.kafka.connect.integration.ConnectWorkerIntegrationTest.testRequestTimeouts() is failing but looks like it is being fixed as part of this PR

hey @gharris1727 , when you have some time can you take a look at this PR?


In 0.3, receive no interest

In version 0.3 and 0.3a1*, my app receive no interest, and I use ndndump to monitor the traffic, I am sure my machine receive the interest. The route has registered into nfd.
However, In version 0.3a1.post3, it works.

One possible reason is that we moved to Naming Convention Rev03 in post4. Can you confirm if you are using this?

Thank you, you are right, after I usr name convention 3 of ndnts library, it works.


launch buddy use with arcdps + ReShade

If a user wishes to use GW2 Launch Buddy while using arcdps, it seems that you have to put the arcdps d3d9.dll into the main folder (Program Files\Guild Wars 2) instead of in the bin64 directory.
I'm not certain why this occurs but i think it has to do with what directory the gw2-64.exe is launched in, as it now uses the main directory as a search path.
This is normally ok, users are just aware to put a copy of the arcdps (or any other added) into the main dir instead. This causes a few problems however.
First, it means the user has to have two copies of the d3d9.dll incase they launch the game client directly.
Second, more importantly, it prevents chain loading into ReShade. This is because ReShade does not load properly if d3d9.dll is in the main directory (also not completely certain yet why this occurs).
Essentially, arcdps will load a chainloader for d3d9.dll which then loads ReShade64.dll. However, ReShade64.dll will not load because it finds the d3d9.dll file in the top level and exits.
Since we need the d3d9.dll in the top level to use launch buddy, this prevents the user from being able to use arcpds with ReShade. Additionally, after the ReShade fails to load, arcdps itself doesn't finish loading and you end up getting neither addon working correctly.
I believe the fault is that launchbuddy changes the load path. Alternatively it may be ReShade code which fails to load when a d3d9.dll is in the top level directory, but I'm unsure how to fix either of these issues.

ReShade64.log.txt
There's a copy of the ReShade64 log after loading with d3d9.dll in the top level,
ReShade64.log.txt
Followed by a copy of the log if I rename d3d9.dll in the top level to something else (obviously launched without launch buddy in this case).

Based on a cursory reading of the ReShade64 code, it appears that when ReShade64.dll is loading, it finds the d3d9.dll in the path so when it finally goes to load the real d3d9.dll it accidentally tries to run the copy found at the top level of the gw2 folder, which in this case isn't a valid d3d9.dll and then it fails to finish loading. and falls apart.
I don't think we can really fix this in ReShade itself.

There are two distinct problems each with an individual cause, though they are only seen in tandem.
The first is that when you run the client with auto login, you need to use the -nopatchui flag. For some reason this flag sets the load directory to the root of the game folder instead of the intended bin folder. There is no way to fix this without either a client update or dll injection (which I am confident will never happen through LB).
The second problem is in Reshade itself. I have never found the root cause of the crash, but something about the way -nopatchui loads the game causes Reshade to bomb. While Reshade is open source, I am not familiar enough with its code base to attempt to debug. Though I believe I submitted an issue to the Reshade github page.
At this point, there's really not much to be done except bug the parties capable of making the changes.

Actually, I wonder..... So when you launch the game with patchui, it then after patching proceeds to launch the game in bin64 folder...
With "-nopatchui" I bet that the game just lauches in the folder it originally was in (the regular directory).
What about adding a "launch in" path so that it launches in bin64 directly instead, when running with nopatchui? I suspect that the nopatchui code just doesnt' change dir, and if you force it to start within the bin64 directory it would work fine?
Essentially, at
https://github.com/TheCheatsrichter/Gw2_Launchbuddy/blob/8285f0e435959f735f8ba3dfb3a81db43984f77f/Gw2 Launchbuddy/ApplicationManager.cs#L119
What if you set the working directory to the bin64 path instead of working directory (but only when launching with nopatchui)?

Maybe something like https://github.com/TheCheatsrichter/Gw2_Launchbuddy/pull/54

Unfortunately @KairuByte is right, and changing the launch directory did not fix the issue (probably due to how the game launches itself). This means the only alternative fix besides changing the gw2 client is in fixing ReShade's crash.


Make: rebuild when header files change

Closes #64

Updated to fix all exercises

LGTM

Looks good 👍


TS2345 error when using function generics for React Components

🔎 Search Terms
React TS2345 instantiated with a different subtype of constraint
⏯ Playground Link
https://www.typescriptlang.org/play?pretty=false&ts=4.9.5&ssl=24&ssc=1&pln=2&pc=2#code/FASwtgDg9gTgLgAgEoFMCGBjOAaBBvVTOAUQBsUwUA7HBAVwGcViAzFlLAXwRZijAQByGOiyCA3MFA0UMFphQIACnwgMAPABUEKAB5xqAEwb4EAbQZwYALgSWYIKgHMAurfuOnnAHx5gCAIQMNFJSACNMAGtbAAo0GCcGW00ASgQAXm8EADcoEENJTikMKCpLZQyELR19IxM8c3t3K083OxbncQRObG8YvGDQiIxIzlsVKDUtbxTbQiwyCmpETPwpQPomVnYsGJi01b8NwMHwqP6eEBRSQyo0SltBNEFulMkNnvMXN-9AkTg6DAqAgYr9jlUABYAJm8EOuEHUAHpod4wQgfkVgCw6FQsCBSggIWgqIZyABhEJnEZxBJJUwsK43O4PdoOTqvWy5fJrAIlMpQcgAOlIUCcNMSGKkwHUSiqeAZ11u9xQzTZXiyp2GkXSeCJJPJlK13ERqKkQA
💻 Code
import React, {ReactElement, useEffect} from 'react';

interface Props<T extends { [str: string]: string}>{
    callback: (args: T) => void;
}

const P = <T extends { [str: string]: string; },>({callback}: Props<T>): ReactElement => {

    useEffect(() => {
       callback({ fieldname: 'a' });
    }, []);
    return (

help

    );
}

function handleCallback(args: { fieldname: string; }): void {
  console.log(args);
}

<P <{fieldname: string}> callback={handleCallback} />

🙁 Actual behavior
TypeScript is reporting an error.
Argument of type '{ fieldname: string; }' is not assignable to parameter of type 'T'.
  '{ fieldname: string; }' is assignable to the constraint of type 'T', but 'T' could be instantiated with a different subtype of constraint '{ [str: string]: string; }'.

example
🙂 Expected behavior
I don't understand why typescript is complaining about this error.
Additional information about the issue
No response

It's because you can do this:
<P<{ fieldname: "b" }> callback={handleCallback} />;

In this scenario, your { fieldname: "a" } is not assignable to this instantiation of T. This means that it can't be trusted within the P's implementation as something that is definitely assignable to T.


Remove version: taers232c.GAMADV-XTD3 version 6.75.01

This version is older than what has been set in max-versions-to-keep by the publisher.
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/taers232c/GAMADV-XTD3/releases/download/v6.75.01/gamadv-xtd3-6.75.01-windows-x86_64.msi
OK
(Automated message - build 910)


Update LICENSE to include MIT rather than BSD license

Apparently the MIT license was indented for this
project as per the setup.py file but somehow a
copy of the 3-clause BSD license was included in
the LICENSE file.

Im not an expert on LICENSEs, I will ask someone at Onelogin to review.


Template Project not created

I tried to create a template project by clicking the template "Create Project" from the URL below.
"Congratulations! Your project is successfully provisioned." is displayed,
I clicked "Navigate to project" but I get a 404 Not found page.
https://azuredevopsdemogenerator.azurewebsites.net/environment/createproject

I solved it below.
https://github.com/microsoft/AzureDevOpsDemoGenerator/issues/1075


 Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you check the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: backend/go.sum
Command failed: go mod tidy
github.com/lyft/clutch/backend/service/k8s imports
	k8s.io/client-go/kubernetes imports
	k8s.io/client-go/kubernetes/typed/auditregistration/v1alpha1 imports
	k8s.io/api/auditregistration/v1alpha1: module k8s.io/api@latest found (v0.19.1), but does not contain package k8s.io/api/auditregistration/v1alpha1


Clarify that DefaultMember is applied in the CPP file

Fixes #24906

ping @adegeo for review

closing and reopening for a fresh build

closing and opening for a fresh build


No Smooth Scroll on Mobile if Finger not Lifted Up While Scroll

Checks

[X] Not a duplicate.

Version
8.7.4
Description
Summary
Hi, I have ran into this issue today.  But If I don't lift my finger and keep swiping with my finger pressed, then smooth scroll doesn't occur.
-Note: This is comparable to how earlier smooth-scroll didn't happen when using scrollbars but later in an update that support was added-
Expected Behaviour
I want to know how to get smooth-scroll when holding down my finger and swiping,
I have attached a demo video showing this.
Steps to Reproduce
Just Use on A Mobile Device check this demo also
https://user-images.githubusercontent.com/67477131/153308306-c1244109-8a95-45ee-9f13-f4aeb7090a6a.mp4
Online Demo
No response

This is a by-design behavior that follows the native scrolling. Inertial scrolling on touch devices depends on the moving velocity of the pointer, so the calculated extra scrolling distance will be short (or almost not scrolling) if you move slowly.

This plugin also prevents smooth scrolling while the pointer moves on touch devices. You can use the following plugin to "lock" the damping value to enable smooth scrolling:
class SmoothTouchScrollPlugin extends ScrollbarPlugin {
  static pluginName = 'smoothTouchScroll';

  transformDelta(delta, fromEvent) {
    if (fromEvent.type === 'touchmove') {
      this.scrollbar.options.damping = 0.1; // change this to whatever you want
    }

    return delta;
  }
}

Love it 😍 Exactly Solves My Problem
Thank You Bro


create sql infrastructure

done and merged

Good one Roz :)
Thanks!
Kane Robinson
0433 788 336
On Thu, 28 May 2020 at 11:15, Roz Hamilton<EMAIL_ADDRESS>wrote:

done and merged
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Kane-R/Project2/issues/4#issuecomment-635070504, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AOPBTBD5JCAVB6WT6VWU7ITRTXJMXANCNFSM4NMB43HQ
.


Add option to manually run upstream CI build

cc @charlesbluca @j-bennet

Have we verified that things work as expected when triggered with workflow dispatch? I'm not too familiar with the behavior of always() in workflows so it's not immediately obvious to me if the build job would run even when check gets skipped


Error on ipsec and healthcheck

When I add new host, in initialization time i got an error on three services:

ipsec
ipsec-router
healthcheck

but ipsec-cni-driver works fine.
Error message:
Error (Couldn't bring up network: failed to find plugin "rancher-bridge" in path [/opt/cni/bin /var/lib/cni/bin /usr/local/sbin /usr/sbin /sbin /usr/local/bin /usr/bin /bin])
I tried copy rancher-bridge from another host, but I got new error:
Error (Couldn't bring up network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input).
The same errors i got in v1.6.3.
Stacktrace on server:
2017-06-28 13:32:35,734 ERROR [b30c0a2f-ab9c-43be-8457-235a9d01c4f6:3148] [instance:123] [instance.start->(InstanceStart)] [] [cutorService-40] [i.c.p.process.instance.InstanceStart] Failed [Dependencies readiness error instance is not running] for instance [123]
2017-06-28 13:32:36,026 ERROR [f127ff18-d2a4-4f51-adc3-57b0fb6ecf85:3138] [instance:121->instanceHostMap:121] [instance.start->(InstanceStart)->instancehostmap.activate] [] [cutorService-55] [c.p.e.p.i.DefaultProcessInstanceImpl] Agent error for [compute.instance.activate.reply;agent=6]: Timeout getting IP address
2017-06-28 13:32:36,026 ERROR [f127ff18-d2a4-4f51-adc3-57b0fb6ecf85:3138] [instance:121] [instance.start->(InstanceStart)] [] [cutorService-55] [i.c.p.process.instance.InstanceStart] Failed [1/5] to Starting for instance [121]
2017-06-28 13:32:36,071 ERROR [f127ff18-d2a4-4f51-adc3-57b0fb6ecf85:3138] [instance:121->instanceHostMap:121] [instance.start->(InstanceStart)->instancehostmap.activate] [] [cutorService-55] [c.p.e.p.i.DefaultProcessInstanceImpl] Agent error for [compute.instance.activate.reply;agent=6]: Timeout getting IP address
2017-06-28 13:32:36,072 ERROR [f127ff18-d2a4-4f51-adc3-57b0fb6ecf85:3138] [instance:121] [instance.start->(InstanceStart)] [] [cutorService-55] [i.c.p.process.instance.InstanceStart] Failed [2/5] to Starting for instance [121]
2017-06-28 13:32:36,114 ERROR [f127ff18-d2a4-4f51-adc3-57b0fb6ecf85:3138] [instance:121->instanceHostMap:121] [instance.start->(InstanceStart)->instancehostmap.activate] [] [cutorService-55] [c.p.e.p.i.DefaultProcessInstanceImpl] Agent error for [compute.instance.activate.reply;agent=6]: Couldn't bring up network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
2017-06-28 13:32:36,114 ERROR [f127ff18-d2a4-4f51-adc3-57b0fb6ecf85:3138] [instance:121] [instance.start->(InstanceStart)] [] [cutorService-55] [i.c.p.process.instance.InstanceStart] Failed [3/5] to Starting for instance [121]
2017-06-28 13:32:36,148 ERROR [f127ff18-d2a4-4f51-adc3-57b0fb6ecf85:3138] [instance:121->instanceHostMap:121] [instance.start->(InstanceStart)->instancehostmap.activate] [] [cutorService-55] [c.p.e.p.i.DefaultProcessInstanceImpl] Agent error for [compute.instance.activate.reply;agent=6]: Timeout getting IP address
2017-06-28 13:32:36,149 ERROR [f127ff18-d2a4-4f51-adc3-57b0fb6ecf85:3138] [instance:121] [instance.start->(InstanceStart)] [] [cutorService-55] [i.c.p.process.instance.InstanceStart] Failed [4/5] to Starting for instance [121]
2017-06-28 13:32:36,181 ERROR [f127ff18-d2a4-4f51-adc3-57b0fb6ecf85:3138] [instance:121->instanceHostMap:121] [instance.start->(InstanceStart)->instancehostmap.activate] [] [cutorService-55] [c.p.e.p.i.DefaultProcessInstanceImpl] Agent error for [compute.instance.activate.reply;agent=6]: Couldn't bring up network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
2017-06-28 13:32:36,181 ERROR [f127ff18-d2a4-4f51-adc3-57b0fb6ecf85:3138] [instance:121] [instance.start->(InstanceStart)] [] [cutorService-55] [i.c.p.process.instance.InstanceStart] Failed [5/5] to Starting for instance [121]
2017-06-28 13:32:36,192 ERROR [f127ff18-d2a4-4f51-adc3-57b0fb6ecf85:3138] [instance:121] [instance.start] [] [cutorService-55] [c.p.e.p.i.DefaultProcessInstanceImpl] Agent error for [compute.instance.activate.reply;agent=6]: Couldn't bring up network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
2017-06-28 13:32:36,216 ERROR [:] [] [] [] [cutorService-55] [.e.s.i.ProcessInstanceDispatcherImpl] Agent error for [compute.instance.activate.reply;agent=6]: Couldn't bring up network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
2017-06-28 13:32:36,740 ERROR [874a0958-d5aa-421f-868c-ff19cca4dce0:3133] [service:4] [service.update] [] [cutorService-58] [c.p.e.p.i.DefaultProcessInstanceImpl] Expected state running but got error: Couldn't bring up network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
2017-06-28 13:32:36,744 ERROR [:] [] [] [] [cutorService-58] [.e.s.i.ProcessInstanceDispatcherImpl] Expected state running but got error: Couldn't bring up network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
2017-06-28 13:32:37,033 ERROR [3823be36-d2eb-4802-9775-39920069ded1:3144] [instance:122->instanceHostMap:122] [instance.start->(InstanceStart)->instancehostmap.activate] [] [cutorService-53] [c.p.e.p.i.DefaultProcessInstanceImpl] Agent error for [compute.instance.activate.reply;agent=6]: Timeout getting IP address
2017-06-28 13:32:37,033 ERROR [3823be36-d2eb-4802-9775-39920069ded1:3144] [instance:122] [instance.start->(InstanceStart)] [] [cutorService-53] [i.c.p.process.instance.InstanceStart] Failed [1/5] to Starting for instance [122]
2017-06-28 13:32:37,090 ERROR [3823be36-d2eb-4802-9775-39920069ded1:3144] [instance:122->instanceHostMap:122] [instance.start->(InstanceStart)->instancehostmap.activate] [] [cutorService-53] [c.p.e.p.i.DefaultProcessInstanceImpl] Agent error for [compute.instance.activate.reply;agent=6]: Timeout getting IP address
2017-06-28 13:32:37,090 ERROR [3823be36-d2eb-4802-9775-39920069ded1:3144] [instance:122] [instance.start->(InstanceStart)] [] [cutorService-53] [i.c.p.process.instance.InstanceStart] Failed [2/5] to Starting for instance [122]
2017-06-28 13:32:37,132 ERROR [3823be36-d2eb-4802-9775-39920069ded1:3144] [instance:122->instanceHostMap:122] [instance.start->(InstanceStart)->instancehostmap.activate] [] [cutorService-53] [c.p.e.p.i.DefaultProcessInstanceImpl] Agent error for [compute.instance.activate.reply;agent=6]: Couldn't bring up network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
2017-06-28 13:32:37,132 ERROR [3823be36-d2eb-4802-9775-39920069ded1:3144] [instance:122] [instance.start->(InstanceStart)] [] [cutorService-53] [i.c.p.process.instance.InstanceStart] Failed [3/5] to Starting for instance [122]
2017-06-28 13:32:37,171 ERROR [3823be36-d2eb-4802-9775-39920069ded1:3144] [instance:122->instanceHostMap:122] [instance.start->(InstanceStart)->instancehostmap.activate] [] [cutorService-53] [c.p.e.p.i.DefaultProcessInstanceImpl] Agent error for [compute.instance.activate.reply;agent=6]: Timeout getting IP address
2017-06-28 13:32:37,172 ERROR [3823be36-d2eb-4802-9775-39920069ded1:3144] [instance:122] [instance.start->(InstanceStart)] [] [cutorService-53] [i.c.p.process.instance.InstanceStart] Failed [4/5] to Starting for instance [122]
2017-06-28 13:32:37,215 ERROR [3823be36-d2eb-4802-9775-39920069ded1:3144] [instance:122->instanceHostMap:122] [instance.start->(InstanceStart)->instancehostmap.activate] [] [cutorService-53] [c.p.e.p.i.DefaultProcessInstanceImpl] Agent error for [compute.instance.activate.reply;agent=6]: Couldn't bring up network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
2017-06-28 13:32:37,216 ERROR [3823be36-d2eb-4802-9775-39920069ded1:3144] [instance:122] [instance.start->(InstanceStart)] [] [cutorService-53] [i.c.p.process.instance.InstanceStart] Failed [5/5] to Starting for instance [122]
2017-06-28 13:32:37,226 ERROR [3823be36-d2eb-4802-9775-39920069ded1:3144] [instance:122] [instance.start] [] [cutorService-53] [c.p.e.p.i.DefaultProcessInstanceImpl] Agent error for [compute.instance.activate.reply;agent=6]: Couldn't bring up network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
2017-06-28 13:32:37,238 ERROR [:] [] [] [] [cutorService-53] [.e.s.i.ProcessInstanceDispatcherImpl] Agent error for [compute.instance.activate.reply;agent=6]: Couldn't bring up network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
2017-06-28 13:32:37,758 ERROR [032b202a-cd5b-430f-8ff9-abfcbd142b40:3134] [service:5] [service.update] [] [cutorService-60] [c.p.e.p.i.DefaultProcessInstanceImpl] Expected state running but got error: Couldn't bring up network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
2017-06-28 13:32:37,764 ERROR [:] [] [] [] [cutorService-60] [.e.s.i.ProcessInstanceDispatcherImpl] Expected state running but got error: Couldn't bring up network: netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input

Useful
Info

Versions
Rancher v1.6.0 Cattle: v0.179.7 UI: v1.6.5

Access
github admin

Orchestration
Cattle

Route
hosts.index

Seconded.  We're seeing this as well but with etcd-2 also on the list. (though if you blink at the wrong time you'll miss it)
Docker is stock RHEL7 and rancher-agent is v1.2.2.

@Spoki4 are your agent hosts able to communicate freely across udp ports 500 and 4500? Seems the ipsec tunnel is broken. You can check that by pinging across the ipsec containers using their 10.42 addresses. In the hosts screen, do your hosts reflect their correct IP addresses?

@Spoki4 Can you please @aemneina's pointers? There are few suggestions in this issue also: https://github.com/rancher/rancher/issues/8383

Ping @Spoki4 ... are you still facing problems?

I had 2 servers, 1 host of rancher and my app, 2 for my app. If I add first server in rancher, I got this problem. Now I solved this problem so I didn't add first server in rancher and bought 3 server for my app. Now I have 3 servers and digital cloud droplets:
1 - rancher
2 - my app
3 - my app
n - digital cloud droplets

baving the same issue with 1.6.10 with correctly set IPs

@tuwid can you file a new issue with logs and details of what youre doing? This is a closed ticket and seems related to an older version of rancher.


update wazuh vulnerability detector

removed rh 7 and ubuntu bionic releases
added rh 9 and ubuntu jammy releases

Looks like CI is broken, but it won't test this change anyway.


Not able to see the SSLO/R grid  dashboard under the Services-APM section

We have defined a SLO for my app using APM agent under SLo/R in the left side pane. Once it is created we are not able to see it in SLO dashboard.
Steps to Reproduce
NOTE: # 1. Login into the New relic account.
NOTE: # 2. Click the SLO/R under the APM agent section.
NOTE: # 3. Click the define SLO button and provide the necessary details.
NOTE: # 4. Click add service button.
Expected Behaviour
NOTE: # We should be able to see the SLO of our Service section
Relevant Logs / Console output
Your Environment

NR1 CLI version used: N/a (created through one.newrelic.com portal)
Browser name and version: Chrome 98 version
Operating System and version: MacOs

Additional context

We also checked in our SLO/R apps to see our created SLOs of our Apps, We Couldnt see there also.


Error when posting tx: cannot parse disfix JSON wrapper

Sending a tx to a custom SDK module (voter).
const signedTx = {
  "msg": [
    [
      {
        "type": "voter/CreatePoll",
        "value": {
          "ID": "970309f2-fb0d-49b6-aaed-67c63540b0a0",
          "creator": "cosmos1nrr7ywy0krtpudeyyvr326lvz3w8897p6vlj87",
          "title": "Soft drinks",
          "options": [
            "Coca-Cola",
            "Pepsi"
          ]
        }
      }
    ]
  ],
  "fee": {
    "amount": [],
    "gas": "200000"
  },
  "memo": "",
  "signatures": [
    {
      "pub_key": {
        "type": "tendermint/PubKeySecp256k1",
        "value": "AqXldvsZkgcjKGegM1R9KOIy6o+CGsI47jMvoB7lcm3R"
      },
      "signature": "WVqPufGnPkF4+5nRLqGfLK2tDMdc6JxhcRAMRWRBEfYKgWi+Dqzb5kcWVcfKNSnlfTQ4ibHyn4yzqe8ZcBSo6A=="
    }
  ]
}

client.postTx(signedTx) // client is SigningCosmosClient

Getting an error: {"error":"cannot parse disfix JSON wrapper: json: cannot unmarshal array into Go value of type amino.disfixWrapper"}

Rest of the code:
const API = "https://localhost:1317"
const mnemonic = "cattle fossil energy reject spare budget ecology sugar state gym obtain clarify achieve gadget ghost valve trick topic cattle tribe front choice switch account"
const wallet = await Secp256k1Pen.fromMnemonic(mnemonic);
const address = wallet.address("cosmos");
const client = new SigningCosmosClient(API, address, wallet);
const { accountNumber, sequence } = await client.getNonce();
const address = client.senderAddress;
const chain_id = client.getChainId();
const req = {
  base_req: { chain_id, from: address },
  creator: address,
  "title": "Soft drinks",
  "options": [
    "Coca-Cola",
    "Pepsi"
  ]
};
const type = "poll"
const { data } = await axios.post(`${API}/${chain_id}/${type}`, req);
const { msg, fee, memo } = data.value;
const signBytes = makeSignBytes(
  [msg],
  fee,
  chain_id,
  memo,
  `${accountNumber}`,
  `${sequence}`
);
const signatures = [await wallet.sign(signBytes)];
const signedTx = { msg: [msg], fee, memo, signatures };
client.postTx(signedTx);

Hi @fadeev, thanks for the report. Which version of cosmjs are you using and what are you running it against (e.g. which version of Cosmos SDK)?

Hi, @willclarktech! I'm using v0.38.4 and "@cosmjs/sdk38": "^0.21.1"

Glad to hear it works for you.

We're using Vue and I prefer to keep it with as few customizations as possible. With Vue 3 we'll switch to TS.

Interesting, thanks for sharing. I don't know Vue very well.


Hex.len()

@rultor release, tag is 0.0.9

@rultor release, tag is 0.0.9

@yegor256 OK, I will release it now. Please check the progress here


npo_watchlist grid-favourite can be missing, spawns an error

If using npo.nl with e.g. max_episode_age_days set it can easily occur that no recent favourites are shown in the mijn.npo.nl list.
This spawns an error, because on line 241 (but also 245 and 249) silently assume that the div with grid-favourite-episodes-today will exist, even though it does not. We need to do more checking if episodes is not None before staring the parsing (are make the parsing safe for None-types)
Log:
2017-08-13 20:48 CRITICAL task          Series-NPO      BUG: Unhandled error in plugin npo_watchlist: 'NoneType' object has no attribute 'findAll'
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/flexget/task.py", line 486, in __run_plugin
    return method(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/flexget/event.py", line 23, in __call__
    return self.func(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/flexget/plugins/input/npo_watchlist.py", line 262, in on_task_input
    entries += self._get_favorites_entries(task, config, page)
  File "/usr/local/lib/python2.7/dist-packages/flexget/plugins/input/npo_watchlist.py", line 225, in _get_favorites_entries
    return self._get_recent_entries(task, config, page)
  File "/usr/local/lib/python2.7/dist-packages/flexget/plugins/input/npo_watchlist.py", line 242, in _get_recent_entries
    entries = self._parse_tiles(task, config, episodes)
  File "/usr/local/lib/python2.7/dist-packages/flexget/plugins/input/npo_watchlist.py", line 168, in _parse_tiles
    for list_item in tiles.findAll('div', class_='npo-asset-tile-container'):
AttributeError: 'NoneType' object has no attribute 'findAll'

@jeroenl would you have time to take a look at this?


"Last updated" uses US date format, not local

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[ ] I have tried the npm run clear or yarn clear command.
[ ] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[ ] I have read the console error message carefully (if applicable).

Description
Doc pages have e.g. Last updated on 4/25/2022 by Simen Bekkhus, which is the US locale. This makes the date ambiguous when the date is 1-12. While that would still be the case if the date uses the local locale, at least I'd read it correctly 😅
Reproducible demo
https://github.com/facebook/jest
Steps to reproduce
Look at the bottom of e.g. https://jestjs.io/docs/jest-object#fake-timers
Expected behavior
For non-US locales, that it says Last updated on 25/04/2022 by Simen Bekkhus, like new Intl.DateTimeFormat().format() returns when I run it in the Chrome console. I.e. uses local locale, not US locale.
Actual behavior
It uses US date formatting.
Your environment

Public source code:
Public site URL: https://jestjs.io/
Docusaurus version used: 2.0.0-beta.18
Environment name and version (e.g. Chrome 89, Node.js 16.4): Chrome 100 (and whatever version of node Netlify uses)
Operating system and version (e.g. Ubuntu 20.04.2 LTS): macOS 12.13.1

Self-service

[ ] I'd be willing to fix this bug myself.

It's a bit complicated and constantly brought up, but even after https://github.com/facebook/docusaurus/pull/6430, we don't have a good way to fix this issue (or is it an issue?) yet. We've added a little explanation in our docs. Basically, because the site's locale is en, which defaults to en-US, we choose to display the US date format instead.
Maybe we should update the date formatting once we are in browser in useEffect? @slorber thoughts? Would that be weird since the markup changes after hydration?

I tried to search for an existent issue, didn't find those... But yeah, I don't want to decide per locale, I'd want the user's locale to "win". I've never really used React's hydration, so I don't have anything to contribute as to how feasible it is 😀 But defaulting to US is sorta weird (albeit understandable) - they're the only ones who use it 😅 Could do ISO? e.g. yyyy-MM-dd? No ambiguity (albeit somewhat specific to code, but docusaurus is mainly dev docs, so maybe fine?)

We don't specifically format the date by some format; we format it by currentLocale using Intl.DateTimeFormat. And it happens that per ISO spec, en defaults to en-US, so new Intl.DateTimeFormat("en").format(Date.now()) is 4/27/2022. And we probably don't want to have a special case for en where we always use yyyy-MM-dd, because... well, special cases are evil. Plus, if you use en-GB as locale name, you probably want specifically dd-MM-yyyy. Updating the date format after hydration is not a big problem IMO, considering it's usually below the visible area when the page first loads.

I added a suggestion of ISO after original post, might be a good middleground?

It's usually not that ambiguous. e.g. fr would format the date as dd-MM-yyyy which seems reasonable to every French-speaking person. It's just English that has this complication😅 And when it comes to i18n, it's usually not the site creator's call to say what to display, so an config option doesn't seem right to me either. So the solutions I can think of are:

Special-case en (which is the default anyways, so it is already special in some sense) where we always use yyyy-MM-dd
Update the date format after hydration

Both seem like good ways out.

Wow, i18n is complicated... We should stop assuming language === region and update region-specific tags everywhere...

Will keep this open until we provide more flexibility for users to define how they want to handle blog/doc date formats
See also https://github.com/facebook/docusaurus/pull/7673#issuecomment-1170186409


[Task]: Git sync UI polishing

SubTasks

[ ] This can use some UI/UX improvements. The problem is with the formatting of the error messages, specially the dual alert icon.

[x] The hover label takes 2-3 seconds to show. This should be instant.

[ ] The repo disconnection today feels like we can add a new repo link after deleting. Whereas we completely delete the git data from that app. This needs some UX improvements.

[x] When you open branch window, everything in the background should be covered with a translucent layer. Shifting the focus on the branches, its a crucial action to switch branch. Also we need to remove BETA tag from here.

[ ] This error pops up when someone clicks remote branches.

[ ] The hover states for modal are not there. Please follow the new modal design.

[x] The edit navigation (link) needs to be removed. We can simply say go to your profile and edit default. Also when you toggle default configuration the Author name and Author email goes blank. We can make these editable and existing information can still be there.

[x] The placeholder for new repo url can be some dummy format hinting about the SSH repo url.

[ ] The git errors should point towards the field which can be fixed to correct this. This can use some design help.

[x] Placeholder for commit input is missing

[x] Bug on resize of the commit input.

[x] The time for latest deployed preview link should say “less than 1 min ago” instead of 0 seconds ago.

[x] When commit number is 9+ things break.

When commit number is 9+ things break.

@hiteshjoshi @Debsourabh

Please provide details of what's breaking, and
Please suggest the solution.

@IAmAnubhavSaini did you get answers for your queries in the last two comments?

@vuiets No.

For the comment here we can go with whole numbers.

Git tooltip message update.

"Commit changes" to "Commit"
"You have uncommitted changes .... " to "Pull"

@hiteshjoshi IIRC we had decided to keep the tooltips more friendly by appending changes for git actions like commit changes, pull changes etc. Is there any reason we are again moving away from this?

@abhvsn
Single word: Its cleaner. Users are developers, they know what commit/pull/merge mean. That's my reasoning for it.
For visual indicator thing, I don't think that we should show number of changes on quick-actions at all. Think of the flow without a number or an another hint that there are changes to be committed.
Wouldn't user want to deploy their app after making changes? What happens when they click deploy button?
Today users do deploy their apps after making changes.
After clicking on deploy, users will see the change list on modal.
And we show an * next to branch name if it has changes.
But for the mean time, till we decide which way to go, I have gone ahead and made code changes such that exact number of changes is visible. The alternative was to stay with (9+) thing, which we had agreed to change.
I opined that there will be few cases where users are making 99+ changes without commit/deploy.

@IAmAnubhavSaini

Appending changes text makes action tone friendly, that's why we changed the earlier tooltips from commit, pull etc to what we have today. It's not about if user understands these terms because both the terminologies are clear enough IMO, it's just that we are bringing the same nomenclature where we started off, that's why this resistance. (Also I can understand this is a small change so this discussion might not be required, but wanted to know why we went in other direction if this is fine for everyone now 🙂)
Agreed we can keep the actual count now and update this later. It's just that when we run migration on multiple resources there is high chance of seeing huge number which might scare the user.

Scrolling issue is fixed in https://github.com/appsmithorg/appsmith/pull/11813


feat(protocol): Batch

Description
kona-derive is nearly decoupled from protocol-level types. The final remaining types are the batch types: single and span batches.
This PR ports over all batch types from kona-derive's batch module, introducing a new minimal trait abstraction for batch validity checks called the BatchValidator. Effectively, it is a subset of the L2ChainProvider trait in kona-derive.
Additional Context
Works on https://github.com/anton-rs/kona/issues/695

This PR is replaced by the stack started in #186


fail to publish from the github action

FYI, https://github.com/k-paxian/dart-package-publisher/issues/25

so probably if you need to have this constraint for flutter in place, you should pass an action input flutter: true to let it understand that it should be invoked via flutter pub command

Must pass flutter: true as action input.


Reasons I cannot use Pirate Weather in my apps

First of all thanks for providing an alternative weather API. Unfortunately, after spending $25 with the intention of evaluating this in my apps for a month, I had to switch away to another service (using WeatherKit) after just a few days.  The following are all reasons why I had to discontinue using your API, and I hope this may illustrate items that you might want to address in case other developers have needs similar to mine.

Inaccurate high temperatures in the evening (I believe after 7 PM). The forecasts show a seemingly random (IE not the high for the current day or the next day) high temperature during the evening time for the current (zero index) day. This temperature appears to represent the highest temperature for the rest of the daily forecast range, as it is greater than the high for the current or next day. For example, today's high was only 62. Tomorrow's high is 68, the next day is 69. However the first entry in the daily->data array shows a high of 72.57. This appears to be the high temperature 3 days from now, and is grossly incorrect for the current day forecast.

API latency. The API response time I see, minimum, is over 1000 ms. This is far too slow for an API of this kind, and is probably the result of the on-demand AWS lamdba functions having to process into a massive dataset for each request. Sure this is convenient on your end, for scalability, ease of implementation and only paying AWS for the minimum processing you need, but it is at a performance cost for all end users. If you really want to provide nationwide coverage, then pre-generating static json in 3km grids would result in vastly faster response times, and if your service grows in use, will actually require less processing on average as well. Regardless, this latency is directly passed down to my app users (although I cache county-wide data in 15 minute intervals to save on API calls, so at least some of the requests are cache hits), and it is far too slow.

Cost. I already pay $100 a year for the Apple Developer Program, so basically I get 500k REST weather requests a month free. However even if I didn't, it would still only cost $8.33 a month for 500k requests purely to access weather from Apple. Pirate Weather costs $25 a month for 300k requests, which is 3 times as much for less requests. Further it isn't clear what happens when I exceed 300k requests, or how one goes about paying for a plan to get more than 300k requests per month.

There is no way (that I could find) to track my API request usage. Sure, I can try and count this on my end, but whatever the service itself is counting is what really matters, as that is the limit that, when exceeded, could immediately cause my app's weather to cease functioning for the remainder of the billing period.

The Minutely, Hourly and Daily "summary" is no longer a summary as it was in DarkSky, but is just a precipitation condition code, like "Clear" or "Rain". The "Clear" value is apparently used to represent any condition that is not precipitating. Thus overcast, foggy, cloudy, etc all has a summary of "Clear" which is highly inaccurate. Regardless, the summary fields were, for my use, the highest value piece of information in the entire forecast dataset (with the possible exception of the low and high temp). This is not generated by your API, so this cannot serve as a drop-in DarkSky replacement for me, which is how the service is advertised.

The code used by the API is not open source, as the true core of the implementation, which is whatever is generating the JSON output, has not been released. I believe this is the code that is in error or deficient as discussed above, and the lack thereof also prevents me from rolling my own internal processing of NWS data to pre-calculate the data I need instead of doing so only on demand. So I am unable to fix, enhance or increase the performance of this service. It just seems to advertise as an open source service when it isn't.

I have the same concerns in the inverse priority order.

Hi,
Thank you so much for taking the time to write out this list- your points here are clear, well laid out, and well taken on my end. I came to this project from a data processing standpoint, which means I'm very new to thinking about a lot of the concerns you're raising.
While I can't promise I'll have terribly satisfying answers, I'll do my best to address these in turn:

This is a long-standing issue, and relates to a more systemic problem of how I handle recent historic data. I set everything up going forward from an initial forecast, so anything outside of this paradigm creates a ton of issues. As it stands now, it's not random, but not as good as it should be. I have a solid plan for how to address this, but it involves changing my processing pipeline, so not as easy of a fix as I would like. If you're interested in the full discussion, it's all in issue #5.

Yup, your guess here is spot on- the time is what's required for Lambda to go and read the data/ process everything. It works well enough at the moment for a lot of non-time sensitive applications, but I completely understand why it's too slow. The only bit of good news here is that I've improved this a lot over the past year (going from ~1500 ms to ~800ns), and I have some longer term ideas to get this below ~500ms, but I don't think it'll ever be faster than that.

This isn't something I'd heard before, so appreciate hearing this! I picked the prices to be about 75% of Dark Sky, but I should take a look at what Apple Weather and other providers are up to. My main concern is being able to cover the costs of the free tier, so once I get a better idea of what the ratio of paid/ unpaid subscribers is, I'll hopefully be able to bring this down.

This is a big issue, and has become the top priority on my roadmap! I'm getting close to the limits imposed by AWS on their API gateway, so moving to Kong, which will return the number of requests as a header. At the current rate of signup, I'll hit the AWS limit in the next month, so I'll have to get this working before then!

Another big issue, and one I was working on before I realized how close I was to the API limits. This comes down to a giant series of IF statements, so not a particularly complex problem, but one that takes a while to write up.

Great point, and compared to the other issues, technically easy to fix at least! I really want this to be open and transparent, hence the variable documentation, but I also have an existential fear of Amazon or someone coming along and just replicating this service on their own. My gut says that I shouldn't worry too much about that, and I'd be fine to just publish the script (it's only 2000 lines of Python, so not exactly groundbreaking), but it's something I'm still mulling over. In the meantime, I'm always happy to explain how anything is calculated, and you should always be able to reference the original model data.

To be perfectly honest, I've been blown away by the interest in this, and so I really apologize that it's pretty rough around the edges. In the last month, the level of traffic has grown 10x, which is incredibly exciting and motivating, but also raises the expectations a lot. I'm hopeful that in a few months this will have improved to the point I can address some of these concerns, and again, appreciate the time you took to write everything out.

Thanks for your extremely detailed response! Some further comments on my end.

I think the ideal solution, once your usage increases to a certain point, is to precalculate the entire country (or at the least precalculate any 3km cells that have been requested recently) into static json that can be served with practically zero overhead (or even better, purely by a CDN). As an example, say in a very densely populated area you receive 500 requests per time bucket (I think I read you process in 15 minute intervals), so you are repeating the same processing 500 times to output the same data. It would be far more economical to use a standard EC2 compute instance to be doing that work every 15 minutes than on-demand Lambda per request. The performance of your service, to the end user, would be incredibly fast.

WeatherKit is the official replacement for DarkSky, but it is neither a drop-in replacement (it is extremely similar but many field names have changed), nor does it contain any text forecasts at all (same exact issue as #5). So although it is "free" for existing app developers like myself, it is still not suiting my needs.  In regards to cost, my normal monthly DarkSky requests were in the low 100,000s. Looking back at my invoices, my monthly costs were around $10-$12.  With your service pricing tiers my only option was to use your most expensive "all the data" tier at $25. So although you priced your service at 75% of that of DarkSky for 300k requests, I am paying over 200% more than DarkSky for my 100k requests.

As I mentioned in #2, WeatherKit is not providing this either. When I chose DarkSky several years ago it was because of the extremely good text forecasts their API provided over anything else I evaluated. I think I was using Weather Underground API up until that point (and they stopped providing their service or began charging a ridiculous amount to use it - I can't remember which), and I was extremely impressed with DarkSky's text forecasts. They were both extremely detailed, and very concise (IE compact and not wordy). I think there is a big space here for you to fill that gap in text based forecasts. In my apps, the display of the day's weather forecast and current conditions is secondary to the primary information displayed in my app (car accidents, power outages, weather alerts, school closings, earthquakes...), and I do not need a robust data set, but just a simple concise text based forecast. At this point my plan is to implement my own routines to generate that from the lower-level data, but hopefully you'll beat me to it.

For me personally, I have flirted with the idea of getting the data I need directly from NWS for a long time now, and I have implemented back end stuff to consume from their "new" higher-level API (https://weather-gov.github.io/api/general-faqs) when it went live a few years ago, but their new API was never stable enough for me to actually use it. Plus it is missing some very basic pieces of information that appeared to be pure oversight on their end. So I made the decision to consume weather data from 3rd parties (DarkSky, Pirate Weather, etc) until I could make the "big" leap and consume the GRIBs directly. However on my end I would be processing the GRIBs on a fixed schedule so the data my apps need are sitting there as static JSON ready for them to consume. So again, for me personally, your implementation would not suite my needs (on-demand Lambda based), and I'm also very loathe to commit to any provider's proprietary services (I have steered the companies I work for away from Lambda on multiple occasions, and this has saved a tremendous amount of money), and in general I prefer a LAMP stack for the massive amount of flexibility it provides on the hosting side. However I'm always happy to look at code for purposes of understanding data formats or what hoops I need jump through. Still as a fellow developer I totally understand your stance and that is a totally legitimate concern.

You could release it with GPL license or something similar. I understand your concerns, but if it's not released it prevents people (including me) to contribute to that part of the project and pushes all the development burden to you.

I'd love to contribute to the frontend code too. That'd enable non-json response formats that could be more memory efficient.

@oisact I have a weather app too and I have similar concern with you. So this is some reason I will not using Pirate Weather in my apps:
1, The author want to startup a weather service with open data, he will not open source all the code.
He only share some code of it it gain trust from retire Dark Sky user.
2, The quality of data never near the old Dark Sky or the new in the hand of Apple with many commercial source of data, I have a developer account there and using it.
3, Many opensource project, they open all the code, but still get the value back in money, like Home Assistance, Ubuntu Linux ... there many way to get the money back, not by close its source code. Or first they open it all until the product reach stable level.


Portal is undefined in android

I am trying to use with new react-native version but got error " portal is undefined "
please say what can i do ??

is your react-native version > 0.29?


fix(pacmak): python pack fails when installing 'black' via pip

The failure is because of intermittent unavailability of black or one of
its packages from the PyPI index.
Instead, install back into the environment, i.e., superchain, and use
that.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: b0c3d38f9d6ebfc82d635b85c8cf122772390720
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 0d75233667acb0e6537bc7afb250c4923df7746d
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Feels a bit weird to include this in superchain, but I see the pragmatic reasoning.

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 097a007d8943007afdae34ffce3a6d99fc51707d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 557585d9f46a2461e342bb44d957eb219f8ef9df
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository