cksum: implement -z

       -z, --zero
              end each output line with NUL, not newline, and disable file name escaping

we don't have it currently. Should be easy!

Hi, I'm attempting to work on this issue and have linked a draft PR.
I have added the --zero option and implemented the nul/newline by changing the instances of println! to print!, then adding an "\0" or "\n" based on the existence of the flag. Is such an approach acceptable?
I'm currently trying to figure out the 2nd use of the flag, which is "and disable file name escaping". Any guidance on this would be much appreciated!

@orangeng I did some digging and if you look at the output_file function in digest.c, you'll see where the -z flag is also used to control whether "problematic characters" in the filename are escaped:
https://github.com/coreutils/coreutils/blob/v9.5/src/digest.c#L1050
They basically check if the delimiter is "\n" and if it is, then they do some special handling of the filename. Looking through the comparable code in https://github.com/uutils/coreutils/blob/main/src/uu/cksum/src/cksum.rs, I don't see anywhere where any escaping is being done, so it may be that -z is already implicitly being handled and that we need to implement escaping for when -z isn't specified.

I'm not sure about looking at the GNU coreutils source code. But at least according to the info cksum I have noticed that -z is also used for special handling of the filenames. Will work on seeing how that can be implemented in the Rust code.

Right, that's what I meant. I think we don't currently do any escaping which means that we're not consistent with filename handling when -z is not specified.

@dchenbecker Please don't look at or link the GNU source code. That policy is our guarantee that uutils is original code. The documentation fair game though.
In ang case, good find on that functionality!

Apologies! I only looked at digest.c, so I'll steer clear of any future contributions related to that.


ntpclient.c: Replace home-grown ntp_addr_u with sockaddr_storage

Summary
ntpclient.c: Replace home-grown ntp_addr_u with sockaddr_storage
Impact
Testing
It tested IPv4 with lm3s6965-ek:qemu-protected on qemu.
IPv6 is not tested.

i withdraw this


Replace Console Landing page with something better

Is your feature request related to a problem? Please describe.
Replace this with a better page

Closing this in favor of: https://github.com/akash-network/console/issues/100


drivers/syslog: Ensure the buffer zero terminate

Summary
This patch fix the regression by:
commit 174b2403258cbf0e063ac389beeedcd09b8a0b1a
Author: Xiang Xiao<EMAIL_ADDRESS>Date:   Fri Sep 17 11:56:21 2021 +0800

    drivers/syslog: Call up_puts in syslog_default_write instad up_putc

    since some drivers(e.g. semihosting) have more fast implementation.

Report here: https://github.com/apache/incubator-nuttx/pull/4566
Impact
Fix the regression.
Testing

Tested this with few of my projects that use CONFIG_SYSLOG_BUFFER. Works and change looks good to me.


Use hook for time tick computation

This moves the time tick computation into a memoized hook in TimeScrollView.tsx and renames some of the variables. It also uses vectorized pixel placement computation at the time the ticks are computed, to avoid doing it in the paint function (even though that's probably not a big driver of anything under present expectations).
To account for the margins, I added an optional (defaults to 0) extra pixel offset for the 1d time to pixel matrix computations; this fixed a bug I introduced while playing with this.

Looks good to me, merging.


Can't install anything, problem with PGP signatures

I've done fresh install.
Then when I pacman -Syu I got the following error message warning: Public keyring not found; have you run 'pacman-key --init'? downloading required keys... error: keyring is not writable
Following the message, I run pacman-key --init
Then again pacman -Syu  it keeps asking me to import PGP keys. That's suspicious but I did it. Then I got the error error: archlinux-keyring: signature from "Christian Hesse (Arch Linux Package Signing<EMAIL_ADDRESS>is unknown trust:: File /var/cache/pacman/pkg/archlinux-keyring-20211028-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n]
I also tried just installing archlinux-keyring but it also failed.
In conclusion, I can't install anything.

Hi, Thank you for reporting.
Did you run populate?
sudo pacman-key --populate

https://wsldl-pg.github.io/ArchW-docs/How-to-Setup/

It worked ! thank you ! I didn't noticed the link to the setup page.


WIP: Install - add group&owner support

For this, move the chown & chgrp functions to uucore

@rivy @Arcterus @nbraud
show_info is using executable!() which uses module_path() to get the name of the program.
In this PR, I would like to use the actual binary name instead of uucore. Otherwise, it causes unexpected output and test failure like:
  left: `"uucore: changing group of \'/tmp\': Operation not permitted (os error 1)"`,
 right: `"chgrp: changing group of \'/tmp\': Operation not permitted (os error 1)"`', tests/common/util.rs:132:9

Any idea how to fix that? thanks

@rivy @Arcterus @nbraud
show_info is using executable!() which uses module_path() to get the name of the program.
In this PR, I would like to use the actual binary name instead of uucore. Otherwise, it causes unexpected output and test failure like:
  left: `"uucore: changing group of \'/tmp\': Operation not permitted (os error 1)"`,
 right: `"chgrp: changing group of \'/tmp\': Operation not permitted (os error 1)"`', tests/common/util.rs:132:9

Any idea how to fix that? thanks

Yeah, don't do it this way... avoid UI I/O within uucore and instead refactor to return Result<...>'s.
Then, you can handle the results within the specific util itself including any UI.

@sylvestre , I know I read something about why you wanted to do this... but I can't find the email/post.
Would you reiterate your reasoning for the move?

Would you reiterate your reasoning for the move?

@rivy because the "install" command can change the ownership & group of a file. As we are already doing this for chgrp & chown, I think it would be better to have it uucore and make them reusable by both programs.

Yeah, don't implement it as a straight copy of the code... avoid UI I/O within uucore and instead refactor to return Result<...>'s. Then, you can handle the results within the specific util itself including any UI.

I was hoping for something easier but you are right, I will do that, thanks :)


