Grad-CAM for visual language tasks dose not work on the lavis blip model !!

I have installed the lavis and omniXAI from your official repositories and then followed your example for Grad-CAM for visual language tasks by the way it seems your example is out of date when I tried to load the model it gives me this error:
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
Input In [15], in <cell line: 3>()
      1 pretrained_path = \
      2     "https://storage.googleapis.com/sfr-vision-language-research/BLIP/models/model_base_retrieval_coco.pth"
----> 3 model = BlipITM(pretrained=pretrained_path, vit="base")
      4 image_processor = load_processor("blip_image_eval").build(image_size=384)
      5 text_processor = load_processor("blip_caption")

TypeError: __init__() got an unexpected keyword argument 'pretrained'

So, I come up with a way to load the model as the lavis mentioned it loaded
model = load_model(
        name="blip_image_text_matching", model_type="base", is_eval=True, device=device, checkpoint=ckp_path
    )

but in the explainer method, I got this error!
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Input In [13], in <cell line: 1>()
      1 explainer = GradCAM(
      2     model=model,
----> 3     target_layer=model.text_encoder.base_model.base_model.encoder.layer[6].
      4         crossattention.self.attention_probs_layer,
      5     preprocess_function=preprocess,
      6     tokenizer=tokenizer,
      7     loss_function=lambda outputs: outputs[:, 1].sum()
      8 )

File ~/.conda/envs/lavis/lib/python3.8/site-packages/torch/nn/modules/module.py:1177, in Module.__getattr__(self, name)
   1175     if name in modules:
   1176         return modules[name]
-> 1177 raise AttributeError("'{}' object has no attribute '{}'".format(
   1178     type(self).__name__, name))

AttributeError: 'BertSelfAttention' object has no attribute 'attention_probs_layer'

Could you please help me to solve this issue?

Hi, thanks for raising the issue. We will revise the interfaces of OmniXAI as well as Lavis for this problem in the next release. We will send you a quick fix for this problem "AttributeError: 'BertSelfAttention' object has no attribute 'attention_probs_layer'".


Fix typo "definitly" -> "definitely"

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


AVRO-2732: Fix openjdk changes by using stretch base image

Make sure you have checked all steps below.
Jira

[X] My PR addresses the following Avro Jira issues and references them in the PR title. For example, "AVRO-1234: My Avro PR"

https://issues.apache.org/jira/browse/AVRO-2732
In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

Tests

[X] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Build fix.
Commits

[X] My commits all reference Jira issues in their subject lines. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain Javadoc that explain what it does

Cherry-picked into branch-1.9 just in case.


Fixes deprecation warnings in React 15.5.0

React 15.5.0 introduced deprecation warnings for PropTypes, createClass, and react-addons: https://facebook.github.io/react/blog/2017/04/07/react-v15.5.0.html
This PR updates dependencies to address those warnings.

Changes Unknown when pulling ec2ae091898ac666a184a9b102484cc1c6d71543 on charliecochran:master into ** on helior:master**.

Closes https://github.com/helior/react-highlighter/issues/38

@helior Specific holdup here?

No hold-ups, this looks great, thanks you @charliecochran!


Fix typo and delete unnecessary spaces

typo:
,
,
 ->

delete unnecessary spaces: As Markdown syntax, there was a large amount of half-width spaces that did not affect the display, so I deleted it

@changeworld : Thanks for your contribution! The author, @mamccrea, has been notified to review your proposed change.

#sign-off

@changeworld Thanks for your continued contributions.
I'm not sure that updating spacing is a good idea. Is it necessary when the output looks almost identical? I feel like this is risky and is not really changing the output, since we aren't seeing a preview of the page.
I want us to be cautious about changing formatting as trivial as it may be, because it is very hard to test out until we get a build of the page.

I did spend a lot of time testing the table spacing originally and it looked fine I thought. I'm curious did you see any problems in the real docs page?

Note that we do not optimize for Markdown previews in github, since we are optimizing the docs page at https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-define-outputs

There is a mixed school of thought around  tags. Open tags, versus closing tags, versus self-closing tags.  https://www.w3schools.com/tags/tag_br.asp

Stack overflow says they are the same, but could be  is sufficient. https://stackoverflow.com/questions/1946426/html-5-is-it-br-br-or-br
Maybe  was invalid without an opening .
At the end of the day, I don't think perfecting the br tags will change the docs very much, since humans don't see the markdown and HTML mark up tags most of the time.
Thanks, Jason

@changeworld That is very interesting. Thanks for sharing.
We can do better to check the formatting in multiple languages. Maybe we need to follow up with the docs localization team to have them check the spacing feature in machine learning to avoid some of the headaches. Maybe you already talked to them about it?
In the screenshot example you cited, adding line breaks will fix the formatting for the code blocks connecting to the paragraph preceding.
Do the end of line spaces (like this one #20907) that you removed impact the machine translated articles too?
Thanks, Jason

@JasonWHowell Thank you for your comment.

Maybe you already talked to them about it?

Although I respond as follows, I have not explained it as it is now.
ja docs: https://github.com/changeworld/azure-docs.ja-jp/commits/live/articles/hdinsight/connect-on-premises-network.md
my 1st pr: https://github.com/changeworld/azure-docs.ja-jp/commit/bbe17e07d6db4a9f3cddd0a24e259baa441197e0#diff-ebe16d7e080936018ce7b75d59c660e3
translated using machine learning:  https://github.com/changeworld/azure-docs.ja-jp/commit/354c4c8785bafd0f6331b45e139441305b529a36#diff-ebe16d7e080936018ce7b75d59c660e3, https://github.com/changeworld/azure-docs.ja-jp/commit/7ebb5965fbd331db3bbbf6b6cf3ea6217329da0b#diff-ebe16d7e080936018ce7b75d59c660e3, https://github.com/changeworld/azure-docs.ja-jp/commit/d6b72d0ad99d5a9975df194b46426707b9a0f810#diff-ebe16d7e080936018ce7b75d59c660e3
my 2nd pr:https://github.com/changeworld/azure-docs.ja-jp/commit/1f9e693ff9f1ec4bdb71366766c849aa18fcaff5#diff-ebe16d7e080936018ce7b75d59c660e3
I heard that in January next year people from the localization team will visit Microsoft's office in my country and hold an event. I'm preparing documents that explain in English what kind of things I'm talking to you right now and about some patterns I learned through PR.

Do the end of line spaces (like this one #20907) that you removed impact the machine translated articles too?

I do not have data that explicitly indicates this because I do not fully understand the mechanism of translation and identification patterns by machine learning.
What I understand is that the notation of the original (English version) document is adversely affecting the document of each language version.
Thanks,
Takashi

@changeworld I will mentioned our conversation and your work to the localization team so they can be sure to sync up with you about the patterns you observed.
Thanks for the assistance improving MicrosoftDocs.
Best regards, Jason


Uses of inaccessible hypotheses not distinguishable from accessible ones

Compare

with Emacs:

I'm not yet sure completely hiding the cross was the best solution btw. It complicates copy&paste, and maybe position retrieval for any interactive features in the future.


Split Disk Option?

First, thanks for the awesome docker setup, works like charm.
I was wondering if there might be a way to split the disk or use multiple disk images?  I currently have multiple drives setup with my system and would like some redundancy if I am to use this DSM docker setup but I don't see a way around that unless I can somehow split the root image into multiple parts (spread across drives) or use multiple images mounted into DSM which would then RAID them together?
I have previously set up a multiple image setup with xpenology and RAID inside DSM but this would be way simpler to maintain and update if there was some way to do it through your docker image.
I have read through your other replies about using iSSCI or NFS to mount the external drives inside DSM, but I would really like to take advantage of DSM's ability to RAID and provide some redundancy and speed improvement if I am able to place multiple images across drives.
Architecturally I could see a system where in a user mounts multiple volumes to /storage /storage1 /storage2 etc. and the assumption is that each of these storage mounts are on different drives.  Then during the image generation step the script can detect which folders are available and create an image in each one with the specified size.  Finally, it would mount all of these images as separate drives onto the DSM VM.
Let me know what you think :)

This container doesn't provide this options because if you want redundancy its much easier to do it at the host-level.
For example, you create the RAID array in Linux using two disks, and use it as the location for your virtual disk image. That way you can have full RAID redundancy for this container (or any other container).
I think this is a much better method, because you will have a fully standard RAID (instead of us creating a hacky solution) which will work with all the standard tools, etc.

I guess that is a fair point.  I mainly wanted the option because I am currently using unRAID with their standard setup (ie. non-ZFS/RAID parity) - I wanted to keep open the possibility of having different sized drives.  Being able to create multiple virtual disk images would allow for this and help me in my procrastination of setting up ZFS ;)
I am not positive, but I believe having multiple images RAIDed inside of Synology could help corruption of the images themselves?

Maybe an alternate way would be to somehow mount a folder through docker that would then be passed through to the DSM VM?  This way all the users files could be stored outside the OS image and the files could be stored in any manner outside of docker.
It looks like qemu supports folder mounting? - https://wiki.qemu.org/Documentation/9psetup
-virtfs local,path=/host/path/to/share,mount_tag=host0,security_model=mapped,id=host0

I might experiment with this myself to see if it's a viable option.

At the end of the day, I am just worried about this single image corrupting and it having all my images (using Synology Photos) and as a result having to restore a multi-TB file from backup.

Ah that stinks about the folder mounting as that would be the most ideal situation.  I did get DSM RAID working with multiple virtual disks in the unRAID VM system (also uses qemu).
If you are wondering why I am looking to switch it's due to the tinycore redpill approach being fragile with updates.  This docker approach would also be easier to manage.


Food gives permanent bonus to damage resistance(s)

Food items that increase damage resistance(s) can become permanent when the effect is active, and you save and load.

Game Version
<IP_ADDRESS>
Language
English (EN)
New Game
Yes
Reproduction Steps
Use a food consumable that increases at least a single damage resistance, make a save, load the save.

Bump, this bug is still present.


Add option to output mark.js version number

It would be great if we could simply output the current version number of the used mark.js code.

Can you please share your use case?

I am using mark.js in a project which is using several third party js libraries. The admin interface of this project lists all used frameworks and the related version numbers. This works without issues for jQuery, DataTables, Bootstrap etc. and gives a good overview of the used versions.


[SIGNAL] Changed audio loading backend to soundfile

Using pysoundfile which allows for:

Reading 24-bit audio
Working on variety of formats such as FLAC

Rebased in https://github.com/python-acoustics/python-acoustics/pull/238.


False positive with rayon's into_par_iter, fold and reduce

Since I am at it, thanks a lot for this amazing piece of software!
Minimal repro I could come up with:
use std::collections::HashMap;

use rayon::prelude::*;

type C = HashMap<u64, (Vec<u64>, Vec<u64>)>;

fn main() {
    let a = vec![1u64];
    a.into_par_iter()
        .enumerate()
        .fold(C::default, |_, _| todo!())
        .reduce(C::default, |acc, other| todo!());
}

