RC Spot-Check Test: Magnets and Electromagnets 1.0.0-rc.2

RC Spot-Check Test
Mentions: @arouinfar @ariel-phet @kathy-phet @KatieWoe @Nancy-Salpepi
Simulation links

github repository for issues - Please create issues in faradays-electromagnetic-lab.
phet top-level directory
sim: all_phet.html
phet-io wrapper index
link to phet-io zip file

Test Matrices
General Test:

[x] Tester = NS, Platform = mac + safari , Time =
[x] Tester =JD , Platform = Chrome, win 11 , Time = .25

PhET-iO Test:

[x] Tester = NS, Platform = mac + safari, Time = .25
[x] Tester = JD  , Platform = chrome win 11 , Time = .25

Additional Features Test:

[ ] Tester = , Platform = , Time =
[ ] Tester = , Platform = , Time =

Features included

PhET-iO
Dynamic Locale
Alternative Input
UI Sound
Sonification
Description
Voicing

Focus and Special Instructions
This sim is part of a suite of 4 sims, all being released and tested at the same time. These QA issues should therefore be done together:

https://github.com/phetsims/qa/issues/1128
https://github.com/phetsims/qa/issues/1129
https://github.com/phetsims/qa/issues/1130
https://github.com/phetsims/qa/issues/1131

Issues to Verify
These issues have the "status:ready-for-review" label. Unless an issue says to close after verifying, assign the
issue back to the developer.
See the last comment in each issue for instruction describing how to verify.

[x] https://github.com/phetsims/faradays-electromagnetic-lab/issues/202
[x] https://github.com/phetsims/faradays-electromagnetic-lab/issues/201
[x] https://github.com/phetsims/faradays-electromagnetic-lab/issues/194
[x] https://github.com/phetsims/faradays-electromagnetic-lab/issues/2

For QA...

General features

What to Test

Click every single button.
Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.

If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Test some query parameters. (See QA Book for a
list of query parameters.)
When making an issue, check to see if it was in a previously published version.
Try to include version numbers for browsers.
If there is a console available, check for errors and include them in the Problem Description.
As an RC begins and ends, check the sim repo. If there is a maintenance issue, check it and notify developers if there
is a problem.
As the RC ends, notify the developer of any new QA credits that need to be added.

PhET-iO features

What to Test

Make sure that public files do not have password protection. Use a private browser for this.
Make sure that private files do have password protection. Use a private browser for this.
Make sure standalone sim is working properly.
Make sure the wrapper index is working properly.
Make sure each wrapper is working properly.
Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make
sure the simulation loads without crashing or throwing errors.
Load the login wrapper just to make sure it works. Do so by adding this link from the sim deployed root:/wrappers/login/?wrapper=record&validationRule=validateDigits&&numberOfDigits=5&promptText=ENTER_A_5_DIGIT_NUMBER

Further instructions in QA Book
Conduct a recording test to Metacog, further instructions in the QA Book. Do this for iPadOS + Safari and one other
random platform.
Conduct a memory test on the stand alone sim wrapper (rc.1).
Test one platform combination with ?phetioDebug=true on the Studio and State wrapper.
If Pan/Zoom is supported, make sure that it works when set with PhET-iO State.
Test that the sim works offline:

Click the link to the phet-io zip file (at top of issue) to download the zip file.
Unzip it to a spot locally.
Open index.html by double clicking it on your desktop or in a Finder-view.
It should look like the standalone version of the sim in PhET-iO brand.

Accessibility features

What to Test

Specific instructions can be found above.

Make sure the accessibility (a11y) feature that is being tested doesn't negatively affect the sim in any way. Here is
a list of features that may be supported in this test:

Alternative Input
Interactive Description
Sound and Sonification
Pan and Zoom
Mobile Description
Voicing

Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.
Test all keyboard navigation inputs (if applicable).
Test all forms of input with a screen reader (if applicable).

If this sim is not in this list or up to date there, make an
issue in website to ask if PhET research page links need updating. Please
assign to @terracoda and @emily-phet.

Screen Readers
This sim may support screen readers. If you are unfamiliar with screen readers, please ask Katie to introduce you to
screen readers. If you simply need a refresher on screen readers, please consult the
QA Book, which should have all of the information
you need as well as a link to a screen reader tutorial made by Jesse. Otherwise, look over the a11y view before opening
the simulation. Once you've done that, open the simulation and make sure alerts and descriptions work as intended.

Platforms and Screen Readers to Be Tested

Windows 10 + Latest Chrome + Latest JAWS
Windows 10 + Latest Firefox + Latest NVDA
macOS + Safari + VoiceOver
iOS + Safari + VoiceOver (only if specified in testing issue)

Critical Screen Reader Information
We are tracking known screen reader bugs in
here. If you find a screen reader bug,
please check it against this list.

Keyboard Navigation
This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a
screen reader.
Magnification
This sim supports magnification with pinch and drag gestures on touch screens, keyboard shortcuts, and mouse/wheel
controls. Please test magnfication and make sure it is working as intended and well with the use cases of the
simulation. Due to the way screen readers handle user input, magnification is NOT expected to work while using a screen
reader so there is no need to test this case.

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

QA is done

Thanks QA!  All issues have been verified, and I'll proceed with 1.0 production deploy.


Add CI

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@bb3962f). Click here to learn what that means.
The diff coverage is 16.66%.

@@            Coverage Diff            @@
##             master      #11   +/-   ##
=========================================
  Coverage          ?   96.35%
=========================================
  Files             ?        8
  Lines             ?      329
  Branches          ?        0
=========================================
  Hits              ?      317
  Misses            ?       12
  Partials          ?        0

Impacted Files
Coverage Δ

src/czml3/properties.py
100% <ø> (ø)

src/czml3/core.py
100% <ø> (ø)

src/czml3/enums.py
75% <16.66%> (ø)

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 bb3962f...d33ec76. Read the comment docs.


New update is not working

Issue Type: Bug
Hover/Bring the cursor to the text(instead of erasing it and typing it again)(new update) in .css file is not working
VS Code version: Code 1.51.0 (fcac248b077b55bae4ba5bab613fd6e9156c2f0c, 2020-11-05T18:18:23.642Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-2400S CPU @ 2.50GHz (4 x 2494)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: unavailable_offopengl: enabled_onprotected_video_decode: unavailable_offrasterization: unavailable_offskia_renderer: disabled_off_okvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.83GB (3.52GB free)

Process Argv
--crash-reporter-id a07bb4c3-1052-4dc1-aa04-793782e9dca3

Screen Reader
no

VM
0%

Extensions (13)

Extension
Author (truncated)
Version

stories
ben
2.20.0

bracket-pair-colorizer
Coe
1.0.61

vscode-eslint
dba
2.1.13

prettier-vscode
esb
5.7.1

auto-rename-tag
for
0.1.5

beautify
Hoo
1.5.0

google-search
kam
0.0.1

vscode-docker
ms-
1.7.0

python
ms-
2020.10.332292344

vsliveshare
ms-
1.0.3121

debugger-for-chrome
msj
4.12.11

LiveServer
rit
5.6.1

vscode-todo-highlight
way
1.0.4

Can you provide more detailed steps with screenshots or a screen-cast?

Here is the recording
I read that I can change the properties if I just hover my mouse or cursor. But I had to erase and again type.

Another Recording on the same issue

I think you misunderstood the feature. This is about when code completion is open (Ctrl +Space) you can move the cursor to the left and will see additional proposals.


react ts app yarn test:unit fails with SyntaxError: Cannot use import statement outside a module

Thank you for your work on this package and apologies in advance if this issue is the result of user error.
I see the following error in the example react-app-ts and also when incorporating vite-jest into my own react app.
/code/vite-jest/examples/react-app-ts/node_modules/vite-jest/bin/vite-jest.js:3
import fs from 'fs'
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at Module._compile (internal/modules/cjs/loader.js:895:18)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
    at Module.load (internal/modules/cjs/loader.js:815:32)
    at Function.Module._load (internal/modules/cjs/loader.js:727:14)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1047:10)
    at internal/main/run_main_module.js:17:11

I think this is a Yarn 2 specific problem, and to be more specific this is because Yarn 2 cannot currently run ES Modules.
See https://github.com/yarnpkg/berry/issues/638
When I try to run the example with pnpm it works, but not using yarn

@mijamo The error in my screenshot was with npm v7.19.0. I have not tried pnpm, although I did observe the same issue with Yarn 2 as you indicated as well.


Inserting into table with clustering based on a object's property fails in 4.2.x

CrateDB version: 4.2.1
Environment description:

Docker: version 19.03.8
Problem can be reproduced without docker:

Haven't checked that but I find it very likely

Problem description:
Consider a simple table that uses clustering based on an object's property such as
CREATE TABLE objects (complex object(strict) AS (id INT, name TEXT)) CLUSTERED BY (complex['id']) into 4 shards;

When trying to insert a simple row like:
INSERT INTO objects VALUES ({id=4, name='George'});

We run into this error:
SQLActionException[SQLParseException: Clustered by value is required but is missing from the insert statement]
Which seems to be incorrect as the id was given.
The same query works with version 4.1.8
If we leave out the clustering in 4.2.1, it also works.
CREATE TABLE objects_unclustered (complex object(strict) as (id int, name text));
INSERT INTO objects_unclustered VALUES ({id=4, name='George'});

Thank you for the report. We've a fix pending (https://github.com/crate/crate/pull/10273) which will be released with 4.2.2


Fixing a spell typo

Fixing a small spell typo that was reported through feedback hub

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

@tiburd Please merge this PR. Thanks


Windows WebView2 ScriptDialogOpening CoreWebView2ScriptDialogOpeningEventArgsIt not useful

Describe the bug
But with CoreWebView2ScriptDialogOpeningEventArgs, you cannot tell it that it has not been intercepted and to finally launch the original, okay, this is not a bug, it is a feature proposal.
What is a bug, though, is that CoreWebView2ScriptDialogOpeningEventArgs has an Accept but no cancel. Therefore, in the case of a Confirm,
if (e.Kind == CoreWebView2ScriptDialogKind.Confirm) {
	if (Confirm(e.Message)) {
		e.Accept();
	}
}

