Bug in resolving PyPI deps?

Checks

[x] I have checked that this issue has not already been reported.

[x] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
command:
pixi install

pyproject.toml:
[build-system]
build-backend = "hatchling.build"
requires = ["hatchling"]

[project]
description = "descr"
name = "my-proj"
requires-python = ">= 3"
version = "0.0.0"
readme = "README.md"
dependencies = ["tensorflow"]

[tool.pixi.project]
channels = ["conda-forge"]
platforms = [
  "linux-64",
]

[tool.pixi.pypi-dependencies]
my_proj = { path = ".", editable = true }

yields
  × failed to solve the pypi requirements of 'default' 'linux-64'
  ├─▶ failed to resolve pypi dependencies
  ╰─▶ Because only the following versions of tensorflow are available:
 ...
have no wheels with a matching Python ABI tag and you require tensorflow, we can conclude that your requirements are unsatisfiable.

hint: Pre-releases are available for tensorflow in the requested range (e.g., 2.18.0rc2), but pre-releases weren't enabled (try: `--prerelease=allow`)

Issue description
Running pixi v<IP_ADDRESS>.
Expected behavior
Tensorflow is pip installable.

There seem to be no 3.13 wheels yet. Try:
requires-python = ">=3.12, <3.13"

We install a python intepreter in the environment and 3.13 is selected as its the highest current version.


Add social buttons at the team page for email, phone and Whatsapp

Would have liked to also include Telegram and Gitlab, however - as also concluded in #13 for Gitlab - these icons are not present in the included icon packs. (Although Telegram is currently part of the latest version of the free icomoon pack).
As all the other links take the full URL instead of just the username (e.g. github = "https://github.com/Addono" instead of github = "Addono") did I do the same with the Whatsapp link. However, as it might not be completely trivial for every user might it be nice to include some example link instead of whatsapp = "#". In case one is wondering, Whatsapp links look like https://web.whatsapp.com/send?phone={phone number} where the phone number includes the country code without leading zero's or plus sign - for me it would be https://web.whatsapp.com/send?phone=31640410001.
Anyway, thanks for the port! It's nice.

OK, people can see this now, so thanks for writing in.

From your response I am not entirely sure that you that the PR still adds support for phone, email and Whatsapp. If you don't want to support them by default, then that is fine. Just made the PR as I wanted it for my own project and I can image that others have similar needs.

Yeah, but you'd closed the PR and deleted the branch, so I left it at that.

Aah, my bad. Wasn't the intention, I restored the branch. Can you re-open the PR or should I make a new one?
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, February 19, 2019 12:15 PM, Steve Lane<EMAIL_ADDRESS>wrote:

Yeah, but you'd closed the PR and deleted the branch, so I left it at that.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

OK, done, thanks for your additions. I'm going to leave the config file as it is, a quick search through the repo will find these examples. Cheers


Landing/Home Page

We need to have a landing page for the website

I would like to do this, if everyone is okay with that


appending custom kernel device tree

Hey Matt, you seem to be swamped lately so I'll keep this short.
What were the main reason(s) behind using kernel files from https://github.com/madisongh/linux-tegra-4.9 rather than the kernel provided with the L4T BSP? I don't need the whole history just a quick reason or two.
I only noticed when I was overriding customized files in tegra-binaries and I found my pmc config and pinmux config were being used in the image (verified via hashes) but my kernel device tree (.dtb) was not. I had to include the files as part of the linux-tegra recipe so they would end up in the git source tree.
# installs in the expected location but not used by linux-tegra
recipetool appendsrcfile -wm jetson-tx2-4gb ../meta-local tegra-binaries $HOME/tegra186-quill-p3489-0888-a00-00-base.dtb 'Linux_for_Tegra/kernel/dtb/tegra186-quill-p3489-0888-a00-00-base.dtb'

# installs and used by linux-tegra and other downstream recipes
recipetool appendsrcfile -wm jetson-tx2-4gb ../meta-local linux-tegra $HOME/tegra186-quill-p3489-0888-a00-00-base.dtb '../build/arch/${ARCH}/boot/dts/tegra186-quill-p3489-0888-a00-00-base.dtb'

What we have is a modified version of the kernel device tree provided by Nvidia, so I'm wondering if we should be using linux-tegra-4.9 as a base instead.

Well, I wanted to be able to build the kernel from source, so it can be customized/fixed/etc..  NVIDIA makes the kernel source available via git, but it's split across 16 or so separate repositories, which wasn't very convenient, so with each L4T release I fetch their sources and recombine them into one source tree.  Device tree sources are in there... if you have a customized device tree, you should be able to fork linux-tegra-4.9 and make the necessary modifications.

Good answer, thank you!


Prevent database connections to sqlite

CATEGORY

[x] Bug Fix
[ ] Enhancement (new features, refinement)
[ ] Refactor
[x] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY

SQLite allows users to create DBs locally on the machine running Superset. This is dangerous because it allows mapping the local filesystem and can also lead to DoS attacks. There is no good reason to be using SQLite as an analytics DB, so we've opted to prevent it from being used.
This change introduces a new flag PREVENT_UNSAFE_DB_CONNECTIONS which is true by default. Any other future unsafe db connections can be added to the same logic I've written here.
TEST PLAN

Unit tested, smoke tested locally
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS
@willbarrett @craig-rueda @nytai

It would be good to add tests for the endpoints to ensure that SQLite connection strings are rejected at the API layer. I think this deserves a partial integration test or two.

I think this is a case to write a note on UPDATING.md

Codecov Report

Merging #9218 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #9218      +/-   ##
==========================================
+ Coverage   58.91%   58.92%   +0.01%
==========================================
  Files         372      372
  Lines       11996    11999       +3
  Branches     2937     2940       +3
==========================================
+ Hits         7068     7071       +3
  Misses       4750     4750
  Partials      178      178

Impacted Files
Coverage Δ

...frontend/src/views/dashboardList/DashboardList.tsx
59.34% <0%> (ø)
:arrow_up:

...uperset-frontend/src/views/chartList/ChartList.tsx
63.39% <0%> (ø)
:arrow_up:

...ontend/src/components/ListView/TableCollection.tsx
90% <0%> (+1.11%)
:arrow_up:

Continue to review full report at Codecov.

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


Update authenticating-users-with-navuserpassword.md

Fixed typo.

Thanks for catching this, much appreciated!


Design footer for BossY

This includes designing a nice footer for the app.

@sharmaaditya570191 @somyaranjan26 I would like to work on this issue. please assign me.

@sharmaaditya570191 Can I also work on this issue?

@sharmaaditya570191 @somyaranjan26 Can I also work on this issue?

As you know one participant can work one issue at a time in a project. As @BhuwanChandra already assigned for this issue so, right now we can't assign you this issue.
@sharmaaditya570191 if you have any suggestions about any feature or design for this project, tell us on slack, if we find it appropriate we will create an issue and directly assign you.

@somyaranjan26 @sharmaaditya570191 can you tell me what I need to include in the footer?

Please wait a bit for the footer component.

@sharmaaditya570191 I would like to work on this issue.


Include package type in error messages

When changing deps over from Bower to npm packages, the error messages of what's included in the manifest but not application (and vice-versa) get confusing. This helps that!

:+1:


Archival code structure

The archival code is a bit strange in that it runs the code on importing. This is very unexpected behavior and should probably be changed.
Also, by default the code currently archives to the repository folder. The user should need to specify a save folder path, either by an input, the config, or by graphical selection, perhaps via:
http://stackoverflow.com/questions/3579568/choosing-a-file-in-python-with-simple-dialog
I'm also curious as to why the archive option isn't available through the library, e.g. library.archive()
Also, I had meant to only have one zip file instead of multiple files, I changed my mind on this halfway through the discussion and it probably was unclear. The file then should contain multiple folders as well as a single meta data file. Feel free to champion a different structure ...

The answer in the SO link you posted uses Tkinter, which I'd like to avoid. I'll be using PyQt's QFileDialog (https://doc.qt.io/qt-5/qfiledialog.html), which I'm mainly just posting here to remind myself. I'll implement it tomorrow.
Your other points should all be fixed now.

Users are now able to select file paths, and retries on connection failures / interrupts are now supported.


Use Avram format to express schema

The schema format can be changed without much modification to comply with Avram format. Seems like independent invention of a MARC schema format resulted in very similar outcome, so it must be good.

split the file into one schema file per format (e.g. bibliographic)
wrap the list of fields in a root object with key fields and add key family with value marc and
rename key leader  to LDR
remove key fixed, its value is implied by existence of subfields
rename key name to label
rename key values to codes
change object indicators with keys 1 and 2 to indicator1 and indicator2
change value of positions to an Avram position object
change staticValues to positions. Value static seems to be implied by existence of this field, so static can be removed.

By the way feedback to the specification is appreciated. Final version 1.0 should be released in 2024 with formal test suite.

In addition rename key value to code (in code lists), this will be added in Avram specification: https://github.com/gbv/avram/issues/38

This can be closed with #12 although some errors remain - I will open independent issues for these.


Bump the dependency on base to < 4.15 (was < 4.13)

GHC 8.8.* uses base = 4.13 (July 2019) and GHC 8.10.* uses base = 4.14 (January 2020).
The current .cabal file dependency for base is < 4.13, so fadno-xml will not build on these versions. It is also listed as broken (not compiling) in the set of Nix curated packages, nixpkgs.
I have checked that it compiles and runs with GHC 8.8.4, base-<IP_ADDRESS> after the dependency is changed to base < 4.14. I haven't really tested it, but the Haskell base package changelog doesn't seem to have any relevant changes, so it should be safe to change.
The packages fadno and fadno-braids are also listed as broken in nixpkgs and can likely be made to compile in the same way.

Thanks for this! I'm enabling Github CI in honor of your PR, once I get it working it would be great to merge that into this and get the result.

OK the CI is "working" (it succeeds on GHC 8.6.5 and fails on configure in 8.8.4 and 8.10.2, which is where this PR comes in :)

Merged! Thanks -- CI will tell us if there's any issues.


cleanup remove dynamic schema support from memtable

Proposed changes
Dynamic schema is no longer used, remove it from memtable.
So we can get rid of dependency on rowset writer in memtable.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Change interop calls code-generation to a more standard one