it shows as an error in VS code with the configuration below, but it compiles fine. Changing to type C = HashMap<u64, (u64, u64)>; does not show the error.
rust-analyzer version: rust-analyzer version: 7d6fcbc0b 2021-12-06 stable
rustc version: rustc 1.56.1 (59eed8a2a 2021-11-01)

Confirmed. Most likely a duplicate of #10822. According to the help, it picks reduce from the Iterator trait instead of Paralllelterator.

Probably fixed in #11074:


Wrong parametrs to substr function

If you trying to call $message->getText(true)  for message where only command is present then you calculation would be wrong Line 376:
$text = substr($text, strlen($command) + 1, strlen($text));
And substr will return false because start position is higher than $text  it self. I think it should be something like this
$text = substr($text, min(strlen($command) + 1, strlen($text)), strlen($text));

Hello, would you pr?

how is possible?
this test works
https://github.com/akalongman/php-telegram-bot/blob/master/tests/Unit/Entities/MessageTest.php#L58

I tried to call $message->getText(true) for message with only command and instead of empty string I got false. Then I found that in EchoCommand example you wrap this call with trim
trim($message->getText(true));

Could you provide the raw update?


Edge.JS Access Violations

We're occassionaly seeing the Edge.js AV exception from time to time (see Edge issue we logged here). Below is the error logged to eventlog.xml.
<Event>
    <System>
        <Provider Name=".NET Runtime"/>
        <EventID>1026</EventID>
        <Level>0</Level>
        <Task>0</Task>
        <Keywords>Keywords</Keywords>
        <TimeCreated SystemTime="2016-06-15T21:04:17Z"/>
        <EventRecordID>698472453</EventRecordID>
        <Channel>Application</Channel>
        <Computer>RD000D3A308A72</Computer>
        <Security/>
    </System>
    <EventData>
        <Data>
Application: w3wp.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at EdgeJs.Edge.NodeStart(Int32, System.String[]) at EdgeJs.Edge.
            <Func>b__1() at System.Threading.ThreadHelper.ThreadStart_Context(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Threading.ThreadHelper.ThreadStart()

            </Data>
        </EventData>
    </Event>

So we're sometimes seeing it outside of the App Domain cycle scenario (which never happens in Azure)? If so, that's bad news. Maybe that's the reason behind the occasional 503s we see in Azure?

In all my Function Apps I'm deploying private site extensions, forcing stops/starts, etc., so I'm not sure if unusual usage patterns like that are the cause, or if this can be reproed by normal users. I also don't know the frequency. We basically need to attempt to get a repro.

Right, if you deploy private site ext, then you'd be exposed to AppDomain restart. It may not be the same root cause as the 503 we all see occasionally in Prod. That one is nasty.

Need to investigate if we can see this in production or if it is related to private site extensions.

Closing this for now, since I saw this in the context of my own Function App that I was deploying private site extensions to, forcing restarts, etc.


[BUG] Particle Tunneling Out of Constraints

Describe the bug
At high speeds, the particle moves quickly enough that its center-point can clip completely out of bounds. This causes the particle to leave the simulation window, never to return.
To Reproduce
Steps to reproduce the behavior:

Spawn a particle with a velocity vector of sufficient magnitude for the step size.
Step the simulation until the particle reaches an edge.
See error.

Expected behavior
The particle's center-point will completely clip out of bounds, causing it to fly off infinitely.
Additional context
There will always be something which breaks the simulation -- the goal is to make this less of an issue via simulation parameters that can be tweaked as needed.

Addressed this as part of https://github.com/hayesHowYaDoin/physics_backend/pull/25. Workaround is to apply a sub-step to each step, which decreases the distance fast-moving particles move per-step. It is still possible to clip out of bounds, but it is assumed that any users will need to tune their simulation parameters individually to match their performance needs.


Upgrade Vue app loader-utils dependency

This gets rid of a critical security warning. Should do a whole npm audit fix while I'm at it.

Done.


Fix drone for tags

As title

LGTM

Codecov Report

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

@@           Coverage Diff           @@
##           master    #2573   +/-   ##
=======================================
  Coverage   27.33%   27.33%
=======================================
  Files          86       86
  Lines       17137    17137
=======================================
  Hits         4684     4684
  Misses      11775    11775
  Partials      678      678

Continue to review full report at Codecov.

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

LGTM


ODOT traffic count 2020

Using the ODOT Traffic Count dataset (https://discovery.smartcolumbusos.com/dataset/odot/traffic_counts_2016_to_2020) create a visualization that shows the following:

[x] Line diagram
[x] Weekly breakdown
[x] Demonstrates the increases and decreases of traffic counts on a weekly basis only for 2020

TN:

Built in Plot.ly
Save visualization and share link with @jakeclark

Amigos:
@JarredOlson , @carriebrinkley

https://discovery.smartcolumbusos.com/visualization/prpct37z


Incorrect combined metal+rough textures when 1 input is not connected to a texture

Describe the bug
With recent versions of the exporter the behaviour of exported combined rough+metal texture has been changed when 1 of the roughness/metallicity material parameters is a texture while the other is a fixed constant. This change was introduced in PR #1968. Previously when generating the combined texture only values for parameters with a connected texture were written to the output texture with all other channels being set to 1.0. After the change the fixed constant is being written to all pixels in place of the previous written 1.0. This is incorrect as the same value is being written to the materials base factor ASWELL as now to the texture component (e.g. if we had a base roughness of 0.1 then the output gltf has 0.1 written into the texture and 0.1 written to roughnessFactor which results in incorrectly calculated final roughness = 0.1*0.1).
To Reproduce
Steps to reproduce the behavior:

Create a material with a texture connected to the metallicity parameter
Set the roughness to a constant value (e.g. 0.1)
Export GLTF
Compare exported combined metal+rough texture which has 0.1 written into the texture corresponding roughness channel ASWELL as having 0.1 written to the materials roughnessFactor in the gltf
The same issue occurs if switching metal/roughness in the steps above

Expected behavior
Previous versions of the exporter handled this correctly. The rough/metal value in the presence of a texture is equal to the base factor multiplied by the texture value. In the above example the roughness is calculated with base factor (roughnessFactor) multiplied by the roughness channel of the texture. This should result in a final value matching the one set in blender (here 0.1) but due to the change in exported textures now does not (here 0.1*0.1 = 0.01). For rough/metal texture channels with an unconnected texture the texture should contain 1.0 as with previous versions of the exporter.
From the GLTF spec:
The value for each property MAY be defined using factors and/or textures (e.g., baseColorTexture and baseColorFactor). If a texture is not given, all respective texture components within this material model MUST be assumed to have a value of 1.0. If both factors and textures are present, the factor value acts as a linear multiplier for the corresponding texture values.
Screenshots
Example material:

using following texture for metallicity:

Exported combined metal+roughness texture for different blender versions

3.6.5 (correct)
4.0.1 (incorrect)

Corresponding material in exported GLTF from 4.0.1 (note this is identical to 3.6.5):
{
			"name":"Material",
			"pbrMetallicRoughness":{
				"baseColorFactor":[
					0.800000011920929,
					0.800000011920929,
					0.800000011920929,
					1
				],
				"metallicRoughnessTexture":{
					"index":0
				},
				"roughnessFactor":0.10000000149011612
			}
		}

Comparison of exported GLTF as viewed in babylonjs:

3.6.5 (correct)
4.0.1 (incorrect)

.blend file/ .gltf
blenderTest.zip
Version

OS: Any
Blender Version 4.0+

Confirmed

This is now fixed in 4.1 alpha
As this is a regression, I will try to make it included in 4.0.x maintenance release.


Updated ME67 and added additional unit tests

added tests to verify the change not only passes existing tests but extends and verifies and passes additional scenarios that were incorrectly failed in production previously
TP2000-914 Your PR title here
Why

ME67 did not pass in valid scenarios.
Unit test coverage missed some data configurations that were valid.

What

Updated the logic for ME67 to verify the date range of the change against the data
Added tests to cover additional scenarios, observed as incorrectly raising violations in production

Checklist

Requires migrations? NO
Requires dependency updates? NO

Links to relevant material
See: Description

Codecov Report
Patch coverage: 93.10% and no project coverage change.

Comparison is base (1a0f6b2) 92.51% compared to head (00ebb89) 92.52%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #945   +/-   ##
=======================================
  Coverage   92.51%   92.52%
=======================================
  Files         431      432    +1
  Lines       30154    30202   +48
  Branches     2306     2306
=======================================
+ Hits        27898    27943   +45
- Misses       1799     1802    +3
  Partials      457      457

Impacted Files
Coverage Δ

measures/tests/test_business_rules.py
95.72% <ø> (-0.05%)
:arrow_down:

measures/tests/test_buinsess_rules/test_ME67.py
92.30% <92.30%> (ø)

measures/business_rules.py
89.15% <100.00%> (+0.05%)
:arrow_up:

... and 1 file with indirect coverage changes

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


[Refactor] improve internal typings and refactor to become in sync with the new types

thank you so much for this! will review it this week and we can release a minor version with the bug fix and type improvement. 🙏

These two PRs were actually my first contributions to open source!
You really made a great impression on me by being so welcoming and nice. Thanks a lot :)

That's awesome to hear! you are making huge improvements to this library. Please make more if are interested. Thank you @ali-garajian

published https://github.com/bluebill1049/react-simple-animate/releases/tag/v3.5.0


add --verbose flag so I can watch pip-compile progress

https://github.com/jazzband/pip-tools/issues/521

I've read the linked issue, and my understanding of the problem is that at times pip-tools runs extremely slow and it's hard to tell if it's making any progress (correct me if I'm wrong).
While having a progress bar might look nice, I feel like this feature will make code harder to maintain without any adding practical benefit.
I'm closing the issue, but feel free to reopen with a good argument.

Even without the progress bar it's good to be able to see what package is taking a long time

Yeah, must be feeling good, but how does this information help? I mean, there is no way to speed up any particular package. pip-tools will take as much time as it needs. And the slow package will be slow during installation too, so it's not an insight.

@peterdemin I don't really care too much about the progress bar, just some sort of verbose output
sometimes I end up with pathological cases where it's sat retrying because I forgot to connect to the VPN

I'll be happy to review the PR with this  feature. -v/—verbose  that streams live pip-tools progress.

@graingert Stumbled across this whilst searching for exactly the same thing. I've sketched out a partial solution in #247, reckon it's got legs?


Add split window (like tmux or cmder)

Hello Powershell team,
Could you please add the split window feature to Powershell, like tmux for linux, cmder to windows.
This will make Powershell really powerful.  Thx.

I don't think this is something we would have as part of PowerShell.  Similar to tmux, screen, cmder, I think it's something that's outside the shell.

@SteveL-MSFT,
Thx for your reply, I have two main usages of the split window.
1/ When I connect to my remote admin server by PSRemoting from my desktop. As it's a admin server, I often need to launch multiple powershell windows to manage other servers. And as we don't have the split window yet, I have to launch multiple PSRemoting from my desktop, it takes time.
2/ In VSCode for Windows, we can only see one terminal at the same time, I really need multiple terminal consoles at the same time instead of  switching among them each time. Cmder is a GUI application that cannot be intergrated into VSCode terminal.
If the Powershell team doesn't want to implement the split windows, we don't have any other choice ...

