After update my editor fonts disappeared

Issue Type: Bug
Hi
After the newest update my editor fonts disappeared. Old files appear with the correct font colors but all new files are just 100% white. Furthermore it stopped adding '' when I type ' . How do I get my old settings back? Also I am pretty new to coding so please express yourself simply. Thanks.
VS Code version: Code 1.27.1 (5944e81f3c46a3938a82c701f96d7a59b074cfdc, 2018-09-06T09:14:32.385Z)
OS version: Darwin x64 17.7.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz (4 x 3000)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledrasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
1, 1, 1

Memory (System)
8.00GB (2.16GB free)

Process Argv
/Applications/Visual Studio Code.app/Contents/MacOS/Electron

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

vscode-babel-coloring
dza
0.0.4

python
ms-
2018.8.0

sublime-keybindings
ms-
4.0.0

(1 theme extensions excluded)

Old files appear with the correct font colors but all new files are just 100% white.

What file types are we talking about? Can you share a screenshot of what you mean?

Furthermore it stopped adding '' when I type ' .

What does this mean?

Not sure why, but it works now. Thanks for your help Joao.


Minor import paths issue

Hello,
In AFHTTPRequestSerializer+OAuth2.h and AFOAuth2Manager.h, I suggest you change
#import <AFNetworking/...h>
to:
#import <AFNetworking.h>
for increased compatibility.  They currently result in an error if include paths aren't set to include system paths, which is important to many developers.
Thanks,
Drew

Actually it should stay as #import <AFNetworking/AFNetworking.h>, otherwise it will break when used with cocoapods and the use_frameworks! flag.
I did note that the 3.0.0 branch switched to module imports (@import). Could this be reverted? Modules are not available when using objective-c++.


Add node groups

[4.0.0] - 2022-07-20
Added

AWS managed node groups
multiple custom node groups
NodeSelector input for loki and prometheus components
Labels and taints for node groups

Fixed

Loki issue #5909 with image v2.5.0-with-pr-6123-a630ae3

Amazing work @qemanuel. You also replaced the ASG Launch configuration (deprecated) with the Launch Template.
You just could update the default value of the variable "k8s_auth_api" "client.authentication.k8s.io/v1alpha1" (deprecated) with "client.authentication.k8s.io/v1beta1"

Amazing work @qemanuel. You also replaced the ASG Launch configuration (deprecated) with the Launch Template. You just could update the default value of the variable "k8s_auth_api" "client.authentication.k8s.io/v1alpha1" (deprecated) with "client.authentication.k8s.io/v1beta1"

Sure, i can do that. It had that default because when we added that input  PR #15  , we didn't want to add a breaking change. But this PR have a lot of breaking changes, so i can update it

Amazing work @qemanuel. You also replaced the ASG Launch configuration (deprecated) with the Launch Template. You just could update the default value of the variable "k8s_auth_api" "client.authentication.k8s.io/v1alpha1" (deprecated) with "client.authentication.k8s.io/v1beta1"

Requested changes added


Multiple Scattering implementation

Hi guys,
As I understood from the code of your shaders and your excellent documentation, you have an implementation of multiple scattering for some cases. However, I would like to ask if you plan to modify it somehow taking into account new publications on this topic? For example, some of the publications by Stephen McAuley seemed very interesting to me:
Advances in Rendering, Graphics Research and Video Game Production
A Journey Through Implementing Multiscattering BRDFs and Area Lights

I've already studied those publications and we're not going to change our multiscattering implementation at this time. There's no good reason to do so especially considering how cheap the current version is.


Check bounds before accessing Vol::evacuate array

Fixes #8647
This PR does bounds checking on the Vol::evacuate array.  While this may fix crashes related to Dir entries with invalid offsets, it does not address whatever happened to generate the bad offsets.  So this is a partial fix at best.
There are other places where this array is accessed unchecked from dir_evac_bucket but these are the places that are involved in the reported crash.

I will look at it.

Looks reasonable to me.

Cherry-picked to v9.2.x


⚠ Adacta-fintech.com has degraded performance

