Set a stream web-public, in stream settings

This is a follow-up on #5014, which was for displaying when a stream is web-public.
In the stream settings screen (which you get to e.g. via the "info" icon in the app bar when looking at the stream narrow), we offer a switch to make the stream private or public.
We should add the option to make it web-public. This probably means replacing the boolean switch UI with a UI to choose from a list.
While we're at it, this is probably a good prompt to add the concept of private streams with shared history (vs. private streams with protected history): #2683. So it'll be a choice between four options:

web-public
public
private, shared history
private, protected history

See the corresponding UI in the web app for comparison. Note there's kind of a lot of text accompanying each option -- which is probably necessary, because distinctions like "public" vs "web-public", or "shared history" vs "protected history", are a bit subtle.

Closing as fixed by #5389.


Is this still maintained?

It seems you have the best approach of all the clients.

Yes, this is still supported. I'm not actively adding features but I do respond to issue requests and patch bugs when they are filed


The total length of a DataValidation list cannot exceed 255 characters

When using DataValidation list  for foreign key fields:
[The total length of a DataValidation list cannot exceed 255 characters]
Will be raise : exceeds Excel's limit of 255, use a formula range instead.

Can you give more details?

I have these models:
class AccountTypeSheet(Sheet):

    class Meta:
        exclude=('id','name',)
        Model = AccountType
        title_header = True
        obj_name="account_type"

class AccountSheet(Sheet):

    class Meta:
        exclude=('id',)
        Model = Account
        validation_exclude  = ('account_type',)
        title_header = True

class TestSheet(CombinedSheet):
    account_type = AccountTypeSheet()
    account = AccountSheet()