@copdips the lack of similar tools on Windows and in VSCode is certainly a problem, maybe we can look into it after 6.0.0

@copdips For multi-window terminal support in VSCode, you might want to open an issue in their repo https://github.com/Microsoft/vscode

There already is an open issue for split terminal in https://github.com/Microsoft/vscode/issues/7504

Last vscode insider version just added a feature on vertically splitted terminal

I have vim running in PowerShell and I really need the ability to split panes both horizontally and vertically. It would also be nice to have vi bindings to navigate through the panes as specified here: https://github.com/christoomey/vim-tmux-navigator#usage

@kazimir-malevich I think the closest you will get to this is to use the new Windows Terminal - https://www.microsoft.com/en-us/p/windows-terminal-preview/9n0dx20hk701?activetab=pivot:overviewtab /  https://github.com/microsoft/windowsterminal app.
It supports h/v split panes e.g:

@rkeithhill that's really awesome bro, i start using it from now

I was still not happy with the solutions presented, especially via ssh (multiple ssh connections from a console with tab support).
So I made my own tool similar to tmux.
https://github.com/osen/vimux
Just run 'vimux' and then use shortcuts like  to open a new terminal within the same ssh session.

I use Windows Subsystem for Linux.  When I want tmux-type utility, I just start my session with "wsl tmux".  Note, you must have tmux installed in wsl.  From there, I can run powershell.exe or cmd.exe to use those shells, but they are running under bash under tmux under bash/wsl.  A bit kludgy, but it works just fine and ALL of tmux is available... split screens, tabs, resizing windows, etc.  I imagine there may be better shortcuts... maybe some form of "wsl tmux -c powershell.exe" or the like, but I haven't explored it that deeply.


RDP window opens by itself

after reconnecting to a remote desktop session, the window opens by itself maximized and in the foreground
RC 3.1.1, operating system win 10 20H2, reproducible

with version 3.2 and --start-hidden the problem no longer occurs.


Snapshot management via CLI not working

Instructions
Creating snapshot via CLI
I ran flow emulator --persist with default configuration (previously created by flow init). After emulator started, I ran the command to create a snapshot of the current emulator state:
➜ flow snapshot save temp.json --network emulator
❗  warning: using insecure client connection to download snapshot, you should use a secure network configuration...
❌ Command Error: failed to get latest finalized protocol snapshot from gateway: client: rpc error: code = Unavailable desc = error reading from server: EOF

Note that this command failed for the emulator network but worked for the testnet.
The emulator emitted the following logs, while I ran the above command:
➜  flow emulator --persist
INFO[0000] ⚙   Using service account 0xf8d6e0586b0a20c7  serviceAddress=f8d6e0586b0a20c7 serviceHashAlgo=SHA3_256 servicePrivKey=c352ff3900a3a790813dcadf83a89662f3bcf6f7c97a02a2011d0da901c9c6c2 servicePubKey=aada506b7837942b9bf395d5aac2e108ccd219ab5f26ef4cefb601dd2f687e275c2adc8a437c432b587c19fe7512ffc3936369d453259571d94f49584d9a6009 serviceSigAlgo=ECDSA_P256
INFO[0000] 📜  Flow contract                              FlowServiceAccount=0xf8d6e0586b0a20c7
INFO[0000] 📜  Flow contract                              FlowToken=0x0ae53cb6e3f42a79
INFO[0000] 📜  Flow contract                              FungibleToken=0xee82856bf20e2aa6
INFO[0000] 📜  Flow contract                              FlowFees=0xe5a8b7f23e8b548f
INFO[0000] 📜  Flow contract                              FlowStorageFees=0xf8d6e0586b0a20c7
INFO[0000] 🌱  Starting gRPC server on port 3569          port=3569
INFO[0000] 🌱  Starting REST API on port 8888             port=8888
INFO[0000] 🌱  Starting admin server on port 8080         port=8080
panic: implement me

goroutine 322 [running]:
github.com/onflow/flow-emulator/server/backend.(*Backend).GetLatestProtocolStateSnapshot(...)
	github.com/onflow/flow-emulator@v0.34.0/server/backend/backend.go:593
github.com/onflow/flow-emulator/server/backend.(*Adapter).GetLatestProtocolStateSnapshot(0x140009b79d8?, {0x100e96938?, 0x101c09580?})
	github.com/onflow/flow-emulator@v0.34.0/server/backend/adapter.go:199 +0x30
github.com/onflow/flow-go/access.(*Handler).GetLatestProtocolStateSnapshot(0x140009b7a18?, {0x101cadbd0?, 0x1400093c210?}, 0x1400093c690?)
	github.com/onflow/flow-go@v0.26.14-test-synchronization.0.20220801105506-320bb18569ff/access/handler.go:468 +0x30
github.com/onflow/flow/protobuf/go/flow/access._AccessAPI_GetLatestProtocolStateSnapshot_Handler.func1({0x101cadbd0, 0x1400093c210}, {0x101ba6d40?, 0x14000952040})
	github.com/onflow/flow/protobuf/go/flow@v0.3.1/access/access_grpc.pb.go:918 +0x74
github.com/grpc-ecosystem/go-grpc-prometheus.(*ServerMetrics).UnaryServerInterceptor.func1({0x101cadbd0, 0x1400093c210}, {0x101ba6d40, 0x14000952040}, 0x140005e1ad8?, 0x1400090a4b0)
	github.com/grpc-ecosystem/go-grpc-prometheus@v1.2.0/server_metrics.go:107 +0x74
github.com/onflow/flow/protobuf/go/flow/access._AccessAPI_GetLatestProtocolStateSnapshot_Handler({0x101c4c4a0?, 0x14000643bc0}, {0x101cadbd0, 0x1400093c210}, 0x140005b8720, 0x14000630250)
	github.com/onflow/flow/protobuf/go/flow@v0.3.1/access/access_grpc.pb.go:920 +0x138
google.golang.org/grpc.(*Server).processUnaryRPC(0x140005a8c40, {0x101cbbe78, 0x140063a2000}, 0x140001b9320, 0x14000643c50, 0x1027e9948, 0x0)
	google.golang.org/grpc@v1.46.2/server.go:1283 +0xb50
google.golang.org/grpc.(*Server).handleStream(0x140005a8c40, {0x101cbbe78, 0x140063a2000}, 0x140001b9320, 0x0)
	google.golang.org/grpc@v1.46.2/server.go:1620 +0x82c
google.golang.org/grpc.(*Server).serveStreams.func1.2()
	google.golang.org/grpc@v1.46.2/server.go:922 +0x84
created by google.golang.org/grpc.(*Server).serveStreams.func1
	google.golang.org/grpc@v1.46.2/server.go:920 +0x290

Creating snapshot via HTTP
Then I saw there is supposedly another way to create a snapshot using an HTTP request, described here. So I ran the bellow command, and got a promising response back:
➜  http GET http://localhost:8080/emulator/snapshot/first
HTTP/1.1 200 OK
Content-Length: 108
Content-Type: application/json
Date: Fri, 12 Aug 2022 12:23:32 GMT

{
    "blockId": "13c7ff23bb65feb5757cc65fdd75cd243506518c126385fae530ddebdad10b17",
    "context": "first",
    "height": 0
}

Emulator logs:
2022/08/12 14:23:32 http: superfluous response.WriteHeader call from github.com/onflow/flow-emulator/server.EmulatorAPIServer.Snapshot (emulator.go:129)

Problem
Snapshot management doesn't seem to work when using CLI, but does work when using HTTP API.
Another thing I should mention is that the flow-emulator README mentions that you need to use --persist flag to be able to use snapshot features, but flow docs doesn't mention that anywhere. I was also a bit confused about whether I needed to use the persist flag.
Steps to Reproduce
See reproducible steps in the instructions section above.
Acceptance Criteria
Users should be able to use both CLI and HTTP APIs to manage snapshots.
Context
I'm working on implementing the new snapshot feature in Flowser tool.

I found a related issue comment that already mentions the above error: https://github.com/onflow/flow-cli/issues/420#issuecomment-1158076367

Thanks for flagging this, will lyk when we are implementing this feature @bartolomej

Thank you for reporting this, but the command you were using is not intended to do a snapshot of the emulator, but something else. We need to yet support making snapshots in the CLI, currently you can only make them using the emulator API directly as found here https://github.com/onflow/flow-emulator#managing-emulator-state
We already have an issue documented to add this to the CLI so closing this one.


try to set the playerLoadingFallback, but occasionally it didn't work

version list:
Flutter 3.16.9
flick_video_player: ^0.7.0
video_player: ^2.8.2
demo:
FlickVideoPlayer(
        flickManager: flickManager,
        flickVideoWithControls: FlickVideoWithControls(
          videoFit: BoxFit.contain,
          controls: SafeArea(
            child: FlickPortraitControls(
              iconSize: 22,
              fontSize: 14,
              progressBarSettings: FlickProgressBarSettings(
                padding: const EdgeInsets.symmetric(
                  vertical: 10,
                ),
              ),
            ),
          ),
          // TDLoading is a custom style loading widget
          playerLoadingFallback: const Center(
            child: TDLoading(
              size: TDLoadingSize.medium,
              icon: TDLoadingIcon.circle,
              iconColor: Color.fromRGBO(214, 224, 244, 1),
            ),
          ),
        ),
      )

But it still shows the purple one. What should I do?

@ly75x12
I tried adding a custom playerLoadingFallback and it worked fine for me, attached a video for your reference.
flick_video_player : 0.8.0
video_player : 2.8.6

Can you update flick version and try out again ?
https://github.com/GeekyAnts/flick-video-player/assets/29561914/d86a7e63-f8f0-4d0d-a0cd-57f03afcb8dc


Thank you for your effort in these documentations, John!

No problem Sky! I hope you are doing well!


Better NVIDIA Pascal GPU Support

This PR clarifies which features are supported on P100 via its tests, though Pascal is not officially and fully supported by Triton.
What this PR does

Skip unsupported tests on P100.

Atomic RMW
tl.dot() (perhaps not all patterns, but basically most tl.dot() tests do not work on P100).

Add an explicit error if shared memory size >= 64K on P100.

Otherwise it causes Invalid CUDA argument error at cuLaunchKernel(), but this error is not very straightforward to understand. Instead of this generic CUDA argument error, this PR makes Triton show an error during codegen when sm < 70. This check happens in C/C++ so won't add an overhead in Triton's Python runtime.
3 tests (see below) are currently failing, but these are not marked as skipped because any codegen update in the future can change the kernel size of the other tests.

This change won't affect Triton-MLIR. Hopefully Triton-MLIR's generic tl.dot() implementation would support P100.

