add vanadium step: send result to database

Add the step VTestResultsAnalyzerStep to send build result the test results to database.

test this please

@changev @yyscamper @anhou

@keedya  Thanks for your reviewing.
I already moved the db server to the slave: vmslave-packer-ova
The slave is on the same ESXI with the Jenkins master slave.

@PengTian0  i thought this VM is used for packer only.

@keedya
Could you please help to set up a machine as the db server?

@PengTian0  of course, can you send me the details in a private email. I can set it up tomorrow

@keedya Thank you so much!
I will send you the email~

:+1:  looks good.


[ci] WIP: fix secrets

Closes https://github.com/paritytech/ink-waterfall/issues/20

@alvicsam Do you know if other tokens might be affected as well? For example, we have a lot here in ink! and some of them are only used when e.g. our fuzz tests would fail: https://github.com/paritytech/ink/blob/master/.gitlab-ci.yml#L86-L109.

@cmichi AKAIK they should be fine, we didn't change them


fix: Create auth file even if some parent dir does not exist

Codecov Report

Merging #1408 (a7fd1c0) into master (ad31f58) will decrease coverage by 0.21%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1408      +/-   ##
==========================================
- Coverage   99.19%   98.97%   -0.22%
==========================================
  Files          84       84
  Lines        6470     6466       -4
  Branches     1136     1107      -29
==========================================
- Hits         6418     6400      -18
- Misses         26       35       +9
- Partials       26       31       +5

Flag
Coverage Δ