At the moment our interop packages are just stubs that declare some functions without real implementation. Calls to these stubs get replaced by syscalls in the compiler which maintains a map of functions to interop names. In general, this mechanism is far from perfect, see #397 and #913.
What's proposed here is to make our interop packages work the same way ordinary ones do by completely removing internal compiler mapping and moving syscall logic into interop packages implementation. This can be done if we're to define one low-level syscall function (compiler intrinsic) and then use it to implement interops.
So instead of
// Log instucts the VM to log the given message.
func Log(message string) {}

// Notify an event to the VM.
func Notify(arg ...interface{}) int {
        return 0
}

we'll have something like this in interops:
// Log instucts the VM to log the given message.
func Log(message string) {
    neogointernal.Syscall("Neo.Runtime.Log", message)
}

// Notify an event to the VM.
func Notify(arg ...interface{}) int {
    neogointernal.Syscall("Neo.Runtime.Notify", arg...)
    return 0
}

neogointernal package should then be declared as neo-go specific package that can't be overriden (and we'll provide a stub for it made the same way all our current interops are), we can move other intrinsics like AppCall, FromAddress, ToByteArray, etc. there and provide regular interop APIs for them too.
This should simplify our compiler a bit, solve both #397 and #913 and help solving #296 in longer term.
@fyrchik?

I like the idea, it will make adding new pretty straitforward. Maybe neogointernal should also mirro  functions declared in emit, so it's used like "inline assemly".
The only problem I can imagine is a presence of opaque types like Asset or Contract, but those can stay, and be processed in neogointernal like interop items.

By "inline assemly" I understand some interop package with low-level interops which can or can not be used in regular contracts. I.e. there will be a single package with a pretty stable interface and simple to compile, and another interop and builtin packages implemented on top of this.

There can be a problem with syscalls which must be invoked by id. We can generate ID in constants via go:generate for all provided interops.

Even if syscalls are defined as functions, make sure we inline them (like it is done now).


Multiple values support.

This is a WIP branch adding some multiple-value expression support to the interpreter. It uses bottom up typing and demonstrates that even this single pass compiler can get enough type information to generate useful output, and that adding type information to blocks is not necessary.  The code is rough, far from optimized, but this seems to be enough to demonstration the type system and the ability to handle these operations which is the main goal.
The extensions:

The values operator constructs a multiple value expression from its arguments and the values type subsumes the current void and single values types: (values) == (nop) (values (i32.const 1)) == (i32.const 1)). A single value is consumed from each argument and the rest discarded: (values (values (i32.const 1) (i32.const 2)) (values (i32.const 3) (i32.const 4)) == (values (i32.const 1) (i32.const 3))

The conc_values operator constructs a multiple value expression from the concatenation of all the values of its arguments. For example (conc_values (i32.const1) (nop) (values (i32.const 2) (i32.const 3))) == (values (i32.const1) (i32.const 2) (i32.const 3)) Valid code must have a fixed number of values for each argument to ensure that the number of consumed values for each expression is static, for example the follow is invalid: (conc_values (if (i32.const 1) (nop) (i32.const 1))). This operator would challenge top-down typing which might require encoding the number of values consumed from each argument.

The mv_call operator is similar to the call operator but accepts a single expression argument and passes all the values to the callee. For example (mv_call $f (values (i32.const1) (i32.const 2))) == (call $f (i32.const1) (i32.const 2))). This could be generalized to accept multiple arguments and concatenate all the values like conc_values but this can done with (mv_call $f (conc_values ...)) so would just be an extra convenience.

Where there are multiple exits or input/outputs for an operator, such as block/break if select, the type system accepts conflicting value types and missing values so long as they are not consumed. This makes it convenient and efficient to discard unused values which is a nice property in a language in which all operators are expressions. In the limit this gives the current behaviour for the single values types and the void/zero-value type, where single values can be discarded when not used. For example (i32.add (call $fn_returning_i32_f32) (call $fn_returning_i32)) is valid and (i32.add (call $fn_returning_i32_f32) (call $fn_returning_i32_f64)) is valid, and in both cases only the first value is consumed.

The br br_if return and potentially the br_table operators pass on all the values of their single expression. The text syntax accepts a missing expression which is encoded as a nop: (br $l) == (br $l (nop)) == (br $l (values)). For example (values (i32.const 1) (i32.const 2)) == (block (values (i32.const 1) (i32.const 2))) == (block $l (br $l (values (i32.const 1) (i32.const 2))))

Functions can return multiple values. For example (func $f1 (result i32 i64) (values (i32.const 1) (i64.const 2))) for which (call $f1) => (values (i32.const 1) (i64.const 2)). The interpreter supports returning multiple values for exported functions.

A block1 operator returns the values of the first expression and discards the values of all other block top level expressions, in contrast to the block operator that returns the values of the last expression. Combined with block this allows returning the values of an arbitrary expression in an effective block. For example (block (exp1) (block1 (exp2) (exp3))) returns the values of (exp2).

TODO Support for storing multiple values into multiple local variables would also be needed to make this viable, perhaps this could be a pick-style operation allowing some values to be ignored and some used multiple times, or just the first-n values, lots of options.

TODO Support could also be added for picking/duplicating values if this helped.

The type system:

The base types are empty and values. The empty type is the set of no types and represents the type of unreachable code. The values type is a sequence of value types, i32, i64, f32, f64, plus the union type which represents any of i32, i64, f32, or f64, plus an optional type which also includes the value being missing.

Where an expression has potentially multiple result types at runtime, the result is computed with a union operation. The union of any type with the empty type is itself. The union of values types is computed per element. If either value is the optional type or missing then the result type is optional, otherwise if the types differ the result type is union, otherwise the types are the same and this is the result type for the element. Note that this computation is an expansion of the set of result value types, not the most specific, but wasm only validly consumes values elements with a matching type, or expressions with a fixed number of values, so the union operators can be simplified to a flat sequence. For example, the precise union applied to (if (cond) (values (i32.const 1) (f32.const 2)) (values (f32.const 3) (i32.const 4))) is (or (values i32 f32) (values f32 i32)), but it is sufficient for wasm to expand this set to (values union union) == (or (values i32 i32) (values i32 i64) (values i32 f32) (values i32 f64) (values i64 i32) ...).

Type checking is a subset relationship - the actual type must be a subset of the expected type. Wasm consumers always expected a fixed number of values and all values consumed have a fixed expected type, so the expected type can not be the empty type or have values type elements of type union or optional. (Todo an expected element type for non-consumed elements). If the actual type is the empty type then this test is always true for any expected type as the empty set is a subset of all sets. If the actual and expected types are values types then all the consumed expected element types must match their respective element in the actual type, and other elements in the actual type are ignored.

Interesting, thanks for sharing this.

I see little prospect of this making the cut. A wasm focused on expressionless operators might be far simpler and meet the use cases where the call operator just returns multiple values to multiple local variables.
If I can be permitted to express an opinion. Expressions in wasm seem to have brought it well into the bike-shedding territory and made progress almost impossible. Whatever the outcome for expressions it seems that they will just be some baggage to work around, to be canonicalized into a more primitive expressionless form and re-built into expressions for presentation. The pre-order/post-order saga seems unnecessary without expressions. I have seen a number of issues with the type system and been unable to make progress. I started out thinking that expressions were the saving grace for wasm but have come full circle and have completely given up on them. Giving up on expressions in the wasm code section does not mean giving up on them in the file as a whole, as they can be rebuild with the aid of meta information for presentation. I have re-encoding AngryBots using a simple expressionless encoding, and already uncompressed it is only 15% larger, and brotli encoded is 16% larger, and I see some prospect of closing this gap. I have explored writing a few of the expressionless instructions in v8 and their decoding seems efficient.


[Question] Usage in Modpacks

Greetings,
I'm currently working on a VulkanMod based performance Modpack and would like to include this particular mod as well. However, I haven't found any information about the usage in Modpacks in the description.
What am I allowed to do?

feel free to include it in ur modpack without asking.


Certain filenames are not detected

I recently ran sarek with a custom reference genome combined_reference.fasta. This causes a couple of of genome-related files to be generated by sarek, some of which end up looking like this:
(base) ➜  ~ aws s3 ls s3://ntap-cnf-cell-project-tower-bucket/cnf_transgene_detection/tabix/
2023-09-14 10:42:28          0
2023-09-14 10:42:28      18323 [combined_reference.fasta].bed.gz
2023-09-14 10:42:28      44435 [combined_reference.fasta].bed.gz.tbi

Unfortunately, this causes an error with synindex.py:
usage: synindex.py [-h] [--storage_id STORAGE_ID] [--file FILE] [--uri URI]
                   [--parent_id PARENT_ID] [--config CONFIG]
synindex.py: error: argument --file: expected one argument

Looking at the command used in the workflow, it appears that no --file parameter is passed with this odd filename:
synindex.py   --storage_id 41864   --file    --uri 's3://ntap-cnf-cell-project-tower-bucket/cnf_transgene_detection/tabix/[combined_reference.fasta].bed.gz.tbi'   --parent_id syn52498904

I'd suggest that this is also a bug with sarek or one of its modules, but I think the synindex workflow should also be able to handle edge cases like this.

Note: workaround is to simply change filenames
(base) ➜  ~ aws s3 mv 's3://ntap-cnf-cell-project-tower-bucket/cnf_transgene_detection/tabix/[combined_reference.fasta].bed.gz' s3://ntap-cnf-cell-project-tower-bucket/cnf_transgene_detection/tabix/combined_reference.fasta.bed.gz

move: s3://ntap-cnf-cell-project-tower-bucket/cnf_transgene_detection/tabix/[combined_reference.fasta].bed.gz to s3://ntap-cnf-cell-project-tower-bucket/cnf_transgene_detection/tabix/combined_reference.fasta.bed.gz
(base) ➜  ~ aws s3 mv 's3://ntap-cnf-cell-project-tower-bucket/cnf_transgene_detection/tabix/[combined_reference.fasta].bed.gz.tbi' s3://ntap-cnf-cell-project-tower-bucket/cnf_transgene_detection/tabix/combined_reference.fasta.bed.gz.tbi

move: s3://ntap-cnf-cell-project-tower-bucket/cnf_transgene_detection/tabix/[combined_reference.fasta].bed.gz.tbi to s3://ntap-cnf-cell-project-tower-bucket/cnf_transgene_detection/tabix/combined_reference.fasta.bed.gz.tbi