In 775bd16, Adacta-fintech.com (https://www.adacta-fintech.com) experienced degraded performance:

HTTP code: 200
Response time: 2346 ms

Resolved: Adacta-fintech.com performance has improved in 09d1c59 after 21 minutes.


Initial Submission Spiderpig86

Check List:

[x] Tests pass (./test.sh <username> shows no differences between expected and actual outputs)
[x] All formatting changes by the build are committed
[x] Your launch script is named calculate_average_<username>.sh (make sure to match casing of your GH user name) and is executable
[x] Output matches that of calculate_average_baseline.sh
[x] For new entries, or after substantial changes: When implementing custom hash structures, please point to where you deal with hash collisions (line number)

Execution time:
Execution time of reference implementation:

Runs out of heap space for the 1B file (when run on 32 cores). Also please note that as per the README and PR template, new entries should run in about 10 sec to keep things manageable at this point, this one runs way longer before OOM-ing.

Gonna close this one for now as I haven't heard back and need to clean the slate a bit Please feel free to reopen once all the issues have been addressed. Thx!


Make Parquet changes related to #1720

The ORC related pushdown changes were made in this commit. The following equivalent Parquet changes also are needed to get the full perf benefit from the changes for #1720:

In ParquetPageSourceFactotry::createPageSource , we extract sufficient columns (to exclude overlap) for pushdown instead of base columns. For example, columns = ["a.b.c", "a.b"], you only pushdown "a.b" here, using the method projectSufficientColumns.
Now, the projected columns need to be converted to Parquet representation of the subcolumn. (In ORC, we have OrcColumn structure for every subcolumn recusrively). We need to use these subcolumns for predicates and scans.

FYI, I have a PR on top of #1720 and #2672 here: https://github.com/lyft/presto/pull/47. There's an open issue around handling absent element rows (see test in the PR) that causes this exception:
Loaded block positions count doesn't match lazy block positions count

This is a duplicate of #3396.


feat: Configure world-state to follow the proven chain only

Related to #7346

Benchmark results
Metrics with a significant change:

proof_construction_time_sha256_100_ms (16): 6,648 (+23%)
avm_simulation_time_ms (Token:mint_public): 45.1 (-41%)
app_circuit_proving_time_in_ms (FPC:prepare_fee (avm)): 2,782 (+39%)
app_circuit_proving_time_in_ms (Token:transfer_public (avm)): 3,920 (+70%)
app_circuit_proving_time_in_ms (AuthRegistry:consume (avm)): 3,043 (+55%)
app_circuit_proving_time_in_ms (FPC:pay_refund (avm)): 23,505 (+158%)
protocol_circuit_proving_time_in_ms (base-rollup): 92,647 (+17%)
protocol_circuit_proving_time_in_ms (root-parity): 43,872 (+29%)
protocol_circuit_proving_time_in_ms (public-kernel-setup): 43,760 (+19%)
protocol_circuit_proving_time_in_ms (public-kernel-app-logic): 47,255 (+28%)
protocol_circuit_proving_time_in_ms (public-kernel-teardown): 43,014 (+16%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,725
1,537
702
734 (-1%)
776 (+1%)

proof_construction_time_sha256_30_ms
11,726
3,150
1,417 (+1%)
1,430
1,474 (+1%)

proof_construction_time_sha256_100_ms
43,784
12,022 (+2%)
:warning: 6,648 (+23%)
5,394
5,367 (+1%)

proof_construction_time_poseidon_hash_ms
78.0
34.0
34.0
58.0 (-2%)
87.0 (-1%)

proof_construction_time_poseidon_hash_30_ms
1,515
415
199
220
269 (+1%)

proof_construction_time_poseidon_hash_100_ms
5,605
1,515
677 (+1%)
747 (+2%)
750

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
708
708
708

l1_rollup_calldata_gas
6,576
6,594
6,576

l1_rollup_execution_gas
583,038
583,207
583,340

l2_block_processing_time_in_ms
752 (-2%)
1,426
2,697 (-2%)

l2_block_building_time_in_ms
13,087
25,877 (+1%)
50,153 (-1%)

l2_block_rollup_simulation_time_in_ms
13,086
25,876 (+1%)
50,153 (-1%)

l2_block_public_tx_process_time_in_ms
11,023
23,638 (+1%)
47,917 (-1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 8 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
7,070 (+1%)
10,113 (+2%)

node_database_size_in_bytes
12,415,056
16,478,288 (+1%)

pxe_database_size_in_bytes
16,254
26,813

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Function
time_ms
bytecode_size_in_bytes

GasToken:_increase_public_balance
78.6 (-3%)
13,790

GasToken:set_portal
14.8 (+5%)
3,339

Token:constructor
110 (+7%)
23,692

FPC:constructor
70.1 (-2%)
13,592

GasToken:mint_public
60.4 (-3%)
10,158

Token:mint_public
:warning: 45.1 (-41%)
19,034

Token:assert_minter_and_mint
90.7 (-4%)
12,925

AuthRegistry:set_authorized
38.9 (+11%)
7,812

FPC:prepare_fee
116 (+5%)
15,062

Token:transfer_public
35.2 (-8%)
31,218

FPC:pay_refund
134 (+2%)
25,260

Benchmarking:increment_balance
1,330
15,267

Token:_increase_public_balance
15.0 (+2%)
15,006

FPC:pay_refund_with_shielded_rebate
164 (+1%)
26,347

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.153 (+3%)

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
256 leaves
512 leaves
1024 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.3 (-1%)
16.8
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.7
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.595 (-1%)
0.514
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
47.9 (-1%)
75.5 (-1%)
131
246
469 (-1%)

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
287
543
1,055

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.490 (-1%)
0.464 (-1%)
0.449 (-1%)
0.445
0.438 (-1%)

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
59.1 (-1%)
111 (-1%)
182 (-1%)
354
691 (-1%)

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
109
207
355
691
1,363

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.500 (-1%)
0.500
0.482 (-1%)
0.478
0.474 (-1%)

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
72.5 (-1%)
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
133
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.516 (-1%)
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
74,105
667,868

Transaction size based on fee payment method
| Metric |  |
| - |  |


Create 11ty-collected-notes

Starter blog with Collected Notes as a CMS

You want a .json file extension on your new file!

Silly me, I'm sorry 😭

Thank you!


Image garbage collection is not working on workers

For what reason Kamaji has garbage collection disabled, according to this line:
https://github.com/clastix/kamaji/blob/755cc5bacdd4b18f901c083c9878677347d28e73/internal/kubeadm/uploadconfig.go#L115
The garbaje collection for images is triggered
(see: https://github.com/kubernetes/kubernetes/issues/79929)

Also all of these zeroDuration look weird to me? Is there any reason why are they configured like so?
https://github.com/clastix/kamaji/blob/755cc5bacdd4b18f901c083c9878677347d28e73/internal/kubeadm/uploadconfig.go#L110-L125
According to kubelet configuration, they should have default values:
https://kubernetes.io/docs/reference/config-api/kubelet-config.v1beta1/

Definitely a bad choice from our side, I guess it was just a basic scaffolding since most of the time nodes are joining with a dedicated kubeadm configuration file (e.g.: Cluster API).
Wondering if you're facing this issue even tho running with Cluster API, IIRC a local configuration has precedence over the one stored in the cluster.


[WIP] adds contributor guides to the docs

Summary
This takes @bbbales2 #192 PR and adds it to the stan math docs. I broke things up a bit into separate sections and fleshed out an example based on Ben's stuff. I like the example because it's pretty much real Stan math code and I think makes it easier to see the context on how we use the special widgets etc. we have. I'd like to add another example that's a bit more complicated for something like multiply but I'll do that later. This still needs some heavy editing and I'll tag people for particular sections.
This also changes the settings in doxygen.cfg so that even if there are warnings the docs are still built. I think it's annoying that some versions of doxygen compile the docs fine while others don't. This is most entirely because of warnings like
stan/math/rev/functor/idas_integrator.hpp:63: warning: argument 'dae' from the argument list of stan::math::idas_integrator::solve has multiple @param documentation sections

Which comes from us having a lot of different specializations and doxygen having trouble working out the docs for each. So I set the WARN_AS_ERROR flag for doxygen to NO
# If the WARN_AS_ERROR tag is set to YES then doxygen will immediately stop when
# a warning is encountered.
# The default value is: NO.

WARN_AS_ERROR          = NO

Release notes
Adds docs for new contributors
Checklist

[x] Math issue #(issue number)

[x] Copyright holder: Steve Bronder
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[x] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
dependencies checks pass, (make test-math-dependencies)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

You can make the docs locally by running make doxygen

Nice nice! Yeah gimme bite size pieces and happy to add on.

I'm going to try to restructure this a lil bit tmrw. I'd like to better structure this like Eigen's docs

Question: Do we want to add which checks to run locally before submitting a PR? Also a note on clang-format and the rest?
If yes I can handle that.

Yeah that would be awesome! I think that would go under the testing section

@rok-cesnovar if you have time to write up the PR stuff that would be rad but otherwise I think this is good to go!

Will do over the weekend.

Obviously that weekend has long passed. Lets merge this.


updated python-slybot and python-dateparser with latest versions from main

As part of the SC weekly upgrade.
Is there anything else I should do @vshlapakov ?

@agusc Could you please rebase your PR (it overlaps a bit with https://github.com/scrapinghub/scrapinghub-stack-portia/pull/4)? Thanks!

@vshlapakov done!


Call OnReportBegin in ReadClient for events, and report in OnError callback in Darwin framework

Call OnReportBegin before ReadClient calls OnEventData, and report attribute/event in OnError in Darwin framework callback
Issue #18783 - Sort out interaction of OnReportBegin/OnReportEnd with subscriptions in the Darwin framework
Problem

Fixes #18783 so that Events are also properly bracketed by OnReportBegin/End (or OnError).
If OnError happens in the middle of report, Darwin framework currently doesn't do anything with the accumulated attribute or event data. This change checks if there are unreported data, and reports them.

Change overview

Combined mIsInitialReport and mSawAttributeReportsInCurrentReport into mIsReporting, in ReadClient, and added NoteReportingData right before actually reporting data, to accurately reflect when reports begin.
Added cleanup in BufferedReadCallback for when OnError happens
Added logic to Darwin framework to report accumulated attribute/event data when OnError happens.

Testing
How was this tested? (at least one bullet point required)

Tested locally with darwin-framework-tool to see that no regressions happen with normal subscription / read flow
Tested locally with darwin-framework-tool, with a modified ReadClient to simulate error in the middle of reporting, and see that attributes are indeed

/rebase


SUB Day - AI Spawns

Verify that the AI is spawning properly on the map.

Let me know if you have questions with setting it up!

I spent about an hour setting up the correct AI spawn locations, added music from broncodrome day, and attached the map to the level selection widget.


Please invite me to the GitHub Community Organization

Name
Dejan Teofilovic
Discord Username (if applicable)
Dejan
Additional Context
I first met Eddie at a local tech meetup about a year ago. He was giving a talk on open-source contributions and how they can significantly impact both personal and community growth. I was really impressed by his knowledge and passion for fostering a collaborative environment.
What I appreciate most about this community is its welcoming nature and the emphasis on mutual learning and support. Everyone seems genuinely committed to helping each other grow, and there is a strong sense of camaraderie that I haven't found in many other places. The diversity of projects and the willingness of community members to share their expertise make it a rich learning ground, which is exactly what I am looking for.
I want to join this community because I believe in the power of collaboration and continuous learning. I have seen how active participation in such communities can lead to improved skills, broader perspectives, and meaningful connections. Additionally, I am keen to contribute my own knowledge and skills to help others in the community, as I have benefited from similar support in the past. I am excited about the opportunity to be a part of and contribute to this vibrant and innovative community.

On Tue, Oct 31, 2023 at 11:32 AM Dejan Teofilovic <
@.***> wrote:

On Tue, Oct 31, 2023 at 11:31 AM github-actions[bot] <
@.***> wrote:

Closed #921 https://github.com/Design-and-Code/support/issues/921 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/Design-and-Code/support/issues/921#event-10824685327,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BC23NHNKBIRI7QELQA22PRLYCE7XZAVCNFSM6AAAAAA6YE7QASVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJQHAZDINRYGUZTENY
.
You are receiving this because you authored the thread.Message ID:
@.***>


babel-runtime

when doing npm start :
ERROR in ./src/js/modules/msg.js
Module not found: Error: Can't resolve 'babel-runtime/helpers/typeof' in '/Users/x/dev/testing/salsita/chrome-extension-skeleton/src/js/modules'
 @ ./src/js/modules/msg.js 1:0-51
 @ ./src/js/devTools.js

ERROR in ./src/js/modules/runner.js
Module not found: Error: Can't resolve 'babel-runtime/core-js/json/stringify' in '/Users/x/dev/testing/salsita/chrome-extension-skeleton/src/js/modules'
 @ ./src/js/modules/runner.js 1:0-67
 @ ./src/js/options.js

I had same problem; I fixed it adding to devDependencies:
"babel-runtime": "^6.1.4"
I also had to update to<EMAIL_ADDRESS>to make it work with<EMAIL_ADDRESS>


Error NO_PUBKEY A4B469963BF863CC when run Dockerfile

I fixed it with additional key as below ( before # Install basics ):
RUN apt-key adv --fetch-keys https://developer.download.nvidia.com/compute/cuda/repos/$distro/$arch/3bf863cc.pub
With $distro/$arch need change , ex : ubuntu1804/x86_64
Source : link

This error can be reproduced, with the following error code:

Error code and console output
$ docker build ./ -t openpcdet-docker
Sending build context to Docker daemon   5.12kB
Step 1/13 : FROM nvidia/cuda:10.2-cudnn7-devel-ubuntu18.04
10.2-cudnn7-devel-ubuntu18.04: Pulling from nvidia/cuda
11323ed2c653: Pull complete
9b0c32b3202c: Pull complete
55d4aa3df964: Pull complete
ced0e45f533f: Pull complete
a6d5f855f26c: Pull complete
532188ad0a5d: Pull complete
53b0132b34a2: Pull complete
d63f711e9949: Pull complete
776e7a7e28b2: Pull complete
69004237646f: Pull complete
Digest: sha256:8ad8e6331ba04bf26d82bad34e80c4aeb8b2366d958bd9a38fd06d74027c43d4
Status: Downloaded newer image for nvidia/cuda:10.2-cudnn7-devel-ubuntu18.04
 ---> aee6ba485fef
Step 2/13 : RUN echo 'debconf debconf/frontend select Noninteractive' | debconf-set-selections
 ---> Running in 4a0ca0038de0
Removing intermediate container 4a0ca0038de0
 ---> 9eed9600a8bc
Step 3/13 : RUN apt-get update -y     && apt-get install build-essential     && apt-get install -y apt-utils git curl ca-certificates bzip2 tree htop wget     && apt-get install -y libglib2.0-0 libsm6 libxext6 libxrender-dev bmon iotop g++ python3.7 python3.7-dev python3.7-distutils
 ---> Running in 4b43d64fa86e
Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:2 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64  InRelease [1575 B]
Err:2 https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64  InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A4B469963BF863CC
Get:3 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB]
Ign:4 https://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64  InRelease
Get:5 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 Packages [21.1 kB]
Get:6 https://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64  Release [564 B]
Get:7 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [1498 kB]
Get:8 https://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64  Release.gpg [833 B]
Get:9 https://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64  Packages [73.8 kB]
Get:10 http://security.ubuntu.com/ubuntu bionic-security/restricted amd64 Packages [909 kB]
Get:11 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [2734 kB]
Get:12 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:13 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:14 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [11.3 MB]
Get:15 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [186 kB]
Get:16 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1344 kB]
Get:17 http://archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages [13.5 kB]
Get:18 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [2272 kB]
Get:19 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [29.8 kB]
Get:20 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages [942 kB]
Get:21 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [3168 kB]
Get:22 http://archive.ubuntu.com/ubuntu bionic-backports/main amd64 Packages [12.2 kB]
Get:23 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 Packages [12.9 kB]
Reading package lists...
W: GPG error: https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64  InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A4B469963BF863CC
E: The repository 'https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64  InRelease' is not signed.
The command '/bin/sh -c apt-get update -y     && apt-get install build-essential     && apt-get install -y apt-utils git curl ca-certificates bzip2 tree htop wget     && apt-get install -y libglib2.0-0 libsm6 libxext6 libxrender-dev bmon iotop g++ python3.7 python3.7-dev python3.7-distutils' returned a non-zero code: 100

As mentioned by @tuan97anton this issue can be solved by adding the following line to the Dockerfile.
RUN apt-key adv --fetch-keys https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64/3bf863cc.pub


Crash on registration

I'm getting the following exception when trying to add an event lister for 'register' events. Any ideas?
FATAL EXCEPTION: IntentService[GcmRegistrationService] at com.oney.gcm.GcmRegistrationService.onHandleIntent(GcmRegistrationService.java:30)
Process: com.myapp, PID: 23592
android.content.res.Resources$NotFoundException: String resource ID #0x0
 at android.content.res.Resources.getText(Resources.java:321)
 at android.content.res.Resources.getString(Resources.java:407)
 at android.content.Context.getString(Context.java:377)
 at com.oney.gcm.GcmRegistrationService.onHandleIntent(GcmRegistrationService.java:31)
 at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)
 at android.os.Handler.dispatchMessage(Handler.java:102)
 at android.os.Looper.loop(Looper.java:135)
 at android.os.HandlerThread.run(HandlerThread.java:61)
Force finishing activity 1 com.myapp/.MainActivity
Tried to remove non-existent frame callback

Do you have android/app/google-services.json file?

Yes. I'm not sure how to validate that it's correct, but it is there.

Please try this solution.
Or, remove android/build and android/app/build directories and re-run.
The last solution is finding project_number in android/app/google-services.json(eg<PHONE_NUMBER>18 in TestGcm project), and hard code the projectNumber in node_modules/react-native-gcm-android/android/src/main/java/com/oney/gcm/GcmRegistrationService.java
// int resourceId = resources.getIdentifier("gcm_defaultSenderId", "string", packageName);
// String projectNumber = getString(resourceId);
String projectNumber = "309660514018";

@oney First suggested solution worked well, thanks! Closing.


New tool: Sherlock Online

I found this website running the OSiNT Tool sherlock used for finding other accounts of a person by thier username.
Link to website: https://w-e-b.site/?act=sherlock

Very useful


feat: apisixtls schema

Please answer these questions before submitting a pull request

Why submit this pull request?

[ ] Bugfix

[x] New feature provided

[ ] Improve performance

[ ] Backport patches

Related issues

Bugfix

Description

How to fix?

New feature or improvement

Describe the details and related test reports.

Backport patches

Why need to backport?

Source branch

Related commits and pull requests

Target branch

Need some test-case for jsonschema

@gxthrj e2e cases about SSL already test it.

@gxthrj e2e cases about SSL already test it.

But no error case covered.

@gxthrj e2e cases about SSL already test it.

But no error case covered.

That'd will be a huge workload, as we also lacks the cases for ApisixRoute.

https://github.com/apache/apisix-ingress-controller/issues/387 I have added an issue to track the test cases.


mysql support please?

just as the title suggests... including the drivers for mysql as an option would help me out loads. been trying to get this working for a couple weeks on and off without much luck. an out of the box solution would go miles.

upon further inspection into the root i see that you indeed have the support in the Dockerfile already declared... i'm going to keep investigating my causes. one thing i've done differently than what you've suggested is set up an external volume for /var/atlassian/crowd to a local drive. i want to be able to rebuild my docker images without having to install again every time... this might be the cause, but more to come...

I think i'm just going to wait for https://github.com/mergermarket/crowd/commit/7d21626cb56b9596dd75172a0888bb9b3263d2ce to be completed. Enough troubleshooting for one day.

Also the ip adress "<IP_ADDRESS>" looks suspicious.

Is this a Docker container? Won't work because ip adresses inside Docker change. You must use a network name.
Is this an MySQL demon on the host machine? Won't work, because by default there is no network route from inside a Docker network to the host machine.

Upon further inspection I can tell you that CROWDDB_URL and CROWDIDDB_URL do not work in the latest crowd release. You have to go through the crowd setup wizard in order to setup crowd and crowdid. Afterwards restart the container and access the crowdid context with your crowd admin account.

Thanks for taking a look:
The ip address <IP_ADDRESS> is the mysql database. it is not a docker instance. full fledged database server separate from the docker server... should be accessible by the docker image though. I have noticed that i've been forced to go through the wizard but that still doesn't explain the other issues of nothing in /var/atlassian/crowd inside the container :(
Further testing inbound...

i may have found the cause... but not the remedy yet, just a workaround:
the volume is added to the container with the root user and created on the host system as root... but the scripts inside the container run as user crowd. It's a simple user permission issue...
it looks like the uid of the user is 1000 so creating the folders on the docker host before you create the container is necessary if you want to mount a persistent volume.
To correct this, i think it might be best to add a line in the Dockerfile that validates the permissions of the CROWD_HOME and CROWD_INSTALL variables. make sure they are owned and accessible by uid:1000 (crowd).

This issue happens because you have mounted host directories with -v /config/crowd/home:/var/atlassian/crowd -v /mnt/ostium/ssl:/ssl  and would not happen if you use docker volumes.
Another fix would be if your system has a user with the user id 1000 and group id 1000. Make sure that the mounted directory has write permissions for the user and the directory must be empty. Otherwise the mount behavior of Docker will not copy the images files to the folder.
No change inside the Dockerfile will fix this issue. I could only add a check to the entrypoint that will check this issue and notify before shutting down. Not sure if that would help you.


fix setting flow as undefined

Warnings

:warning:

Source/dom/layers/Layer.js changed, but not:

📚 its docs

That's OK as long as you're refactoring.

  Generated by :no_entry_sign: dangerJS


[ Future feature request ] Add way to match geometric nth-of-type patterns

Such as 2n + 1, kn + a , etc
This ought to not be standard behaviour as it may interfere with people's intent by overfitting and assuming that someone's random selection of examples was actually specifying a geometric progression
It ought to be an option that can be surfaced once someone fails to map their intended pattern using the standard method

Closing because it's for the future


feat(DDI-1239): Added docs for icon component

Added storybook page for icon component
Design: https://www.figma.com/file/AedpWLVFBdEwWDRBUEgwUJ/Icon-layout?t=Ti7SFT43hq5Z99JX-0

:tada: This PR is included in version 2.0.0-alpha.14 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.0.0-alpha.119 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.159 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.21 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Problem creating a new task

Hi!!
I have a problem when I try to create a new task.
When I catch the error, the message is "(19,8):LogonType". In fact, I try to create the new task into setup project in VS 2010.
I'm not sure if the type of project is the problem, because I have the same code in windowsform project  and the task is created correctly.
Hope you can help me.
Thanks
Originally posted: 2013-05-29T16:46:10

What environment are you in? If this is an ASP.NET instance, please search the discussions for how to set permissions and accounts correctly within that environment.
Originally posted: 2013-05-31T09:40:20


Add support for ~username syntax (fix #1033)

This is my first time writing Go, so please critique the style and implementation. But as far as my testing goes, this should solve #1033.
I've only tested this on Linux, but I see no reason why it wouldn't also work with other systems, as long as os/user handles it properly.

This almost works; there's just one fix that needs to be done. Let's take a look at util.go:353, the return statement:
return strings.Replace(path, "~", home, 1)

Let's say in micro I do > open ~www-data/html/index.html. For this, we'll say the www-data service account has a home of /var/www. The changes you made work; ~ is replaced with /var/www, but now we have a munged path of /var/wwwwww-data/html/index.html.
This is a pretty easy fix, though: just changed the "~" in line 353 to homeString so it replaces both ~ and ~otheruser patterns.

Also, while I'm not a Go developer myself, I can provide some feedback based on what I've seen!

From my understanding, the best practice is to run go fmt on a piece of code to unify the formatting of it.
For clarity, I would change foo to something a bit clearer, like homeUser or usr (if neither of those are reserved words)
There's a couple of things that can be cleaned up a bit. Both err declarations could be put right underneath the declaration for the user object. Since userString is only used in one place, you could remove the declaration of it and change user.Lookup(userString) to user.Lookup(homeString[1:]), although that's being a touch pedantic on my end (and it helps that userString helps to clarify what that substring is without comment).

I think it looks fine myself, although I'm mostly a C and Ruby developer, so take my words with however much salt you'd like. :p

I've made that fix, and also replaced the non-descriptive variable names.
I'm surprised I allowed myself to make a pull request for code with foo left in it. In my defense, I wrote the commit while in class.
I will take a look at your other suggestions now, and see if I can't clean it up a little.

No big deal; I've done that before when getting code out of my brain and onto paper into a file.
The only other thing that I can think of is what I pointed out before with the err declarations. I do a lot of embedded work, so refactoring user.Lookup(userString) is solely because I'm thinking in an embedded mindset where memory can be pretty tight.

Alright, with all that taken care of, this code should be good. Go is fairly nice to work with from a first time user's perspective. I mean, anything that uses slices for arrays makes me happy. :)

This crashes if there is an error looking up the user because it doesn't return when an error occurs. I'll merge this and then fix it on master.


Refactor certificate actions

Fixes #581
- What I did
Refreshcerts action now raises a PR rather than committing directly to trunk (which doesn't work due to branch protection rules)
Build for virtualenv:vip moved to at_server action to run when we do a prod release
- How to verify it
Will need to be merged before it can be properly tested :/
- Description for the changelog
Refactor certificate actions

Closing and reopening to see if that triggers status check actions into life.


DRILL-4275: Refactor e/pstore interfaces and their factories to provide a unified mechanism to access stores

The main changes are the following:
Remove EStore and EStoreProvider interfaces.
Rename PStore to Store, PStoreProvider to StoreProvider
Extend Store with getMode():StoreMode that returns store persistence level
Ensure StoreProvider.getStore(mode) acts like a factory.
Ensure Store implementations throw StoreException in case of failures and handle StoreExceptions
All other files contain very tiny, local, satellite changes like variable name updates for name consistency, exception handling et cedera.

I don't think we should change the PStore API without some level of discussion since it was designed as a public API. Can you share the driving requirements that pushed you to propose these changes? I also think renaming PStore to PersistentStore could cause user confusion since PersistentStore is very generic and could be mistaken for some place where people can store tables.

I took the API somewhat Drill internal but you are right about discussing this in the public list first. This patch -as the numbers above check out- is more of a clean-up than an extension. My plan was to discuss possible changes to API going forward once this clean-up patch made its way to master. Here is the rationale: I spent quite a while trying to understand the current design, event flow in the API in an attempt to find a way for subscribing to store events. Especially being notified when an ephemeral node dies just like what Zookeeper watches offer. I got confused multiple times with E/PStore and E/PStoreProvider distinction at interface level as it seems redundant. That's how the idea of this clean-up patch rolled out.
As for naming, I am open for non-abbreviated alternates. I would invite developers relying on this interface to read the documentation first. To this end, I will go ahead and extend documentation with possible warning areas.
Please let me know if you want me to address specific issues with this patch.

You want to do a hangout to discuss the concept of EStores and watches and the relationship with the ClusterCoordinator interface. We're currently actively in the process of implementing a new EStore/PStore pair and I'd like to figure out the best way to improve the interface without major disruption to the work we're doing.

Cool. Let's sync up on tomorrow's weekly hangout. Let me know if that does not work for you.

Let's do a separate hangout. This seems to deep/specific to cover in a
large group.
On Jan 18, 2016 9:51 AM, "Hanifi Gunes"<EMAIL_ADDRESS>wrote:

Cool. Let's sync up on tomorrow's weekly hangout. Let me know if that does
not work for you.
—
Reply to this email directly or view it on GitHub
https://github.com/apache/drill/pull/325#issuecomment-172604790.

How about anytime tomorrow from 10am till noon?

I have created the following doodle to schedule this.


Adding support for Windows machines

@randomstuart correct, that is a restriction. I needed to make that happen and didn't have an opportunity to do that yet.

Hi @benjaminprojas, thanks for the response its much appreciated.
Do you think that you will be able to sort this anytime soon as I'm in a real pickle as I need to launch a website but i cannot access it for final approval?

I don't think this will be fixed anytime soon unfortunately. My work schedule is very full at the moment.


[FLINK-25369][table] CatalogManager provide right tables or views in given catalog database

What is the purpose of the change
CatalogManager provide right tables or views in given catalog database name
Brief change log

put the given catalog or database name in the function args, instead of current name

Verifying this change
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? no

@flinkbot run azure

@flinkbot run azure

@RocMarshal CI result has been success now. Thanks!

@Airblader Is there anything else to do with this? please have a look, Thanks!


EGS: Some games don't work

The Alto Collection doesn't start through the steam shortcut & default compat tool, but by switching to using wine directly, it runs (x)
Watch Dogs 2 doesn't work at all (x)

What works:

God's Trigger seems to work, but more-or-less freezes completely as soon as the steam controller is used (also seems to freeze the system, or maybe that's just my 4 Gigs of RAM)
Enter the gungeon, controller support doesn't work
Shadowrun Hong Kong, since the game doesn't support controllers, everything seems to work (didn't check the other games in the series)
Wilmot's Warehouse, controller support doesn't work (x)

I've marked the ones I care about with (x)

There isn't anything GamerOS can do about some games not working.
I have also noticed that gamepads are not working either. I expect this to be fixed with a new version of Proton at some point.

I tried installing a few different versions of Proton GE and although I could launch Steam games I couldn't launch any EGS games with it. When launching it just freezes the system.


Add League Endpoints

Acceptance Criteria

All tests should pass.
Add endpoints for league creation, updates, and information retrieval.
Understandable endpoint documentation within the API Docs.

Closing in favor for #10.


Remove unused APIs, DAO, routes & controllers

Codecov Report

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

@@          Coverage Diff           @@
##           master   #1335   +/-   ##
======================================
  Coverage    54.5%   54.5%
======================================
  Files         182     182
  Lines        3772    3772
  Branches      834     834
======================================
  Hits         2056    2056
  Misses       1716    1716

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 bc8ce05...7f3ceff. Read the comment docs.

Coverage increased (+0.3%) to 27.84% when pulling 7f3ceffb189ffadb76a731dd3a53fe7d46eeec7a on mars-lan:master into bc8ce0508a4be3c201da17f0078a019e68d31ef4 on linkedin:master.

@theseyi  please verify the removed code is indeed not needed by the UI.


gboard isnt working you should improve your appp :D

gboard isnt working you should improve your appp :D

Hey, thanks for pointing out this mistake. As described in #3, the problem is not in my code. It's a problem with Google's GBoard that I can't do much about, unfortunately.
For me, the keyboard still works if you swipe back once and then click on "New Chat" again. Or you can use a different keyboard, such as the Samsung Keyboard.
P.S. A more detailed error description would be useful too... ;)

Jannis Zahn @.***>, 16 Eyl 2023 Cmt, 09:34 tarihinde
şunu yazdı:

Closed #4 https://github.com/DevEmperor/WristAssist/issues/4 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/DevEmperor/WristAssist/issues/4#event-10389113230,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AS7H2GZ4RXCKT4FQ2IDHC6TX2VB6FANCNFSM6AAAAAA42FG7CM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Actually samsung keyboard is working but the voice thing only support english i want to use turkish

Okay, I'll do some more research and see what I can do about that bug.


Temporary 'AccessDenied: Missing credentials in config' error

Hi,
we're using the fanout function to push Kinesis Streams' data from one AWS account to another. Looking at the Streams' data throughput in both accounts, it seems to be working correctly. However, when we enabled a Cloud Watch alarm to capture the function's invocation errors, here's what we get periodically:

This happens several times a day and seems as a temporary glitch, but we haven't yet had the opportunity to validate if there is any data loss occurring in the process.
Any information you could provide would be appreciated.
Thanks,

Do you have any information o how often that error occurs? We regularly refresh the credentials to connect to the outputs, and that may be linked.
Could you provide, for this function:

when the first entry in that log stream appeared
when the error occurred (8:41)
if the error occurred later (and if yes when)
if there is another log stream where this happened, the same information

Thanks,
Julien

Hi Julien,
yes, this seems to be connected to our issue. Further details:
The time of  the first entry to the log group in question is 7:41. The error didn't occur later, but we deactivated the triggers for the function at 4 pm, so we didn't monitor it after that time. From 8:41:33 to 8:41:44, the function failed and retried for 5 times altogether, at 8:41:44 succeeded to process that RequestId.
Here are the occurrences of the error for 2017/02/03:

Here's the info on another log stream from that day where this happened 2 times:

time of first entry in the log group: 00:12:17
time of first error: 01:12:06 (failed and retried 5 times, succeeded at 01:12:15)
time of second error: 02:12:06 (failed and retried 3 times, succeeded at 02:12:12)

Thanks,
Mirna

Hi Myrna, in the lib/services.js file, could you try a couple changes?

line 43, change the value of the stsSessionDuration variable to 600 (from 3600), that will force credentials refresh every 10 minutes
line 138, change the value 5 to 30 in (stsSessionDuration - 5) to have it as (stsSessionDuration - 30), that will force a refresh 30 seconds before expiration

Could you make these changes and update the defined function and get back to me?
Julien

Doing that, I got a validation error in the Lambda log saying "Member must have value greater than or equal to 900", so I updated the stsSessionDuration to 900 and left it running. Will keep monitoring it and post an update on the current situation.
Thanks,
Mirna

Update: the modified function has been running smoothly for the past 2 days.
Thanks a lot for your help and fast response, Julien!


[java-snapshot] should remove label if PR changes from regular release to snapshot

https://github.com/googleapis/java-bigtable/pull/1215 was originally opened as a regular release, but changed to a snapshot. Automation then tried to release the snapshot and failed.

Labels are not updated at all during PR update.

This is extremely rare and we probably don't actually need this.


#479 - More updates to match checkstyle rules - Added comments to

@param; Limited all lines 100 characters; Turned on ability to add
comments that turn off formatter
This gets the number of warnings down to 198
$ find -type f -name checkstyle-results-java.xml | xargs grep warning | wc -l
198

Warnings are now down to 159

+1


dev server load time takes awhile

runing dev server takes awhile to load, unsure if this is result of lucia session, but a normal sveltekit dev server is fast

Yes it’s because many packages are loading and it optimizes the code on loading. Production code is much faster though. After it fully loads it usually doesn’t take long after you perform updates while it’s running.


[Codegen] extract emitDouble from parsers modules to shared parsers-primitives

Summary

Part of https://github.com/facebook/react-native/issues/34872
This PR extracts the content of the case 'Double' (Flow, TypeScript) into a single emitDouble function in the parsers-primitives.js file. Use the new function in the parsers.
Changelog

[Internal] [Changed] - Extract contents of the case 'Double' into a single emitDouble function inside parsers-primitives
Test Plan

I tested using jest and flow commands.

Rebased the branch because of conflicts


Simplify native interop?

Given the following code:
      .flatMap(({src, dst}) => _(new Promise((resolve, reject) => fs
          .createReadStream(src)
          .on('error', err => reject(err))
          .pipe(request.put(dst))
          .on('end', () => resolve({src, dst}))
          .on('error', err => reject(err)))))
     .parallel(8)
     .last()
     .forEach(() => console.log("DONE"))

Which is quite ugly. Is there a better way to do it? I.e. can we somehow wrap a writeable stream in a way that we can use through and keep the highland error/end handling?
Something like?
  .flatMap(({src, dst}) => _()
    .concat(fs.createReadStream(src)))
    .through(fromWritable(request.put(dst)))
    .last())
  .parallel(8)
  .last()
  .forEach(() => console.log("DONE"))

You can wrap all of the error handling inside a function and give it to through. Here's an implementation that adapts the logic for through streams to writable streams.
function pipeToWritable(writable) {
    return function (stream) {
        return _(function (push, next) {
            stream
                .on('error', push)
                .pipe(writable)
                .on('error', push)
                .on('end', push.bind(this, null, _.nil));
        });
    });
}

You can use it like this
.flatMap({src, dst}) =>
    _(fs.createReadStream(src))
        .through(pipeToWritable(request.put(dst))))
