fix: update style of buttons in toast

Update toast spacing, alignment, and button style.

Update icon buttons to have transparent backgrounds by default. This is configurable via the new SASS vars:
$icon-button-bg: transparent !default;
$icon-button-invert-bg: transparent !default;

Coverage remained the same at 87.767% when pulling f07918020c443b5ba1bdbcb5398d75c571fe0e32 on abutterworth/toast-update into d4df79b2eade2aa55244fc541ef6c6cb81f5a961 on master.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Rover Project

Authors

Thomas Hall @tjh2822

Abstract
Begin the design and construction of a mock rover. A rover would be an area of space exploration completely new to SPEX, because of this there are a lot of unknowns that need to be answered before starting this project. Because of this the project will require a large amount of prototyping and testing. The team would look at the talent and skills of RIT Space Exploration and answer the question: what caliber of rover are we able to make. It would employ a multidisciplinary team to cover for construction and development. The project would be slated to run for two semesters. The rover would be extremely promotable and would look great at Imagine RIT.

@runphilrun Please review


issue with local domains on latest stable version

currently the latest stable version that composer installs is 0.4.2 witch depends on ratchet/pawl 0.1.*
but pawl 0.1.2 uses google's dns resolver witch of course cannot resolve local domains.
https://github.com/ratchetphp/Pawl/blob/v0.1.2/src/Factory.php#L32
this means that the latest stable version is not working on local domains
you have to either use ip address for the connection details instead of myserver.local
or install dev-master or 0.4.x-dev in order to work with local domains

@paranic - I am currently refactoring and separating out the components of Thruway so that we can possibly get a new release out. As it is right now, the dependencies are not at stable releases so we are blocked.

v0.5.0 has been released, which resolves this issue.


Is the libcaer_cm_encoder missing?

Hi!
Probably I'm overlooking something here, but shouldn't be there a corresponding libcaer_cmp_encoder.h to the libcaer_cmp_decoder.h (and for the non compressed variant as well) ?
For evt3 and mono this seems to be the case.

Well, I never really needed a libcaer encoder so I didn't lift out the implementation within the libcaer driver.
Do you have a use case where you want to encode in libcaer_cmp format?

Ah, thank you! That was exactly what I was overlooking. I only skimmed the README where only the metavision driver was mentioned and didn't go through the available repositories myself.
I greatly appreciate the effort you put into this!


HTML Links and Images

Description
Describe HTML links and images elements along with its attributes.
Domain
Frontend Dev HTML/CSS/JS
Type of Contribution
Documentation
Code of Conduct

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

/assign

/assign

/assign

/assign


How to increase font size?

The editor font size is not used in this plugin. How can I increase the font size to match the editor font?
(4k monitor here)

Hi. When editing file via plugin open Options dialog via last toolbar icon or context popup menu and navigate to "Font" category and press "Change font" button.

Assuming answer was sufficient. There is a plan to support shortcuts to change font size on the fly, but it's deep in TODO list...


Move package to ngx-md.

Ok. angular2-markdown created when angular was in beta stage. Since then there are so many updates to the packages.
In https://github.com/dimpu/angular2-markdown/issues/93 issue  @mischkl sugged to use ngx-* for the package name. I really think that's a great idea.
So, I'm thinking of moving to ngx-md module. What do you guys think?

👍


Incorrect field property definition for robot height in documentation.

On Widget List and Properties Page for the field widget under properties robot "height" is defined as
robot_height - The length of the robot in meters (defaults to 0.85)
Decimal number

I have found that it needs to be "robot_length", using "robot_height" for the property doesn't work.
//xxx example of how it has to be defined using Shuffleboard API with properties to make it work correctly.
frc::Shuffleboard::GetTab("Teleoperated").Add("Field", m_field).WithProperties({{"robot_width", nt::Value::MakeDouble(kTrackWidth.value())}, {"robot_length", nt::Value::MakeDouble(kWheelBase.value())}}).WithSize(10, 5).WithPosition(2, 0);

Didn't notice this until now, good catch! I'll update the docs and also make the existing code compatible with this property name in case if other people experience issues with it


[dev mode bug: 8.0.0-canary.10-17] Uncaught ReferenceError: webpackHotUpdate is not defined

Bug report
Describe the bug
Beginning with 8.0.0-canary.10 (I think?) through the current canary version, running a Next app in dev mode results in an Uncaught ReferenceError: webpackHotUpdate is not defined error in the console, pointing to line 1 of _next/static/webpack/static/runtime/main.js.[hash].hot-update.js. This causes the page to refresh every few seconds, which makes development with hot reloading nearly impossible.
Importantly, this does not affect Next at all in production and/or serverless mode.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Clone my repo: git clone https://github.com/4cm4k1/personal-website
In your terminal, use yarn command to install dependencies: yarn
Use package.json script to start dev mode: yarn dev
Open Chrome to app (macOS): open http://localhost:3000
Open Chrome DevTools (macOS): ⌘+option+i
Observe the errors in the Console tab (screenshot below).

Expected behavior
I expected dev mode with hot reloading to work without console errors.
Screenshots
When using yarn dev:

When using yarn dev:proxy:

System information

OS: macOS 10.14.4
Browser: Chrome 73.0.3679.0
Version of Next.js: 8.0.0-canary.10 - 8.0.0-canary.17

Additional context
Also, I use yarn dev:proxy to develop in dev mode with an HTTPS proxy. The error occurs there, too, along with other errors that may be caused by the first one. I’ve attached a screenshot for that as well. If it needs to be tested, you need to install mkcert (brew install mkcert), run yarn gen-dev-certs (this uses mkcert to generate valid SSL certificates for localhost, <IP_ADDRESS>, and ::1), and then you can run yarn dev:proxy (this runs yarn dev and yarn proxy simultaneously).

Closed because this issue pertains to the aforementioned plugin.

@4cm4k1 I get the same error. How do you solve it?

I've checked that indeed when you remove next-offline the error disappears . Then I went to check on the code source for the webpapck plugin of next-offline and seems like they're using an async hook where it should be synchronous...
const generateNextManifest = require('./next-manifest');