Importantly, Triton passed all the other tests on P100.  Though this support is not official, it is great for, for example, PyTorch's TorchDynamo/Inductor, which can use Triton (without tl.dot()) for its backend (https://github.com/pytorch/torchdynamo/issues/1591).
Results on P100 (Google Cloud)
$ pytest test/unit
...
================================================================================== short test summary info ==================================================================================
FAILED test/unit/language/test_core.py::test_reduce2d[argmin-float32-shape99-1] - RuntimeError: Device does not support shared memory of 65536bytes
FAILED test/unit/language/test_core.py::test_reduce2d[argmax-float32-shape113-1] - RuntimeError: Device does not support shared memory of 65536bytes
FAILED test/unit/language/test_core.py::test_permute[float32-shape5-perm5] - RuntimeError: Device does not support shared memory of 67584bytes
================================================================== 3 failed, 3824 passed, 952 skipped in 470.90s (0:07:50) ==================================================================

 Environment Details (collapsed)

VM details (Google Cloud)
https://cloud.google.com/
# You need a paid account (free trial does not cover GPUs)
Google Cloud -> New Project -> Compute-Engine -> VM Instance
Machine:
GPU: NVIDIA Tesla P100 x 1
CPU: 2 vCPUs, 7.5GB memory
Boot disk:
  OS: Ubuntu 18.04 LTS
  Disk: 40GB (cannot build Triton on the default 10GB disk)
- When I tried, about $1.2 per hour.
- US instances were full when I tried.  I used Asia or Australia.
- Needed a paid account (GPU is not covered by free trial)
- Needed quota request for any GPU instance (by default, no GPU instance is allowed).  Needed to wait an hour for approval

Reproducer
## 1. Install CUDA and a driver
# Update the apt key (https://developer.nvidia.com/blog/updating-the-cuda-linux-gpg-repository-key/)
sudo apt-key del 7fa2af80
wget https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64/cuda-keyring_1.0-1_all.deb
# Download CUDA as instructed
wget https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64/cuda-ubuntu1804.pin
sudo mv cuda-ubuntu1804.pin /etc/apt/preferences.d/cuda-repository-pin-600
sudo apt-key adv --fetch-keys https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64/7fa2af80.pub
sudo add-apt-repository "deb https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64/ /"
sudo apt-get update
sudo apt-get -y install cuda
# Are you using P100?
nvidia-smi | grep "Tesla P100"

## 2. Setup the build environment
sudo apt update
sudo apt install -y build-essential wget git libz-dev
wget https://repo.anaconda.com/archive/Anaconda3-2022.05-Linux-x86_64.sh
bash Anaconda3-2022.05-Linux-x86_64.sh -b -p $(pwd)/anaconda3
eval "$($(pwd)/anaconda3/bin/conda shell.bash hook)"
conda create -y --name triton_base
conda activate triton_base
conda install -y cmake setuptools

## 3. Build Triton
git clone https://github.com/openai/triton.git
cd triton/python
pip3 install -e '.[tests]'

## 4. Test
pytest test/unit

Environment
$ nvidia-smi
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 520.61.05    Driver Version: 520.61.05    CUDA Version: 11.8     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  Tesla P100-PCIE...  On   | 00000000:00:04.0 Off |                    0 |
| N/A   36C    P0    25W / 250W |      0MiB / 16384MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

Would someone merge this PR if it looks okay? I don't have write access.


(git.install) Add option to disable GCM

It seems to be possible to disable GCM on installation.
See: https://github.com/git-for-windows/build-extra/commit/8764c72d83cd05a709fcb21700e42081d226037b and https://github.com/git-for-windows/build-extra/commit/612999af6eeade875c0659c0cad1ea019a9b07d1
Therefore we should ad a parameter to disable GCM on installation to the git.install package.

