Improve portability of CmiMemoryAtomic*/ReadFence/WriteFence

Disable C11 stdatomic.h support with GCC < 7.1 when OpenMP or
Objective-C are in use

Add MSVC intrinsics for memory fences

Always create cmiMemoryLock: it won't be obvious to the runtime, which
compiles as C++, if C user code such as the Converse tests need it, e.g.
for CpvInitialize

Spurious MPI Linux SMP failure:
../../../bin/testrun  ./sparse +p4 ++ppn 2  +setcpuaffinity
Running on 2 processors:  ./sparse +ppn 2 +setcpuaffinity
charmrun>  /usr/bin/setarch x86_64 -R  mpirun -np 2  ./sparse +ppn 2 +setcpuaffinity
Charm++> Running on MPI version: 3.1
Charm++> level of thread support used: MPI_THREAD_FUNNELED (desired: MPI_THREAD_FUNNELED)
Charm++> Running in SMP mode: 2 processes, 2 worker threads (PEs) + 1 comm threads per process, 4 PEs total
Charm++> The comm. thread both sends and receives messages
Converse/Charm++ Commit ID: 94d591b
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received
The build has been terminated

Confirmed that this fixes netlrts-linux-x86_64-omp-smp on Ambition


How about key --minimized ?

Is it have it? --minimized or -startintray, maybe -silent?

--background
Duplicate of #62


.ttl file to load ontology from github

Hey Casper,
I talked to Simon about this and he said I can ask you. Is it possible to have a .ttl file which loads the current version of the ontology from the github development branch.
The reason is that then by just opening this file people can browse the ontology without the need of downloading/pulling the recent updates.
Best Micha

Sure, this can be done by editing the catalog-v001.xml file. I can create a commented out line. One would then have to manually change the commentation lines in this file to be able to fetch the Turtle files from the desired location (locally or from GitHub).

Hey Casper, thanks for the response. I am not sure if I understand. Can one open the catalog-v001.xml file with protege? I am not sure about the role of this file.
If you can provide such an .xml file, this would be great.
Thank you
Best Micha

So to understand completely. You wish to have a file you can pass around that will automatically load the ontologies from GitHub? Or do you wish to have a URL you can use in Protégé that will ensure everything is loaded correctly there?

I think a file is perfect. You open it with protege and it displays the current state of the ontology for review. I think this is easiert to handle. Thanks I will have a look :)

I think a file is perfect. You open it with protege and it displays the current state of the ontology for review. I think this is easiert to handle. Thanks I will have a look :)

Excellent. I have opened a PR for it #20. I have written some instructions to follow to try it out in the PR description. When you have done so, please let me know in the PR and I will then add a section to the README as well as update the file properly to point to the branch that makes most sense for you. Whether that should be main or development.

Hey, great, i tested it :) it should point to development.
Thank you for your help.

The development branch has now been successfully updated.
To see the updated README when one first goes to the repository, the README in the main branch must be updated accordingly.


Add ClearNever

What do you think about naming this similarly to NonNullable built in? Maybe NonNever :D I think it could make it simpler to understand the purpose of this type. Could you leave one line explanation in the readme as well?
Also, FYI: there's a possibility to write some tests using type assertion library. This should be fairly easy to test.

Personally I like ClearNever better, but I understand that NonNever would relate to NonNullable. Gonna change in a moment.

Also, FYI: there's a possibility to write some tests using type assertion library. This should be fairly easy to test.

I know, I was too lazy to write tests though :trollface: Gonna add some in a moment.

Just to reiterate on the naming - NonNullable operates on basic types, NonNever operates on object types and clears properties which have never value.

@Andarist yeah, I have also realized this difference. I am not pushing renaming it really hard, I just think it's slightly easier to understand now 😆
Thanks for writing the test 👍


Fasttext need one line at a time

Bug 💥
FasttextLangDetector need one single line when getting text input. However, Page.get_text() returns text with line breaks.
Expected behavior  🧮
No crash when calling LanguageDetectionService

Closing with PR #81


Linter error priority

It would be useful if there was a way to assign a priority to linters.
For example I am running both the php and phpcs linters. The first one checks syntax errors, the second one checks code style.
Syntax errors should always 'override' code style violations: I want to see the syntax error rather than try to work out why the coding standard is being violated (because a missing parenthesis throws the whole coding style checker out of whack). Currently the phpcs errors shadow the php -l errors.
I see this working in two ways:

for a given line a higher priority linter will display its errors before lower-priority linters.
a higher priority linter will disable lower priority linters if it detects errors.

I prefer the first one myself.

The SL4 beta provides this feature for icons in the gutter, check it out!  https://github.com/SublimeLinter/SublimeLinter3#sublimelinter-4-beta
Priority for inline highlights would be super complicated, it doesn’t weigh up to the value it would provide.


Enable and configure KSM according to memory pressure

What this PR does / why we need it:
Enabling KSM has a substantial impact on performance, and isn't useful when there's plenty of memory available.
This PR preserves and respects the existing API, but tells KSM to run only when there's less than 20% memory available.
There's also some logic to tweak a couple parameters depending on the amount of available memory and the amount of time it's been low.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:

As stated in the code, the logic was inspired from oVirt

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note:

Dynamic KSM enabling and configuration

/cc

@jean-edouard can you address the compute failures? They are ksm related. Thanks

Thanks @jean-edouard! Can I ask you to add the functests deletion reasoning in the commit description too? In this way future us will be able to understand it from the git log. Thank you

@fossedihelm I brought back the functional tests with a few debug annotations, PTAL!

/approve

/retest-required

/lgtm
Thanks @jean-edouard

/unhold

Wow.

Wow.

Lots of goodies in 1.1 ;)


remove BindingGroup and use property bindings for validation instead

fixes #331

Closing since this is handled by #326


Conversion from pocolog/rock logs to H5 + Dockerfile

This PR gives the option of using pocolog format. It also provides documentation and support with a Dockerfile

lgtm


Fix activity state logic (#197)

Fixes the main issue raised in #197.
The logic for selecting current state was slightly off, and it would lead to the first button having very weird behavior (more details in the issue).

This breaks ignored git repos as it is removing the inactive state which is what ignored git repos should be
https://gyazo.com/3bf112ecb55ea21634a971c54d2be9bd


fix: Don't reuse brillig with slice arguments

This is a quick fix after https://github.com/AztecProtocol/aztec-packages/pull/5737 since that PR assumes that one generated brillig is valid for all calls to the brillig function. This is however not true, since the generated brillig can differ if the arguments contains slices. This is because the entry point codegen depends on the size of the slice.
We currently cannot copy slices of any length into brillig due to the limitations of CALLDATACOPY where the size being copied needs to be known at compile-time. I'm going to chat with the AVM team to see if we can lift this restriction and make brillig entry points be able to copy in arguments that contain slices of any length.

Benchmark results
No metrics with a significant change found.

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.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
772
772
772

l1_rollup_calldata_gas
6,820
6,844 (+1%)
6,832

l1_rollup_execution_gas
587,301
587,325
587,313

l2_block_processing_time_in_ms
1,416 (-4%)
5,422
10,343 (-2%)

note_successful_decrypting_time_in_ms
247 (+3%)
599 (+2%)
902

note_trial_decrypting_time_in_ms
49.9 (-9%)
106 (+16%)
120 (-2%)

l2_block_building_time_in_ms
13,229 (-1%)
52,080
103,822

l2_block_rollup_simulation_time_in_ms
13,004 (-1%)
51,253
102,187

l2_block_public_tx_process_time_in_ms
5,678
22,195 (-2%)
44,504 (-1%)

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

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
15,983
30,589 (+2%)

note_history_successful_decrypting_time_in_ms
1,244 (+1%)
2,254 (+2%)

note_history_trial_decrypting_time_in_ms
59.7 (+16%)
79.7 (-35%)

node_database_size_in_bytes
18,726,992
35,168,336

pxe_database_size_in_bytes
29,859
59,414

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

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
158 (+6%)
44,725
26,424

private-kernel-inner
162 (+1%)
72,200
26,424

private-kernel-ordering
112 (+2%)
51,090
39,297

base-parity
40.8 (+1%)
128
311

root-parity
7.49 (+5%)
1,244
311

base-rollup
16,173 (+1%)
110,820
957

root-rollup
47.2
4,551
821

public-kernel-app-logic
88.9
48,175
40,933

public-kernel-tail
123 (-1%)
60,044
7,385

merge-rollup
6.86 (-9%)
2,760
957

public-kernel-teardown
84.7 (-1%)
48,175
40,933

public-kernel-setup
83.0 (-2%)
48,175
40,933

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
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.9 (-1%)
17.7
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.6
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.637 (-1%)
0.548
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
51.3
81.2
259 (-2%)
502
976 (-3%)
1,944 (-3%)
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
96.0
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.526
0.500
0.472 (-2%)
0.470
0.464 (-3%)
0.465 (-3%)
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
60.0
119 (-2%)
375 (-4%)
739
1,460 (-3%)
2,910 (-3%)
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
105
207
691
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.531
0.539 (-2%)
0.512 (-4%)
0.509
0.507 (-3%)
0.506 (-4%)
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
67.5

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
109

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.590

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
41,029
528,895

Transaction size based on fee payment method

Metric
native fee payment method
fpc_public fee payment method
fpc_private fee payment method

tx_with_fee_size_in_bytes
905
1,161
1,377

Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes
2 new note hashes

tx_pxe_processing_time_ms
1,198
802 (+2%)
3,412 (-1%)

Metric
1 public data writes
2 public data writes
3 public data writes
4 public data writes
5 public data writes
8 public data writes

tx_sequencer_processing_time_ms
495
326 (-1%)
891 (-1%)
414 (-1%)
1,483
492 (+1%)


syntax error in documentation

Hi
I am having trouble following the following documentation on retrieveing full instance using specific JPEG 2000 transfer syntax for encoding of bulk data.  The brackets are not balanced, and I could not figure it from the code what is the expected syntax.
https://dicomweb-client.readthedocs.io/en/latest/usage.html#wado-rs-retrieveinstance

never mind.  sorry.


feature add 4 array functions

array_concat
array_pushback
array_pushfront
array_zip

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Request: add jonic.cn to the filter

Evidence: https://jonic.cn/qa/?qa=929514/scala-is-there-a-way-to-add-extra-metadata-for-spark-dataframes
Original: https://stackoverflow.com/questions/32628845/is-there-a-way-to-add-extra-metadata-for-spark-dataframes
Current entry for jonic.cn does not filter above example.
*://*.jonic.cn/*

Many thanks!

Will be corrected by #143


Complete Site Mockup Draft 1

Reviewed 3/21/2023, revisions made to figma mockup per Marija & Paloma's guidance.


Don't Merge! PR real time test for source branch full build

Docs Build status updates of commit c4df97b:
:clock10: Pending: waiting for processors (27 builds ahead of you)
:warning: Docs Build is busy, currently there are 27 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit c4df97b:
:clock10: Full build: the average full build time is 7 min(s) 34 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit c4df97b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docfx.json
:white_check_mark:Succeeded

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


Adding tooltips to the transaction summary field values

This will add tooltips to the transaction summary field values in components/cards/TransactionSummaryView.tsx
closes #189
This builds off of the work on this PR -> #195 I will update the branch once that PR has been merged.

Hi @codynhat & @gravenp , I've made requested changes and updated the branch based on the previously closed PR. Could you please have a look again?


Improve: Add important log to indicate missing file might lead to issue

Add a log indicate the metrics might be 0 and error fast
this is helpful for debug and know what happened ahead ..

print
I1107 01:30:38.736880       1 slice_handler.go:165] Not able to find any valid .scope file in /sys/fs/cgroup/cpu, this likely cause all cgroup metrics to be 0


