ja: Make docs/concepts/security/pod-security-standards.md follow v1.19 of the original text

This is a Feature Request

What would you like to be added
Update docs/concepts/security/pod-security-standards.md to follow v1.19 of the original (English) text.
Why is this needed
content/ja/docs/concepts/security/pod-security-standards.md is outdated.
Comments
/language ja
/good-first-issue
File to update
https://github.com/kubernetes/website/tree/dev-1.19-ja.1/content/ja/docs/concepts/security/pod-security-standards.md
Original
https://github.com/kubernetes/website/tree/release-1.19/content/en/docs/concepts/security/pod-security-standards.md
diff between translated and v1.19
https://gist.github.com/df3b235f34e342165b6fdfd2d4ac7ccd
Note
Currently, we use dev-1.19-ja.1 branch. Please open a PR targeting the branch.
ref
https://kubernetes.io/ja/docs/contribute/localization/
If you have a question, feel free to ask us at slack.k8s.io #kubernetes-docs-ja channel.

/triage accepted

/aggisn

/assign

確認してみたのですが、すでにv1.19より新しいバージョンのドキュメントが #24961 で新規翻訳されていたため、この更新は必要なさそうでした。
/close

closeお願いします🙏

/close


Patient header UI update in Patient details page

Proposed Changes

Fixes #9376

Updated patient Header

Updated state value in demography tab

Updated tranfer labels to relevant colours

@ohcnetwork/care-fe-code-reviewers
Merge Checklist

[ ] Add specs that demonstrate bug / test a new feature.
[ ] Update product documentation.
[ ] Ensure that UI text is kept in I18n files.
[ ] Prep screenshot or demo video for changelog entry, and attach it to issue.
[ ] Request for Peer Reviews
[ ] Completion of QA

Summary by CodeRabbit
Summary by CodeRabbit

New Features

Updated language for improved clarity in patient management and healthcare procedures.
Enhanced layout for displaying patient information in the Patient Home component, organizing details about facility, treating doctor, and assigned volunteer.
Introduced new icon options for the Badge component to enhance visual representation.
Added authorization checks to the Button component, ensuring proper access control.

Bug Fixes

Corrected spelling in patient-related text strings.
Improved data retrieval for patient state information.

Documentation

Updated text strings for consistency and user-friendliness.
Added new strings to enhance functionality related to volunteer assignments.

@Jacobjeevan i replaced chip with badge . can you once look into it

@rithviknishad i have done the changes

@rithviknishad i have done changes. can you once look into it.

Hey @Jacobjeevan @rithviknishad can you please update the review of this PR

@Mahendar0701 clear the merge conflict

@nihal467 , @rithviknishad @Jacobjeevan with the latest merges in care.ohc.network, the actions buttons in patient details page is looking inconsistent.This PR will resolve it.

Should i raise a PR immediately to correct the design of buttons if this PR takes time to get merged??

@rithviknishad can you please update review and let me know if any changes are required.

no longer relevant in new architecture


Build improvements

Commits: 16cef4a0e79126e3cb5c8be9ed16b550db340e9b, 59ad6ef0006d0fc9e57dfd08f90d911d1ee00761, c8327da1f153f2a6ab0ccb9c75c0b675cb9c5c5

During tsc --build and other scenarios where we would do existence check as well as stat which resulted in two stat calls, we just check modified time

Commits: cb7aca3ad0b6e1a3226eea62811922876df3541a

In tsc --build while determining upto date ness status, we now check if referenced projects have errors so that we dont need to go through input and output timestamps in that case

Commits: 89d2d4c2d184cc95b49c3c66e05622f65b02383e

During watch especially during polling file watch and in some scenarios during native file-system based watch we stat on files and that time is now passed through as part of file watcher event so tsc --build can use it.

Commits: 6e0c91650fee5c0f0ece17f6624bb94a0934a9e9

Apart from this in watch mode we save timestamps for all the watched files. These get updated through watcher event callback or are repopulated if watcher event didn't query the time. So if 2 files changed out of 20 input files then at max we will requery timestamps for those two files (if watch callback didn't already give us updated time)
Fixes #45082

Commits: 7cb0f40f071cb81c362cda46dbf42ec47f32b362, 1a8abacee9473d98fa8872ec91edfe109e0eac7f, 59f2b5c078f249a856f1e83c17e36f84a1b0812b, dc21283cac5690db49ed1699778266ebd182abba, 5bccee86ada6c48706290561e9292e6c1d3ed42c,

If its incremental build, tsbuildInfo alone determines upto date ness of the build. For this we now store changeFileSet, dtsChangeTime and emitSignatures for the output files in the buildInfo when in multi file emit scenario.
We store fileVersions, outSignature, dtsChangeTime in single file output scenario.
The emitSignatures and outSignature are the d.ts hash of the output that last changed to the disk. Since any composite project already has declaration as must we can store this easily and save having to read files on emit to see if the d.ts file has changed. This makes sure that whether you are in tsc --build or tsc --build --watch mode the state is persisted so we know exactly if we need to really build or just update timestamps.
In case of multi file emit scenario, tsbuildinfo timestamp, changeFileSet and errors in the buildInfo determine whether we need to rebuild project or not. This way we dont have to update timestamps for anything except buildInfo when thing appear uptodate but timestamp doesnt reflect that. (eg upsteam project changed but didnt change d.ts files)
In case of single file emit scenario, tsbuildInfo timestamp is enough because we cant emit tsbuildinfo without emitting other output files.
Earlier we checked input file timestamps and found newest file, now in case of incremental build, we first check buildInfo as missing it, or errors is clear indication of requiring rebuild. After that we check each input file timestamp against buildInfo so that the number of checks can be smaller.
Fixes #46677

Commits: 2f2e370d6a7998d324fc63a44550a47e6b1470db, fcf07f81beb14219a132d5c58970a1a0d3ef1699, 15fe24e744faa476183111eba659573c7a7014f6

In non incremental project, we still need to update timestamps for output files that didnt change as there is no other way to tell if project is upto date or not. But we dont need to read d.ts files to see if .d.ts files have chaned since these projects cannot be referenced by other projects. (composite also means incremental which is must for referenced proejcts)

Commits: 6198fa38778a89b179f3f62d99c7931895bf6f3e,

With so much depending on buildInfo, it is now cached and passed through emit as additional data so we dont have to reparse the json or identify which file is tsbuildinfo

Commits: 62c687be8401c0595580db50ca78bc0cfe3613e3

We store the hash of files written in bundle emit to ensure that when we try to manipulate the sources for pseudo update (because d.ts of referenced project didnt change so only prepends need to concatenated in right order), we can check if file hasnt changed. This is now needed because bundle buildInfo also stores .d.ts change time and if incremental was toggled between compilations we might use wrong file text and get incorrect d.ts Look at 62c687be8401c0595580db50ca78bc0cfe3613e3 for details and https://github.com/microsoft/TypeScript/commit/62c687be8401c0595580db50ca78bc0cfe3613e3#diff-6b83fa9d09e38f88c61b24a70aec8668c68e0d8322e8404dbd85c90120f14eeeL1016 shows test that failed without this change

Commits: 4fb6773b78ca63ea289019056bab41f7accb9132

We also cache output file timestamps so that we dont have to requery as we are the one who write those files.

Commits: 0f7903de42fd3607e091113837c3b0a07147013c, 437619eb7825c0e3c4c725e001b29cd060cfdd77

This also has some refactoring of BuilderState, BuilderProgramState etc structures so its correctly reflected.
With this change we also have flags for emitting compiler option key into the buildInfo based on multi file or single file emit

Commits: e6a3ee84cafa65db5fb94428fddd05f64507f410

tsc --build --force now doesnt query input file stamps (it never did query output file stamps)

Commits: b32d2ebad2d7807eeae369c3b315c1158cfae9c9

In builder, earlier we use to copy too many structures as part of backup which is internal method to ensure we can restore state if declaration emit fails. So now we are only storing emit state instead of reference map etc

Commits: 303824eee922dd1e801ba0bec1fa09f07a0e936e

Other change in builder is that earlier we use to maintain new delta of changes for affected files new signatures as well as new exported modules map. We use to commit it once all the affected files for the changed file is handled. (This was due to our API usage where we could cancel the operations in between and would still need to be able to reuse the state as much as possible). Now i have changed this to instead maintain copy of old signatures and old export map so that all we do is clear these these maps instead of having iterate through each and update them into the latest copy on commit

Commits: 28a9ff34a724ae7eeb2bc9afa17000d6002cfa11

During tsc --build if file timestamp is changed but its text has not, we read the file and do pseudo update (only in incremental build).

Commits: e4e66726098201f38f5e8908a538e7a506f15efd

Delete only tsbuildinfo instead of all output files when doing clean on incremental project

Here are the numbers from run on solution with large (1994) number of projects.
| main | PR | Delta | % | Projects Built | Timestamps Updated | Total projects
-- | -- | -- | -- | -- | -- | -- | --
tsc -b | 120.21 | 93.38 | -26.83 | -22.32% | 255 | 0 | 1994
tsc -b (Fix one error) | 39.13 | 31.50 | -7.63 | -19.50% | 22 | 0 | 1994
tsc -b (Fix multiple errors in files) | 43.96 | 35.74 | -8.22 | -18.70% | 43 | 0 | 1994
tsc -b -w | 373.25 | 326.22 | -47.03 | -12.60% | 484 | 0 | 1994
Fix error | 19.69 | 17.76 | -1.93 | -9.80% | 11 | 0 | 1994
Fix error | 61.48 | 60.71 | -0.77 | -1.25% | 66 | 0 | 1994
Fix error | 11.53 | 8.97 | -2.56 | -22.20% | 3 | 0 | 1994
Fix error | 7.19 | 6.18 | -1.01 | -14.05% | 2 | 0 | 1994
tsc -b | 620.07 | 480.23 | -139.84 | -22.55% | 796 | 0 | 1994
tsc -b No change | 26.78 | 19.59 | -7.20 | -26.87% | 6 | 0 | 1994
Local Change | 36.70 | 20.14 | -16.57 | -45.13% | 7 | 477 | 1994
D.ts change Average | 74.60 | 54.47 | -20.12 | -26.98% | 138 | 346 | 1994
tsc -b -w | 630.56 | 557.41 | -73.15 | -11.60% | 796 | 0 | 1994
Local Change | 8.98 | 7.52 | -1.46 | -16.21% | 5 | 131 | 1994
D.ts change Average | 89.21 | 70.56 | -18.65 | -20.90% | 136 | 133 | 1994
tsc -b -w no change | 37.58 | 26.37 | -11.21 | -29.83% | 6 | 0 | 1994