.parallel(8)
...

Perfect!


Output parameter not set when calling stored procedure

After upgrading to version 4.0.4 from 3, output parameter is not being set when executing stored procedure. Value of parameter is null in request.parameters.
Main result records of stored procedure are returned.

As described in migration guide, output collection was moved from request to the result object.


wcFlightMaster sometime only works on reload

After I disable wcFlightMaster in TaxiMap. If I enable wcFlightMaster again. wcFlightMaster won't work. @cksky

And I also suggest put wcFlightMaster into permanent feature. No need to switch on/off


Adding an interval when setting a trial's paramters on trial start

There is already a neat way to set a trial's parameters dynamically using the on_start function (https://www.jspsych.org/overview/trial/#the-on_start-event)
I would like to be able to set a trial's parameters, say the choices for a html-keyboard-response trial, but with a delay. So, for instance, my trial should start with the participant not being able to click anything but after a small delay, they should be able to click specified buttons. In other words, this SHOULD work (but it DOES NOT):
var mytrial = {
    type: 'html-keyboard-response',
    stimulus: 'Cannot click anything for 3 seconds - this should change after 3s but it does not',
    choices: jsPsych.NO_KEYS,
    on_start: function(trial) {
        jsPsych.pluginAPI.setTimeout(function() {
            trial.stimulus = 'Click stuff now!'
            trial.choices = jsPsych.ALL_KEYS
            }, 3000)
    }
}