This command to generate excel:
python manage.py tenant_command generate_sheet --xls account.xls --sheet finance.sheet.TestSheet
When  get the dropdown for account_type  based on the value in the database, if  list of data is more than  255  chars will be raise exception:
[Exception:The total length of a DataValidation list cannot exceed 255 characters]
from stack overflow:
(https://stackoverflow.com/questions/28197219/exceptionthe-total-length-of-a-datavalidation-list-cannot-exceed-255-characters)

That isn't straightforward, as this means we will have a sheet for the data validation ranges. And we need to reference it and try it to hide it somehow.
Lets evaluate this and get back to you.

Sorry for the delay, it was crazy few weeks, We fixed this issue, thanks to @mahmoodnasr, and a new version is released
https://pypi.org/project/django-batch-sheet/


pull request for e2e test at 12/08/2016 07:26:03

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


added some information about linux capabilities into README

I think this information will be useful

Thanks @misterkramer !


Remove switch grids pipeline

Starting to cause issues and cannot be ported to new managers, so it has to be removed before the big switch

Codecov Report

:exclamation: No coverage uploaded for pull request base (area-manager-rework@6f703b1). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@                  Coverage Diff                   @@
##             area-manager-rework     #157   +/-   ##
======================================================
  Coverage                       ?   76.83%
======================================================
  Files                          ?       50
  Lines                          ?     4235
  Branches                       ?        0
======================================================
  Hits                           ?     3254
  Misses                         ?      981
  Partials                       ?        0

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

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


fix(clustering): version compatibility for acme

Summary
fix version compatibility for acme
KAG-615

Please add changelog entry to changelog.md

Please add changelog entry to changelog.md

This fix may not be worth recording to changelog. The original PR missed to add the field into removed_fields.lua. This PR is to fix it.


Add label configuration for release

Some repositories may use an automated tool or bot to merge their pull requests. In this case the bot could be triggered by labeling the pull request instead of merging directly to the base branch. This allows a release_label to be configured which will result in git release adding the label rather than merging to the base branch.
Also made a few bonus updates:

Allow specs to pass on a fork
Update .travis.yml to latest Ruby 2.x
Fix Rubocop warnings
Update gem version to 3.2.0

I need to do a little testing before this is ready for merge, so this is just to collect some early feedback. Will update when this is ready to be merged!

Coverage increased (+0.004%) to 99.609% when pulling 6bb261727908359b48344d52a5c717dcf15a8f80 on f1sherman:add-label-configuration-for-release into d3df54c68bc301fc56401348af7ef9ad8a272a02 on wireframe:master.


Update the terms and privacy URLs in the invite email

Summary
The following PR updates the terms and privacy URLs in the invite email.
Change Type
Mark the type of change your PR introduces:

[x] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 51.92% (-0.005%) from 51.925%
when pulling 85d2868f1730b9f80eff1eab09ee95727b0c9ba7 on fix-urls
into fa80a3b1b3495bb905a49dba2bc85ead2ae9a89b on main.


Fix 1058 runqing

IMPORTANT: By submitting a patch, you agree that your work will be licensed under the license used by the project.
If your pull request does not pass CI, it will not be merged (unless heavily justified).
Description
Implemented new feature that association class will now accept two roleNames on both side of a single end association.
Tests
Added a few JUnit tests for expected result.
Closes #1058

Great. I tested it and it worked.
I am going to merge this PR. However, @runqingz, as a separate PR, could you please add an update to the user manual page, describing the extended syntax. You may want to add an executable example, such as the followng:
class A{
  f;

  public static void main(String [ ] args)
  {
    A anA = new A("theA");
    C aC = new C("TheC");
    B aB = new B(anA, aC);
    System.out.println("The A is " + anA + " and the bs are " + aB + " and the c is " + aC) ; }
}

 associationClass B{
   * A a1;
   * b2 C a2;
 }

class C {
   d;
}


Set the patch version of time

The time::format_description::well_known::Rfc2822 used in this crate
has been added since time version 0.3.6. Therefore, Cargo.toml must set 0.3.6.

Thanks for the contribution!


Cannot get URL of  a 'new-window' from one website.

Electron version:0.36.8
Operating system:Windows 8.1

I found a webview issue. I added an event handler to webview using ES6 like as below.
webview.addEventListener("new-window", (e) => {
  console.log("url: " + e.url);
});

In almost website, I can get proper URL from e, but I cannot get the proper URL from the URL as below.
http://ima.goo.ne.jp/word/69252/イメチェンが裏目に「恐怖！加工人間」?from=ima_rec
You can reproduce by clicking the link on the right side of girl's image.
e.url is same as URL as above.

I think the URL is passed as the second parameter .
see http://electron.atom.io/docs/v0.36.8/api/web-contents/#event-new-window

a little debugging showed the site uses google tag manager, which uses window.open to open links with target=_blank and sets the location.href of the new window later. This can be fixed by providing complete support to location object on BrowserWindowProxy.

I'm merging this to #1865.


python3Packages.absl-py: 0.13.0 -> 0.15.0

Motivation for this change
Update to latest upstream release 0.15.0
Change log: https://github.com/abseil/abseil-py/blob/b188d9080c8e5628bb52a93a04ad930abb1717eb/absl/CHANGELOG.md#0150-2021-10-19
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@fabaff can you rebase?

Will be part of #147426


Utility script to add a reference test.

After forgetting one of the steps to add a ref test so many times, I added a script to do it all for me.

Good utility script; thank you!


Update runner command to remove flash.

With the flash sub-command, the following error is produced.
     Running `espflash flash --monitor target/riscv32imc-esp-espidf/debug/hardware-check`
New version of espflash is available: v2.0.0-rc.3

Error: espflash::connection_failed

  × Error while connecting to device
  ╰─▶ Serial port not found
  help: Ensure that the device is connected and your host recognizes the serial adapter

This updates all of the .cargo/config.toml files to remove the flash sub-command. This make's it work on macOS and Linux without the error.
Closes: https://github.com/esp-rs/espressif-trainings/issues/182

Not needed after updating with cargo install<EMAIL_ADDRESS>--force (Please check that you are running esp flash v2.0 or better if you are having the same issue. Ideally don't update to a pinned version of espflash also.


Fix some issues with taffybar.rc loading

This pull request fixes some issues with loading of taffybar.rc, mostly that it is now loaded after initGUI so it can override (and use) any resources loaded by the system gtkrc files, it also fixes an issue with using gtk_color_scheme, which causes already loaded rc files to be reloaded, which could cause overwriting of resources defined in taffybar.rc. It also prefixes all stylesdefined in taffybar.rc with the "taffybar-" so the style names should be more unique.

Oh, thanks.  I will take a look at this very soon.  I've known that things weren't quite right (especially if you have an XSettings daemon running) for a while, but I never dug into the reasons.  I actually never really understood gtkrc, so this is helpful.

Not sure if this is the reason. But this would probably make users of light gtk themes hate taffybar. It looks great with a dark theme, but light themes look awful.


chore(package): add sideEffects: false for Webpack 4

Fixes #2589.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #2941   +/-   ##
=======================================
  Coverage   99.78%   99.78%
=======================================
  Files         161      161
  Lines        2760     2760
=======================================
  Hits         2754     2754
  Misses          6        6

Continue to review full report at Codecov.

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

Released in<EMAIL_ADDRESS>


services/horizon: make fork of throttled primary dependency

PR Checklist
PR Structure

[x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[x] This PR's title starts with name of package that is most changed in the PR, ex.
services/friendbot

Thoroughness

[ ] ~This PR adds tests for the most critical parts of the new functionality or fixes.~
[ ] ~I've updated any docs (developer docs, .md
files, etc... affected by this change). Take a look in the docs folder for a given service,
like this one.~

Release planning

[ ] ~I've updated the relevant CHANGELOG (here for Horizon) if
needed with deprecations, added features, breaking changes, and DB schema changes.~
[x] I've decided if this PR requires a new major/minor version according to
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.

Summary
Make @bartekn's fork of the throttled dependency the primary dependency for that dependency instead of being just a custom source.
Goal and scope
This is part of the initiative to move to Modules (#1634) and is a small change to simplify our Gopkg.toml/lock files to make that transition simpler.
Using the fork seems to be confusing the go tooling in go1.12 and go1.13rc1, with both behaving a little differently. Since this fork is the only fork of a dependency we use and it is simple package, it is straight forward for us to switch to using the fork fully in name rather than to try and make it work consistently with both versions.
For context, in modules a replace directive is how we tell the go toolchain that we want to use a fork of a module. However, a replace statement only applies when go commands are executed inside this repo as the main module and so importers of our repo won't be using the fork. This doesn't really matter for throttled because we only use it in internal and main modules of horizon, but it's important to be aware of.

In one test I ran on go1.12.9 where this repo was being imported, all the dependencies for the project were imported and the tool got confused and stuck on importing a version of throttled because the commit only existed in the fork. It was trying to get it from the source repo because it was ignoring the replace directive. Go1.13 doesn't attempt to pull all dependencies like go1.12 does so this won't be a problem in the future, but go1.12 will be around for ~7 months from today.

In another test I ran inside just this repo while pulling in all the dependencies locally the go toolchain saw the reference back in the fork in the example_test.go file and then attempted to pull in the source. This results in the project pulling in additional dependencies. This might be a bug, but I haven't been able to clearly reproduce it to open a ticket on the Go project.

In general we've been using this fork long term and the change has never been merged back upstream. Given the divergence I think in principle it's fine if switch to using the full name of @bartekn's fork and treating it as the primary dependency, and that is a smaller effort vs attempting to make this one case we use a fork work with a replace directive. Removing the need for a replace directive keeps our future go.mod file simple, which as newbies to Modules will hopefully mean we will have less problems and complexity to deal with.
Summary of changes

Replace github.com/throttled/throttled as a dependency with github.com/bartekn/throttled so that it is the name of the dependency and not just the source used to retrieve the dependency.
Replace github.com/throttled/throttled in import paths with github.com/bartekn/throttled.
Change the revision of github.com/bartekn/throttled to include an additional commit that @bartekn committed yesterday that removed the only self-referencing import line from an example test that we don't need. This was so that the original throttled package doesn't become a dependency.

Known limitations & issues

This pattern of entirely replacing a package with a fork isn't a pattern we can use in every situation. If we were using a fork of a more complex package with sub-packages those sub-packages would still reference it. This is a pattern we have the luxury of using with this simple package, and if the package was more complex we'd have to find a more complex solution or possibly work with the developers of the go toolchain to identify the precise way forward.

What shouldn't be reviewed
[TODO]

🤦♂ I missed there were other files in @bartekn's fork that still reference throttled/throttled, and due to a typo in a test I ran, I wasn't testing it properly. Will close and reassess.


Avoided repeating stage name when multiple executions are running in parallel

Should fix #329.

Thanks!

No problem! :-)


WIP: enhance LocalAuthoritiesExtractor with appId (from broker binding)

we can not avoid name clashes when two applications provide the same scope e.g. scope... localScopeChecks should not be supported...


ES2015 Classes not highlighting correctly

For some reason VSCode will not highlight the ES2015 class seen on the left in the same way it does in the traditional class on the right. Is this intended? Can I make it highlight in the same way?

We expect somewhat different highlighting in these cases, but the difference should not be that drastic. Can you please provide:

What color theme you are using?
Are you using any extension? Try running code with --disable-extensions to see if this still repos.
Provide the example code for the two files.

Thanks

@synthecypher Please provide the requested information so that we can investigate this

@mjbvz I was using the Base16 Themes extension.
It appears to no longer be a problem, maybe they fixed it.


Do we have an example nginx config somewhere?

Just wondering if someone has a nginx config example... I having a little trouble.
Thanx in advance.

yii2-app-advanced on single domain (Apache, Nginx)

Haha  thank you :)  I'd been using my own doctered config for so long now ... lol Back to original and all is well :)
Thanks again.


License

I am interested in maplite and it is possible that I would make use of the source code, but currently there is no license in this repo, at least I could not find it. Please provide a proper license file.

License file added


[No QA] [TS migration] Migrate 'validateReassureOutput.js', 'createDocsRoutes.js', 'reopenIssueWithComment.js', 'postTestBuildComment.js' and 'isStagingDeployLocked.js' .github files to TypeScript

Details

[TS migration] Migrate 'validateReassureOutput.js', 'createDocsRoutes.js', 'reopenIssueWithComment.js', 'postTestBuildComment.js' and 'isStagingDeployLocked.js' .github files to TypeScript
Fixed Issues

$ https://github.com/Expensify/App/issues/25365
$ https://github.com/Expensify/App/issues/25366
$ https://github.com/Expensify/App/issues/25367
$ https://github.com/Expensify/App/issues/25368
$ https://github.com/Expensify/App/issues/25369
PROPOSAL: N/A
Tests

[x] Verify that no errors appear in the JS console

Offline tests

N/A
QA Steps

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

On hold till GithubUtils PR is merged.

@VickyStash PR has merge conflict.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/youssef-lr in version: 1.4.58-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

This wasn't an emergency, this PR only has changes tied TypeScript and has no effect on the actual product.

🚀 Deployed to production by https://github.com/Beamanator in version: 1.4.58-8 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Updating hosts file in linked/dependent containers on restart

Similar to the line of discussion on https://github.com/docker/docker/issues/6350 I'm wondering if it's possible to have the hosts files inside surviving (non-restarted) containers get updated with the new IP of the restarted container? As it stands right now it appears I have to manually go through and restart containers when those they're linked to get restarted, so as not to break communication?

Yep, I think it could be a feature that could be activated by flag or so.

https://github.com/signalfuse/maestro-ng/issues/154 seems like a more elegant solution. Closing.


Doesn't support nested routes

For example:
[{
  path: '/user/:id', component: User,
  children: [
    {
      // when /user/:id/profile is matched
      path: 'profile', component: UserProfile
    },
    {
      // when /user/:id/posts is matched
      path: 'posts', component: UserPosts
    }
  ]
}]

Support for nested routes is available in 2.1.0. Thanks for your feedback!


unexpected behavior-- .sql files in macros directory not being parsed when parsemacro is set to true

unexpected behavior-- .sql files in macros directory not being parsed when parsemacro is set to true. after some lightweight testing it appears that this conditional:
sql_files = [i[5:] for i in paths if '.sql' in i]

is filtering out .sql files in the macros dir (but it does not filter out .sql files in the model director). a bit counterintuitive, merits further investigation.

note to self: make sure these changes are applied to the discovery util as well. other note to self: package up a new release when PR is merged to address this


Update blog post about Sentinel

What is the purpose of the change
Update blog post about Sentinel (rearrange and refine some content in CN version).

LGTM, thanks for the pull request!


Gamut fitting algorithm when lch chroma is negative seems off

So, let me start off by mentioning that I realize chorma of < 0 is not really a normal use case and I was more experimenting with corner cases in the algorithm. My interest was that I was implementing the Lch Chroma gamut fitting that you guys describe, and I was comparing against your output as a sanity check.
What I noticed is this:

What this shows is that when we fit an Lch value which has a negative chroma, the color doesn't quite come out as expected. But if we convert the Lch color to Lab and back to Lch, then we can fit it and get a more expected result.
Now, I implemented the deltaE2000 directly from http://www2.ece.rochester.edu/~gsharma/ciede2000/ciede2000noteCRNA.pdf, so I was very literal in my translation to code. With that said, I noticed one difference from what I'm doing than from what you guys are doing. That is specifically getting the initial chroma values by calculating it from a and b.
    lab1 = color.convert("lab")
    lab2 = color2.convert("lab")

    l1, a1, b1 = lab1._channels
    c1 = math.sqrt(math.pow(a1, 2) + math.pow(b1, 2))
    l2, a2, b2 = lab2._channels
    c2 = math.sqrt(math.pow(a2, 2) + math.pow(b2, 2))

You guys seem to just take the chroma from the already calculated Lch value, which I am assuming is coming out as negative. I suspect this may be the issue unless there is some kind of handling that occurs before we get here. I tried to change to what you guys were doing only to run into failures, so I imagine there may be something else occurring before you get here. Since my library isn't carrying around all the color spaces already, I have to explicitly convert to a color space, so I imagine that
may also have forced me not to run into this issue.
	let [L1, a1, b1] = color.lab;
	let C1 = color.chroma;
	let [L2, a2, b2] = sample.lab;
	let C2 = sample.chroma;

I am seeing consistent behavior by calculating the chorma from a and b:
>>> c = colorcss("lch(100% -50 10)")
>>> c.fit_gamut("srgb")
>>> c.to_string()
'lch(97.977% 9.8831 199.06)'

And when round-tripping, it is the same:
>>> c = colorcss("lch(100% -50 10)")
>>> c1 = c.convert("lab").convert("lch")
>>> c1.fit_gamut("srgb")
>>> c1.to_string()
'lch(97.977% 9.8831 199.06)'

Hopefully, this helps. I am no color expert, but I wanted to report this to you guys in case it was a bug 🙂. Or maybe this is completely expected or is undefined behavior.

A negative chroma is an error case, right? It sounds like we should just be clamping that to 0 before using it.

The current library seems to consider both Lab and Lch as always "in gamut". But I agree that it would seem that this should be clamped, at least when outputting a final value, I'm not as sure when dealing with conversion as this is not my area of expertise.

Indeed, I'd classify this as a bug.

OK so now I am clamping any negative Chroma to zero. I also check for NaN Hue and arbitrarily set it to zero, which is probably fine since in general the Chroma will be near-zero in that case.
to: {
		lab (LCH) {
			// Convert from polar form
			let [Lightness, Chroma, Hue] = LCH;
			// Clamp any negative Chroma
			if (Chroma < 0) {
				Chroma = 0;
			};
			// Deal with NaN Hue
			if (isNaN(Hue)) {
				Hue = 0;
			}
			return [
				Lightness, // L is still L
				Chroma * Math.cos(Hue * Math.PI / 180), // a
				Chroma * Math.sin(Hue * Math.PI / 180)  // b
			];
		}
	},

Now, I implemented the deltaE2000 directly from http://www2.ece.rochester.edu/~gsharma/ciede2000/ciede2000noteCRNA.pdf, so I was very literal in my translation to code.

Excellent. I did too. Many online calculators git this wrong in small ways. I also put all the Sharma dataset into the color.js deltaE tests as another sanity check.

This helps when When converting from Lch to Lab, but are we still going to hit a deltaE issue as the Chroma is grabbed directly from Lch without any adjustment? Or is this resolved somehow before we get to this point? It is unclear looking at the code.
	let [L1, a1, b1] = color.lab;
	let C1 = color.chroma;
	let [L2, a2, b2] = sample.lab;
	let C2 = sample.chroma;

You guys seem to just take the chroma from the already calculated Lch value, which I am assuming is coming out as negative.

I don't see how a calculated Chroma could be negative
return [
	L, // L is still L
	Math.sqrt(a ** 2 + b ** 2), // Chroma
	angles.constrain(hue) // Hue, in degrees [0 to 360)
	];

but user-entered coordinates could be.

I'm unsure whether to try and trap user input on LCH, or to do the check again in deltaE2000

Calculated probably couldn't be, but in the case I originally posted, chroma was user defined.
Not sure if the user input should always be clammped as zero chroma or not as it doesn't seem to be helpful. I'm not sure preserving the negative helps with translation to other colors either. At the very least, if deltaE2000 calculated chroma from a and b, you'd at least get a sane positive chroma, even if the value may be a little off as zero should probably be used. At least that is my impression.
I could be wrong though, this is just my amateur analysis 🙁 .

In general,avoiding clamping slightly-out-of-range values is a good thing. For example, CIE XYZ is defined to be all-positive, so implementations often did clamping to non-negative. But then it turn out if you measure colors under one illuminant and then chromatically adapt to a different one you can end up with small negative values. So te current recommendation is not to clamp, to avoid cumulative round-trip errors.

Okay, so it sounds like a negative chroma input by the user is to be accepted as an undefined case. Translation via a roundtrip conversion through Lab will correct it. DeltaE2000 will continue to assume chroma is correct and use it instead of recalculating it from the current Lab space?

DeltaE2000 will continue to assume chroma is correct and use it instead of recalculating it from the current Lab space?

No, I think it should correct it too.

No, I think it should correct it too.

Okay, that makes sense. Was just making sure I was following the direction. I think in the past month I've learned more about colors than I planned to. It is a surprisingly complex area 🙂.

fix negative Chroma in LCH to Lab
fix negative Chroma in LCH-based distance metrics

. It is a surprisingly complex area

💯


Preimage resistance of cryptographic hash funtions

Overview
This pull request enriches the bitcoin-utils package by introducing a comprehensive suite of cryptographic hash functions and utility scripts designed to assess and demonstrate the robustness of these functions.
Modifications
hashfunctions.py
Implemented Functions:
hash_sha256(b: bytes) -> bytes: Computes SHA-256 hash.
hash_ripemd160(b: bytes) -> bytes: Computes RIPEMD-160 hash.
hash_sha1(b: bytes) -> bytes: Computes SHA-1 hash.
calculate_hash_rate(hash_function, duration_seconds=1): Measures the computation rate for any given hash function.
estimate_computers_needed(hash_rate_per_computer, years_to_break): Estimates the computational resources needed for breaking a hash via a preimage attack in specified years.
security_hash_functions.py
Purpose: Demonstrates the use of hash functions to calculate hash rates and estimate the number of computers required to theoretically perform a preimage attack on SHA-256 within one year.
Rationale
This update aims to provide tools for understanding and evaluating the security implications of using different cryptographic hash functions in blockchain technologies. It also serves as an educational resource for learning about the computational demands and security strength of these cryptographic functions.
Invitation for Collaboration
Feedback and suggestions on these implementations are highly encouraged, especially in areas of enhancing security features and educational clarity. Contributions for further cryptographic explorations are also welcome.

Hi @Hugongra
This code is independent of the library. You create new hashing functions (even those not needed by Bitcoin) although they also exist in the library. The measurements are also outside the scope of this project.


Could not find com.github.RoaringBitmap:RoaringBitmap:0.9.9

Gradle
implementation 'ru.yandex.clickhouse:clickhouse-jdbc:0.3.0'
A problem occurred configuring root project 'project'.
> Could not resolve all files for configuration ':runtimeClasspath'.
   > Could not find com.github.RoaringBitmap:RoaringBitmap:0.9.9.
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/com/github/RoaringBitmap/RoaringBitmap/0.9.9/RoaringBitmap-0.9.9.pom
     If the artifact you are trying to retrieve can be found in the repository but without metadata in 'Maven POM' format, you need to adjust the 'metadataSources { ... }' of the repository declaration.
     Required by:
         project : > ru.yandex.clickhouse:clickhouse-jdbc:0.3.0

Possible solution:
 - Declare repository providing the artifact, see the documentation at https://docs.gradle.org/current/userguide/declaring_repositories.html

Could you add repository https://jitpack.io? They didn't push latest artifact to maven central. Alternatively, you can use shaded jar and exclude all its dependencies.

I added an exclusion(I don't use bitmaps in jdbc). But I don't think it is good idea to publish artifact to storage without dependency.

Right. Maybe we should make RoaringBitmap dependency as optional("provided" in maven).

RoaringBitmap is now an optional dependency. It's downgraded to 0.9.3 so that we can use maven central in order to compile, and it's no longer included in the shaded jar.


Add Awesome-Ethereum

Please read the instructions for creating a new list, contributing guidelines and the awesome manifest.
Especially this part:

Wait at least a couple of weeks after creating a list before submitting to give it a chance to mature.

Ping me here in a few weeks and I'll reopen ;)


java.lang.NoClassDefFoundError: openvr/EVREye

Hi
(Sorry for the x-post)
I've been trying to get this project running under Windows. I was able to build the application after adding the Kotlin compilers and Eclipse kotlin support. However, when I try to run the project, I get the exception 'java.lang.NoClassDefFoundError: openvr/EVREye'
I'm using the following batch file to run the program:
@echo off

set CLASSPATH=build\libs\jogl-hello-vr.jar;jogl-hello-vr\lib\gluegen-rt.jar;jogl-hello-vr\lib\jogl-all.jar;jogl-hello-vr\lib\openvr.jar;jogl-hello-vr\lib\glm.jar;jogl-hello-vr\lib\jna-4.2.2.jar;jogl-hello-vr\lib\streamex-0.6.2-SNAPSHOT.jar

kotlin -classpath %CLASSPATH% hellovr.App

Can you see any mistakes in what I am doing? Any help in getting this running would be much appreciated.
Cheers

I must admit I seem to remember when I got this working before I may have had some hacky patching possibly even inside the source somewhere to get it to find the native library properly, hopefully someone else'll weigh in, but I might try to look back at it for you.
It might be as simple as you needing to add a -Djava.library.path argument.  It's been a little while since I've done any Java (never even glanced at kotlin) and I'm a little foggy on remembering how this project dealt with its native dependencies but I remember it needing a little bit of hacking to work for me in Eclipse.

Could you try with Idea?

Cheers guys. I think I see the class file in the openvr jar, just not able to get the JVM to pick it up. I'll fiddle around with the class paths a bit more as you suggested and see if I can get it working.
I'll try out Idea too.

Gradle was downloading jar files for openvr, glm and uno-sdk from maven repos synced with the @elect86's github account and compiling against them, and it looks like these did not match the files in the libs directory (which I was trying to run against). I made some progress after using the jar files downloaded by gradle, but after trying out Idea as suggested by @elect86, it just worked!
If I get some time, I might try an update the example to work with the updated libs and submit a merge request.
Cheers!

Nice to hear it worked
Pull requests are welcome :)


Fix the conversion from filetime to ns

I might be wrong, but the current code does not seem to line up with the comment on filetimes. Hopefully this is the correct fix

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see CONTRIBUTING.md for more information.

Turns out my initial guess here was wrong. The code is actually functioning correctly, but the naming of many of the variables is suspect. By dividing by 10 (the original code), a conversion was being done from 100ns buckets to microseconds, not back to nanoseconds. A number of variables that were named ns_ were actually storing quantities in microseconds.
This PR no longer affects functionality, but solves some naming issues with these variables

This begs the question, since Timespec uses nanosecond precision, whether throwing out the 100ns precision is correct.

Aha! I looked into this a bit as well and I thought the number of 0s on the end of that constant looked suspicious... Thanks for this!

I'd also be fine actually using the ns precision if possible :)


Add credentials for ECS

Fixes #8559.
Description
Allow Druid to fetch credentials from within an ECS container on AWS.
I added an instance of EC2ContainerCredentialsProviderWrapper which seems to be the fully baked way to get credentials on ECS with the SDK. I first tried adding new ContainerCredentialsProvider() but saw that constructor was deprecated. Despite EC2 in the name, I believe this should work for ECS Fargate as well. I noticed a similar change in the Hadoop project.
I also noticed that the line below (new InstanceProfileCredentialsProvider()) was showing a deprecation warning in my editor. The docs say that this constructor had been deprecated in favor of the .getInstance method on the same class.

This PR has:

[x] been self-reviewed.
[x] added documentation for new or modified features or behaviors.
[ ] ~added unit tests or modified existing tests to cover new code paths~.
[ ] ~added integration tests~.
[ ] been tested in a test Druid cluster.

I can test this change in a development Druid cluster. I noticed that there are no unit tests for this class, but unit tests don't seem like a good fit. I'd be happy to add onto any integration tests that I may have missed.

Key changed/added classes in this PR

AWSCredentialsUtils

@vogievetsky, wondering if you could provide some guidance on any additional testing or documentation changes that would be needed here.

Hi @mitchlloyd, thanks for the contribution!
It looks like this just passes through to the instance profile credentials, so it might be ok to not have to update any documentation since this is already mentioned in the s3 aws authentication documentation. I think that doc would probably be the place to update though if you feel we should elaborate or if any of the details from the EC2ContainerCredentialsProviderWrapper docs seem useful to include in our documentation.

I would definitely suggest updating the s3.md doc. There should be a new entry added between "Profile information" and "Instance profile information". The description could be something like,

Type: EC2 container credentials
Details: Based on environment variables AWS_CONTAINER_CREDENTIALS_RELATIVE_URI or AWS_CONTAINER_CREDENTIALS_FULL_URI as described in the EC2ContainerCredentialsProviderWrapper documentation.

I don't think tests are needed for this patch; they would be nice, but we don't currently have a good way to test the provider chain, and this patch doesn't need to be the place to add that testing ability.
I am good to merge this patch after the doc update I mentioned above. Thanks for the contribution @mitchlloyd!

I updated the documentation in s3.md doc. Note that I changed the suggested wording slightly. It seems that EC2ContainerCredentials is a misleading name. The JavaScript SDK has a better name for this: ECSCredentials. Really this is all about using ECS and this authentication method should work with ECS configured with EC2 instances and ECS configured with Fargate instances.
With that in mind I made sure to mention ECS.

Ah, it looks like this PR is failing the spellcheck which isn't so smart unfortunately :cry:, https://travis-ci.org/apache/incubator-druid/jobs/596731393#L274
You can add entries for the things it is flagging to this file https://github.com/apache/incubator-druid/blob/master/website/.spelling

Finished a test. Before the patch I see these logs on ECS:
2019-10-11T19:47:27,671 DEBUG [KinesisSupervisor-spade-kinesis] com.amazonaws.auth.AWSCredentialsProviderChain - Unable to load credentials from org.apache.druid.common.aws.ConfigDrivenAwsCredentialsConfigProvider@278b2493: Unable to load AWS credentials from druid AWSCredentialsConfig
2019-10-11T19:47:27,673 DEBUG [KinesisSupervisor-spade-kinesis] com.amazonaws.auth.AWSCredentialsProviderChain - Unable to load credentials from org.apache.druid.common.aws.LazyFileSessionCredentialsProvider@3615d336: cannot refresh AWS credentials
2019-10-11T19:47:27,673 DEBUG [KinesisSupervisor-spade-kinesis] com.amazonaws.auth.AWSCredentialsProviderChain - Unable to load credentials from EnvironmentVariableCredentialsProvider: Unable to load AWS credentials from environment variables (AWS_ACCESS_KEY_ID (or AWS_ACCESS_KEY) and AWS_SECRET_KEY (or AWS_SECRET_ACCESS_KEY))
2019-10-11T19:47:27,673 DEBUG [KinesisSupervisor-spade-kinesis] com.amazonaws.auth.AWSCredentialsProviderChain - Unable to load credentials from SystemPropertiesCredentialsProvider: Unable to load AWS credentials from Java system properties (aws.accessKeyId and aws.secretKey)
2019-10-11T19:47:27,674 DEBUG [KinesisSupervisor-spade-kinesis] com.amazonaws.auth.AWSCredentialsProviderChain - Unable to load credentials from com.amazonaws.auth.profile.ProfileCredentialsProvider@749c1076: profile file cannot be null
2019-10-11T19:47:29,684 DEBUG [KinesisSupervisor-spade-kinesis] com.amazonaws.auth.AWSCredentialsProviderChain - Unable to load credentials from com.amazonaws.auth.InstanceProfileCredentialsProvider@f21c0fd: Unable to load credentials from service endpoint
java.lang.RuntimeException: com.amazonaws.SdkClientException: Unable to load AWS credentials from any provider in the chain

No tasks can start.
After the patch I see
2019-10-11T21:00:13,848 DEBUG [task-runner-0-priority-0] com.amazonaws.auth.AWSCredentialsProviderChain - Unable to load credentials from org.apache.druid.common.aws.ConfigDrivenAwsCredentialsConfigProvider@673ec5ca: Unable to load AWS credentials from druid AWSCredentialsConfig
2019-10-11T21:00:13,850 DEBUG [task-runner-0-priority-0] com.amazonaws.auth.AWSCredentialsProviderChain - Unable to load credentials from org.apache.druid.common.aws.LazyFileSessionCredentialsProvider@1c2e9c96: cannot refresh AWS credentials
2019-10-11T21:00:13,850 DEBUG [task-runner-0-priority-0] com.amazonaws.auth.AWSCredentialsProviderChain - Unable to load credentials from EnvironmentVariableCredentialsProvider: Unable to load AWS credentials from environment variables (AWS_ACCESS_KEY_ID (or AWS_ACCESS_KEY) and AWS_SECRET_KEY (or AWS_SECRET_ACCESS_KEY))
2019-10-11T21:00:13,850 DEBUG [task-runner-0-priority-0] com.amazonaws.auth.AWSCredentialsProviderChain - Unable to load credentials from SystemPropertiesCredentialsProvider: Unable to load AWS credentials from Java system properties (aws.accessKeyId and aws.secretKey)
2019-10-11T21:00:13,852 DEBUG [task-runner-0-priority-0] com.amazonaws.auth.AWSCredentialsProviderChain - Unable to load credentials from com.amazonaws.auth.profile.ProfileCredentialsProvider@505d97d9: profile file cannot be null

And after that tasks successfully run.
I'll update the spelling config.

AFAICT this is a stalled step in the build. Maybe someone with access could just restart that part?

I restarted that stalled test


[Enhancement] Add option to not show "No Completions" message

When writing new functions fuzzy autocomplete still tries to find completions for method names and when it can't it pops up a message saying "No Completions" that gets in the way of what you are trying to write. Perhaps it would be better to follow the xcode default of not showing any message if there are no autocomplete options available.

+1 for this feature, if there are no completions, you should only dismiss the dialog and show nothing.

Agreed, should be consistent with default Xcode behaviour.


Prevent Build failures from being reverted by GitHub

Fixes: #150

Wrong repo.  :facepalm:  Sorry again.


Multi tenancy?

Description of issue
I'd like to run a hosted locust for various different team. To do so, it would be nice if I can have a single master pointing at multiple --host. I could not find how to do so in the documentation.
Expected behavior
I can point locust master to multiple hosts.
Actual behavior
I don't think I can based on the docs.

I don't really understand what you are asking.  Also, this is the issue tracker and is not for general questions or feature requests.


add este/component

Boilerplate for React component written in babeljs with limited dev stack for linting, tests, etc.

What is babeljs?


ios15 flutter web render html not work

Steps to Reproduce

Run flutter create bug.
Update the files as follows: ...
...

Expected results:
Actual results:

Logs

Hi! @WisBingo , I am unable to understand what you are trying to say. Can you please be a little more clear?


Further fixups

The depext is to make the build work again on freshly installed macs, the dune file change is just to make the update from the previous PR behave exactly as before (almost: I kept safe-string out as it is the default now and can create runtime and compiler error when libraries are compiled with mixed safe/unsafe strings in old compilers).

Does this mean people have to install openmp in order to install owl? Do we really want to enforce this dependency (especially most users probably won't enable openmp)? By default, OpenMP is disabled and Owl can certainly run without it. @mseri @jzstark

This was already the case but it breaks the build if your mac doesn’t have openmp (like mine)

Ah, this is a bug then, because it should break the build if the user doesn't have OpenMP installed. @jzstark I think this is due to AEOS which is responsible for tuning OpenMP parameters, even when openmp is disabled, the build process still relies on AEOS to generate a dummy header file to continue. Jianxin, I think you probably need to fix this by having a dummy header file in the place by default, if OpenMP is enable, let AEOS overwrite the default header file to use the best parameters.
Also, if OpenMP is disabled, we should not compile AEOS module at all in the first place to avoid breaking the build process.

Btw I have nothing baout disabling openmp, I nave added the depext because it was the way I made the master branch of owl work on my mac

Yes I see. The AEOS configuration is quite rudimentary. I've changed its dune file recently to make it from a library to executables. I'll take a look at removing its dependency on OpenMP when AEOS is disabled by the dummy file solution. However, since I've tested it on all kinds of containers and still failed to find this issue the last time, do you have any suggestion about how to disable the OpenMP for testing? @mseri

@jzstark dummy header is the cleanest solution AFAIK, because owl needs that header file anyway which should NOT have dependency on AEOS, especially when the user does not want to enable OpenMP. In short, AEOS should not be compiled and run if openmp switch is off.

I agree on the dummy header. We could simply make owl-aeos a depopt: we can use the select function from dune to pick the right header depending on owl-aeos being present or not.

Closing this as we are discussion aeos fix somewhere else.
I am moving the reintroduction of the :standard flags to a separate PR


Menu Doc: "Files", "Search" and "Starred" Missing from the top left

Update to 1.1.8
Open and close application
those icons at the top left disappear.

I’m assuming this is related to the tabs being hidden. You can turn off the hiding by turning off the hide tab bar setting
Get Outlook for iOShttps://aka.ms/o0ukef

From: Scott Larson @.>
Sent: Wednesday, December 21, 2022 9:17:12 PM
To: Make-md/makemd @.>
Cc: Subscribed @.***>
Subject: [Make-md/makemd] Menu Doc: "Files", "Search" and " (Issue #20)
—
Reply to this email directly, view it on GitHubhttps://github.com/Make-md/makemd/issues/20, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAFHKNWLGAD6OQQ5YQKFPATWOO22RANCNFSM6AAAAAATGHG3MA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

The only option I see about tabs is the "Show Title Tab Bar" and that is enabled...

You need to goto the make.Md settings
Get Outlook for iOShttps://aka.ms/o0ukef

From: Scott Larson @.>
Sent: Wednesday, December 21, 2022 9:26:23 PM
To: Make-md/makemd @.>
Cc: JP Cen @.>; Comment @.>
Subject: Re: [Make-md/makemd] Menu Doc: "Files", "Search" and "Starred" Missing from the top left (Issue #20)
The only option I see about tabs is the "Show Title Tab Bar" and that is enabled...
—
Reply to this email directly, view it on GitHubhttps://github.com/Make-md/makemd/issues/20#issuecomment-1362314384, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAFHKNRAHHW3HJGBICEYH53WOO347ANCNFSM6AAAAAATGHG3MA.
You are receiving this because you commented.Message ID: @.***>

Ahh shoot. I found it, thanks.

Thanks, our documentation is still in development as we are adding more features. Currently it’s all in our discord. We will make it available on the web once its ready.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Scott Larson @.>
Sent: Wednesday, December 21, 2022 9:28:35 PM
To: Make-md/makemd @.>
Cc: JP Cen @.>; Comment @.>
Subject: Re: [Make-md/makemd] Menu Doc: "Files", "Search" and "Starred" Missing from the top left (Issue #20)
Its "Show Sidebar Tabs" btw
—
Reply to this email directly, view it on GitHubhttps://github.com/Make-md/makemd/issues/20#issuecomment-1362315422, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAFHKNTH7P6TZ53U7WDBEG3WOO4FHANCNFSM6AAAAAATGHG3MA.
You are receiving this because you commented.Message ID: @.***>

Sounds good. Awesome plug-in btw. Im finally able to sort the way I want to.

Thanks!
Get Outlook for iOShttps://aka.ms/o0ukef

From: Scott Larson @.>
Sent: Wednesday, December 21, 2022 9:31:48 PM
To: Make-md/makemd @.>
Cc: JP Cen @.>; Comment @.>
Subject: Re: [Make-md/makemd] Menu Doc: "Files", "Search" and "Starred" Missing from the top left (Issue #20)
Sounds good. Awesome plug-in btw. Im finally able to sort the way I want to.
—
Reply to this email directly, view it on GitHubhttps://github.com/Make-md/makemd/issues/20#issuecomment-1362317929, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAFHKNVMND3ZZG3DIXQ67I3WOO4RJANCNFSM6AAAAAATGHG3MA.
You are receiving this because you commented.Message ID: @.***>


Site positioning problem

Hello,
I'm trying to draw ground reaction forces using site cylinders organized in a body like so:
XML file:
<default class='force_marker_size'>
    <site size="0.005 0.1"/>
</default>
.
.
.

<body name="force_LF" pos="0 0 0">
    <site name="force_LF_x" type="cylinder" rgba="1 0 0 1" euler="0 1.57 0" class='force_marker_size'/>
    <site name="force_LF_y" type="cylinder" rgba="0 1 0 1" euler="0 0 -1.57" class='force_marker_size'/>
    <site name="force_LF_z" type="cylinder" rgba="0 0 1 1" euler="0.0 0 0" class='force_marker_size'/>
</body>

C code:
    int id = mj_name2id(m, mjOBJ_SITE,"force_LF_x");
    m->site_size[3*id+1] = force(0)/20.0f;     //change size (length)
    m->site_pos[3*id+0] = force(0)/20.0f;     //reposition it in the x axis (along the cylinder)

    id = mj_name2id(m, mjOBJ_SITE,"force_LF_y");
    m->site_size[3*id+1] = force(1)/20.0f;     //change size (length)
    m->site_pos[3*id+1] = force(1)/20.0f;    //reposition it in the y axis (along the cylinder)

    id = mj_name2id(m, mjOBJ_SITE,"force_LF_z");
    m->site_size[3*id+1] = force(2)/20.0f;     //change size (length)
    m->site_pos[3*id+2] = force(2)/20.0f;    //reposition it in the z axis (along the cylinder)

because of the fact I cannot change the cylinder length during runtime (like with the XML fromto property), I just scale it with m->site_size[] property. Also, the cylinders are resized automatically on both ends, which means, whenever I want to draw a longer cylinder, I also have to reposition it, by the same value it was resized. I have found a problem with repositioning sites that have the euler property missing or filled with zeros in the XML file. Basically, the force_LF_z cylinder can be resized by cannot be repositioned without applying rotation in the euler property in the XML file. So simply saying:
This does not work (repositioning with m->site_pos[] property doesn't work):
<site name="force_LF_z" type="cylinder" rgba="0 0 1 1" euler="0.0 0 0" class='force_marker_size'/>
whereas this works as expected:
<site name="force_LF_z" type="cylinder" rgba="0 0 1 1" euler="0.000001 0 0" class='force_marker_size'/>
You can see on the GIF below how the Z-axis component behaves. Basically, X and Y are correct, but the Z component can be only resized, thus it goes in both directions.

After setting the euler property rotation to a tiny rotation in the XML file the problem is gone. It's not a big issue for me, but maybe you'd like to fix it (in case its really a bug, not my misunderstanding of basic concepts :) )
Best Regards,
Piotr Wasilewski

Hi,
Could you please take a step back and explain why are you not using MuJoCo's built in contact force visualisation?
In simulate the relevant keys are 'C', 'F' and 'P'.
All visualisation options are available in the GUI on the right and keyboard shortcuts can be seen by right-clicking in the GUI.

Hello,
sorry, I forgot to explain the reason behind it - I'm doing it to check if my calculated forces (from motor torques using the jacobian matrix) actually match the ones calculated by MuJoCo. I'm going to use proprioceptive force sensing and this is my way of validating the jacobian matrix and other related calculations. This is why I need to dynamically change the cylinder lengths, not in the XML file.

You did not answer my question.
I did not ask why you want to visualise forces.
I asked: why are you not using the built-in force visualisation?

I'm actually using the MuJoCo generated forces, I just turned their visualization off in the GIF so you could see the cylinders better. I hope this is what you meant?
This is how it looks with the force visualization (simulation.c F key equivalent)

Is there a way to draw these forces of user-defined magnitude? I thought they are like a built-in non-editable feature.

Yes. You can change the width, length and colour of MuJoCo's built in forces.

Alright, but can I use the visual/map/force property to set an arbitrary magnitude that won't be affected by the MuJoCo itself? From the visual/map/force description I understand its only a scaling factor:
"This attributes controls the visualization of both contact forces and perturbation forces. The length of the rendered force vector equals the force magnitude multiplied by the value of this attribute and divided by the mean body mass for the model (see statistic element below)."
I'd like to have a visual indicator of my own force quantity not affected by the simulation engine at all.

Ah ok! You want to draw your own externally calculated things in the 3D scene... this was unclear.
This is done by directly adding visual geoms to the mjvScene. No need to touch the XML or mjModel, it is unrelated the MuJoCo physics.
See if you can figure out how to do it, write here if you get stuck, we'll help.
Apologies that the C API is not super well documented, but everything you need is exposed. Read this chapter, the mjvisualize.h header, and the relevant mjv_ functions.

Yes, that's my intention, sorry if I was unclear, I probably got fixed on my idea of representing data..
Thank you for the suggestion, I tried it and it works as expected :) I had some initial struggle with determining the order of operations so if anyone was interested in doing the same thing here you have a small example (based on mr. Emo's comment here) :
This is the part of the code where I add a custom geom (an arrow):
`        mjv_updateScene(m, d, &opt, &pert, &cam, mjCAT_ALL, &scn);
    mjvGeom* geomtest = scn.geoms + scn.ngeom++;

    mjv_initGeom(geomtest, mjGEOM_ARROW, NULL,NULL, NULL, NULL);

    geomtest->size[0] = 0.05;
    geomtest->size[1] = 0.05;
    geomtest->size[2] = 0.5;
    geomtest->pos[0] = 1;
    geomtest->pos[1] = 1;
    geomtest->pos[2] = 0;

    mjr_render(viewport, &scn, &con);`

I'd be grateful if you could tell me if I'm doing it right.
In the end, I'd like to ask you about the mjv_addGeoms function - I'm having a hard time guessing what it does based on the description (its only mentioned twice in the docs). How does it add a geom to the existing mjvscene?

Hi,
My team and I are trying to use mujoco to simulate a robotic system which has been taught through demonstration learning, and we would like to show the clients the variance of this gaussian process.
We decided to do this by generating a custom mesh instead of a geometry predefined in mujoco.
would this be achievable with the functionality you described above? I was trying to achieve this by adding buffer by hand to the mujoco context, i.e. Adding a skin and reallocating the VBO and the other buffers, but it seems like a very hacky way to do it.
If you have any sugestion it would be appreciated.

Hi @Joaopmoliveira,

Yes, what you want would be achievable this way, if you can do it with primitives (what the OP is about). Primitives might be a very good idea, depending on the data visualised.
It is also possible to do it with meshes (rather than skins), but the flow is different. You would change the mesh shape in mjModel.mesh_vert (definition) and then call mjr_uploadMesh (declaration, implementation). The integers (e.g. number of vertices) should stay fixed at runtime, but you can change the vertices and alpha channel (mjModel.{geom_rgba or material_rgba}) at runtime.
For skins, which are the only thing that give you the nice spline smoothing, you are right, there is no convenient way to do it right now. We are missing an mjr_uploadSkin function (so you would edit the floating point arrays in mjModel.skin_xxx and call this function), though it would be straightforward to add. Sounds like maybe you've already written it :sweat_smile:? Feel free to submit a PR or a gist of what you've done, if you think it could be useful.

If you wish to follow up, please do it in a new issue for visibility. Cheers.

Kindly tell me how to get ground reaction forces and its location on the say for foot of robot

@Krishnendu1984
Relevant links:

Contact data for extracting contact information.
Function to get the value of contact forces:
void mj_contactForce(const mjModel* m, const mjData* d, int id, mjtNum[6] result)
id  is the contact ID.

Now you may want to know the bodies corresponding to this contact id.
You can get geometries in contact by checking:
int geom1_id = d->contact[id].geom1 and
int geom2_id = d->contact[id].geom2
Now, to know the bodies to which these geometries belong:
int body1_id = m->geom_bodyid[geom1_id] and similarly for geom2.
You may further use mj_id2name to check whether it is the body you were looking for. (Pass mjOBJ_BODY in place of int type).
You can loop the above code for contact id from 0<= id < d->ncon to search for the required pair of contact.
d->ncon gives the number of active contacts at the moment.
You may search "geom_bodyid" in mjModel)
You may want to read more explanation on why to use mj_contactForce() here.

Ok thats the force but its location or coordinates how to get?


Add cross compilation example

Add a new examples directory to be used for sharing example code & projects linked from blog posts. Also add a small cross-compilation example for an upcoming blog post.

LGTM!


[oadp-1.4] fix: restic removal message

Why the changes were made
cherry picked from commit 542204474e283e519b203b52695af6ac8b0e347c : PR https://github.com/openshift/oadp-operator/pull/1412
How to test the changes made
Follow instructions from parent PR.

/lgtm


ttl.tensor.reduce needs to be run twice to produce correct output

Running the following line once produces a tensor with incorrect values in some tiles:
ttl_output_tensor = ttl.tensor.reduce(ttl_input_tensor, ttl.tensor.ReduceOpMath.SUM, reduce_op_dim, 1 / input_shape[-1])

Re-running it right after the second time produces the correct result

Running the following line once produces a tensor with incorrect values in some tiles:
ttl_output_tensor = ttl.tensor.reduce(ttl_input_tensor, ttl.tensor.ReduceOpMath.SUM, reduce_op_dim, 1 / input_shape[-1])
Re-running it right after the second time produces the correct result

Is this for any reduce dim or a specific one?

Is this for any reduce dim or a specific one?

It happens for both H and W dims. I haven't tried HW

@jliangTT , we believe this to be very high priority as it could impact all models.

@umadevimcw , thanks for assigning @VirdhatchaniKN. We probably need to fast track this as this has been opened for a while.

Hi @tt-aho , @arakhmati , @eyonland , @jliangTT
I ran the test file tests/ttnn/unit_tests/operations/test_mean.py to work on the error, and as @arakhmati  mentioned, the reduce op needs to be run twice to get the correct result. But this assertion error is specific to dim -2 (height) only. Width seems to work fine.

We tried implementing mean in TTDNN, so that we can export it to TTNN and update the file, but we faced issues with the result here (Assertion error).
On debugging , It was found that reduce result did not match with the expected result. We implemented using reduce, sum, mean_hw , but we could still see no change.

I have discussed in detail about the code, and PCC value for each method for the same formula (mean = total/dimension) in this document - Link

@arakhmati @eyonland Any inputs on this to proceed further

@arakhmati @eyonland
While using reduce op for mean calculation, the scaler value being passed is calculated with respect to the dimension being reduced.
the scaler value for mean operation is calculated  as  1 / size_of_dim_to_be_reduced
ex., for a tensor (1 , 2, 32 , 64), the scaler for different dimensions
dim= -1 , scaler = 1 / input_shape[-1] = 1/64
dim= -2 , scaler = 1 / input_shape[-2] = 1/32
dim= (-1, -2), scaler = 1 /(  input_shape[-1] * input_shape[-2]) = 1 / (32 * 64)
When testing with above scaler values for the different cases, the second reduce operation was not necessary
From this observation, the fix has been made in #7965


[d3d9] Pico Park: Classic Edition (Steam id 461040) renders white screen only on some machines

That is not universally reproducible, e. g, I could reproduce it on Deck and my AMD desktop but not on Nvidia (while other people were seeing that on Nvidia too).
The issue is not there with wined3d (but running that with wined3d hits an unrelated bug which I have fixed only locally so far).
I didn't reproduce the issue on the same AMD desktop when running with DXVK on Windows, although recorded apitrace (from native Windows d3d9) reproduces the issue when replayed on Linux with dxvk (attaching the apitrace here just in case).
The game is using FFP only (at least at start) and in rather simple way (e. g., no lighting, vertex blending or else trickery). The issue seems to be in the world / projection matrix multiplication precision in ffp shader. I first proved that by hacking the thing in the following way:

provide identity matrices to ffp shader;
perform multiplication on the CPU in DrawPrimitiveUP (the only draw functions called at start are DrawPrimitiveUP with 2 triangles).
This way it renders fine. The culprit seems to be in Z coordinate which ends up being exactly 0 when multiplying on the CPU (while that is achieved with non-orthogonal matrices and involves nonzero multiplication and addition to get that final zero). I think in the shader it gets slightly negative (or maybe even just -0.0f??) and hits clipping.

That is clipping, not depth or other test which is failing (all those tests may be hack-disabled with the same result).
I am attaching a proof of concept hack which lets it render (the hack does depth clamping insted of clipping).
pico_park.zip
poc.txt

Did some testing and it seems that depth clip is unconditionally enabled on native D3D9, so I guess the only solution is to actually do the mutliplication on the CPU side using a very specific instruction sequence? How exactly did you do the multiplication?
It's rather absurd that games are relying on this.

Fixed in above commit.

@doitsujin @K0bin Is this one that we could get in the 1.10.x branch so that it can be fixed in Proton-stable?

Already done.
#2934

@K0bin Sweet!!! Thank you so much :)


Swapping workspaces between monitors with one workspace having a fullscreen window causes status bar display problem

I'm not sure if this is related to #2077 or not so I'm just opening a separate issue.
Steps to reproduce:
On a setup with two monitors and waybar displayed on both monitors make a window fullscreen on one display.
Then, swap the workspaces between monitors using swapactiveworkspaces.
Expected outcome:
The swap happens with the fullscreen window moving to the other monitor.
Noted outcome:
The swap happens, but the status bar remains absent on the monitor that formerly had the fullscreen window. Likewise the status bar is overlayed on top of the fullscreen window on its new display. Swapping back and un-fullscreen'ing the window fixes the issue.

check with 247ff4e60df15c167f0f6b6b2d899aa22101b2a5

Yes that seems to have resolved the issue. Thanks.


replace PosixPath with PurePosixPath (fixes #28)

Hey, thanks for reporting & fix attempt! I feel likeI need to add Windows to CI. Should be straightforward in github actions..
However I tested locally (linux) and it fails to open compressed files for me. As far as I recall, the reason I used PosixPath was because:

couldn't use PurePath/PurePosixPath because I needed to override open behaviour (which is first defined in Path )
couldn't use Path itself because it's sealed

I'll investigate further, but at the moment seems that the quickest portable way would be to dispatch the Path flavor we need based on OS. I gave it a shot in https://github.com/karlicoss/HPI/pull/new/cpath-windows, can you let me know if it helps?
P.S. I also need to figure out how to make this bit configurable.. not sure if you want to use .xz at all?

I added I added a comment in your other PR.

P.S. I also need to figure out how to make this bit configurable.. not sure if you want to use .xz at all?

I'm not sure either. I haven't tried compression yet. Things seem to be working for now.


ci(coveralls): remove Coveralls

It seems to be broken, and I can not be arsed to re-auth it for now

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Shell option has no effect

[X ] I am on the latest Hyper.app version

[ X] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name: Windows 10

Hyper.app version: 1.0.0

Link of a Gist with the contents of your .hyper.js: https://gist.github.com/con-ssc/26cd65a2888cf26953a801e0799a9ae4

Relevent information from devtools (CMD+SHIFT+I on Mac OS, CTRL+SHIFT+I elsewhere): no errors

The issue is reproducible in vanilla Hyper.app: Yes

Issue
Adding shell: "C:\cygwin64\bin\zsh" to the .hyperterm.js config does not open zsh shell at that location on startup.

You need double slashes and an extension on Windows: shell: "C:\\cygwin64\\bin\\zsh.exe 😄

@Specro If you had looked at the gist, you would've seen, there are double slashes ;)

Yeah sorry, I missed that 😄 Also the shell option should be in the config section.

@Specro Ah okay, that was the fault then. Thank you for your help. Would it be possible to have a json schema for the config?


Maximum call stack size exceeded with @bugsnag/plugin-angular in SSR

Following #441, I'm now getting RangeError: Maximum call stack size exceeded during server-side rendering in Angular.

{
  "@bugsnag/js": "^5.1.0",
  "@bugsnag/plugin-angular": "^5.1.0"
}

// core.module.ts

import bugsnag from '@bugsnag/js';
import { BugsnagErrorHandler } from '@bugsnag/plugin-angular';

const bugsnagClient = bugsnag({ ... });

export function errorHandlerFactory() {
  return new BugsnagErrorHandler(bugsnagClient);
}

@NgModule({
  ...
  providers: [
    { provide: ErrorHandler, useFactory: errorHandlerFactory },
    ...
  ]
})
export class CoreModule {}

// core.server.module.ts

import { CoreModule } from<EMAIL_ADDRESS>
@NgModule({
  imports: [
    CoreModule,
    ...
  ]
})
export class CoreServerModule {}

If I'm not mistaken, since @bugsnag/js is universal, it doesn't need to be initialised differently for server-side rendering, does it?

There doesn't appear to be any @bugsnag/node frames in the stacktrace you showed there…?
Our example app runs with SSR (using the command ng serve --aot) which I have confirmed to be working.
The library is universal, yes, and it doesn't need to be initialised differently for SSR. Does your error go away when you remove Bugsnag?

Yeah, if I remove Bugsnag, everything works fine.
The app is served with Express, as explained in Angular's documentation - https://angular.io/guide/universal#step-4-set-up-a-server-to-run-universal-bundles
The error comes up as soon as I start the server with node.

How does your app differ from our example? Can you provide a simple repo where this issue can be reproduced?

@axelboc Which version on nodejs do you use?
I faced with this bug on nodejs version 10.15.0. After downgrading to 8.15.0 everything became ok. Also I need to mention that SSR guide from angular page uses express with nodejs 8 runtime. Maybe this would help you.

Indeed, I'm on Node 10.15.1. Good to know about v8, thanks! I'd still love to get it working on v10, though.

Thanks @oleksmir, I did manage to update to @bugsnag/js on Node 10 without getting the error by initialising Bugsnag only in the browser. Not ideal since I have errors in SSR that are still not reported, but at least I'm up to date.

I've been investigating this issue and cannot reproduce it. I used the project on this page: https://angular.io/guide/universal
Using node v10.15.1, here are the versions of the top-level dependencies that got installed:
<EMAIL_ADDRESS>/Users/bengourley/Development/universal-angular
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>(github:brandonroberts/in-memory-web-api-bazel#50a34d84b627ec88816242dec77603d6dcb9c880)
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
Error reporting works on the server and in the browser, and the node process not crash (unless I throw an error and make it).
Closing this off as it looks like this is no longer an issue. Please feel free to post steps to reproduce if you are still seeing an issue like this and believe Bugsnag to be the cause.


Add a way to exclude page subtype from search index

Is your proposal related to a problem?
In our project, we have a number of page types that exist to be the index page for some other page, e.g. BlogIndex is the parent for BlogPost pages. We don't want BlogIndex offered as a search result; we would rather have our search results link directly to the BlogPost pages. Until now we have been achieving that by defining BlogIndex's as search_fields = [] but in Wagtail 2.16, the check command now tells us Core Page fields missing in search_fields. I can silence that warning globally but I would rather be able to explicitly configure BlogIndex to be excluded from search. That way the check command will still be able to tell me when I have incorrectly configured one of my other page types.
Describe the solution you'd like
I asked the Slack channel if there was an existing option and got:

I don't think there is currently a flag for "don't index this model", but it would make logical sense to add one, alongside the search_auto_update one... https://docs.wagtail.io/en/stable/topics/search/indexing.html#disabling-auto-update-signal-handlers-for-a-model

I am filing this issue to remind myself - or anyone else who wants to give it a try - to look into adding a flag for excluding a page model from the search index.

This is fixed in Wagtail 5.0 by #9821 From the release notes:

Add the ability to disable model indexing by setting search_fields = [] (Daniel Kirkham)

Nice. Good find @cnk


Error types

Replaces failure with thiserror error types

Codecov Report

Merging #79 (78d8e54) into develop (2919eb3) will decrease coverage by 0.31%.
The diff coverage is 14.28%.

@@             Coverage Diff             @@
##           develop      #79      +/-   ##
===========================================
- Coverage    57.90%   57.58%   -0.32%
===========================================
  Files           28       28
  Lines         2632     2650      +18
===========================================
+ Hits          1524     1526       +2
- Misses        1108     1124      +16

Impacted Files
Coverage Δ

src/abci/mod.rs
0.00% <0.00%> (ø)

src/call.rs
5.12% <0.00%> (ø)

src/client.rs
80.51% <0.00%> (ø)

src/collections/map.rs
92.13% <0.00%> (-0.12%)
:arrow_down:

src/contexts/nonce.rs
0.00% <0.00%> (ø)

src/contexts/signer.rs
0.00% <0.00%> (ø)

src/merk/backingstore.rs
0.00% <0.00%> (ø)

src/merk/merkstore.rs
0.00% <0.00%> (ø)

src/merk/proofbuilder.rs
0.00% <0.00%> (ø)

src/query.rs
0.00% <0.00%> (ø)

... and 6 more

Continue to review full report at Codecov.

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


⚠ Shadow Does Streams has degraded performance

In 8c7a8fc, Shadow Does Streams (https://stream.everythingbagel.me) experienced degraded performance:

HTTP code: 200
Response time: 8585 ms

Resolved: Shadow Does Streams performance has improved in 7fcfd06 after 9 minutes.


Enable JSON-LD profiles for response serializations

Resolves: https://jira.duraspace.org/browse/FCREPO-1615

Please do not squash these two commits.


Replace Bower with Library Manager

[x] Removed Bower
[x] Added Library Manager to the project
[x] Configured project to restore client-side libraries upon project build
[x] Restored Library Manager packages

Because all the files are already there. I think we should disable the restore on build for faster build time. There are couple of miner thing need to be correct. I will correct it after merge this pr.
Thank you for the good work

Looks like the readme file need to be changed to VS 2017 15.8 at least in order to use library management.


Improve mission planner script provided to teams.

This only sends telemetry when it changes, which prevents uploading
duplicate data. It prints error messages from failed requests. It prints
the upload rate over the last 10 seconds.
Fixes #146

I've pinged a friend who knows missionplanner to help test it. I'll hold off submitting until I get his feedback. PTAL in the meantime.

Some nits, otherwise LGTM


Add a copyWith() method in Area

For the moment, if we want to change some attributes of an Area, we need to create a new one using same id and configuring the attributes we want to change.
In your example:
dynamic oldId1 = _controller.areas[0].id;
dynamic oldId2 = _controller.areas[1].id;
_controller.areas = [
  Area(id: oldId1, flex: 1, builder: (c, a) => Container()),
  Area(id: oldId2, flex: 2, builder: (c, a) => Container())
];

With a copyWith() method it would have been more elegant and less verbose I think, especially when we just want to change one value such as the flex or min soze for examples:
_controller.areas = [
  _controller.areas[0].copyWith(flex: 1),
  _controller.areas[1].copyWith(flex: 2),
];

Or maybe simple setters would have been easier that having to recreate new areas?

@The4Summers Hello. I've added this functionality to a new package created from this.
https://pub.dev/packages/multi_split_view_next

@The4Summers,
It will be available in version 3.3.0. Thanks.


Google Sheets BatchGet does not take ranges parameter

I wanted to use BatchGet for the google sheets api and it seems the range parameter was omitted making it impossible to use properly.

These clients are in maintenance mode. We don't plan to address this issue.
@pongad for the next generation of clients.


ReportTemplateGenerator generates LaTeX template

Hello. I made a feature that generates LaTeX template files on report submission pages.
I hope you merge this pull request.
If any questions, please notice me on them.
Sincerely,

The button appears as in this image and clicks it to start downloading the LaTeX file.

@mkobayashime Could you check this pull request? Thanks.

@yudukikun5120
Thanks a lot for your work. I'm happy with the feature and this implementation in general and willing to merge them. I've just merged an change to tsconfig.json to resolve failing typecheck here on CI, so could you rebase this branch to the latest main at first?

@mkobayashime Thank you for setting compiler options as to my changes. I made the merge to be up to the fix, so could you perform CI workflows again?

@mkobayashime I rebased the commits, Thank you.

@yudukikun5120
In addition to the comments above, I strongly believe customization of the template should be provided ASAP, as how people want their LaTeX file to be varies a lot (e.g. document class). I think making a new section to input custom template in the options page and save it in chrome.storage.sync is a good solution, could you help implementing it after this PR is merged?

@mkobayashime I truly appreciate your code reviewing. Could you check the fixes I made on them?


Unable to backport after renaming master to main

See e.g. https://github.com/scikit-image/scikit-image/pull/5243#issuecomment-809031809
I must admit I don't know how to look at the relevant logs. 😂

While renaming default branches may still be a problem, I would suggest to close this as the master--main migrations happened, and the bot is very unlikely to cause any more troubles.

I believe this has been addressed.


Add Exported Url Display

References User Story #52
Add a display that shows the exported URL so that it may be seen and copied manually in case it is needed/wanted.

Added url export display
Researched Bootstrap link styling
{t:30}


H5PYDataset incorrect subset handling leads to dataset split contamination

>>> from fuel.datasets import CIFAR10
>>> # One of these should be an error, or at least the get_data call should return 0 examples
>>> valid = CIFAR10(which_sets=('train',), subset=range(50000, 60000))
>>> valid_data = valid.get_data(request=range(0, 10000))
>>> test = CIFAR10(which_sets=('test',))
>>> test_data = test.get_data(request=range(0, 10000))
>>> (test_data[0] == valid_data[0]).all()
True
>>> (test_data[1] == valid_data[1]).all()
True

This is a rather serious bug. I spent this weekend using the test set for model selection when I didn't mean to.

This makes me think that we've over-engineered things to the point that


string-formatting: Example might be wrong

From the bug report dump on Slack

I think the example code is incorrect:
f := 4.3242
fmt.Printf("%.4", f)
// Output: 4.32
If the desired output is 4.32 given 4.3242, and you want rounding, then I think this is correct:
f := 4.3242
fmt.Printf("%.2f", f)
// Output: 4.32
For that matter, I think "f" is a confusing variable name given the Printf formatting operator "f". I would suggest "number".

INCORRECT EXAMPLE IN FLOATING POINT PRECISION
In your example under String track for Go, the example you gave for implementing floating point precision is this:
f := 4.3242
fmt.Printf("%.4", f)
// Output: 4.32
The above won't work because the formatting verb (f) is not stated immediately after the precision figure. Also, the correct precision to arrive at that output will be 2 and not 4. It should be:
f := 4.3242
fmt.Printf("%.2f", f)
// Output: 4.32

@bobtfish Would you have time to address this? You already worked on those concept docs.

Yep, I can fix this.
Thanks for the bug report @SaschaMann and thanks for tagging me @junedev


Entering duty while retainer window is open doesn't autohide the bell icon

open duty finder and queue for duty (unrestricted low level trial for ease of reproduction)
open retainer window while duty finder notice is open, the bell icon to enable/disable the plugin is now visible at the top of the screen
accept the duty, once you're in the bell icon doesn't go away and you have to right click on it to remove it

Given that normally the icon goes away when you close the retainer window, and this only seems to happen with duties, I assume it's a bug.

i also have this issue. has it been addressed yet?


mT5 sentence piece tokenizer

Hey guys,
Thanks for open-sourcing mT5!
Is it maybe possible to provide a link to the sentence piece model file that is used for the pre-trained mT5 checkpoints?
I could not find the file anywhere in the provided checkpoint links.

Hi @patrickvonplaten ,
I think this is what you are looking for:
https://console.cloud.google.com/storage/browser/t5-data/vocabs/mc4.250000.100extra
According to :
https://github.com/google-research/multilingual-t5/blob/master/multilingual_t5/tasks.py

Yes, @agemagician's got it.

@agemagician Hey, by any chance would you know how does the mt5 sentencepiece tokenizer have those extra_ids by default ?
what i need is: how do i too add the extra_ids already  for the tokenizer such that i could keep the extra_ids=0
I've been seeing in the mt5 tokenizer the extra 100 ids needed for the sentinel tokens come already included in the tokenizer.
'gs://t5-data/vocabs/mc4.250000.100extra/sentencepiece.model'
how do i too train my own sentencepiece tokenizer where i could too include the 100extra already in my tokenizer, just like the original one above.
as i am training a variant of mt5 that covers multiple langugaes that the common mt5 does cover. i went on to training a unigram sentencpiece tokenizer with 250000 vocab_size but i tripped into confusion, on how to get the 100 extra_ids similar the the official mt5 tokenizer.

Hey @Adam Roberts. Thanks a ton for your time and helping me out on this issue.
however could you please confirm if this configuration of training the sentencpiece tokenizer for the mt5 is the appropriate option.
or do i need to change any args.
(I just need to exactly train the sentencepiece tokenizer as it was trained for mt5.   ps:  im scared i might do something wrong and irrelavant.)
path=/home/stephen/storage_bucket/corpus_text
spm_train --input=$path/large_corpus.txt, --model_prefix=ciil_50M_mt5_spm_250000_unigram --vocab_size=250000 --character_coverage=0.9995 --model_type=unigram --num_threads=128 --byte_fallback=true --train_extremely_large_corpus=true


[SPARK-6578] [core] Fix thread-safety issue in outbound path of network library.

While the inbound path of a netty pipeline is thread-safe, the outbound
path is not. That means that multiple threads can compete to write messages
to the next stage of the pipeline.
The network library sometimes breaks a single RPC message into multiple
buffers internally to avoid copying data (see MessageEncoder). This can
result in the following scenario (where "FxBy" means "frame x, buffer y"):
           T1         F1B1            F1B2
                        \               \
                         \               \
           socket        F1B1   F2B1    F1B2  F2B2
                                 /             /
                                /             /
           T2                  F2B1         F2B2

And the frames now cannot be rebuilt on the receiving side because the
different messages have been mixed up on the wire.
The fix wraps these multi-buffer messages into a FileRegion object
so that these messages are written "atomically" to the next pipeline handler.

Jenkins, test this please.

Test build #29622 has started for   PR 5336 at commit 4d3395e.

This patch merges cleanly.

Test build #29622 has finished for   PR 5336 at commit 4d3395e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/29622/
Test PASSed.

Thanks. Merging.

Mind closing the PR? Since this is not in master, github won't close the pr automatically.


Upgrade tails server deployments

The Tails Server was updated recently, and our deployments need to be upgraded to the latest version.
A new image has been built and rolled out to dev. Next steps are:

[x] test and ensure everything still works as expected
[x] Upgrade test
[x] Upgrade prod

Deployments have been updated, waiting to close issue while final verification that everything works takes place.
previous image was tagged as  tails-server:20220510, if a roll-back is necessary.


Round forecast times

Detailed Description
Would be good to have forecasts that are rounded to mins, 6.05 to 6.10, currently they 06:03:17 to 06:08:17
Context
We want regular forecast value times
Possible Implementation
im not sure where, but somewhere, we must use datetime.utcnow(), and we should then round that down to the nearest 5 mins

The caller can already specify a date using --date.
Either the caller does it or we add another option like --round-to-minute 5, where we would use the closest date before "now" (or --date if it is specified).
I don't think we should do it by default however.

yea, please add --round-to-minute 5, then that allows us to be flexible to 30 mintues for example


FE dependabot failures

most are in dev packages with will not be running during prod

Looking into this now. Seems like we are running this version of gatsby: https://github.com/gatsbyjs/gatsby/releases/tag/gatsby%403.14.0
From those release notes:

We will keep publishing patches for 3.14.x with hotfixes until 4.0.0 stable is published and at least several weeks after.

4.0.0 was released in October, so it's possible they're not updating this anymore. There are a few dependency issues from gatsby, which I would have expected to be fixed upstream. I'm going to try updating to the latest and see what happens.

Running npm install gatsby@latest.

Actually, now that I know how to do this, I can confirm that you're right that it's dev-only:
% npm audit --prod

                       === npm audit security report ===

found 0 vulnerabilities
 in 274 scanned packages

The deploy action even has a check for it: https://github.com/usds/justice40-tool/blob/main/.github/workflows/deploy_staging.yml#L51 https://github.com/usds/justice40-tool/blob/main/.github/workflows/deploy_main.yml#L52
I created https://github.com/usds/justice40-tool/pull/1041, because I think this qualifies as over-alerting.

I think we can call this done now.

New dependabot config is merged to only alert on prod security issues.


Question about the shifting operation in read heads

Thanks for the implementation! Really helpful for others to understand neural turing machine! I find that in the code, shifting (Eq. (8) in https://arxiv.org/pdf/1410.5401v2.pdf) seems to be implemented using pure convolution instead of circular convolution (https://github.com/snipsco/ntm-lasagne/blob/master/ntm/heads.py#L382-L390). Will this cause some problems?

This is very true, I chose to use flat convolutions instead of circular convolutions. In my early tests, they seemed to be faster than the circular ones. In practice, this had no impact on the experiments on the algorithmic tasks.
I will add a comment to address this!

Hi tristandeleu, can you please clarify what do u mean by flat convolutions
thanks


Please invite me to the GitHub Community Organization

Name
brilliantseniordev
Discord Username (if applicable)
No response
Additional Context
I'd like to be a part of awesome community

It's great having you contribute to this project
If you would like to continue contributing to open source and would like to do it with an awesome inclusive community, you should join our Discord Server and our GitHub Organisation - we help and encourage each other to contribute to open source little and often 🤓 . Any questions let us know.

You have generate duplicate new case