@typescript-bot pack this

@typescript-bot perf test this

@typescript-bot pack this

@typescript-bot pack this

Initial run shows: build time for big solution changing from 258.54s to 169.24s and similar changes during watch time. Need to analyze further

@typescript-bot pack this

@typescript-bot pack this

@amcasey @andrewbranch i have highlighted important commits and the change in the description and also have left some comments during the change. Let me know if you need more details.
This PR is basically aggregation of lot of changes that mostly needs to be together.. So minor refactoring can be a separate PR but rest needs to be together for everything to work so cant make this into smaller PR.

@sheetalkamat That table's great!  When you ran those scenarios, did you do any checks to determine whether the output was the same as before?  Also, do you have a similar (or simpler) table for compiling TypeScript itself?

I think this might have caused a regression. In my project, when I introduce errors and build with tsc -p, I get errors, as expected. When I build with tsc --build, it exits very quickly, and shows no errors.
λ ./tools/tvui/node_modules/.bin/tsc -p packages/tsconfig.json
# ... expected error messages omitted

Found 3 errors in 3 files.

Errors  Files
     1  node_modules/relay-hooks/lib/RelayHooksTypes.d.ts:56
     1  packages/@tvui/fx2-transition/src/utils.tsx:173
     1  packages/@tvui/redux/testing/unitTestingEnhancer.ts:8

tvui on  nth/ts-4.8 [!⇡] via  v16.16.0 took 10s

λ time ./tools/tvui/node_modules/.bin/tsc --build packages/tsconfig.json

________________________________________________________
Executed in  523.05 millis    fish           external
   usr time  413.25 millis   47.00 micros  413.20 millis
   sys time  188.29 millis  588.00 micros  187.70 millis

--build does seem to be faster, but perhaps it's so fast that it's not doing any work. :smile:

@NickHeiner

I'm happy to open a new issue for this if that's preferable.

New issue is definitively better, check if there is no similar issue.
If you have a standalone minimal project to reproduce it will be gold for maintainers :hugs:
Thank you!


⚠ Processors has degraded performance

In 836f8d2, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 54 ms

Resolved: Processors performance has improved in 2b3aa61.


Replace clap with lexopt in mls_validation_service

Clap is a huge dependency with lots of different features used by mls_validation_service to parse only 2 command line flags. We can instead use lexopt which is a much smaller dependency that achieves the same ergonomics but without the compile time

Love it


options don't work properly

Hi, I have these options
    options: {
        e: ["NODE_ENV=development", "FOO=bar"],
        p: ['4444:4444'],
        shmSize: '2g',
        rm: true
    }

when running wdio they get translated like this:
[... ]--rm -e=NODE_ENV=development -e=FOO=bar -p=4444:4444 --shm-size=2g

not sure if I'm doing something wrong, I'm sure i saw them working earlier.
    "wdio-docker-service": "^2.1.5-rc.0"

This is a new way of serialization. Does this break anything?

From: Sathia<EMAIL_ADDRESS>Sent: Friday, January 3, 2020 1:09:27 PM
To: stsvilik/wdio-docker-service<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [stsvilik/wdio-docker-service] options don't work properly (#66)
Hi, I have these options
options: {
    e: ["NODE_ENV=development", "FOO=bar"],
    p: ['4444:4444'],
    shmSize: '2g',
    rm: true
}

when running wdio they get translated like this:
[... ]--rm -e=NODE_ENV=development -e=FOO=bar -p=4444:4444 --shm-size=2g
not sure if I'm doing something wrong, I'm sure i saw them working earlier.
"wdio-docker-service": "^2.1.5-rc.0"

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/stsvilik/wdio-docker-service/issues/66?email_source=notifications&email_token=AABC3UE2PZOQSRWE44HHC4DQ355NPA5CNFSM4KCQIYEKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ID5R3DA, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AABC3UELFP5XAXGBNZSQLFDQ355NPANCNFSM4KCQIYEA.

well, yes, i can't set a proxy, if docker receives -e=https_proxy=http://proxy.com:1234  it is not recognised

Different serialization should not break anything. Here is what I ran and it works fine:
$ docker run -it -e=https_proxy=http://proxy.com:1234 nginx /bin/bash
root@227011abb15b:/# printenv
HOSTNAME=227011abb15b
NJS_VERSION=<IP_ADDRESS>.2.7-1~stretch
NGINX_VERSION=1.15.8-1~stretch
PWD=/
HOME=/root
https_proxy=http://proxy.com:1234
TERM=xterm
SHLVL=1
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
_=/usr/bin/printenv
root@227011abb15b:/#

@sathio could you try new RC (2.1.5-rc.1) I pushed out and let me know if that works?

hi, i was in a weird state of mind when I was debugging the parser,  after hours of wrong tests. I'm sorry it seems it's indeed fine. I was carried away by the weird -e=FOO=bar syntax. thanks for your work


Updating python version to including <=3.13

Allow for people to use with more recent version of python

Thanks for adding this @joaomdmoura. We were already planning to upgrade it soon.
I will merge this PR and will update the poetry.lock file in a follow up.


Clicking header renders launch page

Made the changes specified in the issue. Now clicking the header (GSoC Analyser) rerenders the launch page. #37

A good start, but I have a few concerns. The current changes do not clear the input properly. What seems a better approach to me is to create an initialState object in the AdvancedSearch component. Create a resetSearchState function in the AdvancedSearch component which sets all the states to the initial state object. That will ensure that all the values are being reset properly. Also note that you will have to invoke the function from the parent component, i.e the Home component. There are pretty good answers on StackOverflow regarding invoking a child component function from a parent. Please refer to that if needed.
This shall be the body of reRenderLauncher:
const reRenderLauncher = () => {
    resetSearchState();
    setValidList([]);
    setDisplayLauncher(true);
}

@Sparsh1212
Alright, will work on it.

Hey @Sparsh1212 !
I made the changes you requested and it works!! Please take a look.
Also, I had a little trouble with merging the changes made by others(into your master branch) into my issue#37 branch.
It would be great if you could explain the correct method to do that.

Hey @Sparsh1212 ! I made the changes you requested and it works!! Please take a look.
Also, I had a little trouble with merging the changes made by others(into your master branch) into my issue#37 branch. It would be great if you could explain the correct method to do that.

Ahh, I see. This is because you are facing merge conflicts. I'd suggest reading or watching some tutorials on resolving merge conflicts. Let me know if you are not able to find a relevant resource.

Ok, will make the changes.

Have made changes. Please review @Sparsh1212

LGTM!


[RFC] Add conversion between qcodes legacy DataSet and xarray format

Changes proposed in this pull request:

Add conversion methods between the QCoDeS legacy dataset and xarray Dataset

A minimal example:
from qcodes.tests.legacy.data_mocks import DataSet1D, DataSet2D
qd = DataSet1D()
xds = qd.to_xarray()
print(xds)
qds = DataSet.from_xarray(xds)

@jenshnielsen The goal of this PR is to allow conversion between the easy cases (e.g. 1D, 2D). Since the two datasets have slightly different formats, we do not cover all cases. Can you comment on whether this functionality can be added to qcodes and if the structure of the PR is good?

@peendebak Thanks, I will have a look. Happy to merge this to QCoDeS. I have edited the description to clarify that this is about the legacy data.dataset and not the current QCoDeS dataset.

@astafan8 I addressed the comments, and added some more tests. The build seems to be failing due to a general error.

The build seems to be failing due to a general error.

@peendebak  what do you mean with "general error"? the error here https://github.com/QCoDeS/Qcodes/pull/2938/checks?check_run_id=2399670141 seems to be a typo in the assert method call:
>       self.asserEqual(qd.default_parameter_array().shape, xarray_dataset.tmin.shape)
E       AttributeError: 'TestDataSet' object has no attribute 'asserEqual'

it should be assertEqual, with "t" :)


Item Conduits don't connect to TE Machines

The Item Conduits don't connect to TE Machines.
I'm using the latest EnderIO version (EnderIO-1.7.10-<IP_ADDRESS>5) and the latest TE (ThermalExpansion-[1.7.10]4.0.0B8-23)
Item Conduit (is NOT disabled):

GUI showing only Energy Conduit:

Have you tried picking up the machine and placing it back down? I've noticed if you put the pipe down after it doesn't actually update the connection so placing the TE machine back down seems to link it back up for me.

I tried, also I broke the Item Conduit and placed it again. Also I tried to place only a Item Conduit without the Energy Conduit, still no connection. After some testing it worked again. Don't know why it didn't work for me in the first time.
Thanks for your time and help!


How-to change the number of classes?

Yes, I know, really close to "Why can't I change the network architecture at runtime?", the very first Deep Learning question in FAQ section... but I'm asking some help as well. I think DLIB is great to quiclky develop tools for classification: today digits, tomorrow letters or shapes. But today 10 classes, tomorrow 24 or whatelse. I really need to have a parametrized number of classes because I want to release just one tool. That said, far from asking to change anything in DLIB architecture, could someone give me some hints (links, literature, tutorials) about those "compile time constructs in C++ you can use to enumerate network architectures (e.g. loop over filter widths) if you really wanted to do so."? Thank you very much.
Michele.

You can change the number of classes at runtime, so long as you haven't allocated the tensor to the corresponding layers (which I am guessing that they most likely are fc or con.
Let me give you an example:
https://github.com/davisking/dlib/blob/c7062aa3631ba4912255a9bcc0563d404d3bdd5d/examples/dnn_introduction_ex.cpp#L71-L78
You can change the number of outputs of the fc layer by doing:
long num_outputs = 42;
net_type net;
net.subnet().layer_details().set_num_outputs(42);

