Is there any way to capture code block content?

Hi, is there any way to capture content of code blocks? I was able to get block start/end but on the middle is pure text which I'd like to capture as "CodeContent" for future parsing.
let text = "This is Peter on ![holiday in Greece](pearl_beach.jpg).\n```rust\nuse pulldown_cmark::*```";

Parser::new_ext(text, Options::empty())
        .map(|event| match event {
            | Event::Start(Tag::CodeBlock(CodeBlockKind::Fenced(ref syntax))) | Event::End(Tag::CodeBlock(CodeBlockKind::Fenced(ref syntax))) => {
                log::debug!("{:?}", syntax.as_ref());

                event
            },
            | Event::Text(ref text) => {
                log::info!("code {:?}", text);

                event
            },
            | _ => event,
        })

If I have understood you correctly, one way to do this would be to use a custom iterator which tracks whether the iterator is currently inside a codeblock or not. When you'd encounter a codeblock start, you then accumulate all subsequent text events into a buffer (read: a String) and then when you'd find a codeblock end, you could emit that buffer as a CodeContent event.

If code is not closed by ending marks I'd like to skip this event but it seems that parser is taking whole input text after and then the last event is end tag🤔 I'm curious if wouldn't it be nice to hide this behind pulldown_cmark abstraction, but I can try to do my best and figure out how to implement it.

string buffer with additional flag is working but I want to cry when I see my implementation, but it works
struct CodeBlock {
    text: String,
    is_started: bool,
}

impl CodeBlock{
    fn new() -> Self {
      Self{is_started: false, text: String::new()}
    }

    fn start(&mut self) {
        self.is_started = true;
    }

    fn finish(&mut self) {
        self.is_started = false;
        self.text.clear();
    }

    fn insert(&mut self, line: &str) {
        if self.is_started {
            self.text.push_str(line);
            self.text.push_str("\n");
        }
    }
}