👍 I agree since it's part of the installer.
Looks like we also need to add .NET 4.5.1 as a dependency (can't remember if it already is)


Update libsass version to 3.6

Sorry it's much more complicated than this.

Very well then I'll leave the job up to the rest of you.


Error on Hilight php

Why after <<<DATA  all php variables look bad, is my implementation problem ?


Resolve CNFE in upstream weld in-container tests.

@pferraro this doesn't solve the problem for WFLY preview because there is a separate module.xml file for weld core module.
Preview variant is located here.
Adding the same change there fixes the problem I was seeing in Weld TS.


[BUG] New messages aren't being set as "read" when they arrive

Your Rocket.Chat.Android version: 2.0.0
Mobile device model and OS version: Sony Xperia
When I receive new messages and I'm inside of the chat, the chat isn't marking the messages as read. It should mark them as read.
This video shows the bug happening:

I also think that the unread message should appear in the center of the marker.

@rafaelks I'd like to work on this. I have a rough idea of where the problem is and what needs to be done to fix it.
@leonardoaramaki I kept the text right aligned since that is how it was in the web app. I'll shift it to the center .


Sampling for ROI Qual Interviews Study

Creating a github issue for the random stratified sampling of recruits for the ROI Qualitative Interviews Study. Selection criteria and requirements discussed between Nicole and Brittany.
ROI Qualitative Interviews Requirements + Invitation Strata: https://nih.app.box.com/folder/288120201144
@FrogGirl1123 @BrittanyCrawford405 please add additional info here, if needed.
Also tagging @m-j-horner here, as I was not able to add her as an assignee.

@BrittanyCrawford405 How is this work coming along? Please let me know when the sampling is complete so that I can generate the alternative IDs.

Hi @jacobmpeters Brittany and Leila have finalized the selection, but we will need to wait for the DCCPS team and Paul Albert (from biostats) to review the selection distribution before we can move on to creating the masked IDs and crosswalk to make sure it aligns with the sampling plan. I just sent to the DCCPS team and I believe Nicole will be sending to Paul once back online from travel.

@robertsamm thank you for the update. I'll stay tuned as that process plays out.

@BrittanyCrawford405 Sampling plan for the 2nd batch of recruits is located here: https://nih.app.box.com/file/1699409595842 and is ready for selection.

Hi @jacobmpeters , the sampling for the second batch of interviews is complete. The list of IDs is located here: https://nih.app.box.com/folder/290062713308

Hi there. I have been OOO unexpectedly since Nov. 14. I anything needed from me at this point?

@BrittanyCrawford405 @jacobmpeters @FrogGirl1123 Just a heads up, we may need to go a 3rd round of selection/crosswalk invitations for the ROI Qualitative Interviews. DCCPS has a couple more interviews to get through this week and will update the tracking spreadsheet on Friday but we may be still just a few participants short of their sampling size goal of 15-20 by the end of the week. We will decide on Monday morning whether we will go an additional round based on the response rate DCCPS provides on Friday.

Hi @BrittanyCrawford405 we are going to need to go a 3rd round of invitations for the ROI Qual Interviews. The invitations won't go out until after the holidays, but we would like to go ahead and begin finalizing the selection. In order for DCCPS to provide us with an updated sampling frame for round 3, they need to get the current demographic information for individuals who have opted in for the 1st and 2nd batches combined.
Here is the masked ID tracker list of individuals who have opted in. Can you use this list and the crosswalk to run high level demographic information on those that have 'opted in'? Please create a table similar to table 4 for the initial batch distributions but updated for everyone who has opted in so far.
The only thing that may need to chage is this table has age as 'LT 40' and 'LE 40' and DCCPS is looking to oversample people in the upper and lower ends of the age range. @m-j-horner do you think Brittany should update the age categories to be more specific? Perhaps do 5 year age groups?

@robertsamm Thanks for the update! I'll begin working on the demographics table and keep an eye out for input on the age categories.

The only thing that may need to chage is this table has age as 'LT 40' and 'GE 40' and DCCPS is looking to oversample people in the upper and lower ends of the age range. @m-j-horner do you think Brittany should update the age categories to be more specific? Perhaps do 5 year age groups?

@BrittanyCrawford405  @robertsamm  please use 5 year age groups

Good morning @BrittanyCrawford405, this can be uploaded here: https://nih.app.box.com/folder/290756387567. Can you name the file with something that distinguishes it as 1st and 2nd batch opt in distributions? or opt in distributions as of X date? As there a couple of similar files in that folder at this point?

Thanks @robertsamm! The file 'OptinDistributions_asof_12132024' has been uploaded to the Box folder.

Thanks @BrittanyCrawford405 I have shared this with the DCCPS team! Once they review and provide us with an updated sampling plan for the 3rd batch, we can begin the selection and masking process for the 3rd round. We're hoping to have this ready to go in early Jan.
Noting, that we'll likely need their IRB amendment approval for expanding the sampling plan before we place the 3rd batch selection and masked ID lists in the shared Box folder with DCCPS.
Tagging @jacobmpeters and @m-j-horner for their awareness of next steps.

Hello @BrittanyCrawford405 I have uploaded the sampling plan for Batch 3 to Box here: https://nih.app.box.com/file/1728715009344. Can you please work on the selection process for Batch 3 and reach out to Nicole if you have any questions?
The selection can be uploaded to Box here in our internal CCC Data folder: https://nih.app.box.com/folder/290062713308
Tagging @jacobmpeters for his awareness as once the selection is finalized and approved we can move on to creating the list of masked IDs and crosswalk. DCCPS received IRB approval yesterday, so no concerns with sharing the finalized masked ID list for the 3rd batch with DCCPS once it is ready.

Will do, thanks @robertsamm!


README typo

Hey @juco
This is not a typo, this snippet refers to the alpine image, which ships with ash.
Closing, but do let us know if you have any trouble with consulting the logs.


Issues with requirements.txt and Compatibility

I've been struggling for the past three days trying to get this repository to work, and I'm quite frustrated. It would be really helpful to have a detailed and accurate requirements.txt file. I have Python 3.11 installed, and the current requirements.txt installs Torch 2.4. However, I've read that Torch 2.0.1 and CUDA 12.2 were used. I'm confused about how CUDA 12.2 is supposed to be compatible with Torch 2.0.1. My attempts to get this setup working have failed. Additionally, I noticed another contributor is using CUDA 11.8 with Torch 2.1.0, which seems more compatible, but I still encountered issues with torch.compile(model) on Windows.
Please complete the requirement.txt with the corresponding versions of the libraries used. Information about the system used and how to use it for Windows users would also save hours or days of trial and error.

Hi! All code was tested on Linux, Windows is not something we can support.


Color of the bitmap changing from red to blue ?

Hi,
Thank you so much for the awesome library. Unfortunately when I tried to get bitmap from a tiff file using TiffLoader.getBitmap(int dir,int sampleSize) , but the color of the bitmap is changed from red to blue. I checked the config it is ARGB_8888. Can you please suggest a solution on this issue?

What version do you use? There is no class TiffLoader in library.

@ksyamkrishnan perhaps you are swapping red/blue channels, or your image has the channels reversed (BGR instead of RGB). In TiffBitmapFactory.Options there is one option named inSwapRedBlueColors that is usually set to false, but perhaps you need or are setting it the other way round.

There was a problem with swapping red and blue colors. It was fixed but for some reason I decided to keep inSwapRedBlueColors option.
Any way in the latest release <IP_ADDRESS> this problem is solved


app_loader failure at tensorflow.org makes website unusable

System information

TensorFlow version: N/A
Doc Link: https://www.tensorflow.org/

My locale is set to uk_UA. When I visit https://www.tensorflow.org/, the app_loader.js tries to load https://www.gstatic.com/devrel-devsite/v138ceba75b8052825cb18f1c6025ea06485e9d36137e0fd82d2d54619f803209/tensorflow/js/devsite_app__uk.js (notice the added '__uk' suffix). The file does not exist. Since devsite_app.js provides the main functionality, none of the links, buttons, and selectors that use JavaScript are operational. This includes the top nav bar, the side nav bar, and the search. It also makes it very hard to navigate to APIs and to browse the API pages. It is not possible to change the language, because the language drop-down is also using JavaScript.
The problem persists across different browsers (Firefox, Safari, Chrome, Vivaldi) and I assume it also affects other locales for which a localised devsite_app.js is not available (for instance, Belarusian be, Croatian hr, etc.)
Ideally, the app_loader should check whether the localised version exists. If not, it should load the unlocalised version instead.
I'm sorry if this is not the right place for the bug. However, it is directly related to the documentation and I could not find any other places to submit.

Thanks, Roman.
I've filed an an internal bug against site infra: b/126800213

Marked as fixed in b/116473083
I think this is the same issue as https://github.com/tensorflow/tensorflow/issues/26449


Implement object deep inspector (#8456)

What type of PR is this?
/kind bug
What this PR does / why we need it:
Original PR on ingress-nginx: https://github.com/kubernetes/ingress-nginx/pull/8456
Reference:
CVE-2021-25745: Ingress-nginx path can be pointed to service account token file
CVE-2021-25746: Ingress-nginx directive injection via annotations
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Implement object deep inspector

/cc @RainbowMango


Filter date range

In your feature board there is a filter by date-range.
if i place daterange the date pickers disapear.

Working on it. I had not quite finished that feature yet...


NetCDF should reject hdf5 files with cycles of symbolic links

Hello,
I am contributing to a project which reads files in a large number of formats, including NetCDF and a format built on hdf5 which contains cycles of symbolic links. While working on integrating all these formats, we noticed that we can feed this hdf5 format into the NetCDF API and cause a crash after a long delay.
I would like to suggest adding some heuristics for the hdf5 backend that check whether or not the hdf5 file is in fact a NetCDF file.
(I note that I have only tried this with the Python API.)
Thanks for your time.
Environment Information

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

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

32 and/or 64 bit?

[ ] 32-bit
[x] 64-bit

What build system are you using?

[ ] autotools (configure)
[ ] cmake

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

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

Steps to reproduce the behavior
The following Python script creates an hdf5 file and then reads it into NetCDF, reproducing the problem.
import h5py
import numpy as np
f = h5py.File("test.h5","w")
grp=f.create_group('discretizations')
subgrp=grp.create_group('root-disc')
subgrp.create_dataset('disc',data=np.array([0,1,2]))
subsubgrp=subgrp.create_group('first-level')
f['discretizations/root-disc/first-level/parent']=h5py.SoftLink('/discretizations/root-disc')
subsubgrp.create_dataset('disc',data=np.array([0,1,2]))
f.close()

from netCDF4 import Dataset
f=Dataset('test.h5')

Currently, netcdf-c explicitly will not accept and HDF5 file
with group cycles (including symlinks). Testing this on a file
can be somewhat time consuming, so it would best be pushed off
to a tool.

Thanks for your reply. That makes total sense.
In our case, we use heuristics such as file name or opening the file via a backend to check it looks like a NetCDF file. We just wanted to make sure that you were aware that when faced with such a file the API does not fail gracefully.

It may be worth noting that the crash is in the form of a segmentation fault, so this is a possible security/DOS issue.

Can you send me your test file that causes a crash?

Is the test script in the issue not sufficient? It’s been a couple years now and we may not be able to track down the original problematic file.

I will come up with a test file, probably tomorrow, and start to explore this issue. I will see if I can reproduce the seg fault.
My first thought for a solution is that I can look at the objinfo and get a unique set of integers that identify a group. If I do that for each group, I should be able to tell that I am in the same group again. In that way, I can detect loops.
We can just error at that point or, if we can figure out what to do that is useful, we can do that. First I will see if I can detect that it is happening, and I would like to ensure that checking it does not impact performance, since I've been working hard to increase performance and reduce what the library does when opening a file. Most files do not have loops, and I don't want to kill performance for everyone checking for loops.

On python3.7, using h5py 2.8.0 (not sure what the underlying hdf5 version is), numpy 1.15.0, and netCDF4 1.4.0 running the script @Yurlungur attached in the initial report consumes ~25 GB of RAM on my MacOS 10.13 system. It doesn't crash but it does cause my system to start hitting the page file pretty hard and uses all available RAM.

Ah, here we are:
Summary of the h5py configuration
---------------------------------

h5py    2.8.0
HDF5    1.10.2
Python  3.7.0 (default, Jun 29 2018, 20:13:13)
[Clang 9.1.0 (clang-9<IP_ADDRESS>)]
sys.platform    darwin
sys.maxsize<PHONE_NUMBER>854775807
numpy   1.15.0

I have tested with both 1.10.1 and 1.10.2, and in both cases it rejects my circularly linked file with NC_EHDFERR. There is no detectable difference in time to execute with or without the statement that attempts to open the file.
I have a test for this which will be added to the code base when it gets merged, so we can detect if this fails in the future, or in other circumstances (i.e. one of the many CI test variants).

Since detecting cycles is O(V+E),  you are unlikely to see any major performance
hit unless you have a large number of groups.
It occurs to me that we might be able to do incremental cycle detection
as the netcdf library walks part or all of the groups. As each group is read,
we could do the cycle check for just that group. The cost would be the same
but would be spread out over the group read costs.  Since we do not do
lazy group reading, this might not save much.

OK, good point, but the sample given to recreate the problem uses only a couple of groups.
@Yurlungur did the problems only occur on files with lots of groups? Do you have any sample files on which a problem occurred?

@edhartnett I can try to track down the original problem file for you, but it's been many years since I encountered this problem. The original problem indeed had a large number of groups. However, as @ngoldbaum points out, the test script I provided, which generates a file, caused problems for me. And that file produces only four groups.

Thank you for looking into this, by the way!


How I can add cache header?

Exists any feature to enable cache header in response?
You accept pull request for this?

I've added a new feature in version 0.5.5, take a look: https://django-db-file-storage.readthedocs.io/en/stable/#customizing-http-headers
Does that work for you?

I try this
path('files/get/', db_file_storage_views.get_file,
        {
            'add_attachment_headers': False,
            'extra_headers': {'Cache-Control': 'public, max-age=31536000'}
        },
        name='db_file_storage.get_file'),

In response header a see the cache-control header but when a refresh the page the server send a response with status 200 and not 304.

@dannluciano
AFAIK, when the server sends a Cache-Control header, the responsibility of caching the response falls on the client. The browser (or whatever your client is) should handle this.
In the example below, I changed the URLs of the demo project like this:
    url(
        r'^book-cover-view/',
        db_file_storage_views.get_file,
        {
            'add_attachment_headers': False,
            'extra_headers': {'Cache-Control': 'public, max-age=31536000'}
        },
        name='book.view_cover'
    ),

And I changed the books list template to use the new URL:
<img height=64 width=64 src="{% url 'model_files:book.view_cover' %}?name={{ obj.cover }}" />

As you can see in the screenshot below, Google Chrome handles the caching process: after fetching the image once, it was stored in the browser's cache and it was not requested again from the server.

Nice. In Firefox when I reload the page with 'F5' the images sent by whitenoise return 304 and images sent by db_file_storage returns 200. But when I reload the same page with a link the images sent by db_file_storage return 200 but with cached value.
Thanks for your answers.

No problem
Whitenoise may be using the ETag header


what is energy_penalty returned by triggerConstantContract?

What is this data?
Why isn't typed correctly in version 6.0.0-beta.1?
How should I use it to calculate the fees for the execution of a smart contract?

According to tron dev documentation, this data refer to the penalty energy consumption. We'll typed it in the next beta version.

so that is already counted in energy_used right?

Yes!

energy_penalty is contained in energy_used field. You don't need to concern about the return of /wallet/getcontractinfo.


Kubernetes menu options don't automatically update after upgrade from 1.2 to 1.3

Rancher Version: master
Steps to Reproduce:

Create a kubernetes environment with kubernetes 1.2
After it is fully setup, upgrade it to 1.3
Check the kubernetes menu

Results: Menu doesn't update to the new 1.3 menu with stacks and deployments until a refresh
Expected:  Shouldn't have to refresh

Version - v1.2.0-pre4-rc4
Verified fixed


Confirmation does not work with one-time config

Given replace as the default behavior sometimes I try to confirm with insert (if there is no character matching to keyword_pattern at the end of suggestion).
  confirmation = {
    default_behavior = cmp.ConfirmBehavior.Replace,
  },

  mapping = cmp.mapping.preset.insert({
    ['<C-m>'] = cmp.mapping.confirm({
      behavior = cmp.ConfirmBehavior.Insert,
      select = true,
    }),
  }),

but I cannot pass one-time configuration. With
diff --git a/lua/cmp/init.lua b/lua/cmp/init.lua
index f8a1340..5986220 100644
--- a/lua/cmp/init.lua
+++ b/lua/cmp/init.lua
@@ -183,6 +183,7 @@ end)
 cmp.confirm = cmp.sync(function(option, callback)
   option = option or {}
   option.select = option.select or false
+  print(vim.inspect(option))
   option.behavior = option.behavior or cmp.get_config().confirmation.default_behavior or cmp.ConfirmBehavior.Insert
   callback = callback or (function() end)

I still get
{
  behavior = "replace",
  select = true
}

instead of expected insert.

I can't reproduce. Please update nvim-cmp (and if you use packer.nvim, please try packer compile.)

I use nvim-cmp as a git submodule and have the current main (I would not able to test  347fabf without it). To ensure that no outdated cache is loaded I disabled https://github.com/lewis6991/impatient.nvim.
Maybe more complete example based on https://github.com/hrsh7th/nvim-cmp/blob/main/utils/vimrc.vim will be needed to (not) confirm it, but I need some time to prepare and test it.

Hm... OK. I'll try to re-check this if I have spent of time.

Please run nvim -u /tmp/vimrc.vim /tmp/test
if has('vim_starting')
  set encoding=utf-8
endif
scriptencoding utf-8

if &compatible
  set nocompatible
endif

let s:plug_dir = expand('/tmp/plugged/vim-plug')
if !filereadable(s:plug_dir .. '/plug.vim')
  execute printf('!curl -fLo %s/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim', s:plug_dir)
end

execute 'set runtimepath+=' . s:plug_dir
call plug#begin(s:plug_dir)
Plug 'hrsh7th/nvim-cmp'
Plug 'hrsh7th/cmp-buffer'
call plug#end()
PlugInstall | quit

lua << EOF
local cmp = require 'cmp'
cmp.setup {
  mapping = {
    ['<C-Space>'] = cmp.mapping(cmp.mapping.complete(), {'i', 'c'}),
    ['<CR>'] = cmp.mapping.confirm({ select = true }),
    ['<C-m>'] = cmp.mapping.confirm({
      behavior = cmp.ConfirmBehavior.Insert,
      select = true,
    }),
  },
  confirmation = {
    default_behavior = cmp.ConfirmBehavior.Replace,
  },
  completion = {
    completeopt = 'menu,menuone',
  },

  sources = cmp.config.sources({
    { name = "buffer" },
  }),
}
EOF

append
this
that
test

to /tmp/test, go to t in that, press a then <C-Space>.

compare confirmation the first item with <CR> and <C-m>.
(offtop, but related to bug mentioned in https://github.com/hrsh7th/nvim-cmp/issues/1146#issuecomment-1223667380) look at the confirmation of the next item.

    ['<A-CR>'] = cmp.mapping.confirm({select = true, behavior = cmp.ConfirmBehavior.Insert}),

The above assignment works but '' not. In Insert mode <C-m> has the same effect as <CR> - maybe it's the reason.


Consider Dapr sidecar to implement a file watcher to pickup binding file updates

Watching the binding folder in standalone mode and picking up new binding changes provide a behavior more consistent with the Kubernetes mode.

Closing it for now, will revisit if enough users request for this functionality in standalone mode.


US 17 As an author, I want to delete my own public posts.

Working on US 17 by adding a ellipsis menu button with delete post as one of the options to each post object. Next step is to create logic for the delete post button in the front end.


Still getting "error acquiring lock"

I'm using graphroot at /scratch/fedid/podman and overlay filesystem. I thought the overlay was supposed to fix the below errors, but I still have them:
ERRO[0001] Refreshing container c3aec97f7c02f9157f8de0cb494647969fd551408d80b3e48d5ba9d11b48584c: error acquiring lock 0 for container c3aec97f7c02f9157f8de0cb494647969fd551408d80b3e48d5ba9d11b48584c: file exists
restarting stopped dev-c7 container latest ...
dev-c7

Do I have the wrong idea?

Andy,
please can you try adding the latest changes described in here to your storage.conf file
https://dls-controls.github.io/dev-c7/main/how-to/podman.html#update-settings
particularly
mount_program = "/bin/fuse-overlayfs"

If that does not work come and chat to me

First ran with run-devc7.sh -d to delete the old copy of the container.
We don't know what the problem is but below looks like it fixed it
diff --git a/libpod.conf b/libpod.conf
index cd19506..c96b0e0 100644
--- a/libpod.conf
+++ b/libpod.conf
@@ -22,4 +22,5 @@ EventsLogFilePath = ""
 detach_keys = "ctrl-p,ctrl-q"

 [runtimes]
-  runc = ["/usr/bin/runc", "/usr/sbin/runc", "/usr/local/bin/runc", "/usr/local
/sbin/runc", "/sbin/runc", "/bin/runc", "/usr/lib/cri-o-runc/sbin/runc"]
+  crun = ["/usr/bin/crun", "/usr/sbin/crun", "/usr/local/bin/crun", "/usr/local/sbin/crun", "/sbin/crun", "/bin/crun", "/usr/lib/cri-o-runc/sbin/crun"]


Treat trivy errors as warnings

Description

License Acceptance

[x] This repository is Apache version 2.0 licensed and by making this PR, I am contributing my changes to the repository under the terms of the Apache 2 license.

Type of changes

[ ] Add/update a helper script
[ ] Add/update link to an external resource like a blog post or video
[ ] Bug fix
[ ] New feature
[x] Test updates
[ ] Text cleanups/updates

Checklist

[x] I have read the CONTRIBUTING document.
[x] All new and existing tests pass.
[ ] Any scripts added use #!/usr/bin/env interpreter instead of potentially platform-specific direct paths (#!/bin/sh is an allowed exception)
[ ] Scripts added/updated in this PR are all marked executable.
[ ] Scripts added/updated in this PR do not have a language file extension unless they are meant to be sourced and not run standalone. No one should have to know if a script was written in bash, python, ruby or whatever. Not including file extensions makes it easier to rewrite the script in another language later without having to change every reference to the previous version.
[ ] I have confirmed that any links added or updated in my PR are valid.

🦙 MegaLinter status: ❌ ERROR

Descriptor
Linter
Files
Fixed
Errors
Elapsed time

✅ ACTION
actionlint
1

0
0.01s

✅ COPYPASTE
jscpd
yes

no
1.02s

❌ DOCKERFILE
hadolint
1

1
0.08s

✅ EDITORCONFIG
editorconfig-checker
2

0
0.01s

✅ REPOSITORY
gitleaks
yes

no
0.28s

✅ REPOSITORY
git_diff
yes

no
0.0s

✅ REPOSITORY
secretlint
yes

no
0.64s

⚠ REPOSITORY
trivy
yes

1
4.19s

✅ SPELL
misspell
2

0
0.04s

✅ YAML
prettier
1

0
0.4s

✅ YAML
v8r
1

0
2.14s

✅ YAML
yamllint
1

0
0.19s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff
MegaLinter is graciously provided by


fix typo

Signed-off-by: sgbasaraner<EMAIL_ADDRESS>Description
Rebased version of https://github.com/opensearch-project/OpenSearch/pull/1245
Check List

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

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

start gradle check

start gradle check


Use httpx instead of requests

Description
Please include a summary of the change and specify which issue is being addressed. Additionally, provide relevant motivation and context.
Fixes # (issue number)
Type of change
Please delete options that are not relevant.

[x] Bug fix (a non-breaking change that resolves an issue)

Checklist

[x] My code adheres to the style guidelines of this project (scripts/lint.sh shows no errors)
[x] I have conducted a self-review of my own code
[x] I have made the necessary changes to the documentation
[x] My changes do not generate any new warnings
[x] I have added tests to validate the effectiveness of my fix or the functionality of my new feature
[x] Both new and existing unit tests pass successfully on my local environment by running scripts/test-cov.sh
[x] I have ensured that static analysis tests are passing by running scripts/static-anaylysis.sh
[x] I have included code examples to illustrate the modifications

@davorrunje @rjambrecic why it is marked as a new release?

@davorrunje @rjambrecic why it is marked as a new release?

We need a new version with all the changes we made since 0.1.5 for making a tutorial video. Just to make it more consistent with what we have.


Renaming section twincat3 to PLC

What does this PR do?
Improve repo
For resources
Description
Why is this valuable (or not)?

There are more PLC systems than TwinCat-3 https://en.wikipedia.org/wiki/Programmable_logic_controller like SCADA, so better be generalist to improve #4579 #5092
Synchronize TOC with missing listing sections.

How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines
[x] Search for duplicates. Completes #5517
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction)

Followup

Check the output of Travis-CI for linter errors!

This is a good change. Our headings are there to help users find things, and I'm pretty sure more people have heard of "PLC's" than have heard of "Twincat".


Fixes #8: connection leak when the response is terminated unexpectedly

Changed connection close/release strategy to support unexpected request
terminations.

Shouldn't it be merged and published already?
Is there an issue with the code, it seems fine to me :)

This has been resolved by #14


Installer failed with exit code:<PHONE_NUMBER> While trying to download with winget.

Im sorry for opening a new issue, i accidently closed the other one. This time i tried installing with winget
The error is in the title. (this still didnt create any logs)

Just checked online and the value for this error in hex is 0xe0434352, which seems to indicate a problem with the runtime. You've installed it for the first time just now, right? Can I see the runtime listed in Apps & Features?

sorry for the language but im polish, here you go.

Can you try uninstalling the first and the second one, and then install this one?

Alright, give me some minutes and ill try.

Alright, it works. Thanks for support.

Oh, it does? Okay, great!


make DummyFeaturization

We want to enforce that Atoms objects with encoded features populated always carry a featurization. However, for certain model layers (e.g. graph convolution), the output is another such Atoms object, but the original featurization doesn't actually make sense anymore (and in fact may not even be strictly valid if the size of the feature matrix changed through the layer). Hence, we should probably make a DummyFeaturization to basically be a placeholder and if you try to actually do a decode with it, it gives some helpful message explaining why it can't decode.
On a related note, I had to comment out some checks in the main AtomGraph constructor that were validating that the encoded features actually matched the featurization (because it now dispatches on AbstractFeaturization rather than GraphNodeFeaturization specifically), so we could just make a new function like validate_features(encoded, fzn) that would dispatch across different featurization types, and if you fed in a DummyFeaturization it would always say it was okay.
Labeling priority because some solution to this is needed to make AtomicGraphNets compatible with the restructured package.

On second thought, since we don't really have a specific use for validate_features right now, I'm putting that in a separate issue #YAGNI


integration with CraueFormFlowBundle

Hello,
I might have missed something obvious but I've failed to get my translatable fields working with CraueFormFlowBundle (sf2.8 project), although I've got translated fields working in sonata.
The fields show up nicely, and I can save data once, but when I come to edit data, saved data won't be retrieved, leading to blank fields and in case of form submission, database constraint violations because new inserts are done.
I've already opened an issue for CraueFormFlowBundle but I'm not sure of where the issue really comes from so I opened this issue too.
Any idea about what could be wrong ?

Problem fixed, quite basic issue (was missing the translations in the select part of the doctrine query, required as partial loading was forced).
Sorry for the distraction.


Shut downs when hitting Enter on the arrow for more options

Hey,
I just installed this theme, and as the title says, I'm unable to see the "more options" menu when moving to the arrow and hitting Enter. Is there any log I can look up so we can figure this out?
Great theme, thanks!

The down arrow isn't for more options unfortunately. It literally does mean shutdown.
I don't think there's a way in rEFInd to create a sub menu.

Oh... What about the options like "boot to Lenovo Repair tool, boot to memcheck", etc.? I have a row of about seven icons below my main OSes.
I like that they're hidden, but is there any way to access them?

For me I don't use those features, so in this theme I've hidden them.
There was some small discussion about adding icons for things like that over in #15 but I haven't gotten around to finding something exactly to my liking.
You would have to petition Roderick to have a feature added to rEFInd that allows the extra options to be hidden away.


Not able to dismiss the tooltip of "Clear Filters" button and "1" control using the "Esc" key

Actual:
When we navigate to "Clear Filters" button and "1" control using Tab key tooltip appears but we are not able to dismiss the tooltip of "Clear Filters" button and "1" control using the "Esc" key
Expected:
The user should be able to dismiss the tooltip of "Clear Filters" button and "1" control using the "Esc" key

Fixed in v0.5 (2413b17b8cf2f5a11cf4238df5418f00eddd43a1). Thanks for reporting!

Fixed in v0.5 (2413b17b8cf2f5a11cf4238df5418f00eddd43a1). Thanks for reporting!


bitcoin: 0.15.1 -> 0.16.0

Bitcoin 0.16.0 now builds against the lastest Boost.
Motivation for this change
Things done

[ ] 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
[ ] other Linux distributions

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

@GrahamcOfBorg build bitcoin

Failure on x86_64-darwin (full log)
Partial log (click to expand)
checking for miniupnpc/upnpcommands.h... yes
checking for main in -lminiupnpc... (cached) yes
checking miniupnpc/upnperrors.h usability... yes
checking miniupnpc/upnperrors.h presence... yes
checking for miniupnpc/upnperrors.h... yes
checking for main in -lminiupnpc... (cached) yes
checking for Qt5Core Qt5Gui Qt5Network Qt5Widgets... no
configure: error: Qt dependencies not found
builder for '/nix/store/l4l64vx9m952k6s3lkq6l89w8hga79qr-bitcoin-0.16.0.drv' failed with exit code 1
error: build of '/nix/store/l4l64vx9m952k6s3lkq6l89w8hga79qr-bitcoin-0.16.0.drv' failed

@jb55 Would you like to review?

Failure on x86_64-linux (full log)
Partial log (click to expand)
libtool: warning: library '/nix/store/qbbvdpg81bp9lrmr35kl40vgb98iwahk-qtbase-5.10.1/lib/libQt5DBus.la' was moved.
libtool: warning: library '/nix/store/qbbvdpg81bp9lrmr35kl40vgb98iwahk-qtbase-5.10.1/lib/libQt5Core.la' was moved.
libtool: warning: library '/nix/store/qbbvdpg81bp9lrmr35kl40vgb98iwahk-qtbase-5.10.1/lib/libQt5Core.la' was moved.
  CXX      qt/test/qt_test_test_bitcoin_qt-compattests.o
  CXX      qt/test/qt_test_test_bitcoin_qt-rpcnestedtests.o
  CXX      qt/test/qt_test_test_bitcoin_qt-test_main.o
  CXX      qt/test/qt_test_test_bitcoin_qt-uritests.o
  CXX      test/qt_test_test_bitcoin_qt-test_bitcoin.o
building of ‘/nix/store/z9k7ch7wljp98ijv91xphps43aiha9br-bitcoin-0.16.0.drv’ timed out after 1800 seconds
error: build of ‘/nix/store/z9k7ch7wljp98ijv91xphps43aiha9br-bitcoin-0.16.0.drv’ failed

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/5sz9s7147sj5ksrj0hbz6w0b3lzc1bv7-bitcoin-0.16.0/bin/test_bitcoin-qt
shrinking /nix/store/5sz9s7147sj5ksrj0hbz6w0b3lzc1bv7-bitcoin-0.16.0/bin/test_bitcoin
shrinking /nix/store/5sz9s7147sj5ksrj0hbz6w0b3lzc1bv7-bitcoin-0.16.0/lib/libbitcoinconsensus.so.0.0.0
gzipping man pages under /nix/store/5sz9s7147sj5ksrj0hbz6w0b3lzc1bv7-bitcoin-0.16.0/share/man/
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/5sz9s7147sj5ksrj0hbz6w0b3lzc1bv7-bitcoin-0.16.0/lib  /nix/store/5sz9s7147sj5ksrj0hbz6w0b3lzc1bv7-bitcoin-0.16.0/bin
patching script interpreter paths in /nix/store/5sz9s7147sj5ksrj0hbz6w0b3lzc1bv7-bitcoin-0.16.0
checking for references to /tmp/nix-build-bitcoin-0.16.0.drv-0 in /nix/store/5sz9s7147sj5ksrj0hbz6w0b3lzc1bv7-bitcoin-0.16.0...
postPatchMkspecs
/nix/store/5sz9s7147sj5ksrj0hbz6w0b3lzc1bv7-bitcoin-0.16.0

@GrahamcOfBorg build bitcoind

Failure on x86_64-linux (full log)
Partial log (click to expand)
error: attribute ‘bitcoind’ in selection path ‘bitcoind’ not found

Failure on x86_64-darwin (full log)
Partial log (click to expand)
error: attribute 'bitcoind' in selection path 'bitcoind' not found

@GrahamcOfBorg build altcoins.bitcoind

@GrahamcOfBorg build altcoins.bitcoind

Failure on x86_64-darwin (full log)
Partial log (click to expand)
checking for exit in -lboost_filesystem... yes
checking whether the Boost::Program_Options library is available... yes
checking for exit in -lboost_program_options... yes
checking whether the Boost::Thread library is available... yes
checking for exit in -lboost_thread... yes
checking whether the Boost::Chrono library is available... yes
checking for exit in -lboost_chrono... yes
configure: error: hexdump is required for tests
builder for '/nix/store/w496gy6f7d7j366k4gnhd0jkcqlmq3sq-bitcoind-0.16.0.drv' failed with exit code 1
error: build of '/nix/store/w496gy6f7d7j366k4gnhd0jkcqlmq3sq-bitcoind-0.16.0.drv' failed

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0/bin/bitcoind
shrinking /nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0/bin/bench_bitcoin
shrinking /nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0/bin/test_bitcoin
shrinking /nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0/lib/libbitcoinconsensus.so.0.0.0
gzipping man pages under /nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0/share/man/
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0/lib  /nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0/bin
patching script interpreter paths in /nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0
checking for references to /tmp/nix-build-bitcoind-0.16.0.drv-0 in /nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0...
/nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0

it wants at least hexdump on macOS.

Yes.  Bitcoin has been broken on darwin for years.  I'm waiting for a darwin enthusiast to propose a patch, but it seems there aren't any bitcoin-darwin-nix enthusiasts at the moment.
Maybe one day I can borrow a friend's OSX machine and figure out people build bitcoin on that platform.

Then it should be disabled at least on macOS.

Success on x86_64-linux (full log)
Partial log (click to expand)
/nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0

@roconnor sure, testing it now

Tested ACK 2d102cb40831d5bca73c631b6eec47313ecb1317

Failure on aarch64-linux (full log)
Partial log (click to expand)
error: attribute 'bitcoind' in selection path 'bitcoind' not found

@Mic92 How to disable darwin?  A cursory pass through the nixpkgs manual didn't reveal anything to me.

Failure on aarch64-linux (full log)
Partial log (click to expand)
  CXX      libbitcoin_server_a-addrdb.o
  CXX      libbitcoin_server_a-addrman.o
  CXX      libbitcoin_server_a-bloom.o
  CXX      libbitcoin_server_a-blockencodings.o
  CXX      libbitcoin_server_a-chain.o
  CXX      libbitcoin_server_a-checkpoints.o
  CXX      consensus/libbitcoin_server_a-tx_verify.o
  CXX      libbitcoin_server_a-httprpc.o
building of '/nix/store/6ylmqf9qn4r1gzdi8lk4411qbn3vgjg4-bitcoin-0.16.0.drv' timed out after 3600 seconds
error: build of '/nix/store/6ylmqf9qn4r1gzdi8lk4411qbn3vgjg4-bitcoin-0.16.0.drv' failed

Failure on aarch64-linux (full log)
Partial log (click to expand)
  CXX      libbitcoin_server_a-net.o
  CXX      libbitcoin_server_a-net_processing.o
  CXX      libbitcoin_server_a-noui.o
  CXX      policy/libbitcoin_server_a-fees.o
  CXX      policy/libbitcoin_server_a-policy.o
  CXX      policy/libbitcoin_server_a-rbf.o
  CXX      libbitcoin_server_a-pow.o
  CXX      libbitcoin_server_a-rest.o
building of '/nix/store/fahgs13jyam3bbcmkgld52b5224g4sf9-bitcoind-0.16.0.drv' timed out after 3600 seconds
error: build of '/nix/store/fahgs13jyam3bbcmkgld52b5224g4sf9-bitcoind-0.16.0.drv' failed

Failure on aarch64-linux (full log)
Partial log (click to expand)
gcc gen_context.o -o gen_context
./gen_context
  CC       src/libsecp256k1_la-secp256k1.lo
  CCLD     libsecp256k1.la
/nix/store/lvx1acn1ig1j2km8jds5x3ggh3f2wa8v-binutils-2.28.1/bin/ar: `u' modifier ignored since `D' is the default (see `U')
make[3]: Leaving directory '/build/bitcoin-0.16.0/src/secp256k1'
  CXXLD    libbitcoinconsensus.la
  CXX      bitcoind-bitcoind.o
building of '/nix/store/6ylmqf9qn4r1gzdi8lk4411qbn3vgjg4-bitcoin-0.16.0.drv' timed out after 3600 seconds
error: build of '/nix/store/6ylmqf9qn4r1gzdi8lk4411qbn3vgjg4-bitcoin-0.16.0.drv' failed

Failure on aarch64-linux (full log)
Partial log (click to expand)
  CXX      libbitcoin_server_a-bloom.o
  CXX      libbitcoin_server_a-blockencodings.o
  CXX      libbitcoin_server_a-chain.o
  CXX      libbitcoin_server_a-checkpoints.o
  CXX      consensus/libbitcoin_server_a-tx_verify.o
  CXX      libbitcoin_server_a-httprpc.o
  CXX      libbitcoin_server_a-httpserver.o
  CXX      libbitcoin_server_a-init.o
building of '/nix/store/fahgs13jyam3bbcmkgld52b5224g4sf9-bitcoind-0.16.0.drv' timed out after 3600 seconds
error: build of '/nix/store/fahgs13jyam3bbcmkgld52b5224g4sf9-bitcoind-0.16.0.drv' failed

@roconnor  for example by changing meta.platforms = platforms.unix; to platforms = platforms.linux;.

Thanks.  I'll look into it.
FWIW, I think https://github.com/NixOS/nixpkgs/issues/25188 could provide a solution to this problem if implemented.

@roconnor in future maybe.

@Mic92 Okay, I've added a dependency on darwin.shell_cmds.  I think this actually may fix the build on darwin but I don't have a machine to test it on.  Maybe we can try GrahamcOfBorg?
If it fails, I'll revert and change the meta.platforms instead.

@GrahamcOfBorg build altcoins.bitcoind

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Try '/nix/store/h4i092yq3v0dh48g3flj5nvyh27sdw6a-bison-3.0.4/bin/bison --help' for more information.

** BUILD FAILED **

The following build commands failed:

(1 failure)
builder for '/nix/store/zgm4av2j3ypbavpqwnq630macpc63jf1-shell_cmds-osx-10.11.6.drv' failed with exit code 1
cannot build derivation '/nix/store/s5d9cl3bgj2l688f9blnvdqh6xh16zan-bitcoind-0.16.0.drv': 1 dependencies couldn't be built
error: build of '/nix/store/s5d9cl3bgj2l688f9blnvdqh6xh16zan-bitcoind-0.16.0.drv' failed

@LnL7 out of general interest by looking at the error message, does bison in nixpkgs comes from GNU or from macOS?

I see, darwin.shell_cmds doesn't even build.  I guess this is too far out of my league.  I'll disable darwin builds.

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0/bin/bitcoin-tx
shrinking /nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0/bin/bitcoind
shrinking /nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0/bin/bench_bitcoin
shrinking /nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0/lib/libbitcoinconsensus.so.0.0.0
gzipping man pages under /nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0/share/man/
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0/lib  /nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0/bin
patching script interpreter paths in /nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0
checking for references to /tmp/nix-build-bitcoind-0.16.0.drv-0 in /nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0...
/nix/store/bfqwgvk44b89cf2x7nfswgp9q4pn50xj-bitcoind-0.16.0

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/a848mzv0m2fh60p06yjnc0jd4kah9nh1-bitcoin-0.16.0/bin/test_bitcoin-qt
shrinking /nix/store/a848mzv0m2fh60p06yjnc0jd4kah9nh1-bitcoin-0.16.0/bin/test_bitcoin
shrinking /nix/store/a848mzv0m2fh60p06yjnc0jd4kah9nh1-bitcoin-0.16.0/lib/libbitcoinconsensus.so.0.0.0
gzipping man pages under /nix/store/a848mzv0m2fh60p06yjnc0jd4kah9nh1-bitcoin-0.16.0/share/man/
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/a848mzv0m2fh60p06yjnc0jd4kah9nh1-bitcoin-0.16.0/lib  /nix/store/a848mzv0m2fh60p06yjnc0jd4kah9nh1-bitcoin-0.16.0/bin
patching script interpreter paths in /nix/store/a848mzv0m2fh60p06yjnc0jd4kah9nh1-bitcoin-0.16.0
checking for references to /tmp/nix-build-bitcoin-0.16.0.drv-0 in /nix/store/a848mzv0m2fh60p06yjnc0jd4kah9nh1-bitcoin-0.16.0...
postPatchMkspecs
/nix/store/a848mzv0m2fh60p06yjnc0jd4kah9nh1-bitcoin-0.16.0

Failure on aarch64-linux (full log)
Partial log (click to expand)
  CXX      rpc/libbitcoin_server_a-rawtransaction.o
  CXX      rpc/libbitcoin_server_a-safemode.o
  CXX      rpc/libbitcoin_server_a-server.o
  CXX      script/libbitcoin_server_a-sigcache.o
  CXX      script/libbitcoin_server_a-ismine.o
  CXX      libbitcoin_server_a-timedata.o
  CXX      libbitcoin_server_a-torcontrol.o
  CXX      libbitcoin_server_a-txdb.o
building of '/nix/store/92k2yrv1rb32r4yjhya8ndgdlybwmf36-bitcoin-0.16.0.drv' timed out after 3600 seconds
error: build of '/nix/store/92k2yrv1rb32r4yjhya8ndgdlybwmf36-bitcoin-0.16.0.drv' failed

Failure on aarch64-linux (full log)
Partial log (click to expand)
  CXX      rpc/libbitcoin_util_a-util.o
  CXX      support/libbitcoin_util_a-cleanse.o
  CXX      libbitcoin_util_a-sync.o
  CXX      libbitcoin_util_a-threadinterrupt.o
  CXX      libbitcoin_util_a-util.o
  CXX      libbitcoin_util_a-utilmoneystr.o
  CXX      libbitcoin_util_a-utilstrencodings.o
  CXX      libbitcoin_util_a-utiltime.o
building of '/nix/store/fahgs13jyam3bbcmkgld52b5224g4sf9-bitcoind-0.16.0.drv' timed out after 3600 seconds
error: build of '/nix/store/fahgs13jyam3bbcmkgld52b5224g4sf9-bitcoind-0.16.0.drv' failed

@Mic92 Darwin builds should be disabled now.  Please merge when you are satisfied.

Failure on x86_64-linux (full log)
Partial log (click to expand)
  CXX      qt/qt_libbitcoinqt_a-moc_signverifymessagedialog.o
  GEN      qt/moc_splashscreen.cpp
  CXX      qt/qt_libbitcoinqt_a-moc_splashscreen.o
  GEN      qt/moc_trafficgraphwidget.cpp
  CXX      qt/qt_libbitcoinqt_a-moc_trafficgraphwidget.o
  GEN      qt/moc_transactiondesc.cpp
  CXX      qt/qt_libbitcoinqt_a-moc_transactiondesc.o
  GEN      qt/moc_transactiondescdialog.cpp
building of ‘/nix/store/6n4w499lf70v4kv4lmi74b9yh7pzvaqx-bitcoin-0.16.0.drv’ timed out after 1800 seconds
error: build of ‘/nix/store/6n4w499lf70v4kv4lmi74b9yh7pzvaqx-bitcoin-0.16.0.drv’ failed

Failure on aarch64-linux (full log)
Partial log (click to expand)
  CXX      libbitcoin_server_a-net.o
  CXX      libbitcoin_server_a-net_processing.o
  CXX      libbitcoin_server_a-noui.o
  CXX      policy/libbitcoin_server_a-fees.o
  CXX      policy/libbitcoin_server_a-policy.o
  CXX      policy/libbitcoin_server_a-rbf.o
  CXX      libbitcoin_server_a-pow.o
  CXX      libbitcoin_server_a-rest.o
building of '/nix/store/92k2yrv1rb32r4yjhya8ndgdlybwmf36-bitcoin-0.16.0.drv' timed out after 3600 seconds
error: build of '/nix/store/92k2yrv1rb32r4yjhya8ndgdlybwmf36-bitcoin-0.16.0.drv' failed

@Mic92 We don't have a separate version of bison as far as I know.


Add label for Button view

Resolves: #112

@asimonok
ready for review

Codecov Report
Attention: Patch coverage is 86.66667% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 99.02%.  Consider uploading reports for the commit 4d134d4 to get more accurate results

Files
Patch %
Lines

src/components/ButtonView/ButtonView.tsx
81.81%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #125      +/-   ##
==========================================
- Coverage   99.21%   99.02%   -0.19%
==========================================
  Files          51       51
  Lines        1017     1027      +10
  Branches      243      251       +8
==========================================
+ Hits         1009     1017       +8
- Misses          8       10       +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Poor result on kaggle 2016 ultrasound nerve dataset

I am trying to change surgery dataset to  custom dataset, the kaggle ultrasound nerve dataset, which can be found in https://www.kaggle.com/c/ultrasound-nerve-segmentation/data. However, the result is far less than the starting point Keras version UNet here, https://github.com/jocicmarko/ultrasound-nerve-segmentation.
The training images and corresponding masks in this custom dataset are both one channel with the size 420, 580. I have cropped them to 416, 576 and use the modified RoboticsDataset to load them.

each subdataset consists

In images folder, there are 1127 images.
Training hyperparameters:
--batch size 16
--learing rate 0.00001
--epoch 100
--Adam
--UNet
Final IoU results: (%)
-- 17.31
The IoU achieve 0.4 by using previous Keras version UNet. Could your offer me some help to illustrate this problem? Thanks a lot.

I remember that competition, I finished 10th in it.
The metric was noisy, validation did not work well and post-processing added a lot.
But IOU = 17.31 looks pretty strange.  I would expect ~0.5-0.6 out of the box.
Did your train loss stop decreasing?

it seems the loss has been converged to 0.9 ~ 1.0. I have try to modify the
loss function to dice loss, but got the same problem. Since the ultrasound
nerve dataset consists images with one channel, robot surgery dataset with
three channels, the preprocess (Normalize) will be different. Will this
preprocessing be a problem? Besides, I have tried to modify RoboticsDataset
to support loading with one channel image. with 36 epochs, IoU = 0.48447
which is far from 10 epochs IoU = 0.753 received in three channel input.
Any suggestions to deal with gray images input? Thanks a lot. I really
appreciate your help.
On Fri, Jul 6, 2018 at 2:19 PM Vladimir Iglovikov<EMAIL_ADDRESS>wrote:

I remember that competition, I finished 10th in it.
The metric was noisy, validation did not work well and post-processing
added a lot.
But IOU = 17.31 looks pretty strange. I would expect ~0.5-0.6 out of the
box.
Did your train loss stop decreasing?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ternaus/robot-surgery-segmentation/issues/9#issuecomment-402937816,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGoHF_XR4UaaUqtfLR6NQ1NDm6mSVBddks5uDwGIgaJpZM4VEuo-
.


add Dockerifle to build dagger-cue

bringing this back since it's required by the dagger-for-github action
Signed-off-by: Marcos Lilljedahl<EMAIL_ADDRESS>

Hello folks !
This is critical in the sense of :

people were pushed to use the fabulous GitHub action from dagger to see how cool it is :-)
dagger changed the cli to replace by another high level, and we must now use dagger-cue
All the CI of cool people (first adopters) are broken until they change them
Naive approach of upgrading the cli and replace dagger do by dagger run are not producing expected results: worst, it does something and output nothing and exit with 0 return code, letting the user think this is "OK"