The same goes for con layers, there's even an example that does it:
https://github.com/davisking/dlib/blob/c7062aa3631ba4912255a9bcc0563d404d3bdd5d/examples/dnn_mmod_train_find_cars_ex.cpp#L283
And, if you are loading a pretrained network, this example shows how to do it:
https://github.com/davisking/dlib/blob/c7062aa3631ba4912255a9bcc0563d404d3bdd5d/examples/dnn_introduction3_ex.cpp#L76-L96
I hope this is helpful.

Thank you @arrufat, quick and neat... shame on me, it was so simple...

@ilChelo, great! Feel free to close the issue if you don't have any more questions.

Bye!


Heterogeneous data in a column is not cast to a common type

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 20.04
Modin version (modin.__version__): f74eec3b2c807d13721d367f62ee3ba18dcd0ba7
Python version: 3.8.10
Code we can use to reproduce:

import modin.pandas as pd
import pandas
from modin.config import NPartitions

NPartitions.put(4)

temp = pandas.DataFrame([1, 2, 3, 4]*32, columns=["col1"])
temp.to_csv("temp.csv", index=False)
df = pd.read_csv("temp.csv", header=None, names=["col1"])
df2 = pandas.read_csv("temp.csv", header=None, names=["col1"])

print(df, "\n\n", df2)
from modin.pandas.test.utils import df_equals
df_equals(df, df2)

Describe the problem

In the first partition, the numbers remain as strings, in the rest partitions they are already python ints. In the case of pandas, all values in the column are defined as python strings.
This example may turn out to be too artificial, but the same problem remains in the case when float numbers are present in the column with ints.
Source code / logs

