Graphic needed: CHAOSS Retractable Banner

Hi Design Team 😍
We are going to be hosting our first booth at open source conferences this year and we need some signage. In particular, we are looking at getting this retractable banner printed (in the 33"x81" size).
Is there anyone that would be interested in designing a generic "CHAOSS" banner that would have the CHAOSS logo and basic design elements of our slide deck and website?
If so, here's a PDF template (I also have an .ai file too).
pdf-template.pdf
We are looking to have this ready to go to the printer by June 30, 2023.
Thank you!  :heart:

@ElizabethN do you think there are more branding materials we may need apart from the banner? @iamkingsleey will be good in leading this team

@kaxada Maybe a tablecloth in the future but that would just have the CHAOSS logo on it. @iamkingsleey advised me to open an issue but I couldn't quite remember where the best place would be - if there's a better repo let's move it there :smile:

Good thing is tagged. We can collaborate here if we get a better place we can shift the conversation.

It's okay, @ElizabethN. We'll get a few hands to deliver this before the deadline. Meanwhile, are there specific details you would like to include on each of these banners/decks? For CHAOSScon, we added sponsors, QR code, and the event hashtag.

@iamkingsleey thank you so much! Nah, this would be just a generic banner we could use at any CHAOSS event, with mostly the CHAOSS logo. I do like the idea of a QR code that would lead to the CHAOSS website, though! I also like some of the design backgrounds and elements in the website and slide deck.

Okay.

What do you think @ElizabethN? I am available to make any updates

Noted, Yeah I love the teal too @ElizabethN

Love them!! Love the teal too.

If this works then, below is a editable/printable pdf of the design. @ElizabethN

CHAOSS-Banner-Design.pdf

@iamkingsleey THIS IS WONDERFUL! Thank you so, so much for this. I'll let you know if I need anything else for this, but this PDF should work great. 🥳 😻

Anytime 👌


Code for the bert on NQ baseline and TAP method used in the paper

Could you share code for the BERT on NQ baseline and TAP method used in the paper?

The TAP submission to the internal baseline was from a different group.
That code was based on https://github.com/IBM/translucent-answer-prediction
but it was apparently modified for the submission to the TechQA leaderboard and the modified code has not been open-sourced.
The system for the BERT on NQ baseline was described here: https://arxiv.org/pdf/1909.05286.pdf
and is not open-sourced.
The reason why we released this code is because it outperforms the BERT on NQ and we could open-source the code.


有微信交流群吗

可以加一个群吗 对项目比较感兴趣

Can @Sze-qq please help?

Please ask here if you have questions or ideas! @zhangfan-algo

You can join the Discord to ask questions.
You can join the WeChat above and questions reaches me too.
Email me to schedule a discussion.


Add a license to the repository

I recently came across your project Master-Thesis-QEC-simulation and I noticed that the repository github.com/Serock3/Master-Thesis-QEC-simulation currently does not have a license specified.
Why Adding a License is Important?
As GitHub documents

Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you'll need to license it so that others are free to use, change, and distribute the software.

Would be possible to add a valid license to this repository? Probably something really OpenSource such as the Apache 2.0 license would fit really well.
Thanks!

Hello Juan. Thank you for bringing this to my attention. Of course, I want my master's thesis software to be freely available and open source, even though I didn't consider it back then. I opted for the MIT license due to its simplicity.


Add support for building WebAssembly on Mac/Linux

Currently, ILC can only produce WebAssembly on Windows because it depends on LLVMSharp, which in turn depends on a Windows build of libLLVM. There appears to be a Linux build of LLVMSharp, so the work should be to incorporate the Linux version and an associated Mac/Linux version of libLLVM into building ILC.
When this is complete, please also remove the no_unix file from tests/src/Simple/HelloWasm in order to enable the test for Mac and Linux.

Slightly off-topic, but the WASM design doc states:

While it may be possible to create a WASM RyuJIT target architecture, that's likely fairly expensive to get working and even more expensive to build WASM-specific optimizations for. If WASM becomes a major .NET usage scenario, we'd likely revisit this.

If the ultimate goal is to produce WASM by RyuJIT, should there be a separate issue to that effect?
If that's not a goal, then how is the investment on:
CoreRT -> LLVM codegen -> {Emscripten tool chain} -> wasm
better / different than:
CoreRT -> CPP codegen -> {binaryen tool chain} -> wasm?

@am11 , questions are certainly welcome. I don't have any problem with having an issue tracking RyuJIT. That said, I wouldn't say that we know whether the "ultimate goal" is RyuJIT or not yet -- that's part of why we're experimenting!
On the tool chain choices, to clarify, CPP codegen would also need to use Emscripten -- binaryen is a WASM library, but not a C++ compiler (Emscripten uses binaryen to emit WASM). The main reason we chose LLVM was that WebAssembly doesn't allow pointers to the stack, which we need for Garbage Collection, Exception Handling and other features. In order to make stackwalks possible, we had to manage our own stack, which falls out more naturally from a low-level representation than C++.
You could also imagine building the toolchain as:
CoreRT -> binaryen -> wasm
But we chose not to do that because:

It would likely mean building an optimizer from scratch
Emscripten also provides asm.js support, which would be helpful for polyfills and possibly debugging.

From a different angle, you can look at https://github.com/dotnet/corert/tree/master/src/ILCompiler.WebAssembly/src as general LLVM-based codegen for CoreRT. Most of it is pretty general, not specific to WebAssembly.

@morganbr I pushed an update to LLVMSharp which upgrades things to the most recent stable release (5.0) and also have native libraries for linux64 and osx. It's using the new 15.3 tooling for setup so all that is needed is  and it'll pick the dependencies properly.

