Support for screen-recording media type

Is your feature request related to a problem? Please describe.

Support for screen-recording media type.
Found that Photos also classified Videos screen recordings recorded on iPhone (and possibly Mac).
On the Database it shows as subtype of 103  on the database.

Describe the solution you'd like

Tried to make the code changes.. but I'm stuck on a few tests.

I've created branch screen-recording branch on my fork.
I'm missing something on info.py and  print_photo_info.py  with shallow True/False and as_dict for the new key .

It's also missing documentation update.
@RhetTbull: If you give me a few pointers I'll try to fix it prior to submitting a change request.

Describe alternatives you've considered
N/A
Additional context
Errors:
(...)
_________________________________________________________________________________ test_iphoto_info[photo_dict12]

iphotodb = osxphotos.iPhotoDB(dbfile='/Users/MSP/Documents/GitHub/osxphotos/tests/Test-iPhoto-9.6.1.photolibrary/Database/apdb/Library.apdb')
photo_dict = {'adjustments': {}, 'album_info': [{'folder_list': ['dmCBXs4sSXaZ8nEJV+AM%A', 'NtsvmxOMR6WM3nYJy5X3ow'], 'folder_names...er_names': [], 'parent': None, 'sort_order': 0, ...}], 'albums': ['AlbumInFolder', 'Last Import'], 'burst': False, ...}

    @pytest.mark.usefixtures("set_tz_pacific")
    @pytest.mark.parametrize("photo_dict", photo_info())
    def test_iphoto_info(iphotodb: iPhotoDB, photo_dict: dict[str, Any]):
        """Test iPhotoPhotoInfo properties"""

        # rather than test each property individually, just compare json output
        # to the test data
        # when called with shallow=False, the json output will contain the output
        # of iPhotoAlbumInfo, iPhotoPersonInfo, etc. so each class will be tested

        uuid = photo_dict["uuid"]
        photo = iphotodb.get_photo(uuid)
        for key, value in json.loads(photo.json(shallow=False)).items():
            if key != "fingerprint":
                # fingerprint not implemented on linux
>               assert value == photo_dict[key]
E               KeyError: 'screen_recording'

tests/test_iphoto.py:194: KeyError
==================================================================================== short test summary info
FAILED tests/test_iphoto.py::test_iphoto_info[photo_dict0] - KeyError: 'screen_recording'
FAILED tests/test_iphoto.py::test_iphoto_info[photo_dict1] - KeyError: 'screen_recording'
FAILED tests/test_iphoto.py::test_iphoto_info[photo_dict2] - KeyError: 'screen_recording'
FAILED tests/test_iphoto.py::test_iphoto_info[photo_dict3] - KeyError: 'screen_recording'
FAILED tests/test_iphoto.py::test_iphoto_info[photo_dict4] - KeyError: 'screen_recording'
FAILED tests/test_iphoto.py::test_iphoto_info[photo_dict5] - KeyError: 'screen_recording'
FAILED tests/test_iphoto.py::test_iphoto_info[photo_dict6] - KeyError: 'screen_recording'
FAILED tests/test_iphoto.py::test_iphoto_info[photo_dict7] - KeyError: 'screen_recording'
FAILED tests/test_iphoto.py::test_iphoto_info[photo_dict8] - KeyError: 'screen_recording'
FAILED tests/test_iphoto.py::test_iphoto_info[photo_dict9] - KeyError: 'screen_recording'
FAILED tests/test_iphoto.py::test_iphoto_info[photo_dict10] - KeyError: 'screen_recording'
FAILED tests/test_iphoto.py::test_iphoto_info[photo_dict11] - KeyError: 'screen_recording'
FAILED tests/test_iphoto.py::test_iphoto_info[photo_dict12] - KeyError: 'screen_recording'
============================================================== 13 failed, 2003 passed, 153 skipped, 4 xfailed in 286.63s (0:04:46) ===

@oPromessa I'm impressed with how thorough your branch is -- nice work! A couple pointers:
The "screen_shot" key should be added inasdict() for photo PhotoInfo and the iPhoto PhotoInfo and it must be added in the if not shallow: block. This prevents new keys from messing up the comparison in osxphotos export to the stored JSON data for a photo. Only keys in the shallow=True dictionary are compared when exporting.
Additionally, in the iPhoto test, you'll need to update the test data at tests/iphoto_test_data.json to add the new key so the tests works.

Yeah! Basically RTFM 😉 Test Data -- BTW I've edited it a bit.