[129 rows x 1 columns]
Traceback (most recent call last):
  File "test.py", line 14, in <module>
    df_equals(df, df2)
  File "modin/pandas/test/utils.py", line 527, in df_equals
    assert_frame_equal(
  File "miniconda3/envs/modin/lib/python3.8/site-packages/pandas/_testing/asserters.py", line 1308, in assert_frame_equal
    assert_series_equal(
  File "miniconda3/envs/modin/lib/python3.8/site-packages/pandas/_testing/asserters.py", line 1077, in assert_series_equal
    _testing.assert_almost_equal(
  File "pandas/_libs/testing.pyx", line 53, in pandas._libs.testing.assert_almost_equal
  File "pandas/_libs/testing.pyx", line 168, in pandas._libs.testing.assert_almost_equal
  File "miniconda3/envs/modin/lib/python3.8/site-packages/pandas/_testing/asserters.py", line 665, in raise_assert_detail
    raise AssertionError(msg)
AssertionError: DataFrame.iloc[:, 0] (column name="col1") are different

DataFrame.iloc[:, 0] (column name="col1") values are different (75.1938 %)
[index]: [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, ...]
[left]:  [col1, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, ...]
[right]: [col1, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, 4, 1, 2, 3, ...]

cc @YarShev

Related to https://github.com/modin-project/modin/issues/3278.


ResourceHandler: Always add version

Based on this ticket reported to PF: https://github.com/primefaces/primefaces/issues/6083
Modify the PrimeExt ResourceHandler to always add the extension version to URL's for cache busting and change it from v= to e= for extensions.
So for example this URL now becomes.
/primeext-showcase/javax.faces.resource/primeicons/primeicons.css.jsf?ln=primefaces&v=8.0&e=8.0.4
With the url displaying both versions ?ln=primefaces&v=8.0&e=8.0.4  This way it differentiates the  two versions and it will cache bust if you update either PF or PF Extensions.

I have tested this successfully with the theme switcher in PF Showcase and PFE Showcase and no issue by doing this.


Focus seems wrong when opening analysis tab

The analysis tab claims you can add analyses using shift+enter but at least on Safari it seems impossible to get the focus of shift+enter outside the model notebook.

Thanks for the report. This is a known issue but it's good to have it recorded. In fact, the reported behavior is currently hard-coded due to the lack of frontend infrastructure for managing focus across different panes.
I'll create a separate issue to track that. I'm going to remove the "good first issue" label because unfortunately I don't expect that getting this right will be straightforward.


[BUG] Training Error

Description
After providing human feedback on an Agent answer, KeyError is thrown.
Steps to Reproduce
=====
Please provide feedback on the Final Result and the Agent's actions. Respond with 'looks good' or a similar phrase when you're satisfied.
=====
looks great
Human feedback:  looks great
Expected behavior
continue to the next task or exit successfully if training is complete.
Screenshots/Code snippets
=====
Please provide feedback on the Final Result and the Agent's actions. Respond with 'looks good' or a similar phrase when you're satisfied.
=====
looks great
Human feedback:  looks great
Traceback (most recent call last):
File "~/Developer/CrewAI/job_application_crew/src/job_application_crew/main.py", line 40, in train
JobApplicationCrew().crew().train(n_iterations=int(sys.argv[1]), filename=sys.argv[2], inputs=inputs)
File "~/Developer/CrewAI/job_application_crew/.venv/lib/python3.12/site-packages/crewai/crew.py", line 504, in train
result = TaskEvaluator(agent).evaluate_training_data(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "~/Developer/CrewAI/job_application_crew/.venv/lib/python3.12/site-packages/crewai/utilities/evaluators/task_evaluator.py", line 112, in evaluate_training_data
f"Improved Output:\n{data['improved_output']}\n\n"
~~~~^^^^^^^^^^^^^^^^^^^
KeyError: 'improved_output'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "~/Developer/CrewAI/job_application_crew/.venv/bin/train", line 8, in
sys.exit(train())
^^^^^^^
File "~/Developer/CrewAI/job_application_crew/src/job_application_crew/main.py", line 43, in train
raise Exception(f"An error occurred while training the crew: {e}")
Exception: An error occurred while training the crew: 'improved_output'
An error occurred while training the crew: Command '['uv', 'run', 'train', '1', 'training_data.pkl']' returned non-zero exit status 1.
Operating System
macOS Sonoma
Python Version
3.12
crewAI Version
0.86.0
crewAI Tools Version
0.17.0
Virtual Environment
Venv
Evidence
Traceback (most recent call last):
File "~/Developer/CrewAI/job_application_crew/src/job_application_crew/main.py", line 40, in train
JobApplicationCrew().crew().train(n_iterations=int(sys.argv[1]), filename=sys.argv[2], inputs=inputs)
File "~/Developer/CrewAI/job_application_crew/.venv/lib/python3.12/site-packages/crewai/crew.py", line 504, in train
result = TaskEvaluator(agent).evaluate_training_data(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "~/Developer/CrewAI/job_application_crew/.venv/lib/python3.12/site-packages/crewai/utilities/evaluators/task_evaluator.py", line 112, in evaluate_training_data
f"Improved Output:\n{data['improved_output']}\n\n"
~~~~^^^^^^^^^^^^^^^^^^^
KeyError: 'improved_output'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "~/Developer/CrewAI/job_application_crew/.venv/bin/train", line 8, in
sys.exit(train())
^^^^^^^
File "~/Developer/CrewAI/job_application_crew/src/job_application_crew/main.py", line 43, in train
raise Exception(f"An error occurred while training the crew: {e}")
Exception: An error occurred while training the crew: 'improved_output'
An error occurred while training the crew: Command '['uv', 'run', 'train', '1', 'training_data.pkl']' returned non-zero exit status 1.
Possible Solution
None
Additional context
doesn't matter how many training iterations I choose, this error happens every time I try to train this crew. Crew project was created using crewai create crew xxx from cli.
Not sure if it's related to this defect, but the training does not pause for human feedback for each task when async_execution=True

looks to be same issue as https://github.com/crewAIInc/crewAI/issues/1353#issue-2549398032


fix: pass initConfig to insertionMethod

defaultInsertionMethod checks for insertionMethod string to determine if it should append or prepend styles in the head: https://github.com/modulz/stitches/blob/e0a99d32005657a839d94784dab795413eb50eac/packages/core/src/defaultInsertionMethod.js#L12. However the config object doesn't have the insertionMethod prop, so it's impossible to overwrite the default prepend behavior with append. The solution is to pass initConfig.

@jonathantneal thanks for reviewing! Would really appreciate if you could merge this and https://github.com/modulz/stitches/pull/551 and make a patch release 0.1.6 if that's possible.

Yes, a patch release will come this morning. I want to be sure that we want to pass initConfig and not mix insertionMethod into config instead.


S3 Expires top level output member should be a string instead timestamp

aws/aws-sdk-go@5bdeab7
internal id: 176722195

Released in https://github.com/awslabs/aws-sdk-swift/releases/tag/0.6.0, closing as completed.


Support selecting a pdf version for the output

I needed to trim PDFs with specific version requirements on write. Not sure if it has a place in master but here is the PR.
Regardless, I would be grateful if you could review whether this is all it is needed to generate PDFs with specific versions or not. @hhrutter

Coverage decreased (-15.6%) to 71.518% when pulling a8a2821a8b081aebc41293262eb9bc970f76140f on 0x1EE7:feature/pdf-version into 4a397e87c1fe847cd2f96208ea5f7d492c472b89 on hhrutter:master.

Coverage decreased (-15.6%) to 71.518% when pulling a8a2821a8b081aebc41293262eb9bc970f76140f on 0x1EE7:feature/pdf-version into 4a397e87c1fe847cd2f96208ea5f7d492c472b89 on hhrutter:master.


feature request: add used/free space

sorry if i write this topic on a wrong section of the project.
here the question: is it possible to add the bar which shows free/used space below each driver?

There already is a page in Windows Settings that provides this information. I don't think adding this information would fit well with the current aesthetic of Files.
Not promising anything, but maybe in the future we'll add a pro-mode with a ribbon and drive storage info.

If there was a 'this pc' page in the app, it would make sense to have the information there.

If there was a 'this pc' page in the app, it would make sense to have the information there.

Yes, i agree with you cause i see this app as a very good alternative to 'this pc' so here the reason why i wrote the previous post

Change of plans. There won't be any unused space indicator on the Favorites page, but I will include this information within the Properties dialog.

What about making a 'This PC' page?

@SimonTek27 this information is now available in the properties window. You can download the latest version of Files from https://files.community/download.


Build failure on Arch with hyprland-git.

Hyprland Version
 System/Version info
<Paste the output of the command here>

(none, trying to move to hyprland-git via AUR)

Bug or Regression?
Bug
Description
Used yay to try and install hyprland-git to use hyprpm, but this is what I got instead (last few lines of the output)
mv: cannot stat '/home/admin/.cache/yay/hyprland-git/pkg/hyprland-git/usr/include/wlr': No such file or directory
==> ERROR: A failure occurred in package().
Aborting...
-> error making: hyprland-git-exit status 4
-> Failed to install the following packages. Manual intervention is required:
hyprland-git - exit status 4
How to reproduce
Attempt to install hyprland-git via AUR.
Crash reports, logs, images, videos
No response

I cd'd into the path and made the wlr directory myself, but still got the error whenever I tried to install.

Build directly from the PKGBUILD and delete lines 130-131 before you run makepkg

I do not maintain the aur pkgs, ask maintainers to fix it

I do not maintain the aur pkgs, ask maintainers to fix it

Ok.


3rd party dcache implementation

I am creating a 3rd party open source dcache implementation and have found that there are missing calls in at least main.c for plugging in a dcache library provider, initializing a dcache provider and adding index-data to the dcache provider as it is read from the index partition. There may be other files as well that need modifications. If anyone has a provider and is willing to share the files it would be much appreciated.

The purposes of the dcache are

Return a metadata without tape mount
Reduce the memory foot print of on memory meta-data

At this time, we don't think dcache I/F have a big value in the single drive environment. Because it is no demand to return meta-data from dcache without tape mount. And it is really bad idea to fill a tape with tens or hundreds million files, that idea might waste the capacity of tape.
On the other hand, the dcache is a kind of cache. So we don't have any intent to build it from the index on tape directly. It shall be created (rebuilt) from read metadata from the index on tape.
Of course, IBM Spectrum Archive LE has such kind of codes but I'm sorry to say we cannot provide it to the open source project at this time.

In regards to value of dcache. We have customers who have small files and require that we archive files exactly as they are, in other words will not allow us to bundle them into say .zip or .tar files. We also have systems that have a dozen or more tapes drives loaded at one time and therefore memory consumption is becoming an issue. Why this  has become more concerning is that the tape capacities have increased such that when we remaster say LTO5 tapes onto LTO9 tapes our memory usage goes up by a factor of 6x. With the possibility of 40 TB+ tapes in the future we see this problem only becoming much worse and basically rendering LTFS unusable for many archival environments. I understand that IBM does not want to provide their dcache code present in their enterprise version however better definition of the functions defined in dcache.c sure would be useful. From a community standpoint if anyone else has this requirement I certainly would be open to partnering with them in the creation of an open source version of dcache.

I understand that IBM does not want to provide their dcache code present in their enterprise version however better definition of the functions defined in dcache.c sure would be useful. From a community standpoint if anyone else has this requirement I certainly would be open to partnering with them in the creation of an open source version of dcache.

It's OK to develop it by your lead and to open the PR for merge it but I can't help you. Because (as you know) I'm working in IBM.
IBM allows me to make activities on this project unless I don't make any negative impact the IBM product. One more thing is I'm a developer of the dcache module bundled into IBM Spectrum Archive LE, so I cannot re-implement it in the open source world because it means the source code leak from IBM.
In this topic, I cannot say anything anymore. Please help him if someone can join in this idea without any restriction.

Thanks to IBM LTFS OSS project.
Hi, I am a user of IBM Spectrum Archive LE for archiving system in Japanese post production.
I am also keeping watch on this issue.
There is a requirement in the video and medical industries to store large numbers of sequentially numbered images without having to tar or zip them.
The number of files can be quite large, as in the example of archiving a single-frame, single-file film to LTO.
I have been helped by LTFSLE,
but given the migration,
it is natural to want dentry support.
My LTFSLE usages:
https://www.lespace.co.jp/Product-Detail/8UCUPUoU
(sorry, only in Japanese)
Although I write programs for file copy software,
I don't have the technical skills to support the internal implementation of dentry.
I hope to come up with some good ideas on this issue in the future:)


Update GoReleaser config and CI pipelines

What does this PR change?

 If yes, please list them.
None
Checklist
I confirm, that I have...

[x] Read and followed the contributing guide in CONTRIBUTING.md
[x] Added tests for this PR
[x] Formatted the code using go fmt (if applicable)
[x] Updated documentation on the Paralus docs site (if applicable)
[x] Updated CHANGELOG.md

@niravparikh05 Please review this PR.

@niravparikh05 Please take a look at this PR when you get time. Thanks!


[Question] Verify constructor

I have a class A that has a method b().
The method B creates the object C with some specific args and execute the d() method.
So A().b() calls C(specific args).d().
The signature of B and D methods are the same. A only exists to create C with those specifics Args. So it's kind of a proxy in order to be aligned to DRY and not call C(specific args) multiple times in different places + be more semantic. B is a generic name and D is a better name for my specific use case.
I already have all the tests written for A and B, but since C.d is a proxy to A.b that only specifies custom logic to the constructor, I don't want to retest everything again. I only want to make sure C was called with the correct arguments.
How could I do this?

Can't you invert the dependency and inject a factory that makes C into A? you could then unit test against the factory AND that A().b() calls the factory separately

You can also make de C constructor overridable within A:
class A {
  A({
    @visibleForTesting C Function()? testCConstructor
  }) : _cConstructor = testCConstructor ?? C.new;
}

And pass testCConstructor on your testing returning a Mocked C and verify D usage.


Can vvenc generate user-mandated IDRs

we want to keep key frames from source video，it need to force vvenc to generate key frames at any encoding time

For now this is not possible. The only think you could do, would be to chunk the video into pieces starting at your desired IDR points and encode each chunk separately. Than you could just cat the chunks together.
We will discuss internally if this is something we want to support. But either way, because it is an interface change and quite out of our current way of doing thinks, this will take quite some time. I will keep the issue open as a reminder.

For now this is not possible. The only thing you could do, would be to chunk the video into pieces starting at your desired IDR points and encode each chunk separately. Than you could just cat the chunks together.
We will discuss internally if this is something we want to support. But either way, because it is an interface change and quite out of our current way of doing things, this will take quite some time. I will keep the issue open as a reminder.

Noted , thks!
This is a common function that x265 x264 and nvenc has supported!

Is there a use case for that feature besides live transmissions (e.g., conferencing), where you want to insert key frames to compensate for packet loss or joined participants?

Hi @adamjw24 ,
it was nice meeting you at the previous JVET / MPEG meeting!
As discussed there, for us (Fraunhofer IIS), it would also be very convenient to have an IDR-on-demand functionality in VVenC.
Our use case is that with MPEG-H 3D Audio, the bitstream can contain configuration changes at arbitrary, but video frame grid aligned positions. For DASH we would ideally like to start at new Period at each of these configuration change positions to enable e.g. ad insertion by DASH Period replacement. This would require an IDR at this position s.t. we can start a new video segment aligned with the audio segment. Ideally, at least for this use case, the IDR-on-demand would also restart the regular IDR grid at the IDR-on-demand position s.t. we can keep using a Segment Template in the new Period.
Do you think it would be possible to enable this in the future?

Btw, this can be easily achieved by encoding each IDR in a separate encoder instance. It will cause some overhead, more so the mroe threads are used. But the functionality would be achieved.

Btw, this can be easily achieved by encoding each IDR in a separate encoder instance. It will cause some overhead, more so the more threads are used. But the functionality would be achieved.

Sure, that is what we currently do, however we could simplify our architecture (and get rid of the mentioned overhead) if it wasn't necessary.


go-get is now deprecated!

Problem:
go get: installing executables with 'go get' in module mode is deprecated.
        Use 'go install pkg@version' instead.
        For more information, see https://golang.org/doc/go-get-install-deprecation
        or run 'go help get' or 'go help install'.

So:
How do I fix it?

Forget about it. I fixed it.
Try:
go install github.com/BurntSushi/wingo@latest


Fix console logs after restart

PR changes:

Don't complete a resource logger when a resource is deleted. The only scenario where resources are deleted right now is restart, and we still want logs to be available after a restart.
Correctly display in-memory logs, i.e. logs written by resource logger service, when viewing the console logs page. They're no longer cleared away when console logs watch stops.

Fixes https://github.com/dotnet/aspire/issues/5803
Checklist

Is this feature complete?

[x] Yes. Ready to ship.
[ ] No. Follow-up changes expected.

Are you including unit tests for the changes and scenario tests if relevant?

[x] Yes
[ ] No

Did you add public API?

[ ] Yes

If yes, did you have an API Review for it?

[ ] Yes
[ ] No

Did you add <remarks /> and <code /> elements on your triple slash comments?

[ ] Yes
[ ] No

[x] No

Does the change make any security assumptions or guarantees?

[ ] Yes

If yes, have you done a threat model and had a security review?

[ ] Yes
[ ] No

[x] No

Does the change require an update in our Aspire docs?

[ ] Yes

Link to aspire-docs issue:

[x] No

Microsoft Reviewers: Open in CodeFlow

@drewnoakes this is relevant to the conversation we were having today about health checks UX in the dashboard. Specifically this bit:

Correctly display in-memory logs, i.e. logs written by resource logger service, when viewing the console logs page. They're no longer cleared away when console logs watch stops.

For 9.0 we might be best to just write the resource log with error messages from health checks. Previously it wasn't that great of an experience, but by persisting the log messages between visits to the logs page it changes things.

Hrm ... this still doesn't preserve the logs from before the process starts. The WaitFor implementation uses the resource logger to output some messages like the following:

The process can finish starting up and be running and not be showing the Kestrel log outputs, but if I navigate away and come back I see this:

You can use the waitfor playground to verify this. You need to look at the console logs quickly though before it has a chance to start (only takes about 3 seconds once the dashboard is visible).

Subtle observation, if you catch it early enough the text in the drop down is different:

But once the process is running it changes to the screenshot I have up above (the first one).

The problem is in how WaitFor does logging. I created an issue for it: https://github.com/dotnet/aspire/issues/5908
The problem is that IResource doesn't know about the unique name that is generated by DCP. Maybe the value could be generated ealier and stored in an annotation. Then GetLogger(IResource) would have the right name. That wouldn't work for resources with replicas where there are multiple names.

Hrm ... realistically if we had two replicas, both replicas would be getting held up by the same set of health checks - so we would want the log to show up in both places. We might need an API that allows us to do some kind of "aggregate logging" across replicas.


Migrate to Python 3

The CI failed when installing Lektor due to an import in Watchdog. It's about time to migrate to Python 3 since both Lektor and Watchdog has stopped support Python 2.7.
  Traceback (most recent call last):
    File "<string>", line 1, in <module>
    File "/tmp/pip-build-sZeQjb/watchdog/setup.py", line 18, in <module>
      import importlib.util
  ImportError: No module named util

I tested building locally with Python 3.9 as well as via GitHub Actions, and it worked. When you created this issue, did you have any known Py 3 incompatibilities in mind, or was this just assuming it wouldn't work with Python 3 because CI was still using Python 2?

I may have already addressed this in the past, pretty sure I was using 3 locally. If it's already running, then it sounds like those changes are still enough.


Kshitij

@wimpywarlord Thanks for the PR. I'll review and merge it soon.

You may look into a few good first issues which are up for grabs.

:white_check_mark: Link to the repository


[Bug]: [error] 26#26: *1250 connect() failed (111: Connection refused) while connecting to upstream, client: <IP_ADDRESS>,

Description
https://app.abcdefg.com/ gives a NGINX 502 Bad Gateway
I have a service to an application on port 3000. But the NGINX Ingress cannot reach the service:

nginx-ingress-nginx-controller-5876c489c5-k9pwp 2024/08/28 08:12:05 [error] 27#27: *1275 connect() failed (111: Connection refused) while connecting to upstream, client: X.X.X.X,
server: app.abcdefg.com, request: "GET / HTTP/2.0", upstream: "http://<IP_ADDRESS>:3000/", host: "app.abcdefg.com"

http://<IP_ADDRESS>:3000/ is the correct IP of the application pod

NGINX version 4.10.1

Here is my service and ingress config:
---
apiVersion: v1
kind: Service
metadata:
  name: abcdefg-app
  namespace: application
  labels:
    app.kubernetes.io/name: abcdefg-app
spec:
  type: ClusterIP
  ports:
    - protocol: TCP
      port: 80
      targetPort: 3000
  selector:
    app.kubernetes.io/name: abcdefg-app
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: abcdefg-app
  namespace: application
  annotations:
    kubernetes.io/ingress.class: nginx
    cert-manager.io/cluster-issuer: letsencrypt-production
spec:
  ingressClassName: nginx
  tls:
    - hosts:
        - app.abcdefg.com
      secretName: abcdefg-app-tls
  rules:
    - host: app.abcdefg.com
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: abcdefg-app
                port:
                  number: 80

Kube.tf file
module "kube-hetzner" {
  providers = {
    hcloud = hcloud
  }
  hcloud_token = var.hcloud_token
  source = "kube-hetzner/kube-hetzner/hcloud"
  ssh_public_key = file("~/.ssh/hcloud.pub")
  ssh_private_key = null
  network_region = "eu-central" # change to `us-east` if location is ash
control_plane_nodepools = [
    {
      name        = "control-plane-fsn1",
      server_type = "cx31", # cax11 zou voldoend moeten zijn
      location    = "fsn1",
      labels      = [],
      taints      = [],
      count       = 2
    },
  ]

  agent_nodepools = [
    {
      name        = "agent",
      server_type = "cx31",
      location    = "fsn1",
      labels      = [],
      taints      = [],
      count       = 4
    },
  ]
  load_balancer_type     = "lb11"
  load_balancer_location = "fsn1"

  ingress_controller = "nginx"

  cluster_name = "abcdefg"

  enable_cert_manager = true
  dns_servers = [
    "<IP_ADDRESS>",
    "<IP_ADDRESS>",
    "2606:4700:4700::1111"
  ]
  lb_hostname = "app.abcdefg.com"

  nginx_version = "4.11.2"
}

provider "hcloud" {
  token = var.hcloud_token
}

terraform {
  required_version = ">= 1.5.0"
  required_providers {
    hcloud = {
      source  = "hetznercloud/hcloud"
      version = ">= 1.43.0"
    }
  }
}

output "kubeconfig" {
  value     = module.kube-hetzner.kubeconfig
  sensitive = true
}

variable "hcloud_token" {
  sensitive = true
}

Screenshots

Platform
Mac

Container did not allow port 3000, my bad


Create method

Can you explain your issue?

Whoops
Anyways...
Would you be opposed to a static create() method that took the service name and created the object for you? (Like omnipay) Just trying to avoid including a bunch of classes that are actually not needed just to use a switch to figure out which one I need for this particular instance.

Something like this?
Omnimail::create(Omnimail::SendGrid, $apiKey);

I think you would need to pass an array or interface rather than a single variable as it might vary

So like this:
Omnimail::create(Omnimail::SendGrid, [
    'apiKey' => $apiKey
]);

Anyone got time for this? Should be a simple implementation.

Merged into develop branch.


Missing documentation - at_onboarding_flutter (Scores Tab)

Score tab is missing documentation for:

[x] provide documentation
[x] support multiple platforms
[x] pass static analysis
[ ] support sound null safety

Hi @sarika01 we need to review this very old ticket for accuracy, potentially close it and divert to the new pub.dev publishing issue. Creating new issue cards today.

I think this gonna be covered by @Intiserahmed

@Intiserahmed can you please look at this.

This is already actioned and published under https://github.com/atsign-foundation/at_widgets/issues/281

But still the score tab has 20 points less. That is due to null safety issues.

@yahu1031 That is applicable to all packages depending upon hive. There is nothing much that we can do at this point.

13 packages doesn't show null-safety tag in pub.dev

All packages depending upon hive_flutter will have this issue. This was brought up and discussed months back. The decision was to leave it as it is till the at_client moves away from hive.

Okie then, I'm closing this.


[riverpod_lint] Dependencies lint misses providers used in methods

Describe the bug
When using a provider inside a method that is being called in the build method, the provider usage is not detected.
To Reproduce
In this code, the linter doesn't detect the usage of eventsWithStreamedCompletionProvider:
@Riverpod(dependencies: [calendars])
class CalendarFeed extends _$CalendarFeed {
  @override
  Future<CalendarFeedState> build() async {
    final calendars = await ref.watch(calendarsProvider.future);
    final events = await listenToEvents();
    return CalendarFeedState(events: events, calendars: calendars);
  }

  Future<List<EventWithAsyncCompletion>> listenToEvents() async {
    final completer = Completer<List<EventWithAsyncCompletion>>();
    ref.listen(
		eventsWithStreamedCompletionProvider(),
		/*function that completes the completer*/
	);
    final events = await completer.future;
    return events;
  }
}

but it does here:
@Riverpod(dependencies: [calendars])
class CalendarFeed extends _$CalendarFeed {
  @override
  Future<CalendarFeedState> build() async {
    final calendars = await ref.watch(calendarsProvider.future);
    final completer = Completer<List<EventWithAsyncCompletion>>();
    ref.listen(
		eventsWithStreamedCompletionProvider(),
		/*function that completes the completer*/
	);
    final events = await completer.future;
    return CalendarFeedState(events: events, calendars: calendars);
  }
}

Expected behavior
It should detect it as well or at least give a way to add it manually to then dependencies without the linter complaining (forcing).

I'm not sure what you mean by scoped. But here is a rough implementation of it:
@Riverpod(dependencies: [eventsWith, profiles])
Stream<List<EventWithAsyncCompletion>> eventsWithStreamedCompletion(
  EventsWithStreamedCompletionRef ref, [
  EventProviderParam param = const EventProviderParam(),
]) async* {
  final f = await ref.watch(profilesProvider.future);
  final events = await ref.watch(eventsWithProvider(param).future);

  final cache = events
      .map((e) => EventWithAsyncCompletion(e, const AsyncLoading()))
      .toList();
  yield cache;
  yield* Stream.fromFutures(events.map(updateCache)).map((_) => cache);
}


Regular user cannot recreate container

Hey guys,
thanks for the great software making docker more accessible in our institution!
I have the following problem:
Regular users have the permissions to create containers with exposed ports etc. but the recreate button is not showing up.
This button is really important to update the container to a new image.
The button does not show up because of the following permissions being false:

allowBindMountsForRegularUsers
allowDeviceMappingForRegularUsers
allowPrivilegedModeForRegularUsers

Which is hiding the Recreate button:

Button: https://github.com/portainer/portainer/blob/9e80037e72fa9ed53cabe93eee52dce7927b3788/app/docker/views/containers/edit/container.html#L39
Condition in the controller: https://github.com/portainer/portainer/blob/9d18d47194c902c2be1d7b43bc4b76ac1e7d6ce0/app/docker/views/containers/edit/containerController.js#L116

If I have the rights to create a container, why cant I recreate one?
Out of security concerns in our institution we cannot enable those options:
https://documentation.portainer.io/v2.0/settings/security/
It is very tedious to manually add a container with the GUI. Can someone enlighten me?
Version:
1.24.1
I will gladly provide more information!

Not a bug, this is intended behaviour now and was implemented via this PR https://github.com/portainer/portainer/issues/4032

Issue closed

Okay, I understand.
But a regular user, who created a container should be able to recreate it right? A container created with certain restrictions should be able to be recreated as long as recreating doesn't violate those restrictions.
At the moment I have to delete the container and create a new one if the image has changed.

@campfireman Unfortunately these settings affects ALL the regular users. It will be very difficult for us to track who created a container to check if he should be able to re-create a container with some restrictions disabled for that specific user as well as checking if the restrictions are OK or not for that user.

@campfireman Unfortunately these settings affects ALL the regular users. It will be very difficult for us to track who created a container to check if he should be able to re-create a container with some restrictions disabled for that specific user as well as checking if the restrictions are OK or not for that user.

@deviantony thanks for the insight! The only reason I'm asking is because I want to update the image of a container without having to delete the container. Is there some other way to do that under the given circumstances?

@deviantony thanks for the insight! The only reason I'm asking is because I want to update the image of a container without having to delete the container. Is there some other way to do that under the given circumstances?

No such concept with containers.
An edit is a redeploy. Thats the architecture of Docker/Containers.

No such concept with containers.
An edit is a redeploy. Thats the architecture of Docker/Containers.

Okay, thank you very much for the quick responses!
For now we have to reconsider our security settings if we want to increase the convenience. As a little appendix an explanation why such feature is relevant in our use case. Maybe that is useful for you guys:
Situation:

We use gitlab CI to continuously create the most recent image of the master branch and push it to our internal registry.
This pipeline is greatly abstracted to make it usable for anyone creating applications in our institution.
Staff then can deploy their applications to our internal network through portainer

This stack is designed to be used by scientists with very different IT backgrounds.
Advantages of portainer in this context:

Access to infrastructure can be regulated and simplified
Deployment much easier with GUI
docker more understandable with GUI
perfectly integrates with our CI pipeline through image registry
...
=> quick deployment of prototypes

The only thing required to make it perfect:

pull latest image and redploy with previous settings (under given restrictions :P)
maybe even an API endpoint to trgger this programmatically with gitlab CI scripts
(- and full docker-compose v3 support but thats another thread ^^)

Thanks again!

Okay, thank you very much for the quick responses!
For now we have to reconsider our security settings if we want to increase the convenience. As a little appendix an explanation why such feature is relevant in our use case. Maybe that is useful for you guys:
Situation:

We use gitlab CI to continuously create the most recent image of the master branch and push it to our internal registry.
This pipeline is greatly abstracted to make it usable for anyone creating applications in our institution.
Staff then can deploy their applications to our internal network through portainer

This stack is designed to be used by scientists with very different IT backgrounds.
Advantages of portainer in this context:

Access to infrastructure can be regulated and simplified
Deployment much easier with GUI
docker more understandable with GUI
perfectly integrates with our CI pipeline through image registry
...
=> quick deployment of prototypes

The only thing required to make it perfect:

pull latest image and redploy with previous settings (under given restrictions :P)
maybe even an API endpoint to trgger this programmatically with gitlab CI scripts
(- and full docker-compose v3 support but thats another thread ^^)

Thanks again!

Consider using docker swarm and deploying your app as a service, that way you can use “service update” to pull the latest image and do a rolling upgrade of the app.
You can use our webhooks from your CI to trigger this for a hands-free process.

Consider using docker swarm and deploying your app as a service, that way you can use “service update” to pull the latest image and do a rolling upgrade of the app.
You can use our webhooks from your CI to trigger this for a hands-free process.


🙉File upload with Null content

Hello,
i have tried many option with okhttp but not get conclusion.
i want to send value as null for any parameter parameter.
Good bug reports include a failing test! Writing a test helps you to isolate and describe the problem, and it helps us to fix it fast. Bug reports without a failing test or reproduction steps are likely to be closed.
Here’s an example test to get you started.
https://gist.github.com/swankjesse/981fcae102f513eb13ed

Thanks for your question. This issue tracker is only for bug reports with test cases and feature requests. Please ask usage questions on Stack Overflow.
https://stackoverflow.com/questions/tagged/okhttp

Thanks for your question. This issue tracker is only for bug reports with test cases and feature requests. Please ask usage questions on Stack Overflow.
https://stackoverflow.com/questions/tagged/okhttp


Change the internal payload representation

use an array of len=1 characters
support use "as" a len=: string

@hsnyder, I don't know why it won't let me assign you as a reviewer, but feel free to do the review on this


Fusionauth 1.27.0 tenant updates

There are some new additions to tenants which means that the provider currently fails to update tenants with external_identifier_configurations:
https://fusionauth.io/docs/v1/tech/apis/tenants/
e.g.
tenant.externalIdentifierConfiguration.twoFactorOneTimeCodeIdGenerator.type [String] Required defaults to randomAlphaNumeric Available since 1.27.0

    The type of the secure generator used for generating the two factor one time code Id. Possible values are:

        randomAlpha

        randomAlphaNumeric

        randomBytes

        randomDigits

I'll have a look at adding the missing functionality next week

Have this branch going https://github.com/gpsinsight/terraform-provider-fusionauth/pull/51


Distro ascii art really big

Description
If you're suggesting a new feature then just a description will suffice.
Neofetch version
Latest from the arch repos as of writing this
Screenshot

Config file
Default (just installed)
Verbose log

Run neofetch -vv 2> neofetchlog
Upload the contents of neofetchlog to pastebin, gist or equivalent.

Thanks in advance for the help

Your terminal emulator's character width is very wide (due to your language).  I'd look for a terminal which handles variable-width better than urxvt, since a previous patch for it was rejected

i fixed it by setting urxvts letterspacing to -1

Closing since this is a terminal issue and not a neofetch issue.


User Guide: scanner examples could be improved

Initiated from an scons-users thread, which may be found at https://pairlist4.pair.net/pipermail/scons-users/2024-January/009286.html
The examples in the User Guide chapter on scanners have some errors.  The specific errors that are just incorrect code are in https://scons.org/doc/4.6.0/HTML/scons-user.html#id1490  (using a version-specific link intentionally), a missing closing paren, and a scanner function declaration that expects an arg parameter, but then the Scanner is not created with an argument kwarg, so the scanner won't actually be called with arg.
The examples in this chapter are not set to generate results via the usual bin/docs-create-example-outputs.py script and be included in the generated text, so we don't have an automated way to detect syntax errors.
There are also some inconsistencies... there's mention of a "foo" scanner (perhaps following on from the Builder chapter's examples of building from .foo sources), but the suffix used is actually .k.  A fair bit of useful explanation seems to be missing, and if you did make the example in section 20.3 run, it wouldn't show anything interesting. The use of a path variable and a scanner path function is never actually elaborated on - it shows how to pass the path_function on SCanner creation, but the scanner function does not show making any use of the path tuple it will be called with as a result.

One more from the list thread:
env = Environment(ENV={'PATH': '/usr/local/bin'})

is used - that's poor practice, as it wipes out any default values of env['ENV'] and makes any actual execution of an external command unlikely to work well. Perhaps can be made to work for the example, but should introduce things in a better way, so the learning translates to "real life" usage scenarios.

One more from the list thread:
env = Environment(ENV={'PATH': '/usr/local/bin'})

is used - that's poor practice, as it wipes out any default values of env['ENV'] and makes any actual execution of an external command unlikely to work well. Perhaps can be made to work for the example, but should introduce things in a better way, so the learning translates to "real life" usage scenarios.

There are real world build environments where you don't want to use or reference anything from /usr/bin for example. So this can be a reasonable thing to do, but perhaps just needs more explanation?

In the 20.3 example the skeys perhaps should be ['.input'] ?
It's not really clear that we're registering a scanner to scan .k files with a builder who's input is .input files?


tutorial example pipeline

The error you encountered could be a result of how you need to import the project in order to test. Do the error continue if after checking out the branch you restarted the pipeline?

This error sometimes appears in general, not only in this project when running the session interactively multiple times, usually, it resolves after restarting the memory server or restarting the session.

The error you encountered could be a result of how you need to import the project in order to test. Do the error continue if after checking out the branch you restarted the pipeline?

Are your referring to the Plotly Warning? If so, no the warning persists.

Are your referring to the Plotly Warning? If so, no the warning persists.

No, the others. Yes, plotly error is because of prophet, it won't go away (I have looked into it in the past, it can be filtered out by redirecting sys.stderr). The error right after of NoneType and the error about OutputNotFound is this memory server error it seems.

No, the others.

Alright, the error for opening a node goes away, after trying to open once. The OutputNotFoundError persists even after restarting. (only when running all nodes simultaneously)


One config on top

These 3 commits add a new table on top of the results listing that contains the result of running a single
configuration across all the files and speeds in the test set.

PTAL

lgtm


Migration to Lexv2 and Installer script

Description
This PR contains updates to the code and Quickstart guide to transition to the Lex V2 APIs.
Some notable additions:

Only one Lambda function is now required
Code can be uploaded via zip file contained in the repository
Migrated Lambda to 3.7, now using requests library
Lex Bot is now created automatically with installer script
Lambda function now created automatically with installer script

Motivation and Context
AWS deprecated support for python 2.7 a while back - Roxie needed some love
Instructions were written to support V1 of Lex APIs, which are currently being deprecated
How Has This Been Tested?
Tested in the TM Lab - all is well!
Screenshots (if appropriate):
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:
Go over all the following points, and put an x in all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help!

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTION document.
[ ] I have updated the CHANGELOG file accordingly for the version that this merge modifies.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Looks good Mike! :shipit:


tools/babel contains Python 3 syntax errors

tools/babel/messages/extract.py
tools/babel/messages/frontend.py

These two files contain legacy print statements that would fail as syntax errors on Python 3.  The current babel supports Python 3 so it should either be pip installed or re-vendored.  Discovered but not fixed https://github.com/google/personfinder/pull/459/commits/f99351aa4af59bfc5d97cfe55c1f6334c686d016#r238889957

Thanks for finding it. Actually there is also app/vendors/babel which I believe is newer. We should probably refer to it instead.

Why not just pip install babel instead of vendoring it in?

App Engine upload tool only uploads files in app directory. So all dependency libraries, including babel, must be located inside app before running the app. There would still be an option not to track app/vendors with Git, and instead let individual developers install them, though.

Filed #463 for migration to app/vendors/babel.


feat(autoware_adapi_v1_msgs): add object recognition msg

Description

add the msg required for object recognition

Related links
https://github.com/autowarefoundation/autoware/issues/3225#issuecomment-1409895712
https://github.com/autowarefoundation/autoware-documentation/pull/321

Tests performed

Notes for reviewers

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[x] The PR follows the pull request guidelines.
[x] The PR has been properly tested.
[x] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@tkhmy
LGTM. The remaining consideration is whether to use generic shapes (https://github.com/autowarefoundation/autoware_adapi_msgs/pull/26).

@tkhmy PredictedObject is the classification that the perception component uses internally, so please rename it to DynamicObject.
@yukkysaito I think that classification and shape are also used in static object, so I didn't add the dynamic prefix, is this right?

Before
After

ObjectClassification
ObjectClassification

ObjectKinematics
DynamicObjectKinematics

PredictedObject
DynamicObject

PredictedObjectArray
DynamicObjectArray

PredictedPath
DynamicObjectPath

Shape
ObjectShape

It depends on the definition of DynamicObject, but I understand that the current Autoware treats anything that was not there when the map was created as a DynamicObject (including cones). So I think it is ok to put Dynamic as prefix. cc @xmfcx @mitsudome-r

Thanks for the commend
I will change it

@xmfcx Hi, can you review the changes and approve if it looks fine for you?
Thanks

@isamu-takagi I do not have the merge permission, can you help me to merge it?


Redirect to feed after completing the bank connection

Explanation of Change

Fixed Issues

$ https://expensify.slack.com/archives/C06ML6X0W9L/p1730461357005019?thread_ts=1729596921.819569&cid=C06ML6X0W9L
PROPOSAL: https://expensify.slack.com/archives/C06ML6X0W9L/p1730688809259139?thread_ts=1729596921.819569&cid=C06ML6X0W9L
Tests

[x] Verify that no errors appear in the JS console

Offline tests

Internal QA Steps

Go to Company Card Page
Add new Company Card
Select Chase Bank
Select Direct Feed
Complete the bank connection
Verify that the App navigate to Company Feed Page

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@mountiny The PR is up

@dukenv0307 @allgandalf Could you guys help to review this PR? Please comment on this PR and start reviewing soon. Thanks

Please comment on the code change then the Melvin will not get another C+ when I open the PR

@dukenv0307 I still trying to test this change. It seems hard to test on dev without an auth connection

@dukenv0307 Problem: When users complete the bank account flow, the App doesn't navigate them to Company Feed. This PR will fix this problem
https://github.com/user-attachments/assets/deb3fc7b-132a-46cf-a9cf-81fd13ba2aef

I anticipate this is hard to test locally, sorry there is no way to handle it.
How does the xero connection or other integration connections handle it, i think they must use the same approach

I anticipate this is hard to test locally, sorry there is no way to handle it.
How does the xero connection or other integration connections handle it, i think they must use the same approach

This is another flow, and I don't think we can use the same way here. Trying another way

Mock data to test on dev env:
On src/pages/workspace/companyCards/addNew/BankConnection/index.tsx
Add
    const mockBankResponse = () => {
        Onyx.set(`${ONYXKEYS.COLLECTION.SHARED_NVP_PRIVATE_DOMAIN_MEMBER}${18600095}`, {       // PLease update your workspace account id
            settings: {
                accountManager: 9666036,
                accountManagerAssignmentDate: '2023-11-02 14:17:44',
                companyCardNicknames: {'ofx.chase.com': ''},
                companyCards: {
                    'Expensify Card': {
                        asrEnabled: false,
                        forceReimbursable: 'force_no',
                        liabilityType: 'personal',
                        preferredPolicy: '',
                        reportTitleFormat: '',
                        statementPeriodEndDay: 1,
                        uploadLayoutSettings: null,
                    },
                    'oauth.chase.com': {
                        asrEnabled: false,
                        forceReimbursable: 'force_no',
                        liabilityType: 'personal',
                        preferredPolicy: '',
                        reportTitleFormat: '',
                        statementPeriodEndDay: 1,
                        uploadLayoutSettings: null,
                    },
                },
                oAuthAccountDetails: {
                    'oauth.chase.com': {
                        accountList: ['C. DUNBAR...0546', 'J. HAYES...4754', 'K. BAACK...8211', 'L. BORGNINO...9008', 'C. MILES...4129', 'J. BRUSH...8303'],
                        credentials: 'ASDF',
                        expiration:<PHONE_NUMBER>,
                    },
                },
                technicalContactEmail<EMAIL_ADDRESS>                twoFactorAuthExemptEmails<EMAIL_ADDRESS>                useTechnicalContactBillingCard: true,
            },
        });
    };

Add a button to trigger mock data
            <Button onPress={mockBankResponse}>
                <Text>Click me</Text>
            </Button>

@mountiny For sure, we need to make a build and reach out to some internal QA who have chase accounts to test this PR

@dukenv0307 Could you help to test this PR on other platforms?

@dukenv0307 On native, I still get some problems

There are some updates
We only need to mock this response
        Onyx.set(`${ONYXKEYS.COLLECTION.SHARED_NVP_PRIVATE_DOMAIN_MEMBER}${18600095}`, {
            settings: {
                oAuthAccountDetails: {
                    'oauth.chase.com': {
                        accountList: ['C. DUNBAR...0546', 'J. HAYES...4754', 'K. BAACK...8211', 'L. BORGNINO...9008', 'C. MILES...4129', 'J. BRUSH...8303'],
                        credentials: 'ASDF',
                        expiration:<PHONE_NUMBER>,
                    },
                },
            },
        });

@dukenv0307 Please help to review again

@dukenv0307 kindly bump

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


🔌📊 Generate PowerGraphs for Charging Sessions W/O DT

Charging sessions without an ISO15118-2 Departure Time now have a preview graph that showcases the charging behavior.

See Issue #92 for additional context, and this comment specifically for a demo of this functionality!
Set to draft while running last minute tests, will switch to full when R4R!

@the-bay-kay this is failing DCO. I am going to pull so that I can resign and then submit.

Closing since this is superceded by https://github.com/EVerest/everest-demo/pull/97


Bound finalized header, execution header and sync committee by pruning older data beyond threshold

Description
This PR enables pruning older FinalizedHeader, ExecutionHeader and SyncCommittee. This is required to put bounds on the storage of the pallet. As left unchecked it could be huge amount of data.
First three PR adds support for pruning of FinalizedHeader, ExecutionHeader and SyncCommittee respectively. Fourth commit adds comprehensive tests for the same. Fifth commit is just cargo fmt changes.
How it works?
ExecutionHeader
For ExecutionHeader there is a queue like simulated data maintained that allows pruning of older data as the new data gets added.
Since execution headers are not contiguous, to maintain the queue, we need to maintain a mapping of u64 -> ExecutionHeader and also keep track of front and back of the queue. While we push new data to back, we remove data from front this is supported by (oldest_bound, latest_bound) storage.
FinalizedHeader
For FinalizedHeader we are pruning it as per MaxFinalizedHeaderSlotArray. As, FinalizedHeader and its associated data with slot less than 0th element of the vector will not be used by relayer in anycase.
SyncCommittee
Since SyncCommittee is stored in an order, we can rely on it to prune oldest sync committee.
Configuration changes
Both ExecutionHeader and SyncCommittee's pruning threshold is defined in pallet configuration.
Relayer changes
Due to change in FinalizedSlotArray storage, there is a change in relayer to maintain compatibility.

@ParthDesai Cool and thanks for the contribution!  Though IMHO implementation with some ringbuffer structure without pruing could be more simple and effiecent.
https://substrate-developer-hub.github.io/substrate-how-to-guides/docs/storage-migrations/ringbuffer/

@ParthDesai Cool and thanks for the contribution! Though IMHO implementation with some ringbuffer structure without pruning could be more simple and effiecient. https://substrate-developer-hub.github.io/substrate-how-to-guides/docs/storage-migrations/ringbuffer/

The while loop here is not supposed to be running more than one time in current version of code base. As it tries to prune oldest entry after every insert.

@ParthDesai Cool and thanks for the contribution! Though IMHO implementation with some ringbuffer structure without pruning could be more simple and effiecient. https://substrate-developer-hub.github.io/substrate-how-to-guides/docs/storage-migrations/ringbuffer/

But, yes. The Ringbuffer structure does look like something which can be more efficient and simple than this. I will open another PR with updated implementation.


Mentioning forceUpdate in the Updating part of the component lifecycle

I'm not sure if it was left out intentionally because it's considered bad practice but or the sake of completeness I added a third option that causes a component to rerender: explicitly calling forceUpdate() on that component.

Yeah, I think it wasn't explicitly called out. The page includes docs for forceUpdate later, so I think it's fine. Thank you for your PR!


Fix invalid bitcast in SROA

LGTM, could you create a unit test in HCC?  I believe there was one in one of the discussion threads?

I found another bug when trying to add a test. Basically a byval function parameter should be mapped to a generic pointer instead of a pointer in alloca addr space. The issue will show up if a byval function parameter is taken address and assigned to another pointer. I will fix it and add then add test.

Added unit test https://github.com/RadeonOpenCompute/hcc/pull/364


MM-11782: Make archived channels experimental and off by default.

Recreating pull request to make spinmints work properly (hopefully). No changes to code since original PR
Summary
Change View Archive Channels to a new config setting that's off by default.
Ticket Link
https://mattermost.atlassian.net/browse/MM-11782
Checklist

[x] Ran make check-style to check for style errors (required for all pull requests)
[x] Ran make test to ensure unit and component tests passed
[x] Has UI changes

Webapp Changes: https://github.com/mattermost/mattermost-server/pull/9281

Setup Test Server label detected. Spinmint test server created if build succeeds (checks pass and no conflicts with base branch).

Spinmint test server created at: https://i-0d005e99a4efc6056.test.spinmint.com
Test Admin Account: Username: sysadmin | Password: sysadmin
Test User Account: Username: user-1 | Password: user-1
Instance ID: i-0d005e99a4efc6056

@cpanato  Can you restart this spinmint server please?

@grundleborg @wiersgallak restart server is running but returns 404

@grundleborg you have access to this server thru vault for debugging

What is the status of this PR? Can a new spinmint be generated?

Spinmint test server destroyed


Fix @celo/connect README code example

Description
Fixes the code example in the @celo/connect README.
Tested
Docs only change
Backwards compatibility
Yes
Documentation
Yes

@nicolasbrugneaux I'm looking for the lines that set the CeloProvider in the connection constructor.
But I can't find it
https://github.com/celo-org/developer-tooling/blob/0ad9c011b868c4bf5456f4048cb6d405c9dd8c8e/packages/sdk/connect/src/connection.ts#L70

Ah my bad, it's here
https://github.com/celo-org/developer-tooling/blob/0ad9c011b868c4bf5456f4048cb6d405c9dd8c8e/packages/sdk/connect/src/connection.ts#L77-L93


Features/tdi 37482 snowflake

Please check if the PR fulfills these requirements

[X ] The commit message follows Talend standard
[X ] Tests for the changes have been added (for bug fixes / features)

What is the current behavior? (You can also link to an open issue here)
What is the new behavior?
This is the Snowflake connector, and some changes to move code from the JDBC connector to components common so that it can be reused. The JDBC connector is not currently in use as it is not complete. The Snowflake connector will not go in the release.
I would like to get the changes to components-common in for 6.3 to make it easy to use the Snowflake connector with that release. The changes to components-common affect only JDBC and Snowflake.
Does this PR introduce a breaking change?

[ ] Yes
[X ] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Oh, I realized another minor refactoring, moving the WizardComparator class into the components-api (that hits salesforce), but it's a very low risk change.

Pull request test result: failure :x:


Add Migration guide for KeyVault packages

Add migration guides for azkeys, azcerts, azsecrets

Tracked in https://github.com/Azure/azure-sdk-for-go/issues/21078


Updates to spack v0.19.2

I'm curious to see what happens.

launch jenkins all

tsa
:green_circle: unit testTest:green_circle:summary
WARNING: Serial tests did not run for system tests

daint
:green_circle: unit testTest:green_circle:summary
WARNING: Serial tests did not run for system tests

balfrin
:green_circle: unit testTest:green_circle:summary
WARNING: Serial tests did not run for system tests


Support invoking task selectors on included builds

Expected Behavior
I would like to be able to invoke a task selector on an included project.
tasks.check.configure {
    // run check on all included builds
    dependsOn(gradle.includedBuilds.map { it.taskSelector("check") })
}

Current Behavior
This fails
tasks.check.configure {
    // run check on all included builds
    dependsOn(gradle.includedBuilds.map { it.task("check") })
}

with error
* What went wrong:
A problem occurred configuring root project 'my-template'.
> Could not create task ':check'.
   > Task path 'check' is not a qualified task path (e.g. ':task' or ':project:task').

But using :check here only executes check on the root project, not on all subprojects.
I would like to execute check on all subprojects of an included build.
Context
Related:

https://github.com/gradle/gradle/issues/21942
https://github.com/gradle/gradle/issues/15309

Related docs:

https://docs.gradle.org/current/userguide/intro_multi_project_builds.html#sec:executing_tasks_by_name
https://docs.gradle.org/current/userguide/command_line_interface.html#executing_tasks_in_multi_project_builds
Composite builds

Would love this, my current solution is to create a task in the included build like this:
tasks.register("clean") {
    for (subproject in subprojects) {
        subproject.tasks.findByName("clean")?.let {
            dependsOn(it)
        }
    }
}

Which is very verbose


Silent payment for Angor project identifiers

To break the ability to link a transaction to the Angor protocol we should use the same techniques as silent payments.

https://github.com/MetacoSA/NBitcoin/issues/1240

This is the plan.
(inspired by the silent payment design bip352)
Creating the project identifier, the founder uses their private key to create a shared secret
A = founder key
B = angor key
P = project identifier key
Let P = B + hash(a·B)·G
Encode P as an Angor identifier with bech32 prefix angor+pubkey (on the blockchain it will be a P2WPK output)

Spending the fee in the Angor Identifier address
Let p = b + hash(A·b)·G

p is the private key that can spend the coins in the Angor address
P can only generated by the founder and angor key.
p can only be generated by angor key.


merge package template from Kronos-Tools/npm-package-template

Updated standard to latest version

Codecov Report

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

@@           Coverage Diff           @@
##           master      #75   +/-   ##
=======================================
  Coverage   89.47%   89.47%
=======================================
  Files           1        1
  Lines          19       19
=======================================
  Hits           17       17
  Misses          2        2

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 bc81d5f...4731dbf. Read the comment docs.


Handle sentences with multiple dots at the end

The bot fails at the following example:
Dr. P. S. Deshmukh
I see the objection to my amendment, and do not press it. But, I think it would sound far better if the first word "an
other" is changed into "a" and the word "third" altered into "another". I am afraid that it might look as if I am sugg
esting too many changes. But we are making a constitution, and I do not want that anything should go out of this House
....

Another Sample
1.2.71
The Chairman
I now put the Resolution of Pandit Nehru to the vote...... I declare it carried.

Potential solution could be to replace multiple dots with a single dot.
re.sub(r'\.+', ".", a)


Implemented the requested feature and fixed minor errors

Hey I Implemented the issue ( Capitalize the First Letter of Files in the Components and Pages Folders ).
Along the way I had to fix 2 minor issues caused by adding "plugin:react/recommended" into package.json

I added the following code in ThemeContext.js

+ import PropTypes from 'prop-types';
+ ThemeContext.propTypes = {
+ children: PropTypes.node.isRequired,
+ };

Reason: It was giving me this error: src\context\ThemeContext.js Line 26:26:  'children' is missing in props validation  react/prop-types
When adding "plugin:react/recommended", the rules of the eslint-plugin-react plugin are enabled, which includes a set of stricter checks to help ensure safer and more consistent React code.

I renamed all the classes in Collaborators.jsx to ClassName instead of just Class

+className
-class

Reason: When using react/recommended, ESLint has stricter rules, so class wouldn't work and it was giving a bunch of errors.

Note: That error I was dealing with when renaming the files and components apparently is a bug with the eslintcache, when renaming the files it kept the old cache and it was giving errors.
I used this solution to fix it, and I had no more issues with it: rm node_modules/.cache/.eslintcache

GitHub Issue and solution: https://github.com/facebook/create-react-app/issues/10301

I just noticed I named my branch my github username lol my bad for that😶

code  have some Merge Conflicts, plz resolve it.


Enable GPU Support for Mariner AKS 2.0

What type of PR is this?

What this PR does / why we need it:
Adds GPU support for Mariner
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

mostly minor comments, thanks for the PR!

:shipit:


[CMake] Fix detecting -disable-implicit-string-processing-module-import

The check command used to always fail because it fails to load stdlib. Workaround it by adding '-parse-stdlib' to the check command.

@swift-ci Please test


Can't load any file

Any user can't load any file (IMG, GIF) from "Submission"

Please explain more (and better)

/submit
Trying to load gif or img and nothing happend.


Building intercept should automatically trigger a PBO (re)build

A post-build script should be called that will (re)build the PBO, after building the dll successfully, so that the Intercept library is in a working state as soon as the build finishes.
Optionally, if the PBO doesn't need to be rebuilt because the files have not changed, then maybe have a script that will check for that and only run PBO building when needed?
If the building program (makepbo?) is not present, fail the compilation as Intercept without a PBO is unusable anyway.

as Intercept without a PBO is unusable anyway
But normally you can use the pbo from the official release.. that said... You won't be able to when we sign our plugins.
Which doesn't apply to Intercept core though.

But normally you can use the pbo from the official release

Yes, but if you plan on using the official release, you don't need to recompile anything either way :)
Also, a day will come when you will update the sqf scripts and reusing those from the release will not be possible anymore.
True, it's not really needed and people can live without that facilitation, but on the other hand... why not make it simpler if we can?
That's one less thing to remember when you're cloning a fresh repo - my main motivation for this ticket. Especially that I tend to delete repos and clone them from scratch quite often.

I don't want builds to fail. Because of something you don't even need. If it's only a warning if makePbo is not there that's good. But I don't want a fail.


missing script folder?

Hi, based on the instruction it seems that there should be a script folder in which there's another dataset folder. But it seems missing?

Thanks for pointing this out. Looks like the submodule was not moved to GitHub.
Addressed in a385a47e99b5026a4d8986e3c944ffe04de13ba1, closing.
Cheers,
Max


Add the single thread build that works in Electron.js

@Honry , please help try this single thread build (*_st means that) of TFLite webnn delegate. It works for me to access WebNN-native node.js binding for segmentation sample. To use it, please include tflite_model_runner_cc_st.js. And it may require to post tflite_model_runner_cc_st.wasm to semantic_segmentation/ folder.

Thanks @huningxin, I will test it today.


update release process to include monthly releases

Release process section should include:

[ ] verbiage about releasing by end of month
[ ] Style for Release notes:

[ ] Release notes should include major, minor, & patch changes since last release
[ ] Be tagged to a semver tag

Closing, as per event release, s.a., #163


.

It's okay that you are new to GitHub and want to contribute but please don't spam this repository with unnecessary PRs like this one.

Okay sir
Will take care next time
On 11-Oct-2017 8:43 PM, "Yashovardhan Agrawal"<EMAIL_ADDRESS>wrote:

It's okay that you are new to GitHub and want to contribute but please
don't spam this repository with unnecessary PRs like this one.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Cybros/Lecture-Series-1-HTML-CSS-JS/pull/14#issuecomment-335844497,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ac0OtpOsnr0EOlIXl6ZP5ZJz45eYVWz7ks5srNsBgaJpZM4P1iT9
.

Okay sir
Will take care next time
On 11-Oct-2017 8:43 PM, "Yashovardhan Agrawal"<EMAIL_ADDRESS>wrote:
It's okay that you are new to GitHub and want to contribute but please
don't spam this repository with unnecessary PRs like this one.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Cybros/Lecture-Series-1-HTML-CSS-JS/pull/14#issuecomment-335844497,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ac0OtpOsnr0EOlIXl6ZP5ZJz45eYVWz7ks5srNsBgaJpZM4P1iT9
.


why training torso rely on head model?

could you plz let me know why training for torso rely on head_model?
head_model needs to be loaded here
I think if that folder is empty, still we can keep traning for torso.
thx

this is very minor. I will close it.

Because during inference the torso model need to cooperate with head model to render the final image. So it is necessary for jointly training to achieve natural head-torso connection results