How to send an HTML attachment from a Microsoft Teams bot

I noticed that when you use the app to send a card to another user, it has the desired effect- a short summary of the weather appears in the toast popup. Looking inside the JSON that represents that message shows that the "card" is actually an HTML attachment.
Am I able to replicate this by sending an HTML attachment? I have (naively) tried the following but it causes an exception:
  Activity reply = new Activity();
            reply.Type = ActivityTypes.Message;
            reply.Text = "Test the toast";

            reply.Conversation = new ConversationAccount()
            {
                Id = conversationResponse.Id
            };
            reply.Attachments.Add(new Attachment()
            {
                ContentType = "text/html",
                Content = "
Some generated html
"
            });

The exception I'm getting is "Operation returned an invalid status code 'BadRequest'" from within mscorlib.dll.

@catchmeifyou Sending a Html attachment from a bot is not currently supported. You could try opening the Html content inside a Task Module .

Thank you for response.


New ReactSDK API

Updated React SDK API. Many changes across the board. See the README.md how to use it now.

thanks @Munter !

thanks @Swiftwork ! mind having another look? updated all the hooks including a rename of useUser etc. to go under useUpdateContext.

this example doesn't make much sense, but hopefully illustrative enough: https://github.com/bucketco/bucket-javascript-sdk/blob/new-api/packages/react-sdk/README.md#useupdatecontext
ideas are very welcome.


Add more split integration tests

Closes #3407

I'm working on a test for the first mentioned TODO in #3407. I have the main things roughly in place but am not exactly sure what to test for:

// ELASTICITY_TODO tablets used to always split into 2 tablets. Now the split operation will
// split into many. How does this impact a tablet with many files and the estimated sizes after
// split vs the old method. Need to run test where we add lots of data to a single tablet,
// change the split thresh, wait for splits, then look at the estimated sizes, then compact and
// look at the sizes after. For example if a tablet has 10M of data and the split thesh is set
// to 100K, what will the est sizes look like across the tablets after splitting and then after
// compacting?

@keith-turner, it looks like you authored this comment. Do you have any suggestions for testing this, i.e. what to check for after each step in the process outlined in the comment?

@keith-turner, it looks like you authored this comment. Do you have any suggestions for testing this, i.e. what to check for after each step in the process outlined in the comment?

The first thing I would try in manual experimentation.  Like create a tablet w/ 1M file, split into 100 tablets (maybe some split outside the range of the data) and look at what the estimates look like.  Then I would go from there for creating an IT. Would probably check that each estimated size falls with in some range.

Originally I was planning to address both of the cases outlined in #3415 but since one is already done and I don't have a clear path for the second one yet, I'll just merge this in.


New frontiers

Dear @MatteoMacchini, my ultimate goal is to publish the package on PyPI.
In order to achieve this, I would like to hit some milestones / cover some missing areas before publishing

[ ] Implement tests
[ ] Adding a functionality that takes a file as input
[ ] Adding and publishing docs
[ ] (Optional) Add a better interface

Are you willing to help? In such case, please choose one of the first two bullet points and tell me which one you prefer.
x
Andrea

Hi @andreasala98, I would rather try to implement the tests.

That’s great, thanks!
Are you familiar with pytest?
It’s very intuitive (the trick is that the testing functions must start with the ‘test’ word)
Try to emulate pytracer or qibo
I already implemented on the reverse branch a function to check if a code is valid, maybe you could use it.
Moreover once a few tests are done, it would be cool to set up a github action that runs all the tests upon commits (CI)

I never used pytest, but I have seen some examples in pytracer.
Surely a github action could be very useful later on.

Lovely. When you start working, I suggest you open a new issue & PR to keep better track of your progress.
Time wise, it would be great  if we finish the project by the end of October.
PS I will change the project name to simply “getcf”


DOI catalogs exceed 100,000 records

I noticed in the Zenodo release that:

unpaywall_100k.csv.gz has 105,647 DOIs
wos_100k.csv.gz has 103,539 DOIs

The study preprint indicates that each sample DOI catalog contained only 100,000 DOIs.
This isn't an issue for me, just wanted to make sure you're aware of this discrepancy.

true!  Yup, the exact numbers didn't make it into the paper.  We lose a few of them in our analysis because they don't have years in crossref, so the numbers in our analysis are closer (though still not I think absolutely exactly) 100k.


How to increase number of schedules in a day

Hello,
I am using monthly view. So I want to increase number of schedules in a day.  Now its only 2.
Is it possible?
thank you.

Is it possible to achieve such an effect that all meetings are displayed and the line height is calculated automatically?
actual

expected


Feature: Ability to debug config loader strategies

Add the ability to provide a logger and have configuration between each strategy (when processing) outputted to the logger.
How to verify

Check out this feature branch.
Run $ npm link.
Create a new project directory.
In that directory, create a new file called config-test.js and put the content of this gist in it.
Link our new project to our feature branch by executing $ npm link stormpath-config.
Execute $ node config-test.js.
Check the console.

Expected
The following console output:
Before:FooStrategy:
{}

Result:
{
    "abc": "123"
}

Config loaded with null { abc: '123' }

Other than my comments on the double quotes and the tests, I've verified that this works as advertised 👍

@typerandom I've fixed my comments for you. Please review :)

LGTM

Looks good. Thanks @timothyej! :+1:


Model support request：RealSR、ATD-SR

RealSR DF2K
RealSR DPED
RealSR DF2K (JPEG)
These three models are said to be ESRGAN architecture.
May I ask if the author plans to use the RealSR model as a built-in support model? This way there are more parameters that can be adjusted.I saw that some App projects for image super-resolution also use RealSR as a built-in model. I tested it and the effect was pretty good.
RealSR
RealSR-NCNN-Android
ATD_SRx4
There is also a model of ATD architecture. I wonder if this can be supported?
The licenses of the above models are Apache2.0.

The 3 RealSR models have been added. And pre-converted models are available in Google Drive.
What kind of parameters of RealSR models would you like to adjust?
ATD support is not feasible due to Core ML issue:
ValueError: Core ML only supports tensors with rank <= 5. Layer "x.7", with type "reshape", outputs a rank 6 tensor.

What I'm wondering is whether the RealSR model can adjust the magnification and noise reduction strength.
Also, thank you very much for your work.


Added list read/write for symbols

Fixes #266
This adds the option to read multiple symbols at once, or write to multiple at once.
Unfortunately this is not directly compatible with adsSumRead and adsSumWrite (assuming we don't want the redundant info lookup when using only the name).
This is because those functions are based on the SAdsSymbolInfo structs, which contain the integer dataType, instead of a ctypes like plc_type.
I've tried to move some of the logic to separate functions so they can be reused, but the new symbol read/write methods resemble the classic functions a lot.
Example script:
from pyads import Connection
from random import random

plc = Connection('<IP_ADDRESS>.1.1', 851)

with plc:

    var_names = [
        "GVL.my_double",
        "GVL.another_double",
        "GVL.my_text",
        # "GVL.my_list"
    ]

    symbols = [plc.get_symbol(var) for var in var_names]

    new_data = [random(), random(), "Hello again"]

    data_with_names = dict(zip(var_names, new_data))

    # response = plc.write_list_by_name(data_with_names)
    # print(response)

    response = plc.write_list_symbols(symbols, new_data)
    print(response)

    # data = plc.read_list_by_name(var_names)
    # print(data)

    result = plc.read_list_symbols(symbols, True)
    print(result)

    for symbol in symbols:
        print(symbol.name + ":", symbol.value)

@stlehmann I was hoping you might already have some insights here.
Would you like less overlap with the old *_list_by_name functions?
Do the new interfaces seem right?

This looks like a pretty good additional feature, nice work! The symbol way of using pyads I think is fast becoming a favourite from the looks of things. I can already see a use case to optimise some of my code to use the reading a list of symbols.
I haven't looked through the implementation in detail yet, but some fast thoughts with my opinion:

My thought is this is going to be a well used feature, as I said as soon as I noticed this PR and your example I got excited

given this addition there will sort of be two competing ways to use pyads from an end users perpsective so time should be given to make sure this is straight forward and clear to the end user what all methods do but also maintain familarity between them.
Also given my point that I think it will be well used, time should be given to make sure it's straightforward and clear for the maintainer and contributors of pyads to maintain.

I believe changing the method names to read_list_of_symbols and write_list_of_symbols may read better to the user, gives an accurate description of what the method is doing and isn't that much longer for a name.
Possibly could think about the parameters for the write_list_symbols; would it make sense to make this a dictionary so the interface is in line with write_list_by_name with the keys being the symbol and the values the value to write to that symbol. There is an argument that could be had to which one is a nicer interface (two lists or a dict) and which one is optimal, but since write_list_by_name and to some extend write_structure_by_name use dictionaries as input I believe consistency across the module would be beneficial.
Have read_list_symbols always return the dictionary and do away with the optional parameter. Again for consistency with read_list_by_name and also I believe the user will likely be expecting something back when asking to read something from the plc even though in this case it is not actually required. I expect the time overhead of additionally inserting the keys into a dictionary will not be of importance? Alternatively just swap the optional parameter around so the default is to return.
I am wondering if it is possible to modify adsSumReadBytes to have the same interface as adsSumRead but instead just return bytes instead of doing the processing as you say. I'm not sure it is possible to modify data_symbols: List[Tuple[int, int, int]] into  data_names: List[str], data_symbols: Dict[str, SAdsSymbolEntry],   structured_data_names: List[str] and then that processing for the conversion can be pushed into the method that calls adsReadSumBytes.

The singledispatch library could be considered (or two methods or using more private methods with more descriptive names or another solution) so that am adsSumReadBytes like method could exist for datanames, then we can have adsReadSum just call that. Also down the same lines, just have an adsReadSum which accepts both options.
I think my main concern here is that as you say there is an overlap with the existing functions, but I think that is ok and can not be avoided to some extent as both methods (by dataname and by symbol) are both just reading bytes from the PLC and converting them into the desired format at the end of the day. I think it just needs to be thought about and made clear to why there are similar methods that appear to do a similar thing but have different parameters.
From an end users perspective this is just the internals of the library but I think for the maintenance of the library going forward it is important.
Is there scope to potentially have read_list_of_symbols just wrap around read_list_by_name with the addition of updating the symbol cache. As the symbol contains the dataname. I guess this becomes memory inefficient as you then build up two caches and adds an extra overhead of having to fetch the handle twice.
I am sure @stlehmann will have a better understanding of the organisation of the library and be able to give more thoughts

I am not 100% sure if it is applicable here , but I know beckhoff advise that no more that 500 symbols/requests are read/written in one ADS call. Therefore in the implementation of read/write_list_by_name the list of datanames is chunked up into number of ads_sub_commands blocks. I think this is required here too as there is still a number of ads requests:

Could consider renaming convert_data_to_value method to again be a more specific and descriptive (naming is always hard and contentious so I apologise if this seems petty). possibly something like get_value_from_ctype_data.
Could also consider refactoring to be more like read_list_by_name where the conversion from bytes to relevant symbol data function is in pyads_ex.py, then can make convert_data_to_value a private method that doesnt span modules, possibly making ads.py easier to read. Again I'm sure @stlehmann will have a better thought on this.
It could be worth splitting this work into two PRs, purely from an admin perspective, one that refactors pyads_ex.py and adds in the adsReadSumBytes, potentially making it compatible with the existing adsReadSum. Then another PR for actually adding in the read/write_list_symbols feature. This way I think it may make it easier to test and make sure the first PR and refactoring of the pyads_ex.py file does not break anything given the difficulty in thoroughy testing this library. This could be made into a minor release, giving maintainers a chance to easily debug in the future.
Likely you were planning on it but tests and docs wil need to be added too.

My apolgies for what grew into a longer list than I thought as I spent more time thinking about it but I hope that is food for thought and helps you and @stlehmann guide this feature smootly into the library.
Also, I know that I am not a maintainer of pyads, but I have contributed and I use it a lot so I have an interest in the features that get added so thank you again for your work on the AdsSymbol side of things!

Whoof, a lot. But thanks @chrisbeardy , that's very useful.

I believe changing the method names to read_list_of_symbols and write_list_of_symbols may read better to the user, gives an accurate description of what the method is doing and isn't that much longer for a name.

Agreed, I'll change that.

Possibly could think about the parameters for the write_list_symbols; would it make sense to make this a dictionary so the interface is in line with write_list_by_name with the keys being the symbol and the values the value to write to that symbol. There is an argument that could be had to which one is a nicer interface (two lists or a dict) and which one is optimal, but since write_list_by_name and to some extend write_structure_by_name use dictionaries as input I believe consistency across the module would be beneficial.

Yep, was thinking about that too. I'll change it.
Though nothing stops us from accepting both? We could detect if the first argument is a list or dict, and take it from there? Though that might make the interface too complicated.

Have read_list_symbols always return the dictionary and do away with the optional parameter. Again for consistency with read_list_by_name and also I believe the user will likely be expecting something back when asking to read something from the plc even though in this case it is not actually required. I expect the time overhead of additionally inserting the keys into a dictionary will not be of importance? Alternatively just swap the optional parameter around so the default is to return.

Also agreed. Will change.

Could consider renaming convert_data_to_value method to again be a more specific and descriptive (naming is always hard and contentious so I apologise if this seems petty). possibly something like get_value_from_ctype_data.

Will change.
No, I don't find it nick-picky! This part of writing good code, and in terms of naming I can still learn some.
Alright, I think that most of the concrete points. I guess now is the part where we debate about structure and details.
About the refactoring stuff, that is a good point. Though I think we need both interfaces (read_list_by_name and read_list_of_symbols) in order to write a good shared low-level base.
I'm personally not too worried about things breaking. The changes I made so far are no big changes. But I understand wanting caution.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

35 of 81 (43.21%)  changed or added relevant lines in 2 files are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-2.5%) to 91.9%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pyads/ads.py
4
50
8.0%