Input components (#5)

As title says. Happy Hacktoberfest!

Please create ´stories/PInput.js` just like the PButton version, fix the minor stuff from review and you're good to go!

Please create ´stories/PInput.js` just like the PButton version, fix the minor stuff from review and you're good to go!

I guess the right file name is ´stories/PInput.stories.js´ just like ´stories/PButton.stories.js´, isn't it?

I guess the right file name is stories/PInput.stories.js just like stories/PButton.stories.js, isn't it?

Yes you're right :)

Can you add another example that show this works on a v-model and multiple radio buttons (meaning if I check one, others are unchecked)

Can you add another example that show this works on a v-model and multiple radio buttons (meaning if I check one, others are unchecked)

Yes, I've just added it.

Thanks @liquorburn


fix path to bash 'script'

in order to run svc_check the path to bash must be provided
otherwise we see next error message in service log:
May 03 08:31:41 srv3 Keepalived_vrrp[614395]: Script bash cannot be accessed - No such file or directory
May 03 08:31:41 srv3 Keepalived_vrrp[614395]: Disabling track script chk_svc_port since not found/accessible
with provided path it's run successfully even with WARNING message about user:
May 03 12:50:48 srv3 Keepalived_vrrp[1861909]: WARNING - default user 'keepalived_script' for script execution does not exist - please create.

@johnsca could please let me know when we can see new version of the charm in charmstore?

Fixes https://bugs.launchpad.net/charm-keepalived/+bug/1926991


504 andrey fix yarn fetch

This fixes the algorithm - images are looked not only by the logo, but also by the item name. Thus we don't have problems when multiple items have the same logo.

Deploy preview for landscape ready!
Built with commit a0b27cc340628f87cba360f508dff96e09a1cfef
https://deploy-preview-516--landscape.netlify.com

In your PR, cached_logos/alauda-kcsp.svg is corrupted because it has an extra return above the xml declaration.

Also cached_logos/alauda-ee.svg is corrupted.

There's also some strange cropping going on, like with LinuxKit: https://github.com/cncf/landscape/pull/516/files?short_path=bd99803#diff-bd99803f71ab299a8e28b7f1806c5a70

It is not corrupted, just github  can not display it, but browser displays everything. Anyway, I've removed an empty line.

Linux kit actually looks ok , it is a github viewer which display is improperly. I've opened it in a new tab and tried to change the browser size, the image was adjusted properly


run/markdown-preview: sample for a secure 2-tier app

Early PR to check how tests are running.

Will this be a tutorial on cloud.google.com?

There will be a tutorial. Revised/added a README pointing at the prospective location.


Provide error if flags not set correctly

We have a couple bool flags in our unmanaged-cluster create command.
These need to either be preset, or explicitly set equal to the desired
value. So either:

--tty
--tty=false

If this value is incorrectly provided as:

--tty false

Cobra interprets that as tty==true and a command line argument of
"false". Since we only expect our cluster name to be provided as a
positional argument, this either sets the cluster name to "false" if
"--type false" is provided before the name, or ignored if provided after
the name.
This updates our command definition to explicitly set the maximum number
of allowed positional arguments to 1. It also changes things to not
error out if the positional argument is not provided since we now can
read that from a configuration file. Our validation already errors out
if no cluster name is defined after parsing this config.

Thoughts?

Yep. With the way you provided this as --tty false and no cluster name, cobra is interpreting this as "set tty to true" and "cluster name is 'false'. It's a syntax problem with how cobra handles that switch. Unless you specify --tty=false, it will not work the way you are expecting.
I left a comment on Slack, but wonder since the use of this flag will usually be to disable tty, maybe we should invert things and rename it to --no-tty.

Ooops, yeah that makes sense. Didn't realize I left out the cluster name (arg)!
However, i'm a little surprised, so cobra cannot evaluate --tty false? It needs to be tty=false?

However, i'm a little surprised, so cobra cannot evaluate --tty false? It needs to be tty=false?

That is my understanding. Maybe @jpmcb can confirm, but I had to walk through in a debugger to confirm that --tty false was setting the tty variable to true and false was one of the args being passed through to the cmd.

Perhaps it would be more clear and best practice to introduce an argumentless flag.
For example: --tty=false to --tty-disable.
Let's get @jpmcb input as to whether this is a good practice. To me, --tty-disable seems more clear.

Sean is correct; this is a symptom of how spf13/pflag is implemented which is what Cobra uses for persistent flags.
spf13/pflag is doing a best effort here with what it's given as a "default" value:

If it finds --tty, it's going to treat this as a switch flag and set this to true (which is already the default value). Note here that it won't attempt to interpret any next "word" as an argument to this flag since it's condition has already been satisfied as a boolean flag.
If it finds _no --tty flag, it's going to use the default value we've set which is true.
If it finds -tty={value} it's going to attempt to use that value as the new flag bool.

Again, in the case where it is seeing just --tty, it's going to interpret that as just a boolean switch, take the argument after and use that as the argument to the create command.
There's actually a good little chunk about what's happening here and the possibility to change the default behavior given no flag is set the pflag library: https://github.com/spf13/pflag#setting-no-option-default-values-for-flags
I agree with Josh, I think the best thing to do here is set a --tty-disable flag that acts as an inverse switch to what we were doing and turns TTY off.

Thanks for the details @jpmcb.
@stmcginnis can we move forward with, --tty-disable. I prefer it over --no-tty because i'd like the noun tty to come before the verb disable.

Updated, but now I see there are merge conflicts. Rebase on its way.

thanks! I'll review and test this shortly.

--tty-disable is now available :heavy_check_mark:
josh@u:~$ ./tanzu-unmanaged-cluster-linux_amd64 create --help

Create an unmanaged Tanzu cluster. This sets up a Kubernetes cluster and installs
Tanzu packages. Once the environment is bootstrapped, your kubectl context is
automatically switched, enabling you to begin using the kubectl and tanzu CLIs.

No configuration is required for this command. However, you can setup a config
file by running tanzu unmanaged-cluster configure <cluster name>. This config file can
then be referenced using the -f flag.

When create is called, it respects the following precedence for all configuration:

1. flags (most respected)
2. environment variables
3. config file
4. defaults (least respected)

Usage:
  tanzu unmanaged-cluster create <cluster name> [flags]

Flags:
  -c, --cni string            The CNI to deploy; default is antrea
  -f, --config string         A config file describing how to create the Tanzu environment
  -h, --help                  help for create
      --pod-cidr string       The CIDR for Pod IP allocation; default is <IP_ADDRESS>/16
  -p, --port-map strings      Ports to map between container node and the host (format: '80:80/tcp' or just '80')
      --provider string       The infrastructure provider for cluster creation; default is kind
      --service-cidr string   The CIDR for Service IP allocation; default is <IP_ADDRESS>/16
      --skip-preflight        Skip the preflight checks; default is false
  -t, --tkr string            The URL to the image containing a Tanzu Kubernetes release
      --tty-disable           Disable log stylization and emojis

Global Flags:
      --log-file string   Log file path
  -v, --verbose int32     Number for the log level verbosity(0-9)

default create uses stylization :heavy_check_mark:

--tty-disable removes stylization :heavy_check_mark:

TTY autodetect still works (validated in cmd prompt, windows) :heavy_check_mark:


Converting DreamShaper_8 results in invalid model

Hi!
I am trying to convert digiplay/DreamShaper_8 to CoreML. I am using…
python -m python_coreml_stable_diffusion.torch2coreml --convert-unet --convert-text-encoder --convert-vae-decoder --convert-safety-checker --model-version digiplay/DreamShaper_8 -o <OUTPUTNAME> --bundle-resources-for-swift-cli
…to convert the model. While the command succeeds, trying inference using the (unmodified) sample project from the CLI like…
./StableDiffusionSample --resource-path <PATHTOMODEL>  --compute-units cpuAndGPU --scheduler dpmpp "car"
…always results in…
Loading resources and creating pipeline (Note: This can take a while the first time using these resources) Step 19 of 20  [mean: 0.91, median: 0.98, last 0.97] step/sec Error: MultiArray shape (1 x 512 x 512 x 3) does not match the shape (1 x 768 x 768 x 3) specified in the model description
The only thing I am noticing during convert is the following output:
scikit-learn version 1.3.1 is not supported. Minimum required version: 0.17. Maximum required version: 1.1.2. Disabling scikit-learn conversion API.
What am I doing wrong? Or is this a bug?

Looks like there is an inconsistent latent dimension that results in an inconsistent output resolution. Can you try reexporting with --latent-h 64 --latent-w 64 to make sure HF hub config files are overridden? (This will enforce 64x64 for latents and 512x512 for the output space)

Thanks for your answer! I tried converting the model using
python -m python_coreml_stable_diffusion.torch2coreml --convert-unet --convert-text-encoder --convert-vae-decoder --convert-safety-checker --model-version digiplay/DreamShaper_8 -o <OUTPUTNAME> --bundle-resources-for-swift-cli --latent-h 64 --latent-w 64
and inference with
./StableDiffusionSample --resource-path <PATHTOMODEL>  --compute-units cpuAndGPU --scheduler dpmpp "car"
and it results in the very same error message
Loading resources and creating pipeline (Note: This can take a while the first time using these resources) Sampling ... Error: Unable to compute the asynchronous prediction using ML Program. It can be an invalid input data or broken/unsupported model.

Great! For ANE inference, you will need --compute-units cpuAndNeuralEngine

Awesome, that works great. Thanks for your support. My models now run on CPU+GPU and ANE (if enough RAM is present).
But: Is it normal that on every app relaunch, ANECompilerService takes approx. 1 to 3 minutes to compile my model for ANE?


More unsoundness in future_sync and future_desync

From PR #7:

Actually, there's more soundness bugs with the signatures of the future_[de]sync() methods. To illustrate:
use desync::Desync;
use futures::executor;

fn leak_local<T: Send>(v: T) -> &'static mut T {
    let desync = Desync::new(v);
    let future = desync.future_sync(|v| async { v });
    executor::block_on(future).unwrap()
}

This was introduced by the change in v0.8 that removed the need to box the future, I think. The lifetime of the borrow is insufficiently restricted without the higher-order trait bound imposed on the function.

future_sync() and future_desync() had a function with the signature for<'b> FnOnce(&'b mut T) -> BoxFuture<'b, TOutput> which prevented this in versions prior to v0.8.
Always having to box the future was a pain, so I wanted to eliminate that and also allow for this kind of code:
let mut foo = true;
bar.future_sync(|x| async { if x.test() { foo = false; } }).await;
if foo { /* ... */ }

which is possible with sync(). I think I can add my own trait to replace BoxFuture to remove the need to call .boxed() all the time, but I think Rust's implementation of higher order trait bounds means there's no way to fully describe the lifetime of the future, so the example above won't work any more (need to be able to write for<'b: 'a> FnOnce(&'b mut T) -> SomeFuture<'b>)

