text:
Should clearing input's searchStr and tabbing away remove scope.selectedObject?

I fixed it by calling callOrAssign(undefined) in the hideTimer
      scope.hideResults = function(event) {
          if (mousedownOn && mousedownOn.indexOf('angucomplete') >= 0) {
            mousedownOn = null;
          }
          else {
            hideTimer = $timeout(function() {
              clearResults();
              scope.$apply(function() {
                if (scope.searchStr && scope.searchStr.length > 0) {
                  inputField.val(scope.searchStr);
                }
                //new: clear selectedObject
                else {
                  callOrAssign(undefined);
                }
              });
            }, BLUR_TIMEOUT);

Could you describe the exact step that user would take?
Is it about receiving angucomplete-alt:clearInput event then hitting tab?

Thanks for following up, Nozaki.
Originally, I was trying to keep my model and autocomplete display in sync.
If I selected an item in the autocomplete, the model would update and they would match.
However, if I cleared the autocomplete, the model would not update to “undefined” yet the autocomplete would be blank.
I decided to change my UI to always clear the value in the autocomplete after selection.
angucomplete-alt( …  clear-selected="true"  …)
            -David

From: Hidenari Nozaki [mailto:notifications@github.com]
Sent: Monday, June 22, 2015 2:46 PM
To: ghiden/angucomplete-alt
Cc: Garrett, David
Subject: Re: [angucomplete-alt] Should clearing input's searchStr and tabbing away remove scope.selectedObject? (#182)
Could you describe the exact step that user would take?
Is it about receiving angucomplete-alt:clearInput event then hitting tab?
—
Reply to this email directly or view it on GitHubhttps://github.com/ghiden/angucomplete-alt/issues/182#issuecomment-114215960.

Thanks for making this change.
I’m trying to use angucomplete-alt like a typical dropdown control, but with filtering.
Is there an easy way for the selected-object.originalObject to two-way bind to a property on my model?
If model.state changes, I’d like the angucomplete input to show the corresponding state as well.
Model: { states: [‘Georgia’,…], state: ‘Georgia’ }
            angucomplete-alt(
                            placeholder="Choose State…”
                            selected-object="model.state"
                            local-data="model.states"
                            search-fields="?"
                            title-field="?"
                            minlength="0"
                            input-class="form-control form-control-small"
                            class="ng-isolate-scope")

[http://cdn8view1.turner.com/tbs/tbscomm/emailgraphics/logosig_mss.png]

DAVID GARRETT | APPLICATIONS ARCHITECT | MEDIA SOFTWARE & SERVICES
O. 404-575-6310 | C. 404-583-1970 | DAVID.GARRETT@TURNER.COMmailto:DAVID.GARRETT@TURNER.COM
TURNER BROADCASTING SYSTEM, INC. | 1000 TECHWOOD DRIVE NW ATLANTA, GA 30318
From: Hidenari Nozaki [mailto:notifications@github.com]
Sent: Tuesday, June 23, 2015 5:17 AM
To: ghiden/angucomplete-alt
Cc: Garrett, David
Subject: Re: [angucomplete-alt] Should clearing input's searchStr and tabbing away remove scope.selectedObject? (#182)
Closed #182https://github.com/ghiden/angucomplete-alt/issues/182 via bd7cfddhttps://github.com/ghiden/angucomplete-alt/commit/bd7cfdd5301f274471da299b21d45872bfb97a37.
—
Reply to this email directly or view it on GitHubhttps://github.com/ghiden/angucomplete-alt/issues/182#event-337591573.

Hi David,
Angucomplete-alt does not provide 2-way data binding. This behavior is from the original Angucomplete. The closest you can do is use initial-value. Have a look at the example 9 http://ghiden.github.io/angucomplete-alt/#example9

authors: davidmgarrett ghiden

repo: ghiden/angucomplete-alt


text:
vt: add documentation for all control sequence types

There are more than 5 types of control sequences. Define each and
provide a simple example or syntax for each.

Perfectly done thanks

source: gharchive/pull-request

authors: mitchellh rockorager

repo: ghostty-org/website

license: MIT

license_type: permissive

license_source: github-api


text:
About use in docker container

We try to use pyftpdlib in docker contianer...  But it can't useable in docker container.
here is link for Dockerfile https://github.com/u-u-z/pyftpdlib-test/
It maybe wrong in our Dockerfile...
But we use the same( host environment ) method install it to docker container  in manual .
Many images have been tried, but without success. :-(
What's the happen go on  > <...

In ftp client ... it's response 257 "/" is the current directory.
It can't get the directory list.

Not sure about Docker, sorry, but I doubt this is a bug related to pyftpdlib. Closing.

source: gharchive/issue

authors: giampaolo u-u-z

repo: giampaolo/pyftpdlib

license: mit

license_source: bigquery


text:
Update README.rst

fixed link to code samples

the first pull request wasn't right and didn't get all the links.


text:
Reconciliation

Providers as DockerSwarm are able to manage reconciliation by them self but what happen with DigitalOcean or other that are not able to manage this behavior?
At the moment nothing happen. We are not able to detect when a node is down and to replace them with new instances. That's something that we need to address as soon as possible.

[ ] Basic API
[ ] Provider: SwarmMode
[ ] Provider: DigitalOcean

https://github.com/gianarb/orbiter/issues/17

repo: gianarb/orbiter


text:
Include the MC endpoint in log message to indeicate which MC

What this PR does
Fixes https://github.com/giantswarm/giantswarm/issues/30298
Include the MCs API server endpoint in the log output to make it clear which cluster we are running the tests against.
Checklist

[x] Update changelog in CHANGELOG.md.

Trigger e2e tests

/run cluster-test-suites

Hmmm.... doesn't really help with CAPVCD or CAPV 🤔
{"level":"info","ts":"2024-04-02T13:04:50Z","msg":"Checking connection to MC is available. API Endpoint: https://10.205.9.6:6443/"}
  {"level":"info","ts":"2024-04-02T13:04:51Z","msg":"Workload cluster name: t-t4gtffyyjgsv9nlrxt"}

/run cluster-test-suites

Awwww yeah!
/app/internal/suite/setup.go:32
  {"level":"info","ts":"2024-04-02T15:17:20Z","msg":"Checking connection to MC is available."}
  {"level":"info","ts":"2024-04-02T15:17:20Z","msg":"MC API Endpoint: 'https://10.10.222.230:6443/'"}
  {"level":"info","ts":"2024-04-02T15:17:20Z","msg":"MC name: 'gcapeverde'"}

repo: giantswarm/cluster-test-suites


text:
Device Auth Flow

What does this PR do?
Add support for "device authentication flow" to the login command and introduce a new --device-auth flag to activate it.
What is the effect of this change to users?
When using kubectl-gs login with the --device-auth flag, the users will be able to log in without the need to open a browser window on the same machine that runs the kubectl-gs process.
Opening a browser window and going through the standard authentication flow between Dex and the identity provider is still required, but it can happen asynchronously - in a different environment or even on a different machine.
When the login process in kubectl-gs needs to open a browser window, it pauses the execution and prints a URL, which needs to be opened in the browser. When the user is finished with the in-browser authentication, the login process in kubectl-gs can be resumed and finished.
What does it look like?
$ kubectl gs login installation --device-auth
Open this URL in the browser to log in:
https://dex.basedomain.io/device?user_code=USER-CODE
Press ENTER when ready to continue

Then the user needs to copy the URL, open it in a browser and go through the authentication process.
Once it is successfully finished, the user can go back to kubectl-gs, hit ENTER and...
Logged in successfully as 'user-device' on cluster 'installation'.

A new kubectl context 'gs-installation' has been created and selected. To switch back to this context later, use either of these commands:

  kubectl gs login installation
  kubectl config use-context gs-installation

Any background context you can provide?
Towards https://github.com/giantswarm/roadmap/issues/1933
What is needed from the reviewers?

Try to log in using the device authentication flow and verify that it works.
Check if the instructions provided by the command and its user experience in general make sense

Do the docs need to be updated?
Yes
Should this change be mentioned in the release notes?

[x] CHANGELOG.md has been updated

Is this a breaking change?
No

Interesting. I also tested it on Golem and it worked for me. Maybe it behaves differently on different operating systems? I will investigate.
Regarding the context name - it is intentional. Kubectl-gs relies heavily on context name and derives it from various input data, so I thought it would be safer to change the user name and keep the same context name. It may be possible to change the context name as well, but then it might be necessary to make adjustments in many other places of kgs. If I add it to this PR, it may grow in size quite a bit. Is that OK?

I think using the same context name is fine. So far it does not seem to cause any issues.
As for golem, I'm not really sure what the problem is. I can try to debug a bit when I have time. I thought it might be related to CAPA somehow but it must be something else if you don't see the same thing.

The reported issues have been addressed:
When the context already exists and the --device-auth flag is ignored, kgs prints a new message in yellow colour:
A valid 'gs-codename' context already exists, there is no need to log in again, ignoring the 'device-flow' flag.
Parsing of JWTs has been refactored. That should help prevent the parsing error observed in Golem.

authors: anvddriesch vvondruska

repo: giantswarm/kubectl-gs


text:
default ingress controller

We as Giantswarm want to be able to provide a default ingress controller.
Discovery:
how to deploy a default ingress controller?

Deploy it like any other default app. Make sure it's configurable by the customer in case they want to use their own ingress controller
Do we need an extra LB?
What does "extra" mean? Generally an ingress only makes sense if it's bound to a LB on the provider side.
How to have multiple IC running as smooth as possible?
Observe best practices regarding running multiple ingress controller. Utilize kyverno to prevent known issues like resolving foreign ingress classes. Highly depends on the specific case.

In regards to requirements for default ingress controller for SSO we started a live doc: https://docs.google.com/document/d/1T5BaiX5adnKGZobpIqvkovE1vUb8QcTPBG-KZbjPFHY/edit

This is phased kind of ambiguously.

Do we want to provide a default ingress controller for customers to use?
Does our infrastructure (e.g. dex) require a default ingress controller on WCs?

As we see no point in "forcing" an ingress controller on the customer if they can just as well install it themselves if the need one, we're assuming that it's about GS requiring a default ingress controller.

If this is about having an ingress route to WC clusters for GS requirements we also discussed the option of having a central ingress controller on the MC that routs traffic to the WC. That way we only need one provider LB for alll WCs

Next steps:

Please get answers for the outlined questions from the stakeholders
We want to investigate if one ingress controller can resolve multiple ingress classes
Get specific requirements from Big Mac regarding SSO

also see this issue https://github.com/giantswarm/giantswarm/issues/20858

repo: giantswarm/roadmap


text:
Travis Nix job exceeded the maximum log length

The Nix builds are failing on Travis because
The job exceeded the maximum log length, and has been terminated.

I see you've been working on the Nix build @vaibhavsagar
https://github.com/gibiansky/IHaskell/pull/852

Closed by #1103.

authors: jamesdbrock vaibhavsagar

repo: gibiansky/IHaskell


text:
Asynchronous i/o not working well

Using the IPython kernel, executing the following code cell
print("Hello, what is your name: ", end="")
name = input()
print(name)
print("And what is your age: ", end="")
age = input()
print(age)

will result in an interactive dialog, where prompts, inputs, and responses are nicely interleaved.
However, trying the same thing with the IHaskell kernel fails:
dialog :: IO()
dialog = do
  putStr "Give me a string: "
  line <- getLine
  putStrLn line
  putStr "Give me another one: "
  line2 <- getLine
  putStrLn line2

dialog

With my locally installed IHaskell kernel (under MacOS; IHaskell 0.9.0.3 GHC 8.2.2), the input is read, without any output being shown, and once cell execution is finished all the output is shown together. I.e., i/o is not asynchronous.
With the IHaskell kernel on https://mybinder.org/v2/gh/gibiansky/IHaskell/master (IHaskell 0.9.1.0 GHC 8.2.2), you get this exception:
<stdin>: hGetLine: end of file

Currently, this is a showstopper for our educational use of IHaskell.

This issue is actually totally unrelated to IHaskell, but actually due to the default buffering of stdout in Haskell (its probably line buffered). When you call putStr the runtime will wait for you to print a newline.
The solution is to add a hFlush stdout after each putStr, or maybe even define a function:
putStrFlush :: String -> IO ()
putStrFlush str = do
   putSrr str
   hFlush stdout

and use that instead.

@erikd Indeed, it still does not work satisfactorily with hFlush.  But it is a step forward.
In fact, using putStrLn instead of putStr already helps in simple programs.
When there is more/slow output, the input box is briefly flashed on the screen (actually, you see this box before the preceding output was printed) and it then disappears. After this, the kernel hangs, and needs restarting.

We reimplement our IO handling, so maybe the problem is there?

authors: erikd vaibhavsagar wstomv


text:
Reproducing the results in the Paper

Dear Spyros Gidaris, Praveer Singh and Nikos Komodakis,
i have read your paper "Unsupervised Representation Learning by Predicting Image Rotations" and was impressed by your work and the astonishing results receive by pretraining a "RotNet" on the rotation task and later train classifiers on top of the feature maps.
I have downloaded your code from GitHub and tried to reproduce the values in Table 1 for a RotNet with 4 conv. blocks. However, running "run_cifar10_based_unsupervised_experiments.sh" and altering line 33 and for 'conv1' also line 31 in the config file "CIFAR10_MultLayerClassifier_on_RotNet_NIN4blocks_Conv2_feats.py", i obtain slightly lower values than in the paper especially for the fourth block:
Rotation Task: 93,65  (Running your Code) / ---
ConvBlock1: 84,65 (Running your Code) / 85,07 (Paper)
ConvBlock2: 88,89  (Running your Code) / 89,06 (Paper)
ConvBlock3: 85,88 (Running your Code) / 86,21 (Paper)
ConvBlock4: 54,04 (Running your Code) / 61,73 (Paper)
Are there further things I need to consider before running the code to achieve the results in the paper? I have used a GeForce GPX 1070 to run the experiment.

Excuse me, I am a beginner, I want to ask you a question: the author omitted the detail code of function train_step, evaluation_step, without this part of the code, is not training? Did you complete it? Looking forward to your reply. Thank you @Xenovortex

It is a year ago, so I don't remember in detail. But to my knowledge, those functions are implemented and it should work out of the box. Maybe I didn't exactly understand your question/problem.
Also I didn't my own implementation of the FeatureRotNet (based on the knowledge provided in the paper), if you need some reference you can have a look at it, but i am pretty sure their original code should work as well.

Sorry, I didn't look at the code carefully before. I have studied it carefully these two days and found that the code can work successfully.Thanks for your reply. @Xenovortex

no problem

Hi, @Xenovortex .
Have you reproduced supervised NIN? I have reproduced supervised NIN as the paper setting, which is 88.23 in my experimental results, but the result of the paper report is 92.80.
Thank you.

Yes, I did reproduced the supervised NIN. With my code (https://github.com/Xenovortex/Implementation-FeatureLearningRotNet), I achieved slightly lower accuracy than in the paper but pretty close:
Total Accuracy: 91.39 %
Accuracy by classes:
plane: 91.60%
car: 95.90%
bird: 87.00%
cat: 83.20%
deer: 92.10%
dog: 85.50%
frog: 94.80%
horse: 93.90%
ship: 94.70%
truck: 95.20%
However, running the code of the authors, I got 92.81%.

Yes, I did reproduced the supervised NIN. With my code (https://github.com/Xenovortex/Implementation-FeatureLearningRotNet), I achieved slightly lower accuracy than in the paper but pretty close:
Total Accuracy: 91.39 %
Accuracy by classes:
plane: 91.60%
car: 95.90%
bird: 87.00%
cat: 83.20%
deer: 92.10%
dog: 85.50%
frog: 94.80%
horse: 93.90%
ship: 94.70%
truck: 95.20%
However, running the code of the authors, I got 92.81%.

Thank you for your reply.
The num_stages is 3 in the author code of supervised NIN (that is nine convolutional layers), but num_stages is 4 in the unsupervised NIN architecture (that is twelve convolutional layers), so I am a bit confused. Such unsupervised results and supervised results may be a bit unfair.

I mean, if you think it is an unfair comparison. Then, there is really nothing stopping you from changing num_stages to 3 or 4 respectively and run the authors code to see if it makes a difference.

authors: Chen-Song Pengyujiao Xenovortex

repo: gidariss/FeatureLearningRotNet


text:
Firebase!

Hello.
I changed the information in the database, added the rules in the firebase, but when I run the application, it does not add the information in the database.
Is there an ".json" file for me to create the database?
Thank you, hug.

Did you update the Firebase config settings with your own Firebase project information? You can find these settings in the app.module.ts file
// YOUR SETTINGS GOES HERE!
export const firebaseConfig = {
  apiKey: "AIzaSyAjiJc9cXvd3bzl-aW0wbQC6sajr6RH5hg",
  authDomain: "brilliant-inferno-1044.firebaseapp.com",
  databaseURL: "https://brilliant-inferno-1044.firebaseio.com",
  storageBucket: "brilliant-inferno-1044.appspot.com",
  messagingSenderId: "1097950001655"
};

I clone the project, made the changes mentioned, added the rules in the Firebase settings, but still does not add the data in the firebase.
This message appears on the console:
[16:20:18] tslint: src / pages / mysettings / settings / settings.ts, line: 8
             Unused import: 'PersonalProfilePage'
L7: import {AboutPage} from '../../../pages/about/about';
        L8: import {PersonalProfilePage} from '../../myinfo/personalprofile/personalprofile';
        L9: import {ProfileDetailsPage} from '../../myinfo/profiledetails/profiledetails';
[16:20:18] tslint: src / app / app.component.ts, line: 23
             Unused import: 'firebase'
L22: // firebase
       L23: import firebase from 'firebase';
When I try to add a new user to the application, the following message appears:
Sign Up Failed
Your account has been disabled. Please contact support!

When I use your database information, the application runs normally, but when I change to my database it does not.
Should it be some mistake in the rules?

Hi @jowbjj, in your own Firebase project select Authentication in the left menu and then select the SIGN-IN METHOD tab. Make sure you enable the Email/Password option.
Let me know how it goes

Worked perfectly!
Created the entire database structure.
Thank you very much!

Glad to hear!

authors: gigocabrera jowbjj


text:
OneDrive

OneDrive Logo SVG

The link is not working, use this one instead.
Microsoft Office OneDrive (2019–present).svg

Added in 028450df5370ab04535e3d1b0f5e343232d94d2d
Thanks

authors: chasegiunta gilbarbara paulwaldmann

repo: gilbarbara/logos


text:
Add Ghostdown for live editing. Add ability to add more categories 'fold...

This PR includes changes that allow for live editing of the markdown, save changes to the markdown page, deleting a page, adding a new page and adding a new category from the web interface

Thanks for the PR @matthiassb.
You've done a lot of work, so I'll need to look at this in-depth before merging.
Will update with status changes

Reviewing this now

This all worked on the first try, excellent PR.
Thanks for this PR @matthiassb, lots of people were wanting an online editor including myself.

Cool! Glad to be of help :)

@matthiassb, I'm in the process of moving dependencies like jQuery, Bootstrap, and such to Bower to keep things clean and audit-able.
When searching for "ghostdown" on Bower, I didn't find any results. I do see that your Ghostdown files contain CodeMirror, so could you provide some more insight on which pieces are reusable so I can move them to Bower?
I did a quick Google search for "Ghostdown" and found this, but I wanted to check with you since you added Ghostdown to the project. https://github.com/timsayshey/Ghost-Markdown-Editor

authors: matthiassb ryanlelek

repo: gilbitron/Raneto


text:
Mapping libxul.so on Linux panics in xmas_elf::ElfFile::get_string due to bad slice

I'm not having any luck using addr2line to symbolicate a Firefox libxul.so on Linux.
My code:
extern crate addr2line;

fn main() {
    let mapping = addr2line::Options::default()
        .build(
            "/home/mstange/code/mozilla/obj-x86_64-pc-linux-gnu/dist/bin/libxul.so",
        ).expect("Mapping libxul.so failed");
    println!("0x33e4812: {:?}", mapping.locate(0x33e4812));
}

Output:
    Finished dev [unoptimized + debuginfo] target(s) in 0.0 secs
     Running `target/debug/addr2line-libxul`
thread 'main' panicked at 'slice index starts at 77309416265 but ends at 1434107856', /checkout/src/libcore/slice/mod.rs:741:4
stack backtrace:
   0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace
             at /checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::_print
             at /checkout/src/libstd/sys_common/backtrace.rs:71
   2: std::panicking::default_hook::{{closure}}
             at /checkout/src/libstd/sys_common/backtrace.rs:60
             at /checkout/src/libstd/panicking.rs:380
   3: std::panicking::default_hook
             at /checkout/src/libstd/panicking.rs:396
   4: std::panicking::rust_panic_with_hook
             at /checkout/src/libstd/panicking.rs:611
   5: std::panicking::begin_panic_new
             at /checkout/src/libstd/panicking.rs:553
   6: std::panicking::begin_panic_fmt
             at /checkout/src/libstd/panicking.rs:521
   7: rust_begin_unwind
             at /checkout/src/libstd/panicking.rs:497
   8: core::panicking::panic_fmt
             at /checkout/src/libcore/panicking.rs:92
   9: core::slice::slice_index_order_fail
             at /checkout/src/libcore/slice/mod.rs:741
  10: <core::ops::range::Range<usize> as core::slice::SliceIndex<[T]>>::index
             at /checkout/src/libcore/slice/mod.rs:864
  11: <core::ops::range::RangeFrom<usize> as core::slice::SliceIndex<[T]>>::index
             at /checkout/src/libcore/slice/mod.rs:947
  12: core::slice::<impl core::ops::index::Index<I> for [T]>::index
             at /checkout/src/libcore/slice/mod.rs:717
  13: xmas_elf::ElfFile::get_str_table::{{closure}}
             at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/xmas-elf-0.3.0/src/lib.rs:97
  14: <core::result::Result<T, E>>::map
             at /checkout/src/libcore/result.rs:458
  15: xmas_elf::ElfFile::get_str_table
             at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/xmas-elf-0.3.0/src/lib.rs:97
  16: xmas_elf::ElfFile::get_string
             at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/xmas-elf-0.3.0/src/lib.rs:72
  17: xmas_elf::sections::SectionHeader::get_name::{{closure}}
             at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/xmas-elf-0.3.0/src/sections.rs:92
  18: <core::result::Result<T, E>>::and_then
             at /checkout/src/libcore/result.rs:602
  19: xmas_elf::sections::SectionHeader::get_name
             at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/xmas-elf-0.3.0/src/sections.rs:90
  20: xmas_elf::ElfFile::find_section_by_name
             at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/xmas-elf-0.3.0/src/lib.rs:84
  21: <object::elf::Elf<'a> as object::object_trait::Object<'a>>::get_section
             at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/object-0.1.0/src/elf.rs:13
  22: <addr2line::DebugInfo<'object, Endian>>::new
             at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/addr2line-0.3.0/src/lib.rs:271
  23: addr2line::Mapping::symbolicate
             at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/addr2line-0.3.0/src/lib.rs:251
  24: addr2line::Mapping::new_inner::{{closure}}::{{closure}}
             at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/addr2line-0.3.0/src/lib.rs:230
  25: <owning_ref::OwningHandle<O, H>>::try_new
             at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/owning_ref-0.2.4/src/lib.rs:475
  26: addr2line::Mapping::new_inner::{{closure}}
             at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/addr2line-0.3.0/src/lib.rs:228
  27: <owning_ref::OwningHandle<O, H>>::try_new
             at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/owning_ref-0.2.4/src/lib.rs:475
  28: addr2line::Mapping::new_inner
             at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/addr2line-0.3.0/src/lib.rs:225
  29: addr2line::Options::build
             at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/addr2line-0.3.0/src/lib.rs:175
  30: addr2line_libxul::main
             at src/main.rs:4
  31: __rust_maybe_catch_panic
             at /checkout/src/libpanic_unwind/lib.rs:98
  32: std::rt::lang_start
             at /checkout/src/libstd/panicking.rs:458
             at /checkout/src/libstd/panic.rs:361
             at /checkout/src/libstd/rt.rs:59
  33: main
  34: __libc_start_main
  35: _start

The Firefox build I'm testing with is a regular local opt build.

We're in the process of moving to goblin for object file needs -- will need STR + test case to see if this panic still reproduces once we've moved this crate over as well.
Thanks @mstange !

I've experimentally updated the object dependency in addr2line from 0.1.0 to 0.3.0, and now it's no longer panicking, but the mapping returns an error:
   Compiling addr2line v0.3.0 (file:///home/mstange/code/addr2line)
   Compiling addr2line-libxul v0.1.0 (file:///home/mstange/code/addr2line-libxul)
    Finished dev [unoptimized + debuginfo] target(s) in 5.66 secs
     Running `target/debug/addr2line-libxul`
thread 'main' panicked at 'Mapping libxul.so failed: Error(Msg("failed to analyze debug information"), State { next_error: Some(Error(Msg("encountered invalid compilation unit"), State { next_error: Some(Error(InvalidDebugSymbols(SubroutineMissingName(483643027, 3111142)), State { next_error: None, backtrace: Some(stack backtrace:
   0:     0x5628b7fb0b94 - backtrace::backtrace::libunwind::trace
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.2/src/backtrace/libunwind.rs:53
                         - backtrace::backtrace::trace<closure>
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.2/src/backtrace/mod.rs:42
   1:     0x5628b7fb0f5f - backtrace::capture::{{impl}}::new
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.2/src/capture.rs:64
   2:     0x5628b7fa5b9c - error_chain::make_backtrace
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/error-chain-0.7.2/src/lib.rs:411
   3:     0x5628b7fa5c5f - error_chain::{{impl}}::default
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/error-chain-0.7.2/src/lib.rs:462
   4:     0x5628b7f1336c - addr2line::errors::{{impl}}::from_kind
                        at /home/mstange/code/addr2line-libxul/<error_chain_processed macros>:48
   5:     0x5628b7f13659 - addr2line::errors::{{impl}}::from
                        at /home/mstange/code/addr2line-libxul/<error_chain_processed macros>:8
   6:     0x5628b7f0aa38 - addr2line::{{impl}}::parse<gimli::endianity::LittleEndian>
                        at /home/mstange/code/addr2line/src/lib.rs:732
   7:     0x5628b7effc95 - addr2line::{{impl}}::new<gimli::endianity::LittleEndian>
                        at /home/mstange/code/addr2line/src/lib.rs:287
   8:     0x5628b7efeeab - addr2line::{{impl}}::symbolicate
                        at /home/mstange/code/addr2line/src/lib.rs:250
   9:     0x5628b7efe8ed - addr2line::{{impl}}::new_inner::{{closure}}::{{closure}}
                        at /home/mstange/code/addr2line/src/lib.rs:229
  10:     0x5628b7ebfa9b - owning_ref::{{impl}}::try_new<alloc::boxed::Box<object::elf::Elf>,alloc::boxed::Box<addr2line::EndianDebugInfo>,closure,addr2line::errors::Error>
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/owning_ref-0.2.4/src/lib.rs:475
  11:     0x5628b7efebd0 - addr2line::{{impl}}::new_inner::{{closure}}
                        at /home/mstange/code/addr2line/src/lib.rs:227
  12:     0x5628b7ebf7bb - owning_ref::{{impl}}::try_new<alloc::boxed::Box<memmap::Mmap>,alloc::boxed::Box<addr2line::MmapDerived>,closure,addr2line::errors::Error>
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/owning_ref-0.2.4/src/lib.rs:475
  13:     0x5628b7efe4e5 - addr2line::{{impl}}::new_inner
                        at /home/mstange/code/addr2line/src/lib.rs:223
  14:     0x5628b7e5f941 - addr2line::{{impl}}::build<&str>
                        at /home/mstange/code/addr2line/src/lib.rs:173
  15:     0x5628b7e5fa17 - addr2line_libxul::main
                        at src/main.rs:4
  16:     0x5628b7fd63dc - panic_unwind::__rust_maybe_catch_panic
                        at /checkout/src/libpanic_unwind/lib.rs:98
  17:     0x5628b7fcfbf4 - std::panicking::try<(),closure>
                        at /checkout/src/libstd/panicking.rs:458
                         - std::panic::catch_unwind<closure,()>
                        at /checkout/src/libstd/panic.rs:361
                         - std::rt::lang_start
                        at /checkout/src/libstd/rt.rs:59
  18:     0x5628b7e5fbd2 - main
  19:     0x7ff6e19ba3f0 - __libc_start_main
  20:     0x5628b7e59409 - _start
  21:                0x0 - <unknown>) })), backtrace: Some(stack backtrace:
   0:     0x5628b7fb0b94 - backtrace::backtrace::libunwind::trace
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.2/src/backtrace/libunwind.rs:53
                         - backtrace::backtrace::trace<closure>
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.2/src/backtrace/mod.rs:42
   1:     0x5628b7fb0f5f - backtrace::capture::{{impl}}::new
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.2/src/capture.rs:64
   2:     0x5628b7fa5b9c - error_chain::make_backtrace
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/error-chain-0.7.2/src/lib.rs:411
   3:     0x5628b7fa5c5f - error_chain::{{impl}}::default
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/error-chain-0.7.2/src/lib.rs:462
   4:     0x5628b7f1336c - addr2line::errors::{{impl}}::from_kind
                        at /home/mstange/code/addr2line-libxul/<error_chain_processed macros>:48
   5:     0x5628b7f13659 - addr2line::errors::{{impl}}::from
                        at /home/mstange/code/addr2line-libxul/<error_chain_processed macros>:8
   6:     0x5628b7f0aa38 - addr2line::{{impl}}::parse<gimli::endianity::LittleEndian>
                        at /home/mstange/code/addr2line/src/lib.rs:732
   7:     0x5628b7effc95 - addr2line::{{impl}}::new<gimli::endianity::LittleEndian>
                        at /home/mstange/code/addr2line/src/lib.rs:287
   8:     0x5628b7efeeab - addr2line::{{impl}}::symbolicate
                        at /home/mstange/code/addr2line/src/lib.rs:250
   9:     0x5628b7efe8ed - addr2line::{{impl}}::new_inner::{{closure}}::{{closure}}
                        at /home/mstange/code/addr2line/src/lib.rs:229
  10:     0x5628b7ebfa9b - owning_ref::{{impl}}::try_new<alloc::boxed::Box<object::elf::Elf>,alloc::boxed::Box<addr2line::EndianDebugInfo>,closure,addr2line::errors::Error>
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/owning_ref-0.2.4/src/lib.rs:475
  11:     0x5628b7efebd0 - addr2line::{{impl}}::new_inner::{{closure}}
                        at /home/mstange/code/addr2line/src/lib.rs:227
  12:     0x5628b7ebf7bb - owning_ref::{{impl}}::try_new<alloc::boxed::Box<memmap::Mmap>,alloc::boxed::Box<addr2line::MmapDerived>,closure,addr2line::errors::Error>
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/owning_ref-0.2.4/src/lib.rs:475
  13:     0x5628b7efe4e5 - addr2line::{{impl}}::new_inner
                        at /home/mstange/code/addr2line/src/lib.rs:223
  14:     0x5628b7e5f941 - addr2line::{{impl}}::build<&str>
                        at /home/mstange/code/addr2line/src/lib.rs:173
  15:     0x5628b7e5fa17 - addr2line_libxul::main
                        at src/main.rs:4
  16:     0x5628b7fd63dc - panic_unwind::__rust_maybe_catch_panic
                        at /checkout/src/libpanic_unwind/lib.rs:98
  17:     0x5628b7fcfbf4 - std::panicking::try<(),closure>
                        at /checkout/src/libstd/panicking.rs:458
                         - std::panic::catch_unwind<closure,()>
                        at /checkout/src/libstd/panic.rs:361
                         - std::rt::lang_start
                        at /checkout/src/libstd/rt.rs:59
  18:     0x5628b7e5fbd2 - main
  19:     0x7ff6e19ba3f0 - __libc_start_main
  20:     0x5628b7e59409 - _start
  21:                0x0 - <unknown>) })), backtrace: Some(stack backtrace:
   0:     0x5628b7fb0b94 - backtrace::backtrace::libunwind::trace
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.2/src/backtrace/libunwind.rs:53
                         - backtrace::backtrace::trace<closure>
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.2/src/backtrace/mod.rs:42
   1:     0x5628b7fb0f5f - backtrace::capture::{{impl}}::new
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.2/src/capture.rs:64
   2:     0x5628b7fa5b9c - error_chain::make_backtrace
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/error-chain-0.7.2/src/lib.rs:411
   3:     0x5628b7fa5c5f - error_chain::{{impl}}::default
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/error-chain-0.7.2/src/lib.rs:462
   4:     0x5628b7f1336c - addr2line::errors::{{impl}}::from_kind
                        at /home/mstange/code/addr2line-libxul/<error_chain_processed macros>:48
   5:     0x5628b7f13659 - addr2line::errors::{{impl}}::from
                        at /home/mstange/code/addr2line-libxul/<error_chain_processed macros>:8
   6:     0x5628b7f0aa38 - addr2line::{{impl}}::parse<gimli::endianity::LittleEndian>
                        at /home/mstange/code/addr2line/src/lib.rs:732
   7:     0x5628b7effc95 - addr2line::{{impl}}::new<gimli::endianity::LittleEndian>
                        at /home/mstange/code/addr2line/src/lib.rs:287
   8:     0x5628b7efeeab - addr2line::{{impl}}::symbolicate
                        at /home/mstange/code/addr2line/src/lib.rs:250
   9:     0x5628b7efe8ed - addr2line::{{impl}}::new_inner::{{closure}}::{{closure}}
                        at /home/mstange/code/addr2line/src/lib.rs:229
  10:     0x5628b7ebfa9b - owning_ref::{{impl}}::try_new<alloc::boxed::Box<object::elf::Elf>,alloc::boxed::Box<addr2line::EndianDebugInfo>,closure,addr2line::errors::Error>
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/owning_ref-0.2.4/src/lib.rs:475
  11:     0x5628b7efebd0 - addr2line::{{impl}}::new_inner::{{closure}}
                        at /home/mstange/code/addr2line/src/lib.rs:227
  12:     0x5628b7ebf7bb - owning_ref::{{impl}}::try_new<alloc::boxed::Box<memmap::Mmap>,alloc::boxed::Box<addr2line::MmapDerived>,closure,addr2line::errors::Error>
                        at /home/mstange/.cargo/registry/src/github.com-1ecc6299db9ec823/owning_ref-0.2.4/src/lib.rs:475
  13:     0x5628b7efe4e5 - addr2line::{{impl}}::new_inner
                        at /home/mstange/code/addr2line/src/lib.rs:223
  14:     0x5628b7e5f941 - addr2line::{{impl}}::build<&str>
                        at /home/mstange/code/addr2line/src/lib.rs:173
  15:     0x5628b7e5fa17 - addr2line_libxul::main
                        at src/main.rs:4
  16:     0x5628b7fd63dc - panic_unwind::__rust_maybe_catch_panic
                        at /checkout/src/libpanic_unwind/lib.rs:98
  17:     0x5628b7fcfbf4 - std::panicking::try<(),closure>
                        at /checkout/src/libstd/panicking.rs:458
                         - std::panic::catch_unwind<closure,()>
                        at /checkout/src/libstd/panic.rs:361
                         - std::rt::lang_start
                        at /checkout/src/libstd/rt.rs:59
  18:     0x5628b7e5fbd2 - main
  19:     0x7ff6e19ba3f0 - __libc_start_main
  20:     0x5628b7e59409 - _start
  21:                0x0 - <unknown>) })', /checkout/src/libcore/result.rs:860:4