Files with Coverage Reduction
New Missed Lines
%

pyads/testserver/testserver.py
5
90.76%

Totals

Change from base Build<PHONE_NUMBER>:
-2.5%

Covered Lines:
1611

Relevant Lines:
1753

💛  - Coveralls

I've started a refactor branch containing the refactors I did in this branch (but without the new interface): https://github.com/RobertoRoos/pyads/tree/feature/refactor
We can create a pull request for that, and retarget this PR into that one to split the diffs.

I like this as an API for the user.
I agree that it may be the case the user is using symbols and lists and then it would be irritating to force them to convert this to a dictionary just for the input to the write method. My only slight concern is the use of advising the user to write to a private value of the symbol class. I guess the "proper" way do do it would be to to make sure auto_update is off and then write the property value instead but I can understand why that would be awkward and confusing to a user who doesn't care about the implementation. I guess as long as it is properly documented then I see no big harm. I am also happy with the writing of the private variables in the implementation of read/write_list_of_symbols as they are tightly coupled to the symbol class anyway and can be dealt with using unit tests.
The only other change to be considered from a user API perspictive is the ads_sub_commands option which by default should be set to 500.
As you say that I believe that is the concrete / user perspective points. The rest is internal implementation, this can be discussed and I believe @stlehmann is likely best placed to have a view on this when they have time available. Although as it is internal and I agree your changes are not huge, there is always scope to just refactor the internals at a later date if/when required.
As for naming, I discovered this cheatsheet a little while ago and I thing it sums up and makes some good suggestions.

Also I forgot to mention, i like the use of
Comparable to :meth:`Connection.read_list_by_name`.
See also :class:`pyads.AdsSymbol`.

in the docstrings.

Sorry to keep you guys waiting. I'm a bit busy at work at the moment and hardly finding any sparetime for development. @RobertoRoss I'll try to give it a closer look during the week.

@stlehmann yeah I never rebased this branch onto the other refactoring branch. I'll do that next.
About the double interfaces, I don't think splitting this package would be necessary. I would say all real functionality remains in separate functions, and the Symbol class just references those function.
I find it hard to estimate how confusing the two methods are to new Pyads users. I think it's manageable.

Yes, a rebase would be good. You can rebase on master because the refactoring branch has already been merged.

Ah this looks much better now. Thanks for rebasing. 👍

Okay, I've created the above. I think this could work, I like the unit-purposes:
* `read_list_by_name` handes the name-info retrieval while `read_list_of_symbols` only processes the symbol objects

* `_read_list` queries the pyads_ex back end to get Python values out of symbol infos (also handles ads query limit)

* `adsSumRead` gets binary data from symbol info and turns that into Python values (regardless of the type of info storage)

@stlehmann , thoughts?

I gave this some thoughts and I come to dislike the idea of different functions for symbols and names more and more. The Symbols approach should integrate smoothly in the current API and shouldn't feel so much like a complete different way of doing things with pyads. So my preferred way is to with Connection.read_list and Connection.write_list processing both strings and symbols and given some time deprecate the read_list_by_name function.