There is no way for the confirm to return FALSE. Because if you not fire Accept, return of confirm( on javascript will be null.
This does not give me the tools to substitute the original behavior of Confirm since it can result in true or false.
Yes, I could do a workaround and intercept the result by JavaScript and if it is === null, transform it to false. But that is not a solution. CoreWebView2ScriptDialogOpeningEventArgs should allow me to substitute the original behavior of the events.
Also, as I said before, I do not understand why it does not have a return property that allows me to launch the default event despite having intercepted it.
Steps to reproduce the bug
Create a WebView2
Intercept ScriptDialogOpening
Try to return false on the javascript confirm call.
Expected behavior
Confirm dialog, by default, can be true or false.
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.2.5: 1.2.230313.1
Windows version
Windows Insider Build (xxxxx), Windows 11 (22H2): Build 22621, Windows 11 (21H2): Build 22000, Windows 10 (21H2): Build 19044, Windows 10 (21H1): Build 19043, Windows 10 (20H2): Build 19042, Windows 10 (1809): Build 17763
Additional context
No response

Thanks @champnic. Closing this bug to avoid duplication.


when kubeadm upgrade to v1.10.1 ,it will be fatal

export OS_IMAGE=centos7

[all:vars]

# Kubernetes
#kube_version=v1.9.3
kube_version=v1.10.1
token=b0f7b8.8d1767876297d85c

TASK [kubernetes/master : Init Kubernetes cluster] *******************************************

fatal
fatal: [<IP_ADDRESS>]: FAILED! => {"changed": true, "cmd": "kubeadm init --service-cidr <IP_ADDRESS>/12 --kubernetes-version v1.10.1 --pod-network-cidr <IP_ADDRESS>/16 --token b0f7b8.8d1767876297d85c  ", "delta": "0:02:10.301000", "end": "2018-04-21 17:10:02.936757", "msg": "non-zero return code", "rc": 1, "start": "2018-04-21 17:07:52.635757", "stderr": "\t[WARNING FileExisting-crictl]: crictl not found in system path\nSuggestion: go get github.com/kubernetes-incubator/cri-tools/cmd/crictl\ncouldn't initialize a Kubernetes cluster", "stderr_lines": ["\t[WARNING FileExisting-crictl]: crictl not found in system path", "Suggestion: go get github.com/kubernetes-incubator/cri-tools/cmd/crictl", "couldn't initialize a ........1.10.1", "\t\t- k8s.gcr.io/etcd-amd64:3.1.12 (only if no external etcd endpoints are configured)", "", "If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:", "\t- 'systemctl status kubelet'", "\t- 'journalctl -xeu kubelet'"]}
to retry, use: --limit @/vagrant/site.retry
PLAY RECAP ****************************************************************************************************************************************************************************
<IP_ADDRESS>               : ok=11   changed=2    unreachable=0    failed=1
journalctl -xeu kubelet'

output
Apr 21 17:24:50 master1 kubelet[27523]: W0421 17:24:50.988435   27523 hostport_manager.go:68] The binary conntrack is not installed, this can cause failures in network connection clea
Apr 21 17:24:50 master1 kubelet[27523]: W0421 17:24:50.988492   27523 cni.go:171] Unable to update cni config: No networks found in /etc/cni/net.d
Apr 21 17:24:50 master1 kubelet[27523]: I0421 17:24:50.988537   27523 docker_service.go:244] Docker cri networking managed by cni
Apr 21 17:24:51 master1 kubelet[27523]: I0421 17:24:51.005521   27523 docker_service.go:249] Docker Info: &{ID:NC7E:CYY4:TOY6:QJPM:CP6S:KQT7:GKCY:NF63:MOT6:B2IW:5HQY:FHVS Containers:0
Apr 21 17:24:51 master1 kubelet[27523]: F0421 17:24:51.005645   27523 server.go:233] failed to run Kubelet: failed to create kubelet: misconfiguration: kubelet cgroup driver: "systemd
Apr 21 17:24:51 master1 systemd[1]: kubelet.service: main process exited, code=exited, status=255/n/a
Apr 21 17:24:51 master1 systemd[1]: Unit kubelet.service entered failed state.
Apr 21 17:24:51 master1 systemd[1]: kubelet.service failed.
lines 1219-1270/1270 (END)

Honestly, the only work-around is to do a reset and then re-deploy! Closing this as this is a non-issue


PyLepton Not working on raspberry pi

I have downloaded and installed the pylepton from github and wired it up to my raspberry pi, but when the pylepton capture code is run, it runs indefinitely without outputting the image, and when I force it to quit it says it was at a time.sleep() command. Any ideas?

Start with the easy stuff?

double check the wiring to the Lepton is on the right pins
double check the lepton lens is firmly seated into the lepton board

On Fri, Mar 1, 2019 at 4:29 PM Vikram Bhat<EMAIL_ADDRESS>wrote:

I have downloaded and installed the pylepton from github and wired it up
to my raspberry pi, but when the pylepton capture code is run, it runs
indefinitely without outputting the image, and when I force it to quit it
says it was at a time.sleep() command. Any ideas?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/groupgets/pylepton/issues/29, or mute the thread
https://github.com/notifications/unsubscribe-auth/AGmeVedpqKpeYIRUpY8VT0c5x6G8rmi1ks5vSZvOgaJpZM4bZ2J3
.

I have checked the wiring, with the clk in both ce1 and ce0, but to no avail. The lepton works on an old repo called lepton module master, which was on the pi before I started working on this project, but I can't get it to work in python.

CE0 and CE1 most definitely should not be wired to the SPI-CLK pin.

I am using this codebase successfully (on master) with RPi2 & 3 with both a Lepton 2.5 and 3.5 with no problems. Every time I have an issue it is usually associated with wiring, incorrect configuration, or a broken sensor.

I got it to run, but now when I display the image that it saved it shows a black/grey screen even when I put my hand or something hot in front of the camera

This sounds like an implementation issue and not the library itself. Without seeing your capture code I am unable to help you troubleshoot this.

I am using the stock pylepton_capture code from this library, I will update this thread after I troubleshoot more tomorrow

Are you still having issues with the pylepton_capture software? Also have you tried switching the selected CE port in the code? Also make sure you have a pull-down/pull-up resistor on the CE line. You can set this on the Raspberry pi itself -> https://issuu.com/themagpi/docs/the_magpi_issue_2_final
See pages 10-14
Also does your original code that works use the same libraries to communicate with the Lepton?

I have not tried this pull-down/up resistor that you are talking about. I will try to switch the CE port in the code, for now I have switched to the purethermal mini over usb because that seems to be working. I believe the original code doesn't use python, but the leptonModule library on the flir website.

You're aware that the lepton raw output is in greyscale? You have to apply
a colorscale to the image if you want it to look like a commercial Flir
device. If I remember correctly, pylepton_capture doesn't apply any color
to the output all by itself.
That said, if it's working, you should see edges and shapes where the
thermal value is different.
On Mon, Mar 4, 2019 at 4:01 PM Vikram Bhat<EMAIL_ADDRESS>wrote:

I have not tried this pull-down/up resistor that you are talking about. I
will try to switch the CE port in the code, for now I have switched to the
purethermal mini over usb because that seems to be working. I believe the
original code doesn't use python, but the leptonModule library on the flir
website.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/groupgets/pylepton/issues/29#issuecomment-469420146,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGmeVTMqMHkfB0Ufe1DgrFDUU1jadwN3ks5vTYm3gaJpZM4bZ2J3
.

Yup, I do know its greyscale, but I get no discernable picture when I use the capture code, just a flat grey screen with a white line at the bottom, even when I or something hot is in the frame.

A typical scene will have a very low dynamic range in 14 bits of data, and that needs to be contrast extended if you want to see something. If you have a line at the bottom of the screen that's outside the range of your signal, it's going to cause problems with that contrast extension.

As @kekiefer said, make sure to use a hot object in front of the camera. You can also use OpenCV to recolor the image and normalize it as well. Check some of my code here for examples -> https://github.com/sentient-controls/plantspy/blob/master/plantspy.py#L105

I'm trying to use python3 with pylepton. When I run my script. it said No module named 'Lepton'. I need to use python3 for my project. Does anyone know how to solve this issue.
Thanks


tracebacks sometimes show in failing tests

I open this issue to trace the fix for the problem, first mentioned in https://github.com/TobikoData/sqlmesh/issues/3353#issuecomment-2466291702. Ping @georgesittas .
sqlmesh --version
0.131.0

As a repeat of the results in #3352, here is an example with no traceback:
sqlmesh test
...F......
======================================================================
FAIL: test_arrays_bug (/project-dir/tests/test_arrays_bug.yaml)
----------------------------------------------------------------------
AssertionError: Data mismatch (exp: expected, act: actual)

  aggregated_duplicates
                    exp     act
0                (c, b)  (b, c)

----------------------------------------------------------------------
Ran 10 tests in 0.159s

FAILED (failures=1)