added observation list and list items

Some comments are not meant for observation files.  We can fix later

:+1:


added horizontal margins

added horizontal margins of 10px.

Good work @kamara-moses,
Can we have this properly centered for every screen width?

Are you meaning centering the accordion title elements or the entire html?

Never mind Sebu's PR took care of this issue, we are good to go 👍🏽 🥳


[WIP] Update prometheus client to 0.6.0, handle counter metric name change

What does this PR do?
Like summaries and histogram types have their _sum / _bucket / _count timeseries aggregated in a single metric using the trimmed name, versions 0.4.0+ of the python prometheus/openmetrics client trim the _total suffix out of counter metric names.
This is a breaking change for us, as integration and custom checks should change their configuration to refer to counter metrics with the new shorter metric name.
This PR introduces a compatibility layer to make this transition transparent. When looking up a metric name in one of the scraper_config's map/list, the following happens:

the lookup is attempted with the current (possibly trimmed) name
if the lookup fails and the metric is a counter, a second lookup is attempted, adding the _total suffix to the metric name.

If we go this route, the prometheus mixin should also be updated, as it uses the same client lib.
Alternative route
We could patch create_scraper_configuration to scan config['label_joins'], config['metrics_mapper'], config['ignore_metrics'] and metrics_mapper to duplicate all entries containing a _total suffix to a new entry without it.
This would avoid the double-lookup cost ; but as we do not know if a given metric is a counter at this time, we might create false-positives by matching non-counters with a _total suffix (example:  the kubelet's container_network_tcp_usage_total is a gauge)
Other changes:

kubelet/tests/test_kubelet.py : update a test that is accessing internals of the Sample object

Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Review checklist (to be filled by reviewers)

[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached
[ ] Feature or bugfix must have tests
[ ] Git history must be clean
[ ] If PR adds a configuration option, it must be added to the configuration file.

superseded by #3700


Make the components import better

create an index file that will exporting all compoents so that instead of:
import { component1 } from `./ui/components/component1`;
import { component2 } from `./ui/components/component2`;

we should be able to :
import { component1, component2 } from `./ui/components`;

Up to you, I find this annoying to have to not forget to add it to an index.ts every time :shrug:

True - but reduces a LOT of lines of code

I really have no strong opinion there. If you prefer it that way, please go ahead, I'll make follow.


CMake failed because of nlohmann_json

Hi,
I am trying to install DDSIM and cmake reported error when I am building qfr:
-- Using the single-header code from /home/user/ddsim/extern/qfr/extern/json/single_include/
CMake Error at src/CMakeLists.txt:112 (install):
install TARGETS given target "nlohmann_json" which does not exist in this directory.
It seems like nlohmann has updated his json repo, since his new README/External section is using nlohmann_json::nlohmann_json.
I am building the codes on WSL2 ubuntu 18.04 LTS. My CMake version is 3.10.2.
I am not familiar with CMake so I am not sure how to fix it...
BTW the README of DDSIM repo doesn't mention the 'mkdir build & cd build' part, which seems a bit misleading for me to find it out...

Hi there,
thanks for your interest in our project.
Regarding the README of the DDSIM repo: mkdir build & cd build is only required for CMake versions <3.13. I added a corresponding hint in the README.
Concerning your real error: I can't quite reproduce it on a fresh git clone or our CI builds. Are you sure you did a recursive submodule update (git submodule update --init --recursive) after cloning? This is necessary in order to clone all the submodules of the sub-projects. Alternatively you could try a fresh clone of the project and add the --recurse-submodules flag.

Hi,
The problem is caused by the old version of CMake. I updated my CMake and the problem is gone.
Known valid CMake version (in my tests): 3.13, 3.19.
Ubuntu 18.04 LTS's default CMake version is 3.10.
Thanks.


Group main help message to put important commands to the top

I.e. the version, help and completion commands should be put into a separate section below the main commands. This can be achieved with the same technique as found for kn that uses advanced templating techniques from Cobra.

/remove-lifecycle stale

/remove-lifecycle stale

Hi @rhuss! Are you still working on this issue? If not, I would try to solve it, based on your suggestion to use your code and ideas from kn. I have some years of knowhow in go, Cobra, Kubernetes&Co. I have already briefly analysed your solution for kn and the question would be if we need exactly the same for func or maybe something simplified.

@grafvonb would be great if you can take a look on this.

Great, I'll take over.

@grafvonb any update on this please?

Would love to see this in 1.0

@zroubalik I will submit my status this coming weekend. Is that ok for you?

@grafvonb sure, thanks a lot!

@zroubalik as discussed, I have checked the context, made a fork and run the core tests successfully on my Mac locally. So I am ready to start developing this change. Two questions before I start:

My plan is to reuse the parts of the code from the fn project, as suggested by @rhuss. I just don't want to reinvent the wheel. Is that ok with you from a technical and legal perspective?
@lance What is the schedule for the 1.0? I would like to make a schedule as I am doing this in my spare time.

Thanks a lot!

@grafvonb I suppose you meant kn project (https://github.com/knative/client/)? Then it is completely fine to use it and it is actually preferred :)
Thanks for contributing this!

Yes, exactly kn, as you can see, I think about functions only ;).

Yes, exactly kn, as you can see, I think about functions only ;).

@grafvonb you can track our progress towards 1.0 here https://github.com/orgs/knative-sandbox/projects/7/views/13

/assign @grafvonb

/close

Done by https://github.com/knative-sandbox/kn-plugin-func/pull/1152


Reimplementing pong events

Description
Socket.io has removed pong events in the latest version, so we need to implement our own, in order to keep tracking latency
In DocumentDeltaConnection, when we listen to "newListener", we will have a loop of tracking latency every minute, and emit pong event, which will go all the way to deltaManager to log to telemetry.
If we find latency that's more than 1 min, we will log separately as well

need to move test I added as the container test only run with local server


module close-buffers not found

Its installed correctly, config is correctly loaded, but module close-buffers not found error is coming up

Hi @sahilsehwag ,
Appologies, looks like the README needs a little update.
Try close_buffers.
Thanks,
Kevin


Create a documentation page that contains links to all the examples

Is your feature request related to a problem? Please describe.
The project has a number of examples, all of them can be found at https://github.com/vmware-labs/wasm-workers-server/tree/main/examples.
We also keep extensive documentation on how to use the project at https://workers.wasmlabs.dev/docs/get-started/introduction.
Describe the solution you'd like
Create a documentation page that first links to every example in the project, with a GitHub link  to that examples README.md given that every example has its own README.md file.
Describe alternatives you've considered
No response
Additional context
No response

Hey @ereslibre
Your suggestion sounds exciting and I would like to ask to start doing it if noone is a candidate yet 👍 🤔

#270


[Feature]: Option to Change Focused Block Border Color

Feature description
Right now, the block you are focused on has a green border, and there’s no way to change this color. Even if you use different tab background colors like blue or red, the focused block stays green, which doesn’t look good.
I would like an option to change the border color of the focused block.

Implementation Suggestion
I would like to change the border color through the settings.json file, similar to how we change the window:bgcolor.
Anything else?
No response

there is actually a "secret" meta key that will set this on a per block basis frame:bordercolor:focused.  you can try wsh setmeta frame:bordercolor:focused=red (or any "#rrggbb" color).  that doesn't do it global or system-wide though.  it should be an easy-enough change to add.  probably makes sense to add to the tab backgrounds configuration.

@sawka Nice!! I will use this option for now 😄

in the background presets, you can now set: "bg:activebordercolor": "rgba(0, 0, 255, 1.0)" to override the active border color for blocks


Set custom attribute name instead of model's register id

Hello!
This isn't really an issue with the gem, more like an information request! I'd like to know if it is possible to generate the views/stylesheets from rails_admin somehow, or where can I customize them.
For example, let's say that I have a car-lending system, and I'd want to set that "X" car belongs to "Y" user, when I'm selecting the cars on my list, I'd see Car #1, Car #2, etc. How can I set it that instead of their IDs, I see a list of their names?
I'm sorry if this is the wrong place to ask, or if this has been answered before, but I really couldn't find this anywhere, the only thing I found was that some time ago you could generate the views via "rails g ...", and now it has been deprecated and you should use the DSL, but through the DSL I can't see/have access to everything I'd like to change, or at least I haven't found out how to use it properly so far D:
Thank you so much for your time!

by default rails_admin use name or title attributes as labels.
if you have one of this attribute in your cars model (table), you have nothing to do by default rails_admin use name or title attributes as labels.
if you have one of this attribute in your cars model (table), you have nothing to do. If not, you should add a method in your model and config rails_admin like this :
model cars < AR
 def my_car_name_or_title_or_other
    self.label_attribute # or a string "My super car..."
end

rails_admin do
  object_label_method :my_car_name_or_title_or_other
end
end

wiki Method for instances label: https://github.com/sferik/rails_admin/wiki/Navigation and https://github.com/sferik/rails_admin/wiki/Base-configuration

A huge thanks to @fmh for the help and for the really fast reply! The example code ended up like this:
class Car < AR
def car_model_name
self.car_model
end
on my config/initializers/rails_admin.rb
config.model 'Car' do
object_label_method :car_model_name
end
Thanks again!


Jhendr m365 community

Category

[X] Content fix

Docs Build status updates of commit 1482d2c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Community/Yet-another-Tool-Why-you-will-probably-love-Project-Moca-aka-Outlook-Spaces.md
:warning:Warning
View
Details

Community/article-template.md
:white_check_mark:Succeeded
View

Community/Yet-another-Tool-Why-you-will-probably-love-Project-Moca-aka-Outlook-Spaces.md

Line 35, Column 1: [Warning-file-not-found] Invalid file link: 'media/yet-another-tool-why-you-will-probably-fall-in-love-with-project-moca-aka-outlook-spaces/outlook-spaces-project.png'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 95e05f2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/Yet-another-Tool-Why-you-will-probably-love-Project-Moca-aka-Outlook-Spaces.md
:white_check_mark:Succeeded
View

Community/article-template.md
:white_check_mark:Succeeded
View

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


Relative installs with develop = true not exporting to requirements.txt correctly

When exporting with a relative package, with develop = true, the requirements.txt file is not created correctly.
pyproject.toml
[tool.poetry.dependencies]
package-name = { path = "../relative/path/to/package-name", develop = true }

requirements.txt with 1.7.1
package-name @ file:///absolute/path/to/package-name ; python_version >= "3.10" and python_version < "4.0"

requirements.txt with 1.8.0
-e file:///absolute/path/to/package-name ; python_version >= "3.10" and python_version < "4.0"

When installing via pip, it does not copy the package files into the target directory. It puts the dist-info folder, and a package_name.pth file.

It is created correctly. develop = true is the same as -e (--editable) for pip. #258 is a bugfix for #145.

When installing via pip, it does not copy the package files into the target directory. It puts the dist-info folder, and a package_name.pth file.

That's what develop/editable should do.
Having said that, a PR introducing a flag for the export command to ignore the value of develop and export all dependencies as non-editable would probably be accepted.

@radoering, I realize you folks are busy but it is worth noting that this change broke dependency resolution for folks using poetry with a monorepo, because pip can't resolve multiple versions of editable dependencies. We're currently stuck on an old version of poetry-plugin-export because of this.

@williamhakim10 Do you pass --no-deps to pip? This often resolves such issues. By the way, it does not make sense to let pip resolve dependencies again, i.e. not using --no-deps, because the exported requirements.txt contains all resolved direct and transitive dependencies.


Fix and Test FinalSubmission

I stopped the final branch PR (#337) from crashing in most cases - but there is still a bug (I think it's with the with the pre_put_hook)
Two issues:

On invite - a user loses their final submission  until the other person accepts or rejects the invite
There's something off on the version deployed - which assigns a Final Submission to all of the users assignments (This might be affecting the actual datastore - which would be bad. The frontend is also impacted)

@papajohn - Can you take a look at the pre_put_hook of the Group method?

I'll add more tests to ferret out the rest of the bugs.

I added tests for the following scenarios:

create a group of 2 (invitation and acceptance)
try to create a group of 2 but someone declines
create a group of 2 and then someone leaves

Groups of 3 remain untested, but I think that's ok.
These same scenarios don't have integration tests. I'll try to add one now, but only have a few minutes.
Logic changes:

get_final_submission now ignores your group if you're only invited, not a member
pre-put hook for final submission is gone; I think it's too expensive and complicated. Instead, we should just write a lot of tests.

I'll look at this.

I can still reproduce the invite removes final submission bug. I don't think calling update_final_submission is fixed it - Here's how I test it in case you want to run it
Start the server and login as<EMAIL_ADDRESS>remove partner1 from the Hog Group. Now invite<EMAIL_ADDRESS>back - the page will now tell you that you have no submission.

Investigating now. Thanks for the description.
On Tue, Jan 27, 2015 at 2:56 PM, Sumukh Sridhara<EMAIL_ADDRESS>wrote:

I can still reproduce the invite removes final submission bug. I don't
think calling update_final_submission is fixed it - Here's how I test it in
case you want to run it
Start the server and login as<EMAIL_ADDRESS>remove partner1 from
the Hog Group. Now invite<EMAIL_ADDRESS>back - the page will now
tell you that you have no submission.
—
Reply to this email directly or view it on GitHub
https://github.com/Cal-CS-61A-Staff/ok/pull/340#issuecomment-71746216.

Perhaps the error has to do with get_group? When update_final_submission is called - get_group for the user that sent the invite returns None. I don't think it should return none - it should update the users submission to the group.
('Updating user'<EMAIL_ADDRESS>'Group: ', None)

I'm having a hard time constructing a test that exercises the API in the
appropriate way, but so far I've noticed (and corrected locally) the
following error:

get_final_submission doesn't query on assignment

On Tue, Jan 27, 2015 at 5:35 PM, Sumukh Sridhara<EMAIL_ADDRESS>wrote:

Perhaps the error has to do with get_group? When update_final_submission
is called - get_group for the user that sent the invite returns None. I
don't think it should return none - it should update the users submission
to the group.
('Updating user'<EMAIL_ADDRESS>'Group: ', None)
—
Reply to this email directly or view it on GitHub
https://github.com/Cal-CS-61A-Staff/ok/pull/340#issuecomment-71765634.

Interesting - can you push that and I'll also try to take a look?

Pushed a partial test and some small fixes. Since I can't seem to write a
working regression test, I'll try debugging through the UI now.
On Tue, Jan 27, 2015 at 6:04 PM, Sumukh Sridhara<EMAIL_ADDRESS>wrote:

Interesting - can you push that and I'll also try to take a look?
—
Reply to this email directly or view it on GitHub
https://github.com/Cal-CS-61A-Staff/ok/pull/340#issuecomment-71768381.


vue build后出现TypeError: Cannot read property 'format' of undefined

vue项目使用numeric-keyboard，使用build后报错 TypeError: Cannot read property 'format' of undefined

Can you give more information, code snippet or something?


Adding CORS to apiv1

Seems to be similar to #297 (but this PR has been rejected) and https://forums.hummingbird.me/t/cors-access-to-main-site-api/16862
Is there a way to add CORS to apiv1 for javascript call support?
Thanks

To enable it, juste add Access-Control-Allow-Origin: * to the response header.

I can't remember any security implication as said in the other PR, I don't see any problem with it, but it's better to see if @NuckChorris can remember some obscure problem related :laughing:

Please don't forget that to the next version! Thanks :wink:


[fix] Generator does not use latest RDFA file

replaces #54
3 commits now - cause I forgot to add the new files 🙈 😄
The Readme says:

The code in src is generated from Schema.org's RFDa standards file

The corresponding raw link would be: master/data/schema.rdfa
But the Generator uses sdo-callisto/data/schema.rdfa - this file seems outdated and misses some properties and even some new types.

Most important part is that the generator changes are separated :) Thanks!


Error in the console when I launch Sublime

When I launch in to Sublime Text 3 (3211) and check the console I get an error from this package:
reloading plugin Sass.sass_completions
Traceback (most recent call last):
  File "/opt/sublime_text/sublime_plugin.py", line 125, in reload_plugin
    m = importlib.import_module(modulename)
  File "./python3.3/importlib/__init__.py", line 90, in import_module
  File "<frozen importlib._bootstrap>", line 1584, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1565, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1532, in _find_and_load_unlocked
  File "/opt/sublime_text/sublime_plugin.py", line 1199, in load_module
    exec(compile(source, source_path, 'exec'), mod.__dict__)
  File "/home/thomas/.config/sublime-text-3/Installed Packages/Sass.sublime-package/sass_completions.py", line 688
    details = f"<code>{prop}</code> property-value"
                                                  ^
SyntaxError: invalid syntax

I also got the same error， i guess this is python version compatible issue， any solution ?

Damn, a python 3.8 language feature slipped in. Thanks for reporting!


🍒 Cherry pick PR #9682 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/9682 to staging 🍒

🚀 Deployed to production by @roryabraham in version: 1.1.79-17 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Minor: Less indicators

Really appreciate the plugin, extremely helpful for learning. I'd be grateful if npc highlights became togglable, I can already see them pretty easily. Thanks for the plugin!

I will look into this soon. Thanks for the suggestion :)