Alright, that's understandable. I'll modify the code (but I think I'll archive the current version on my fork just in case).
I intend to approach it with an if ... else ... in read_list(), calling one of two private methods to do the real read.

Yes, I think a simple if ... else should do to separate the two cases.

And there it is. I started with updating the docs too.

@stlehmann , alright, that makes sense, no worries.
I think I'll just merge this into my own project, so it's the same to me in the end.

In the meantime @RobertoRoos  you could look at making a separate pypi package as an extension of pyads, called pyads-symbols as Stefan suggested. This would allow you to work downstream of pyads and add lots of symbol features. This could make pyads easier to maintain in the future and give the symbols some more freedom. It can then always be merged back in later if deemed wise at the time.

In the meantime @RobertoRoos you could look at making a separate pypi package as an extension of pyads, called pyads-symbols

I very much support this idea. It has many benefits in terms of maintainability and it makes it easier to implement new features on top of pyads without bloating the pyads package too much. A first step could be to move the symbols module there and then go on and add new features successively


FileReloader doesn't see changes to included and inherited templates

If I'm using the FileReloader and change a template that I {% extend %} from or {% include %}, Ibis still shows the old file content. See here:
from pathlib import Path
from time import time

# import inspect
import ibis
from ibis.loaders import FileReloader

loader = FileReloader('templates')
ibis.loader = loader

def snippet_cache():
    # load it once to cache
    loader('main.html').render()

    new_text = str(time())
    changed_file = Path('templates/snippet.html')
    changed_file.write_text(new_text)

    actual = loader('main.html').render()
    if not new_text in actual:
        print('expected:', changed_file.read_text())
        print('got', actual)

def base_cache():
    # load it once to cache
    loader('child.html').render()

    new_text = str(time())
    changed_file = Path('templates/base.html')
    changed_file.write_text(new_text)

    actual = loader('child.html').render()
    if not new_text in actual:
        print('expected:', changed_file.read_text())
        print('got', actual)

snippet_cache()
base_cache()

Just want to bring it to your attention.

Thank you!


automate infra proxy cookbook list UI

:nut_and_bolt: Description: What code changed, and why?
Code changes for the introduction of infra proxy cookbook list component in infra proxy module to make automate-ui a single source of truth for chef infra cookbook data here
In this PR following points we have covered:

Created cookbook-list component in infra-proxy module to show cookbook list of specific Org
Designed infra proxy cookbook-list UI flows and used Infra-proxy-service
Fixed chef-sever left side navbar option issue for non accessible policy

:chains: Related Resources
Refered Wireframes: https://chef.invisionapp.com/share/3JVLVFMASDZ#/screens/401258847
For feature description refer: #1544
:+1: Definition of Done

Added cookbook-list component in infra proxy module
Fixed chef-sever left side navbar option issue for non accessible policy

:athletic_shoe: How to Build and Test the Change
build components/automate-ui

Unable chef server side nav option under Infrastructure using feature flag
add sever and org credentials of chef-sever/chef manage
click on specific org to check cookbook list

:white_check_mark: Checklist

[x] I have read the CONTRIBUTING document.
[x] Tests added/updated?
[ ] Docs added/updated?
[x] All commits have been signed-off for the Developer Certification of Origin.

:camera: Screenshots, if applicable

@sachin-msys  Do you know where we get the credentials for step 2 of your testing instructions?

add sever and org credentials of chef-sever/chef manage

@SEAjamieD i believe you can use infra_service_load_sample_data  now

maybe not, that doesnt seem to allow me to get to the cookbooks page

believe you can use infra_service_load_sample_data  now

I think that gets us halfway there

ya, that only adds cookbooks and orgs https://github.com/chef/automate/blob/master/dev-docs/adding-data/adding_test_data.md#adding-data-to-infra-views


9.0.457 is broken

Steps to reproduce
vim -u NONE
Expected behaviour
Vim should start like usual.
Instead, I see this repeated five times at the bottom of the screen, as vim messages: E341: Internal error: lalloc(0, )
Version of Vim
9.0.457
Environment
Ubuntu 20.04
terminal= kitty 0.26.2
shell: bash 5.0.17
Logs and stack traces
No response

I should also add that once I make the messages go away, the statusline is the last screen line in the console, instead of the penultimate one.
This last symptom also happens in gvim.

Sorry, it looks like one needs a vimrc containing se ls=2 to make this show up right when starting vim.  I have make a vimrc that contains ONLY that, I see the problem upon startup.
Also, git bisecting reveals that the bad patch is 9.0.455.

The incorrect placement of the statusline also appears in xterm, though using xterm I don't see the error messages.

Setting cmdheight temporarily to 2 and then back to 1 will redraw the statusline correctly: :set cmdheight=2 cmdheight=1
Tested with alacritty terminal.

I have the exact same environment (OS, terminal, shell, Vim) and I can't reproduce.  I guess something else is required.
If Vim is compiled locally, how is it configured?
If it's not, what's the output of :version?

Also, git bisecting reveals that the bad patch is 9.0.455.

Cc: @luukvbaal via https://github.com/vim/vim/pull/11117

Able to reproduce in kitty, not in st. I'll look into it.

Using a file only containing "set ls=2" and using "vim -u {that-file}" I see there is no command line.
Reverting patch 9.0.0455 fixes it.
Since no test catches this I suspect it's a startup problem.
I hope Luuk can locate the problem.

Yes, the problem was easily located(the change in main.c from https://github.com/vim/vim/commit/5ed391708a62b4ebaa84dd23e32a416e5c3383d9 is the culprit, it seems some terminal communication may rely on the window size before it is initialized with that change, resulting in the alloc error.) from. Currently it feels like we are littering the code with workarounds for 'splitscroll'. I'll investigate once more if it is possible to refactor the code for 'splitscroll' to stay localized to window.c, it feels like that should be. If not, I'll find another workaround to fix this issue.

I see the same issue with my ~/.vimrc on Linux.
The problem started with this patch:
commit 5ed391708a62b4ebaa84dd23e32a416e5c3383d9 (tag: v9.0.0455)
Author: Luuk van Baal<EMAIL_ADDRESS>Date:   Tue Sep 13 11:55:10 2022 +0100

    patch 9.0.0455: a few problems with 'splitscroll'

    Problem:    A few problems with 'splitscroll'.
    Solution:   Fix 'splitscroll' problems. (Luuk van Baal, closes #11117)

Yet my ~/.vimrc does not set splitscroll.
Furthermore, just doing /foo to search for string foo fails like this:
E342: Out of memory!  (allocating<PHONE_NUMBER>3709551604 bytes)
E486: Pattern not found: foo

This silly looking command works around it:
:set cmdheight=2 cmdheight=1

Note that merely doing :set cmdheight=1 does not fix it.
Bug does not happen with vim --clean.  I'll try to narrow down what triggering it in my ~/.vimrc.

@dpelle have you checked the linked patch? Does the issue still occur there?

If I use this minimalistic one-liner ~/.vimrc...
set laststatus=2

.... then, just starting vim gives:
E341: Internal error: lalloc(0, )
E341: Internal error: lalloc(0, )
E341: Internal error: lalloc(0, )
E341: Internal error: lalloc(0, )
E341: Internal error: lalloc(0, )

I see it with the latest vim-9.0.459 and it started with vim-9.0.455 (vim-9.0.454 and earlier are fine).

@dpelle have you checked the linked patch? Does the issue still occur there?

Ah, I just saw your message as I was investigating.
Yes your patch posted earlier indeed fixes it.
Heel erg bedankt @luuk!

For what it's worth, this reproduced the bug without having to create/modify ~/.vimrc:
$ vim --clean --cmd 'set laststatus=2'
E341: Internal error: lalloc(0, )
E341: Internal error: lalloc(0, )
E341: Internal error: lalloc(0, )
E341: Internal error: lalloc(0, )
E341: Internal error: lalloc(0, )

apparently fixed by https://github.com/vim/vim/commit/470a14140bc06f1653edf26ab0b3c9b801080353


Run nf-core lint

Running pipeline tests  [####--------------------------------]   12%  'check_files_exist'
ERROR: Found test failures in 'check_files_exist', halting lint run.

INFO: ===========
 LINTING RESULTS
=================
  10 tests passed   1 tests had warnings   2 tests failed

WARNING: Test Warnings:
  https://nf-core.github.io/errors#1: File not found: ['tests/run_test.sh']

ERROR: Test Failures:
  https://nf-core.github.io/errors#1: File not found: ['.travis.yml', '.circle.yml']
  https://nf-core.github.io/errors#1: File not found: ['CHANGELOG.md']

ERROR: Sorry, some tests failed - exiting with a non-zero error code...


Add OWASP dependency checking

@anthonydahanne consider this is a prototype of how this could be done. We should probably assess the impact on cloudbees before we merge it. In particular I'm wondering if it's going to repull the whole NVD database every time it runs.

I think this PR is a step in the good direction, even if there is some duplicated configuration.
Shall we proceed ?

I would like this to go through. So I approved it. A let you decide if a refactoring is needed.


Fix how we export KHR_Texture_Transform

Flattening the texture is not a good idea
https://forum.babylonjs.com/t/sandbox-glb-export-destroys-khr-texture-transform/7338

Pinging @Drigax for thoughts

Hi I am using this BABYLON.GLTF2Export.GLTFAsync(scene, "object").then((gltf) => {
gltf.downloadFiles();
});
for my base I have set texture offset and scale.
output in .gltf is showing like these
"baseColorTexture": {
"index": 0,
"texCoord": 0
}
how to enable KHR_texture_transform

I pinged back @Drigax on the forum thread to double check

ok thanks @sebavan

I agree, I'm not sure why this was done. I responded back on https://forum.babylonjs.com/t/sandbox-glb-export-destroys-khr-texture-transform/7338/8 with my findings. Basically, our KHR_Texture_Transform implementation bakes the texture if it is translated such that the center of the texture is no longer at (0,0).
My proposed fix removes this check and baking logic.


[JOSS review] Manuscript Figure 1 (PySAL logo)

I think that Figure 1 of the manuscript (i.e., the PySAL logo) is not needed and should hence be deleted - especially considering that JOSS papers tend to be very brief.
https://github.com/openjournals/joss-reviews/issues/2826

Thank you for bringing this point. We agree with this suggestion. We have removed the image in #588.


exchange value missing in RPC_Load_Test.jmx

I had a problem on RPC_Load_Test.jmx. The exchange value is missing on
RCP Response configuration. I put in exchange field the value my_rpc_exchange. It's solve for me.

Fixed, thanks.


no space ，and  can not start the project  ,how to solve the problem

no space ，and  can not start the project  ,how to solve the problem
my acount si<EMAIL_ADDRESS>

There was a problem when starting the project runtime. This should be resolved shortly. Please try again later

again  again  again  ,but still again

hi, can you tell us exactly what error you are getting?

i  can  not  start  the  gpu or  cpu   mode
---Original---
From: @.>
Date: Fri, Jan 14, 2022 13:08 PM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [aws/studio-lab-examples] no space ，and  can not start the project  ,how to solve the problem   (Issue #48)
hi, can you tell us exactly what error you are getting?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>

Closing this for now due to lack of detail.


Demote java-xz to specs-extended

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary

Nothing actually requires xz-java to build/run. ant-junit has a build requirement only %if %{with antlr} which is disabled by default. apache-commons-compress in SPECS-EXTENDED however does still require it, so demote the package to SPECS-EXTENDED.
Change Log

Demote xz-java to SPECS-EXTENDED.

Does this affect the toolchain?

NO
Test Methodology

https://dev.azure.com/mariner-org/mariner/_build/results?buildId=543160&view=results

Why not just remove this one?
Both of apache-commons-compress and apache-commons-vfs2 require it in extended.


etcdhttp: etcdserver: request timed out, possibly due to previous leader failure

Hi,
We have a 3 node etcd cluster and seeing this error on two nodes once the cluster has formed. This is one time error and later all the etcd write work. I also tried to run a script for infinite etcd write to see if I hit this error but all the writes were successful. Could you please help me understand the reason this error occurs and write fails?

@nshubhy what version of etcd is this? can you provide the etcd server logs with the error?

@nshubhy any updates?

I am closing this due to the low activity. Reopen if you can provide more information.


Set sudomain

This allows for the subdomain to be set manually. which allows verne to be made to work with less permissions granted to the kubernetes role assigned.

Thanks for the contribution @samk-mesh!


Fails to create a rotation

Here are the logs when running with slack run:
2023-09-21 12:43:37 [info] [Wf05SYNCFQSK] (Trace=Tr05TAAZCNG5) Workflow step 'Opens a rotation form' completed
2023-09-21 12:43:38 [info] [Wf05SYNCFQSK] (Trace=Tr05TAAZCNG5) Workflow step 3 of 4 started
2023-09-21 12:43:38 [info] [Fn05TD5T5LH1] (Trace=Tr05TAAZCNG5) Function 'Create rotation' (app function) started
There was an error scheduling the trigger invalid_start_before_now undefined
2023-09-21 12:43:39 [info] [Datastore:rotations] (Trace=Tr05TAAZCNG5) Datastore get succeeded with 'id: C02ARJE6XNU'
2023-09-21 12:43:39 [error] [Fn05TD5T5LH1] (Trace=Tr05TAAZCNG5) Function 'Create rotation' (%!!(MISSING)s(<nil>) function) failed
	invalid_start_before_now
2023-09-21 12:43:40 [error] [Wf05SYNCFQSK] (Trace=Tr05TAAZCNG5) Workflow step 'Create rotation' failed
2023-09-21 12:43:40 [error] [Wf05SYNCFQSK] (Trace=Tr05TAAZCNG5) Workflow 'Manage Rotation' failed
	invalid_start_before_now
2023-09-21 12:43:41 [error] [Fn05TD8P3QQJ] (Trace=Tr05TAAZCNG5) Function 'Manage Rotation' (%!!(MISSING)s(<nil>) function) failed
	invalid_start_before_now

Seems like this error handling code is being triggered.

This error is caused when the date and/or time that's selected in the modal is before the current day/time. This could be mitigated with form validation either on change or on submit.


econnreset?

Load bots and it states "econnreset" alot of times even though i used the proxies an hour ago and they all work (200+) and then i try now and only 4 bots work???

what type of proxies? im a similar issue with socks. but http is working

sock5  i got it working an hour ago but not its broke again. I even checked the proxy and it works so idk.

ME TO


aply entitlement manifests when running on CI image

Signed-off-by: Carlos Eduardo Arango Gutierrez<EMAIL_ADDRESS>

/uncc jmencak
/cc @kpouget
/assign @kpouget

/uncc jmencak
/cc @kpouget
/assign @kpouget

hey, can you protect the oc create with [[ "${INSIDE_CI_IMAGE:-}" == "y" ]] so that it happens only in the CI ?
(and add a p to apply ;-)

hey, can you protect the oc create with [[ "${INSIDE_CI_IMAGE:-}" == "y" ]] so that it happens only in the CI ?
(and add a p to apply ;-)

with the fix above, good to merge :)

with the fix above, good to merge :)

with the fix above, good to merge :)
PTAL

with the fix above, good to merge :)
PTAL

Ready for review @kpouget

Ready for review @kpouget

With the changes suggested by @kpouget, /lgtm

With the changes suggested by @kpouget, /lgtm

/lgtm

/lgtm


Training hours

Thank you for your contributions! In estimate, how long does it take to train the network with 8 RTX 4090 GPUs?

Thank you for your interest! For the provided pretrain model, I have trained the VQVAE for about 15 hours and the Occworld for about 12 hours with 8 RTX 4090.


Refactoring of compiler (WIP)

Thanks for reviewing, I'll consider using MacroTools to improve the code.

Regarding the @VarName macro, here's a sketch of the function that I would propose to replace it with:
make_varname(expr::Symbol) = (expr, (), gensym())
function make_varname(expr::Expr)
    @assert expr.head ==  :ref "VarName: Malformed variable name $(expr)"
    return _make_varname(expr, Vector{Union{Symbol, Expr}}())..., gensym()
end
function _make_varname(expr::Expr, indices::Vector{Union{Symbol, Expr}})
    if expr.args[1] isa Symbol
        return expr.args[1], vcat(Symbol(expr.args[2]), indices)
    else
        return _make_varname(expr.args[1], vcat(Symbol(expr.args[2]), indices))
    end
end

(named make_varname to distinguish from the other varname function that we have.)
This doesn't quite work correctly, in particular the type of the second thing returned isn't quite the same as what @VarName currently returns, but it shouldn't be hard to refactor to make it return the right thing. eg. run make_varname(:(x[5][4])) and @VarName x[5][4] to see the difference.

Regarding the @VarName macro, here's a sketch of the function that I would propose to replace it with:

There are cases where a function isn't enough, and a macro is required. Consider the following case

x = 1
y = 2
a = Array(undef, 4,4)

a[x,y] ~ Normal(0,1)

Here the indexing only becomes available at runtime. So we have to generate the variable name using a macro.

@yebai I completely agree that we require a way to construct indices dynamically, but disagree that it necessitates the extra macro. I'll open a separate issue to discuss so that we can resolve this in a separate PR.

@trappmartin The compiler can be simplified a lot after removing model_f(;data=Dict()) interface (https://github.com/TuringLang/Turing.jl/issues/475):
    # Compiler design: sample(fname_compiletime(x,y), sampler)
    #   fname_compiletime(x, y; compiler=compiler) = begin
    #      ex = quote
    #          fname_runtime(vi::VarInfo, sampler::Sampler) = begin
    #              x=x, y=y
    #              # pour model definition `fbody`, e.g.
    #              x ~ Normal(0,1)
    #              y ~ Normal(x, 1)
    #          end
    #      end
    #      Main.eval(ex)
    #   end

I'm currently checking if the closures constructed by the compiler behave in the way I would expect. One surprising thing is that drawing from the prior does not produce results in the way I was hoping for.
In particular, if I ran the following code with the compiler on the master branch
@model testmodel() = begin
    x ~ Normal(0.0, 1.0)
end

f = testmodel()
@info mean(first(f().vals) for _ in 1:1_000)

I get 1.383 as a result. For the case of a discrete distribution (e.g. Bernoulli) everything seems fine.
@yebai is this intended behaviour?
Side note: The refactored compiler has the same behaviour but in fewer lines of code :P

@yebai is this intended behaviour?

I guess the answer is yes. There are some initialization tricks introduced when implementing HMC.
@xukai92  can you confirm? If so, will this behaviour break samplers like IS, SMC and PG which relies on the prior as proposals.

Yes this initialisation is done by the init function defined in https://github.com/TuringLang/Turing.jl/blob/master/src/samplers/support/init.jl.
For r.v.s from Normal, which are unconstrained, the mean should be MathConstants.e / 2.
NOTE: MathConstants.e is an arbitrary value I choose.
Also I notice https://github.com/TuringLang/Turing.jl/blob/master/src/samplers/support/init.jl#L2 and https://github.com/TuringLang/Turing.jl/blob/master/src/samplers/support/init.jl#L3 are using different constants for this purpose, which really should be the same.

@xukai92 can you confirm? If so, will this behaviour break samplers like IS, SMC and PG which relies on the prior as proposals.

This behaviour in master only triggered when assume is called with sampler being nothing. So there is no such a problem for the code in master.

@yebai is this intended behaviour?

@trappmartin Can you correct this behaviour? I think we want to sample from the prior for such an interface.

@xukai92 why do we have a separate variable _lp in model functions (performance issues?)?

Yes it's because of some performance gain we got by doing so with ReverseDiff.jl. I think should and can safely remove it because we don't use ReverseDiff.jl anymore

@trappmartin Can you correct this behaviour please? I think we want to sample from the prior for such an interface.

We also need to change the assume function for HMC samplers. Basically the thing I mentioned here: https://github.com/TuringLang/Turing.jl/issues/498#issuecomment-418927299

We also need to change the assume function for HMC samplers. Basically the thing I mentioned here: #498 (comment)

Let's solve #498 in a separate PR.

The current code breaks the ad.jl tests. I'm not sure why this is the case and I don't recall observing this before the last rebase.
ad1.jl: Error During Test at /home/travis/build/TuringLang/Turing.jl/test/utility.jl:73
  Got exception outside of a @test
  LoadError: DivideError: integer division error
  Stacktrace:
   [1] rem at ./int.jl:233 [inlined]
   [2] chunk_mode_gradient!(::Array{Float64,1}, ::getfield(Turing, Symbol("#f#84")){Turing.VarReplay.VarInfo,typeof(ad_test_model),Nothing}, ::Array{Float64,1}, ::ForwardDiff.GradientConfig{ForwardDiff.Tag{getfield(Turing, Symbol("#f#84")){Turing.VarReplay.VarInfo,typeof(ad_test_model),Nothing},Float64},Float64,0,Array{Dual{ForwardDiff.Tag{getfield(Turing, Symbol("#f#84")){Turing.VarReplay.VarInfo,typeof(ad_test_model),Nothing},Float64},Float64,0},1}}) at /home/travis/.julia/packages/ForwardDiff/hnKaN/src/gradient.jl:127
   [3] gradient!(::Array{Float64,1}, ::getfield(Turing, Symbol("#f#84")){Turing.VarReplay.VarInfo,typeof(ad_test_model),Nothing}, ::Array{Float64,1}, ::ForwardDiff.GradientConfig{ForwardDiff.Tag{getfield(Turing, Symbol("#f#84")){Turing.VarReplay.VarInfo,typeof(ad_test_model),Nothing},Float64},Float64,0,Array{Dual{ForwardDiff.Tag{getfield(Turing, Symbol("#f#84")){Turing.VarReplay.VarInfo,typeof(ad_test_model),Nothing},Float64},Float64,0},1}}) at /home/travis/.julia/packages/ForwardDiff/hnKaN/src/gradient.jl:37
   [4] gradient_forward(::Array{Float64,1}, ::Turing.VarReplay.VarInfo, ::Function, ::Nothing, ::Int64) at /home/travis/build/TuringLang/Turing.jl/src/core/ad.jl:32
   [5] gradient_forward(::Array{Float64,1}, ::Turing.VarReplay.VarInfo, ::Function) at /home/travis/build/TuringLang/Turing.jl/src/core/ad.jl:21

Does anybody have an idea why the ad tests break?
cc: @yeba @xukai92

Looks like CHUNK_SIZE isn't getting changed from zero for some reason. Just changing the initialisation for this constant to something other than zero (10?) sorts it out.
const CHUNKSIZE = Ref(10) # default chunksize used by AD

on line 51 of Turing.jl

Thanks, @yebai! The assume function calls look much better now.


feat: add ci job to push docker image

This PR creates a GH workflow to build and push the docker image to Babylon docker hub.

For new PR, the docker image will be tagged with the PR's commit hash.
For new tag, the docker image will be tagged with the tag's version.

@lesterli ok the new commit doesn't work jfyi

For new tag, the docker image will be tagged with the tag's version.

how did you test this one?

Tested it in my forked repo. After releasing with a tag, it successfully triggered the docker image build with the tag version.


fix latest release version to 2.14.11

There is a minor typo in latest release number. Actual release version is 2.14.11 but typed as 2.14.1.
As part of this PR, fixing it.

@milismsft
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@seesharprun
PRMerger will accept sign-off from the listed author only. However, if you are a Microsoft employee authorized to update this content, you can send a request to<EMAIL_ADDRESS>for this PR to be merged. Include your role and an explanation of why the PR should be merged without approval from the listed author.

Merging per email request.


Start generating internal QA checklist with assignments

Pullerbearing (@Jag96)
cc @roryabraham
Details
Adds a new Internal QA section to the Staging Deploy checklist for issues tagged "Internal QA"
Fixed Issues

$ https://github.com/Expensify/App/issues/5195
Tests

Added automated tests

QA Steps

None, we'll have to test with a deploy.

Removing HOLD!

@yuwenmemon You'll need to recompile actions and update the tests

Yeah sorry bad internet - push was hanging

LGTM, thanks @yuwenmemon. Should we hold this till next week?

It's not consumer-facing so I don't see a need to 🤷

Okay, sounds good. I'll merge as soon as tests pass.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @roryabraham in version: 1.1.14-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @AndrewGable in version: 1.1.15-15 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Update syntax based on PlantUML 1.2020.5

Update the syntax file from the "java -jar plantuml.jar -language" results.
"in at are to the and" is moved to plantumlKeyword under "gant".
The keywords added in 3f79146 and 4767a23.

Thank you for this!

Thank you!


Does not compile in 32bit

Line 105 uses File.size, this returns a ulong and is not compatible with uninitializedArray:343's assert for size_t (uint).

I wish I had a nickel for every time I wrote this bug.


Feat 62 typeorm config

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

v2.8.2
GitHub release

Your semantic-release bot :package::rocket:

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

v2.8.2
GitHub release

Your semantic-release bot :package::rocket:


U# project referencing

Added support for U# project referencing.
Algorithm:

UnrealSharpWeaver order all user assembly by U# dependencies.
Create file UnrealSharp.metadata.json with loading order

Example:
{"AssemblyLoadingOrder":["SubSubProject","SubProject2","SubProject","Core"]}

U# plugin read this info and load assembly with their metadata in correct order.

Example:

TestController:

TestComponent:

Result:

I'm not sure of the correct implementation, but in my tests everything work fine.

Really needed fix! Thank you ⭐
    private static readonly List<PluginLoadContextWrapper> LoadedPlugins
    private static readonly List<AssemblyName> SharedAssemblies
    private static readonly AssemblyLoadContext MainLoadContext

These are now unused in Main. Otherwise it looks good! :D

Really needed fix! Thank you ⭐
    private static readonly List<PluginLoadContextWrapper> LoadedPlugins
    private static readonly List<AssemblyName> SharedAssemblies
    private static readonly AssemblyLoadContext MainLoadContext

These are now unused in Main. Otherwise it looks good! :D

fixed


Modified template to reflect new repository structure, added launch v…

…ariables

[test]

This PR is connected to this one: https://github.com/redhat-developer/rh-che/pull/639
There has been a lot of conversation for this PR. These are some appreciations from the conversation I've had with @ScrewTSW:

The job changed in this PR is using a template that is based on job_template_defaults, which doesn't have the TARGET logic (running ci_cmd twice, one with the extra_target and one without), as opposed to job_template_build_defaults which has this logic.
The concern was that by looking at the actions performed by the ./.ci/cico_rhche_prcheck.sh script (as seen in https://github.com/redhat-developer/rh-che/pull/639) it was building, tagging and pushing a RHEL based image to the prod registry, but not a CentOS one.
As explained by @ScrewTSW, this is the workflow: docker base pull -> rh-che build -> docker push -> OSD deploy -> functional-tests -> report to github. Essentially this image is being used just to run the functional tests in OSD.
This means that indeed there is no reason to build the CentOS image as the tests are being executed with the RHEL based containers.
I had been tempted to add the TARGET logic to job_template_defaults, but it's true that it's not necessary, although this job remains an exception.


Remote WSL: Run active file in terminal does not work for local files

Found when verifying https://github.com/microsoft/vscode/issues/90098

open a remote wsl window on a folder
open a regular Windows file in the workspace (open FIle, show local)  (eg. C:\...\README.md)
open a terminal
run run active file in terminal
see that the path in the terminal is not converted to WSL

Marking as out of scope as disabling the command would be harmful to local terminals in remote windows and I don't think we have a context key for that

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


k8s: k8s CEP controller runs for restored endpoints

We currently have endpointmanager.Insert and AddEndpoint and they are
used in different codepaths. The controller was only started in
AddEndpoint, but should be started in the Insert case as well.
Fixes: #issue-number
How to test (optional):
I tested manually.

kubectl create -f ./examples/minikube/demo.yaml
restart cilium
cilium status --all-controllers | grep sync-to-k8s-ciliumendpoint should show one controller per endpoint

test-me-please

test-me-please


Feature request: make option to select departure branch for PR

Now mask is working only for destination branch.
I need to be notified if I have PR for merge from "test-automation/.*" branch to "develop" branch.
Thank you.

It could be done by adding ability toswitch between:
event.getPullRequest().getToRef() and
event.getPullRequest().getFromRef()

Also stumbled upon this behaviour. In the description of the PATTERN->CHANNELNAME,ANOTHERPATTERN->ANOTHERCHANNELNAME it seems that the source branch is referred to, not the target branch.
Would you accept PRs for this feature? I'd like to have this.


Mach 1: Document functionality

[x] Document composer installation
[x] Document composer functionality
[x] Document Google Drive API

see readme


ModelResolver modifier issue

Hi again IIya,
I'm totally loving this library. Making my GraphQL project super productive. Have found another issue however.
All of my model resolvers have this modification added to exclude any virtually deleted records
const defaultOptions = {
modifier: (query, args) => query.whereNull('deletedAt')
}
I.e.
export const Person = ModelResolver(PersonModel, defaultOptions)
export const Company = ModelResolver(CompanyModel, defaultOptions)
export const Office = ModelResolver(OfficeModel, defaultOptions)
Assuming a person works at a company and a company has multiple offices.
When I query the above I get a SQL error saying:
and deletedAt is null - Column 'deletedAt' in where clause is ambiguous",
Hope that's something you could take a look at.
Cheers,
Matt

Hi sorry I closed this by mistake.

Since you're building your own query filter here I don't see how the library may possibly help. The resulting SQL query that you have extended is ambiguous... so you need to take care of this.
I'd suggest to use per-model options:
export const Person = ModelResolver(PersonModel, {
  modifier: (query) => query.whereNull(ref('person.deletedAt'))
})

export const Company = ModelResolver(CompanyModel, {
  modifier: (query) => query.whereNull(ref('company.deletedAt'))
})

I realised today (after I was away from my computer) I could do what you've suggested and was just testing it this very moment.
Was about to close this and saw your comment. Thanks for that and apologies for wasting your time.


create methods for anchor upload and server initialization

Verified that make virtualenv works on my build environment
When xrdsst is invoked without any arguments, I think it should not exit successfully, but instead print brief usage message (probably to stderr, not to stdout) and exit with non-zero code. Currently it is completely quiet and exits successfully -- when e.g. constructing xrdsst calls with user arguments in scripts, this can get error-prone. Sample session:

$ xrdsst
|> xrdsst <| uns@antp450s:~/dev/niis/xrdsst-review/X-Road-Security-Server-toolkit$ echo $? # what was exit code?
0 #

make test also works in my build environment and tests pass. There is one warning, but as it comes from site-packages I would ignore this at the moment. Warning itself is

tests/test_xrdsst.py::test_xrdsst
  /home/uns/dev/niis/xrdsst-review/X-Road-Security-Server-toolkit/env/lib/python3.8/site-packages/cement/ext/ext_plugin.py:7: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
    import imp

More generic question then about init -- if I have one server already initialized and add a new configuration anchor for reinitialization (or just somehow mix up anchor location in the config when editing some other parameters)-- then what happens? Is this situation just silently ignored because the server is considered initialized by the check_init_status call? Is it possible to address such situations?

More generic question then about init -- if I have one server already initialized and add a new configuration anchor for reinitialization (or just somehow mix up anchor location in the config when editing some other parameters)-- then what happens? Is this situation just silently ignored because the server is considered initialized by the check_init_status call? Is it possible to address such situations?

In a fully automatic run I think it should not try to update the anchor if the server is initialized. In my opinion, for updating the anchor for some reason, there should be some other option, like for example running the process again with some command line argument

In a fully automatic run I think it should not try to update the anchor if the server is initialized. In my opinion, for updating the anchor for some reason, there should be some other option, like for example running the process again with some command line argument

I tend to agree. However, in described situation, if anchor is changed, either by intent or accidental typo in config file should there be some warning issued? Is that even possible, I suppose anchor contents on server and new specified anchor content should be compared to understand it these are identical.

So I had a bit of a walk around the room and this kind of seems to boil down to more general issue of config application and config validation. Let's take a case of config file with 2 security servers ss1 and ss2 defined -- first config is all correct, second has everything correct but an api-key is accidentally missing (or say, missing one GUID character)
Do we proceed with config execution for ss1 and only fail when we get to ss2 config or should we do complete config pre-validation? Here I tend to lean towards having separate pre-validation step, so that errors could be determined early. In such approach if each server configuration happens to contain the same kind of error, as unfortunately quite often happens with copy-pasting, all these errors would be reported at once, whereas on direct execution they would be reported separately after fixing the config.

On the config validation part: when logging file path is wrong, the error message we get takes almost full console screen:
Traceback (most recent call last):
  File "/home/uns/dev/niis/xrdsst-review/X-Road-Security-Server-toolkit/env/bin/xrdsst", line 11, in <module>
    load_entry_point('xrdsst', 'console_scripts', 'xrdsst')()
  File "/home/uns/dev/niis/xrdsst-review/X-Road-Security-Server-toolkit/xrdsst/main.py", line 42, in main
    app.run()
  File "/home/uns/dev/niis/xrdsst-review/X-Road-Security-Server-toolkit/env/lib/python3.8/site-packages/cement/core/foundation.py", line 916, in run
    return_val = self.controller._dispatch()
  File "/home/uns/dev/niis/xrdsst-review/X-Road-Security-Server-toolkit/env/lib/python3.8/site-packages/cement/ext/ext_argparse.py", line 808, in _dispatch
    return func()
  File "/home/uns/dev/niis/xrdsst-review/X-Road-Security-Server-toolkit/xrdsst/controllers/init.py", line 56, in init
    self.initialize_server(config_file)
  File "/home/uns/dev/niis/xrdsst-review/X-Road-Security-Server-toolkit/xrdsst/controllers/init.py", line 59, in initialize_server
    logging.basicConfig(filename=config_file["logging"][0]["file"],
  File "/usr/lib/python3.8/logging/__init__.py", line 1976, in basicConfig
    h = FileHandler(filename, mode)
  File "/usr/lib/python3.8/logging/__init__.py", line 1143, in __init__
    StreamHandler.__init__(self, self._open())
  File "/usr/lib/python3.8/logging/__init__.py", line 1172, in _open
    return open(self.baseFilename, self.mode, encoding=self.encoding)
FileNotFoundError: [Errno 2] No such file or directory: '/home/unserializable/dev/niis/xrdsst-review/logs/'

On the config validation part: when logging file path is wrong, the error message we get takes almost full console screen:
Traceback (most recent call last):
  File "/home/uns/dev/niis/xrdsst-review/X-Road-Security-Server-toolkit/env/bin/xrdsst", line 11, in <module>
    load_entry_point('xrdsst', 'console_scripts', 'xrdsst')()
  File "/home/uns/dev/niis/xrdsst-review/X-Road-Security-Server-toolkit/xrdsst/main.py", line 42, in main
    app.run()
  File "/home/uns/dev/niis/xrdsst-review/X-Road-Security-Server-toolkit/env/lib/python3.8/site-packages/cement/core/foundation.py", line 916, in run
    return_val = self.controller._dispatch()
  File "/home/uns/dev/niis/xrdsst-review/X-Road-Security-Server-toolkit/env/lib/python3.8/site-packages/cement/ext/ext_argparse.py", line 808, in _dispatch
    return func()
  File "/home/uns/dev/niis/xrdsst-review/X-Road-Security-Server-toolkit/xrdsst/controllers/init.py", line 56, in init
    self.initialize_server(config_file)
  File "/home/uns/dev/niis/xrdsst-review/X-Road-Security-Server-toolkit/xrdsst/controllers/init.py", line 59, in initialize_server
    logging.basicConfig(filename=config_file["logging"][0]["file"],
  File "/usr/lib/python3.8/logging/__init__.py", line 1976, in basicConfig
    h = FileHandler(filename, mode)
  File "/usr/lib/python3.8/logging/__init__.py", line 1143, in __init__
    StreamHandler.__init__(self, self._open())
  File "/usr/lib/python3.8/logging/__init__.py", line 1172, in _open
    return open(self.baseFilename, self.mode, encoding=self.encoding)
FileNotFoundError: [Errno 2] No such file or directory: '/home/unserializable/dev/niis/xrdsst-review/logs/'

I have no such error. It is probably due to the fact that the folder you are referring to does not exist. The folder has to exist.

On 11/11/2020 08:37, Bert Viikmäe wrote:

I have no such error. It is probably due to the fact that the folder you
are referring to does not exist. The folder has to exist.
Hey, yes the error will occur only on non-existant folder, but could
this error reporting be made shorter?

--
Taimo Peelo<EMAIL_ADDRESS>+372 53 922 704)

I noticed that make test with coverage is not working (revision 276c531bb724d311c04b7688dd435e76cecb3b15),
$ make test
python -m pytest \
	-v \
	--cov=xrdsst \
	--cov-report=term \
	--cov-report=html:coverage-report \
	tests/
ERROR: usage: __main__.py [options] [file_or_dir] [file_or_dir] [...]
__main__.py: error: unrecognized arguments: --cov=xrdsst --cov-report=term --cov-report=html:coverage-report
  inifile: None
  rootdir: /home/uns/dev/niis/xrdsst-review/X-Road-Security-Server-toolkit

make: *** [Makefile:15: test] Error 4

I noticed that make test with coverage is not working (revision 276c531),
$ make test
python -m pytest \
	-v \
	--cov=xrdsst \
	--cov-report=term \
	--cov-report=html:coverage-report \
	tests/
ERROR: usage: __main__.py [options] [file_or_dir] [file_or_dir] [...]
__main__.py: error: unrecognized arguments: --cov=xrdsst --cov-report=term --cov-report=html:coverage-report
  inifile: None
  rootdir: /home/uns/dev/niis/xrdsst-review/X-Road-Security-Server-toolkit

make: *** [Makefile:15: test] Error 4

You need to run "pip3 install pytest-cov" first and then "make test"

You need to run "pip3 install pytest-cov" first and then "make test"

Hmm, I seem to remember it working before without that step (pycov-test is listed in requirements-dev.txt). However, that was apparently when I default python of mine was at version 2 still (now it is 3), might be that this somehow made a difference.

FAILED tests/unit/test_init.py::TestInit::test_upload_anchor - FileNotFoundError: [Errno 2] No such file or directory: '/etc/xroad...
FAILED tests/unit/test_init.py::TestInit::test_upload_anchor_exception - FileNotFoundError: [Errno 2] No such file or directory: '...
============================================== 3 failed, 13 passed, 1 warning in 0.78s ==============================================
Exception ignored in: <function ApiClient.__del__ at 0x7f6430f23ee0>
Traceback (most recent call last):
  File "/home/uns/dev/niis/xrdsst-review/X-Road-Security-Server-toolkit/xrdsst/api_client/api_client.py", line 78, in __del__
    self.pool.close()
  File "/usr/lib/python3.8/multiprocessing/pool.py", line 649, in close
    self._change_notifier.put(None)
  File "/usr/lib/python3.8/multiprocessing/queues.py", line 368, in put
    self._writer.send_bytes(obj)
  File "/usr/lib/python3.8/multiprocessing/connection.py", line 200, in send_bytes
    self._send_bytes(m[offset:offset + size])
  File "/usr/lib/python3.8/multiprocessing/connection.py", line 411, in _send_bytes
    self._send(header + buf)
  File "/usr/lib/python3.8/multiprocessing/connection.py", line 368, in _send
    n = write(self._handle, buf)
OSError: [Errno 9] Bad file descriptor


Add support for modals

Usage can be seen in the new example in the example folder
Notes:

Im still looking into how to store data on TextInputs. The rest of my solution does not prevent that so I think it is outside of the scope of this PR. The ashlen and hyper solution both seem doable right now.
I know __init_subclass__ is a little strange but I think it works better than a decorator. This is because I want dataclass_transform and the methods on the Modal base class to be typed properly.

It seems like we need a Factory that's used in modals instead of TextInput. (I'm gonna shoot myself).

Proofread the docs. LGTM.


Unable to get property 'jscomp_symbol_toStringTag10' of undefined or null reference

This error is thrown here (and only in IE11, but that's also the only place the polyfill is being loaded):
o = e.getOwnPropertyDescriptor(r, "toString"), o.value = function () {
                            var e = i.call(this), t = this[Symbol.toStringTag];

Specifically, the t = this[Symbol.toStringTag];. The page is loading highcharts, which seems to be the library that is having trouble with this. This is part of a polymer project, in which this polyfill is part of the default export-

are you using 'use strict'; and naively concatenating files together, such that this highcharts function is incorrectly being ran in strict mode?

'use strict'; is at the top of the Highcharts library files so why is that a problem? I'll say this, I'm running into the same issue with webcomponentsjs in IE11 and they have 'use strict'; at the top of their webcomponents-bundle.js. Removing the 'use strict'; from their bundle fixes the issue, but I shouldn't have to be doing that, so there's something more going on here.
After some testing it looks like loading the core-js polyfills before webcomponentsjs fixes the issue since that applies their Symbol polyfill before webcomponentsjs polyfills Symbol using this polyfill. I think it's worth investigating and possibly taking some inspiration from their polyfill to help fix up this one.
@TimvdLippe you are a maintainer of webcomponentsjs and have done a commit to this polyfill, any thoughts?

@alienriver49 Sorry I am not familiar with this issue nor with the Highcharts library. If this polyfill does not work in strict mode, I think it is best to try and fix that. As far as I know, 'use strict'; is used in all modern projects now, so I would expect that we are not the only ones running into this issue.

@ljharb Yes, 'use strict'; was the issue, although I had to remove it not just from the highcharts lib, but also @TimvdLippe I had to remove it from the webcomponents-sd-ce-pf.js file as well, to get my web-component to work in IE11

@TimvdLippe most polyfills run in sloppy mode and require it; a file written in one mode must never be run in a different one. Modern build processes do not naively concatenate files; they bundle modules, and do not have this problem.

Sounds like this is answered.

No - your choice of strict mode applies only to that file. The answer is, don’t use an archaic build process.
I can assure you that zero bunglers - webpack and rollup included - put their entire file in strict mode, as that would break a ton of code. They put each module’s closure in strict mode, which is fine.

In other words, any tool that assumes everything is in strict mode is inherently broken. No note in the readme is required, because it would be true for the entire language.

That's an unfortunate default; is there any issue filed on rollup to fix that?

You can disable it:
https://rollupjs.org/guide/en#output-strict-strict-no-strict-
Op vr 2 nov. 2018 om 19:53 schreef Jordan Harband<EMAIL_ADDRESS>
:

That's an unfortunate default; is there any issue filed on rollup to fix
that?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/es-shims/get-own-property-symbols/issues/13#issuecomment-435476765,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFrDb_D0aaSPb_AouQzR0bDGtC7d67uCks5urKLTgaJpZM4W5dra
.

Apparently the Rollup maintainers arrived at a different conclusion. I personally am indifferent about it, but with recent changes to the platform like ES modules by default are strict, I don't think they made a bad choice per se. If you want to challenge their choice, I think it is best to raise an issue at https://github.com/rollup/rollup/issues


Add Awesome List + Llama Index

I would like us to add a list of Awesome Panel Chat Resources by the community. It will help users understand to understand how powerful it is and how to get started.
I would also like to add a section on Llama Index. For Llama Index I would suggest we keep the code on Llama Hub. The Llama Hub people have already agreed that the upcoming panel_chatbot pack can grow into a multipage app of examples.

small nit: it is technically *LlamaIndex but I don't think that should block

Should be fixed now.

All the openai tests fails. My guess is the OPENAI_API_KEY is no longer valid @ahuang11

Test seems unrelated. Merging. Thank you!


[Suggestion] Add minified version to /dist

I'm half thinking "Yeah this is undoubtedly necessary", and half cringing at what it says about me (i.e. laziness) that I find this necessary.
I have a project with a dozen js modules, all maintained via NPM, including moment and (to my total delight) moment-range. I use gulp to build/concat these into one file for optimized http requests. Every other module provides a .min.js version. It's really no big deal for me to add 6 lines for the convenience of automating the minification of this one file, it's just ... inelegant?

There are certainly better reasons than mine for you to offer a minified version. I just thought I'd voice in and suggest the idea, as others might find it equally useful :)
Cheers!

You might consider using webpack instead of handcrafted gulp tasks. Webpack will handle the minification of your dependencies while bundling.
Having done the same step just recently, it may take a few hours, but I feel it's worth the effort.

You're right of course, I'm using a task runner as a bundler.
Webpack has been on my must-learn-list for almost 2 years now.
Thanks for the nudge :)


How to set compress video size is less than 10mb

Hi there how to write in the code to set maximum size of video is less than 10mb in this library?

try this MediaCompressSignal


Added proposal

Signed-off-by: Krzysztof Spisak-Spisacki<EMAIL_ADDRESS>

Hopefully this PR will be less messy than previous one! :)


fix(deps): yarn upgrade + read-pkg to v5

Closes #104

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Links not working

Hi,
I am using your HBS file in my project and able to generate the test report. I am facing an issue while clicking on the API name to view the details. It is not giving details page, can you please help what I am missing here.

I tried in IE, Chrome and Firefox..same behavior

Thanks i will verify

Any update Marcos???

Yeah, I made some tests here and works perfectly,i don't understand this behavior with your tests, my template uses bootstrap framework likes default template.
Could you run your tests with default template, and if collapse test don't works there are some error with browsers.
The command to run newman with default template is:
newman run -e my.environment.json --reporters cli,html --reporter-html-export nice_report.html my.collection.json

Thanks. Do i need to install bootstrap?
On Sat, 26 May 2018, 20:16 Marcos Ellys Rocha Honorato, <
<EMAIL_ADDRESS>wrote:

Yeah, I made some tests here and works perfectly,i don't understand this
behavior with your tests, my template uses bootstrap framework likes
default template.
Could you run your tests with default template, and if collapse test don't
works there are some error with browsers.
The command to run newman with default template is:
newman run -e my.environment.json --reporters cli,html
--reporter-html-export nice_report.html my.collection.json
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MarcosEllys/newman-html-report-template-verbose/issues/2#issuecomment-392251798,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AkT4LqVvIHahoH99h7uBdJ9ixfXqNi2eks5t2SuCgaJpZM4ULjm-
.

No, bootstrap is already include in the template :)

Mate I tried running by default template and collapsible pannel worked perfectly, when I switched to yours its again broken.

Hey man, i made a few changes, do you could test now with my template?

No my friend..all links and clicks are not working.. :(..not sure what setting at my end casuing this..

Ok, well, it's a bit funny but i cannot understand this behavior, then could you to make more one test?
Please, verify if this collapse code work's well -> https://codepen.io/HelloLeeChan/pen/gaqbrq
If it works i can change my template and help you :)

Yes the collapsible panels in the link are working for me. Appreciate if u can align ur template according to this code.

Hey, any update. any reason why it is closed now?

Tonight I added the aria-expanded property, which was the only property that was not present

Do u want me to try template u have?

Finally worked mae. thank you very much for your support..


Update to Laravel 5.1

This pull request updates the laravel version from 4.0 to 5.1

Just fired it up locally. Looks good to me. I do have two remarks I'd like someone to verify:

Collapse/expand of route results doesn't work on my local install (this might be a local issue)
Also getting a Uncaught TypeError: $(...).tooltip is not a function on route:264

I don't have time to investigate this further. @pietercolpaert: If you can't reproduce those issues, feel free to merge this PR. If not, well, we'll have to make issues for them here on GitHub.

@pietercolpaert @nicoverbruggen plz wait before merge this one i noticed some missing things like favicon, apple icon. etc... I will bring this back in ASAP

@Tjoosten does the collapse/expand work for you? Works for me here...

Here it works. But that Uncaught TypeError: $(...).tooltip is not a function on route:264
needs investigation in my opinion

This is from the live version. Does this tooltip appear? I'm guessing it's this.

It doesn't appear by me @nicoverbruggen

I merged this with development now. Will open a different PR for development to stable master soon

Alright I'm making in that time further improvements.


add progress support for download function

Codecov Report

Merging #35 into master will decrease coverage by 2.28%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #35      +/-   ##
==========================================
- Coverage   97.21%   94.92%   -2.29%
==========================================
  Files           5        5
  Lines         251      256       +5
==========================================
- Hits          244      243       -1
- Misses          7       13       +6

Impacted Files
Coverage Δ

src/Downloads.jl
98.18% <100.00%> (+0.18%)
:arrow_up:

src/Curl/utils.jl
78.12% <0.00%> (-18.75%)
: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 1bef96a...1e2ebc4. Read the comment docs.

I'll merge this now and cleanup the tests later when I've merged the download and request APIs.


Permit "instances" as child of deploymentNode

The dsl for deploymentNode is as follows
deploymentNode <name> [description] [technology] [tags] [instances] {
    ...
}

With "description", "technology" and tags also permitted as children of deploymentNode element, which I personally prefer for readability.
However, the syntax forces to write all elements inline instead of as children in order to be able to specify an instance count.
What I would like to do :
deploymentNode <name> {
     description ""
     technology ""
     tags ""
     instances 42
}

This is not valid with regards to the DSL
Or
deploymentNode <name> 42 {
     description ""
     technology ""
     tags ""
}

This is valid with regards to the DSL but does not produces the expected output (showing the instance count on the deploymentNode).
See attached :

A DSL for Solution # 1 solution1.dsl.txt
A DSL for Solution # 2 solution2.dsl.txt
An expected output

I've added support for the following:
deploymentNode <name> {
     instances 42
}

Hey @simonbrowndotje !
Do you have any idea when this will be released ?
Thanks in advance !

Probably some time in July.


card.io Android Crosswalk issue

Hi,
We have installed the Card.IO Cordova SDK. However, once plugin is installed we received the following issue in our Android version:

Once we remove the plugin the following issue is disappeared.
What may be the reason for this issue?
Thanks,
Yoav

+1, any update?


Is it not possible to share a step between contexts?

https://github.com/Behat/Behat/issues/924 and https://github.com/Behat/Behat/issues/558 appear relevant, so I already have an inkling that this is not supported, but I'm not entirely sure, so I'm asking anyway.
Can I share a step like Data should be JSON in a base class (or similar approach?) between two different test classes? Currently when both those classes inherit from the same base, I get an error that the Step has been implemented multiple times.
Very terse example of what I'm trying to do:
class Test1 extends Base {
  /** @Given I do thing */
  function a() {
    $this->data = [];
  }
}
class Test2 extends Base {
  /** @Given I do thing */
  function a() {
    $this->data = (object)[];
  }
}
class Base implements Context {
  /** @Then Data should be json */
  function shouldBeJson() {
    $data = json_decode($this->data);
  }
}

Well, if you register the 2 context classes in the same suite, you cannot have the definition of the same step in both classes (be it through inheritance from a parent class or from explicit declaration in the class), as that would be ambiguous (Behat would not know which context it should use when calling the method).
if your 2 contexts are used in different suites, both are fine. Behat does not care where the methods are defined. It cares about having only one definition for each step among registered contexts.

So I switched the suites around so my two sub classes are now in separate suites:
default:
  suites:
    Hello:
      contexts:
        - HelloFeatureContext:
          - say: 'hello'
    World:
      contexts:
        - WorldFeatureContext:
          - say: 'world'

However, then I get the opposite problem instead, where Behat considers the World specific functions missing from the Hello feature, even though they are not used there.
$ cat features/Hello.feature
Feature: Test Hello

  Scenario:
    Given I say "hello"
    Then I should say hello

$ cat features/World.feature
Feature: Test world

  Scenario:
    Given I say "world"
    Then I should say world

$ cat features/bootstrap/HelloFeatureContext.php
<?php
use Behat\Behat\Context\Context;
class HelloFeatureContext extends FeatureContext {
    public function __construct($say) {
        parent::__construct($say);
    }

    /**
     * @Then I should say hello
     */
    public function iShouldSay() {
        echo "hello";
    }
}

$ cat features/bootstrap/WorldFeatureContext.php
<?php
use Behat\Behat\Context\Context;
class WorldFeatureContext extends FeatureContext {
    public function __construct($base_uri) {
        parent::__construct($base_uri);
    }

    /**
     * @Then I should say world
     */
    public function iShouldSay() {
        echo "world";
    }
}

$ cat features/bootstrap/FeatureContext.php
<?php
use Behat\Behat\Context\Context;

/**
 * Features context.
 */
class FeatureContext implements Context {
    public function __construct(array $parameters) {
        var_dump($parameters['say']);
    }

    /**
     * @Given I say :arg1
     **/
    public function iSay($arg1) {
        echo $arg1;
    }
}

The above yields:
--- HelloFeatureContext has missing steps. Define them with these snippets:

    /**
     * @Then I should say world
     */
    public function iShouldSayWorld()
    {
        throw new PendingException();
    }

--- WorldFeatureContext has missing steps. Define them with these snippets:

    /**
     * @Then I should say hello
     */
    public function iShouldSayHello()
    {
        throw new PendingException();
    }

Or you may use traits for that

you can inject contexts in each other

Well, you would need to configure the proper filters so that each suite only loads the feature files corresponding to it. With your config, you will load all your features files for both suites, which of course will complain about missing step definitions.

Thanks, for the feedback, I'll have another go at this with the added information. :)


Infrequent flake in golang_integration_test

This doesnt seem to happen very often but its persisting
Ive mentioned it a few times on the golang slack channel but raising here as i think we need to look further
example fail:
[2023-09-07 17:22:55.282][120290][critical][golang] [contrib/golang/common/log/cgo.cc:27] log test
[2023-09-07 17:22:55.282][120290][error][golang] [contrib/golang/common/log/cgo.cc:24] log test false
[2023-09-07 17:22:55.282][120290][critical][golang] [contrib/golang/common/log/cgo.cc:27] log test false
[2023-09-07 17:23:05.285][119877][critical][assert] [test/integration/http_integration.cc:550] assert failure: 0. Details: Timed out waiting for new connection.
[2023-09-07 17:23:05.285][119877][critical][backtrace] [./source/server/backtrace.h:104] Caught Aborted, suspect faulting address 0x3e90001d445
[2023-09-07 17:23:05.285][119877][critical][backtrace] [./source/server/backtrace.h:91] Backtrace (use tools/stack_decode.py to get line numbers):
[2023-09-07 17:23:05.285][119877][critical][backtrace] [./source/server/backtrace.h:92] Envoy version: 0/1.28.0-dev/test/RELEASE/BoringSSL
[2023-09-07 17:23:05.286][119877][critical][backtrace] [./source/server/backtrace.h:96] #0: __kernel_rt_sigreturn [0xffffb63088dc]
[2023-09-07 17:23:05.286][119877][critical][backtrace] [./source/server/backtrace.h:96] #1: abort [0xffffb607daac]
[2023-09-07 17:23:05.313][119877][critical][backtrace] [./source/server/backtrace.h:96] #2: Envoy::HttpIntegrationTest::waitForNextUpstreamConnection() [0x2ad7d6c]
[2023-09-07 17:23:05.361][119877][critical][backtrace] [./source/server/backtrace.h:96] #3: Envoy::HttpIntegrationTest::waitForNextUpstreamRequest() [0x2ad74bc]
[2023-09-07 17:23:05.392][119877][critical][backtrace] [./source/server/backtrace.h:96] #4: Envoy::HttpIntegrationTest::waitForNextUpstreamRequest() [0x2ad7fd4]
[2023-09-07 17:23:05.413][119877][critical][backtrace] [./source/server/backtrace.h:96] #5: Envoy::GolangIntegrationTest::testDynamicMetadata() [0x13bdbfc]
[2023-09-07 17:23:05.434][119877][critical][backtrace] [./source/server/backtrace.h:96] #6: Envoy::GolangIntegrationTest_DynamicMetadata_Async_Sleep_Test::TestBody() [0x13be640]
[2023-09-07 17:23:05.454][119877][critical][backtrace] [./source/server/backtrace.h:96] #7: testing::internal::HandleExceptionsInMethodIfSupported<>() [0x3c32420]
[2023-09-07 17:23:05.475][119877][critical][backtrace] [./source/server/backtrace.h:96] #8: testing::Test::Run() [0x3c322c0]
[2023-09-07 17:23:05.496][119877][critical][backtrace] [./source/server/backtrace.h:96] #9: testing::TestInfo::Run() [0x3c33410]
[2023-09-07 17:23:05.516][119877][critical][backtrace] [./source/server/backtrace.h:96] #10: testing::TestSuite::Run() [0x3c3417c]
[2023-09-07 17:23:05.537][119877][critical][backtrace] [./source/server/backtrace.h:96] #11: testing::internal::UnitTestImpl::RunAllTests() [0x3c41684]
[2023-09-07 17:23:05.557][119877][critical][backtrace] [./source/server/backtrace.h:96] #12: testing::internal::HandleExceptionsInMethodIfSupported<>() [0x3c41138]
[2023-09-07 17:23:05.578][119877][critical][backtrace] [./source/server/backtrace.h:96] #13: testing::UnitTest::Run() [0x3c40f94]
[2023-09-07 17:23:05.598][119877][critical][backtrace] [./source/server/backtrace.h:96] #14: Envoy::TestRunner::RunTests() [0x35c054c]
[2023-09-07 17:23:05.619][119877][critical][backtrace] [./source/server/backtrace.h:96] #15: main [0x35bf0b4]
[2023-09-07 17:23:05.619][119877][critical][backtrace] [./source/server/backtrace.h:96] #16: __libc_start_main [0xffffb607de10]
================================================================================
FAIL: //contrib/golang/filters/http/test:golang_integration_test (see /build/bazel_root/base/execroot/envoy/bazel-out/aarch64-opt/testlogs/contrib/golang/filters/http/test/golang_integration_test/test.log)
INFO: From Testing //contrib/golang/filters/http/test:golang_integration_test:
INFO: Elapsed time: 2725.781s, Critical Path: 553.54s
INFO: 34540 processes: 15507 remote cache hit, 12759 internal, 1 local, 6273 processwrapper-sandbox.
//contrib/golang/filters/http/test:golang_integration_test               FAILED in 21.9s

https://dev.azure.com/cncf/envoy/_build/results?buildId=148510&view=logs&j=767be981-567e-57d8-68c3-2140ede0a0bd&t=8a34f9ed-4946-5fcf-7cd6-99c93070884d&l=1473

cc @doujiang24

Okay, I'll look further and keep an eye on it, thanks~

Still happening (link)


WIP: PullRequestResource

This is not ready for review! It is meant to accompany #778 as a draft/POC and this design doc.

v exciting @dlorenc ! could you include in this somewhere (e.g. PR description and/or comments in pullrequest-init/main.go) a brief description of what the interface is here? e.g. what files will be provided via the download, and what functionality is available for upload?

cc @rawlingsj @ccojocar @pmuir - would be interested to hear your thoughts from a JX perspective.

Closing this one in favor of #895


Branding Patch API

Currently the Branding Patch does not have an API, meaning mod developers cannot programmatically change the version and game branding, and the patch is taken solely from the launch arguments (which Fabric/Quilt Loader adds).

How would we deal with multiple mods requesting a branding change? will there be a priority system or similar?

We'll have to come up with a solution for that yeah. I imagine a priority system would be relatively straightforward, but we could even have more complex collision handling, where multiple messages are added after one another.


Enhance CI, add license and readme, and fix some issues

This fixes #52
Note the UBSAN job is expected to fail, it needs to be investigated and resolved.  I added symbol visibility to the exceptions but that didn't make a difference (it should be there anyway).
Since you do not have Travis CI or AppVeyor enabled on this repository, here are the build results:
AppVeyor: https://ci.appveyor.com/project/jeking3/algorithm/builds/20008102
Travis CI: https://travis-ci.org/jeking3/algorithm/builds/449921988

@mclow a few things to do here:

Enable Travis CI builds on boostorg/algorithm
Enable AppVeyor builds on boostorg/algorithm
Analyze the UBSAN in the travis result link in the description.  It's a bad vtable in a dtor.

As admin for this repo you must do items 1 and 2 to enable PRs and merges into develop and master to run a build.

Wow did you pay for travis-ci.com?

This was passing on my fork...
https://github.com/jeking3/algorithm/pull/2

What's the status on this? I think that landing a change along these lines would help me a lot, as I could offload most of my b2 permutations to CI.


chapter4.txt is not a data file

Seems a code script is uploaded by mistake. Please check.

Hi @hzhu6666
Thanks for the update. File deleted.
Regards


The number of examples in the out-of-domain dev set are not accurate

For example:
DROP: 1557 vs 1,503
DuoRC.ParaphraseRC: 1648 vs 1,501

Hi,
How are you counting?
If you count using this script you should get the right numbers.
from __future__ import absolute_import
from __future__ import division
from __future__ import print_function

import sys
import json
import gzip

examples = 0
fname = sys.argv[1]

with gzip.open(fname, 'rb') as f:
    for i, line in enumerate(f):
        obj = json.loads(line)

        if i == 0 and 'header' in obj:
            continue

        examples += len(obj['qas'])

print('Num examples: %d' % examples)


Check event subscriber

Check registered event subscribers (correct callback referenced etc.).

Corresponding documentation: http://symfony.com/doc/current/components/event_dispatcher/introduction.html#event-dispatcher-using-event-subscribers


Automatically installs beta version of php-cs-fixer 3

Describe the bug

Three hours ago, v3.0.0-beta.1 of php-cs-fixer was released. If no explicit version is pinned in the Setup PHP action config, Setup PHP chooses this release over the stable version.
Version

[x] I have checked releases, and the bug exists in the latest patch version of v1 or v2.
[x] v2
[ ] v1

Runners

[x] GitHub Hosted
[ ] Self Hosted

Operating systems

Ubuntu Latest (20.04.2)
PHP versions

7.3, 7.4, 8.0
To Reproduce

      - name: Setup PHP environment
        uses: shivammathur/setup-php@v2
        with:
          php-version: ${{ env.php }}
          coverage: none
          tools: php-cs-fixer

Expected behavior

The latest stable version of php-cs-fixer v2 should be installed.
Screenshots/Logs

Additional context

Are you willing to submit a PR?

I believe this is a bug in php-cs-fixer, so I have opened an issue in their repo as well: https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/5558
I think we should keep this issue open for better visibility of the problem until it is fixed by the php-cs-fixer team.

Until the releases is marked correctly, to install the last stable version, you can specify the exact version in tools input.
- name: Setup PHP
  uses: shivammathur/setup-php@v2
  with:
    php-version: 8.0
    tools: php-cs-fixer:2.18.4

Test workflow: https://github.com/shivammathur/test-setup-php/actions/runs/672028723/workflow

Three hours ago, v3.0.0-beta.1 of php-cs-fixer was released. If no explicit version is pinned in the Setup PHP action config, Setup PHP chooses this release over the stable version.

3.0.0-beta by definition is a not stable. please, consider adding a "-beta" suffix (-alpha, -rc etc) to you the logic.


allow tests to run without xnd or ndtypes installed

These small changes allow the test suite to be run without xnd or ndtypes installed. (It looks like that was already the intention for xnd, but then there were statements like backend == XndBackend in some test cases that would fail if it was not present.)

This issue has cropped up a few times now -- Would it be possible to add a CI entry for this?

Should the contents of xnd_backend.py also be in a try/except as done for cupy_backend.py?
Not for this PR, but I think it would be worth making pytorch optional as well since that is quite a large dependency.

This issue has cropped up a few times now -- Would it be possible to add a CI entry for this?

I have not used Azure previously. It looks like I could just copy the Tests entry of azure_pipelines.yml to something like TestsNoXnd and then either add a line to that case to uninstall ndarray/xnd or make a separate .conda/environment.yml that does not install it in the first place. Is that what you were thinking?

Yes, something along those lines.

It seems MyPy is failing. Could you add a small type hint?

The try/except in 9b4657d was also necessary (otherwise there is a failure to import ndtypes while collecting the tests)
It looks like the behavior is as expected on Azure (more skipped cases showing up in TestsMinimalEnv)

Thanks @grlee77!


BLD: Update to Cython 0.29.33

Reference issue
Pre-requisite for https://github.com/scipy/scipy/pull/18153.
What does this implement/fix?
Reason: Cython 0.29.33 brings support for const-qualified memoryviews (see https://github.com/cython/cython/issues/1772).
Additional information
Downstream projects (like scikit-learn) already have adopted Cython 0.29.33 for the support of this fix since it allows enhanced safety.

Nah that's just the Cython beta for 3.0, which is a bigger can of worms. We have an issue open for it.

There are no new CI failures, I just checked.
I squash-merged b/c of the empty CI re-retrigger commit

Also, can you let us know if the downstream issues merit backporting in your opinion? We can label this and the read-only view PR appropriately then

Backporting both would be useful for scikit-learn.

Thank you for asking.
Backporting both PRs would be useful for scikit-learn. 🙂


Write A SQL query example of Count of people that reach the IRB page by Department

Write A SQL query example of Count of people that reach the IRB page by Department

SELECT dept.name, count(proj.id) AS Projects
FROM approver_project as proj
JOIN approver_person as pers
ON pers.id = proj.owner_id
LEFT JOIN approver_clinicaldepartment AS dept
ON pers.department_select_id=dept.id
WHERE proj.reached_irb_page_count > 0
GROUP BY dept.id


Improvement of Oxygen in Purifier

from what i have read so far now every item use a specifiac amount of oxygen to get processed
that way you get with higher tiers and upgrades in machines an exponential rise of needed oxygen per items processed.
i think the last days at work alot about that fact and try to find another way to make it "oxygen efficient" in higher tiers and with upgrades.
my idea bases on a oxygen consumption over time in a machine with higher values for higher tiers of machines and also an improvement for the seperators in diffrent tiers.
but step by step
what if an purification chamber (PC) tier 1 uses every second maybe 100 oxygen,
a tier 2 PC 300 oxygen per second, tier 3 PC 500 oxygen and last tier 4 700 oxygen?
when you upgrade the machines with speed upgrades the oxygen comsumption rate will be the same, which makes it more efficient for the items.
also i am meaning an extra slot for flint and energy upgrade in tier 3 and 4 is nedless and that way you can input in tier 4 an 8's slot for processing ores.
why doing so, well if you advance that far you should have enough recources that you didn't need the slots and if you need them, well than you have yourself overestimated.
another improvement is a introduction of tier 1, 2 and 3 of the seperator
which produce more oxygen per time and use more water to do so.
i come up with some numbers based on the PC values from above.
a tier 1 seperator produce 50 oxygen per second, tier 2 120 oxygen per second and tier 3 250 oxygen per second.
the values for hydrogen are double the values of oxygen, because of the H2O
and water used value is three times the oxygen value.
tier 1 uses 150 mb of water per second and produce 50 oxygen and 100 hydrogen
tier 2 uses 360 mb of water per second and produce 120 oxygen and 240 hydrogen
tier 3 uses 750 mb of water per second and produce 250 oxygen and 500 hydrogen.
all in all to run a tier 4 PC u need without the changes i mention above 3 tier 3 seperators to produce the needed oxygen with and extra 50 oxygen per second, with the changes you need 4 and produce enough oxygen to have 200 oxygen income per second which makes it in some way energy saving under the line.
at the end let me say you are free to comment and discuss and let me say with that changes it will be a way more easier to have tier 3 and higher.
english is not my motherlanguage so any mistakes inside this text are owned by the founder ;-)

Thanks for the suggestions!  I like the ideas, but to be honest, it seems like a big hassle all in order to just  have better upgrade support - I don't want to have to deal with different tiers of each Mekanism machine!