@mjsabby , that's good to know. I believe Emscripten is currently on LLVM 4.0. Do you know if we're likely to hit compatibility issues? (The current state is also mismatched, but it's closer -- we have LLVMSharp using 3.9 and Emscripten using 4.0).

Is the contract LLVM bitcode or IR? IR has been changing somewhat recently, but the bitcode format is more stable. However, I can just create a 4.0 package and publish it so you can use that if you'd like.

It's bitcode. If LLVMSharp on 4.0 is easy and adds Mac and Linux, that sounds fantastic.

Fixed in #5297


[PY] fix: Use download url if possible in TeamsAttachmentDownloader

Linked issues
closes: #1789
Details
If download_url is available, it uses that to download the corresponding file in TeamsAttachmentDownloader. This is using the guidance here: https://devblogs.microsoft.com/microsoft365dev/working-with-files-in-your-microsoft-teams-bot/
Change details
Looks like a similar

Describe your changes, with screenshots and code snippets as appropriate

Looks like similar logic is in the C# codebase too: https://github.com/microsoft/teams-ai/blob/0534743ff7a65d7e8718111a53c0afee22179a4b/dotnet/packages/Microsoft.TeamsAI/Microsoft.TeamsAI/Application/TeamsAttachmentDownloader.cs#L83
I added a unit test and also tested it locally by sending myself a markdown file. Without this change, I got a 403 error. With this, the file was successfully downloaded.

Thanks for finding this bug and resolving it, @heyitsaamir!


feat: update prince library from official wrapper (r15)

Downloaded from http://www.princexml.com/download/prince-php5-r15.zip
ZIP update: 2016-01-05

Nice, thanks. Also closes #2 #4

This is great! Will you do a version bump for Composer users? Thanks in advance.


Remove CallOptions from uattributes.proto

The CallOptions message does not get included in any message or sent on the wire. It appears to be intended as a data wrapper for uE code interacting with the Layer 2 client API.
Since it is not a part of the actual message data model ("Layer 0"), it should be removed in favor of allowing language-specific APIs to implement the best fit for their language.

Although your statement is true, I want to know why we couldn't define it here?

Because interacting with protobuf objects is really unpleasant in situations where it is not required. It is simpler to provide a context-specific interface that takes the appropriate parameters for that situation. See UMessageBuilder in up-rust. We are mirroring that API in the up-cpp updates.
Protobuf messages intended for use as purely internal APIs are only a hindrance to defining idiomatic language APIs. This goes back to the L2 update where the required methods are listed, but their signatures are left to the language-specific APIs to define.

merged in https://github.com/eclipse-uprotocol/up-spec/pull/133

Need to reopen because the spec has not been updated yet ...

be my guest 😁

@sophokles73 we are rewriting rpcclient.adoc anyways for the new high level L2 API specifications, shouldn't we do it at that point? The only reference to CallOptions are in that file.

Closing, we will resolve reference in the L2 PR


Silent miner

“Hey, I have access to the PCs that I want to mine silently. Is there a method to make the miner invisible to antivirus software?”

If you want to reduce detections then you usually have to use crypters or protectors. Crypters can usually be found on forums while protectors are made by companies.

What do you mean with Protector?


Added download script

Question: How would we like to handle the generated python client and authlib? It's currently duplicated in both the ServalApp under samples and now in the scripts folder. I hate to have duplicate code, but it also doesn't make sense to me to combine those folders. I also hate to clutter things with some kind of shared folder. Thoughts?
Related to #233

This change is

Could the generated client be in the Serval repo itself and have a pip package?  That may be the best way to handle it.

Ok - let's just leave it as it is and keep it simple.


Add "runApp", replacing "bootstrapFactory"

One small addition, I'd love us to include a runAppAsync variant:
Future<ComponentRef<T>> runAppAsync(ComponentFactory<T> component, {
  Future<void> Function(Injector) beforeComponentCreated,
});

This is complete as of HEAD. We'll have CHANGELOG entries/docs on this soon.


Is kvrocks production ready?

Is kvrocks production ready? Is it being used in production by others as well?
Is there any benchmark?

yeah, we're running more than fifty kvrocks instances in production，but just open-source soon so I am not sure any others use it in production. the README show some benchmark metrics.

Thanks for answering. Closing this issue.


Enhancement | Sort Articles by Date & claps

Current:
All articles listed in the /blogs page are unsorted and shown in the order they were originally created. That means, the newest article is at the bottom of the page and the oldest article is at the top of the page.
Expectation:
Articles with highest claps should be at the top AND order by creation-date in descending order (newest at the top)

Can i work on this issue?

Sure


Update license attribute

specifying the type and URL is deprecated:
https://docs.npmjs.com/files/package.json#license
http://npm1k.org/

please point the PR at master and I'll merge it happily


chore: Bump FAB to 3.4.0

SUMMARY

Bumping FAB to latest 3.4.0
Changes:

dpgaspar/Flask-AppBuilder#1735 [Daniel Vaz Gaspar]
dpgaspar/Flask-AppBuilder#1733 [Ke Zhu]
dpgaspar/Flask-AppBuilder#1728 [Daniel Vaz Gaspar]
dpgaspar/Flask-AppBuilder#1707 [Daniel Vaz Gaspar]

@junlincc Please tag this for v1.4

@kamalkeshavani-aiinside FYI I updated the description to link to the PRs on the FAB GH repo (now the numbered tags were pointing to issues on this repo)

I tried the 1.4.0rc1 but the login/logout flow hasn't been fixed. I'm unable to logout. It just automatically logs in and brings me to the welcome screen. And the login flow is incorrect as well. If you have a single provider it doesn't show login UI but takes directly to enter email/pass UI(google in my case).

@usamaB  with FAB 3.3.0 that behaviour is expected, have you rebuilt your container with this commit included?


ISPN-14177 Netty 4.1.82.Final

https://issues.redhat.com/browse/ISPN-14177

Running a second build with "Image Required" so that I can easily test the changes in Openshift.

The HTTP/2 issue is verifiable even locally: just uncomment the server identity in infinispan.xml and connect with Firefox or Chrome.

Image pushed for Jenkins build #2:
quay.io/infinispan-test/server:PR-10351

It fixes the issue :+1:


rename repo to ecs-logging-nodejs

I'd like to rename this repo from ecs-logging-js to ecs-logging-nodejs. ECS-based structured logging for the browser with, AFAIK, no meaningful transport into the Stack, doesn't have value.  Of the 3 current logging frameworks supported it is possible to use one (maybe two with a shoehorn) in the browser, but it really isn't their focus. The focus is node.js usage.

Done now.


Refactoring DecodeOutput

v4l2decode.cpp related to decodehelp.h, and used the global vairables.
so now can not merge.


Documentation - Broken link to Kuesta Overview

What happened?
Got 404 error when clicked "Overview of Kuesta" at https://nttcom.github.io/kuesta-website/docs/ .

en: https://github.com/nttcom/kuesta-website/blob/main/content/en/docs/_index.md?plain=1#L13
ja: https://github.com/nttcom/kuesta-website/blob/main/content/ja/docs/_index.md?plain=1#L15

What did you expect to happen?
Transit to the overview page of Kuesta.
How can we reproduce it (as minimally and precisely as possible)?

Access https://nttcom.github.io/kuesta-website/docs/
Click "Overview of Kuesta".

Thank you for your comment.
The OVERVIEW page is currently under construction. (Due to our plans to make major changes to the architecture of Kuesta.)
We apologize for the misunderstanding. We will remove the relevant link at once.


Problems logging in with GitHub when the user has Unicode in their name

Rancher versions:
rancher/server: v1.6.2
rancher/agent: N/A
Infrastructure Stack versions:
healthcheck:N/A
ipsec:N/A
network-services:N/A
scheduler:N/A
kubernetes (if applicable):N/A
Rancher User Interface	v1.6.5
Docker version: (docker version,docker info preferred)
1.13.1, build 092cba3
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
16.04.2 LTS (Xenial Xerus) / 4.4.0-1022-aws
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
AWS
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
HA Rancher with AWS RDS external DB backend (RDS MySQL 5.6.27)
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Cattle v0.181.4
Steps to Reproduce:
The problem occurs when someone with Unicode in their GitHub user-profile name logs in to Rancher with GitHub OAuth for the first time

Set up a Rancher instance and grant it access to GitHub, setting things up so that an organisation has permission to log in.
Get a colleague that's part of their organisation but has not yet accessed your rancher instance to update their name so that it contains unicode (specific example, http://www.fileformat.info/info/unicode/char/0144/index.htm - Kopiński)
Get that colleague to try log in to your Rancher instance for the first time.
The user will get an internal server error

Note that this particular error occurs on creation of the account for the first time - but there may be similar issues that could occur if a user updates their name when they already exist. I've not tested these.
Results:
On the Rancher server, docker logs of the rancher container will show:
2017-07-17 15:27:55,835 ERROR [:] [] [] [] [.....] [i.g.i.g.r.handler.ExceptionHandler  ] Exception in API for request [https://rancher.bloomandwild.com/v2-beta/token].  Kopiński','user','...uuid-over-here....','requested','2017-07-17 15:27:55.829','{}','1584002','github_user','healthy','2']

This works fine on the default internal database, so I expect you have the wrong string encoding setup on your RDS.  utf8 character set, utf8_general_ci collation.


ISPN-8793 Server task documentation

https://issues.jboss.org/browse/ISPN-8793
One more example needs to be added that uses cached data. We have an example but it's a bit clunky due to ISPN-8814/ISPN-8815.
I'll create a JIRA to follow up once those two issues have been fixed.

Looks good to me overall. I wonder if a slightly more complex example would be better though.

I wonder if a slightly more complex example would be better though.

Of course it would and that's the plan. The PR description should have made it clear :)
I don't want to add more complex examples yet cos they'd be clunky due to the need to have separate RCMs depending on whether you're executing tasks or storing data. Once those tutorials look good them I'll add them to the documentation. Tutorials 1st, documentation 2nd. Tutorials guarantee the examples work :)

Btw, @gustavonalle told me he's planning to look at ISPN-8814/ISPN-8815 before final.

@wburns Fixed the system out.

Merged, thanks

Sounds good @galderz 👍


Support for Kailh 1232 series

Kailh released new low profile switches with an even lower total and pre travel. Unfortunately they also have a different form factor for the base.
I'm not sure they can be used in combination with the hot swap sockets but it doesn't look like.
References:

Announcement
Specification
Buy

The brown switch looks amazing, almost no pretravel. Seems to be the low profile version of the Kailh Bronze.

This switch is not general, so I decided not to use it.

But I found https://github.com/davidphilipbarr/36keys/tree/master/42Keys/chocorne low


Add docs for string methods

If this is under hacktoberfest, Can I try to work on this?

If this is under hacktoberfest, can I try to work on this?

@Kaushik-Iyer Ah this is something that has been pending for a while. Yes this is under hacktoberfest - you can work on it 👍


empty style tag in head

wondering why the script appends an empty style element into the head when we are already loading an external css from the cdn?
I've tried various configuration options to see if it resulted in any actual style rules being added there but it always seems to be empty for me.
Would be nice if the script did not add the style element unless it actually is going to add style rules there.

The tag looks empty, but they are defined dynamically via javascript, therefore it is not displayed in the dev tools.


Temporary files occupy a lot of disk space, after tikv-ctl compact cluster.

Bug Report

What version of TiKV are you using?

v3.0.5
What operating system and CPU are you using?

CentOS Linux 7.4, x86_64. Interl Xeon CPU. 64 cores CPU
Steps to reproduce

When there are too many low-level files, execute tikv-ctl compact cluster.
What did you expect?
Temporary files occupy proper size of disk space.
What did happened?
Temporary files take up a lot of space, about hundreds of gigabytes temporary files.

/severity moderate


Job Launcher - Fix balance

Description
Balance is being converted from wei to eth, but it is dollars.
Motivation
Fix error
Implementation details
Fix the error and return the right value in dollar

Was merged to https://github.com/humanprotocol/human-protocol/pull/756 as a part of the balance task.


add a CLI

Taking a shot at https://github.com/transitive-bullshit/chatgpt-api/issues/362
@transitive-bullshit you may not even want this in the project, and it definitely would need some refinement to fit the configuration of your project, but I figured I'd push it up here as a conversation starter.

This is awesome @zeke. I'm going to merge and then finesse on my end if that's cool.

Nice!


Unexpected alignments

Attached is a single read from Simpson et al. '23. The vector sequence is also attached, as well as the alignments in SAM format. There are two unexpected things about these alignments:

There are 11 reads but only 1 is marked supplementary. The other 10 are neither secondary nor supplementary. (I am using feat-44-sam-flags-and-tags branch).
Several of the alignments are contiguous without gaps - these should be a single alignment.

test_data.tgz

For reference, here are the minimap2 alignments
minimap_test.sam.gz

Fixed in https://github.com/fulcrumgenomics/stitch/pull/46/commits/c6bd79f271aca547bd5358bb9f84d2a5cbdd08bf
Also, here's some settings that penalize the jumps a bit more, which seems to make a difference.
	--jump-score-same-contig-and-strand -40 \
	--jump-score-same-contig-opposite-strand -80 \
	--jump-score-inter-contig -160 \

Let me know if this works for you and we can close this issue.

Perhaps we should change the defaults in the tool as well?

Yes, the commit fixes the flags issue, and those parameters fix the split alignment issue.
I like the idea of tuning the jump parameters individually (right now all are set to -10), but maybe we should see a few more cases before deciding. I'll open a separate tracking issue for that.


double-beep: Watch wdguideline.com

double-beep requests the watch of the watch_keyword wdguideline\.com. See the MS search here and the Stack Exchange search here.

wdguideline\.com has been seen in 1 true positive, 1 false positive, and 0 NAAs.

Approved by Makyen in Charcoal HQ


Trim trailing slash in registry path so that URL will be valid

Trim trailing slash so that path can't have consecutive trailing slashes causing URL to be invalid

@davidcorbin is there an open issue associated with this? We would want to first see the error output and registry configuration before reviewing this as a solution.

@dmcgowan Not yet but I can create an issue with config, logs and description of behavior.

Closing as caused by unrelated CNI issue


Equals signs in solution path causes CS1679 when calling CSC

It is valid for a Windows path to contain an equals ("=") sign.
Preconditions:

The solution is located in a path containing an equals sign and no spaces.
A project in the solution references another project or a Nuget package under the solution folder.

Actual Result

References are passed to csc.exe unquoted in the form /reference:C:\Development\=solution=\packages\test.dll.
The C# compiler returns CS1679: Invalid extern alias for '/reference'; 'C:\Development\' is not a valid identifier

Expected Result

The solution builds without error.

Comments
When the solution path contains spaces, MSBuild encloses the paths passed to CSC /reference in double quotes. The issue would be resolved if all reference paths were quoted, or if reference paths containing an equals sign were quoted. Currently, CSC interprets unquoted reference paths containing an equals as aliases. I suppose the issue could be fixed in CSC (first check if the entire reference switch represents a valid path, only fall back on alias behavior if it does not), but it seems more appropriate for the MSBuild Csc task to understand how to craft valid arguments to CSC.

This looks like an issue with Roslyn. Can you open this issue there? I think MSBuild is doing the right thing here and quotes shouldn't be needed around the /reference. @jaredpar let me know if you disagree here.

Even if quotes are needed around the reference, the right place for that is in the Csc task, which isn't in the core MSBuild repo.

Thanks for taking a look at this, guys.
@AndyGerlicher  - how is CSC.EXE supposed to know the difference between an alias and a path with an equals? What if I want to alias a reference that has an equals in its path? It is even possible to construct a path with multiple equals signs and commandline where it is ambiguous whether alias or direct reference is intended, without quotes. The caller who is constructing the commandline (i.e. the MSBuild Csc Task) has all of the information required to construct a valid commandline.
@rainersigwald - what's the right way to file an issue against the Csc task? Connect?

The Csc task is in Roslyn here.

Thanks! Closing this and opened another over there.


Subscription resolvers are not polled reliably

Expected Behavior
When multiple clients connect to a subscription endpoint, all of the streams should be polled correctly, such that they successfully return all data available from the source that is polled.
Actual Behavior
Instead what happens is that most of the subscribers get the latest results. But for some reason, there is almost always one or a few of the subscribers who "lag behind" and aren't sent all the entries.
I've confirmed that the data is truly not being sent (using Chrome's dev-tools).
I've also confirmed that the data (in those cases) is "being delayed from being accessed" within the async resolver functions: The resolver function is always calling my_broadcast_receiver.recv().await in a loop, for all clients' instances, but for some reason, async-graphql is not "polling" some of the futures reliably, causing some of them to have delayed/unreliable access to the latest broadcasted entries (and thus the client inherits those delays as well).
Anyway, the reason I think the issue is in async-graphql (rather than in the broadcast library I'm using or something), is that:

I have tried three different broadcast libraries (tokio::sync::broadcast, flume, and async-broadcast), and they all exhibit the same issue.
I can fix the issue merely by wrapping the future from my_broadcast_receiver.recv() in a call to this:

/// A weird but necessary workaround to resolve the issue of some futures not being polled reliably.
pub async fn make_reliable<T>(fut: impl Future<Output = T>) -> T {
    // Pin the future so it can be polled.
    let mut fut = Box::pin(fut);

    // Create a new context to be passed to the future.
    let waker = Arc::new(EmptyWaker).into();
    let mut cx = Context::from_waker(&waker);

    let mut interval = tokio::time::interval(Duration::from_millis(10));
    loop {
        // The next two lines are where the magic happens: every 10 milliseconds, poll the future...
        // ...even if the future-context "above" this function/future is not getting polled reliably
        interval.tick().await;
        match fut.as_mut().poll(&mut cx) {
            Poll::Pending => {},
            Poll::Ready(res) => {
                return res;
            },
        }
    }
}

struct EmptyWaker;
impl Wake for EmptyWaker {
    fn wake(self: Arc<Self>) {
        // do nothing; we merely need a context-object to pass to poll()
    }
}

I have taken screen captures, showing before and after with my hack/fix.
Without fix:
loop {
  let get_msg_future = msg_receiver.recv();
  let msg = get_msg_future.await.unwrap();
  send_msg_to_client(msg);
}

With fix:
loop {
  let get_msg_future = msg_receiver.recv()

  // added
  let get_msg_future_fixed = make_reliable(next_msg_future);

  let msg = get_msg_future_fixed.await.unwrap();
  send_msg_to_client(msg);
}

Steps to Reproduce the Problem
I have not yet put together a minimal reproduction case for this issue. I will likely do so at some point (if the issue is not already known), but I want to post it here first in case there's something simple I am overlooking that could resolve the issue. (I have spent several hours trying to narrow down this bug already)
Specifications

Version: 3.0.28
Platform: Linux (Debian) [my host computer is Windows, but the server is running in a debian docker container (specifically, based on the docker image debian:bookworm-slim), in a local Docker Desktop kubernetes cluster]

Thank you very much for your hard work, this problem happened before, but it was fixed later, maybe I missed something.

Did you use tokio::select! to receive messages from async_graphQL:: HTTP::WebSocket stream?

Did you use tokio::select! to receive messages from async_graphQL:: HTTP::WebSocket stream?

Well, I am not interacting with async-graphql's WebSocket struct directly, so I guess it depends on what the async_graphql_axum integration is doing: https://github.com/async-graphql/async-graphql/tree/master/integrations/axum/src
Specifically, here is the point at which I create a GraphQLSubscription instance, and hook it up to axum: https://github.com/debate-map/app/blob/3740b240c6f473cf35d3daa1630538934c1d466d/Packages/monitor-backend/src/gql_.rs#L134-L140

I've been testing for a long time but can't reproduce this issue. 😂

Okay, I will try to make a small reproduction case at some point. (Thank you for trying, even despite my repro-case laziness. 😅)

Here is the test repo:
https://github.com/sunli829/test-async-graphql-subscription

Ah nice, thanks for the starter. (I might use that and try to reproduce -- or alternately, I might start from my main project, and just keep cutting huge chunks out, to see how small I can get the repo while keeping the bug present.)


iOS support not available!

Please add support for iOS authentication. Very critical to our live app.

Hi @abdulrehmank7
Hope you are doing great!
Currently the process to add IOS SDK support to our flutter package is under evaluation. We will keep you updated regarding the progress of the same.
In case of any further questions, please feel free to reach us via our support channel https://developer.truecaller.com/support for a faster and dedicated response.
Regards,
Parth


Work Needed for Deno

I don't really know why this is on the Deno plugin ecosystem because you are supposed to have the .ts extension in import/export urls.  I advise you read the Deno Style Guide for contributing because there are a couple of conflicts with your code to the style guide.

Hi,
Yeah I tried to make this work but did not had time to finish...
I've publish a v6 and it seems to be working now... 🎉


Error installing model

On Windows, the command 'python -m caffe2.python.models.download -i squeezenet' fails with the error "'module' object has no attribute 'symlink'. It is my understanding that symlink is not available on non-Unix OSes.

I've got the script to run by replacing the line os.symlink("{folder}/__sym_init__.py".format(folder=dir_path),"{folder}/__init__.py".format(folder=model_folder)) with win32file.CreateSymbolicLink("{folder}/__init__.py".format(folder=model_folder), "{folder}/__sym_init__.py".format(folder=dir_path), 1) in download.py (and adding 'import win32file'), but when I try to import squeezenet from caffe2.python.models it fails.
I think my source and target may be the wrong way round, but if I swap them I get an error about creating a file that already exists.

I replaced the 1 flag passed to CreateSymbolicLink with a 0 and that seems to have fixed it.

@orionr When I use "python -m caffe2.python.models.download -i resnet50" to install resnet50 model, I ran into following problem:
Traceback (most recent call last):   File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main     "__main__", fname, loader, pkg_name)   File "/usr/lib/python2.7/runpy.py", line 72, in _run_code     exec code in run_globals   File "/home/ygj/caffe2/build/caffe2/python/models/download.py", line 176, in <module>     print("'{model}' is not a valid model name.".format(model)) KeyError: u'model'
I find it is because there is a small bug in line 157 of  download.py,i.e if not re.match("^[a-zA-Z_]+$", name):. '$' should be remove, otherwise the model name with num ending can't be correctly install.