Edit: Note that I am aware of the minimum_valid_rt argument when initializing the experiment (see here) but I want a trial-specific solution, as the minimum_valid_rt would not apply across all trials in the same way.
Any advice is appreciated!

This is not really feasible given the current implementation of plugins. It would require some kind of re-render event and the plugin architecture isn't designed with this in mind. And it would be a major overhaul to add this kind of support.
This won't generalize to all instances where this feature could be used, but you could always chain two plugins together to create the feel of a single trial.
var mytrial = {
    type: 'html-keyboard-response',
    stimulus: 'Cannot click anything for 3 seconds - this should change after 3s but it does not',
    choices: jsPsych.NO_KEYS,
    trial_duration: 3000
}

var mytrial2 = {
    type: 'html-keyboard-response',
    stimulus: 'Click stuff now!',
    choices: jsPsych.ALL_KEYS
}


pypy support

Hi,
Which versions of PyPy are supported for 'azure>=2.0.0rc6' module ?
Thanks -Madhu

Hi @madhugilla
Our current Travis tests are running against pypy 5.4.
If you think we should update this to a newer version, please let me know which one you suggest.
@brettcannon if you have a suggestion here.

I got tests to work against pypy3.5 5.8.0. This is plugged on Travis.
Thanks,


no more Security option on the dataset?