stack backtrace:
   0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace
             at /checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::_print
             at /checkout/src/libstd/sys_common/backtrace.rs:71
   2: std::panicking::default_hook::{{closure}}
             at /checkout/src/libstd/sys_common/backtrace.rs:60
             at /checkout/src/libstd/panicking.rs:380
   3: std::panicking::default_hook
             at /checkout/src/libstd/panicking.rs:396
   4: std::panicking::rust_panic_with_hook
             at /checkout/src/libstd/panicking.rs:611
   5: std::panicking::begin_panic_new
             at /checkout/src/libstd/panicking.rs:553
   6: std::panicking::begin_panic_fmt
             at /checkout/src/libstd/panicking.rs:521
   7: rust_begin_unwind
             at /checkout/src/libstd/panicking.rs:497
   8: core::panicking::panic_fmt
             at /checkout/src/libcore/panicking.rs:92
   9: core::result::unwrap_failed
             at /checkout/src/libcore/macros.rs:31
  10: <core::result::Result<T, E>>::expect
             at /checkout/src/libcore/result.rs:762
  11: addr2line_libxul::main
             at src/main.rs:4
  12: __rust_maybe_catch_panic
             at /checkout/src/libpanic_unwind/lib.rs:98
  13: std::rt::lang_start
             at /checkout/src/libstd/panicking.rs:458
             at /checkout/src/libstd/panic.rs:361
             at /checkout/src/libstd/rt.rs:59
  14: main
  15: __libc_start_main
  16: _start

