Properly propagate RCS backend on gopass clone

Fixes #750

Codecov Report

Merging #820 into master will decrease coverage by 0.03%.
The diff coverage is 20%.

@@            Coverage Diff             @@
##           master     #820      +/-   ##
==========================================
- Coverage   64.52%   64.49%   -0.03%
==========================================
  Files         170      170
  Lines        9552     9555       +3
==========================================
- Hits         6163     6162       -1
- Misses       2631     2633       +2
- Partials      758      760       +2

Impacted Files
Coverage Δ

pkg/action/clone.go
52.63% <20%> (-3.53%)
:arrow_down:

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 71f9ad6...3e9eabe. Read the comment docs.


Move everything from unix to linux

The code was written in the assumption that unix codebase will be common to both mac and linux, But it proved to be difficult than expected. Hence move all the files from unix directory to linux directory. Verify that it compiles by making appropriate changes in CMakeLists.txt

Hey can i contribute to this issue. I am a beginner and would love to understand this issue. Can u please explain what i should do? Thank YOU.

@hari-krishnan-88 this is a bit outdated issue, I've been meaning to close this as there were some architecture changes rendering this useless. If you prefer javascript you could work on UI part, Thanks!


Use graal-sdk instead of svm

Caused by https://github.com/quarkusio/quarkus/pull/34145

@gastaldi As far as I can see, this change should not be downstreamed to the 2.x versions, right?

Because org.graalvm.sdk:graal-sdk is already in (always has been) in the Quarkus application's BOM, I don't believe there is a need to have a separate branch.
It is a breaking change in the sense that the dependency is no longer available in the BOM, but it doesn't require changing any sources.

@gastaldi thanks for the clarification :slightly_smiling_face:

Final question: (when) will svm be removed? I.e. when do we need to release a new version?

Do we need a separate 3.0.x branch to support older versions?

you most likely will unless you don't use any jakarta/javax dependencies ?

@turing85 in 3.2.1 is the plan. next week :/

Do we need a separate 3.0.x branch to support older versions?

you most likely will unless you don't use any jakarta/javax dependencies ?

What does jakarta have to do with the svm dependency?
If you mean the switch from JavaEE to JakartaEE: we already migrated; that's what the 2.x branch is for.

@turing85

What does jakarta have to do with the svm dependency?
If you mean the switch from JavaEE to JakartaEE: we already migrated; that's what the 2.x branch is for.

sorry - I thought you mean Quarkus 2.0 vs 3.0 - if already branched you should be fine.

I think the question was misunderstood. The graal-sdk dep has been in the bom for ages (e.g 3.0.0) so as George said, it doesnt seem like you should need a branch for older 3.x versions.
I've made the switch and released quarkus-qpid-jms against Quarkus 3.2 again without issue.

@turing85 in 3.2.1 is the plan. next week :/

Is it? The PR isnt marked for backport and prior discussion suggested it would wait for 3.3

Should we move the discussion to the mailing list? I imagine there are other quarkiverse extensions that are affected as well.

Yeah, I should have done that before opening the PRs, sorry. I'll start a thread in the quarkus-dev list


attaching a list of CUI from UMLS in the december release that are not current in UMLS

Mondo term (ID and Label):
see attached
Xref that should be fixed (ID and label):
delete these.  I spot-checked, and believe that these are indeed no longer current
cui_not_current_for_mondo.txt
Your nano-attribution (ORCID)
If you don't have an ORCID, you can sign up for one here
Other comments:

Thanks @maglott, I'll take a look at this asap.

Thanks @maglott, I'll take a look at this asap.

Hello @maglott
I'm Sabrina, a new curator who recently joined the Mondo team.
We will address your issue as soon as possible. Thank you for your patience.
If this is a high priority, please let me know and we can prioritize it. Thank you!


Added PermissionError

https://board.aternos.org/thread/68975-share-access-erorr/
2022-07-01 03:40:55 DEBUG    https://aternos.org:443 "GET /panel/ajax/stop.php?TOKEN=XXX&SEC=XXXX HTTP/1.1" 402 None
2022-07-01 03:40:55 INFO       GET completed with 402 status

I forgot the import in init.py
Ignore this one and refer to #33


[21pt] Module for downloading bridge point cloud data

We received a bridges database for the state of Texas from Andy Carter. I put together a simple mockup in QGIS of the steps we'd need based on our understanding of that data, and after meeting with Andy about it, we got additional information and will receive some of Andy's already-processed point cloud DEMs for the bridge areas themselves, which we should be able to slot into this workflow relatively easily.


Document the set and getsub methods

For some reason the docs for them is missing from the readme?

.get is useful for getting
"foo" : {
  ...all of this...
}

.getsub is useful for getting
"foo:bar" : {
  "pads" : {
    ...all of this...
  }
}

``setSub`` sets the subkeys of keys IE

"foo:bar" : {
"pads" : {
...all of this...
}
}

# ``getSub``
``key`` is the key IE "foo:bar"
``subkey`` is an array of subkeys you want to ``get`` IE ``['pads','someothersubkey'];``
Example:
``const result = await db.getSub(key, subkey);``

# ``setSub``
``key`` is the key IE "foo:bar"
``subkey`` is an array of subkeys you want to ``set`` IE ``['pads','someothersubkey'];``
``value`` is a value to set IE "hello world"
Example:
``db.setSub(key, subkey, value);``


Not able to compare the research paper with the code

In the paper, section 3.1 BERT, it is said that -
we extract a fixed sized vector via max pooling of the second to last layer. then A sentence of N words will hence  esult in an N ∗ H embedding vector. The closer to the last layer, the more the semantic information carried by the weights (Zeiler et al., 2011); hence our choice of the second to last layer.
In section 3.1 Sentence-BERT -
We extract fixed size sentence embeddings using a mean over all the output vectors, similar to the method we used for BERT
But in the code -
def get_features_from_sentence(batch_sentences, layer=-2):
    """
    extracts the BERT semantic representation
    from a sentence, using an averaged value of
    the `layer`-th layer

    returns a 1-dimensional tensor of size 758
    """
    batch_features = []
    for sentence in batch_sentences:
        tokens = roberta_model.encode(sentence)
        all_layers = roberta_model.extract_features(tokens, return_all_hiddens=True)
        pooling = torch.nn.AvgPool2d((len(tokens), 1))
        sentence_features = pooling(all_layers[layer])
        batch_features.append(sentence_features[0])
    return batch_features

there is only AvgPooling of second last layer. There is not max-pooling from second-to-last layer.
Is it a bug in the code?

The maxpooling happens here : https://github.com/gdamaskinos/unsupervised_topic_segmentation/blob/cefa8ba65f964220435d35a0cb39722790f9c0b4/core.py#L75


Add cosine-distance meta example

Added cosine.sg and cosine.rst to create meta examples for distance-cosine and generated cookbook for distance-cosine.

@vigsterkr The cookbook preview does not show the right commit version for some reason. I noticed this before: the added cookbook is not part of the html renderer

@IOcodegeass can you squash the commits please

About the failing octave build, you read the error message. It might have told you that the build timed out, I restarted it :)

@karlnapf infra contains the code

About the d overloading, just remove the d for the distance. It is not used anywhere anyways. Just give the formula on the right hand side of the = sign

Changes made in cosine.rst and cosine.sg.

One more amend and ready to be merged

@karlnapf changes made. kindly review.

Cool I merged the data, so you can update the data version as well, see wiki for testing data howto

@karlnapf updated cosine.rst .

@karlnapf I am not sure about last commit. I have read the DEVELOPING.md and accordingly done
git commit data -m "Added testing data for cosine distance" git push origin feature/cosine_distance
But the explanation in DEVELOPING.md says to commit the updated version hash of the submodule which i couldn't understand.

It is exactly that. Now we wait for travis to execute the integration test for your example. Ping me if it passed.

@karlnapf CI is completed :)

Nice one. Well done on first merged cookbook page :)

Ah can you pls check to remove a potential cosine distance example from undocumented/python_modular folder

@karlnapf there exists euclidean distance example in  undocumented/python_modular folder although meta example for euclidean distance exists.
Should i remove that as well?

Yes! Thanks


Memoize?

I cannot find memoize in dictionaries, shouldn't it have been memorize?
https://github.com/astral-sh/ruff/blob/0b9af031fb8f51e7f9a72c31366bf5f87b90ca3c/crates/ruff_formatter/src/format_extensions.rs#L72
https://github.com/astral-sh/ruff/blob/0b9af031fb8f51e7f9a72c31366bf5f87b90ca3c/crates/ruff_formatter/src/prelude.rs#L5
https://github.com/astral-sh/ruff/blob/0b9af031fb8f51e7f9a72c31366bf5f87b90ca3c/crates/ruff_python_formatter/src/expression/binary_like.rs#L36

Interesting. I guess the problem why the term isn't in a general purpose dictionary is because it is a term specific to computer science. https://en.wiktionary.org/wiki/memoize

I wouldn't be surprised if many words "specific to computer science" were initially actual misspellings. I don't see a substantial difference between the definitions of memorize and memoize, one that would explain the new spelling. Besides, the usual word in computer science for "store (the result of a computation so that it can be subsequently retrieved without repeating the computation" is cache.
It is true memoize has been used more "widely" since 1980, but many orders of magnitude less than memorize. I wonder how to find the seminal misspelling around 1970-1980, just to check whether it seems intentional or not.

The wikipedia page for memoization suggests the spelling was intentional, and describes it as a specific type of caching


Add Carthage support

😄

I'm out of town until early next week, but will look it over then. I'm sure it's good. 🙂

@zhigang1992 Merging this in. 😄


Update the CHQ home page UI

🏆 Task Description: The homepage has a lot of text, update it to look more sleek
👨🚀 Skills Needed: HTML, CSS

Requirements

Update the UI design by making it less text heavy
Use a minimal and simple approach to display the information

@all-contributors please add @Abdulkarim-Suleiman for content


update documentation for version 0.1 (which will happen once default parameters are implemented)

I think I did this?


Fix example in JSON class.

I tried the first block of example code from https://docs.godotengine.org/en/stable/classes/class_json.html and got an error:

Identifier "json" not declared in the current scope.

I tried changing it to var error = JSON.parse(json_string) but then got this error:

Cannot call non-static function "parse()" on the class "JSON" directly. Make an instance instead.

So I think it needs this line added: var json = JSON.new()
Note: this was originally (and incorrectly) filed under the docs repo: https://github.com/godotengine/godot-docs/pull/7540

Yes, parse_string() is mentioned just below this code example on the page, so no need for that here as well.


Add missing Timeout variant for AcquireError

Fixes #issue
PR checklist:

[ ] make succeeds (on *nix)
[ ] make reftests succeeds
[x] tested examples with the following backends: dx12 vk
[ ] rustfmt run on changed code

I was thinking the same thing, but I'm sure there's some rationale behind it.


Support for firebase@ext?

Hi, is there any plan to add support to firebase@ext and its new API?
Thanks!

@FezVrasta assuming that you mean Firebase Extensions, then unless I'm missing anything, this is server side functionality so wouldn't be appropriate for this library?

No I'm referring to this:
https://modularfirebase.web.app/

Ah, I'd missed this @FezVrasta.
We can definitely add this support in the future, but it may be worth waiting until the API stabilises further. However, I am more than happy if anybody wishes to contribute a PR to add experimental support in the meantime?

About a month ago, Firebase 9 entered beta, so hopefully most of the API is stable now.

Hi, any updates on this?

Would love to use this library with Firebase 9. Any plans on merging the code from @jdpowell1?


LC0010: the cyclomatic complexity of CASE statements

I really like the LC0010 (check Cyclomatic Complexity/Maintainability Index) because it always reminds me to write simple and short functions.
But as soon as I have to make a distinction between enum values, I have to violate this rule.
Example: an enum has 10 possible values. Depending on the option, something different should happen.
The simplest/least complex way to program this is:
local procedure CheckOption(MyEnum: Enum "My Enum")
begin
case MyEnum of
MyEnum::Value1:
DoOption1();
MyEnum::Value2:
DoOption2();
MyEnum::Value3:
DoOption3();
...
MyEnum::Value10:
DoOption10();
end;
end;
but this function will raise a LC0010 anyway (cyclomatic complexity >= 8). But there is no posibility to do this less complex.
I would like to suggest that a case statement increases the cyclomatic complexity only by 1, no matter how many option values are queried. BTW: this is the only way to get an advantage from case statements compared to querying the options with 10 if-then statements.
If you think this change would contravene the definition of cyclomatic complexity too much, I would like to ask if my suggestion can be added as an optional setting, so that I can activate it via the extension settings.

I completely understand your request and also I've stumbled upon this to be honest. Applying a case statement with different enum values will indeed quite easily hit the cyclomatic complexity threshold of the LC0010 rule. I'm not on expert on the calculation of the cyclomatic complexity, where I'm unsure if changing the behavior of the rule is the right approach for resolving this.
Ideally we should replace a CASE statement with Enums and Interfaces to achieve extensibility and improve code maintainability.
Cognitive Complexity
In the future maybe we can add Cognitive Complexity to the LinterCop as an alternative: https://github.com/StefanMaron/BusinessCentral.LinterCop/discussions/285. An example of the differences between the both of them:

https://www.sonarsource.com/blog/cognitive-complexity-because-testability-understandability/


Implement per-channel prompts

Hmm, still running into extra commits coming along. Could you maybe refork it and use a different branch to do PRs later?

Right, I'll do that.


Downgrade @monaco-editor/react package version

PR includes

[x] Bug Fix

Related issues
Resolve #658

/canary


Space Shooter Extension Feature

Is your feature request related to a problem? Please describe.
The platform currently lacks engaging action-oriented games, limiting user entertainment options.
Describe the solution you'd like
Introduce a Space Shooter extension to the platform, providing users with an immersive gaming experience. Players can navigate a spaceship, shoot enemies, and collect power-ups across different levels.
Describe alternatives you've considered
While there are various game genres to explore, a Space Shooter aligns with the platform's goal of offering diverse and interactive content that appeals to a wide audience.
Additional context
Space Shooter games are popular for their adrenaline-pumping gameplay and visually appealing graphics. By integrating this extension, we can attract users seeking action-packed entertainment within the platform.
What problem is this feature trying to solve?
This feature aims to address the lack of action-oriented games on the platform, providing users with an engaging and thrilling gaming experience.
How do we know when the feature is complete?
The feature will be considered complete when users can seamlessly access and enjoy the Space Shooter extension, with smooth gameplay mechanics, visually stunning graphics, and challenging levels that encourage continued play and positive user feedback.

@Sulagna-Dutta-Roy please assign this to me i am GSSOC'24 contributor with 2+ years of experience in development


Fix docs markup

Codecov Report

Merging #381 (8e7f272) into main (ced1fc5) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #381   +/-   ##
=======================================
  Coverage   94.62%   94.62%
=======================================
  Files          74       74
  Lines        6432     6432
=======================================
  Hits         6086     6086
  Misses        266      266
  Partials       80       80

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


add new FEC, OpenSecrets, and MapLight IDs for 115th

Thanks, @mrumsky!

Glad to contribute. Thanks to the MapLight data team for their help.


Improve future composition