So I guess the good move if you want to keep 1st adopters (actually I was at the point to organize a meetup about dagger to share my ❤) is to prioritize this issue and write a documentation (excuse me if it's already exists) where you state clearly that the only way for now is to pin the version to 0.2.*

Hello folks ! This is critical in the sense of :

people were pushed to use the fabulous GitHub action from dagger to see how cool it is :-)
dagger changed the cli to replace by another high level, and we must now use dagger-cue
All the CI of cool people (first adopters) are broken until they change them
Naive approach of upgrading the cli and replace dagger do by dagger run are not producing expected results: worst, it does something and output nothing and exit with 0 return code, letting the user think this is "OK"

So I guess the good move if you want to keep 1st adopters (actually I was at the point to organize a meetup about dagger to share my ❤) is to prioritize this issue and write a documentation (excuse me if it's already exists) where you state clearly that the only way for now is to pin the version to 0.2.*

Hi Fred, very sorry about this. What you describe (clearly informing early adopters + giving them an simple migration path) was/is the plan but we screwed up executing on it. We’ll prioritize fixing this.

No worries ! Was just raising the point to avoid others to dig for this issue when their CI fail :-)
Thanks for the quick prioritization and nice rework ! Actually, using a 0.x branch is an acceptance for "things may break".

Hey @fredleger, did this fix it for you? https://github.com/dagger/dagger-for-github/issues/80#issuecomment-1339918641