but for this one (with my initially wrong test), there is a traceback:
sqlmesh test
........F..
======================================================================
FAIL: reproduce_bug (/project-dir/sqlmesh-20-duplicate-arbitrage/tests/test_recursive_cte_bug.yaml) (cte='"id_contact_a_with_aggregated_id_contact_bs"')
----------------------------------------------------------------------
Traceback (most recent call last):
  File "project-dir/sqlmesh/core/test/definition.py", line 550, in test_ctes
    self.assert_equal(expected, actual, sort=sort, partial=partial)
  File "project-dir/sqlmesh/core/test/definition.py", line 273, in assert_equal
    raise e
  File "project-dir/sqlmesh/core/test/definition.py", line 247, in assert_equal
    pd.testing.assert_frame_equal(
  File "project-dir/.venv/lib/python3.12/site-packages/pandas/_testing/asserters.py", line 1218, in assert_frame_equal
    raise_assert_detail(
  File "project-dir/.venv/lib/python3.12/site-packages/pandas/_testing/asserters.py", line 614, in raise_assert_detail
    raise AssertionError(msg)
AssertionError: Data mismatch (rows are different)

Unexpected rows:

  id_contact_a aggregated_id_contact_bs
0            b             (c, d, e, f)
1            c                   (d, f)

----------------------------------------------------------------------
Ran 11 tests in 0.176s

FAILED (failures=1)

I fixed this in the other PR I merged, it should work in main.


clarify organizational account type requirements

'User' and 'Viewer' type accounts are not permitted to create hosted feature services.  They can upload a .zip file, but no additional options appear.
Because of this we should definitely mention the explicit requirements in our own doc.

Whoa, didn't realize how long this one had been sitting around...

i addressed @nixta's entirely valid feedback and squashed.

Oh yucky. What editor are you using that adds whitespace at the ends of lines, @jgravois?
Makes it really hard to see what's actually changed 😫 I know that I can go to the URL and add ?w=1 to hide the whitespace differences but it'll still show up as diffs by default in the history. Any chance you could undo those and squish again?

my changes aren't adding whitespace, they're removing what was introduced by whatever text editor @alaframboise used in 87bf12728e0d2b1bed35125ab24c3ad17fcaad38.
tbh i can't see myself putting more work into this PR at this point :bowtie:.

Fair enough. My bad. I should have looked more closely at the changes. The diff between your prev commit and this threw me, but the additional change however it happened is +ve, I suppose. I'll go through and remove other trailing spaces for consistency if need be.

The diff between your prev commit and this threw me.

understandable.  it was cause i pulled from master.

Wait. I'm really confused. a) I don't see whitespace added in that commit you mention and b) why is it so different to what you submitted originally?
I'm also now struggling to merge with changes I've made in a restructuring branch even though none of the changes conflict with the terms change you made. But as far as I can tell, none of them conflict with any changes (whitespace or otherwise), so git is really killing me on this one now.

a) its not highlighted, but it must be at the trailing end of al's line.
b) i'm really not sure.  maybe i submitted this PR from a stale branch and didn't get it in sync until i incorporated your feedback the other day?  i don't see how though, and i can't trace the history because i blew it away ¯_(ツ)_/¯
nixta: js4-update-and-develop-restructure

This branch is 17 commits ahead, 2 commits behind Esri:gh-pages

i'm happy to help you tomorrow.  you need to either pull or fetch/rebase the two commits introduced by this PR (my own and your merge commit) into your own branch. afterward we'll be able to pull your own work in cleanly.
i'm pretty sure the fact that you tweaked line 68 and i added a new line 69 is what git is considering a conflict.  because of this, you need to compare all discrepancies between your own README.md and the remote README.md and choose to keep everything from your branch and incorporate my own one liner.  no wonder you were being so fussy about that whitespace!

Cool. Thanks. I did try merging the gh-pages into my branch but during the merge the repo got into a state I wasn't entirely confident of so it'll be good to have your adult supervision tomorrow :) I think I'm one git command and a sane review away from it being good.


register view updates to "No such target" and code view with "Empty Response"

I am running Voltron on Kali 32-bit () via terminator with 3 panes.
In the bottom pane I start gdb on a sample program (gdb ./test)
In the top right pane I set voltron view to register ("voltron view register")
In the top left pane I set voltron view to disasm ("voltron view disasm")
in bottom pane I set a breakpoint on main and run ("b main then run")
The panes update as desired.
As I step through the code I find often both the disasm and the regs view will 'dropout'
[regs:general] will display "No such target"
[code] will display "Empty response"
Is this expected? Perhaps its because the code / registers are inaccessible at that point in time?

That is not expected. If you could enable debug logging per the wiki and send me the logs I'll have a look.

Ok attached are my log files. I can reproduce the problems with a simple 'standard' hello world program compiled with gcc. Usually you will see the correct result (e.g. disassembly listing is disasm view) flash up before being replaced by the error message.
logs.zip

OK, can you do this for me:

Kill all your views and GDB

Start GDB with the test inferior included with Voltron:
$ cc -o tests/inferior tests/inferior.c
$ gdb tests/inferior

Start a Python process in another terminal and paste in the following:
import voltron
c = voltron.core.Client()
while True:
    print(c.perform_request('state', block=True))

In the debugger:
(gdb) b main
(gdb) run
(gdb) stepi
(gdb) stepi
(gdb) stepi

Step maybe 10 or so times and paste the output from the Python session here? I'll have to grab a Kali image to try to reproduce it locally, but something seems to be going wrong with the client<->server comms. From your debug logs the server is responding correctly but the client is getting None back for some responses.

Ok I did that although I had to make sure I run to main before starting the python script otherwise python script dies with 'Connection refused'.
Once I 'run' in gdb... then start python script I get the following output...
root@Kali:~# python vtest.py
{"status": "error", "data": {"message": "The request timed out", "code": 4100}, "type": "response"}
{"status": "success", "data": {"state": "stopped"}, "type": "response"}
{"status": "success", "data": {"state": "stopped"}, "type": "response"}
{"status": "success", "data": {"state": "stopped"}, "type": "response"}
{"status": "success", "data": {"state": "stopped"}, "type": "response"}
{"status": "success", "data": {"state": "stopped"}, "type": "response"}
{"status": "success", "data": {"state": "stopped"}, "type": "response"}
{"status": "success", "data": {"state": "stopped"}, "type": "response"}
{"status": "success", "data": {"state": "stopped"}, "type": "response"}
{"status": "success", "data": {"state": "stopped"}, "type": "response"}
{"status": "success", "data": {"state": "stopped"}, "type": "response"}
{"status": "success", "data": {"state": "stopped"}, "type": "response"}
{"status": "success", "data": {"state": "stopped"}, "type": "response"}
{"status": "success", "data": {"state": "stopped"}, "type": "response"}
{"status": "success", "data": {"state": "stopped"}, "type": "response"}
{"status": "success", "data": {"state": "stopped"}, "type": "response"}
{"status": "success", "data": {"state": "stopped"}, "type": "response"}
{"status": "error", "data": {"message": "The request timed out", "code": 4100}, "type": "response"}
{"status": "error", "data": {"message": "The request timed out", "code": 4100}, "type": "response"}
{"status": "error", "data": {"message": "The request timed out", "code": 4100}, "type": "response"}
The timeouts happen while idle (no keys hit) where as the success msgs come from the steps...

Here is another result from further stepping:
No handlers could be found for logger "core"
{"status": "error", "data": {"message": "Empty response", "code": 4104}, "type": "response"}
{"status": "error", "data": {"message": "The request timed out", "code": 4100}, "type": "response"}

OK, I'll have to try and reproduce it here.

Ok thanks. Let me know if you want me to help in any way. It seems like a great idea and I am hoping I can use it actively.

No problem. Just waiting on a Kali image to download on my slow internet.

Evidently I am bad at thread synchronisation. Should be fixed in 145fe94456f7e750f8ff5d66ad5ff7b35ab137aa.


Add .sln and update csproj files for packaging

This change adds a .sln file with links to each project. This will simplify the build process as dotnet cli commands can now be run from the project root, instead of in each project directory.
I've also updated the two projects that produce nuget packages (Honeycomb & Honeycomb.AspNetCore) to consolidate the .nuspec files into the csproj. Each .nuget package will also use the honeycomb.png image as the package image.
I also updated the Test and Sample projects to netcoreapp5.0 apps.

Testing is still currently a WIP in PR #22.

Testing is still currently a WIP in PR #22.

@MikeGoldsmith looks good, I can rebase & fix #22 once this is merged. Can you add some quick start commands (test and build perhaps) in README for the rest of us dotnet nooobs? 😄

@MikeGoldsmith looks good, I can rebase & fix #22 once this is merged. Can you add some quick start commands (test and build perhaps) in README for the rest of us dotnet nooobs? 😄

@vreynolds I've added build/test instructions and project requirements 👍

@vreynolds I've added build/test instructions and project requirements 👍


livesrever

Type: Feature Request
My liveserver won't open
VS Code version: Code 1.74.2 (e8a3071ea4344d9d48ef8a4df2c097372b0c5161, 2022-12-20T10:29:14.590Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


[v9] issue: images in Atomik theme don't seem to be contained within grid column

Images in Bootstrap columns are displayed full width instead of being contained within the grid column boundaries. The Elemental theme's content.less used to have this:
max-width: 100%;
height: auto;

which is a standard Bootstrap setting. Looks like that's gone now from the theme. Is that intentional?
This is how it is now:

This is how it should be:

Sorry, false alarm. Bootstrap 5 has a new class 'img-fluid' for images which fixes that issue.
Can't I delete posts on github?

Sorry, false alarm. Bootstrap 5 has a new class 'img-fluid' for images which fixes that issue.
Can't I delete posts on github?

I'd like to reopen this issue because I've added a Gallery block to a page in the Atomik theme and all thumbnails are all cramped into the column one on top of another instead of being distributed evenly one in each column. I expected the Gallery to be an image per column, not all images in one column.

I'm not sure I understand – I don't think there's a bug here with the theme per se, I think the gallery just isn't behaving in the way you'd expect. When I add images to the gallery I don't see them cramped in one column, I see them evenly distributed .

This is how they look:

You might try investigating why your images look different than the images in the Atomik sample content, which all come in in a grid. Maybe a particular thumbnail type doesn't exist or for some reason isn't being used?

I've just made a test page and added the block there. There is nothing else on the page.
I can see the view has $tag = (new Image($image['file']))->getTag(); but does that output a 'img-fluid'?

@aembler , I don't see any 'img-fluid' in the concrete/src/Html/Object/Picture.php


changed rabbitmq url to env variable

@longshuicy Every containers related to this PR have been made and tested in kube clusters.

@longshuicy maybe let's get this merged as well. If there is any more changes needed, let's create new PR


Code not making use of GPU

I am running train.py --model='Both' but the training time per step is 58 seconds, too slow.
On running nvidia-smi, it shows the GPU is not being utilized. Is there something I am missing?

I think that would work. But after installation and running train.py, the follow error occurs:
AttributeError: module 'tensorflow' has no attribute 'contrib'

I think the version of tensorflow needs to be 1.6 or higher.
I am using 1.7

Hi @hiroto911 Thanks for the answer.
I have reinstalled tensorflow with gpu support.
tensorflow-gpu         1.7.0     tensorflow-tensorboard 0.1.8
On running train.py again, the nvidia-smi command shows no usage of GPU.
Not sure why is that happening.

Got it thanks! :)