Some keybidings doesn't work

When I press the format keys it says: "There is no formatter for a C# files..." or sometimes "The combination Ctrl + K, Ctrl + F is not a command". As I know is setted like this in keymap. I reinstalled and reset the keymap, but, it didn't work.
Regards

The keybinding troubleshooting guide may be helpful: https://github.com/Microsoft/vscode/wiki/Keybinding-Issues

Thank You. I will give it a try.
Regards
On Nov 13, 2017 5:57 PM, "Rob Lourens"<EMAIL_ADDRESS>wrote:

The keybinding troubleshooting guide may be helpful:
https://github.com/Microsoft/vscode/wiki/Keybinding-Issues
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/38253#issuecomment-344055280,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHFEMilSvqik2N3m16lyRESNO9HnVSJ1ks5s2K1DgaJpZM4QcXi1
.

@MAC293 We do not ship out-of-the-box with formatters for all possible programming languages. You need to search for a suitable extension that contributes a formatter for your programming language of choice.

Understood. Thank You for your help!!!
From: Alexandru Dima
Sent: Tuesday, November 14, 2017 5:51 AM
To: Microsoft/vscode
Cc: MAC293; Mention
Subject: Re: [Microsoft/vscode] Some keybidings doesn't work (#38253)
@MAC293 We do not ship out-of-the-box with formatters for all possible programming languages. You need to search for a suitable extension that contributes a formatter for your programming language of choice.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Can you recommend me a properly extension for it please?
Regards