fn parser<'markdown_txt> (markdown_txt: &'markdown_txt str)
  -> impl 'markdown_txt + Iterator<Item = Event<'markdown_txt>>
{
    let mut code_block = CodeBlock::new();

    Parser::new_ext(markdown_txt, Options::empty())
        .map(move |event| match event {
            | Event::Start(Tag::CodeBlock(CodeBlockKind::Fenced(ref syntax))) => {
                code_block.start();

                event
            },
            | Event::End(Tag::CodeBlock(CodeBlockKind::Fenced(ref syntax))) => {
                log::debug!("{} {:?}", syntax, code_block.text);

                code_block.finish();

                event
            },
            | Event::Text(ref text) => {
                code_block.insert(text);

                log::info!("text {:?}", text);

                event
            },
            | _ => event,
        })
    ```

string buffer with additional flag is working but I want to cry when I see my implementation, but it works
struct CodeBlock {
    text: String,
    is_started: bool,
}

impl CodeBlock{
    fn new() -> Self {
      Self{is_started: false, text: String::new()}
    }

    fn start(&mut self) {
        self.is_started = true;
    }

    fn finish(&mut self) {
        self.is_started = false;
        self.text.clear();
    }

    fn insert(&mut self, line: &str) {
        if self.is_started {
            self.text.push_str(line);
            self.text.push_str("\n");
        }
    }
}

fn parser<'text> (text: &'text str)
  -> impl 'text + Iterator<Item = Event<'text>>
{
    let mut code_block = CodeBlock::new();

    Parser::new_ext(text, Options::empty())
        .map(move |event| match event {
            | Event::Start(Tag::CodeBlock(CodeBlockKind::Fenced(ref syntax))) => {
                code_block.start();

                event
            },
            | Event::End(Tag::CodeBlock(CodeBlockKind::Fenced(ref syntax))) => {
                log::debug!("{} {:?}", syntax, code_block.text);

                code_block.finish();

                event
            },
            | Event::Text(ref text) => {
                code_block.insert(text);

                log::info!("text {:?}", text);

                event
            },
            | _ => event,
        })

I found nice implementation in source code that it's possible to write custom iterator for events
impl<'a> Iterator for Parser<'a> {
    type Item = Event<'a>;

    fn next(&mut self) -> Option<Event<'a>> {
        match self.tree.cur() {
            None => {
                let ix = self.tree.pop()?;
                let tag = item_to_tag(&self.tree[ix].item, &self.allocs);
                self.tree.next_sibling(ix);
                Some(Event::End(tag))
            }
            Some(cur_ix) => {
                if self.tree[cur_ix].item.body.is_inline() {
                    self.handle_inline();
                }

                let node = self.tree[cur_ix];
                let item = node.item;
                let event = item_to_event(item, self.text, &self.allocs);
                if let Event::Start(..) = event {
                    self.tree.push();
                } else {
                    self.tree.next_sibling(cur_ix);
                }
                Some(event)
            }
        }
    }
}

how can I wrap this events to match interested events only and store code block in string buffer and release custom Event, I'd need experienced mentor 🙏

@marcusklaas could you lead me how to accumulate it? I've tried to implement it but I've stuck and I'm not proud of my code

@bartekupartek not sure I understand your question entirely but it sounds like you're trying to handle code blocks as a single event instead of start/text/end event. I am doing something similar. Maybe this code helps: https://github.com/mitsuhiko/struckdown/blob/bca1847550b0453c8e3dc0755a5958b8a245f29d/struckdown/src/parser.rs#L186-L226

Since this looks to solved outside of the pulldown library itself, I am closing this issue. Please feel free reopen it if any new issues pop up.

Since this looks to solved outside of the pulldown library itself, I am closing this issue. Please feel free reopen it if any new issues pop up.

It took me long time to learn all things on the way, it turned out that read_raw function from struckdown was everything I needed to collect code block form iterator and skip other events. Thank you for patience and assistance!

It took me long time to learn all things on the way, it turned out that read_raw function from struckdown was everything I needed to collect code block form iterator and skip other events. Thank you for patience and assistance!


[PyAMQP] Connections TODO

This PR tries to address 2 TODOs for Connection

_incoming_open :  if a connection flow during Open receives an illegal state, how do we handle. Today uamqp & pyamqp both ignore it.  Right now I've set it that if any other state appears while opening, close. Looking at some other libraries and the amqp specs, there doesnt seem to be any defined thing that should happen if the Open process goes off path, so it might be open to the implementer ?
_incoming_close: How to handle a close frame on an invalid channel. I moved the todos around popping the channels on both incoming and outgoing since the spec mentions either party can close and then they mutually close. If the channel specified is not found, then is it an log and move on or close the entire thing with an error. Ive chosen the latter now

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-eventhub

/azp run python - eventhub - tests

/azp run python - eventhub - tests


Improve individual page footer spacing for readability

Especially when there is short content, the footer information (edit and last modified) is quite close to the content and spacing/layout could be improved to make easier to read.
This may be because we're using the red link style for now but flagging this for a future review/improvement.

I agree a bit more bottom padding would help separate the github links from the main content

I've added some padding that I think improves readability if there are more changes reopen and we can review.


[typescript] Opt out of suffix for enum value keys

Is your feature request related to a problem? Please describe.
It's a bit odd that suffixes are applied to enum values in addition to the enum itself (when using typesSuffix):
export enum RoleSuffix {
  UserSuffix = 'USER',
  AdminSuffix = 'ADMIN'
}

Normally the suffix is useful to disambiguate the overall type when importing and using it in files, but there is not much benefit to having a suffix on the values themselves in most cases (UserSuffix, for example).
Describe the solution you'd like
Add a flag to opt out of this behavior. suffixEnumValues true/false

This issue bugs us as well and I can contribute an enhancement for it. I checked the code and it seems that the useTypesPrefix is ignored for enum values.
I see 2 options to implement this and keeping it consistent:

Just ignore the suffix for enum values. This would be a breaking change.
Add suffixEnumValues and prefixEnumValues options with defaults matching the current behaviour.

Personally, I am fine with both approaches. I would prefer Option 1 if breaking a bit the generated code is OK. I don't think anyone would want to add suffix or prefix to their enum values. And I would lean on simpler configuration until there is an actual need for that.
Which approach do you think makes more sense?
/cc @n1ru4l

Following this PR: https://github.com/dotansimha/graphql-code-generator/pull/1553
Maybe, it is really Option 1 that I should go with...


backticks are still treated as special inside of opaque blocks

That is, the following:

  let result = `foo${bar}`;

...results in a pre containing let result = foo${bar};, rather than the intended backticks for a template literal.
Other Markdown shorthands are not parsed inside of an opaque element, but backticks are done in a special early phase that doesn't look for opaque elements.
Showed up in the wild in https://github.com/w3c/permissions/pull/149

this also applies to ``` blocks, not just


Adding .toContainKey to matchers

What
Adds .toContainKey to matchers, and closes #11 in the process.
Housekeeping

[x] Unit tests
[x] Documentation is up to date
[x] No additional lint warnings
[x] Add yourself to contributors list (yarn contributor)

NB: I didn't think to make a branch when I opened #61, so this is a bit of a mess. Apologies in advance!

Codecov Report

Merging #63 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #63   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           8     10    +2
  Lines          40     49    +9
  Branches        5      7    +2
=====================================
+ Hits           40     49    +9

Impacted Files
Coverage Δ

src/matchers/toContainKey/index.js
100% <100%> (ø)

src/matchers/toContainKey/predicate.js
100% <100%> (ø)

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 0803d80...e1e34bc. Read the comment docs.

Thanks @andrewhayward!


npm support

Please create package.json and publish your library on npm
Thanks

Bower is now deprecated

There seem to be a node module available for this:
https://www.npmjs.com/package/unitegallery
but it doesn't seem maintained by original owner in here and it is not up to date (currently 1.7.28 where local repository is 1.7.40)


Add e2e test for authorization proxy server installation

Description
Add e2e test for CSM Operator Supports Install of Authorization Proxy Server.
GitHub Issues
List the GitHub issues impacted by this PR:

GitHub Issue #

#https://github.com/dell/csm/issues/511

Checklist:

[x] I have performed a self-review of my own code to ensure there are no formatting, vetting, linting, or security issues
[x] I have verified that new and existing unit tests pass locally with my changes
[x] I have not allowed coverage numbers to degenerate
[x] I have maintained at least 90% code coverage
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have maintained backward compatibility

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Are these added as part of nightly tests? Also: Can we use the auth proxy server deployed in this test to work with the tests that deploy auth sidecar?

For now I am testing manually, I haven't look in nightly job yet. I am new to operator world, not sure we do multiple deployment in single scenario, I am looking into that

LGTM would be a good idea to add this to nightly tests

Jenkins and enabling multiple resources apply need some more works, we take that as beyond FC

Will you be adding steps in the /tests/README.md for how to execute the test?

Will you be adding steps in the /tests/README.md for how to execute the test?

Yes


Adding Communications & Political Science programs

That's a lot of contributions! Thank you very much!


Broken Link in README

In the README.md, under the heading "Logging into Django with Twitter", the link to http://apiwiki.twitter.com/Sign-in-with-Twitter returns a "Page Not Found."

Fixed. Thanks for the report!


WIP: Separate RE matching of issuer/subject from strict

Signed-off-by: Ville Aikas<EMAIL_ADDRESS>Summary
Add two new fields issuerRE and subjectRE so that if the user wants RE matching of issuer/subject, it's crystal clear
that RE is being used. issuer / subject are now strict matches only.
Still WIP since I want to add more test coverage.
Ticket Link
Fixes #1871
Release Note

CIP issuer/subject are now strict matches. Add two new fields issuerRE and subjectRE that will then use RE for matching.

Codecov Report

Merging #1956 (fe4524c) into main (2b4d69b) will increase coverage by 0.01%.
The diff coverage is 81.81%.

@@            Coverage Diff             @@
##             main    #1956      +/-   ##
==========================================
+ Coverage   34.71%   34.72%   +0.01%
==========================================
  Files         153      153
  Lines       10037    10045       +8
==========================================
+ Hits         3484     3488       +4
- Misses       6166     6169       +3
- Partials      387      388       +1

Impacted Files
Coverage Δ

...g/apis/policy/v1alpha1/clusterimagepolicy_types.go
0.00% <ø> (ø)

...kg/apis/policy/v1beta1/clusterimagepolicy_types.go
0.00% <ø> (ø)

pkg/cosign/kubernetes/webhook/validation.go
74.00% <0.00%> (ø)

...s/policy/v1alpha1/clusterimagepolicy_validation.go
92.48% <66.66%> (-0.58%)
:arrow_down:

...is/policy/v1beta1/clusterimagepolicy_validation.go
93.06% <66.66%> (ø)

pkg/cosign/verify.go
33.58% <100.00%> (+0.80%)
:arrow_up:

pkg/cosign/tuf/client.go
61.98% <0.00%> (-0.83%)
: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 2b4d69b...fe4524c. Read the comment docs.


[FEAT] In-game Scoreboard/Leaderboard

Types of Changes

[ ] Bug fix (non-breaking change that fixes an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Description

Closes #127, adds an in-game scoreboard on the top right hand corner of the screen which can be configured to either display both the user's score, and whether they have guessed, just guess status, or disable it completely on the game settings screen.
On mobile a little button is added next to the game duration which opens up a dialog to view the leaderboard.
How Has This Been Tested?

All tests pass, and is currently deployed on my instance along with my other changes from PR #572
Screenshots (if appropriate):

Works very well, should merge this

Hello,
Really sorry... totally forgot to check the pr. Code seems good for me. :)
I have to same UX suggestion:

When I play in "Single player", I don't we need to see checkbox "Display scoreboard".

Maybe put scoreboard in the front when round result are print.

I've hidden the leaderboard options in singleplayer, and additionally moved the leaderboard when the full screen map appears at the end of the round, I think this looks better than just increasing the z-index since it would overlap the edges of the map.

Looks pretty good

@all-contributors please add @Troplo for code
@all-contributors please add @ElectricS01 for review


Apply matplotlib rc parameters correctly throughout

I've long struggled with the correct way to apply rcparams in matplotlib, I now think a decorator which is applied during axis/figure creation, for all initialize_plot and update_frame calls and during rendering is the best approach.
Fixes https://github.com/ioam/holoviews/issues/1222

Ready for review.

Seems like a sensible approach and I am happy with it as long as it works (preferably better than before).
My only comment is that I think mpl_context should be called mpl_rc_context to be explicit.

I suppose my only other comment is that it might be nice to test - if it is easy enough to set up such tests.

Ready now, pretty sure the coverage report is false, when I click through to it, it doesn't actually tell me which files now have reduced coverage.

Ready now, pretty sure the coverage report is false

Yeah, a -1.4% coverage change is surprising.
Anyway, looks good and I'll now merge.


Validate the kubebuilder annotations to make sure it is generating a valid OpenAPI structure.

What would you like to be added:
Need to find a way to generated and validate the CSV with the kubebuilder annotations to make sure that the generated CSV is compliance with the OpenAPI required by Kubernetes.
One option to validate would be using something like:
kustomize build config/crd | kubectl apply -f -

Why is this needed:

That means our CI needs to instantiate either KIND or Minikube, right?

probably, idk yet.
there must be another way.


update link to solid integration

We don't endorse the use of lightning-tv usage nor want to have references to it at thispoint, and SolidJS developed has halted on lightningjs. In fact we should remove the reference all together for clarity. Can you remove it @jfboeve ?


[Feature Request]: Limit to set the tag for list.

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
As you can see in the attached screenshot. If there is many tag associate with one tag it's cause of destructure the card design in user end. It's styling was broken.
And I think there should be no more than 4 tag was needed for one list.
Use Case

So I modify the tags display for each card. I display the tags Icon same to same as present in the filter options along with this website red color. Which looks more beauitifull and doesn't affect it's style.
Also I set the backend logic to limit this tag association of maximum 5 tag for one list in every possible input section like in -- new list create form, edit list form, also in admin dashboard

Benefits
No response
Add ScreenShots

@Soujanya2004   Assign it to me under label-3 because there is front end work needed along with backend logic in three different  position 1. new list create form  2. edit list form  3. also in admin dashboard
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@Suvadip-sana make it limited to 3

@Suvadip-sana make it limited to 3

Okkk


Data

Resolves kuanb#8.

Summary of Findings
Lessons Learned:
It is important to remove duplicate records from the comprehensive dataset - doing so reduces table size from 7M to 800K, makes query speed more tolerable, and decreases possibilities for error.
The data is dirty enough to introduce questions and confusions about the ideal schema.

In many instances, although only 0.7% of the total, defendant names on the same citation are spelled in slightly different ways.
In many instances, although only 0.2% of the total, locations on the same citation are spelled in slightly different ways.
In many instances, although only 1.1% of the total, payable statuses on the same citation are different.
In many instances, although only 0.3% of the total, violation codes on the same citation are the different.

Additional data integrity concerns include:

appointments for the same defendant and citation are scheduled at the same time but in different rooms (maybe this is due to schedule updates?)
a handful (0.28%) of violation codes have duplicative alternate descriptions
7.8% of violation descriptions have duplicative alternate codes
defendant names lack person identifiers
citations lack citation dates and times
citation locations lack lat/long
although it is assumed all hearings are held in the same building, hearings lack building address information
hearings/appointments lack unique identifiers

Schema Decisions
Relationships
One Citation has and belongs to many Hearing.
Once Citation has and belongs to many ViolationCode. Although an overwhelming majority of citations only have one violation code, this decision is based on information contained in http://ditweb.atlantaga.gov/mcw/, where it is common for the same citation id to have many violations.

Attributes
Citation

guid
location(s) ** going to overwrite duplicates with the latest value
payable(s) ** going to overwrite duplicates with the latest value
defendant(s) ** going to overwrite duplicates with the latest value

Hearing

date
time
room ** going to overwrite duplicates with the latest value by updating the hearing identifier on the CitationHearing join table

ViolationCode

code
description

closing without merge. has been implemented by #10


How can I build AAR-ANCE index?

when I run index_builder.py，I got an error
ValueError: You have to specify either decoder_input_ids or decoder_inputs_embeds
I guess it may due to ANCE's T5 based(encoder-decoder), and I don't find where decoder is in index_builder.py.
So I wonder how I can solve this question, thanks!

Sorry, there is a bug when determining the model type in multi gpu setting, which may result in inability to properly recognize T5-based models.
We have fixed it, you can try it again.
Note: For ANCE, you should set pooling_method to cls.


Is there an ActivitySource or DiagnosticSource that can be listened to?

We are setting up distributed tracing across multiple applications, some of which are Azure Functions worker applications (the dotnet-isolated runtime v3 and targeting .NET 5). We do not use Application Insights. What, if any, diagnostic source should we listen to in order for the runtime to start and stop an activity for each function invocation?
For context, here's how one could listen to the activity start and stop diagnostics in an ASP.NET Core application. In practice we use the OpenTelemetry library to do this, which uses a more standards-compliant ActivityListener. This code snippet is just to illustrate how one would discover the name of any available diagnostic sources and the names of their diagnostics:
DiagnosticListener.AllListeners.Subscribe(listener =>
{
    if (listener.Name == "Microsoft.AspNetCore")
    {
        listener.Subscribe(diagnostic =>
        {
            if (diagnostic.Key == "Microsoft.AspNetCore.Hosting.HttpRequestIn.Start")
            {
                // ...
            }
            else if (diagnostic.Key == "Microsoft.AspNetCore.Hosting.HttpRequestIn.Stop")
            {
                // ...
            }
        });
    }
});

What is the listener name and what are the diagnostic names we should use in an Azure Functions worker app?
Edit: it seems that DiagnosticListener.AllListeners remains empty, so the Azure Functions worker runtime does not have any, is that correct?
Edit: adding a listener to ActivitySource.AddActivityListener(ActivityListener) does not result in any callbacks to the listener, so it seems the Azure Functions worker runtime also does not have any activity sources.

I have found that there are several OpenTelemetry contribution packages for .NET available in the opentelemetry-dotnet-contrib repository here on GitHub, including one for AWS Lambda. Will Microsoft publish a similar contribution there, or will OpenTelemetry support be part of a future runtime release?

@michielvoo there is work currently in progress for host instrumentation to do exactly what you're requesting. We'll also be tracking worker specific events you can listen to.
Doesn't look like we have a specific issue tracking what you're looking for on the repo at the moment, so I'm leaving this one open.
There will be a number of enhancements made in logging, and we're tracking them here https://github.com/Azure/azure-functions-dotnet-worker/labels/logging

@brettsam @kshyju for awareness.

@fabiocav I cannot find a specific issue to track the progress of the implementation of host instrumentation. Could you give an update about this?

any news on this?

Any news on this?

We now have an activity source you can listen to: Microsoft.Azure.Functions.Worker
https://github.com/Azure/azure-functions-dotnet-worker/blob/2d16152a9c9cad8ed71e8aae1f660d7025a9c498/src/DotNetWorker.Core/Diagnostics/FunctionActivitySourceFactory.cs#L14


Add nippon colors extension

Description
This extension enbale to explore nippon(japanese) colors! which are collected at the site below!
NIPPON COLORS is made by Takehiko Ono, who is a web designer and developer in Japan!
https://nipponcolors.com/
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@sxn thanks! oh my goodness, I'm ashamed of myself.
it's totally alright with me. I appriciate you!!!

Overall, the extension looks pretty good! One thing that I noticed is that it is pretty slow, and it is hitting the website pretty hard every time the command gets loaded.
As it's the first time I've heard of nipponcolors, I'm not aware e.g. how exactly it's used. Do the colors change often? Do they ever change? if they don't change, I'd suggest to move the fetching to a separate script, that can be run manually by you, or maybe automatically on install / build / etc. That way the extension will be fast, and we're not constantly making requests to the website.
If the colors do change, we should then figure out how often, and only fetch new data if the cache is absent or outdated.
Does that make sense? 😸

of course! there are a couple other extensions that work kind of the same way. For example dot-new, Bible, Lucide Icons etc, so hopefully you can find some inspiration.
If you get stuck, just ping me here or on Slack and we can figure out whatever we need. 😸

Thanks!, I'm gonna study them. I will work on it soon🔥!!!

oh, that's much better! 👏 let's get this merged! :shipit:

Thanks you for reviewing lol


Jan 2024 CPU - Temurin JDK21 release triage

Release Summary Report for release-openjdk21-pipeline
Report generated at: Wed, 17 Jan 2024 02:03:02 GMT
TRSS Build and TRSS Grid View
Jenkins Build URL https://ci.adoptium.net/job/build-scripts/job/release-openjdk21-pipeline/19/
Started by upstream project "build-scripts/utils/releaseTrigger_jdk21u" build number 1682 at 1/16/2024, 6:42:10 PM

✔ results in these Tables means the activity has successfully completed.
⏳ results means that we are actively working on closing off the runs needed for this version, platform, binaryType.
⛔ means there is no build planned for that version/platform combination.
⏸ means activity not yet started.

Platform
Status
Results

x86-64_mac
✔
comment

x86-64_linux
⏳
comment

x86-64_windows
⏳
comment

aarch64_linux
⏳
comment

aarch64_mac
✔
all pass

x86-64_alpine-linux
⏸
comment

ppc64le_linux
⏸
build failed, will need a rerun

s390x_linux
⏸
comment

ppc64_aix
⏸
comment

x86-64_linux
jdk21_x64Linux_AQAvitTaps.zip
TAPverification shows:
sanity.openjdk - 5 targets fail, jdk_lang_0, jdk_lang_1, jdk_util_0, jdk_util_1 and jdk_foreign_0 - rerun in Grinder/8539
waiting on extended.openjdk results
all other top-level test targets passing

x86-64_windows
jdk21_Windows_AQAvitTaps.zip
waiting on sanity.system and extended.openjdk results
all other top-level targets pass

x86-64_alpine-linux
jdk21_alpineLinux_AQAvitTaps.zip
waiting on sanity.openjdk and extended.openjdk results
all other top-level targets pass

ppc64le_linux
rerun in https://ci.adoptium.net/job/build-scripts/job/release-openjdk21-pipeline/21/ - Grid view
Release Summary Report for release-openjdk21-pipeline
Report generated at: Wed, 17 Jan 2024 19:34:22 GMT
TRSS Build and TRSS Grid View
Jenkins Build URL https://ci.adoptium.net/job/build-scripts/job/release-openjdk21-pipeline/21/
Started by upstream project "build-scripts/utils/releaseTrigger_jdk21u" build number 1682 at 1/17/2024, 9:37:43 AM

s390x_linux
jdk21_s390x_AQAvitTaps.zip
waiting on extended.openjdk
all other top-level targets pass

ppc64_aix
jdk21_aix_AQAvitTaps.zip
============================
list AQAvit TAP files in /Users/shelleylambert/Downloads/AQAvitTaps
============================
1. List sanity.openjdk ...
Test_openjdk21_hs_sanity.openjdk_ppc64_aix.tap
2. List extended.openjdk ...
*extended.openjdk*.tap
3. List sanity.functional ...
Test_openjdk21_hs_sanity.functional_ppc64_aix.tap
4. List extended.functional ...
Test_openjdk21_hs_extended.functional_ppc64_aix.tap
5. List special.functional ...
Test_openjdk21_hs_special.functional_ppc64_aix.tap
6. List sanity.system ...
Test_openjdk21_hs_sanity.system_ppc64_aix.tap
7. List extended.system ...
Test_openjdk21_hs_extended.system_ppc64_aix.tap
8. List sanity.perf ...
Test_openjdk21_hs_sanity.perf_ppc64_aix.tap
9. List extended.perf ...
Test_openjdk21_hs_extended.perf_ppc64_aix.tap
============================
List failed tests in /Users/shelleylambert/Downloads/AQAvitTaps
============================
./Test_openjdk21_hs_extended.perf_ppc64_aix.tap:not ok 20 - renaissance-philosophers_0

aarch64_alpine-Linux

Test_openjdk21_hs_extended.openjdk_aarch64_alpine-linux ❌ ABORTED ❌
Test_openjdk21_hs_extended.openjdk_aarch64_alpine-linux_testList_0 ❌ ABORTED ❌
jdk_beans_1 => deep history 0/2 passed | possible issues
jdk_security3_0 => deep history 0/1 passed | possible issues
jdk_net_0 => deep history 0/1 passed | possible issues
jdk_time_1 => deep history 0/1 passed | possible issues
jdk_jmx_0 => deep history 8/9 passed | possible issues
jdk_jfr_1 => deep history 0/1 passed | possible issues
Test_openjdk21_hs_extended.openjdk_aarch64_alpine-linux_testList_1 ❌ ABORTED ❌
jvm_compiler_0 => deep history 0/1 passed | possible issues
Test_openjdk21_hs_extended.openjdk_aarch64_alpine-linux_testList_2 ❌ ABORTED ❌
jdk_io_1 => deep history 0/1 passed | possible issues
jdk_other_1 => deep history 0/1 passed | possible issues
jdk_net_1 => deep history 8/9 passed | possible issues
jdk_nio_1 => deep history 8/9 passed | possible issues
jdk_text_0 => deep history 8/9 passed | possible issues
jdk_management_0 => deep history 8/9 passed | possible issues
Test_openjdk21_hs_sanity.openjdk_aarch64_alpine-linux ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "21.0.2" 2024-01-16 LTS
OpenJDK Runtime Environment Temurin-21.0.2+13 (build 21.0.2+13-LTS)
OpenJDK 64-Bit Server VM Temurin-21.0.2+13 (build 21.0.2+13-LTS, mixed mode, sharing)

jdk_util_0 => deep history 11/13 passed | possible issues
Test_openjdk21_hs_sanity.openjdk_aarch64_alpine-linux_rerun ⚠ UNSTABLE ⚠
Rerun failed
java -version
openjdk version "21.0.2" 2024-01-16 LTS
OpenJDK Runtime Environment Temurin-21.0.2+13 (build 21.0.2+13-LTS)
OpenJDK 64-Bit Server VM Temurin-21.0.2+13 (build 21.0.2+13-LTS, mixed mode, sharing)

Failures in the rerun test build
jdk_util_0
jdk_util_0
jdk_util_0


fix: should support disordered array as fieldname, close: ant-design/ant-design#8985

Close: https://github.com/ant-design/ant-design/issues/8985

ci broken

It is just lint which was introduced in https://github.com/react-component/form/pull/138 and I fix it in https://github.com/react-component/form/pull/144


fnmatch breaks referential transparency

fnmatch gives different outputs on successive calls with the same inputs:
ghci> import FnMatch as F
ghci> F.fnmatch "a" "a" []
False
ghci> F.fnmatch "a" "a" []
True

fnmatch version: <IP_ADDRESS>
GHC version: 9.2.8
System: NixOS 23.05

❯ stack ghci
Configuring GHCi with the following packages: fnmatch.
GHCi, version 9.6.3: https://www.haskell.org/ghc/  :? for help
[1 of 1] Compiling FnMatch          ( /home/domen/dev/fnmatch/src/FnMatch.hs, interpreted )
Ok, one module loaded.
Loaded GHCi configuration from /home/domen/.cache/stack/ghci-script/1fc6c52b/ghci-script
ghci> import FnMatch as F
ghci> F.fnmatch "a" "a" []
True
ghci> F.fnmatch "a" "a" []
True
ghci> F.fnmatch "a" "a" []
True
ghci>


Allow use of the enter key for password input for code-server

Describe in detail the problem you had and how this PR fixes it
Accept enter in addition to clicking the submit button on the code-server login page.
Is there an open issue you can link to?
#478

Could we use a regular form instead? Then enter would just work as expected. It feels slightly odd to me to re-implement form logic in JavaScript.


CA-187421: CA-140647 was fixed in XenAdmin, but the change has never …

…made it to SDKs
Moved code to SDKs
Signed-off-by: Gabor Apati-Nagy<EMAIL_ADDRESS>

Just bringing code from XenCenter into the SDKs.

Thanks Stephen, merging now.


docs: Add encode and decode to the user guide

Which issue does this PR close?

Closes #.
Rationale for this change
Documents code added in https://github.com/apache/arrow-datafusion/pull/6821 by @ozgrakkurt
What changes are included in this PR?
Add new section to the user guide (based off https://www.postgresql.org/docs/9.4/functions-binarystring.html)

Are these changes tested?
existing tests

Are there any user-facing changes?
docs

Thanks for the review @r4ntix


Kamelet API test rate limit

--- FAIL: TestNewRepositoryWithCamelKamelets (0.06s)
    repository_test.go:151:
        	Error Trace:	repository_test.go:151
        	Error:      	Received unexpected error:
        	            	GET https://api.github.com/repos/apache/camel-kamelets/contents/kamelets: 403 API rate limit exceeded for <IP_ADDRESS>. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.) [rate reset in 50m05s]
        	Test:       	TestNewRepositoryWithCamelKamelets
    repository_test.go:152:
        	Error Trace:	repository_test.go:152
        	Error:      	Should be true
        	Test:       	TestNewRepositoryWithCamelKamelets

I think we need to review that test to mitigate the number of API hit.

Probably the issue is not only for testing, but rather more broadly related to the way how the cli and testing interact with GitHub API.
https://docs.github.com/en/developers/apps/building-github-apps/rate-limits-for-github-apps
So a cli which interacts with GitHub API should be aware of GITHUB_TOKEN and when it's available it should use the token to mitigate the rate limits. For example, we interact with GitHub API through kamel run and when we run kamel run github:...  many times we'll hit the same rate limit issue.
Likewise GitHub Actions provides a secret.GITHUB_TOKEN for each workflow so we can utilise the token for the CI tests.

Marking as a bug as this is starting to fail with insistence in our checks. Should be solved with priority.


All repository methods now return a task

This does not include the void methods.

Void methods now also return tasks.


Use streaming for ChatGPT access

The ChatGPT chat API is currently pretty slow, so it might seem to the user that nothing is happening if we wait for the whole request to finish. It seems necessary to use the streaming version of the chat API so that the user sees the answer trickling in.

Duplicate of #5


Use IOptions<T>.Value rather than Options

This sample is shown here: http://docs.asp.net/en/latest/fundamentals/configuration.html#using-options-and-configuration-objects

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

:shipit:

Thanks for the PR! However, this has already been fixed in d522c691b34f5a0e50b4d86715ce71abe923717b

Allright! :+2:


rust-bindgen: 0.49.2 -> 0.49.3

Motivation for this change
Update rust-bindgen to the latest release.
https://github.com/rust-lang/rust-bindgen/releases/tag/v0.49.3
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

@GrahamcOfBorg build rust-bindgen


[* Number] Ordinal recognizer could not tag "last"

For Query = "delete last sentence in the note", the word "last" will not be annotated as ordinal, while it works for queries "delete [first|second|...] sentence in the note".
Could ordinal support "next" or "last"?

Support for "Last" is planned in Ordinal. However "next" doesn't seem like it fits well in the Ordinal behaviour.

When you open new issues, please keep the issue template as it makes it easier to analyze/classify issues. Thanks!


Debug dnx . ef commands?

Hi,
I'm developing a vNext project.
I was wondering if it's possible to attach a debugger to the dnx . ef command, so that when executing migrations, I can place a breakpoint at the OnModelCreating piece in my context.
I believe this feature doesn't exist, but do you think it would be a good idea? Is it easily achievable?

Hmm.. I asked xUnit.net to add a -debug flag for similar reasons, but I'm not sure if debugging models and migrations is quite as common. You can always add the following to you code to get a debugger attached.
Debugger.Launch();

Closing. We discussed as a team and decided that this should either be a DNX feature or left up to the users--there's nothing for the EF team to do here.


Change the navbar and footer and style of the FAQ page to that of the contributor page.

Make it so that the FAQ page stays responsive.
The FAQ UI is like that of the other pages except Homepage.

Please assign me this issue under JWOC '24

Go for it! @Sneha123-zudo


Update Helm Chart to support mariaDB

NOTE: This depends on https://github.com/SUSE/stratos-ui/pull/1229

 Update Helm chart to use MariaDB


[WIP] feat: automatically register logstream

Changes

Automatically register logstream for each commonly known component in knative-eventing namespace

/cc @pierDipi
This is WIP, please leave feedback!

Closing in favour of opening a new PR based on the new logging in ekb


A way to refer to named ranges?

Is there a way to refer to named ranges? One thing I face is that I have to integrate a spreadsheet into my code, where the spreadsheet changes a lot. Now, I could try to find some column name field and populate my column references that way, but since the spreadsheet already has named ranges in it, it would be easier for me to refer to the range name instead. Is there a way to do that? Thanks.

Why not in a future release. But it is not possible for the moment.


Handling Error 1006

Hi,
I've recently seen that I hit the pusher error 1006:
Error { type: 'WebSocketError', error: 'close code 1006' }

I no longer seem to receive any messages after this event occurs so I took a look at the code and found that you've chosen not to handle this error with a retry:
https://github.com/dirkbonhomme/pusher-client-node/blob/master/lib/connection.js#L124
https://github.com/dirkbonhomme/pusher-client-node/blob/master/lib/connection.js#L128
I'm just wondering why this isn't included as part of the range you would like to retry on?
Also is there a way I can actively recover from such a disconnection?
Thanks

Hmm good question. This node client is a port of the official Pusher JavaScript (client-side) library. They use the same handling of this code:
https://github.com/pusher/pusher-js/blob/0ef56995ed9605b79ba4b22d1a13c84652d47793/src/core/connection/protocol/protocol.ts#L95
The official library has since been rewritten and can now also be used in Node.js. If possible, try to switch to their library: https://github.com/pusher/pusher-js
It might have some retry logic for this error code these days.

Thanks I'll raise it with them although it seems to follow the same thinking.


Planning for the "5.0" release (i.e. the one after 3.1) will start in the coming weeks.
Pull requests from the last week
EF Core

Query

Fixed incorrect queryable conversion for sources that are not queryable
Refactored shaped query compilation visitors
Fixed several issues in navigation expansion
Fixed conditional and null-coalescing handling in parameter extraction
Removed internal in-memory operator provider
Fixed Contains translation for arbitrary collection types
Mitigate usability of IX-Async and EF Core together
Optimization of null semantics when checking if expression is null

Model building:

Fixed generation of non-static members
Warn when converting collection property without comparer
Fixed incorrect seeding of store-generated properties
Fixed snapshot for spurious model diffs when using owned types
Stop showing auto-property backing fields in debug view

Migrations/tooling:

Fixed tools NuGet package to not include dependency group
Fixed scaffolding of value-generation facets
Fixed snapshotting temporary values for Added entities

Other:

Code cleanup
Fixed SQLite provider to treat in-memory databases as always existing

Test improvements:

Test for constant projection after set operation

EF6

Reverted ef6.exe to use .NET Core 3.0

Microsoft.Data.Sqlite:

Fixed possible exceptions when disposing SQLite readers

Documentation

Added mark-down linter to docs build

Community contributions

@riccikl contributed a change to move doc code samples into compilable projects
@chrfin contributed an improvement to EF6 query compilation performance
@ite-klass contributed formatting improvements in EF6 API docs
@OOberoi contributed improved wording for EF Core 3.0 query documentation
@Psypher9 contributed a typo fix for the EF6 documentation

Many thanks for your contributions!
Issues remaining for 3.1
This is the burn-down chart we use internally to track progress towards EF Core 3.1. Some observations:

The gray bar at the top represents all the issues already fixed for 3.1 - we are at 129 issues fixed

Latest releases
EF Core:

Daily builds: install the latest preview SDK, then follow the instructions from the wiki
Latest preview: EF Core 3.1 Preview 1
Current: EF Core 3.0.0
LTS: EF Core 2.1.11

EF6:

Daily builds: install the latest preview SDK, then use the feeds listed on the repo homepage
Latest preview: EF 6.4 Preview 1
Current: EF 6.3.0

More Information
See the top of this issue for links to more information.
Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

November 7, 2019
EF Core 3.1
EF Core 3.1 Preview 2 is on NuGet! However, we still recommend using the daily builds--see below.
What you need to know about EF Core 3.1:

The release cycle is short--EF Core 3.1 is scheduled for release on December 3.
The goal of this release is to stabilize 3.0 and fix bugs to prepare 3.1 for long term support (LTS)
We have fixed 140 issues so far
EF Core 3.1 contains no new significant features

Builds to use

The daily builds are the most up-to-date available.

Using the daily builds is a great way to find issues and provide feedback as early as possible. The sooner we get such feedback, the more likely it will be actionable before the next official release.
We work hard to keep the daily builds in good shape by running over 50,000 tests per TFM for each build.
Currently we have daily builds for 3.1 and for "5.0". Most work is currently going into the 3.1 builds.

EF Core 3.1 preview 2 is available now on NuGet.

Preview releases on NuGet are a reasonable way to help find issues and provide feedback. However, keep in mind that these releases tend to lag a couple weeks from what is happening on GitHub, and so are usually not as good an option as the daily builds. For example, the daily builds of 3.1 contain fixes for 36 issues not in the preview 2 release.

Current: EF Core 3.0.0
LTS: EF Core 2.1.11

What are we doing now?
We are currently spending most of our time fixing bugs for the 3.1 release--see above.
In addition, we are working on:

Technical debt

Code cleanup, additional testing, test reliability, etc.

Documentation

Updating docs to be cover changes in the 3.0 release
An overhaul of the getting started docs to make them more approachable/easier to follow
Re-organization of docs to make things easier to find and to add cross-references
Adding more details and clarifications to existing docs
Updating the samples and adding more examples

Planning and process improvements

Planning for the "5.0" release (i.e. the one after 3.1) will start in the coming weeks.
Pull requests from the last week
This week we have merged 12 pull requests from community contributors! Way to go, community! Thanks so much!
Community contributions

@pmiddleton fixed metadata for function mapping to use namespace-qualified names
@chrfin fixed a concurrency issue in EF6 and re-enabled some perf improvements
@breyed fixed a typo
@morrisjdev added the FileContextCore database provider to the external providers list
@gurmeetsinghdke added several links and small improvements to the EF6 documentation: 1859 1858 1860 1873
@EricStG updated documentation for Npgsql spatial transformations
@Psypher9 fixed a typo
@vanillajonathan fixed code formatting
@StefH fixed double quote characters

EF Core

Query

Fix query filters against null navigations
Fix connection resiliency/Azure retries for queries
More fixes to improve optimization of null expansions
Fix to improve null handling with flags enums
Fix to handle casts in navigation expansion
Fix to generate correct default for FirstOrDefault in sub-queries
Unwrap query nodes around entity before doing member lookup
Deprecated NullConditionalExpression
Deprecated UseRowNumberForPaging API, since it is no longer functional
Improvements to expression printing

Other:

Updated Cosmos dependency to 3.3.3
Updated SQLitePCL.raw dependency to 2.0.2
Code cleanup

Test improvements:

Remove unnecessary element sorters
Test older model snapshots with owned types
Fix some pseudo-non-determinism in tests
Apply element sorter in AssertIncludeQuery
Ignore line-endings in test assertions
More test coverage for null semantics
Test for coalesce with not equals
Improve reliability of Cosmos tests
Disable flakey Cosmos tests: 18683 18726

Documentation:

Updated Cosmos provider documentation

Issues remaining for 3.1
This is the burn-down chart we use internally to track progress towards EF Core 3.1. Some observations:

The gray bar at the top represents all the issues already fixed for 3.1 - we are at 140 issues fixed

Latest releases
EF Core:

Daily builds: install the latest preview SDK, then follow the instructions from the wiki
Latest preview: EF Core 3.1 Preview 2
Current: EF Core 3.0.0
LTS: EF Core 2.1.11

EF6:

Daily builds: install the latest preview SDK, then use the feeds listed on the repo homepage
Latest preview: EF 6.4 Preview 2
Current: EF 6.3.0

More Information
See the top of this issue for links to more information.
Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

November 14, 2019
EF Core 3.1
EF Core 3.1 Preview 3 is on NuGet! This is the last preview before GA/RTM and contains almost everything we plan to ship in 3.1. Please try it now!
What you need to know about EF Core 3.1:

The release cycle is short--EF Core 3.1 is scheduled for release on December 3.
The goal of this release is to stabilize 3.0 and fix bugs to prepare 3.1 for long term support (LTS)
We have fixed 145 issues so far
EF Core 3.1 contains no new significant features

Builds to use

The daily builds are the most up-to-date available.

Using the daily builds is a great way to find issues and provide feedback as early as possible. The sooner we get such feedback, the more likely it will be actionable before the next official release.
We work hard to keep the daily builds in good shape by running over 50,000 tests per TFM for each build.
Currently we have daily builds for 3.1 and for "5.0". Most work is currently going into the 3.1 builds.

EF Core 3.1 preview 3 is available now on NuGet.

Preview releases on NuGet are a reasonable way to help find issues and provide feedback. However, keep in mind that these releases tend to lag a couple weeks from what is happening on GitHub, and so are usually not as good an option as the daily builds.

Current: EF Core 3.0.0
LTS: EF Core 2.1.11

What are we doing now?
The 3.1 release is now locked down; we don't expect to put any more changes into 3.1.
Planning for the "5.0" release (i.e. the one after 3.1) has started! We will share more in the coming weeks.
In addition, we are working on:

Technical debt

Code cleanup, additional testing, test reliability, etc.

Documentation

Updating docs to be cover changes in the 3.0 release
An overhaul of the getting started docs to make them more approachable/easier to follow
Re-organization of docs to make things easier to find and to add cross-references
Adding more details and clarifications to existing docs
Updating the samples and adding more examples

Planning and process improvements

Pull requests from the last week
Community contributions

@vanillajonathan fixed formatting issues
@jtheisen submitted an update to the external extensions list

Many thanks to @vanillajonathan and @jtheisen!
EF Core

Query

Fixed culture-specific comparison causing query failures for some languages
Ported the fix for filtering against null reference types to 3.1
Fixed joins where key selector is anonymous with single property
Added support for non boolean bitwise compliment

Other:

Updated README
Removed obsolete code ready for 5.0

Test improvements:

Fixed query assertions
Added regression tests for parameter reuse
Added regression tests for GroupBy on keyless entities
Enabled more null semantics tests
Switched to using declarations in many tests: 18816 18801
Cleaned up test output helpers
Cleaned up parameter naming in async tests

Documentation:

Clarifications for owned-types documentation
New documentation for setting Azure SQL database options
Show how to map multiple columns to the same property when using TPH
Clarifications for value generation of primary key values

Issues remaining for 3.1
This is the burn-down chart we use internally to track progress towards EF Core 3.1. Some observations:

As stated above, we don't have any more changes planned for 3.1.
The gray bar at the top represents all the issues already fixed for 3.1 - we are at 145 issues fixed

Latest releases
EF Core:

Daily builds: install the latest preview SDK, then follow the instructions from the wiki
Latest preview: EF Core 3.1 Preview 3
Current: EF Core 3.0.0
LTS: EF Core 2.1.11

EF6:

Daily builds: install the latest preview SDK, then use the feeds listed on the repo homepage
Latest preview: EF 6.4 Preview 3
Current: EF 6.3.0

More Information
See the top of this issue for links to more information.
Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

November 21, 2019
EF Core 3.1
EF Core 3.1 Preview 3 is on NuGet! This is the last preview before GA/RTM and contains almost everything we plan to ship in 3.1. Please try it now!
What you need to know about EF Core 3.1:

The release cycle is short--EF Core 3.1 is scheduled for release on December 3.
The goal of this release is to stabilize 3.0 and fix bugs to prepare 3.1 for long-term support (LTS)
We have fixed 150 issues so far
EF Core 3.1 contains no new significant features

Builds to use

The daily builds are the most up-to-date available.

Using the daily builds is a great way to find issues and provide feedback as early as possible. The sooner we get such feedback, the more likely it will be actionable before the next official release.
We work hard to keep the daily builds in good shape by running over 50,000 tests per TFM for each build.
Currently we have daily builds for 3.1 and for "5.0". Most work is currently going into the 3.1 builds.

EF Core 3.1 preview 3 is available now on NuGet.

Preview releases on NuGet are a reasonable way to help find issues and provide feedback. However, keep in mind that these releases tend to lag a couple weeks from what is happening on GitHub. This means daily builds are often a better option.

Current: EF Core 3.0.1
LTS: EF Core 2.1.14

What are we doing now?
The 3.1 release is now locked down; we don't expect to put any more changes into 3.1.
Critical bugs in 3.1 are now being considered for patch releases.
Planning for the "5.0" release (i.e. the one after 3.1) has started and we are making good progress. We will have something to share soon.
In addition, we are working on:

Technical debt

Code cleanup, additional testing, test reliability, etc.

Documentation

Updating docs to be cover changes in the 3.0 release
An overhaul of the getting started docs to make them more approachable/easier to follow
Reorganization of docs to make things easier to find and to add cross-references
Adding more details and clarifications to existing docs
Updating the samples and adding more examples

Planning and process improvements

Pull requests from the last week
Community contributions

@ptjhuang fixed queries with deep nesting by flattening Case expressions
@ivaylokenov fixed a typo in ParameterExtractingExpressionVisitor
@Youssef1313 updated docs metadata for dotnet commands
@jfoshee fixed a typo in the SDK link

Many thanks to all our contributors this week!
EF Core

Query

Fixed issue with complex OrderBy/ThenBy using navigations
Fixed comparisons of spatial types to not use topological semantics
Corrected SqlFunctionExpression to accept SqlExpression
Enable optimizations by injecting SearchConditionConvertingExpressionVisitor into ParameterValueBasedSelectExpressionOptimizer
Make ParameterBasedQueryTranslationPostprocessor public
Stop using VisitAndConvert in ProjectionBindingExpressionVisitor

Cosmos

Renamed Get/SetPropertyName to Get/SetJsonPropertyName

Dependency updates:

Updated Microsoft.Azure.Cosmos dependency to 3.4.1
Updated Microsoft.Data.SqlClient dependency to 1.1.0

Other:

Make health checks more robust by catch exceptions in CanConnect
Stop exposing ICurrentDbContext on QueryCompilationContextDependencies

Test improvements:

Improve developer experience by splitting large test classes
Switched to using declarations in remaining tests

Documentation:

Fixed typo in owned entity docs
Cleaned up doc links

Issues remaining for 3.1
The 3.1 release is now closed down. The burn-down will return for 5.0 once the plan is ready.
Latest releases
EF Core:

Daily builds: install the latest preview SDK, then follow the instructions from the wiki
Latest preview: EF Core 3.1 Preview 3
Current: EF Core 3.0.1
LTS: EF Core 2.1.14

EF6:

Daily builds: install the latest preview SDK, then use the feeds listed on the repo homepage
Latest preview: EF 6.4 Preview 3
Current: EF 6.3.0

More Information
See the top of this issue for links to more information.
Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

December 5, 2019
EF Core 3.1
The GA/RTM release of EF Core 3.1 is out and available on NuGet now!
What's new in 3.1?
The primary goal of EF Core 3.1 is to polish the features and scenarios we delivered in EF Core 3.0. EF Core 3.1 will be a long term support (LTS) release, supported for at least 3 years. To this end we have fixed over 150 issues for the 3.1 release, but there are no major new features to announce.
Support for .NET Standard 2.0
EF Core 3.1 reintroduces support for .NET Standard 2.0, rather than requiring .NET Standard 2.1 as was the case for EF Core 3.0. This means EF Core 3.1 will run on .NET Framework versions supported by the standard.
Builds to use

The daily builds are the most up-to-date available.

Using the daily builds is a great way to find issues and provide feedback as early as possible. The sooner we get such feedback, the more likely it will be actionable before the next official release.
We work hard to keep the daily builds in good shape by running over 50,000 tests per TFM for each build.
Daily builds now contain work scheduled for release in EF Core 5.0.

Current: EF Core 3.1.0
LTS: EF Core 3.1.0

EF 6.4
The GA/RTM release of EF 6.4 is also out and available on NuGet now. Similar to EF Core, the primary goal of EF 6.4 is to polish the features and scenarios we delivered in EF 6.3. To this end we have fixed important issues found in EF 6.3 to create a more stable release.
What are we doing now?
Critical bugs in 3.1 are now being considered for patch releases. The first patch release is tentatively scheduled for January.
Planning for the "5.0" release (i.e. the one after 3.1) has started and we are making good progress. We will have something to share soon.
In addition, we are working on:

Technical debt

Code cleanup, additional testing, test reliability, etc.

Documentation

Updating docs to be cover changes in the 3.0 and 3.1 releases
An overhaul of the getting started docs to make them more approachable/easier to follow
Reorganization of docs to make things easier to find and to add cross-references
Adding more details and clarifications to existing docs
Updating the samples and adding more examples

Planning and process improvements
Holiday spirit and recovering from the intense 3.0/3.1 release!

New features in EF Core 5.0
As stated above, planning of 5.0 major features is ongoing, but in addition to bug fixes we have already merged a few small features/enhancements.
Simple Logging
This feature is the moral equivalent of Database.Log in EF6. That is, it provides a simple way to get logs from EF Core without the need to configure any kind of external logging framework.
EF Core replaces Database.Log with a LogTo method called on DbContextOptionsBuilder in either AddDbContext or OnConfiguring. For example:
protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
    => optionsBuilder.LogTo(Console.WriteLine);

Overloads exist to:

Set the minimum log level

Example: .LogTo(Console.WriteLine, LogLevel.Information)

Filter for only specific events:

Example: .LogTo(Console.WriteLine, new[] {CoreEventId.ContextInitialized, RelationalEventId.CommandExecuted})

Filter for all events in specific categories:

Example: .LogTo(Console.WriteLine, new[] {DbLoggerCategory.Database.Name}, LogLevel.Information)

Use a custom filter over event and level:

Example: .LogTo(Console.WriteLine, (id, level) => id == RelationalEventId.CommandExecuting)

Output format can be minimally configured (API is in flux) but the default output looks something like:
warn: 12/5/2019 09:57:47.574 CoreEventId.SensitiveDataLoggingEnabledWarning[10400] (Microsoft.EntityFrameworkCore.Infrastructure)
      Sensitive data logging is enabled. Log entries and exception messages may include sensitive application data, this mode should only be enabled during development.
dbug: 12/5/2019 09:57:47.581 CoreEventId.ShadowPropertyCreated[10600] (Microsoft.EntityFrameworkCore.Model.Validation)
      The property 'BlogId' on entity type 'Post' was created in shadow state because there are no eligible CLR members with a matching name.
info: 12/5/2019 09:57:47.618 CoreEventId.ContextInitialized[10403] (Microsoft.EntityFrameworkCore.Infrastructure)
      Entity Framework Core 5.0.0-dev initialized 'BloggingContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer' with options: SensitiveDataLoggingEnabled
dbug: 12/5/2019 09:57:47.644 CoreEventId.ValueGenerated[10808] (Microsoft.EntityFrameworkCore.ChangeTracking)
      'BloggingContext' generated temporary value '-2147482647' for the 'Id' property of new 'Blog' entity.
...

Translation of Contains on byte arrays
Queries using Contains on byte[] properties are now translated to SQL. For example:
var blogs = context.Blogs.Where(e => e.Picture.Contains((byte)127)).ToList();

Translates to the following on SQL Server:
info: 12/5/2019 11:42:42.022 RelationalEventId.CommandExecuted[20101] (Microsoft.EntityFrameworkCore.Database.Command)
      Executed DbCommand (1ms) [Parameters=[], CommandType='Text', CommandTimeout='30']
      SELECT [b].[Id], [b].[Picture], [b].[Title]
      FROM [Blogs] AS [b]
      WHERE CHARINDEX(0x7F, [b].[Picture]) > 0

Pull requests from the last two weeks
Community contributions

@cincuranet reintroduced GeneratePseudoFromClause for use by external providers
@OOberoi fixed grammar in getting started documentation
@rmarskell contributed a clarifying change to a parameter name
@ozantopal fixed a typo in index documentation

Many thanks to all our contributors!
EF Core

Query

Fixed invalid SQL when using conditional expression with null-valued parameter

This issue is approved for the 3.1.1 patch release.

Fixed exception thrown from Avg/Min/Max when result is zero

This issue is approved for the 3.1.1 patch release.

Fixed incorrect exception message for SingleAsync
Support for Contains on byte arrays with SQLite
Support for Contains on byte arrays with SQL Server

Dependency updates:

Pin dependencies to 3.1 versions

Other:

Fixed incorrect Obsolete link

This issue is approved for the 3.1.1 patch release.

Implementation of simple logging
Implemented a debug view for the state manager
Implemented a shorter debug view for the model
Updated private nested classes to avoid virtual methods
Moved GitHub wiki pages to markdown in repo
Removed unused SqlServerOptions

Tests:

Updates to null-expansion regression tests
Improvements to query validation tests
Test cleanup
More test cleanup
Fixed simple logging test failure
Fixed a SQLite test reliability issue
Added byte array property to test model

Documentation:

Added breaking change documentation for IMemoryCache
Fixed SQLite documentation metadata
Improvements to relationship documentation
Fixed typo in owned entities documentation
Updated EF6 guidance for for using transactions and execution strategy

Issues remaining for 5.0
The burn-down will return for 5.0 once the plan is ready.
Latest releases
EF Core:

Daily builds: install the latest preview SDK, then follow the instructions from the wiki
Current: EF Core 3.1.0
LTS: EF Core 3.1.0

EF6:

Daily builds: install the latest preview SDK, then use the feeds listed on the repo homepage
Current: EF 6.4.0

More Information
See the top of this issue for links to more information.
Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

December 12, 2019
EF Core 3.1
The GA/RTM release of EF Core 3.1 is out and available on NuGet now!
Builds to use

The daily builds are the most up-to-date available.

Using the daily builds is a great way to find issues and provide feedback as early as possible. The sooner we get such feedback, the more likely it will be actionable before the next official release.
We work hard to keep the daily builds in good shape by running over 50,000 tests per TFM for each build.
Daily builds now contain work scheduled for release in EF Core 5.0.

Current: EF Core 3.1.0
LTS: EF Core 3.1.0

What are we doing now?
Critical bugs in 3.1 are now being considered for patch releases. The first patch release is tentatively scheduled for January.
Planning for the "5.0" release (i.e. the one after 3.1) has started and we are making good progress. We need to sync with the .NET directors before we can share publicly.
In addition, we are working on:

Technical debt

Code cleanup, additional testing, test reliability, etc.

Documentation

Updating docs to be cover changes in the 3.0 and 3.1 releases
An overhaul of the getting started docs to make them more approachable/easier to follow
Reorganization of docs to make things easier to find and to add cross-references
Adding more details and clarifications to existing docs
Updating the samples and adding more examples

Planning and process improvements
Holiday spirit and recovering from the intense 3.0/3.1 release!

New features in EF Core 5.0
As stated above, planning of 5.0 major features is ongoing, but in addition to bug fixes we have already merged a few small features/enhancements.
Debug views
Debug views are an easy way to look at the internals of EF Core when debugging issues. A debug view for the Model was implemented some time ago. For EF Core 5.0, we have made the model view easier to read and added a new debug view for tracked entities in the state manager.
Model debug view
Drill down into the Model property of the DbContext in your debugger of choice and expand the DebugView property.

The LongView is the model view we have had for some time. The ShortView is new and doesn't include model annotations, which make it much easier to read.  To find it, drill down into the ChangeTracker property of the DbContext in your debugger of choice and then look in the StateManager property and expand the DebugView.

The short view of the state manager shows:

Each entity being tracked
Its primary key value(s)
The entity state - one of Added, Unchanged, Modified, or Deleted.
The values of an foreign key properties

For example:
Engine (Shared) {Id: 1} Unchanged FK {EngineSupplierId: 1}
Location (Shared) {EngineId: 1} Unchanged FK {EngineId: 1}
Team (Shared) {Id: 4} Modified FK {EngineId: 1} FK {GearboxId: <null>}

The long view shows everything in the short view together with:

The current value of each property
Whether or not the property is marked as modified
The original value of the property, if different from the current value
The entity referenced by a reference navigation using the referenced entity's primary key value
The list if entities referenced by a collection navigation, again using primary key values

For example:
Engine (Shared) {Id: 1} Unchanged
  Id: 1 PK
  EngineSupplierId: 1 FK
  Name: 'FO 108X'
  EngineSupplier: <null>
  Gearboxes: <null>
  StorageLocation: {EngineId: 1}
  Teams: [{Id: 4}]
Location (Shared) {EngineId: 1} Unchanged
  EngineId: 1 PK FK
  Latitude: 47.64491
  Longitude: -122.128101
Team (Shared) {Id: 4} Modified
  Id: 4 PK
  Constructor: 'Ferrari'
  ConstructorsChampionships: 16
  DriversChampionships: 15
  EngineId: 1 FK Modified Originally 3
  FastestLaps: 221
  GearboxId: <null> FK
  Name: 'Scuderia Ferrari Marlboro'
  Poles: 203
  Principal: 'Stefano Domenicali'
  Races: 805
  Tire: 'Bridgestone'
  Version: '0x000000000001405A'
  Victories: 212
  Chassis: <null>
  Drivers: []
  Engine: {Id: 1}
  Gearbox: <null>

Pull requests from the last two weeks
Community contributions

@svengeance fixed an issue when concatenating null with strings
@cincuranet contributed several fixes for SQL Server-specific ordering in provider tests: 19217 19223 19221
@redoz Fixed a typo in the change tracking documentation

Many thanks to all our contributors!
EF Core

Query:

Fixed issue preventing both constructor and property initializers being used in a projection

This issue is approved for the 3.1.1 patch release.

Improved MemberInfo matching for explicitly built expression trees
Cleanup: 19191 19271
Added argument checking for InExpression

Cosmos:

Fixed corruption of owned collection when updating in same context as query

This issue is approved for the 3.1.1 patch release.

Dependency updates:

Pin dependencies to 3.1 versions

Other:

Warn when an AddEntityFramework... method is called from application code

This issue is approved for the 3.1.1 patch release.

Updated nullable metadata and checking for query and Cosmos
Replaced Debug.Assert with less complex alternative
Updated LogTo logging based on design meeting feedback

Tests:

Query regression tests: 19195 19198 19197 19196

Documentation:

Merging of relational table documentation

Microsoft.Data.Sqlite

Huge documentation overall for Microsoft.Data.Sqlite including lots of new information

Connection Strings
Data Types
Parameters
Database Errors
Transactions
Batching
Metadata
In-Memory Databases
Encryption
Online Backup
User-Defined Functions
Custom SQLite Versions
Collation
BLOB I/O
Interoperability
Extensions
Using with Entity Framework Core
Using with Dapper
Compare to System.Data.SQLite
Using with Xamarin

Issues remaining for 5.0
The burn-down will return for 5.0 once the plan is ready.
Latest releases
EF Core:

Daily builds: install the latest preview SDK, then follow the instructions from the wiki
Current: EF Core 3.1.0
LTS: EF Core 3.1.0

EF6:

Daily builds: install the latest preview SDK, then use the feeds listed on the repo homepage
Current: EF 6.4.0

More Information
See the top of this issue for links to more information.
Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.


feat: create fast api wrapper

Summary
Create stub of FastAPI wrapper for our Gradescope API
Details
Adding the stubs for the FastAPI wrapper to gain feedback and review of the changes.
Checks

[x] Tested changes
[ ] Attached Logs

Team to Review
All
Reference to the issue
Mention the issue ID or resources

yea, what calvin said. we would have to clean up the commit history if it dupes


Installing the extension prevents from compiling any .qmd document

Thanks for the nice extension!
However I did not maage to make it work, I get this error mesage:
[string "..."]:296: module 'base64.lua' not found:
        no field package.preload['base64.lua']
        no file 'N:\XXXXX\XXXXX\_extensions\shafayetShafee\downloadthis\resources/lua/base64.lua'
        no file 'C:\Users\XXXXX\AppData\Local\Programs\Quarto\bin\tools\lua\base64\lua.lua'
        no file 'C:\Users\XXXXX\AppData\Local\Programs\Quarto\bin\tools\lua\base64\lua\init.lua'
        no file 'C:\Users\XXXXX\AppData\Local\Programs\Quarto\bin\tools\base64\lua.lua'
        no file 'C:\Users\XXXXX\AppData\Local\Programs\Quarto\bin\tools\base64\lua\init.lua'
        no file 'C:\Users\XXXXX\AppData\Local\Programs\Quarto\bin\tools\..\share\lua\5.4\base64\lua.lua'
        no file 'C:\Users\XXXXX\AppData\Local\Programs\Quarto\bin\tools\..\share\lua\5.4\base64\lua\init.lua'
        no file '.\base64\lua.lua'
        no file '.\base64\lua\init.lua'
        no file 'C:\Users\XXXXX\AppData\Local\Programs\Quarto\share\pandoc\datadir\base64\lua.lua'
        no file 'C:/Users/XXXXX/AppData/Local/Programs/Quarto/share/filters\base64\lua.lua'
        no file 'C:\Users\XXXXX\AppData\Local\Programs\Quarto\bin\tools\base64\lua.dll'
        no file 'C:\Users\XXXXX\AppData\Local\Programs\Quarto\bin\tools\..\lib\lua\5.4\base64\lua.dll'
        no file 'C:\Users\XXXXX\AppData\Local\Programs\Quarto\bin\tools\loadall.dll'
        no file '.\base64\lua.dll'
        no file 'C:\Users\XXXXX\AppData\Local\Programs\Quarto\bin\tools\base64.dll'
        no file 'C:\Users\XXXXX\AppData\Local\Programs\Quarto\bin\tools\..\lib\lua\5.4\base64.dll'
        no file 'C:\Users\XXXXX\AppData\Local\Programs\Quarto\bin\tools\loadall.dll'
        no file '.\base64.dll'
stack traceback:
        [string "..."]:296: in upvalue 'orig_require'
        [string "..."]:1353: in function 'require'
        (...tail calls...)
        ..._extensions\shafayetShafee\downloadthis\downloadthis.lua:53: in local 'chunk'
        ...rin/AppData/Local/Programs/Quarto/share/filters/main.lua:13966: in function 'initShortcodeHandlers'
        ...rin/AppData/Local/Programs/Quarto/share/filters/main.lua:15371: in main chunk

Looking forward for a solution, since it's supposed to dexactly what I am after!

What ia the quarto version that you are using?

Thank you for your quick reply!
I am using 1.3.321 according to quarto check

Did you install the extension using the command quarto add shafayetShafee/downloadthis? ( I have checked this extension for versions 1.2.475, 1.3.309 and 1.3.333. It is working fine so far.


document webhook event types

Feature Description
our webhook docs imply an event type, for which they mention push as an example.
it would be nice if we could document what event types gitea offers, and when these might trigger, if more than just push.
Screenshots
No response

Dito.
A good place to start may be:

Repo webhook settings page: https://github.com/go-gitea/gitea/blob/main/templates/repo/settings/webhook/settings.tmpl#L25

Field translations: https://github.com/go-gitea/gitea/blob/main/options/locale/locale_en-US.ini (descriptions of what the event does)

The struct HookEvents: https://github.com/go-gitea/gitea/blob/main/models/webhook/webhook.go#L122 (which seems to contain the json name of the hook that probably appears in the payload).

You could also take a look at https://gitea.com/jolheiser/gitea-webhook where I had done a little work to get thus started.
Admittedly I meet to rerun, as they are a bit out of date, but it should be a good start.
I'll try to get them updated soon.

It's funny how there's still no proper documentation in web hooks after so much time. Thanks @Timoses andd @jolheiser you help me big time.

This is the list of all Hook Events Types directly from their codebase:
https://github.com/go-gitea/gitea/blob/main/modules/webhook/type.go#L6
Till @lunny updates the docs, here is the list:
	HookEventCreate                    HookEventType = "create"
	HookEventDelete                    HookEventType = "delete"
	HookEventFork                      HookEventType = "fork"
	HookEventPush                      HookEventType = "push"
	HookEventIssues                    HookEventType = "issues"
	HookEventIssueAssign               HookEventType = "issue_assign"
	HookEventIssueLabel                HookEventType = "issue_label"
	HookEventIssueMilestone            HookEventType = "issue_milestone"
	HookEventIssueComment              HookEventType = "issue_comment"
	HookEventPullRequest               HookEventType = "pull_request"
	HookEventPullRequestAssign         HookEventType = "pull_request_assign"
	HookEventPullRequestLabel          HookEventType = "pull_request_label"
	HookEventPullRequestMilestone      HookEventType = "pull_request_milestone"
	HookEventPullRequestComment        HookEventType = "pull_request_comment"
	HookEventPullRequestReviewApproved HookEventType = "pull_request_review_approved"
	HookEventPullRequestReviewRejected HookEventType = "pull_request_review_rejected"
	HookEventPullRequestReviewComment  HookEventType = "pull_request_review_comment"
	HookEventPullRequestSync           HookEventType = "pull_request_sync"
	HookEventPullRequestReviewRequest  HookEventType = "pull_request_review_request"
	HookEventWiki                      HookEventType = "wiki"
	HookEventRepository                HookEventType = "repository"
	HookEventRelease                   HookEventType = "release"
	HookEventPackage                   HookEventType = "package"
	HookEventSchedule                  HookEventType = "schedule"


Cleanup Exception trace python

See https://dodona.ugent.be/activities/270198713/

The first file reference line should be removed (as is refers to internal code of the judge). The second file reference line may be retained. In other judges, we even link this line to the corresponding line in the "Code" tab of the feedback (Dodona has support for this). We might consider replacing 'submission.py' by <code>, as the name of the file itself is also internal to the judge.

Also check why there's a double "uitvoeren code" in the feedback.

The double "uitvoeren code" cames from the context description and the testcase description

The stacktrace isn't cleaned because of the specific evaluator


Add get_reversed_path in JointSpacePath

Get the reversed path. Good for debugging and creating paths more easily.

Published 0.1.1 to pypi: https://pypi.org/project/lisdf/0.1.1/


Avatax plugins should have own tax rate models

Avatax uses the cache to store data about tax rates. We should create new models for storing this data and drop usage of cache as we don't need them anymore.

Closing as plugins are getting deprecated and won't be developed anymore.


Running in RHEL

Didn't work
I am not sure if it's specific to ubutu, you need to mention
it did bunch of things and than removed containers

Can you explain what happened? I am unable to understand how it will remove containers. Moreover, the base image I am used is debian. I crafted the Dockerfile such that it would help me build a docker image with hadoop & hive together to ease my test process.


The system log is always loading, and many network-related plugin settings pages have errors!

The system log is always loading, and many network-related plugin settings pages have errors!
/usr/lib/lua/luci/ccache.lua:70: error loading module 'luci.model.network' from file '/usr/lib/lua/luci/model/network.lua':
/usr/lib/lua/luci/model/network.lua:1485: ')' expected near '!'
stack traceback:
[C]: in function 'loader'
/usr/lib/lua/luci/ccache.lua:70: in function </usr/lib/lua/luci/ccache.lua:61>
[C]: in function 'require'
/usr/lib/lua/luci/model/cbi/nlbw/config.lua:8: in function 'func'
/usr/lib/lua/luci/cbi.lua:66: in function 'load'
/usr/lib/lua/luci/dispatcher.lua:1232: in function '_cbi'
/usr/lib/lua/luci/dispatcher.lua:916: in function 'dispatch'
/usr/lib/lua/luci/dispatcher.lua:440: in function </usr/lib/lua/luci/dispatcher.lua:439>
/usr/lib/lua/luci/ccache.lua:70: error loading module 'luci.model.network' from file '/usr/lib/lua/luci/model/network.lua':
/usr/lib/lua/luci/model/network.lua:1485: ')' expected near '!'
stack traceback:
[C]: in function 'loader'
/usr/lib/lua/luci/ccache.lua:70: in function </usr/lib/lua/luci/ccache.lua:61>
[C]: in function 'require'
/usr/lib/lua/luci/model/cbi/mwan/globalsconfig.lua:4: in function 'func'
/usr/lib/lua/luci/cbi.lua:66: in function 'load'
/usr/lib/lua/luci/dispatcher.lua:1232: in function '_cbi'
/usr/lib/lua/luci/dispatcher.lua:916: in function 'dispatch'
/usr/lib/lua/luci/dispatcher.lua:440: in function </usr/lib/lua/luci/dispatcher.lua:439>

The system log is always loading

Not related to LuCI.
Caused by ubus and/or libubox update yeasterday by @ynezz
Discussed in http://lists.infradead.org/pipermail/openwrt-devel/2019-December/020840.html

many network-related plugin settings pages have errors!
/usr/lib/lua/luci/ccache.lua:70: error loading module 'luci.model.network' from file '/usr/lib/lua/luci/model/network.lua':
/usr/lib/lua/luci/model/network.lua:1485: ')' expected near '!'

Likely caused by commit 72247ee09f17fe1f7  in #1951 that was merged yesterday.
Fix proposed in #3434

This is indeed a plug-in problem, but the system log is still loading, this problem has not been fixed

The system log loading is caused by hanging logread which in turn is caused by libubox updates in OpenWrt master.


Make the output reproducible.

Whilst working on the Reproducible Builds effort [0], we noticed
that yardoc generates output that is not reproducible due to the
use of a fallback glob that relies on (non-deterministic)
filesystem ordering.
[0] https://reproducible-builds.org/
Signed-off-by: Chris Lamb<EMAIL_ADDRESS>Description
Describe your pull request and problem statement here.
Completed Tasks

[ ] I have read the Contributing Guide.
[ ] The pull request is complete (implemented / written).
[ ] Git commits have been cleaned up (squash WIP / revert commits).
[ ] I wrote tests and ran bundle exec rake locally (if code is attached to PR).

You would have to sort the globs, not the entire list. One of YARD's features is allowing manual ordering of the source list.

(This is also filed in Debian as https://bugs.debian.org/849972)

Coverage remained the same at 93.483% when pulling 1c4476da0baebeef0e5611ffc35f4f5376b33ab2 on lamby:reproducible-output into e8fb64aa05e50584e355b7aa2f5d1a50afe48540 on lsegal:master.

sort the globs

Well, surely expand the default glob and sort only that, not sort the glob itself? ;)

Well, surely expand the default glob and sort only that, not sort the glob itself? ;)

Yes, I meant that. Also note that it is already being sorted, but by length-- that has to stick around too.

Ah, interesting. My Ruby isn't that great alas - would a patch be easy for you to prepare? Happy to test it.

Sure. If you close this and open an issue for the bug we can track it there.

Closing as requested in favour of https://github.com/lsegal/yard/issues/1049


infinite loop

https://github.com/mitmproxy/mitmproxy/blob/61236759ce468268c58fed66a253df23c0447d62/mitmproxy/net/tcp.py#L620 infinite loop occurs when r=[]
This problem occurred when executing browser.close() twice by mistake

Please follow the bug report template when reporting a problem.

I just searched the error on google and reported it on the first github result thinking I was reporting it on pyppeteer project... WOW, sorry...
It turns out that the result was correct but the error is not pyppeteer related.
Where's "the bug report template" ? I couldn't find it.

No need to open a bug. The code you are pointing at will be removed in the next release anyway.


Modal: Body - Fix logic and styles

Modal: Body - Fix logic and styles
This update resolves some of the integration issues we saw from
integrating it into Beacon. Tests were added to catch those
edge-cases.
Follow-up to https://github.com/helpscout/blue/pull/155

Changes Unknown when pulling 30ef523f545236da188f82ea18b53d82351cfbb1 on Modal/Body-fix-logic-and-styles into ** on master**.


Use the DSS to store per-project matrix files

The matrix service will generate per-project matrix output files in all supported formats (csv, loom, mtx, etc.).
In the short term these will be stored in an S3 bucket but in the long term they shoudl be stored in the DSS.
This will require support for different types of bundles (https://app.zenhub.com/workspaces/dcp-5ac7bcf9465cb172b77760d9/issues/humancellatlas/metadata-schema/986) so that the matrix service can create a bundle for each of its output files and notify Azul.

Once this proposal makes more progress it would be great to understand how the matrix files will be written back to the DSS, if this will use the same process as the analysis pipelines via ingest or another solution

@lauraclarke The plan is for the Matrix Service to create bundles via the DSS PUT/bundles interface and have Azul (@hannes-ucsc) subscribe to the DSS notifications for this bundle type.

It would be good to hear from you, @hannes-ucsc, @brianraymor and @ambrosejcarr if there is a plan to moving to use ingest as the analysis pipelines do. Ultimately we are likely to want to accept 3rd party matrix files associated with peoples projects and this feels like an ideal way to pilot that.
I understand starting with DSS put to expedite matters but it would be great to think longer term too

I understand starting with DSS put to expedite matters but it would be great to think longer term too

I think there is value in going through ingest in the longer term, but suspect that the overall decision will be hashed out in an RFC that springs from the prioritization of this theme: https://docs.google.com/document/d/1yRjkxdAncqC_g02QJV3bMQFy0KN6S9pCIjRBb3Uv0fg/edit
Does that seem like a reasonable place to discuss this question?

@lauraclarke, if you could have someone from MD review https://github.com/HumanCellAtlas/metadata-schema/issues/986 because I think that's currently blocking this from going forward.
Whether the matrix bundles are ingested or directly submitted to DSS could be decided independently.
@ambrosejcarr, I'm not opposed to a more generic solution but feel that an incremental approach may give tractable results earlier.

What is the difficulty with submitting this to ingest?  Is there a deficiency in ingest?  Where this does the metadata come that describes matrix? how is it linked to the rest experiments, How the does AUDR handle it?
Architectural shortcuts might be expedient, however, it would be good to understand how this should be implemented, and if the shortcuts really save time or just create problems that need to be addressed elsewhere.

+1 to @diekhans comment. I'm not sure why this ticket is in the browser repository (will the browser be doing work here?) but attempting to send matrix files directly to the DSS will add significant complexity and possibly recapitulate or duplicate a lot of ingest engineering work that will likely need to be unpicked later. Who will do metadata validation? Assignment of tracking of UUIDs and versions? File format validation? Cloud upload of files and transfer into DSS with appropriate content types? Copy-forward into bundles?
By design, submission of files to the DSS goes through ingest. But whatever actually happens, I'd expect an RFC to propose a design for this and some discussion with tech arch. This certainly seems like a substantial change and a cross-component concern.

Apparently, this is an idea on how to implement Data consumers can get analysis results for a single project, yet it has become something with blocking issues.
This needs to be raised at tech arch, as it is a cross-component issue that changes the current architecture.

The need for Q2/Q3 2019 (near instantaneous user download experience) is satisfied by humancellatlas/data-browser#364.
If the matrix service provided a "few seconds" response time to per-project matrix requests (by caching or other means) then the Data Browser could change the "matrix file download" link to interactively call the matrix service and we could remove the need to pre-generate these files in an S3 bucket.
In the longer term it may be desirable to allow matrix output files to be retained permanently (e.g. as part of a Data Release) in which case storing them as a special bundle type via the Ingestion Service may make sense. I'll repurpose this ticket towards that goal and move it to the dcp repo for further consideration.


Does react-native-config works for you on ignite?

Just wondering, Ignite already released the version with react-native-config, but I couldn't make it work.
I created the ticket https://github.com/luggit/react-native-config/issues/32 with no success, does it work for you guys?
Also Ignite released 1.7.0 with React Native updated to 0.33 did you experience this issue?
https://github.com/facebook/react-native/issues/9841
I needed to rollback back to 0.32, so my Ignite update is not full. Those are just questions, as you keep releasing new versions of Ignite, i am just wondering if I am the only one who has problems.

Hi @ruskid - Excellent work and tickets!  I love issues that are organized like this.
Let's see:
I do NOT currently have the problem with react-native-config, but we are using a branch of RNConfig that was released by @skellock - which might be a different version?
Are you igniting a brand new project, or upgrading?  If upgrading, can I talk you into running a newclear
As for the facebook ticket 9841, I did not experience this issue.  But that's regarding a fresh build of Ignite.

Be extra sure to newclear https://github.com/GantMan/mobile-commander/blob/master/bin/newclear.sh
That might be residual mess.  I find upgrades sometimes require baptism by fire :)

Tried to use newclear, still no result, config is undefined(((

@skellock  I don't know where to reply now xd you broke the system.
Yes, this is still an issue, I tested your version and 0.1.0.
I shared my app with @pedro and waiting for his reply on this. I guess you can close this ticket here, as it doesn't relate to ignite, it's just a question.

Roger.  I'm sorry.  Haha.


Can pre-trained models be shared?

Hi author，
I would like to quote your approach as a comparison algorithm, could you share the pre-trained models?
Looking forward to your reply！

+1

The pre-trained models can be downloaded from the following Baidu Net Disk link, and this link has also been updated to the readme of the GitHub code.
Files shared Baidu Net disk Link: https://pan.baidu.com/s/1Ace1zD_lUg-_KW7v_aVAOg?pwd=neg1 Extract code: neg1


run test suite also against libstd with full MIR

I have zero experience with Travis, so I will see whether my script makes any sense when Travis checks this PR. Also, I don't think this entire multi-platform-testing stuff will work out here and I am not sure what is the best way to fix that.
Someone should look at the situation with these two environment variables (RUST_SYSROOT vs. SYSROOT).

Well, that actually went better than expected. I had to make the stack overflow test less precise, because the exact point where the stack overflow happens depends on how many functions are called "between" the 'start' lang item and main, but other than that, things seem to Work (TM) now.
Maybe the compiled xargo should be cached somehow?

We could cache it, but the next nightly will break the cache

I think this only runs for the host now. Fine by me. Xargo can't generate libstd for other targets anyway.

Yeah, that's true. I tried using xargo build --target ..., but that failed. I assume it's because there is some C code being compiled here (in jemalloc)?

Nevermind. It runs the old Test suite for all targets and the Xargo one for full mir

Glad you're fine with that :)

Idk what the issue is. Just that the xargo docs state the fact that libstd can only be generated for the host

They do? Must have missed that part.^^

They did, but I got it the wrong way around. You couldn't build a sysroot for the host. But you can now


Feature/rate limits

This pull request adds 2 new features:

allow reconfiguring the rate limits through appsettings or environment variables, this allows self hosting users to set a custom rate limit
allow passing a JWT token that overrides the configured rate limits

You can generate JWT tokens in development by hitting the /dev/token endpoint (endpoint is not available outside DEBUG environments).
Documentation has also been rudimentary updated to explain self hosting users to configure the rate limits.
Additionally, it also updates the documentation to refer users to https://helldivers-2.elixus.be so that if we ever rename the project or move away from Fly.io the URL wouldn't break all applications

One discussion I'm open to is whether the domain should be under elixus.be or if we want to consider a custom domain for hosting this API (and perhaps the other projects in the organisation?)

I have also already configured a JWT signing key on Fly

then this shouldn't be merged until domain is agreed upon

@lambstream @chatterchats what domain are we thinking of setting up then?
ideally we'd communicate the new URL as fast as possible to get users migrated ASAP

@dealloc @chatterchats I think something like helldivers2.app or helldivers2-api.dev

@dealloc @chatterchats I think something like helldivers2.app or helldivers2-api.dev

Both are good, and available

helldivers2-api.dev or helldivers-2-api.dev (more in line with the org name)

I'd say helldivers-2-api.dev if it's between those 2, dash lines up with the github 😂

helldivers-2-api.dev is good for me, thoughts @lambstream?
PS: fixed merge conflict

@chatterchats @lambstream PR should be good to review now


problems with config  file.

I am having problems with the config.json file. I have installed homebridge on iMac. I am getting the following error when starting homebridge with the config.json file listed at bottom.
[3/6/2018, 4:09:21 PM] Loaded plugin: homebridge-neato
[3/6/2018, 4:09:21 PM] Registering platform 'homebridge-neato.NeatoVacuumRobot'
[3/6/2018, 4:09:21 PM] ---
[3/6/2018, 4:09:21 PM] Loaded config.json with 1 accessories and 1 platforms.
[3/6/2018, 4:09:21 PM] ---
[3/6/2018, 4:09:21 PM] Loading 1 platforms...
[3/6/2018, 4:09:21 PM] [NeatoVacuumRobot] Initializing NeatoVacuumRobot platform...
[3/6/2018, 4:09:21 PM] Loading 1 accessories...
/usr/local/lib/node_modules/homebridge/lib/api.js:64
throw new Error("The requested accessory '" + name + "' was not registered by any plugin.");
^
Error: The requested accessory 'Neato' was not registered by any plugin.
at API.accessory (/usr/local/lib/node_modules/homebridge/lib/api.js:64:13)
at Server._loadAccessories (/usr/local/lib/node_modules/homebridge/lib/server.js:264:42)
at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:86:38)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:40:10)
at Object. (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (module.js:662:30)
at Object.Module._extensions..js (module.js:673:10)
at Module.load (module.js:575:32)
at tryModuleLoad (module.js:515:12)
at Function.Module._load (module.js:507:3)
And this is the config.json file
{
"bridge": {
"name": "Homebridge",
"username": "CC:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},
"description": "This is an example configuration file with one fake accessory and on$

"accessories": [
    {
        "accessory": "WeMo",
        "name": "Coffee Maker"
    }
],

"platforms": [
    {
        "platform": "NeatoVacuumRobot",
        "email": "my neato login",
        "password": "my neato password"
    }
]

}
I have tried changing the "accessories": block different ways. Not sure what is going on. Can you give any advise. Thanks.

Good evening,
In my side i have this problem, can you help me :

`*** WARNING *** The program 'nodejs' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=nodejs
*** WARNING *** The program 'nodejs' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=nodejs&f=DNSServiceRegister
[4/18/2018, 9:19:31 PM] Loaded plugin: homebridge-neato
[4/18/2018, 9:19:31 PM] Registering platform 'homebridge-neato.NeatoVacuumRobot'
[4/18/2018, 9:19:31 PM] ---
[4/18/2018, 9:19:31 PM] There was a problem reading your config.json file.
[4/18/2018, 9:19:31 PM] Please try pasting your config.json file here to validate it: http://jsonlint.com
[4/18/2018, 9:19:31 PM]
/usr/lib/node_modules/homebridge/lib/server.js:207
throw err;
^
SyntaxError: Unexpected token : in JSON at position 11
at JSON.parse ()
at Server._loadConfig (/usr/lib/node_modules/homebridge/lib/server.js:201:19)
at new Server (/usr/lib/node_modules/homebridge/lib/server.js:57:38)
at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:26:16)
at Object. (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
`

The config.json is :
"platforms": [{
        "platform": "https://neatorobotics.com/my-neato",
        "email"<EMAIL_ADDRESS>        "password": "xxxxxxxxxxx",
        "refresh": 60,
        "extraCareNavigation": true,
        "disabled": ["dock", "dockstate", "eco"]
    }]
"platforms": [{
        "platform": "https://neatorobotics.com/my-neato",
        "email"<EMAIL_ADDRESS>        "password": "Vince28091980",
        "refresh": 60,
        "extraCareNavigation": true,
        "disabled": ["dock", "dockstate", "eco"]
    }]

Please can you give me if you have some solution?
Thank you in advance.
Vince

Good evening,
In my side i have this problem :
pi@raspberrypi:~/.homebridge $ homebridge
*** WARNING *** The program 'nodejs' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=nodejs>
*** WARNING *** The program 'nodejs' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=nodejs&f=DNSServiceRegister>
[4/18/2018, 9:19:31 PM] Loaded plugin: homebridge-neato
[4/18/2018, 9:19:31 PM] Registering platform 'homebridge-neato.NeatoVacuumRobot'
[4/18/2018, 9:19:31 PM] ---
[4/18/2018, 9:19:31 PM] There was a problem reading your config.json file.
[4/18/2018, 9:19:31 PM] Please try pasting your config.json file here to validate it: http://jsonlint.com
[4/18/2018, 9:19:31 PM]
/usr/lib/node_modules/homebridge/lib/server.js:207
    throw err;
    ^

SyntaxError: Unexpected token : in JSON at position 11
    at JSON.parse (<anonymous>)
    at Server._loadConfig (/usr/lib/node_modules/homebridge/lib/server.js:201:19)
    at new Server (/usr/lib/node_modules/homebridge/lib/server.js:57:38)
    at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:26:16)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)

And the config.json is :
"platforms": [{
        "platform": "https://neatorobotics.com/my-neato",
        "email"<EMAIL_ADDRESS>        "password": "xxxxxxxxxxxxx",
        "refresh": 60,
        "extraCareNavigation": true,
        "disabled": ["dock", "dockstate", "eco"]
    }]

Have you an idea about this problem?
Thank you in advance.
Vince

Hey, this is your only plugin right? The posted config is just the part for my plugin. In order to get homebridge working you need some basic config stuff. Here is a working example:
{
	"bridge": {
		"name": "Homebridge",
		"username": "CC:22:3D:E3:CE:30",
		"port": 51826,
		"pin": "031-45-154"
	},

	"accessories": [],

	"platforms": [{
		"platform": "https://neatorobotics.com/my-neato",
		"email"<EMAIL_ADDRESS>		"password": "xxxxxxxxxxxxx",
		"refresh": 60,
		"extraCareNavigation": true,
		"disabled": ["dock", "dockstate", "eco"]
	}]
}