And that's because resolve_name falls through all the cases and reaches the Ok(None) at the end for what seems like all programs.

Oh, this new error only starts appearing if I add .with_functions(). With my original code (using the default options), mapping succeeds but locate returns Ok(None).

For a smaller test case, compile the following using g++ -g -Os -std=gnu++11 -fno-exceptions
#include <iostream>
struct Foo { Foo() { std::cout << "Foo\n"; } };
typedef struct { Foo foo; } Bar;
int main() { new Bar(); }

The constructor for Bar is missing a name in the DWARF. Sometimes the compiler gives it a name, but not with those specific compilation options. Seems like a compiler bug? We should still handle it by ignoring that subroutine, instead of raising an error.

Seems like a compiler bug?

Care to file a bug with gcc?

We should still handle it by ignoring that subroutine, instead of raising an error.

👍

Care to file a bug with gcc?

I gave up on that, they don't make it easy to file bugs, and this one seems minor.

authors: fitzgen mstange philipc


text:
Add reduction for arrays.

This PR adds some reduction kernels for arrays. For CUDA and HIP the existing reduction kernels are reduced, with only one kernel added.
TODO

[ ] Add a return overload.

I want to ask whether we make Array class related to the device (not header only) or not? (before release 1.4)
for now, we have fill and this pr reduce.