THanks @allaway for reporting this!  I'll create a Jira ticket and try to tackle this at some point.

We are deprecating this repository and instead maintaining its functionality in nf-synapse. This issue is tracked in Jira here.


ci: build workflow login to mia registry

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 84.316%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2059

Relevant Lines:
2442

💛  - Coveralls


TabNavigation Icon is cut off

I created a TabNavigator with three screens, each screen got an Icon from MaterialIcons in navigationOptions.
The icons get cut off if I set the size > 26. Is there any possibility to increase the size for the icons in the TabNavigator?
Best regards, Markus
const SettingsScreen = ({ navigation }) => (
  <Settings
    banner={'Settings Screen'}
    navigation={navigation}
  />
);
SettingsScreen.navigationOptions = {
  tabBar: ({ state, setParams }) => ({
    icon: ({ tintColor }) => (
      <MaterialIcons
        name="settings"
        size={ 30 }
        style={{ color: tintColor }}
      />
    ),
  }),
};

See issue #677. They made a pull request but got rejected. I need this feature too.

I try custom view and I need this feature.max Size 26 is not useful.
icon: ({tintColor}) => {  return( <TouchableOpacity onPress={() =>
{animate();try{state.state.params.reRequest();}catch(e){console.log('errr '+e)}}}>
        <View style={{flex:1,backgroundColor:'blue'}} >

          {state.state.params.cartItemCount==0?null:circleFactory(state.state.params.cartItemCount*10)}
      <Icon name='shopping-basket'
        type='font-awesome' size={30} color={tintColor} />

     <View style={{backgroundColor:'red',position:'absolute',top:1,right:0,width:20,height:20,borderRadius:11,borderWidth:2,
borderColor: 'red'}}><Text style={{color:'white',fontSize:12,textAlign:'center',fontWeight:'bold'}}>{state.state.params==undefined?0:state.state.params.cartItemCount}</Text></View>
    </View>

)  }

Use label and render what you want. There is no size restriction for label.

@navid94 : They made a pull request but got rejected.

Which pull request got rejected?

@satya164 #677 was rejected, but now with #965 the fix is in master. You can use iconStyle: { width, height} to render the icon with the right size and without being clipped. @Catharsis68 @TestTitans you can point to master with
npm install react-navigation@https://github.com/react-community/react-navigation.git --save

and use iconStyle prop, just a temporary solution until v1.0.0 beta 8 comes out.

It was not rejected. It was still open, changes were requested and the author hadn't made the changes yet.

@satya164 ok

I have included the latest from master:
"react-navigation": "https://github.com/react-community/react-navigation.git"
...and I am using the tabs as such:
  Profile: {
    screen: Profile,
    navigationOptions: {
      tabBar: {
        label: 'Profile',
        icon: ({tintColor}) => <Icon name='ios-contact' size={38} color={tintColor}/>
      }
    },
  },
...