I will look into this soon. Thanks for the suggestion :)


HOS : Delete Bucket GCP

Issue/Feature Description:
Why this issue to fixed / feature is needed(give scenarios or use cases):
How to reproduce, in case of a bug:
Other Notes /  Environment Information: (Please give the env information, log link or any useful information for this issue)

Completed in I Release


terminal doesn't recognize filename and line number

originally posted here: https://github.com/ocaml/dune/issues/6908
when using the OCaml ecosystem (in my example dune) the errors can't be clicked on in the terminal:

I often can't click on the file because it isn't relative to where I am, and when I can click it doesn't get me to the line number. I'm not sure how other languages do it but I don't remember having that problem in other ecosystems.
I'm also not sure how to fix it. I believe the terminal / vscode will detect filename:linenumber all the time, but the "File "src/base/snark_intf.ml", line 588, characters 50-75" is not recognized.

yeah looks like we don't support that case atm, though this one comes close
https://github.com/microsoft/vscode/blob/5dbb41f91d0f33f72746b3ad55ef9cccda59364a/src/vs/workbench/contrib/terminal/browser/links/terminalLocalLinkDetector.ts#L60

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_smiling_face: This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

The situation is pretty good on Insiders after the many link changes that have gone in since December:

Keeping this open to also match the characters part and ideally select the actual range in this case.