have fill and reduce in class:
good for usage,
but need to link all ginkgo always and still use free function to use fill/reduce in the device side
only have fill and reduce free function
Array is header-only class
but always use free function to call fill/reduce.

Generally, I like to think of gko::Array as a the only vocabulary type that Ginkgo exposes. Something that can be used universally for interoperability with other libraries and user data. Now we have a few additions, namely value-converting Array::operator= and Array::fill that rely on actual device kernel and only work for specific ValueTypes. The more I think about it, the more I think it might be better to keep these out (replacing them by explicit conversion kernels for arrays only used internally, and maybe a datatype-agnostic Array::fill that acts like repeated memcpy)
All of this becomes especially important in the context of #715, where Array is the fundamental type that gets passed around between all shared libraries.
My point here is: If people want to compute a reduction over an array, I believe they should use more high-level functionality, like Dense or (maybe later) the simple kernel interface. Otherwise we risk overloading the Array type.

I agree with making not overloading Array, but I think that can severely restrict functionality. For example, the only way to store integer types right now is with arrays. And there are many situations where you need reductions for these integer arrays.

In that case, wouldn't a free function ValueType reduce(const Array<ValueType>&) be more suitable? What use case do you have in mind for index calculations from the user side?

Yes, I guess we could add a free function instead of member functions. I am not sure where to add them though. I think there are multiple use cases for reduction over integer arrays. To calculate the total number of non-zeros in a matrix, if you have the number of nonzeros per row to give a very specific example :)
But in general, I believe this is something useful not only from a user's perspective but also for us to write our algorithms more easily in our core.

In core algorithms, we usually need prefix sums, not plain reductions. And these computations are mostly necessary in the context of a matrix conversion, which we represent with a high-level interface already. If we want to use this operation inside core, we can use existing kernels.
I think we need to find a balance of how much we want to enable to write their own complex algorithms, and how generic we want to make that. Sum reductions are for example not the only important operation, think of (arg)min/max for building ELL.

authors: pratikvn upsj yhmtsai

repo: ginkgo-project/ginkgo


text:
负载均衡的一点想法，

目前负载均衡有三种模式，轮询，随机，递进。
配置如下
# strategy for node selecting
strategy        round

max_fails       2

fail_timeout    30s

# period for live reloading
reload          10s

# peers
peer    mwss://ra.elyzc.net:443?ip=80.63.188.5
peer    mwss://ra.qdlyzc.net:443?ip=80.63.188.6

我看了下nginx里面的负载均衡的算法貌似更合理。
# strategy for node selecting
###

max_fails       1

fail_timeout    30s

# period for live reloading
reload          10s

# peers
peer	round/random	mwss://ra.elyzc.net:443?ip=80.63.188.5
peer	round/random	mwss://ra.qdlyzc.net:443?ip=80.63.188.6
peer	round/random	mwss://ra.qdlyzc.net:443?ip=80.63.188.7
peer	fifo				mwss://ra.qdlyzc.net:443?ip=80.63.188.8

基本思路就是，
轮询或者随机的关系是并行的，没有先后顺序，
fifo - 自上而下 作为灾难备份。
如果我现在有三个优质节点，一个备用节点，就可以轮询或者随机三个优质节点，
如果优质节点全部挂掉才会启用备用节点。
按照现在的模式，是没法满足这种需求的，
要么全部随机，轮询，
或者等第一个节点宕机之后才会连接第二个，
三个随机，一个作为灾难备份，nginx的思路更好一些。
upstream tomcats {
    server 192.168.0.100:8080 weight=2 max_fails=3 fail_timeout=15;
    server 192.168.0.101:8080 weight=3;

    server 192.168.0.102:8080 backup;
}

直接采用nginx的写法更好，

# strategy for node selecting
# peers
peer	mwss://ra.elyzc.net:443?ip=80.63.188.5		weight=1		max_fails=3	fail_timeout=15;
peer	mwss://ba.qdlyzc.net:443?ip=80.63.188.6	weight=1		max_fails=3	fail_timeout=15;
peer	mwss://ca.qdlyzc.net:443?ip=80.63.188.7	weight=2		max_fails=3	fail_timeout=15;
peer	mwss://sa.qdlyzc.net:443?ip=80.63.188.8	backup;

repo: ginuerzh/gost


text:
[Question] supported game system?

@sergystepanov
which system supports?
support neo geo cd?
this cloud-game can run specific system only? or run all?

Here is the default list (for cloudretro.io also) https://github.com/giongto35/cloud-game/blob/master/pkg/config/config.yaml#L189.
An yes, you can add there your own, like NeoGeo CD.
It was tested with nes, snes, gba, mame, psx, n64, but in theory it may run any Libretro core with CPU or OpenGL emulation (backend). But keep in mind that cloud-game has a lot of missing parts compared to Retroarch (the reference Libretro frontend).
So, cloud-game can load any ROM (that are scanned at the start of the app) from that list of Libretro cores in the configuration file.
In debug mode (see the config) it will print all the ROMs found into the console, like:
14:03:02.1852 3a9c DBG c     Lib dump
--------------------------------------------
--- The Library of ROMs                  ---
--------------------------------------------
     snes   Earthbound (U) (Earthbound (U).smc)
     pcsx   Mega Man X4 (USA) (Mega Man X4 (USA).chd)
      nes   bad_apple_2_5 (bad_apple_2_5.nes)
      nes   Alwa's Awakening (Demo) (Alwa's Awakening (Demo).nes)
      n64   Legend of Zelda, The - Majora's Mask (U) [!] (Legend of Zelda, The - Majora's Mask (U) [!].z64)
     pcsx   Xenogears1 (Xenogears1.cue)
     pcsx   WWF WrestleMania - The Arcade Game (USA) (WWF WrestleMania - The Arcade Game (USA).chd)
    dosbox   shocktro (shocktro.zip)
      nes   Nekketsu Kakutou Densetsu (Japan) (Nekketsu Kakutou Densetsu (Japan).nes)
      nes   R.C. Pro-Am 2 (U) [!p] (R.C. Pro-Am 2 (U) [!p].nes)
      n64   Sample Demo by Florian (PD) (Sample Demo by Florian (PD).z64)
      n64   Super Mario 64 (USA) (Super Mario 64 (USA).z64)
     pcsx   Mega Man X4 (U) [SLUS-00561] (MegamanX4\Mega Man X4 (U) [SLUS-00561].cue)
      nes   Super Mario Bros. (World) (Super Mario Bros. (World).nes)
      nes   dpadhero2 (dpadhero2.nes)
     mame   ddsom (mame\ddsom.zip)
    dosbox   shocktro (1) (shocktro (1).zip)
      nes   Super Mario Bros. + Duck Hunt (USA) (Super Mario Bros. + Duck Hunt (USA).nes)
      gba   anguna (anguna.gba)
      gba   butano-fighter (butano-fighter.gba)
     mame   1945kiii (mame\1945kiii.zip)
