Add adwaita-qt & qgnomeplatform

Motivation for this change
elementary uses this to improve the look and feel of qt applications.
(It's default in Fedora for Gnome too...)
Screenshots
Before:

After:

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option 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"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

cc @jtojnar

@GrahamcOfBorg build adwaita-qt qgnomeplatform

Success on x86_64-linux (full log)
Attempted: adwaita-qt, qgnomeplatform
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/0mg19qh5906ri8lj0vjy24jdjmp65z42-qgnomeplatform-0.4
shrinking /nix/store/0mg19qh5906ri8lj0vjy24jdjmp65z42-qgnomeplatform-0.4/lib/qt-5.11/plugins/platformthemes/libqgnomeplatform.so
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/0mg19qh5906ri8lj0vjy24jdjmp65z42-qgnomeplatform-0.4/lib
patching script interpreter paths in /nix/store/0mg19qh5906ri8lj0vjy24jdjmp65z42-qgnomeplatform-0.4
checking for references to /build in /nix/store/0mg19qh5906ri8lj0vjy24jdjmp65z42-qgnomeplatform-0.4...
postPatchMkspecs
postPatchMkspecs
/nix/store/hbxsnhlbxda015137kkhf9rzyzz4p606-adwaita-qt-1.0
/nix/store/0mg19qh5906ri8lj0vjy24jdjmp65z42-qgnomeplatform-0.4

Success on aarch64-linux (full log)
Attempted: adwaita-qt, qgnomeplatform
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/4560mlls19wi1dnh0w09cf4bdfrs88ws-qgnomeplatform-0.4
shrinking /nix/store/4560mlls19wi1dnh0w09cf4bdfrs88ws-qgnomeplatform-0.4/lib/qt-5.11/plugins/platformthemes/libqgnomeplatform.so
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/4560mlls19wi1dnh0w09cf4bdfrs88ws-qgnomeplatform-0.4/lib
patching script interpreter paths in /nix/store/4560mlls19wi1dnh0w09cf4bdfrs88ws-qgnomeplatform-0.4
checking for references to /build in /nix/store/4560mlls19wi1dnh0w09cf4bdfrs88ws-qgnomeplatform-0.4...
postPatchMkspecs
postPatchMkspecs
/nix/store/rlg2k5w0r1nx4dqm5z834msdxg1m4g0q-adwaita-qt-1.0
/nix/store/4560mlls19wi1dnh0w09cf4bdfrs88ws-qgnomeplatform-0.4

Success on aarch64-linux (full log)
Attempted: adwaita-qt, qgnomeplatform
Partial log (click to expand)
/nix/store/rlg2k5w0r1nx4dqm5z834msdxg1m4g0q-adwaita-qt-1.0
/nix/store/4560mlls19wi1dnh0w09cf4bdfrs88ws-qgnomeplatform-0.4

Success on x86_64-linux (full log)
Attempted: adwaita-qt, qgnomeplatform
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/hbxsnhlbxda015137kkhf9rzyzz4p606-adwaita-qt-1.0
shrinking /nix/store/hbxsnhlbxda015137kkhf9rzyzz4p606-adwaita-qt-1.0/lib/qt-5.11/plugins/styles/adwaita.so
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/hbxsnhlbxda015137kkhf9rzyzz4p606-adwaita-qt-1.0/lib
patching script interpreter paths in /nix/store/hbxsnhlbxda015137kkhf9rzyzz4p606-adwaita-qt-1.0
checking for references to /build in /nix/store/hbxsnhlbxda015137kkhf9rzyzz4p606-adwaita-qt-1.0...
postPatchMkspecs
/nix/store/hbxsnhlbxda015137kkhf9rzyzz4p606-adwaita-qt-1.0
/nix/store/0mg19qh5906ri8lj0vjy24jdjmp65z42-qgnomeplatform-0.4

Success on x86_64-linux (full log)
Attempted: adwaita-qt, qgnomeplatform
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/m9lfa8y7vmlbpsyp5idrcn1a5s018ihj-qgnomeplatform-0.4
shrinking /nix/store/m9lfa8y7vmlbpsyp5idrcn1a5s018ihj-qgnomeplatform-0.4/lib/qt-5.11/plugins/platformthemes/libqgnomeplatform.so
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/m9lfa8y7vmlbpsyp5idrcn1a5s018ihj-qgnomeplatform-0.4/lib
patching script interpreter paths in /nix/store/m9lfa8y7vmlbpsyp5idrcn1a5s018ihj-qgnomeplatform-0.4
checking for references to /build in /nix/store/m9lfa8y7vmlbpsyp5idrcn1a5s018ihj-qgnomeplatform-0.4...
postPatchMkspecs
postPatchMkspecs
/nix/store/hbxsnhlbxda015137kkhf9rzyzz4p606-adwaita-qt-1.0
/nix/store/m9lfa8y7vmlbpsyp5idrcn1a5s018ihj-qgnomeplatform-0.4

Success on aarch64-linux (full log)
Attempted: adwaita-qt, qgnomeplatform
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/nalhlvjv4xv7pdmxhpyp1hbmzsby2914-qgnomeplatform-0.4
shrinking /nix/store/nalhlvjv4xv7pdmxhpyp1hbmzsby2914-qgnomeplatform-0.4/lib/qt-5.11/plugins/platformthemes/libqgnomeplatform.so
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/nalhlvjv4xv7pdmxhpyp1hbmzsby2914-qgnomeplatform-0.4/lib
patching script interpreter paths in /nix/store/nalhlvjv4xv7pdmxhpyp1hbmzsby2914-qgnomeplatform-0.4
checking for references to /build in /nix/store/nalhlvjv4xv7pdmxhpyp1hbmzsby2914-qgnomeplatform-0.4...
postPatchMkspecs
postPatchMkspecs
/nix/store/rlg2k5w0r1nx4dqm5z834msdxg1m4g0q-adwaita-qt-1.0
/nix/store/nalhlvjv4xv7pdmxhpyp1hbmzsby2914-qgnomeplatform-0.4

Thanks.


Don't report duplicate folding ranges

I’m not entirely sure when this started occurring but when retrieving folding ranges for e.g.
func foo() {
    print("someText")
}

SourceKit reports the folding range of "someText" twice: Once as the body of the call to print and once as the body of the first argument. Each folding range on its own makes sense because you might want to collapse either all arguments or only a single argument. But it doesn’t make sense to report the same range twice and this is causing SourceKit-LSP tests to fail.

@swift-ci Please test


Update README.md

conatiner is not a thing
Type of change

[ ] New feature
[ ] Bug fix
[X] Security patch
[ ] Documentation update

Description
Correct @Johannestegner spelling mistakes
Related issue

Motivation

Checklist

[X] I have read the CONTRIBUTING document.
[X] I have read and accepted the Code of conduct
[X] I have accepted to be king of the world
[ ] Eslint passes.
[ ] Jest tests passes.
[ ] Documentation of new public methods exists.

LGTM!
Should probably create a CVE for this too!


[WIP] list social media accounts

fix #125

@Kachulio1 a build was canceled + branch needs to be updated
https://dashboard.cypress.io/#/projects/qa7fe2/runs/1147/specs looks nice! How many social media accounts can we add?

Should we limit it to max 5 accounts?

@appinteractive nah, I was like: "Cool, I didn't try out the code but I'm curious how many accounts can we add?" I would limit the accounts and fix a problem that we don't have at the moment.

Closed in favour of https://github.com/Human-Connection/Human-Connection/pull/237


Where are hardware-specific drivers, such as those for STM32?

Hello,
I got the drivers from the samples repo, but shouldn't they be included in this repo?
Thanks!

ST is in the process of integrating USBX with their MCU offering.  Please contact ST for availability and schedule.

For example, in the samples repo, I can see files such as _ux_hcd_stm32_asynch_schedule.c with the following comment:
/**************************************************************************/
/*                                                                        */
/*  FUNCTION                                               RELEASE        */
/*                                                                        */
/*    _ux_hcd_stm32_asynch_schedule                       PORTABLE C      */
/*                                                           6.1          */
/*  AUTHOR                                                                */
/*                                                                        */
/*    Chaoqiong Xiao, Microsoft Corporation                               */
/*                                                                        */
/*  DESCRIPTION                                                           */
/*                                                                        */
/*    This function schedules a new transfer from the control/bulk lists. */
/*                                                                        */
/*  INPUT                                                                 */
/*                                                                        */
/*    hcd_stm32                           Pointer to STM32 controller     */
/*                                                                        */
/*  OUTPUT                                                                */
/*                                                                        */
/*    TRUE or FALSE                                                       */
/*                                                                        */
/*  CALLS                                                                 */
/*                                                                        */
/*                                                                        */
/*  CALLED BY                                                             */
/*                                                                        */
/*    STM32 Controller Driver                                             */
/*                                                                        */
/*  RELEASE HISTORY                                                       */
/*                                                                        */
/*    DATE              NAME                      DESCRIPTION             */
/*                                                                        */
/*  05-19-2020     Chaoqiong Xiao           Initial Version 6.0           */
/*  09-30-2020     Chaoqiong Xiao           Modified comment(s),          */
/*                                            resulting in version 6.1    */
/*                                                                        */
/**************************************************************************/

So those files are from Microsoft, not ST. My question is what aren't they included in this repo?

Closing this issue.  Feel free to reach out if you have additional questions.

I'm sorry, but my question hasn't been answered. Why aren't hardware-specific files, such as the _ux_hcd_stm32_asynch_schedule.c file I mentioned, included in this repo? It's a fair question.
The USB stack repo from Micrium, for example, includes hardware-specific files.

@trinhnhatnam, ST already added USBX support (with proper drivers) for their STM32H7 family MCUs: https://www.st.com/en/embedded-software/x-cube-azrtos-h7.html
And ST is in the process of expanding such support into more MCUs (such as their L4 family, F7 and F4 family MCUs).
These drivers are maintained by ST, therefore Microsoft does not re-distribute the drivers in Azure RTOS repo.

Can you forget about what ST is doing for a moment?
I'm asking about the hardware-specific files for USBX that I see in the "samples" repo. Those are clearly maintained by Microsoft, with proper comments and versioning. Why aren't they in this repo?

@trinhnhatnam Let me try to clear things up here. Microsoft doesn't really want to write and maintain drivers and BSPs for hundreds of different devices, which is why we've partnered with a handful of popular semiconductor manufacturers. Microsoft wrote drivers to get those samples working on real hardware. We got the samples up on github for people to start using right away while ST, Renesas, NXP, Microchip, etc. work on integrating Azure RTOS into their IDEs. The semis are going to be providing the drivers for their hardware. They want to be the one-stop-shop for developers using their devices (e.g. you download stm32cube IDE and everything is in there - Azure RTOS, drivers, sample code, etc). They want to "curate" the "developer experience."
You're not the only one that has asked about USBX drivers. I'm an Azure RTOS developer and I've asked if we're going to put drivers up on github. We have a lot of old drivers (from the Express Logic days), but that's just it - they're for older and obsolete devices. It's actually nice that the semis want to write and maintain the drivers, because they know their hardware much better than we do, so they can write drivers that take full advantage of all the hardware capabilities.

Why not put all those "old" and "obsolete" drivers up anyway? They're already available. They can help someone, like me, who tries to switch to AzureRTOS stuff. My devices are not new to wait for manufacturers to write "good" drivers for. For example, an ST device of mine is not an H7; I don't want to wait for ST to write something for it. I can tell you that your "obsolete" drivers really help me.
And if you worry about the obsoleteness, then put up a warning directing users to  semiconductor manufacturers for possible newer and better drivers.
And even if the semiconductor manufacturers are going to write all drivers from now on, I think Microsoft should make an effort to make this an independent product by trying to bring those drivers over to this repo. One obvious reason, in ST case, is that not everyone likes stm32cubeide, they may prefer IAR for example.
This is my humble opinion. You don't have to reply. Thanks @yuxin-azrtos and @goldscott.

@trinhnhatnam - I agree with you. The old drivers are helpful. But it's not my decision to put them up.


add Downsampling code

Added a process to downsample the target point cloud.

Changed ndt-cpu-single.cpp to ndt-cpu-single.hpp .
Added main.cpp and main_downsample.cpp.
main function has been changed to output the average processing time of 10 times, and the SVG file has been changed to output two files, one conventional and one plotting covariance.

LGTM !!


Track click through in algolia

Currently search results are not reporting click through in algolia, which means we don't quite know how effective the search is in meaningful results.

This has landed.


DEV-43: Add and apply prettier to the project

At the moment, the code is controlled by linter and it makes it quite nice and clean. But much better and useful is to have prettier installed as well and configure your editor to prettify your code automatically on save.
You can find more about prettier here: https://prettier.io/
Once prettier is installed, would be good to check all the existing files and apply prettier to all of them so the code becomes more structured and clean.
To work on this issue, please use a branch DEV-43 created from devel. When the work is finished - create a PR to the devel branch. At the end of each development circles, code from the devel branch (if everything is ok) goes to the master branch and deploys to production.

Hey, I have prettier in my VS code, shall I fix this?

Sorry, @AbhinavReddy-Dev, the PR for this issue is already merged.


Clarify build config in VS/IIS dev-time support topic

Fixes #9531
Internal Review Topic (Run the project section)
Thanks @Neutrino-Sunset for the issue.

Sounds like a VS issue. I'd wait for Bill to respond on the original issue before changing the docs here

Will do, but I guessed from the result of trying it that it is by-design ...

ping @BillHiebert

@shirhatti The commit is in ....
Follows up from the email with a single line that gives the reader a heads-up on the warning that VS will throw with a Release config and dev-time support.

@scottaddie Bill said offline that the remark ...

Debugging a Release build configuration with Just My Code and compiler optimizations results in a degraded experience (for example, break points aren't hit).

... is ok. That gives a dev a heads-up on the warning that they'll get from VS if they try to use dev-time support with a Release build config.
The other change here is trivial .......... if I got the commas in the right spots. 😝lol

@shirhatti I'm going to go ahead with this based on Bill's approval. If you would like me to make changes to it, hit me up ... you know how to find me. 😀


Busgraph unittesting (WIP)

Wondering if we should consider migrating verify_embedding "upstream" to minorminer?

That makes tons of sense.  I was thinking about duplicating the old find_clique_embedding stuff anyway, both to test against and to provide support for chimera graphs with t>8.

I'll look at moving dwave.embedding wholesale into minorminer, and patching up the imports to maintain backwards compatibility for everybody using dwave.embedding

IMO things like embed_bqm, unembed_sampleset and the chain break resolution methods make sense in dwave-system rather than in minorminer (not least because minorminer has no notion of a BQM/SampleSet). So I think that part of the dwave.embedding namespace makes sense to keep there.

Ah, yes, agreed.  I hadn't looked into the details yet.   I'm thinking:
polynomialembedder.py
chimera.py
pegasus.py
exceptions.py

Summary of private conversation: yes, but not on this ticket.

Test failure is an issue in dne.find_clique_embedding


Renaming IPWhiteList to IPAllowList

What does this PR do?
Renaming IpWhiteList to IpAllowList.

Motivation
Fixes #9437

More

[x] Added/updated tests
[x] Added/updated documentation

Additional Notes

Hello @Wambug and thanks for your contribution,
After a quick review, we saw that you missed renaming the ipwhitelist pkg itself and the corresponding source files. You also forgot to rename the menu item in the documentation (this should be done in the mkdocs.yaml).
Please, could you also ensure that the case is always the same as before? ipwhitelist should become ipallowlist, ipWhiteList should becomeipAllowList, and IPWhiteList should becomeIPAllowList.

sure lemme make the corrections👍

ok

anytime

The documentation still needs to be updated as it still talks about ipWhiteList everywhere

This PR has been merged on branch v3, and this PR has also updated the documentation content.
I think you are talking about the documentation of v2.

may i ask why this was done? what new functionality does allowlist provide over whitelist?
it just caused me many hours of work because of broken systems.. primarily when watchtower auto-updated traefik to :latest on not-so-critical-systems

Hello @mrambossek,
This is not expected, as you can see https://github.com/traefik/traefik/pull/10341 reintroduced the IpWhitelist middleware to ease migration.
Can you please open a dedicated issue and explain how to reproduce the issue?
Thanks!


Fix wording in README.md

Description
What changes are included in this pull request?
Reason

[ ] Bug fix
[ ] Feature enhancement
[ ] New feature
[x ] Documentation update
[ ] Upgrade
[ ] Other

Are you responding to a filed Issue? (bug report, feature request, documentation request, etc)

Testing
Aras Innovator

Major version:
Service pack(s):

Browsers

[ ] Internet Explorer 11
[ ] Firefox ESR
[ ] Chrome
[ ] Edge

Does this pull request include known issues?

Checklist

[ ] Did you confirm the Install Steps in the README are still correct?
[ ] If this PR adds or changes functionality, did you update the Usage Steps in the README?
[ ] Did you add your GitHub user name to the "Credits" section in the README?

Canceling this test PR


extract the number of accepted features, and total number of features in the detected object, over time

hi
is there any way to extract the number of accepted features, and total number of features in the detected object?
I want to plot it over time, (not only for one frame)
thanks

You would have to implement that feature. In the current UI, those numbers are only shown in the Statistic Panel and they are not published over ros...


[network] Upgrade yamux to v0.4.2 which is futures-0.3 compatible

Yamux-0.4.2 introduces new semantics on connection ownership through 2 objects - Connection and Control. Control is a cloneable type which can be used for opening new outbound substreams and for closing the connection. Connection on the other hand is a non-Clone/Copy type that is solely responsible for listening for inbound substreams. This is a welcome change, since it gives it a similar ownership model as mpsc queues.
To integrate this change, we also modify the connection upgrade protocol to run Identity exchange before "upgrading" to Yamux. IMO, this is better because we can upgrade network protocols at this level, right after Noise (which will be a part of the advertised address itself).

Cluster test results:
Feb 11 05:51:52.575 INFO Experiment Result: all up : 711 TPS, 847.5 ms latency, no expired txns

:umbrella: The latest upstream changes (presumably 630bd498e77e39941ea933d13198d4e7a01043d3) made this pull request unmergeable. Please resolve the merge conflicts.

@bors-libra r=phlip9

:pushpin: Commit 8780a10 has been approved by phlip9

:hourglass: Testing commit 8780a1077d6255d0b2c806863528fde9348e78f4 with merge 07cf4e6b5eaadef28598b38509233d1d6fe0da0d...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: phlip9
Pushing 07cf4e6b5eaadef28598b38509233d1d6fe0da0d to master...


Scala 2.13.4 (and 2.12.12)

Fixes #381

CI failure looks transient

@SethTisue Fixed, green now.


[PlutusIR] [Uniques] Added renaming

This splits the renamer into two parts:

internals
the user-facing API

Internals are then used in order to define the renaming procedure for Plutus IR terms. The motivation for that is that I started to change the way we deal with uniques and realized that at least some Plutus IR procedures (removeDeadBindings, for example) implicitly rely on global uniqueness (@michaelpj, please confirm or reject), so things started to break.
In any case we'll need a type checker for Plutus IR at some point, so it's nice to have a renamer.
Any suggestions on how to test the renamer are welcome (generators are not merged, we do not have usage analysis or a suitable Eq instance).

some Plutus IR procedures (removeDeadBindings, for example) implicitly rely on global uniqueness

Or maybe it's just due to
     -- it is important we run the two computations in the same Quote together, otherwise we might make
     -- names during compilation that are not fresh

but rename can help in that case as well. But only for closed types/terms, processing open terms is still a mess. I'm now thinking it's worth making runQuote and rename less efficient, but guaranteed to return types/terms with the unique of any bound variable being greater than the unique of any free variable. In any case, things in Quote are no longer supposed (the PR is coming) to be unique as per discussion in slack, so we should do something about it.
We're writing papers on wrong subjects. We should write a paper on name handling, that's way more tricky than everything else. Well, we should write a paper once we understand how to handle names.

Hmm, yes I think you're right.
Annoyingly, I don't recall why I say that PIR compilation does not produce a term with unique names, since it certainly runs in Quote. I think it might preserve the property, but the input usually doesn't have it.
So yes, I agree that we need a renamer, thanks for doing this.

Seems to be a bit slower, probably not so much that we would care to block it, but maybe worth noting and thinking about.

It's reproducible so I doubt it. I can try on my laptop (I'm running these on my desktop) but other than that unless you have a concrete reason the benchmarks shouldn't be affected and a way to demonstrate the problem, I don't buy that the benchmarks are wrong.

The only thing I changed that is not just renaming of Haskell functions/variables is that I made RenameM a newtype rather than a type. But that is supposed to be no-op, right?

If that is the case, I don't think it's anything interesting about our code, but it might be interesting - I will dig deeper.

My experience has been the the benchmarks vary wildly from run to run and it's very difficult to conclude anything after switching branches.

I can help debug things on your end if you're having trouble with the benchmarks, but it is not the case that they vary wildly from run to run here.

Comments addressed.

No brilliance has occurred to me.
Have you tried putting this in appropriate places in the PIR pipelines to check it doesn't break anything?

Have you tried putting this in appropriate places in the PIR pipelines to check it doesn't break anything?

In another branch (which lets the tests pass (they wouldn't pass otherwise)). I can add renaming here if you prefer. I'm not blocked, so we can keep this open for a while, so that you have time to figure out where to add renaming.

Just wondering, since it would be useful as a sanity check. I'm fine to put this in anyway.


feat: all posts link end with /

Both the canonical and RSS article URLs end with "/", for consistency with the standard, it is best to use "/" at the end of the article URL.
Otherwise, there will be an additional 308 redirect.

Yes.
You're right.
Besides your updates, I found that other links also need to have trailing slash in order to prevent unnecessary redirects.
Thanks for pointing this out.


[#2120] Support Update the RssConf while reload config from config file

What changes were proposed in this pull request?
Support Update the RssConf while reload config from config file
Why are the changes needed?
Fix: #2120
Does this PR introduce any user-facing change?
User can get the reconfigured value from dashboard.
How was this patch tested?
Tested by dashboard conf button.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 52.74%. Comparing base (d170004) to head (5b5ed5a).
Report is 3 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #2121      +/-   ##
============================================
+ Coverage     51.72%   52.74%   +1.01%
+ Complexity     3275     2912     -363
============================================
  Files           524      452      -72
  Lines         29833    23433    -6400
  Branches       2556     2237     -319
============================================
- Hits          15431    12359    -3072
+ Misses        13400    10238    -3162
+ Partials       1002      836     -166

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


about useWeb3Modal open method

Can the open method return a promise object, I need to perform the following actions after the connection

Open method only opens the modal, so awaiting it wouldn't solve the issue, however you can await user connection in 2 ways

If you are using web3modal with wagmi, check out https://wagmi.sh/react/hooks/useAccount hook, which gives you all the data about users connection state

If you are using modal in standalone mode without wagmi, you should already have access to WalletConnect client and can await connection on it i.e. as in this example https://docs.walletconnect.com/2.0/web3modal/standalone/installation#create-pairing-and-open-the-modal


A question about cache_dir

Dear author, would you please tell me what is this cache? thx a lot.
~/workspace/InstructRAG-main$ sh generate_rationale.sh
usage: inference.py [-h] [--dataset_name DATASET_NAME] [--rag_model {InstructRAG-FT,InstructRAG-ICL}]
[--model_name_or_path MODEL_NAME_OR_PATH] [--load_local_model] [--do_rationale_generation] [--n_docs N_DOCS]
[--output_dir OUTPUT_DIR] [--cache_dir CACHE_DIR] [--prompt_dict_path PROMPT_DICT_PATH] [--temperature TEMPERATURE]
[--max_tokens MAX_TOKENS] [--seed SEED] [--max_instances MAX_INSTANCES]
inference.py: error: argument --cache_dir: expected one argument

I think I have fixed this problem. So vllm needs to download the models manually instead of automatically?

Hi @NoW0NDER, many thanks for bringing this up! The argument --cache_dir is actually optional, and I've updated the script accordingly. Let me know if you have any further questions.


Treat Carthage path as vendored

Hi, I have Carthage dependency in my project. My project is written in Swift, but the vendored dependency is Obj-C. That results in Github treating my project as Obj-C.
Carthage is a framework manager for iOS/Swift: https://github.com/Carthage/Carthage

There are only 2 repositories with a Carthage dependency on GitHub: https://github.com/search?p=1&q=Olivier+Halligon+path%3Acarthage&ref=searchresults&type=Code&utf8=✓
@arfon Should there be a minimum requirement on in-the-wild usage for vendored paths/files?

@pchaigno thanks for looking into it. Your search term includes 'Olivier Halligon' (@AliSoftware) which shows only Carthage frameworks from this single author. It showed the usage of the OHHTTPStubs. If we search for the import keyword instead we can see more hits:
https://github.com/search?utf8=✓&q=import+path%3Acarthage&type=Code&ref=searchresults
Cartage dependencies are created in the Carthage folder located in the project root. I think they represent 3rd-party/vendored code and should not influence language statistics of the Github repository that includes them.

Oh! my bad, I though he was the author of the framework manager :/
I guess it's okay then :-)

Nope, I'm a contributor of another dependency manager (CocoaPods) that exists since longer than Carthage, but I've nothing to do with Carthage (I don't even use it myself, I just made my OHHTTPStubs lib compatible with it)

This search suggests there's a bunch of these files.
@jspahrsummers - this change makes sense to me. Is there anything we're missing here?

Seems reasonable to me. :zap:

:+1: thanks for the review @jspahrsummers :smile:
@evgenyneu - this change will be live in the next release of Linguist (likely another week or so away)


Trouble deleting/recreating channel

Error is:  Failed to create channel. global name 'sql' is not defined

I've seen this before -- you probably have an illegal char in your chan name (perhaps "-")?

The admin interface works as far as this functionality is concerned.

I agree.  But sometimes the process doesn't complete and recreating
channels fails.  I can show you.  After SFN!
Best,
Will
On Fri, Oct 16, 2015 at 7:54 AM, Kunal Lillaney<EMAIL_ADDRESS>wrote:

The admin interface works as far as this functionality is concerned.
—
Reply to this email directly or view it on GitHub
https://github.com/openconnectome/open-connectome/issues/166#issuecomment-148696911
.

I've seen this message.  I will fix.
I am working on backup/restore as we speak and I have a working backup
system ready to push.
On Fri, Oct 16, 2015 at 6:42 AM, William Gray<EMAIL_ADDRESS>wrote:

I agree. But sometimes the process doesn't complete and recreating
channels fails. I can show you. After SFN!
Best,
Will
On Fri, Oct 16, 2015 at 7:54 AM, Kunal Lillaney<EMAIL_ADDRESS>wrote:

The admin interface works as far as this functionality is concerned.
—
Reply to this email directly or view it on GitHub
<
https://github.com/openconnectome/open-connectome/issues/166#issuecomment-148696911
.

—
Reply to this email directly or view it on GitHub
https://github.com/openconnectome/open-connectome/issues/166#issuecomment-148706292
.

--
Randal Burns
Associate Professor
Department of Computer Science
The Johns Hopkins University

@randalburns Ready to push to master?

@willgray This is now fixed.


[Bug]-[1000]:Renaming a query/object from the entity explorer causes context switch from current tab to the renamed query/object

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Renaming a widget or datasource from the entity explorer, simply changes the name whereas, changing the name of a query or a JS object from the entity explorer causes the active tab to change from current page to the renamed entity.
Context should only switch when users select the query/object and not when they are simply choosing to rename the entity from the explorer. This is because when a user is on the canvas or the editor and is in the middle of writing code, and wants to rename a few queries/objects, the intention is to simply rename the entities and continue wherever the user is on the current tab. Not switch to the query and navigate back to where the user was.
Steps To Reproduce

Add widgets, queries and objects to an app
Rename a query/object from the entity explorer when present on the canvas - observe that on successfully renaming the query/object, context is switched from canvas to the query
Rename a widget/datasource from the entity explorer when present on the canvas - observe that on successfully renaming the widget/datasource, context does not move away from the current content

https://www.loom.com/share/d717a0c1a6c84e5983b6a4493fcd39ed
Public Sample App
No response
Version
cl

Stats

Stat
Values

Reach
1000

Effort (months)
0.5

With the new segmented control, this no longer happens


Cow: Watch newshusk.com

Cow requests the watch of the watch_keyword newshusk\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

newshusk\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by VLAZ in Charcoal HQ


Updated the parser for Bikupan

Bikupan in BMC Uppsala has changed their page. This should fix this.

Thanks for merging, and thanks for the project!
I have slack integration pending in my fork (https://github.com/withrocks/lunch-menu/tree/master) - at SNP&SEQ we are totally dependent on Slack telling us what to eat. I can create a PR for that if that's interesting to others.

I am surely interested in it, but maybe you should wait a bit. We (Data centre) will get a kubernetes cluster in the coming weeks, and I might want to restructure some things once we get it hosted there. If you have any suggestions etc, I'd be happy for the input.

Right, I can rebase onto your changes then. The changes I made in the fork we're using are, if I remember correctly:

use click for implementing the cli, for convenience, as I needed to add a few new parameters.
slack integration, i.e. one can send in parameters for formatting the menu differently and then sending it to slack
support using the cli with a cache, so it's faster to test/develop the parsers


Full version?

Hi there - please could you advise as to how I can gain access to the "Full Version".
Absolutely loving the backtester, so great work, but have a C1 that requires me to test a 1 level cross

sorry the full version will not be released, but was published the source code


Add sloped sprites to wallbr8, wallbr16, and wallbr32

The next of my sloped wall PRs. As before, these sprites were made by ripping existing sprites and hand-editing in Paint.NET.
Pinging @ZeeMaji for review.

Comparison with RCT1 terrain edge (for texture; the color can't be matched):

Hmm right i forgot about that, the colors not matching is kind of unfortunate but i don't think it impacts the walls on their own too much.
On their own, i think they look fine. Nice work.


Incorporate Gloss Sense Disambiguation

Our current text-to-gloss translation can lead to ambiguity in the generated glosses. We propose enhancing our system by incorporating gloss sense disambiguation to better capture the intended meaning of the input text.

To illustrate how big of a problem this is, here are four translations for `KLEIN'
https://signsuisse.sgb-fss.ch/fileadmin/signsuisse_ressources/videos/EB019CAA-D768-D07E-571E219A5F6AA5AB.mp4
https://signsuisse.sgb-fss.ch/fileadmin/signsuisse_ressources/videos/FC9A32C5-C1B1-9B67-BB8C75F7039B568D.mp4
https://signsuisse.sgb-fss.ch/fileadmin/signsuisse_ressources/videos/79B5C9E9-FFBD-7DD2-D579FB9D6E5BC384.mp4
https://signsuisse.sgb-fss.ch/fileadmin/signsuisse_ressources/videos/2171343E-AEF1-76DD-E213221C22CB0261.mp4
And it is unclear how to choose.


assertlib-client-listGroupRelatedGroups add with intergrate test

Description of changes:

Add apigw and lambda interface in Assetlibrary-client for listGroupRelatedGroups Service defined in Assetlibrary.
Add integration test source for it.
Modify file named "inversify.config.ts" in order to test in both mode(baseurl/lambda).

Evidence:

apigw:

lambda:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi @kaerukoara thanks for the PR. Building and testing it, there are linting issues. Can you run rush test and fix the raised issues. Thanks.

Hi @boardthatpowder , thanks for your confirmation. I am sorry not do that step last time. I fixed it, Could you confirm it again?


chore: remove turbopack crates

Why?
vercel.com/blog/turbopack-moving-homes

These crates got merged into next.js with https://github.com/vercel/next.js/pull/68127


Can't deploy locally: failed to start control-plane

I wanted to try out local deployment (haven't tested remote providers), but failed with:
$ node . create --verbose --config ./config/create.local.sample.json
Creating cluster 'testnet5'...
Creating cluster "testnet5" ...

 • Ensuring node image (kindest/node:v1.17.0) 🖼  ...

 ✓ Ensuring node image (kindest/node:v1.17.0) 🖼
 • Preparing nodes 📦   ...

 ✓ Preparing nodes 📦

 • Writing configuration 📜  ...

 ✓ Writing configuration 📜
 • Starting control-plane 🕹  ...

 ✗ Starting control-plane 🕹

ERROR: failed to create cluster: failed to init node with kubeadm: command "docker exec --privileged testnet5-control-plane kubeadm init --ignore-preflight-errors=all --config=/kind/kubeadm.conf --skip-token-print --v=6" failed with error: exit status 1

Command execution failed with code: 1
Could not create local deployment: 1
Could not create cluster: 1
Deleting cluster "testnet5" ...

$ node --version
v14.3.0 // but also tried at v10.21.0
$ docker --version
Docker version 19.03.11, build 42e35e61f3

The failure happens after couple being stuck at "Starting control-plane" for couple of minutes.
Any ideas what can be wrong?

Traced down the issue to be kind related (installed separately), and the symptoms are dauntingly similar to https://github.com/kubernetes-sigs/kind/issues/1569 so I think I'll need to wait for the upstream fix. Closing.


Networking / packet API

A networking / packet API has been requested.

I can imagine having a PlayerConnection that we can have the following structure:

public interface PlayerConnection {

    int ping();

    InetAddress getHostAddress();

    String getHostName();

    Optional<Player> getPlayer();

    void sendCustomMessage(Object plugin, String channel, byte[] rawMessage);

}

I have some reasons that packets shouldn't directly be within the API mostly because packets are entirely implementation based (Compare a packet from Flowstone to vanilla Minecraft and even custom packets created by forge mods). The only packet I can imagine supporting are the custom payload packets that is a basic requirement.

I wrote a PR #363 to handle things like this.

I think it's been fully agreed that beyond the official mod communication packet, SpongeAPI will not contain a packet API. As that part is already complete, this issue is fixed.


Make use of dunder len

The package schwifty make extensive use of a property length. This makes it hard to:

Integrate with libraries like django that rely on the dunder method. (If their's any need to len(IBAN(...)) we are force to inherit from the class and implement the dunder method __len__ ourselfs).

Was their any reason to create a property length instead of using the dunder ?

I agree that it would be more pythonic to make use of the __len__ method. I think it was simply not considered at the time of the original implementation, and there is no reason to not add it now.


[GITHUB-2] Allows agent to be stopped by default

Added autostart option that to allow the agent to be started at
a later date. Also ensured that the service is stopped and disabled
so it won't start on machine boot up.

Pure Awesomeness!

good solution :+1:


Upgrade GitHub API to V3

Upgrade GitHub API to V3
Support LGTM from review approve

See the PR example
@go-gitea/maintainers you can try it on https://lgtm.wu-boy.com/
The old LGTM website can't enable any repository now. https://lgtm.gitea.io/

LGTM

CI failed

Codecov Report

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

@@           Coverage Diff            @@
##             master     #36   +/-   ##
========================================
  Coverage          ?   41.5%
========================================
  Files             ?      15
  Lines             ?     559
  Branches          ?       0
========================================
  Hits              ?     232
  Misses            ?     314
  Partials          ?      13

Impacted Files
Coverage Δ

model/review.go
0% <0%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b044f5a...fe5f415. Read the comment docs.

@lunny Build success finally. :)

LGTM


Test case and fix for RESTEASY-222

It seems that RESTEASY-222 should be reopened again, because when I use 'lastModified' the actual Last-Modified header is not correctly formatted. This is a fix, plus a test-case.

Hi Michiel,
Have you looked at the failing test (https://s3.amazonaws.com/archive.travis-ci.org/jobs/95601252/log.txt)? org.jboss.resteasy.test.client.ResponseTest.getLastModifiedTest()
@Test
public void getLastModifiedTest()
{
   Date date = Calendar.getInstance().getTime();
   Response response = Response.ok().lastModified(date).build();
   Date responseDate = response.getLastModified();
   System.out.println(date);
   System.out.println(responseDate);
   Assert.assertTrue(date.equals(responseDate));
}

fails because
metadata.putSingle(HttpHeaderNames.LAST_MODIFIED, getDateFormatRFC822().format(lastModified));

truncates milliseconds and
metadata.putSingle(HttpHeaderNames.LAST_MODIFIED, lastModified);

doesn't.
-Ron

I'll look into it.

Well, I think since dates are always truncated in http headers, the test case is actually wrong.  Also I doubt if whether it is a good idea to depend the test on the current time. It won't test the same every time like that.  So I propose to simply use the same, rounded, date every time in this test.

I've created RESTEASY-1299, a clone of RESTEASY-222.
This PR is ready to merge. Thanks, Michiel.

Confirmed with Ron this change failed TCK. I'll revert it.


feat(apps/prod/tekton/configs): add tiproxy triggers

branch
tag
dev-build with office repo

Signed-off-by: wuhuizuo<EMAIL_ADDRESS>

It depends on:

https://github.com/PingCAP-QE/artifacts/pull/184

/approve


Add Banksy image annotation

Tool added : Banksy
Please let me know in case of any changes to description.
Thanks !

Thanks for the submission, @SangamSwadiK. This tool hasn't been updated since July 2020, so I think it fails our criterion of being 'actively maintained'. Welcome to hear if you think that this is still commonly used + the fact that it isn't regularly maintained isn't a problem.


const instead of let in swipl-bundled.temp.js

Hi, thanks for making this package :)
When trying to use it, I'm getting following error
✘ [ERROR] Cannot assign to "size" because it is a constant

    ../eye-js/node_modules/eyereasoner/dist/swipl-bundled.temp.js:2711:20:
      2711 │                     size = -1;
           ╵                     ~~~~

  The symbol "size" was declared a constant here:

    ../eye-js/node_modules/eyereasoner/dist/swipl-bundled.temp.js:2707:22:
      2707 │                 const size = parseInt(r.headers.get("content-length"));
           ╵                       ~~~~

/Users/ieben/WebstormProjects/SWIPL-WASM-Example/node_modules/esbuild/lib/main.js:1566
  let error = new Error(`${text}${summary}`);
              ^

Error: Build failed with 1 error:
../eye-js/node_modules/eyereasoner/dist/swipl-bundled.temp.js:2711:20: ERROR: Cannot assign to "size" because it is a constant
    at failureErrorWithLog (/Users/ieben/WebstormProjects/SWIPL-WASM-Example/node_modules/esbuild/lib/main.js:1566:15)
    at /Users/ieben/WebstormProjects/SWIPL-WASM-Example/node_modules/esbuild/lib/main.js:1024:28
    at runOnEndCallbacks (/Users/ieben/WebstormProjects/SWIPL-WASM-Example/node_modules/esbuild/lib/main.js:1438:61)
    at buildResponseToResult (/Users/ieben/WebstormProjects/SWIPL-WASM-Example/node_modules/esbuild/lib/main.js:1022:7)
    at /Users/ieben/WebstormProjects/SWIPL-WASM-Example/node_modules/esbuild/lib/main.js:1134:14
    at responseCallbacks.<computed> (/Users/ieben/WebstormProjects/SWIPL-WASM-Example/node_modules/esbuild/lib/main.js:671:9)
    at handleIncomingPacket (/Users/ieben/WebstormProjects/SWIPL-WASM-Example/node_modules/esbuild/lib/main.js:726:9)
    at Socket.readFromStdout (/Users/ieben/WebstormProjects/SWIPL-WASM-Example/node_modules/esbuild/lib/main.js:647:7)
    at Socket.emit (node:events:513:28)
    at addChunk (node:internal/streams/readable:324:12) {
  errors: [
    {
      detail: undefined,
      id: '',
      location: {
        column: 20,
        file: '../eye-js/node_modules/eyereasoner/dist/swipl-bundled.temp.js',
        length: 4,
        line: 2711,
        lineText: '                    size = -1;',
        namespace: '',
        suggestion: ''
      },
      notes: [
        {
          location: {
            column: 22,
            file: '../eye-js/node_modules/eyereasoner/dist/swipl-bundled.temp.js',
            length: 4,
            line: 2707,
            lineText: '                const size = parseInt(r.headers.get("content-length"));',
            namespace: '',
            suggestion: ''
          },
          text: 'The symbol "size" was declared a constant here:'
        }
      ],
      pluginName: '',
      text: 'Cannot assign to "size" because it is a constant'
    }
  ],
  warnings: []
}

Node.js v18.12.1

When I looked at that location, the error is correct, in swipl-bundled.temp.js the following code is included (formatted):
url_properties(url) {
    return fetch(url, {method: "HEAD"}).then(r => {
        if (r.status == 200) {
            const size = parseInt(r.headers.get("content-length"));
            const mods = r.headers.get("last-modified");
            const time = Date.parse(mods) || 0;
            if (!size instanceof Number) size = -1;
            return {url: r.url, status: r.status, size: size, last_modified: time / 1e3}
        } else {
            return {url: url, status: r.status}
        }
    })
}

As you can see, size is declared using a const and later on being reassigned.
I'm not sure where to report this issue, but as I'm getting this error using this package, I'm reporting it here and then we'll see where the fix should happen in the end :)

If I clone the repo and manually fix this in the bundled file, I get this package to work, so very promising!

Thanks for the report - the file is auto-generated from the build command in https://github.com/rla/npm-swipl-wasm/pull/8; I am happy to accept a PR with your manual fix but it won't solve the underlying problem produced by either swipl-devel or emscripten; so I will also try and work out what the upstream cause is.
In the meantime could you provide a minimal repro for this error (or even better would be a test case included with the PR doing the manual fix) so that we don't accidentally re-introduce the error when migrating to depend on npm swipl wasm

Can you also test to see if you get the same error when using the node and web exports of SWIPL from https://github.com/rla/npm-swipl-wasm (as opposed to the bundled version used in eye-js).

Aha - looks like the real bug is here https://github.com/SWI-Prolog/swipl-devel/blob/952794b3b03e6b073e767465b884cf81a0207737/src/wasm/prolog.js#L583 - so I will create a PR there with a fix; the manual patch PR here would also be useful in the meantime.

I've made a PR with the manual fix, it's pretty simple 😄
Due to upcoming exams I lack the time to also write test cases for this but once you've merged the PR and released a new version of this package, I can give you a working example where this package is used :)

Thanks a lot for the quick actions. As promised, here is a working example of reasoning with EYE in the browser using this package (wrapped in another package @smessie/eye-js) https://reasoner.smessie.com.

wrapped in another package @smessie/eye-js

Happy to accept functions like that upstream here as well rather than having a bunch of micro-packages. Note that the logic you have seems to just be doing the same as
  // Load EYE into the SWIPL Module and run consule("eye.pl").
  loadEye(Module)

  // Load the the strings data and query as files data.n3 and query.n3 into the module
  Module.FS.writeFile('data.n3', data);
  Module.FS.writeFile('query.n3', query);

  // Execute main(['--nope', '--quiet', './data.n3', '--query', './query.n3']).
  queryOnce(Module, 'main', ['--nope', '--quiet', './data.n3', '--query', './query.n3']);

Noting that --nope is just returning the result of the query and removing the proof.

https://reasoner.smessie.com/.

Nice work!
I am observing the page is taking a while to load since it is loading all the WASM before rendering; might be worth lazy loading the eye-js module or; using the browser version of SWIPL in https://github.com/rla/npm-swipl-wasm/ rather than the default bundle we export as that loads the WASM file separately using a fetch call.
The SWIPL bundle currently exported here is designed to "just work" out of the on both node and browser. But that simplicity is coming at a performance cost in your case.


Themable menus & Full support for RB Themes

Full support for menu themings & help images
Full support for recalbox themes & every existing EmulationStation Themes.
Add video & marquee support in detailed view (video is used in RB detailed view)
Fixes for video start delay & fadings.
Updated menu & buttons resources : they need to be white to draw correctly with themed menus.
GuiMenu opening animation.
Menu navigation : when on top & moving top, select last item ( et inversement... )

you keep : current.name = "atari5200"; ?

you keep : current.name = "atari5200"; ?

It is a "hack" for windows in debug mode rounded with #ifdefs : I couldn't load bios information, so I wrote this to see what the menus looked like. This code can be removed in the future it is there for testing purposes only.


minor updates on formatting for better documentation

@aymgal the CI failed with the latest changes in coolest. Do you know why this is the case? Can you also please make a pip release such that we can do stable development on our side since this can impact many other pull requests? Thank you very much!

Yes @sibirrer this is because I pushed some changes to the main branch. It is indeed a good idea to switch to the pip installable version (v0.1.8) that has been released some time ago 👍

Yes @sibirrer this is because I pushed some changes to the main branch. It is indeed a good idea to switch to the pip installable version (v0.1.8) that has been released some time ago 👍

Wonderful! It worked. Thank you very much!


Make App stop asking to import bibles during start up

I would like to have an option to make the app stop asking for bibles to import
during start up si that I can get into the app faster.

Fixed in version 3


:sparkles: Support for Sharding

https://discord.com/developers/docs/topics/gateway#sharding
https://discord.com/developers/docs/topics/gateway#sharding-for-very-large-bots

So weird thing to suggest but maybe bots should Be automatically sharded? It shouldn't hurt anyone to have it on automatically

pretty sure thats how dpy does it. I don't really have a preference tbh.

pretty sure thats how dpy does it. I don't really have a preference tbh.

no? i mean like automatically activated by the lib not needing to enable it

Not sure but my gut is that it'll abstract away too much

wdym?

I think its assumed that bots won't be sharded by default and we shouldn't do whats more unexpected.


Drop 3.8 and 3.9 on next sourmash version (after 4.8.4)

Solution to issue cannot be found in the documentation.

[X] I checked the documentation.

Issue
https://github.com/sourmash-bio/sourmash/pull/2848 dropped 3.8 and 3.9 support upstream, so remove this on next build once a new sourmash version is released.
Installed packages
not applicable

Environment info
not applicable

Note: this will drop PyPy for some time, since it is still on pypy3.9 and bumping to 3.10 is a big task (and even 3.9 was not migrated all the way in conda-forge yet...)

Fixed in #55


'contextSensitiveHelpUrl' appears to be required to build, but is not available in 2.0

Describe the bug
ALC refuses to build a package that was building fine a few days ago. I have not changed the source code. Might be because of a silent update of AL Language? I am currently using 4.0.198182. The error given is this:
error AS0051: The property 'contextSensitiveHelpUrl' must be specified.
The real issue is, that my project is targeting runtime 2.0 and in this runtime I am not allowed to provide a contextSensitiveHelpUrl:
error AL0666: 'contextSensitiveHelpUrl' is not available in runtime version '2.0'. The supported runtime versions are: '3.0' or greater.
To Reproduce
Steps and to reproduce the behavior:

Create a project
Set runtime to 2.0
Build

Expected behavior
I am OK with providing this URL. But if the runtime does not allow it to be set, it should'nt be required to be set.
5. Versions:

AL Language: 4.0.198182

Hi @hemisphera ! You can disable this error by using a ruleset for now. I will fix it so that the analyzer is version aware.

@atoader
On a related note: Using the ignoreRuleSet.json for this issue allows the main project to build and deploy, but strangely not the Unit Test project. The only real differencies between the two app.json's are dependendies and the "test"-tag in Unit Test project.
We added this to a Unit Test project ignoreRuleSet (but, not working):
{
"id": "AS0051",
"action": "None",
"justification": "The property contextSensitiveHelpUrl is not supported in Runtime2.0 and can not be added to app.json"
},

Hi @mivtf! If you can provide a sample project to reproduce the problem, please open a new issue.

@atoader
Created related issue  "Error AS0051: The property 'contextSensitiveHelpUrl' must be specified" cannot be suppressed by ruleSet - see https://github.com/microsoft/AL/issues/5440

The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 38464.
If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo
For more details on code branches and docker images please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://blogs.msdn.microsoft.com/freddyk/2018/04/16/which-docker-image-is-the-right-for-you/


refactor _splash.less

#659 : Refactor splash.less to use less features instead of CSS

@chatRG Did you run npm run compile. Because your changes are not visible yet.

@chatRG Did you run npm run compile. Because your changes are not visible yet.

@HADES-01 Do I commit the dist/sbuttons.css as well?

Great work!
@all-contributors please add @chatRG for code


[PROPOSAL] Facet for file format type

Purpose:
Spark integration with OL can collect information about dataset location (warehouse+metastore) and its schema. But file format is currently collected only for Iceberg implementation, non-Iceberg tables have no such information. This can be important for data discovery.
Proposed implementation
Currently there is a facet StorageDatasetFacet with fields storageLayer and fileFormat. But fileFormat is optional and storageLayer is not, which does not make sense for non-Iceberg tables.
I see 3 options here:

Update StorageDatasetFacet spec to name storageLayer optional, and fileFormat mandatory. But this may conflict with facet name.
Passing some static value to storageLayer field, e.g. native or none, without any changes in StorageDatasetFacet sper.
Adding another facet just for fileFormat. But having 2 slightly different facets is cumbersome.

Why not just add file format where it makes sense using existing type?
storageLayer should indicate what the storage is anyway - pure format is sometimes not enough to reason how to interact with the data anyway

Why not just add file format where it makes sense using existing type?

Do you mean option 2?

Passing some static value to storageLayer field, e.g. native or none, without any changes in StorageDatasetFacet sper.

Basically, yeah - but providing information about what native means - local filesystem? Object storage?
I think the constraints in the facet are needlessly narrow:
"Storage layer provider with allowed values: iceberg, delta."
"File format with allowed values: parquet, orc, avro, json, csv, text, xml."

Yeah, I agree - we should encourage some standarization though, even if people can actually put everything there and event still be valid with regards to schema, similar to what we do with dataset naming.

but providing information about what native means - local filesystem? Object storage?

I struggle to find a value which is both meaningful for users and does follow the original storageLayer definition. spark? hive? default?


License not clear

Hi SFCC-CI team,
When i have a look at the projet  you say that the BSD-3 licence  apply.
In the license file , the first line says that this product depends on salesforce.
So is-it dependant of Salesforce or the community ?
Could be great to clarify that point for evryone.
Kind regards

Hi @amahe,
we have followed our Salesforce open sourcing processing when open sourcing the CLI tool and thus are using the same type of license as for other Salesforce open source tools. For specific questions on type of licenses I kindly refer to contacting the Salesforce legal at https://www.salesforce.com/company/legal/

Is there any other question on that or can we close this?

Yes it's ok, can close then. Thx.


Implement commit parsing/formatting

To be able to support git commits with multiple signature headers, we have to implement our own parsing and formatting.
Signed-off-by: Alexis Sellier<EMAIL_ADDRESS>

Nice, would this be useful to have in radicle-git?

Yup, I think eventually we can move some of the git code into radicle-git and depend on that, instead of having it here.

Yup, I think eventually we can move some of the git code into radicle-git and depend on that, instead of having it here.

Sweet, would be good to keep track of those things as issues in radicle-git and have some understanding of when you'd like to move them over. I imagine you're keeping it here for quicker iteration, right?

Yup, I think eventually we can move some of the git code into radicle-git and depend on that, instead of having it here.

Sweet, would be good to keep track of those things as issues in radicle-git and have some understanding of when you'd like to move them over. I imagine you're keeping it here for quicker iteration, right?

Yeah, I think 99% of it should be in radicle::git and radicle::storage::git. It's indeed easier for me to make changes here until the code and interfaces stabilize. There is also the option of having more of a monorepo and moving radicle-git in here in the long run.

Looks good to me too


ChannelReducer breaks with new version of sklearn

AttributeError                            Traceback (most recent call last)
<ipython-input-12-060e126c4e4f> in <module>
----> 1 acts_ = ChannelReducer(6, "NMF").fit_transform(np.maximum(activations,0))

/opt/conda/lib/python3.7/site-packages/lucid/misc/channel_reducer.py in __init__(self, n_components, reduction_alg, **kwargs)
     52     for name in dir(sklearn.decomposition):
     53       obj = sklearn.decomposition.__getattribute__(name)
---> 54       if isinstance(obj, type) and issubclass(obj, sklearn.decomposition.base.BaseEstimator):
     55         algorithm_map[name] = obj
     56     if isinstance(reduction_alg, str):

AttributeError: module 'sklearn.decomposition' has no attribute 'base'

Sounds like a version issue.

(This was Chris Olah posting the issue under my account - definitely seems to be a version issue)

Yep! Thanks to @mcleavey for letting me note this down while we were pairing. :)
Seems to be resolved by #221.


TypeError: list indices must be integers or slices, not float .How to get rid of it

Hi @05MrTom,
This error does not seem to be stemming from wandb. Could you check by disabling wandb?
Thanks,
Ramit

Hi @05MrTom, since we have not heard back from you we are going to close this request. If you would like to re-open the conversation, please let us know!


Add csharp_ls

Which server would you like to request to be added?
Server name:csharp_ls
Server homepage (e.g., GitHub page):https://github.com/razzmatazz/csharp-language-server
Which languages does this server target?
Languages:csharp

I think this language_server use dotnet and not mono , It is better than omnisharp

https://github.com/williamboman/nvim-lsp-installer/pull/294
Ok I make a pr


                f"Create on in advance by using `modalities data pack_encoded_data`."
            )

        with self._data_path.open("rb") as f:
            # get number of bytes in data section
            data_section_length_in_bytes = f.read(self.DATA_SECTION_LENGTH_IN_BYTES)
            self.data_len = int.from_bytes(data_section_length_in_bytes, byteorder="little")

            # get number of bytes for encoding a single token
            f.seek(self.DATA_SECTION_LENGTH_IN_BYTES)
            token_size_as_bytes = f.read(self.TOKEN_SIZE_DESCRIPTOR_LENGTH_IN_BYTES)
            self.token_size_in_bytes = int.from_bytes(token_size_as_bytes, byteorder="little", signed=False)

            # get index
>           f.seek(self.HEADER_SIZE_IN_BYTES + self.data_len)
E           OSError: [Errno 22] Invalid argument

src/modalities/dataloader/create_packed_data.py:212: OSError

The current state in main contains dgx-specific paths. Probably dgx2. I want to emphasize again that this is a bad idea. Especially modifying test resources like the lorem_ipsum config (e.g. here).
Git blame indicates @mali-git . Please don't do this. This makes the tool unusable on different devices and undermines the stability of the tests and invites people to ignore them even more.

Seems like this problem was introduced with the tokenizer merge. (At least using the previous state of 60feafe29ec882939202be4e88892bbcde2e53f5 Are you sure about the code's stability for the usage on Taurus? @le1nux, @mali-git

I was able to fix the tests. They pass in my local setup. Since the Ci is still broken due to our non-GPU setup and flash-attn being integrated, I verified it locally by creating a dockerized environment.
I did not make the utilities for the Docker build part of this PR. But you can try reproducing it by checking out this tagged version: https://github.com/Modalities/modalities/tree/dockerized-pytester


Showing output on HDMI (only using RCWI as camera control)

Maybe I'm missing something simple, but I just want to use RCWI to control the camera remotely (changing PiCamera settings) but I don't see a setting for turning on or off HDMI overlay preview. How can this be accomplished? I don't need motion, webcam, recording options ATM.

I don't understand what you mean by HDMI overlay preview. This software does not do anything with HDMI.
It does make available a mjpeg stream which can be accessed by the browser interface as required. Is that what you are referring to?
If so then what are you trying to achieve with the camera? Do you want a different web interface that is control only? One could do that with a simple modification to the index.php to skip the preview frame. But then how is the camera being used and how will you know what the effect of changing camera settings is?

This is in a conference room setting with an overflow area. I can see the HDMI monitor while adjusting the camera. I haven't looked through the code yet but you are saying in the index.PHP I can turn off the streaming and enable the raspicam preview (overlay is the video preview over the login screen, no GUI)?

I am still don't understand your set up.
What app is displaying on the HDMI monitor?
With the raspberry pi camera everything is controlled via the MMAL layer and only one application has ownership of that at any one time.
So if you have some other raspberry camera application then trying to control its settings has to be done via whatever controls app has. You can't do it via this interface.
On the other hand if the main HDMI monitor is showing the browser view of this app then a second browser client to the same server can remotely control its settings as it is the same server based instance of the camera app involved. The secondary client in this case can show the preview as well or it could be removed if desired as previously mentioned.

It's ok. I did some homework and found that some simple coding with picamera.py and flask did the job. I just needed a simple setup to control the camera through a web interface.


node_modules/changelog forgot in package

Somehow, the changelog package got abbandoned in the package here http://registry.npmjs.org/coffeelint/-/coffeelint-1.10.0.tgz
as it can be seen below
$ npm install coffeelint
<EMAIL_ADDRESS>node_modules/coffeelint
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>$ npm ls
└─┬<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>extraneous
├──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └─┬<EMAIL_ADDRESS>│ │   ├──<EMAIL_ADDRESS>│ │   └──<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>unfortunaltely this makes npm shrinkwrap yell.
npm 2.9.0
Also tested on a machine that still had npm 1.4.3, worked like a charm, although that doesn't help my situation too much

I'm not sure how this is possible since CoffeeLint doesn't use shrinkwrap and doesn't depend on changelog. I don't doubt you have a problem, I just don't know how I can help

https://github.com/clutchski/coffeelint/compare/v1.9.7...v1.10.0
^ The diff here shows that package.json hasn't changed in a way that would do this

When downloading http://registry.npmjs.org/coffeelint/-/coffeelint-1.10.0.tgz it already has a node_modules folder with a changelog in it.
This was probably just a bug with publishing.
Can you please try just releasing another version? (no change to the code needed)

http://registry.npmjs.org/coffeelint/-/coffeelint-1.10.1.tgz does not have a node_modules. I have no idea how or why npm published it on 1.10.0

Thanks for the help :)

Thank you!

Thank you!


Find/fetch/prefetch/threading refactor

This PR started out as an effort to be able to support surfacing errors from remote backends, but has evolved into a refactor of how the find/fetch cycle operates, removal of the remaining special handling for the remote finder and reader, and support for all finders to be able to find and fetch multiple patterns at once.  This is a pretty hefty change, and there are a few things that could probably be broken out into separate PRs if that is a concern.  I did take pains to improve test coverage as much as possible as I went.
The core change that opened up this line of thinking was the idea that if finders are made responsible for defining their own factory() class-method then it becomes possible for the remote finder to create a separate finder for each cluster host rather than trying to handle all cluster hosts together within a single finder.  That in turn makes it possible to drastically simplify the logic within both RemoteFinder and RemoteReader as now they only need to handle a single backend host and all thread handling can be moved into STORE.find and STORE.fetch (nee STORE.remote_fetch, see below).
The next change was to move the handling of the find_nodes / node.fetch logic down into BaseFinder in the fetch method, which in turn uses find_multi to get the list of matching nodes.  This means that STORE.fetch is able to dispatch a call to fetch on each finder (legacy finders that don't extend BaseFinder are monkey-patched to ensure backward compatibility) and let it handle either going through the standard find_nodes/node.fetch process or to redefine fetch as RemoteFinder does.
The next big change is that all fetches now use the prefetch path, so evaluateTarget dispatches datalib.prefetchData that in turn calls STORE.fetch and stores the returned data from all finders in requestContext.  Remote and local finders are treated just the same, datalib has no concept of finders at all, and STORE only uses the local flag on a finder is to honor the local request parameter.  datalib.fetchData just pulls the prefetched data for the given path expression from requestContext and merges the results from the various finders.  The REMOTE_PREFETCH_DATA setting was removed as it is no longer needed.  It is also worth noting that the REMOTE_FIND_TIMEOUT and REMOTE_FETCH_TIMEOUT settings now apply to all finds & fetches, we may want to consider adding FIND_TIME_LIMIT and FETCH_TIME_LIMIT or similar settings to control the total time that the find/fetch threads can run, and leave the REMOTE_ settings to control only the timeouts on the individual HTTP calls.
Once all that was done and each finder was now operating in its own thread with no need to handle results from multiple backends etc or re-dispatching requests for data that was already being fetched there was no longer any need for the FetchInProgress, wait_for_result etc stuff, so all that was removed.
There are a number of other supporting refactors included to cut down on duplicated code and to fix bugs that I came across as I worked through things, I will go through and add comments in the patch to explain them in more detail.
As always, any and all feedback is appreciated!

Codecov Report

Merging #2093 into master will increase coverage by 2.77%.
The diff coverage is 98.92%.

@@            Coverage Diff             @@
##           master    #2093      +/-   ##
==========================================
+ Coverage   75.69%   78.47%   +2.77%
==========================================
  Files          80       78       -2
  Lines        7711     7525     -186
  Branches     1512     1483      -29
==========================================
+ Hits         5837     5905      +68
+ Misses       1613     1386     -227
+ Partials      261      234      -27

Impacted Files
Coverage Δ

webapp/graphite/readers/utils.py
100% <ø> (+5.78%)
:arrow_up:

webapp/graphite/settings.py
76.88% <ø> (-0.13%)
:arrow_down:

webapp/graphite/finders/utils.py
100% <100%> (+57.62%)
:arrow_up:

webapp/graphite/tags/base.py
100% <100%> (+19.56%)
:arrow_up:

webapp/graphite/util.py
80% <100%> (+0.44%)
:arrow_up:

webapp/graphite/storage.py
82.12% <100%> (+31.21%)
:arrow_up:

webapp/graphite/render/datalib.py
100% <100%> (+3.38%)
:arrow_up:

webapp/graphite/worker_pool/pool.py
100% <100%> (+8.82%)
:arrow_up:

webapp/graphite/readers/__init__.py
100% <100%> (ø)
:arrow_up:

webapp/graphite/finders/remote.py
96.66% <100%> (+54.2%)
:arrow_up:

... and 10 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 370ab87...0e32b27. Read the comment docs.

@iksaif I'd love to get your feedback on this

I'm out until next week. Will try to look on Monday.
Le 3 nov. 2017 19:05, "Dan Cech"<EMAIL_ADDRESS>a écrit :

@iksaif https://github.com/iksaif I'd love to get your feedback on this
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/graphite-project/graphite-web/pull/2093#issuecomment-341766563,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_DAwVgBH-0o6MH2xsKtrgLJtoNYwzgks5sy0fbgaJpZM4QJtJh
.

This looks good. I'm mostly afraid about plugins compatibility here as it will be quite hard to support 1.0 and >1.1 with all these changes in the finder/reader API.
Do you think there would be a way to keep some of the symbols just for backward compatibility ? (Thinking about FetchInProgress and alike).

Hmm, that is an interesting question.  I'd really like to avoid maintaining that stuff moving forward, especially since it isn't the easiest thing in the world to follow.  Let's think about what that would look like, since we'd also need to re-add code in the store to run wait_for_results or similar.

Maybe we should release 1.1 before merging this and then merge it to master and give users some time to change 3rd party plugins?

Well, I doubt there are many (any besides biggraphite?) plugins using the 1.x "plugin api", so I'd rather get it released ASAP than have things drag on.  At this point anyone running 1.0.x should really upgrade to 1.1.x anyway, unless we want to backport some stuff and cut a 1.0.3

Ok, makes sense.

Well, all existing plugins are used "1.0.x" plugin api AKA "master" plugin api, because there's no other api exist, right? :)
I know at least 3 more-less actively used in a wild - https://github.com/InfluxGraph/influxgraph, https://github.com/brutasse/graphite-cyanite and https://github.com/yandex/graphouse/tree/master/src/main/pySources and a bunch of more-less outdated. But probably not a big deal, though.
I mostly worried about documentation here. This - https://graphite.readthedocs.io/en/latest/storage-backends.html - is mostly outdated now, right? Can we fix that before releasing this?
And or we need some working custom finder there, probably big-graphite is enough.

I'll make biggraphite compatible during the week

@deniszh all that documentation is still correct, I didn't change compatibility with any 0.9.x-style plugins.  Looking at the code influxgraph, graphite-cyanite & graphouse will all work.  Right now there is no support for the graphite-api-style fetch_multi call so it won't take advantage of that for influxgraph or cyanite, but I think that it should be possible with a little refactoring in BaseFinder.  I will check that out and update the plugin API docs with the 1.1+ spec later this week.

Looking deeper the issue with trying to support fetch_multi is that it doesn't return which path expression each result is related to, which is required for the prefetch mechanism to work properly.  At this point I think the best way to move forward is to update the docs so people have a guide to implementing the more efficient fetch path, but use the code in this branch as-is.

At this point I think the best way to move forward is to update the docs so people have a guide to implementing the more efficient fetch path, but use the code in this branch as-is.

If old plugins will work - then that's great, let's proceed! 👍
We never had fetch_multi support anyway.
Thanks for digging that, @DanCech !

Cool, I'm going to go ahead with this merge so that I can open a PR for the index.json update, will open an issue for updating the docs to include the new capabilities that are currently only documented in the code of BaseFinder and BaseReader.


🚀 - Screen glass reflection

Which @codeimage/* package(s) are relevant/releated to the feature request?
No response
Description
Possibility to add screen glass reflection to window editor


Remove Tixati.Tixati 3.19 to Tixati.Tixati.Portable 3.19

Microsoft Reviewers: Open in CodeFlow

URL: https://download2.tixati.com/download/tixati-3.19-1.portable.zip
(Automated message - build 597)

URL: https://download2.tixati.com/download/tixati-3.19-1.portable.zip
(Automated message - build 597)

Indeed the URL for this version of the package is the one provided in the comment.

Yeah, sorry, automation checks this based on the PR title. It matched "Remove" and performed the check.

Readd in #147055


Hash Checking

Recently a popular Monero wallet site was hacked, the attackers replaced a known trusted binary with a backdoored one to allow crypto theft. The only reason the attack was uncovered because the attackers didnt update the binary hashes on the site.
More on the story here
Would ScreenToGif consider publishing known safe hashes to a key system so we can validate the software we are downloding can be trusted? Infact, is this already being done?
Thank you

Well, ScreenToGif has a code signing certificate in use, I'm not sure if adding the hashes would help much. What do you think?

A few notes on this:

If you do post file hashes, you'd want to post the hashes to an independent, 3rd party site unrelated to Github.  This is because, if your Github account is hacked, it's not difficult for the attacker to change the hash to the malware-infected version.  You could potentially just add it to the end of your new release twitter posts.

If you go this route, use SHA 256 hashes, which are sort of the standard thanks to sites like VirusTotal.  There are other hashing standards, but if you're the sort of person checking hashes for security reasons, you're not going to trust MD5 and SHA-1.

Another option is to generate GPG signatures, which are very difficult to forge, but not in wide use.  Even though it's an open standard and has been around for decades, even security personnel I've known won't bother with it.  I can't explain why.
Anyway, you can see a bit more about Github and GPG signatures here: https://github.blog/2016-04-05-gpg-signature-verification/ or https://help.github.com/en/github/authenticating-to-github/managing-commit-signature-verification or I can point you to some other sources with additional explanation.

The signature probably covers it to be honest. Hash checking probs not needed


Server Commands

@jpd002 browsing through some of the documents and code you have and was curious if you implemented a way to send animation id commands through the chat log to see the animations on demand?
I am working on completing the Emotes and Skill information and it would make it much easier if i can queue up a command and watch it go. Please let me know, thanks!

You could basically hook something up in the ProcessChat function (https://github.com/jpd002/SeventhUmbral/blob/66e35361d27a17185534c12b91540be316f6b6bc/daemon/GameServerPlayer.cpp#L412). I think it should work for playing animations on characters.

Perfect, thanks! I can do that, wasn't sure if you already had a way to see the animations or not. =)


You can build in wilderness with block-place false if inside a claim

In the image above, the blue circle is an admin claim. The user has permission trust (manager).
This was also tested in an admin claim where the user doesn't have permission trust. They can simply stand inside any claim and build on the wilderness when the wilderness has block-place false.
The wilderness claim has 'block-break any false' and 'block-place any false'.
While inside the claim:

You can build outside the claim (should not be able to)
You cannot build inside the claim (should be able to I believe) - Need administrators permissions

While outside the claim:

You cannot build inside (should be able to) - Need admin perms
You cannot build outside the claim - Need wilderness admin perms

What build are you using?

Was using build 62. Works perfectly in latest builds. Thanks!


Use cloudaux

In order to better collect information about an account in the gather phase for the python version, I should use https://github.com/Netflix-Skunkworks/cloudaux
That will improve gathering data from large accounts where rate limiting may occur.

I've decided to replicate the concept behind cloudaux myself to store the data as files.


kubectl apply -f kub-flannel doesn't create /etc/cni content

I have created a vagrant box and try to create a kubernetes cluster following the instructions at https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/
On step 3 launch:
kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/v0.9.1/Documentation/kube-flannel.yml
no content at /etc/cni and receive message in journal:
Unable to update cni config: No networks found in /etc/cni/net.d
Expected Behavior
Should be content at /etc/cni after apply kube-flannel.yml
Current Behavior
No content at /etc/cni
Possible Solution
Steps to Reproduce (for bugs)

Create a virtualbox machine with vagrant:

# Vagrantfile
Vagrant.configure("2") do |config|
  config.vm.provider "virtualbox" do |v|
    v.cpus = 4  # CPU settings. VirtualBox works much better with a single CPU.
    v.memory = 4096

    # Disable VirtualBox DNS proxy as it may cause issues.
    # See https://github.com/docker/machine/pull/1069
    v.customize ['modifyvm', :id, '--natdnshostresolver1', 'off']
    v.customize ['modifyvm', :id, '--natdnsproxy1', 'off']
  end

  config.vm.define "kbt_1" do |config|
    config.vm.box = 'coreos-stable'
    config.vm.box_url = 'https://stable.release.core-os.net/amd64-usr/1520.8.0/coreos_production_vagrant.json'

    config.vm.box_check_update = false
    config.vbguest.auto_update = false
    config.vm.network "private_network", ip: "<IP_ADDRESS>"
    config.vm.synced_folder ".", "/vagrant", id: "core", :nfs => true
    config.vm.network :forwarded_port, guest: 8001, host: 8001

    config.vm.hostname = 'coreos1'
  end
end

Install kubeadm with

docker run -it \
-v /etc:/rootfs/etc \
-v /opt:/rootfs/opt \
-v /usr/bin:/rootfs/usr/bin \
 -e K8S_VERSION=v1.8.4 \
 -e CNI_RELEASE=v0.6.0 \
xakra/kubeadm-installer:0.4.7 coreos

Init cluster:

sudo systemctl daemon-reload
sudo systemctl enable docker kubelet
sudo systemctl restart docker kubelet

sudo kubeadm init --pod-network-cidr=<IP_ADDRESS>/16

mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

sudo sysctl net.bridge.bridge-nf-call-iptables=1

Install flannel:

sudo kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/v0.9.1/Documentation/kube-flannel.yml

Context
I'm trying to start to test kubernetes to move it to production.
Your Environment

Flannel version: 9.1
Backend used (e.g. vxlan or udp): ?
Etcd version:
Kubernetes version (if used): 1.8.4
Operating System and version: CoreOS 1520.8.0 in a Windows 10, Vagrant with vagrant-winnfsd plugin

It's probably worth seeing if someone can help you on slack https://github.com/coreos/flannel#contact

thanks @tomdee, you are right.

same problem


Is it possible to access the iFrames ?

Hey,
I'm trying to make a theme for the client but I'm facing a difficulty trying to modify the TFT page. The page is in an iframe and its src is https://prod.embed.rgpub.io/wwpub-lunar-gala-2023/en_US/ , I found out it's not possible to modify the elements' style that are inside an Iframe if its src is different that the current origin.
It returns : VM9420:1 Uncaught DOMException: Blocked a frame with origin "https://<IP_ADDRESS>:28773" from accessing a cross-origin frame.
at :1:73
I modified the config.cfg file in the league-loader folder to :
[Main]
LeaguePath=C:\Riot Games\League of Legends
DisableWebSecurity=1
IgnoreCertificateErrors=1

But same error. If anyone knows a work-around that would be helpful ! There are a lot of iframes used in the client

Disabling web security also disable all same site and cross-origin policies.
I have not tested with iframe, but seems there is no possible solution since Chromium v91.

Disabling web security also disable all same site and cross-origin policies. I have not tested with iframe, but seems there is no possible solution since Chromium v91.

I see, thank you anyway


Fix carousel header overflow

User amp-fit-text to ensure that text fit's into available space.  Fixes #953

@kul3r4 & @morsssss PTAL


Error thrown during cleanup

If a window is closed, Router.prototype.clean is run in response to the window's close event:
https://github.com/m0n0l0c0/electron-router/blob/db1f1fa487bc98552eaa47a18e562fd4e92cc365/router.js#L116-L123
However, this.clean is not bound to this, so trying to access members of the _name property will fail with a TypeError:
https://github.com/m0n0l0c0/electron-router/blob/db1f1fa487bc98552eaa47a18e562fd4e92cc365/router.js#L411-L412
A possible solution would be to bind clean to the instance during construction:
      }

      // Bind clean to instance to make it usable as event handler
      this.clean = this.clean.bind(this)

      this._setup(true, cfg)
    }

If that sounds feasible to you, I can prepare a PR.

Hello Raphael,
Thanks for catching that up. Could you provide a MWE?
It looks okay to me, although I would set it up here because it's a setup in the renderer process instance https://github.com/m0n0l0c0/electron-router/blob/db1f1fa487bc98552eaa47a18e562fd4e92cc365/router.js#L117-L124
 win.on('close', this.clean.bind(this))

Best,
Guillermo

Your proposed solution would turn this line in Router.prototype.clean into a no-op:
https://github.com/m0n0l0c0/electron-router/blob/db1f1fa487bc98552eaa47a18e562fd4e92cc365/router.js#L420
As for a MWE: I'll try to provide one.

MWE
git clone https://gist.github.com/1ae2d7bbb2a8813787e02ec310d7f16b.git electron-router-mwe
cd electron-router-mwe
npm i && npm start

Running the above should log (among other things) something similar to the following message:
Uncaught TypeError: Cannot read property 'toUpperCase' of undefined
    source: /xxx/electron-router-mwe/node_modules/electron-router/router.js (412)

Hi @raphinesse,
You're absolutely right with this, I'm going with your solution.

Your proposed solution would turn this line in Router.prototype.clean into a no-op:
https://github.com/m0n0l0c0/electron-router/blob/db1f1fa487bc98552eaa47a18e562fd4e92cc365/router.js#L420
As for a MWE: I'll try to provide one.

Thank you for catching this up, I'll update right away

Thanks for handling this so quickly


Do not ignore docker history command errors.

Fixes #292

May I ask how this prevents docker save from writing an empty output file?


Update create-logical-networks.md

Updated variables and commands in static and dynamic methods to match.

@alkohli - can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off Changes look good.


Can not see variable's value in Android Studio debugger

Android studio 1.5.1
org.codehaus.groovy:groovy:2.4.5:grooid
classpath 'org.codehaus.groovy:gradle-groovy-android-plugin:0.3.8'
When in debbuger I alt-click on the variable, I get such an error-message:

When I place cursor over a variable, I see:

This issue seems to be related with https://github.com/groovy/groovy-android-gradle-plugin/issues/47
However in this case I see no way to switch between Groovy/Java

This is not an issue with the android-groovy plugin. Rather an issue with Android Studio.
Some workaround ideas are to use IntelliJ, or try using the watches window.
I would suggest filing a bug with Android Studio if you want to see this issue fixed. https://sites.google.com/a/android.com/tools/filing-bugs

I am still getting this error even using the watches window.
Android Studio 3.0.1 and Groovy plugin version 2.4.11.
Maybe you could explain how it's and Android Studio bug if it only effects Groovy projects? A bug report to Google results in them saying they don't support Groovy so what am I supposed to do here?
Even if this is an Android Studio bug it makes this project crippled and unusable so it should be a priority to fix it. As it stands I am now migrating my project off Groovy ASAP.


Group name white name list

For http will send escaped char，&-& So is Group nickname with those special chat, code cannot identify.
Use group_name=html.escape(group_name) maybe good

I just tried, special symbols such as facial expressions can be successfully matched in the configuration on MacOS :)

You can try on windows with group name like this:

OK, I'll  test this case on windows. By the way, for normal conditions, can you run successfully on windows？


They fix bugs in Combine, we update our awesome test suite!

...and fix them too.
The bug fixes happened in macOS 10.15.1

LGTM

  Generated by :no_entry_sign: Danger Swift against 8525c89b8c53707d1b3f61b5201d62c9a9c163ca


ArcCW Weapons do not work for NPCs.

When playing this addon with myself or others, it can get bland having Combine carry around the same Half-Life 2 weapons. SO, I enable an option in ArcCW Base that allows HL2 NPCs to spawn with ArcCW weapons. However, they do absolutely zero damage and this is only a problem with Lambda. This is just a phenomenal Campaign addon and it sucks that this one issue is holding me back. Please look into this or at least tell me how I can fix it myself. Thanks!

So, is this fix live or is it coming in another update?

The fix is merged, the workshop entry has to be yet updated.


Do not reset spree preferences starting from v2.9

We need this to remove deprecation warnings into extensions. Of course, this could let some spec fail on 2.9 or master.
This PR stops resetting preferences after each spec run and provides an alternative method to use into extensions (and stores) specs. This method will work for all supported Solidus versions and it will be easy to remove later since they have the same signature: we can just remove the require 'solidus_support/testing_support/preferences' for solidus support rails_helper without any change in the extensions.

@spaghetticode can you please review?

Better to wait for https://github.com/solidusio/solidus/pull/3275, which could change the signature of the stub_spree_preferences method.

I tried this branch in a real extension (https://github.com/solidusio/solidus_auth_devise/pull/166), waiting for the CI to run before merge here.


BREAKING CHANGE: ProxySettings: Add CurrentUser support - Fixes #423

Pull Request (PR) description
BREAKING CHANGE: This PR is refactors ProxySettings resource to add a new Target key parameter and removes the IsSingleResource parameter. This is to enable support for setting the Proxy for the CurrentUser account.
This Pull Request (PR) fixes the following issues

Fixes #423

Task list

[x] Added an entry under the Unreleased section of the change log in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[x] Resource documentation added/updated in README.md in resource folder.
[x] Resource parameter descriptions added/updated in schema.mof
and comment-based help.
[x] Comment-based help added/updated.
[x] Localization strings added/updated in all localization files as appropriate.
[x] Examples appropriately added/updated.
[x] Unit tests added/updated. See DSC Resource Testing Guidelines.
[x] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

@johlju - would you mind reviewing when you have time?

Thanks @johlju - appreciate that!


Make delivery of CloudTrail to CloudWatch Logs and SNS optional

Because we have a very AWS Lambda heavy workload, delivery to a Cloudwatch Logs generates a lot of costs. We don't need the logs, because the central S3 is enough. This PR makes both Cloudwatch Logs and SNS delivery optional (with the default remaining the same).

@wheerd Sorry for the delay. Providing a way to opt-out log delivery seems reasonable, thanks for the patch!


Recipe font size does not include recipe description

Currently the recipe description is stuck on a single font size even when the setting font size is changed.
It seems like the font size specified in the settings should also apply to the description:

What exactly are you using the font scale for?
The font scale got introduced to make long recipe names visible on the category screen.
If you need to scale the entire app you should consider your system wide text scale usually available in the accessibility settings.
I was actually thinking of removing the setting altogether and find a better way to prevent overflowing text.


added username filter

Checks for vulgar words when users are registering (based on an online list)
List is not directly stored as a text file but rather as an encrypted file, so we won't be directly storing said list lol

How would one use hash functions to check if a hashed string is a substring of a normal string? Symmetric encryption allows for data recovery, so its pretty straightforward there, but I'm not sure about hashing.
Ex. check if "hello" contains the substring "hel". "hel" is only available as a hashed string. "hello".hash() does not contain "hel".hash(). How to work around this?

I guess i could brute force and hash every possible substring in the checked string to see if it matches some hash, but is there another way to work around this?

Closing this for now, I think the better approach would be to setup better moderation tools and do a better job of verifying accounts.


Short Nonces in ECDSA

Hello @jvdsn   I saw your work on GitHub and decided to write to you as I have questions.
When creating ECDSA, it happens that some devices generate short Nonce.
Approximately 2 ^ 243 - 2 ^ 244
Accordingly, if Nonces is short, then it must contain null at the beginning.
That is, the first 3 bits of the Nonce contain a beginning null.
Given the known signature values [R, S, H (e)], can we define and calculate if the Nonce is short?
Is there a way to find out information about the first 3 bits of Nonces?

If the nonces are not generated uniformly at random in the interval [1, n - 1], then you have a biased nonce attack
If the modulus n is k bits, and the nonces are only l bits, with l < k, then the first (k - l) bits will be 0, yes
So if your modulus is 247 bits (weird choice of modulus), then the first 3 bits would be 0, yes

@jvdsn I'm interested in whether it is possible to determine that a specific signature contains short Nonce using the signature values [R, S, H (e)] for calculations? Is there a script or algorithm for these calculations?

In order to know if the nonce is biased, you need to know how it was generated. If you don't know that, like in your case where you only have the signature, then you can't know.


added my-name to the list of contributors

@owais4321 please review and merge this PR .

@all-contributors please add ibrahimijc for first-contribution

@all-contributors please add ibrahimijc for Content

@all-contributors please add ibrahimijc  for content


Simple sort by value in column

I have just started using your component. It is excellent. I am having trouble with the instruction in the FAQ though regarding sort -
Current answer: The little arrow icons near the aggregator dropdown allow you to sort renderer output either by row/column key (the default) or by rol/column total.
Which little arrow icons ? There is no reference to any specific example.
I am trying to show a pivot of number of people that have used our services more than once.
My pivot code is simple :
$(function(){
Papa.parse("factServics.csv", {
download: true,
skipEmptyLines: true,
complete: function(parsed){
$("#output1").pivot(parsed.data, {
rows: ["sEmailAddress"],
cols: ["nStatus"],
filter: function(record){ return record["nStatus"]!= "Canceled"; },
renderer: $.pivotUtilities.renderers["Heatmap"],
rendererOptions: {
table: {
clickCallback: function(e, value, filters, pivotData){
var services = [];
pivotData.forEachMatchingRecord(filters,
function(record){ services.push(record["sServiceName"]); });
alert(services.join("\n"));
}
}
}
});
}
});
});
The output is attached. I would like to either filter out the totals of 1 or sort the totals in descending order.
ForIssueReport.xlsx

Got it. Refered to example :
https://pivottable.js.org/examples/mps_prepop.html


Add sphinx documentation

This adds a sphinx documentation of the markdown files in the doc/ folder. It makes navigating it a bit easier, as there is a table of contents etc. We can also potentially auto-generate some docs, e.g. for scripts.
A preview of the rendered version can be seen at https://test-doc-icubam.readthedocs.io/en/latest/index.html There is quite a few things that can be improved in the docs (there are some outdated parts), but I'd like to do that in a separate PR after this one,
To make it work, we need to,

create a pyodide project at https://readthedocs.org/ for the icubam/icubam repo (I don't have enough permissions to do it, currently using my fork for the demo). Add me as a co-maintainer (login: rth) and I'll setup the rest, if needed, though it should mostly work out of the box.
(optional) by default the docs would be at icubam.readthedocs.io to use the icubam.net domain we would need to setup a CNAME from e.g. docs.icubam.net to readthedocs.io (https://docs.readthedocs.io/en/stable/custom_domains.html)

https://icubam.readthedocs.io/en/latest/  is now working.