refactor(client): replace "draftNumber" in SearchResult with "commitId"

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 8 (12.5%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 86.082%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tensorbay/client/job.py
0
3
0.0%

tensorbay/client/search.py
1
5
20.0%

Files with Coverage Reduction
New Missed Lines
%

tensorbay/client/search.py
1
33.75%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
7985

Relevant Lines:
9276

💛  - Coveralls


[CARBONDATA-2981] Support read primitive data type in CSDK

[CARBONDATA-2981] Support read primitive data type in CSDK
   1.support readNextCarbonRow
   2.support read different primitive data type in c code from java side: int double short long string
   3.support some data type and convert: date timestamp varchar decimal array<T>
         3.1 return int when read date
        3.2  return long when read timestamp
        3.3 return string when read varchar
        3.4 return string when  read decimal
        3.5 support array<string>

This PR is based on PR2738, and will remove related commit after PR2738 merged.
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[ ] Any interfaces changed?
add new interface

[ ] Any backward compatibility impacted?
No

[ ] Document update required?
Yes

[ ] Testing done
update test case in c code

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.
jira 2951

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/657/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8919/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/851/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/661/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/856/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8924/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/662/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/663/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8926/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8927/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/859/

@kunal642 OK，added

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/733/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/932/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9000/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/736/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9001/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/933/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/748/

@KanakaKumar I optimize this PR. remove change in carbonRecordReader and add static method in RowUtil.
I will raise a new PR for reading schema

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9015/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/947/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/756/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9022/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/954/

retest this please

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9028/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/960/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/764/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/767/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9032/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/964/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/771/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9036/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/968/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/775/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9040/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/972/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9041/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/973/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/778/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9043/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/975/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/779/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9044/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/976/

@KanakaKumar @kunal642 @ajantha-bhat @jackylk please review it.

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/880/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9145/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/883/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9148/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1081/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/884/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9149/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1082/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/996/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1209/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9262/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/998/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1211/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9264/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/1000/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9266/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1213/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1221/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9273/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/1011/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9276/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/1024/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/1025/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/1026/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9291/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1238/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/1035/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1248/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9300/

@xubo245 : Please update description as
readNextCarbonRow is not used and this is not depend on 2738

ok, done, please check again @ajantha-bhat

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/1038/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1251/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9303/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/1043/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9308/

LGTM


Cyclomatic complexity scripts should fail on error if the --fail-on-error CLI option is used

@tisnik Your image is available in the registry: docker pull quay.io/openshiftio/rhel-fabric8-analytics-f8a-api-gateway:SNAPSHOT-PR-33


Model performance changes when repeated

I am trying to use MedVit on a custom image. Whenever I run the model repeatedly, the accuracy of the output changes every time. Is this something expected or is there any parameter that I am missing?
All I am doing is, importing the model and doing output = model(inputs).

Hi,
There are a few steps you can take to stabilize your results when using MedVit on a custom image dataset:
1- Set a random seed: To ensure consistency in your results, set a fixed seed using torch.manual_seed() or a similar function. This will help ensure that the model initialization, data shuffling, and other stochastic processes remain consistent across runs.
2- Augmentations: If you're applying data augmentations, keep in mind that they can introduce variability in the results, which may sometimes boost accuracy or cause fluctuations. You can experiment with or control the type and extent of augmentations used.
3- Normalization: Properly normalizing your inputs to the same scale as the data used to pre-train the model can help improve the stability and accuracy of your results.
By following these practices, you should be able to reduce the variability in your model's output.


Document how to fetch data from OSM

Hi!
Having these cycle nodes in geojson is pretty cool. I do wonder however; where did you get the data from, exactly? How did you collect the network ids? I was trying to add data for more countries, but the exact query to the overpass api is missing.

Thanks, I'll go check it out.


[azure-sdk-for-cpp] Upgrade vcpkg manifest files

Update functions that are now deprecated, update manifest for better feature organization.

VcPkg team, please help me - how should I format the file, what is the command line to format it? I can't see what is wrong with the file - is it line endings, or some JSON formatting?

@JackBoosY, after adding "port-version": 1, do I need to run vcpkg x-add-version with --overwrite-version, or without? (currently I ran with it)

@antkmsft You need to revert changes in versions and rerun command x-add-version : (

@JackBoosY, got it. It actually makes sense. Thank you! I undone the changes and reran, it was not hard: git checkout origin/master versions, and then the usual vcpkg x-add-version without --overwrite-version.

LGTM, thanks for all the cleanup!


[Website] Change mailing list archive link

What is this PR for?
Change mailing list archive link from mail-archives.apache.org to lists.apache.org
What type of PR is it?
Improvement
Todos

[x] - Change link

What is the Jira issue?
How should this be tested?
Run website locally and see
Screenshots (if appropriate)
Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

LGTM

👍  Let's merge

Thanks @felixcheung @bzz I'm merging it to gh-pages and update website.


Built files reference build path

The lintian QA tool reported several file-references-package-build-path issues for the Debian package build of NetCDF <IP_ADDRESS>:

usr/bin/nccopy
usr/bin/ncdump
usr/bin/ncgen
usr/lib/x86_64-linux-gnu/libnetcdf.so.13
usr/lib/x86_64-linux-gnu/cmake/netCDF/netCDFConfig.cmake
usr/lib/x86_64-linux-gnu/libnetcdf.settings

Adding -DNDEBUG is not sufficient to fix these issues (by removing assert).
Please help make netcdf-c builds reproducible by fixing these issues.
Environment Information

What platform are you using? (please provide specific distribution/version in summary)

[x] Linux
[ ] Windows
[ ] OSX
[ ] Other
[ ] NA

32 and/or 64 bit?

[ ] 32-bit
[x] 64-bit

What build system are you using?

[ ] autotools (configure)
[x] cmake

Can you provide a sample netCDF file or C code to recreate the issue?

[ ] Yes (please attach to this issue, thank you!)
[x] No
[ ] Not at this time

Not sure what this is or how to fix. Can you provide more info or s PR with  a fix?

Here are the strings in question:
$ strings /tmp/netcdf-bin/usr/bin/nccopy | grep "/build/netcdf-<IP_ADDRESS>"
/build/netcdf-<IP_ADDRESS>/ncdump/nccopy.c
/build/netcdf-<IP_ADDRESS>/ncdump/nciter.c
/build/netcdf-<IP_ADDRESS>/ncdump/utils.c

$ strings /tmp/netcdf-bin/usr/bin/ncdump | grep "/build/netcdf-<IP_ADDRESS>"
/build/netcdf-<IP_ADDRESS>/ncdump/ncdump.c
/build/netcdf-<IP_ADDRESS>/ncdump/vardata.c
/build/netcdf-<IP_ADDRESS>/ncdump/dumplib.c
/build/netcdf-<IP_ADDRESS>/ncdump/nctime0.c
/build/netcdf-<IP_ADDRESS>/ncdump/utils.c
/build/netcdf-<IP_ADDRESS>/ncdump/nciter.c

$ strings /tmp/netcdf-bin/usr/bin/ncgen | grep "/build/netcdf-<IP_ADDRESS>"
/build/netcdf-<IP_ADDRESS>/ncgen/genbin.c

$ strings /tmp/libnetcdf13/usr/lib/x86_64-linux-gnu/libnetcdf.so.13 | egrep "/build/netcdf-<IP_ADDRESS>"
/build/netcdf-<IP_ADDRESS>/libdap4/d4data.c
/build/netcdf-<IP_ADDRESS>/libdap4/d4parser.c
/build/netcdf-<IP_ADDRESS>/libdap4/d4meta.c

$ grep "/build/netcdf-<IP_ADDRESS>" /tmp/libnetcdf-dev/usr/lib/x86_64-linux-gnu/cmake/netCDF/netCDFConfig.cmake
set(netCDF_C_COMPILER_FLAGS "-g -O2 -fdebug-prefix-map=/build/netcdf-<IP_ADDRESS>=. -fstack-protector-strong -Wformat -Werror=format-security -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 ")

$ grep "/build/netcdf-<IP_ADDRESS>" /tmp/libnetcdf-dev/usr/lib/x86_64-linux-gnu/libnetcdf.settings
Build Directory:        /build/netcdf-<IP_ADDRESS>/obj-x86_64-linux-gnu
CFLAGS:                 -g -O2 -fdebug-prefix-map=/build/netcdf-<IP_ADDRESS>=. -fstack-protector-strong -Wformat -Werror=format-security -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64

A common cause for this issue is assert which embeds the path to the source file in question into the binary. Building with -DNDEBUG should remove those calls.
If I could provide a fix, I would have submitted a patch. And as long as the CLA is required for PRs, that's the best I can do.

OK, I think  I have found the problem. nccopy uses the NC_CHECK macro, which is this:
./ncdump/utils.h:#define NC_CHECK(fncall) {int ncstat=fncall;if(ncstat!=NC_NOERR)check(ncstat,__FILE__,__LINE__);}
Note that this has FILE in it. If we took that out, I think it would solve your issue.

That looks promising indeed, perhaps only include that for (explicitly enabled) debug builds.

Fixing ncgen is going to take some time since when I built it I was not smart
enough to wrap the use of FILE.
Not sure what to do about libnetcdf.settings since it deliberately contains
build info such as this:

Build Directory: 	/cygdrive/d/git/netcdf-c
Install Prefix:         /usr/local

netCDFConfig.cmake: I do not know, but this is apparently generated
as part of a cmake build.

libnetcdf.settings is notoriously unreproducible. The Debian package already contains a patch to remove the Configured On & Host System fields, the patch will also need to remove the Build Directory field. The -fdebug-prefix-map flag is set by dpkg-buildflags and harder to fix, removing the CFLAGS field is an option or patching CMakeLists.txt to strip that flag which would also fix netCDFConfig.cmake.
I don't know which projects use the libnetcdf.settings file and what parts they rely on. A quick search for libnetcdf.settings using https://codesearch.debian.net doesn't show any users.
There was a time when libnetcdf.settings was not included in any of the resulting binary packages, and nobody complained, so we could choose to not install it at all.

Alternatively, I would be happy to update libnetcdf.settings to make it more reproducible. Whatever best serves the community :)

That would be great. Most of the General section needs to be removed to make it reproducible, only the NetCDF Version & Install Prefix aren't that problematic.

Followon PR https://github.com/Unidata/netcdf-c/pull/1327 to fix ncgen

Thanks. Confirmed fixed with ad3e3bd, that just leaves libnetcdf.so.13 and the .settings file.


Add support for setting the working directory of tasks on Linux

Glibc 2.29 will add posix_spawn_file_actions_addchdir_np. A method with
the same signature also exists on Solaris, and there is currently a
proposal to add a "posix_spawn_file_actions_addchdir" to POSIX, so
proactively re-structure the code to prefer using a
posix_spawn_file_actions_addchdir[_np] style function to set the working
directory.
We fall back to an alternate mechanism where available, or continue to
assert as before.
rdar://46069443

@swift-ci please smoke test


✨ installation.md

#24  👈
main

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

Join @RTLS and the rest of your teammates on  Graphite


(PUP-6361) Add validation error on definition names starting with '::'

A class, define, function, or type declaration that uses a name that
start with '::' is illegal. This commit ensures that such names are
trapped by the parser validator.

CLA signed by all contributors.


Register v1.0.0

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/102297
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" fd8b872c7708cb0e5fd56583b69ef45282e1bd8a
git push origin v1.0.0


Variable data length overload return types

The put*(byte[], offset, length) methods in SBE return the length, which any caller knows because its passed into the method. They could actually return this in the same way that the other methods on the encoder do. The encoding methods that take strings directly - where you don't actually know how long the encoding was actually return this and not the length.
Is this the right direction to go with the API or should they all return this.

I think this would be a good change.


Create screens in the front-end for all of our supported routes/URLs/paths

The front-end will support the following routes:

/: Landing page where users will type in a game ID, and either create a new game or join an ongoing one
/:id: Page that display's an ongoing game's state. Users will play games on this route
/create: Page to create a new game
/join/:id: Page to join a game that's already begun. Users will set their display name, choose a team to join, and jump into an ongoing game on this route

react-router routes need to be prepared for each of these routes, and new screens/react components need to be made for each of these routes.

After hacking on this a bit, I think it'll actually be more convenient to develop the front-end with only two routes instead of the aforementioned four:

/: Landing page
/:gameID: Either jump into the lobby of a game that hasn't been created yet, or join an ongoing game

This will make it easier to organize the front-end components involved, and figure out which screens to display in different scenarios. It'll also make things easier on the back-end: the server just listens for new requests on the /:gameID route, attempts to establish a Websocket connection with the client, then beams them down appropriate information along that connection, like if a game already exists with the provided gameID, and if so, who's on which team.


BIGTOP-3369: RHEL8 does not have PowerTools repo but CodeReady Builder

Update puppetize.sh to use CodeReady repo when the environment is RHEL8.
I tested this change w/ RHEL8 on AWS EC2.
Note that if you want to run puppetize.sh, you may have to add /opt/puppetlabs/bin in secure_path as noted in README.md and re-login.
(Though this is out-of-scope of this PR, should we automate this process?)

Though RHEL 8 is not our officially supported distro, this fix may be useful for some users.
I tested the PR and confirmed it worked (with adding /opt/puppetlabs/bin to secure_path in /etc/sudoers).
+1, thanks @masatana!

Thank you @sekikn !


Adding 'Edit with VS Code' to main branch

Pull Request Checklist
Go through the check boxes given below and make sure you mark the relevant ones.
To check put x inside [ ] eg. [x] Extension
Is your project an

[x] Extension
[ ] Application

Given below are the mandatory requirements we expect from your project. Your Pull Request will be reviewed only if all the minimum requirements relevant to your project are satisfied.

[x] Added readme.md to my project folder with relevant information.
[x]  I have provided the demo video link (showing the functionality in action) or the public deployment link of my extension of application within the readme.md (if Applicable).
[x] I have explained the process in a readable manner within readme.md.

Terms and Conditions
Plagiarism check from Team Crio will be solid and if your code is found to be plagiarized, the team has every right to reject your Pull Request and take necessary actions.

[x] I can assure you that this is my own contribution and I did not involve in any kind of plagiarism activities.

Buckle up and wait till you recieve communication from the review team. Keep a tab on this pull request page for comments on your project. Any necessary suggestions will also be provide here. All the best :)
Once your PR get's merged, take some time ⏲, celebrate 🥳 and share it with the community on slack.