I am assuming this has been fixed. closing the issue. If there are any further question or if the issue persists feel free to reopen :)

Same problem here. GTX 1080, CUDA 9.0 and wavenet + wavenet-gpu installed. My CPU (R7 2700x) is being pegged 90% while my gpu sits idle. If I uninstall just wavenet then I get
AttributeError: module 'tensorflow' has no attribute 'contrib' error.
Snippet from output log:
No model to load at logs-Tacotron-2\taco_pretrained

Generated 64 train batches of size 8 in 1.379 sec

Generated 81 test batches of size 8 in 1.632 sec
Step       1 [59.480 sec/step, loss=11.39907, avg_loss=11.39907]
Saving Model Character Embeddings visualization..
Tacotron Character embeddings have been updated on tensorboard!
Step       2 [48.279 sec/step, loss=7.72918, avg_loss=9.56413]

I have the same issue as Ishansan38 had but, using tensorflow 1.7 is also giving the same error as
AttributeError: module 'tensorflow' has no attribute 'contrib'
PS. i have installed latest tensorflow gpu aswell

I faced the same issue as Ishansan38 after installing tensorflow gpu and tensorflow1.7 its still giving same error:
AttributeError: module 'tensorflow' has no attribute 'contrib'

Did anyone figure out what happened here? I'm on 1.13 and having similar issues.


Remove the contents: write permission from ockam-package.yml workflow

Remove the contents: write permission from the ockam-package workflow as we only write to packages in the build-and-publish-artifact job

We love helping new contributors! ❤
If you have questions or need help as you explore, please join us on Discord. If you're looking for other issues to contribute to, please checkout our good first issues.

Hey, I'd like to take this issue up!

Hello @tharun634 I have assigned you to https://github.com/build-trust/ockam/issues/6177, we can assign you to this issue when the former is done and closed

@tharun634 assigning this to you now. Thank you.


Fix getting workspace ignores in case of non-monorepo

Description
Hey @mehulkar I tried to fix #4140 .
This is my first time reading or writing in go so it's likely I may have done something wrong.
The way I did it is a bit redundant, as in the case of a monorepo the call to getWorkspaceGlobs is made 2 times and so is not the most efficient. Unfortunately I think I lack a lot of context to try and come up with a better solution, but I felt like trying :)

Just making sure, do you mean there's a duplicate call to fs.ReadPackageJSON?

Yes, that's what I meant.
By the way, I tried the refactor you suggested!

What happens in a real monorepo when the workspace config is missing?

This should still error as we call packageManager.GetWorkspaces in the BuildPackageGraph context constructor.

* In `npm` and `pnpm` implementations of `getWorkspaceIgnores`, the default return value is `**/node_modules/**`. Should we use that as the default here also? Or can we trust the user that if the workspaces config is missing, then we really only want to ignore the root `./node_modules`?