..., {
  animationEnabled: true,
  swipeEnabled: true,
  tabBarPosition: 'bottom',
  tabBarOptions: {
    iconStyle: {
      width: 100,
      height: 100,
      paddingBottom: 10,
    },

...but alas no change and the cropped icon is limited to size 29 on Android...

@studiobrain check if iconStyle prop is present in file
node_modules/react-navigation/src/views/TabView/TabBarTop.js

otherwise it means that you don't have installed it correctly.
Mine setup is:
static navigationOptions = {
        header: {
            visible: false
        },
        tabBar: {
            icon: ({ tintColor }) => {
                return (
                    <FontAwesome
                        name='cubes'
                        size={27}
                        color={ tintColor }
                    />
                );
            }
        }
    }

var MainTabNavigator = TabNavigator({
    ...
}, {
    lazyLoad: true,
    animationEnabled: false,
    tabBarOptions: {
        activeTintColor: '#3b5998',
        inactiveTintColor: '#cccccc',
        showIcon: true,
        showLabel: false,
        iconStyle: {
            width: 35,
            height: 30
        },
        style: {
            backgroundColor: 'white'
        },
        pressColor: '#d5dcea',
        indicatorStyle: {
            backgroundColor: 'white'
        }
    }
});

and it works. Maybe your icon is too big and you have to increase the size of the tab bar with the style prop.

Yeah, I checked and it is found.  Im currently using react-native-vector-icons/Ionicons and have a width and height set on style:
style: {
      backgroundColor: common.baseHex,
      borderTopWidth: 2,
      borderTopColor: "white",
      height: viewport.width * 0.2,
      width: viewport.width,
    },

It works fine on iOS, at least the icons render as expected.  On Android I see the cropping, but also Im not sure the iconStyles are even being rendered.  Are there any other params I can try to see if they are being read?  backgroundColor or any positioning doesnt work either.  I will continue to debug.

@studiobrain sorry but I don't know then, the IconStyle prop it's a normal style object for a view containing the icon, see https://github.com/react-community/react-navigation/blob/master/src/views/TabView/TabBarIcon.js.
You can also try increasing the dimensions of the single tab with tabStyle prop.

@navid94 I just wanted to respond back and let you know that after closing the server and simulator for both android and ios and then running the server (I run each platform on a separate port) and building, the iconStyle started rendering as expected!  Thanks!

@studiobrain nice!

Is it possible to prevent the height of the tab bar from growing when chaning iconStyle size. It looks like there's a fixed padding around the icon.

@rom1k if you want to increase the size of the icon without the tab bar increasing its size, you have to use the prop size directly on the icon:
import MaterialIcons from 'react-native-vector-icons/MaterialIcons';
static navigationOptions = {
        header: {
            visible: false
        },
        tabBar: {
            icon: ( { tintColor }) => {
                return (
                    <MaterialIcons
                        name='format-list-bulleted'
                        size={30}
                        color={ tintColor }
                    />
                );
            }
        }
    };

@navid94
I did that, but I want to have a badge on the top right of my tab icon, but it is clipped. That's why I'm trying increase the size of the icon container but that causes the whole tab bar to grow.

@rom1k try using the prop
tabStyle: {
    height: value
}

i tried and it decrease the size of the tab bar even if iconStyle has major height.

@navid94
That's what I did. Maybe it's because i'm using a bottom tab bar?

@rom1k i tried this setup:
var MainTabNavigator = TabNavigator({
    ...
}, {
    lazyLoad: true,
    animationEnabled: false,
    tabBarPosition: 'bottom',
    tabBarOptions: {
        activeTintColor: '#3b5998',
        inactiveTintColor: '#cccccc',
        showIcon: true,
        showLabel: false,
        iconStyle: {
            width: 35,
            height: 60
        },
        tabStyle: {
            height: 40
        }
        style: {
            backgroundColor: 'white'
        },
        pressColor: '#d5dcea',
        indicatorStyle: {
            backgroundColor: 'white'
        }
    }
});

static navigationOptions = {
        header: {
            visible: false
        },
        tabBar: {
            icon: ( { tintColor }) => {
                return (
                    <MaterialIcons
                        name='format-list-bulleted'
                        size={70}
                        color={ tintColor }
                    />
                );
            }
        }
    };

this is the result, isn't that what you want?
https://s22.postimg.org/xt7etgl01/Screenshot_2017-04-12-11-11-22.png

@navid94 It works! Thanks!

Sorry guys I am still struggling here. Can you guys take a look at this. My icons are still getting cut off on android only.
"react-navigation": "1.0.0-beta.11",

tabNavigation.js
const HomeTabNavigation = TabNavigator(

  {
    Profile: { screen: Profile },
    PhotoCard: { screen: PhotoCard },
    Chat: { screen: Chat }
  },
  {
    tabBarPosition: "bottom",
    // animationEnabled: true,
    initialRouteName: "PhotoCard",
    swipeEnabled: false,
    lazy: true,
    tabBarOptions: {
      activeTintColor: '#0080FF',
      inactiveTintColor: '#f4f4f4',
      showIcon: true,
      showLabel: false,
      pressColor: '#0080FF',
      // iconStyle: {
      //   width: 20,
      //   height: 20,
      //   color: '#0080FF'
      // },
      style: {
        backgroundColor: 'white',
        borderTopColor: 'white',
        borderTopWidth: 1,
        height: metrics.DEVICE_HEIGHT * 0.08
      },
      tabStyle: {
        width: metrics.DEVICE_WIDTH / 3,
      },
      indicatorStyle: {
        backgroundColor: 'white',
      },
    },
  }
);

static navigationOptions = {
header: {
visible: false
},
tabBarIcon: ({ tintColor }) => {
return(
<Icon name="ios-mail"
//  size={27}
color={tintColor}
/>
)
}
}

i still get this bug on tablet, not on smartphone strange.
const MyTabView = createBottomTabNavigator(
  {
    FeedObservations: { screen: FeedObservations },
    Projects: { screen: Projects },
    NewObservation: { screen: NewObservation },
    Explorer: { screen: Explorer },
    Profil: { screen: Profil }
  },
  {
    swipeEnabled: false,
    initialRouteName: initialRouteName,
    tabBarPosition: "bottom",
    tabBarOptions: {
      activeTintColor: "green",
      pressColor: "green",
      inactiveTintColor: "#373738",
      showIcon: true,
      showLabel: false,
      style: {
        backgroundColor: "white"
      },

      indicatorStyle: {
        backgroundColor: "green"
      }
    }
  }
);

And the component who display the truncated camera icon
export default class NewObservation extends React.PureComponent {
  static navigationOptions = ({ navigation }) => {
    return {
      tabBarIcon: ({ tintColor }) => (
        <TouchableOpacity
          underlayColor={"green"}
          onPress={() => {
            navigation.navigate("AddObservation");
          }}
        >
          <IconIonic name="md-camera" size={20} color={tintColor} />
        </TouchableOpacity>
      ),
      tabBarOnPress: () => {
        // ticket en cour https://github.com/react-navigation/react-navigation/issues/5708
        navigation.navigate("AddObservation");
      }
    };
  };

  render() {
    return <AddObservation />;
  }
}

Version
"react": "^16.8.4"
"react-native": "^0.59.2"
"react-native-vector-icons": "^6.4.0"

Any fix ? thanks

Use label and render what you want. There is no size restriction for label.

This is a great solution, thank you!  If anyone is interested in our usage:
tabBarLabel: ({ tintColor }) => (<View style={{ flexDirection: "column", justifyContent: "center", alignItems: "center", alignContent: "center", paddingBottom: 20 }}><Icon name="home" color="#4db6ac" size={addButtonSize === "tablet" ? 50 : 25} /><Text style={{ fontSize: addButtonSize === "tablet" ? 25 : 10, color: tintColor }}>Home</Text></View>)

Use label and render what you want. There is no size restriction for label.

This is a great solution, thank you! If anyone is interested in our usage:
tabBarLabel: ({ tintColor }) => (<View style={{ flexDirection: "column", justifyContent: "center", alignItems: "center", alignContent: "center", paddingBottom: 20 }}><Icon name="home" color="#4db6ac" size={addButtonSize === "tablet" ? 50 : 25} /><Text style={{ fontSize: addButtonSize === "tablet" ? 25 : 10, color: tintColor }}>Home</Text></View>)

Also make sure to set showLabel to true and showIcon to false:
tabBarOptions: {
showLabel: true,
showIcon: false,
tabStyle: {
height: Dimensions.get('window').height * 0.088,
width: Dimensions.get('window').width * 0.25
}
                },


BUG: csgraph normalized laplacian return_diag=True returns an array that is not the diagonal

Following the docstring example in http://docs.scipy.org/doc/scipy/reference/generated/scipy.sparse.csgraph.laplacian.html:
>>> from scipy.sparse import csgraph
>>> G = np.arange(5) * np.arange(5)[:, np.newaxis]
>>> G
array([[ 0,  0,  0,  0,  0],
       [ 0,  1,  2,  3,  4],
       [ 0,  2,  4,  6,  8],
       [ 0,  3,  6,  9, 12],
       [ 0,  4,  8, 12, 16]])
>>> csgraph.laplacian(G, normed=False, return_diag=True)
(array([[  0,   0,   0,   0,   0],
       [  0,   9,  -2,  -3,  -4],
       [  0,  -2,  16,  -6,  -8],
       [  0,  -3,  -6,  21, -12],
       [  0,  -4,  -8, -12,  24]]),
array([ 0,  9, 16, 21, 24]))
>>> csgraph.laplacian(G, normed=True, return_diag=True)
(array([[ 0.        , -0.        , -0.        , -0.        , -0.        ],
       [-0.        ,  1.        , -0.16666667, -0.21821789, -0.27216553],
       [-0.        , -0.16666667,  1.        , -0.32732684, -0.40824829],
       [-0.        , -0.21821789, -0.32732684,  1.        , -0.53452248],
       [-0.        , -0.27216553, -0.40824829, -0.53452248,  1.        ]]),
array([ 1.        ,  3.        ,  4.        ,  4.58257569,  4.89897949]))

This behavior is the same for both dense and sparse matrices with different implementations, so it's not just a typo within scipy.  I'm not sure if it is the intended behavior but I think it is not.  No tests in https://github.com/scipy/scipy/blob/master/scipy/sparse/csgraph/tests/test_graph_laplacian.py use this keyword argument yet.
If this is agreed to be a bug, then I'd plan to fix it and add a test after the COO setdiag PR is merged, because setdiag could simplify the sparse laplacian code.

gh-3827 was merged


added lagrangian multiplers output

I'm not sure which version of the qpgen2() FORTRAN code you started from, but it appears that there is another variation that includes Lagrange multipliers in the output. My Mac version of R includes the Lagrange multipliers as well.
For an example of this version of qpgen2() look at https://github.com/Chromatical/node-quadprog-native/blob/master/src/solve.QP.f
This diff passes your test script. The multipliers for the first example correspond to the R result on my Mac. I don't think that adding the multipliers will break any existing code.

Thanks a lot for the contribution.
I ported the code before Lagrange multipliers were include in the FORTRAN code.
Then, when a new version is released, I check the new code line by line, if there is any change.
Until now there was no any request about Lagrange multipliers.
Thanks for your interest.
A few notes about PR.
I would prefer Lagrangian: lagr, as in the original R code.
Shall you modify the tests to check the multipliers?

I'm not familiar with your test system. Please change the code however you think best.

Thank you!


added get_fancy amd set_fancy to the algodiff library

In this PR, I added get_fancy and set_fancy to Algodiff.
I've also added unit tests for get_slice and get_fancy.

I have reviewed this, looks all good! Thanks @tachukao :100:

Are the indentation changes related to the other ocamlformat PR?

Oh this is awesome!

Not sure about the indentation changes. I'm currently still on ocamlformat 0.15.0 and that might be why...


remove "echo" and $_POST in the controllers.

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 58
- Added 2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 59
- Added 2

See the complete overview on Codacy


Add ports to Task struct

Current coverage is 42.07% (diff: 100%)

Merging #322 into master will decrease coverage by 0.62%

@@             master       #322   diff @@
==========================================
  Files            12         12
  Lines         10048      10048
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           4291       4228    -63
- Misses         4645       4702    +57
- Partials       1112       1118     +6

Powered by Codecov. Last update 23406c9...963f4a0

LGMT


Installation command issues

Need to cd into ~/audit_helper
wget command is incorrect, outputting wget stdout rather than the file
Path needs : not ;

Fixed: 5af26bfe541cb0bfd3786e8ae1a22698749a644a


Changed popup_centered by popup_centered_minsize in editor dialogs

cool, did it work well?
On Wed, Apr 8, 2015 at 2:05 PM, Franklin Sobrinho<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/okamstudio/godot/pull/1654
Commit Summary

Changed popup_centered by popup_centered_minsize in editor dialogs

File Changes

M tools/editor/connections_dialog.cpp
https://github.com/okamstudio/godot/pull/1654/files#diff-0 (2)
M tools/editor/editor_node.cpp
https://github.com/okamstudio/godot/pull/1654/files#diff-1 (66)
M tools/editor/editor_reimport_dialog.cpp
https://github.com/okamstudio/godot/pull/1654/files#diff-2 (6)
M tools/editor/plugins/animation_player_editor_plugin.cpp
https://github.com/okamstudio/godot/pull/1654/files#diff-3 (4)
M tools/editor/plugins/baked_light_editor_plugin.cpp
https://github.com/okamstudio/godot/pull/1654/files#diff-4 (4)
M tools/editor/plugins/mesh_editor_plugin.cpp
https://github.com/okamstudio/godot/pull/1654/files#diff-5 (12)
M tools/editor/plugins/multimesh_editor_plugin.cpp
https://github.com/okamstudio/godot/pull/1654/files#diff-6 (18)
M tools/editor/plugins/particles_editor_plugin.cpp
https://github.com/okamstudio/godot/pull/1654/files#diff-7 (8)
M tools/editor/plugins/polygon_2d_editor_plugin.cpp
https://github.com/okamstudio/godot/pull/1654/files#diff-8 (2)
M tools/editor/plugins/resource_preloader_editor_plugin.cpp
https://github.com/okamstudio/godot/pull/1654/files#diff-9 (4)
M tools/editor/plugins/sample_library_editor_plugin.cpp
https://github.com/okamstudio/godot/pull/1654/files#diff-10 (2)
M tools/editor/plugins/script_editor_plugin.cpp
https://github.com/okamstudio/godot/pull/1654/files#diff-11 (2)
M tools/editor/plugins/sprite_frames_editor_plugin.cpp
https://github.com/okamstudio/godot/pull/1654/files#diff-12 (4)
M tools/editor/project_export.cpp
https://github.com/okamstudio/godot/pull/1654/files#diff-13 (12)
M tools/editor/property_editor.cpp
https://github.com/okamstudio/godot/pull/1654/files#diff-14 (2)
M tools/editor/resources_dock.cpp
https://github.com/okamstudio/godot/pull/1654/files#diff-15 (2)
M tools/editor/scene_tree_dock.cpp
https://github.com/okamstudio/godot/pull/1654/files#diff-16 (18)
M tools/editor/scene_tree_editor.cpp
https://github.com/okamstudio/godot/pull/1654/files#diff-17 (4)
M tools/editor/script_create_dialog.cpp
https://github.com/okamstudio/godot/pull/1654/files#diff-18 (8)

Patch Links:

https://github.com/okamstudio/godot/pull/1654.patch
https://github.com/okamstudio/godot/pull/1654.diff

—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/pull/1654.

It work nice with a accept dialog. But with a confirmation dialog, it don't work well with small labels, especially with long titles.


Test fix / Cucumber 2 / Rails 4.2

3 commits in this PR
1 fix a failing test due to rails date selectors only showing 5 years into the past by default
2 allow cucumber 2
3 add rails 4.2 to test matrix

thank you @twalpole


Update 2023-07-31-paris-dev-sprint.md

Towards #165
Mostly order names alphabetically
Also change the sum from 33 to 33

@GaelVaroquaux
First of all, congratulations on your first PR to the blog repo!  Thank you for the PR. We hope you enjoyed the Welcome banner!
a small comment:
The blog has a date of 2023-07-31.  Can we change it to 2023-09-12 ? or 2023-09-10 ?

We hope you enjoyed the Welcome banner!

I looooooooved it!! Do we have something as nice for scikit-learn?

The blog has a date of 2023-07-31. Can we change it to 2023-09-12 ? or 2023-09-10 ?

Sure! Shall I do this in this PR?

Sure! Shall I do this in this PR?

Date change done

Sure! Shall I do this in this PR?

Date change done

I thought the actual file name needed to be changed.  But, maybe not?

I'll merge it in and see what the date shows.

I thought the actual file name needed to be changed. But, maybe not?

Ha, I was being not clever. Thanks for handling it.


Fix popperjs import for SvelteKit Patch-2

I was still faced with this issue #463 after fetched the latest fix #356
I made a fix in two more files.

I sent a fix here: https://github.com/bestguy/sveltestrap/pull/566

I sent a fix here: #566

@benmccann What is the difference between this PR and yours?

Oops! I looked at this too quickly originally. Yes, your fix is the same as mine. Sorry about that. The issue description in my PR will close some linked issues with the magic "fixes" and "closes" keywords. If you want to copy that into your PR description (it doesn't work in comments, but only by editing the description) I can go ahead and close my PR

@benmccann No worries. Let's keep yours and I'm going to close this one. Thanks.


X86_64 overlapping register listing highlight

Running 9.0.4
I'll come across instructions like xor R13D,R13D for example and then later instructions accessing just R13.  A wheel click on R13D will highlight both, but a wheel click on R13 will only highlight R13.
With the GPR this is not case, so may only effect the 64-bit mode-only GPR.

PUSH R13
MOV EAX,R13D
POP R13
RET
PUSH RDX
MOV EAX,EDX
POP RDX
RET

Looked into this a bit more, and still makes no sense.  A simple dummy case, highlight works both ways with RDX, but not R13.  The register set and regex get built up in the same manner
[R13, R13D, R13W, R13B] \QR13\E|\QR13\E|\QR13D\E|\QR13W\E|\QR13B\E
[R13D, R13, R13W, R13B] \QR13D\E|\QR13\E|\QR13D\E|\QR13W\E|\QR13B\E
[RDX, EDX, DX, DL, DH] \QRDX\E|\QRDX\E|\QEDX\E|\QDX\E|\QDL\E|\QDH\E
[EDX, RDX, DX, DL, DH] \QEDX\E|\QRDX\E|\QEDX\E|\QDX\E|\QDL\E|\QDH\E
And the code flow looks similar, the only difference being RSP is not check in isWriteOnly for the RDX case

I am stepping through this with the Eclipse debugger, and the problem seems to be in here:
https://github.com/NationalSecurityAgency/ghidra/blob/85e25af7e8f8407c74a0867dfeb6ec8f035fcdd6/Ghidra/Features/Base/src/main/java/ghidra/app/plugin/core/codebrowser/ListingHighlightProvider.java#L145-L154
https://github.com/NationalSecurityAgency/ghidra/blob/85e25af7e8f8407c74a0867dfeb6ec8f035fcdd6/Ghidra/Features/Base/src/main/java/ghidra/app/plugin/core/codebrowser/ListingHighlightProvider.java#L161-L175
In my case:
currentHighlightPattern = \QR15\E|\QR15\E|\QR15D\E|\QR15W\E|\QR15B\E
text = R15D,AX
start = 0
end = 2

c ends up being 'D', which causes it to return false.
I think the smaller r15 regex pattern should be moved to the end of the currentHighlightPattern regex, or we need to match on the longest pattern.  I don't really know this code though, so I have to verify with others...I'm not sure what else that would affect/break.

I'm currently stepping thought this to try to figure out what's going wrong.  It's somewhere in here I think:
https://github.com/NationalSecurityAgency/ghidra/blob/85e25af7e8f8407c74a0867dfeb6ec8f035fcdd6/Ghidra/Features/Base/src/main/java/ghidra/app/plugin/core/codebrowser/ListingHighlightProvider.java#L145-L154
https://github.com/NationalSecurityAgency/ghidra/blob/85e25af7e8f8407c74a0867dfeb6ec8f035fcdd6/Ghidra/Features/Base/src/main/java/ghidra/app/plugin/core/codebrowser/ListingHighlightProvider.java#L161-L175
In my case:
currentHighlightPattern = \QR15\E|\QR15\E|\QR15D\E|\QR15W\E|\QR15B\E
text = R15D,AX
start = 0
end = 2

c ends up being 'D', which causes it to return false on the first iteration of the matcher.find() loop.  But then there end up being no more iterations, which seems wrong.

I'm thinking the different parts of the regex just need to be grouped correctly.  The existence of the loop implies to me that each register should try to be matched.

I am stepping through this with the Eclipse debugger, and the problem seems to be in here:
https://github.com/NationalSecurityAgency/ghidra/blob/85e25af7e8f8407c74a0867dfeb6ec8f035fcdd6/Ghidra/Features/Base/src/main/java/ghidra/app/plugin/core/codebrowser/ListingHighlightProvider.java#L145-L154
https://github.com/NationalSecurityAgency/ghidra/blob/85e25af7e8f8407c74a0867dfeb6ec8f035fcdd6/Ghidra/Features/Base/src/main/java/ghidra/app/plugin/core/codebrowser/ListingHighlightProvider.java#L161-L175
In my case:
currentHighlightPattern = \QR15\E|\QR15\E|\QR15D\E|\QR15W\E|\QR15B\E
text = R15D,AX
start = 0
end = 2

c ends up being 'D', which causes it to return false.
I think the smaller r15 regex pattern should be moved to the end of the currentHighlightPattern regex, or we need to match on the longest pattern.  I don't really know this code though, so I have to verify with others...I'm not sure what else that would affect/break.

https://xkcd.com/1171/
Thanks for tracing down down the issue, I skipped over this whole chunk when I was looking at it


Add package folly

https://github.com/facebook/folly
Dependencies and build based on CMake. Would be nice to have in hunter

CMake build currently only supported on Windows. Not sure why.

Isn't folly entirely cmake based no, no more autotools or anything?
https://github.com/facebook/folly

@OvermindDL1 thanks for the update. It seems you are correct. Maybe I'll patch it for Hunter after all.

For note, as documented at https://github.com/facebook/folly/issues/734#issuecomment-365728656 the required dependencies is:  Folly depends on zlib, openssl, libevent, double-conversion, glog, gflags, lz4, liblzma, snappy and boost

Ya I packaged the dependencies months ago. The only remaining task was folly itself.

From same thread, just adding this for completion:  Folly also depends on zstd.


Sometimes bytes read is less than the value length for some Native Pixel dicoms

For some DICOMs, the number of bytes read assuming it is in a native pixel format is smaller than the defined value length. It is possible that for these images the Bits / pixel are larger or that there is some special encoding that needs to be looked into further.
It is assumed that an image contains standard native pixel data when the value length of the PixelData attribute is not undefined length.

Upon investigation, this can likely be handled by better handing different BitsAllocated (tag (0028,0100)) values.

This is addressed in 8cf48e440567c47a21ffeb64df6865b756501bc9 in #7


add CrJson

추후 additional_info, size_info 등을 위한 CrJson Scalar 추가적용했습니다.

Pull Request Test Coverage Report for Build 9

23 of 26 (88.46%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-3.05%) to 85.526%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/json.js
21
24
87.5%

Totals

Change from base Build 6:
-3.05%

Covered Lines:
44

Relevant Lines:
49

💛  - Coveralls

CrJson 기 생성으로 해당PR건 삭제


Add whois.nic.es

Description
The .es domains have activated the whois on port 43 (whois.nic.es), but to get an answer we need to do an accreditation procedure.
The indications are here:
https://www.dominios.es/dominios/en/todo-lo-que-necesitas-saber/valores-anadidos/puerto-43
Without the accreditation of the IP address the server responds but does not provide information, with the accreditation only the domain name and the registrant are provided.
The accreditation is free, to request is sent the IP address from which the calls come.
(https://www.dominios.es/dominios/sites/dominios/files/en_Procedimiento de alta servicio whois puerto 43 v4_cambio sede (ult)_0.pdf)
Example
Answer without accreditation
`    Conditions of use for the whois service via port 43 for .es domains
Access will only be enabled for  IP addresses  authorised  by Red.es.  A maximum of one  IP address per
user/organisation is permitted.

Red.es accepts  no responsibility  whatsoever  for  the availability  of access to WHOIS,  which may be
suspended at any time and without prior warning at the discretion of the public entity.

The service will be limited to the data established by Red.es.

The user  promises  to make use of the service and to  carry out any action derived  from the aforesaid
use in accordance with  current applicable  regulations, in particular with legislation on “.es” domain
names and personal data protection.

In particular, the user undertakes not to use  the service  to carry out abusive  or speculative domain
name registrations, pursuant to section 5 of the Sixth Additional Provision of Law 34/2002, of 11 July,
on Services of the  Information  Society and  Electronic Commerce. Likewise, the User undertakes not to
use the service to  obtain data, the possession  of which may  contravene the provisions of Organic Law
15/1999,  of  13 December,  on Personal Data Protection, and  its Regulations, or in Law 34/2002, of 11
July, on Services of the Information Society and Electronic Commerce.

Failure  to comply with these conditions will result in the immediate withdrawal of the service and any
registered domain name which breaches said conditions may be officially cancelled by Red.es.
-------------------------------------------------------------------------------------------------------

The IP address used to perform the query  is not authorised  or  has exceeded the established limit for
queries.To request access to the service,complete the form located at https://sede.red.gob.es/sede/whois,
where you may also consult the service conditions.

-------------------------------------------------------------------------------------------------------
More information on each domain may be consulted at www.dominios.es.`

Answer with accreditation
`    Conditions of use for the whois service via port 43 for .es domains
Access will only be enabled for  IP addresses  authorised  by Red.es.  A maximum of one  IP address per
user/organisation is permitted.

Red.es accepts  no responsibility  whatsoever  for  the availability  of access to WHOIS,  which may be
suspended at any time and without prior warning at the discretion of the public entity.

The service will be limited to the data established by Red.es.

The user  promises  to make use of the service and to  carry out any action derived  from the aforesaid
use in accordance with  current applicable  regulations, in particular with legislation on “.es” domain
names and personal data protection.

In particular, the user undertakes not to use  the service  to carry out abusive  or speculative domain
name registrations, pursuant to section 5 of the Sixth Additional Provision of Law 34/2002, of 11 July,
on Services of the  Information  Society and  Electronic Commerce. Likewise, the User undertakes not to
use the service to  obtain data, the possession  of which may  contravene the provisions of Organic Law
15/1999,  of  13 December,  on Personal Data Protection, and  its Regulations, or in Law 34/2002, of 11
July, on Services of the Information Society and Electronic Commerce.

Failure  to comply with these conditions will result in the immediate withdrawal of the service and any
registered domain name which breaches said conditions may be officially cancelled by Red.es.

The  User will be held accountable for the use they make of the service and will be responsible for any
claims that may be filed by third parties in this regard against Red.es and will have to compensate the
public entity for any damages it may incur as a result.

The data which  can  be consulted via  this service include:  availability and  name of the holder of a
domain.

A maximum of 10 queries per minute  can  be  made by each  registered IP address.  Should this limit be
exceeded, the service will be blocked for two hours, after which a new query may be performed.

Queries can be performed on second and third level domains.
-------------------------------------------------------------------------------------------------------

Domain:
-------
   Domain Name:                  google.es

Registrant:
-----------
   Registrant Name:              Google LLC

>>> LAST UPDATE: 10/10/2019 07:00:04
-------------------------------------------------------------------------------------------------------
More information on each domain may be consulted at www.dominios.es.`

Thanks for the merge!


[Feature Request] - Multiple UI element types (multi input, radio, dropdown, etc) in a single popup - Like Pashua

Is your feature request related to a problem? Please describe.
Pashua has the ability to mix different elements in a single window (dropdown, radio, input field, etc.) Each distinct element result via input has its 'own' result variable.
It would be super beneficial if we could assign multiple element types, with each to a separate variable rather than rely on 'returned' results of a call (button clicks should still be recorded). I have been putting some results into arrays and parsing those out, but we are limited to how many UI elements are avail in a single popup. Yes? Or am I missing something. I have used the secondary_accessory_view_type and payload, but would like at least 3 or 4 more possibilities and all UI element types avail in a popup window.
Maybe I'm missing something, I just started w/ this tool last night.
Describe the solution you'd like
Capability for multiple and different types UI elements in a single popup (like pashua)

Each element having its own specific variable that we can assign, like elementTitle or similar. Each element would also have it's own definable width/height, etc
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Added my current onboarding screen I built in Pashua. Would love for these types of features in IBM Notifier.

Hi @spikehed thanks for making this feature request and sorry for the delay. The limit of 2 accessory views for popup UI has been made on purpose since the small pop-up alert is not meant to collect too much information from the user.
We're currently working on an improved Onboarding UI that will allow the admin to include an array of accessory views in each page to collect information from the end user (plus some other new features for the Onboarding workflow itself). Do you think this could resolve your FR?

I think that it would. Thanks for responding.
On Tue, Mar 1, 2022 at 18:12 Simone Martorelli @.***>
wrote:

Hi @spikehed https://github.com/spikehed thanks for making this feature
request and sorry for the delay. The limit of 2 accessory views for popup
UI has been made on purpose since the small pop-up alert is not meant to
collect too much information from the user.
We're currently working on an improved Onboarding UI that will allow the
admin to include an array of accessory views in each page to collect
information from the end user (plus some other new features for the
Onboarding workflow itself). Do you think this could resolve your FR?
—
Reply to this email directly, view it on GitHub
https://github.com/IBM/mac-ibm-notifications/issues/71#issuecomment-1055955262,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABVS4FUMOXN7YHDSRGZWLHLU52P5HANCNFSM5OEQD3JA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Cool I can spoiler you that this feature will be implemented in the v2.6.0 that should be published by the end of this month.


v0.6.3

#726  👈
main

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

Join @alanvardy and the rest of your teammates on  Graphite


[WIP] Add cool functions

There are a lot of ugly for loops that can be replaced with :cool: functions. Still much to be done, do not merge yet.

ich liebe liggy

ich liebe lemmmy


Updated texts for planting site creation flow

#2690  👈
main

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

Join @tommylau523 and the rest of your teammates on  Graphite


pixie: remove

Description of changes
Pixie hasn't seen a commit since October 2017 and depends on python2.

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

cc @bendlas. Also, can you rebase?

cc @alekcz

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/why-did-the-dust-package-got-removed/25015/2


ButtonGroup retains divider color when disabled and variant="text"

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example: https://codesandbox.io/s/green-violet-1o2jb7?file=/demo.tsx
Steps:

Create a button group like the following:

      <ButtonGroup
        color="error"
        orientation="vertical"
        aria-label="vertical contained button group"
        variant="text"
        disabled
      >
        {buttons}
      </ButtonGroup>```

### Current behavior 😯

When disabled, the button group retains its color in the divider lines.

### Expected behavior 🤔

In all other variants, all colors go into the gray scale when disabled.

### Context 🔦

_No response_

### Your environment 🌎

  npx @mui/envinfo

System:
OS: macOS 13.2.1
Binaries:
Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 9.1.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
Browsers:
Chrome: 111.0.5563.146
Edge: Not Found
Firefox: 111.0.1
Safari: 16.3
npmPackages:
@emotion/react:  11.10.5
@emotion/styled:  11.10.5
@mui/icons-material:  5.11.0
@mui/lab:  5.0.0-alpha.118
@mui/material:  5.11.15
@mui/system:  5.11.9
@mui/utils:  5.11.9
@mui/x-date-pickers:  5.0.18
@types/react:  17.0.53
react:  17.0.2
react-dom:  17.0.2

Can I work on this issue?

A friend of mine and I are working on this for a University project because we have seen nothing has been done for a few weeks. Hope that is ok!


ProgressBar#current= supports indeterminate progress bars too

Describe the change
I noticed that #current= failed for indeterminate progress bars. The primary test I added would error like this:
     ArgumentError:
       comparison of NilClass with 5 failed

I added a new ArgumentError guard to also preserve the existing, desirable, behavior of not supporting #current = nil, and a test to cover this. Note that current = nil was already raising ArgumentError in both the determinate and indeterminate cases (comparison of Integer with nil failed, comparison of NilClass with 0 failed, etc.); now the error message is one that we set.
Why are we doing this?
As far as I can tell, there's no reason that current = shouldn't work for indeterminate progress bars. It seems that indeterminate progress bars are meant to have a current value, and can have it by calling .advance, so adding support seems consistent with the rest of the library.
Benefits
It's quite nice to be able to set current progress for indeterminate progress bars!
Drawbacks
I don't have any to highlight.
Requirements

[x] Tests written & passing locally?
[ ] Code style checked?
[x] Rebased with master branch?
[ ] Documentation updated?
[x] Changelog updated?

@piotrmurach The errors now focus on "numeric" instead of a particular class. Let me know what you think!

@piotrmurach I've made that small change for consistency

@piotrmurach let me know if you want me to do anything else to make this mergeable

@alexcwatt This is on my list, I promise I'm not ignoring you. Please bear with me.

@alexcwatt Released v0.18.3. Once again thanks for the PR!


fix: disable the submit button until forgot password fields have value

fixes gravitee-io/issues#8552

Tests on 3.19.x environment :
Nominal case : PASS
Custom field : PASS
Multiple custom fields : PASS
Confirm identity : PASS


Add topic documentation on cloud billing concepts

Cloud billing is a vast area with many nuances. However, because of our usage patterns, we only need to understand a small-ish subset of it. This needs to be a shared understanding, so we all have a common base to reason from.
Since the goal here is to have a shared understanding, I'd like for everyone in engineering working on cloud
infrastructureto review this before we merge it!

[x] @sgibson91
[x] @GeorgianaElena
[x] @damianavila
[x] @AIDEA775
[x] @consideRatio

Fixes https://github.com/2i2c-org/infrastructure/issues/3760

For a cloud provider like Azure where we do not have access to the 'billing' components, are we still able to see what the costs incurred are? Or are those cost invisible to us?

@jmunroe right now, with the only azure customer we do have, afaik we don't have that visibility.

Small note: update mentions of dollar amounts with the "$" at the front - e.g. $589
I found this basic rundown of where costs are accrued and definition of things helpful as a scientist! Admittedly some sections were dense for me still. I would encourage users I interface with to read this as they're exploring options for cloud computing.
However I know a handful of users who would want even more specific estimates for the types of workflows they're doing. I don't think those specific estimates need to live here, I know Coiled has shared a couple of blogposts showing workflows+cost+time that demonstrate this. Those users need to see more experiences from peers, and frankly, need to learn-by-doing to get the estimates they're looking for.

I've also received feedback from @BriannaLind via this hackmd (https://hackmd.io/XOT50WWUTiCDqfxLjcevUw?view) and have pushed https://github.com/2i2c-org/infrastructure/pull/3773/commits/27d622e499162f3a7189b52cd3a96c48078bb459 with some fixes. Thank you for your suggestions, @briannalind!
And thanks for your feedback too, @alexishunzinger! I think based on your and @briannalind's feedback, I'll try to open some issues for follow-up documentation to be written.

I'd still like @damianavila to take a quick look, but otherwise this is good to go.

Thanks for the reviewing and feedback, everyone!


sys/linux/dev_binder.txt: also support real-world binder device names

It was reported that binder isn't covered when using syzkaller on a real
Android device, since the binder device names are different.  Update the
descriptions to know about the real-world device names too.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1435   +/-   ##
=======================================
  Coverage   56.62%   56.62%
=======================================
  Files         135      135
  Lines       25652    25652
=======================================
  Hits        14525    14525
- Misses      10453    10454    +1
+ Partials      674      673    -1

Impacted Files
Coverage Δ

prog/target.go
55% <0%> (-7.15%)
:arrow_down:

prog/prog.go
81% <0%> (-2.5%)
:arrow_down:

prog/any.go
88.69% <0%> (-0.71%)
:arrow_down:

prog/rand.go
87.63% <0%> (-0.55%)
:arrow_down:

pkg/csource/csource.go
81.63% <0%> (+5.83%)
:arrow_up:

Continue to review full report at Codecov.

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

A better way to handle this would be to enable binder0/31 on the tested devices. That is the intention behind the current descriptions (binder0/31 are not present on any kernel unless they are specifically enabled). A devices needs to be prepared for fuzzing anyway (enable KASAN/KCOV, etc). Using real binder devices will cause interference between test processes and with services connected to the binder devices.

Hm, this is an interesting problem. The difficulty is that we are attempting to fuzz given different SELinux policies (e.g. fuzz from an untrusted app), so renaming the interfaces makes that harder as we'd also have to change the SEPolicy to match, and risk fidelity issues.
I'm not sure what the ideal solution is here, but renaming is probably going to be hard. What is the problem with interfering with services connected to binder?

I see. This is nasty. Let's try this then.


NPE with new json deserialization support of non EntityView but classic DTO or shuch is provided

If you use a normal DTO like https://github.com/EugenMayer/java-spring-pocs/blob/master/src/main/java/de/kontextwork/poc/spring/blaze/fullapp/subject/group/model/api/TestDTO.java
@Data
@Builder
public class TestDTO
{
  String name;
}

if you deserialize this, you get an NPE
Caused by: java.lang.NullPointerException
	at com.blazebit.persistence.integration.jackson.EntityViewAwareObjectMapper.readerFor(EntityViewAwareObjectMapper.java:71)
	at com.blazebit.persistence.spring.data.rest.impl.json.EntityViewAwareMappingJackson2HttpMessageConverter.readJavaType(EntityViewAwareMappingJackson2HttpMessageConverter.java:71)
	at com.blazebit.persistence.spring.data.rest.impl.json.EntityViewAwareMappingJackson2HttpMessageConverter.read(EntityViewAwareMappingJackson2HttpMessageConverter.java:59)
	at org.springframework.web.servlet.mvc.method.annotation.AbstractMessageConverterMethodArgumentResolver.readWithMessageConverters(AbstractMessageConverterMethodArgumentResolver.java:205)
	at org.springframework.web.servlet.mvc.method.annotation.RequestResponseBodyMethodProcessor.readWithMessageConverters(RequestResponseBodyMethodProcessor.java:158)
	at org.springframework.web.servlet.mvc.method.annotation.RequestResponseBodyMethodProcessor.resolveArgument(RequestResponseBodyMethodProcessor.java:131)
	at org.springframework.web.method.support.HandlerMethodArgumentResolverComposite.resolveArgument(HandlerMethodArgumentResolverComposite.java:127)
	at org.springframework.web.method.support.InvocableHandlerMethod.getMethodArgumentValues(InvocableHandlerMethod.java:167)
	at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:134)
	at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:105)
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:893)
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:798)
	at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:87)
	at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1040)
	at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:943)
	at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006)
	... 100 more

from com.blazebit.persistence.integration.jackson.EntityViewAwareObjectMapper#canRead
where
ManagedViewType<?> managedViewType = entityViewManager.getMetamodel().managedView(type);

managedViewType is null, while the type is a java list
Seems like the BP integration, out of any reason, thinks it is a EV? ( TestDTO are used in a list here as a payload
Reproduction
As usual at
https://github.com/EugenMayer/java-spring-pocs/blob/master/src/test/java/de/kontextwork/poc/spring/blaze/fullapp/subject/group/controller/GroupControllerTest.java#L134

I never yet wrote such a deserializer / serializer for jackson, but i would expect that
com.blazebit.persistence.spring.data.rest.impl.json.EntityViewAwareMappingJackson2HttpMessageConverter#canRead
would be called before an class get's deserialized bu an specialized deserializer? It is not called at all in my case, so i wonder if that might be the reason?
Since we are implementing HttpMessageConverter for that matter i wonder why it is never called?
The docs of that interface for canRead tell us
 * Indicates whether the given class can be read by this converter.

Looking at ProjectingJackson2HttpMessageConverter it seems like the implementation of EntityViewAwareMappingJackson2HttpMessageConverter seems about right.

Interestingly during parsing of this TestDTO the first converter called is
org.springframework.http.converter.json.AbstractJackson2HttpMessageConverter#canRead(java.lang.reflect.Type, java.lang.Class<?>, org.springframework.http.MediaType)

And for that one, org.springframework.http.converter.json.AbstractJackson2HttpMessageConverter#canRead(java.lang.reflect.Type, java.lang.Class<?>, org.springframework.http.MediaType) is called.
The whole logic with canRead is done in

There the relevant canRead for asking for the targetClass should be called, but i'am not entirely sure what this semantically means
if (genericConverter != null ? genericConverter.canRead(targetType, contextClass, contentType) :
						(targetClass != null && converter.canRead(targetClass, contentType))) {

AFAIU this semantically
genericConverter != null ? genericConverter.canRead(targetType, contextClass, contentType) :
						(targetClass != null && converter.canRead(targetClass, contentType))

It is like "if the genericConverter is set( which is indeed the same as converter,EntityViewAwareMappingJackson2HttpMessageConverterin our case ) use the canRead guard whch us basically something likecan you convert from this to that mimetype` .. this guard is not targetClass specific, it's just the the mimetypes in general.
If it is not set, the converter is asked ( which is EntityViewAwareMappingJackson2HttpMessageConverter again ) .. but this type using the targetClass guard (which would be the right one for us )
... the latter is never called thus the EntityViewAwareMappingJackson2HttpMessageConverter is used to deserialize the non EntityView class and it clashes.
From my POV this is a spring bug since that simply makes no sense. Of course it makes sense to ask for the general compatibitliy of the source to target mimetype - but right after one needs to ask for the compatibility with the target type too - this is not what is implemented here and it hardly makes sense to me considering the signature of the both canRead and their meaning.

Thank you @beikov !


Added heightmap models created by Ibrahim

@ibrahimhroob I think you can add the heavy heightamp that you showed me in the same zip containing the vines as discuss. If the URL link changed compared to the one listed in the CMake, please push a new commit with only the new link. After that, we can close this PR ;)

I am closing this PR. @ibrahimhroob will open a new one where all the heightmap model will be contained in a zip downloadable at compile time from Cmake.


Array () missing for converted types

(string[] types, string[] names, string[]? fields) = ExtractProperties(parser);

is being converted to
Dim TupleTempVar As (String, String, String?) = ExtractProperties(parser)

It should be
Dim TupleTempVar As (String(), String(), String()) = ExtractProperties(parser)

Fixed in converter <IP_ADDRESS>

Fixed in converter <IP_ADDRESS>


Fix Issue 20288 - std.format with separator and double causes RangeError

std.format with separator and double causes RangeError
https://issues.dlang.org/show_bug.cgi?id=20288

Please put the issue title in the commit/PR title, it's impossible to know what "Fix Issue 20288" means without further action.

Robert Schadek: I need a win32_64 box

This should help -> https://github.com/dlang/phobos/pull/7226 (Azure 10 parallel boxes and thus drastically faster start times).

Shouldn't "-nan" not exist at all? I'm aware, that there are several ways to express nans in the IEEE standard, but I always thought, that D does not distinguish between them and therefore should still output "nan" instead of "-nan" when the sign bit of a nan is set.
I'd like to point to issue 19878 which questions the result "-nan"  when using writeln.
Is there anything official about using -nan or not? I was not able to find anything useful.

@berni44 I looked at the standard. Section 6.3 of 754 2008 states that the standard does not interpret the sign bit of NaNs, but some operation specify it. IMHO phobos should there display the sign.

rikki cattermole wrote in the Forum in a related thread, that the behaviour of printf is the baseline. According to this -nan is correct and issue 19878 should be marked "invalid".

printf on which platfrom, win32 win64, glibc, bsd? they all do things differently.

printf on which platfrom, win32 win64, glibc, bsd? they all do things differently.

Shouldn't that be covered by the C standard?

I don't have the latest standard at hand, but in the latest publicly available one
http://www.open-std.org/JTC1/SC22/WG14/www/docs/n1570.pdf
on page 312 it states that

Adouble argument representing a NaN is converted in one of the styles
[-]nan or [-]nan(n-char-sequence) — which style, and the meaning of
any n-char-sequence, is implementation-defined.

The phrase implementation-defined appears quite a lot in the paragraph.
real values are not mentioned at all.
More interesting is footnote 277

When applied to infinite and NaN values, the -, +, and space flag characters have their > usual meaning; the # and 0 flag characters have no effect

I therefore think that the implemented behavior of this PR is "correct" in that it makes all platforms act as linux 64bit.
Which I turn IMHO is the sanest of them all (sign is preserved)

Interesting. So printf and the C documentation is not really a reliable source...
Maybe we (= D community) have to define ourselves, what format() should do and clearly document that. Looks like lot of work...

eventually yes, but not in this PR. This PR fixes a crash and makes a minor thing behave equal across all platforms.
Doing the thing you mentioned, would firstly require phobos to have its own float formatting. Currently we call snprintf.
But again, the this PR does a tiny narrow thing. And shouldn't grow to do all that.

Yes, I agree. In my oppinion, this PR can be merged.
Beyond this PR, for me the question is, what's better: Do more of such corrections or provide a complete rewrite of formattedWrite and Co. using regex for parsing the format string, providing our own float formatting and so on. When looking into bugzilla, there are lots of bugs in here and correcting them might be more work than a sound rewrite.

I think doing our own formatImpl from float/double/real to string would be pretty good already.

Having had a closer look at the files, I don't understand how the changes in std.conv are related to this bug.

windows 32 is doing some really crazy stuff with floats, these changes just add some  sanity checks.

and std.conv.to!string( some_float ) uses std.format

We have discussed yesterday performance issue with float --> string conversion. The default implementation in libC is painfully slow. PyPy is 2x faster (!!) because they have their own implementation. Something like this in Phobos would be welcome: https://www.reddit.com/r/ProgrammingLanguages/comments/930pch/ryu_a_new_algorithm_to_quickly_convert_floating/

I ported the ryu algorithm to D in about an hour, source here: https://github.com/dragon-lang/mar/blob/master/src/mar/ryu.d

Meanwhile I read through the paper on ryu. I may be wrong, but I think this algorithm is not useful for this task, for two reasons:
a) The goal is slightly different to that of printf. While ryu tries to print as few digits as possible, printf prints as much as the format string defines. If that's larger than what ryu computes, the remaining digits will be wrong.
b) Ryu uses a lookuptable which is IMHO far too large for a standard library. For 128bit reals it's about 300K of data, that needs to be stored.

@UplinkCoder I'll have a look at the grisu implementations to see if it can be used for this task. But due to my time schedule this will probably have to wait one or two weeks.

@marler8997 I'm working on a more robust (than the original) translation that has everything you need to replace the current implementation format() uses.  Already have support for only printing out some digits; main task now is not to print out numbers with small exponents as scientific notation (that is, 123.45 instead of 1.2345e+2).  Then trailing/leading zeroes should be easy enough.
Benchmarks suggest a not quite 2x bump in speed; maybe 1.8x.

@moon-chilled great.  You'll have to share it.  I only ported the 32-bit version of ryu.  For the 64-bit version I wasn't sure if it should be completely separate like the original did, or if I should try to combine them and re-use common code.  I look forward to seeing your port.

Here.  (Lookup tables end at line 380--I really need to ctfe those, because they kill compile times.)
I was planning on mostly re-using code, once I figured out a good architecture for the 64-bit version.
Oh, also - I forgot; it'll probably also get a decent speedboost once I get the 128-bit multiplies in hardware.

https://issues.dlang.org/show_bug.cgi?id=19124

This caused a regression: https://issues.dlang.org/show_bug.cgi?id=20623


[C-626] Improve member search in merge members

From a user:
"Searching for merging members is a pain. The autocomplete will give you only the name, no preview like avatar, only 10 in the autocomplete, leading to the member page and searching the exact members' name."
This is not the normal search, but for example when searching for members to merge
Solution
We should have a better search. We should show the avatar and organization (just name).
From SyncLinear.com | C-626

only organization name missing


ariaLabel prop does not work for the node and edge

Describe the Bug
Hi, from the doc, the arialLabel of the edge is from ${source} to ${target} at default. but when I hover the mouse on edge in the overview example, this label does not show. The buttons on the control do show the label.
I also add the arialLabel to the node data in the initial-elements.js as the following example, but it still does not work.
 {
    id: '1',
    type: 'input',
    data: {
      label: 'Input Node',
    },
    position: { x: 250, y: 0 },
    ariaLabel: "This is a input node"
}

Your Example Website or App
https://codesandbox.io/s/wm2vrx?file=/initial-elements.js&utm_medium=sandpack
Steps to Reproduce the Bug or Issue
This example is the copy of the official overview example with little change.

Hover the edge, no ariaLabel
Add the ariaLabel pros in the inittial-elements.jsthe node,
Hover the node,  no ariaLabel

Expected behavior
We can see the ariaLabel for the edge and node as the minimap or control buttons.
Screenshots or Videos
No response
Platform

OS: [Windows]
Browser: [Microsoft Edge]
Version: [Version 110.0.1587.46 (Official build) (64-bit)]

Additional context
Thanks for your help.

Hey! An aria label is meant to be used by screen readers. It's not a tooltip equivalent. If you want that, you can create a custom node and use the title prop. ariaLabel prop for nodes and edges work as expected.

Thanks a lot:)