Hey, @Apprentice76 kudos to your hard work, please go through the below notes:

It will be easy for us to review the pull request if you don't add the project as a submodule.
To do so:
Fork this repo,
Clone to your local machine
Add all files other than the .git folder

make sure you add folders like .vscode, .DS_Store which are not relevant on other machines in .gitignore and not add it the repo

Make sure to provide a readme.md file explaining the project as a whole

The deadline has been extended so feel free to add more features or changes to the extension and improve the code readability in any way possible.
Cheers,
Aayush

You will have to make a new pull request for this work.
Feel free to add your thoughts and doubts if you have any in the comments or on slack.
closing this pull request as of now.

Ok, I'll remove it as submodule and create a new PR

@Apprentice76  will have to make a new pull request for this work.
Closing this pull request!
waiting for your new pull request :partying_face:


feat(ci/cd): Changed lintstaged to prettier-check, also added format and format:fix script, and also added check.yml for prettier & eslint github action

I have changed lintstaged to prettier-check so it checks instead of fix/format when someone runs git commit. Also added format and format:fix script in package.json. And also added a check.yml in .github/workflows/check.yml for running prettier and eslint check when someone makes a PR request.

#15

Squashed all 4 commits into one


Update tr.coffee

Hello, @ecemm! Thank you for contributing. Can you sign our CLA so that I can merge your pull request?

Hi @Imperadeiro98! I signed the CLA. Can you please merge it?

Thanks


Feature Request: Exclude parts of code from coverage

Forgive me, if this is a stupid request, but I have almost no experience in test driven developement and I'm just getting started with Rust.
But I have a simple program, with some functions I don't want to test. For example the main (), which changes a lot and is basically a few lines of "glue" code for functions from other modules.
I think a way to exclude such code from coverage with a rust attribute or a command line argument could help focusing on other parts of the code which are really lacking test coverage.

 The next release of tarpaulin will let users exclude files from coverage (with wildcards!) But not parts of a single file.
So next release or if you want to use the current development one you could exclude main.rs. I have considered this but am loathe to make people tag comments into code, I don't think a coverage tool should change how the code base looks, so I'll look into other solutions!

I'd suggest using scoped attributes in Rust so it'd look like:
#[tarpaulin::exclude]
fn foo() {}

I believe that's nightly only still however.
As to your general feeling of how coverage tools shouldn't affect the source code.. consider how rustfmt affects the source code indirectly if I mark a function with rustfmt::skip; and, consider that if I had functions which simply aren't called during tests then the current approach (exclude a file) would require me to restructure my code to keep such functions in their own file.

@mehcode  I'll look into adding attributes as I prefer that as a solution instead of comment tags like kcov uses.

So scoped attributes are also referred to as tool attributes and are only available for tools packaged with rustup (so clippy and rustfmt are the only ones using them current afaik). However, there is a solution cfg_attr.
Now users can put #[cfg_attr(tarpaulin, skip)] over modules, functions, traits, impls, and methods to remove those blocks from coverage results. This has been implemented along with a full suite of tests and merged into develop if you want to use it early. If not I'll probably release 0.6.1 near the end of the week.
Cheers @mehcode for pointing me in the right direction :+1:


Thanks!

Not an issue, but i wanted to say thanks for this library and your efforts to keeping it up to date.  The types annotations, docstrings are extremely useful! 🙏🏽

Thanks for the comment!  I do try to document as much as I can.  :-)


clear cached "actionsById" on ActionTypes.COMMIT

Committing creates a clean slate, however initialLiftedState.actionsById is left with old actions leaving an unnecessary memory footprint

That's a good catch, but this problem will also occur for RESET, ROLLBACK , IMPORT_STATE and any other action that affects actionsById. It's happening because we're mutating this object, but this shouldn't affect initialLiftedState.
What do you think of the solution I've implemented in https://github.com/zalmoxisus/redux-devtools-instrument/pull/2/commits/48478e14de81af87c2fddf2d04024c5814f0bac8?


Max vertices error

After running:
fbx-conv -p -v "path to file"

FBX-conv gives me a warning that there are too many mesh vertices. So I try setting the maximum allowed indices with this command:
fbx-conv -p -v -m 64k "path to file"

It prints the warning again and tells me the max is now "64." If FBX-conv does not accept *k numbers then please do not put them in the help printout. So I ran:
fbx-conv -p -v -m 64000 "path to file"

Now what does it do, it says "Error, maximum vertex count must be between 0 and 32k"
This is annoying, as now I have to go back into my model editor and split up the node.
So in conclusion, please make FBX-conv accept *k numbers, and please make it accept larger vertex counts if possible.