unittests
98.97% <100.00%> (-0.19%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/schemathesis/service/hosts.py
100.00% <100.00%> (ø)

src/schemathesis/specs/openapi/validation.py
76.47% <0.00%> (-11.77%)
:arrow_down:

src/schemathesis/_compat.py
77.77% <0.00%> (-11.12%)
:arrow_down:

src/schemathesis/runner/impl/threadpool.py
98.21% <0.00%> (-1.79%)
:arrow_down:

src/schemathesis/extra/pytest_plugin.py
98.24% <0.00%> (-1.76%)
:arrow_down:

src/schemathesis/cli/callbacks.py
98.33% <0.00%> (-1.67%)
:arrow_down:

src/schemathesis/cli/cassettes.py
98.47% <0.00%> (-1.53%)
:arrow_down:

src/schemathesis/utils.py
97.71% <0.00%> (-0.92%)
:arrow_down:

src/schemathesis/service/worker.py
100.00% <0.00%> (ø)

src/schemathesis/cli/output/default.py
100.00% <0.00%> (ø)

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 ad31f58...a7fd1c0. Read the comment docs.


GraphicFeatures refactor and improvements

collection of current issues with GraphicFeature

events info is becoming a bit of a mess and needs more consistency with information returned by events, #174
support selections of multiple indices for collections (like selecting multiple contours or temporal traces with Ctrl + click for example). This would also involve changes to Interaction
#123
#132
#101
#85
allow passing unique integers for color labels, useful for sklearn classifier outputs:

I feel like as far the euclidean function goes we could add a default None mapping arg to link() that could take values like ["euclidean", "emd", etc.]

Oh I see, you are using mapping above to map changes between selection and cmap

I just got another idea of how we could use link, make it not just between graphics but also widget classes?
# for exampline LinearSelector for time
time_selector.selection.link(
  "selection",
  target=image_widget,
  mapping={"selection": "current_index.t"},
  bidirectional=True
)

Would require making current_index a @dataclass probably, with dimensions as the attributes, and it would have to have event handlers in order to be bidirectional. Or maybe we allow bidirectional only for graphic features?
I think we could make it such that you can do graphic.feature.link(), and make it use something from the pick_info to set the attribute of any other arbitrary object.
The brainstorming continues...

My initial thoughts are that I like this a lot, I think it will give us a lot more control with our interactivity and it would prevent us from having to make tons of event_handler functions
For instance, if this were possible, I would not need to have an event handler func to link my ethogram linear selector to the time dim IntSlider in my iw

The only thing I think we are missing is how to address more complicated mappings that we might have without passing a callback func in the link step


THuman2.0 test list

Hi thanks for great work!
Is it possible to provide THuman2.0 test list? Thanks!

Sorry about the late reply. We use the scans from 0505-0525 for testing.

What about the test views of these meshes for the texture rendering camparison?

We render four views of each mesh, 0, 90, 180, 270 for testing.


test_raftstore: error handling of call_command_on_leader

Signed-off-by: 5kbpers<EMAIL_ADDRESS>
What problem does this PR solve?
Issue Number:
close #3262
Problem Summary:
Sometimes leader could be elected slowly and also could be changed during CI running.
What is changed and how it works?
What's Changed:
Better error handling of call_command_on_leader to reduce the possibility of test fail.
Related changes

Need to cherry-pick to the release branch

Check List
Tests

Unit test
Integration test

Release note

Not available

#2649 calls call_command instead of request, seems not related to this PR.

#2649 calls call_command instead of request, seems not related to this PR.

Checkout to v2.1.0, it fails on https://github.com/tikv/tikv/blob/v2.1.0/tests/raftstore_cases/test_multi.rs#L422

You probably look at the wrong version. The stack said it panicked in function test_leader_change_with_uncommitted_log instead of must_transfer_leader.

You probably look at the wrong version. The stack said it panicked in function test_leader_change_with_uncommitted_log instead of must_transfer_leader.

@BusyJay Do the archaeological survey again, already removed it.

/lgtm

/merge


HADOOP-17887. Remove the wrapper class GzipOutputStream

As we provide built-in gzip compressor, we can use it in compressor stream. The wrapper GzipOutputStream can be removed now.

cc @sunchao

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 57s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
34m  1s

trunk passed

+1 :green_heart:
compile
22m 45s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
19m 17s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
0m 59s

trunk passed

+1 :green_heart:
mvnsite
1m 31s

trunk passed

+1 :green_heart:
javadoc
1m  1s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 34s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
2m 25s

trunk passed

+1 :green_heart:
shadedclient
18m 33s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 56s

the patch passed

+1 :green_heart:
compile
22m  5s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
22m  5s

the patch passed

+1 :green_heart:
compile
19m 18s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
19m 18s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 57s

hadoop-common-project/hadoop-common: The patch generated 0 new + 6 unchanged - 2 fixed = 6 total (was 8)

+1 :green_heart:
mvnsite
1m 29s

the patch passed

+1 :green_heart:
javadoc
0m 59s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 36s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
2m 34s

the patch passed

+1 :green_heart:
shadedclient
18m 21s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
17m  3s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 49s

The patch does not generate ASF License warnings.

189m  2s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3377/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3377

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux bb03b956ac24 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / a32b475667ac3df98986a1f84b5291e6b7da57bd

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3377/1/testReport/

Max. process+thread count
2016 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3377/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 56s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
33m 28s

trunk passed

+1 :green_heart:
compile
22m 40s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
19m 20s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
1m  0s

trunk passed

+1 :green_heart:
mvnsite
1m 32s

trunk passed

+1 :green_heart:
javadoc
1m  1s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 35s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
2m 25s

trunk passed

+1 :green_heart:
shadedclient
18m 23s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 56s

the patch passed

+1 :green_heart:
compile
22m 10s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
22m 10s

the patch passed

+1 :green_heart:
compile
19m 17s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
19m 17s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 58s

hadoop-common-project/hadoop-common: The patch generated 0 new + 6 unchanged - 2 fixed = 6 total (was 8)

+1 :green_heart:
mvnsite
1m 28s

the patch passed

+1 :green_heart:
javadoc
1m  0s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 36s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
2m 40s

the patch passed

+1 :green_heart:
shadedclient
18m 53s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
17m 59s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 46s

The patch does not generate ASF License warnings.

189m 49s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3377/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3377

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 3b7034dde0b3 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 728a659c3964d81612c917542426a9786984b1c9

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3377/2/testReport/

Max. process+thread count
1852 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3377/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

I did a microbenchmark by running 10 times of compressing/decompresing random data.
The average time:
After: 12.93s
Before: 13.52s
It is pretty close.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 58s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
33m 39s

trunk passed

+1 :green_heart:
compile
22m 46s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
19m 24s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
1m  1s

trunk passed

+1 :green_heart:
mvnsite
1m 32s

trunk passed

+1 :green_heart:
javadoc
1m  1s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 36s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
2m 27s

trunk passed

+1 :green_heart:
shadedclient
18m 19s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 56s

the patch passed

+1 :green_heart:
compile
21m 58s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
21m 58s

the patch passed

+1 :green_heart:
compile
19m 25s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
19m 25s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m  0s
/results-checkstyle-hadoop-common-project_hadoop-common.txt
hadoop-common-project/hadoop-common: The patch generated 1 new + 61 unchanged - 2 fixed = 62 total (was 63)

+1 :green_heart:
mvnsite
1m 29s

the patch passed

+1 :green_heart:
javadoc
1m  0s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
1m 37s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
spotbugs
2m 34s

the patch passed

+1 :green_heart:
shadedclient
18m 45s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
17m  6s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 49s

The patch does not generate ASF License warnings.

189m 16s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3377/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3377

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux de8f4df59f6d 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 3442e671682c2717cd7297b4ad009420adde8876

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3377/3/testReport/

Max. process+thread count
2993 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3377/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Merged. Thanks @viirya for the contribution!


FIX: coreg spin box calling set_parameter twice

This PR is extracted from #10224:

fixes the spin box "double call"

Maybe there is simpler... This is only what I suggest and tested locally :sweat_smile:

What do you think @larsoner ?

Why is this necessary? On main if I add a print(f'set {value} {mode_name} {coord}') as the first line in _set_parameter_safe, I already only get one value change per click I think (note that the "trans not shown at start" bug is still present on main):
$ mne coreg -s sample -d subjects -f MEG/sample/sample_audvis_raw.fif --trans MEG/sample/sample_audvis_raw-trans.fif

https://user-images.githubusercontent.com/2365790/151190271-2e399633-e970-476a-a01b-b8e2794bc79d.mp4
What I don't like is that the display seems to update twice, which I assume has to do with an errant update=True somewhere or something...

You do not have this behaviour... Is it only me then?
main
https://user-images.githubusercontent.com/18143289/151191083-133b5537-572b-4d06-a8d4-233fc4a88f25.mp4
PR
https://user-images.githubusercontent.com/18143289/151191116-96f97a30-2dd0-4839-8d08-82cb98162730.mp4

Oh you said in #10244

I tried using Qt.ConnectionType.QueuedConnection with PyQt5 5.15.6 but it still did not fix the issue locally.

It's too bad this didn't work :(

I am using PyQt5 5.15.6:
❯ python -c "import mne; mne.sys_info()"
Platform:       Linux-4.19.223-1-MANJARO-x86_64-with-glibc2.17
Python:         3.8.12 (default, Oct 12 2021, 13:49:34)  [GCC 7.5.0]
Executable:     /home/guillaume/source/anaconda3/envs/mne-py38/bin/python
CPU:            : 4 cores
Memory:         7.7 GB

mne:            1.0.dev0
numpy:          1.22.0 {}
scipy:          1.7.1
matplotlib:     3.5.1 {backend=QtAgg}

sklearn:        1.0
numba:          Not found
nibabel:        3.2.1
nilearn:        0.8.1
dipy:           1.4.1
cupy:           Not found
pandas:         1.3.3
pyvista:        0.32.0 {OpenGL 4.5.0 NVIDIA 495.44 via NVIDIA GeForce GTX 960M/PCIe/SSE2}
pyvistaqt:      0.8.dev0
ipyvtklink:     0.2.1
vtk:            9.1.0
PyQt5:          5.15.6
ipympl:         Not found
mne_qt_browser: Not found
pooch:          v1.5.2

I tried connecting the spin boxes with QueuedConnection two days ago but it did not solve the issue.

Every time we parallelize something we make debugging harder, but this seems to be a real bug on your system at least so I guess we have to live with the complexity. Feel free to merge if it does fix things for you @GuillaumeFavelier , I at least notice no change in behavior (in a good way) on my system.

Okay, but the other PRs have higher priority. Now that I know that this could be related to my system, I think I'll hold on a bit before merging.
I can try:

[ ] a fresh new conda env
[ ] a different version of PyQt5
[ ] a different OS (on the same system)

If you hit the bug, and it's a known behavior of Qt under some circumstances (based on the threads), it's at least somewhat likely some user will have this problem. We don't want to make them mess with Qt installs as a fix...

Amazing detective work, @GuillaumeFavelier!


Remove invalid com.azure.cosmos.models.JsonSerializable import

Removes invalid import com.azure.cosmos.models.JsonSerializable which has been moved into implementation. This resolves build failures being seen in the From Source builds for Azure Core.

@kushagraThapar if you could take a quick look.


add Design and API call for History page

This PR will add code for the Design and API call for the History page
In this PR, 401 additions and 46 deletions lines of code

some files contain only 5 to 6 lines of code
if you don't like you can avoid reviewing Backend related files

Please review this PR and give your feedback

To Log In, you can use these credentials
email<EMAIL_ADDRESS>password: johnDoe123

Live URL

Thank you for reviewing,


Fix put_bigendian_uint32()

The implementation of put_bigendian_uint32 and put_bigendian_uint24 is identical and the comments don't match. Therefor fix the former to really put uint32.

Good pick, merged.


clip-art type parameter changed

Looks like the type specification parameter (in the query) for 'clip-art' has changed from 'clip-art' to 'clipart'.  Should be an easy fix around this line.  Thanks for making the nice tool!

@ezavesky thanks for pointing this out. The issue was fixed in #172 . Closing this issue.


raidboss: Apply ESLint prefer-arrow/prefer-arrow-functions to 00-misc

Converted via:
find ui/raidboss/data/00-misc/ -type f | xargs -i sed -i 's/function((.*)) {/(\1) => {/' {}

I will also add that on this (and others), if there is a this being used in the function body of an arrow function, eslint will yell about it.  That's what led to #2896.  So, I think this is a relatively safe conversion.


Fix list_themes()

I actually misread the D7 documentation. list_themes() returns an associative array of objects.

Okay, after re-reading, I see it now, too. And the Extension object should work fairly close to a plain \stdObject object.
 * @return
 *   An associative array of the currently available themes. The keys are the
 *   themes' machine names and the values are objects having the following
 *   properties:


Fix/update hint and test for cat photo app course

Checklist:

[X] I have read freeCodeCamp's contribution guidelines.
[X] My pull request has a descriptive title (not a vague title like Update index.md)
[X] My pull request targets the main branch of freeCodeCamp.
[ ] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

@texas2010 You did not explain why the changes were made. Why were these changes necessary?

@RandellDawson Hello, I was going to explain when I am done with this PR and update my PR comment. (but I am still in the process of work and checking some lessons) but I can answer this. I did not know it was on purpose to ask users to write text anywhere if they did not put it in the h1 element.
At first, I thought test don't need to be there because there is the last test to check and ensure the CatPhotoApp text exists in the h1 element. Another reason I removed it because that test was blocked when the h1 element did not exist if users decided to delete the h1 element or change it. And it will ask the user to write the CatPhotoApp text.
And now, I realize it is a mistake to do that. As you explained, asking users to write it first if they did not use the element or put text into the h1 element is better.
I will revert it.

@texas2010 Yeah these hints have to be written in a particular order unlike the old curriculum, since only the first one that fails the tests shows up.  I wrote most of the tests for the first two projects in RWD section.  I spent extra time on the first half of the first project as evident with all the hints.  I did that to try "guide" the users to the solution taking in consideration the kinds of mistakes we have all seen on the forum as moderators over the past several years of the older RWD section.  I hope the hints/tests being written for the first half of the first JS project will be written with extreme beginners in mind or we will see mass confusion on the forum.
I will say that a lot of the projects that appear later in the RWD section seem to be more "Do x, y, and z" when new concepts are introduced and less explanation of why, but that is my opinion.  Those kinds of steps are fine if the user is forced to apply the same concept multiple times in a project, but if they are one-off without much explanation why, I do not think users will really "learn" the concepts.  Many of the more advanced CSS topics/concepts included in the later projects in the new RWD probably need 25% to 50% more steps to get more repetition of the concepts we currently see frustrating users in the current RWD curriculum.

Closing as discussed.


QA: Response Snake -> Camel; Request (body, query) Camel -> Snake

Hello.
Maybe someone can give me an idea where should I put the logic of converting properties?
Interceptor? Or just wrap fetch with some function that converts, and calls "wrapper".

@san4io
You can try

Using decamelizeKeys  on query/body inside onRequest interceptor
Using camelizeKeys on response._data when responseType is json  inside onResponse interceptor

Checkout humps for utilities related to (de)camelization
async onRequest({ options }) {
  if (options.params) {
    options.params = decamelizeKeys(options.params)
  }
}

Nice solution @huynl-96. I would suggest using unjs/scule which is a better alternative to humps.

Nice, I've just had a quick look at scule, definitely gonna give it a try.
Thank @pi0 for the suggestion

I'm interested in doing this, as well. In onResponse, should I just replace response._data with the case-modified version like this?
onResponse({ request, response, options }) {
   response._data = camelCaseKeys(response._data, { deep: true })
}

Returning a case-modified object doesn't seem to affect the result downstream:
onResponse({ request, response, options }) {
   return camelCaseKeys(response._data, { deep: true })  // Data in my Nuxt app is still snake_case
}

The documentation for the onResponse interceptor shows how to read the response data, but isn't clear on how to modify it before it goes on its way.


Eliminate RawDriver from Host struct / config.json

Unfortunately, I realized a bit too late that there are a couple of issues with this method. Originally it was intended to be the "preserved" state of the Driver between Machine runs, since the client side (which handles persistence to disk) doesn't know which interface is being used on the server side.
But now I have two main concerns with it having used and distributed it a while:

Users may not realize that the []byte is only a very thin layer of obfuscation and still contains trivially decodable secrets, so I worry that they'll post docker-machine inspect output that contains secrets without realizing it.
Some users (including myself) are accustomed to being able to change the values in the Driver JSON object, and have them affect the result of the run program.  This is not possible with 0.5.0 today and makes things like manually rotating AWS keys in the JSON (which, while not advised, is being done) difficult to impossible.

cc @docker/machine-maintainers

Out of curiosity -- are the AWS credentials being stored in this blob?

@charlesg3 Yes -- it's the reason why editing the config manually to update the credentials no longer works.

Ah, bummer. Can you describe any workflow that would allow updating the creds?

Hm, I know this is a terrible hack (and really we should fix this since I think manually editing configs is a valid use case), but until we roll out a solution you might be able to paste your desired driver JSON into the JSON literal in this Go program (probably as a Go file running locally): http://play.golang.org/p/JTzFal8zfJ and run the code to see the what you should put in the RawDriver field.  That might help until we can get a proper fix.  Does it make sense?
(There's probably a more elegant way to do this in Go, but this closely mimics what's actually going on in the actual Machine code).

Really sorry about this, and the issue is slated to be worked on for 0.5.1, which is scheduled to be released in about two weeks' time.

I'm willing to give that a shot for now. Happy to help try to work around these issues as things progress. There's huge potential for docker-machine to help our workflow but I think we have a particular usage pattern that may not be the usual.

Seems not too unusual to me so I'm happy to help.  In fact in the future I'd like to make the type of secret management you're doing by hand today a little more easy to do automatically.

Yeah that'd be awesome. Basically we realized how awesome docker-machine is but then realized we needed an ability to pass around the environments to different machines. Since we had vault setup we rely on the security model of that to pass things around (and patch up the directories / access keys and the like). It's sort of like a "machine repository" for us.

In that go function -- I simply provide the machine name and aws secret key in that program?

(It only has the key and not the access id, I would expect it to require both)

@charlesg3 You should paste the whole of the Driver JSON that you want to convert.

This seems to be working (for now) to renew the credentials.
Note that I am receiving the following errors:
WARNING >>> It looks like you have used an older Docker Machine binary to interact with hosts after using a 0.5.0 binary.
WARNING >>> Please be advised that doing so can result in erratic behavior due to migrated configuration settings.

Not sure how that is determined but things seem to be working.

@charlesg3 Yes due to the weird behavior the error falsely believes you have reverted to an older config schema.  It should be fine to ignore it and let us know if you run into any issues.

Hi @nathanleclaire :+1: for this. I was attempting to write some import/export tooling for docker machines and got tripped up by this RawDriver struct. Why base64 encode that at all?

@bhurlow It's just how []byte gets json.Marshaled by Golang.  It's kind of an implementation detail of the plugins' first iteration that, as mentioned, I'd like to get rid now that it's apparent it's not really needed.

ah! that makes sense thanks

Here is a snippet of how we did it in Python within a Docker Machine helper class:
    def inspect_machine(self, node):
        command = ["docker-machine", "inspect", node]
        info = json.loads(subprocess.check_output(command))
        return info
    def list_nodes(self):
        command = ["docker-machine", "ls", "-q"]
        nodes = subprocess.check_output(command).strip().split('\n')
        return nodes
    def update_aws_keys(self, new_token=None, new_access_key=None, new_secret_access_key=None):
        for node in self.list_nodes():
            info = self.inspect_machine(node)

            if new_token and new_access_key and new_secret_access_key and info['DriverName'] == 'amazonec2':
                info['Driver']['SessionToken'] = new_token
                info['Driver']['AccessKey'] = new_access_key
                info['Driver']['SecretKey'] = new_secret_access_key
                info['RawDriver'] = base64.b64encode(json.dumps(info['Driver']))
                path = info['HostOptions']['AuthOptions']['StorePath']
                self.__dump_config(path, info)

Yeah, hopefully we can tackle this in time for 0.5.2 (a couple of weeks from now).  Pretty high in importance IMO.

@nathanleclaire I gave it a shot and got lost!! I'm going to assign you

@miguelpuyol -- we've added a similar snippet to what's above to our own flow and it works for us. :+1:


CUDA out of memory

你好，
RuntimeError: CUDA out of memory. Tried to allocate 72.00 MiB (GPU 0; 1024.00 MiB total capacity; 378.05 MiB already allocated; 0 bytes free; 418.00 MiB reserved in total by PyTorch)
除了更换更高更强的GPU，有无其他的解决方案，谢谢

1G显存确实有点小，你是做inference还是training？

Closing due to inactivity.


Fork image updated

Added my details

Please resolve the merge conflicts and update the PR @EvilSeal1980

Good job @EvilSeal1980
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

SignIn / SignUp in ClueLess Website .

Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.


detect_mobile? should return false instead of nil

nil is a falsy in Ruby, so this is the correct behavior. Even the stdlib does return nil from predicate methods:
1.nonzero?
=> 1

0.nonzero?
=> nil

If you really really want a boolean, use !!browser.device.mobile?


Provide a way to pass in the custom parser during add_resource so it can be used in stream_remote_resources

In order to submit an issue, please ensure you can check the following. Thanks!

[3.6 ] Declare which version of Python you are using (python --version)
[Ubuntu ] Declare which operating system you are using

Currently I have to create a sseparate task in order to use a custom parser like this:
https://github.com/strets123/frictionless-pres/blob/master/smdataproject/stream_remote_resources_custom.py
This breaks pep8

Hey @strets123 - can you explain your use case here?

I would like to be able to make datapackage pipelines connecting to many disparate JSON, XML and HTML data sources. Often this requires changes to custom parsers of tabulator but I cannot then easily re-use the stream_remote_resources code. I do not want to copy and paste a whole module just to change one line. Therefore I resorted to the above hack of importing the dpp mopdule at the abottom of the file.
In the above case I had a JSON parser for the JSON API spec that also did pagination. This follows a similar pattern to the SQL data parser. I also have a similar one for SPARQL endpoints.
To frame the issue in another way problem when reusing code from the dpp project is that the CSV dump code is class based and can be easily overridden but the stream_remote_resources module has import time logic making its re-use difficult.

If there is a desire to retain the simplicity of functional approach for dpp modules, might it be possible to have a magic "run" function. This would retain backwards compatibility but if users wanted they could put their import time logic in the run function instead.
This would allow users to override specific functions without a full class-based approach.


Teach OkHttp to lookup the X509TrustManagerFactory.

Right now there's problems with our ability to confirm certificate pins with
root certificates because we don't actually know which certificate authority
was used.
This unblocks that work.
This code is particularly fragile and gross. There's no API to get the
TrustManager from an SSLSocketFactory. We can potentially change the way
that we compute the initial SSLSocketFactory, but this approach is most
general.
This is motivated by https://github.com/square/okhttp/issues/1699

Manually tested on OpenJDK 7, OpenJDK 8, Android 2.3, Android 4.1, and Android 6.0.

Hmm, the problem is I use okhttp as a transitive dependency of retrofit. Is there a snapshot build?

Snapshots are here:
https://oss.sonatype.org/content/repositories/snapshots/com/squareup/okhttp3/okhttp/3.3.0-SNAPSHOT/
You'll have to configure your build tool to import snapshot builds.

Thanks, found them and that seems to work. I think I can even just leave it and use the code in defaultTrustManager().


alpinewsl: Add version 3.15.0-0

Add AlpineWSL 3.15.0-0 .
Manifest is directly modified from ArchWSL.

[x] I have read the Contributing Guide.

/verify

You'll need to use a custom checkver regex because the "github" checkver does not recognize hyphens.

/verify

/verify

/verify


SendKeys to Multiline TextBox misses first letter

When sending multi line text using SendKeys to a TextBox (Wrapping enabled) in a UWP app, first letter is missed. This is easily reproducable but does not occur always. Also calling click before SenKeys workaround seems to always work, but is annoying.
Example
element.SendKeys("Orange\rtree");

Most of the time ends up as "range\rtree"
OS - 16299

Thanks for calling this out @harvinders - can you (or @AmitVerma4HP) share a small test case to help us validate this issue?

Sorry for late response. This issue was very straight but not always reproducible.
Try typing "testfiles" in Search in Photos Apps then it misses "t" (first letter).
CODE:
// Search for Saved Pictures folder.
PhotosSession.findElementByName("Search").sendKeys("testfiles");
log.info("Searching "Test Folder - testfiles"");
Thread.sleep(1000);
App Screenshot


To summarize 90% the issues

I recon you can summarize most of the issues into one:
FactorySkyline resets every change in the keybind configuration.
I would like to not see any other issue that addresses the same topic because it's not necessary to spam the dev with the same issue all the time.

I will use a independent input system to solve all the problems.
You know this mod is not embedded to the interface as a recommended way. I think it is the only way to avoid key conflict.


Upgrade cmake on all buildbots

Once 0.5.0 is out the door, upgrade cmake on all the buildbots to at least 3.4.3.  This script, newly updated, should work just fine.
Note; do NOT upgrade mingw cross-compilers to 5.4,  we need to keep those held back to 4.9 until we have a solution for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77333

Can we upgrade cmake just on power for now, so https://github.com/JuliaLang/julia/pull/18557 can be merged? Since the power buildbot is so new it's not a huge deal if the power build of an upcoming release gets delayed a tiny bit.

Should be done.  Feel free to try it out.

I don't think it's on the path yet? https://build.julialang.org/builders/package_tarballppc64le/builds/88/steps/make/logs/stdio

Needed to shuffle around the PATH priorities in .bash_profile.  Restarted as https://build.julialang.org/builders/package_tarballppc64le/builds/89

did that also result in a different compiler getting used? missing glibcxx version symbols?

Yes it did!  Apparently we weren't using the GCC 6.2 that I custom built on there before now.  I'll just nuke and restart.

New build: https://build.julialang.org/builders/package_tarballppc64le/builds/92

oh you had done a gcc build there? didn't realize. this is a system we share with people right? so not feasible to run on some older centos 6 (if that works on power)? do we have permissions to run in a vm? might be a little slower but it's already our fastest buildbot

I don't think we have any virtualization software installed.  Would Docker be enough?

yes, if that works on power. then we'd need to port your ansible scripts to dockerfiles which I'd kind of prefer myself, at least for linux

or install ansible in the docker image I suppose

The ansible scripts have the advantage of being the same across all platforms, I'd kind of like to not split the configuration.

Looks like it's missing one of the environment variables or make flags that we had to be careful about, to point at the right libstdc++ from the built gcc?

Fixed via
PATH=$HOME/local/bin:$HOME/bin:$PATH
LD_LIBRARY_PATH=$HOME/local/lib64:$HOME/local/lib:$LD_LIBRARY_PATH

export PATH
export LD_LIBRARY_PATH

In ~/.bash_profile.  Silly me for forgetting.  New build going through here.

This will need doing on the centos 5 intel buildbots before we can merge https://github.com/JuliaLang/julia/issues/19123

Done, let's go ahead and test it.

windows buildbots need this too, they're on the 3.3 cygwin package - be very careful if you upgrade this through cygwin setup though, need to manually switch to "keep" on all the mingw cross compilers to stay at 4.9

Note; do NOT upgrade mingw cross-compilers to 5.4, we need to keep those held back to 4.9

Note; do NOT upgrade mingw cross-compilers to 5.4, we need to keep those held back to 4.9

Thanks for reminding me of that, I do not remember writing that, and would have thought it was a good idea to upgrade everything.  :P  Windows buildslaves are updated as well now.

I think something's broken about the cmake you just installed, it doesn't run cmake --version. And I'm having trouble finding where the buildbot clone lives to get https://github.com/staticfloat/julia-buildbot/commit/22eb0736b232d297f71571a03e7ccf6b45cfd89e to take effect

I did notice that myself, but I seemed to remember something about windows cmake acting very strangely.  The buildbot instance on<EMAIL_ADDRESS>in ~/buildbot.  I've reloaded it.

"very strangely" doesn't usually involve exit status of 127. How did you install it? Adding cygwin gdb might be useful for this.

I installed it through the cygwin setup, selecting keep for everything except cmake and cmake dependencies.  I'll add gdb.

oh, should allow the other stuff like the cygwin dll etc to get upgraded, the cross-compilers should be the only thing you need to hold back

Looks like it needed a reboot.  cmake is much happier now and everything non-mingw is upgraded:
$ cmake --version
cmake version 3.6.2

CMake suite maintained and supported by Kitware (kitware.com/cmake).

Ah, maybe the buildbot process or something was keeping some old library loaded. Something is still a bit flaky, jobs are pending for way longer than they should be...

The win32 builder is going to need another shutdown, reboot, and rebaseall of all cygwin processes, buildbot was dying in fork failures. Once that's back up I think we can call this closed.

Done.
-E
On Thu, Dec 22, 2016 at 7:40 AM, Tony Kelman<EMAIL_ADDRESS>wrote:

The win32 builder is going to need another shutdown, reboot, and rebaseall
of all cygwin processes, buildbot was dying in fork failures. Once that's
back up I think we can call this closed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/staticfloat/julia-buildbot/issues/54#issuecomment-268825411,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAH_aO15OKDEkFUQS6z0ZSxmFAWbak2Bks5rKpn2gaJpZM4J_qAZ
.

still having trouble? https://build.julialang.org/builders/package_win6.2-x86/builds/1017/steps/Julia checkout/logs/stdio

For future reference, rebasing, enabling ASLR, and removing/recreating the python virtualenv and restarting seems to have done the trick.

You forgot to not upgrade the cross compiler. Need to use cygwin time machine to downgrade back to 4.9

Shoot, on the very last invocation I must have forgotten to check "keep"
for those packages.  Urgh.
I'm unable to get manual package installation or the time machine to work.
The time machine looks to be down today, not sure what other choices we
have.  My dislike for cygwin increases, despite this problem being my own
fault.
-E
On Thu, Dec 22, 2016 at 2:36 PM, Tony Kelman<EMAIL_ADDRESS>wrote:

You forgot to not upgrade the cross compiler. Need to use cygwin time
machine to downgrade back to 4.9
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/staticfloat/julia-buildbot/issues/54#issuecomment-268906048,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAH_aLhjT9fLLays8EigS-0qQxbJmn1Fks5rKvtigaJpZM4J_qAZ
.

if you still have the downloads locally, it's possible to manually modify the setup.ini listing and use a local copy to act like 4.9.2 is the latest version, from your local files. if you don't have them locally, I can put my copy somewhere along with a setup.ini that I had used.

Yes, looks like I still have the old files cached locally.  What do I need to do with my setup.ini file?

IIRC, change the version numbers and checksums for the mingw packages to match 4.9.2 instead of 5.4

cygwin makes everything a bit of an ordeal, but calling this done now. thanks!

I attempted to run the ansible script on buildslave_centos7.1-x64 (which we missed), but didn't succeed - ERROR: become is not a legal parameter in an Ansible Playbook. Could you run that?

Sure thing.  That error means, (I believe) that your ansible version is too
old.
-E
On Thu, Dec 29, 2016 at 12:52 PM, Tony Kelman<EMAIL_ADDRESS>wrote:

I attempted to run the ansible script on buildslave_centos7.1-x64 (which
we missed), but didn't succeed - ERROR: become is not a legal parameter
in an Ansible Playbook. Could you run that?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/staticfloat/julia-buildbot/issues/54#issuecomment-269691772,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAH_aEmIzaMAceIfsMeQdr5V8MHvv7fyks5rNB2mgaJpZM4J_qAZ
.


Weekday.daysUntil

Nice library !!
I think there is a little bug. The test fails for wed.daysUntil(.mon) and wed.daysUntil(.sun).
test "daysUntil" {
    const wed: Weekday = .wed;
    try std.testing.expectEqual(0, wed.daysUntil(.wed));
    try std.testing.expectEqual(6, wed.daysUntil(.tue));
    try std.testing.expectEqual(5, wed.daysUntil(.mon));
    try std.testing.expectEqual(4, wed.daysUntil(.sun));
}

Probably it has something to do with -% or +% because u3 has 8 values, not 7.

Ooh good find.
This is because the algorithm assumes a larger integer than a u3. It's relying
on underflow to work:
https://howardhinnant.github.io/date_algorithms.html#weekday_difference
For Wednesday -> Monday, the math is:
Monday (1) - Wednesday (3) = -2
-2 as a u3 = 6, but we are checking if the difference is <= 6 so we return 6
instead of adding 7.
If we do this as a u8, -2 is 254. Add 7 with overflow, and we get 5.


Refine isGhes logic

Description:
I'm fixing the logic within helper method isGhes to ensure that it doesn't misrecognize GitHub Enterprise Cloud instances as GHES instances.
Related issue:
https://github.com/newsroom/press-releases/data-residency-in-the-eu
Check list:

[ ] Mark if documentation changes are required.
[x] Mark if tests were added or updated to cover the changes.

I'm not sure why CI/CD is failing.  Looks like rate limiting?

k

k

k


qbe: unstable-2020-10-05 -> unstable-2021-06-17, enable tests, add passthru.tests

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

[x] (Package updates) Added a release notes entry if the change is major or breaking
[x] (Module updates) Added a release notes entry if the change is significant
[x] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 127674 at d2a8d3c6 run on aarch64-linux 1

1 package failed to build:

qbe

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.


Adding missing TOC.

Added missing TOC entry for capabilities vocabulary extensions.

Docs Build status updates of commit 732a4c7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Odata-docs/TOC.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Update chihuahua to v5.0.2

Chihuahua chain will be upgraded to v5.0.2 at block 9180000.
https://www.mintscan.io/chihuahua/blocks/9180000
Estimated Time:  Sep 11th 2023, 16:42:34
Proposal: https://www.mintscan.io/chihuahua/proposals/53

ghcr.io/akash-network/cosmos-omnibus:v0.3.47-rc2-chihuahua-v5.0.2


feat: record and replay any remote backend

⚠ TECH PREVIEW ⚠
This PR introduces the capability for the syndesis dev server to interact with any backend - local or remote - through a proxy set up by CRA and record the responses to be able to replay them in a later moment (eg. for testing).
This effectively removes the need to have the whole syndesis dev environment installed locally for the most common development needs.
There are two new scripts available to run, one in the syndesis app:

start:mocks:record that's used to connect to a backend and record it
start:mocks:replay that's used to replay a previously recorded session

How to connect to a backend and record a session
BACKEND=https://syndesis.<IP_ADDRESS>.nip.io yarn start:mocks:record

This command will:

set up an hand-crafted config.json that sets apiBase to be the same as the development server address, to allow us to intercept requests to /api
ask the user to login against the provided BACKEND to retrieve the right Cookies to use with the proxy. This is done by a Chromium instance controlled by Puppeteer through the syndesis/scripts/get-login-cookie.js script.
pass the cookie to the proxy and fire an instance of talkback (that's the underlying tool that does the actualy proxing, recording and replaying of the requests) running on localhost:556
record the requests done while using the app

Recordings will be stored in syndesis/tapes/[sanitized BACKEND]. Additional recording session will extend/update a previously recorded one.
For the moment, tapes will not be saved under version control.
How to replay a session
BACKEND=https://syndesis.<IP_ADDRESS>.nip.io yarn start:mocks:replay

This command will:

set up an hand-crafted config.json that sets apiBase to be the same as the development server address, to allow us to intercept requests to /api
will use syndesis/tapes/[sanitized BACKEND] as the tapes source
in case of requests that are not available in the tapes, a 404 response will be returned

Further work ideas
We could maybe make the script more flexible, decoupling the proxing by the recording. The reasoning is that being able to proxy a backend as effortlessly as it's now possible to do is something that has value by its own, where recording a proxied session is something that could be done for specific reasons, eg. to record a specific scenario we want to use in a later moment for testing.
So maybe BACKEND=http://... yarn start:proxy would be a better way to fire up the proxy, and BACKEND=http://... yarn start:proxy:record some-scenario-name could be used instead to fire up a proxy and record it under syndesis/tapes/[some-scenario-name] (with yarn start:proxy:replay some-scenario-name to replay it).
Demo
<EMAIL_ADDRESS>

Taking the time to finally review this and try it out since I'm thinking of borrowing some stuff :-)

Also when running yarn start:mocks:record (I dunno why I foolishly decided to first run `yarn start:mocks:replay :smile: ) am I supposed to need to close the browser window after logging in and getting redirected to staging?  If I let it sit there I see a timeout exception in the script output, same behavior if I close it, and then in either case I see that all the backend requests are getting oauth redirect responses rather than the proper API response.

Also when running yarn start:mocks:record (I dunno why I foolishly decided to first run `yarn start:mocks:replay 😄 ) am I supposed to need to close the browser window after logging in and getting redirected to staging? If I let it sit there I see a timeout exception in the script output, same behavior if I close it, and then in either case I see that all the backend requests are getting oauth redirect responses rather than the proper API response.

That window should close on its own. If it doesn't then the script that intercepts the cookie isn't working properly. Just wondering, is the BACKEND url you provided with or without an ending /? Because I found it should not have the ending / to work.

Yep, that sorted it, thanks @riccardo-forina!

phew 😂 yeah that behavior should be documented, or the script should warn about this if a trailing / is found

I ain't complaining too much, it's awesome seeing it working :-)  So +1 for merging once the port's changed.

New commands:
BACKEND=https://syndesis.<IP_ADDRESS>.nip.io yarn start:proxy to start a proxy to BACKEND without any recording or replay thingy.
BACKEND=https://syndesis.<IP_ADDRESS>.nip.io yarn record session-name to start a proxy to BACKEND and recording all requests/responses in a folder named session-name
yarn replay session-name to proxy all requests to the mock server in replay-only mode, using the previously recorded session session-name to load the tapes.
WIP: figure out how to set up the app in jarn tests so to fire up the mock server on demand pointing to a previously recorded session, to simulate e2e testing.

The mock server is also available as a stand alone script in  ./scripts/mock-server.js
./scripts/mock-server.js
mock-server.js replay <session>

Replay the previously recorded <session>

Positionals:
  session

Options:
  --version         Show version number                                [boolean]
  --port            This server port.                   [number] [default: 8556]
  --recordingsPath  Path where to load and save recorded sessions.
                                                              [string] [default:
                 "/Users/riccardoforina/Code/syndesis-react/dev/syndesis/tapes"]
  --silent          Disable requests information console messages in the middle
                    of requests.                                [default: false]
  --summary         Enable exit summary of new and unused tapes at exit.
                                                                [default: false]
  --debug           Enable verbose debug information.           [default: false]
  --help            Show help                                          [boolean]

Examples:
  mock-server.js dashboard  Replays a previously recorded session named
                            dashboard

Not enough non-option arguments: got 0, need at least 1

./scripts/mock-server.js record
mock-server.js record <session> <host>

Record a <session> proxying request to <host>. If <session> already exists, it
will be updated.

Positionals:
  session                                                             [required]
  host     The remote backend host                                    [required]

Options:
  --version         Show version number                                [boolean]
  --port            This server port.                   [number] [default: 8556]
  --recordingsPath  Path where to load and save recorded sessions.
                                                              [string] [default:
                 "/Users/riccardoforina/Code/syndesis-react/dev/syndesis/tapes"]
  --silent          Disable requests information console messages in the middle
                    of requests.                                [default: false]
  --summary         Enable exit summary of new and unused tapes at exit.
                                                                [default: false]
  --debug           Enable verbose debug information.           [default: false]
  --help            Show help                                          [boolean]

Examples:
  mock-server.js record dashboard           Replays a previously recorded
  https://syndesis.<IP_ADDRESS>.nip.io      session named dashboard

Not enough non-option arguments: got 0, need at least 2

PR Storybook available here

PR Storybook available here

PR Storybook available here

PR Storybook available here

PR Storybook available here

This should hopefully be in better shape now.

storybook for the app is gone.
Jest for the app should be usable.
the mocks recorder/replayer has its own CLI, to hopefully make it easier to work with it.
Cypress for integration testing is now available for the app. There is a single test right now to showcase how it works; to see it working you'll need yarn replay running, and then in another shell yarn run cypress open

Cypress is in "preview mode", it's not integrated to CI and I don't expect us doing that anytime soon. At least not until we have a critical mass of Cypress tests, which means that we have eaten our own dogfood and fixed the millions of bugs I introduced with this.

Oh, I also reworked the README a bit. Any feedback about it is appreciated!


restyle readmore buttons

Build log
Preview build with this PR (bac9ad8a53e83f6435d29de6bd2e21277fd0a667)

more info:cloud: Storage Free space   5.31 GiB    35.38%:open_file_folder: 111.50 MiB  CI_WORK/GitHubActions/roki-web


sqlmap: 1.0.11 -> 1.1

Additionally disable sqlmap for python3 as it is incompatible:
"[CRITICAL] incompatible Python version detected ('3.6.1'). For successfully running sqlmap you'll have to use version 2.6 or 2.7 (visit 'http://www.python.org/download/')"
Motivation for this change
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

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

Ew, this conflicted with 7a6b150f94b, /cc @FRidh & @Mic92.  I resolved now for the other commit, but I mainly didn't want to spend much time resolving conflicts between staging and master that are unrelated to my changes.  There were more conflicts, usually trivial where I went for fetchPypi over fetchurl.
A couple more complex cases: for mitmproxy I took the version from 27ac74daa586 and not 19183d17ed; for flask-testing I took 9b65bc9649 over d58e1f1c7b (different hashes! so I tested).

Thank you @vcunat. It's really hard to prevent these kind of issues when staging is blocked from merging. I won't attend NixCon but I hope this topic will be discussed.

"blocked" because of slow rebuilds, or do you know about another problem?

When staging is in a state that it cannot be fixed, fixes are contributed but often at the same time new breaking commits are merged/pushed as well, thus "blocking" staging from being merged.

That will be difficult, I think, but we should find some way to improve it.  As announced, staging is for non-breaking changes only, but in practice it's difficult to always use it that way.  (Because one doesn't have any darwin machines, for example.)


Not excluding recommendations

Actual word: ABLED
1st: HILLS
2nd: ALLEL
Not excluding ALLEL from the list despite grey L in 2nd and 5th position

fixed


Emit normal_roughness compatibility code in custom functions

Fixes: https://github.com/godotengine/godot/issues/94777
When reading from the normal_roughness buffer we need to emit compatibility code to ensure that the user gets proper normals even though the texture is stored in a custom format.
In master the compatibility code is only added when the normal_roughness uniform is used directly. When the normal_roughness uniform is passed as an argument to a custom function the compatibility code is not used.
This PR does two things:

It checks if the source of the argument is a a screen_texture and emits the compatibility code if it is
It bans passing a screen texture to custom function if the custom function is already used with a non-screen texture (we already had this logic in place for when two uniforms were used with different filter or roughness settings)

As a bonus, we can now undo the restriction added in https://github.com/godotengine/godot/pull/72300 which forbid passing screen textures to custom functions when using XR shaders.

Thanks!


musicpd album url list ?

can i download from this url ? https://music.bugs.co.kr/musicpd/albumview/41677
or how can i  get track url form that address ?
thank you in advance.

Playlists aren't supported, and there's no current intention to support them in the future.
You'll need to download the respective albums of the tracks you want.


Nodes with many trigger pins construct in a random order

If a Metasound node contains many trigger outputs they will construct in a seemingly random order.

Hi @kellermcdivitt thank you for reaching out here, I'm taking a look -- just to confirm, are you using the main or develop branch of this repo?

main

Thank you for this! So, essentially we've got two issues:

pins from inlets/outlets don't sort based on the index of the inlet or outlet
we don't have any sort of sorting for pins from inport/outport. we could explore having something users put in meta, lexically sort, or etc.


Append to an existing table in SQL

How can we go about appending additional rows to an existing table?
The append option doesn't seem to work.
bcpy.SqlTable(sql_config, table=table_name, if_exists='append')

Please use the

use_existing_table=True

argument.
https://github.com/titan550/bcpy/blob/f57aadf8857c5bcb571d85cf4a837b3ce816312e/bcpy/data_objects.py#L146


New package: EnforcedTypeSignatureCallables v1.0.0-DEV

Registering package: EnforcedTypeSignatureCallables
Repository: https://gitlab.com/nsajko/EnforcedTypeSignatureCallables.jl
Created by: https://gitlab.com/nsajko
Version: v1.0.0-DEV
Commit: 1282fc732b1eab6a8f67b450fc9b860dea500868
Git reference: HEAD
Description: A tiny Julia package providing a simple wrapper type for enforcing the argument and return types of a wrapped callable object. Basically provides a way to express a type signature for a callable in Julia's type system.

#111416


Config not checked for mod integration

The config option is not used for checking whether to perform mod integration when generating copper and tin ore, except for "thermal_foundation". The config is ignored for "mekanism" and "immersiveengineering".
The issue is due to missing parenthesis; it's an order-of-operations issue for boolean operations.
https://github.com/AlgorithmLX-Team/DimOre/blob/69d10433dd02bea3898971e8649eb3e4a9473955/src/main/java/com/algorithmlx/dimore/setup/DimOreReg.java#L76-L84

Also, as a feature suggestion: a config to force the nether/end copper/tin ore to spawn, regardless of installed mods, would probably be a good idea, in case someone is using a mod with copper/tin other than mekanism, immersive engineering, or thermal foundation.

hmm.. then I will only leave the config to check so that the ore does not depend on these mods. I was just going to make sure that ore appears only when these mods are installed, but apparently I have to abandon this idea

fixed


chore(TDI-38134): avoid test failed in SalesforceSessionReuseTestIT.testUseExistingConnection

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)
SalesforceSessionReuseTestIT.testUseExistingConnection() test failed randomly
I guess the session is not disabled in some situation.
What is the new behavior?
Move the faild part into try catch behind invalidSession(connProps, null);
Does this PR introduce a breaking change?

