First draft of the new n-dimensional arrays + NB use case

This PR will eventually solve #85. The goal is to have an abstract layer that can be implemented by concrete library that enables all traditional functionality provided by n-dimensional arrays: array manipulation, transformation, basic linear algebra routines, views e.t.c.
The abstract layer I am proposing here enables us to:

have arrays that can hold multiple types, including strings
implement more efficient ML algorithms that minimize memory copy operations
have ML algorithms that declare more granular requirements to input and output types, e.g. we can declare an input type for an algorithm that does need a simple non-mutable array w/o typical linear algebra routines.

As a bonus, this PR introduces a row-major dense matrix that might get handy in some cases.

@morenol there are multiple problems with this PR, like printlns, lack of documentation, e.t.c. and I plan to fix these within next 3-4 of weeks. But I thought I'd share this PR with you so that you can take a look on proposed changes earlier. Besides, I've decided to try new abstract layer on NB first.

Codecov Report

Merging #108 (2c7fab0) into development (1208051) will decrease coverage by 1.47%.
The diff coverage is 76.77%.

@@               Coverage Diff               @@
##           development     #108      +/-   ##
===============================================
- Coverage        84.17%   82.70%   -1.48%
===============================================
  Files               78       87       +9
  Lines             8249     9614    +1365
===============================================
+ Hits              6944     7951    +1007
- Misses            1305     1663     +358

Impacted Files
Coverage Δ

src/linalg/mod.rs
50.30% <ø> (-2.46%)
:arrow_down:

src/num.rs
20.83% <20.83%> (ø)

src/naive_bayes/mod.rs
68.00% <42.85%> (-5.92%)
:arrow_down:

src/linalg/nalgebra/vector.rs
53.95% <53.95%> (ø)

src/linalg/ndarray/vector.rs
68.00% <68.00%> (ø)

src/linalg/ndarray/matrix.rs
72.22% <72.22%> (ø)

src/linalg/nalgebra/matrix.rs
76.78% <76.78%> (ø)

src/linalg/dense/matrix.rs
80.60% <80.60%> (ø)

src/linalg/base.rs
80.92% <80.92%> (ø)

src/naive_bayes/categorical.rs
82.28% <85.36%> (-0.21%)
:arrow_down:

... and 20 more

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 1208051...2c7fab0. Read the comment docs.

@VolodymyrOrlov this looks nice.
Since we are rethinking the way that the arrays are represented I think that we should consider the usage of const generics.

Any concrete ideas how we can use const generics to improve the proposed abstract layer? For example, const generics can be used to define number of dimensions in S

I think that I edited your comment instead of a response: here it is

Any concrete ideas how we can use const generics to improve the proposed abstract layer? For example, const generics can be used to define number of dimensions in S

I am not sure how we can use them in the abstract layer. I was thinking  in the structs defined in linalg::dense::. We can create an special type for static sized arrays. But maybe it is better to keep it simple and use nalgebra and ndarray when we want that kind of optimization

Great work Volodymyr! This looks really promising.
Just few notes to check if I understood the new abstraction and to help devs in digging:

we are going to have new traits groups to define types for array/vectors elements: Num/Number and FloatNumber (I like it!) directly using num_traits;
A lot of things going on in linalg/base.rs:

new smartcore Array-related type declarations to provide a unified interface, including the ones from optimised strides read/write.
this interface is the toolbox to be leveraged by higher-level types, in particular the new implementations in linalg/dense/;

we have now "views" types that, I assume, are to provide segmentation for the unerlying structs so to allow reusing of the same instantiated struct and avoid copying;
supercool the "Decomposable"s for structs decomposition.

Will help with documentation as soon as it is relatively stable.
@steboss check it out!

Great work Volodymyr! This looks really promising.
Just few notes to check if I understood the new abstraction and to help devs in digging:

we are going to have new traits groups to define types for array/vectors elements: Num/Number and FloatNumber (I like it!) directly using num_traits;

A lot of things going on in linalg/base.rs:

new smartcore Array-related type declarations to provide a unified interface, including the ones from optimised strides read/write.
this interface is the toolbox to be leveraged by higher-level types, in particular the new implementations in linalg/dense/;

we have now "views" types that, I assume, are to provide segmentation for the unerlying structs so to allow reusing of the same instantiated struct and avoid copying;

supercool the "Decomposable"s for structs decomposition.

Will help with documentation as soon as it is relatively stable.
@Steboss check it out!

That's right! The goal is to build a rich interface for 1- and 2-dimensional arrays that can be extended by anyone later. On one hand we can make ML algorithms more efficient by relying on a concrete library, like nalgebra or ndarray. Investing time into an abstract layer that facilitates integration with 3rd partly libraries, on the other hand, gives us a lot of flexibility and saves time later, if we find it necessary to bring in some other library in the future.

@morenol please take a look, there are still missing implementation but the code is at least cleaned up.

conflicts with development should be now solved
there are some types that are not correct, in particular in src/linear/ridge_regression.rs and src/linear/logistic_regression.rs
tests need to checked against the new typed structures and implementations.
... (probably hundreds of things more) 💯

please fetch this branch and run cargo build --lib, maybe there are some errors for which the solution is evident to you people.

I can take a look later today

sure, when you have time. If we can fix the static analyzer (in src/ensemble) and compiler errors maybe we can move into running test 👍🏼

@montanalow please take a look to ensemble and linear modules as you are more familiar with those procedures. The objective is to make things to compile and then move into making the tests to pass. Also I saw some conflicts when pulling the very latest changes.

great job @morenol
Can you tell me why we are missing definitions for ElasticNetSearchParameters, LassoSearchParameters, LinearRegressionSearchParameters? that instead are present in development?
I will try a merge, another hundred conflicts to solve

ElasticNetSearchParameters

not completely sure, we probably need to split in several PRs once we have all the conflicts solved in order to make it easy to review

@montanalow great! I was splitting the changes into multiple PRs but if you can do in one pass that would be awesome.

@montanalow great! I was splitting the changes into multiple branches but if you can do in one pass that would be awesome.

#171 is up that should resolve all merge conflicts in this branch, although it's a fairly large change set...

The library now compiles but there are still a lot of runtime errors and tests to fix.
I have not yet a clear understanding about what it is going to be the substitute for DenseMatrix, I thought it should have been Array2 but how to instantiate it? For example this test. Also predict_oob is still broken as I don't know how to implement it without using the samples property that has been removed.
I am not still sure we can merge this all at once, I will probably start opening a PR to merge num.rs so we can do it gradually.

#173
Also I still don't understand how traits like QRDecomposable and the others are supposed to be used.

I am seeing discrepancies between the metrics::recall module in development and the one in this branch. Things are getting too entangled, please move and follow up to #173 for a more stepwise implementation.

please help. it is quite easy, just follow the implementations in the other ported modules. cc: @morenol @montanalow @titoeb
Missing modules,

preprocessing
readers
svm

All work moved to https://github.com/smartcorelib/smartcore/tree/v0.5-wip


docs: FlameGame needs documentation+dartdocs about W

The generics of FlameGame needs a sentence or two in the Flame docs and as dartdocs.
Originally posted by @IanWadham in https://github.com/flame-engine/flame/pull/2842#discussion_r1397089423

Can I work on this issue sir?

Go for it, I'll assign you to the issue


New variability of authorization

Reworked authorization.
Rendered by AuthRefresh Interceptor.
Added AuthDelegate to implement custom authorization.
Are dynamic types now Object?.
Updated dependencies.
Updated example with new authorization.
Somewhere tests are added.

[x] The ability to take additional fields
[ ] Authorization tests

It looks like for some reason commits can't be linked to you. Maybe you used different email? Would you like to open new PR with correct info? I can merge all commits before 4f93fa6

I'm sorry, I don't have enough time right now to actively participate in this.
I saw your remarks and agree to take them off.
can I delegate it all to you?

Sure, thanks for the bug fixes.
I made a draft PR that cherry picks most of the commits from this PR in #25.
For some reason commits in this PR can't be linked to you, it credits "pashkadev" for commits. Probably due to changed info.


IDVA6-855 analytics cancel an authorised person

Link to Jira:
https://companieshouse.atlassian.net/browse/IDVA6-855
Changes:

Matomo tags added to cancel person page

CI: No security warnings found

CI: No security warnings found


Haxelib ignores dev-version as existing dependency

haxelib  list hxcpp
hxcpp: [git]

haxelib git hxcpp-debugger https://github.com/HaxeFoundation/hxcpp-debugger.git
Installing hxcpp-debugger from https://github.com/HaxeFoundation/hxcpp-debugger.git
Library hxcpp-debugger current version is now git
Installing dependency hxcpp
Downloading hxcpp-3,3,49.zip...
750515/49476374 (23%)
^C

This should not occur because the any version specified in the haxelib.json and dev/git version is already exists.

Steps to reproduce:

haxelib remove hxcpp remove all hxcpp versions;
haxelib git hxcpp https://github.com/HaxeFoundation/hxcpp.git install only dev git version;
haxelib git hxcpp-debugger https://github.com/HaxeFoundation/hxcpp-debugger.git install library dependent on hxcpp;
Haxelib will do Installing dependency hxcpp but it's already exists as dev.

Strangely it doesn't happen if you replace step 2 with haxelib dev hxcpp ./hxcpp/.

I think it because wrong behaviour in the call-path:

checkout if dev-version is existing
but there no checking VCS-version, only .dev: see code function getDev( dir ) return File.getContent(dir + "/.dev").trim();