On Initial Setup, ASGARDEX Public Key for BCH - ERROR. Invalid. How can this be fixed?

<!--
  Is this a bug report?
  If so, go back and select the "Bug report" option or your issue WILL be closed.
--!>

@timajor67 Could you some more details, pls? Which ASGARDEX desktop version, which OS, what's the error in detail, share screen shot if possible...

hey @timajor67. really strange issue and we need more details...
actually i've tried to run an application from a scratch with virtual box with win10 image installed and have not faced any issues there

@timajor67 Pls let us know about if you still have any issues. Closing this issue for now ...


Remove deprecated code for 3.0

When dependent code has had dependencies made more flexible to allow for a 3.0 version, the develop branch of RDF.rb can have version updated to 3.0.0. Prior to that, probably need to do work on a branch.

Fixed in bbd09a9ac379d1999205200abb938564938fd2a3.


Detect padding in doc comments

What does this PR accomplish?

🦚 Feature

Closes #133.
Changes proposed by this PR:
Detect padding in doc comments with CommentPaddingStyle enum
Notes to reviewer:
Adds enum and detect_padding method to parse and store padding style
📜 Checklist

[ ] Works on the ./demo sub directory
[ ] Test coverage is excellent and passes
[ ] Documentation is thorough

Thanks for the feedback on this! I updated the branch with your comments, should this be incorporated into the trim_span method or should it only detect the padding style for now and leave the padding inside the TrimmedLiteral?