what's Insiders?

I'm enjoying the improvement, but the pattern lines X-Y still doesn't work, e.g.:
File "lib/formula.ml", lines 296-297, characters 4-48:
Thanks!

@lukstafi is that a real example or did you make up the characters part? I'm not sure what multi-line and multi-character means exactly

Thank you @Tyriar  for your work! It's a real example, just going to the first line is good enough for me! The meaning of  File "F", lines N1-N2, characters C1-C2: is "in the selection within file F, spanning from line N1, character/column C1 to line N2, character/column C2" (subject to off-by-one errors, I don't remember how the characters are counted).

Oh ok, that makes sense 👍

FYI the row/col end part of the link should work when https://github.com/microsoft/vscode/pull/185888 is merged 🎉


Documentation improvements

Closes #167

requires ipywidgets for improved tqdm rendering
simplifies some other output for import notebook
fixes some docstrings that weren't rendering well on readthedocs.

Docs preview at: https://lsdb--222.org.readthedocs.build/en/222/index.html


Check entity ai behaviour: minecraft:behavior.avoid_mob_type

Check if the ai behaviour: minecraft:behavior.avoid_mob_type is update to date

I checked and this component seems complete compared with bedrock.dev and official docs.

Thanks!


Add ability to define cterm colors (and define default cterm colors)

added in https://github.com/petertriho/nvim-scrollbar/commit/8c0bf2d6806c55c40e0f3cac9f3c124154df5b73


fix: Fix spurious author extraction errors

This fixes edge cases including the following names:

Joris van Kuijc van Malsen
दिल
शिला के.सी.
Lady Garcia
Carolina de la O
உயிரோவியம் தங்கராஐ;
Alexandre Koch II

@rjsparks I'm still running the tests in a loop to generate more failures, but I think this is ready for review in the meantime.

Found another case, where "இந்திராணி ஆதர்ஷ்,ஆதேஷ்" renders as "Intiraanni Aatrss,aateess" and the comma is confusing the current regex.

No more failures in the last few hours.


[Request] Warp Speeds, Strange Dilithium, and more Drives

What do you think is missing or what do you think can be done better

I believe that the current Warp Speed is too slow, thus I suggest the implementation of a Warp Scale and Warp Speeds.

[Describe in detail what you want to see and how it makes the mod better]

I would like to see different Warp Speeds with varying fuel consumption and time to reach the destination. Warp Speeds could use a custom Warp Scale, with a base fuel cost increase of tenfold per Warp Speed, and a base speed increase to match. Warp 1 would require 10 Fuel and be 1 times Light Speed, Warp 2 would require 100 Fuel and be 10 times Light Speed, etc, etc. Warp 10 would be achievable utilizing "Strange Dilithium" which has a 1 in 20 chance of replacing normal Dilithium Ore. I'll write down the drives when I have time.

Drives:

Hyper Drive: Dangerous and requires a Mapping Computer (Along with the Warp Controller), requires 1000RF to enter Hyperspace.
Pros: No Dilithium requirement, cheap.
Cons: Dangerous (Has a 1 in 100 chance of destroying parts of a ship.)

Ion Drive: Cheap but requires a warm-up time before use.
Pros: Cheap, no fuel.
Cons: Warm-up time.

Solar Sail: Massive, made of various metal alloys and glass, cheap(ish), speeds up during the flight.
Pros: Cheap(ish), no fuel.
Cons: Massive.

I find it strange that all of the drives you've just mentioned are "cheap", with the exception of the Solar Sail which is "cheap-ish"
I'm not a fan of implementing interstellar travel with sub-light technology. Ion Drives and Solar Sails aren't going to get you to even the nearest planet in a reasonable amount of time for quick Sci-Fi universe space travel. I'm okay with multiple forms of faster-than-light drives, but anything slower shouldn't be used for going anywhere further than a moon or another planet in a red dwarf system.
Also, I'm not a fan of anything that has a chance of destroying a player's build simply for using it.

I ran out of ideas.

If you wanted a different superluminal drive, try Alcubierre drives. (Also called curvature propulsion). Technically possible, need exotic matter, really cool. Subluminal transportation should likely be limited to intersystem only. For that ion, nuclear thermal, bussard ramjets, and solar sails would all work, but be somewhat more balanced.
And as a side note, 1000 RF for hyperspace? With RF inflation? Try 1M RF.

Alcubierre Drives are just Warp Drives with a different name.

How about 1M RF to enter Hyperspace and 1000RF/t to stay in Hyperspace?

If you wanted a different superluminal drive, try Alcubierre drives. (Also called curvature propulsion). Technically possible, need exotic matter, really cool. Subluminal transportation should likely be limited to intersystem only. For that ion, nuclear thermal, bussard ramjets, and solar sails would all work, but be somewhat more balanced.
Alcubierre Drives should have some advantage over Warp Drives if implemented
And as a side note, 1000 RF for hyperspace? With RF inflation? Try 1M RF.
How about 1M RF to enter Hyperspace and 1000 RF/t to stay in Hyperspace?
As well, the ion drive should absolutely require fuel.
Ion Drive could run off of Rocket Fuel.
Of the gasses to be ionized; Bussard Ramjet and solar sails are the only two "passive".
Ramjet should require a hydrogen collection block located within a multiblock at the front of the ship.

Drives:

Hyper Drive: Dangerous and requires a Mapping Computer (Along with the Warp Controller), requires 1000RF to enter Hyperspace.
Pros: No Dilithium requirement, cheap.
Cons: Dangerous (Has a 1 in 100 chance of destroying parts of a ship.)
Ion Drive: Cheap but requires a warm-up time before use.
Pros: Cheap, no fuel.
Cons: Warm-up time.
Solar Sail: Massive, made of various metal alloys and glass, cheap(ish), speeds up during the flight.
Pros: Cheap(ish), no fuel.
Cons: Massive.

I recently read Hitchhiker's Guide to the Galaxy and would like to see the Infinite Improbability Drive.

Bussard ramjet only needs power. It uses electromagnetic fields within a huge solenoid to gather fuel. No "scoops" needed, they're magnetic for this one.

Bussard ramjet only needs power. It uses electromagnetic fields within a huge solenoid to gather fuel. No "scoops" needed, they're magnetic for this one.

Okay, than a multiblock electromagnet structure and a multiblock thruster.

Here were some example structures I made for the ramjet.
Needs unobstructed I/O through the center of the solenoid.

Here were some example structures I made for the ramjet.
Needs unobstructed I/O through the center of the solenoid.
The angel block is the controller.

Does it have to use Iridium?

Not necessarily? Probably aluminium on up, though.

Not necessarily? Probably aluminium on up, though.

How exactly would it be tiered?

There's an issue on here for it with a bunch of discussion.
https://github.com/zmaster587/AdvancedRocketry/issues/1572


WESM.gpkg coordinate ordering changed!

Very strange, but sometime recently, the coordinate ordering in the USGS WESM.gpkg changed, causing our search and tests to fail 🤦 :
ogrinfo -so -al /vsicurl/https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/WESM.gpkg | grep Extent
#Extent: (13.232000, -179.250067) - (71.507000, 179.854651)
ogrinfo -so -al WESM.gpkg | grep Extent
#Extent: (-179.250067, 13.232000) - (179.854651, 71.507000)

(maybe last update on 2024-11-24T06:33:34.000Z according to https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/metadata/)
I'll setup a workflow to run tests nightly to keep track better track of these sorts of changes... Also sent an email to USGS.

Good catch! Did the crs and axis order definition change? Are we loading that directly, or assuming 4326?

Quick note that for now I'm just doing this to reverse the coordinates after loading:
gf_lidar['geometry'] = gf_lidar['geometry'].map(lambda polygon: shapely.ops.transform(lambda x, y: (y, x), polygon))

Seems fixed as of file update at 2024-12-04T20:03:29.000Z


Analytics to tell if a supplier is eligible to apply for a brief

Overview
Pivotal story
When a supplier clicks to apply for a brief they can be one of 4 states:

are eligible and can apply
are not eligible as they are not on the framework
are not eligible as they are not on the lot
are not eligible as they can not provide the specialist role

After clicking the button to apply for a brief, in all of the above cases, they are taken to the same URL. In the success case (eligible) they are shown the form to apply. In the failure case (not eligible) they are shown the relevant message for why they can not apply to this brief. We wish to add analytics to this page so we can track the 4 cases. This is done by setting a Google Analytics custom dimension with a value related to one of the 4 cases.
Approach