Info about VCS-version (git or hg) stores in the .current file as git or hg - name of subdir.
For fix if we should add there checking "if current is git or hg ⇒ continue".


Feature request: Add position in the string for each node

Thanks for this library, it works well and I didn't found any issue 🚀
It could be nice to add information about each node like the position in the original string and the length of start/end tag (including the separator character, arguments and spaces).
It could be also nice to have the raw inner content of the current tag (if I want to make a [code][/code] tag that don't render anything in it).
For the following string: "example [b=value] my text [/b   ] end", we could imagine to add a startTag and endTag with the following informations:
[
  "example",
  " ",
  {
    "tag": "b",
    "attrs": {
      "value": "value"
    },
    startTag: {
      "index": 8,
      "length: 9
    },
    endTag: {
      "index": 26,
      "length: 7
    },
    "content": [
      " ",
      "my",
      " ",
      "text",
      " "
    ]
  },
  " ",
  "end"
]

What do you think?

Good idea. It can produce more useful information when error occurs.

Thank you so much ! It will help me to support [code] tags that contains bbcode :)


Gem update?

Hi, I find your gem cool, but it is not compatible with actual version of https://rubygems.org/gems/prawn. For example:
uninitialized constant Prawn::Core::LiteralString

Will you update this gem?
Thanks a lot.

Are there any details with the error or it's cause?
I looked into the code...does prawn-forms do just text-fields or can it do more.  Parts look like it can do a button, but the code indicates some "option flags" for doing checkboxes/radios.  combo boxes?


ENTITY:SetBodyGroups with nil causes error

Entity:SetBodyGroups() with "nil" given will error where function expect "string"

Resolved via edbba15f4edb79fd4b8103b02d517536ef9749eb.


Add classification flags for all mythos events

All mythos events need to have one of these added:
mythosFlavor - Events that do not have any game effect
mythosMinor - Events that do not have a large impact
mythosMajor - Events that have a large impact
mythosDeadly - Events that will mess you up
Some may also have:
mythosIndoors - Events that affect investigators indoors
mythosOutdoors - Events that affect investigators outdoors
mythosHallway - Events that happen to investigators in a hallway
mythosStreet - Events that happen to investigators in a street or alley
mythosGrave - Events that happen to investigators in a crypt, graveyard or morgue
mythosLibrary - Events that happen to investigators in a library
mythosKitchen - Events that happen to investigators in a kitchen
#fire - Events that happen to investigators in a fire (controlled by Valkyrie)
mythosDarkness - Events that happen to investigators in darkness
Or others as appropriate.

My Ranking System:
Add up all the potential damage:
Facedown Damage/horror: 1
Faceup Damage/Horror: 1.5
Condition: 1.5
Flip faceup: 0.5
If multiple investigators are affected multiple by the likely number of targets.
For negating damage multiply by these factors:
negate-2;10.6
negate-1;10.4
negate 1;10.25
negate+1;10.15
negate+2;1*0
negate-2;20.7
negate-1;20.6
negate 1;20.5
negate+1;20.4
negate+2;2*0.25
negate-2;30.9
negate-1;30.8
negate 1;30.65
negate+1;30.5
negate+2;3*0.4
negate-2;40.9
negate-1;40.8
negate 1;40.7
negate+1;40.6
negate+2;4*0.55
For avoiding damage multiply by these factors (note if there is a bad thing in a fail, add that in with the inverse factor):
test-2;1 *0.6
test-1;1 *0.4
test  ;1 *0.25
test+1;1 *0.15
test+2;1 *0
test-2;2 *1
test-1;2 *.85
test  ;2 *0.7
test+1;2 *0.5
test+2;2 *0.4
test-2;3 *1
test-1;3 *1
test  ;3 *0.95
test+1;3 *0.85
test+2;3 *0.7
Some events drop items or do other things, these are harder.


Add support for forcing MFA on SP

Create a placeholder for ForceMFA = $true or something in ManualSPSettings.

Solved by #201
Just use builtin Access Control Policy: Permit everyone and require MFA
as a Custom Access Control Policy


Bugfix for #7527

When the createResource is rejected on ssr evaluation v is undefined which is not handled. I actually don't really understand what  v is.
I don't want to blame here any good open source soul, but just wanted to metion in a lovely manner that naming things in a verbose way makes the code 100% more readable for other developers :)
Actually I don't know if this is correct way to approach this issue, it could be that there is an underlying problem that causes v to be undefined
fixes #7527

can you please add a test that covers this scenario?

I can definetly try, but currently I have no idea how to achieve that.
Btw. would be very kind if this issue #7513 gets fixed very soon :)

I'm not sure how to achive hydration testing in solidjs. When I just use this simple example:
 function Page() {
      return (
        <div>
        </div>
      )
    }

    const rendered = render(() => <Page/>, {hydrate: true})