Is it still the case that libgdx uses signed short indices? Is there no way to have more than 32k triangles in a mesh?

So this explains why I am not able to load complex models... @xoppa, why does libgdx use signed short indices?
Is there any workaround so I can load models like this one: http://tf3dm.com/3d-model/sa342-gazelle-97281.html ?
Thanks!

Because java doesn't support unsigned short. Don't expect random high poly models to work. Use low poly models instead.

Thanks @xoppa, and Merry Christmas!

Hi guys, I started use libGDX for our project, but limitation 32k is too small for us.
If I fork engine and change all short values for example to int does it work good?
Or short value is system restriction?
Can somebody explain me please?


Two questions about image rendering

Hi,
Thanks for open-sourcing this great benchmark! I have two questions regarding image rendering and hope you can help with. Thanks!

I think it has been mentioned that the rendered image is up side down for some systems. However, do I also need to flip the left and right side of the image? Because I notice that for some tasks, the expert trajectory involves rotation that is opposite to the language discription of the task. E.g., for the task faucet-open-v2, Appendix A of the paper says that this task "rotate the faucet counter clockwise". However, the rendered video rotates the faucet clockwise as shown below. So I want to check that if left-right flipping is also needed? Or is it an issue with the language instruction itself?

https://github.com/user-attachments/assets/21144221-1435-49cb-afb8-1fd3192121e5

I notice that there are some small spheres with different colors and sizes in the rendered image. Intuitively they seem like some reference points for things like goal positions? I was wondering that what rules are followed to generate these spheres? And will their colors change with parametric variations inside each task?

Thanks for your help!

Hi! 1. It be just code drift through the years that switched the close and open descriptions. You shouldn’t need to do anything else to the video, other than flip it
2. Yes those should change with the parametric variations!


ImageStyle Person card in documentation is not aligned properly

The Try it yourself button is showing on top of the person image.

Thanks, this should be fixed now if you refresh the page :)


du: use USimpleError instead of set_exit_code

Fixes #3389
@tertsdiepraam is this what you meant? I found that UResult is meant to be returned at the end, but since we want to display the errors quickly, during the path traversal, we probably want to use USimpleError.

It's close! The use of show! is definitely correct and it's nice that it's using USimpleError. My initial thought was to use UIoError and print that with show!. For example, the first change can become:
show!(e.map_err_context(|| format!("cannot read directory {}", my_stat.path.quote()));

The second case becomes something similar (the whole match on the error kind can be removed)

Is there anything else I should work on, or are we cleared for merging?


Bug: Traveller has disappeared from the "add new character" list

If you don't already have the Traveller added you can't add her.
If you delete her you cant re-add her.

Wait. It's some weird interaction with the new filter system:
You have to filter by sword, anemo AND geo:


ci: fetch only locked dependencies

[ ] Added an entry to CHANGELOG.md if this change could be valuable to users

Codecov Report

Merging #1965 (cbce92e) into master (95582c3) will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #1965      +/-   ##
=========================================
+ Coverage    8.97%   9.01%   +0.03%
=========================================
  Files         133     133
  Lines       57490   57227     -263
=========================================
- Hits         5161    5160       -1
+ Misses      52329   52067     -262

Impacted Files
Coverage Δ

lapce-data/src/keypress/keypress.rs
73.02% <0.00%> (-0.21%)
:arrow_down:

lapce-ui/src/app.rs
0.00% <0.00%> (ø)

lapce-ui/src/tab.rs
0.00% <0.00%> (ø)

lapce-ui/src/title.rs
0.00% <0.00%> (ø)

lapce-data/src/data.rs
0.00% <0.00%> (ø)

lapce-ui/src/editor.rs
0.00% <0.00%> (ø)

lapce-ui/src/window.rs
0.00% <0.00%> (ø)

lapce-data/src/proxy.rs
0.00% <0.00%> (ø)

lapce-data/src/title.rs
0.00% <0.00%> (ø)

lapce-data/src/rename.rs
0.00% <0.00%> (ø)

... and 8 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

What is the benefit of this, just for my understanding?

It should not grab latest transitive or direct dependencies which are not locked to full version.


drivers: dai: ssp: clear RSE bits on ACE

On ACE RSE bits should be cleared unconditionally if ssp is no longer in use
This will allow to successfully disable SSP in dai_ssp_pm_runtime_dis_ssp_power() and enable it correctly in the next run

@nashif @galak this one fixes a release blocker.


Translating(ES) docs - advanced guides

I finished Spanish translations for the Advanced section.
I wasn't sure about what writing style to use so I chose a pretty informal one, is this something we want to keep doing?
Please let me know of any typos, or if there is anything that can be explained better in another way.

#152


New command: get information about the specified file

Get information about the specified file

command: spo file get -w|--webUrl <webUrl> -u|--url [url] -i|--id [id] --asString --asListItem
webUrl: The URL of the site where the file is located
url: server- or site-relative URL of the file
id: file ID
asString: retrieve the contents of the specified file
asListItem: retrieve the underlying list item
either url or id must be specified to retrieve the file, but not both
if the asString and asListItem properties are not specified, retrieves the properties of the file object
requires connection to a SharePoint site

For more information see the Get-PnPFile cmdlet

@waldekmastykarz can I pick up this one too?

All yours! Awesome! 🎉


Merge some of the crates (probably only rustup and rustup-dist)

Split out from https://github.com/rust-lang/rustup.rs/issues/1611
The current crates tree is:
rustup-win-installer
└── rustup
    └── rustup-dist
        └── rustup-utils
            └── download

[dev-dependencies]
└── rustup-mock

WDYT about squashing that down to:
rustup-win-installer
└── rustup

And the only reason to keep those separate is because I can't run rustup-win-installer with its build.rs.  WDYT?

:+1: I'm keen on this and have contemplated something similar myself in the past. I'd also be keen to turn Rustup into a workspace, rather than a bunch of separate crates. I think it might make sense to keep rustup-mock separate since it is only used for testing and is quite different from the rest. I think it might also make sense to keep download separate, if it can be a strongly encapsulated crate (ideally shared with Cargo).

Ok I'll make it a workspace and keep download separate.  But rustup-mock I was just going to have as a module of the rustup tests (much like the "support" module in cargo's testsuite).

Root layout-wise @kinnison prefers
/Cargo.lock
/Cargo.toml
/src/ (the sources of the rustup crate)
/download/ (the separate download crate)

The code in rustup-mock would either become #[cfg(test)]-gated code in the rustup crate, or directly a module in the tests.


display manager: use extensible option types

Motivation for this change
Use a more adapted option type for display manager settings.
This PR is the first in a series to use extensible option types when relevant.
Advantages:

The type used for displayManager.enable, nullOr enum, enforce the restriction that only a single display manager can be enabled.
This change is fully backward compatible. If the previous displayManager.foo.enable is used, it is automatically translated in the new setting and display a warning message.

Notes:
I am not sure of the naming of the new option, displayManager.enable, as enable options are usually used with booleans.
There might be more appropriate option name, and suggestions are welcome!
This PR has 2 commits, the first one change only so display manager related module system and can be used to test backward compatibility.
The second update the display manager usages in the tests and other places.
cc: @edolstra @nbp
Things done

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

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

I am not sure of the naming of the new option, displayManager.enable, as enable options are usually used with booleans.
There might be more appropriate option name, and suggestions are welcome!

available?

maybe services.xserver.displayManager.selected = "kdm"; ?

ping @edolstra @nbp
Any thoughts on this, so far the list of propositions for this kind of option name are:

enable
enabled
select
selected
manager
managers
available

Update: fixed the conflicts.