module.exports = class InlineNextPrecacheManifestPlugin {
  constructor(opts) {
    this.opts = opts;
  }

  apply(compiler) {
    const errorhandler = err => {
      throw new Error(`Precached failed: ${err.toString()}`);
    };

    if (compiler.hooks) {
      compiler.hooks.done.tap(
        'CopyPlugin',
        async() => generateNextManifest(this.opts), //    !!!!here!!!!
        errorhandler
      );
    } else {
      compiler.plugin(
        'done',
        async() => generateNextManifest(this.opts),
        errorhandler
      );
    }
  }
};
`
``

Updating next-offline to 3.3.7 seems to have solved it for me.

@themao is correct.


Fix initial zoom. When new data is loaded, show all data points.

Fix Issue #8

lgtm with a nit

Thanks! Merging.


Working implementation of fast dtw

DO NOT PUSH TO MASTER. The branch has conflicts that must be resolved.


Correctly fix the problem with '$/' notifications

The notifications come in the form of a JSON object rather than a JSON
string.
Fixes https://github.com/alanz/haskell-lsp/issues/206.

I verified in VSCode that spurious errors are displayed with the old code and they are not anymore with this change. The problem can be seen whenever some settings value change in the Settings UI.

Can this PR be reviewed/merged please?


how to get the address list?

Description
I use lncli unlock but it returns"it was unlocked already", but I don't know the address, So I generate a new address with lncli newaddress np2wkh and get some coin from the faucet using the new address,but the walletbalance is still 0, Do I need to change to this new address and how to do it?

Have you verified that the transaction confirmed? What’s the txid?

I’m not sure what’s meant by change to the new address, but you shouldn’t have to do anything extra to see the balance. The process you describe sounds correct.

Ok,my fault,I know something about it . Please close this issuse thank you so much On 2018-08-27 11:10 , Conner Fromknecht Wrote: I’m not sure what’s meant by change to the new address, but you shouldn’t have to do anything extra to see the balance. The process you describe sounds correct. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

Good to hear, no problem


excellent examples pull in Pepr dist folder to test new api functionality

Is your feature request related to a problem? Please describe.
When there are changes to the surface of the Pepr api, excellent examples is not able to be run against them in CI until the branch is pulled into main.
export async function moduleBuild({ version = "", verbose = false } = {}) {
  // can't have await expressions in default args, so gotta do it here
  if (version === "") { version = await peprVersion() }

  // pepr cmds use default tsconfig.json (NOT the cli's tsconfig.json)
  const pepr = { TS_NODE_PROJECT: "" }

  let cmd = `npx --yes pepr@${version} build`
  console.time(cmd)
  const build = await new Cmd({ env: pepr, cmd }).run()
  if (verbose) { console.log(build) }
  console.timeEnd(cmd)
}

Describe the solution you'd like

Given we are running the e2e in ci against a PR candidate not merged into main
When we build the module moduleBuild
Then the candidate branch is cloned, build, and the dist folder is copied to the excellent examples

Describe alternatives you've considered
(optional) A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

I'm not 100% that this would be better than just symlinking pepr --> pepr-excellent-examples/node_modules/pepr as we've been doing manually. :thinking:
moduleBuild is called for every excellent example which means that an update as described would do a separate clone & build every time, which... would not be awesome.   I suspect it'd be easier / faster to just add the symlinking as a distinct step before we ran the test suite in CI, no?

A manual workaround for developers is included as part of pepr-excellent-examples. I'll consider both approaches as I work on this

After some review, the best option seems to be using the approach taken by tests in journey/ that run npx --yes ${peprAlias} where peprAlias points to pepr-0.0.0-development.tgz (the thing we're trying to test.
I ran into some issues with file path references that ate up a lot of time, so a usable solution shouldn't be as brittle as things are right now.
For reference:

PR to pepr-excellent-examples
PR to pepr
CI job logs for passing proof of concept for a simple excellent-example

In CI, we can just provide the build-under-test with an npx command.
Locally, we've favored a symlink-based approach. Both approaches could work (i.e., symlink to a directory during test setup or copy a .tgz archive during test setup). The best place for this setup so that it only runs once every time we trigger the test suite looks like _hepers/dev/cli.mts by way of a preAction & postAction hook.

The test suite will probably support 3 behaviors when testing the pepr CLI package:

default: Use pepr version defined in node_modules. Current behavior.
--local-package: Build a pepr CLI package locally and use it for tests. Good for local testing when you're modifying pepr frequently.
--custom-package: Use a provided pepr CLI package for tests. Good for CI when pepr is already built by an earlier step.

Example usages would look something like:
npm run test:e2e -w $EXCELLENT_EXAMPLE
npm run test:e2e -w $EXCELLENT_EXAMPLE -- --local-package
npm run test:e2e -w $EXCELLENT_EXAMPLE -- --custom-package ../my-pepr.tgz


Fix https://github.com/jenkinsci/puppet-jenkins/issues/668

This is a Fix/Workaround for voxpupuli/puppet-archive bug https://github.com/voxpupuli/puppet-archive/issues/242

gem addressable (used by travis indirectly) has release 2.5.0 which now needs some other gem which requires ruby 2.0. Second commit fixes this


Fix programmatic method invocation.

@eahefnawy this PR contains a small fix that was breaking the programmatic invocation of custom methods on the @serverless/template component. CLI usage however was working normally.
I also added a README file with some examples as I see a lot of people struggling with programmatic usage of this component.
This has been tested manually for both CLI and programmatic usage, all the cases I could think of.

@eahefnawy This is fixing a breaking change, so it is super important to be addressed. @Pavel910
Can I make the following comments:

Throwing an error in createCustomMethod may be appropriate, but without any testing, changes like this can (and in fact, this change does) cause unintended consequences.
Perhaps unit/integration tests on the core libraries. Not saying that things need to be tested vigorously but it may be a good idea (in fact, I will open an issue for this).
Thanks very much for the README. It is super helpful.

To make this component better overall, the template path should be passed to constructor, and not to methods themselves (then your proposed solution with trying would work nicely), but then it is a major change that also involves updates to CLI. That's something @eahefnawy must allow us to do :)

It seems like this may be the way to go. However such a big change may need to wait for testing (sorry I am going on about testing, but it seems tough to make any change to a core library without testing).

@barrysteyn Agreed, it would be nice to have at least basic tests in place.

Thanks folks. Testing is absolutely planned. We just didn't 100% settle on the API yet and currently taking feedback. PR like these are exactly the feedback that we need.
LG2M 😊


Addeed Contribution Guidlines

Added contribution Guidelines in Readme.md .Please merge it #Hackoberfest

We can't Merge this PR because before generating a PR the issue must be assigned to you. This issue is already assigned to someone else.


CV reports errors - unknown book names due to misspelled book names in the program data file

Robert says It would have been incorporated in v1.0.2 released 16 Jan. (See the Versions tab here.)
https://www.npmjs.com/package/uw-content-validation

This is pushed as a WIP PR
so it won't be merged yet
but preview is here
https://deploy-preview-697--tc-create-app.netlify.app/

Preview looks good. Not seeing the error. Thanks @ancientTexts-net

Not seeing this error in translationCore Create - v1.2.0-rc.2 build 28-4717783.

Errors not showing in v1.2.0-rc.2 build 35-01cd274


Add NodeJS ImageStream and BuildConfig

On the back of https://github.com/absa-subatomic/laboratory/issues/22, add the ImageStream and BuildConfig for the NodeJS Jenkins slave.

Incorrectly raised issue in this repo. Moved to https://github.com/absa-subatomic/local-hadron-collider/issues/14.


Add documenso service

Changes

Adds https://documenso.com/ in services list

Issues

fix #3910

I decided to close this PR because I created it from the fork. Check #4550


Encode spaces as '%20' in images paths

Hi and thank you for this extension :)
Just a little issue: If we want to use a path or a filename with spaces, the image is not displayed. In fact, spaces are not allowed in urls. But we can url-encode them to get a %20 and then it works perfectly :)
Have a good day !

The issue was fixed just now. You can update to 1.0.5 check it.  :)

Perfectly works ! Thanks :)


TryParse should handle all exceptions that could arise from parsing

Fixes #1837
The current code doesn't catch AmazonClientException which can occur if the account id is not well formed: https://github.com/aws/aws-sdk-net/blob/92cdca1f9e331826a46502b1706999af0b8e6880/sdk/src/Core/Arn.cs#L61

PR is released as part of version <IP_ADDRESS> of AWSSDK.Core. Thanks for the PR.


Cache policy with environment flag and identity flags conflicts

Let say I configure a FlagsmithCache of 1 minute.
If I call getEnvironmentFlags and then call getIdentityFlags, then the first cached call will be returned for the second call.
I feel like this behavior is error prone as we don't expect to have the "default" value of environment flags when we request for a specific identity override, even if we cache the results of the API.

Thanks for raising this @bamanrich - I totally agree with you here. I'll look to roll this into a new release in the near future.


Update build to work with newer dcos-commons version

Done as part of getting https://github.com/mesosphere/universe/pull/1580 working.
cc @mberhault so that I'm not completely alone here, but self-merging on the assumption that you don't really know/care about this

LGTM with not a whole lot of context. The mix of ${} and plain $ is bothering me, but not enough to argue.


Improve project structure

The project have all files dumped into the root. It would be a lot easier if the source files were moved into a sub folder. Either to a flat layout or a src layout.
flat layout
.
├── README.md
├── pyproject.toml
├── setup.py
├── wikmd/
│   ├── plugins/
│   ├── __init__.py
│   ├── cache.py
│   └── wiki.py
└── tests/
    ├──test_basics.py
    └── test_plugins.py

src layout
.
├── README.md
├── pyproject.toml
├── setup.py
├── src/
│    └── wikmd/
│            ├── plugins/
│            ├── __init__.py
│            ├── cache.py
│            └── wiki.py
└── tests/
    ├──test_basics.py
    └── test_plugins.py

Hi @Jerakin,
This is a good idea, I was already looking into it, would also be handy to package wikmd. I guess my preference goes to the src-layout. If you think the other one would be better, let me know.

I am also partial to a src layout. Are you looking into this or should I take a stab at it?

Alright lets do it that way then. I did not look into it yet.


Gitignore node_modules

The first step of DEVELOPING.md is to run npm install, which fills up node_modules with dependency artifacts that shouldn't be tracked by git.
Same PR as #4024 but targeting branch 0.6.x instead of master.

Okay, good to know -- I'll do that going forward. I've squashed the two commits into one.


Encrypt Plain text Db (expose sqlcipher_export)

I Hope you expose these functions in sqlite swift API to encrypt plain text DB
try dbConnection.execute("ATTACH DATABASE '\(encryptedPath)' AS encrypted KEY '\(password)';")
try dbConnection.execute("SELECT sqlcipher_export('encrypted');")
try dbConnection.execute("DETACH DATABASE encrypted;")

Yes, this is planned. See #1098

hi  @jberkel When will 0.14.0 be released ?

[Decrypt a SQLCipher database to a Plaintext Database](https://www.zetetic.net/sqlcipher/sqlcipher-api/#example-2-I Hope you expose these functions in sqlite swift API  decrypt-a-sqlcipher-database-to-a-plaintext-database)
public func plaintext_export(_ location: Location, key: String) throws {
let schemaName = "plaintext"
let sql = "PRAGMA key = (key)"
try run(sql)
try attach(location, as: schemaName, key: "")
try run("SELECT sqlcipher_export(?)", schemaName)
try detach(schemaName)
}
@jberkel


HDDS-9654. Support ranged GET request for a specified part

What changes were proposed in this pull request?
Currently, we do not support a 'ranged' GET request for a specified part, which is useful for downloading just a part of a multipart key. Even when a part number has been specified, we still download the entire multipart key.
With this fix, we should be able to download just a part of a multipart key. The additional client logic introduced takes advantage of the existing BlockID to partNumber mapping as part of the KeyLocation proto message for filtering out the OmKeyLocationInfo list.

Added integration tests
Green CI/CD checks: https://github.com/tanvipenumudy/ozone/actions/runs/6807544806/

@SaketaChalamchala @xBis7 @vtutrinov can you please take a look as well?

LGTM
@tanvipenumudy thank you for adding the feature.

Thank you @tanvipenumudy for this change and @vtutrinov for the review. @tanvipenumudy can you please extend the robot test to read a part and validate the size read?

Thanks @tanvipenumudy for the patch, @kerneltime, @vtutrinov for the review.


Add parcellation output

[x] Add extractor for parcellation output
[x] Add interface for parcellation output
[x] Adjust segmentation mask orientation

stub here

File looks good; only a minor comment for the code. We use 'file_path' as standard name for arguments in interfaces and extractors, I would follow this practice here and rename mat_file_path to file_path in both extractors and interfaces


Auto-complete declaration names in arbitrary namespaces

This fixes exactly #1659. It does not (yet) attempt to do fuzzy-matching across the entire declaration name including namespaces, as that is potentially slow and can yield unhelpful results if the namespace is the only thing that matched; on the other hand, some examples in https://leanprover.zulipchat.com/#narrow/stream/270676-lean4/topic/autocomplete.20woes are of this kind, so this is something we should revisit in the future.

It does not (yet) attempt to do fuzzy-matching across the entire declaration name including namespaces,

One thing that's quite common is to not know whether the lemma you're looking for is of the form SomeProp.someLemma or someProp_someLemma (_ vs . and s vs S). Is this something that autocomplete can help with as of this PR?

Is this something that autocomplete can help with as of this PR?

Only if matching against someLemma is sufficient for finding it

We need more autocompletion tests at tests/lean/interactive.

It does not (yet) attempt to do fuzzy-matching across the entire declaration name including namespaces,

One thing that's quite common is to not know whether the lemma you're looking for is of the form SomeProp.someLemma or someProp_someLemma (_ vs . and s vs S). Is this something that autocomplete can help with as of this PR?

I'm wondering whether including the last two segments, i.e. usually the type/prop and function/theorem would yield a sensible balance of exhaustiveness, relevance, and performance. But that feels a bit arbitrary, let's go with this more limited and clear-cut extension for now.

I think this is ready to go as a relatively conservative extension of the current behavior, unless someone can think of additional interesting tests to add


Flag loader as cacheable

According to the webpack docs, a loader is cacheable if it is deterministic. This seems to apply to DustJS templates. So, in order to improve re-compilation time, the code should be adjusted to mark the loader as cacheable.

Has been incorporated


Empty current-context not recognized

Hey!
I just ran kubectl config view --raw --flatten on my cluster
to export the config for use in Lens:
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: ...
    server: https://<IP_ADDRESS>
  name: local
contexts:
- context:
    cluster: local
    user: cluster-admin
  name: ""
current-context: ""
kind: Config
preferences: {}
users:
- name: cluster-admin
  user:
    client-certificate-data: ...
    client-key-data: ...

I've added this to $HOME/.kube/config.
Lens would not recognize the cluster at first.
I then gave the the context a proper name (which previously was ""):
...
contexts:
- context:
    cluster: local
    user: cluster-admin
  name: "my-k8s-cluster"
current-context: "my-k8s-cluster"
...

After that change, everything works as expected.
Not sure if this is already fixed in a more recent version of Lens.

What would you like to be added:
Either

having an empty current-context ("") should just work
or the user should be prompted to set a proper context name

Why is this needed:
Bad UX for users new to Kubernetes or Lens.
Environment you are Lens application on:

Kubernetes distribution: NixOS on-prem
kubectl --version: v1.19.6-rc0
Desktop OS: Ubuntu 20.04.3
Lens Version: 5.2.5.latest-20211001.2 (installed via .deb from website)

The reason that the cluster was not shown is because the name was empty on the context object, not because the current-context field was the empty string.
As for the errors being more visible to the user, that is a duplicate request from #3436

Alright thanks!
Closing in favour of #3436.

BTW is having "" even valid for a cluster? I would expect that kubectl (being written in golang) would treat that field as empty (since golang default initializes everything)

Looking only at the Go type definitions of Config and Context it seems that both current-context and contexts[0].name are generally allowed to be "" 🤔

Oh they will be allowed to be "" and even will be set to "" if not present in the JSON or YAML file itself, I would expect that errors would be thrown by kubectl if they are empty. And if you look at https://github.com/kubernetes/client-go/blob/v0.22.2/tools/clientcmd/api/helpers.go#L47 then you should be able to see that it considers "" to be "not-set"


nucamp

review this https://shanenull.com/adventure/
setup on new mac air + add any notes required for setup
improve python & js notes & anything I can reuse to udpate  buddhism/ workflow/ and related sub projects
review this context for first letters memorization apps

https://learn.nucamp.co/course/view.php?id=29&section=1#module-9778


feat(ssa): Multiple slice mergers

Description
Problem*
Resolves #2599
Summary*
This PR implements the following (this is also partially outlined in the issue discussion):

When we have a push_back, we need to check whether the length == capacity. If they are not equal we need to actually perform an array_set rather than making a new array. Simply adding an element to a slice which is the result of a slice merger would potentially result in the element being included after placeholder data in the slice's SSA value. When the slice is later accessed the placeholder data will potentially be accessed where the element that was pushed back is expected.
In order to conditionally array_set or make a new slice value we will need to expose the merging of values (the merge_values method in flattening) to the entire SSA crate rather than it being part of the flattening pass' context.
When we have a pop_back we no longer construct a new array by directly popping off of the the SSA array value that represents a slice. Instead, we simply array_get the flattened values of a slice and reduce the dynamically tracked length by one. For example in this program:

fn merge_slices_push_then_pop(x: Field, y: Field) -> [Field] {
    let mut slice = [0; 2];
    if x != y {
        slice = slice.push_back(y);
        slice = slice.push_back(x);
    } else {
        slice = slice.push_back(x);
    }
    slice = slice.push_back(30);
    if x == 20 {
        slice = slice.push_back(20);
    }
    let (slice, elem) = slice.pop_back();
    assert(elem == 30);
    let (slice, elem) = slice.pop_back();
    assert(elem == x);
    slice
}

When we get to the first pop_back we have a slice of (length 5, [0, 0, y, x, 30, 0]). If we just pop_back the slice value directly we will get 0. So instead we just do an array_get at len - 1 and leave the slice the exact same. The simplified result where we want to return (slice, elem) is just ((length 4, [0, 0, y, x, 30, 0]), 30). So the slice stays the same and we just reduce the length.
I posted under the issue description how I thought insert and remove would be the most challenging to implement, but it is in fact just push_back and pop_back as placeholder information is only every attached to the end of the slice. We can keep slices sound as long as we accurately track the slice length and its internal elements. This PR moves to further ignore any values that are part of a slice's SSA array value, but past the dynamically tracked slice length.
Documentation

[] This PR requires documentation updates when merged.

[ ] I will submit a noir-lang/docs PR.

[] I will request for and support Dev Rel's help in documenting this PR.

Additional Context

PR Checklist*

[X] I have tested the changes locally.
[X] I have formatted the changes with Prettier and/or cargo fmt on default settings.

I haven't finished going through this PR, but can you fix the conflicts?

I haven't finished going through this PR, but can you fix the conflicts?

Yup will do, these look to be new ones that came up after the PR was made.


backend: sort unconfirmed transactions by created time

This commit updates the transaction history sorting to handle multiple unconfirmed transactions. These transactions are now sorted by their created time.

Please adjust the unit test to cover sorting by CreatedTimeStamp with the various options.

@benma updated, PTAL


Trouble testing component that uses the helper with a custom config

I have a component that uses the helper with a custom config. It works perfectly in the app but now I am trying to write an integration test for it.
My first stab got me this: Failed to create an instance of 'sanitizer:links-only'. Most likely an improperly defined class or an invalid module export.
So I figured I need to run the initializer. My test now looks something like this:
import { moduleForComponent, test } from 'ember-qunit';
import hbs from 'htmlbars-inline-precompile';
import initializer from 'my-app/initializers/setup-sanitizers';

moduleForComponent('my-component', 'Integration | Component | my component', {
  integration: true,

  setup() {
    // manually invoke the ember-sanitize initializer
    initializer.initialize(this);
    //initializer.initialize(this.container);
  }
});

test('it renders', function(assert) {
  ...
});

But now I get container.registerOptionsForType is not a function coming out of the initializer. I think I'm on the right track but I'm not sure what to pass to the initializer. Any suggestions? Thanks.

Ok, this seems to work but I'll bet there's a better way:
import Ember from 'ember';
import { moduleForComponent, test } from 'ember-qunit';
import hbs from 'htmlbars-inline-precompile';
import sanitizer from 'my-app/sanitizers/links-only';

moduleForComponent('my-component', 'Integration | Component | my component', {
  integration: true,

  setup() {
    this.container.registry.register('sanitizer:links-only', Ember.Object.extend(sanitizer));
  }
});

test('it renders', function(assert) {
  ...
});

I've done this before, but remember it being a bit evil when I did it too & having to go through the container (now registry) like you're doing.
The problem is, as you've seen, that initializers aren't run in component tests as the app isn't booted.
I'll ask around and see what the best way of doing it is. I wonder if there's a way for the addon to hook into the tests so it sets up the initializer for you automagically?

I'm having this issue too, @rlivsey have you figured out the best way of testing?

I wrote my component test like this:
...
import sanitizeInitializer from 'my-app/initializers/setup-sanitizers';

moduleForComponent('foo-bar', 'Integration - pods/components/foo-bar', {
  integration: true,
  beforeEach() {
    sanitizeInitializer.initialize(this.container.registry);
  }
});


docs: add long timeout code snippet

This code snippet is very similar to the SyncAPI sample.
The purpose of this sample is to explain how to use the keep-alive setting to send a sync request with long timeout.

Here is the summary of possible violations 😱
There is a possible violation for not having product prefix.
The end of the violation section. All the stuff below is FYI purposes only.
Here is the summary of changes.
You are about to add 1 region tag.
This comment is generated by snippet-bot. If you find problems with this result, please file an issue at: https://github.com/googleapis/repo-automation-bots/issues. To update this comment, add snippet-bot:force-run label or use the checkbox below:

[ ]  Refresh this comment

Optimization AI is in restricted GA (GA with allowlist). The region tag prefix can be found here: https://devrel.corp.google.com/admin/products/463?t=snippets


bug: Afetbilgi Icon needs to change.

Bug Definition
Afet Bilgi Icon can be changeable. On right bottom side.
** discord username: Yağız M.# 0539 ** (do not assign me pls)
Bug environment
afetharita.com
Describe how you are producing the bug step by step

Expected Behaviour
Needs to show Afetbilgi site icon.
Screenshots

Desktop Information

Operating System: [Windows]
Browser [Microsoft Edge]

I'm taking this

issue must be approved by product team. wait for approved label before started to work.

This should be go in before the layout changes (filters etc.), there is also a refactor on related PR #774


[UI] Increase selected option contrast

It's not clear to some people if they really voted for a proposal. The contrast seen may be improved.
Possibilities:

use different colors
change background color
use borders and/or boxes

How it is today:

The contrast may be obvious for you, but for some people with special disabilities and some underpowered devices and their poor screens, the story may be different.
Anyway, this is just a suggestion.


Install new ZED X camera + NVIDIA AGX perception computer

09/09/2024 Update:

Status: Doing research on the best implementation/mount for ZED cameras.
Next Steps: Create rough engineering requirements, including schematics that show the exact position of the ZED cameras on the car, pitch/angle, required field of view, and the materials needed for mounting (e.g., 80/20 material).
Projected Completion: TBD (subject to feedback and coordination with Gueren and Abhinav)
Update: I have been exploring the optimal placement for the ZED cameras, with a focus on achieving front-facing, high positioning, wide field of view, and ensuring minimal glare or obstructions. The mounting points on the car’s front, back, and side rails. Additionally, I will need coordinate with Gueren on the ROS setup and Nvidia Orin installation, which will involve running GMSL2 cables from the cameras to the Orin. I've also reviewed the physical dimensions of the cameras and the Orin to better understand the mounting challenges..

09/16/2024 Update:

Status: Waiting on ZEDX Camera/Orin configuration.
Next Steps: Take Measurements/Fabricate Orin Computer Mount
Projected Completion: TBD (subject to feedback and coordination with Gueren and Abhinav and Ryan)
Update: We have figured out mounting position for the Orin computer and will simply find another foot 80/20 material and build it on top of the OBC mount (specific measurements will be taken this week). We will need to determine whether or not the cameras need to at an angle to capture a good enough FOV. We will also need to add the ZEDX Cam Connector PCB Board to the Orin. We should also get an idea of how to implement the wiring.

Ideas for Mounting
Cameras

Computer

Reminder for next update...

Next Steps: Looking into 3D Printed Mounting to more precisely hold the ZEDX Cameras. Check the printer we have in the lab and see what kind of material we have (hopefully have the kind of material that can handle the heat of the sun). Need to also create better mounting solution for the Adafruit MCU rather than keeping the plastic tub (me and Ryan also looking into 3D printed solution that hooks to the rails of the car).

09/24/2024 Update:

Status: Continued working on mount design.
Next Steps: Fabricate Orin Computer Mount and Prototype 3D Print Mount
Projected Completion: TBD
Update:

This is a first prototype that encapsulates the cameras. Printing something like this will take a bit of material but will protect the camera. There are plenty of ways we could have optimized or gone for a completely different design entirely but..... we just wanted to go with something that will be sturdy and protect the camera.

09/24/2024 Update:

Status: Tested mount design.
Next Steps: Fabricate Orin Computer Mount and continue iterating mount to create better FOV.
Projected Completion: TBD
Update:

@NitroxNinja (Ryan) will continue to CAD variations of the mount but some additional 80/20 might be required to create better position for FRONT/BACK cameras.
Current prototype of mount fits camera and mounting holes need to be increased in diameter to account for shrinkage during cooling process.

Also got to see FOV for ZED cameras and will need to define what we would like to see. 360 Vision? How close to the car would you like to see? Har far should the cameras be seeing?....

For some of the viewing angles, you can see the roof of the car blocks the bottom half of the view, so we will need to create higher mounting positions with 80/20 + 3D Printed material.

10/6/2024 Update:

Status: Tested mount design.
Next Steps: Fabricate Orin Computer Mount and continue iterating mount to create better FOV.
Projected Completion: TBD
Update:
We were thinking for a second, and I reduced the amount of material for the 3D print so it can print a little faster. It doesn't compromise structural integrity because it has a good enough factor or safety(assuming final product is made up of nylon), since assuming a flat surface traveling at the car's top speed(40MPH I think) it only experiences about 64.4N of force(may need to be recalculated, I am still learning how to run FEA).

I also have a design ready that is a little more angled. To do that, I have some 8020/ C channel design that could angle the camera. However we ran into a dilemma. As originally we were going to mount it higher up, but realized that blocked the LiDAR. To avoid the camera getting in the way, the decision was made to mount the camera further up. This challenges the true 360 camera system, because by 4 cameras, there may be some blind spots in between the front 2, and that could be detrimental in terms of fully accurate understanding of the environment to our developers... but we will proceed and suggest mounting the side cameras partially "more forward" to encapsulate a full 3D environment

These will be later printed in black PLA and I didn't want to burn through my black PLA supply.
I tried using the 3D printer in the lab but it was really weird for me to use. Ultimaker 3D Cura Slicer doesn't come with a preset to slice STL files for the Dremel Digilab printer(I can set up the presets on my own later, but I don't have much experience in this). I tried using the Dremel dedicated slicer but it was super slow for some reason and the program never booted up on my computer.
I will try and figure out how to use the Dremel 3D printer properly later, but for now I am just gonna use my personal printer.

This is the picture of the mount using black PLA and mounted on the roof rack of the car.

10/14/2024 Update:

Status: New front/rear camera mounts
Next Steps: Fabricate Orin Computer Mount and continue iterating mount to create better FOV, adjust just in case
Projected Completion: TBD.....
Update:
As I am still learning how to use Solidworks, me and Andy tested a variety of camera position placements and determined, that placing the camera 6 inches away from the horizontal bar is the optimal spot, so that it wouldn't capture the top of the windshield or pick up any other obstructions which will make it hard to parametrize stuff for the dev team. This also minimizes the amount of "blindspots" there are in the view as the ZedX camera captures. It is pretty unique on how much space it can acquire.

Luckily, I was able to make a design that is pretty similar to the other one, and may require 2 prints, but I am also learning 3D printing as a whole again. This one is non-adjustable unfortunately, however it turns out we might this can be adjusted via the 8020 that will be attached to the 8020.

10/21/2024 Update:

Status: New front/rear camera mounts printed
Next Steps: Fabricate Orin Computer Mount, and continue iterating mount to create better FOV, adjust just in case
Projected Completion: TBD......
Update:
We will get these mounted on Monday before the meeting so we can get a see the FOV of the camera. The back camera still needs to be printed. The car might be too long to enable 360 degree FOV based on previous testing but, we will continue to adjust mounts as necessary.

2 mounts of the one above have been printed and will be added to the car on Monday.

All mounts are mounted... You can loosen the screws to adjust horizontal positioning.


Update version of expensify-common

Details

Fixed Issues

For https://github.com/Expensify/Expensify/issues/244065

Tests

[x] Verify that no new errors appear in the JS console (I see the same on this branch and main)
[x] Sign up with an account on the domain accountant.com (eg,  test@accountant.com), or sign in with one of the credentials already created
[x] Get validate code from psysh using Auth::getAccountValidateCode(AuthTokenManager::getEmailToken('test@accountant.com'))
[x] Set a password by going to localhost:8080/setpassword/78/VALIDATECODE on web
[x] Clicked green button when going through the sign up flow  / Clicked workspace > ... when going through the sign in flow
[x] Created a new workspace
[x] Confirmed the workspace name was based on the email prefix and not the domain (eg, it was called Test's Workspace for<EMAIL_ADDRESS>and not accountant.com's workspace or something like that)
[x] Repeat the steps for<EMAIL_ADDRESS>and confirm the workspace name is Cead22's Workspace

Offline tests

[x] The I turned off wifi using chrome dev tools
[x] Clicked avatar > cead22's workspace > ... > new workspace
[x] Confirmed a new workspace was created with the right name Cead22's Workspace 2

QA Steps

[ ] Verify that no new errors appear in the JS console
[ ] Sign in with<EMAIL_ADDRESS>(or any other account on that domain)
[ ] Get validate code from https://www.expensify.com/_support/specialLinks, if you don't have access, ask @cead22 or someone else with access, and get accountID from the account as well (you can do this by support logging in)
[ ] Go to staging.new.expensify.com/setpassword/AccountID/VALIDATECODE
[ ] Set a password and you should be logged in
[ ] Click green button
[ ] Create a new workspace
[ ] Confirm the name of the workspace contains the front part of the email you signed up with, eg "Test1's Workspace" and that it doesn't contain the domain name (ie, no "accountant.com's Workspace")
[ ] Turned off wifi using chrome dev tools
[ ] Click avatar >the workspace button > ... > new workspace
[ ] Confirm a new workspace was created with the right name (eg, "Test1's Workspace 1")

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] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[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 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 was added in all src/languages/* files
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[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 a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[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(themeColors.componentBG)

[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] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

PR Reviewer Checklist
The reviewer will copy/paste it into a new comment and complete it after the author checklist is completed

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for expected offline behavior are in the Offline steps section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] 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)
[ ] 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).

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] iOS / native
[ ] Android / native
[ ] iOS / Safari
[ ] Android / Chrome
[ ] MacOS / Chrome
[ ] MacOS / Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] 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).
[ ] I verified that comments were added to code that is not self explanatory
[ ] 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.
[ ] I verified any copy / text shown in the product was added in all src/languages/* files
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] 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.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] 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
[ ] I verified that if a function's arguments changed that all usages have also been updated correctly
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

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

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

[ ] 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)
[ ] 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.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos
Web

accountant.com
cead22.com
cead22.com offline

Mobile Web - Chrome
Covered by Web since this change isn't platform specific
Mobile Web - Safari
Covered by Web since this change isn't platform specific
Desktop
Covered by Web since this change isn't platform specific
iOS
Covered by Web since this change isn't platform specific
Android
Covered by Web since this change isn't platform specific

: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 @grgia in version: 1.2.34-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

This is a pass!

🚀 Deployed to production by @luacmartins in version: 1.2.34-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Screen gets black after swiping back and forth fast

I think the issue has become an edge case with all the adjustments but still it can be easily triggered by Swiping back and forth fast + tapping on a tabBar item at the same time.
This issue has to do with new a transition being triggered without the previous transition being finished. My initial guess is that I'll have to work with snapshot views to avoid any potential issue and restore the original state if we encounter an error.
Any extra help is welcome!

Solved in #37


Remove version: Bitnami.WAMP version 8.1.11-0

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://downloads.bitnami.com/files/stacks/wampstack/8.1.11-0/bitnami-wampstack-8.1.11-0-windows-x64-installer.exe
OK
(Automated message - build 910)

Hi @Exorcism0666,
This manifest has the highest version number for this package. Is it available from another location? (This might be in error if the version is switching from semantic to string, or string to semantic.)
(Automated response - build 886.)


Update anonymous-read-access-overview.md

AllowBlobPublicAccess should be changed to AllowBlobAnonymousAccess in the entire document as this display name is already changed in Azure Portal but the document the not updated with AllowBlobAnonymousAccess
Currently there are 2 places in the document which needs to be changed with AllowBlobAnonymousAccess instead of AllowBlobPublicAccess

Thanks for pointing it out. We have already made changes in all locations. This was inadvertently missed.
#sign-off

Close/reopen to clear validation error


Saving a link - removes inner text

I add a new link with inner text, but after saving link's text disappear.

fixed in v0.8.4


Reallocate hardware serial port in ESP32 Heltec LoRa V2

Would it be possible to add an additional constructor to map a hw serial port to new pins? It would be particularly useful when using Heltec ESP32 LoRa V2 to map Serial2 to two of the few available pins on the board (e.g. 37,13).
In PZEM-004Tv30.h, additional public constructor:
PZEM004Tv30(HardwareSerial* port, int rx_pin, int tx_pin, uint8_t addr=PZEM_DEFAULT_ADDR);
In PZEM-004Tv30.cpp:
PZEM004Tv30::PZEM004Tv30(HardwareSerial* port, int rx_pin, int tx_pin, uint8_t addr)
{
port->begin(PZEM_BAUD_RATE, SERIAL_8N1, rx_pin, tx_pin);  //Baud rate, parity mode, RX, TX
this->_serial = port;
this->_isSoft = false;
init(addr);
}
So in the sketch, the instance of the class would be created with two additional parameters for the pins:
PZEM004Tv30 pzem(&Serial2, 37, 13); // (serial port, RX pin, TX pin)
I have checked the library with these modifications and it works fine.
Thanks!

There is constructor for pin mapping on ESP32.
Are you sure you're using exactly this lib? Looks like you're using library for v3.0 of PZEM

You're right, I was using the mandulaj/PZEM-004T-v30. Sorry for the mistake.

@ManuelJimenezBuendia there is a PR pending for this feature. You can use mine branch meanwhile if you like

You're right, I will use yours.
Thanks!!!


On Scroll product isn't loading

I am using a this free module. When I scroll down ajax request initiate and response come with new page content . But this response not updating on current content. Can anyone suggest the solution for this

You may have some compatibility issue(s) with 3rd-party extensions or custom code. Could you try disabling other extensions to see if at least the Infinite Scroll functionality works?

Hello @gsomoza ,
Thanks for your suggestion. I tried with that and yes it worked for me.  But due to this I am unable to use the other extension. In that case can you please suggest me any ajax filter which is compatible with Infinite Scroll?

Any AJAX-related extensions that heavily modify the way the catalog pages are displayed/rendered will have conflicts with our extension. This means that a developer will have to integrate them together manually.
Unfortunately this is not something we can do ourselves because this is a free extension and there are dozens of other extensions that we would have to provide (and maintain!) compatibility for. Most of the code in this extension was built by several people during their free time, as a way to give back to the Magento community.
If you have the resources, I recommend you ask your developer to make the integration. And if that works out it would be awesome if you could then submit the integration code to this repository so that other people can benefit as well!


Expose RequestScheduler in the public API

We should consider exposing parts of RequestScheduler in the public API, especially concurrency settings like maximumRequests, maximumRequestsPerServer, requestsByServer, and throttleRequests. This would give developers more control over tile request concurrency.
In fact before RequestScheduler was introduced throttleRequestByServer.maximumRequestsPerServer was part of the public API.
Any reasons not to do this? It would be a quick PR.

Hi guys, just following up on this request . Is it possible that you can provide us an angular-cesium example of how to use the TileProviderError , such as a small snippet of code just to understand how best to capture the errorEvent..thanks

@wadeward I think your question is not related to this issue. Please open a thread in the Cesium forum with some more information on what you're trying to do.


Add Elemental to the header/more from SUSE menu.

In particular KW went back into the menu as a decision coming from Guna and Mike Latimer. There is likely to be more iterations on this with inputs from various stakeholders over time.

Yes, there are also k3s a Longhorn, that are fairly popular. Not sure how many projects we should have, and which.
I would try to order them by popularity, like:
* Rancher

* Rancher Desktop

* K3s

* Longhorn / Kubewarden (CNCF projects)

* Fleet (not stable?) / Elemental / Harvester

* Opni (not stable?)

That ordering is being laid out for us at the moment. Consistency across all sites probably.

Probably, there will be a reduction in the number of menu items in 'More from SUSE' as well. Discussions apparently ongoing. But, in the interim, I think this is fine to merge.


Add multiple lines in site footer description

It ain't perfect, since there is an extra <br> in the HTML output. But the browser doesn't render it, so it isn't noticeable.

<3


Question about the variant regions and LCR

Hi, I have taken a look into the commands in the log folder, and found that bcbio uses bedtools subtract command to remove the regions overlapped in LCR. However, the variant regions displayed in the command differ a litter from those defined in the bed file by variant_regions paramter. For example, the command for chr 2 I found the command is bedtools subtract -nonamecheck -a /ngs/zhengu/liuqf/final/vardict/chr2/liuqingfeng-chr2_29220713_211424290-regions.bed -b /bio/bcbio/genomes/Hsapiens/hg38/coverage/problem_regions/repeats/LCR.bed.gz > /ngs/zhengu/liuqf/final/bcbiotx/tmpK2Dw2J/liuqingfeng-chr2_29220713_211424290-regions-nolcr.bed, while my regions defined in the bed file related to chr2 is

chr2    29192773        29921566
chr2    211375716       212538841

The start coordinate 29220713 locates after the first region of interest, while 211424290 locates in the middle of the second region of interest. What is the logic for the determinat of the regions? Is there any problem of my running? Thanks in advance.

Thanks for the question and sorry about the issues. The documentation describes the intentions of the LCRs and links to the original paper where they're derived:
https://bcbio-nextgen.readthedocs.io/en/latest/contents/configuration.html?highlight=lcr#analysis-regions
It's worth manually checking the LCR regions (/bio/bcbio/genomes/Hsapiens/hg38/coverage/problem_regions/repeats/LCR.bed.gz) to see if they're doing the removal, or if you sample doesn't have coverage in the regions of interest.
If the LCRs falling into your regions of interest, you don't need to exclude them and can avoid adding them to exclude_regions which should hopefully avoid this. Hope this helps.

@chapmanb
Thanks for your prompt reply. I removed the exclude_regions parameter, i.e. using no LCRs regions, and rerun the pipeline. I found the chr2 are still split into three sub-region in the variant calling process. They are:

chr2_0_29209876
chr2_29220713_211424290
chr2_211665307_242193529

I also found that the coordinates of these regions are same to those of the running used LCRs. I guess this depends on my sample coverage or other things.

Thanks for investigating. bcbio picks splits based on coverage calculations so it does sound like there is no coverage in some regions you might be expecting. You could look at either the bcbio coverage calculations from mosdepth or the BAM file itself in a viewer like IGV to confirm that it's doing the right thing. Let us know if you find any issues and hope this helps for your analysis.

Asked and answered.


RE: Nativescript plugin background-http produces issue "error during upload"

Hi, I am testing nativescript-background-http to test upload a picture file to server.
I test using physical mobile device. Below is the coding file
==================================start of a.component.ts================================
import { Component } from '@angular/core';
import * as bghttp from "nativescript-background-http";
import * as fs from "file-system";

@Component({
    moduleId: module.id,
    template: "<Button text='Upload File' (tap)='uploadFile()'></Button>"
})
export class aComponent {
    public session = bghttp.session("image-upload");

    uploadFile() {
        const filepath: string = "/data/user/0/org.nativescript.Groceries/cache/img_by_sj_1493113215112.jpg";
        const filename: string = "img_by_sj_1493113215112.jpg";

        let fileExist = fs.File.exists(filepath);
        // confirm file exists.
        console.log("file exist? ", fileExist);
        let request = {
            url: "http://it-enable.net:9191/file",
            method: "post",
            headers: {
                "Content-Type": "application/octet-stream",
                "File-name": filename
            },
            description: "{ 'uploading': '" + filename + "' }"
        }

        let task = this.session.uploadFile(filepath, request);
        task.on("progress", this.logEvent);
        task.on("error", this.logEvent);
        task.on("complete", this.logEvent);

    }
    logEvent(e) {
        console.dump(e);
    }
}

==================================end of a.component.ts================================
==================================start of package.json================================
{
  "name": "typescript anuglar redux",
  "version": "0.0.1",
  "description": "NativeScript Application",
  "license": "SEE LICENSE IN <your-license-filename>",
  "readme": "NativeScript Application",
  "repository": "<fill-your-repository-here>",
  "nativescript": {
    "id": "org.nativescript.Groceries",
    "tns-android": {
      "version": "2.5.0"
    }
  },
  "dependencies": {
    "@angular/common": "2.4.3",
    "@angular/compiler": "2.4.3",
    "@angular/core": "2.4.3",
    "@angular/forms": "2.4.3",
    "@angular/http": "2.4.3",
    "@angular/platform-browser": "2.4.3",
    "@angular/platform-browser-dynamic": "2.4.3",
    "@angular/router": "3.4.3",
    "@ngrx/core": "^1.2.0",
    "@ngrx/effects": "^2.0.2",
    "@ngrx/store": "^2.2.1",
    "email-validator": "^1.0.7",
    "file-system": "^2.2.2",
    "nativescript-angular": "1.4.0",
    "nativescript-background-http": "^2.5.1",
    "nativescript-camera": "0.0.8",
    "nativescript-drawingpad": "^1.1.2",
    "nativescript-social-share": "^1.3.2",
    "nativescript-telerik-ui-pro": "file:F:\\NativeScript\\Packages\\nativescript-ui-pro.tgz",
    "nativescript-theme-core": "~1.0.2",
    "ramda": "^0.23.0",
    "reflect-metadata": "~0.1.8",
    "rxjs": "~5.0.1",
    "tns-core-modules": "2.5.0"
  },
  "devDependencies": {
    "babel-traverse": "6.4.5",
    "babel-types": "6.4.5",
    "babylon": "6.4.5",
    "eslint": "^3.19.0",
    "lazy": "1.0.11",
    "nativescript-dev-android-snapshot": "^0.*.*",
    "nativescript-dev-typescript": "^0.3.5",
    "typescript": "~2.1.0",
    "zone.js": "~0.7.2"
  }
}

==================================end of package.json================================
I am using the node.js restify to accept the file. I have tested using Postman and it works file. The code of the restify is as below
==================================start of restify index.js================================
var restify = require('restify');
var fs = require('fs');
var os = require('os');
var server = restify.createServer({
    name: 'software-manufacture-backend-file',
    version: '0.1.0'
});
var Throttle = require("stream-throttle").Throttle;
var outDir = "/mnt/diskc/p/restify-file/uploads/";
server.use(restify.acceptParser(server.acceptable));
server.use(restify.CORS());
server.use(restify.queryParser());
server.use(restify.gzipResponse());
server.use(function (req, res, next) {
    console.log('it reach the restify-file api without body parser');
    return next();
});
server.get('/test', function (req, res, next) {
    res.send(200, 'SUCCESS');
    res.end;
    return next();
});
server.post('/file', function (req, res, next) {
    console.log(req.params);
    var fileName = req.headers["file-name"];
    console.log("req.headers are", req.headers);
    var logger = console;
    logger.log(req.method + "Request! Content-Length: " + req.headers["content-length"] + ", file-name: " + fileName);
    logger.dir(req.headers);
    var out = outDir + "upload-" + new Date().getTime() + "-" + fileName;
    logger.log("Output in: " + out);
    var total = req.headers["content-length"];
    var current = 0;
    var shouldFail = req.headers["should-fail"];
    req.pipe(new Throttle({ rate: 1024 * 2048 })).pipe(fs.createWriteStream(out, { flags: 'w', encoding: null, fd: null, mode: 0666 }));
    req.on('data', function (chunk) {
        current += chunk.length;
        if (shouldFail && (current / total > 0.25)) {
            logger.log("Error ");
            var body = "Denied!";
            res.send(408, "Die!", { "Content-Type": "text/plain", "Content-Length": body.length, "Connection": "close" });
            res.end();
            shouldFail = false;
            logger.log("Terminated with error: [" + out + "]: " + current + " / " + total + "  " +
                Math.floor(100 * current / total) + "%");
        }
        else {
            logger.log("Data [" + out + "]: " + current + " / " + total + "  " + Math.floor(100 * current / total) + "%");
        }
    });
    req.on('end', function () {
        logger.log("Done (" + out + ")");
        var body = "Upload complete!";
        res.send(200, "Done!", { "Content-Type": "text/plain", "Content-Length": body.length });
        res.end();
    });
    req.on('error', function (e) {
        logger.log('it reach the file received error!');
        logger.log(e);
    });
});
process.on('uncaughtException', function (err) {
    console.log('uncaught Exception is ', err);
});
server.listen(9191, function () {
    console.log('%s listening at %s', server.name, server.url);
});

==================================end of restify index================================
==================================start of restify packson.json================================
{
  "name": "restify-file",
  "version": "0.0.1",
  "description": "It only accepts files",
  "main": "index.js",
  "author": "Sam Liaw<EMAIL_ADDRESS>  "license": "MIT",
  "dependencies": {
    "ramda": "^0.23.0",
    "restify": "^4.3.0",
    "stream-throttle": "^0.1.3"
  }
}

==================================endof restify packson.json================================
When I use the Postman, I provide the following attirbutes
Method: Post
URL: http://it-enable.net:9191/file
Header: {"Content-Type":"application/octet-stream"}
Attached a picture file.
If the file is uploaded successfully, I can see the response of "Done!".
When I run the project in physical mobile device, I hit the error "error during upload." When I look at backend restify, I find that the nativescript-background-http hits error before it sends the file to backend restify. This is because the backend restify doesn't inidicate it has receives any file.
I do test this whole afternoon but to no vail. I copy the source code that people have claim successful executing but it doesn't work for me. There is no detail error code so I am not able to figure what is wrong.
Any suggestion or method  is welcomed.

This issue was moved to NativeScript/nativescript-background-http#61

Hi,
I spend some more time to debug and finally confirm what cause the issue. Please look at the code in the component. I simply change the lowercase "post" to all uppercase "POST" and it works perfectly.
hopefully this will help other people who face similar issue like me.
    let request = {
        url: "http://it-enable.net:9191/file",
        method: "post", //<----- change post to POST solve the issue
        headers: {
            "Content-Type": "application/octet-stream",
            "File-name": filename
        },
        description: "{ 'uploading': '" + filename + "' }"
    }


fix logging

Change-Id: I06e9edfc8e13d245442498a9c71b489f341de669

Codecov Report

Merging #222 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #222   +/-   ##
=====================================
  Coverage      80%    80%
=====================================
  Files          19     19
  Lines        1591   1591
=====================================
  Hits         1268   1268
  Misses        208    208
  Partials      115    115

Impacted Files
Coverage Δ

adapter/analytics/staging.go
67% <100%> (ø)
:arrow_up:

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 899f0bf...79efa82. Read the comment docs.


+$+Tummy Tear Dark Private Viral Video Link

Tummy Tear Dark Leaked Video Viral On Social Media X TikTok Trending
17 seconds ago-L𝚎aked Video Tummy Tear Dark Original Video Viral Video L𝚎aked on X Twitter Telegram
Tummy Tear Dark Original Video video took the internet by storm and amazed viewers on various social media platforms. Minahil Malik, a young and talented digital creator, recently became famous thanks to this interesting video.


Fog error in animated ModelInstance

If i have a animated modelInstance, the fog don't work correctly. Looks like it calculates the postion on [0,0,0] not relative to the camera. In others no animated ModelInstance, it works normally.

Please include the information required to reproduce the issue you're reporting. See https://github.com/libgdx/libgdx/wiki/Getting-Help

I try to reproduce this error in one separate class to send to you. But i can't. I think the error is on my game. Thanks for attention.


add spelling bee

This is a list of video games. Such browser-based games are not targeted content. Sorry, but I will not merge this pull request.

OK no worries, just saw the puzzle section and thought it might fit there. Thanks for reviewing!


Rerender

and update recipe.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


chore(main): release 5.0.0

:robot: I have created a release beep boop
5.0.0 (2022-12-30)
⚠ BREAKING CHANGES

requires node 16

Features

add checkSatisfiesVersionsInDependency (59cb1d2)
deps: update dependency chalk to v5 (#219) (b1ac9b1)

Miscellaneous Chores

drop node 14 (3d4c7f1)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/christophehurpeau/check-package-dependencies/releases/tag/v5.0.0 :sunflower:


Fix duplicate  <xs:complexType name="Layout">

[Current coverage][cc-pull] is 76% (diff: 100%)

Merging [#1557][cc-pull] into [master][cc-base-branch] will decrease coverage by <1%

@@             master      #1557   diff @@
==========================================
  Files           270        270
  Lines         16318      16318
  Methods        2611       2611
  Messages          0          0
  Branches       1775       1775
==========================================
- Hits          12432      12420    -12
  Misses         3483       3483
- Partials        403        415    +12

[][cc-pull]

Powered by Codecov. Last update [53b01ea...0b3d281][cc-compare]
[cc-base-branch]: https://codecov.io/gh/NLog/NLog/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/NLog/NLog/compare/53b01eac36061eb0e3f199ab21d5f768123ed116...0b3d28102e678ca4bb0a5f356dadc03ac23ac313?src=pr
[cc-pull]: https://codecov.io/gh/NLog/NLog/pull/1557?src=pr


Network policy which allows endpoint ping local node do not work

General Information

Cilium version (1.8.2 67089eaef 2020-08-28T18:36:23+08:00 go version go1.14.6 linux/amd64)
Kernel version (4.19.117 x86_64 GNU/Linux)
Orchestration system version in use (Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.6")
Link to relevant artifacts (policies, deployments scripts, ...)
Generate and upload a system zip:
cilium-sysdump-latest.zip
cilium-sysdump-20200904-173839.zip

How to reproduce the issue

create pod A on node 1, config policy enforce mode = default
label pod A with policy=whitelist
3 create a policy as :

apiVersion: "cilium.io/v2"
kind: CiliumNetworkPolicy
metadata:
  name: "alow-44"
spec:
  endpointSelector:
    matchLabels:
      k8s:policy: whitelist
  egress:
  - toCIDR:
    - node1 ip

4 ping node 1 from pod A. Pod A could not ping node 1

This behavior is expected. To match the host, you need to use the host entity with toEntity: https://docs.cilium.io/en/latest/policy/language/#entities-based.
This limitation is documented in the CIDR-based policy section: https://docs.cilium.io/en/latest/policy/language/#ip-cidr-based:

Conversely, CIDR rules do not apply to traffic where both sides of the connection are either managed by Cilium or use an IP belonging to a node in the cluster (including host networking pods). This traffic may be allowed using labels, services or entities -based policies as described above.

@lrouter does that fixes your issue?

@aanm @pchaigno yes. thanks.


Running assertj generator on JDK 11

I am trying to build a library with OpenJDK 11 with the maven-assertj-generator plugin enabled. However, the plugin succeeds, but generates non-compiling code.
Has anyone had any succes on running the assertj-generator with OpenJDK 11?
Generated code:
/**
   * Verifies that the actual Melding's referenties contains the given interface Referentie elements.
   * @param referenties the given elements that should be contained in actual Melding's referenties.
   * @return this assertion object.
   * @throws AssertionError if the actual Melding's referenties does not contain all given interface Referentie elements.
   */
  public MeldingAssert hasReferenties(interface Referentie... referenties) {
    // check that actual Melding we want to make assertions on is not null.
    isNotNull();

    // check that given interface Referentie varargs is not null.
    if (referenties == null) failWithMessage("Expecting referenties parameter not to be null.");

    // check with standard error message, to set another message call: info.overridingErrorMessage("my error message");
    Iterables.instance().assertContains(info, actual.getReferenties(), referenties);

    // return the current assertion for method chaining
    return this;
  }

Wrong line:
public MeldingAssert hasReferenties(interface Referentie... referenties) {
Expected line:
public MeldingAssert hasReferenties(Referentie... referenties) {
To solve the issue, I tried building the assertj-assertions-generator on OpenJDK 11, but I also ran into all kinds of trouble.

Tried to build a latest version of com.google.testing.compile:compile-testing
Tried to upgrade Guava
Needed to upgrade to JDK 8 source code
Ran into troubles running JUnit Theories

The generator has not been tested on JDK 11 indeed.
It looks like the issue is related to introspection, there might have been differences with JDK 11 as per finding type names.
I haven't much time to spend on the generator but I'm happy to review PRs if you feel like fixing the issue.

It looks like JDK 11 is not the issue here, since I have the same issue with a JDK 8 installed.
I have made it work with the assertj-assertions-generator-maven-plugin version at 2.0.0 and assertj-core at 3.9.0 (higher version gives other errors) for now.

@NeoJustin thanks for the feedback!


ReflectionProbes don't work predictably in VR when rendering with GLES3

Godot 3.3 Stable
Windows 10, GLES3, Windows Mixed Reality, running on GTX 1060
Reflections via ReflectionProbes are not consistent with the viewport when running ARVR on GLES3.

Steps to reproduce:
Using OpenVR addon, add the necessary script to set the Viewport to ARVR. Place MeshInstances and make a mesh's material highly reflective. Add a reflection probe.
Within the viewport, reflections of surrounding geometry look correct. When running in ARVR, the reflection will be dark and indistinct.
The ReflectionProbe is not completely absent in VR, as some ambient lighting effects seem to translate correctly.
I found reflections work properly with GLES2.
Minimal Reproduction Project:
gdmrp reflectionprobe arvr.zip

I can confirm this. I think it happens because the reflections are captured before the scene is actually loaded, leading to it not actually capturing the reflections

I think the only reasonable solution would be to add the option the prebake the reflection map into a resource file rather than capture it on scene loading

I think the only reasonable solution would be to add the option to prebake the reflection map into a resource file rather than capture it on scene loading

It works in GLES2, can't we fix it in GLES3 too?

If it doesnt happen in GLES2 I'm probably wrong about my theory

If it doesnt happen in GLES2 I'm probably wrong about my theory

I'm pretty sure setting the update mode to Constant instead of Once doesn't improve the situation either.