[x] No

Other information:
https://jira.talendforge.org/browse/TDI-38134

Pull request test result: failure :x:

Pull request test result: success :star:

Pull request test result: success :star:

Pull request test result: success :star:

@sgandon
I have push new commits to ignore 2 tests testUseExistingConnection() and testOutputReuseSession() which failed randomly. But can't find a good way to fix it.
I can't reproduced that in my local side.

Pull request test result: failure :x:

Pull request test result: failure :x:

Pull request test result: success :star:

@jzhao-talend LGTM, you can merge it whenever you want.


Add all Aave V1 and V2 tokens

Currently, we only display icons for tokens V1 (below you can see how it looks from my wallet perspective) https://etherscan.io/token/0xfC1E690f61EFd961294b3e1Ce3313fBD8aa4f85d?a=0x80cc263cb3fa1be2aec748b3811261c1e2a1ba8d
we need this for V2 too
https://etherscan.io/token/0x028171bca77440897b824ca71d1c56cac55b68a3?a=0x80cc263cb3fa1be2aec748b3811261c1e2a1ba8d
Zeplin: https://zpl.io/bWl54p1
and please add all aTokens.

@hboon can u help me with adding this images, how can i find right contrats for this aave tokens?

@hboon can u help me with adding this images, how can i find right contrats for this aave tokens?