Great, thanks! Should this be in or before the trim_span method then? I know you had mentioned moving the padding detection after, but it seems like we would need ti there.
Also, I think we'll need to bump the version of fancy-regex to take advantage of the replace_all method for parsing this if that's alright


volume-permissions - volumes are rw by default

@allamand can you take a look ? there is no reason tests fail because of that change

needs to be rebased on master for triggering tests


Add Lobste.rs

Adding https://lobste.rs at 685 bytes.
I created this SVG in Inkscape using this png as a reference.

That's a really good start - thanks!
Would you mind adjusting it so it matches the template at https://github.com/edent/SuperTinyIcons/blob/master/CONTRIBUTING.md ?
Shout if you need any help.

Sorry @edent, I should have read the CONTRIBUTING.md before opening this PR!
I think this is all ready to go now.

Looks good to me! Thanks for updating the PR


Jobs report does not reliably report all jobs with --running

Consider these two queries (live data):
[larstha@ml2 sonar]$ ./sonalyze jobs -u- --data-path data --host=ml2 --running
jobm      user    duration  host  cpu-avg  cpu-peak  mem-avg  mem-peak  gpu-avg  gpu-peak  gpumem-avg  gpumem-peak  cmd
3637115>  limeng  0d 1h25m  ml2   1854     2560      108      118       340      394       27          29           python
[larstha@ml2 sonar]$ ./sonalyze jobs -u- --data-path data --running
jobm      user      duration  host  cpu-avg  cpu-peak  mem-avg  mem-peak  gpu-avg  gpu-peak  gpumem-avg  gpumem-peak  cmd
233139>   larsbent  0d23h55m  ml7   411      887       17       19        4        27        2           2            python
236008>   larsbent  0d23h55m  ml7   434      891       16       16        3        19        2           2            python
255151>   larsbent  0d23h55m  ml7   436      876       17       18        3        19        2           2            python
257926>   larsbent  0d23h55m  ml7   444      839       16       17        4        20        2           2            python
261275>   larsbent  0d23h55m  ml7   0        0         81       81        0        0         0           0            python
265485>   larsbent  0d23h55m  ml7   0        0         80       80        0        0         0           0            python
611949>   tobiasao  0d23h55m  ml7   467      823       4        4         0        0         0           0            python
631575>   tobiasao  0d23h55m  ml7   468      827       4        4         0        0         0           0            python
640122>   tobiasao  0d23h55m  ml7   468      827       4        4         0        0         0           0            python
1718595>  saeedes   0d23h55m  ml7   45       110       14       38        13       70        7           11           python3
1719530>  saeedes   0d23h55m  ml7   2        3         3        3         0        0         0           0            python3
1810351>  saeedes   0d23h55m  ml7   44       92        42       155       12       84        11          11           python3
1819603>  saeedes   0d23h55m  ml7   2        3         3        3         0        0         0           0            python3
1882506>  hermanno  0d23h55m  ml7   1        2         2        2         0        0         0           0            kited
1882622>  hermanno  0d23h55m  ml7   0        0         1        1         0        0         0           0            code-abd2f3db4b
3034150>  saeedes   0d23h55m  ml7   46       89        13       38        13       43        9           11           python3
3035684>  saeedes   0d23h55m  ml7   2        3         3        3         0        0         0           0            python3
3243423>  adamjak   0d22h25m  ml7   38       60        3        3         95       99        9           9            python