For the non eligible case, the not_is_supplier_eligible_for_brief_error template is used. We add a data-reason attribute to the page that stores the reason for ineligibility such as "supplier-not-on-dos".

For the success case (where the supplier is eligible to apply) we add nothing to the template.

When visiting the route to apply for a brief, we check the html content to see if a data-reason is present. If so, we send that value. If not then we can assume that they are viewing the page to apply and are eligible, so we send "supplier-able-to-apply". Note, the javascript acts as the gateway by checking the page url to make sure we only send this custom dimension on the required route (as our templates may be shared by several pages, we may have data-reasons present on different routes).

Looks good to me, nice work 👍


Electron won't read from asar archive

Following the pretty simple Application Packaging directions, I cannot get electron.exe to read from my asar archive.
This is the hello world app from the tutorial, which executes correctly with electron.exe if I copy the original source into the resources directory under an app/ folder. However, when I package this in an asar archive, remove the original source from the resources directory and put the asar archive there, running electron.exe does nothing.
Is there a way to debug what's going on here? Is there a step/file I'm missing?

Ah figured it out, I had entirely emptied out the resources directory, but it looks like you need to keep the atom.asar file.

I wonder what is the function of asar type file.

The asar file type is there to allow a developer to package up all his
assets into one file.
On Sun, May 3, 2015 at 6:41 PM cloudlakecho<EMAIL_ADDRESS>wrote:

I wonder what is the function of asar type file.
—
Reply to this email directly or view it on GitHub
https://github.com/atom/electron/issues/1563#issuecomment-98552617.

Thanks for the information, Frank.
I have other question. When I read the source code in atom/electron version 0.25.2. I found this code section in atom_main.cc;
int APIENTRY wWinMain(HINSTANCE instance, HINSTANCE, wchar_t* cmd, int) {
int argc = 0;
wchar_t** wargv = ::CommandLineToArgvW(::GetCommandLineW(), &argc);
scoped_ptrbase::Environment env(base::Environment::Create());
I just wonder how I understand this line in the section;
"wchar_t** wargv = ::CommandLineToArgvW(::GetCommandLineW(), &argc);"
the ** and :: Would you able to interpret? I know that the * normally use to point and :: for member function, but in the line there is two * and :: is used without her class name. Do I miss something?

I'm definitely not a good C++ programmer so I'm going to guess here. I think wargv is a pointer to an array of arguments. The :: makes sure that the function resolution happens in the global namespace.

Thanks for the response. I understand the global namespace. For the double asterisks, I will search around Internet.


radare2: 2.2.0 -> 2.3.0

Bump radare2.
Also, bump to pinned capstone revision instead
of the capstone release (3.0.4) from 2015.

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

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

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

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘radare2-2.3.0’ in /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/development/tools/analysis/radare2/default.nix:50 is not supported on ‘x86_64-darwin’, refusing to evaluate.

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

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

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/qmijcmga7ilswwx6apdd6qvnp044f6bk-radare2-2.3.0/bin/ragg2
shrinking /nix/store/qmijcmga7ilswwx6apdd6qvnp044f6bk-radare2-2.3.0/bin/r2agent
gzipping man pages under /nix/store/qmijcmga7ilswwx6apdd6qvnp044f6bk-radare2-2.3.0/share/man/
strip is /nix/store/adidfx4pa7vmvby0gjqqmiwg2x49yr27-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/qmijcmga7ilswwx6apdd6qvnp044f6bk-radare2-2.3.0/lib  /nix/store/qmijcmga7ilswwx6apdd6qvnp044f6bk-radare2-2.3.0/bin
patching script interpreter paths in /nix/store/qmijcmga7ilswwx6apdd6qvnp044f6bk-radare2-2.3.0
/nix/store/qmijcmga7ilswwx6apdd6qvnp044f6bk-radare2-2.3.0/bin/r2pm: interpreter directive changed from "/bin/sh" to "/nix/store/fcxliihmhm2ak9z4890gk0qw63zsbrcx-bash-4.4-p12/bin/sh"
/nix/store/qmijcmga7ilswwx6apdd6qvnp044f6bk-radare2-2.3.0/bin/ragg2-cc: interpreter directive changed from "/bin/sh" to "/nix/store/fcxliihmhm2ak9z4890gk0qw63zsbrcx-bash-4.4-p12/bin/sh"
checking for references to /build in /nix/store/qmijcmga7ilswwx6apdd6qvnp044f6bk-radare2-2.3.0...
/nix/store/qmijcmga7ilswwx6apdd6qvnp044f6bk-radare2-2.3.0

Failure on aarch64-linux (full log)
Partial log (click to expand)
checking for libmagic ... no
Using PKGCONFIG: pkg-config
checking pkg-config flags for capstone... no
checking for libz ... yes
checking for libzip ... no
checking for libssl ... yes
checking pkg-config flags for openssl... yes
./configure: line 524: syntax error: support for $((arith)) is disabled
builder for '/nix/store/cwcbgagi9gs6k2idkh5mnzabib9gimla-radare2-2.3.0.drv' failed with exit code 2
error: build of '/nix/store/cwcbgagi9gs6k2idkh5mnzabib9gimla-radare2-2.3.0.drv' failed

aarch64 failure is the "/bin/sh" problem, lack of arith expr support.  Don't know if it worked previously, but at least this particular failure should be resolved by fixing/updating that.

@GrahamcOfBorg build radare2

Success on x86_64-linux (full log)
Partial log (click to expand)
/nix/store/qmijcmga7ilswwx6apdd6qvnp044f6bk-radare2-2.3.0

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘radare2-2.3.0’ in /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/development/tools/analysis/radare2/default.nix:50 is not supported on ‘x86_64-darwin’, refusing to evaluate.

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

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

Success on aarch64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/1y7iabf6arzj607krb4i6k7sysprgy4z-radare2-2.3.0/lib/libr_asm.so.2.3.0
shrinking /nix/store/1y7iabf6arzj607krb4i6k7sysprgy4z-radare2-2.3.0/lib/libr_anal.so.2.3.0
gzipping man pages under /nix/store/1y7iabf6arzj607krb4i6k7sysprgy4z-radare2-2.3.0/share/man/
strip is /nix/store/skd6ix5ipkyhxzq7naylj4digawakl4j-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/1y7iabf6arzj607krb4i6k7sysprgy4z-radare2-2.3.0/lib  /nix/store/1y7iabf6arzj607krb4i6k7sysprgy4z-radare2-2.3.0/bin
patching script interpreter paths in /nix/store/1y7iabf6arzj607krb4i6k7sysprgy4z-radare2-2.3.0
/nix/store/1y7iabf6arzj607krb4i6k7sysprgy4z-radare2-2.3.0/bin/ragg2-cc: interpreter directive changed from "/bin/sh" to "/nix/store/shjmvsnwrlg7rd8m0kzgpygqq4if312z-bash-4.4-p12/bin/sh"
/nix/store/1y7iabf6arzj607krb4i6k7sysprgy4z-radare2-2.3.0/bin/r2pm: interpreter directive changed from "/bin/sh" to "/nix/store/shjmvsnwrlg7rd8m0kzgpygqq4if312z-bash-4.4-p12/bin/sh"
checking for references to /build in /nix/store/1y7iabf6arzj607krb4i6k7sysprgy4z-radare2-2.3.0...
/nix/store/1y7iabf6arzj607krb4i6k7sysprgy4z-radare2-2.3.0

Yep, that was the reason for the aarch64 failure! Works now! :+1:


Iife build

Adding gulp-iife so that this version of jQuery can't interfere with others. Locking version of bootstrap so it doesn't upgrade without proper testing.

@tylercherpak we have decided to take a different approach which does not require a change to the design system. This was done primarily because the issue of conflicting jQuery versions was a problem specific to our WordPress Usage and not with the design system itself.


Possible to generate Python wheel?

I have successfully installed OpenCV, including the Python bindings.
print(cv2.getBuildInformation())

General configuration for OpenCV 4.9.0 =====================================
  Version control:               unknown

  Extra modules:
    Location (extra):            /home/ica/opencv_contrib/modules
    Version control (extra):     unknown

  Platform:
    Timestamp:                   2024-03-22T14:59:28Z
    Host:                        Linux 5.10.192-tegra aarch64
[...]

The problem is that when I install a package that depends on opencv, it will not see this and pull the python-opencv wheel, which has fewer capabilities.
There is another repo that builds the wheels, would it be possible to integrate that into this script? Or adjust it to generate the right output? If not, we could export the CMake options in this repo into the wheel building script.
The uglier alternative is to create a dummy wheel that serves as a placeholder.

A common problem. To overcome ownership issues, I use virtual environments.
The wheels you're referring to are all CPU-based. When integrating CUDA acceleration, you're facing too much deviation. Not only the Python version but the CUDA architecture must also be taken into account.


We wish add user auth system.

:)

@wkshare Bosun is easily composable, for web access one can use any proxy with http basic auth support plus optional SSL. As for managing configuration - just use, for example, Gitlab repo and post-commit hook to update bosun.cfg and restart daemon.

@elementai we used cas.

Closing as no detail and we will be covering in separate ticket


Offset Wrong [Free Fire Game]

I dumped free fire with game guardian and libdumper GUI, and the offsets are correct. But with Zygisk the offsets came differents

You should provide me with more information, such as the game package name and relevant screenshots of the problem you mentioned.

maybe because of different arch?

I have same problem offsets different when I use zygisk on mobile legend and blade idle

kurulum hatası alıyorum neden acaba


Change the process title for workers to easily differentiate them.