I just roll backed my changes from this morning, and it's working like a charm 🎉
Now i'm just waiting for asdf plugin for dagger-cue to test the dropin replacement of previous dagger cli on my laptop :-)
Thanks for the follow up

Now that we have a fix for this, I would be inclined to remove this since we don't yet know what a dagger CLI v0.2 -> v0.3 migration path will look like. I expanded on my thinking in https://github.com/dagger/dagger-for-github/pull/79#issuecomment-1341634068

SGTM!

I guess we should revisit the dagger-for-github altogether. Since the action currently has a feature to build dagger from source and requires that Dockerfile to be present to work. I think it doesn't hurt to leave the Dockerfile in the repo until we decide what to do with the github action.
I there's a reason to remove it, I'm good for that as well.


Prevent crash when checking permissions of external reviewer without shares

Check for existence of share before checking share.can_comment to prevent exception for external reviewers without shares

Not sure I follow this logic - if the Share object is the thing that determines whether an external reviewer has access to a page, why is it valid for an external reviewer not to have one?

Not sure I follow this logic - if the Share object is the thing that determines whether an external reviewer has access to a page, why is it valid for an external reviewer not to have one?

I think the idea was a Share was a separate mechanism for sharing a particular draft revision in a time limited fashion (eg the shares panel), but if it was on a particular task state, it should always be reviewable by the external users assigned to that task.


What precisely is reconnectSuggested ?

What precisely is reconnectSuggested ?

it's never explained anywhere
how to use it
If I missed the doco on that, very sorry, url ?

Kindly,

@smhk According to the comments in Transport.swift, it's delivered when "the connection has upgrade to wifi from cellular. you should consider reconnecting to take advantage of this".


New PR to test SignCLA at 2018-04-12 16:29:54.766346525 -0700 PDT m=+5.196493516

Body of PR

indiv-pass-fork-staging: test succeeded