when right-clicking on the dataset, there is no Security option (today - I'm sure there must have been in the past but not now)
I was able to find the Security option only by navigating from the report to the Related objects, then "..." on the dataset

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

ID: d5505062-94f3-e15d-a52f-ce1ac7f8cb69
Version Independent ID: 34076b73-0ded-2111-ed44-2a31e07deb53
Content: Row-level security (RLS) with Power BI - Power BI
Content Source: powerbi-docs/enterprise/service-admin-rls.md
Service: powerbi
Sub-service: powerbi-admin
GitHub Login: @paulinbar
Microsoft Alias: painbar

Thanks for your comment, @aldonetti. This issue has been assigned to the doc author for review.

and sorry - I also noticed that if you access from the Data Hub you don't see the Security option (as described above). Instead if one goes to the Workspace, from there the Security option is visible

Hi @aldonetti, thanks for your comment. Yes, you are right - its appearance is inconsistent. For instance, I do not see the "security" option in the data hub, but when I am in the workspace list view, and display the dataset options there, I do see the option. Of course it also depends on your permissions, but for the same dataset, you'd expect it to be consistent. I have seen this before and have raised the issue, and I think I was told that it's a known issue that they are planning on addressing. In any event I have sent an inquiry to the data hub person for an update and I'll let you know what I hear.

I see you were investigating too! :)


Email functionality is missing.

There is a functionality that is missing where applicants are not notified when their job status changes to Accepted or Rejected.

Email functionality has been added. Now applicants are notified via email when their job status changes.


Modified layout capabilities when display layout is successfully changed.

Fixes #53.  Modified layout capabilities when display layout is successfully changed.
Signed-off-by: Mike Burke<EMAIL_ADDRESS>

Need to investigate any side-effects of making this change.  SdlProxyBase is a large, complicated beast and all of these mutable variables are returned directly (in SdlProxyALM), meaning they could be modified in any part of the system.  Assuming no other parts of the system are messing with these variables, this PR should be good to go.

Feature requests should be merged into develop, not master.  Will create a new PR for this.


Key word arguments breaks pmap

This code
def f(index1, index2):
  return np.arange(36).reshape(6, 6)[index1, index2]
g = jax.jit(jax.pmap(f))
g(index1=onp.asarray([1]), index2=onp.asarray([2]))

Causes this error.
google3/third_party/py/jax/api.py in _pmap_axis_size(args)
    724     return next(_axis_size(leaf) for arg in args for leaf in tree_leaves(arg))
    725   except StopIteration:
--> 726     raise ValueError("pmap requires a leading axis to map over.")
    727
    728 def _axis_size(x):

ValueError: pmap requires a leading axis to map over.

Whereas the exact same code without the kwargs works correctly.

def f(index1, index2):
  return np.arange(36).reshape(6, 6)[index1, index2]
g = jax.jit(jax.pmap(f))
g(onp.asarray([1]), onp.asarray([2]))

Which nicely prints
DeviceArray([8], dtype=int32)

as expected.

I think the underlying issue is that we only look at args to determine the axis size, even though once the axis size is determined we handle kwargs correctly.


[BUG] TC-DA-1.7 PAI's AKID is wrong and PAA and signature is invalid

Reproduction steps

Tested on TE1.1 commit
At step 4 - PAI's AKID matches a PAA and signature is valid fails
Logs
- DUT: esp32.txt
- TH: th.txt

Bug prevalence
EveryTime
GitHub hash of the SDK that was being used
7e69c66bb44c91fe0b9bed7c7b8d272d3208c8dd
Platform
esp32
Platform Version(s)
No response
Anything else?
No response

@PSONALl you should not be using the SDK default PAI for this test. you will need to generate PAA/PAI and use those on your product


See next Screen, before slide in

Behaviour on iOS real device - it not happens on the emulator:
When i tap a link (view A), it shows directly the next view ( view B). Than the transitions starts and slides B out and slides B in - Finally it shows view B.
However, during the transition the starting view A is not visible.
Have someone this problem also?

+1 same here, ionic with crosswalk, same issue

+1
I just started seeing this issue (iOS simulator AND device) when i updated Ionic from 1.2.1 to the latest nightly 1.2.4 build. I was not seeing it before.

To expand a bit on my previous statement, it looks like changes made specifically in Ionic 1.2.4-nightly-2811 causes this issue (1.2.4-nightly-2775 works fine). After digging in a bit, I have found that removing the following line in ionic-angular.js fixes the issue...
css.opacity = opacity;

Not sure what that means yet for any potential fix to the ionic-native-transitions code though.