Why is the job listed in the first report not listed in the second report?
Indeed there are about 30 jobs running on ml6 as well that don't show up in the report.  This is pretty bad.
I ran this from ml2 but since there is a problem with ml6 jobs too, I don't think that has anything to do with it.

Evolving task list:

[x] sonarlog: return a hostname-keyed set of metadata instead of global metadata
[x] sonarlog: merge metadata with data, when appropriate
[x] sonalyze: pass around and use hostname-keyed metadata
[x] test cases

One issue I see is that when the files are being enumerated, logtree also finds the cpuhog.csv and deadweight.csv files.  That's broken, but these records are rejected, so that's not the problem, and ad-hoc filtering those names validates that conclusion.
The number of samples read and remaining after filtering remains the same up through the filtering of streams - the number of filtered streams is the same.  But then the by-host filtering diverges from the all-hosts filtering.  The all-hosts filtering leaves us with 19 jobs (the ones seen above), the sum of the by-host filtering with 80 jobs (more like what we expect).

This was starting to look like a rustc Heisenbug, and it is a relative of that, because it involves time: it's the computation of the LIVE_AT_END attribute that is wrong.  This attribute is set if the time of the last record in a job equals the time of the last record read from disk.  But this is bogus, because sampling across hosts are not synchronized.  With a single host, we read only the records for the one host, and so time is sane.  With multiple hosts, the latest time must always be per-host.  So it's the --running flag that triggers the bug, because that causes that attribute to be examined.