I think I mostly got it. But have it but still question what to do in these code lines (now commented. 'cause if I uncomment, tests/test_cli.py fail 😢 on assert with  where 1 = <Result KeyError('screen_recording')>.exit_code
print_photo_info.py:L56
print_photo_info.py:L102
photoinfo.py:L2173

All tests pass now! YAY 💯
Ran build.sh... some warnings related with latex and pdf (guess I don't have the tools). stderr: build.txt
On docsrc/README.md is there a typo: cd docs should be cd docsrc ? Did not want to change it, in case I was wrong. Also build.sh generates the docs. PS: Did not install

Ran build.sh... some warnings related with latex and pdf (guess I don't have the tools)

The docs building needs work. Don't worry about this as I don't build the docs until I do the release. For individual PRs, just update the appropriate files but don't build the docs as they will get re-built as part of my release process.

On docsrc/README.md is there a typo: cd docs should be cd docsrc ?

Yes, you're right. I'll fix it.

I think I mostly got it. But have it but still question what to do in these code lines (now commented. 'cause if I uncomment, tests/test_cli.py fail 😢 on assert with  where 1 = <Result KeyError('screen_recording')>.exit_code

The test_cli.py is a monster....on my to do list to break this up into smaller chunks as it has become very unwieldy.
Basically, for the tests that are failing, you need to track down where they're getting the "expected" data from. For example, in test_query_uuid(), it's reading CLI_OUTPUT_QUERY_UUID which is defined elsewhere in the file. This is a JSON string that will be reconstituted and compared to the JSON output of the query command. This JSON string will need to be modified to contain the screen_recording key.
There may be other places that need to be modified.

Had to set property screen-recording to None for <= _PHOTOS_4_VERSION).

Can this be closed? I think your PR already addressed this issue, right?


Make TransportationComlex a space

It seems that TransportationComplex is the last remaining top-level feature type that "is" not a space (by derivation) but that "has" spaces (by aggregation, namely TrafficSpace, AuxiliaryTrafficSapce and TransportationSpace).
For me it would be much more consistent with the other modules if TransportationComplex would be modelled as space. Then the thematic surfaces TrafficArea and AuxiliaryTrafficArea could be directly related to it. ClearanceSpace could  also be linked to it (or just be mapped on a clearanceHeight property?).
I do not see the additional intention of a TransportationSpace compared to TrafficSpace.

Will be discussed together with issue #64.

Has been solved by issue #64.


navigateTo and useRouter path change with different layouts doesn't load dom elements in client side mode (no ssr)

Environment

Operating System: Windows_NT
Node Version:     v16.14.1
Nuxt Version:     3.0.0-rc.6
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      css, build, vite, ssr, runtimeConfig
Runtime Modules:  -
Build Modules:    -

Reproduction
https://github.com/cpaczek/nuxt-nav-bug
Describe the bug
When SSR is set to false and you are using useRouter or navigateTo and the layout is changing, for example when the layout changes from foolayout to default none of the content loads on the second page. There is a vue warn in console.

If the layout doesn't change this issue does not occur, also if you are in SSR mode the issue does not occur.
If you refresh the page the content does load so the issue is to do with programmatic navigation.
Additional context
No response
Logs
No response

I'm experiencing this too, every page/layout has a single root node, but parts of the previous layout are coming across on to the new route.
The main root node for the previous layout is being used on the page too.
Its as if its trying to merge the two layouts instead of replacing.
I've wrapped everything in my first layout with a new single node (just a div) and this seems to have solved it pulling other elements in.

Would you open a new issue with a reproduction? Happy to take a look.


Design flaw: when pressing arrow up in input field of chat your written prompt is gone

I was writing an extensive prompt for copilt chat in vscode and after minutes of writing I pressed arrow up to go to the top of the input field to re-read my prompt and my whole message was gone. This is a serious design flaw.

You can then press the down arrow and it should go back to your edited prompt.


1 test failed. locale:x-pseudo:calendar day (2493.6)

Hi There,
just occasionally ran the testframework and got an error. Yesterday at 02:00AM Germany switched to DST. Therefore there was no 02:00am but instantly 03:00am.
Not sure, if this is a bogus test-case which simply fails 2 times a year (if DST is applicable) or should be handled transparently by the library.
Client info
Date String   : Mon Mar 27 2017 09:47:42 GMT+0200 (CEST)
Locale String : 27.3.2017, 09:47:42
Offset        : -120
User Agent    : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 OPR/43.0.2442.1144
Moment Version: 2.18.1

====
locale:x-pseudo:calendar day (2493.6)
yesterday at the same time
// Expected Ý~ést~érdá~ý át 02:00
// Actual   Ý~ést~érdá~ý át 03:00
"Ý~ést~érdá~ý át 03:00" === "Ý~ést~érdá~ý át 02:00"

Thanks for the report.

Not sure, if this is a bogus test-case which simply fails 2 times a year (if DST is applicable)

I'm pretty sure that's what this is. With a couple of exceptions, the library itself works well with DSTs, but the tests make lots of assumptions in their asserts that aren't valid across DSTs, leading to test failures like this; i.e. Moment did what it was supposed to but the test didn't expect it to, so it failed. So I'm going to close this as probably-not-a-real-problem.


Version 6 - beta test for Envoy with firmware 7.x.x

I have published v6.0.0-beta to test.
In Authorization section You can enable support for FW. 7xx.x and paste your generated token.
This test version may not working correct at this time, it is only to test correct login to envoy.
I don’t have Envoy with FW 7.x.x and all your help  and test will be very helpful for me.
For test please also enable debug mode and always post the log.
This will close #57 #61 #60 #

I am on V7.0.107 Firmware, Happy to help beta test.
First Project I've attempted to help with so go easy.
Attempted to use Un-Commisioned Token, Feedback:
Device: <IP_ADDRESS> Envoy-S, inventory error: AxiosError: Request failed with status code 401, reconnect in 15s.
Used token fed via "https://enlighten.enphaseenergy.com/entrez-auth-token?serial_num={}"
(Long Term Tokens)
Feedback:
Device: <IP_ADDRESS> Envoy-S, inventory error: AxiosError: Request failed with status code 401, reconnect in 15s.
Same errors.
Like I said I'm new not much involved with any sorting coding, Unsure how to correctly find logs.
If anyone can brief me i will certainly find them
From a user sadly missing V5.x.xxx Firmware

@NoSnow3
Thanks for test but please enable debug in plugin settings advanced section and post the complete log.  As i see your error is from other section, looks like token login is working.

homebridge.log.txt
Hoping this is what you are looking for.

@NoSnow3
pushed beta.7 to test, also please test again with the log.
It will be very helpful for me if someone can get me the remote access to Envoy with FW 7.x.x.

HomeBridge Beta7 Log.txt
New Log...
"Device: <IP_ADDRESS> Envoy-S, inventory error: Error: self signed certificate, reconnect in 15s."
Regards Remote access. To the actual Envoy? unsure on how we can do that envoy itself

beta.8 pushed, try again

homebridge Beta8 Log.log.txt
"inventory error: TypeError: this.digestAuthInstaller is not a function, reconnect in 15s."

again beta.10

homebridge Beta10 Log.txt
"Envoy-S, inventory error: Error: self signed certificate, reconnect in 15s."

OK, try beta.11

homebridge Beta11 Log.txt
Same again,
"inventory error: Error: self signed certificate, reconnect in 15s."

beta.14 ready

homebridge Beta14 Log.txt
"Envoy-S, inventory error: AxiosError: Request failed with status code 401, reconnect in 15s."
Seems to take longer to error this time

try beta.16

homebridge Beta15 Log.txt
"Envoy-S, meters error: AxiosError: Request failed with status code 401, reconnect in 15s."
Beta 15 was all that available

homebridge Beta16 Log.txt
"meters error: AxiosError: Request failed with status code 401, reconnect in 15s."

I Changed token from the shorter timed one that was on the "https://entrez.enphaseenergy.com/entrez_tokens" Link
To my longer Validated Token on "https://enlighten.enphaseenergy.com/entrez-auth-token?serial_num={}"
This time the Log is showing readouts from the envoy but still showing error.
" power mode error: AxiosError: Request failed with status code 401, reconnect in 15s."
homebridge Beta16.2 Log.txt

ok looks better now, try beta.22

homebridge Beta22 Log.txt
Looking better, Thought i had seen an error but its refreshing to fast to catch it

Ah found it,
"[11/12/2022, 11:57:04] [homebridge-enphase-envoy] Device: <IP_ADDRESS> Envoy-S, home error: TypeError: Cannot read properties of undefined (reading 'updateCharacteristic'), reconnect in 15s."

try beta 23

Scrap the above as regards to errors
homebridge Beta23.2 Log.txt
"[11/12/2022, 13:01:52] [homebridge-enphase-envoy] Device: <IP_ADDRESS> Envoy-S, home error: TypeError: Cannot read properties of undefined (reading 'updateCharacteristic'), reconnect in 15s."

No errors spotted.
Still Can not see Devices in Eve or Controller at this moment.

Arę you added it to the HomeKit app

you need add this accessory ti the home.app first

Can confirm i have done this.

this is bridge not the accessory itself, look here https://github.com/grzegorz914/homebridge-enphase-envoy/wiki#adding-to-homekit

beta.25 pushed to test

Updateded but still can not find the accessory when scanning once the child bridge is added

Can you post the log after update to b.25
Also try this if can not find the accessory https://github.com/grzegorz914/homebridge-enphase-envoy/wiki#troubleshooting

Followed Troubleshooting, No results as of yet.
homebridge Beta 25.txt
Log attached.

homebridge Beta 26 Log.txt
Log Attached

Nice, probably final beta 27 ready

Downloading, Still yet to see in Eve or controller, Scratching my head on that one

"Device: <IP_ADDRESS> Envoy-S, ensemble inventory error: TypeError: Cannot read properties of undefined (reading 'devices'), reconnect in 15s"
homebridge Beta 27.txt

28 ready

Might be an ios16 issue hold on

No,  try this https://github.com/grzegorz914/homebridge-enphase-envoy/wiki#troubleshooting and after this restart whole homebridge then try add accessory again, no need add bridge to home.app

any log from beta.28

homebridge Beta 28 Log.txt
Same Error again

ok beta.29 ready

homebridge Beta 29 Log.txt
No immediate errors

Nice, ready to publish release.
Many thanks for testing and patience.

No problem, still struggling with displaying in eve/controller

This must be added to Home.app first

I can not add just the accessories only the bridge.

May be try to change the name in plugin Config

Also try to clear Homebridge cashe

Cleared cache and added using iOS 15.5. Shows on Eve and Controller now

Nice.

v6.0.0 released


series_decomp_multi

try  to run which in FEDformer.py get an error which was in class series_decomp_multi(nn.Module) in Autoformer_enc_dec.py:
I don't know how to fix it, and the tensor's dimension is not match: one is (3, 95, 7), another is (3,96,7).
Guess it should be (3,96,7)
Wishing to get your help! Thanks.
if __name__ == '__main__':
    class Configs(object):
        ab = 0
        modes = 32
        mode_select = 'random'
        # version = 'Fourier'
        version = 'Wavelets'
        moving_avg = [12, 24]
        L = 1
        base = 'legendre'
        cross_activation = 'tanh'
        seq_len = 96
        label_len = 48
        pred_len = 96
        output_attention = True
        enc_in = 7
        dec_in = 7
        d_model = 16
        embed = 'timeF'
        dropout = 0.05
        freq = 'h'
        factor = 1
        n_heads = 8
        d_ff = 16
        e_layers = 2
        d_layers = 1
        c_out = 7
        activation = 'gelu'
        wavelet = 0

    configs = Configs()
    model = Model(configs)

    print('parameter number is {}'.format(sum(p.numel() for p in model.parameters())))
    enc = torch.randn([3, configs.seq_len, 7])
    enc_mark = torch.randn([3, configs.seq_len, 4])

    dec = torch.randn([3, configs.seq_len//2+configs.pred_len, 7])
    dec_mark = torch.randn([3, configs.seq_len//2+configs.pred_len, 4])
    out = model.forward(enc, enc_mark, dec, dec_mark)
    print(out)

class series_decomp_multi(nn.Module):
    """
    Series decomposition block
    """

    def __init__(self, kernel_size):
        super(series_decomp_multi, self).__init__()
        self.moving_avg = [moving_avg(kernel, stride=1) for kernel in kernel_size]
        self.layer = torch.nn.Linear(1, len(kernel_size))

    def forward(self, x):
        moving_mean = []
        for func in self.moving_avg:
            moving_avg = func(x)
            moving_mean.append(moving_avg.unsqueeze(-1))
        moving_mean = torch.cat(moving_mean, dim=-1)
        moving_mean = torch.sum(moving_mean * nn.Softmax(-1)(self.layer(x.unsqueeze(-1))), dim=-1)
        res = x - moving_mean
        return res, moving_mean

today is ok , all turn to (3, 96,7)
sorry, close it


Deprecated use of np.int inside NSGAIII implementation

Dearest,
I am using JMetalPy to solve a multi-objective problem. I found that NSGIII makes use of the deprecated np.int.
Could you modify the implementation to use int instead?
Thank you so very much.

Fixed.
Thanks for pointing it out.


added class Bunch in utils

Otherwise an exception is generated:
'dict_keys' object has no attribute 'sort'

I'll use easydict instead of bunch. This is in the next few days.

Please check the code again. The issue is fixed. Thank you for your support.


no msvs 2015

maztheman I'm getting 60 s/s with nicehash's miner with a nvidia 750ti on windows 8.1. On my windows vista the first release 11 s/s because i can't load msvs 2015. Is it possible to make a build that doesn't use msvs 2015 error says missing 140.dll. I'm mining at nicehash selling my hash. And I cant compile. Would like to try your latest release for cuda. thx  :)

Please download and install this redistribution:
https://www.microsoft.com/en-us/download/details.aspx?id=48145
It is available for Windows 8.1.  I use 2015 because of the compiler enhancements.

Thank you but windows VISTA 64x won't install 2015.

Okay, Ill see about putting up a vs 2012 version.

I hope this works for you:
https://github.com/maztheman/nheqminer/releases/download/v0.4l/v0.4l_vs120.7z

Thx But the last driver was 5-2016 and it's saying it won't work with that driver.

oh because im using CUDA 8.0 ?

Okay try this instead!, cuda 7.5, visual studio 2013:
https://github.com/maztheman/nheqminer/releases/download/v0.4l/v0.4l_vs120_cuda75.7z

Says now I need cudart60_80.dll

cudart60_80.dll or cudart64_80.dll ?
On Mon, Nov 28, 2016 at 2:03 PM, auroracoin<EMAIL_ADDRESS>wrote:

Says now I need cudart60_80.dll
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/maztheman/nheqminer/issues/6#issuecomment-263393321,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABZS8McPEvVJ78xm7Yx3P_BPIn4AHSxiks5rC0GIgaJpZM4K7lb0
.

cudart64_80.dll

get it here:
https://github.com/maztheman/nheqminer/releases/download/v0.4l/cudart64_80.dll

nheqminer.exe      -u wallet.VISTA  -p x  -cd 0 1  is this the right bat file?  so many different miner apps.  It opens then almost starts hashing then closes.

try doing a cuda query first:
nheqminer.exe -ci
then benchmark the devices by:
nheqminer.exe -b 25 -t 0 -cd 0
where "0" is the device id listed in the cuda query.

ok trying  thank you

crash using only this   nheqminer.exe -b 25 -t 0 -cd 0

oh hmm....I dont know what else to try, im not sure how to get this to work as I dont have any Vista installs.

at this point it maybe my bat file?

I dont think so, if its crashing just benchmarking I would need to see the screen shot of the crash, as it might help me figure out why its happening...

ok  trying to grab it with this      nheqminer.exe -b 25 -t 0 -cd 0

http://i.imgur.com/omqpo5G.jpg

then crashes

for comparison or info here is nicehashs first miner i think or ?    http://i.imgur.com/9j5TcIY.jpg

with this command it almost starts hashing.
nheqminer.exe      -u wallet.VISTA   -p x  -cd 0 1  -t 0

If this helps this is a pic of files of yours and the one that works with 2 cards at very low hashrates.
http://i.imgur.com/RcDZ98m.jpg


change k_s picture

Please commit the change to the init_gh-pages branch! 😃

pr rebased accordingly

Due to git issues i just added your picture directly to the branch 👍


fix: do not fatal on failure to create cloud object

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #441
Special notes for your reviewer:
The caller will handle any errors in creating the cloud object. We do not need to handle any intermittent cloud api errors, the next reconciler should do the job.
Release note:
none

/ok-to-test


SPAN elements in row cells are showing up empty - no data binding on rows

I'm submitting a ...  (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here

Current behavior

The "table" itself will render the correct number of rows (visible by inspecting the rendered page). However, it appears that data isn't being properly bound to the body-cell.component. .datatable-body-cell-label appears with an empty SPAN element.

Expected behavior

Row data should be bound to the element and render to the page
Reproduction of the problem

Follow the examples in Getting Started as well as using the fetch method described in the demo.
What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Mac OS 10.10.5
VS Code
Webpack
Angular CLI 1.0.15
Node

Table version: 6.0.2

Angular version: 2.4.5

Browser: all

Language: TypeScript 2.0.10

Can you make a demo?

Hmm, haven't been able to recreate the issue. Made a couple test builds using both Angular quickstart and CLI and in both cases the plugin is working fine. Something to do with my project environment then :/

Alrighty. I'm gonna close for now then.

@pixelsailor, were you able to figure out what is wrong with your environment that caused the empty spans in row data cells?
I am having the same issue and wondering what I am doing wrong
I have observables for both rows and columns, using the async pipe

Never mind, I figured it out
My columns names were in PascalCase and if I do lowercase for my row names in name value pairs there seems to be an issue matching columns to rows ... an error would have saved me 4hrs but, I am just learning this component so it is alright
Thank you for a fantastic data-grid though 👍

Issue is present.
When I get data from controller in PascalCase see screenshot #1 below
Data display properly in code:

{{company.Name }}
{{company.ContactPerson}}
{{company.OMSId}}
{{company.Token}}

but data doesn't display properly in grid, see screenshot#2
<ngx-datatable class="bootstrap ngx-datatable"
#someTable
[rows]="page.Items"
[loadingIndicator]="loading"
[columns]="columns"
[externalPaging]="true"
[externalSorting]="true"
[columnMode]="ColumnMode.force"
[count]="page.TotalElements"
[limit]="page.Size"
[offset]="page.PageNumber"
(page)="onPage($event)"
(sort)="onSort($event)"
[headerHeight]="50"
[summaryRow]="true"
[summaryPosition]="'bottom'"
[footerHeight]="50"
rowHeight="auto"
[reorderable]="reorderable">

{{ value }}

#screen 1

#screen 2


interesting lead

Hello, yesterday I talked to http://azer.bestavros.net/ who told me he had had a PhD student who worked on building shapley value estimators. Probably interesting to dig deeper... :-) Cheers

I contacted him this morning, I am waiting for his response

I checked the paper of his student but unfortunately they only used a Monte-Carlo approach.


some text is not localized in Chinese site mode

Describe the bug
some text is not localized in Chinese site mode,perhaps because the relevant adaptations are not done.

Reproduction

Open the offical website

Expected behavior
Proper display of configured localized text
System Info
System:
    OS: macOS 12.6
    CPU: (8) arm64 Apple M1
    Memory: 120.80 MB / 8.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.18 - /usr/local/bin/yarn
    npm: 8.19.2 - /usr/local/bin/npm
  Browsers:
    Chrome: 106.0.5249.61
    Safari: 16.0

Additional context
No response
Validations

[X] Read the docs
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

I think the themeCofig.locales could expose more params such as lastUpdatedText、prevPage、nextPage to support different language  in these areas.

yep, I think so too, I mentioned a pr


TaxonName component

This component will be used in various locations throughout the app. It should include:

[ ] Optional Common Name (Body1 sizing) - default to scientific name if there is no common name available
[ ] Optional Scientific Name (Body3 sizing, italic)
[ ] Optional Location component (location pin icon and a place name)
[ ] Optional Date component (a clock icon and a date string)
[ ] Optional green dots (Confidence Interval Bar) to indicate CV score (5 dots, rounded to the nearest confidence percentage from 1-100%)

Default color for all elements except for inatGreen dots should be:

[ ] #454545 (darkGray)

[ ] Since names can be long, all text should be able to wrap onto multiple lines for components like ObsListItem

[ ] We'll also need a prop to limit Common Name and Scientific Name to a single line for ObsGridItem

I'd prefer to a) build off of https://github.com/inaturalist/iNaturalistReactNative/blob/main/src/components/DisplayTaxonName.js, and b) restrict the scope here to deal only with the taxon name. Name display is complicated and we don't want to repeat all the logic involved in deciding what name to show first, whether to show a common name, what common name to show, etc. The additional details only pertain to an observation and pretty much only occur in the ObsListItem so I'm not sure they need to be their own components.
As to how we can build off of <DisplayTaxonName>, I guess that's up to the developer. One option would be to add a prop to that component so renders two text components. Another might be to abstract some of the name choice logic out and make two components, one for the name in a single line and another for a two-line display.

Ok, updated these issues to move date/location/confidence interval into ObsListItem to-dos and to clarify that this should build off the DisplayTaxonName component.

I can get something going on this.


style: update workflow descriptor formatting

Fix typos/definitions, reformat Snakemake descriptor files with snakefmt and run linting in CI.

Add snakefmt autoformatter to new requirements file environment.dev.yml
Update docs to indicate that developers (but not users) should update their environment with the packages listed in environment.dev.yml
Run snakefmt on workflow descriptor files
Run Snakemake linting and resolve issues arising from linting
Add linting to CI pipeline (only passes if linting passes)

All issues except one have been solved:
    * Absolute path "/^>/ {{print \$1; next}} 1" in line 72:
      Do not define absolute paths inside of the workflow, since this renders your workflow irreproducible on other machines. Use path relative to the working directory
      instead, or make the path configurable via a config file.
      Also see:
      https://snakemake.readthedocs.io/en/latest/snakefiles/configuration.html#configuration

As you can see, there is no path stated but the lint interprets / as a path indicator. See the same issue with a possible solution here. Should I use this solution?

I guess if you were to go that route, you'd have to put it in both.
Anyway, I don't like this workaround as it puts stuff where it doesn't belong. I mean, commands in the config? :see_no_evil: It also makes the workflow harder to follow/read (i.e., we can't see what's happening just by examining the descriptor files).
I'm sure there are many other possible solutions. For example, you could try something along the lines of the other approach listed in that issue, i.e., use something like variable interpolation, either on the Python side, or in Bash, to construct your command. Or possibly directly in awk as in here: https://stackoverflow.com/questions/19789643/search-pattern-containing-forward-slash-using-awk
If none of that works, you could always write an awk script. It still hides the actual call, but I'd much rather inspect a script to see what command is being executed than the config.

Btw, I changed the name and description of this issue because I thought it was a PR :rofl:

I tried different command lines, I asked chatGPT and nothing works; I will proceed with the awk script if that is alright.

Sure :)

It seems that the two times this command line is used uses different input formats; the first one is a compressed fasta and the second one is just a fasta file. This implies that the input must be read from a pipe (the firs one will used zcat and the second one cat). Should the output be write in the standard output? If so the script will look like this:
#!/bin/bash

# Setting to strict mode
set -e
set -u
set -o pipefail

# Trimming fasta ID
awk -F" " "/^>/ {{print \$1; next}} 1"

If not, > $1 will be add to the awk command

Fine with the pipe. I think STDOUT is fine, too.


scsictl shall accept generic key/value pairs for options that take parameters

Some scsictl options expect more than one parameters for some options, e.g. the options for copying/renaming files. With #1238 there are up to three parameters. The current syntax for such a case expects the parameters in a particular order, separated by a colon. keys are implicit, only the values are specified. If only the third parameter is needed the parameter list has to start with two colons in order to pass the empty parameters, e.g.
>scsictl -s::mapping_info

Sometimes it may be simpler to just pass all possible parameters as key value pairs and in any order, e.g.
>scsictl -soperations=mapping_info:folder_pattern=pattern

In order to support both styles, when there is an equals ('=') character in the parameter list scsictl shall assume that the key/value format is used and parse the parameter list accordlingly.

>scsictl -soperations=mapping_info
Supported image file extension to device type mappings:
  hd1->SCHD
  hda->SCHD
  hdi->SCHD
  hdn->SCHD
  hdr->SCRM
  hds->SCHD
  is1->SCCD
  iso->SCCD
  mos->SCMO
  nhd->SCHD


Fix: fix enums naming convention in all project

@ErezBiren You have Lint issues

Thanks @baruchiro , Lint issues have been fixed.


fix: correct homepage studio button link

Changes
Change the path to the simple-asyncapi.yml example
Description
Correct the link in the Studio Button
Correct the links in some of the blog pages
Fixing issue(s)
https://github.com/asyncapi/website/issues/2491

I'm not sure this PR is relevant or not, because Open in Studio button is running fine on the website. Any views? @derberg

There was another PR that was made at the same time and that made the same correction.
The only difference is that the other PR is using asyncapi/asyncapi and not the correct one pointing to the repo asyncapi/spec


Better handle edge cases where ElementBlogPosts targets a missing blog page

The block assumes that the blog page will always exists, which may not be the case. For example:

you could have a misconfiguration
the blog page could be archived after the block has been created
the blog page might not exists in the current locale

This PR makes the getPostsList logic more resilient and beefs up the matching test.

@maxime-rainville we've tagged 2.1.2 with your patch. Thanks again!

Travis is upgrading people to a new Ubuntu image which doesn't automatically start MySQL.
We've had that issue on core module, so you might be having the same problem.

Thanks for the pointer. I grabbed a travis file from another of our projects and seemed to do the trick, but we'll monitor that.


creation of the asset custodianship requisition form(doctype)

@brianraila creation of the asset custodianship requisition form(doctype)

The pr also contain the doctype for the Asset Description.

@brianraila The Form PR is missing the Section of Terms.


ci: update base node image to 14

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


bump dependencies

In particular pick up https://github.com/RalfJung/rustc-build-sysroot/pull/22 to fix the fallout from https://github.com/rust-lang/rust/pull/128534.

@bors r+

:pushpin: Commit 9a3553725ed19da5c7dd428e1c69faababc4375b has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit 9a3553725ed19da5c7dd428e1c69faababc4375b with merge 2543c986b7c92c0278c2d6051b71c2e0f473ea83...

:broken_heart: Test failed - checks-actions

@bors r+

:pushpin: Commit 6f24bf7aa5e4d15b2f4b52bf5bd81161ad3b6b0b has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit 6f24bf7aa5e4d15b2f4b52bf5bd81161ad3b6b0b with merge 7e08769bbf0966ea7548af11524a3fe7d23a0610...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 7e08769bbf0966ea7548af11524a3fe7d23a0610 to master...


HotFix django-polymorphic requirements

Current version not support django_polymorphic>=0.8
For example:
ImportError: cannot import name PolymorphicModel

PolymorphicModel class not exists in polymorphic module.
It need be imported from polymorphic.polymorphic_model import ...
This is a hotfix

Thanks, fixed in 1.0.6.


Add reactor-bom and netty-bom in cosmos test.

Add reactor-bom and netty-bom in cosmos test.

/azp run java - cosmos - tests

/azp run java - cosmos - tests

Why are you referencing a BOM? We should be specifying our dependency versions explicitly for our libraries, at which point the BOM doesn't add much value?

@mitchdenny
Sorry for make you confused.
It's just a demo PR, used to discuss this issue: https://github.com/Azure/azure-sdk-for-java/issues/17986
I changed the PR to Draft just now.


password of user

Due to use github oauth as we do not consider any password , the password parameter in database has been kept as nullable= False , this must be changed to True.
For users  using github login random sample passwords must be generated to store in database.
Please check the code to understand further.

Hi I would like to try to work on this issue.

go ahead @gabrielhicks

@DiptoChakrabarty I would like to work on this issue . Please assign this to me.

@TechnoPhasePRO I opened a PR #11 if you want to check it out and see if its a solution

@DiptoChakrabarty I would like to work on this issue . Please assign this to me.

Hey @TechnoPhasePRO  this issue has been solved already and its working you can try some of the other issues present


Record limit option

Is it possible to set a record limit to be returned together with paging without calculating it manually? Currently, I would have to do a $count and then use $top and $skip. Are there any other ways or methods that I can call?
Thanks in advance!

Hi, and sorry for the late response. Did you try WithCount clause? It should return the result count together with actual results.


[FEA] Profiling tool should not suggest increase spark.sql.shuffle.partitions if there is huge shuffle skew

Is your feature request related to a problem? Please describe.
Profiling tool should not suggest increase spark.sql.shuffle.partitions if there is huge shuffle skew.
This normally happens when we see huge skew in a shuffle stage.
Current logic of Profiling tool will check if there is spilling, and if there is, it will suggest increase spark.sql.shuffle.partitions.
However this could make things worse:
Adding more shuffle partitions will not resolve skew issue, instead, it might make the query slower.
We can define the threshold of the skew, and which metrics to look at.
For example, here is just one proposal:
We can look at the shuffle stage's below metrics, once the Max >= 10 x Median, then no need to suggest increase spark.sql.shuffle.partitions:

Spill(Memory)
Spill(disk)
Shuffle Read Size
Shuffle Write Size

Close this issue since it is already fixed in 24.02.1


Thought about Armenian "ու" Character

Background
Lately while presenting cmints slides and talking about order, @androideveloper mentioned an interesting issue that might be a case when using localeCompare, currently in Armenian in order to write character which read as "U" using Unicode, you might use combination of two letters which is "ու", Currently this letter is located after Armenian letter "ց" in Armenian Alphabet, while the letter "ո" is located after letter "շ".
Questions

How would browsers deal with current edge case, while Unicode misses single character option for current character?
Why there is no single character in Unicode?
If it's a bug, how in general such edge cases are fixed ?

Exactly. Thanks :) Where should we report this issue?


Add helper utilities for testing RPN functions

What have you changed? (mandatory)
This PR adds RpnFnScalarEvaluator which can be used to test RPN function implementation easily.
Sample usage:
let output = RpnFnScalarEvaluator::new()
    .push_param(Some(1.0f64))
    .push_param(Some(1.0f64)
    .evaluate(RpnFnFoo)
    .unwrap();
assert_eq!(output, Some(2.0f64));

[x] Merge https://github.com/tikv/tikv/pull/4573 first.

What are the type of the changes? (mandatory)

Engineering (engineering change which doesn't change any feature or fix any issue)

How has this PR been tested? (mandatory)
No.

/rebuild

Close since we can directly merge https://github.com/tikv/tikv/pull/4575


WIP: Rewrite tests

Rewrite tests to kotlin + mockk. Remove mockito

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


Operator-sdk run bundle failed registry pod due to missing root schema field

Bug Report

What did you do?
Run operator-sdk run bundle quay.io/henry_h_li/common-service-operator-bundle:a9101de0-dirty --install-mode OwnNamespace
What did you expect to see?
Successful run with registry pod running and operator pod running
What did you see instead? Under which circumstances?
The operator never gets installed because the registry pod is in crash loop.
$ oc get pods
NAME                                                              READY   STATUS   RESTARTS      AGE
uay-io-henry-h-li-common-service-operator-bundle-a9101de0-dirty   0/1     Error    2 (22s ago)   24s

Logs
time="2023-09-26T19:27:53Z" level=info msg="starting pprof endpoint" address="localhost:6060"
time="2023-09-26T19:27:53Z" level=fatal msg="object '{\"image\":\"quay.io/henry_h_li/common-service-operator-bundle:a9101de0-dirty\",\"name\":\"ibm-common-service-operator.v4.3.0\",\"package\":\"ibm-common-service-operator\",\"properties\":[{\"type\":\"olm.gvk\",\"value\":{\"group\":\"operator.ibm.com\",\"kind\":\"CommonService\",\"version\":\"v3\"}},{\"type\":\"olm.package\",\"value\":{\"packageName\":\"ibm-common-service-operator\",\"version\":\"4.3.0\"}},{\"type\":\"olm.csv.metadata\",\"value\":{\"annotations\":{\"alm-examples\":\"[\\n  {\\n    \\\"apiVersion\\\": \\\"operator.ibm.com/v3\\\",\\n    \\\"kind\\\": \\\"CommonService\\\",\\n    \\\"metadata\\\": {\\n      \\\"labels\\\": {\\n        \\\"app.kubernetes.io/instance\\\": \\\"ibm-common-service-operator\\\",\\n        \\\"app.kubernetes.io/managed-by\\\": \\\"ibm-common-service-operator\\\",\\n        \\\"app.kubernetes.io/name\\\": \\\"ibm-common-service-operator\\\"\\n      },\\n      \\\"name\\\": \\\"example-commonservice\\\"\\n    },\\n    \\\"spec\\\": {\\n      \\\"size\\\": \\\"starterset\\\"\\n    }\\n  }\\n]\",\"capabilities\":\"Seamless Upgrades\",\"containerImage\":\"icr.io/cpopen/common-service-operator:latest\",\"createdAt\":\"2023-09-26T19:21:40Z\",\"description\":\"The IBM Common Service Operator is used to deploy IBM Common Services\",\"nss.operator.ibm.com/managed-operators\":\"ibm-common-service-operator\",\"nss.operator.ibm.com/managed-webhooks\":\"\",\"olm.skipRange\":\">=3.3.0 <4.3.0\",\"operatorChannel\":\"v4.3\",\"operatorVersion\":\"4.3.0\",\"operators.openshift.io/infrastructure-features\":\"[\\\"disconnected\\\"]\",\"operators.operatorframework.io/builder\":\"operator-sdk-v1.30.0\",\"operators.operatorframework.io/project_layout\":\"go.kubebuilder.io/v3\",\"repository\":\"https://github.com/IBM/ibm-common-service-operator\",\"support\":\"IBM\"},\"apiServiceDefinitions\":{},\"crdDescriptions\":{\"owned\":[{\"description\":\"CommonService is the Schema for the commonservices API. Documentation For additional details regarding install parameters check https://ibm.biz/icpfs39install. License By installing this product you accept the license terms https://ibm.biz/icpfs39license\",\"displayName\":\"CommonService\",\"kind\":\"CommonService\",\"name\":\"commonservices.operator.ibm.com\",\"specDescriptors\":[{\"description\":\"Accepting the license - URL: https://ibm.biz/integration-licenses\",\"displayName\":\"Accept\",\"path\":\"license.accept\",\"value\":[false],\"x-descriptors\":[\"urn:alm:descriptor:com.tectonic.ui:checkbox\"]},{\"description\":\"The size of deployment profile for IBM Cloud Pak foundational services\",\"displayName\":\"Size\",\"path\":\"size\",\"x-descriptors\":[\"urn:alm:descriptor:com.tectonic.ui:select:starterset\",\"urn:alm:descriptor:com.tectonic.ui:select:starter\",\"urn:alm:descriptor:com.tectonic.ui:select:small\",\"urn:alm:descriptor:com.tectonic.ui:select:medium\",\"urn:alm:descriptor:com.tectonic.ui:select:large\",\"urn:alm:descriptor:com.tectonic.ui:select:production\"]},{\"description\":\"The profile controller for IBM Cloud Pak foundational services\",\"displayName\":\"ProfileController\",\"path\":\"profileController\",\"x-descriptors\":[\"urn:alm:descriptor:com.tectonic.ui:select:default\",\"urn:alm:descriptor:com.tectonic.ui:select:commonservice\",\"urn:alm:descriptor:com.tectonic.ui:select:turbonomic\",\"urn:alm:descriptor:com.tectonic.ui:select:vpa\"]}],\"statusDescriptors\":[{\"description\":\"Installed Bedrock Operator Name\",\"displayName\":\"Name\",\"path\":\"bedrockOperators[0].name\"},{\"description\":\"Installed Bedrock Operator InstallPlan Name\",\"displayName\":\"InstallPlanName\",\"path\":\"bedrockOperators[0].installPlanName\"},{\"description\":\"Installed Bedrock Operator Status\",\"displayName\":\"OperatorStatus\",\"path\":\"bedrockOperators[0].operatorStatus\"},{\"description\":\"Installed Bedrock Operator Subscription Status\",\"displayName\":\"SubscriptionStatus\",\"path\":\"bedrockOperators[0].subscriptionStatus\"},{\"description\":\"Installed Bedrock Operator Version\",\"displayName\":\"Version\",\"path\":\"bedrockOperators[0].version\"},{\"description\":\"Installed Bedrock Operator Troubleshooting\",\"displayName\":\"Troubleshooting\",\"path\":\"bedrockOperators[0].troubleshooting\"},{\"description\":\"The Overall Status Of All Installed Bedrock Operators\",\"displayName\":\"OverallStatus\",\"path\":\"overallStatus\"}],\"version\":\"v3\"}]},\"description\":\"# Introduction\\n\\nThe `IBM Cloud Pak foundational services` is a bridge to connect IBM Cloud Paks and Operand Deployment Lifecycle Manager (ODLM) with IBM Cloud Pak foundational services. You can also install the `IBM Cloud Pak foundational services` in stand-alone mode.\\n\\nWhen you install this operator, the operator completes the following tasks:\\n\\n  - Installs ODLM in all namespaces mode\\n  - Creates the `ibm-common-services` namespace\\n  - Creates the Common Services `OperandRegistry` and `OperandConfig` in the `ibm-common-services` namespace\\n\\n# Details\\nFor more information about installing this operator and other Common Services operators, see [Installer documentation](http://ibm.biz/cpcs_opinstall). If you are using this operator as part of an IBM Cloud Pak, see the documentation for that IBM Cloud Pak to learn more about how to install and use the operator service. For more information about IBM Cloud Paks, see [IBM Cloud Paks that use Common Services](http://ibm.biz/cpcs_cloudpaks).\\n\\nFor more information about the available IBM Cloud Pak foundational services, see the [IBM Knowledge Center](http://ibm.biz/cpcsdocs).\\n\\n## Supported platforms\\n\\nRed Hat OpenShift Container Platform 4.5 or newer installed on one of the following platforms:\\n\\n - Linux x86_64\\n - Linux on Power (ppc64le)\\n - Linux on IBM Z and LinuxONE\\n\\n## Operator versions\\n\\n - 4.3.0\\n\\n## Prerequisites\\n\\nBefore you install this operator, you need to first install the operator prerequisites:\\n\\n- For the list of prerequisites for installing the operator, see the IBM Knowledge Center [Preparing to install services documentation](http://ibm.biz/cpcs_opinstprereq).\\n\\n### Resources Required\\n\\n#### Minimum scheduling capacity\\n\\n| Software                   | Memory (MB) | CPU (cores) | Disk (GB) | Nodes  |\\n|\"}}]}\n' is missing root schema field"

Not sure why there is a missing q from quay in the pod name either.
Environment
Operator type:

/language go

Kubernetes cluster type:
OpenShift
$ operator-sdk version

$ go version (if language is Go)
go version go1.21.0 linux/amd64
$ kubectl version

Possible Solution

Additional context
I hit this error when using operator-sdk v1.30.0 and v1.31.0.
I did not see this issue when using operator-sdk v1.29.0 or v1.28.0, so I do not think it's because of opm since the same default index image was used for all runs.
The only change related to operator-sdk run bundle I could find between v1.29.0 and v1.30.0 is this one https://github.com/operator-framework/operator-sdk/pull/6477, but I do not see how this change would cause the error log above.
I also have another operator where operator-sdk run bundle runs successfully even at v1.30.0 or v1.31.0, https://github.com/IBM/ibm-cert-manager-operator

/bug

/kind bug

/triage support

This is interesting. At first glance of the error it seems like there is no schema: field in the FBC object that is being parsed, but running opm render on the image provided in the issue description that field does exist. I haven't had time to try and replicate this, but will swing back around when I have some time if someone else hasn't already taken a look at this.
Thanks for filing the issue!

Let me know how I can help debug the issue. It probably is something specifically with common-service-operator since cert-manager-operator did not see issues.


Spin up multisite using built in php webserver

Hi, Id like to use the built in php webserver to launch a multisite for development use. Is this possible?
i.e. given that ive setup the multisite using the instructions https://learn.getgrav.org/advanced/multisite-setup, can I launch it with 'something' like :
php -S <IP_ADDRESS>:8080 system/router.php

To give some more context:

Cloned grav from github, and performed the install steps.
Added the example setup_subdirectory.php file from the multisite documentation in the grav root and renamed it setup.php.
Copied an existing (working) grav site into user/sites/mysite such that plugins, user etc exist in this folder

Running the above php command in the grav root gives :

HTTP 404 for http://<IP_ADDRESS>:8080/notmysite
'Theme 'antimatter' does not exist, unable to display page.'  for http://<IP_ADDRESS>:8080/mysite

However if I then cd to user/sites/mysite and run the php command then

http://<IP_ADDRESS>:8080 works as expected

I have tried to reinstall antimatter into both the grav root and into grav/user/sites/mysite using :
bin/gpm install antimatter

Still no luck though...

Realised my mistake was I should only copy the user/plugins, user/config, user/themes and user/pages folders into user/sites/mysite. Still doesnt work but Im not getting the 'antimatter' error anymore.


Scrolling in Safari becomes very choppy when disableAnimation is false on many floaters

🐛 Bug Report
I have about 40 components with a floater on each element that displays a tolltip when the user hovers over an element. The 40 components are in a scollable container and the user can scroll down and up. On Chrome the scrolling is very smooth, but on Safari the scrolling is very choppy.
Disabling animation with disableAnimation=true on the Floater make scrolling on Safari smooth again.
To Reproduce
See above
Expected behavior
Smooth scrolling in Safari as it is in Chrome
Run npx envinfo --system --binaries --npmPackages react-floater
System:
OS: macOS 10.14.5
CPU: (4) x64 Intel(R) Core(TM) i5-8210Y CPU @ 1.60GHz
Memory: 75.25 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 11.2.0 - ~/.nvm/versions/node/v11.2.0/bin/node
npm: 6.4.1 - ~/.nvm/versions/node/v11.2.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
npmPackages:
react-floater: ^0.6.4 => 0.6.4

To add some more info: although disabling the animation did result in a somewhat better performance the scrolling was still a bit choppy, so I decided not to use the floater altogether.
That resulted in a performance improvement in Chrome as well. I'm using infinite scroller to show more than the 40 components if the user scrolls down and in Chrome the items rendered very slowly when I scrolled to about 200th component. After removing the floater the components are rendered quickly again even when scrolling very far down the list.
I really love react-floater and will keep using it, but as long as it impacts performance this way I'll refrain from using it in a lot of components on one page.

I've also encountered this issue. We resolved it by rendering the floater component only when it has to be shown. Otherwise it's really laggy when you are scrolling.

Does setting eventDelay to 0 help? It seems to have helped for us in a long list.

Probably fixed in 0.8.0


[Smart Accounts] Add fee payer to authentication request & track

This generally looks good but will probably wait on merging to not break the contracts on the testnet


Way to crawl private groups?

Is there a way to "log in" the crawler with my credentials?
I assume it's doing web requests and I could just attach e.g. a cookie to the web request?
I know python very well, so a hint into the right direction would be enough.

Hi @philippkeller ,
Of course, yes, you can push your code to this project. Thanks!


Color prop responsive type v3

🐛 Bug Report
Since the original issue got closed and I'm unable to reopen it, I'm creating a new one. There is a problem with the type definition of a color prop because it combines the type of a color attribute prop and color utility prop. This means that only strings are valid inputs.
I'd gladly help to resolve this issue :)
To Reproduce
Use color prop with an object.
<x.a
  href="#"
  color={{
    _: 'indigo-500',
    hover: 'indigo-600',
    visited: { hover: 'indigo-900' },
  }}
>
  Link
</x.a>

Expected behavior
The color prop should accept objects with responsive/state values as described in docs.
https://xstyled.dev/docs/hover-focus-other-states/
Link to repl or repo (highly encouraged)
https://codesandbox.io/s/xstyled-color-type-error-forked-v3kz2?file=/src/App.tsx

I'm dealing with kind of the same problem related to the borderColor in my case. However, @AlfonzAlfonz I think your codebox is working as expected. What is the exact problem?

@pawelangelow Yes, the code is working as intended, but the problem is with the type of color. Typescript doesn't accept an object as color and marks it as an error.


website: add more use cases in en version.

What type of PR is this?

Check the PR title.

[ ] This PR title match the format: <type>(optional scope): <description>
[ ] The description of this PR title is user-oriented and clear enough for others to understand.

(Optional) Translate the PR title into Chinese.
(Optional) More detailed description for this PR(en: English/zh: Chinese).

en:  dd more use cases in en version
zh(optional):  网站英文版本添加更多用户案例，用户案例待翻译（TODO）
(Optional) Which issue(s) this PR fixes:

有兴趣参与用户案例翻译的同学，欢迎直接提交 PR。


Detect changes in private trait definitions [WIP]

This pull request builds upon @Duhemm's work in
https://github.com/sbt/sbt/pull/2441, but changes slightly the way it's
solved. It instead adds a specific api change that only invalidates
changes via inheritance (both global and local) and doesn't invalidate
member references, which gives us more correctness and precision.
As explained in https://github.com/sbt/sbt/issues/2490, the previous fix
violated some of the invariants of the incremental algorithm. As such,
we introduce the notion of an extra api hash which is independent of the
normal one. This extra hash, in the case of traits, is computed from the
private definitions found whose encoding produces wrong compilation issues, and
otherwise it's the same as the normal hash. As a result, we can tell apart the
cases where there are changes in the normal public API hash and the extra one,
and act accordingly.
I've called it extra instead of "privateHash" or something similar so that it
could accommodate other fixes in the future that have nothing to do with
accessibility of definitions. We cannot afford adding a new hash per
AnalyzedClass every time we need to have HashAPI be special cased for a
particular encoding.
Fixes:

source-dependencies/trait-private-val
source-dependencies/trait-private-var
source-dependencies/trait-private-object
source-dependencies/trait-super

And it also adds another two tests to complement
source-dependencies/trait-member-modified in checking that member
references to private trait definitions do not trigger unnecessary
compilations and that local inheritance does trigger an extra compile.
This is still work in progress as more unit tests need to be added. I'm open
to changing some details of the implementation since I'm not still 100% sure
that the apiExtraHash route is the best choice. Maybe we should go for
something more explicit in name?

To validate this pull request against other sbt modules, please visit this link.

P.S. I wanted to tackle this problem before I merge both API and Dependency and implement hashing on the fly so that I can have a better understanding of how I will handle this extra API hash then.

Shouldn't you only include private val/var, not private def? The latter do not need fields in the subclasses. (It seems that including private def is what allow trait-super to pass but that's a special case: super-accessors are created as private defs but become public later in the compiler pipeline)

Integration tests are passing. Lacking the junit tests, @eed3si9n @smarter would you mind reviewing the current design? I'd like to have early suggestions so that I can batch the implementation of junit tests and the potential improvements to the fix.

Could you have a look at this too? @dwijnand Would love some feedback.

Feedback addressed and unit tests added. @eed3si9n Can you review this? I'd love to merge this some time soon so that I can continue working on this area 😸

After struggling a little bit with the CI, now it's green.


add test: check if decoding is one to one by generating collisions

Two encodings that produce identical term: <<47>> and <<129,47>>. This is a violation of "choose optimal length encoding" rule in from protocol description here: https://github.com/ethereum/wiki/wiki/RLP
Note that the decode_length function rejects invalid encodings that have "non-optimal"
lengths, namely (1) singleton strings whose only byte is below 128 that are encoded
with a short (i.e. one-byte) length of 1 instead of as the strings themselves and (2)
strings and lists with long (i.e. multi-byte) lengths with leading zeros (which must be
absent) or below 56 (which should be encoded using short lengths).

This PR contains test detecting the error only, no fix.

@pdobacz PR to ExRLP - can't add you as an reviewer, unfortunately.

@paulperegud @pdobacz good catch. Currently, we don't handle errors from https://github.com/ethereum/tests/blame/develop/RLPTests/invalidRLPTest.json It'd be great if you implement it

@paulperegud hey, I rebased this on top of the #27's master and the prop test passes :tada:
Now, I also added a commit, with an alternative formulation of the generator, can you take a look if this makes sense? https://github.com/mana-ethereum/ex_rlp/pull/24/commits/b91d2a885f6376f1d61b92ea8e0515d631442a57

I dropped the binary() case since it is covered in the other generator already
went with 1/ list of binaries 2/ list of binaries or lists of binaries 3/ list of binaries, lists or binaries or lists of (binaries or lists of binaries) :joy:. So 1-, 2-, 3- levels of nesting resp.


Device profile switcher

I found this project which I thought may be of use to you: https://github.com/flopp/fritz-switch-profiles
I know being able to switch profiles was discussed in #6 and I don't know Python (or even own a fritzbox at the moment!) but thought it'd be worth posting this here as I discovered it when researching

Thanks for the hint.
Interesting. In #6 it sounded like the protocol would not support it, so it might be interesting to take a look how the mentioned package does allow setting of the profiles.

I'll close this issue in favor of the other one (which contains more meaningful history of conversation)


Announcement Banner in absolute position

At our company, we are trying to integrate this plugin into our Backstage instance. Overall, it looks really nice, thanks for the work!
However, we found something that might be interesting to others (or maybe am I misunderstanding how it works?). We wanted to use the NewAnnouncementBanner as a kind of alert to be shown in every page. However, we expected this element to be like the AlertDisplay provided by Backstage and not a component that moves down the whole page so it can fit on the top.
After making a couple changes in the css using the Firefox inspector (basically removing the "relative" property and adjusting spacing), I got something like this:

If you think this is something more people would like to have, I can create a PR with a new component and explain how it must be placed.

#93 should provide something similar to what you did :)


[DO NOT MERGE] Renamed navigation Step enum cases

This PR causes Xcode 10 to fail to finish compiling, in accordance to the SO post I wrote, some code change it causing the Swift compiler to fail, I will go through the changes to pinpoint what is causing it.

Closing in favor of: https://github.com/OpenZesame/Zupreme/pull/11


[image_picker] iOS permission "Access Your Photos": Select Photos is broken

Steps to Reproduce

install the app to the physical iOS device (in order to get permission request in the Future)
call await ImagePicker().getImage(source: ImageSource.gallery) on iOS device
Pick "Select photos" in "Flutter App Would like to Access Your Photos"
Allow access: pick any photos and confirm access (Done)
Pick a photo for using: pick another photo, the one that you didn't allow to use

Expected results: not allowed photos mustn't be available for picking
Actual results:  all photos are available for picking
I've tested this on iPhone 7 and iPhone X. And it seems like 'Selected photos' are ignored and an app has access to all photos.
You can use this app for checking https://github.com/furaiev/picker

Logs

[✓] Flutter (Channel stable, 2.2.1, on macOS 11.3 20E232 darwin-x64, locale en-GB)
    • Flutter version 2.2.1 at /Users/admin/developer/flutter
    • Framework revision 02c026b03c (2 weeks ago), 2021-05-27 12:24:44 -0700
    • Engine revision 0fdb562ac8
    • Dart version 2.13.1

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/admin/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/admin/Library/Android/sdk
    • Java binary at: /Applications/Android Studio 4.2 Preview.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5, Build version 12E262
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio 4.2 Preview.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.55.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.20.0

[✓] Connected device (2 available)
    • iPhone 12 Pro Max (mobile) • B03EDC35-812B-4969-B6CC-28A41F7C807D • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-5
      (simulator)
    • Chrome (web)               • chrome                               • web-javascript • Google Chrome 91.0.4472.77

@furaiev
Check if this open issue sounds similar to your case.
If so, you may close this and follow-up in linked one for further updates.
Thanks.

@darshankawar thank you, I didn't believe that it could be so old issue so didn't find it.


Non-arm plugin-git is pulled when using next

Component
agent
Describe the bug
All builds are failing because for some reason a non-arm version of plugin-git is pulled on my arm64 machine:
exec /bin/plugin-git: exec format error

System Info
{"source":"https://github.com/woodpecker-ci/woodpecker","version":"next-dfd4622b"}

Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A join our Discord Chat Server or the Matrix room.

hmm can you test if this still is the case if you pull and run it manually ?

Yep, the latest tag is still broken on my pi4:
[daniil@pi4 home.daniil.it]$ docker run --rm -it docker.io/woodpeckerci/plugin-git:latest
exec /bin/plugin-git: exec format error

More details: builds on arm64 are broken because the arm64 latest, 2.*, v1.6.1 and next tags of https://hub.docker.com all contain x86_64 executables.
For example (example sha taken from https://hub.docker.com/layers/woodpeckerci/plugin-git/latest/images/sha256-014a6e296eb573e06179841bdd09d0888f1993602ddcf5f8d2cfbe9933c54f23?context=explore), same result with img=woodpeckerci/plugin-git:latest
img=woodpeckerci/plugin-git@sha256:014a6e296eb573e06179841bdd09d0888f1993602ddcf5f8d2cfbe9933c54f23
docker pull --platform linux/arm64 $img && docker export $(docker create $img) | tar -x && file bin/plugin-git

Result:
bin/plugin-git: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, Go BuildID=SocNPx-xVnJaWH3SXQm8/YeNxHOfgXcmgEmH5w_0P/6_-qnapFoT7e-0x7VgVV/dMC7aku4xrgzcX6-fppX, stripped

Any update on this?
It should be a really simple fix, just re-building and pushing the woodpeckerci/plugin-git latest tag.

Turns out I actually forgot I was force-pulling the master tag of the git plugin from my woodpecker job yaml, however docker hub still has x86 images tagged as arm64, this should really be fixed :)

Here is a way to demonstrate the bug (on linux/amd64)

docker pull woodpeckerci/plugin-git --platform linux/arm/v7
docker create --name plugin-git-arm woodpeckerci/plugin-git
docker cp plugin-git-arm:/bin/plugin-git .
file plugin-git

Example run
$ docker pull woodpeckerci/plugin-git --platform linux/arm/v7

Using default tag: latest
latest: Pulling from woodpeckerci/plugin-git
810dd31423a9: Pull complete
950f45ce9dde: Pull complete
ad3d4bc55836: Pull complete
abde5c80bb26: Pull complete
Digest: sha256:883677218ecb0599f55347a87526bdef44c6d5684c9c800001d56aab15ee4c19
Status: Downloaded newer image for woodpeckerci/plugin-git:latest
docker.io/woodpeckerci/plugin-git:latest

$ docker create --name plugin-git-arm woodpeckerci/plugin-git

WARNING: The requested image's platform (linux/arm/v7) does not match the detected host platform (linux/amd64) and no specific platform was requested
919db7b7e51d34ba4df0fab77d4779582c5d8088b5e49f9969f451d71eaff877

$ docker cp plugin-git-arm:/bin/plugin-git .

$ file plugin-git

plugin-git: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, Go BuildID=SocNPx-xVnJaWH3SXQm8/YeNxHOfgXcmgEmH5w_0P/6_-qnapFoT7e-0x7VgVV/dMC7aku4xrgzcX6-fppX, stripped

The issue seems to first appear with version 1.6.1
I don't know if I should open an issue in https://github.com/woodpecker-ci/plugin-git ?

@6543 mind fixing this?
Woodpecker is essentially unusable on arm without manual config changes.

@6543 I would be happy to help with the bug but I got stuck here
https://github.com/woodpecker-ci/plugin-git/issues/53

Found the issue !
The container was an arm one but there were undefined environment variables that caused the Makefile to default to linux/amd64 for the go build
I deleted the first 2 "ARG" lines of the Dockerfile and it seems to fix the problem. The ARG lines still exist in the Dockerfile because they were duplicated !
I tried a locally built version of the plugin and it seems to work :)

wow I just noticed that my 2 first comments were giving exactly the same information that @danog, sorry about that

It's OK, as long as https://github.com/woodpecker-ci/plugin-git/pull/54 gets merged :)

If you want to try the image, you can clone my repo, checkout on arm fix and use
docker buildx build --platform linux/arm/v7 --tag woodpeckerci/plugin-git:local --output type=docker -f docker/Dockerfile.multiarch .
(with the right platform)
And then use woodpeckerci/plugin-git:local in .woodpecker.yml
I personally build it like this on my desktop and used docker save/load to have it on my rasberry pi

I worked around this without rebuilding the image by specifying the 1.5.0 tag in the job yaml: https://github.com/danog/MadelineProto/blob/stable/.woodpecker/.build.yml#L11

next plugin release planed ...

blocked by https://github.com/woodpecker-ci/plugin-git/issues/56

fixed by 7f5c3d3191350e59d43934c8c8801bc7b015a115 & 7651c7311de954b23fcf2cb8bfda0e2677c35eb3


Client Allocation Request for: Julien NOEL - Twinquasar

Client Allocation Questions
Core Information

Name: Julien NOEL - Twinquasar
Website / Social Media: @s0nik42
Region: Europe
DataCap Requested: 10TiB
Addresses to be Notarized: f3rpqqflz4bhyylporz3kjhejftvfs2gbjxv7gcw3imvviklmrqgee2jqsgp6hrl35ufckv76kdd245q352dtq
Notary Requested: neogeweb3

@s0nik42 Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

Hi @neogeweb3 ,
We're uploading a public dataset to filecoin, We previously work with the Filecoin Fundation (Philipp)  in EU, but now, We're the only remaining notary in EU. That's the reason why we decided to apply to a notary in another region.
Previous granted application : https://github.com/filecoin-project/filecoin-plus-client-onboarding/issues/145
Thank you,
Julien

Hey @s0nik42, thanks for the request. I do see the difficulty while you are the only notary in EU, but I could only allocate 5TiB to you at this moment because I have already allocated quite a lot DataCap to the EU while I am the GCN notary. Do you mind issuing another 5TiB request after you used up the first 5TiB?

Hi @neogeweb3 , <e can split in 2 requests.5TiB is perfect for now.
Thank you,
Julien

Great! Thanks for understanding, @s0nik42!

Request Approved
Your Datacap Allocation Request has been approved by the Notary
Message sent to Filecoin Network

bafy2bzacecwv6m6jc3grs4twywjeab5du64ppcfkdtuvs53fmb7chmqr377mm

Address

f3rpqqflz4bhyylporz3kjhejftvfs2gbjxv7gcw3imvviklmrqgee2jqsgp6hrl35ufckv76kdd245q352dtq

Datacap Allocated

5TiB

You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecwv6m6jc3grs4twywjeab5du64ppcfkdtuvs53fmb7chmqr377mm


Add SSH key path option to Digital Ocean doc

Modify the docs based on this PR https://github.com/docker/machine/pull/3761

@nathanleclaire might want to check PR along the docker/machine PR when you get a chance.

The upstream PR only seems to be against the machine repo's master. If this is a new feature, the doc PR needs to be against vnext-machine rather than master Please rebase if necessary.
@londoncalling PTAL

@mstanleyjones this is indeed a new feature that has been merged into machine's master.
Correct me if I'm wrong. But isn't this PR already pointed to be merged into vnext-machine rather than master?

v4n wants to merge 1 commit into docker:vnext-machine from v4n:vnext-machine


input and textarea error

Basically the same error i mentioned in my first post in #6 about the input, sadly i didn't check the input example again, my bad.
The compiled code ( and your src) for input and textera contain referenes to
this['{opts.name}']
this['{this.name}']

The html contains
<input type="{opts.type || \'text\'}" disabled="{disabled}" placeholder="{opts.placeholder}" onkeyup="{changeValue}" value="{value}" autocomplete="off" name="{this.name}">

but the i guess the reference with brackets causes an eror for the compiler somehow ?
Fixed this issue by simply giving a static name ( e.g. 'input'), but you probably intended something different here.

@Vantraninthena  Sorry for delay. Yes, you are right. There was a problem with custom names of input and textarea. It was necessary to transmit name from material-input (material-textarea) to sub input (textarea) into those tags. Before version 2.3 it worked fine. Then riot's developers made some changes regarding options. Currently all of options transmited to tag will be changed, for instance if we transmit "waves-color" in tag's attribute, into opts it will be represented like opts.wavesColor. Also construction like "this['{this.name}']" stopped to work as well. Proceeding from it i've made fixes regarding these issues. And added extended version of vanilla example.


AddTask and RemoveTask Testing

In this Pull Request we made the following Changes ♻ ...
- Added Tests fir addTask and removeTasks functions.

Installed Jest for testing.
Created test files for addTask and removeTask functions.
Add Mock functions for Local Storage and DOM.
Updated add&removeTest file to test the actual functions.
Fixed Linters

@osamaashraf6
We appreciate the time taken to go through this project.


updated names from pets to people and for fun because....the force

Codecov Report

Merging #103 (e31113f) into main (d2f5846) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #103   +/-   ##
=======================================
  Coverage   94.15%   94.15%
=======================================
  Files           5        5
  Lines         342      342
=======================================
  Hits          322      322
  Misses         20       20

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 d2f5846...e31113f. Read the comment docs.


[#2330] Map based spatial coverage editing for file metadata

Adds coverage map widget for selecting coordinates in file metadata.

@dtarb @aphelionz @horsburgh This can be tested at https://park.hydroshare.org
Waiting for approval on solution to start code review.

This code is ready for review now.

@pkdash Can you review this? If not I can.

Done fixing merge conflicts.

Build finished.

Build finished.

Build finished.

Build finished.

@Maurier please fix the failing tests.  Once tests pass @hyi can review per discussion on teleconference.

Build finished.

Build finished.

Build finished.

@pkdash, @aphelionz The tests have passed and the code is ready for review.


Fix for #107

Based on feedback/hints in #107 and some head-bashing, generated this PR, with which the full functionality of the Daikin AC units via Niko is avaiable in HA.

Just to note on the .exception vs .error - it seems the error I previously reported is related to the energy component; disabling the device as recommended in the README removes the error, but for reference, with .exception, a fuller trace is:
2024-01-11 09:37:19.380 ERROR (Thread-5 (_thread_main)) [custom_components.nhc2.nhccoco.coco] 'NoneType' object has no attribute 'loop'
Traceback (most recent call last):
  File "/config/custom_components/nhc2/nhccoco/coco.py", line 150, in _on_message
    self._device_instances[device[MQTT_DATA_PARAMS_DEVICES_UUID]].on_change(topic, device)
  File "/config/custom_components/nhc2/nhccoco/devices/generic_energyhome.py", line 76, in on_change
    callback()
  File "/config/custom_components/nhc2/entities/generic_energyhome_electrical_power_to_grid.py", line 53, in on_change
    self.schedule_update_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1157, in schedule_update_ha_state
    self.hass.loop.call_soon_threadsafe(self.async_write_ha_state)
    ^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'loop'`

Addressed the outstanding review comments in 7b8c47c

Oops, apologies - f0e0398 has those removed

Thanks for your patience!


Remove **/__*__/** from ignore

Describe the bug
I am setting up a template for future projects in our collection repo - the folder is called __template__ as we always do with template repo's
After digging for ours I find the following line in your code, which most definitely will explain why I cannot get the routes to load:
https://github.com/hannoeru/vite-plugin-pages/blob/885484f30eec4feb50a09d44df32805e5d897fbd/src/files.ts#L8-L10
Is there a way to remove this from the ignore, or override it please?
Reproduction
Can't really set one up as it's due to folder name down the path
System Info
System:
    OS: Linux 5.15 Ubuntu 20.04.4 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i7-6820HK CPU @ 2.70GHz
    Memory: 9.77 GB / 23.47 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 16.16.0 - ~/n/bin/node
    Yarn: 1.22.19 - ~/n/bin/yarn
    npm: 8.18.0 - ~/n/bin/npm
  Browsers:
    Firefox: 103.0

Used Package Manager
npm
Validations

[X] Follow the Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A please open a GitHub Discussion.
[X] The provided reproduction is a minimal reproducible example of the bug.

Is it released also? Just asking to be sure because then I can remove the bash file I used to change it inside the library

Not yet, wait next release.


Documentation Engineering a.k.a. Reliable Up-To-Date Docs

Documentation Engineering
Summary
This project approaches the problem of documentation development by approximating it to the problems in source code development and addressing it with software and process engineering. It provides a high level of automation and software support, comparable to the one in a best practice, complex end-to-end development processes, particularly in OSS projects.
In a nutshell it:

fuses the documentation process into the software development process
utilises the same process automation infrastructure - CICD, containers, bots, automatic PR checks
supports separation of concerns between documentation providers (domain experts creating content) and documentation publishers (experts in design and delivery of documentation content)
frees capacity for creative work, automating procedural tasks in the documentation process from development of material to publishing it on a publishing channel
supports complex, multicomponent projects spread across multiple repositories that have established end-to-end processes

Motivation
Documentation development and delivery is traditionally seen as a separate domain that eventually has cross points with software in the production process. But paradigm shifts in software engineering like agile processes and design thinking bring closer the previously distinct roles in the process and they start to exchange and adopt process models and tools in a more unified approach. That is particularly visible in open source projects, where dynamism and collaboration but also the "do-more-with-less" approach are survival factors. These are some reasons why we see a new paradigm at documentation development called  documentation-as-code making its way more and more and particularly in open source and especially in complex projects.
Often this approach is described as keeping your documentation close to code and using the same tools as developers to work on it. While this is true there is a lot between the lines here. Considering that this means having a docs folder with markdowns in your repo and using git to check in and out and pull requests to collaborate over changes is a good start, but it is almost certainly an oversimplification of the potential of the documentation-as-code paradigm. It wouldn't bring significant benefits to a complex projects with CICD-orchestrated automatic processes, consisting of multiple repositories, each being a component that needs documentation, like Gardener or Kubernetes for example. In fact most claims for implementation of documentation-as-a-code in OSS projects that we see stop short at the tool support in the initial development material phase on a per repo basis. When documentation material moves close to code for good, and there are multiple repositories to consider, we face a distinct issue. How the documentation content from multiple repositories can be aggregated in a consistent, publishable  documentation bundle and qualify it. And then how to release and deploy documentation with software releases, considering product and component versions.
Applying the documentation-as-code paradigm implies a high degree of automation and software support, comparable to the one in a development process, which is a software engineering problem. In fact, the documentation development process resembles significantly the software development process in that way. Coming from this angle, this project addresses the documentation process problems with software engineering means not only focusing on the initial phase of documentation development but all the way along the whole process down to a delivery on a publishing channel.

Proposal
The proposal is to define the practices and deliver the software necessary to support a documentation process that shares the same infrastructure as software development process for multicomponent, multi-repository, GitHub-based projects, that can be used to deliver documentation on multiple publish channels from the same source.
Formally such documentation process can look like this:

Or if we apply this concept to the delivery of documentation by the Gardener OSS project:

Material Contribution
A documentation material contribution, being new material or existing one pulled for update, is the usual  GitHub-driven process with change commits, collaboration and reviews until a final agreement, known from contributing code.
Developing documentation on this stage can be supported by local editor, containerized build and preview of changes, or the same provided by an online CMS, such as netlify CMS. Running the same build as CICD and previewing changes as they will be seen by end users on a publish channel, or at least the documentation bundle that will be transformed for that, introduces a transparency that significantly reduces the turntime for a change.
Introducing formal enforcement of guidelines such as markdown formatter, or early and formal quality check, including dead links, spelling and expression checks is a significant improvement reducing review times and removing the burden of trivial checks.
Finally, merging documentation changes to a repository is subject to automatic formal checks that guard the quality of the contributed material. These are mostly the same quality checks that are available to be run while developing material.
Build
Building a documentation bundle has several stages. The common one is the initial - aggregating source content into a desired structure. The next build stages depend on the purpose of the bundle and the publishing technology and may require technology-specific transformation. Therefore they can be customized as needed for the specific use-case.
Building starts from a manifest file that describes the desired documentation bundle and its structure. It is convenient to manage this file in a repository dedicated to documentation or a root component of the project.
The product of the build is a documentation bundle publishable on a particular platform.
Continuous Integration and Continuous Deploy (CICD)
Projects that have CICD setup to orchestrate change management will have the documentation reusing it for coherent release and deploy cycles. When a documentation change is merge a CICD job is triggered to build the documentation bundle and run quality checks. Upon release the build result, that is the documentation bundle and source are added to the release artifacts. Continuous deploy uses those artifacts to publish them on a target publish channel.
There can be more than one publishing channel and normally that will require also different documentation bundle possibly structured precisely for that channel and optionally built for a specific publishing platform. Publishing on each channel can be performed by dedicated CICD pipelines.
Summary of topics
The project supports documentation development process similar to software development contributing software support in the following directions:

Material change contribution

Sandboxed build
Change Previews
Quality and compliance control
Pull requests quality control gardener/docs-toolbelt#8

Build documentation bundle  gardener/docforge#23

Pull documentation sources from multiple locations and storage system types (incl. GitHub and file system) as instructed by a documentation bundle manifest
Reconcile linked resources in documents - download as appropriate and rewrite links  gardener/docforge#7
Applying automatic processing on source documents, including for a particular build system (e.g. Hugo) gardener/docforge#20

CICD integration guidelines

Validation Scenarios
OSS project
The scenario validates the extremely popular among OSS project process organization with GitHub-based dev process, CICD integration, build with Hugo, publish on GitHub Pages. The project to validate it will be Gardener and the expected result is versioned documentation bundles published at https://gardener.cloud upon Gardener release.
Internal project
The scenario validates the versatility of the concept and the implementation in a different environment and process. For example, publishing documentation in a DITA system. A stakeholder with more concrete scenario is to be defined.
Definition of DONE

[ ] Validation scenarios accomplished
[ ]  Documented
Documentation for adopters, and developers
[ ]  Tested
75%+ avg code coverage with tests, integration tests
[ ] Stable
The project concepts and core implementations are stable enough to adopt and extend with new tools in the given scope without significant changes.

[ ] 1+ more alternative(s) to a supplied solution in the scope

most of the things are already done.
Others are not anymore in the backlog


Add cycle option to fzf

Hi,
First I'd like to say that this is a great plugin!
Could you please add the switch --cycle on line 58 of find_files.sh ?
Thanks

Thanks! I'll add the switch (or maybe a configuration option to pass additional flags such that everybody can tailor this command as they see fit) the next time I release an update!

Thank you!

Hey @shlomocarmeter, as of 0.0.19, this option is now the default. Thanks for the suggestion!

@tomrijndorp Thanks!


What about callbacks from gatt?

I am sorry but i can't find anything about GATT's callbacks like onConnection, onRecieve and etc. How to us it?

Ok, I don't need onConnect event because of coroutines, i just use it "synchronuously". But server can send me a messages sometimes and how should i get it?

The whole point of coroutines is to not pollute your code with routine callbacks. Or one of its points at least.
Also, I bet that by ""synchronously"", you meant "sequentially".
What are the messages sent from the server you are talking about? If it's notifications, this is already supported, you can find find all the documented functions you should need in the GattConnection interface.

Also, I bet that by ""synchronously"", you meant "sequentially".

@LouisCAD you right. English is not a native language for me...
 Should i get notifications like this:
//somewhere in my code
launch {
    while (true) {
        var notify = notifyChannel.recieve()
        //do something with notify.
    }
}

I think i begin to understand the main idea of corutines in BLE. I have a scenario:
connect
send data to characheristic AA
read data from AA
wait notify from BB
read BB
disconnect

i think i understand how to implement it with API
But what if i have a special characteristic CC that can send me a notify asyncronously at any time of my scenario? In my case this characteristic says about ERROR, and it sends me a ERROR-code, after that device waits for timeout and reboots. So it's very important to read CC in time to know the reason of reboot. How to read CC? I suppose i can't do it in any parallel coroutine

Also how to add events from UI to this chain? The only way i see now is to have a synchro context with some values, which my Main Coroutine will read.  But sounds not good. Can you suggest another aproach?

If notification are enabled on both devices for the target characteristic, yes, notifyChannel.receive() in a loop can work, but please, look at the openNotificationSubscription function

The only way i see for now is to have a synchro context with some values, which my Main Coroutine will read.

What do you mean by "synchro context" and "some values"? And what are you referring to exactly when you write "Main Coroutine"?

Ok , let me explain from the very begining.
I have a BLE device, that sends me some events (with notify as you mentioned). I understand how does GATT works (in basics), i've already made this BLE device and i got an application that is made with callbacks. And it works pretty well but...
I want to refactor my BLE code with your API (because i want to try Kotlin and modern aproaches) and i don't understand how to design my app properly.
I've got event-driven system. My BLE device can sand me various events time to time, so i have to catch them in separate infinite loop as we dicussed it before. But also i've got some events from UI, user can send cancel or something else to BLE device. So i should synchronise somehow UI thread and this loop. Also there is some buisness logic, like handshaking and validation between smartphone and BLE device (our special protocole).
Is it possible to do protocole, catch events from BLE and handle user's command (like "Cancel") at the same time without synchronization of contexts and Spaghetti code?
BTW proper and clear synchronisation is a main goal that i want to achieve with
Thank you for help anyway

You can launch child concurrent coroutines with… launch { }. If you want to cancel some running coroutine based on user action or whatever, you can call cancel() on the Job returned by launch, as usual with coroutines. I'd recommend to launch a coroutine for listening to notifications, and you can launch other coroutines if it makes sense for your use case.
Also, if you want to abstract technical details away, you can write an interface with suspending functions and regular functions if needed to, that you implement using this library. That may help making your code cleaner and more independent from the library used, which is at least one step farther from spaghetti code.
Does it make sense to you? Let me know how that works for you and your codebase :)

It really does thank you! Tomorrow i will try to do something with it.

Also for those who has similar beginner's questions as me i recommed this video:
https://www.youtube.com/watch?time_continue=2369&v=a3agLJQ6vt8
Speaker tells how to use coroutines with channels, how to syncronise content and so on. It was really helpfull for me.

So, i implemented everything i want with Channels
I've made bunch of channels, like
val eventAChannel : Channel<bool>
val eventBChannel : Channel<bool>
In main code, where i want to implement main functionality i do something like:
...
eventBChannel.receive() // We will wait here our event
doMyActions()
eventAChannel.receive()///
fooBar()
...

Channels are syncrhonised out of the box so i don't worry about concurency and other async stuff
Then eanywere in code i can send() anything and i will get everything i want
I like this aproach very much.

Thank you guys for this library!


Binary files (documentation no longer accurate)

The documentation reads as follows regarding handling binary files:
$ cp /etc/krb5/krb5.keytab > krb5.keytab
$ sops -e -o krb5.keytab
# an example of what this might result in:
$ head krb5.keytab

The -o flag is not usable. (Yields "flag provided but not defined: -o")
Also, the first line appears that either the command should be cat or the redirect should be eliminated. This line should probably read either
$ cp /etc/krb5/krb5.keytab krb5.keytab

or
$ cat /etc/krb5/krb5.keytab > krb5.keytab

Is it still possible to process binary files?

sops has recently released 3.9.0 that has updated their options - you should refer to their project for the documentation .
-o is deprecated
if you do not have rules setup in your .sops.yaml for the specified file, you'll probably need to use --input-type and --output-type appropriately.
The documentation here should be updated to reflect that.  If you have more changes I'm sure they would be welcome.

@sedlund: Thank you for the prompt, well-informed reply.
I generated a minor pull request with the documentation changes and am closing this issue.


Updating the building and testing steps within the README of the repo.

Updated the steps to be more accurate. Added some clarifying details from recent changes to the wiki: https://github.com/dotnet/corefxlab/wiki
cc @karelz, @dotnet/corefxlab-contrib, @adamsitnik, @MisinformedDNA

👍


When doing write operations, should create related entities as well

Currently, it is expected you create all your entities before writing the parent element.
This is bollocks and a really lazy design decision of mine 👎  I'm sorry ❤
What it should do is take your payload, check whether the target has any children, check the payload and write to all entities within the payload.
Child elements will be treated as such, in verb context:
POST, PUT, PATCH: child doesn't have an id property: just create the new entity.
POST, PUT, PATCH: child entity has an id property: find–update or create
POST: payload has no children, nothing happens
DELETE: noop

I'm pretty sure that the jsonapi module does most of this already 🤔

Note: This should be in core, in the handlers so all plugins are predictable.


Publish of 4.0.1-rc.1 to npm

As per title

At this point it's probably going to be easier to wait until 4.0.1 is released, at which point I will definitely remember to push it to NPM. Right now it's not a part of my release checklist, which is why I forgot it for 4.0.1-rc.1.


pino: option to disable the extension

It would be great if there was an option to disable the extension. During local development I do not want to use the extension.

Hi!
What kind of solution did you have in mind? For local development, you probably don't want to enable the New Relic agent either, and if you disable that from the newrelic.js config as detailed here, then log enriching with Pino will also be disabled.
Alternatively, you can also write your own code to look something like this
const enricher = process.env.NODE_ENV === 'development' ? function() {} : pino_enricher

If these two don't work for you, what would you like to have instead?

I'll assume the above suggestions solved the problem. If they haven't, we can reopen the issue.


Pixel Streaming in Unreal Engine 5.2

My team and I have been attempting to deploy an Unreal application that uses the most up-to-date version of the Unreal Engine (5.2 at the time of writing) in Azure.  Looking at the repository, it seems like the last time it was updated was for 4.27 a few years back.  Since then, there have been quite a few changes made to the engine.
I was wondering if there were plans to update this repository to support version 5.2 and beyond.  I also wanted to ask what changes were made here from Epic's Pixel Streaming Infrastructure repository to make it "Azure-ready" so we could make the necessary modifications ourselves if need be.
Thank you so much!

Hello @WilBlanchardPR, this repository is no longer being updated going forward, and the new feature work was put into Epic's Marketplace solution in Azure (https://azuremarketplace.microsoft.com/en-us/marketplace/apps/epicgames.unreal-pixel-streaming?tab=overview), but we kept this around for folks wanting to use Terraform instead of ARM. The Marketplace solution does support UE5 as the binary, but the web UI for Pixel Streaming is not updated to the latest 5.2. Customers are using UE5 with the Marketplace solution (a UE5 exe works). I believe the tweaks for this repo were also allowing UE5, though the nodejs UI/code was not updated to the latest UE5 code... just allows the UE5 exe to work (mostly the WindowsNoEditor name changed in UE5).

Hey @microsoftman, That link to the Azure Marketplace solution is no longer valid.  Is there a way to use pixelstreaming at scale with Azure using UE5.3 applications?

Hi @AMGI-Pipeline, Epic Games has taken down the Marketplace solution due to shifting priorities and being able to support it going forward; however, they did Open Source it here if you want to check it out:  https://github.com/ue4plugins/UnrealPixelStreamingOnAzure

@microsoftman, Thank you for the explanation and the link to the repo.


Update Oracle details

Updated Rinkeby testnet oracle details as mentioned in the docs.
This resolves #2

Thanks!
Can you add these to the helperconfig too?
Also, what's up with the submodule changes? Can you remove those?


Progress tracking issue for 1.0.7 release

Before the release

[ ] Do a fresh clone of the repository
[ ] Verify that index.php, SSI.php, install.php and upgrade.php have the correct CURRENT_VERSION and CACHE_STALE.
[ ] generate detailed-version.js:

run generate_detailed-version.php from the root directory
move the newly generated detailed-version.js out of the package directory
delete generate_detailed-version.php
note: generate_detailed-version.php will check that all the files changed during the preparation of the patch have the correct version number. The following git command is used by the script to obtain the list of files changed between two branches:

git log --name-only --pretty=oneline --full-index master..patch_1-0-x | grep -vE '^[0-9a-f]{40} ' | sort | uniq

[ ] commit detailed-version.js to gh-pages:

checkout the gh-pages branch (fetch the repository if necessary)
create a new branch
replace the file detailed-version.js with the one just generated
commit the changes
push online and send a PR to the ElkArte repository

[ ] create a pull request from the release branch (e.g. patch_1-0-x) to the master branch
[ ] Write a draft of the release announcement. It should consist of:

a general description of the release
a release notes document including the major changes since the previous version (for development versions like alpha, beta and RC is the previous dev version, for final versions is the previous stable version).
a known issues document listing the major issues affecting the release (i.e. bugs not critical enough to be blocker, but potentially annoying)

The following command helps writing the list of changes used in the release notes:
git log --pretty=format:'[*][bugfix] %s ([url=https://github.com/elkarte/Elkarte/commit/%h]ref[/url]).' --abbrev-commit

Packages creation check list:

[ ] Do a fresh clone of the repository
[ ] From the install directory, move the following files to the base directory:

Settings.php
Settings_bak.php
install.php
db_last_error.php
install_1-0_mysql.sql
install_1-0_postgresql.sql

[ ] remove the following files and directories:

.git
.gitattributes
.gitignore
.scrutinizer.yml
.travis.yml
CONTRIBUTING.md
DCO.txt
phpdoc.yml
README.md
docs
install
tests

[ ] create a package with the remaining files

Complete the release

[ ] Merge the pull request for the detailed-version.js update
[ ] Merge the pull request from the patch branch to the master branch
[ ] Create a new release at github using the announcement previously drafted, and attach the packed files
[ ] ...
[ ] Profit!!!

I remember I said there was a fix worth backporting, but I can't remember which one it is... :-\

Was it this one? https://github.com/elkarte/Elkarte/issues/1722

Yes!!
You are GREAT!!!
/me tracks the backport not to forget. LOL

If nothing else is left, I'd prepare the release for around the next weekend?

Since you opened a 1.0.8, I'd say yes !  Make sure we push the latest updates to the site for the tire kicking.   I'm going to be even less useful (yes it really possible even if inconceivable!) next week due to some commitments and stuff ...

Sure!
I had some personal issues in the latest few days, I'll update the site tomorrow and start preparing patches... and the release announcement.