Example of what ps command looks like on my Mac running rake evm:start with one provider
$ ps -ef | grep<PHONE_NUMBER>
  501 29796 25394   0  5:16PM ttys006    0:00.00 grep --color=auto<PHONE_NUMBER>
  501 28639 28576   0  5:13PM ttys007    0:14.16 MiqEventHandler id:<PHONE_NUMBER>011, queue: ems
  501 28641 28576   0  5:13PM ttys007    2:04.12 MiqGenericWorker id:<PHONE_NUMBER>012, queue: generic
  501 28642 28576   0  5:13PM ttys007    2:04.77 MiqGenericWorker id:<PHONE_NUMBER>013, queue: generic
  501 28645 28576   0  5:13PM ttys007    1:30.94 MiqPriorityWorker id:<PHONE_NUMBER>014, queue: generic
  501 28646 28576   0  5:13PM ttys007    1:32.97 MiqPriorityWorker id:<PHONE_NUMBER>015, queue: generic
  501 28650 28576   0  5:13PM ttys007    0:14.35 MiqReportingWorker id:<PHONE_NUMBER>016, queue: reporting
  501 28651 28576   0  5:13PM ttys007    0:14.32 MiqReportingWorker id:<PHONE_NUMBER>017, queue: reporting
  501 28654 28576   0  5:13PM ttys007    0:17.06 MiqScheduleWorker id:<PHONE_NUMBER>018
  501 28656 28576   0  5:13PM ttys007    0:14.57 MiqUiWorker id:<PHONE_NUMBER>019, uri: http://<IP_ADDRESS>:3000
  501 28658 28576   0  5:13PM ttys007    0:14.42 MiqWebServiceWorker id:<PHONE_NUMBER>020, uri: http://<IP_ADDRESS>:4000
  501 28803 28576   0  5:14PM ttys007    0:34.92 MiqEmsRefreshCoreWorker id:<PHONE_NUMBER>021, queue: ems_1000000000002
  501 28805 28576   0  5:14PM ttys007    0:32.20 Vmware::InfraManager::RefreshWorker id:<PHONE_NUMBER>022, queue: ems_1000000000002
  501 28807 28576   0  5:14PM ttys007    0:21.13 Vmware::InfraManager::EventCatcher id:<PHONE_NUMBER>023, queue: ems_1000000000002
  501 28812 28576   0  5:14PM ttys007    1:06.90 MiqVimBrokerWorker id:<PHONE_NUMBER>024

@matthewd Please review
cc @akrzos

As the pid ends up in the worker table anyway, we can probably skip the id, and just focus on "extra info" -- leaving identity to the pid, as PostgreSQL, for example, does with its processes.


Whoas should support Redis as a queue provider

Something with persistence but still pretty simple

Related to lookout/deploydb#14

I think this issue is closed by mistake. Reopening..


chore: update deps

Coverage remained the same at 100.0% when pulling f4f1f18119eda0aadd5dd0910b221d0a14261f29 on update-deps into 0f8d7251e8274f7e1d7e53f486ee7ea3c5ee95b0 on master.

Coverage remained the same at 100.0% when pulling f4f1f18119eda0aadd5dd0910b221d0a14261f29 on update-deps into 0f8d7251e8274f7e1d7e53f486ee7ea3c5ee95b0 on master.


PVR support for ASTC formats.

I believe only V3 files support ASTC. We need to support.

Looks like working except the HDR astc pvr V3 files are not loading.


SWS-94: Add multiple layouts for graphs.

Instead of just the one layout, add multiple layout options(3) for the graphs selectable on a toolbar.

There are still two other layouts that need to be added: cosa and klay (their configurations and libraries are more complicated). But nothing stopping this from being merged.
SWS-94

Pull Request Test Coverage Report for Build 240

70 of 99 (70.71%) changed or added relevant lines in 12 files are covered.
18 unchanged lines in 4 files lost coverage.
Overall coverage increased (+1.6%) to 35.314%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/CytoscapeLayout/graphs/DagreGraph.ts
3
4
75.0%

src/components/CytoscapeLayout/graphs/GraphType.ts
0
1
0.0%

src/components/CytoscapeLayout/graphs/BreadthFirstGraph.ts
3
4
75.0%

src/components/CytoscapeLayout/graphs/GraphStyles.ts
2
3
66.67%

src/components/CytoscapeLayout/graphs/ColaGraph.ts
3
4
75.0%

src/components/CytoscapeLayout/CytoscapeLayout.tsx
2
5
40.0%

src/pages/ServiceGraph/CytoscapeToolbar.tsx
16
21
76.19%

src/pages/ServiceGraph/ServiceGraphPage.tsx
20
26
76.92%

src/components/About/AboutUIModal.tsx
14
24
58.33%

Files with Coverage Reduction
New Missed Lines
%

src/components/About/AboutUIModal.tsx
3
52.0%

src/components/CytoscapeLayout/CytoscapeLayout.tsx
4
27.78%

src/services/Api.ts
5
66.67%

src/pages/ServiceGraph/ServiceGraphPage.tsx
6
58.82%

Totals

Change from base Build 237:
1.6%

Covered Lines:
327

Relevant Lines:
753

💛  - Coveralls

I did squash and rebase. I have no idea why it shows these commits that are already merged.

I can try moving this commit to a new PR.

Closing in favor of: https://github.com/swift-sunshine/swsui/pull/104


Run 'git standup' from any subdirectory of a git repo

@kamranahmedse please review whenever you have some time :smile:

@kamranahmedse any chance you could take a look at this? Thanks!

Thanks 👍


Fix transitions and clipping

#77 Entrance transitions were completely broken, as was all dynamic clipping. Upgrading to<EMAIL_ADDRESS>fixed this; however, that upgrade necessitated upgrades to<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Also cleaned up a related hack (from #74) that is not needed anymore, and some bogus props that made debugging more confusing :P

@chrisbolin approved pending getting CI to pass

released as<EMAIL_ADDRESS>


add and document new ci/cd abstraction

Fixes #4
Fixes #35
Related to #30
Alternative to #59

/brig run


Flutter plugin link updated.

To configure Flutter plugin in Android Studio the link has been updated
I have replaced the Flutter plugin download link for Android Studio IDE it was misplaced by Visual Studio Code plugin Link.
By updating the link, Beginners will get correct information to download the Flutter plugin in Android Studio IDE.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@sfshaza2 any updates?

Just curious, the plugin is compatible with both Android Studio and Intellij, so why is the separation actually required?

cc @jacob314 to check if this change is reasonable.

plugin

I don't understand

cc @jacob314 to check if this change is reasonable.

I believe this pull request should be closed as I believe the fix made by https://github.com/flutter/flutter/commit/32122480b5cff211cb6cbe545d22d143af121f25 resolves the issue this pull request was addressing while making it clearer that one Flutter plugin supports both IntelliJ and Android Studio.
Adding a link to https://docs.flutter.dev/get-started/editor?tab=androidstudio from the readme could be reasonable but I would keep in separate from the links pointing to the plugins for VSCode and Android Studio and I would add a link to https://docs.flutter.dev/get-started/editor?tab=vscode as well for consistency.

@jacob314 no doubt but if user/newbie want to setup Flutter in Android Sfudio it should redirect it to Android Studio setup page, and if the user want to setup flutter on VS Code the individual link should redirect to VS Code specific page.
With the help of two different links the user will setup the System with ease rather than going and searching for other.

@yashjani01 I support adding a link for Android Studio setup instructions as well as a link to the Android Studio/ IntelliJ plugin. The problem is right now this CL has an IntelliJ link that goes to the plugin for both Android Studio and IntelliJ and an Android Studio link that goes to the android studio setup instructions. I would suggest renaming the link labeled [IntelliJ] to be [Flutter IntelliJ / Android Studio Plugin] to reduce confusion. Right now it is not clear why the one link is to the plugin while the other is to setup instructions.

@jacob314 I'll rename it..

@jacob314 Changes are successfully done.

@yashjani01 Is this still a PR you are interested in? If you merge the conflicts and apply the suggested edits I can land it.

@yashjani01 Is this still a PR you are interested in? If you merge the conflicts and apply the suggested edits I can land it.

Yes, I'll do today.

I'm going to close this PR for now, since it's been a while with no updates, please if you are still interested in fixing this please submit a new PR. Thanks!

**@guidezpl please add cla i think it is been removed by you on => ** "[guidezpl] removed the cla: yes label on May 1, 2022"


🐛 [firebase_app_check] Allow manual setting of app check token in debug mode

In the Android and iOS sections of the App Check docs, there are instructions to configure the App Check debug provider for unit testing in a CI environment. Links:
https://firebase.google.com/docs/app-check/android/debug-provider#ci
https://firebase.google.com/docs/app-check/ios/debug-provider#ci
There are no similar instructions or available methods for App Check in flutter. This makes it difficult to perform an automated test on an app that requires App Check in multiple environments, such as real devices or emulators in Firebase Test Lab. In these situations, a token is printed to console and must be manually added to the Firebase console for each device, instead of all sharing the same token.
The feature should be added to the flutter package as simply as possible. For example:
FirebaseAppCheck.instance.setDebugProviderToken(MY_TOKEN);

@jt274
FirebaseAppCheck.instance.setDebugProviderToken(MY_TOKEN);

This method will allow us to simplify the use of the same token in a project with many developers.
Adds token by token (each developer generating one), it's a bad way.

Any updates or workarount?

Hey folks, this is actually a duplicate of this issue: https://github.com/firebase/flutterfire/issues/11719
Could you please add your thumbs up on that issue. We are considering this feature so it is worth your time. Thanks 🙏


npm start with autoreload

:clipboard: Description
In TUTORIAL.md I need to start and stop npm server every time to load new changes? That's cumbersome. Is there any autoreload mechanism for /services/?