i found that there is several places where we can find aave tokens, but how can i select right one?
https://etherscan.io/accounts/label/aave-v2
https://etherscan.io/tokens/label/aave?subcatid=0&size=50&start=0&col=3&order=desc

i found that there is several places where we can find aave tokens, but how can i select right one?
https://etherscan.io/accounts/label/aave-v2
https://etherscan.io/tokens/label/aave?subcatid=0&size=50&start=0&col=3&order=desc

@colourfreak if you have acquired them, can you help to list them? Otherwise we’ll have to figure out another way.
@vladyslav-iosdev usually they will list it in their docs. Try looking there too?

@colourfreak if you have acquired them, can you help to list them? Otherwise we’ll have to figure out another way.
@vladyslav-iosdev usually they will list it in their docs. Try looking there too?

@hboon seems like we can follow these links
https://etherscan.io/tokens/label/aave
https://etherscan.io/tokens/label/aave-v2

@hboon seems like we can follow these links
https://etherscan.io/tokens/label/aave
https://etherscan.io/tokens/label/aave-v2

@vladyslav-iosdev Ok

@vladyslav-iosdev Ok


mac12.5 - Unable to install the staging app

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.3.91-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Launch the url https://staging.new.expensify.com/NewExpensify.dmg
Download and open the application