I believe the fix to remove the need to use a boxed future is to add a trait like this:
pub trait IntoBoxFuture<'a, 'b, TBorrow, TOutput> {
    fn make_box(self, val: &'a mut TBorrow) -> BoxFuture<'b, TOutput>;
}

impl<'a, TFn, TBorrow, TFuture> IntoBoxFuture<'a, TBorrow, TFuture::Output> for TFn
where
    TFn: FnOnce(&'a mut TBorrow) -> TFuture,
    TFuture: 'a + Send + Future,
    TBorrow: 'a,
{
    fn make_box(self, val: &'a mut TBorrow) -> BoxFuture<'a, TFuture::Output> {
        (self)(val).boxed()
    }
}

Then change the signature of future_sync() and future_desync() as follows:
    pub fn future_sync<'a, TFn, TOutput>(&'a self, job: TFn) -> impl 'a + Future<Output=Result<TOutput, oneshot::Canceled>> + Send
    where
        TFn:     'a + Send + for<'b> IntoBoxFuture<'b, T, TOutput>,
        TOutput: 'a + Send,

and then make sure the function is called with a lifetime where the data is safe to borrow.
I think this works perfectly for future_desync() where the returned future has a static lifetime but I'm not sure that it's possible to restrict the lifetime of the generated future enough to support the case where future_sync() borrows values from outside.

ecfaaad2ca61b219e9e5b637102d3d022a76378d fixes this by going back to using BoxFuture. I'm going to leave this open for the moment as I'd quite like to figure out a way to get the method outlined above to work.
The problem is that Rust isn't quite smart enough to infer it needs to create a for<'a> FnOnce instead of just a FnOnce when calling a function using the trait so it produces a slightly confusing error.

There's no way to write this so that it works effortlessly with closures on the caller's end. There's only three options:

The caller must write their closure to return a BoxFuture (or similar).
The caller must wrap their closure in a macro that puts it into a funnel to constrain the type (similar to higher-order-closure).
The caller must use an async fn instead of a closure returning a Future.

The last two options require helper traits to write the bounds.

Ah, thanks for letting me know: I want to keep everything working with stable so this probably won't make it in until it's ready, but this definitely looks like something that will help with this problem (it's a fairly minor annoyance but always 'feels' wrong when it's a problem)


Handle multiple keyboards with switchXKBLayoutRequest

Describe your PR, what does it fix/add?
It fixes multiple keyboards issue (see picture below) when changing xkb layout with hyprctl.

Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
There is a problem with how CVarList parses things - it ignores quotes("). Hence when you supply the first parameter, keyboard name, with spaces (see in the picture above) it interprets the keyboard name and param wrong. So either this request has to change the separator, add a wiki note regarding this issue, or change how CVarList parses things.
Is it ready for merging, or does it need work?
Yes.

you mean duplicated keyboard names? That's a problem in keyboard naming, not switchxkblayout.

you mean duplicated keyboard names? That's a problem in keyboard naming, not switchxkblayout.

Oh yes, I agree, totally. But then either Hyprland should give a unique attribute(name/id or whatever) for all devices or iterate through all - like it was done here (I don't like this approach, tho). An additional argument for a unique attribute would be as I explained about the CVarList problem - that a lot of keyboards have spaces in their name and then it is failing to interpret the correct name and value.

spaces should not be showing anymore, update hyprland.

should be fixed with 409ac12f236c06cbb28756239e1d1536078b33bb

Nice, thank you:)


A number of fixes and improvements

#19

Sorry for a delay, want to run through the code and check the built artifact first

It's all great, except for the UACHelper - I don't really like the concept of using nugets in this specific app, as I try to keep it a single artifact, without DLLs - this is why I ripped some of the code and made it "embedded" to sources.
Can you either remove it, or embed relevant parts? Similar to what I did with PropVar, PropertyKey and others.

Can you either remove it, or embed relevant parts? Similar to what I did with PropVar, PropertyKey and others.

I've looked at the UACHelper project, it'll be needed to rip the whole project to make it work. I don't think it would be wise. And I personally don't like to reinvent the wheel and copy-paste code from packages. However I see your point and will remove UACHelper from the code.
BTW regarding single-file idea, have you thought about moving to .NET Core? It has a single-file publishing feature.

That's a good point to consider.
I'll merge request as is, and will probs migrate to newer dotnet and go for single-file deployment by the weekend.
Again, thanks for you contribution, that's really appreciated 👍


Fix deprecation warnings for .Sites.First and .Site.IsMultiLingual

This fixes the warnings mentioned in the issue https://github.com/McShelby/hugo-theme-relearn/issues/920#issue-2540511134

Will be fixed in #912


[CMT-36] Q2 Financial Report #145- German translation

german translation

@jeffor12 Looks like this was made before the blog update. Can you copy your translation, close this pr, and make a new PR and I will be able to merge it.

ok will try..

closed because merged #586


docs: raise DeprecationWarning when 'dialogflow' is installed

Closes #243.
To be released manually as dialogflow 1.1.1, to signal to remaining users that they should use the new package name google-cloud-dialogflow.
Attempting to import dialogflow results in a Deprecationwarning.
(env) busunkim@busunkim:~/github/python-dialogflow$ python3
Python 3.9.2 (default, Feb 28 2021, 17:03:44)
[GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import warnings
>>> warnings.simplefilter('always')
>>> import dialogflow
/usr/local/google/home/busunkim/github/python-dialogflow/dialogflow_v2/__init__.py:53: DeprecationWarning: The package 'dialogflow' has been renamed to 'google-cloud-dialogflow'. 'dialogflow' will no longer be updated. For help upgrading to google-cloud-dialogflow>=2.0.0, see https://github.com/googleapis/python-dialogflow/blob/master/UPGRADING.md.

After October 28, 2021, importing code from the latest release of 'dialogflow' will result in a RuntimeError. If you need to continue to use 'dialogflow' after this date, please pin to a specific version of 'dialogflow' (e.g., dialogflow==1.1.1). If you have questions, please file an issue: https://github.com/googleapis/python-dialogflow/issues.

On/after October 28, 2021 an additional 2.0.0 dialogflow release will be made that raises a RuntimeError instead.
Googlers, see internal doc.

@parthea @telpirion @galz10 Please take a look! I put Oct 28 in the date as that is 97 days from today - if it looks like the release will happen later than next Thursday I will re-adjust the date.

Kokoro build failures are expected since CI setup on master is different from what is set up on the last 1.x release, merging.

Released: https://pypi.org/project/dialogflow/1.1.1/


Github communit standards - missing Descritpion, security policy etc.

Missing are:

Issue templates
Descritpion
security policy etc.
See https://github.com/Proteobench/ProteoBench/community

Done, very simple for now, could make it more elaborate in the future.


Minor bump to support bevy 0.14.

I went ahead and published this crate.

Thank you for updating!


Repository is being misclassified as HTML instead of Python

https://github.com/alexisCata/tornado

This is because your single HTML file is vastly larger than the two Python files:
HTML 3.87 KB
Python 1.15 KB
... which works out to ~77% HTML and ~23% Python so the classification is correct.
If you don't want the HTML to count, you'll need to use a manual override or write more Python 😉


NSFS | Regular object key & dir content object overriding

Explain the changes

PR will handle Key and Key/ overriding, object obj1 overriding with obj1/ should not fail and vice versa

unlink the file obj1 when try to override with dir obj1/ to avoid Not a directory error
delete the folder obj1/ when try to override with file obj1 to avoid error InternalError
normal override(object1 overrides object1 or dir1/ overrides dir1/) will not delete the file/folder

Issues: Fixed #xxx / Gap #xxx

https://github.com/noobaa/noobaa-core/issues/8320

Testing Instructions:

Please refer test in issue https://github.com/noobaa/noobaa-core/issues/8320
when obj1 override with obj1/ dir, a new folder should be created with the name obj1/
when obj1/ dir override with key obj1, a new file should be created with the name obj1
object1 overrides object1 and dir1/ overrides dir1/ should not delete the respective file/folder

[ ] Doc added/updated
[X] Tests added

These changes wont work with versioning, Need to update the code once versioning changes are merged. PR Blocked


Onboarding Request: testme

Active Development
Yes
Tool name
testme
Tool abbreviation
tm
Author(s)
Kat Doe
NOAA Internal
Yes
Maintainer Name
Kat Doe
Maintainer Email
<EMAIL_ADDRESS>Background Text
more information to come soon!
Citation
Doe. 2022. Test me.
References
No response
Associated Tools
No response
User Organizations
Northwest Fisheries Science Center
Online App Link
https://docs.github.com/en/communities/
Executable Link
https://docs.github.com/en/communities/
Website Link
https://docs.github.com/en/communities/
Documentation Link
https://docs.github.com/en/communities/
Source Code Link
https://docs.github.com/en/communities/
PDF Download Link
https://docs.github.com/en/communities/test.pdf
Software Badges
No response
Toolbox Drawers

[ ] Ecosystems
[ ] Fish and Fisheries
[X] Human Dimensions
[ ] Protected Species
[X] General Modeling and Productivity Tools

Keywords

[ ] ADMB
[ ] Age Structured Model
[ ] Bayesian Modeling
[ ] Bycatch
[ ] C++
[X] Calculator
[ ] Data Exploration
[ ] Data Limited Method
[ ] Data Visualization
[ ] Decision Support Tool
[ ] Developer Utilities
[ ] Economics
[ ] Ecosystem
[ ] Ensemble Modeling
[ ] Fish Biology
[ ] Fisheries
[ ] Gradient Solver
[ ] Guided User Interface
[ ] Individual Based Model
[ ] Legacy Tool
[ ] Length Structured Model
[ ] Management Strategy Evaluation
[ ] Marine Mammals
[ ] Maximum Likelihood Estimation
[ ] Model Builder
[ ] Model Comparision
[ ] Multispecies Model
[X] Natural Mortality Model
[ ] NOAA Branding
[ ] North Pacific
[ ] Output Visualization
[ ] Projection Modeling
[ ] R Package
[ ] Reference Points Model
[ ] Risk Assessment Tool
[ ] Salmon
[ ] Sampling Decision Tool
[ ] Shiny
[ ] Simulation
[ ] Size Spectra Model
[ ] Size Structured Model
[ ] Socioeconomics
[ ] Spatial Model
[ ] Species Distribution Model
[ ] Standardized Reporting
[ ] Stock Assessment Model
[ ] Stock Assessment Projections
[ ] Stock Assessment Tool
[ ] Surplus Production Model
[ ] Tag Data Model
[ ] Teaching Tool
[ ] Time Series
[ ] TMB
[ ] User Utilities
[ ] Virtual Population Analysis
[ ] Visualization
[ ] Web App

Uses Github Releases
Yes
Static version number
No response
Comments
No more, looks great!
Code of Conduct

[X] I agree to follow the FIT's Code of Conduct

Automatically generated JSON for the onboarding request:
{
  "active_development": true,
  "tool_name": "testme",
  "tool_abbreviation": "tm",
  "authors": "Kat Doe",
  "noaa_internal": true,
  "maintainer_name": "Kat Doe",
  "maintainer_email"<EMAIL_ADDRESS>  "background_text": "more information to come soon!",
  "citation": "Doe. 2022. Test me.",
  "user_organizations": ["Northwest Fisheries Science Center"],
  "online_app_link": "https://docs.github.com/en/communities/",
  "executable_link": "https://docs.github.com/en/communities/",
  "website_link": "https://docs.github.com/en/communities/",
  "documentation_link": "https://docs.github.com/en/communities/",
  "source_code_link": "https://docs.github.com/en/communities/",
  "pdf_download_link": "https://docs.github.com/en/communities/test.pdf",
  "toolbox_drawers": ["Human Dimensions", "General Modeling and Productivity Tools"],
  "keywords": ["Calculator", "Natural Mortality Model"],
  "uses_github_releases": true
}

Automatically generated JSON for the onboarding request:
{
  "active_development": true,
  "tool_name": "testme",
  "tool_abbreviation": "tm",
  "authors": "Kat Doe",
  "noaa_internal": true,
  "maintainer_name": "Kat Doe",
  "maintainer_email"<EMAIL_ADDRESS>  "background_text": "more information to come soon!",
  "citation": "Doe. 2022. Test me.",
  "user_organizations": ["Northwest Fisheries Science Center"],
  "online_app_link": "https://docs.github.com/en/communities/",
  "executable_link": "https://docs.github.com/en/communities/",
  "website_link": "https://docs.github.com/en/communities/",
  "documentation_link": "https://docs.github.com/en/communities/",
  "source_code_link": "https://docs.github.com/en/communities/",
  "pdf_download_link": "https://docs.github.com/en/communities/test.pdf",
  "toolbox_drawers": ["Human Dimensions", "General Modeling and Productivity Tools"],
  "keywords": ["Calculator", "Natural Mortality Model"],
  "uses_github_releases": true
}


Dashboard views aren't scrollable

Dashboard view above, view from "Create New View for Output" below.
Recreating issue
Create a dashboard view that is too tall to fully display, then try scrolling.
Expected behavior
The dashboard scrolls like an output view.
Additional information
"Create New View for Output" views are scrollable. They create a ClonedOutputArea (extended from Panel) and put it in a MainAreaWidget. Dashboards are not scrollable, despite being extended from MainAreaWidget and DashboardWidgets being extended from Panel.
The difference might occur because Dashboard's content is a Panel that new DashboardWidgets are added to, instead of a single Panel widget that takes up the entire MainAreaWidget like in "Create New View for Output" view.

Behavior with BoxPanels
The lack of scrolling is even worse using BoxPanels as the content of the dashboard.

The views aren't scrollable because the BoxPanel organizes widgets so there's never any overflow. Although the actual cloned widget underneath may be clipped, the direct child of the BoxPanel (the DashboardWidget containing the clipped widget) is fitted. Individual views have been made scrollable by PR #15 but the expected behavior of a smoothly scrollable, complete dashboard should be resolved by the custom layout in development.


Adding my bindings to the list

Adding my bindings to the list. Please note that this project is istill a work in progress

@legendaryredfox thanks for the addition! 👍😄


Ruby-BuildPack Merger

BAM!
Just needed Ruby 2.1.4 support.

Guessing this isn't going anywhere...


Expected value for DOCKER_CERT_PATH error when value is present

I cannot run any boot2docker command because of a config error, however, the variable that is listed in the error has a value.
boot2docker stop
error in run: config error: Near line 6 (last key parsed 'DOCKER_CERT_PATH'): Expected value but found '/' instead.

echo $DOCKER_CERT_PATH
/Users/matt/.boot2docker/certs/boot2docker-vm

ls /Users/matt/.boot2docker/certs/boot2docker-vm
ca.pem		cert.pem	key.pem

This ended up being caused by my trying to set the DOCKER_CERT_PATH variable from ~/.boot2docker/profile


optimize Select #include? similar to #selected?

Optimize #include? similar to #selected? for Select, as desired by the TODO comment.

Thanks for a pull request!
I think the purpose of this TODO was to provide with similar to #selected? logic:

raise UnknownObjectException if no options present
check both option text and label attribute

Thus, I think the same changes should be applied.
Also, can you write a specs for all these cases. An example of such specs for #selected? are in watirspec. Let me know if you need any help with this.

Howdy @p0deje! Thanks for your response.

I'm not sure raising an UnknownObjectException makes sense for #include? since it is only checking if the option exists.  The existing behavior is to just return False if the option does not exist.  A select list without any options would just always return False.
I'll add the label attribute check and tests, the #include? description actually says "text or label" already https://github.com/watir/watir-webdriver/blob/master/lib/watir-webdriver/elements/select.rb#L41

The current implementation checks several times if each element is enabled, which this code doesn't do. Are select list options often disabled? And do we want to change our true/false based on that? Do we need a spec for this to verify this solution works?
Without the enabled checks, this solution makes significantly fewer wire calls and is more efficient at finding the first matching element.
I agree with @Conky5, it makes sense to raise an error if we are passing in a parameter and asking for information about it when it doesn't exist. Asking if it is included in the list should return true/false. I would see a potential test being, is it included, then check to see if it is selected so it doesn't raise the exception in the latter call.

The current implementation checks several times if each element is enabled, which this code doesn't do. Are select list options often disabled? And do we want to change our true/false based on that? Do we need a spec for this to verify this solution works?

I think it doesn't make sense to check for enabled/disabled in #include? because can question method is responding to is if it's included, not can be selected.

I agree with @Conky5, it makes sense to raise an error if we are passing in a parameter and asking for information about it when it doesn't exist. Asking if it is included in the list should return true/false. I would see a potential test being, is it included, then check to see if it is selected so it doesn't raise the exception in the latter call.

Agreed, let's stick to this behavior.

Agreed. Definitely more performance boost than I expected. @Conky5 - Nice work.

Thanks @titusfortner :+1:


mtmv remove mvtmv create table p0 case

Proposed changes
temp  remove mtmv p0 case
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

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

fixed in #15909

I will close this PR, since it is fixed in https://github.com/apache/doris/pull/15909


Helix's get constraints API does not response constraints with related preconfer pubkey

Note that: preconfer pubkey may be not needed. Because when the validator is selected to propose a block, all the constraints should be its delegated preconfer if there is no errors.
Now the /constraints/v1/constraint/{slot} API only return a tx array constraint.
{
  "slot": 0,
  "constraints": [
    [
      {
        "tx": "string"
      }
    ]
  ]
}

We need to add preconfer pubkey field
{
  "slot": 0,
  "constraints": [
    [
      {
        "preconfer_pubkey": "string"
        "tx": "string"
      }
    ]
  ]
}

The preconfer pubkey is useful for rbuilder and taiyi-boost local builder to distinguish the constraints, for example, local builder can do a filtering, only include its own configured preconfer's constraints.
Similiarly, Bolt has pubkey field: https://docs.boltprotocol.xyz/technical-docs/api/relay#constraints

@Akagi201 Do we still need this? I am closing it now. Feel free to reopen it if you think it is neccessary.


Default k8s version switch to 1.23

For 2.6.5 release, we want to switch the default k8s version to 1.23.
The change needs to happen for the following (list may need to be expanded):

Downstream RKE1 (in https://github.com/rancher/kontainer-driver-metadata/blob/dev-v2.6/rke/k8s_version_info.go)
Downstream RKE2/k3s (in https://github.com/rancher/kontainer-driver-metadata/blob/dev-v2.6/channels.yaml and https://github.com/rancher/kontainer-driver-metadata/blob/dev-v2.6/channels-rke2.yaml using appDefaults section as introduced per https://github.com/rancher/rancher/issues/36827)
RKE1 itself (?)
k3s version embedded into Rancher when running in Docker

Note for updating the default version of RKE
Because rancher/rke pulls the metadata from the URL https://releases.rancher.com/kontainer-driver-metadata/release-v2.6/data.json, updating the default version of RKE will happen after the KDM is released.
ref:
https://github.com/rancher/rke/blob/release/v1.3/codegen/codegen.go

The fix is available in the latest 2.6-head
Areas or cases that should be tested

in the docker-install mode, the local cluster should use k3s v1.23.6+k3s1
when creating a node-driver RKE1/RKE2/K3s cluster, the default version should be the latest 1.23.x

the fix can be validated in v2.6.5-rc7

tested on v2.6.5-rc8:

rke 1 and rke2 clusters now default to v1.23.6
docker install default version is v1.23.6+k3s1


Add a relevant FAQ link in "Thinking In React"

I think this FAQ entry is more directly relevant to the question of props vs. state. The linked "State and Lifecycle" section (I updated the url from /docs/interactivity-and-dynamic-uis.html, which is a redirect, I assume from a previous name) has one sentence comparing them (State is similar to props, but it is private and fully controlled by the component.), but it's tucked away and easy to miss.

👍 thanks


.idea folder is not excluded from gitignore in intellij

Is there a reason why the '.idea' folder is not excluded from intellij's gitignore?
Because it adds the idea folder to commit. After looking into it, I found the vcs.xml file in the .idea folder is not getting excluded.
This is what git status shows in Intellij.

The template does ignore parts of the .idea/ directory, just not the whole directory.
https://github.com/toptal/gitignore/blob/master/templates/JetBrains.gitignore#L4-L25
There is a comment in the template to ignore more if you're using gradle or maven.
https://github.com/toptal/gitignore/blob/master/templates/JetBrains.gitignore#L27-L35

Yeah, but can  vcs.xml be added to the exclusion set?

Sure, add it to the template list: https://github.com/toptal/gitignore


[bug] After accidentally copying a large text content, opening the ecopaste search board is stuck

Describe the bug
In macos, the contents of a txt text of more than 50 mb were accidentally copied, after opening the ecopaste search box stuck, and the tauri://localhost process usage in the task manager kept exceeding 100%, while the ecopaste process usage exceeding 50%
Reproduction
No response
Expected behavior
It is best to give an option to limit the size of the content saved by ecopaste
Application and system information
{
  "appName": "EcoPaste",
  "appVersion": "0.1.0",
  "tauriVersion": "1.7.2",
  "platform": "Darwin",
  "platformArch": "aarch64",
  "platformVersion": "14.7.0"
}

Additional context
No response

Duplicate of #569


Remove -out parameter

This is not used anywhere as far as I can tell and prevents the orb being used with Terraform cloud
Error: Saving a generated plan is currently not supported

The "remote" backend does not support saving the generated execution plan
locally at this time.

This is not used anywhere as far as I can tell and prevents the orb being used with Terraform cloud
Error: Saving a generated plan is currently not supported

The "remote" backend does not support saving the generated execution plan
locally at this time.

Hi @martin308 can you expand on your statement The "remote" backend does not support saving the generated execution plan locally at this time. ?
I'm trying to understand where and how this is failing. Is it occurring in when the TF planis executed in the TF Cloud remote environment? Such as the TF VM worker environment in TF cloud?
Interested in your response. Also could you share some of the details such as sample code, error messages and log entries if you have them to better understand and troubleshoot
thanks

Hi,
I got the same error (running Terraform Cloud in a project). It comes when the remote backend is active and the TFC workspace is set in "remote" execution mode.

Switching to local execution will remove the error, but I'd want to keep the remote execution active.
In my understanding, the remote execution mode workflow in TFC doesn't allow the plan to be used out of TFC to do some checks (like some OPA policy run on the plan) before sending it back in an apply. One should simply run apply to trigger the full workflow in TFC where it will be handled by the integrated tools.
This case is only related to the remote mode, the local execution behaves only as state backend and the current orb script works fine.
Hopefully, #43 should allow to remove the out parameter by passing "" to the plan_file parameter, I kept plan.out to keep the default behavior. One will get the plan content streamed, but no way to write it locally to use it in CircleCI in the remote mode.

Hey folks, wanted to let you know that the -out is used now but was not properly referenced earlier. The problem is being resolved in a minor version change.
As for removing the parameter. We are going to be working on a major version update immediately after the minor update. I would expect the major version change, which will support TF cloud, to come out within the next two weeks.
We have done some major refactoring that renders this PR outdated. I will close this for now but please keep an eye out for version 4. Thank you!


[HELP NEEDED] Spell checking/change language

I am trying to change the primary language of the keyboard extension, to affect things like spell checking etc. in the host application, for instance Pages.
If you open Pages and type Swedish text with an English, native keyboard, the Swedish words will be underlined with red. If you now switch to a Swedish, native keyboard, the red goes away.
This works with SwiftKey as well, which should use the same sandboxed keyboard extension environment that KeyboardKit is limited to. So it is possible, I just don't know how to do it.
I try to change preferredLanguage, but it's always nil. I also tried changing the preferred languages with user defaults, but it has no effect.

I don't know anything about custom keyboards, but is this snippet of any help? It's for setting the language of the native keyboard to the one the app expects the user to input. From a subclass of UITextView. Probably unrelated to your issue.
  override var textInputMode: UITextInputMode? {
    guard let languageCode = language.languageCode else { return super.textInputMode }
    for inputMode in UITextInputMode.activeInputModes {
      if let language = inputMode.primaryLanguage {
        if language.hasPrefix(languageCode) {
          return inputMode
        }
      }
    }

    return super.textInputMode
  }

@simme Thank you - I think you're on to something! You can do this even in a keyboard extension. However, when I hard-code sv-SE as language code, it doesn't seem to have any effect on the spell-checking.

I'm closing this since I haven't been able to replicate this.


Configurable schedule and time_zone for CAI Export Cloud Scheduler

Configurable schedule and time_zone for CAI Export Cloud Scheduler

Aaron, thanks for the PR. When we wrote this example, we felt the schedule was sufficiently simple to configure in the Terraform code. If you strongly feel for having it customizable, can you bundle together both variables in a single schedule_config one?


Replace all fmt.Errorf with errors.Wrap  and errors.Errorf

@themandalore
I'm interested in working on this issue, invite me through Gitcoin
my work plan is to make all the changes

@developerfred , sent.  You're our space monkey with regards to testing out this whole gitcoin thing, so let me know if you need anything

@themandalore Thanks, perfect!

Looks like there's still some fmt.Errorf in httpRetriever.go and logConfig.go (the util package)

@themandalore I'll check here, thanks for letting me know.

@themandalore done.

Looks good, let me know the next steps with regard to gitcoin

@themandalore You can add me to the bounty, when I try to express interest I get an error. I reported to the team and I'm analyzing the Gitcoin code to see why.
my gitcoin user: @developerfred

@developerfred , I can't really do anything. I'll reach out to them, but if it takes more than a day or two, just reach back out and we'll close it and manually fix it

@themandalore perfect, i'm talking to them too.
They will fix it now, then the process is just to approve me and then pay.

@themandalore done, now you need to approve me on Gitcoin, for me to submit PR.

Reopening as this is not what I had in mind we need to utilize errors.Wrap, errors.Wrapf and also remove the stutter words like - can't, error, failed.. when adding these in in the final message these will be repeated.
Here are few examples:
errors.Errorf("file %s stat error: %v", historyPath, err)
changed to
errors.Wrapf(err,"stats for file: %v", historyPath)

Note removing the error word - we don't needs it as this is clear and the final print message will include it twice.
Using errors.Wrap allows us to do error matching in the caller and it is generally more structured:
see: https://blog.golang.org/go1.13-errors
errors.Errorf("failed to read psr file @ %s: %v", historyPath, err)
changed to
errors.Wrap(err,"read psr file:%v", historyPath)

please note again the removal of the word failed it is not needed. Also here we don't use Wrapf, but just Wrap


0.2.0 - Refreshed Cookbook Metadata

Modified the cookbook to bring it inline with the current best practice.

Thanks very much


Add Support for stringified JSON fields

PR to support stringified JSON fields, like this one from json-schema.org
Issue 112
Fixes #112

Awesome sauce!!!
And thanks so much for the feedback, I really appreciate the advice!!!

Hey @StefanTerdell , sorry for the miss on that. Looks like I didn't run the build: scripts.
I did a bit of googling and found that support for type narrowing via switch(true) was added in typescript 5.3:
https://www.typescriptlang.org/docs/handbook/release-notes/typescript-5-3.html#switch-true-narrowing
But, I'm not sure it's worth updating the deps just to make that change work. I'll leave that decision up to you.
Thanks again for the great advice and all the hard work that goes into this project!!!


[5.4] Public path hardcoded

Laravel Version: 5.4.16
PHP Version: 7.0.10
Database Driver & Version: MySQL on latest stable Homestead release

Description:
Had issues with laravel Mix and realized that actually it is Laravel's public folder that is causing the issue. I have changed 'public' dir to 'public_html' and it worked fine except for the public_path() helper. Than I realize that 'public' is hardcoded in Illuminate\Foundation\Application.php on line 376
    public function publicPath()
    {
        return $this->basePath.DIRECTORY_SEPARATOR.'public';
    }

I know it's not meant for public dir to be changed I guess, but lots of us are unfortunately forced to do this by our clients hosting. So having the public dir editable in some config file would be a great solution. If possible.
Thanks
Steps To Reproduce:
Change 'public' dir to anything else through the app files and public_path() helper will still return the old one.

I have found temporary solution by rewriting path.public service in AppServiceProvider
    /**
     * Register any application services.
     *
     * @return void
     */
    public function register()
    {
        $this->app->bind('path.public', function() {
            return base_path().DIRECTORY_SEPARATOR.'public_html';
        });
    }


Enable / Disable OnSave, OnDemand format tool

Hi
(thank you for all the tools to go around atom!)
Is it possible to add option to enable / disable each tools (gofmt, goimports, goreturns) on save and on demand ?
goimports and goreturns can be very very slow, it would be ideal to disable them on save action, but you can run them with Ctrl+P cmd.
I have to remove them on formatter.js, to avoid waiting 3 to 5 seconds before atom wakes at each save.
Thks a lot.

This is already possible. Go to Atom > Preferences > Paxkages > gofmt > Settings and disable format on save. The commands can be accessed via cmd-shift-p (OS X, use Linux or Windows equivalent of on those platforms) and you can type golang:gofmt / golang:goimports / golang:goreturns - you'll also see their keyboard shortcuts at that time.

Hum, yes, sorry. A fresh install of all plugins give me this option (or I've not seen it before). Thanks a lot !


Optimize font loading performances with font subsetting

Your missing font issue teased me…
Here is some code to:

use woff2 format. woff2 is supported by every browser since a long while now, woff is pretty much a legacy format. woff2 format for each font is like 10kb less in our case,
shrink font file sizes by removing unnecessary characters from the files [1]
show text as soon as possible rather than waiting for custom font to be loaded
use next/fonts to prevent as much as possible the potential layout shift caused by the new loading strategy [2]

[1] .woff font files were around 50kb each, now the subsetted .woff2 files are around 16kb each. It doesn't sound like much but since font files are things we want to load as fast as possible, it is often on the "critical loading path" and just those few saves are meaningful. :warning: The risky thing of doing this is, if in the future we have weird content with rare characters (like, Ž), we have to remember to build the subsetted fonts again (see new README.md file).
[2] after a few tests, I figured for now, using next/fonts with preloading disabled [3] is the simple thing to do. next/fonts has this cool thing of generating a fallback font that matches sizing of our custom font to prevent layout shift. It's cool because now we render text as soon as possible with font-display: swap rather than waiting for the custom font face to be loaded, so there can be a small time without custom font shown when network is bad.
[3] Preloading is intentionally disabled with next/fonts because if we enable it, it preloads every variant of the font, which is already too much for our use case, it actually impacts negatively the loading speed.
Other things we could dig into to improve font loading:

We could try to preload only the regular and bold variants of the fonts, as those are the ones used early and mostly. Without next/fonts, I did try to preload specific files manually, but that required either a custom webpack loader, or going out of the next assets pipeline, for seemingly not really impactful effects anyway.
use less font weights. We could argue ExtraBold and Medium weights are not that important, and sticking to Regular/RegularItalic/Bold would be enough. But that's just me really overthinking things :)

With this, I think most of the improvements are done and I guess working on this more would be overthinking it. Something I already done way too much tonight.
Note: I left a few commits that could theoretically be squashed, but I'd like to leave them, as it's interesting history to have in order to understand why I ended up with next/fonts in the end.

Now it's ready for real @lebaudantoine!


Add TO Go deliveryservices routes

Also versions the deliveryservice structs and API.

@DylanVolz What do you think of this versioning scheme?
The highlights are:
Structs are versioned via anonymous members:
	DeliveryServiceNullableV12
	DeepCachingType   *DeepCachingType `json:"deepCachingType" db:"deep_caching_type"`

There's a GetRefType for each different version:
	return &refTypeV12
}

{1.3, http.MethodGet, `deliveryservices/?(\.json)?$`, api.ReadHandler(deliveryservice.GetRefTypeV13()...

(This still isn't necessary for routes that don't change, e.g. divisions can still only have {1.2, http.MethodGet, divisions/?(.json)?$, api.ReadHandler(deliveryservice.GetRefType()... [which implicitly serves 1.3])
And functions on each API alias that don't change can be reused:
	v12 := TODeliveryServiceV12(ds.DeliveryServiceNullableV12)
	return v12.GetType()
}```

Tested against our production delivery services.
I started to write API tests, but the API test framework doesn't look like it currently supports objects with data from multiple tables, specifically that it has no way to associate IDs from other tables with the "fixture" data. It looks like it'll take a nontrivial amount of work to extend the framework to support it.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1399/
Test PASSed.

@rob05c We're trying to stay away from id's in the "fixture data" so in your API test you have to make multiple calls (by calling the get by name) to get the ID's

@dewrich Is there an example of that in the code or docs somewhere? I was looking for one to go off of, but didn't see any

@rob05c The cdnName in these two examples refer to the cdnName linkage in the tc-fixtures.json.  The Test case will read the fixtures and use that cdnName to retrieve the associated CDN to get it's id.
https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/testing/api/v13/tc-fixtures.json#L549
https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/testing/api/v13/profiles_test.go#L46
To complete the test case though, you have to setup all the data dependencies by calling the funcs from the other test cases to setup for instance the CDNs, Regions, Divisions, Types (for example) before you can start testing Profiles.

@dewrich Ah, great, that's what I was looking for. I'll try to make deliveryservice tests based on that, and add them to this PR. Thanks!

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1401/
Test FAILed.

np, lemme know if you need help

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1408/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1430/
Test PASSed.

Adding WIP label: As far as I'm aware, this is complete, but I haven't thoroughly tested.
Delivery Services endpoints:

create and delete parameters
create SSL keys in Riak
update SSL keys in Riak
create DNSSEC keys in Riak

If anyone tests and verifies everything works, feel free to merge. Otherwise, I'll test when I can, probably next week, and remove the WIP label then.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1453/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1454/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1455/
Test FAILed.

RAT flagged a couple of files for lack of license -- don't forget to check those..

RAT flagged a couple of files for lack of license -- don't forget to check those..
Fixed

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1469/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1470/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1471/
Test PASSed.

just checking this out to help with crconfig testing -- routes.go has conflicts on rebasing,  but got this after fixing that:
deliveryservice/dnssec.go:34:2: cannot find package "github.com/miekg/dns" in any of:
	/home/dkirkw202/go/src/github.com/apache/incubator-trafficcontrol/traffic_ops/traffic_ops_golang/vendor/github.com/miekg/dns (vendor tree)

so,  looks like you're missing a dependency in vendor/...

@dangogh Fixed the merge conflicts, vendored miekg/dns

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1498/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1499/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1521/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1660/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1661/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1670/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1674/
Test PASSed.

don't forget to add the new vendor'd dirs to .rat-excludes
Done

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1676/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1685/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1708/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1709/
Test PASSed.

@rob05c is the license for the DNS library dep valid for Apache?
https://github.com/miekg/dns/blob/master/LICENSE

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1717/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1718/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/1719/
Test PASSed.


Line labels

This PR adds legend labels for both the fit lines in the scatter plots, as well as the vertical lines in the histograms. The labels match the color of the lines in the viewers, and the order of the labels matches the relevant selection order.

I'm not sure where the upside down check marks in front of the numbers are coming from, but I'm guessing @heywooddogwood may want to style those legends differently. Merging in for now, so we can still have the functionality and we can work on the design details later.


delete a linked resource

Link a crew to a location, then delete the crew. Below would happen:

The same to linking a resource to flight.

Should be fixed with #253


Readme.md says that BoundingBox.prefab is necessary for AppBar + Bounding box interactble to work

In this Readme.md: https://github.com/Microsoft/MRDesignLabs_Unity/tree/master/DesignLabs_Unity_Examples
It looks like BoundingBox.prefab is no longer necessary to be put into the scene in order for AppBar + Bounding box to work. Also, BoundingBox.prefab no longer exists and seems to have been replaced by ShellBoundingBox and BasicBoundingBox. Now, it looks like BoundingBox target automatically instantiates the ShellBoundingBox

Thanks for the heads up. I've updated the readme and will close this issue once it's been reviewed.

@ei2kpi @Railboy I'll review updated logic and related documents. Thanks!


Error with a BC21 container

Describe the issue
Can't acces to my BC21 container, the output script don't give me errors, but have some error in the eventlog.
Scripts used to create container and cause the issue
$ContainerName = 'BC21'
$imageName = 'BC21'
$artifactUrl = Get-BCArtifactUrl -type sandbox -country es -select Latest
$UserName = 'someUser'
$Password = ConvertTo-SecureString "somePassword" -AsPlainText -Force
$Credential = New-Object System.Management.Automation.PSCredential ($UserName, $Password)

$licenseFile = 'LicensePath'

New-BCContainer -accept_eula `
-useSSL:$false `
-containerName $containerName `
-credential $credential `
-auth NavUserPassword `
-artifactUrl $artifactUrl `
-includeTestToolkit `
-multitenant:$false `
-assignPremiumPlan `
-licenseFile $licenseFile `
-dns '<IP_ADDRESS>' `
-updateHosts `
-isolation hyperv

Full output of scripts
BcContainerHelper is version 4.0.5
BcContainerHelper is running as administrator
Hyper-V is Enabled
UsePsSession is True
Host is Microsoft Windows 11 Enterprise - 22H2
Docker Client Version is 20.10.20
Docker Server Version is 20.10.20
Removing Desktop shortcuts
Downloading application artifact /sandbox/21.0.46256.48790/es
Downloading C:\Users\carlos.perez\AppData\Local\Temp\65eac736-dd09-4737-9316-6579acb40edd.zip
Unpacking application artifact to tmp folder using Expand-Archive
Downloading platform artifact /sandbox/21.0.46256.48790/platform
Downloading C:\Users\carlos.perez\AppData\Local\Temp\f72ccf82-4b88-4d03-832c-d27c386ec3c4.zip
Unpacking platform artifact to tmp folder using Expand-Archive
Downloading Prerequisite Components
Downloading c:\bcartifacts.cache\sandbox\21.0.46256.48790\platform\Prerequisite Components\IIS URL Rewrite Module\rewrite_2.0_rtw_x64.msi
Downloading c:\bcartifacts.cache\sandbox\21.0.46256.48790\platform\Prerequisite Components\DotNetCore\DotNetCore.1.0.4_1.1.1-WindowsHosting.exe
Fetching all docker images
Fetching all docker volumes
Using image mcr.microsoft.com/businesscentral:10.0.20348.1129
Creating Container BC21
Style: sandbox
Multitenant: No
Version: 21.0.46256.48790
Platform: 21.0.46384.48780
Generic Tag: <IP_ADDRESS>
Container OS Version: 10.0.20348.1129 (ltsc2022)
Host OS Version: 10.0.22621.674 (22H2)
Using hyperv isolation
Using locale es-ES
Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
Using license file C:\Licencias\bc21.flf
Files in C:\ProgramData\BcContainerHelper\Extensions\BC21\my:
- AdditionalOutput.ps1
- license.flf
- MainLoop.ps1
- SetupNavUsers.ps1
- SetupVariables.ps1
- updatehosts.ps1
Creating container BC21 from image mcr.microsoft.com/businesscentral:10.0.20348.1129
f3a7e98badabf3856eefd43a3725e2ab9b1cd10cae24bc0de28f72f86f7d1594
Waiting for container BC21 to be ready
Using artifactUrl https://bcartifacts.azureedge.net/sandbox/21.0.46256.48790/es
Using installer from C:\Run\210-new
Installing Business Central
Installing from artifacts
Starting Local SQL Server
Starting Internet Information Server
Copying Service Tier Files
c:\dl\sandbox\21.0.46256.48790\platform\ServiceTier\Program Files
c:\dl\sandbox\21.0.46256.48790\platform\ServiceTier\System64Folder
Copying PowerShell Scripts
c:\dl\sandbox\21.0.46256.48790\platform\WindowsPowerShellScripts\Cloud\NAVAdministration
c:\dl\sandbox\21.0.46256.48790\platform\WindowsPowerShellScripts\WebSearch
Copying Web Client Files
c:\dl\sandbox\21.0.46256.48790\platform\WebClient\Microsoft Dynamics NAV
Copying ModernDev Files
c:\dl\sandbox\21.0.46256.48790\platform
c:\dl\sandbox\21.0.46256.48790\platform\ModernDev\program files\Microsoft Dynamics NAV
Copying additional files
Copying ConfigurationPackages
C:\dl\sandbox\21.0.46256.48790\es\ConfigurationPackages
Copying Test Assemblies
C:\dl\sandbox\21.0.46256.48790\platform\Test Assemblies
Copying Extensions
C:\dl\sandbox\21.0.46256.48790\es\Extensions
Copying Applications
C:\dl\sandbox\21.0.46256.48790\platform\Applications
Copying Applications.ES
C:\dl\sandbox\21.0.46256.48790\es\Applications.ES
Copying dependencies
Copying ReportBuilder
Importing PowerShell Modules
Restoring CRONUS Demo Database
Setting CompatibilityLevel for CRONUS on localhost\SQLEXPRESS
Modifying Business Central Service Tier Config File for Docker
Creating Business Central Service Tier
Installing SIP crypto provider: 'C:\Windows\System32\NavSip.dll'
Starting Business Central Service Tier
Importing license file
Stopping Business Central Service Tier
Installation took 111 seconds
Installation complete
Initializing...
Setting host.docker.internal to <IP_ADDRESS> in container hosts file (copy from host hosts file)
Setting gateway.docker.internal to <IP_ADDRESS> in container hosts file (copy from host hosts file)
Setting kubernetes.docker.internal to <IP_ADDRESS> in container hosts file (copy from host hosts file)
Setting host.containerhelper.internal to <IP_ADDRESS> in container hosts file
Starting Container
Hostname is BC21
PublicDnsName is BC21
WARNING: Container starts with TimeZone = Hora estÃ¡ndar romance, which is not recognized in the list of TimeZones.
Using NavUserPassword Authentication
Creating Self Signed Certificate
Self Signed Certificate Thumbprint D0DF4F17B3557A8A56FC425C8F6E7A3250F704D7
DNS identity BC21
Modifying Service Tier Config File with Instance Specific Settings
Starting Service Tier
Registering event sources
Creating DotNetCore Web Server Instance
Using application pool name: BC
Using default container name: NavWebApplicationContainer
Copy files to WWW root C:\inetpub\wwwroot\BC
Create the application pool BC
Create website: NavWebApplicationContainer without SSL
Update configuration: navsettings.json
Done Configuring Web Client
Enabling Financials User Experience
Using license file 'c:\run\my\license.flf'
Import License
Creating http download site
Setting SA Password and enabling SA
Creating admin as SQL User and add to sysadmin
Creating SUPER user
WARNING: The password that you entered does not meet the minimum requirements.
It should be at least 8 characters long and contain at least one uppercase
letter, one lowercase letter, and one number.
Assign Premium plan for ADMIN
Container IP Address: <IP_ADDRESS>
Container Hostname  : BC21
Container Dns Name  : BC21
Web Client          : http://BC21/BC/
Dev. Server         : http://BC21
Dev. ServerInstance : BC
Setting BC21 to <IP_ADDRESS> in host hosts file

Files:
http://BC21:8080/ALLanguage.vsix

Container Total Physical Memory is 8.5Gb
Container Free Physical Memory is 6.4Gb

Initialization took 37 seconds
Ready for connections!
Reading CustomSettings.config from BC21
Creating Desktop Shortcuts for BC21
Synchronizing Permissions Mock on default
App successfully synchronized
Installing Permissions Mock on default
App successfully installed
Synchronizing Test Runner on default
App successfully synchronized
Installing Test Runner on default
App successfully installed
Synchronizing Any on default
App successfully synchronized
Installing Any on default
App successfully installed
Synchronizing Library Assert on default
App successfully synchronized
Installing Library Assert on default
App successfully installed
Skipping app 'C:\Applications.ES\Microsoft_Permissions Mock_21.0.46256.48790.app' as it is already installed
Synchronizing Library Variable Storage on default
App successfully synchronized
Installing Library Variable Storage on default
App successfully installed
Publishing C:\ProgramData\BcContainerHelper\Extensions\BC21\34451969-6031-4c28-88b6-a00288041600\Microsoft_System Application Test Library_21.0.46256.48790.app
Synchronizing System Application Test Library on tenant default
Installing System Application Test Library on tenant default
App Microsoft_System Application Test Library_21.0.46256.48790.app successfully published
Publishing C:\ProgramData\BcContainerHelper\Extensions\BC21\51bf80c1-a01b-42e1-985a-0822427cdb28\Microsoft_Tests-TestLibraries_21.0.46256.48790.app
Synchronizing Tests-TestLibraries on tenant default
Installing Tests-TestLibraries on tenant default
App Microsoft_Tests-TestLibraries_21.0.46256.48790.app successfully published
TestToolkit successfully imported
Container BC21 successfully created

Use:
Get-BcContainerEventLog -containerName BC21 to retrieve a snapshot of the event log from the container
Get-BcContainerDebugInfo -containerName BC21 to get debug information about the container
Enter-BcContainer -containerName BC21 to open a PowerShell prompt inside the container
Remove-BcContainer -containerName BC21 to remove the container again
docker logs BC21 to retrieve information about URL's again
...

Additional context
I have other bccontainers working, only happends with that ones.

Hi Freddy,
The eventlog its from the container, anyways, when open the url in a normal browser session, dont log me in, but i didn't try to do it in-private, now its working.
Thank you!


Add exercise: saddle-points

I've marked this as a draft because I had to add some test procedures for type(point_t) arrays, and I'm not sure where best to put them.
They're too exercise-specific to be added to testlib/TesterMain.f90 at the track level. If they're in a separate file, how do I make them available both in the editor and via CLI? I currently have a saddle_points_helper module in saddle_points_test.f90, but that would be too visible to students (e.g., in the editor's test tab).

I'd suggest you don't want to hide the code from the student. List the helper file in .meta/config.json in the .files.editor array. The CLI will download it as a separate file, and the web editor will display it as a source file but readonly.

How does that look to you? A satisfactory solution?
I would suggest adding a brief comment to the helper file indicating that it's used by the test suite, and the student should not worry about not understanding all of it. Or something to that effect.

Sorry, I don't know cmake.


Arg '--cookies-file' broken on 2.0

I was trying this simple code using 2.0:
from selenium.webdriver.phantomjs import webdriver

driver = webdriver.WebDriver(service_args=['--cookies-file=cookies.txt'])
driver.get('http://google.com')
driver.quit()

The 'cookies.txt' file wasn't being created, tried many times, no lucky. Downgraded to 1.9.8 and bang, working 100%

Hi,
I encountered the same issue. By changing one line in the "phantom.cpp" file I got it working, but I'm not sure if this is the correct way to do it (or if it will break existing code).
Change the the line in the Phantom::createCookieJar method from:
return new CookieJar(filePath, this);
to
return new CookieJar(m_config.cookiesFile() != "" ? m_config.cookiesFile() : filePath,this);

Are you sure? Because I don't see that line in phantom.cpp.

I mean in this method:
https://github.com/ariya/phantomjs/blob/master/src/phantom.cpp#L297

Yes, maybe manually modifying the source can fix the issue. But people behind PhantomJS need to fix that!

can this be a possible workaround http://stackoverflow.com/questions/34797962/phantomjs-custom-persistent-cookie-handling ?

I met the same problem. 1.9.8 does working!

I have the same problem.

+1, Does anybody can fix it?

Perhaps there is a problem with Ghostdriver. Because the plain PhantomJS script works.

This is at line 310 now.

I'm running into some serious issues because of this, and I would've expected functionality like this to be much more visible, and problematic for a lot of users. Is there perhaps some workaround I'm not aware of?

The "workaround" is to compile it yourself after fixing the code the way @yali25 suggests.
Here's a wiki page with step by step instructions https://github.com/Yossi/agent-stats-utils/wiki/How-to-compile-phantomjs-for-yourself

That "workaround" may be suitable for things that only use phantomjs locally, but it's certainly not for the acceptance tests of my open source project, which have to run on TravisCI as well as on the local machine of anyone who wants to develop the project.
For anyone else who has similar needs, I have come up with a workaround the solves the problem if your environment requires phantomjs, but has no control over the version or compilation. I'm using Selenium WebDriver in my tests, to wrap phantomjs. I've written some wrapper methods that are called to get a Browser instance and to request pages; after a page is requested (before teardown), I use WebDriver's get_cookies() method to retrieve a list/array of cookies and then serialize that to disk as JSON. When a new Browser is constructed and a page is first loaded, I deserialize the JSON and use add_cookie() to inject the cookies back into phantomjs. As far as I can tell, this works with any phantomjs version (and in theory should work with any other WebDriver-supported browser as well).


Handle provisional notification status on iOS 12 and above

Fixes #27

@Vanethos This is much-needed PR. Please merge and release the new version.
Thank you.

Thanks, I don't have the permissions to merge the pull request and would also need to update the version number.

Thank you very much for the PR @DuncanKelbie ! Released new version: 0.4.7


Repository listing filter broken after upgrading from gogs 0.11.91 to gitea 1.12.0-rc2

Gitea version (or commit ref): 0.12.0-rc2
Git version: 2.20.1
Gogs version: 0.11.91
Operating system: Debian Buster (stable with all current updaes installed)
Database:

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes
[ ] No
[x] Not relevant

Log gist:

Description
After migrating from gogs 0.11.91 to gitea 1.12.0-rc2 the "Repositories" list to the right is broken. It was still working with 1.11.6. It seems to be a filtering issue: if I select archived (✓) or not archived (-) it works - with the empty checkbox (which should list both archived and non-archived) I get an empty list as per the attached screenshot.
Steps taken for the migration:

stop gogs
create a new minimal app.ini
set DB version to 13 as per #5318
start gitea 1.6.4 (since #5318 seems to imply this is supported without going through previous versions)
sop gitea
start gitea 1.11.6 (with #10026 dropping migrations from before 1.6.x in current code that to me implies going from 1.6.4 to 1.11.6 should be safe)
Run "Reinitialize all missing Git repositories for which records exist"
Remove gogs hooks: find $REPO_DIR -path *-receive.d/*-receive -delete (see #3558 for Details)
Run "Resynchronize pre-receive, update and post-receive hooks of all repositories" (or PRs will break #8208)
stop gitea
start gitea 1.12.0-rc2

Screenshots

OK it looks like we could add another migration v142.go which does this step.
Probably reasonable to do it as we never really want is_archived to be NULL

For 1.12 unfortunately we can't backport the auto-migration but the gitea doctor command could be used to fix this.


re-implement the OverfittingFeatures in Java

@sophiehye has done great OverfittingFeatures in Python, we can reimplement them in Java in Coming.

link

@jaxxgu,
May I know how much you have reimplemented for the overfitting features? I feel like it may be a bit confuse and difficult for you when you start without any guidance. Maybe I can do the framework and discuss with you, then you can contribute the details. WDYT? I will back to office August 1st.

Hey @SophieHYe
I am still at Context2Name, but I am also reading your scripts.
It would be helpful to have one discussion, when you have time.


[BUG]: nb::c_contig constraint is not enforced for non-contiguous PyTorch arrays

Problem description
When binding a function processing tensors, one can specify contiguity flags, like nb::c_contig. Nanobind is expected to ensure the input tensors are contiguous in memory before calling the function.
However, when passing a non-contiguous PyTorch tensor to such a function will raise an error, instead of making it contiguous under the hood.
Modifying the Nanobind example project with the following function definition allows to reproduce this issue.
Function binding
m.def("add", [](nb::ndarray<float, nb::c_contig> a, nb::ndarray<float, nb::c_contig> b) { return 0; }, "a"_a, "b"_a);

Reproducer
from nanobind_example import add
import drjit as dr
import torch
a = torch.ones((3,3))
b = dr.ones(dr.llvm.TensorXf, (3,3))

# DrJit tensors, works as expected
print(b,b)
print(b,b[::-1])

# PyTorch tensors, fails
print(add(a,a))  # Contiguous tensors, returns 0
print(add(a,a.T)) # a.T is non-contiguous, this fails

This raises the following issue
Traceback (most recent call last):
  File "<stdin>", line 11, in <module>
TypeError: add(): incompatible function arguments. The following argument types are supported:
    1. add(a: ndarray[dtype=float32, order='C'], b: ndarray[dtype=float32, order='C']) -> int

Invoked with types: torch.Tensor, torch.Tensor

Just double-checking: wasn't the error in the cholespy repository about a crash? (Rather than a TypeError mentioned here).

The bug mentioned a crash, but the reproducer produced this error, without crashing.

Does that mean that the code in the original issue didn't have the annotation? Otherwise it sounds like there are two separate issues.

The bindings in cholespy already had the nb::c_contig annotations, prior to this issue.

Fixed in https://github.com/wjakob/nanobind/commit/23ea3202294a5f3758b6d496404a875527386555.

@bathal1 : I released nanobind v1.5.2 -- you might want to re-release cholespy with those fixes.


[SwitchBase] readOnly doesn't work as per doc

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

Setting readOnly prop on [Checkbox][Radio][Switch] doesn't work as per doc
Expected Behavior 🤔

Ether change the doc by removing "It prevents the user from changing the value of the field"
Or fix it

Steps to Reproduce 🕹

This CodeSandbox demonstrate an issue
Context 🔦

Why we'd like to fix it
Read-only controls are different from Disabled
The readonly attribute has the following effects on an element:

Read-only elements values are sent when submitting the form.
Read-only elements receive focus but cannot be modified by the user.
Read-only elements are included in tabbing navigation.
Read-only elements may be successful.

The disabled attribute has the following effects on an element:

Disabled controls values aren't sent when submitting the form.
Disabled controls do not receive focus.
Disabled controls are skipped in tabbing navigation.
Disabled controls cannot be successful.

Why we'd like to change the doc
HTML readonly attribute set to <input> with type="checkbox"  or type="radio" doesn't work (please see CodeSandbox)
Your Environment 🌎

Tech
Version

Material-UI
v4.9.1

React

Browser

TypeScript

etc.

This is a duplicate found here: https://github.com/mui-org/material-ui/issues/19546

@TommyJackson85 , I found this bug while fixing another in the [SwithBase] component and it's not about [FormControlLabel], which doesn't pass the readOnly prop to its control. It's about an old issue with readOnly for checkboxes, radios, and switches themselves.
BTW, I'm good with the solution in the https://github.com/mui-org/material-ui/issues/19546, which does what we expect from it, but it's not relevant for the issue here described

ok, well I am working on the other issue anyway. Would you think the methods to fix each are simular. Is there anything that needs to be blocked from a readOnly prop? Maybe handleChange?

The issue is in the way browsers treat <input type="checkbox|radio" readonly>—they just don't handle this case allowing users to change checkboxes and radios.
Taking that into consideration, I'm curios whether we need to support readonly the way we prevent changing [SwitchBase] components. If so, the implementation is tricky a bit, because at least we'll need to

override the provided onChange (for controlled components)
track onKeyDown to prevent Enter or Space click, which triggers change (for uncontrolled components)
prevent clicking by adding pointer-events: none; CSS (for uncontrolled components)

But if we're good with the standard behavior in browsers and we don't fix browsers bugs here, I'll just update the doc

But if we're good with the standard behavior in browsers and we don't fix browsers bugs here, I'll just update the doc

What i'm getting at is that if it's a know browser issue and we don't want to fix it here, we'll need to do our best to pass the readonly down to the native <input> element anyway so that users are able to fix it on their side the way they prefer.
From that I wanna ask the crew whether we'd like to add the readOnly prop to [FormControl], so the readOnly is passed by [FormControlContext] to each form control element (like disabled, error etc.). If so, I'll create a separate Issue[Feature request] with that

So maybe use this issue as a discussion platform first instead to generate ideas. Then create separate issues for each task.
While this is not a duplicate of #19546 I think it would be best to do one at a time. I could at-least use this repository for reference.

Duplicate of #17043


fix: Update syntax highlighting on posts

This addresses issue #3
However, I had an issue with the following post: https://www.bryanbraun.com/2014/11/27/every-possible-way-to-define-a-javascript-function/
This has all the code inside of a <table /> and would require manually setting up the highlighting, from what I can tell. However, I think some of this can be worked around by tweaking your Markdown settings in the _config.yaml. Right now there isn’t anything specifying which Markdown renderer to use, but from what I can tell, Kramdown supports Markdown inside HTML tags.
Hope this helps!

Thanks Z! This looks great.


Uninitialised value(s) in parse_number (numberparsing.h:509)

Another fuzzing victim...
The following input:
echo  '-7.9431' >prettynormal

Gives the following input in a Debug build:
valgrind tools/jsonstats prettynormal

paul@tonfisk:~/code/delaktig/simdjson/build-plain-normal$ valgrind tools/jsonstats prettynormal
==25144== Memcheck, a memory error detector
==25144== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==25144== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==25144== Command: tools/jsonstats prettynormal
==25144==
==25144== Conditional jump or move depends on uninitialised value(s)
==25144==    at 0x132CB4: parse_number (numberparsing.h:509)
==25144==    by 0x132CB4: simdjson::haswell::unified_machine(unsigned char const*, unsigned long, simdjson::ParsedJson&) (stage2_build_tape.h:201)
==25144==    by 0x13AC71: int simdjson::unified_machine<(simdjson::Architecture)1>(unsigned char const*, unsigned long, simdjson::ParsedJson&) (stage2_build_tape.h:25)
==25144==    by 0x10C75A: int simdjson::json_parse_implementation<(simdjson::Architecture)1>(unsigned char const*, unsigned long, simdjson::ParsedJson&, bool) (jsonparser.h:41)
==25144==    by 0x10C4FD: simdjson::json_parse_dispatch(unsigned char const*, unsigned long, simdjson::ParsedJson&, bool) (jsonparser.cpp:75)
==25144==    by 0x10C39E: simdjson::json_parse(unsigned char const*, unsigned long, simdjson::ParsedJson&, bool) (jsonparser.cpp:23)
==25144==    by 0x10C56D: simdjson::build_parsed_json(unsigned char const*, unsigned long, bool) (jsonparser.cpp:86)
==25144==    by 0x10B4AD: simdjson::build_parsed_json(char const*, unsigned long, bool) (jsonparser.h:180)
==25144==    by 0x10B519: simdjson::build_parsed_json(simdjson::padded_string const&) (jsonparser.h:218)
==25144==    by 0x10AA9C: simdjson_compute_stats(simdjson::padded_string const&) (jsonstats.cpp:42)
==25144==    by 0x10B0D2: main (jsonstats.cpp:133)
==25144==
# integer_count float_count string_count backslash_count non_ascii_byte_count object_count array_count null_count true_count false_count byte_count structural_indexes_count
0 1 0 0 0 0 0 0 0 0 8 2
==25144==
==25144== HEAP SUMMARY:
==25144==     in use at exit: 0 bytes in 0 blocks
==25144==   total heap usage: 51 allocs, 51 frees, 93,967 bytes allocated
==25144==
==25144== All heap blocks were freed -- no leaks are possible
==25144==
==25144== For counts of detected and suppressed errors, rerun with: -v
==25144== Use --track-origins=yes to see where uninitialised values come from
==25144== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

Same issue.

Unfortunately not, it still reproduces even with your fix in 65b30623c9655edbc7f0043ceaf4352754f01c1a (I cherry-picked it on my local branch)

$ valgrind ./parse jsonchecker/pass23.json ==4333== Memcheck, a memory error detector
==4333== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==4333== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==4333== Command: ./parse jsonchecker/pass23.json
==4333==
number of iterations 1000
number of bytes 23 number of structural chars 2 ratio 0.087
mem alloc instructions:      51212 cycles:      27743 (31.74 %) ins/cycles: 1.85 mis. branches:        183 (cycles/mis.branch 151.31) cache accesses:       1921 (failure          7)
 mem alloc runs at 1206.22 cycles per input byte.
stage 1 instructions:      54512 cycles:      34254 (39.18 %) ins/cycles: 1.59 mis. branches:        603 (cycles/mis.branch 56.77) cache accesses:       1921 (failure          0)
 stage 1 runs at 1489.34 cycles per input byte.
stage 2 instructions:      33371 cycles:      25421 (29.08 %) ins/cycles: 1.31 mis. branches:        335  (cycles/mis.branch 75.79)  cache accesses:       1636 (failure          2)
 stage 2 runs at 1105.30 cycles per input byte and 12710.93 cycles per structural character.
 all stages: 3800.86 cycles per input byte.
Estimated average frequency: 6.987 GHz.
Min:  1.2511e-05 bytes read: 23 Gigabytes/second: 0.00183838
==4333==
==4333== HEAP SUMMARY:
==4333==     in use at exit: 0 bytes in 0 blocks
==4333==   total heap usage: 12,127 allocs, 12,127 frees, 26,798,358 bytes allocated
==4333==
==4333== All heap blocks were freed -- no leaks are possible
==4333==
==4333== For counts of detected and suppressed errors, rerun with: -v
==4333== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

Right. So it is not exactly the same issue, but if you look at the fixes, you see it is the same conceptual error repeated throughout copied-pasted code. So it is really just one fix.

Yep, https://github.com/lemire/simdjson/commit/84d2d89b385da54a56fa91ef40203cbfe09c399c indeed fixes this!

Thanks.


[DOC] Update documentation website theme

Context
The documentation currently uses very basic conda-store brand colors, but these need to be updated esp for dark mode.
Value and/or benefit
Consistent and more polished website.
Anything else?
No response

Update: I've worked on a color system for this, and I'm currently working with @pavithraes to iron out a few kinks and to understand what variables and colors are being used in the theme

I discussed with @pavithraes that I'd need to see some previews before I can finalise the colours, so this is a starting point to see how the colours look and I'll tweak them accordingly
:root {
  /* Light */
  /* colors */
  ----ifm-color-primary: #298642;
  ----ifm-color-primary-dark: #206532;
  ----ifm-color-primary-darker: #144321;
  ----ifm-color-primary-darkest: #0a2210;
  ----ifm-color-primary-light: #5cb975;
  ----ifm-color-primary-lighter: #85cb97;
  ----ifm-color-primary-lightest: #d6eedc;
  /* Dark */
  /* colors */
  ----ifm-color-primary: #5cb975;
  ----ifm-color-primary-dark: #85cb97;
  ----ifm-color-primary-darker: #addcba;
  ----ifm-color-primary-darkest: #d6eedc;
  ----ifm-color-primary-light: #298642;
  ----ifm-color-primary-lighter: #206532;
  ----ifm-color-primary-lightest: #144321;
}


Renamed CONTRIB.md and linked it in README.md

Solves #184

Despite the check failure, my CLA is signed:

I re-signed the CLA with the same email I used to author the commits on the pull request.

Hey @googlebot ! Can you check again please?

@dellagustin It looks like you used a different email in the commit than the one you used signing the CLA. You can see in this PR that the commit doesn't show your profile image next to it.
Try adding the email (dellagutin@) to your GitHub account or sign the commit with a different email. Then say "I signed it!"


Add pre-release image to LazyView

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

File
Status
Preview URL
Details

docs/views/lazyview.md
:white_check_mark:Succeeded
View

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


7.10 migration: Override default NFData implemtation for newtype X

The simple travis configuration present in the repo at the moment only builds agains GHC 7.6.3, how do you feel about configuring it to build against all versions from 7.6.3 to HEAD in order to catch these kinds of problems ?

Yeah, that would be a good idea.  How do I set that up?

Vector travis configuration is solid and @hvr has an ubuntu ppa with that is used there which also has a binaries for 7.10.1, you'll just have to also add that to the vector config as they don't build yet for 7.10.1 on travis. Or I can do it.:-P

I opened #15 to remind myself

Ok, be aware that there might be some package that do not build with 7.10.1 on travis, I belive due to using to much memory but I may be completely wrong, I for one could not get a vector build going with 7.10.1.

Alright.  Thanks for the warning :)


Your Xcode is too outdated while attempting to install brew packages

[X] Confirmed this is a problem with running a brew command and not brew installing or the post-install behaviour of one or more formulae? If it's a formulae-specific problem please file this issue at https://github.com/Homebrew/homebrew-core/issues/new
[X] Ran brew update and retried your prior step?
[X] Ran brew doctor, fixed all issues and retried your prior step?
[X] Ran brew config and brew doctor and included their output with your issue?

Brew config
HOMEBREW_VERSION: 1.2.3
ORIGIN: https://github.com/Homebrew/brew
HEAD: ed9942fbd1ec4243f0a92ab8f9b2411c8b1fb091
Last commit: 10 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: b1a20488ab08fe888a0deadb584cc2394f5c8608
Core tap last commit: 87 minutes ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_REPOSITORY: /usr/local/Homebrew
HOMEBREW_CELLAR: /usr/local/Cellar
HOMEBREW_BOTTLE_DOMAIN: https://homebrew.bintray.com
CPU: octa-core 64-bit haswell
Homebrew Ruby: 2.3.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby
Clang: 8.1 build 802
Git: 2.13.0 => /usr/local/bin/git
Perl: /usr/bin/perl
Python: /usr/bin/python
Ruby: /usr/bin/ruby => /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby
Java: N/A
macOS: 10.13-x86_64
Xcode: 8.3.3
CLT: <IP_ADDRESS>.1.1497666128
X11: N/A
What are you trying to do
Running brew install will throw an error pertaining to a Xcode issue.
Error: Your Xcode (8.3.3) is too outdated.
Please update to Xcode 9.0 (or delete it).
Xcode can be updated from
  https://developer.apple.com/download/more/

What do you expect to happen
brew install should work normally and not being affected by Xcode.
How to reproduce
Just run the install command for any packages will result in the error. It seemed like Xcode is taking precedence over anything else.

Your Xcode (8.3.3) is too outdated.

It is.

@MikeMcQuaid Is there not workaround to use Xcode 8.3.3 as default?

@ruchern I’m unsure about this, but I’d say the issue lies in your mismatch of the Xcode command-line tools (CLT) with Xcode itself. They have a full major version of difference.

@vitorgalvao It's alright now. I have downloaded Xcode 9 beta 2 from my developer's account and it now works.

@ruchern It's not supported on the macOS beta.

@MikeMcQuaid Yes, apparently macOS High Sierra requires a minimum of Xcode 9 now.

@ruchern I think that (at least) since macOS changed to an yearly update schedule that has been the case. They always present the new macOS and Xcode versions at WWDC.

FWIW Xcode 8.3.3 still works just fine on High Sierra.
The message is misleading, Xcode 8.3.3 is not outdated. If the issue is that there is mismatch between cli tools & the current xcode at xcode-select --print-path, then it should say that instead.

@thepatrick we require that Xcode 9 be used regardless of whether it still works just fine.

@thepatrick Apparently the 8.3.3 on High Sierra is blocking me from installing packages, so I don't think it could just be as simple as that of yours.
If anyone is curious, I was trying to install asciinema.


add: ./node_modules/bin to PATH

HT @pugio

This actually requires reorganizing the code base a bit.

Closed via 580c0b06ee64049ae1f4f23834fee9783ac58c1f