Yea… the frontend reloads when it changes, but it doesn't pick up changes to the badge examples until npm run examples is run again. If that happened automatically, that's something I would find quite handy.
The services do not reload either, though I haven't found that to be a significant problem since I do most of my work through the test runner.
Do you mean live editing of TUTORIAL.md? That's something else entirely.

I followed the tutorial and found it too cumbersome to restart server on every change to example service. nodemon is good, but it keeps reloading all the time. Probably because vim updates some temporary file there.

How were you testing it?

I opened #3401 which adds nodemon. I tweaked the config a bit – it is only watching .js files – though it may be necessary to ignore some more files. The verbose option is on, so it should print what is triggering the reload.
If you take it for a spin and notice anything else that needs adjusting, let me know!


Debugging in chrome does not work

After long pause i return to my app and try to update to latest version. I have some bugs, but i can´t debug it, because chrome debugger does not work now.
I enable remote debugging in devmenu, chrome tab is open with message like «Debugger session ... is active», but console is empty, debugger keyword not work and debugger not pause on exceptions.
How i update my app:

Install new version
Fix issues (use react instead of react-native, etc)
react-native upgrade

Additional Information

React Native version: update from 0.22 to 0.35 (also i try 0.34)
Platform: iOS
Operating System: macOS Sierra

I would try restarting everything in your dev environment. After that, the first question I would ask is whether it's this specific app or your React Native setup, and to figure that out I would see, can you reproduce this problem on a blank app that you create?

Yes, i have same error on blank app (react-native init).

That is strange. Either something is borked on your particular install of React Native or you are doing something unusual without realizing it, because in general the debugger does work on new apps. I would try this on a different machine to be sure you are doing the right steps. If that does not work then really you just have to restart things and reinstall them - I don't know a better way. Make sure you kill any lingering processes - restarting your computer, watchman, the packager, all of these are good things to restart. Sorry I don't have a more intelligent answer here.

Oh, i restart computer and now everything is ok.
Thank you very much, @lacker!

Turning it off and on again baby! The bugfixing technique of champions.


[Snyk] Security upgrade setuptools from 39.0.1 to 65.5.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

requirements-doc.txt

Vulnerabilities that will be fixed
By pinning:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

441/1000  Why? Recently disclosed, Has a fix available, CVSS 3.1
Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-SETUPTOOLS-3113904
setuptools:  39.0.1 -> 65.5.1
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)

Codecov Report
Base: 83.79% // Head: 83.86% // Increases project coverage by +0.06% :tada:

Coverage data is based on head (9ba039f) compared to base (d220f2e).
Patch coverage: 81.08% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #30      +/-   ##
==========================================
+ Coverage   83.79%   83.86%   +0.06%
==========================================
  Files          40       40
  Lines        2487     2497      +10
  Branches      373      373
==========================================
+ Hits         2084     2094      +10
  Misses        297      297
  Partials      106      106

Impacted Files
Coverage Δ

cowbird/constants.py
91.95% <ø> (ø)

cowbird/handlers/impl/geoserver.py
75.00% <42.85%> (ø)

cowbird/handlers/impl/magpie.py
77.38% <66.66%> (ø)

cowbird/api/webhooks/views.py
92.06% <71.42%> (+0.26%)
:arrow_up:

cowbird/__meta__.py
100.00% <100.00%> (ø)

cowbird/app.py
92.85% <100.00%> (+0.85%)
:arrow_up:

cowbird/handlers/__init__.py
100.00% <100.00%> (ø)

cowbird/handlers/handler.py
89.74% <100.00%> (+0.85%)
:arrow_up:

cowbird/handlers/handler_factory.py
97.05% <100.00%> (ø)

cowbird/utils.py
71.80% <100.00%> (+0.21%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add support for scrollable grids

We now support (vertically) scrollable grids with viewporting. If the
scroll doesn't reveal any new rows, we execute the scroll with a repaint
(i.e., no layout). If the scroll reveals a new row, we trigger a layout
to change the set of materialized children in the viewport.

I'm very excited to see this.  lgtm, but @Hixie is of course a better reviewer here and likely worth waiting for.

LGTM, I think. This is some dark magic.


Fixing the missing searchbox bug

Coverage increased (+0.2%) to 81.584% when pulling afe0a64532564d35bcf0a1c33095261ce61a4d66 on mistercrunch:fix_searchbox into 0bedaed3676c2185aff8f0de52f07fd40b45b985 on airbnb:master.

Coverage remained the same at 81.627% when pulling 168bc4a98f12ba6bdd158d2e5196dc0c9a685af5 on mistercrunch:fix_searchbox into 673cce9e561d9f264d70efb0ac2449fab64d05d1 on airbnb:master.


Sort nodes in ascending order for HighNodeUtilization

Sort nodes in ascending order for HighNodeUtilization.
This fixes the issue reported in https://github.com/kubernetes-sigs/descheduler/issues/756 and a part of issue in https://github.com/kubernetes-sigs/descheduler/issues/725

hi @dineshbhor  thanks for bring this

@JaneLiuL Thanks for the comment. I kept the logic the same as LowNodeUtilization, just in ascending order.
As the discussion proceeds the approach is still not decided so for the time being until we finalize the approach we can keep the same behavior as LowNodeUtilization just the order is ascending.

Hello @JaneLiuL, @damemi
Thanks for taking the time to review this PR.
We have 2 GKE clusters (dev-670, prod-1200 approx) for which we are trying to introduce a descheduler along with an inbuild managed cluster autoscaler to reduce the overall cost (HighNodeUtilization).
This bug is a kind of blocker for that work. If possible it would be really helpful to get this PR reviewed/merged/released sooner.
Thanks in advance 🙇
Dinesh

Thanks, @ingvagabund for the comment. Fixed it.
@damemi

Please add a config setting for this so it isn't turned on by default, and also test cases to cover it. Thanks!

Config setting for this so it isn't turned on by default
Correct me if I am wrong.
This was a bug in existing behavior which will be fixed by this PR. So there is no change in the behavior from the user's perspective. So in my opinion there is no need to introduce a config setting. If I misunderstood your request please share more information.

Agree with @dineshbhor this is a bug. On the other hand the unit test comes handy :)

@dineshbhor ah sorry, my mistake, I was thinking this was more part of the feature request from https://github.com/kubernetes-sigs/descheduler/issues/725. A unit test will still be good to have though

Thanks, @ingvagabund @damemi for the comments. I added the unit tests.
Please check when you get time. 🙇
I also would like to know what is the release policy for descheduler and when the new image can be available? Please direct me to the available related document if possible.
Thank you 🙇

@dineshbhor Thank You for addressing the comments. Would you mind squashing before the final approval?

@dineshbhor Thank You for addressing the comments. Would you mind squashing before the final approval?

Thanks, @ingvagabund for the comment. Done

https://github.com/kubernetes-sigs/descheduler/issues/735 for a start

01:00 UTC Wednesday 30th March 2022: Week 12 — Code Freeze

Oh, Tomorrow is code freeze. I hope to get this PR included in the next release. 🙇
Thanks all for the review.

/approve
/lgtm

@dineshbhor we don't cut the release for descheduler until after the upstream Kubernetes release, so code freeze isn't a problem, this will make it in to the next descheduler release

Thanks, @damemi for sharing the information. 🙇


Add key button in AnimationPlayer is not entirely clickable.

Windows 10 Home Edition
Nvidia GTX 950
Godot 3.0 Alpha
Issue description:
Only the extreme right side of the add key marker is clickable.  I almost thought the add key was not working at all.  But I am able to consistently repeat the action.
Steps to reproduce:
Just give it a go.

Fixed by #13014


[TO-PR] [tiktok] Privacy Report Submission.

name: Tiktok
ratings:
locationTracking: 1
dataRetention: 0
userControl: 1
darkPatterns: 1
crossSiteTracking: 0
summary: "/privacy-report-card/details/tiktok"
reference: "https://example.com/privacy"
category: "privacy-report-detail"
Tiktok's Privacy Policy - Summary

and another one

This issue was automatically created from an API call.


[v1.1][F11-B1] CRM-Book

Changelog: This PR Contains

Updates to Developer Guide
Separating of leads and contacts
Adding placeholder command for LinkedIn login

Reviewing now; but a few things to take note for next submission (i.e v1.2 onwards)
Comment here when you are ready for review and give a summary of the changes -- i.e
"Add xxx function"
"Change xxx", etc
So I can see what new changes there are :)

@karrui I wanted to do the alias commands on a weekly basis so that I am able to do a code enhancement on a weekly basis.

@davidten @Sheikh-Umar @WoodyLau @zhuleyan @A0155428B Please note the new post about defining your major and minor enhancements - https://github.com/nus-cs2103-AY1718S2/forum/issues/28
Namely, a major enhancement should span multiple stories, with stories spanning multiple tasks, and a minor enhancement should be a single story. Make sure your issue tracker and milestones are properly set up before the tutorial.
A demo issue tracker has also been released for your perusal. You may also find it at https://github.com/MyTAOrg/DemoGradle/issues
@Sheikh-Umar Your alias command should not span multiple weeks. It is an extremely minor enhancement and should be all done at once. Last week's enhancement by you was not satisfactory. Please finish up the alias command by this week if you are using it as your minor enhancement.


Add 'encapsulated' boolean parameter (default: true) to rich.console.export_svg method

Type of changes

[ ] Bug fix
[ ] New feature
[ ] Documentation / docstrings
[ ] Tests
[x] Other

Checklist

[x] I've run the latest black with default args on new code.
[x] I've updated CHANGELOG.md and CONTRIBUTORS.md where appropriate.
[ ] I've added tests for new code.
[x] I accept that @willmcgugan may be pedantic in the code review.

Description

Adds a (filterable) warning when the unique_id parameter added by #2537 is used.
Adds an encapsulated parameter that is intended to provide a migration path towards the removal of the unique_id variable in future