Expected Result:
App installed on device
Actual Result:
Unable to install the app
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

https://github.com/Expensify/App/assets/78819774/9a50eed0-2888-4963-b9ff-e34cde762413

View all open jobs on GitHub

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

I think I might have broke this with: https://github.com/Expensify/App/pull/30299 Looking into it

Confirmed there is a difference in arch when building on an M1 runner:

@lanitochka17 can you try to install again? This should be fixed now I think.

Applause confirmed here: https://expensify.slack.com/archives/C9YU7BX5M/p1698284083405129?thread_ts=1698270511.559109&cid=C9YU7BX5M
Closing


Exec tachikoma update<PHONE_NUMBER>0307

:hamster::hamster::hamster:   Strategy david
Powered by David Update as a Service - Tachikoma.io Announcement: 2015-06-28 Updated permissions - Tachikoma.io

Coverage decreased (-2.2%) to 75.87% when pulling ee2a828fa73153cc5aa6cb9b8ef7fb1a31f89a8c on pazjacket:tachikoma/update-20161204170307 into 561aeec19d8836578f0838fe4cbff883050bb66d on festivals-tech:master.


Support CDC from MySQL

Is your feature request related to a problem? Please describe.
I would like to use data-prepper to ingest CDC from MySQL database, including Aurora DB
Describe the solution you'd like
Support Kafka Connect with Debezium MySQL connector plugins
Describe alternatives you've considered (Optional)
N/A
Additional context
connect-pipeline:
  source:
    kafka_connect:
      worker_properties:
        group_id: group
        config_storage_topic: pipeline-configs
        offset_storage_topic: pipeline-offsets
        status_storage_topic: pipeline-status
      mysql:
        hostname: localhost
        credentials:
          type: plaintext
          username: username
          password: password
        tables:
          - topic_prefix: prefix1
            table_name: dbname.tableName1
          - topic_prefix: prefix2
            table_name: dbname.tableName2