I had the same issue and debugged it a little bit. I found a solution which is to add a timeout to the state change in the stateGo() function in the ionic.native-transitions(.min).js which leads to it being run as the last function. The following code works on both iOS and Android devices.
`function stateGo() {
var state = arguments.length <= 0 || arguments[0] === undefined ? null : arguments[0];
var stateParams = arguments.length <= 1 || arguments[1] === undefined ? {} : arguments[1];
var transitionOptions = arguments.length <= 2 || arguments[2] === undefined ? null : arguments[2];
var stateOptions = arguments.length <= 3 || arguments[3] === undefined ? {} : arguments[3];
            if (!state) {
                $log.debug('[native transition] cannot change state without a state...');
                return;
            }
            unregisterToStateChangeStartEvent();
						transition(transitionOptions);
						if (ionic.Platform.isIOS()) {
	            $timeout(function() {
								$state.go(state, stateParams, stateOptions);
							});
						} else {
							$state.go(state, stateParams, stateOptions);
						}
        }`

I decided to add the check for an iOS device and run the timeout only in that case because it was only occurring in iOS devices and the timeout perhaps made Android devices flicker a little on the transition (I could be paranoid and this not really even occurring, or is due to large images on the content on my app).

I had the same issue and debugged it a little bit. I found a solution which is to add a timeout to the state change in the stateGo() function in the ionic.native-transitions(.min).js which leads to it being run as the last function. The following code works on both iOS and Android devices.
function stateGo() {
  var state = arguments.length <= 0 || arguments[0] === undefined ? null : arguments[0];
  var stateParams = arguments.length <= 1 || arguments[1] === undefined ? {} : arguments[1];
  var transitionOptions = arguments.length <= 2 || arguments[2] === undefined ? null : arguments[2];
  var stateOptions = arguments.length <= 3 || arguments[3] === undefined ? {} : arguments[3];

  if (!state) {
    $log.debug('[native transition] cannot change state without a state...');
    return;
  }
  unregisterToStateChangeStartEvent();
	transition(transitionOptions);
	if (ionic.Platform.isIOS()) {
    $timeout(function() {
			$state.go(state, stateParams, stateOptions);
		});
	} else {
		$state.go(state, stateParams, stateOptions);
	}
}

I decided to add the check for an iOS device and run the timeout only in that case because it was only occurring in iOS devices and the timeout perhaps made Android devices flicker a little on the transition (I could be paranoid and this not really even occurring, or is due to large images on the content on my app).
Same fix probably also works in the case that you are using locationurl instead in which case you just set timeout to the "$location.url(url);" function.
Not sure if this would be the final solution for this problem but it works for now.

My header title and back buttons etc don't animate anymore after fixing this with a $timeout. I'm using fixedPixelsTop but of course the title and header buttons just appear after the animation is over.
Any idea on how to use fixedPixelsTop but still take advantage of header elements animation?

This is what fixed it for me:
https://github.com/shprink/ionic-native-transitions/issues/97#issuecomment-220991408
iosdelay = -1

Please help me.
Transition A to B using.
It shows B first and transition A to B
How to solve this problem.


chore: Remove Alessandro and Rafaela from IC rotation who are no longer with konflux program.

Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Issue ticket number and link
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:

[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

Superseded by https://github.com/redhat-appstudio/e2e-tests/pull/1046/files


Source from esm

This addresses #8 by importing cheerio from esm.sh which includes cheerio's own .d.ts files, allowing type checks to work. We no longer need to include types.ts separately.
Verified that:

Type for load function is loaded correctly on IDE
Test passing

Notes
cheerio prior to v1.0.0 did not include .d.ts files and required types from DefinitelyTyped. From v1.0.0 onwards, .d.ts files are included out-of-the-box.

hello, very sorry for the delay, this coincided with my vacation and i didn't check my emails until now; is this the way to get it to work?

@Bestulo
Hi, yes this PR should get it to work.
+++
Do take note that, cheerio from v1.0.0 onwards can be imported in a deno app directly with import * as cheerio from "https://esm.sh/cheerio" without this deno-cheerio wrapper. Not sure if we should deprecate this repo or perhaps mention in the README that this wrapper is no longer necessary.

Hmm, I will add this clarification you mention at the top of the readme. I do think this seems deprecated then if that's the case.


gpio_signal_buffering parastic extraction fail

script used to extract:
#!/bin/env bash

set -uex

if [[ $PDK == "sky130A" ]] ; then
    fd_cells_lef=${PDK_ROOT}/${PDK}/libs.ref/sky130_fd_sc_hd/lef/sky130_fd_sc_hd.lef
    ef_cells_lef=${PDK_ROOT}/${PDK}/libs.ref/sky130_fd_sc_hd/lef/sky130_ef_sc_hd.lef
    tech_lef=${PDK_ROOT}/${PDK}/libs.ref/sky130_fd_sc_hd/techlef/sky130_fd_sc_hd__nom.tlef
    fd_io_lef=${PDK_ROOT}/${PDK}/libs.ref/sky130_fd_io/lef/sky130_fd_io.lef
    ef_io_lef=${PDK_ROOT}/${PDK}/libs.ref/sky130_fd_io/lef/sky130_ef_io.lef
    rcx_rules_file=${PDK_ROOT}/${PDK}/libs.tech/sky130_fd_sc_hd/openlane/rules.openrcx.sky130A.nom.calibre
    macros_lef="[glob ./lef/*.lef]"
fi

cmd="
read_lef $tech_lef
read_lef $fd_cells_lef
read_lef $ef_cells_lef
read_lef $fd_io_lef
read_lef $ef_io_lef
foreach lef "$macros_lef" { read_lef \$lef; }
read_def $1
define_process_corner -ext_model_index 0 X
extract_parasitics \
    -ext_model_file $rcx_rules_file \
    -lef_res
write_spef $1.spef
"

openroad -no_init -no_splash <<EOF
$cmd
EOF

error:
openroad> read_def ./def/gpio_signal_buffering.def
[INFO ODB-0127] Reading DEF file: ./def/gpio_signal_buffering.def
[INFO ODB-0128] Design: gpio_signal_buffering
[WARNING ODB-0293] TECHNOLOGY is ignored
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_28/X, currently on layer li1 at (3381775, 3615625), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_29/X, currently on layer li1 at (3384835, 3618855), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_41/X, currently on layer li1 at (3381775, 3627585), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_59/A, currently on layer li1 at (752525, 215935), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_37/X, currently on layer li1 at (3384835, 2236775), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_171/X, currently on layer li1 at (206220, 3010255), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_69/A, currently on layer li1 at (722625, 215935), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_58/A, currently on layer li1 at (747895, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_26/X, currently on layer li1 at (3381775, 3609645), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_183/X, currently on layer li1 at (206095, 4452365), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_93/A, currently on layer li1 at (2165095, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_79/A, currently on layer li1 at (688095, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_68/A, currently on layer li1 at (717995, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_57/A, currently on layer li1 at (758505, 215935), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_169/X, currently on layer li1 at (206220, 3016235), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_179/X, currently on layer li1 at (206220, 2986335), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_67/A, currently on layer li1 at (723975, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_0/X, currently on layer li1 at (206280, 1752250), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_66/A, currently on layer li1 at (728605, 215935), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_55/A, currently on layer li1 at (764485, 215935), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_32/X, currently on layer li1 at (3381775, 3633565), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_33/X, currently on layer li1 at (3384835, 3636795), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_159/X, currently on layer li1 at (206220, 3046135), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_177/X, currently on layer li1 at (206220, 2992315), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_186/X, currently on layer li1 at (206095, 4428445), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_95/A, currently on layer li1 at (2171075, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_76/A, currently on layer li1 at (694075, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_65/A, currently on layer li1 at (734585, 215935), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_54/A, currently on layer li1 at (759855, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_10/A, currently on layer li1 at (2088115, 4986510), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_165/X, currently on layer li1 at (206220, 3028195), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_167/X, currently on layer li1 at (206220, 3022215), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_64/A, currently on layer li1 at (729955, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_30/X, currently on layer li1 at (3381775, 3621605), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_31/X, currently on layer li1 at (3384835, 3624835), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_175/X, currently on layer li1 at (206220, 2998295), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_188/X, currently on layer li1 at (206095, 4434425), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_96/A, currently on layer li1 at (2177055, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_74/A, currently on layer li1 at (700055, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_63/A, currently on layer li1 at (740565, 215935), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_84/A, currently on layer li1 at (776445, 215935), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_62/A, currently on layer li1 at (735935, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_40/X, currently on layer li1 at (3384835, 3630815), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_163/X, currently on layer li1 at (206220, 3034175), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_172/X, currently on layer li1 at (206220, 3004275), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_189/X, currently on layer li1 at (206095, 4440405), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_97/A, currently on layer li1 at (2183035, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_72/A, currently on layer li1 at (706035, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_61/A, currently on layer li1 at (746545, 215935), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_43/A, currently on layer li1 at (847765, 4984885), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_89/A, currently on layer li1 at (2153135, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_82/A, currently on layer li1 at (676135, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_71/A, currently on layer li1 at (716645, 215935), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_60/A, currently on layer li1 at (741915, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_850_260_hv in net sky130_fd_sc_hd__buf_8_181/X, currently on layer li1 at (206095, 4446385), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_70/A, currently on layer li1 at (712015, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_44/A, currently on layer li1 at (841785, 4984885), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_90/A, currently on layer li1 at (2159115, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_80/A, currently on layer li1 at (682115, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_45/A, currently on layer li1 at (835805, 4984885), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_9/A, currently on layer li1 at (794385, 215935), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_8/A, currently on layer li1 at (793885, 212875), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_7/A, currently on layer li1 at (788405, 215935), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_5/A, currently on layer li1 at (782425, 215935), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_3/A, currently on layer li1 at (770465, 215935), cannot determine exit layer of path
[WARNING ODB-0110] error: invalid VIA layers in via_1090_260_hv in net sky130_fd_sc_hd__buf_8_1/A, currently on layer li1 at (674785, 215935), cannot determine exit layer of path
[WARNING ODB-0149] DEF parser returns an error!

this was ran after removing the blockages section in gpio_signal_buffering which cause a syntax error.

magic version 8.3.337 fixes the invalid via layers.

gpio_signal_buffering is not being used anymore.

I see above that "magic version 8.3.337 fixes the invalid via layers" and "gpio_signal_buffering is not being used anymore."  I'm going to close this ticket because of that and the fact this hasn't been addressed in 18 months.  Please reopen if it is still an issue.


Beginner recursion question - why does this behave this way?

//When written like this, the function allows you to calculate a power function.
function power(base, exponent) {
if (exponent == 0)
return 1;
else
return base * power(base, exponent-1);
}
console.log(power(3, 3));
//27
//When written like this, the maximum call stack is exceeded
function power(base, exponent) {
if (exponent == 0)
return 1;
else
return base * power(base, exponent);
}
console.log(power(3, 3));
//RangeError: Maximum call stack size exceeded
Can someone break down the line by line of what's going on here?

This doesn't seem to have anything to do with node-horseman.


System Proxy Auto-use Issue in wry After webkit2gtk Upgrade from 4.0 to 4.1

Describe the bug

In this issue, I discovered that when using Ubuntu, Tauri v2 cannot automatically use the system proxy, while Tauri v1 can.
Then I noticed that Tauri v1 uses wry v0.24.11, which is significantly behind Tauri v2.
Through my testing, I found that the next version after v0.24.11, v0.25.0, already has the issue where it cannot automatically use the system proxy. The main update in v0.25.0 was the upgrade of webkit2gtk-rs from 0.18.2 to 0.19.1, which caused webkit2gtk to upgrade from 4.0 to 4.1.
It is likely that this issue with automatically using the system proxy was caused by the upgrade from webkit2gtk 4.0 to 4.1.

I noticed that the latest wry already supports manually setting a proxy.
This feature is not supported in webkit2gtk4.0 but is available in 4.1.
After testing, I confirmed that the manual proxy setting feature in latest wry works properly.
However, latest wry can not automatically use the system proxy, it either requires users to manually specify the proxy or does not use any proxy at all.
The software I am developing relies on this automatic proxy feature.
Steps To Reproduce
To reproduce this issue on Ubuntu 22.04, follow these steps:

Create a new project:

cargo new wry-proxy-issue

Modify Cargo.toml:

[package]
name = "wry-proxy-issue"
version = "0.1.0"
edition = "2021"

[dependencies]
wry = "=0.25.0"

Modify main.rs:

fn main() -> Result<(), Box<dyn std::error::Error>> {
    use wry::{
        application::{
            event::{Event, StartCause, WindowEvent},
            event_loop::{ControlFlow, EventLoop},
            window::WindowBuilder,
        },
        webview::WebViewBuilder,
    };

    let event_loop = EventLoop::new();
    let window = WindowBuilder::new()
        .with_title("Proxy Test")
        .build(&event_loop)?;

    let _webview = WebViewBuilder::new(window)?
        .with_url("https://tauri.app/")?
        .build()?;

    event_loop.run(move |event, _, control_flow| {
        *control_flow = ControlFlow::Wait;

        match event {
            Event::NewEvents(StartCause::Init) => println!("Wry has started!"),
            Event::WindowEvent {
                event: WindowEvent::CloseRequested,
                ..
            } => *control_flow = ControlFlow::Exit,
            _ => (),
        }
    });
}

Set up a system proxy(in my case, I used http://<IP_ADDRESS>:7890).

Run the project:

cargo run

You should see an error in the webview:

If you downgrade to wry = "=0.24.11" in Cargo.toml, the issue does not occur, and the proxy works as expected.
This issue persists in the latest version (wry 0.45.0) as well.
To reproduce this issue in the latest wry is basically the same as the steps above, except that the contents of main.rs and Cargo.toml are different.
Modify Cargo.toml:
[package]
name = "wry-proxy-issue"
version = "0.1.0"
edition = "2021"

[dependencies]
tao = "0.30.3"
wry = "0.45.0"

Modify main.rs:
use tao::event::{Event, StartCause, WindowEvent};
use tao::event_loop::{ControlFlow, EventLoop};
use tao::window::WindowBuilder;
use wry::WebViewBuilder;

fn main() -> Result<(), Box<dyn std::error::Error>> {
    let event_loop = EventLoop::new();
    let window = WindowBuilder::new()
        .with_title("Proxy Test")
        .build(&event_loop)?;

    let builder = {
        use tao::platform::unix::WindowExtUnix;
        use wry::WebViewBuilderExtUnix;
        let vbox = window.default_vbox().unwrap();
        WebViewBuilder::new_gtk(vbox)
    };

    let _webview = builder
        .with_url("https://tauri.app/")
        .build()?;

    event_loop.run(move |event, _, control_flow| {
        *control_flow = ControlFlow::Wait;

        match event {
            Event::NewEvents(StartCause::Init) => println!("Wry has started!"),
            Event::WindowEvent {
                event: WindowEvent::CloseRequested,
                ..
            } => *control_flow = ControlFlow::Exit,
            _ => (),
        }
    });
}

After running it you will see the same error as above in the webview.
And to resolve this in latest wry is very simple.
Just set the proxy manually. Change the code in main.rs to the following:
use tao::event::{Event, StartCause, WindowEvent};
use tao::event_loop::{ControlFlow, EventLoop};
use tao::window::WindowBuilder;
use wry::{ProxyConfig, ProxyEndpoint, WebViewBuilder};

fn main() -> Result<(), Box<dyn std::error::Error>> {
    let event_loop = EventLoop::new();
    let window = WindowBuilder::new()
        .with_title("Proxy Test")
        .build(&event_loop)?;

    let builder = {
        use tao::platform::unix::WindowExtUnix;
        use wry::WebViewBuilderExtUnix;
        let vbox = window.default_vbox().unwrap();
        WebViewBuilder::new_gtk(vbox)
    };

    let http_proxy = ProxyConfig::Http(ProxyEndpoint {
        host: "<IP_ADDRESS>".to_string(),
        port: "7890".to_string(),
    });

    let _webview = builder
        .with_proxy_config(http_proxy)
        .with_url("https://tauri.app/")
        .build()?;

    event_loop.run(move |event, _, control_flow| {
        *control_flow = ControlFlow::Wait;

        match event {
            Event::NewEvents(StartCause::Init) => println!("Wry has started!"),
            Event::WindowEvent {
                event: WindowEvent::CloseRequested,
                ..
            } => *control_flow = ControlFlow::Exit,
            _ => (),
        }
    });
}

Expected behavior
I expect the latest wry can automatically use the system proxy when no manual proxy is configured, just as it did in version v0.24.11.
But now latest wry either requires users to manually specify the proxy or does not use any proxy at all, lacking the option to automatically use the system proxy.
Is the inability to automatically use the proxy a problem with webkit2gtk4.1 itself? Can wry automatically use the system proxy?
Screenshots
Platform and Versions (please complete the following information):

OS: Linux Mint 21.2.0 x86_64 (X64)
✔ webkit2gtk-4.1: 2.44.2
✔ rsvg2: 2.52.5
✔ rustc: 1.81.0 (eeb90cda1 2024-09-04)
✔ cargo: 1.81.0 (2dbb1af80 2024-08-20)
✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (default)

Additional context

I tried Luakit, a browser based on Webkit2gtk. Starting from version 2.3.4, it uses Webkit2gtk 4.1.
I installed a fresh Ubuntu 24.04 and directly installed luakit 2.3.6 via apt. I noticed that luakit 2.3.6 automatically detects and uses the system proxy. Does this mean that Webkit2gtk 4.1 has the capability to automatically detect and use the system proxy, right? Or did I misunderstand something?

The reason I tested Luakit on Ubuntu 24.04 instead of Ubuntu 22.04 in my previous comment is that Ubuntu 24.04 provides version 2.3.6 of Luakit through apt, which allows me to avoid manually compiling Luakit.
However, when I went back to Ubuntu 22.04, manually compiled and ran Luakit, the system proxy issue reappeared.
So I went back to Ubuntu 24.04 again, try to reproduce the issue, it was gone.
Now the issue is now quite clear—it is a problem with webkit2gtk4.1 on Ubuntu 22.04.
I’m not entirely sure why, but since libwebkit2gtk4.1 is built-in on Ubuntu 24.04 and has to be manually installed on Ubuntu 22.04, that could be the reason, perhaps?


Enable localization of the Monaco editor

The monaco editor supports localization of strings used in the editor.
We should enable that and work the plumbing into crowdin.

Won't fix for now


Vue 1.0 compatible

Added support for Vue 1.0. Tried it myself, works fine. I got rid of the inline template, since I think this is much cleaner, especially when you use tons of typeahead (like in the project I updated this for).

I don't want to remove the vue-resource.

I want to pass the query and some data too.

I'm thinking about the template, because someone wants to use a custom template.

I believe that the vue-typeahead will be compatible with vue@1 tomorrow. :smiley:

Some good points. It's probably a good idea to keep the template inline for custom use. Although they certainly can be annoying, the generic template simply won't fit all needs.

e32362aa7fe9f52786a6b05493fa0102f10ab88b


sw_engine renderer: support scene opacity composition

this is an additional enhancement of af8c278c5e2a47c21f44440cdb0a7aaf6f6d3baa
Now scene opacity composition is supported.
Also, this implementaion fixes an incorrect scene bounding box computation.
Plus, adding stroking feathering to shape bounding box size.

Description :

Issue Tickets (if any) :

Tests or Samples (if any) :

Screen Shots (if any) :

And there is one more problem.
I think. transform data is not applied to surface (or bounds?).
diff --git a/src/examples/Opacity.cpp b/src/examples/Opacity.cpp
index f733c3d..1d53bae 100644
--- a/src/examples/Opacity.cpp
+++ b/src/examples/Opacity.cpp
@@ -78,6 +78,8 @@ void tvgDrawCmds(tvg::Canvas* canvas)
     shape4->opacity(200);
     scene2->push(move(shape4));

+    scene2->scale(1.2);
+
     //Draw the Scene onto the Canvas
     canvas->push(move(scene2));
 }

In this sample.

red circle is clliped.
Perhaps  red circle is clipped from the original boundary.
Please check this

@JSUYA  Crash is not related with this patch. it was potential problem.


feat: added system notification

What type of PR is this? (check all applicable)

[x] 🍕 Feature

[ ] 🐛 Bug Fix

[ ] 📝 Documentation Update

[ ] 🎨 Style

[ ] 🧑💻 Code Refactor

[ ] 🔥 Performance Improvements

[ ] ✅ Test

[ ] 🤖 Build

[ ] 🔁 CI

[ ] 📦 Chore (Release)

[ ] ⏩ Revert

Description
This PR adds the flash notification features...

Related Tickets & Documents
feat  #281
https://github.com/open-sauced/hot/issues/281#issue-1326298617

Mobile & Desktop Screenshots/Recordings
after merge notifications will pop up on repo submit as shown below

desktop error flash message on invalid repo submit

desktop success flash message on valid repo submit

mobile error flash message on invalid repo submit

mobile success flash message on valid repo submit

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

notifications work on desktop successful build

@bdougie any style suggestions for the toasters? should we have some defined error/warn/success styles?

@bdougie any style suggestions for the toasters? should we have some defined error/warn/success styles?

My suggestion is to go with the default for now, mainly because I don't. The app.opensauced present errors and notifs in line with the form. My only style suggestion is to move the position to the bottom next to the submission form for now.

Thanks for the contribution @SunGoldTech. I went ahead and committed what I suggested.

Just an FYI for next time to add "closes #281" to the PR body when opening

@bdougie any style suggestions for the toasters? should we have some defined error/warn/success styles?

My suggestion is to go with the default for now, mainly because I don't. The app.opensauced present errors and notifs in line with the form. My only style suggestion is to move the position to the bottom next to the submission form for now.

Suggestions: I think having the toast at the top-center position looks good on all devices compared to the bottom as shown below

We went with the top-right instead, but happy to take contribution to move it back if it presents bugs.

We went with the top-right instead, but happy to take a contribution to move it back if it presents bugs.

Ok...That's cool


Tweets.csv doesn't contain media information (gif, video)

Hi!
Thank you for your work. I have just found out that parsed data in tweets.csv doesn't contain any information about such media as GIF or Video. There is nothing in field photos and links. As far I got from tweet.py file this feature is not implemented yet.  I find it quite useful.
Is there any workaround?
As for example I used this tweet https://twitter.com/redbullracing/status/1054097253860818944
My script:
import twint
c = twint.Config()
c.Username = "redbullracing"
c.Store_csv = True
c.Since = "2018-10-12"
c.Until = "2018-11-18"
c.Format = "Tweet id: {id} | Date: {date} | Time: {time} | Username: {username} | User_id: {user_id} | Tweet: {tweet} | Hashtags: {hashtags} | Replies: {replies} | Retweets: {retweets} | Likes: {likes} "
c.Output = c.Username + ".csv"
twint.run.Search(c)

Hi!
It is not possible to scrape video information. In order to get tweet video information you have to use Twitter API.

@andytnt even the fact that the video or gif exists?

Twitter API provides so much information that twint doesn't, if you definitely need video information you  have to use Twitter API. Also if you're making API requests just to get video information of a tweet you would be wasting your API calls and the rest of information which Twitter API provides.
Maybe Twitter Streaming API is what you're looking for?
Just curious, why do you need video information?

@andytnt Thank you. I will take a look.
My plan was to analyse if a picture, video or gif has impact on number of likes / mentions / retweets the tweet gets. So, in my case I don't need all video information, just the fact that video or gif is used.

4a16ca1


REPL: Wrong dependency for Ammonite

When using the module.repl task, Mill try to download a deleted version of Ammonite:
com.lihaoyi:ammonite_3.0.0:2.3.8-65-0f0d597f
        not found: C:\Users\rapha\.ivy2\local\com.lihaoyi\ammonite_3.0.0\2.3.8-65-0f0d597f\ivys\ivy.xml
        not found: https://repo1.maven.org/maven2/com/lihaoyi/ammonite_3.0.0/2.3.8-65-0f0d597f/ammonite_3.0.0-2.3.8-65-0f0d597f.pom

The latest version is now: 2.3.8-124-2da846d2

Ammonite 2.3.8-65-0f0d597f was never released for Scala 3.0.0 and 2.13.6. Unfortunatelly any version bump to ammonite fail the build of mill. See #1337 and #1343. Any help is appreciated.

Fixed by #1371

@Iltotore you can also choose a version compatible with your current scala version in https://mvnrepository.com/artifact/com.lihaoyi/ammonite
change the version ammonite to use :
// in your build.sc
override def ammoniteVersion: T[String] = T("2.4.0")


[SQLite] Wrong icon for date/time columns

System information:

Operating system (distribution) and version Win10
DBeaver version 21.3.1

Connection specification:

Database name and version SQLite

Describe the problem you're observing:
Datetime or timestamp columns have the same icon as varchar/char columns
Steps to reproduce, if exist:

Open table with timestamp column in data editor

Expected: Timestamp column has a clock icon
Actual: It has ABC icon

Maybe it is more of an enhancement than a bug, because date and time data are actually stored as text, but maybe we can differentiate this data.

We can do the same we do for geometry data.


Prepare onboarding guide for publication on DevHub

Describe the issue
We have some tried and true onboarding materials that could be published to make them more readily available to teams contemplating adopting public cloud services - now that we also have a tile on DevHub, we could publish there.
Which Sprint Goal is this issue related to?

Note: 'Milestone' is a ZenHub term that we use synonymously with 'Sprint'.

The 'Milestone' description (created in ZenHub) should clearly list Sprint Goals. This section should indicate which 'goal' this issue is related to.
Additional context

The pre-reading material being worked on now will feed into this work.
Accessibility enabled

Definition of done

Assemble a first batch of onboarding materials for publication on DevHub
Connect with PO about efforts to get a professional source for images in our documents
Review with Product Owner, and incorporate input
Publish on DevHub

Reviewed with Julian 2021-09-01


Strict formatting

Hi,
I found your library to be extremely useful, except for one case that doesn't really have a solution without doing some hacky stuff that i hate. I need a way to allow strict matching of numbers (when other characters are present
var doubleFormat = wNumb({             mark: ',',             thousand: '.',             decimals: 2         });  console.log(doubleFormat.from('thisStillReturnsAValidNumber1.231,1231'));
I would like an option such that the previous code returns the text itself, not just the number from it, since it cannot be directly converted to a number.

I'm not entirely sure what you'd like to do here, but if I understand it correctly you could implement this by using the decoder option (which applies before all other formatting), and invalidate the number there.


How to get equation (5)

My undestanding of the first condition is: the projection of  o to x  on the direction d should be between $t_0$ and $t_1$.
But I don't understand how to get the second condition. Can anyone help me?

I think they are calculating the cosine of the angle with respect to the centerlnie of the cone.
So basically, they are saying the cosine of the angle should be larger then the cosine of the angle made by a point on the surface of the cone. And as the cosine of a smaller angle is larger then of a large angle this means the angle must be smaller, hence the point must be inside the cone.
See also:
angle between vectors


fix #66: ancient_map load pickle or protobuf worlds

In ancient_map operation we are not trying to load the world first as pickle file then as protobuf file, if an exception is thrown. This is probably not the best way to do it and maybe we could create a method name "load_world_file".

we should wait for the Appveyor pull request (#53) before merging it, so we are sure we are not breaking anything on windows.

About the exception: apparently we have no easy way to distinguish a pickle file from a protobuf file, so we just try first to load a file as a pickle file, if this fails we then try to load it as a protobuf file. When the file is a protobuf file an exception is thrown but we do not want to show that necessarily. Maybe we can store the exception and print it when we cannot load the file neither as a pickle or a protobuf file.

Is there a file header? Normally the first 4 bytes can be read to see what format it is. Not sure if this helps or not. :)

https://stackoverflow.com/questions/13939913/how-to-test-if-a-file-has-been-created-by-pickle
^-- pickle doesn't have a reliable header, but the last byte should be the pickle stop op-code we can test for. :)

Another trick, with photobuf is to always make the very first thing written to be a "version" 4-byte of your choice. This way, you can detect your own file format...  give it a try. That way you can test that the file you are inputting is something created by worldengine.

ok, we could try to use these 2 tricks (stop on code and protobuf headers). They seem to be not 100% exclusive but still in practice it should be enough.

We also:

update the version number (we now use it in the protobuf format)
we changed the protobuf format so we update the worlds used in tests

Rebasing after having merged appveyor

ok, we now should be able to recognize the file type (protobuf vs pickle). I do not understandthe error from linthub. @psi29a seems good to you?

I don't understand the error either, I've never used linthub before. ;)
The rest looks good!

yes, I am tempted to just remove linthub... for now I will merge the PR :)


Add WalGStats to Snapshot's Status

Handled changes in that PR: https://github.com/kubestash/apimachinery/pull/111