Probably:

read_logfiles in sonarlog returns a map host => {earliest,latest}, rather than just the two global values
these are passed down through sonalyze and used appropriately
there's going to be some complexity around merging these values when we have cross-host jobs

Fixed.


Fix node edits

Pull Request Description
After #9127, Mod+Click on a node doesn't begin editing the node's code. This is a quick fix to re-enable node code edits.
Important Notes
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[ ] The documentation has been updated, if necessary.
[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[ ] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[ ] Unit tests have been written where possible.
[ ] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

Since we have #9153 now, I think it's not worth merging this anymore.


Fix LDAP parameters for SOC 6

The group_members_are_ids LDAP parameter wasn't added until f9e5076d in
SOC 7, so trying to use it in SOC 6 results in a crowbar proposal
error. This patch moves the parameter so that it is only used with SOC
7.

Is it the only one that is not in Cloud 6? FWIW, a mkcloud run with GM6+up can be used to check this.

@vuntz I checked the keystone schema from release/suse-openstack-cloud/6 and group_members_are_ids is the only parameter used here that wasn't in that schema.


Added working cell revert for invalid submissions in edit data.

This is to fix the cell edit trigger for submitting cells that only worked if it detected changes in the cell from slickgrid. Previously the cell was left alone during an invalid edit (and recognized by slickgrid as having no changes), which meant that when submitting again the trigger would not be fired, causing the invalid data in the cell to be falsely added to the grid. Now a cell revert is done and the invalid cell data is restored so that the cell is recognized as dirty again by slickgrid.
This is similar to the existing logic for invalid edits in the new row.
Fixes https://github.com/microsoft/azuredatastudio/issues/21182
GIFS of the change in action:
Existing row:

New row:

Converted revert functions to proper async, they've been tested to work. Other areas that have async besides these two are proper async functions as well.


add working-directory docs

Good call on adding some docs. Can you change it so that the existing example isn't changed, and add a new example with set working-directory?


[Concurrency] Task options for waiting on tasks

This is ABI breaking, need to figure out if that's still okey or not anymore.
We can add it without breaking by adding new entry points.
This adds TaskOptionRecord* to all await operations, including the async let end so we can wait in there with options as well.
Replaces https://github.com/apple/swift/pull/38019
Resolves rdar://78931812

@swift-ci please smoke test

Missed some IR tests, fixed now.

@swift-ci please smoke test

Replaced by ABI additive version https://github.com/apple/swift/pull/38156