@wanghd89,
Thanks for this proposal. I like the concept of using Debezium and Kafka Connect. This could work nicely with the Kafka buffer concept.
In Data Prepper, sources represent the source from which Data Prepper gets data. In the current proposal, this is a bit inverted. The source name kafka_connect is somewhat of an implementation detail, not a source.
I'd like to see sources based around the actual source rather than the way the source operates with Data Prepper.
connect-pipeline:
  source:
    mysql:
      hostname: localhost
      credentials:
        type: plaintext
        username: username
        password: password
      tables:
        - table_name: dbname.tableName1
        - table_name: dbname.tableName2

Data Prepper's new extensions concept can supply the necessary configurations for configuring Kafka Connect under the hood. In data-prepper-config.yaml:
extensions:
  kafka_connect:
    topic_prefix: myprefix1

See #2588 for the extensions proposal. And #2851 for the recent PR which adds support for configuring extensions in data-prepper-config.yaml.


feat: add "Sync" button re-calculates correlation from current URL.

Fixed text "correlation signals => correlated signals"

@alanconway can you attach some screenshots so @fkargbo can check from UX perspective?
/hold

Overall looks good, just saw a few small things to clean as far as formatting and patternfly alignment goes

Will rebase on #38 when it merges as a simpler and more stable base.

Talked to ts so @fkargbo , he agreed that we can commit this as is and he will provide a better UI design later.
Still holding, depends on #38