The vitest failes with this error message:
TypeError: Cannot read properties of undefined (reading 'completed')
    at hydrate$1 (file:///C:/Users/David%20Bieregger/WebstormProjects/query/node_modules/.pnpm/solid-js@1.8.17/node_modules/solid-js/web/dist/dev.js:726:44)
    at hydrate (file:///C:/Users/David%20Bieregger/WebstormProjects/query/node_modules/.pnpm/solid-js@1.8.17/node_modules/solid-js/web/dist/dev.js:1062:10)
    at Module.render (file:///C:/Users/David%20Bieregger/WebstormProjects/query/node_modules/.pnpm/@solidjs+testing-library@0.8.8_@solidjs+router@0.13.3_solid-js@1.8.17__solid-js@1.8.17/node_modules/@solidjs/testing-library/dist/index.js:55:29)
    at C:\Users\David Bieregger\WebstormProjects\query\packages\solid-query\src\__tests__\createQuery.test.tsx:5925:22
    at file:///C:/Users/David%20Bieregger/WebstormProjects/query/node_modules/.pnpm/@vitest+runner@1.6.0/node_modules/@vitest/runner/dist/index.js:135:14
    at file:///C:/Users/David%20Bieregger/WebstormProjects/query/node_modules/.pnpm/@vitest+runner@1.6.0/node_modules/@vitest/runner/dist/index.js:60:26
    at runTest (file:///C:/Users/David%20Bieregger/WebstormProjects/query/node_modules/.pnpm/@vitest+runner@1.6.0/node_modules/@vitest/runner/dist/index.js:781:17)
    at runSuite (file:///C:/Users/David%20Bieregger/WebstormProjects/query/node_modules/.pnpm/@vitest+runner@1.6.0/node_modules/@vitest/runner/dist/index.js:909:15)
    at runSuite (file:///C:/Users/David%20Bieregger/WebstormProjects/query/node_modules/.pnpm/@vitest+runner@1.6.0/node_modules/@vitest/runner/dist/index.js:909:15)
    at runFiles (file:///C:/Users/David%20Bieregger/WebstormProjects/query/node_modules/.pnpm/@vitest+runner@1.6.0/node_modules/@vitest/runner/dist/index.js:958:5)

Thanks @BierDav for the feedback! I'll try to rename the variables for better readability.
Also @TkDodo Adding a test suite for Solid Query SSR is proving to be a challenging task. Solid testing library either allows running the tests in either in a ssr or a client environment. So testing the correct hydration of SSR data into the client environment is difficult to achieve unfortunately. I have multiple stale branches trying to get this to work but I end up in roadblocks every now and then. I'll revisit this again someday.


Display device type image

netbox-reorder-rack version
v1.1.0
Feature type
Data model extension
Proposed functionality
Display the front/rear picture of the device type for each device like in the normal rack view
Use case
Better clarity when viewing the rack
External dependencies
No response

I have added the ability to load device type images. Due to how things are loaded and how the Javascript work currently if you move a device from front to back etc it may loose the images. Will need to have a proper think about how to fix that in future.


Update set-up-asset-retirement-obligation.md

The small update for better customer understanding

:x: Organization membership check failed
Members of the MicrosoftDocs organization should use the private repo. Please move your changes to https://github.com/MicrosoftDocs/Dynamics-365-Operations, and close this pull request.


Support dataframe protocol.

https://data-apis.org/dataframe-protocol/latest/index.html

Hi @trivialfis
Quick note to say that I'd discourage using the interchange protocol - I've collect some reasons why here: https://github.com/pandas-dev/pandas/issues/56732#issuecomment-2466301769
If I may, I'd like to suggest Narwhals and/or the Arrow PyCapsule Interface. This is what several packages (e.g. Altair, Plotly, Vegafusion, Marimo, scikit-lego, Rio, and more) are using, with several others (Bokeh, Prophet, formulaic) considering doing the same
Happy to give this a go if you'd be open to it

Thank you for sharing, will look into these.

Perhaps I'm missing something, how come that none of these interfaces can return a C pointer for each column.

Going to cc @kylebarron into the conversation

The Arrow C Data interface returns a pointer that describes a struct-type column, which recursively contains the pointers for all nested columns. That's defined on this page: https://arrow.apache.org/docs/format/CDataInterface.html

Thank you for the references! I will look into that.
We are hoping to avoid any c dependency (including copied definition, and no cpython either) and rely on the Python stack for passing data. In addition, we simply concatenate all the chunks in a column and use a np array as the final data view.
https://github.com/dmlc/xgboost/blob/e988b7cf1515b08ad0f949c26beb043ce0b33fe8/python-package/xgboost/data.py#L450
As you can see, it's fragile and delicate in terms of performance. My wish is something simpler like the numpy __array_interface__ for each column. It has no c dependency and we can simply serialize it as a JSON document and pass it around.

and no cpython either

I think you mean Cython?

We are hoping to avoid any c dependency

I am not sure what you mean by "any C dependency" - do you mean it as in "numpy depends on C" or "does it contain Cython code"? Anyway, Narwhals is just Python. No Cython. It's a unified layer to write dataframe-agnostic code.
Perhaps I'm stating something obvious here, but just to be sure. Narwhals' syntax is a subset of the Polars API (just the syntax: it's not using Polars under the hood) and is used to provide maintainers with a way to write dataframe-agnostic code. In other words: if xgboost implemented its data transformation logic with Narwhals, it would work out of the box with Polars, pandas, cuDF, modin, dask... without the maintainers handling the complexity, or having to support requests to use Polars or whatever new dataframe library will be popular in the future.
This enables any-dataframe-in -> same-dataframe-out transformation: if the user passes a pandas dataframe, pandas will be used to do the transformation. if the user goes with Polars, Polars engine will do the transformation. Then, of course, at the end of your data transformation pipeline you can always cast everything into a (collection of) numpy array(s) for the good ol' model.fit().
Hope this provided a bit more context! 😊

I think you mean Cython?

I meant cpython, we use the ctypes Python module for foreign function calls. Using PyCapsule (from arrow) requires Python CAPI.

I am not sure what you mean by "any C dependency"

Apologies for the ambiguity. I meant the ArrowSchema C struct. Using it implies we will need to either copy the definition of this struct and helper functions into XGBoost (this project) and hope that the ABI is indeed stable or include the Arrow C package as a dependency.

Hope this provided a bit more context! 😊

Thank you for the context! Yes, it's helpful. When looking into the arrow interface, I was under the impression that XGBoost should directly consume the arrow stream or the arrow C arrays. (I was hoping that something could help streamline the existing code and improve the performance). But now it's clear that I should continue to use numpy as the middle layer. It's still quite helpful, not meant to complain.

Narwhals is just Python but at some level you need a "C dependency" to pass ABI-stable C data, right?
If you want to use Arrow data for interop, then you need to trust the Arrow project's guarantee that it is actually ABI stable.
I would tend to argue that you should use a helper library to receive the Arrow data rather than trying to manage that yourself. Consider pyarrow, nanoarrow, or arro3.
Arrow and numpy do not map 1:1 to each other. Arrow includes lots of structured types and includes a nullability bitmask that Numpy cannot directly use.


fix(hero): change link of warpcast channel

minor fix on the warpcast channel link
Uploading link_warpcast.mov…

LGTM 👍👍👍👍👍👍


Fix uploads of large crates to S3 breaking the client

Currently, we reuse the client for all files that are uploaded per call
to the relevant code. Unfortunately, S3 will prevent connections from
being long-lived (it's unknown what the exact timeout is, but we hit it
relatively rarely). This code attempts to retry S3 uploads up to 3 times
while replacing the client each time.
r? @QuietMisdreavus

I ran update queue set attempt = 100 where name = 'alt-stm32f30x-hal'; on the DB to temporarily stop building that crate, as we had been attempting to do so for the last 7-10 hours I believe and failing on the upload each time. We'll want to undo that with update queue set attempt = 0 where name = 'alt-stm32f30x-hal'; after deploying this.


Change time or date from input fields in custom popup

Latest

Test Environment
Google Chrome
Current Behavior

I made a custom popup with custom date & time fields. When I change the date or time (see example image), I would like to see the blue block (14:00 - 14:30) change to the values from the input fields (15:00 - 15:30) and move to the according slot in the calendar.  How can I change these values from the input fields?

// Write example code

Expected Behavior

@thomasdevries
I haven't thought about that actually. It would be great if there's a way to modify the range of selection(we call it grid selection) with a public method.
But I'm afraid to say that you can't do it at this moment.

@thomasdevries
In the latest version, 2.1.3, I'm trying to implement a custom popup, but in the documentation I didn't find an explanation on how to use the "events" - I opened an issue here -.
Could you please share the name of the available events?
Thank you

@MarGraz
You can find the docs start reading from README.md.
Here's a documentation about instance events.

@MarGraz
You can find the docs start reading from README.md.
Here's a documentation about instance events.

Thank you for your reply, I will use the documentation from GitHub, because I was reading the documentation available here, but no "events" chapter was present. Thank you

@MarGraz Hi, would you please share how you created the customized popup? I'm struggling on that

@jowpurcinelli yes, it's not difficult.
In the html page where you have installed the calendar, in the script section where you have initialized the calendar, you need to intercept the calendar events in this way:
<script type="text/javascript">

const Calendar = tui.Calendar;
       // --- Get the calendar html element
       const container = document.getElementById('tui-calendar');
       const options = {
           defaultView: 'week',
           usageStatistics: false,
           calendars: [
               {
                   id: 'cal1',
                   name: 'Personal',
                   backgroundColor: '#03bd9e',
               },
               {
                   id: 'cal2',
                   name: 'Work',
                   backgroundColor: '#00a9ff',
               },
           ]
       };

       const calendar = new Calendar(container, options);

       // --- Down here the event handlers https://github.com/nhn/tui.calendar/blob/main/docs/en/apis/calendar.md#instance-events

       calendar.on({
           'selectDateTime': function (e) {
               console.log('selectDateTime when click on the calendar ', e);

               // ---> Here you can call the function where you can trigger your custom modal
               showMyModal();
           },
           'beforeCreateEvent': function (e) {
               console.log('beforeCreateSchedule', e);
               // open a creation popup
           },
           'beforeUpdateSchedule': function (e) {
               console.log('beforeUpdateSchedule', e);
               e.schedule.start = e.start;
               e.schedule.end = e.end;
               cal.updateSchedule(e.schedule.id, e.schedule.calendarId, e.schedule);
           },
           'beforeDeleteSchedule': function (e) {
               console.log('beforeDeleteSchedule', e);
               cal.deleteSchedule(e.schedule.id, e.schedule.calendarId);
           }
       });

       // --- Here a function example to trigger your bootstrap custom modal

       function showMyModal() {

           let modal = new bootstrap.Modal(document.getElementById('my-hidden-modal'), {
               keyboard: false
           });

           modal.show();
       }

</script>

That's it. I hope this can help you and other people.

@MarGraz You`re the best man, Thanks a lot for the knowledge sharing!
Grazie

@jowpurcinelli no problem 😊 sharing is caring. Prego 😋


cannot compile typescript examples

steps to reproduce:

git clone https://github.com/staltz/cycle-onionify.git
npm i
npm run lib
cd examples/lenses/
npm start

node 8.1.4
npm 6.4.1
alex@alexs-mbp : ~/dev/learn/cyclejs
[0] % git clone https://github.com/staltz/cycle-onionify.git
Cloning into 'cycle-onionify'...
[...]

alex@alexs-mbp : ~/dev/learn/cyclejs
[0] % cd cycle-onionify

alex@alexs-mbp ‹ master › : ~/dev/learn/cyclejs/cycle-onionify
[0] % npm i

><EMAIL_ADDRESS>install /Users/alex/dev/learn/cyclejs/cycle-onionify/node_modules/fsevents
> node install

[fsevents] Success: "/Users/alex/dev/learn/cyclejs/cycle-onionify/node_modules/fsevents/lib/binding/Release/node-v57-darwin-x64/fse.node" already installed
Pass --update-binary to reinstall or --build-from-source to recompile
npm notice created a lockfile as package-lock.json. You should commit this file.
added 580 packages from 203 contributors and audited 2610 packages in 20.678s
found 0 vulnerabilities

alex@alexs-mbp ‹ master ● › : ~/dev/learn/cyclejs/cycle-onionify
[0] % npm run lib

><EMAIL_ADDRESS>prelib /Users/alex/dev/learn/cyclejs/cycle-onionify
> mkdir -p lib

><EMAIL_ADDRESS>lib /Users/alex/dev/learn/cyclejs/cycle-onionify
> tsc

alex@alexs-mbp ‹ master ● › : ~/dev/learn/cyclejs/cycle-onionify
[0] % cd examples/lenses/

alex@alexs-mbp ‹ master ● › : ~/dev/learn/cyclejs/cycle-onionify/examples/lenses
[0] % l
total 24
-rw-r--r--  1 alex  staff  366 Oct  6 12:17 index.html
-rw-r--r--  1 alex  staff  695 Oct  6 12:17 package.json
drwxr-xr-x  6 alex  staff  204 Oct  6 12:17 src
-rw-r--r--  1 alex  staff  385 Oct  6 12:17 tsconfig.json

alex@alexs-mbp ‹ master ● › : ~/dev/learn/cyclejs/cycle-onionify/examples/lenses
[0] % npm start

><EMAIL_ADDRESS>start /Users/alex/dev/learn/cyclejs/cycle-onionify/examples/lenses
> npm install && npm run browserify && echo 'OPEN index.html IN YOUR BROWSER'

npm notice created a lockfile as package-lock.json. You should commit this file.
added 160 packages from 194 contributors and audited 1040 packages in 15.377s
found 0 vulnerabilities

><EMAIL_ADDRESS>prebrowserify /Users/alex/dev/learn/cyclejs/cycle-onionify/examples/lenses
> mkdirp dist && tsc

src/Edit.ts(42,3): error TS2322: Type '{ DOM: MemoryStream<VNode>; onion: Stream<Reducer>; }' is not assignable to type 'Sinks'.
  Types of property 'DOM' are incompatible.
    Type 'MemoryStream<VNode>' is not assignable to type 'Stream<VNode>'.
      Property '_ils' is protected but type 'Stream<T>' is not a class derived from 'Stream<T>'.
src/Item.ts(38,3): error TS2322: Type '{ DOM: MemoryStream<VNode>; onion: Stream<(prevState: State) => State>; }' is not assignable to type 'Sinks'.
  Types of property 'DOM' are incompatible.
    Type 'MemoryStream<VNode>' is not assignable to type 'Stream<VNode>'.
src/main.ts(7,23): error TS2345: Argument of type '(sources: Sources) => Sinks' is not assignable to parameter of type 'MainFn<Sources, OSi<{}>>'.
  Type 'Sinks' is not assignable to type 'OSi<{}>'.
    Types of property 'onion' are incompatible.
      Type 'Stream<Reducer>' is not assignable to type 'Stream<Reducer<{}>>'.
        Property '_ils' is protected but type 'Stream<T>' is not a class derived from 'Stream<T>'.

npm ERR! code ELIFECYCLE
[...]

Possibly related? https://github.com/cyclejs/cyclejs/tree/master/examples/intermediate/bmi-typescript works as is, but attempting to upgrade TypeScript to "2.5" or higher in package.json produces the same error.


There's no kubernetes version available for chosing, when I create custom cluster

Rancher Server Setup

Rancher version:v2.4.33
Installation option (Docker install/Helm Chart):
I built rancher image with github source code, then load and run with docker
Proxy/Cert Details: none

Information about the Cluster

Kubernetes version: Kubernetes 1.18.5 (from github)
Cluster Type (Local/Downstream): local

Describe the bug
There's no kubernetes version available for chosing, when I create custom cluster
To Reproduce

Result
no kubernetes version available for chosing,
Expected Result
should list local k8s version here, or at least give me a way to add local k8s version somewhere in source code
Screenshots

Additional context
It should be competible with official k8s release

v2.4.33 is a non existent version, and as you are building from source, I guess a branch or commit is better indication. How did you build it? And populating the dropdown can take a bit longer, how long did you wait before creating the cluster?

Presumably that's the UI tag, which was different than the Rancher one back then.

Right, V2.4.33 is User interface version. the Backend version is V2.4.7
I wait long enough, actually I didn't close the window for hours.
I wonder if it relates with rke/rke-tools. Is there anyway to debug it?

You build from source from tag v2.4.7? How did you build it? What is the build/Docker image tag/commit that is used in the build?

Just followd https://github.com/rancher/rancher#readme
build with scripts/build scripts/package, then I have a rancher image.
run with sudo docker run -d --restart=unless-stopped -p 80:80 -p 443:443 --privileged rancher/rancher
while doing rke up --config cluster.yaml        it reports this error:
Host [<IP_ADDRESS>] is not able to connect to the following ports: [<IP_ADDRESS>:2379]. Please check network policies and firewall rules]
Don't know if this is the cause.

That process should work, it is unclear to me why rke up is involved. Rancher runs in the created Docker container and you can use it to create clusters via the UI/API, but RKE is a CLI tool to create a Kubernetes cluster (and can then be used to run Rancher on top as a Deployment for HA) which is not involved when you manually built Rancher and try to run it as Docker container.

we are trying to use "rke up" to debug. (I guess web UI calls rke command).
If web UI doesn't call rke, then how can we debug it?

Any idea what does "Host [<IP_ADDRESS>] is not able to connect to the following ports: [<IP_ADDRESS>:2379]. Please check network policies and firewall rules]" mean?
Anyway to debug it?

Thats not really the same mechanism, RKE used embedded data or an external URL (specified by RANCHER_METADATA_URL) on run. Even when the container has no internet connection, it should still be able to use the embedded data.json.
The error you see on RKE is a different issue, but is quite clear. It can't connect so a (host) firewall is blocking connection(s).


Properly subtract negative dex from AC

Addresses #733
The existing code had a "bestAttribute" variable to compare to, but that bestAttribute started out at 0, so negative dex modifiers were always ignored.
I'm not sure what added functionality came from comparing "best attributes," but this push works with all armors and things like bracers of defense.

We'll have to let Muttley weigh in on the "bestAttribute" value, it doesn't make sense to me either.

We'll have to let Muttley weigh in on the "bestAttribute" value, it doesn't make sense to me either.

Is there a class that has an option to use a stat other than dex for AC? In that case it might make sense, but off-hand I don't know if that occurs in any first-party classes.

The thinking behind this was to use the best attribute armor in the situation where the player has more than one piece of armor equipped, which is still probably the best way of handling those situations (once the initial setting it to zero issue is addressed).
This pull request is not a good fix however, as it would add the attribute bonus to the AC multiplies times (once for every piece of armor equipped).

Implemented alternate fix


Add ODBC support

Greetings,
In many context, specially those with a lot of information to store such as user information, progress, logins & scoreboards, databases are fundamental to those applications/games.
Unfortunately, there's no support for larger scaled databases in Godot and the current format is extremely limited.
This is why I suggest the implementation of ODBC with, as suggestion, nanodbc.
It is MIT licensed, light and cross-platform.
Why do I suggested ODBC over any other specific method/protocol?
Simply because it's supported by most of database softwares (e.g.: Microsoft SQL, MySQL, PostgreSQL, SQLite, etc.) with a generic syntax and it's platform independent.
Let me know your thoughts about it.
Thanks! :smile:

I think this is better as a separate module.

I can understand this point of view.
The request was more to have a ready to run server/client with a scalable data management service without the need to change the queries. (SQLite for local or light management and scalable to MySQL for larger data manipulation)
I'll let other people give their opinion about this.
I'm just afraid that by doing it as a separate module, it won't be done at all, which seems to happen too frequently... :confused:

The only reason why we are likely to want all things in core is because Godot currently lacks easy plug-and-play of native functionality. If module development evolves further than recompiling the whole engine binary (which is seriously considered here https://github.com/godotengine/godot/issues/3936#issuecomment-224849590), that could be no problem at all. I prefer a clean core than a bloated core :)

Understandable!
Should I migrate this issue to the godotengine/godot-modules repository?
Maybe we should also put your module list in this place?

I'm all for it, having database support out of the box wouldn't hurt, if it's lightweight, cross-platform and can connect to all databases. I see godot-modules being there only for stuff that can't ship alongside godot because of license restrictions or if they do not work properly (in case of theora)

@TheoXD, that's indeed why I suggested it directly into Godot, just like other libraries such as Node regex and others tiny "drivers".

if it's really lightweight, I wouldn't mind it to be integrated into the core.
else, it could become a module that i might need.

This can be added as a module even if it's in Godot's core (such as GDScript, GridMap an IK).

Oh, i think that I used a wrong word. What I mean by "module" is more like "optional plugin".
Personally, I'd rather not to have to compile godot to add or remove modules.
I'd prefer an out of the box slim godot with optional .dll or .so.

Although some would prefer it in an all-in-one executable (like I personally do).
Still, I had migrated this issue to the godotengine/godot-modules repository.
(https://github.com/godotengine/godot-modules/issues/4)
Thanks for the interest!

I'm sorry to ask on an old closed issue but the godot-modules repository seems to be gone these days. What ever happened with this feature request over there?

I'm sorry to ask on an old closed issue but the godot-modules repository seems to be gone these days. What ever happened with this feature request over there?

Feature proposals are now tracked on the Godot proposals repository.

Greetings to anyone comming here:
We've reopened this discussion in the following thread: https://github.com/godotengine/godot-proposals/discussions/4609


[v1.18]: Add CaaSP kube-controller-manager container image

It will be squashed in https://github.com/SUSE/caasp-container-images/pull/66


about retrieve sequence length

I followed your suggestion to modify retriever to adapt to Qwen2.5
When I run function "search". The return sequence seems too short. Though I change the parameter
"long", It doesn't work.

Hi,
I wonder what number you set for choices. If choices is set to small, the returned draft sequences would also be cut.


Can't find the actor loaded in Gedis client

Can't find the registered actor in the actors list although it is loaded and I can execute the methods
t = j.servers.gedis.get("test")
t.start()
gedis = j.clients.gedis.get("local")
gedis.register_actor("greeter", "/home/rafy/sandbox/code/github/threefoldtech/js-ng/jumpscale/servers/gedis/example_actor.py")
gedis.execute("greeter","add_two_ints",2,3)
but if you checked the list

can you invoke
gedis.reload() after registering the new actor? and see if it fixes it for you.

It worked and after discussing this with @ahelsayd, we have concluded that want the client to be manually reloaded after adding a new actor.


JAWS - datepicker pronounced as "Edit type text"

@limonte commented on Fri May 04 2018
Expected: "Birthday edit date. 'selcted-value-if-any'. To set the value use the arrows keys or type the value"
** Actual:** "Edit type text"
JAWS latest 2018.1802.78

To have AT announce the input as "date" instead of "text" one needs to use <input type="date">. The problem then becomes providing a consistent experience across the different browsers, which is more or less impossible at this point.
Chrome, Firefox, Edge and Opera all have custom interfaces for inputting dates.

Would it not be possible to use input type="date" but somehow prevent the UA's native datepicker from getting triggered?

It isn't really important that the type is date. More important is a clear labeland placeholderfor the field.
For example, even the official wai-aria practices have a simple type=text

Wai Aria 1.1 https://www.w3.org/TR/wai-aria-practices-1.1/examples/dialog-modal/datepicker-dialog.html
Wai Aria 1.2 https://www.w3.org/TR/wai-aria-practices-1.2/examples/dialog-modal/datepicker-dialog.html
Wai Aria MASTER https://w3c.github.io/aria-practices/examples/dialog-modal/datepicker-dialog.html


Housecleaning the repositories of deprecated files

I have been going through the repos, and there are a few things that should be cleaned up. Let's discuss the following files before deletion:

[x] Makefile (in Kitura and KituraNet)
[x] Makefile.client (in KituraNet)
[x] .travis.yml.backup
[x] karl-develop remote branch
[x] buildTests.sh
[x] runTests.sh

Please add any additional files you know about, as well.

@kweinmeister is it fine to remove this remote branch?

5th step of Usage in README.md gives following command:
cp Packages/Kitura-net-0.2.0/Makefile-client Makefile

@eimantas look at the README in the develop branch

@dfirsht the develop branch is for later swift snapshot. I'm trying to use master with 02/08 snapshot.
Please refer to #213 for info on which snapshot to use on which branch.

@eimantas Yes that is true for the master branch. The version of Kitura-net downloaded by master (0.2) still has the Makefile-client file and should be used as the master README specifies. This issue is for removing it in future versions.

All files mentioned were removed from develop branches.


Cannot use span tag in "code" tag any more

Describe the issue/behavior that seems buggy
Up to ver.10.3.7 I can add some customization tags between  and . But this feature seems to be removed in version 11.
Sample Code or Instructions to Reproduce

> install.packages('IRkernel')

the related script and style and activation are below.
<link href="//cdnjs.cloudflare.com/ajax/libs/highlight.js/11.5.0/styles/tomorrow-night-bright.min.css" rel="stylesheet" />

Expected behavior
The color of text install.packages('IRkernel') is orange
Additional context
Is this feature removed? or is there other method instead of just using hljs.hilightAll()

This change was intentional. #2889
This functionality could be added back via plugin if anyone wanted to maintain the code, but so far no one has stepped up to the plate to do so.

plaintext

If all you care about is plaintext then see the README for how to ask Highlight.js to ignore that block entirely, in which case the HTML you're using will "just work" since it's just simple HTML - there is no need for this to go thru Highlight.js for plaintext.


feat(stdlib,exts): implement Tr

Summary
This implements the stdlib Tr function (link to docs). Closes #496

Looks great! We may be missing a few bits of the TS file spec (and we don't seem to support XLIFF files yet) but we can handle those in a separate PR as needed.

Yep, that was my thought as well 👍

Hi, I've tried to call huluTr without mocking but I'm receiving the translations source like: "TITLE_YOU_ARE_ELIGIBLE_FOR_A_DISCOUNT" but not the translated text "You’re eligible for a discount", error is not present anymore, but looks like Tr not working properly(

Hey @nadiapadalka — please don't post references to confidential materials here, including translations.  I'm redacting parts of your comment.

Hi @lkipke , I've tried to call Tr without mocking but I'm receiving the translations source like: "HELLO_WORLD" but not the translated text "Hello, world!", error is not present anymore, but looks like Tr not working properly(

@nadiapadalka That may be solved by #587 , which was released in v0.39.0.  Please try again with that version of the interpreter.  If you still see that error, please file a new issue with the simplest file(s) you can find that reproduce the issue 😃

Hey @nadiapadalka — please don't post references to confidential materials here, including translations. I'm redacting parts of your comment.

@sjbarag , sure, sorry

Hi @lkipke , I've tried to call Tr without mocking but I'm receiving the translations source like: "HELLO_WORLD" but not the translated text "Hello, world!", error is not present anymore, but looks like Tr not working properly(

@nadiapadalka That may be solved by #587 , which was released in v0.39.0. Please try again with that version of the interpreter. If you still see that error, please file a new issue with the simplest file(s) you can find that reproduce the issue 😃

thanks, @sjbarag ok, I will try


!rss not working in channel

I can query my bot with !rss and get a response with all available feeds. But if I do the same in the channel where the bot is posting its feeds, I wont get a response for !rss but for !.
Any ideas?

telnet to your bot. it may be a tcl error.

Having the same issue. Amongst others.
When i open a chat with the bot and do !rss i see that !slashdot is available
But when i do !slashdot, there is nothing. I also cannot find the database file anywhere :O

Tuumke, you need to check the settings file and see where the database is set to. Try setting an absolute path, so, instead of ./scripts/feeds/slashdot.db or whatever, try /home/NAME/eggdrop/feeds/slashdot.db or whatever absolute path you see fit, so long as it is writable, ie chmod 777 /home/NAME/eggdrop -R.
Good luck

i get RSS Warning: couldn't open "rss.db". : no such file or directory.

Solution: The script creates automaticly the files after a time.


Use G2DBException from G2Database.py

The G2DBException exception is moving from the Senzing Python SDK to senzing/g2database.   governor_postgres_xid.py needs to reference the exception from the new location.
References

https://github.com/Senzing/g2report/issues/7
https://github.com/Senzing/g2database/issues/18
https://github.com/Senzing/g2-sdk-python/issues/108

Pull requests:

https://github.com/Senzing/g2-python/pull/122


websocket-polyfill headache

TLDR: websocket-polyfill is junk and abandoned, can we switch nostr-tools to something better like isomorphic-ws?
I'm trying to use nostr-tools to add nostr DMs as a notification provider in Uptime Kuma, an open-source uptime monitoring tool. The PR was merged but then reverted because dependencies of websocket-polyfill don't offer binaries for arm.
websocket-polyfill depends on websocket (WebSocket-Node), which depends on bufferutil and utf-8-validate. bufferutil and utf-8-validate are subprojects of ws, and ws says they are optional dependencies for ws. websocket-polyfill uses websocket instead of ws.
bufferutil and utf-8-validate stopped providing arm binaries when something broke with cross-compiling. Since they are not optional dependencies for websocket, and arm binaries aren't available, they have to be built on arm.
Uptime Kuma insists on supporting arm v7 and not requiring users to build anything themselves, so binaries need to be available for all dependencies on all supported platforms.
websocket-polyfill hasn't been touched in 4 years and has almost no issues or PRs, open or closed. Cloning it to build locally doesn't work: it's missing a dev dependency for typescript. After installing that, tsc complains about type errors so it doesn't even build for me.
isomorphic-ws and ws are way more widely used then websocket-polyfill and websocket.
I replaced websocket-polyfill in nostr-tools with isomorphic-ws. It passes the nostr-tools tests and my Uptime Kuma PR works too. The only change to the code was one spot in relay.ts where I had to cast data to a string: incomingMessageQueue.enqueue(e.data.toString('utf8'))
I can try to get ws to start building arm binaries for bufferutil and utf-8-validate again, since they seem to be working now, but swapping out an old and busted websocket-polyfill for something getting widespread use and active development seems like a better fix.

What do you think, @alexgleason?

Here are some examples of global Node.js polyfills:

https://github.com/samchon/websocket-polyfill/blob/master/src/index.ts
https://github.com/tgorka/node-window-polyfill/blob/master/register.js

Seems like you should be able to install ws, and then at some point early in your entrypoint of your application do this:
import ws from 'ws';

global.WebSocket = ws;

Boom, problem solved?
I wouldn't be against switching the devDependency to isomorphic-ws in this repo for tests, but I don't see the point in polyfilling it in the library itself, for the reasons I mentioned here: https://github.com/nbd-wtf/nostr-tools/pull/258#issuecomment-1646874210
When you choose Node.js in the modern world, you have chosen to have to think about polyfills, so in my view the polyfill should be added on the Node.js side.

Yes indeed, problem solved. This has really soured me on ever contributing to anything using node.


License Configuration Check

Is this pull request associated with an issue(s)?
Closes #137
Description
Adds a check to the license_and_format job in the common PR workflow that will fail if the config_file is set to a file name and that file doesn't exist.

🚀 [bumpr] Bumped! New version:v0.3.45 Changes:v0.3.44...v0.3.45


feat: stepper: adds stepper component

SUMMARY:
Adds Stepper component to Octuple.
Updates Carousel overflow css values to horizontal only.
https://user-images.githubusercontent.com/99700808/208216307-ab3485ef-b43b-4e66-89fa-9f1783b56ca8.mp4
JIRA TASK (Eightfold Employees Only):
ENG-2827
CHANGE TYPE:

[ ] Bugfix Pull Request
[X] Feature Pull Request

TEST COVERAGE:

[ ] Tests for this change already exist
[X] I have added unittests for this change

TEST PLAN:
Pull the PR branch and run yarn and yarn storybook. Verify the Stepper and Carousel stories behave as expected.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@3554159). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #471   +/-   ##
=======================================
  Coverage        ?   84.68%
=======================================
  Files           ?      784
  Lines           ?    16288
  Branches        ?     5620
=======================================
  Hits            ?    13794
  Misses          ?     2426
  Partials        ?       68

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


GRG Widget Configuration Page does not load

GRG Widget
Version of widget 1.0
Bug
Repo Steps or Enhancement details
I have attempted to use the GRG widget the hosted version of WebApplication Builder on our Portal. I am able to add the widget to the application; however, I am not able to load the configuration page:

@kgonzago

@topowright I am unable to reproduce it with the latest build of MTA. Can you verify if issue still persists when you get a chance?

verifying and closing.


Examples not working

hi the examples are using rawgit.com which is no longer serving the files hence the samples are broken.
Kindly advise if this plug in still works

Hello,
I haven't worked on this for years, it is not maintained anymore, and most probabmy doesn't work with recent versions of leaflet.
Please seek other solutions. There are other "hacky" projects, but if you really want rotation as a feature, please try using MapLibre or OpenLayers
Fabien


Improved tools for 3D annotation

[x] Add, remove, edit labels in 3D
[ ] Slice interpolation (nD) (plugins?) (see jni/zarpaint#32 and https://github.com/brisvag/napari-label-interpolator)
[ ] 3D Labels editing performance for large volumes
[ ] Add labels, points, or polygons on a clipping or slicing plane
[ ] Add and edit 3D bounding boxes
[ ] Manipulate points and shapes in 3D
[ ] Add points or labels based on intensity of an underlying image or position of polygons or surfaces in other layers

@GenevieveBuckley I incorporated your comments in the draft into two extra items above. I actually strongly disagree that slice interpolation should be built-in rather than in plugins: there are umpteen methods for slice interpolation and it's not particularly clear which method to implement as a built-in. However, because our slicing model is so bad, right now it's pretty clunky to do slice interpolation in a plugin, so I definitely understand the desire to fold it into main. But I think instead that we should focus on improving our slice models (#5949) and expand  our plugin infra/contribution types (#5874) until slice interpolation in both labels and shapes layers is really nice and easy to implement in plugins.
At any rate, we can discuss, I'm definitely not feeling dogmatic about it. But I would very much like to tighten the scope of napari core so we can get some of these long-standing issues sorted, before adding (potentially) complicated algorithms to core.
Regarding performance, have you tried 3D editing recently? Contributions like #5723 / #5732 might have made a significant dent in the user experience. And of course there's #3308 in the pipeline... I hope I can finish that up soon... 😩

Regarding performance, have you tried 3D editing recently? Contributions like #5723 / #5732 might have made a significant dent in the user experience. And of course there's #3308 in the pipeline... I hope I can finish that up soon... 😩

I've been trying to avoid 3D label editing, but in the last fortnight I was editing labels for a large tiled 2D image. It was very, very slow. Almost unusable, given the lag time between moving the paint/erase brush and actually seeing the response to the pixels on screen. I suspect that the plugin might be able to try something more efficient than working with the default new label layer, which might help as well.
EDIT: I've just looked at what napari version I was using at the time, and it's 0.4.17. Looks like there hasn't been a new release for the last seven months, so I think it's safe to say neither of the PRs you linked were in effect. https://github.com/napari/napari/pull/5732 might speed things up a bit, I'll have to try it (but https://github.com/napari/napari/pull/5723 seems irrelevant to this discussion).

Looks like there hasn't been a new release for the last seven months, so I think it's safe to say neither of the PRs you linked were in effect.

Correct. Let us know if you have any issues running from main. Also Grzegorz is gearing up to release 0.4.18 which includes those PRs. Should be out in 1-2 weeks. (Has to happen cos I want to use it at SciPy 😂)

I have a plugin which implements 3D bounding boxes as a custom layer: napari-bbox. There are lots of hacky solutions involved, but the basics are there (2D-3D display, displaying bounding boxes only on slices relevant, editing/creating in 2D etc.). I would be glad to contribute in making it a built-in layer, however, I have only a limited time to work on it. But if someone could join, we can make it work 🙂.
The code by the way is an edited version of the shapes layer (from a previous version of napari, 0.4.15 if I'm correct).

Thanks for chiming in @bauerdavid! What do you think about incorporating the boxes directly into the Shapes layer? They seem to be fundamentally related...?

@bauerdavid I thnk we already talked about this elsewhere before, but in my opinion this should be an overlay. I know that (differently to the already implemented layer bounding boxes) your plugin also provides the ability to give arbitrary bounding boxes; the main question is: do we consider this as "data" per se, or does it only make sense as a "thing that highlights specific regions in another layer"? If it's the second, overlays are the way to go IMO. Depending on the use case, it might actually be time to hook up and use the interaction box overlay.
Alternatively (if the bounding boxes don't need specific interactivity or visualisation tricks), they could also just be helper functions on the shapes layer that can take "something" (another layer, a selection of points, etc) and generate a n-D bounding box around it.

Hey @jni,
In my opinion, there are some reasons which make it necessary to separate shapes from bounding boxes:

Shapes are "fundamentally 2D". If a Shapes layer is 3D, it still means that you are placing 2D objects (which lie on planes) in 3D.
(This is connected to the previous point). Actually you can modify the points of shapes to not lie on a plane, but still in a shape every anchor point is connected with (at most) 2 other points, while in a 3D bounding box every point is connected to 3 other (As we increase the number of dimensions, the number of neighbor points increases, but maybe annotating 4+dimensional images, excluding time and channels, might not be a thing 😄.)
Rendering 3D bounding boxes needs extra care (e.g. in 2D display bounding boxes only if the current slice is inside the span of the bounding box, etc.).
For creating 2D bounding boxes, you could use the Shapes layer. However, in that case editing each point separately (thus turning a rectangle into a general shape) is unnecessary and allows some user error to occur. This is also true rotating bounding boxes (although I can imagine, that in some cases this might be needed).
I think the above points make bounding boxes incompatible with the Shapes layer. What do you think?

Hey @brisvag,
I agree @jni, there are some cases when you don't have any underlying data (like labels or shapes), so I do think that bounding boxes can be considered data in themselves. However, I also like the idea of having a bounding box displayed for some other data ,e.g. highlight the currently selected label in a Labels layer. Actually I use it that way as well, but that would be really nice if it was a property for layers.

I totally forgot that our shapes don't allow for 3D objects... well, ignore that part of my comment xD

highlight the currently selected label in a Labels layer

Yeah this is where overlays would be awesome I think. But I agree that many other cases fall in the "data" world. Is there a reason why we call them "bounding boxes" (which in my mind sounds like a property of some data) versus for instance ROIs, which sounds more like what you're talking about? Or am I mixing up concepts?

I agree, "ROI" might be a better phrase for this concept. Strangely enough, when I saw discussions for 3D ROI's, I usually saw (and used) the term "bounding box"... 🤔

Shapes are "fundamentally 2D". If a Shapes layer is 3D, it still means that you are placing 2D objects (which lie on planes) in 3D.

Actually you can modify the points of shapes to not lie on a plane, but still in a shape every anchor point is connected with (at most) 2 other points, while in a 3D bounding box every point is connected to 3 others

that's true now but not necessarily true in the future. They are 2D because 2D was easier to implement, not because we thought they should be 2D forever.

Rendering 3D bounding boxes needs extra care (e.g. in 2D display bounding boxes only if the current slice is inside the span of the bounding box, etc.).

Again, I think "fancy 3D shape" can define all of the attributes you want that "boring 2D shape" does not. It's just an accident of history. The question is, do we want to have one layer for each dimensionality of shape (in which case we should move "paths" out of Shapes into a Shapes1D layer???), or do we want to have a "vector shapes" layer that encompasses all the dimensions — and rendering options and editing tools appropriate to each shape?

However, in that case editing each point separately (thus turning a rectangle into a general shape) is unnecessary and allows some user error to occur

Even things like moving the vertex of a rectangle I think are supported by an accident of history, not because we thought it was particularly useful to turn rectangles into general polygons. I agree that it's annoying, it's bitten me a couple of times!
See above @bauerdavid, I don't actually think of your points as "fundamental limitations of the Shapes layer" but "accidents of history unfortunately on the Shapes layer", and I think adding 3D bounding boxes would help clean up the design choices of the Shapes layer.

See above @bauerdavid, I don't actually think of your points as "fundamental limitations of the Shapes layer" but "accidents of history unfortunately on the Shapes layer", and I think adding 3D bounding boxes would help clean up the design choices of the Shapes layer.

Yeah, you're right, the points I wrote are more like implementation issues. What you wrote made me rethink the question from a functionality point of view.
Bounding boxes (or ROI's) can only be rectangles or cuboids (or hypercuboids for higher dimensions, but let's not go there right now 😄). They are used to create boxes, which contain some objects. On the other hand, with shapes you can draw the boundaries of the said object precisely. (Duh... 😄)
Now, I think the following questions should be thinked through (from the least important to the most relevant):

a) Would users of napari want to draw 3D shapes manually?
b) What uses would we see for that in image processing?
IMO the Surface layer in napari can be considered the (true) 3D version of Shapes layer. Should these be merged?

Note At first sight the existence of the Surface layer might answer 1/b). I never used it, but if I'm correct, it's basically used for visualization, not for 3D editing or annotation. But correct me if I'm wrong.

It's important that 3D bounding boxes can be edited easily in 2D, even if we are not on the slice where the bounding box corners are. (Imagine that you want to resize the box to be the minimal bounding box of an object. You should be able to drag the sides of the box in the middle of it.) How would you generalize this for any 3D shape? How would you edit a general 3D shape in 2D? Or only boxes should be edited in 2D, anything else only in 3D?
If ROI's are part of the Shapes layer, should editing limitations be applied to bounding boxes (no object-wise rotation, no point-wise editing), or left as it is now (see rectangles)?
(Follow-up from 3. and 4.) Why should ROI's be part of the Shapes layer, if they need special care?

a) Would users of napari want to draw 3D shapes manually?
b) What uses would we see for that in image processing?

3D paths, for sure. Things like spheres/ellipses and cubes also likely. Not sure what those would actually be in terms of data, but if I could use them I would :P

IMO the Surface layer in napari can be considered the (true) 3D version of Shapes layer. Should these be merged?

Note At first sight the existence of the Surface layer might answer 1/b). I never used it, but if I'm correct, it's basically used for visualization, not for 3D editing or annotation. But correct me if I'm wrong.

I disagree; shapes are mathematical descriptions of objects (more "abstract", which allows for different kinds of analysis and uses). Surfaces are also a lot harder to generate and work with in terms of data. There's also several things that surfaces simply couldn't represent (such as paths).

It's important that 3D bounding boxes can be edited easily in 2D, even if we are not on the slice where the bounding box corners are. (Imagine that you want to resize the box to be the minimal bounding box of an object. You should be able to drag the sides of the box in the middle of it.) How would you generalize this for any 3D shape? How would you edit a general 3D shape in 2D? Or only boxes should be edited in 2D, anything else only in 3D?

Definitely agree! If you see how the TransformBox is implemented (set a layer's mode to transform that's exactly how it works. As for general 3D shapes, I don't think we can generalize like that. Something like a path, an ellips(oid), or a box will never overlap perfectly in terms of data and how they can be manipulated. Changing the radii of an ellipse makes sense, not for a path. I think we need to embrace the variability of this layer, rather than force a unified behaviour. If it gets too strange, we can always split it and create sublayers...

If ROI's are part of the Shapes layer, should editing limitations be applied to bounding boxes (no object-wise rotation, no point-wise editing), or left as it is now (see rectangles)?
(Follow-up from 3. and 4.) Why should ROI's be part of the Shapes layer, if they need special care?

If we think of them as "n-dimensional parallelepipeds", they are just another type of shape, and as I was mentioning above, each shape has its own limitations and behaviours already.

Okay, I think I start to understand the concept 😄. So basically there would be a layer, which can handle regular objects (spheres, ellipsoids, "n-dimensional parallelepipeds") both in 2D and 3D; and irregular curves, in which every "anchor point" (I don't know if this is a valid word here) has exactly two other points connected, except for open curves, where the two end points have a single connection. Both ellipsoids and parallelepipeds could be defined by their bounding boxes. I suppose there would be no irregular 3D object (by that I mean objects which have a volume, unlike 3D curves). Does this seem correct?

I disagree; shapes are mathematical descriptions of objects (more "abstract", which allows for different kinds of analysis and uses). Surfaces are also a lot harder to generate and work with in terms of data. There's also several things that surfaces simply couldn't represent (such as paths).

Yeah, this makes sense. My confusion came from the assumption that, for example an ellipsoid would be described by a point cloud in a 3D shapes layer. But I guess they can be defined similarly to the currently available ellipse in Shapes layer (by a bounding box).

I think we need to embrace the variability of this layer, rather than force a unified behavior. If it gets too strange, we can always split it and create sublayers...

I can imagine a Shapes layer with custom behavior for each kind of shape. However, I'm not sure if this is the best option. Again, I can be wrong, but maybe from the UX point of view, it would be clearer to separate different kinds of shapes into separate (sub)layers. Would a user want to annotate ellipsoids, boxes and free-hand curves in the same layer? As a plugin developer, I would be happier if I am sure that the users can only create the types of objects in a layer I want them to create (e.g. boxes). And also, usually if someone annotates ROI's, they want the boxes to have the same orientation as the image grid (no 42.1783° rotation). But of course, I can imagine a checkbox/API for the layer to disable rotation.
I think this is more of a "religious" problem, I can see either option - unified shapes layer vs. separate layer for each type -working, but I'm more for the latter option.


Setting placeholder / defaultValue?

What is the ideal way to prefill the form? I cannot get a placeholder to show nor set a default value, regardless of when in the lifecycle I try to add it (actually, I can set the content with this.refs.phoneInput.state.formattedNumber, but only after the user interacts with it). The idea is that the field should be already filled in with the previous form if they are coming back from an earlier save.

@tr0lyat You can use the value prop to set the initial value. It's not documented, but the functionality is clearly there in the source code. Have a look at the component's constructor function.
However, unlike a standard input component, react-phone-input seems to only acknowledge the prop at construction time. Afterwards, changes can only happen by interacting with the field (which sets state.formattedNumber internally). The value of the internal input is indeed controlled by internal state.
While default values are possible via the value prop, the fact that it is only checked at construction time makes the component impossible to use as a controlled component. This seems like the larger issue IMO. I understand that the internal input element is controlled, but it would make a lot more sense if the exported component could be used in a controlled fashion as well. I believe it would be more powerful, and easier to use for those already familiar with React! It would also be a step towards playing well with redux-form.

The default value does not update with setState

how to update default value using set state:
I am trying to update phone_work state
<ReactPhoneInput
{...phone_work}
value={ this.state.phone_work }
className="inputMaterial"
defaultCountry={'us'}
onChange={ (value) => this.setState({phone_work: value})} />

See issue #40. I am providing a fix against that issue, since I had missed this one had been opened.


[stable/node-local-dns] add .config.dnsServer to -localip only if config.setupIptables is true

Description

Return default configuration to be compatible  with iptables setup.
add dnsServer to -localip only if setupIptables is true
bind to dnsServer ip only if iptables setupIptables is true

Checklist

[v] Title of the PR starts with chart name (e.g. [stable/mychartname])
[v] I have read the contribution instructions, bumped chart version and regenerated the docs
[v] Github actions are passing

@max-rocket-internet please approve!

I think you should also write a better description of your change and why 🙂

I think you should also write a better description of your change and why 🙂

See my comments to your previous post

Description has been updated

JFYI: we are using specific configuration with cilium local-policy-redirect and don't iptables at all

OK cool but do you think changing the default behaviour of chart to suit Cilium for everyone is a good idea?

@max-rocket-internet
For now I have updated the minor version, because there have been many changes.
Is something else is required to be merged?

Thanks @STASiAN


415 Unsupportable Media Type

[Enter feedback here]
I get as far as the first test with postman, and I get that error.  I see no way to handle it

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 583ae3e7-5915-f22b-e54c-6c100cf2a7da
Version Independent ID: 95f2549e-29f9-e31a-b4d0-432b971643ff
Content: Tutorial: Create a web API with ASP.NET Core
Content Source: aspnetcore/tutorials/first-web-api.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

The tutorial works. I'm not sure what step you missed. You might try asking on StackOverflow,.


drupal directory not showing in windows explorer but it shown in bin/bash of php container

I have installed docker4drupal, currently its working and Drupal directories are showing in bin/bash command but drupal directories are not showing in windows explorer.

files are showing when I run command of bin/bash of PHP container.

confusion is that where are Drupal source path located and how to re-configure or move it to related path of and how to use it for git push.

See https://wodby.com/docs/stacks/drupal/local/#usage, you're using vanilla Drupal image when drupal sources are inside the image. If you want to make changes to your codebase and push them you should mount your own Drupal codebase.


Add a Workspaces doc

Changes
There's been a bit of feedback since workspaces were released that
having their documentation spread across tasks.md, taskruns.md,
pipelines.md, and pipelineruns.md made understanding the feature harder.
Having the information organized this way also makes maintenance more
difficult, particularly of those sections which are duplicated across
multiple files.
This PR adds a new doc, workspaces.md, that consolidates all of the
information about workspaces. This doc is then linked to from each of
the individual CRD docs mentioned above which are also updated to
include a very short description of the need for workspaces and a short
example YAML.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes docs (if user facing)
[x] Commit messages follow commit message best practices

Release Notes
Instructions on using workspaces has been consolidated into a single doc to make browsing the information easier.

thanks @sbwsg, couple of minor nits, and one example link is broken, otherwise
/lgtm

Thank you for writing this up, Scott! I will review this later today.
On Mon, Mar 16, 2020, 02:39 Priti Desai<EMAIL_ADDRESS>wrote:

@pritidesai commented on this pull request.
In docs/workspaces.md
https://github.com/tektoncd/pipeline/pull/2230#discussion_r392805612:

Using a Secret as a Workspace has the following caveats:

Secret volume sources are always mounted as read-only. Steps

cannot write content to them and may error out if a write is attempted.

The Secret you want to use as a Workspace must exist prior to

the TaskRun being submitted.

Secrets have a size limit of 1MB.

Kubernetes docs for secret volumes

+> If you need support for a VolumeSource not listed here
+> please open an issue or feel free to
+> contribute a PR.
+
+## Examples
+
+- TaskRun example
+- PipelineRun example
PipelineRuns example is named
../examples/v1beta1/pipelineruns/workspaces.yaml instead of
../examples/v1beta1/pipelineruns/workspace.yaml
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/tektoncd/pipeline/pull/2230#discussion_r392805612,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG3UR4X3WWEMX3O6SDPMMUDRHXCRRANCNFSM4LJAZD7A
.

/test pull-tekton-pipeline-build-tests

/test pull-tekton-pipeline-build-tests

thanks for updates @sbwsg
/lgtm


Outlining

added more scopes
renamed and restructured
fixed some bugs
added scope info to ranges
new collapse type for clauses

Huge great job, man! Thanks a lot.


Updated README

For the KOMOJU Card project we have been implementing the use of pages and while doing so we faced some challenges.
For example the use of Composition & Options API, the initial setup, among others.
This PR just updates the README file to try to make it easier if you have never used the gem.

@Resonious can you help us review this PR, please?


Meson build files for 1.85

Implements the new OpenGL loader. I can't webgpu and sdl_renderer, but added it anyway for other to try.
/cc @eli-schwartz

Thanks. We've migrated to https://github.com/mesonbuild/wrapdb/ now, and this repository is deprecated... the new layout will actually run CI and do various sanity checks via github actions. Can you resubmit the changes there?

Thanks. We've migrated to https://github.com/mesonbuild/wrapdb/ now, and this repository is deprecated... the new layout will actually run CI and do various sanity checks via github actions. Can you resubmit the changes there?

Done in mesonbuild/wrapdb#221.


Rework PELT and uclamp events

Closing as the project has moved to https://gitlab.arm.com/tooling/lisa/


Three JS and the possible use and inspiration of 3D in ETModel

I was sort of overlooking some meetings of other people within Quintel and saw (while walking for tea) that some (or it was just one) of them were presenting a 3D representation of a certain area with 3D windmills and houses.
I was just looking at ThreeJS which uses OpenGL to create interactive 3D objects and animations inside of the browser. I don't know where we might use this for, yet. But I hope this issue might spark the imagination by some of the Quintellers that were actually in that meeting (or weren't in that meeting for that matter).
Obviously ThreeJS is now mainly used in art, advertisement and games but it might also be useful to us. For example this Renault car is completely created with ThreeJs or this game with a fairly ok looking planet with a house. It would be cool if you could draw something more real life to visually convince a user.
Another example of using this library would be for 3D graphs (however useful those may be); an example here.
Or for fun just looking at the stars 🚀

I've created this issue purely as discussion for another tool we might use. Don't know if we will but it does look rather amazing (just my 2 cents).

Or for fun just looking at the stars 🚀

Cool. This reminds me of a long holiday I once took.

unassigning myself

Closing as this is not very actionable.


pewpew 5.6 beta5 preview 4 exits immediately

Describe the bug
Running the new pewpew v.0.5.6 beta 5 preview 4 exits immediately on a 2 minute test without running anything. A try script works fine.
Expected behavior
Test should run
Config file
vars:
  rampTime: 1m
  loadTime: 1m
  totalTime: 2m
  serviceUrlAgent: ${SERVICE_URL_AGENT}
load_pattern:
  - linear:
      from: 1%
      to: 100%
      over: ${rampTime}
  - linear:
      from: 100%
      to: 100%
      over: ${loadTime}
config:
  client:
    headers:
      TestTime: '${epoch("ms")}'
      Accept: application/json
      FS-User-Agent-Chain: Performance Test
      User-Agent: Performance Test
  general:
    bucket_size: 1m
    log_provider_stats: 1m
endpoints:
  - method: GET
    url: http://${serviceUrlAgent}/healthcheck
    peak_load: 30hpm

Command to run
# export SERVICE_URL_AGENT="<IP_ADDRESS>:8080"
# pewpew run -w -f json createtest.yaml

or

# pewpew run createtest.yaml

System info

Operating System: Ubuntu 18.04 and Windows 10
Pewpew version: pewpew 0.5.6-beta5-preview-4

Additional context
Output from run or run -f json
{"type":"start","msg":"Test will end around 10:42:20 26-Jun-2020 in approximately 2 minutes","binVersion":"0.5.6-beta5-preview-4"}

OR

Starting load test. Test will end around 10:42:59 26-Jun-2020 in approximately 2 minutes

Test Summary 10:40:00 to 10:41:00 26-Jun-2020
no data

Test Summary 10:40:59 to 10:42:59 26-Jun-2020
no data

Further reduced test case:
load_pattern:
  - linear:
      from: 1%
      to: 100%
      over: 1m
endpoints:
  - method: GET
    url: http://<IP_ADDRESS>:8080
    peak_load: 30hpm

It appears to be the from: 1% in the load pattern causing the issue. Removing that, or changing it to an explicit from: 0% does not manifest the bug. Alternatively, changing the over to over: 4m does not manifest the bug.


Create cronjob template

What should be the design of the cronjob template? Here is an example of what a cronjob could look like.
# Source: istio-mirroring/templates/k8s.yaml
apiVersion: batch/v1
kind: CronJob
metadata:
  name: RELEASE-NAME-1-job
spec:
  schedule: "*/1 * * * *"
  jobTemplate:
    spec:
      template:
        spec:
          containers:
          - name: iter8
            image: iter8-tools/iter8:0.9
            imagePullPolicy: Always
            command:
            - "/bin/sh"
            - "-c"
            - |
              iter8 k run --namespace default --group RELEASE-NAME --revision 1
          restartPolicy: Never
      backoffLimit: 0

Done.


"Succes"

Succes

😱Whoops...!!
I will fix typo quickly!! Thanks!!!

😱Whoops...!!
I will fix typo quickly!! Thanks!!!

@all-contributors please add @olesgedz  for bug


About aux loss

Hello, I noticed that the aux loss is used in the paper, where is the rmi loss used?
thanks for your work

If I remember correctly, we attach both losses to a single head. There isn't a separate auxiliary head used for aux loss, which is a departure from how it is typically done.
You can experiment though with multiple heads. Our purpose in removing the aux head was to simplify the architecture used in training to eventually make NAS less fussy


Transfer ownership of source.dot.net

The source.dot.net website infra is going to a new home!

Does it need a new service tree entry?
Does it need a new Azure Subscription?
Who will be available to check on it?

Release Note Category

[ ] Feature changes/additions
[ ] Bug fixes
[ ] Internal Infrastructure Improvements

Release Note Description

Privacy review submitted.

Data Residency Assessment submitted.

Ring Assignment request submitted

Submitted request to move repository assignment in Product Catalog out of .NET Core.

Onboarded service to ICM

The final bit I was waiting for has completed. The S360 dashboard is entirely green. I declare this to be complete.
Any follow-ups should be handled through the usual FR/dnceng support mechanism.


generalize blobstore (part 1)

In this PR:

defined interfaces in services: StatusService, GetService, PropsService and ListService
implemented these interfaces for Azure
used these implementations in AzureBlobstore

In part 2, further strip down AzureBlobstore:

get rid of special handling of paths ending in / (which were translated to list of resource names ending with "" but this is fixed now)
implement generic pathConverters and responseConverters in quasar.blobstore.azure (and use these as much as possible in AzureBlobstore instead of the specific implicits in AzureBlobstore)

@wemrysi unless you are already busy with this PR, feel free to skip reviewing it - I'll have the sequel of this up soon(ish)


"awk: cmd. line:1: Unexpected token" - issue with dokku/s3backup:0.9.1?

Hey,
I'm creating an issue here as I can't do it on https://github.com/dokku/docker-s3backup.
Issue
When using dokku-postgres 1.4.12, I can create DB backups fine.
However, after having updated to latest (1.6.0), I have an error awk: cmd. line:1: Unexpected token.
I actually have the exact same error when trying to do DB backup with dokku-mariadb 1.6.0, as well as when using directly latest dokku/s3backup — however, using the latest dokkupaas/s3backup works fine.

Do you mind jumping on our slack chat? I'd like to get the trace mode output but it may contain your personal keys, so probably not quite safe to output here.

Sure, will do tmw morning (CET).

Sounds good, and apologies for breaking your workflow, that was definitely not intended here :(

This was fixed as of 0.9.4.


Update yetus.yml from 14.0 to 14.1

Also upgraded a version of GH actions:
Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: actions/checkout, actions/upload-artifact, actions/checkout

@ruslan-zededa Excellent. I also propose to study the issue with these linters, maybe we can include them? They have been disabled due to the addition of Generics to Golang.
https://github.com/lf-edge/rol/blob/e1fde3c3529e55840b8b93e540044408a4442e0a/.golangci.yml#L5-L9

@ruslan-zededa Excellent. I also propose to study the issue with these linters, maybe we can include them? They have been disabled due to the addition of Generics to Golang.
https://github.com/lf-edge/rol/blob/e1fde3c3529e55840b8b93e540044408a4442e0a/.golangci.yml#L5-L9

Done


nixos/ollama: allow default environment variables to be overriden

Description of changes
I'd like to store the models at a different location but the custom environment variable OLLAMA_MODELS seems to be overwritten by the default environment, so I'm switching the positions of the two attribute sets. I hope this doesn't introduce other issues (especially if the other variables are overwritten instead?)

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.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

[ ] Fits CONTRIBUTING.md.

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

LGTM, @abysssol Looks good for you?

I would rather add nixos options to override HOME and OLLAMA_MODELS, and keep the config options the only way to set those values.
So configuration.nix would contain:
services.ollama = {
  enable = true;
  home = "/home/foo";
  models = "/path/to/ollama/models";
};

If there are no objections to this, I'll create the pull request implementing it.

Closing this in favor of  #302474


Custom radius for each corner

What does this change?
You may set a different radius for each corner
Issue: https://github.com/wasabeef/glide-transformations/issues/181
What is the value of this and can you measure success?
You can use CornerType.ALL to show a different radius for each corner
Screenshots

it seems it's competeley abandoned


请问怎么获得iOS 16 beta 4* ... iOS 16.1 beta 1

请问从哪里可以下载？
谢谢！

Hi @borischou , you can download the beta via https://developer.apple.com/download 🙂

Hi, @1998code, sorry but I meant the image for iOS simulator, not the device support.

@borischou oic.
The simulator is included within Xcode. Please find below:
https://developer.apple.com/xcode/resources/

Thanks, I've found what I need. Thank you for your time.