...

nice many details
many thank man
cheers!

Either here or as a system environment variable like here (almost all config params can be set as system env vars with the prefix CLOUD_GAME_.

In which folder is the core libreretro located?
for add neocd

Most of your questions should be clear if you read the comments in the config.yaml file.
For NeoGeoCD it's something like this:
Read the core docs.
Change cloud-game\pkg\config\config.yaml as shown bellow. The app will download the core automatically into cloud-game\assets\cores after restart.
list:
+ neocd:
+   lib: neocd_libretro
+   roms: [ "cue", "chd" ]
+   folder: neocd
  gba:
    lib: mgba_libretro
    roms: [ "gba", "gbc" ]

Add any NeoGeo CD BIOS to cloud-game\libretro\system\neocd.
Add game ROMS into cloud-game\assets\games\neocd.
Play games.

i go read all doca
many thanks men
cheers!

@sergystepanov
please, you can share cores?

If you want to find them manually, here is the link https://buildbot.libretro.com/nightly/ (have you read config.yaml?). They are system dependent.
(since you've mentioned mupen64plus_next_libretro.cfg file, it was in the very old version of cloud-game so make sure you have the latest version of the code from this repository)

Which one is compatible with your system?
i need get cores for test

Something tells me that you didn't read or understand my previous replies. So I think, cloud-game is a bit complex for you to use, and you would have better chances with Retroarch if you just want to play some games.
I assume that you've downloaded and using compiled cloud-game v2.6.1, don't use it, it's old and obsolete. I don't remember if my instructions can be applied to this old version. The version you need is the one that you have to download and compile from the latest git snapshot.
If you want to find and download cores for some reason manually, which is not good option, then here they are  https://buildbot.libretro.com/nightly/windows/x86_64/latest/. Find needed, download, and extract dll to the assest/cores folder, but you need to add the record about this core into the config.yaml file also. You see, if you add the record first and just run the app (without downloading the cores), the app itself will download this core to you system (windows) automatically.
Also, NeoGeo CD requires a BIOS in order it to boot games. This is not related to cloud-game, but I'm sure you will have troubles with it too.
So, I don't think cloud-game is the right choice for you to use, since those previous quite straightforward instructions are causing such troubles.
P.S. Googling questions helps in 95% of the cases.

authors: discordfar sergystepanov


text:
Pagination

I am working on a line chart and we have daily data to show. Is there any way i could paginate data points for 7 days at a time? Right now the data looks cluttered as in the attached image as we have the fixed width and we don't want to increase the width.

Why not write your own custom pagination object that rebuilds the graph based on data from 7 days when you change weeks?

@woble  how would you suggest we go about that??

This would make a nice plugin. Let's keep a reference to #290

authors: SarasArya VishwaKumar gionkunz woble

repo: gionkunz/chartist-js


text:
[BUG] Transition not working when background-color is applied

When the container element (not particularly the parent) has background or background-color property set to a value other than transparent, then the filter in transition breaks (it immediately shows the items instead of using transition).
However, when the background color is applied to the body or the html element, it works!
Filterizr version
2.2.3 (have not tested with other versions).
To Reproduce
Steps to reproduce the behavior:

Go to https://yiotis.net/filterizr/
Inspect the Demo Gallery h1 element
Select the <main> element (it has no classes applied)
Set background-color: #123456;
Now, try to filter elements using the mouse.
Click on Cities (works). Click on All (notice the bug - instant show up of items!).

Expected behavior
The expected behavior should be without the flashing effect of filtering items.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Linux Mint
Browser: Chromium (78), FF (70.0.1)

Can confirm this is an issue. In my case it isn't related to a background color per se, but rather a combination of a few styles a few levels up in the markup.
I recommend a different approach to managing the animation as there can be unpredicted side effects in the current approach.

@wilbertcaba adding that crazy minus z-index makes the items not clickable so it kind of defeats the purpose of filtering things.

Apologies for spamming,
add this to the parent with background color,
perspective: 1000px; transform-style: preserve-3d;
or any of those (both of them make the animation work)

@wilbertcaba adding that crazy minus z-index makes the items not clickable so it kind of defeats the purpose of filtering things.

@donkutbay As you can see, I mention this issue in my comment with an alternate fix:

If you add a z-index value to the parent element deeper than -1000 you could run into issues where some elements are not clickable. To avoid any of these it's safer to create a pseudo-element for that parent with your background-color and a super deep z-index < -1000...

Glad your solution worked as well.

authors: donkutbay genu manikos wilbertcaba

repo: giotiskl/filterizr


text:
Bug when interacting with vim-dirvish

When using https://github.com/justinmk/vim-dirvish the / search is remapped to account for searching file paths
nnoremap <buffer> / /\ze[^/]*[/]\=$<Home>
nnoremap <buffer> ? ?\ze[^/]*[/]\=$<Home>

defined here https://github.com/justinmk/vim-dirvish/blob/master/ftplugin/dirvish.vim .
It seems to interfere with autosuggest.vim resulting in an error
E867: (NFA regexp) Unknown operator '\zk'

What are the steps to reproduce? I downloaded dirvish but it did not cause error when I searched with /.

fixed
https://github.com/girishji/autosuggest.vim/commit/04c39700653b196b004755eb65b8295147f1860c

authors: EgZvor girishji


text:
CSS Grid

Description
In this PR I will briefly explain CSS Grid and its properties
Kanishk Chhabra
Front-End Web Development using HTML, CSS and JS - Batch 3
Domain
Frontend Dev HTML/CSS/JS
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/aasign

/assign

/assign

repo: girlscript/winter-of-contributing


text:
Cybersecurity: 3.9 File injecting virus

Description
Discuss more about File injecting virus.
Note:

If interested, mention in which format you want to contribute: Documentation or Video
Please avoid copy/paste, BE YOURSELF
Try to explain with Diagrams
Changes should be made inside the Cyber_Security/ directory & Cyber_Security branch.
Task will be assigned on first come first serve
Check it out Contribution Guidelines

Domain
Cyber Security
Type of Contribution
Video, Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

@Harsh-Chaudhary7 You didn't submit your previous work!
Please submit that first!

@Anant1711 can you assign me this?

@Anant1711 can you assign me this?
Documentation

Assigned!


text:
Arithmetic operators in C++

Description
Explaining briefly about operators using example and code snippets.
Domain
C/CPP
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

/assign


text:
DSA String: Super ASCII String Checker

Description
In the Byteland country, a string S is said to super ASCII string if and only if the count of each character in the string is equal to its ASCII value. In the Byteland country ASCII code of ‘a’ is 1, ‘b’ is 2, …, ‘z’ is 26. The task is to find out whether the given string is a super ASCII string or not. If true, then print “Yes” otherwise print “No”.
Examples:
Input: S = “bba”
Output: Yes
Domain
DSA
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

@nimisha-yadav can you please review my work once


text:
rcheckin thinks my working copy is dirty when it is in fact clean

git-tfs v0.18.0.0
$ git tfs rcheckin
error: You have local changes; rebase-workflow checkin only possible with clean working directory.
You may be able to resolve this problem.
- Try 'git stash' to stash your local changes and checkin again.

$ git status -sb
## master

$ git stash
No local changes to save

For future reference: I've seen "the same" issue (means same error message on a PC of a collegue). The problem was, he had git for windows 2.9 installed. After uninstalling and installing 1.9.5 and a fresh clone, rcheckin was working again.

There was some work done for autcrlf handling, e.g. dafdea1c1deb5b4225e11c4d3d0f19a76c7535a6
As we are trying to clean up old/stale issues and this issue hasn't seen any updates (or progress with pull requests) in quite a while, the issue will be closed. In case further information is provided, we can revisit that and reopen the issue again.

authors: JamesDunne apuch siprbaum

repo: git-tfs/git-tfs


text:
github user screen error

Seems to be a bug of the GraphQL API. The color should be a hex number

https://github.community/t/graphql-api-contribution-colors-breaking-change/140855

Temporarily fixed by a tricky way

I believe this should be resolved in the API now! Apologies for the issue

repo: git-touch/git-touch


text:
corrected and added devanagari, verse text, word_meanings and audio

[fixes #59] and corrected and added devanagari, transliteration, word_meanings and modified audio for some of the verses. Following are the specific details. Sharing an example image for all types of issues.
Corrected transliteration and word_meanings
1.5, 1.6, 2.42, 5.8, 5.27, 10.33, 11.26, 12.3, 16.15, 18.36

Corrected Devanagari and modified audio
1.20.1.21,1.26,1.27,1.28
Corrected Spellings in Devanagari for the below
1.18, 5.1, 13.5, 13.10, 16.11, 18.6, 18.40

Added missing transliteration and word_meanings
11.19

@Gupta-Anubhav12 @samanyougarg Pls go through my PR

Hare Krishna
thanks for sending this PR, will review and merge shortly

Hare Krishna
any update @Gupta-Anubhav12

repo: gita/gita

license: Unlicense


text:
Cannot add a new line (shift+enter) in a bullet without it creating another new bullet

Great api!
I've tried every and all combinations to try to get the result below but no luck.  I even tried adding text after a bullet and using inset to mimick it, but inset does not seem to work either.  \n and \r and their combinations were also tried.
Is there a way to update the api to achieve the below?

line 1
new line within the same bullet
line 2

Had the same issue recently. The workaround is to break the string on \n and only add the bullet to the first string. The next one(s) you can add an empty space bullet -> bullet: { code: '0020' }.
If it was a numbered list, you would get disordered numbers because it resets to 1 when you start bullet-ing the next line. In which case you can utilize the 'startAt' property and set it to the correct order.

I had the same issue.  Is there a way to add an option to ignore new line characters so it does not create additional bullets?

authors: ericslattery muftaye sadeks

repo: gitbrent/PptxGenJS


text:
🛑 invidious.lidarshield.cloud is down

In 00cc515, invidious.lidarshield.cloud (https://invidious.lidarshield.cloud/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: invidious.lidarshield.cloud is back up in 3dd39c5.

repo: gitetsu/invidious-instances-upptime


text:
🛑 search.mascotboi.xyz is down

In 70cb1b4, search.mascotboi.xyz (https://search.mascotboi.xyz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: search.mascotboi.xyz is back up in ea05cb2 after 16 minutes.

repo: gitetsu/librex-instances-upptime


text:
🛑 search.madreyk.xyz is down

In 0beb0fa, search.madreyk.xyz (https://search.madreyk.xyz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: search.madreyk.xyz is back up in 5a94f49.


text:
🛑 whoogle.dcs0.hu is down

In 895c44c, whoogle.dcs0.hu (https://whoogle.dcs0.hu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: whoogle.dcs0.hu is back up in 451f872 after 3 minutes.

repo: gitetsu/whoogle-instances-upptime


text:
🛑 whoogle.privacydev.net is down

In badec7a, whoogle.privacydev.net (https://whoogle.privacydev.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: whoogle.privacydev.net is back up in eb27866.


text:
passive_pack

test

Some comment

repo: github-api-test-org/jenkins


text:
[GHSA-mwm4-5qwr-g9pf] Keycloak is vulnerable to IDN homograph attack

Updates

References

Hi there @abstractj! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our highly-trained Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory

repo: github/advisory-database


text:
[GHSA-jg32-8h6w-x7vg] Metabase open source before 0.46.6.1 and Metabase...

Updates

Affected products
Summary

Comments
Trivy is not detecting this vulnerability on vulnerable images. This is a very critical issue, allowing unauthenticated RCE on the Metabase host server.

Hi @exiett, I appreciate your contribution to GitHub's Advisory Database. Unfortunately, I am unable to locate Metabase in a registry supported ecosystem.

authors: CallmeMari exiett


text:
tests failing on Mac

What is the current behavior?
I cloned the repo, did npm install and npm test and got a number of failures shown below.
Note this was with Node 12.18.3 (npm 6.14.6) on Mac OS 10.15.7

```
~/git/docs$ npm test

docs.github.com@ test /Users/jeffmcaffer/git/docs
jest && standard && npm run check-deps

PASS  tests/content/remove-liquid-statements.js
PASS  tests/unit/page.js (5.381 s)
PASS  tests/content/category-pages.js (5.877 s)
PASS  tests/routing/deprecated-enterprise-versions.js (39.664 s)
PASS  tests/routing/redirects.js (43.153 s)
PASS  tests/rendering/breadcrumbs.js (34.25 s)
PASS  tests/routing/developer-site-redirects.js (50.398 s)
FAIL  tests/rendering/server.js (56.332 s)
● static assets › fonts
expect(received).toBe(expected) // Object.is equality

Expected: 200
Received: 404

  567 | describe('static assets', () => {
  568 |   test('fonts', async () => {
> 569 |     expect((await get('/dist/fonts/Inter-Medium.woff')).statusCode).toBe(200)
      |                                                                     ^
  570 |     expect((await get('/dist/fonts/Inter-Regular.woff')).statusCode).toBe(200)
  571 |   })
  572 | })

  at Object.<anonymous> (tests/rendering/server.js:569:69)
      at runMicrotasks (<anonymous>)

● stylesheets › compiles and sets the right content-type header
expect(received).toBe(expected) // Object.is equality

Expected: 200
Received: 404

  665 |   it('compiles and sets the right content-type header', async () => {
  666 |     const res = await get('/dist/index.css')
> 667 |     expect(res.statusCode).toBe(200)
      |                            ^
  668 |     expect(res.headers['content-type']).toBe('text/css; charset=UTF-8')
  669 |   })
  670 | })

  at Object.<anonymous> (tests/rendering/server.js:667:28)
      at runMicrotasks (<anonymous>)

● client-side JavaScript bundle › returns a 200 response
expect(received).toBe(expected) // Object.is equality

Expected: 200
Received: 404

  678 |
  679 |   it('returns a 200 response', async () => {
> 680 |     expect(res.statusCode).toBe(200)
      |                            ^
  681 |   })
  682 |
  683 |   it('sets the right content-type header', async () => {

  at Object.<anonymous> (tests/rendering/server.js:680:28)
      at runMicrotasks (<anonymous>)

● client-side JavaScript bundle › sets the right content-type header
expect(received).toBe(expected) // Object.is equality

Expected: "application/javascript; charset=UTF-8"
Received: "text/html; charset=utf-8"

  682 |
  683 |   it('sets the right content-type header', async () => {
> 684 |     expect(res.headers['content-type']).toBe('application/javascript; charset=UTF-8')
      |                                         ^
  685 |   })
  686 |
  687 |   // TODO: configure webpack to create production bundle in the test env

  at Object.<anonymous> (tests/rendering/server.js:684:41)
      at runMicrotasks (<anonymous>)

PASS  tests/unit/liquid-helpers.js (21.265 s)
PASS  tests/rendering/events.js (34.335 s)
● Console
console.log
  data should NOT have additional properties, data should NOT have additional properties, data should match exactly one schema in oneOf

  at middleware/events.js:24:56

console.log
  data should have required property 'type', data should NOT have additional properties, data should match exactly one schema in oneOf

  at middleware/events.js:24:56

console.log
  data should have required property 'url', data should NOT have additional properties, data should match exactly one schema in oneOf

  at middleware/events.js:24:56

console.log
  data.url should match format "uri", data should NOT have additional properties, data should match exactly one schema in oneOf

  at middleware/events.js:24:56

console.log
  data should have required property 'vote', data should NOT have additional properties, data should match exactly one schema in oneOf

  at middleware/events.js:24:56

console.log
  data.vote should be equal to one of the allowed values, data should NOT have additional properties, data should match exactly one schema in oneOf

  at middleware/events.js:24:56

console.log
  data.email should match format "email", data should NOT have additional properties, data should match exactly one schema in oneOf

  at middleware/events.js:24:56

console.log
  data.comment should be string, data should NOT have additional properties, data should match exactly one schema in oneOf

  at middleware/events.js:24:56

console.log
  data.category should be equal to one of the allowed values, data should NOT have additional properties, data should match exactly one schema in oneOf

  at middleware/events.js:24:56

console.log
  data should NOT have additional properties, data should NOT have additional properties, data should match exactly one schema in oneOf

  at middleware/events.js:24:56

console.log
  data should NOT have additional properties, data should NOT have additional properties, data should match exactly one schema in oneOf

  at middleware/events.js:24:56

console.log
  data should NOT have additional properties, data should have required property 'test', data should match exactly one schema in oneOf

  at middleware/events.js:24:56

console.log
  data should NOT have additional properties, data.group should be equal to one of the allowed values, data should match exactly one schema in oneOf

  at middleware/events.js:24:56

PASS  tests/unit/pages.js (26.201 s)
PASS  tests/rendering/robots-txt.js
PASS  tests/rendering/header.js (37.275 s)
PASS  tests/content/site-data.js (26.117 s)
PASS  tests/content/lint-files.js (100.357 s)
PASS  tests/content/graphql.js (22.673 s)
PASS  tests/content/liquid-line-breaks.js (18.835 s)
PASS  tests/unit/permalink.js
PASS  tests/rendering/early-access-proxy.js
PASS  tests/routing/middleware/redirects/help-to-docs.js
PASS  tests/content/featured-links.js (35.996 s)
PASS  tests/content/site-tree.js (34.16 s)
PASS  tests/content/site-data-references.js (27.327 s)
PASS  tests/unit/algolia/parse-page-sections-into-records.js
PASS  tests/content/webhooks.js (30.935 s)
PASS  tests/content/glossary.js (9.199 s)
PASS  tests/unit/hydro.js
PASS  tests/unit/products.js (31.765 s)
PASS  tests/rendering/early-access-paths.js
PASS  tests/rendering/octicon.js
PASS  tests/content/algolia-search.js
PASS  tests/rendering/rest.js (32.291 s)
PASS  tests/unit/find-page.js
PASS  tests/rendering/page-titles.js (33.27 s)
PASS  tests/unit/liquid.js
PASS  tests/unit/versions.js (35.216 s)
PASS  tests/unit/enterprise-versions.js
PASS  tests/unit/failbot.js
PASS  tests/unit/actions-workflows.js
PASS  tests/rendering/sidebar.js (36.861 s)
PASS  tests/rendering/curated-homepage-links.js (38.831 s)
PASS  tests/rendering/head.js (34.839 s)
PASS  tests/meta/orphan-tests.js
PASS  tests/unit/languages.js
PASS  tests/links-and-images/links-and-images.js (128.414 s)
PASS  tests/unit/algolia/rank.js
PASS  tests/unit/feature-flags.js
PASS  tests/unit/product-names.js
PASS  tests/content/gitignore.js
PASS  tests/content/crowdin-config.js
PASS  tests/unit/toc-links.js (41.24 s)
(node:1530) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
PASS  tests/routing/language-code-redirects.js (30.538 s)
PASS  tests/rendering/footer.js (30.62 s)
PASS  tests/rendering/csrf-route.js (25.021 s)
PASS  tests/routing/top-developer-site-path-redirects.js (38.56 s)
PASS  tests/links-and-images/developer-links-and-images.js (303.602 s)
A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --runInBand --detectOpenHandles to find leaks.
Summary of all failing tests
FAIL  tests/rendering/server.js (56.332 s)
● static assets › fonts
expect(received).toBe(expected) // Object.is equality

Expected: 200
Received: 404

  567 | describe('static assets', () => {
  568 |   test('fonts', async () => {
> 569 |     expect((await get('/dist/fonts/Inter-Medium.woff')).statusCode).toBe(200)
      |                                                                     ^
  570 |     expect((await get('/dist/fonts/Inter-Regular.woff')).statusCode).toBe(200)
  571 |   })
  572 | })

  at Object.<anonymous> (tests/rendering/server.js:569:69)
      at runMicrotasks (<anonymous>)

● stylesheets › compiles and sets the right content-type header
expect(received).toBe(expected) // Object.is equality

Expected: 200
Received: 404

  665 |   it('compiles and sets the right content-type header', async () => {
  666 |     const res = await get('/dist/index.css')
> 667 |     expect(res.statusCode).toBe(200)
      |                            ^
  668 |     expect(res.headers['content-type']).toBe('text/css; charset=UTF-8')
  669 |   })
  670 | })

  at Object.<anonymous> (tests/rendering/server.js:667:28)
      at runMicrotasks (<anonymous>)

● client-side JavaScript bundle › returns a 200 response
expect(received).toBe(expected) // Object.is equality

Expected: 200
Received: 404

  678 |
  679 |   it('returns a 200 response', async () => {
> 680 |     expect(res.statusCode).toBe(200)
      |                            ^
  681 |   })
  682 |
  683 |   it('sets the right content-type header', async () => {

  at Object.<anonymous> (tests/rendering/server.js:680:28)
      at runMicrotasks (<anonymous>)

● client-side JavaScript bundle › sets the right content-type header
expect(received).toBe(expected) // Object.is equality

Expected: "application/javascript; charset=UTF-8"
Received: "text/html; charset=utf-8"

  682 |
  683 |   it('sets the right content-type header', async () => {
> 684 |     expect(res.headers['content-type']).toBe('application/javascript; charset=UTF-8')
      |                                         ^
  685 |   })
  686 |
  687 |   // TODO: configure webpack to create production bundle in the test env

  at Object.<anonymous> (tests/rendering/server.js:684:41)
      at runMicrotasks (<anonymous>)

Test Suites: 1 failed, 55 passed, 56 total
Tests:       4 failed, 67 skipped, 2 todo, 22825 passed, 22898 total
Snapshots:   0 total
Time:        304.86 s
Ran all test suites.
npm ERR! Test failed.  See above for more details.
~/git/docs$ node --version
v12.18.3
~/git/docs$
</details>

cc: @github/docs-engineering

Thanks @jeffmcaffer I'll let @github/docs-engineering know this is ready for a review!

Quick workaround: npm run build once before running the tests.
I opened an issue yesterday to discuss how to actually fix this: https://github.com/github/docs/issues/222

This is a non-issue if you follow the development instructions as outlined in https://github.com/github/docs/blob/main/contributing/development.md#getting-started (updated)
If you have other ideas on how to improve the experience, please discuss in https://github.com/github/docs/issues/222. Thank you!

authors: JamesMGreene janiceilene jeffmcaffer zeke

repo: github/docs


text:
Add documentation for case-sensitive code search / regex mode modifiers

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/search-github/github-code-search/understanding-github-code-search-syntax
What part(s) of the article would you like to see updated?
I found out through StackOverflow that case-sensitive search can be accomplished with the (?-i) mode modifier. The official docs should note this instead of stating "You cannot do case-sensitive searches", which is not true.
Additionally, it would be nice if the section on regular expressions described which mode modifiers are supported by code search. There are many, and different flavors of regex are known to support different modifiers.
Additional information
No response

@victorlin Thank you for raising this issue! I'll get this triaged for review :sparkles: Our team will provide feedback regarding the best next steps for this issue - thanks for your patience! 💛

Hi @victorlin 👋

I found out through StackOverflow that case-sensitive search can be accomplished with the (?-i) mode modifier. The official docs should note this instead of stating "You cannot do case-sensitive searches", which is not true.

Thanks for bringing that to our attention. I think the best thing to do would be to delete the whole section on "Case sensitivity".
Before I open that to contributors, I'd like to give you first refusal if you'd like to open a PR yourself?

Additionally, it would be nice if the section on regular expressions described which mode modifiers are supported by code search. There are many, and different flavors of regex are known to support different modifiers.

However, this isn't typically something we'd document. I'd recommend opening a Discussion on this so we can see what kind of traction it gets.
Could I also take a moment to thank you for raising an issue before going ahead and raising a PR—it's much appreciated and makes the experience better for everyone ✨

authors: nguyenalex836 subatoi victorlin


text:
Hh

Why:
Closes [issue link]

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

https://www.paypal.com/pools/c/8OmsxaiDuZ
On Fri, Oct 21, 2022, 8:53 PM Harlee1994 @.***> wrote:

Why:
Closes [issue link]
What's being changed (if available, include any code snippets,
screenshots, or gifs): Check off the following:

I have reviewed my changes in staging (look for the "Automatically
generated comment" and click the links in the "Preview" column to view your
latest changes).
For content changes, I have completed the self-review checklist
https://github.com/github/docs/blob/main/contributing/self-review.md#self-review
.

You can view, comment on, or merge this pull request online at:
https://github.com/github/docs/pull/21544
Commit Summary

c30c710
https://github.com/github/docs/pull/21544/commits/c30c710c0c78f996ab1a75572620f855aa607cd5
Create datadog-synthetics.yml
c81830c
https://github.com/github/docs/pull/21544/commits/c81830c7f7b377dd41306858401e68cfa8aabe4a
Create static.yml
07320e0
https://github.com/github/docs/pull/21544/commits/07320e0b1e33caf278f1b3f4120689a92a6d7db6
Create nuxtjs.yml
8202940
https://github.com/github/docs/pull/21544/commits/8202940ac806d977487d1523e0057b9fa04dc7b4
Merge branch 'github:main' into main

File Changes
(3 files https://github.com/github/docs/pull/21544/files)

A .github/workflows/datadog-synthetics.yml
https://github.com/github/docs/pull/21544/files#diff-ab96c3ab21cf19fcd16799a9f721717b2c549b257cf0b559849b8ef664e5a6ae
(38)
A .github/workflows/nuxtjs.yml
https://github.com/github/docs/pull/21544/files#diff-cc116af89a34a62bf4de9687b3b7d3cefc665e5826a8f7bd93f29104969fbe91
(89)
A .github/workflows/static.yml
https://github.com/github/docs/pull/21544/files#diff-33f2778a5bb1ccf0ce7a73eeeeb02daf6023c2bdb47ff841fcf782fc3e469404
(42)

Patch Links:

https://github.com/github/docs/pull/21544.patch
https://github.com/github/docs/pull/21544.diff

—
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/21544, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZVIUCXTTL5XUEYWEQLRFCTWEM3HRANCNFSM6AAAAAARLTUI4M
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


text:
Update and rename topics/bitcoin/index.md to หัวข้อ/ bitcoin/index.md

Thank you for contributing! Please confirm this pull request meets the following requirements:

[ ] I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md
[ ] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Which change are you proposing?

[ ] Suggesting edits to an existing topic or collection
[ ] Curating a new topic or collection

Editing an existing topic or collection
I'm suggesting these edits to an existing topic or collection:

[ ] Image (and my file is *.png, square, dimensions 288x288)
[ ] Content (and my changes are in index.md)

Please replace this line with an explanation of why you think these changes should be made.

Curating a new topic or collection

[ ] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
[ ] My folder contains a *.png image (if applicable) and index.md
[ ] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

Please replace this line with an explanation of why you think this topic or collection should be curated.

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

But according to Wikipedia the name is "Satoshi Nakamoto" not "Satoshi Nakamot"
Ref: https://en.wikipedia.org/wiki/Satoshi_Nakamoto

repo: github/explore


text:
Add the Lazarus.gitignore file

The .gitignore file has no extensions that should be ignored in the freepascal and Lazarus project.
Reasons for making this change:

TODO
Links to documentation supporting these rule changes:
https://wiki.freepascal.org/Lazarus_project_files
TODO
If this is a new template:

Link to application or project’s homepage: TODO
https://wiki.freepascal.org/Lazarus_project_files

Yess! Hoping this could get merged soon!

authors: paulosspacheco theonlyasdk

repo: github/gitignore


text:
$ ssh-keygen -t rsa -b 4096 -C "

$ ssh-keygen -t rsa -b 4096 -C "
Originally posted by @UschiSushi in https://github.com/github/hub/issues/2582#issuecomment-662270715

repo: github/hub


text:
Fix thor dependency

Rails now requires Thor 1.0 or higher so we need to update the
dependency on thor in licensed.
This will allow 0.19 or anything higher.

@eileencodes :wave: release 2.9.1 is out with this change https://github.com/github/licensed/releases/tag/2.9.1

authors: eileencodes jonabc

repo: github/licensed


text:
.strings files are listed as binary files

I don't really have syntax, but these files are recognized in diffs as binary files, rather than text files:
https://github.com/overtake/telegram/blob/master/TGShare/en.lproj/Localizable.strings
https://github.com/overtake/telegram/blob/master/TelegramTest/en.lproj/localizations.strings
Example diff: https://github.com/overtake/telegram/pull/211/files

I can't seem to reproduce the issue locally with Linguist. Are you sure it's because of the .strings file extension?

I can't seem to reproduce the issue locally with Linguist. Are you sure it's because of the .strings file extension?

Flagging as stale :flags:

authors: nicatronTg pchaigno

repo: github/linguist


text:
Syntax highlighting for Elixir is broken

Preliminary Steps
Please confirm you have...

[x] reviewed How Linguist Works,
[x] reviewed the Troubleshooting docs,
[x] considered implementing an override,
[x] verified an issue has not already been logged for your issue (linguist issues).

Problem Description
It seems that all files written in the Elixir programming language (file extensions .ex and .exs) lost syntax highlighting. This is something very recent.

URL of the affected repository:
https://github.com/elixir-lang/elixir and all repositories using Elixir programming language
Last modified on:

2018-07-20, 10:48 CEST
Expected language:

Elixir
Detected language:

Elixir but without syntax highlightng

@michalmuskala we use atom-grammar-test https://www.npmjs.com/package/atom-grammar-test
You need to write simple boilerblate spec for atom and a set of grammar-specs.
See a real project here - spec - https://github.com/1c-syntax/1c-syntax/blob/master/spec/language-1s-bsl-spec.coffee
grammar-spec (one of them) - https://github.com/1c-syntax/1c-syntax/blob/master/spec/fixtures/grammar/syntax_test_bsl.bsl

@michalmuskala I can only recommend @nixel2007's suggestion of writing tests with the grammar. We also have some tests when compiling grammars in Linguist, but it's currently difficult to distinguish actual issues from other warnings due to the high number of warnings (cf. #3924). If you know another Elixir grammar with tests and equivalent support for the syntax, we could switch to it.

Linguist 6.3.1 is now live and all the Elixir files are pretty again. 🌈🌈🌈

authors: lildude michalmuskala nixel2007 pchaigno


text:
Grammar for Inno Setup

This pull request adds a grammar for Inno Setup. I also added a sample file.
I found two grammars for Inno Setup:

idleberg/InnoSetup-Sublime-Text: example in Lightshow (the one added in this PR)
shadyproject/sublime-inno-setup: example in Lightshow

I chose the first one because the second one doesn't seem to recognize quoted strings. Also, it seems more active lately. However, the first one recognizes URLs as comments.

:+1:

This is now live on github.com.

authors: arfon aroben pchaigno


text:
Cloudflare: Add Support for Rate Limit

I added basic support for when a 429 HTTP error is returned.
I defaulted to 4 retries with a backoff of 300s.
I copied most of the implementation from the old NS1 implementation
Cloudflare does not return headers to warn you of an upcoming rate limit.

Thanks.

authors: lancehudson ross

repo: github/octodns


text:
Edited fa/metrics.md

Hi
Edited metrics.md
good luck  :)

[ ] Have you followed the contributing guidelines?
[ ] Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

Files changed

😉😉😉

authors: Antonio3m Firegrill ciminbinazadeh


text:
Update getting-paid.md

[x] Have you followed the contributing guidelines?
[x] Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

#2801

I just try it today to see if I will be perfect

Не понимаю о чём ты? Отправлено с моего телефона Huawei-------- Исходное сообщение --------От: Daniellebensone @.>Дата: пт, 15 апр. 2022 г., 10:08Кому: "github/opensource.guide" @.>Копия: Subscribed @.***>Тема: Re: [github/opensource.guide] Update getting-paid.md (PR #2801)
I just try it today to see if I will be perfect
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>


text:
Git guides a11y updates

Overview
Hey there, big regards from @github/brand-engineering 👋
I'm currently updating the https://github.com/git-guides and I've stumbled on couple small accessibility violations in the guides:

Missing a table heading copy
Heading hierarchy violation

That is all! ✨

@qiang88550 ****

authors: GRURoot stamat

repo: github/training-kit


text:
Скласти блок контактної інформації

Посилання на соцмережі (Facebook чи Instagram, тощо), номер телефону чи адреса електронної скриньки, тощо. Може не всі лінки в світі, а тільки ті, що дійсно доречні.

Email- lmazurl@yahoo.com
Phone number - +38(097)-547-4986
linkedIn - https://www.linkedin.com/in/oleh-mazur-51b7a5217/
GitHub - https://github.com/mazurGit

repo: githubMazur/homepage


text:
Address Handling in sendLovelaces.sh

I tried to use this script to transfer ff-testnet lovelaces from one enterprise style address to another in separate directories.  I used the following syntax to launch the script:
./01_sendLovelaces.sh ../priv/payment1 pool-002_enterprise 4425831
payment1 is the send-from address
pool-002_enterprise is the receiver address
4425831 is the number of lovelace to send
Here is the output the script generated:
Sending lovelaces from Address ../priv/payment1.addr to Address pool-002_enterprise.addr:
Current Slot-Height: 817630 (setting TTL to 827630)
Source Address ../priv/payment1.addr: 619ea1cba1088c5d9(truncated)
Destination Address pool-002_enterprise.addr: 617d6c090574b284858(truncated
2 UTXOs found on the source Addr!
HASH: 1f620efdfa52e8(truncated)   INDEX: 0        LOVELACES: 10000000
HASH: 69ebd62083d6(truncarted)   INDEX: 1        LOVELACES: 4425831
Total lovelaces in UTX0:  14425831 lovelaces
Minimum Transaction Fee for 2x TxIn & 2x TxOut:  169725 lovelaces
Lovelaces to send to pool-002_enterprise.addr:  4425831 lovelaces
Lovelaces to return to ../priv/payment1.addr:  9830275 lovelaces
Building the unsigned transaction body:  tx_../priv/payment1.txbody
Error while writing unsigned shelley tx: tx_../priv/payment1.txbody: tx_../priv/payment1.txbody: openBinaryFile: does not exist (No such file or directory)
cat: tx_../priv/payment1.txbody: No such file or directory
Sign the unsigned transaction body with the ../priv/payment1.skey:  tx_../priv/payment1.tx
Error while reading unsigned shelley tx: tx_../priv/payment1.txbody: tx_../priv/payment1.txbody: openBinaryFile: does not exist (No such file or directory)
cat: tx_../priv/payment1.tx: No such file or directory
Does this look good for you, continue ? [y/N] N
Note the errors produced by the script. Perhaps it is not parsing the address name from the path correctly?  The receiver address was in the same directory so I don't know if both send and receive addresses would experience the same issue if a path was prepended to them when launching the script.

you're right. error happend because it generates files with prefix tx_ and that was confusing the script. good point! the transaction files tx and txbody were the only two files using a prefix for the name itself. i corrected it, should now work. please give me a short feedback, thx.

can it be closed?

I didn't try because the F&F network was down.  I will try again soon and respond here.

works.  Thanks!

repo: gitmachtl/scripts


text:
Review the limits on the Grafana pod

Bug description
May we ask @gitpod-io/platform to review the limits on the Grafana pod?
We had an issue today, where the Gitpod Overview dashboard was missing data for about 20 minutes. Upon further examination we found the Grafana pod was crash looping and needed more resources. This was solved by increasing its limits, so that the pod could start and serve the dashboard again (so that we could consume Victoria Metrics).
Please refer to the incident for a complete timeline. As you can see, after this issue happened, we had a separate issue where images could not be pulled, which prevented some users from starting workspaces.
Steps to reproduce
n/a
Expected behavior
The Grafana pod would not crash loop due to resource constraints, within reason of course. :)
Example repository
n/a
Anything else?
Also related to the same incident.

@meysholdt I'm scheduling this ☺

repo: gitpod-io/observability


text:
[WIP] Add auto-completion of usernames

Still very WIP, just made a PR so I can remember to commit my changes and not lose them all like I did last time 😬

(or slightly higher quality YouTube video: https://www.youtube.com/watch?v=7jnJddP0aRA)
Anyways, the basic features are all laid out and it works fine, but would like to add a couple more things before merging:

[ ] Popup the mention box by typing an "@" anywhere in the sentence (currently only works at the end)
[ ] Make it work with issue/PR #'s (maybe another PR?)
[ ] Add normalized name if available (e.g. "@johndoe62 - John Doe")
[x] Add fuzzy search
[x] Make it look nicer
[ ] Maybe add profile images? (I kind of like it how it is)
[x] Take some dope pictures/videos for this PR 😉

I can't even begin to describe how awesome of a job this is @andrewda, wayy exceeded my expectations and you're not even done!
Does clicking any name in the popup mentions box automatically insert the name into the comment text input? If it doesn't that's fine, something we can work on later because even without it this is solid.

@housseindjirdeh Yep! It only works at the end of the current text at the moment but I'm working on making it work anywhere.

I think I'll hold off on the issue and PR suggestions for now so I can implement it a little differently in another PR. Just gotta resolve a couple issues and merge conflicts and should be good to go! :)

@housseindjirdeh Thanks so much!

Will do that in a sec 😄
This happens because I'm checking to see if the last character in the text field is an @ symbol. Not sure how to check what the last character that was actually typed is...
Weird not sure why that's happening. I'll look into this but doesn't seem like a huge deal, probably just open an issue ticket and we can check in on it when anyone gets a chance.

Haven't tested on Android, would much appreciate it if u could check it out <3

Will begin working on issue implementation tomorrow!

authors: andrewda housseindjirdeh

repo: gitpoint/git-point


text:
🛑 MSP-103 is down

In b3f74c2, MSP-103 (https://msp-portal.gw103.oneitfarm.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MSP-103 is back up in 0f86371.

repo: gitsrc/upptime


text:
🛑 MSP-103 is down

In 561d32e, MSP-103 (https://msp-portal.gw103.oneitfarm.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MSP-103 is back up in 76a59f3.


text:
Definition of linear classifier and linear decision boundary

We can consider how to add more definitions or an interactive exercise around what it means for a decision boundary to be linear.  This seemed to be one part of the lesson where participants were not completely following along.  We could prepare an example or question to help contrast linear versus non-linear decision rules, perhaps going back to the housing example.
Some of our linear examples also seemed to be complex.  For this audience, I think of linearly separable to mean that the 2D data plot can be divided into red and blue points with a straight line.  Some of our examples used a linear classifier like SVM with a kernel, such as the RBF kernel.  Explaining that is pretty advanced for the short form of this workshop.

We also need to define the word classifier the first time it is used.  The term is used in the introduction lesson but introduced in the T cell lesson.

Introduction

added classification definition to the Introduction lesson
should we add a simple regression definition? I struggled with this.
In the workshop, the question came up about explaining further the difference between supervised and unsupervised learning - should we maybe add a callout about it?

Let's avoid the word "classifying" in the definition.  How about

predicting a category for the samples in the data set. In the house price example, the categories are high and low.

Regression could be

predicting a continuous number for the samples in the data set. A regression version of the house price example would be predicting the price in dollars.

For unsupervised learning, we discussed not wanting to spend a lot of time on this.  We can use the housing dataset we create to show how clustering would work without requiring the labels.  We can then link to extra resources, like our glossary.  Google's clustering intro is okay but not perfect.

All of these look good to me! I will edit the lesson following the suggestions. Thanks!

authors: agitter cmilica

repo: gitter-lab/ml-bio-workshop


text:
The device in order to implement this code

Hello,Sir
Firstly,Thanks your sharing.I have some question for the system implementation.
Actually,I want to know which device was used to implement this code, CPU or GPU？I could implement this code on CPU.Considering lots of parameters,I want to achieve it on GPU,however ,I don't make it up to now.
[numpy.core._exceptions._ArrayMemoryError: Unable to allocate 128. MiB for an array with shape (8192, 2048) and data type float64]It's one of mistakes I met.
So ,if you make it on GPU ,could you share me your environment setting or other  essential elements to make it？
Thanks

Sorry for the delay, I did not notice this issue. However, I would not have been useful to you anyway because I used a cpu.

authors: giusenso zyc-c

repo: giusenso/seld-tcn


text:
Stackstac 0.5.0 produces bad pixel values for Sentinel-2

When querying Sentinel-2 images from AWS (Element-84), using stackstac 0.5.0 pixel values are significantly different than with 0.4.3. I believe 0.4.3 is giving the correct values. Inspection of some values makes it look like 0.5.0 is subtracting 1000 (maybe incorrectly applying a PB4 correction?) then dividing by 10,000.
Minimal reproducible example:
import stackstac
from pystac_client import Client
geom = {'type': 'Polygon',
 'coordinates': [[(-126.37, 50.43),
   (-126.35, 50.43),
   (-126.35, 50.45),
   (-126.37, 50.45),
   (-126.37, 50.43)]]}
start_date = '2020-07-01'
end_date = '2020-07-03'
url = "https://earth-search.aws.element84.com/v1"
cat = Client.open(url)
date_query = start_date+'/'+end_date
params = {
"intersects": geom,
"collections": ["sentinel-2-l2a"],
"datetime": date_query,}
search = cat.search(**params)
items = search.item_collection()
stack = stackstac.stack(
    items,
    assets=['blue'],
    bounds_latlon=[-126.37,50.43,-126.35,50.45],
    resolution=10,
    epsg=32609)
print(stack[0,0,0,0].to_numpy())

This code with stackstac 0.4.3 give 3176.0 (a reasonable DN for Sentinel-2).
With stackstac 0.5.0, it gives 0.2176.

It should be due to the fact that the newest version applies automatically offset and scale to the data, so that you get the reflectance value and not the digital number. However, in this case there seems to be an issue, since the offset has been introduced with data starting from 2023 onwards.
Related issues to the new processing baseline 4.0 which introduced the offset:
https://github.com/Element84/earth-search/issues/9
https://github.com/Element84/earth-search/issues/23

Ah ok, I see! I did not see the addition of the default rescale=True to stack(). We had our own rescaling in place, so this was a breaking change.
Looking at the first item in the query above, it has s2:processing_baseline = 05.00 so the offset should be applied. The property earthsearch:boa_offset_applied = True. However, raster:bands offset=-0.1. So if stackstac is using the raster:bands property, then it looks like it is wrong for this item. You could use earthsearch:boa_offset_applied but I suppose that is unique the Element-84 STAC.
In our own processing, we have been using the earthsearch:boa_offset_applied. It does complicate things as you have to check both the processing baseline, and whether earthsearch:boa_offset_applied exists and is False for a given item. The property doesn't exist for some items, in which case it becomes None instead of False after calling stack().

Setting rescale=False gives you the correct DN value. So, as you understood, the issue is with the Element84 metadata.
import stackstac
from pystac_client import Client
geom = {'type': 'Polygon',
 'coordinates': [[(-126.37, 50.43),
   (-126.35, 50.43),
   (-126.35, 50.45),
   (-126.37, 50.45),
   (-126.37, 50.43)]]}
start_date = '2020-07-01'
end_date = '2020-07-03'
url = "https://earth-search.aws.element84.com/v1"
cat = Client.open(url)
date_query = start_date+'/'+end_date
params = {
"intersects": geom,
"collections": ["sentinel-2-l2a"],
"datetime": date_query,}
search = cat.search(**params)
items = search.item_collection()
stack = stackstac.stack(
    items,
    assets=['blue'],
    bounds_latlon=[-126.37,50.43,-126.35,50.45],
    resolution=10,
    epsg=32609,
    rescale=False
    )
print(stack[0,0,0,0].to_numpy())
> 3176.0

FYI Element 84 is aware about these confusions and announced aligning processing baseline and metadata in the coming months :)

Great, thanks for the replies! I'll close the issue

FYI this has not been fixed and is quite confusing on the stackstac side since there is no warning or notification that rescaling is happening by default. Given that it has been the better part of a year without resolution on the metadata side, would it be worth making some sort of change on the stackstac side? Could be:
-a note somewhere in the documentation
-a warning if rescale=True and the asset is Sentinel-2 (not sure how hard this would be to implement...)
-changing the default for rescale to be False (this would obviously require a warning/notification to users)

authors: Berhinj clausmichele kearney-sp waltersdan