/lgtm


Integrate with Visual Studio or Adding Bito CLI

Hi,
Can you integrate with Visual Studio (not visual studio code)? Or can you adding bito cli too?

You can clone the repository and recreate the project by opening the .proj or .sln file in Visual Studio.


Windows - rename event is split into two events

I'm on Windows 11 and it seems like rename events are sending two events, unlike the example in the README where there is one event with both the old and the new name.  First the old name is sent, then the new name and  associated is always nullptr.

I have a potential fix for this, I will post a PR tomorrow...

I have not given Windows the care it deserves.
Any help getting Windows up to par is greatly appreciated.

Also, if it's easier for you/depending on what you prefer, you can choose to make changes directly in the amalgamated include/wtr/watcher.hpp file.
Currently, we're set up to amalgamate relevant files in devel/ into include/wtr/watcher.hpp.
However, it's an extra step, and the library is small enough that working directly on a single file might be more convenient/natural.
So, up to you, but we can just remove the whole amalgamation step and whatnot if it suits you.

@e-dant - did you mean to close the other issue?  This one is still open FWIW


citrix_receiver: allow custom certs and hooks for the installation

Motivation for this change
Sometimes it's required to modify some parts of the Citrix build on
their own which is why {pre,post}Install hooks can be quite helpful.
Additionally some corporate clients use their own certificates that
aren't stored as trusted ones in the cacert package with all of the
trusted certs by Mozilla.
Now it's possible to add custom certs like this:
with import <nixpkgs> { config.allowUnfree = true; };

let path = ../../Downloads/custom-corporate-cert.pem; in
citrix_receiver.override {
  extraCerts = [ path ];
}

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

Note: I'm currently testing against older Citrix versions, it currently works with 13.10 though.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: citrix_receiver
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: citrix_receiver
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

just tested my patch with the oldest citrix version available in nixpkgs (13.4.0) and it works fine as well

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: citrix_receiver
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: citrix_receiver
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-linux (full log)
The following builds were skipped because they don't evaluate on x86_64-linux: citrix_receiver
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: citrix_receiver
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.


Add content/es/docs/concepts/overview/components.md

Follows the awesome @bureado work, applies the pending suggestions from #14678 and adds all the missing glossary terms that were causing the build failure.

@raelga that was just an informal review - I'm confident you understood what fixes I was suggesting

/cc @emedina :D

If you did have time to rebase this further @raelga you could probably cut it from 16 commits down to 1

Gracias @emedina, he aplicado tus sugerencias en https://github.com/kubernetes/website/pull/22259/commits/f3b21722e20f324faa919a40f1668ee6e1535101.
Échale un vistazo y me dices!

@raelga that was just an informal review - I'm confident you understood what fixes I was suggesting

I reduced the number of commits, anyhow, this will be squashed on merge.

I've marked this for squash on merge (the default is now merge-method-merge).

/lgtm

I've marked this for squash on merge (the default is now merge-method-merge).

Good to know, thanks! I like to keep some minimum number of logical commits to make easier reviewing and working on the documentation. I will add the label on the next PRs!

/lgtm

Thanks @emedina !
/approve

One more thing on squashing @raelga - if the commits are squashed down as much as you think they can go and each commit message describes a logically separate change, then there's no need to select a squash merge method.

Looking back at this, it's fine, I'd be happy to see that sequence of commits go in as a merge. When I saw more than 30 though I was thinking it could definitely use a tidying.

The 30 commit spike was just the result of accepting all @emedina suggestions. It makes easier to accept all the suggestions using the GitHub PR discussion interface and then squash them into a single accepted suggestions commits coauthored by the reviewer. But you catch me in the middle of the process :P.


docs: Fix type definition code broken by v0.24

Fixes #154

Not sure why checks failed - did I cause that?

Thanks for making a PR! Don't worry about the check that fails, that's something we need to fix.


inlay_hints ui and doc improvements

This is not intended to be exhaustive, but document UI and doc improvements for inlay hints.

Need a new screen grab showing inlay hints in action
Create wiki explaining the current state of inlay hints and what to expect now and in the future


mount .pkgcache for DOCKER_INCREMENTAL_BINARY

- What I did
Made make binary 6x faster
The build cache was introduced in https://github.com/docker/docker/pull/19071, but the cache was not used when we run make binary from the host rather than running hack/make.sh from inside the build env container.
- How I did it
Add the following args to DOCKER_MOUNT, if DOCKER_INCREMENTAL_BINARY is set.
-v .pkgcache/gopath_cache:/go/pkg
-v .pkgcache/vendor_cache:/go/src/github.com/docker/docker/vendor/pkg
-v .pkgcache/goroot_linux_amd64_netgo_cache:/usr/local/go/pkg/linux_amd64_netgo

TODO: add more goroot_GOOS_GOARCH_caches
- How to verify it
Without cache (about 3m15s on GCE n1-standard-1)
$ go get github.com/AkihiroSuda/ntimes
$ ntimes -n 10 make binary
real average: 3m15.749460489s, max: 3m20.81273226s, min: 3m8.789176086s, std dev: 3.43079474s
real 99 percentile: 3m20.81273226s, 95 percentile: 3m20.81273226s, 50 percentile: 3m15.209500849s
user average: 2.6168s, max: 2.72s, min: 2.468s, std dev: 100.643264ms
sys  average: 300.4ms, max: 344ms, min: 252ms, std dev: 33.009089ms
flaky: 0%

With cache (about 35s)
$ DOCKER_INCREMENTAL_BINARY=1 ntimes -n 10 make binary
real average: 34.394968178s, max: 36.553063254s, min: 31.726990108s, std dev: 1.332561861s
real 99 percentile: 36.553063254s, 95 percentile: 36.553063254s, 50 percentile: 33.787053494s
user average: 2.766s, max: 3.688s, min: 2.488s, std dev: 390.574505ms
sys  average: 268ms, max: 372ms, min: 216ms, std dev: 45.057987ms
flaky: 0%

ping @tianon @icecrime

ping @tianon PTAL :heart:

I'm +1!
I have a few superficial naming comments:

I think naming the top-level directory something like .go-pkg-cache would more clearly denote its purpose at a glance
since the subdirectories of that directory aren't related directly to the names of the directories they're mounted to, I think we should follow our normal repo convention of using hyphens instead of underscores (but also, "cache" is implied by the parent directory's name):

.go-pkg-cache/gopath:/go/pkg
.go-pkg-cache/vendor:/go/.../vendor/pkg
.go-pkg-cache/goroot-linux_amd64_netgo:/usr/local/go/pkg/linux_amd64_netgo

Regarding the technical details, do you think it'd be possible to put the actual directory mappings in a Make variable somehow so that the bind-mounts and the init-pkgcache line can be generated dynamically from the same data? (I'm happy to help brainstorm ways to accomplish this if you'd like, but I don't want to steal your thunder :smile:)

@tianon done :smile:

Aha, win! :heart_eyes:
LGTM

LGTM


Hotfix2.

This is actually deployed.

Merging this as it's already live to prevent further confusion.


feat(LightTelemetry): adds TrackException to interface

ILightTelemetry lacked the TrackException method. This was done by design - to avoid consumer code to call TrackException, it seems, because exception handling was supposed to be done at framework level.
Our take is that this creates more problems than solves. Consumers will still be able to directly use LightTelemetry if they desire, or handle the exception and NOT call TrackException when they should.
Also, that meant a lot of violations of LSP in the framework code, and led to numerous issues during testing since it was impossible to mockout the LightTelemetry.TrackEvent dependency.
This commit adds the method and removes all LSP violations that I could find.
Closes #159.

I had to advance this in order to improve testing on #197. It's a simple improvement, so I think we can approve it now.


Networking setup for easy SSH into Jetson

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.
We need the ability to access the jetson remotely through our laptops. It is a pain to have to go to the clubs room and plug in a keyboard, mouse, and monitor into the jetson to do development on it, not to mention we are limited by the number of USB ports available. We have to be able to ssh into the vehicle for doing any testing while driving it anyways.
There is also a slight issue with the ethernet adapter on the jetson. The operating system doesn't recognize eth0, so we have to use a usb-to-ethernet dongle in order for ethernet to work. This is a major inconvenience cause it takes away one of the available usb ports.
Describe the solution you'd like
A clear and concise description of what you want to happen.
We need a few things:

ethernet working on jetson without having to use usb-ethernet dongle
ability to connect to the car via ssh from anywhere, even off campus
ability to create a local area network using ethernet alone so we can have a backup for sshing into the jetson from within the clubs room (I don't want to have to attach the keyboard and whatnot every time)
ability to create a wireless local area network where we can ssh into the car without needing to be wired to it. We don't necessarily need to download anything from the internet so we can have this without an internet connection I think

Being able to connect to the jetson when it is in different places would be nice as well. I'd like to be able to connect to it remotely whether it is in the clubs room or in the breezeway (although the dense concrete might render that impossible). I would really like to be able to drive the rc car remotely in the etlc parking garage, as outside testing might be tough in the winter. This means the wireless access point must work down there.
I would like to not rely on any other clubs to have this happen, so we need to get this all set up ourselves.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Right now we are mooching off of ARVP like crazy, using their ethernet switch, their in-person and remote servers, and their wireless access point to have remote access to our jetson. This requires us to have SSH keys set up on their server and to do a bunch of weird stuff with it. The process is convoluted to say the least, and not scalable or sustainable for new members to use. Only I have access to remotely access the jetson right now.
Additional context
Add any other context or screenshots about the feature request here.

Just a quick update:

can now remotely ssh into the jetson from anywhere by going through a digital ocean cloud droplet as a reverse proxy. The jetson just needs to have an internet connection for this to work.

new members will need to generate ssh keys and I will need to put them on the digital ocean account and the jetson

ethernet switch is (hopefully) all good to go now, so if members want fast ssh into the jetson they can plug an ethernet cable into their laptop and connect it to the switch. They just need to statically set the IP details for the ethernet interface

all that is left is getting a wireless access point (either test first with ARVP's or just buy one) set up in the clubs room so we can locally ssh into the car without internet and without ethernet cables.


Initial support for MaxScale

Initial support for MaxScale.

Does this still encapsulate discussion with a maxscale failover cluster using VIP previously discussed here?

Hey there @advra ! This PR provides an initial support for provisioning MaxScale instances. In order to address it, a Kubernetes Service is provisioned and you can provide extra annotations to it to integrate with third parties like Kube-vip:

https://kube-vip.io/docs/usage/kubernetes-services/

Thanks for the clarification. I will be sure to open an issue should I have questions about the service annotations.

@advra MaxScale support is out. Please take a look at the docs:

https://github.com/mariadb-operator/mariadb-operator/blob/main/docs/MAXSCALE.md


custom font not applied to newly-opened scripts

#1496 is somewhat related.
Opening a script for editing ignores the custom font. I have to close out to the project manager, and load the project again and then the opened scripts will have the custom font.

Confirmed in the current master branch.

Interestingly, after opening a new script to which the custom font is not applied, if you go in the editor settings and clear the "custom font" field, the custom font will be applied to the newly opened script...

does this still happen? looks like it might have been fixed

I tested it last night and when I open a script it still uses the small
font. When I close the project and reopen it and the script is already
open, it uses the custom font. So it's still buggy.
On Sat, Jan 2, 2016 at 1:46 PM, Juan Linietsky<EMAIL_ADDRESS>wrote:

does this still happen? looks like it might have been fixed
—
Reply to this email directly or view it on GitHub
https://github.com/godotengine/godot/issues/2159#issuecomment-168415808.

Is this still valid with the new editor fonts system in 2.1?

I can't reproduce, will assume it's fixed. If the bug still happens, someone can comment here or open a new issue.


1.19.4 branch

Hello, could you open a 1.19.4 branch from 1.19.3? I will PR an update

Just created the branch, thank you!


Customer Doesn't Want to Whitelist "*.botframework.com"

Our customer's security team won't let them whitelist a URL with an asterisk; only concrete URLs or a concrete range of IPs.
Can one of those be provided for "botframework.com"?
Thanks, Gary

Hi @gamullen Thanks for reporting. I was wondering if there is a document you or your customer's security team is referring to?

Sorry, not sure how that comment didn't get associated with the page. This: https://docs.microsoft.com/en-us/azure/bot-service/bot-service-resources-bot-framework-faq?view=azure-bot-service-4.0

Hi! Thanks for your reply. We are coordinating with our engineering team for this issue. Will let you know shortly.

@gamullen *.botframework.com is preferred and certainly more future-proof (in case we change the names or something), but you should be able to get away with using token.botframework.com and <channel>.botframework.com, where <channel> is equal to every channel that your bot uses, for example:

directline.botframework.com
slack.botframework.com
etc

That should cover your needs, but it might be worthwhile to watch traffic over your firewall while testing the bot to make sure something else isn't getting blocked.

Great, thanks! Will that be making its way into the documentation?

I can add the content into the documentation. @gamullen @mdrichardson

@zxyanliu , is there an eta on the document update so we can close this issue?

Hi @CoHealer
Yes, it is fixed in PR 1927. @mdrichardson helped a lot and reviewed the PR. I will close this issue when 1927 get merged.

Great, thanks

Closing the issue since the PR is merged and content will go live soon. @gamullen Thanks again!


Added Mozilla Protocol

Added Mozilla Protocol (via Design Systems Weekly): https://protocol.mozilla.org/
(Probably butchered the JSON in the process though) 😬

Thank you! 🙌 Actually the JSON looks all good! I'll deploy changes later on today! :)


Fix deb artifact path causing docker build to become flaky

What does this PR do?
Changes the DESTINATION_DEB* variable of the agent_deb-x64-a7-auto gitlab job to something unique to this job
Motivation
In a previous PR, a new job was introduced which uploaded an artifact named datadog-agent_7_amd64.deb. However, this name is already being used by the agent_deb-x64-a7 job. This is resulting in a race condition when the docker_build_agent7 job kicks off, if the agent_deb-x64-a7-auto finished after the agent_deb-x64-a7 job
This is causing the docker_build_agent7 job to become flaky, failing periodically on this line because it cannot find the opt/datadog-agent/ folder, which looks like it is because the new job is setting the INSTALL_DIR to a different directory by default
Additional Notes
Follow-up to this PR
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge


trace.

Hello! Thank you for your efforts. I would like to inquire, when using Janus-SWI, how can I prompt it to print out the Prolog inference process (similar to 'trace.')?

Please use our Discourse forum for questions.    In  general you should be able simply call
  janus.query_once("trace, whatever", ...)


New circuit for align/pdk/finfet

This PR adds a new, hierarchical circuit example with place on grid constraints. The test is intentionally disabled and will be enabled in a future PR for triage and debug.

@srini229 , this PR contains a new circuit to reproduce the placement problem. As soon as the test pass, I will merge this PR to master. Then, please feel free to bring this to your PR and enable the test.


Feature/colab

adding colab link in readme

Codecov Report

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

@@           Coverage Diff           @@
##           master       #5   +/-   ##
=======================================
  Coverage   80.45%   80.45%
=======================================
  Files          10       10
  Lines         307      307
=======================================
  Hits          247      247
  Misses         60       60

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 e5909e4...bc5788f. Read the comment docs.


Incomplete Composer Package Update (1.1.11)

Your Fix for 'Deprecated Twig getExtension argument' is missing in latest (1.1.11) composer package of Timber. Maybe some other stuff too... Not cool!
Please fix this asap!

Hey @developer-lindner — that PR came in after 1.1.11 had been released to WP.org. It will be a part of the next release for sure. Is there a particular urgency around that fix? As I understand, that will come into play with Twig 2.0 which is not yet released

Hey @jarednova unfortunately your're wrong here. The fatal error already happens with Timber 1.1.11 or better say with Twig 1.26 which comes with the composer install of Timber 1.1.11. That's why i had to pull the fix out of the github repo. You should release it soon ;)


rotation guizmo sometimes not detecting mouse correctly

I find sometimes the rotation guizmo does not detect my mouse. It works very reliably for translation but only sometimes for rotation. Any tips on what I should try to get the rotation to highligh reliably?
https://github.com/user-attachments/assets/a990046c-5da9-43fd-bde2-6369cddabd11

The problem seems to happen more often when looking along the orthogonal x,y,z axis and less often when looking from non-orthogonal views

an intersection ray/plane is computed for each axis.
Then, intersection is filtered. I guess it's that filtering process that can be improved
https://github.com/CedricGuillemet/ImGuizmo/blob/6d588209f99b1324a608783d1f52faa518886c29/ImGuizmo.cpp#L2044


[Bug]: bin/build script specifies unknown target stage

What happened?
Attempting to run the docker build returns an error where the specified target stage is not defined:
❯ ./bin/build
[+] Building 0.0s (2/2) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 723B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 161B                                                                                0.0s
ERROR: failed to solve: target stage chroma_server could not be found

Looking at the Dockerfile, I'm not seeing a chroma_server target anywhere
Versions
❯ docker --version
Docker version 24.0.2, build cb74dfc

Relevant log output
N/a

I think this build script is unused and a bit old - what are you trying to accomplish?
We can remove the script - let me confirm its unused

what are you trying to accomplish?

I was looking for the canonical way to build the docker image from source 😄

The Dockerfile in the root of the repo would be that!

I've confirmed the script is unused and can be removed.


chore(requirements): update jsonfield to 2.0.0

See https://github.com/bradjasper/django-jsonfield/compare/1.0.3...2.0.0

Codecov Report

Merging #1252 into master will decrease coverage by -0.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1252      +/-   ##
==========================================
- Coverage   87.29%   87.24%   -0.06%
==========================================
  Files          44       44
  Lines        3873     3873
  Branches      673      673
==========================================
- Hits         3381     3379       -2
- Misses        324      325       +1
- Partials      168      169       +1

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 934d68d...cfcaea7. Read the comment docs.