I think from my groking that node_modules/** matches what yarn does by default: https://github.com/yarnpkg/yarn/blob/3119382885ea373d3c13d6a846de743eca8c914b/src/config.js#L816

Let's merge this into my branch then!


⚠ Bofrost.lu has degraded performance

In 947f438, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1819 ms

Resolved: Bofrost.lu performance has improved in b99e678 after 6 minutes.


可以支持有的路由缓存，有的路由不缓存吗？

exclude include
获取 Outlook for iOShttps://aka.ms/o0ukef

发件人: chenqiuling @.>
发送时间: Thursday, October 24, 2024 5:10:42 PM
收件人: irychen/keepalive-for-react @.>
抄送: Subscribed @.***>
主题: [irychen/keepalive-for-react] 可以支持有的路由缓存，有的路由不缓存吗？ (Issue #29)
―
Reply to this email directly, view it on GitHubhttps://github.com/irychen/keepalive-for-react/issues/29, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BKZ4FUNXUMHBWUXEUX7ZHV3Z5C2RFAVCNFSM6AAAAABQQTLYBCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGYYTAOJUHAZDONA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

exclude include


paginating correct blog uri

Regarding the issue - Issue 1045, I have fixed the href attribute in blog/index.html to accomodate blog filters in URL.

Sagan will be soon retired. A note has been added to the README.
We don't accept contributions anymore as a result.
Thanks for your help!


image:: does not render

Drag and Droping an image from the WorkDir View creates
image::imageOfSomething.PNG[]
which does not render in HTML
I have to manually remove one ":" to
image:
then it works
I know ther is a difference between those two, documented here:  http://asciidoctor.org/docs/user-manual/#images
but only "image:" seems to work.

double colon (::) means block image, single colon (:) means inline image. I tested it but it seems working. Could please share a screenshot with editor and preview were open to see this issue ?
Thanks

I had trouble reproducing this error too.
But it seems to have something to do with "spaces" in filenames.
If there is no space in filename then (:) and (::) works fine.
If ther is space in filename only (:) works and (::) doesn't.

I was able to reproduce the issue. The problem is that you include an image block (image::anything.png) inline (i.e. not as a block).
You should either include the image as inline (image:anything.png) or include the image as a real block (preceded and following by a blank line).
This is a problem:
This is an image::anything.png[]
This is also a problem:
This is an
image::anything.png[]

This is not a problem:
This is an image:anything.png[]
This is also not a problem:
This is an

image::anything.png[]

@dewachterken That is the correct explanation. Maybe we could add a line before adding blog image.

I understand, thanks.


ColumnEqualizer

Great work! Please update the documentatie accordingly and we can merge.

Yes Joey of course. Great package btw!

This functionality is planned to be included in the next release.


Support custom authorization schemes

Currently only Bearer authorization scheme is supported. This PR adds option to modify the auth scheme used.
To use a custom scheme:
apollo: {
  authScheme: 'Basic',
  ... // other options
}

Closes #112

Thanks. I will merge it as is and will add minor modifications to it.


[BUG] Tests are flaky

What is the bug?
https://github.com/opensearch-project/opensearch-go/actions/runs/9293150937/job/25575676932
https://github.com/opensearch-project/opensearch-go/actions/runs/9071336838/job/24924837348
https://github.com/opensearch-project/opensearch-go/actions/runs/8796076027/job/24138260213
https://github.com/opensearch-project/opensearch-go/actions/runs/8707746532/job/23883482082
How can one reproduce the bug?
1 out of 5 PRs fails tests intermittently, retrying works.
What is the expected behavior?
Tests to pass reliably.

https://github.com/opensearch-project/opensearch-go/actions/runs/9665682575/job/26663396843?pr=570


Is there any ETA when offline mode would work on Android

@jeandomagni Thanks for your interest. That's be great if you could help us a hand.

I am also looking for the the offline feature of the MapBox on Android device. Are you working on it to make it available?

Yehh i am awaiting for this feature as well.

I am also getting the same error while downloading the map..
04-10 21:47:07.652 I/dalvikvm( 1285): JNI ERROR (app bug): accessed deleted global reference 0x1d3010f2In mgmain JNI_OnLoad
04-10 21:47:07.652 E/dalvikvm( 1285): VM aborting
04-10 21:47:07.652 F/libc    ( 1285): Fatal signal 6 (SIGABRT) at 0x00000505 (code=-6), thread 1285 (.naxam.mapboxqs)

@fleuverouge, @tuyen-vuduc , Any update on this?

@NeerajRai111 We haven't had any ETA yet. We built this based on our needs for our projects. We are happy to provide service to make it happen sooner because free resources aren't always available.

I'm checking out your demo MapBoxQs and seeing this problem when run on a Lenovo Tab 4 device.

FYI I had to revert to this commit 55a4780 as master was not building (missing iOS 4.1.x nuget)

I closed this issue because offline feature is now in latest version. Plz try out and file issues if any.


Case-sensitive SSH settings in NixOS unstable can create misleading sshd config

Describe the bug
Upon migrating from NixOS 22.11 to the current unstable release (soon to be 23.05), the OpenSSH service settings for password and keyboard-interactive authentication have changed. This transition requires case-sensitive adjustments that, if not properly made, can lead to a misleading and potentially insecure sshd configuration file.
Here are some of the settings that have been moved since the 22.11 release (but there are more):

NixOS 22.11
NixOS unstable

services.openssh.passwordAuthentication
services.openssh.settings.PasswordAuthentication

services.openssh.kbdInteractiveAuthentication
services.openssh.settings.KbdInteractiveAuthentication

Say that both settings were set to false.
If the case of these settings is not adjusted properly when migrating, NixOS does not provide any warning or error during the rebuild process. The resulting sshd config file contains both the default (true/yes) and user-specified settings (false/no), with the first one (undesired in this case) taking precedence due to its position in the file. This results in an sshd config file that essentially contains:
...
PasswordAuthentication yes
passwordAuthentication no
KbdInteractiveAuthentication yes
kbdInteractiveAuthentication no
...

Steps To Reproduce

In NixOS 22.11, set service.openssh.passwordAuthentication and/or service.openssh.kbdInteractiveAuthentication to false.
Migrate to the current unstable release of nixpkgs.
Move these settings to services.openssh.settings.passwordAuthentication and services.openssh.settings.kbdInteractiveAuthentication, but do not adjust the case.
Run nixos-rebuild switch.
Examine the resulting sshd config file, /etc/ssh/sshd_config
Access the host via ssh and see how it allows you to enter a password to authenticate.
Weep.

Expected behavior
When migrating and adjusting these settings, NixOS should provide an error if the case is not correctly adjusted. This would be similar to the error NixOS emits when you try to add a non-existent setting, such as services.openssh.settings.MadeUpSettingThatAsExpectedIsNotSilentlyIgnored.
Screenshots
N/A
Additional context
This is a problem because for sshd, the parameters are:
a) case insensitive
b) the first occurrence fixes the value
otherwise, sshd would croak and we would know that something broke.
Notify maintainers
@teto @tokudan @infinisil @pennae

Metadata
[pancho@helium:~]$ nix run nixpkgs#nix-info -- -m
 - system: `"x86_64-linux"`
 - host os: `Linux 6.3.2, NixOS, 23.05 (Stoat), 23.05.20230516.963006a`
 - multi-user?: `no`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.3`
 - channels(root): `""`
 - nixpkgs: `not found`

[pancho@helium~]$ nix flake metadata /etc/nixos
Resolved URL:  git+file:///etc/nixos
Locked URL:    git+file:///etc/nixos
Description:   Port of archify to NixOS + flakes + Home Manager.
Path:          /nix/store/m96s4rsnzx19ncgfs7glx3ayddshw54s-source
Last modified: 2023-05-17 07:30:40
Inputs:
├───disko: github:nix-community/disko/10402e31443941b50bf62e67900743dcb26b3b27
│   └───nixpkgs follows input 'nixpkgs'
├───emacs-overlay: github:nix-community/emacs-overlay/016a781cc93d3c7f7005b6ba12f667e9861056e0
│   ├───flake-utils: github:numtide/flake-utils/5aed5285a952e0b949eb3ba02c12fa4fcfef535f
│   └───nixpkgs follows input 'nixpkgs'
├───home-manager: github:nix-community/home-manager/b7d814c5744dca7e70b3dc2638f06568dce96ca6
│   └───nixpkgs follows input 'nixpkgs'
├───hyprland: github:hyprwm/Hyprland/642030f959efe7bd2692bf6a4236d4c1b39ee51a
│   ├───hyprland-protocols: github:hyprwm/hyprland-protocols/4d29e48433270a2af06b8bc711ca1fe5109746cd
│   │   └───nixpkgs follows input 'hyprland/nixpkgs'
│   ├───nixpkgs follows input 'nixpkgs'
│   ├───wlroots: gitlab:wlroots/wlroots/6830bfc17fd94709e2cdd4da0af989f102a26e59
│   └───xdph: github:hyprwm/xdg-desktop-portal-hyprland/c0e233955568fbea4e859336f6d3d14d51294d7c
│       ├───hyprland-protocols follows input 'hyprland/hyprland-protocols'
│       └───nixpkgs follows input 'hyprland/nixpkgs'
├───nix-index-database: github:Mic92/nix-index-database/219067a5e3cf4b9581c8b4fcfc59ecd5af953d07
│   └───nixpkgs follows input 'nixpkgs'
├───nixos-hardware: github:NixOS/nixos-hardware/71ce85372a614d418d5e303dd5702a79d1545c04
├───nixpkgs: github:NixOS/nixpkgs/963006aab35e3e8ebbf6052b6bf4ea712fdd3c28
└───stylix: github:danth/stylix/a9367cea1bdc0ad35b3b0b2afc4aa9cf94cdecdb
    ├───base16: github:SenchoPens/base16.nix/6b404cda2e04ca3cf5ca7b877af9c469e1386acb
    │   └───nixpkgs follows input 'stylix/nixpkgs'
    ├───flake-compat: github:edolstra/flake-compat/35bb57c0c8d8b62bbfd284272c928ceb64ddbde9
    ├───home-manager follows input 'home-manager'
    └───nixpkgs follows input 'nixpkgs'

thanks for the detailed explanation. You are actually not the first to tumble on this and I heard about similar cases which means something should be done.
To put things in context, my initial PR adding freeform settings aimed at increasing security by making it easier to share a future/potential "hardened ssh nix profile" I missed when switching some ansible ssh hardening script to a nixos configuration.
It apparently resulted in the opposite because of my ignorance about sshd:

I changed the case because to be the same man sshd_config as I thought it made setting discovery easier. It had not crossed my mind that people would make a mistake in updating the config,
nixpkgs runs the ssh -t  validation step of the config so I thought wrong configs would be caught.

After going to #openssh and a few tests, I usually try to avoid blaming others but I am disappointed in the ssh validation command. The whole ssh configuration in fact is awkward with some options that can be repeated across lines or inlines, some not, some separated by a space, some by commas. And the most crucial point is that there is no way (to my knowledge) to run a strict validation steps that fails when options are ignored (because set multiple times for instance).
So IMHO this is really an upstream issue where they should validate the config better but because I dont wanna patch openssh (or rather I dont have the time), I think the best "fix" is to standardize the case as openssh doesn't care either.
I've just written this which might do the trick . I will propose it to https://github.com/NixOS/nixpkgs/pull/231467
commit faa91bc4122a9eff4ddbb07c29aa2b88a71bc49f
Author: Matthieu Coudron<EMAIL_ADDRESS>Date:   Fri May 19 02:27:27 2023 +0200

    attempt to fix sshd issues

diff --git a/nixos/modules/services/networking/ssh/sshd.nix b/nixos/modules/services/networking/ssh/sshd.nix
index 910b9c5e56c..7d7dc54773c 100644
--- a/nixos/modules/services/networking/ssh/sshd.nix
+++ b/nixos/modules/services/networking/ssh/sshd.nix
@@ -22,12 +22,16 @@ let
         # else if isList     v then concatStringsSep "," v
         else throw "unsupported type ${typeOf v}: ${(lib.generators.toPretty {}) v}";

-  # dont use the "=" operator
+  mkLowerCaseKeyValue = {
+    mkValueString ? mkValueStringDefault {}
+  }: sep: k: v:
+    "${lib.strings.escape [sep] (lib.strings.toLower k)}${sep}${mkValueString v}";
+
   settingsFormat = (pkgs.formats.keyValue {
       listsAsDuplicateKeys = true;
-      mkKeyValue = lib.generators.mkKeyValueDefault {
-      mkValueString = mkValueStringSshd;
-    } " ";});
+      mkKeyValue = mkLowerCaseKeyValue {
+        mkValueString = mkValueStringSshd;
+      } " ";});

   configFile = settingsFormat.generate "config" cfg.settings;
   sshconf = pkgs.runCommand "sshd.conf-validated" { nativeBuildInputs = [ validationPackage ]; } ''

Nice, it looks like this was fixed with the above PR, feel free to re-open if that's not the case!


perf: code and performance optimizations

switched from node-fetch to undici since it has 0 dependencies and was made by the Node.js organization.
made so that readConfig() won't do I/O calls every time you call it. the config data should be stored in a global variable called configData, writeConfig() would also overwrite this.
other misc code refactors. see changes in commits.

<3


Make some asset loading functions monomorphic

This reduces the size of executables when using bevy as dylib by ensuring that they get codegened in bevy_assets instead of the game itself. This by extension avoids pulling in parts of bevy_tasks and async_task.
Before this change the breakout example was 923k big after this change it is only 775k big for cg_clif.

For cg_llvm in release mode breakout shrinks from 356k to 316k. For cg_llvm in debug mode breakout shrinks from 3814k to 3057k.

CI passes.

bors r+


Thanks for the good tool

I almost succeeded backing up my data with your tool and im thankful. However i have one question. The resulting sqlite table is encrypted also, and cannot be opened with sqlite.


BindCraft minimum & optimal hardware requirements

Hello.
I am setting up a work platform that can run BindCraft. Could you please tell me the minimum hardware requirements and the optimal hardware requirements for running BindCraft? I would greatly appreciate it.

Well depends, I would recommend getting these GPUs: L40s, V100, A100, or H100. About 128 Gb RAM, several Tb of storage space, and at least 4 CPUs, ideally 32 or more (not for BindCraft but more general downstream usage of other tools). Technically it can run on any Linux computer with CUDA compatible GPU, but GPU memory limits how big your designs can be.

Thank you for your quick reply! It helps a lot


Comm interface into loggers

Merging loggers and comm-interface

Technically not the right title as this isn't integrating Comms and Loggers. But since Comms Radio Interface is done to a good extent, it can be merged to master seperately


Updated inline documentation for code generation

Hi @CamSoper, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (casoper). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


Feature/194 expose Geocoder.isPresent Android

Implements (https://github.com/Baseflow/flutter-geocoding/issues/194)
Pre-launch Checklist

[ ] I made sure the project builds.
[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is does not need version changes.
[ ] I updated CHANGELOG.md to add a description of the change.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I rebased onto main.
[ ] I added new tests to check the change I am making, or this PR does not need tests.
[ ] I made sure all existing and new tests are passing.
[ ] I ran dart format . and committed any changes.
[ ] I ran flutter analyze and fixed any errors.

Fixed in (https://github.com/Baseflow/flutter-geocoding/pull/202) (https://github.com/Baseflow/flutter-geocoding/pull/203) ((https://github.com/Baseflow/flutter-geocoding/pull/204)


Port nuget to .NET core

.NET Core csproj can have nuget build in. Really simplifies solution and does all from dotnet cli easy.

Many libs that support .NET Framework use Cake or Fake to build, pack and publish. I don't think there's an issue with using Cake.

I am considering refreshing the build setup a bit when I get to it, but due to all the other pending issues this is not the highest priority at the moment.
Thanks!
/ Nils


Use config.github.url in email notifications

URLs in email notifications are broken when used with GitHub Enterprise. This should fix it.

Works on staging


Add doc links throughout our user-facing APIs

What was changed
I backfilled doc links throughout our user-facing APIs. I didn't touch the internal package as those aren't supposed to be for external consumption.
While here I cleaned up a few things, like adding links to referenced code samples and removing a doc comment in a spot where they're unsupported; you can't add links in the comments on interface methods or struct members.
Why?
Linking readers to referenced APIs saves them time when trying to understand how to use temporal.
Checklist
This was tested by running godoc locally and inspecting the rendered docs. Note that cross-package doc links still don't work so cannot be verified locally.

I didn't touch the internal package as those aren't supposed to be for external consumption.

Not necessarily true (many times that's the only way we can document struct fields). But this LGTM, feel free to merge at will.

I didn't touch the internal package as those aren't supposed to be for external consumption.

Not necessarily true (many times that's the only way we can document struct fields). But this LGTM, feel free to merge at will or let us know if it won't let you.

Yeah, I'm used to those being internal only so skipped them out of habit. If missing docs still bothers me I'll take a swing at those too


Dockerize BWC test runs

[Triage] Could you provide more information to this issue and acceptance criteria for this issue?

[Triage] We will revisit the design when we start working on BWC testing implementation. Closing this issue for now. We will re-open this again later if required.


(397) Add more data to worldwide org content item

Add ordered people to worldwide org
Whitehall currently shows any people who are appointed to certain roles
in a worldwide org in the following way:

image and details for the person in a primary role, if they exist
details only for people in secondary or "other" roles.

In order to render them in government-frontend, we need to have the
ordered list of people and their roles in the content item.
As these new links include role appointments in the chain, they need to
be exempted from requiring base_path.
Add more fields to the example
Body and logo have already been added to the schema, but not to the example.
⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠
This application is owned by the publishing platform team. Please let us know in #govuk-publishing-platform when you raise any PRs.
Follow these steps if you are doing a Rails upgrade.

This looks good to me. Interesting that you have taken the approach of amalgamating various organisations into one perfect example. Does that have the potential to be confusing down the line?

I thought about that 😅 Yeah, I think I'll revise it to pick the richest org with the minimum of fudging, but still providing enough content to have all the relevant tests in frontend.


Change the Options pop-up position while selecting a row

Ref: https://github.com/bigbinary/neeto-kb-web/issues/6157
https://bigbinary.neetorecord.com/watch/4367ef21-8b5f-456e-bb18-5f60fa30036f
enhancement _t

This will be fixed by https://github.com/bigbinary/neeto-editor/issues/1159


duplicate checking token existence

token existence is checked in ownerOf function. No need to use _exists here

No

Fixes #

Hello @yidongw, thank you for contributing!
This has been brought up a couple times: the reason why _exists is called is that it'll revert if there is no owner. We could remove it and add that check manually here, but a) we'd be duplicating _exists, and b) we'd lose the nice semantics conveyed by the current implementation.


fix: call async methods on hass asyncio loop + add poetry for easier development

Fixes #80
I did lots of debugging, I added more debug statements to the reader and writer functions and I discovered that the stream was never closed and that my writer was stuck at sending the authorization packet.
def callback(_) -> None:
	stream.close()

try:
	async_call_later(self._hass, 0.1, callback)
except Exception as ex:
	pass

I found a few places where we called an async function on a worker thread and that caused errors as the async function needs to be processed on a thread that owns the loop.
I also added poetry, as I find it easy to install it for local testing. Let me know if you don't want that.
Thank you

We cannot remove the 1 second timeout - it wiľ break installation of other people

We cannot remove the 1 second timeout - it wiľ break installation of other people

do you know why it is necessary?
it was not called for me for some reason, I think because of calling it in wrong thread.
so I can run it similarly as the other fixes.
I was just wondering what is the reason for that timeout.

hi @kukulich  I posted an update. however, I am not sure if it is a good idea to close a stream in the main "UI" thread
let me know what you think

There was problem that without the timeout the stream was closed to early and the sent packet was not delivered to Jablotron.

I think this version was used earlier but HA started to report it as problematic codde.

I think this version was used earlier but HA started to report it as problematic codde.

ok, I will try to update it on my side and test it to see if there are issues.
I could see this being a problem only if this was run on the "UI" thread

@kukulich OK, so I know what was the problem. the _send_packet_by_stream is called both on the main thread as well as on the worker threads.
it is okay to do sleep and close it on the current thread if we are not on a main thread.
let me know what you think. I tested this and integration loads find, I tried arming/disarming as well as motion sensors and smoke detectors seem to be working and reporting fine.

@zlymeda is it possible to test just the changes that are necessary to fix the bug?

I've tested it in my environment and it looks there's no problem so I'll merge it. Thanks.


Missed an Invite Link

Please describe the changes this PR makes and why it should be merged:
Somehow missed to update the Support Server invite link in the README.md. Don't know how I managed to miss that, have read over the file multiple times.
Status

[x] Code changes have been tested against the Discord API, or there are no code changes

Semantic versioning classification:

[ ] This PR changes the library's interface (methods or parameters added)

[ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)

[x] This PR only includes non-code changes, like changes to documentation, README, etc.

Didn't ment to add Intents to this pull request. Am not 100% shure why this happened. Anyways any suggestions for the Intent part? I do not really know if that one is good or not.

Adding a section for intents is irrelevant to this PR. Furthermore, I don't think intents section should go in "Creating Events" page.


Display planning and queued time for a query in its profile page

Modified UserSharedBit protobuf for marking planning end time. This will allow for accurately reporting the planning time of a query.
In the absence of this property, for older profiles, the root fragment's (i.e. SCREEN operator) start time is taken as the estimated end of planning time.

+1

Please modify the title to include the JIRA ticket number:
DRILL-XXXX: Display planning and queued...

+1


Switch to debugid crate instead of strings

The Debug ID and Code ID were represented by strings in the breakpad
format.  This switches this to the DebugId and CodeId types from the
debugid crate as also used by symbolic.
The benefit is strong types and that DebugId becomes Copy.
As a result of this some tests which used invalid Debug IDs had to be changed to use valid ones.  Also the CodeId is now normalised resulting in snapshot changes.  I went with uppercase as it seemed more similar to the current display, though lowercase would not need an extra string allocation so might be better.

Argh, sorry about all the merge conflicts. Friggin' dependencies.

My fault for sorting the dependencies...

I'm not terribly confident in reviewing this, I really don't understand the semantics of debugid/codeid stuff. Especially once Breakpad's extensions and bugginess get involved. @luser do you have the time to spare?

Most of my confidence comes from the fact we run symbolic(ator) with this in prod, receiving lots of minidumps from breakpad etc, so its breakpad compatibility should be fine.

@Gankra how happy are you with the casing changes in the code ids?  This affects your json output format and not sure if you correct for this at lookup time (this is what symbolicator does, it fixes the casing based on the symbol server rather than hoping the casing of the original code id was correct).
Otherwise the debugid crate has been updated to represent the PDB 2.0 format so once that's released I'll update this PR.

I'll confirm with the others that this won't break us, but it sounds like keeping things uppercase would be a good compat improvement!

Wait actually hold on I'm a bit confused. I vaguely remember reading some discussion of certain symbol servers being case-sensitive, and I thought the conclusion was "ah yes, everyone expects these to always be uppercase". But now I can't find that (did it happen elsewhere...?).
What is the precise argument for this, again?

Ok so the precise change is that debugids (used for getting symbols/pdbs) would stay the same (always upper case with the "breakpad" formatter..? or does it preserve case?)
But codeids (used for getting the actual binaries, something mozilla doesn't do afaict) would get newly lowercased?
We've tested and microsoft's official tooling seems to be wholy case-insensitive. Our tooling is case-sensitive but if only codeids change then I'm not sure we really care?

But codeids (used for getting the actual binaries, something mozilla doesn't do afaict) would get newly lowercased?

Correct. The Windows binaries are available on Mozilla's symbol server, and Microsoft's debuggers will fetch the matching binaries given a minidump, but nothing in the crash reporting machinery relies on being able to do this itself.
The only usage I've seen of this is heycam's chkimg tool, which does use the code id to build a URL to fetch the matching PE file.
I don't think there's a right answer here. There is no "original" case, all the IDs in question are stored as integers (or GUIDs, which are just a series of integers) in minidumps, so the case in question is just a matter of how you format those integers as hex strings. I don't have any evidence to suggest I know better than the Sentry folks on this matter. :)

I think we can land this for now and let it bake a bit before cutting a release (this is gonna be a big release lmao fuck)

Ok so the precise change is that debugids (used for getting symbols/pdbs) would stay the same (always upper case with the "breakpad" formatter..? or does it preserve case?)

(so non-overlapping timezones seems a challenge, apologies to not responding :/)
Yes, DebugIds maintain the same formatting, also their breakpad formatting (which is uppercase UUID, lowercase age).
The change is in CodeIds which are now all lowercase.  Before the case was mixed, but as pointed out already this is stored in integers etc in the minidump so don't really have a case.  We have encountered some case-sensitive symbol servers which is why our users can configure exact casing rules used by the symbol servers but the casing conversions are only done just before the symbol server requests.


Zip64 writer+reader rebased

Replaces https://github.com/crystal-lang/crystal/pull/7236
Closes https://github.com/crystal-lang/crystal/issues/7103
The original PR was made by @julik
In this PR I did:

[x] Rebased with master branch.
[x] Updated code to make CI happy.

Thank you so much @mamantoha for picking this up. I was actually feeling very guilty for letting this rot for so long, but didn't have time (or energy) to pick it up again. Maybe you could take over my branch too if that's better (there were some comments there from what I see)

Hi @julik, this PR contains 2 commits from your branch rebased with the master branch + some minor changes in the third commit which fix specs. I even didn't change the specs for this :wink:.
I had no plans to change your initial implementation. I was just curious if it actually worked. And yes, this working pretty well.

I will be delighted if you can pick up my implementation and drive it to completion, I won't have time in the coming months to do it.

@mamantoha This is really great! But it's also a lot of effort to review. Do you think there's a chance of splitting this into smaller pieces? I see there are a few new types added, but they seem to be used in the refactored code, so I don't see an easy way for that.
CRC32Writer is missing specs. It's a public API so it should be tested by itself (or really even if it was internal).

This would be a very nice addition - what is needed to get this merged?

Would be great to see this merged.


Add linter to check no "Apply suggestions" commits

Add a linting job to verify that no commit message in a PR contains the
case insensitive string "Apply suggestions from code review". Commits
with exactly this title are generated by GitHub automatically when a
batch of proposed changes from code review are accepted from the GitHub
UI. A number of such commits have made it into various Submariner/*
repos.
Commits addressing code review feedback should typically be squashed
into the commits under review, or made into well-commented discrete
commits.
Signed-off-by: Daniel Farrell<EMAIL_ADDRESS>

I created a PR with an "Apply suggestions" commit to show this failing: https://github.com/dfarrell07/submariner/pull/43


QR code is too small to scan

Even though there's plenty of unused space in this screen, the QR code is too small and my phone fails to scan it.
If I download the code and show it a bit bigger using another program, it scans correctly.
In the screencap from my phone you can see the pixels of the QR code have approximately the same size as the LCD pixels of my monitor, so they are very hard to recognize.
If the code cannot be made bigger, I would suggest clicking on it brings a popup with a larger version.

It works on my phone without any issue. However it's good idea to think about make it a little bigger or give option to present bigger version on layer.

@segfaultxavi address QR has now bigger size. Please check when you will have a time.
For me it works fine.


How to make -storage.local.retention=24h longer

Hi, Team,

I've tried to update "retention" from 24h to 8760h below, but both failed. Any tips? Thanks!

$ kubectl edit statefulsets -n tectonic-system prometheus-k8s
apiVersion: apps/v1beta1
kind: StatefulSet
..
    spec:
      containers:
      - args:
        - -storage.local.retention=24h

Edited this file from console.
kind: Prometheus
  name: k8s
  replicas: 1
  retention: 8760h
  ruleSelector:

Are my storage config right?

  retention: 8760h
  storage:
    volumeClaimTemplate
      - metadata:
        name: prometheus-k8s-db
        annotations:
         volume.beta.kubernetes.io/storage-class: gold
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 10Gi
        selector:
          matchLabels:
            app: prometheus-k8s

The Tectonic Prometheus instance intentionally does not offer persistent storage today, as we're about to migrate it to Prometheus 2.0. Regarding the retention, there is a ConfigMap called tectonic-monitoring in the tectonic-system namespace, within it you can configure selected things for the Tectonic Monitoring stack. We need this in order to be able to control the customization so we can provide any guarantee for automated upgrades to work.
See the documentation for what is explicitly configurable here.

Amazing!

I've set "retention: 8760h" following your guide.

$ kubectl edit cm -n tectonic-system tectonic-monitoring
configmap "tectonic-monitoring" edited
$ kubectl edit statefulset -n tectonic-system prometheus-k8s
Edit cancelled, no changes made.
spec:
      containers:
      - args:
        - -storage.local.retention=8760h

prometheus-k8s-db cannot survive after pod restating, what's your recommendation to backup and recover prometheus-k8s-db? Thanks!

      volumes:
      - emptyDir: {}
        name: prometheus-k8s-db

        volumeMounts:
        - mountPath: /var/prometheus/data
          name: prometheus-k8s-db

Fyi, I used to copy data files out from prometheus container as a backup, and then copy back in as recovery. But those data are unrecognizable at last.
$ kubectl exec -it prometheus-3067433533-4rz0q -- sh
/prometheus # tar zcvf data.tgz data
$ kubectl exec -it prometheus-3067433533-4rz0q -- sh
/prometheus # ls
data      data.tgz
/prometheus # du -sh data.tgz
43.7M    data.tgz
$ kubectl cp default/prometheus-3067433533-4rz0q:/prometheus/data.tgz data.tgz
tar: removing leading '/' from member names
$ ls
data.tgz
$ du -sh data.tgz
44M    data.tgz

Can I add permanent storage the same way as "retention" at here?
$ kubectl edit cm -n tectonic-system tectonic-monitoring
apiVersion: v1
data:
  config.yaml: |
    prometheusOperator:
      baseImage: quay.io/coreos/prometheus-operator
      prometheusConfigReloaderBaseImage: quay.io/coreos/prometheus-config-reloader
      configReloaderBaseImage: quay.io/coreos/configmap-reload
    prometheusK8s:
      retention: 8760h
      storage:
        volumeClaimTemplate
          - metadata:
            name: prometheus-k8s-db
            annotations:
             volume.beta.kubernetes.io/storage-class: gold
          spec:
            accessModes:
            - ReadWriteOnce
            resources:
              requests:
                storage: 10Gi
            selector:
              matchLabels:
                app: prometheus-k8s
      baseImage: quay.io/prometheus/prometheus
    alertmanagerMain:
      baseImage: quay.io/prometheus/alertmanager
    ingress:
      baseAddress: base.address.com
kind: ConfigMap
metadata:
  creationTimestamp: 2017-08-24T08:35:14Z
  name: tectonic-monitoring
  namespace: tectonic-system
  resourceVersion: "35133205"
  selfLink: /api/v1/namespaces/tectonic-system/configmaps/tectonic-monitoring
  uid: 26b85bf4-88a7-11e7-a5f6-123c979a9fd4

Persistent storage for the prometheus-k8s instance is intentionally not configurable today, as we're about to migrate to Prometheus 2.0, which has a completely new storage format, and data migrations are close to impossible. Therefore we decided to only start allowing to configure persistent storage once we roll out Prometheus 2.0. I understand this is not ideal, but Prometheus 2.0 stable was released today, and we're already in the process of integrating it into Tectonic :slightly_smiling_face: .

Thanks! brancz

We're now using tectonic_1.7.5. When can we expect to migrate to Prometheus 2.0 on our stack?

I just read release note and Prometheus 2.0 migration guide. Amazing! We can upgrade to 2.0 on our current Tectonic stack, right? Would be no impact on Tectonic stack itself right?
https://coreos.com/blog/prometheus-2.0-released
https://github.com/prometheus/prometheus/releases/tag/v2.0.0
https://prometheus.io/docs/prometheus/2.0/migration/

This is the only one to access our historic monitoring data, right?

"To retain access to your historic monitoring data, run a non-scraping Prometheus instance running at least version 1.8.1 in parallel with your Prometheus 2.0 instance, and **have the new server read existing data from the old one via the remote read protocol**."

It sounds like you've just rolled out Prometheus, if you don't have a lot of important historical data, I highly recommend just upgrading to 2.0 without data migration.
The Tectonic Monitoring Prometheus instance will automatically be upgraded for you in one of the next Tectonic releases, in facts it's what I'm working on as we speak.

Sorry for sort of hijacking the thread but I was wondering how does one accomplish the same using just kube-prometheus. I don't see any config maps with this entry.

I'll close this here. If you have follow-up questions feel free to re-open or create a new issue.
Happy holidays! :tada:

As retention is not defined in kube-prometheus out-of-the-box, what does it default to?

Persistent storage is not available in the same way on all clusters, the kube prometheus stack is really just an example and is absolutely there for you to customize to your need.
Default retention is 24h iirc.


Done all tasks.

Done all basic tasks and added new hello_world.swift
ps: iosdev747 and iosdev474 are different, kindly do not treat them as duplicate user, their names are Anshul Singh and Arsh Singh respectivly.

@iosdev747 Yup they are different, my bad. Will take care in the future.
However please add a language already not taken as we are overwhelmed by the response and are having a hard time resolving conflicts :smile:
C, cpp and python are already there and hence I cannot merge this


Restrict Mac framework to x86_64

I think this is a real workaround for issues like antitypical/Result#21 and antitypical/Result#25.
I don’t think this will work around issues like #21.

:ok_hand:


Add Typescript support for VS modules installed with Yarn/NPM

What is the motivation for adding / enhancing this feature?
We've just ported the external checkout from Filip to a VS module. But I noticed that installing the module with yarn isn't working, because of the Typescript files included in the module, or a missing configuration file in the module. Anyway, these modules are currently not bundled correctly by Webpack.
What are the acceptance criteria

VS should compile modules that are installed with Yarn/NPM and contain Typescript.
If extra module configuration is needed, add it to  src/modules/module-template

Can you complete this feature request by yourself?
No
Extra info

Tested on VueStorefront 1.8

Maybe we should add the TS support to all vsf-* named modules?

@pkarw even better. I'll add it to the feature request

@patzick can You check this one as well?


I got in touch back in April with @jefflill over email about Cadence/Temporal and your .NET libraries. We (Ionburst) have been looking at integrating Temporal into our stack for a while - and as a .NET Core shop, we're interesting in using Neon.Temporal.
We've been keeping an eye on progress until we had time to start exploring Temporal fully. We're now in that place, so I was hoping to find out if Neon.Temporal is ready to use? I appreciate it's still under active development and we're not looking for a production-ready release, just something we can start to play around with.
Alongside that, we're more than happy to be guinea pigs and help with bug testing and scale/load-testing further down the line.
Cheers! 😄

HI: We're all doing fine and I hope you are too,
We're excited to see Temporal v1 launch.  We started the Temporal port a few months ago but sidelined it for several weeks while Temporal was making their final breaking changes and one of started a new job.
We're planning on getting started back into this beginning next week.  As you probably remember, the current Cadence implementation is actually based on the Cadence GO client and a wrapper program we developed that uses HTTP to proxy calls from .NET our GO proxy and then on to the Cadence server.  We're going to continue with this strategy for Temporal in the near term, but we hope to build our proxy as a DLL/shared library and drop the HTTP stuff and just marshal data between .NET and GO in memory buffers.  We experimented this briefly a year ago and has some problems which we now believe were unrelated.  This will be quite a bit nicer.
Neon.Cadence has been in serious test/production for a year or so now by a sister company and we really haven't seen much trouble (although traffic is pretty low).  These services are deployed as .NET Core to Linux containers running in Kubernetes.  We've seen 2-3 cases where the .NET side lost connectivity with the GO proxy and we had to restart the containers (there's a way to detect this situation from .NET).  We hope this will be moot after we convert to DLLs.
It's too early to give you an ETA on this.  We'll need to get back into this for a few week.  I'm crossing my fingers that perhaps we'll see something beginning to work in 4-6 weeks.
There are a couple important gaps right now in Cadence and Temporal being a port, has the same issues:

There's currently no way for a workflow to wait for one of multiple things to happen, like waiting for one of two child workflows to complete or a signal to be received.  We believe we've thought this through.  This will take a bit of refactoring.

We also haven't doing anything around workflow unit testing support yet.

Our plan is to:

Publish one or more alpha releases in maybe 4-6 weeks when most things work again (excluding the multi-wait and unit testing)
After we've added the multi-wait and unit testing and it looks reasonable, we'll start doing preview releases and we'll port our sister companies production cluster over.
Our thinking is that we'll continue doing preview releases into 2021 that are still based on the GO proxy but expected to be usable for production.
Q1 2021, we're planning on beginning a native gRPC implementation and dropping the GO proxy completely,  I haven't scoped how much work this will be (but hope springs eternal, so hopefully it won't be too bad).  Once this is complete and it looks good we'll make this a production release.

I expect the native gRPC production release to work much the same as he GO proxied one.  I think the main changes will be that some of the API methods will no longer be async and I think we'll be able to replace some of the workflow/activity futures related classes with standard .NET Task semantics.  We ended with more async APIs than are really necessary due to the additional layer of async-ness due to the HTTP communication with the GO proxy.
We really do welcome your interest and would love to have more eyes to be sure we get it right.  I've been super excited about this stuff since I saw Maxim do a Cadence talk 3-4 years ago.  I think the .NET community will love it.
--Jeff<EMAIL_ADDRESS>@johncburns1
@marcusbooyah

Fantastic, thanks for the update!

Hi there, how has this situation developed? Best, Robert

@surumadurum thanks for checking in! Naturally our development slowed down a bit due to unforeseeable circumstances (COVID).   We are still actively working on Neon.Temporal and it is nearing stability.
At the moment we are wrapping up Exceptions and Exception handling.  Once Exception handling is complete, Neon.Temporal will be usable featuring much of the same functionality Neon.Cadence provides.  After this initial port is complete we plan to implement the features mentioned here by @jefflill.
Thanks for the patience and if you have any more specific questions or just want an update please do not hesitate to reach out!

This has been on the back burner but we just decided to restart the effort because the current Cadence/Temporal implementations have stopped working on the latest .NET SDKs due to ASP.NET runtime conflicts.
We currently deploy a GOLANG proxy process that communicates with Cadence/Temporal servers and then bridge calls from the C# side to the proxy via HTTP.  The new plan is to convert the proxies to shared libraries (DLLs on Windows) so we'll be able to just do in-process calls.  We has this close to working a couple years ago but we had to move on to other priorities,
We're going to track this effort here: #1295
The Temporal implementation is otherwise fairly far along.  @johncburns1 has some error handling work remaining and I believe there were still a few unit test failures.


Use xref to link objects automatically in the doc

Describe the issue linked to the documentation
numpydoc.xref can be used to automatically create the links to the objects that are often referenced across the project's docstrings, instead of manually having to write the rst
For example, instead of writing
"""
See :class:`GapEncoder` or :class:`MinHashEncoder` for scalable alternatives.
"""

We could write
"""
See GapEncoder of MinHashEncoder for scalable alternatives.
"""

and still have working doc links!
Suggest a potential alternative/fix
I've started implementing this as part of #571.
This is done by adding the mapping in doc/conf.py, like so:
numpydoc_xref_param_type = True
numpydoc_xref_aliases = {
    # Python
    "file-like": ":term:`file-like <python:file object>`",
    "iterator": ":term:`iterator <python:iterator>`",
    "path-like": ":term:`path-like`",
    "Path": ":class:`python:pathlib.Path`",
    "bool": ":class:`python:bool`",
    # Matplotlib
    "colormap": ":doc:`colormap <matplotlib:tutorials/colors/colormaps>`",
    "color": ":doc:`color <matplotlib:api/colors_api>`",
    "Axes": "matplotlib.axes.Axes",
    "Figure": "matplotlib.figure.Figure",
    "Axes3D": "mpl_toolkits.mplot3d.axes3d.Axes3D",
    "ColorbarBase": "matplotlib.colorbar.ColorbarBase",
    # sklearn
    "LeaveOneOut": "sklearn.model_selection.LeaveOneOut",
    "Transformer": "sklearn.base.TransformerMixin",
    # joblib
    "joblib.Parallel": "joblib.Parallel",
    "joblib.delayed": "joblib.delayed",
}

I guess we can close this since it has been implemented in https://github.com/skrub-data/skrub/pull/571


Add arm64 support

Added arm64 support with the help of this article: https://devblogs.microsoft.com/visualstudio/now-introducing-arm64-support-for-vs-extensions/
The SolutionColors extension now works just fine on my Apple Silicon Macbook Pro (M2 Pro).

Thank you for this!


UIOP:COMMAND-LINE-ARGUMENTS

UIOP has this compatibility layer, no?

Hi Robert,
true, however sometimes I use at least ecl without asdf and then I am forced to include some functionality
like this separately, loading package.lisp and {name}.lisp separately for
simple enough packages.
There is probably a better solution, but this is my dirty one.
However it would be useful to point out in the readme that uiop: hast this.


Payload | Plugin documentation

Plugins - Overview
On the plugins overview page, I read "Writing plugins is no more complex than writing regular JavaScript. If you know how spread syntax works and are up to speed with Payload concepts, writing a plugin will be a breeze."
This got me excited to start writing my first plugin, since my understanding of Payload concepts is little, I wanted to start with copying the plugin code as its provided on this page at the simple plugin section.
import { Config, Plugin } from 'payload/config'

const addLastModified: Plugin = (incomingConfig: Config): Config => {
  // Find all incoming auth-enabled collections
  // so we can create a lastModifiedBy relationship field
  // to all auth collections
  const authEnabledCollections = incomingConfig.collections.filter((collection) =>
    Boolean(collection.auth),
  )

  // Spread the existing config
  const config: Config = {
    ...incomingConfig,
    collections: incomingConfig.collections.map((collection) => {
      // Spread each item that we are modifying,
      // and add our new field - complete with
      // hooks and proper admin UI config
      return {
        ...collection,
        fields: [
          ...collection.fields,
          {
            name: 'lastModifiedBy',
            type: 'relationship',
            relationTo: authEnabledCollections.map(({ slug }) => slug),
            hooks: {
              beforeChange: [
                ({ req }) => ({
                  value: req?.user?.id,
                  relationTo: req?.user?.collection,
                }),
              ],
            },
            admin: {
              position: 'sidebar',
              readOnly: true,
            },
          },
        ],
      }
    }),
  }

  return config
}

export default addLastModified

I copied this code into its own file, imported it in my payload.config.ts file, and added it to my buildConfig options object as a parameter in the plugins array. When I try this sample code, I immediately get an error message: "incomingConfig.collections.filter((collection)", okay that makes kinda sense... I haven't provided a configuration object in my plugins declaration.
So I removed the whole "collections" declaration in the plugin's config. Which resulted in the error "plugin is not a function", weird... So I tried to add a collections array with 1 collection to the options of this test plugin, which threw me a different error (I was providing the slug string of the collection instead of the collection object) and for the sake of this problem definition I'll stop explaining my bugfixing proces cause I believe the point has been clear by now.
Desired solution
While a tutorial on developing your first plugin would be desirable, updating the existing documentation with the following features would already be of great value.

Provide a demo plugin that works straight away
It doesn't have to do anything fancy, console.log something on whatever action/event would already be good enough. My motivation for developing a plug-in is to add an extra config field on a collection. Since the goal of this section of the documentation (in my opinion) is to provide an out-of-the-box (working) demo plugin. I think something as simple as adding a configuration option "sparkle" on a collection level, that would accept a boolean to display a ✨ emoji in front of the collection title in the admin would already be an amazing start to explore creating a payload plugin, while also teasing me a little bit with some of the possibilities within Payload's concepts

Modify the intro section

"(...) If you know how spread syntax works and are up to speed with Payload concepts (..)"
If you are familair with Payload concepts, I expect you are most likely also familair with spread operators. I'd rather see a hyperlink that leads to a page that goes in deep detail on Payload concepts as spread operators. Obviously it doesn't hurt to display both. That said, the existing concepts page is insufficient for this, since this page doesn't make it clear to me how Payload's concept work on a technical level. I know that these concepts exists and what they do, I just don't know how to modify them via a plugin.

Totally missed this one....
https://payloadcms.com/docs/plugins/build-your-own

Good find! Yes, we have some materials regarding plugin creation but plan to make a lot more as well.
Keep an eye out - more is on the way!


Fixing: #1549 Bytes not being parsed correctly in KoreToK parser

Fixes: #1549

What is the correct representation? I've looked through the code and I can't find any syntax or references to such syntax.
If I print anything, it won't parse anyway.
The closest I can come up with is String2Bytes("bytesHex").


Scope Query: WhereTranslation

Never done php tests, but I followed your logic. Hope its correct.
The scope itselft is like you asked

Sorry mate I can't merge your PR because the tests are failing. I did this for you here: https://github.com/dimsav/laravel-translatable/pull/168

Thanks a lot for the contribution!

My bad. Thanks for adding this feature :+1:


Use specific branches when updating sonarqube.

Description
When we do a PR check, we run sonar-scanner and the results are uploaded to our SonarQube instance using the default master branch. We should, instead, upload these results to their own separate branch and only upload to master when the PR is actually merged.
Please note that there will be a separate PR for App-Interface which I'll post here, but it doesn't block this from being merged once I remove the DONOTMERGE label.
Fixes # (issue)
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[ ] Refactor

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I run make pre-commit to check fmt/vet/lint/test-no-fdo

Code coverage properly showing up specifically for the PR (166):


Add structure for Doxygen on API and base for Read the docs

Minimal headers for API documentation

Looks great, thanks

@Skiars ok to merge?


Crash when conjunction is not set

conjunction: config[key].conjunction !== false crashes if conjunction is not set.

Ignore me. I mistyped my key.


Migrate from Drone.io to Github actions

Is your feature request related to a problem? Please describe.
We would want to migrate CI to Github Actions.
Describe the solution you'd like
Drone requires runners to be hosted somewhere.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Worked to keep the CI with Drone. No need to migrate to GH.