@ericsagnes I guess the next step is to rewrite this code using extensible option declaration, with the enum type (#18380), correct?

@nbp I am not sure to understand, this PR is a rewrite of displayManager.*.enable options to use extensible option types (displayManager.enable with a nullOr enum).
For example: Main declaration, extended declaratations.

Ok, sorry I did a quick walkthrough and only noticed https://github.com/NixOS/nixpkgs/pull/20271/files#diff-05435704a2787433f3120047d8dc2b35R319 , which made me think that these were still the old changes. I will try to review it over the week-end.

Thanks for the detailed review and the precise advices, you are always very helpful!
I added the requested changes.
Next step is to use extended option types for desktopManagers and windowManagers to have a consistent xserver configuration.
As making a dedicated PR for each would result in some noise for unstable users, I propose to extend the scope of this PR so it contains desktopManager and windowManager too.
It will also make it easier to document the whole changes and check that all the tests are passing.
I will request another review when everything ready.

Added commits for desktop managers and window managers.
@nbp The PR is ready to review, could you please review it again when you have some time?

Passing the following tests, unchecked means failure:

[x] test.gnome3
[ ] tests.gnome3-gdm
[x] tests.i3wm
[x] tests.plasma5
[x] sddm.default
[x] sddm.autoLogin
[x] slim
[x] xfce

gnome3-gdm was also failing on the latest nixos-unstable (http://hydra.nixos.org/build/53595717), so I suppose the failure reason is not related to this PR contents.

I admit I am not fond of the windowManagers.select and desktopManagers.select changes, as opposed to the displayManager.select option which expect a single result.

I do agree that it does not feel like the perfect solution, but still it is an improvement over the current desktopManager.*.enable and desktopManager.default combination that was requiring extra checks to verify the default desktop / window manager was enabled (and also checks in other modules).
I am open to change this approach to any better solution.

I hope that most NixOS user would never have to learn about mkIf, mkOverride, or mkOrder.
Thus, I am highly worried about the order of the window / desktop managers, as this is an option which is quite visible to new desktop users of NixOS.  While I do not expect new users to split their modules them-self, I would still expect to have new users import someone else configuration.
Before, importing someone configuration would raise an error message about the fact that the option is defined twice.  In this new case this would pick one at random.
I think it would be better to have each window / desktop manager define what is their default display manager with mkDefault, and raise an error if we do not have a uniquely preferred display manager as the result of the merge.  Thus, a user having selected both KDE and Gnome would be prompted to select a display manager as there is no guessable default.
What do you think?

I see it's been a while since this was last commented on but the final suggestion where each configuration comes with a sensible default that I can override makes sense to me.  Have we propositioned the community via IRC and discourse to gain more thoughts around this interface?  Alternatively, has this work been abandoned and this pull request should be closed?

This has changed in 20.03 and is incompatible with this PR.


[$500] App does not display proper result directly on inserting spanish letter in mention (works fine on search)

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:
Precondition: One of the user should have spanish l letter in display name

Open the app in mac safari/ mac chrome
Open any report
Click @ and insert spanish letter which any of the existing known user has in its display name (to directly insert that letter, long press on that letter in keyboard, it will display spanish option, select it using that option number)
Observe that app does not display proper results for that spanish letter, instead it displays results for its english equivalent
Copy that letter, erase it and paste after @
Observe that now app displays proper mention result
Try similarly in search i.e. open search, long and insert Spanish letter as mentioned in step 3 and observe that app displays correct results directly

Expected Result:
App should display results according to inserted Spanish letter as it does on search
Actual Result:
App does not display results according to inserted Spanish letter in mention
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.77-2
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/0713e5d2-4642-4141-857e-85051eb695a6
https://github.com/Expensify/App/assets/43996225/8b256c5c-30ae-46a4-bf6e-8b88ec77bb52
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695036943283459
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01c8bbf298d69a89ce
Upwork Job ID:<PHONE_NUMBER>610187776
Last Price Increase: 2023-11-07

@tienifr Can you confirm this problem with the latest main?

Not overdue, looks like this has been resolved (unable to reproduce)

Not overdue, looks like this has been resolved (unable to reproduce)

Issue not reproducible during KI retests. (First week)

Not overdue, let's wait for the second week of KI tests

Issue not reproducible during KI retests. (Second week)

Not overdue, I think we can close this one since it's not reproducible 2 weeks in a row

Issue not reproducible during KI retests. (Third week)

Not overdue, this one was resolved and can be closed

Same as above
@kavimuru, could you close this one please?

Issue not reproducible during KI retests. (4th week)

Not overdue, looks like the issue isn't reproducible anymore and can be closed
@kavimuru, could you close this one please?

Issue not reproducible during KI retests. (5th week) Closinf


Malayalam support added and multiple correction in 4 existing Indian languages

Adds Malayalam language support
Multiple correct in 4 additional language - Hindi, Marathi, Telugu, Kannada

Added few missing quotes etc.


coreboot-toolchain: 24.08 -> 24.12

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg build coreboot-toolchain.i386

@NixOS/nixpkgs-merge-bot merge

@jmbaur While on it, could you add another patch for moving it into the by-name structure?

@jmbaur While on it, could you add another patch for moving it into the by-name structure?

What do we think that would look like? Since coreboot-toolchain is an attrset of derivations, I don't think it's immediately transferable to pkgs/by-name without some restructuring.


last stable release in v0.16?

I propose to have a stable release in 0.16 branch. That is to have external gems to depend on precise version rather than follow master all the time if they want some features and happy with current master.

Myself or @digitalextremist can do a release of the https://github.com/celluloid/celluloid/tree/0-16-stable branch as soon as all relevant commits have been cherry-picked onto it. Are there things you want in another 0.16 release that aren't presently on the https://github.com/celluloid/celluloid/tree/0-16-stable branch?

I don't have anything in mind. I just want to have a stable release of dcell before it moves to 0.17.

I propose we release 0-16-stable as 0.16.1.pre then and request that Sidekiq users test it.

@tarcieri As long as you start with Square.  :-P

:smile: I can try eating our own dogfood there first

Would it be OK with the world if we did this after getting 0.17.0 to prerelease? With that, there's the hardening of 0.17.0 itself, but also the backported version of that prerelease. Doing a 0.16.0 stable will effectively be 3 releases. I'm good with this, but it'd be nice if we cherry picked once the next release is able ready, rather than adding another step before 0.17.0 is ready to cut an RC of.

I don't mind if it be out after 0.16.

You mean 0.17.0 right?
I am asking that we do this:

0.17.0.rc1 ( no backport mode )
0.17.0.rc2 ( with backport mode )
0.16.1.pre1 ( as requested here )
0.17.0 ( final )
0.16.1 ( final )

@digitalextremist yes, I meant 0.17.

Seems ok

This was cut to its own branch before 0.17.5 proceeded in master


PHP Magic Number Detector

No description from Asana

Added: https://github.com/vatu-team/workflows/blob/6ce27966301dd9cf1239d6cc3539607ca62c099e/.github/workflows/php-magic-number-detector.yml


⚠ Samsung has degraded performance

In 6e000ae, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2432 ms

Resolved: Samsung performance has improved in 7cf5f4f.


[JS] react project Cannot find module: 'swiper'. Make sure this package is installed.

c:\repo\my-app>npm run build

><EMAIL_ADDRESS>build
> react-scripts build

Creating an optimized production build...
Failed to compile.

.\node_modules\adaptivecards\lib\carousel.js
Cannot find module: 'swiper'. Make sure this package is installed.

You can install this package by running: npm install swiper.

Repro steps:
npx create-react-app my-app --template typescript --use-npm
npm i<EMAIL_ADDRESS>--save

then modify app.tsx
import React from 'react';
import logo from './logo.svg';
import './App.css';
import { AdaptiveCard } from "adaptivecards-react";
var card = {
  "type": "AdaptiveCard",
  "version": "1.0",
  "body": [
      {
          "type": "TextBlock",
          "text": "Here is a ninja cat"
      },
      {
          "type": "TextBlock",
          "text": "Here is another ninja cat"
      },
      {
          "type": "Image",
          "url": "http://adaptivecards.io/content/cats/1.png"
      }
  ]
};

var hostConfig = {
  fontFamily: "Segoe UI, Helvetica Neue, sans-serif"
};

function App() {
  return (

      <AdaptiveCard payload={card} hostConfig={hostConfig} />

  );
}

export default App;

This is an issue with how the adaptivecards package declares its dependency on swiper. It should probably be a peerDependency:
https://github.com/microsoft/AdaptiveCards/blob/d0beb67cc1d3affe7847bc6ffc21e40dd7a5d0f2/source/nodejs/adaptivecards/package.json#L47
alternatively, adaptivecards-react could import adaptivecards through the dist folder, which has swiper bundled in to it


feat: use Spring Validator when available

The EndpointInvoker gets the Spring ApplicationContext as constructor parameter, so we can use the Spring Validator Bean instead of the explicit one.
Closes #964.

I see in the issue that you're using Hilla 1.2. That version is not maintained anymore. We can consider backporting down to 1.3 if that can help.

Hi. We are currently evaluating the possibility to upgrade to Hilla 2, but that might take some time. In the meanwhile we intend to use the latest stable 1.x, so making that feature available there would be of great use to us

Hi. In what 1.x version can we expect this to be included? We will be staying on 1.x (latest with regular upgrades) for a while

@gitgdako thanks for asking. Now that this change was backported to the 1.3 branch, it will be included in the next maintenance release, v1.3.15.

Code is working as expected in 1.3.15
Imo this issue is resolved


Update sql-database-cloud-migrate-compatible-export-bacpac-ssms.md

Removed duplicate and irrelevant image from step 2 as it does not fit into description.

Hi @kmataru, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@kmataru - Hi, thanks for your contribution. We are in the process of refactoring the Azure technical articles, so we can’t merge this PR. When the refactoring is complete, we can give you a link to the new location of the article you updated so you can resubmit your update, if you want to.

@kmataru - Thanks for your contribution. We are in the process of refactoring the Azure technical articles, so we can’t merge this PR. When the refactoring is complete, we can give you a link to the new location of the article you updated so you can resubmit your update, if you want to.

@kmataru - Thanks for your contribution to the Azure docs. On November 16th, we announced the availability of our Azure technical documentation in a new location on docs.microsoft.com. You can read about it on our team blog. This change means the article source lives in a new GitHub repository. Because there are some changes in the source markdown as a result of the move, we can’t pull your contribution over to the new repo without creating a ton of merge conflicts. We invite you to resubmit the change (if you are willing) to the new version of the article at https://docs.microsoft.com/en-us/azure/sql-database/sql-database-cloud-migrate-compatible-export-bacpac-ssms. Thanks for your understanding.


Compat Level dropdown value order for New Database dialog is inconsistent

Starts off at 160, then jumps down to 100 and goes up from there. We should probably be ordering it high -> low and then just selecting whatever the current level is from the list.

also collation is oddly collated :)

SSMS selects the current version as the default value IIRC. Since we don't have access to the dropdown options in STS, putting that value first in the list was an easy way to implement it.


Using buoy data available in text format, without converting to HDF5 format

Hello,
I want to run WDRT "Environmental characterization" using buoy data in text format, not available in HDF5 format:
datetime,swh,hmax,tmax,pp1d,mwp,mwd,wind,dwi
2000-01-01 00:00:00,1.37917,2.61388,7.23188,13.4037,9.04123,316.967,6.375,9.13326
2000-01-01 01:00:00,1.38438,2.62504,7.15882,13.3719,9.00193,317.464,6.21826,12.5801
2000-01-01 02:00:00,1.38507,2.62535,7.16642,13.3329,9.02032,317.525,6.00977,15.5671
(...)
How to obtain the environmental contours of significant wave height (swh) and peak period (pp1d), without converting the data into HDF5 format?
Thank you, regards, Ricardo.

Hey WDRT is now a part of MHKiT. Please check out these examples and ask any questions you may have on the MHKiT repository.
https://github.com/MHKiT-Software/MHKiT-Python/blob/master/examples/environmental_contours_example.ipynb
https://github.com/MHKiT-Software/MHKiT-Python/blob/master/examples/extreme_response_MLER_example.ipynb
https://github.com/MHKiT-Software/MHKiT-Python/blob/master/examples/extreme_response_contour_example.ipynb
https://github.com/MHKiT-Software/MHKiT-Python/blob/master/examples/extreme_response_full_sea_state_example.ipynb


Dark Mode Issue with Material-UI v5

I followed the tutorial/example available at https://next.material-ui.com/customization/palette/#heading-dark-mode to implement a dark mode toggle, however, there seem to be a big issue with the merging of my custom theme with the updated mode returned by createTheme.
Here is my code:
color-context.js:
import React from 'react';

export const ColorModeContext = React.createContext({
  toggleColorMode: () => {
    // This is intentional
  },
});

MarketingBar.js:
import { IconButton, Toolbar, Box } from '@material-ui/core';
import {
  Brightness7,
  Brightness4,
} from '@material-ui/icons';
import React from 'react';
import { useTheme } from '@material-ui/core/styles';
import { ColorModeContext } from '../config/color-context';

export default () => {
  const theme = useTheme();
  const colorMode = React.useContext(ColorModeContext);

  return (
    <Toolbar variant='dense'>
      <Box
        sx={{
          display: 'flex',
        }}
      >
        <IconButton
          onClick={colorMode.toggleColorMode}
          color='inherit'
        >
          {console.log(theme.palette)}
          {theme.palette.mode === 'dark' ? (
            <Brightness7 />
          ) : (
            <Brightness4 />
          )}
        </IconButton>
      </Box>
    </Toolbar>
  );
};

App.js:
--- SNIP ---
import MarketingBar from './layout/MarketingBar';
import React from 'react';
import Hero from './components/Hero';
import {
  ThemeProvider,
  alpha,
  styled,
  createTheme,
} from '@material-ui/core/styles';
import { theme as customTheme } from './styles';
import { ColorModeContext } from './config/color-context';

--- SNIP ---

export default () => {
  const routeResult = useRoutes(routes);

  // eslint-disable-next-line no-unused-vars
  const [mode, setMode] = React.useState('light');
  const colorMode = React.useMemo(
    () => ({
      toggleColorMode: () => {
        setMode((prevMode) =>
          prevMode === 'light' ? 'dark' : 'light'
        );
      },
    }),
    []
  );

  const muiTheme = React.useMemo(
    () =>
      createTheme(customTheme, {
        palette: {
          mode: mode,
        },
      }),
    [mode]
  );

  return (
    <ColorModeContext.Provider value={colorMode}>
      <ThemeProvider theme={muiTheme}>
        <Root scheme={muiLayout}>
          <CssBaseline />
          <TopHeader variant='outlined' color='secondary'>
            <MarketingBar />
          </TopHeader>
           --- SNIP ---
          <Content>
            <Hero hasButton subtitle='test' title='Test' />
            <StyledContainer>{routeResult}</StyledContainer>
          </Content>
           --- SNIP ---
        </Root>
      </ThemeProvider>
    </ColorModeContext.Provider>
  );
};

Light mode on:

Dark mode on:

I do not really understand what is going on there, everything should be working just fine...
P.S: For completion sake, here is my theme.js:
import {
  createTheme,
  responsiveFontSizes,
} from '@material-ui/core/styles';
import { blue, red } from '@material-ui/core/colors';

export default responsiveFontSizes(
  createTheme({
    palette: {
      // mode: 'dark',
      primary: red,
      secondary: blue,
      // Used by `getContrastText()` to maximize the contrast between
      // the background and the text.
      contrastThreshold: 3,
      // Used by the functions below to shift a color's luminance by approximately
      // two indexes within its tonal palette.
      // E.g., shift from Red 500 to Red 300 or Red 700.
      tonalOffset: 0.2,
    },
  })
);

Hi @aress31 ,
Can you makde a CodeSandbox for me to test this out?
Thank you

Hi @AlvesJorge all the relevant part of this bug are present in my original post, unfortunately I cannot CodeSandbox this code, I am happy to try out suggestions though.

@aress31 try to isolate your reproduction and create a codesandbox that will illustrate the issue. It is time-consuming for us if we need to setup a project for every issue that we receive. It would help a lot!

@aress31 I guess it is because your customTheme has already been calculated with fixed mode (either light or dark in your theme.js). Even though you call createTheme(customTheme, ...) it does not work because customTheme will replace the default value.
const muiTheme = React.useMemo(
  () =>
    createTheme(customTheme, {
      palette: {
        mode: mode,
      },
    }),
  [mode]
);

What I suggest is to separate between design tokens and components. something like this,
export const getDesignTokens = (mode) => ({ palette: { mode, primary: { ... } } });

export const getThemedComponents = (theme) => ({
  components: {
    MuiButton: {
      styleOverrides: {
        // ...custom theme as usual
      }
    }
  }
})

const lightDesignTokens = getDesignTokens('light');
const darkDesignTokens = getDesignTokens('dark');

const darkTheme = createTheme(getDesignTokens('dark'));
// import { deepmerge } from '@mui/utils';
export const brandingDarkTheme = deepmerge(darkTheme, getThemedComponents(darkTheme));

I find this approach more explicit and predictable.

If I need to guess, the problem is with this code:
  const muiTheme = React.useMemo(
    () =>
      createTheme(customTheme, {
        palette: {
          mode: mode,
        },
      }),
    [mode]
  );

You would need to merge the first argument with the second, and then invoke the createTheme.

I've seen multiple issues with confusion regarding how the first argument is handled differently in createTheme. I believe there is an opportunity here for improving the documentation. Will try to setup some time to look into it this or next week.

@mnajdova @AlvesJorge, here is a sandbox:
https://codesandbox.io/s/agitated-resonance-kd751?file=/src/config/muiLayout.js

@mnajdova what would be the best/recommended way to merge the first and second argument before calling createTheme, could you please provide a code snippet?

Note: @mnajdova maybe worth improving the dark theme switch doc as well, as I followed step by step the documentation on how to implement a dark mode switch and it resulted in this weird behaviour.

Adding this on my TODO list, will work on both these two docs sections probably tomorrow.

@aress31 btw you need to other dynamically set the palette based on the mode, or you need to have two different themes (light and dark) and provide the correct one in the context. I am not sure what is the expected behavior based on the code that you provided on the code sandbox. About merging the two, I meant something like:
const muiTheme = React.useMemo(
  () =>
    createTheme({
      ...customTheme,
      palette: {
        ...customTheme.palette,
        mode: mode,
      },
    }),
  [mode]
);

Well I want to dynamically update the theme based on the mode set with the dark mode switch, changing this value on the theme should update and re-render everything? 🤔

Well I want to dynamically update the theme based on the mode set with the dark mode switch, changing this value on the theme should update and re=render everything?

Well I want to dynamically update the theme based on the mode set with the dark mode switch, changing this value on the theme should update and re-render everything?

https://codesandbox.io/s/quizzical-liskov-0hwu2?file=/src/styles/theme.js
There you go this should be what you want.

@AlvesJorge rather than having to create two palettes and switch it on the ThemeProvide level could a helper function be implemented or a hook that would just take the selected mode light or dark to update the existing palette rather than creating a new one, because this adds code redundancy having to create two palettes for people who just want createTheme to compute the matching dark mode based on contrastTreshold and tonalOffset.

I implemented another solution (that seems much more elegant to me) and which can be viewed here:

https://codesandbox.io/s/mystifying-bouman-z9qzi?file=/src/index.js

One problem though, it seems that although my default preferred colour scheme is dark the useState hook setter is called twice (due to multiple render? 🤔) and that messes up everything other than that, I really like this solution and would be super grateful if someone could help me getting to behave as expected.

@aress31 see https://next.material-ui.com/customization/palette/#system-preference as an example

Thanks @mnajdova already seen and based my code on this example, however, what is missing in the doc is an example that combine both, starting with the preferred mode using useMediaQuery and a switcher to switch from preferred to alternate mode. The theming and dark mode support is pretty good with Material-UI and adding this to the doc can only benefit users.
For my specific case as mentioned I would like to use the approach you linked https://next.material-ui.com/customization/palette/#system-preference by simply changing the mode value with a switcher. So far this is what I done but it causes multiple re-render and therefore is not usable.

https://codesandbox.io/s/mystifying-bouman-z9qzi?file=/src/index.js

@siriwatknp @mnajdova the new example on the doc is very good however if you could add in the example how to theme components based on the palette (dark/light) I think that would be a nice addition as right now only palette changes are explained and most of the time branding/theming of components rely on the palette choice.


Add R.info for static typing Info.plist

The Info.plist file contains data that is sometimes needed at runtime. In particular, for Siri Shortcuts, I'm interested in the NSUserActivityTypes array.
We should add a top level R.info object, that includes relevant fields like userActivityTypes, but also things like applicationShortcutItems, as mentioned in https://github.com/mac-cain13/R.swift/issues/82
Example usage:
let myOrder: String = R.info.userActivityTypes.comMyAppViewOrder
let barcodeScanner: String = R.info.applicationShortcutItems.comMyAppBarcodeScanner.title

Found this list of keys that you can have in a plist, could be a good starting point: https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Introduction/Introduction.html
Apple states it's not up to date, but I see keys stated as iOS 11.0 and later. So it doesn't seem that outdated yet...

Just noticed that what file will be used as the Info.plist is a build setting. So you can use another plist in debug or release for example. That would make it a bit harder to do this right, we should think about that.