Hi,
I'm having a lot of issues handling the error type when composing futures.
Typically:
let three: Future<Int, NoError> = future(3)
let fut: Future<Int, NSError> = future { //long computation that can fail }
let composed =fut.flatMap { _ in three)

Produces an compile error. But it all works when both futures have the same Error Type.
I expected composed to be of type Future<Int, NSError> because one of the error type is a Void type, only the other one makes sense.
If both types conform to ErrorType then I would expect a generic ErrorType on which I can patten match or a composed error (like a tuple of optional errors).
Is there a way of achieving this behaviour? Is it intended? Am I doing something wrong?

You can use promoteError to change the error type of three from NoError to any other error type (in this case NSError).
Let me know if that does the trick for you!

It worked!
But it feels clunky. Why isn't this the default behaviour when composing futures with NoError?
before your answer I "fixed" my problems by converting my all my futures into Future<T?, NoError> so that they would play nice.
Now, using the promote error function, everything works fine and more elegantly

I guess variants of map, flatMap, etc. that know how to handle futures with NoError could be added. Not sure if it is worth the extra code. If you think so, you could try making a PR. Thanks!


Refactor interpolators and splines

This PR refactors Interpolator and PairSpline to give future flexibility in defining the spline potential. For example, it would now be possible to implement B splines in the pair potential rather than Akima splines. This was not previously possible.
One question is if we should rename "mode" to "style" or something like that. We could also separate them into a "mode" (which is value or diff) AND a "style" / "basis" (which is akima, bspline, etc.). That way we would not need to use the "-" that I currently chose. Ex:
mode="diff", style="akima"

vs.
mode="akima-diff"

@clpetix what do you think?

This PR refactors Interpolator and PairSpline to give future flexibility in defining the spline potential. For example, it would now be possible to implement B splines in the pair potential rather than Akima splines. This was not previously possible.
One question is if we should rename "mode" to "style" or something like that. We could also separate them into a "mode" (which is value or diff) AND a "style" / "basis" (which is akima, bspline, etc.). That way we would not need to use the "-" that I currently chose. Ex:
mode="diff", style="akima"

vs.
mode="akima-diff"

@clpetix what do you think?

I like the mode & style being separate arguments; that method seems more logical to me!

OK! Then what we will do for now is revert to mode for value vs. diff, and we will internally store the style="akima" in a variable. If we decide we want to support B splines, we can then come back and expose the style parameter publicly.

This should be ready now. I reverted the changes to mode so that it is just value or diff. I decided it didn't make sense to introduce the style variable now if we are not going to do anything with it, but I think this is a clean way to add the option later if we decide we want to support other types of splines.


Added multi-line output

Added option to make hex output on multiple lines instead of one

completed in f89b0b98526c6ebeb97cd3e1ab61308afbcce864


please help me

I am studying your code ,[https://github.com/bdochen/pydeobfuscate/blob/master/pydeobfuscate.py],and it can not run ,please help me ,thank you

Pydeobfuscate only works with codes that being obfuscated from http://pyobfuscate.tk.
The script was my old small project that has been removed from my profile due to the web has shut down since 2018.

Will you share the script again? I think this is better than any other tool ，thank you


Stable/0.3.x: Django 1.11 compatibility (render_to_response with RequestContext is deprecated)

Now one should use django.shortcuts.render() which automatically uses RequestContext and is backwards-compatible with Django 1.3+. I think this solution is better than the one in #644 which seems to be dropping the request data.

Closing since Swagger UI rendering was reworked while ago and PR is not relevant any more.


VSCode truncate type

Please add an option to show full not truncated type. This is unreadable.

Ha, I finally found it!
noErrorTruncation must be set to true
https://www.typescriptlang.org/docs/handbook/compiler-options.html


Pytest doesn't exit properly when stopping test sessions

Environment data

VS Code version: 1.37.1
Extension version: 2019.8.30787
OS and version: Windows 10 Pro (64 bit)
Python version: 3.7.3
Type of virtual environment used: N/A
Relevant/affected Python packages and their versions: N/A

Expected behaviour
Pytest exit and fire all closing/exit/teardown code when stopping a test session (also in debug mode).
Actual behaviour
Pytest exit and fire without calling closing/exit/teardown code when stopping a test session (also in debug mode).
Steps to reproduce:

Create a python project that utilizes pytest for testing,
Create a pytest fixture that utilizes __enter__ and __exit__ constructors ("with" statement). For example: open(file).
Create a test that utilizes that fixture.
Start the test.
Stop the test session before the fixture closes.

@dillonm197, thanks for letting us know about this.  I was able to reproduce the problem.  We'll look into it.
I tried with the following code in "test_spam.py" under my workspace folder:
import time

import pytest

@pytest.fixture
def fix_1():
    print()
    print('entering 1')
    yield True
    print('exiting 1')

def test_1(fix_1):
    print('testing 1')
    time.sleep(1)
    assert fix_1

@pytest.fixture(scope='module')
def fix_2():
    print()
    print('entering 2')
    yield True
    print('exiting 2')

def test_2(fix_2):
    print('testing 2')
    time.sleep(1)
    assert fix_2

@pytest.yield_fixture
def fix_3():
    print()
    print('entering 3')
    yield True
    print('exiting 3')

def test_3(fix_3):
    print('testing 3')
    time.sleep(1)
    assert fix_3

The tests pass just fine and if I run python3 -m pytest -s . I get the following results:
collected 3 items

test_spam.py
entering 1
testing 1
.exiting 1

entering 2
testing 2
.
entering 3
testing 3
.exiting 3
exiting 2

If I hit CTRL-C while the tests are running, cleanup happens as expected:
collected 3 items

test_spam.py
entering 1
testing 1
^Cexiting 1

!!!!!!!!!!!!!!!!!!! KeyboardInterrupt !!!!!!!!!!!!!!!!!!!

collected 3 items

test_spam.py
entering 1
testing 1
.exiting 1

entering 2
testing 2
^Cexiting 2

!!!!!!!!!!!!!!!!!!! KeyboardInterrupt !!!!!!!!!!!!!!!!!!!

collected 3 items

test_spam.py
entering 1
testing 1
.exiting 1

entering 2
testing 2
.
entering 3
testing 3
^Cexiting 3
exiting 2

!!!!!!!!!!!!!!!!!!! KeyboardInterrupt !!!!!!!!!!!!!!!!!!!

At this point I ran the tests by using the test explorer, and writing to a file instead of printing.  I did not get my "existing" messages when I hit the "Stop" button during execution.  For instance, here is the output when I stopped while test 3 was running:
entering 1
testing 1
exiting 1
entering 2
testing 2
entering 3
testing 3

FWIW, I believe this is not new behavior in the extension.

I can verify this is still an issue. In my case using the sftpserver fixture.

Still an issue

Hello! We have just finished our testing rewrite and are beginning the roll out to users. If you are able, it would be very helpful to know if your issue still exists on the rewrite! To try it yourself, you need to be on the most recent release of the Python extension and add this setting to your users settings.json "python.experiments.optInto": ["pythonTestAdapter"].
You can confirm you have the rewrite enabled by setting  "python.analysis.logLevel": "Trace", in your user settings then check for Experiment 'pythonTestAdapter' is active in your python logs.
Let me know if the rewrite fixes your issue. Thanks!


branch add-rabbit-tracing: how to transfer trace context by rabbitMQ

hello~ i use rabbitMQ in my code. And i want to use 'brave' to trace program.
i want to know how to transfer trace conttext by rabbitMQ.
is it  headers?
But transferring trace context by rabbitMQ‘s headers destructive rabbitMQ‘s Headers Exchange characteristic

can you ask again here please? https://gitter.im/openzipkin/zipkin

Closing as discussion moved to gitter.


migrate eodatasets 1.9 from versioneer to setuptools-scm for Py3.12 compatibility

I was able to upgrade versioneer to be 3.12 compatible, but happy to migrate to setuptools-scm in the future if that's preferable.


Add hover and select states for Cards

To support the master-detail pattern we want to all for the possibility of a card grid to be used as part of the master panel. This will require the possibility for cards to have a select and hover state as was implemented for the DataList.
See designs here: https://docs.google.com/document/d/1kzGP37tb-lf7sVz43xBnnoYEWPsQN4GvNvffebxiuTE/edit?usp=sharing
cc @mcoker @rachael-phillips @LHinson

@mcarrano we already have a hoverable state for cards - is the expectation we will re-use that, and add just a selected state?

Yes, that makes sense @mcoker

@mcoker the selected state will keep the hover drop shadow, but also will have a 3px primary blue border along the top.
Side note, it looks like the small drop shadow that appears behind cards (non hovered/unselected state) was replaced with a gray outline around the card here. Is this a bug?

@lboehling yep, thanks for noting that! It's just an issue with the website, not patternfly, and opened an issue here - https://github.com/patternfly/gatsby-theme-patternfly-org/issues/132

I know there have also been requests for PF to support tiles (with hover and selected states). I made a design proposal for tiles in this doc https://marvelapp.com/50eh328/screen/64407411 (C., or last listing on the second page).
@mcoker would tiles be a variant of cards or a new component? The specs I made are using the same padding as compact cards, but have borders with rounded edges in lieu of a drop shadow, and different hover/select treatments.
@mcarrano

@lboehling what's the difference between a tile and a card? And what all goes into a tile? At first glance, they look like different components.

@mcoker I believe tiles act more like form elements. They can include more grouped info than just radio/check boxes (i.e. icons, longer titles/descriptions) and can be placed within a card/in a gridded layout. Typically these will be pretty plain and compact.
@katierik opened an issue with a few more use cases for tiles here https://github.com/patternfly/patternfly-next/issues/2310
Visually, there would need to be different styling btwn cards and tiles, since tiles can be placed within a card/wizard/modal/components with white backgrounds. This would also eliminate unnecessary stacking of cards with box shadows.

@lboehling thanks, tiles should definitely be a new component.

@lboehling nice!

@mcoker @lboehling I'm a little bit hesitant to see us create a new component for this since I don't really see anything functionally different between a Card and a Tile and it will be easy to confuse them. Just looks like a different visual treatment of the card. Is the issue that we need a card that can be placed on a while vs gray background? Maybe this is just a new variant of Card.

@mcarrano visually I think there are enough stylistic differences that I think it's a valid approach to separate them. If they're the same component, there will be a lot of style overrides of the existing component for the tile variation. Also functionally it looks like tiles have a very specific use and cards do not, so I'm not sure it makes sense to have them tied together as the same component. Meaning if we make changes or add enhancements to either the card or tile, would we likely want those changes to also apply to the other?
That said, you know better than I how you see envision the structure and their intended use, so I'm fine with this being a variation, too, if you think they're similar enough.

All fair points @mcoker . There is a separate issue opened for tiles that @lboehling referenced above, so let's keep this work focused on Cards and we can take up the Tiles question at another time. @LHinson @rachael-phillips are you aware of the request for a "Tiles" component? See #2310

:tada: This issue has been resolved in version 2.45.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Steam Bot Error

Hi,
So I have been trying really hard to get my website running. Today I encountered the following error
https://gyazo.com/3e2f603863d23aecbf6a71490cea93c6
My Log: http://pastebin.com/NG6M1Rt2
My settings: http://pastebin.com/ApFmS83W (I have the correct API I just wrote it out for security reasons)
I don't know what I am doing wrong. Please Help :D
If you want to contact me here is the bot acount I am using http://steamcommunity.com/profiles/76561198216547607/

This should go in https://github.com/ztizzlegaming/CSGOWinBig-SteamBot

@ICallHax Did you solve the issue?

@keinervonus Sorry, I forgot about this thread. Closed. I fixed it by reinstalling the site.


add easter egg songs on launcher

Done! https://github.com/Invasor-de-Fronteiras/Erupe/commit/9b753697a14ddf2679982ec1dfb92d88132a5ef2


[New Format]: NeuroNexus Radiens Allego file format (.xdat and .json)

What format would you like to see added to NeuroConv?
Acquisition using NeuroNexus Smartbox Pro and NeuroNexus Radiens Allego software. The software produces 3 files: a data file (.xdat), a timestamp file (.xdat), and a text file with metadata (.json).
Does the format have any documentation?
From the Radiens website: https://nnx.mcoutput.com/1376106/Content/Home-Radiens.htm
Radiens saves primary time-series data sets (e.g., neural recordings) in a simple, open format.  Each dataset (i.e. recording) is saved in a file set named ‘XDAT’ that consists of three files: (i) flat binary file containing the matrix of all sample values (typical in uV) across the multiple channels, (ii) flat binary file containing all timestamps, (iii) json text file containing enriched metadata.
Existing APIs for format
No. Of note, the Radiens website claims that .xdat files can be read by MatLab and Python, but I have been unsuccessful at reading .xdat files into open source spike sorting programs run through MatLab.
Do you have any example files you are willing to share?
Your system won't let me attach the .xdat files -- is there another way to send them to you?
allego_6__uid1211-12-22-59.xdat.json
Do you have any interest in helping implement the feature?
No.
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] Have you ensured this bug was not already reported?

Hi @dlewis326, thanks for the request!
cc: @alejoe91 @samuelgarcia
I think this is the first formal request for it here on NeuroConv, but it's been in discussion for a while on the upstream projects (SpikeInterface and Neo)
SpikeInterface: https://github.com/SpikeInterface/spikeinterface/discussions/1719
Neo: https://github.com/NeuralEnsemble/python-neo/issues/1296
In both cases it looks like what we need most is some example data - thanks for being willing to share some!
It also looks like aside from that the problem might be that the reader through their API is not completely open (need a license with them to initialize the client) which makes it really difficult or impossible for projects like ours to integrate this.
As a customer, you could request that they make such readers completely open. Other than that, we can try our best to figure it out once we see some example data but no guarantees that it will work.

Your system won't let me attach the .xdat files -- is there another way to send them to you?

The most common way is through Google Drive or Dropbox (or w/e similar platform you and your institution prefer); GitHub has pretty strict size and file type limits

@CodyCBakerPhD Unfortunately the xdat file requires a license fron NeuroNexus...https://github.com/SpikeInterface/spikeinterface/discussions/1719#discussioncomment-6183762

No example recordings yet (just setting it up) but it looks like *_data.xdat is float32 (with last 6 chans reserved for aux or digital IO) and *_timestamp.xdat is int64, plus there's a .json metadata file. Their matlab getAsKilosort2Matrix() just casts to int16 with the OpenEphys 0.195 uV/bit, +/- 6.38976mV range. I don't see the requirement for a license. Code is from: https://www.neuronexus.com/radiens-allego-download-page/
allego_file_reader.py.txt
allegoXDatFileReaderR2019b.m.txt

I've started a reader for this format on Neo. I'm just waiting for permission to add the files shared with me to our gin testing suite for final compliance testing, but feel free to test the IO if you want while I wait for final testing.


Add help screen for the map portlet

We also have a help screen added to our version of this portlet. We'll commit this as well.

That is great Aaron.  Thanks for all the great contributions!!

Awesome @asgrant!
Looking forward to seeing a PR for this!

:bell: any update on this?

We no longer use this portlet, although I can ask one of our student developers to look at adding this feature in.


Problem to connect to OPC UA server: could not Send Open Secure Channel

Hello,
I am struggling with a problem of connection in some machines.
I have a tool to check that the connection to a defined URI works as expected. Here is an example:
opc.tcp://MachineName4862/#Basic256-SignAndEncrypt
According to this URI, the correct endpoint is selected to open a connection to the OPC UA server.
Certificates are stored using the certificate Windows store (X509). Client certificate is generated automatically by the SDK.
It works fine when the tool is started as Administrator in all machines. In some of them, it also works with a standard user (not admin).
But in some machines, with a user which is not administrator, the following errors appear in the logs of OPC UA stack:
2/25/2019 18:00:39.027 EXCEPTION BadTcpInternalError 'Could not send an Open Secure Channel request.'
2/25/2019 18:00:39.027 EXCEPTION BadTcpInternalError 'Error establishing a connection: Could not send an Open Secure Channel request.'
Using SysInternals tools, the following errors appear:
CreateFile - C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys\82da4e98951a81ca813f8b0c84b6a4fc_f165a72f-47b4-49a5-b200-f352463ae0eb - ACCESS DENIED
RegQueryValue - HKLM\SOFTWARE\Microsoft\Cryptography\MachineGuid - BUFFER OVERFLOW
When the connection is successfully done from another machines, the errors are not present and there is no access to the folder C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys...
The workaround is to delete the certificate in the Windows certificate store, start the tool in admin to let him create a new certificate, then start the tool in a normal way (not admin) with the same user.
Why does the SDK try to create a file in this folder ? What is the condition to create a file in this folder ?
Do you have an idea to solve this issue ?
Thanks for your help

Open in wrong project


How to skip to next track

Hi,
I have spotify installer on my LG and can turn it on and play with your SDK. However when carlingue tue command fastForward it jumps of 10s forward but I don't find how to go to the next track. Is there a command for that?
Thanks!

Same here... Any news about this?


add update validation logic to HostedCluster webhook

What this PR does / why we need it:
Continuation of https://github.com/openshift/hypershift/pull/1241, this PR adds the actual validation logic and moves the webhook out of the api package to avoid untangling of deps from a future separate api module.
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #
Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

@sjenning this is good, though I think we could do better with the cluster id, like only allow a change if the previous value is blank, but we can do that later.
/lgtm


Updating app to Django 1.8

Just doing the stuff that's needed to make this compatible with Django 1.8. Databrowse has been removed.

@damonkelley, @ldko, this is ready for review.

:+1:


Any way to use wildcard in config file?

I want to use something like this in my configs. Can I somehow do it?
[/backups/*/]
hourly = 24
daily = 7
weekly = 4
monthly = 12

Hi and thanks for the feedback. This is possible as of version 5.2 that was just released.


Includes user full name in auth user response

Fixes #3335
Includes the full name of the viewing user in the response from the backend, so that it's rendered in the dropdown instead of the username.
Also my first PR in Ruby!

@Kartones @javisantana

Frontend tests were OK :+1: (details)

user.name is an optional field, I'd use a ternary if to check for existance and if not leave user.username

Yep, changed that to use the function in the user object.

Frontend tests were OK :+1: (details)

sadly, Ruby standard says no parenthesis are to be put if the method has no parameters, so to keep following it please remove them :grin:
Other than that, :+1:

Done! Merging ASATP

Frontend tests were OK :+1: (details)


Implement oracle connector

What changes are being made and why?

Implemented Debezium Oracle plugin (will close #61)

How the changes have been QAed?
tasks:
  - id: capture
    type: io.kestra.plugin.debezium.oracle.Capture
    hostname: <IP_ADDRESS>
    port: 1521
    username: c##dbzuser
    password: dbz
    sid: XE
    maxRecords: 5
   includedTables: KESTRA.EVENTS

triggers:
  - id: trigger
    type: io.kestra.plugin.debezium.oracle.Trigger
    snapshotMode: INITIAL_ONLY
    hostname: <IP_ADDRESS>
    port: 1521
    username: c##dbzuser
    password: dbz
    sid: XE
    maxRecords: 100

  - id: realtime
    type: io.kestra.plugin.debezium.oracle.RealtimeTrigger
    hostname: <IP_ADDRESS>
    port: 1521
    username: c##dbzuser
    password: dbz
    sid: XE

Setup Instructions

Start oracle service in docker-compose-ci
Create table using kestra user, and fill with data

@iNikitaGricenko both Trigger and RealtimeTrigger tests are failing, can you have a look so I can merge it?

@iNikitaGricenko maybe it's because of the state that is used transparently, you can test that assumption by configuring a different stateName for each test.


Rewording some error message and fix some tiny issue for shrink page

Signed-off-by: Binlong Gao<EMAIL_ADDRESS>Description
The main changes are:

Rewording some error message.
Change the style of the input form in order to make the page consistent with other pages.

Issues Resolved
#468
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #482 (f273daa) into index-operation (5703a9d) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@                 Coverage Diff                 @@
##           index-operation     #482      +/-   ##
===================================================
- Coverage            60.82%   60.80%   -0.03%
===================================================
  Files                  250      250
  Lines                 8353     8356       +3
  Branches              1475     1478       +3
===================================================
  Hits                  5081     5081
  Misses                2918     2918
- Partials               354      357       +3

Impacted Files
Coverage Δ

.../ShrinkIndex/container/ShrinkIndex/ShrinkIndex.tsx
86.50% <0.00%> (-1.63%)
:arrow_down:

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


Issue with relative links

Description
Relative links work only on second click, if the location.hash is set.
To reproduce

Open a demo: http://output.jsbin.com/jafikuquwe#test/11.
Click on "Google.com" link (first click, sends you straight to the www.google.com)
Go back to the demo.
Click on "Test.html" (first click does no visual effect, location.hash changes)
Click on "Test.html" again. (now you're sent to the test.html page)

Edit link: http://jsbin.com/jafikuquwe/edit?html,js,output

@cognitom could you please check this issue?

@pavel thank you for your reporting. It will be fixed on next release 😄

@cognitom You're welcome. Keep up the good work!


clusterpool: allow setting lifetime for claims

claimLifetime allows admins to set the lifetime for all cluster claims created for
a cluster pool. Two new lifetime configurations are available, default and maximum
clusterpool.spec.cliamLifetime.default
This sets the default lifetime for the claim when one is not set by the claim itself.
clusterpool.spec.claimLifetime.maximum
This sets the maximum lifetime for all claims in the cluster pool. If any user sets lifetime
on the claim, the actual lifetime will be minimum of the maximum allowed by the pool and what was
set on the claim.
This allows the admins makes sure that the tightest lifetime constraint is always respected for the
cluster pool.
Also a new status field is added to the clusterclaim .status.lifetime that provides information of
the exact lifetime including all the pool configurations and the claim spec.
NOTE: the cluster pool controller could also set the lifetime on the claim when it assigns a cluster
to the claim but that would would require setting the intention on the object as part of the UPDATE hence
making it difficult to

later figure out if the lifetime was set by user or pool which is important if the claim ever had to
move to a different pool.
also the user could change the claim lifetime to somthing else after the controller updated it and the controller
would have to fiure out if the change should be kept and then revert the change, possibly race with the user.
This current approach with clusterclaim controller computing lifetime allows users to express their intentions at
both levels in a much more clear way and it can be enforced similarly.

/assign @dgoodwin
/cc @abutcher
xref: https://issues.redhat.com/browse/HIVE-1283

@dgoodwin updated the lifetime to support both the default and maximum explicitly. PTAL

@dgoodwin updated the lifetime to support both the default and maximum explicitly. PTAL

/lgtm

/lgtm


Binary Search Tree Implementation In Java

Can you please assign me this issue?

Yeah go for it.👍

I want to contribute. Please assign it @tanus786  as my first contribution for hacktoberfest 2022.


[DNM] flagging mechanism for fallback translations

PR for conversational purposes -
Our team needed a way to indicate when translations resort to fallback strings (specifically for us - there is always a lag in sending/receiving translations, even though we are constantly deploying in between these events. QA has been reporting translation related bugs that will actually resolve themselves once the next round of translations are returned, so we needed a way to indicate that the strings, while missing in locales currently, will no longer be an issues in the near future).
Could potentially be turned into something more general for other teams to find useful.
Photo example of the pattern.

@MarkhamShofner doesn't this approach fail when you have a baseLocale set in your config?

@Turbo87 it would.
I also don't feel this would be terribly useful in all cases.  Sometimes it's perfectly fine to fallback w/o any need for indication.

@jasonmit - agree that fallback indicator isn't always (or even frequently) needed. In this case, it's pretty specific to what our team needed - but it seems like other people could want to flip similar functionality.
Also - thanks for ember-intl!


Add test to ensure CRL can be signed by intermediate CA cert

Type of change

Test update

Description

Added a test to ensure a CRL can be created and signed by an intermediate CA cert.
Removed dead code from msp.go

Related issues
FAB-17694

/ci-run

/ci-run

/ci-run


[Docs]: better URL structure

What type of suggestions?
Missing Information
What page is concerned?
No response
What is the issue?
Change the URL structure for the documentation to make it friendlier:

remove HTML file extension
remove one level of folders so https://docs.kubefirst.io/kubefirst/overview.html can be https://docs.kubefirst.io/overview.html to remove unuseful redundancy (maybe it's just a URL rewrite and not a docs structure change)

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Will be fixed with #992


What needs to be included on classpath for install?

Hey There,
I was trying to load the plugin into our sandbox xld and got an error:
java.lang.IllegalArgumentException: Unknown enum-class supplied for property sku of kind ENUM: com.microsoft.azure.management.websites.models.SkuOptions
I assume I need to add some stuff to the lib directory.   Can you let me know what I need to add to load and use the plugin?
Thanks!
Bernie

Hey Bernie,
Can you try the alpha2 release? It is in xldp format, so should have all the dependencies.
Regards,
Joris

Dank je Joris!

You speak Dutch?

Nope, just used google :)

Hey Joris or Ravan,
Quick question, when I am creating a new type webapp is the artifact a zip file of the whole webApplication folder?  Kind of fuzzy on the workflow here.
Thanks for any info,
Bernie

Hi Bernie,
It is a zip containing your app binaries. So for iis it will be the HTML and asp files. If you deploy a java app the zip contains the war.
Cheers,
Ravan
Sent from my iPhone
On 26 Apr 2017, at 18:10, bbonn <notifications<EMAIL_ADDRESS>wrote:
Hey Joris or Ravan,
Quick question, when I am creating a new type webapp is the artifact a zip file of the whole webApplication folder? Kind of fuzzy on the workflow here.
Thanks for any info,
Bernie
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/xebialabs-community/xld-azure-app-services-plugin/issues/1#issuecomment-297461513, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAjjvwbf2hhfDcPBEw7M5SCnI5w8EPT3ks5rz2xWgaJpZM4NHqWf.

Closing because of inactivity


Request to improve consistency of direct media links

The problem
The readme says adding /photo/{index} after the post ID allows getting the other medias in the post.
For example, this post https://twitter.com/qiandaiyiyu/status/1753349204380938507 has 3 images, and the following can get all 3 of them:

https://d.fxtwitter.com/qiandaiyiyu/status/1753349204380938507/photo/1
https://d.fxtwitter.com/qiandaiyiyu/status/1753349204380938507/photo/2
https://d.fxtwitter.com/qiandaiyiyu/status/1753349204380938507/photo/3

However, if I request to https://d.fxtwitter.com/qiandaiyiyu/status/1753349204380938507/photo/4, fxtwitter will return the first image for some reason, then https://d.fxtwitter.com/qiandaiyiyu/status/1753349204380938507/photo/5 leads to https://github.com/FixTweet/FxTwitter.
My project uses fxtwitter to extract media (URL)s directly from the post and send them in a Discord channel, but with the current behavior, I can only send the first image URL because I don't have a consistent way of knowing how many medias this post has.
My suggestion
Without considering how fxtwitter works internally (I haven't read the code yet), I have 2 suggestions to resolve this issue:

Return 404 when requesting an invalid media index: With the example above, /photo/4 and beyond should return a 404. This way I can iterate through the indexes from 1 and continue until a 404.
Create a GET API that returns information about a post given the post ID: Maybe something like this:

{
  "id": 12345,
  "content": "something this post says about",
  "medias": [
    "https://pbs.twimg.com/media/GFUk9BRXoAA2zi0",
    "..."
  ]
}

About the 2nd point, we actually have an API for FxTwitter (see api.fxtwitter.com). Not sure if that's helpful in your case. It would probably be a good idea to improve direct media's behavior here cause right now it's handled the same as embeds but it would be probably more useful to actually only return the media if it was found

Nice, the API works for me. It's up to you if you want to fix the direct media links.


Fix generation OS X app when not providing icon and error handling

https://github.com/paulmillr/loggy/pull/23
Decided to fix here. Also, fixed issue with generating an icon in OS X Application for showing notifications. Discovered running node test.js :)

Hey @VitaliyR, thanks for the PR. Could you please suppress errors in index.html?

@shvaikalesh Hi! What does that mean? index.js is returning a function, but not a stream. Are you proposing to add parameters for OS handlers? Or Proxy?

9c860da

e7887fc

Got it, thanks.


Menu icon behavior

Hi.
As for me, playing states at menu icon are inverted:

playing (expected icon is pause "||" )
paused (expected icon is play "|>")

It is always a difficult question whether to show the icon of the current state or the icon of the command that will be executed.
I decided to show command icon . Because:

It matches the icon on the main window. Last coincides with icons in other programmes, e.g. iTunes
It matches the icon in the Plaing Now panel.

I have different states (music is playing) :

This is currently working for me in version Version 6.1.0

@fulldecent

This is currently working for me in version Version 6.1.0

Please clarify what you mean.

The play button enables/disables playback.
You like the icons.
You agree with st1ng7ay and think icons should be changed.

@st1ng7ay

I have different states (music is playing) :

In my opinion the meaning of these icons is different, one is a button, the other is an indicator.
I realize that if icons are placed next to each other it looks strange, but unfortunately there is no perfect solution.
Most of the time people only see the tray icon. And if a pause is drawn on it when playback starts, it will be more confusing.
So for now, the icons will remain as they are.


blackbox-files.txt contains full paths for files

I register a new file and see in the blackbox-files.txt its full path:
for example,

c/users/"user"/documents/github/notes/test.md

If I then add a new admin, re-encrypt files, commit and push and new admin will pull and try to decrypt, he will get an error of not being able to find a file by my old path, wich includes my username.
I can be doing something wrong...

The filenames listed in blackbox-files.txt should not include the base path.  That is, they should be relative to the repo base directory.  Delete c/users/"user"/documents/github/ from the line inblackbox-files.txt and it should work.
I'm not sure how that full path got in there, though I suspect that blackbox_register_new_file doesn't work properly under Windows. That's never been tested.

Yeah, I've tried that (thought it was strange to put the base path in potentially VCS and removed part of the base path in blackbox-files.txt) but it didn't work. I've tried different combinations (including ../) with no luck.

I have the same issue with registering files on MacOs.
Also, when I try to decrypt a file (with blackbox_edit_start) that has been added before and are in blackbox-files.txt file I get an error that file is not found. However blackbox_decrypt_all_files works with old files.

Same issue. Blackbox referencing root of machine rather than root of repo.

I believe this is fixed.  Please try the latest "master".

Hi; I'm experiencing the same issue with the latest version in master.


New line searches

[ ] Hager--Zhang
[ ] Moré--Thunte
c.f. also zoom.

Hey there. I gave implementing the zoom line search algorithm a try, as I find it to be a generally well-working method. At least for some of the problems I have tackled in the past.
The main obstacle (apart from getting used to the JAX control flow for nested if-expressions) is how to retrieve the descent information needed to evaluate the decrease and curvature conditions as well as interpolate the step sizes. In the current implementation of the search and descent interfaces there seems to be no general way to retrieve the descent direction after the descent step is made. Also, the descent methods currently have no common naming scheme regarding the descent direction, if it's even calculated explicitly (I get that this may not alway be necessary), which further complicates things. My understanding is that one would have to divide the current step by the step size to (re-)evaluate the descent direction, which may generally be a bad idea for a value that is supposed to decrease with further convergence. Or am I missing something obvious?
If not, my proposal would be to modify the interface of the descent methods in a way that allows to retrieve the current descent direction in a unified way. Also, I think the abstract line search step method should have an additional argument for the descent direction or even the descent state, as this is most likely required by complex line search methods in one way or another.
On a side note, I'm also working on implementing the L-BFGS algorithm (kind of finished, at least from a methodological point of view), which also relies on common interfaces for descents.
Looking forward to further discuss this topic!

Hello! Thanks for the interest in implementing some new line searches.
Just to be clear, for a minimisation problem of a function $f\colon \mathbb{R}^n \to \mathbb{R}$, an Optimistix descent $\delta\colon \mathbb{R}_+ \to \mathbb{R}^n$ is a curve in $\mathbb{R}^n$ parameterised by the step-size. Line searches handle the inner optimisation loop of choosing $\alpha$ such that $f(y_k + \delta(\alpha))$ is approximately minimised with respect to $\alpha$. We only do the classical line-search algorithm $f(y_k + \alpha p_k)$ for a fixed descent direction $p_k \in \mathbb{R}^n$ when using certain descents, such as NewtonDescent and SteepestDescent. We don't have a common name/interface for the descent direction $p_k$ because most the descents don't compute a quantity like $p_k$ at all, so it's intentionally not supported. It also shouldn't be needed for the Wolfe conditions (or related conditions.)
$\delta(\alpha)$ is computed with the step method on any descent (see the abstract base class here.) The way this gets passed to the line search is via the y_eval argument in the line search step method. y_eval is the proposed next step for a given step-size $\alpha_k$. For a step-size $\alpha_k$ the actual diff $\delta(\alpha_k)$ can then be computed by subtracting y_eval from y, see the BacktrackingArmijo line search for an example.
As for technical details of implementing the Wolfe conditions, there should be no issues here. The classic Wolfe conditions for current iterate $y_k \in \mathbb{R}^n$, proposed step-size $\alpha_k \in \mathbb{R}$ and descent direction $p_k \in \mathbb{R}^n$ are the sufficient decrease condition
$$f(y_k + \alpha_k p_k) < f(y_k) + c_1 \alpha_k p^T \nabla f(y_k)$$
and the curvature condition
$$\nabla f(y_k + \alpha_k p_k)^T p_k \geq c_2 \nabla f(y_k)^T p_k$$
for some constants $c_1, c_2$. We can replace the traditional line-search step $\alpha_k p_k$ with the generalised descent $\delta(\alpha_k)$
$$f(y_k + \delta(\alpha_k)) < f(y_k) + c_1 \delta(\alpha_k)^T \nabla f(y_k)$$
and the curvature condition
$$\nabla f(y_k + \delta(\alpha_k))^T \delta(\alpha_k) \geq c_2 \nabla f(y_k)^T \delta(\alpha_k)$$
without changing the meaning of either of the conditions. When $\delta(\alpha) = \alpha p_k$ these are equivalent to the classical Wolfe conditions. Different relaxations of the Wolfe conditions should be generalisable in roughly the same way.
Does this clear things up?

Thank you for taking the time to write down the general line search problem and current implementation in such detail. This actually helps a lot to clarify the problem I'm currently facing.
First, you are totally right about the Wolfe conditions. I understood that the descent information is computed by substracting y from the current evaluate y_eval, which gives

$\delta(\alpha_k) = \alpha_k p_k $

Evaluating the sufficient decrease condition with $\delta(\alpha_k)$ is straight forward, but I did not notice that multiplying the gradient with $p_k$ or $\delta(\alpha_k)$ on both sides of the curvature condition is equivalent.
The problem still persisting is the computation of new trial step sizes $\alpha_{k+1}$ in the zoom phase  of the line search algorithm suggested in Nocedal, Wright (2006) - Numerical Optimization, 2nd ed. (algorithm 3.6 and 3.5, respectively).
They propose computing new trial step sizes $\alpha_{k+1}$ by minimizing the cubic function interpolating $\phi(\alpha_{k-1})$. $\phi'(\alpha_{k-1})$, $\phi(\alpha_k)$ and $\phi'(\alpha_k)$. The new step size can then be computed by:

$\alpha_{k+1} = \alpha_k - (\alpha_k - \alpha_{k-1}) \left[ \frac{\phi'(\alpha_k) + d_2 - d_1}{\phi'(\alpha_k) - \phi'(\alpha_{k - 1}) + 2 d_2} \right]$
with

$d_1 = \phi'(\alpha_{k-1}) + \phi'(\alpha_k) - 3 \frac{\phi(\alpha_{k-1}) - \phi(\alpha_k)}{\alpha_{k-1} - \alpha_k}$

$d_2 = \left[ d_1^2 - \phi'(\alpha_{k-1}) \phi'(\alpha_k) \right]^{1/2}$
This requires explicit computation of the derivative

$\phi'(\alpha) = \nabla f(y_k + \alpha p_k)^T p_k$
of

$\phi(\alpha) = f(y_k + \alpha p_k) = f(y_k + \delta(\alpha))$
which requires computation of the descent direction $p_k$. At least I could not come up with a way to evaluate the minimizer without doing so.
Please let me know if you have any suggestions. Maybe I'm once again misleaded by the usual notation.

Yep, this looks like it may require a more significant rewrite. As you pointed out, the issue is how to get $\delta'(\alpha)$ without access to $\delta$.
The most obvious solution to this may be to pass the descent step method and the descent state to each line search, either through some very simple custom type or capture the state via closure and pass just the scalar function lambda alpha: descent.step(alpha, descent_state). This is a breaking change since it alters the base class AbstractSearch, but these kinds of line searches should be well-supported in Optimistix and I don't see a non-breaking way to support them. @patrick-kidger do you have any strong thoughts on this? If not I can draft either of these methods in a PR.
@HeSchatz I've already left you in the dark on this for way too long, my apologies. While determining how much of a rewrite this will need, a clunky option which at least gets the autodiff issue out of your way would be to use finite difference. You should be able to compute and store $\delta(\alpha + h)$ and $\delta(\alpha - h)$ using step-rejection and the search state and use the central finite difference approximation. Although this may be a case where it actually makes more sense to just use forward finite difference instead of central finite difference to avoid the extra function call at the cost of some accuracy.

I think I'm happy with a breaking change. We're still early in this project's lifecycle, and this is already an advanced API.


crds: auto-generate preserveUnknownFields field

Longhorn 4600
Signed-off-by: Derek Su<EMAIL_ADDRESS>

@derekbit Please help backport to 1.3. Thanks.


NIFI-377: Add EncodeContent processor

Rebased against develop and force-pushed, with changes from review.

Adam,
I merged this one into develop. It's slated to go out in 0.0.2, which we should be voting on very soon!
Thanks for the work that you've put into this. It urged me to create https://issues.apache.org/jira/browse/NIFI-391 to take care of the old processor :)
Hopefully we'll have both of your contributions in the 0.0.2 baseline - just pending a review of the license for the digital corpora stuff. If that doesn't work, we can just remove those test files and associated unit tests for those particular data types or create our own test files.
Thanks again!
-Mark


fix: make sampling more reproducible

Without setting the random_state in the GroupedDataFrame.sample, we will never be able to reproduce results. Other sampling logic through the file correctly sets the random_state/seed, but this one is missing.

Hello!
Well spotted! Thanks for this :)

Tom Aarsen

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Update cri to f1d492b0cdd14e76476ee4dd024696ce3634e501.

Containerd 1.3 is validated against v1.15, but it is also compatible with Kubernetes v1.12+. (See more details about support metrics)
Features

Supported per-pod containerd shim. The io.containerd.runc.v2 runtime is fully validated and ready to be used in production. This helps minimizing per-pod resource overhead. Note that io.containerd.runtime.v1.linux is still the default runtime. (https://github.com/containerd/cri/issues/1075)
Added file-based generic runtime config options. This will be used by out-of-tree runtimes like gvisor and kata (https://github.com/containerd/cri/pull/1029), e.g.

[plugins.cri.containerd.runtimes.kata]
  runtime_type = "io.containerd.kata.v1"
[plugins.cri.containerd.runtimes.kata.options]
  TypeUrl = "io.containerd.kata.v1.options"
  ConfigPath = "/etc/kata/config.toml"

Added the pod_annotations runtime option. Pod annotations specified in the list will be passed to the runtime as OCI annotations. This enables runtimes to support annotation-based experimental features. (https://github.com/containerd/cri/pull/1084)
Added stream_idle_time option. This makes idle connection timeout of the streaming server configurable. (https://github.com/containerd/cri/issues/1057)
Added traffic shaping pod annotations support. NOTE: traffic shaping is still an experimental feature in Kubernetes. (https://github.com/containerd/cri/issues/1150)
Added max_conf_num option to plugins.cri.cni. This makes it possible to setup multiple CNI networks in a pod. NOTE: multi-network is not an officially supported feature in Kubernetes.(https://github.com/containerd/cri/issues/1154)
Added plugins.cri.registry.configs option to support TLS and auth configs of registries. (https://github.com/containerd/cri/issues/1143) NOTE: Non-mutual TLS is also supported. (https://github.com/containerd/containerd/issues/3521) (see registry.md for more details)
Added tcp endpoint for CRI service. The tcp service can be disabled with the disable_tcp_service option, and it is disabled by default. (https://github.com/containerd/cri/issues/1181)
Added max_concurrent_downloads option to restrict the number of concurrent downloads for each image. The default concurrency is 3. (https://github.com/containerd/cri/pull/1211)
Added privileged_without_host_devices runtime option to disable host devices for privileged pods for the runtime. This is especially useful for runtimes like kata. (https://github.com/containerd/cri/issues/1213)

Enhancements

Avoided Status lockup when CNI network setup/teardown is slow. (https://github.com/containerd/cri/issues/1078)
Added CNI config in Status (crictl info) output. (https://github.com/containerd/cri/pull/1158)
Fixed a bug that https is still attempted when an http mirror is configured. (https://github.com/containerd/cri/issues/1201)
Supported URL path in plugins.cri.registry.mirrors, e.g. https://my.custom.registry/anypath. (https://github.com/containerd/cri/pull/1227)
Added wildcard * support plugins.cri.registry.mirrors. (https://github.com/containerd/cri/issues/1196)
Removed an unnecessary round-trip to the image registry when pulling image. (https://github.com/containerd/cri/issues/1229)
Updated cni library to v0.7.1 which has better context cancellation support. (https://github.com/containerd/cri/issues/1236)
Updated cni plugins to v0.7.6 to fix a race condition in the bridge plugin. (https://github.com/containerd/containerd/issues/3507)

Deprecation

ctr cri load command is deprecated, use ctr -n=k8s.io images import instead.(https://github.com/containerd/cri/issues/909)
The plugins.cri.containerd.default_runtime option is deprecated, use plugins."io.containerd.grpc.v1.cri".containerd.default_runtime_name instead. (https://github.com/containerd/cri/issues/1076)
Runtime options including systemd_cgroups, runtime_engine and runtime_root are deprecated, use runtime options instead. (https://github.com/containerd/cri/pull/1217)
runtimeHandler field is moved from the sandbox info into status. (https://github.com/containerd/cri/pull/1063)
plugins.cri.registry.auths is deprecated, use plugins.cri.registry.configs instead. (https://github.com/containerd/cri/pull/1227)

Signed-off-by: Lantao Liu<EMAIL_ADDRESS>

Here is a diff of the release note to make the change more clear:
15c15
< Added plugins.cri.registry.tls_configs option to support TLS connections to registries. (containerd/cri#1143)
---
> Added plugins.cri.registry.configs option to support TLS and auth configs of registries. (containerd/cri#1143) NOTE: Non-mutual TLS is also supported. (#3521) (see registry.md for more details)
17a18
> Added privileged_without_host_devices runtime option to disable host devices for privileged pods for the runtime. This is especially useful for runtimes like kata. (containerd/cri#1213)
19c20
< Avoid Status lockup when CNI network setup/teardown is slow. (containerd/cri#1078)
---
> Avoided Status lockup when CNI network setup/teardown is slow. (containerd/cri#1078)
20a22,27
> Fixed a bug that https is still attempted when an http mirror is configured. (containerd/cri#1201)
> Supported URL path in plugins.cri.registry.mirrors, e.g. https://my.custom.registry/anypath. (containerd/cri#1227)
> Added wildcard * support plugins.cri.registry.mirrors. (containerd/cri#1196)
> Removed an unnecessary round-trip to the image registry when pulling image. (containerd/cri#1229)
> Updated cni library to v0.7.1 which has better context cancellation support. (containerd/cri#1236)
> Updated cni plugins to v0.7.6 to fix a race condition in the bridge plugin. (#3507)
25a33
> plugins.cri.registry.auths is deprecated, use plugins.cri.registry.configs instead. (containerd/cri#1227)

Codecov Report

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

@@           Coverage Diff           @@
##           master    #3548   +/-   ##
=======================================
  Coverage   44.94%   44.94%
=======================================
  Files         115      115
  Lines       12790    12790
=======================================
  Hits         5748     5748
  Misses       6170     6170
  Partials      872      872

Flag
Coverage Δ

#linux
48.77% <ø> (ø)
:arrow_up:

#windows
40.18% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


CountDown spoon causes switching spaces to focus on Hammerspoon rather than currently visible application

I disabled all spoons except WinWin (it failed when I tried to disable it). I then added in each spoon one by one until I reproduced the errors I was seeing.
When switching between spaces every once in a while switching spaces will give focus to Hammerspoon rather than the application it should give focus to. I tracked this issue down to only happen when the CountDown spoon is enabled.

I couldn't reproduce the errors you saw. Hammerspoon is not supposed to interfere with the current focus.
Can you give me more info about your problem, maybe a screencast?

So when I switch screens Hammerspoon shows up as active. I click Intellij to bring it into focus and then switch back and forth and then suddenly hammerspoon is active again. This only happens when CountDown is active.

It seems I've gotten what you were saying.
I couldn't reproduce the error because I disabled Show menu icon option from the beginning.

If this option is on, then while switching spaces Hammerspoon will steal the focus. Maybe it's a flaw of Hammerspoon?
For now, I suggest you disable this option as well. Hope this be helpful. :)

Awesome. It appears to be caused by the Show dock icon option and CountDown together which makes a bit more sense. I didn't need to disable the menu icon to get this to stop happening. Thanks!

@snowe2010 Ew, I meant to say "disable Show dock icon"...
Anyway, I'm glad it helps. :)


Added Code for issue  #3918

Added minimum spanning tree using prim's algo in DP section.

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
Added Minimum spanning tree using Prim's Algorithm in DP section.
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
#3918

@HarshCasper  plz review my PR.

Ok sir thank u


Now working in redmine version 5

Hello, we have issue with run this plugin on redmine 5 version. Any advice how to renable this plugin?
Is a compatibility update planned?
Thanks

Hello,
We have issue too with run this plugin on redmine 5 version. How run this plugin ?
Thanks for your help.

We found, that redmine 5 implemented mention by default. Soo this plugin is not needed more.


latest docker image tag is not updated when a new tag is pushed

It seems that ci/Makefile.main::docker-push rule does not update the :latest tag when a new tag is pushed.

@dpordomingo I think this is fixed now, right? It would need documentation though.

yes @smola , this feature was implemented in master and in v1.
Since master branch is deprecated and it will be replaced by v1 –where latest push is already documented as well–, do you think we should document it in master too?
If you consider that it should be documented in master too, just tell me and I'll do so :dancer:

@dpordomingo I don't think so, I assume we are about to deprecate master.

master is deprecated, the reason behind still being there is don't break the other old repositories working with this.

Nope, because then the v1 branch will be clone, by default, breaking some projects. What you can do, is wipe the master readme and point to v1.

Closing, since master is deprecated and v1 announced in master README.


chore: fix CI flakiness caused by race condition

The :test:deps task included both :build:components:inline and :watch:components:spec.  The latter use the CJS output (which we want for karma), but the former uses the ESM output (which we don't want). This led to a race condition where the tests only passed when the CJS output ended up being there when the tests started.
I also:

Made sure that watch mode isn't used on CI
Added a bunch of comments to the tasks

R: @hansl


python3Packages.faraday-plugins: 1.5.3 -> 1.5.4

Motivation for this change
Update to latest upstream release 1.5.4
Change log: https://github.com/infobyte/faraday_plugins/releases/tag/v1.5.4
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 142314 run on x86_64-linux 1

3 packages built:

faraday-cli
python38Packages.faraday-plugins
python39Packages.faraday-plugins


Apache Spark

I'm looking for a package for Apache Spark
https://spark.apache.org/downloads.html

There's one in pkgs/applications/networking/cluster/spark available under the name spark.

Thanks !
https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/networking/cluster/spark/default.nix


Adding login backend

Backend:

Create Login route => returns a JWT (needs .env with TOKEN_SECRET variable)

Create Register route

Create middleware function to check if the jwt token is still valid (7 days availability) for future requests that required authentication

Create Model for Users in DB (MongoDB Atlas) (need .env with DB_CONNECTION_LINK)

Adding schema for validation of the register and login forms

Ignore the .TSX created future work in progress

Cherry-picked the commits here and cleaned them up a little bit. Then created a new PR - https://github.com/iampava/frontend.ro/pull/45 that was merged. Closing this one


Error when running update all

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Luanch using SFTP
type "check all"
type "update all"
See error

Expected behavior
It to update plugins
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: Windows 10

Additional context
Add any other context about the problem here.
Traceback (most recent call last):   File "C:\Users\greys\Downloads\pluGET\src\__main__.py", line 16, in <module>     mainFunction()   File "C:\Users\greys\Downloads\pluGET\src\__main__.py", line 14, in mainFunction     getInput()   File "C:\Users\greys\Downloads\pluGET\src\handlers\handle_input.py", line 105, in getInput     handleInput(inputCommand, inputSelectedObject, inputParams)   File "C:\Users\greys\Downloads\pluGET\src\handlers\handle_input.py", line 87, in handleInput     getInput()   File "C:\Users\greys\Downloads\pluGET\src\handlers\handle_input.py", line 105, in getInput     handleInput(inputCommand, inputSelectedObject, inputParams)   File "C:\Users\greys\Downloads\pluGET\src\handlers\handle_input.py", line 58, in handleInput     updateInstalledPackage(inputSelectedObject)   File "C:\Users\greys\Downloads\pluGET\src\plugin\plugin_updatechecker.py", line 266, in updateInstalledPackage     if INSTALLEDPLUGINLIST[i][3] == True: IndexError: list index out of range

Hey,
thank you for your bug report.
I will investigate the issue and will report back.
Stay tuned!

Hey @greysilly7,
i just releases a new version which fixes your problem: v1.5.1
The numbers should also be correctly shown.
Update to the new version and you are good to go.
Thank you for flying with pluGET 🚀

Thanks


The variable is not defined

    @@for(var i = 0; i < button.length; i++){
        @@if(button[i].type == "return"){
            <a href="javascript:;" class="return `+button[i].position+`">

        }
        @@if(button[i].type == "search"){
            <a href="@@webRoot/search.html" class="search `+button[i].position+`">

        }
    }
    @@title

Error Info: i is not defined: (button[i].type == "return")

+1

@Keystion lol, the link you shared is my blog, the solution can solve my problem, but I don't think it is the best way. ^_^

[Laugh & Cry], The careless.

I have been in contact with gulp for a few days, and now I am working on the project with gulp.I encountered the problem of using if in the loop. I judged that the format was similar to the code of the main building.Looked at the host's blog just know originally I have written three yuan problem (^ o ^)
error demo: http://t.cn/RBk8K2M
我刚接触gulp几天，现在正在用gulp做项目。遇到了循环中使用if的问题，判断格式跟楼主的代码相似，结果报错了，也尝试过三元，结果直接输出。看了楼主的博客才知道原来我三元写的有问题（^o^）	【不会英语，x道翻译的凑合用吧，链接是示例代码链接】

I tested it according to the landlord's ternary method. The static content can be passed, but the dynamic data is still unexpectedly interrupted, as shown in the figure:
error demo: http://t.cn/RBkrUFT
我按楼主的三元方法测试了下，静态内容是可以通过的，但动态数据还是意外中断，如图：


(WIP) I1469 GLC Assembly should check KML for validity

This is a first-stab at validating the KML.  The change to the javascript file removes the KML validation done there (which is, arguably, not very good), and to add the lxml.etree validation in the python file.  A large section of the javascript file can be removed, but isn't at this time.

Let's link the GitHub ticket that this PR address. If no GitHub ticket, let's create one.

Let's document this fix in release notes

CI build failed as one of the unit test failed (timeutils_unittest). The changes in this PR does not seem to touch the code used by the unit test. I just re-started to the CI buid.

CI build failed as one of the unit test failed (timeutils_unittest). The changes in this PR does not seem to touch the code used by the unit test. I just re-started to the CI buid.

it's passing now. May be it was a glitch.

@tst-eclamar let's re-target this PR to <IP_ADDRESS> branch


Proposed description of how to generate P4Info for type definitions in P4 programs

OK, this took way too long to write, but hopefully it is clear enough for you to understand.  Corrections, questions, comments all welcome, especially on the weirdness that is Example 3.
https://github.com/jafingerhut/p4-guide/blob/master/p4runtime/README-p4info-and-type.md#proposed-p4c-rules-for-generating-types-in-p4info-files

@hesingh See the link above for a description of a proposed way to determine what to write to part of a p4info file when there are type and/or typedef types in a P4_16 program.  Antonin has not reviewed it yet, so do not be surprised if he finds problems with it later.
I am pinging you here because they seem related to this PR: https://github.com/p4lang/p4c/pull/1736
Until these details are reviewed and approved, I would treat them as 'experimental', and would recommend that you not try to modify that PR yet based on anything written here so far.  Even if we get an approved version of this, it might make more sense for further changes to be made after the PR above is committed (I don't have an informed opinion on whether one PR or two is better here).

@jafingerhut Sure, I didn't have any plans to change the PR code until Antonin asks for a change.   Having skimmed through the note, this is a larger churn than what the PR has and thus punting it makes sense right now.
A nitpick:
Where you say an enum with an underlying type of bit<W>, maybe just say, 'a SerEnum which is a serializable enum` .  Why not allow boolean in the mix for not just SerEnum but for other types.

Antonin had the same question.  The word "serializable" currently appears nowhere in the P4_16 language specification.  The word "underlying" and "underlying type" appear multiple times in the spec in the section on enums where the language feature is defined.  If someone wants to look up what an enum with an underlying type in the language spec is, they can find it.  If they try to look up SerEnum or serializable, they will find nothing.
That could be changed in the spec, of course, but going by what is there today, calling them anything else is an exercise in frustrating the reader looking for a definition.
bool could of course be added.  That would be a change to the current P4Runtime spec.  A small one, admittedly, but a change.

Ok.
Regarding
"Question: Should the P4Info file only include a type in the new_types section if the type is actually used in some other part of the P4Info file? Or should it include all types defined via a type declaration, even if it is not used elsewhere in the program?"
Hmm, during compilation, p4c removes any unused variables by p4c's frontend code.  p4runtime operates after p4 frontend runs.  Thus, I would think all unused types maybe removed as well.   One can test and check.

Created PR proposing mentioning the word "serializable" at least once in the language spec, so people can search the spec for that word: https://github.com/p4lang/p4-spec

Probably the correct answer to that question is that a type should only appear in the new_types section if it is actually used somewhere else in the program that has not been optimized away.

I don't think example 2 (https://github.com/jafingerhut/p4-guide/blob/master/p4runtime/README-p4info-and-type.md#example-2) is correct. Same for this program: https://github.com/jafingerhut/p4-guide/blob/master/p4runtime/expected-p4info-files/p416-type-use3.v1model.p4info.txt
The P4Runtime spec says that for a user-defined type, you need to walk down the chain until you rach a built-in type:

original_type, if and only if no @p4runtime_translation annotation is present. It specifies the underlying built-in P4 type for the user-defined type. If the underlying type used in the P4 type declaration is itself a user-defined type, original_type is obtained by “walking” the chain of type declarations recursively until a built-in type (e.g bit) is found.

That means that the new_types map entries in the P4TypeInfo message must always map to a built-in type, not another user-defined type.

And regarding what should appear in the new_types section, I believe it should only be types that are used somewhere in the P4Info.

Here is an example to make sure what should be the type_name for a MatchField.
Is type_name PortIdUint_t or PortId_t?
typedef bit<32>    PortIdUint_t;
type PortIdUint_t  PortId_t;

I'm also in favor of applying the spec literally as far as the @p4runtime_translation annotation is concerned. In the event of a "chain" of user-defined types T1 -> T2 -> bit<W>.
If an expression of type T1 is used (e.g. as a match field), and T1 has no @p4runtime_translation annotations, then the expressions is not considered "translated", even if T2 has a @p4runtime_translation annotation.
So basically I don't think the annotation should propagate "up the chain".
However, if T1 is a typedef to T2, then the expression is translated, and that's a major difference between typedef's and user-defined types.
In general I cannot think of a good use case for chains of user-defined types.

Here is an example to make sure what should be the type_name for a MatchField.
Is type_name PortIdUint_t or PortId_t?
typedef bit<32>    PortIdUint_t;
type PortIdUint_t  PortId_t;

PortIdUint_t is a typedef, it's not an actual type and it can therefore never appear in the P4Info. type_name is strictly for user-defined types.

Right, but then PortIdUint_t is reaching a built-in type.  So the caveat is that if a built-in type is reached via a typedef, use the parent of the typedef which is PortId_t?

@hesingh If you want to ask questions with a term like "parent" here, I think you need to give an example of which way the "parent-child" relationship goes, in your thinking.  You might be thinking the opposite direction that we are.

I don't think there is any "caveat" here. Either an expression is of type PortId_t or it's not. There is no such thing as an expression of type PortIdUint_t because it's not a type, it's an alias.
If an expression is of type PortId_t, the underlying type is bit<32>, not PortIdUint_t, which is not a type and has no meaning for P4Runtime.

Understood, thanks, Antonin.   In new_types, PortId_t has been used as the code.  I will look into type_name changes in the PR to comply with today's notes.

Antonin, thanks for the review comments.
I have not yet thought of a practical use case where it is beneficial to "stack" type definitions in P4 programs, either.  I only bring them up because I think it is a good idea that either:
(a) the compiler rejects them, or
(b) we say explicitly that P4Runtime does not support P4_16 programs with such type definitions, or
(c) we define precisely what the behavior is when a program contains such types.
I have been going down road (c) so far, to see where it leads and what makes sense there.
So for the following code example:
@p4runtime_translation("foo", 32)
type bit<9> T1;

type T1 T2;

If there is a bit-constrained value (i.e. table search key field, action parameter, etc.) that has type T2, you are saying that it should have type_name: "T2" in the P4Info file, yes?
Would you say its bitwidthshould be 9 or 32 in the P4Info file?  If 32, then we have to pay attention to the p4runtime_translation on T1 somehow.  If 9, then that sounds more consistent with your statements above, and I can't think of any objections, preferably with a mention in some docs somewhere.
Would you expect the following in the type_info message of that P4Info file, or something else?
type_info {
  new_types {
    key: "T1"
    value {
      translated_type {
        uri: "foo"
        sdn_bitwidth: 32
      }
    }
  }
  new_types {
    key: "T2"
    value {
      original_type {
        bitstring {
          bit {
            bitwidth: 9
          }
        }
      }
    }
  }
}

@jafingerhut That's the type_info I would expect and that's what's mandated by the spec, but perhaps I'm biased since I wrote that section.

You are biased in a very educated and informed direction, I would say :-)
I have updated the README based on your comments, and I hope it matches the behavior you expect now.
Latest version is at this link: https://github.com/jafingerhut/p4-guide/blob/master/p4runtime/README-p4info-and-type.md#proposed-p4c-rules-for-generating-types-in-p4info-files
If you would prefer to see the diffs, they are here, although looking at them I am not sure if it is easier to read them, or just the latest version linked above.  I fixed up some wrong P4Info message examples at the same time, which may confuse the diffs a bit: https://github.com/jafingerhut/p4-guide/commit/d38695ecce9928d59933d6ea238e173f8b1b625c

I read https://github.com/jafingerhut/p4-guide/blob/master/p4runtime/README-p4info-and-type.md#proposed-p4c-rules-for-generating-types-in-p4info-files and I think I agree with everything there at this stage.
If you are interested, I would be in favor of including this information either as a separate document in this repository ("Guidance for generating the P4Info message"?) or directly as an appendix in the spec.

Thanks for taking the time to read it over.
I have a slight preference for making it a separate document in this repository, if that would be OK with you.  It could be linked from the spec to make it easier for people to find it.  But I am OK with either choice.
I would like to add a little bit more material there, now that we have some consensus on what is there so far.
For example, a few notes on how to generate the type_info message in general, and including that message in all of the examples.
Also some examples for digest messages and register array element contents, which can have more arbitrary types.  Simple commonly expected kinds of examples are best to start with, but for implementers, having at least one or two wacky crazy ones can help explain the desired behavior in general.

A separate document is fine, especially if it keeps growing :)

Take an example of a value defined with type @p4runtime_translation("my_uri", 32) type bit<9> PortId_t and a table search key field with that type.
I think we have established that the P4Info type_info message should have a new_types sub-message that gives the uri of "my_uri" and sdn_bitwidth of 32.
I think we have also said that the table search key field also have a bitwidth field value of 32, as well as a type_name {  name: "PortId_t" } field.  This bitwidth field value of 32 should be redundant, since it can be determined from looking up the information about the type named "PortId_t" elsewhere in the P4Info message.
Do we want this redundancy?  Or do we want to say that the bitwidth field should be unset in a case where it has a type_info field from which the bitwidth can be calculated?

Created PR: https://github.com/p4lang/p4runtime/pull/193
It contains a slightly extended version of this document that Antonin reviewed, mentioned in an earlier comment on this issue: https://github.com/jafingerhut/p4-guide/blob/master/p4runtime/README-p4info-and-type.md#proposed-p4c-rules-for-generating-types-in-p4info-files
The main additions are more links to Github issues for any questions that I think are still outstanding, and the addition of example 4, which is right now mostly questions on how to represent serializable enum types in a P4Info message.

Closing this issue, since corresponding PR was merged: https://github.com/p4lang/p4runtime/pull/193


Migrations

Integrate corral with alembic
Use a db migrations folder your_project/migrations
Try to create 2 commands python in_corral.py makemigrations and python in_corral.py  migrate with the same functionalities of django migrations
Map all subcommands of alembic with command python in_corral.py alembic <alembic_sub_cms>

Closed with 13f295495e5605879748545e8c6685a960de66d1


modify position to relative

I don't want a full-screen column. Instead, columns are implemented within a qualified container. I think the position should be relative.

Do you have any examples for layouts where this is an improvement? Note that the split pane is meant to be used inside some kind of container component, which must be a flow root, and which will be filled completely by the split pane.
I played around with the attributes a bit, but I haven't found any non-broken examples where changing the position of the SplitPane itself from absolute to relative makes a difference at all.
Changing the position of the DragLayer to relative is definitely wrong and completely breaks the DragLayer. This can be seen by giving the DragLayer an obvious background color, but it is also visible as cursor type flickering while dragging (and would cause spurious pointer events in the inner panes while dragging).

I second this - as I use this in contained components - having position absolute requires me to override this property in style at the moment. A helpful addition would be to add a style prop - so then the end user can pass a style className or just a style CSSProperties Object when they don't want to use the default style. Other than that I haven't had any problems with this package compared to it's counter parts.

@g-monroe I would love make this component more useful for different usecases, but for that I need to understand what these usecases are and how to test them. Do you have a small code example that shows in what case the absolute vs relative position makes a difference?
Note that passing a className prop to the split pane is already possible, but I think it will not help to override the position attribute, as the explicit style setting takes precedence.


Adds a description for parallel compilation to README.

Coverage increased (+0.11%) to 57.0% when pulling c13472dcfc40643ac2ade5cbea4455671d02ca09 on shinnya:feature/doc/parallel_compilation into f845ecee0fcc0860373c3e396150d0f2e6c73ae5 on phpbrew:develop.

Looks good!

Hi @shinnya
I've fixed the CI tests on master branch, so we might want to merge them into develop branch and make the CI tests works on develop too. :D
BTW, you can work on the new features on the branches directly, you don't have to open pull requests for future changes. :)

@c9s
Thank you for your merging :+1:

I've fixed the CI tests on master branch, so we might want to merge them into develop branch and make the CI tests works on develop too. :D

Oh, I understood!

BTW, since you're a co-author of phpbrew, you can work on the new features on branches directly, you don't have to open pull requests for future changes. :)

Exactly! But I sent PRs force of habit...


Update

Codecov Report

Merging #24 (ae16df4) into master (efb6bad) will increase coverage by 1.47%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master      #24      +/-   ##
============================================
+ Coverage     69.49%   70.96%   +1.47%
- Complexity       81       86       +5
============================================
  Files            22       23       +1
  Lines           236      248      +12
  Branches         19       18       -1
============================================
+ Hits            164      176      +12
- Misses           69       70       +1
+ Partials          3        2       -1

Impacted Files
Coverage Δ

src/main/java/edu/fiuba/algo3/Main.java
0.00% <ø> (ø)

...main/java/edu/fiuba/algo3/lector/LectorDeJson.java
91.66% <ø> (ø)

src/main/java/edu/fiuba/algo3/modelo/Teg.java
0.00% <ø> (ø)

...rc/main/java/edu/fiuba/algo3/modelo/CartaPais.java
100.00% <100.00%> (ø)

.../edu/fiuba/algo3/modelo/ColeccionDeCartasPais.java
100.00% <100.00%> (ø)

src/main/java/edu/fiuba/algo3/modelo/Ejercito.java
100.00% <100.00%> (ø)

src/main/java/edu/fiuba/algo3/modelo/Pais.java
100.00% <100.00%> (+3.03%)
:arrow_up:

src/main/java/edu/fiuba/algo3/modelo/Jugador.java
38.46% <0.00%> (-7.70%)
:arrow_down:

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 efb6bad...ae16df4. Read the comment docs.


Change options dynamically

Is there a way to change iScroll options dynamically without having to destroy and initialize it again?
In my case I would like to set mouseWheel value depending on some events.
I didn't see anything in the docs about it, but I might have missed it...

Any feedback on this?

I've been trying the following, but it seems the refresh it is not intended for this purpose?
$('button').click(function(){
	myScroll.options.mouseWheel = false;
     setTimeout(function () {
        myScroll.refresh();
    }, 0);
});

I got the idea from: https://groups.google.com/forum/#!topic/iscroll/LEvagkZqu_I

But the example link provided shows it is not working in my case?

I told ya :)

So... should I assume from that answer that this method doesn't work for the mouseWheel option?

unfortunately, yes... BUT it would be easy to disable wheel on the fly.
All you have to do is to remove (or add) the following events from the this.wrapper element:
'wheel', 'mousewheel', 'DOMMouseScroll'

for reference https://github.com/cubiq/iscroll/blob/master/build/iscroll.js#L1094

Thanks for it, I'll take a look at it.

very untested but should get you started
https://jsfiddle.net/511wmq3h/13/

Thanks!
Should I assume it doesn't support IE 8?
The docs are not very clear about it:

Out of the box multi-platform support. From older Android devices to the latest iPhone, from Chrome to Internet Explorer.

But it seems in the code it is missing the attachEvent event for IE < 9:
//add
this.wrapper.attachEvent('onmousewheel', this);  //IE 6/7/8

//remove
 this.wrapper.detachEvent('onmousewheel', this); //IE 6/7/8

IE8 is not supported, the latest commit adds some kind of IE8 compatibility @sculove can help you with that. IE8 should burn in hell!

Yeah, not such a big deal anyways. Just wondering.

i am trying to remove snap once the scroll reaches the first snap so it can scroll normal after. I managed to set snap = false and refreshed but it throws this error which causes the animation to pause
Cannot read property 'length' of undefined
whats the best way to remove snap and bring it back in as needed or achieve what i am trying to do

@eliteproxy7 try  myScroll.options.snap = false; worked for me


Drop support for Django < 2.2 LTS (incl. Python 2); add support for Django 3.1 & Python 3.9

Continue supporting Python 3.5 because pytest-django depends on django-configurations and supports Python >= 3.5.

LGTM. Only other notes is I think you can remove the following from the top of setup.cfg.
[wheel]
universal = 1

I'll try to find some time this week to update the PR.


Add a missing json_decref in the example

Closes #623

Coverage remained the same at 96.234% when pulling de5f2963ab59fa070590ae36c2c0b22ada7b60f7 on fix-example into 128e9c5f376ac425f13d3b1cf9a38d53e544ad23 on master.


normalize insert query more efficiently

Feature Request
Is your feature request related to a problem? Please describe:

For an insert query containing large strings in the VALUES part, the normalize procedure is not that efficient since it processes the query from beginning to the end.
Describe the feature you'd like:

For insert ... values (xx), we can specially normalize it to be insert ... values(...), i.e, we can skip processing the possible large string after values.
Since normalize only involves lex analysis, with no grammar analysis, we have to specially check the insert and values keywords, which makes it pretty tricky.
Besides, there may be ON DUPLICATE UPDATE in the end of the query, we need to specially handle them as well.
Describe alternatives you've considered:

N/A
Teachability, Documentation, Adoption, Migration Strategy:

Side effect of this improvement is that, both insert into t values(1,1) and insert into t values(1,1),(2,2) would be normalized to insert into t values(...).

this should also recognize replace into. the keyword values can also be value.

this should also recognize replace into. the keyword values can also be value.


cs (patch): sync status tooltip

What is the purpose of this pull request?

What problem is this solving?

Types of changes

[ ] Feat: (new functionality)
[ ] Bug fix: ([#ref number] non-breaking change which fixes an issue)
[ ] Chore: (improvements that will not reflect in production behaviour)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Requires change to documentation, which has been updated accordingly.

#73  👈
main

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

Join @keeganpotgieter and the rest of your teammates on  Graphite


Warn the user if only a few square sizes are signed over

By default, we should sign over all relevant square sizes #239, but if for some reason this is overridden, then we should probably warn the user that their tx might not be included in a block as soon as they expect.

the default is now to sign over all possible square sizes, so this is no longer relevant