(closing to clean up some stale branches and pull requests; commits recoverable with some git magic if-so-desired; I consent to these commits being merged if later considered valuable)


Update Documentation and Unit Tests for MLMD Component

Update Documentation and Unit Tests for MLMD Component
Description

Update README and sample DSPA to include information about optional MLMD Component
Add new Unit Test to verify MLMD Component deployment functionality is working.

How Has This Been Tested?

Run make test
Proofread README.md and dspa_all_fields.yaml

Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

/lgtm


Weighted Generalized Mean

This specifies an alternative method to coding the generalizaed mean. It is lower priority since the straightforward mathematics is already coded.
While the formula is well known and was implemented in this manner for the Mathematica code. The preference would be to utilize the coupled product and coupled power functions. This would then provide a foundation for the function within the coupled algebra context and incorporate the subtleties which arise regarding the variables kappa, alpha, and dimension. It is probably best to have the inputs include an option to specify either the risk_bias = -alpha kappa / (1 + dim kappa) or the alpha, kappa, and dim directly.
The functional specification is given in equation 3.15 of the Reduced Perplexity book chapter.

I'm closing this issue based on the discussion Thursday night. The function exists in the entropy file and will be moved functions file. The function was originally developed using the straightforward mathematical formulation which serves our current needs.


Add a provider for DynamoDB in Traefik v2

Do you want to request a feature or report a bug?
Feature
What did you expect to see?
Traefik v1 supports dynamic config generation for and from a DynamoDB service, i.e. it has a DynamoDB provider.
Now that the main changes for v2 are out, we can re-add previously supported providers, such as the one for DynamoDB.
The existing providers, as well as the code for the DynamoDB provider in v1.7, can be used for inspiration.

Hi,
I'd love to test and use it in production... Please consider DynamoDB as provider

Hi,
Any update on that would be highly appreciated!
Thanks!

Hello,
After some discussions with the team, we thought that it would be better to support the dynamodb provider as a provider plugin (available since Traefik v2.5).
For more details, check out the documentation available in the provider plugin demo repository: https://github.com/traefik/pluginproviderdemo
According to this, we will close this issue and decline #8542.
Thanks again for your interest in Traefik!


chore: upgrade pipelines

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jstrachan: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

pr
11b143ab3839148aee11cdd9a5dd9ae7ccd9c476
link
/retest

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


Readme-jokes is not working!

Yes, it's true, please do fix this, as a LOT of us have these jokes on our READMEs.

Thanks, @Adatta1276 and @Ankit-jailwal for pointing out. It has been fixed now.


Regonize Apache Ant for java section

Description
Add support for showing the java section in a repository where build.xml presents.

Thanks for contributing!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Tooling to force equal positions of nodes in distinct layers (Issue #30)

Following up on https://github.com/oxinabox/LayeredLayouts.jl/issues/30#issuecomment-1459509785, here's a possible implementation of the feature discussed there.
One thing to discuss is the API: should it be more flexible? More generally, we could imagine not wanting to force equal positions in the canonical node ordering, but of some permutation of that. The current implementation doesn't allow that.
One possible API for that could be something like force_equal_layers = [(i,  [n1_i, n2_i, ...]) => (j, [n1_j, n2_j, ...]) where i and j refer to layer positions and n1_i/n1_j, n2_i/n2_j, etc. refer to nodes within that layer.
I didn't add any tests at the moment, but am happy to do so once we settle on an API.

Codecov Report

Merging #31 (9df53fc) into main (f2d6ec6) will decrease coverage by 8.00%.
The diff coverage is 20.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main      #31      +/-   ##
==========================================
- Coverage   91.17%   83.18%   -8.00%
==========================================
  Files           4        4
  Lines         204      226      +22
==========================================
+ Hits          186      188       +2
- Misses         18       38      +20

Impacted Files
Coverage Δ

src/layering.jl
96.22% <ø> (ø)

src/zarate.jl
77.70% <20.00%> (-11.19%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

I think the API might be flexible enough.
If people want more, they can always work it out by hand and use the other ordering argument.
Or post-process their results
Lets see the test.
We just do visual reference tests in this package so it should be easy enough to write

There doesn't seem to be a test that actually uses the new keyword?

Argh, good catch, dunno how that happened; maybe I accidentally dropped it in a rebate. Will fix.

Bump: this should be good to merge now (and would simplify my life a bit if merged).

Bump: fixed merge conflicts.

I'll just bump here again gently; just to keep it going before we both forget again.
I checked the tests on current master locally: they fail there as well (again on sankey_3twos), so I don't think the changes here are causing the failures.

Bump :). Just need to know what you'd like me to do about the sankey_3twos test failures.
As I mentioned, I can reproduce them locally on master, so they don't seem related to anything here.

Sorry, I am just rather busy.
This looks fine now, api and method-wise. Minor stylistic comments.
You will have to rebase this again sorry on top of the bug-fix PR that was merged.
If you can mark the sankey test as @test_broken and open an issue about it and cross link that issue there, that would be great.
then we can merge this.

If you can mark the sankey test as @test_broken and open an issue about it and cross link that issue there, that would be great.

Unfortunately, afaict @plottest from VisualRegressionTests.jl does not allow one to mark a test as broken, i.e., there isn't a @plottest_broken variant, so it would be a little tricky to do this. I can mark the whole block @test_broken, but then it just fails unconditionally since the test-set doesn't evaluate to a boolean.
Preferences?

Okay, in the interest of not dwelling on details, I just commented out the sankey_3twos test and replaced it with a `@test_broken false´.
I'll open an issue about it now.


NIFI-6019 Removes "Trusted Hostname" property from InvokeHTTP processor

Changes in this PR:

Removes "Trusted Hostname" property from InvokeHTTP processor

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically master)?

[X] Is your initial contribution a single, squashed commit?

For code changes:

[X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Thanks for submitting this PR. Can you please add some unit tests demonstrating what happens when a flow which contains this property populated (i.e. set the property value when configuring the TestRunner) tries to run on this processor? We try to enforce backward compatibility, and while this change is definitely necessary, there needs to be a good story (documentation, process, explanation) around this change for users to maintain their existing flow behavior.
I would suggest adding an explanation of why the property no longer exists and how to resolve a problem encountered by upgrading to the InvokeHTTP processor documenation (perhaps in Additional Details) and perhaps adding a section in the User Guide about properly configuring/selecting a truststore for use in a SSLContextService.

In the process of writing the unit test, I found the processor would throw exceptions after the property was removed:
java.lang.IllegalArgumentException: Unexpected char 0x20 at 7 in header name: Trusted Hostname
        at okhttp3.Headers$Builder.checkNameAndValue(Headers.java:313)
        at okhttp3.Headers$Builder.add(Headers.java:271)
        at okhttp3.Request$Builder.addHeader(Request.java:177)
        at org.apache.nifi.processors.standard.InvokeHTTP.setHeaderProperties(InvokeHTTP.java:1008)
        at org.apache.nifi.processors.standard.InvokeHTTP.configureRequest(InvokeHTTP.java:970)
        at org.apache.nifi.processors.standard.InvokeHTTP.onTrigger(InvokeHTTP.java:761)
        at org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
        at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1162)
        at org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:213)
        at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:117)
        at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

The error seems clear enough:  the property is treated as a dynamic property after this change, and the processor tries to send it as a header.  The header name contains a space so the invocation goes boom.
I verified this behavior explicitly via a fresh installation + flow creation + upgrade.
So, removing the property will cause new failures, which seems like breaking backward compatibility.  I'm not sure the best approach for resolving the issue, leaving this comment here and closing the PR.


Stripe API - specific error handling

Created a dict, controller function and model function for generating a specific error message based on http status and error type; failures due to card errors will be generated based on key/value entries in the card_error_message dict.

Looks great! 👍


Make the @yamada-ui/switch component headless

script: make-component-headless
package: @yamada-ui/switch
Description
Currently, the @yamada-ui/switch component has minimal styles set within the component's source code.
We want to make this style transferable to the theme and make the component headless, enabling more flexible UI customization.
Problem Statement/Justification
By making the @yamada-ui/switch component headless, we can achieve more flexible styling tailored to the project.
Proposed Solution or API
The styles within the component are mostly defined by css: CSSUIObject and set to a prop named __css. We will transfer these styles to the packages/theme/src/components.
The code below is just an example and not the actual code.
packages/components/input/src/input-group.tsx
const css: CSSUIObject = {
- width: "100%",
- display: "flex",
- position: "relative",
  ...styles.container,
}

packages/theme/src/components/input.ts
baseStyle: {
  container: {
+   width: "100%",
+   display: "flex",
+   position: "relative",
  },
  field: {
    width: "100%",
    minWidth: 0,
    outline: 0,
    position: "relative",
    appearance: "none",
    transitionProperty: "common",
    transitionDuration: "normal",
    _disabled: {
      opacity: 0.4,
      cursor: "not-allowed",
    },
  },
  element: {
    color: ["blackAlpha.600", "whiteAlpha.700"],
  },
},

[!TIP]
In cases where the styles within the component are dynamically changed, there may be instances where it is not possible to transfer the styles to the theme.
In such cases, it needs to be discussed in this issue. Please feel free to send comments to this issue.

Additional Information
The @yamada-ui/switch component exists in packages/components/switch/src. You need to check all the components in this folder and if they contain styles internally, you need to modify them.
This change could have a significant impact on projects using Yamada UI, so we will work on it within the scope of v2.0.
Please create the branch for working on this issue from the remote branch v2.0, and direct your pull requests to the v2.0 branch as well.
Please select major for the changeset and create a pull request.

can i try this issue?

@lCyou
Hi, thanks for the comment!
Yes, pls.

Fixed #1922