Support for Ripple effect on markers

Use case
I have to add ripple effects to specific types of markers in the map to easily identify from others but I am unable to do it as there is no support available for it. It is also not possible to add any widget in place of markers to customise.

Proposal
I want creators to add ripple/pulse animation effect on multiple markers on the map. It would be very useful for many developers as this is very demanding feature by many clients.

Hi @spatel2212
Can you please provide an example where the Ripple effect is used on markers?  google_maps_flutter uses platform view to render to native maps so if it support native, we would it possible to add in the package

Hi @TahaTesser thanks for your quick reply.
PFA sample recording of ripple effect on marker. Sorry for the poor quality, it was recorded on simulator so.
https://user-images.githubusercontent.com/76149392/119968912-8ffe3500-bfcb-11eb-8f4e-d3727a7e9f17.mov

any updates on this feature request @TahaTesser ?

any updates on this feature request @TahaTesser ?

Unfortunately no updates on this right now.
You will see the issue is assigned to someone or a PR is linked when there is any new update for this issue.

In recent version of flutter, other packages like flutter_animarker and google_map_marker_animation both stopped working.
If anyone have any workaround for this. Please help.

any update?

@ps6067966 hi, how did u later implement it?

any update regarding this?

update this please

update?


New install failure reason: NoWorkerNodesReady

OSD-13511
Investigating AuthenticationOperatorDegraded, which is currently the
fifth-most common install failure, can be annoying because install
failures are not caused by the Authentication operator failing; instead
it is a symptom of another failure. This PR represents a repeatable
finding where a log line indicating that 0 worker nodes have joined the
cluster causes AuthenticationOperatorDegraded.
Returning this instead will point us in a better direction to start
investigating the install failure. If we find that it makes up all cases
of AuthenticationOperatorDegraded we can remove that failure reason.
This error code is very similar to AWSNoWorkerNodes and
GCPNoWorkerNodes, however based on our history neither of them have
triggered for the past 90 days (and anecdotally even longer than that).
I suspect the regex is no longer valid since they were originally
created and this new regex can be their replacement.
cc @iamkirkbater @AlexVulaj

/retest

/test e2e


Passing empty roles list to snowflake_schema_grant

NOOB here, first post sorry if I break rules.
I was wondering if there is a way to pass roles with a list i.e roles = [] in the snowflake_schema_grant. Currently, I have a snowflake_schema_grant resource for granting ALL and one for granting USAGE which I'm driving from a locals structure. Following something like this:
locals {
  schemas = {
    "schema1" = {
      database    = var.snowflake_database_name
      usage_roles = ["ROLE1"]
      all_roles   = ["ROLE1"]
    }
    "schema2" = {
      database    = var.snowflake_database_name
      usage_roles = ["ROLE2"]
      all_roles   = ["ROLE2"]
    }
  }
}

resource snowflake_schema_grant schema_grant_usage {
  for_each      = local.schemas
  schema_name   = each.key
  database_name = each.value.database
  privilege     = "USAGE"
  roles         = each.value.roles
}

resource snowflake_schema_grant schema_grant_all {
  for_each      = local.schemas
  schema_name   = each.key
  database_name = each.value.database
  privilege     = "ALL"
  roles         = each.value.roles

If I wanted schema2 to have no roles that have ALL privileges, ideally it would be nice to just set schema2.all_roles = []. However, I am prevented by the following:
https://github.com/chanzuckerberg/terraform-provider-snowflake/blob/70bf4423b68ac4aed526cf08edcb5a66f6ea930a/pkg/resources/grant_helpers.go#L180

We are closing this issue as part of a cleanup described in announcement. If you believe that the issue is still valid in v0.89.0, please open a new ticket.


Molecule Query Notebook issue and stereochemistry

Wonderful tool! Thanks for the hard work here.  In working with the notebooks, I noticed the following issues that I hope I can help address.
The problem arises when using the molecule_query.ipynb to attempt to locate certain molecules as a demonstration.
For example, when attempting to locate Molnupiravir which is in US11331331 (claims 1-9) and is also part of PatCID using the molecule_query.ipynb with SMILES:
CC(C)C(=O)OC[C@@H]1[C@H]([C@H]([C@@H](O1)N2C=CC(=NC2=O)NO)O)O
The notebook fails in the last cell at:
# Get page index of query molecule
for figure in patent_entry["figures"]:
    if not("smiles" in figure):
        continue
    if (figure["smiles"]["value"] == query_smiles):
        page_index = figure["page"]

# Convert pdf to page image
pages = convert_from_path(os.getcwd() + f"/../data/pdfs/{query_patent}.pdf", dpi=200, first_page=page_index, last_page=page_index)
pages = [None]*(page_index-1) + pages + [None]*(len(patent_entry["page-dimensions"])-page_index)

with:
NameError: name 'page_index' is not defined
Because there is no matching entry among the two .jsonl data files.
If I manually grep it fortuitously matches:

There appear to be important differences in the SMILES entries in: data/patcid/patcid_patent_to_molecules_{office}.jsonl
versus the entries in: data/patcid/patcid_molecule_to_patents.jsonl, at the very least includes the use of case in designating bond order in aromatic rings.
In addtion there could be lost stereochemistry resulting from use of grep and a SMILES string containing [@]'s without accounting for these characters.
Note, if I change the "query_smiles" in the last cell of the notebook to molnupiravir with the stereochemistry removed: query_smiles_mod = "CC(C)C(=O)OCC1OC(N2C=CC(NO)=NC2=O)C(O)C1O" it executes and finds the molecule in the document:

Which as you can see has the stereochemistry that is absent from the modified SMILES query.  I believe MolGrapher can extract this.
My thought is to instead use a data query structure incorporating InChi or InChiKey.  As you can see below, InChiKey would find the molecule by truncating the stereochemistry terms (2nd block):
patcid_molecule_to_patents.jsonl:3247652:
"HTNPEHXGEKVIHG-UHFFFAOYSA-N"
vs.
"HTNPEHXGEKVIHG-QCNRFFRDSA-N"

Hi @loopy321,
Thank you for your interest in PatCID!
As you pointed out, there is no stereo-chemistry stored in the current version of PatCID.
I modified the notebook molecule_query.ipynb to clarify this.
Also, you can now use the query_smiles = CC(C)C(=O)OC[C@@H]1[C@H]([C@H]([C@@H](O1)N2C=CC(=NC2=O)NO)O)O
and its stereo-chemistry will be automatically removed before searching in the dataset.
You are correct that MolGrapher could be configured to recognize stereo-chemistry, but it was not done when creating PatCID.


Don't implicitly infer test context.

Right now we infer the dependency context from whether or not we think the code is running in a test context. This causes problems when running tests on an application target, because the entry point of the application will actually execute, causing live dependencies to be used in a test context. Those failures bleed over to the test target. This is only an issue when testing application targets. Libraries and SPM modules work just fine.
Now technically it is just really bad that Xcode even runs the entry point of the application. This can cause you to accidentally execute API requests, track analytics, write data to disk, etc. without you knowing. TCA is just warning you that this is happening by yelling loudly and failing the test suite.
I'm starting to think it's not worth implicitly inferring the test context. If we stopped doing that, then the test host could go back to secretly using live dependencies without it failing the test suite.
This has come up a number of times, in both discussions and on a Slack.

Typically this would be handled by "turning off" your app when it's launched as a test host. Rather than breaking this nice behavior for that case, couldn't you just recommend the other solution? TCA could even help out by exposing the same "isTest" condition that is used internally.

Typically this would be handled by "turning off" your app when it's launched as a test host.

@jshier do you mean that this is a setting in Xcode to do this, or are you suggesting finding a way to omit your view from executing in the entry point?
If the latter, then technically this can be done using XCTestDynamicOverlay (which comes transitively with TCA) by doing this:
import XCTestDynamicOverlay

@main
struct SearchApp: App {
  var body: some Scene {
    WindowGroup {
      if !_XCTIsTesting {
        …
      }
    }
  }
}

Rather than breaking this nice behavior for that case, couldn't you just recommend the other solution? TCA could even help out by exposing the same "isTest" condition that is used internally.

FWIW, the TestStore automatically sets up .test as the context. So I'm not aware of any situation this actually breaks. It may break for anyone using Dependencies outside TCA, in which case we plan on extracting it to a separate library with its own test helpers very soon.

Doing it manually is what I meant, but an official setting would be nice. It's good that the change doesn't break anything, but might this feature be a good way to audit my app startup in testing to ensure I'm not calling anything? Perhaps there could be a version that allows live instances but produces a runtime warning?

Leaving it the way it is does have the nice side benefit of proving that the launch of your app is not executing live dependencies. But, it's a bit limited since it's only proving it for the duration of how long the test takes to executes, which may be a small amount of time.
If we did decide to move forward with this API you would be able to recapture the current behavior with something like this in your entry point:
RootView(
  store: Store(
    initialState: …,
    reducer: RootReducer()
      .dependency(\.context, _XCTIsTesting ? .test : .live)
  )
)

Just as a note, we've reverted this behavior with the release of swift-dependencies. We believe that defaulting to the test context in tests is required for vanilla apps using the library to fail properly without extra work.
This means that if you do run your tests in an app host, the app must take care to set its context (or omit the runtime entirely during test runs).
/cc @TicTocCroc

@stephencelis
What would be your preferred solution to fix the interference of the Tests with your App host running in parallel?
For me personally, it seems that omitting the launch of the runtime completely by using _XCTIsTesting, currently is the best solution, right? Overwriting the context has the disadvantage of dependencies running against a live environment so that they might call live APIs etc.

@iwt-sebastian-boldt Yup! And we document this here: https://pointfreeco.github.io/swift-dependencies/main/documentation/dependencies/testing/#Testing-gotchas


Feature Request: Add Icon Support

Display filetype icons like the built-in pickers.

Implemented in https://github.com/nvim-telescope/telescope-frecency.nvim/pull/31


Avoid creating an unbound number of atoms when deserializing

I have not checked that this does not break anything. The change assumes that

the structs have all been loaded (which is probably safe to assume) and so the atoms for the field names are already there
the subsequent parsing ignores keys which do not equal an expected struct field name (Probably true in all cases)
the Jason version that Nadia depends on supports the option used (did not check)

This could in theory use Jason.decode!(body keys: :atoms!) but that would crash when TG adds a field.
The code as-is is only secure when talking to a trusted endpoint. Using an untrusted endpoint exposes the user of the library to a potential DDOS attack by exhausting VM memory.
Since the endpoint is configurable, this PR should improve security. Additionally, users might be tempted to wire webhook payload parsing through the existing code, which would expose a security risk over the webhook endpoint.

Sorry for the incomplete fix and the whitespace diff. Hastily opened this via the GH edit function...

Hi,
@schnittchen Can you help me with it? please open PR here:
https://github.com/etroynov/telegraph

I've abandoned Nadia for https://github.com/schnittchen/cablegram


Create a resource that describes the Soroban<>Stellar relationship

The Stellar<>Soroban interop is currently described in out-of-date CAPs and in the code. We need a resource that gathers all this information. Some topics:

Interop scope: wrapped assets and shared accounts
Interop out-of-scope: DEX/AMMs/etc
FAQ: where should I issue my assets? what should wallets default to? etc.

FAQs:

Should wallets hold value in Stellar balance or Soroban balance? When should they transfer them between them? Should they do so automatically? Where should residual funds be sent?
Should wallets show two balances or a single combined balance?

What classic functions do I have access to from Soroban (what can I change or influence in the classic Stellar world from my smart contract)?
If someone wanted to build a Soroban DApp and have payouts to participant accounts, how would they do this?
Can I manage a classic asset from Soroban?

Can I send payments to a Stellar account that doesn't exist on Stellar using Soroban? Yes, yes you can.

Can I use a Stellar classic asset inside a soroban contract, or do I need to convert the asset into a Soroban token first?
If someone has issued assets on Stellar-classic, can the issuer force migration of their asset to Soroban? Maybe making it auth_required and never authorizing it? 🤔
Do Stellar classic accounts exist in Soroban, or will soroban have special kinds of accounts?
Can anyone check how many Soroban tokens any account has?
If an asset already has good traction in Stellar classic and the issuer wants to use soroban, what are the possible routes? Should we recommend they continue with the Stellar classic asset and spin off a parallel new token in Soroban?
Can a token created from Contract A be used in a new Contract B?


Simplified UIViewController extension for layout guides

As far as I know, there's no case where you should be using the top of the topLayoutGuide or the bottom of the bottomLayoutGuide, is there?

@raylillywhite there may be in the future, while typically the top of the top and bottom of the bottom would always be the view that may not be the case always.
Are you experiencing any oddities by using either of these or just feel it's ambiguous/duplicated?

No, I'm not experiencing any problems (besides that I autocompleted to the wrong one without noticing). I just thought that the fact that these layout guides have a non-zero height was merely an implementation artifact, and when I was first learning auto layout, it was confusing that I had to specify that I was pinning something to the bottom of the top layout guide. So I thought that removing that distinction would be a helpful abstraction, and I couldn't think of any way that the top of the topLayoutGuide would be meaningful.
I understand that this breaks backwards compatibility, so that alone might be enough reason not to merge this. But if you agree that the simplification could be worthwhile, let me know and I'll resolve the test failures. Otherwise, feel free to close this.

@raylillywhite I'm going to go ahead and leave these in there, I know it's a bit of confusion but they may be useful in some scenarios we're not considering ( Apple does leave them in there for some reason or another ).


moment to compare times in am and pm

Description of the Issue and Steps to Reproduce:
Please include the values of all variables used.
Environment:
Examples: Chrome 49 on OSX, Internet Explorer 10 on Windows 7, Node.JS 4.4.4 on Ubuntu 16.0.4
Both the browser and the OS are important to us, particularly if you have an unsual environment like an IOT application.
Other information that may be helpful:

The time zone setting of the machine the code is running on
The time and date at which the code was run
Other libraries in use (TypeScript, Immutable.js, etc)

If you are reporting an issue, please run the following code in the environment you are using and include the output:
console.log( (new Date()).toString())
console.log((new Date()).toLocaleString())
console.log( (new Date()).getTimezoneOffset())
console.log( navigator.userAgent)
console.log(moment.version)

Ensure your issue is isolated to moment. Issues involving third party tools will be closed unless submitted by the tool's author/maintainer.

Thanks for opening this request.
This is a great question for Stack Overflow.


Fixed helm bash complete

helm version >= 2.4.0:
helm completion bash
helm version < 2.4.0:
helm completion

lgtm, would you be able to squash your commits into a single one?


Integrate stdlib docs into mdBook documentation

This PR fills out the standard library section of the mdBook documentation. For v0.1 release of standard library will include documentation only for the following modules:

math::u64
crypto::hashes::blake3
crypto::hashes::sha256

The other modules we currently have in the library will remain there, but will be undocumented for now (in the future, it is probably good to add unstable marker to these modules somehow).
Other things changed in this PR:

Updated description for comments.
Minor fixes in std::sys module.

I forgot to add one other comment, which is that the operations in the u64 module are not ordered consistently, which makes them harder to read. For example, the docs currently start with:

overflowing_add
wrapping_add
checked_add
wrapping_sub
checked_sub
overflowing_sub

I forgot to add one other comment, which is that the operations in the u64 module are not ordered consistently, which makes them harder to read.

Yep - noticed this too. I sorted these manually for now - but we'll probably need to come up with a way to sort them automatically in a consistent order somehow in the future.


Spacing in uninstall file path cause error

Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.

[x] are reporting a bug others will be able to reproduce and not asking a question. If you're not sure or want to ask a question do so on our Discourse: https://discourse.brew.sh
[ ] ran a brew command and reproduced the problem with multiple formulae? If it's a problem with a single, official formula (not cask) please file this issue at Homebrew/homebrew-core: https://github.com/Homebrew/homebrew-core/issues/new. If it's a brew cask problem please file this issue at https://github.com/caskroom/homebrew-cask/issues/new. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap.
[x] ran brew update and can still reproduce the problem?
[ ] ran brew doctor, fixed all issues and can still reproduce the problem?
[ ] ran brew config and brew doctor and included their output with your issue?

To help us debug your issue please explain:

What you were trying to do (and why)
Trying to upgrade logitech-options cask

brew cask upgrade logitech-options

What happened (include command output)
Error: No such file or directory - /Applications/Utilities/LogiMgr

==> Upgrading 1 outdated package, with result:
caskroom/drivers/logitech-options 6.80.384
==> Satisfying dependencies
==> Downloading https://www.logitech.com/pub/techsupport/options/Options_6.80.384.zip
Already downloaded: /Users/limyunkai19/Library/Caches/Homebrew/Cask/logitech-options--6.80.384.zip
==> Verifying checksum for Cask logitech-options
==> Starting upgrade for Cask logitech-options
==> Running uninstall process for logitech-options; your password may be necessary
==> Running uninstall script /Applications/Utilities/LogiMgr Uninstaller.app/Contents/Resources/Uninstaller
Error: No such file or directory - /Applications/Utilities/LogiMgr
Follow the instructions here:
  https://github.com/caskroom/homebrew-cask#reporting-bugs
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/2.3.0/open3.rb:199:in `spawn'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/2.3.0/open3.rb:199:in `popen_run'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/2.3.0/open3.rb:95:in `popen3'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/system_command.rb:88:in `each_output_line'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/system_command.rb:25:in `run!'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/system_command.rb:14:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/abstract_uninstall.rb:205:in `uninstall_script'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/abstract_uninstall.rb:59:in `block in dispatch_uninstall_directives'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/abstract_uninstall.rb:56:in `each'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/abstract_uninstall.rb:56:in `dispatch_uninstall_directives'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/artifact/uninstall.rb:7:in `uninstall_phase'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:403:in `block in uninstall_artifacts'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/2.3.0/set.rb:674:in `each'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.3/lib/ruby/2.3.0/set.rb:674:in `each'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:400:in `uninstall_artifacts'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:362:in `start_upgrade'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/upgrade.rb:59:in `block in run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/upgrade.rb:29:in `each'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/upgrade.rb:29:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/abstract_command.rb:35:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:98:in `run_command'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:168:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:132:in `run'
/usr/local/Homebrew/Library/Homebrew/cmd/cask.rb:8:in `cask'
/usr/local/Homebrew/Library/Homebrew/brew.rb:100:in `<main>'

What you expected to happen
The upgrade to be success.

Step-by-step reproduction instructions (by running brew commands)
Installing and uninstalling logitech-options cask (or other cask with a space in file path in executable) will cause the problem.

brew cask install logitech-options
brew cask uninstall logitech-options

After looking on the error call stack trace, and trying to debug myself, I believe that the error comes from the shell commands escaping in the files brew/Library/Homebrew/cask/lib/hbc/system_command.rb.
I fix the error by escaping the executable string in https://github.com/Homebrew/brew/blob/067b9c9e88b617661849c4d77c291a24be32e1af/Library/Homebrew/cask/lib/hbc/system_command.rb#L88
Change to
        Open3.popen3({ "PATH" => path }, executable.shellescape, *args, **options)

And then, I am able to uninstall the logitech-options cask successfully.

ran a brew command and reproduced the problem with multiple formulae? If it's a problem with a single, official formula (not cask) please file this issue at Homebrew/homebrew-core: https://github.com/Homebrew/homebrew-core/issues/new. If it's a brew cask problem please file this issue at https://github.com/caskroom/homebrew-cask/issues/new. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap.

As mentioned: please report to brew cask.

I believe this is the correct place to report as escaping the string in the cask ruby script will cause the file path check to fail
Error: uninstall script /Applications/Utilities/LogiMgr\ Uninstaller.app/Contents/Resources/Uninstaller does not exist.

and I manage to make it work by changing some code in this repository.
Just trying my best to report bug. Hope that this issue is inspected more carefully.

@limyunkai19 I believe this will be addressed by https://github.com/Homebrew/brew/pull/3865 when the next tag is released.


Please do go ahead and change it to whatever makes sense to you and update the docs.


Update how-to-authenticate-an-imap-pop-smtp-application-by-using-oaut…

The article is updated as per Task 6224483, thank you!

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

File
Status
Preview URL
Details

docs/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth.md
:white_check_mark:Succeeded
View

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


Include app URL to the project

@webknjaz All good? Can we merge this branch to master?

Rebase it and get rid of unrelated commits.

@webknjaz Done.

@webknjaz Can we to merge the PR?

@webknjaz Maybe close this PR and to merge just https://github.com/kpi-web-guild/django-girls-blog-serhii73/pull/25 ?

@webknjaz But I can't merge the PR in master, because Travis is red.
blog/urls.py:L   7:(no-member) Module 'blog.views' has no 'post_list' member (C 19), ::E1101
I think I need to unite https://github.com/kpi-web-guild/django-girls-blog-serhii73/pull/24 with https://github.com/kpi-web-guild/django-girls-blog-serhii73/pull/25 .
For example, if I here I need to run git merge feature/6/django_views or to do the opposite?

That's the whole point to having Travis.

The approval means that I agree with what I see in PR, it doesn't mean that it is safe to merge. And review is about high-level things, which are not checked by robots.

@webknjaz What do you recommend to do?

@webknjaz What do you recommend to do?

Merge #25

(to master!)

@webknjaz done


fix of installing xhprof

I completed the 3 steps below:

[x] I've read the Contribution Guide.
[x] I've updated the documentation. (refer to this for how to do so).


Create a CI job to run OpenShift conformance tests against crc

After discussing with OpenShift folks, we conclued that we can call anything OpenShift if conformance tests are passing.
CRC needs to pass all conformance tests. Cluster profile will help fixing failing tests.

Closing this in favor of https://github.com/code-ready/crc/issues/2457 and CI job currently running k8s conformance tests.


add flush and drain during init and homing

Seems like everything works without flushing/draining.

Fixed in v0.4.0


Added order.html and order css files

So you can make the index and webpack accordingly

our menu.html also has ordering in it...


Reorder alphabetically - video, wallpaper, window management, icon links

Reordering alphabetically.

          1 Warning

:warning:
Too many changes (when adding, please keep it to one project per Pull Request)

  Generated by :no_entry_sign: Danger


Left menu does not expand sections

Problem
After updating to sphinx-rtd-theme==1.3.0 I've noticed the page sections are no more expanded in the left menu:

old: https://did.readthedocs.io/en/stable/overview.html#format
new: https://did--321.org.readthedocs.build/en/321/overview.html#format

Reproducible Project
Please give a link to a public reproducible project or provide an example of the Restructured Text that gives an issue.
https://github.com/psss/did/blob/main/README.rst?plain=1#L82
Error Logs/Results
Before:

After:

Expected Results
Be able to expand sections in the left menu, see highlighted last
clicked section.
Environment Info

Python Version: 3.11
Sphinx Version: 7.2.4
RTD Theme Version: 1.3.0

Did you also upgrade Sphinx? In Sphinx 6 jQuery was removed and you have this error:
Uncaught ReferenceError: jQuery is not defined

Make sure to read changelogs when upgrading.

Yes, I've upgraded sphinx to 7.2.4. So, this means that the menu expansion is not expected to work with the latest packages?

I recently updated this package and sphinx to the latest and had this issue as well. What fixed it for me was adding sphinx_rtd_theme as an extension. It's mentioned here: https://sphinx-rtd-theme.readthedocs.io/en/stable/installing.html. Maybe the README should be updated to match this if that is required. Hope that helps.

What fixed it for me was adding sphinx_rtd_theme as an extension.

@brenj, thank you very much for the hint. It helped and now it works again!


Too many jQuery libraries are loading......

There is no way around it, all projects do contain a lot widgets. And many of those widgets have a jQuery Library in them. Within the current design, every widget includes their own version, and quite often not even minimized.
Before a new users session can start, the browser needs to download all of them. With mobile and even sometimes on a desktop this takes longer that patience of its users. This not nice and unnecessary.
The end user will blame Mendix, and Mendix will blame the developer....
We should re-thing the way of using jQuery!

Does a widget need jQuery, for simile dom manipulations?
Is there a way, we could share jQuery libs across widgets?
Should widgets in the app store be minimized before approval?
Can we change the most common widgets to use the same version of jQuery?
Could the modeler and runtime be shipped with a jQuery library?

As I am going to refactor the Boilerplate soon, this a fairly good point.

For DOM manipulation you can use Dojo, which has all the features that jQuery can do. So no, jQuery is not needed. In the widget generator this will be optional and not encouraged.
A lot of the older libraries that widgets have, depend on jQuery. So including jQuery is a necessity then. The problem with that is that each widget will have their own copy (Widget/lib/jquery) which is not shared indeed
Minified libraries have posed problems in the past, because Dojo Build would fail when it would try to bundle the widgets.

There is not a simple way to get around it.

Minified libraries and widgets should be the standard. So in that sense I agree with you we should have developers have their widgets minified.
Upon approval, we do check the code of widgets. If I see there is no need to include jQuery, I prefer to dismiss the approval and point out that it should be cleaned up.
Personally I want to see less and less jQuery in our widgets.

Another option for jQuery (which isn't entirely friendly) would be a different widget that is only included for their libraries:

You create a widget called "Libraries" that is included in your project (has to be on one of the pages or a template so it's included in widgets.js)
Libraries is a simple widget that will ship jQuery
Other widgets can refer to "Libraries/lib/jQuery" and thus share the library, that will only be included once

I am going to check with R&D whether or not we can find a viable solution. I'll ask them to join the discussion, as I am not the expert on Dojo build, the process that is used by the Modeler to bundle widgets.

As I mentioned on the forum topic: we minify widgets during the build step. You should not (and are urged not to) bundle minified libs with your widgets.

Added options to version 2.0.0 of the widget generator whether or not to include jQuery or not


Exit code for --max-downloads

As a unix user I fundamentally disagree with how #852 went but that's history now.
That said I can't imagine why you would want to exit non-zero when you use --max-downloads.
I wanted maximum 8 files, you gave me 8 files. Then exited with an error.
How does this make sense?

As a reference, this "feature" is added in 94fd3201b237b2a1d04e06dd7fb5ea4130bddded. I guess it's because script writers need to know the reason of exiting. Ping @phihag.
By the way, --max-downloads violation has already a non-default exit code 101.

Agreed with @weedy, a nonzero exit code is not appropriate in this situation as I mentioned in another issue here: https://github.com/rg3/youtube-dl/issues/13598#issuecomment-317215157
The canonical way to do this would be via some stats/summary info, either printed out to the console or to a file in a computer-readable format.


Feature/wheel contents

Exclude tests packages in setup.py to avoid including them in the final wheel.
Bumpversion

This is not working 🗡

This is related to BBVA/deeptracy/issues/7


No handlers could be found for logger "grpc._plugin_wrapping"

I am getting the following error:
No handlers could be found for logger "grpc._plugin_wrapping" and the data doesn't get published in the pubsub.

Are you able to find the solution for this issue @babsuz12 ?

I am also getting this error...

No handlers could be found for logger "grpc._plugin_wrapping"

My problem turned out to be Raspberry pie Internet connection
On Mon, Aug 6, 2018 at 10:03 AM, Dalton Cézane<EMAIL_ADDRESS>wrote:

I am also getting this error...
No handlers could be found for logger "grpc._plugin_wrapping"
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/googlecodelabs/iot-data-pipeline/issues/6#issuecomment-410778187,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATMwk6Wg_xLwW8Xvup9anGfy9eyllJHKks5uOHbHgaJpZM4VG_4c
.

+1, not resolved by @sunsetmountain suggestion 😔


[CI Problem] The compilation schedule in TVM

Hi everyone;
I want to study for the compilation schedule in TVM. who can share with me some tutorials about it?
Many thanks!

This is better asked in https://discuss.tvm.apache.org/


Exception to deserialize 'com.spotify.docker.client.messages.Event'

Description
I'm trying to serialize events from Docker to send for a monitoring tool. I can serialized an event to json, but when I try to deserialize  arise an exception : Exception in thread "main" com.fasterxml.jackson.databind.JsonMappingException: For input string: "2017-01-11T06:43:34.000+0000" (through reference chain: com.spotify.docker.client.messages.Event["time"])
How to reproduce
package br.cin.gfads.adalrsjr1.docker_monitor;

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

import com.fasterxml.jackson.databind.ObjectMapper;
import com.spotify.docker.client.DefaultDockerClient;
import com.spotify.docker.client.DockerClient;
import com.spotify.docker.client.EventStream;
import com.spotify.docker.client.ObjectMapperProvider;
import com.spotify.docker.client.messages.Event;

public class App
{
	private static final Logger log = LoggerFactory.getLogger(App.class);

    public static void main( String[] args ) throws Exception
    {
    	DockerClient docker = DefaultDockerClient.fromEnv().build();
    	DefaultDockerClient.builder()
    					   .uri("localhost:2376")
    					   .connectionPoolSize(1)
    	                                   .build();

    	EventStream eventStream = docker.events();
    	while(eventStream.hasNext()) {
    		Event ev = eventStream.next();

    		ObjectMapperProvider omp = new ObjectMapperProvider();
    		ObjectMapper mapper = omp.getContext(Event.class);

    		String json = mapper.writerWithView(Event.class).writeValueAsString(ev);

    		Event ev2 = mapper.getFactory().createParser(json).readValueAs(Event.class);
//    		Event ev2 = mapper.readerFor(Event.class).readValue(json); // also not working
    		log.info(ev2+"");
    	}

    	docker.close();

    }
}

What do you expect
I expect something like this:
Event{status=null, id=null, from=null, type=NETWORK, action=disconnect, actor=Actor{id=hvb6mpc8t4iu7j85vu27sb1n6, attributes={container=a2ceade7f529694723695256c5d04b135e5573f9b05c597448e1a8d171a22231, name=ingress, type=overlay}}, time=Wed Jan 11 03:52:33 GFT 2017, timeNano=1484117553094885100}
What happened instead
Exception in thread "main" com.fasterxml.jackson.databind.JsonMappingException: For input string: "2017-01-11T06:43:34.000+0000" (through reference chain: com.spotify.docker.client.messages.Event["time"])
Software:

docker version:
Client:
Version:      1.13.0-rc5
API version:  1.25
Go version:   go1.7.3
Git commit:   43cc971
Built:        Thu Jan  5 03:07:30 2017
OS/Arch:      windows/amd64

Server:
Version:      1.13.0-rc5
API version:  1.25 (minimum version 1.12)
Go version:   go1.7.3
Git commit:   43cc971
Built:        Thu Jan  5 03:07:30 2017
OS/Arch:      linux/amd64
Experimental: true

Spotify's docker-client version: 7.0.0

Full backtrace
Exception in thread "main" com.fasterxml.jackson.databind.JsonMappingException: For input string: "2017-01-11T06:54:27.000+0000" (through reference chain: com.spotify.docker.client.messages.Event["time"])
	at com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:210)
	at com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:177)
	at com.fasterxml.jackson.databind.deser.BeanDeserializerBase.wrapAndThrow(BeanDeserializerBase.java:1475)
	at com.fasterxml.jackson.databind.deser.BeanDeserializer._deserializeWithErrorWrapping(BeanDeserializer.java:463)
	at com.fasterxml.jackson.databind.deser.BeanDeserializer._deserializeUsingPropertyBased(BeanDeserializer.java:377)
	at com.fasterxml.jackson.databind.deser.BeanDeserializerBase.deserializeFromObjectUsingNonDefault(BeanDeserializerBase.java:1100)
	at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserializeFromObject(BeanDeserializer.java:294)
	at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:131)
	at com.fasterxml.jackson.databind.ObjectMapper._readValue(ObjectMapper.java:3674)
	at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:1996)
	at com.fasterxml.jackson.core.JsonParser.readValueAs(JsonParser.java:1511)
	at br.cin.gfads.adalrsjr1.docker_monitor.App.main(App.java:39)
Caused by: java.lang.NumberFormatException: For input string: "2017-01-11T06:54:27.000+0000"
	at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
	at java.lang.Long.parseLong(Long.java:589)
	at java.lang.Long.parseLong(Long.java:631)
	at com.spotify.docker.client.jackson.UnixTimestampDeserializer.deserialize(UnixTimestampDeserializer.java:47)
	at com.spotify.docker.client.jackson.UnixTimestampDeserializer.deserialize(UnixTimestampDeserializer.java:36)
	at com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:520)
	at com.fasterxml.jackson.databind.deser.BeanDeserializer._deserializeWithErrorWrapping(BeanDeserializer.java:461)
	... 8 more

It looks to me like the problem is that we have a custom deserializer class for the Event.time field, but we do not have a corresponding serializer class. So you can read the events from docker just fine (Event.time is created from the unix timestamp), but when you serialize out to JSON the time field is written out to a String in whatever default way java Dates are written. When you then try to deserialize the object you just serialized out, the custom deserializer says "I don't recognize this time value. Doesn't look like a unix timestamp to me." and it throws an error.
In fact, this same behavior would happen on any object -> json -> object round trip if the object has a Date property.
To fix this, we would need to create a serializer class that takes Dates and writes them as unix timestamps, reversing the process of the deserializer. Everywhere in docker-client that currently uses the custom deserializer should also use this to-be-written custom serializer.

I agree that it would make sense for the Event class, if it has a custom deserializer for the date field, to also attach serializer too, just in case anyone wants to go from Object -> JSON.
On the other hand, as a workaround, anyone trying to serialize these Events back to JSON could add their own serializer or customize the ObjectMapper instance themselves - I am surprised anyone would want to use the same ObjectMapperProvider we use internally.

@mattnworb I'm using the same ObjectMapperProvider because I don't want need to implement a new one by myself. As the API have an object mapper why not use it? But this problem mess up my plans.
I have learned that whenever a class has a serializer it also must have a proper deserializer, and I was wonder that Event class follows this rule.
Anyway, there is a plan to fix this issue? I've attempted to create my custom deserializer for Event class, but the API disallow that I instantiate a Event externally and I would like not need to create a MyEvent class to do exactly the same that original Event class.


[BUG] Unable to view project tags in the project details for User account

Describe the bug
Unable to view project tags in the project details for User account. In Old UI, can view and add tags for the project, the same is not available for the same account in Primate.
To Reproduce
Steps to reproduce the behavior:

Log in as a User
Go to 'Projects'
Click on any project and check tags.

Expected behavior
Project tags should be shown and provision to add tags based on the permission.
Desktop (please complete the following information):

OS: Mac
Browser: Safari
Version 13.1.1

@sureshanaparti were you an account added to the project, I couldn't reproduce the error. For project where you've access you'll be able to add/remove/list tags.

@sureshanaparti were you an account added to the project, I couldn't reproduce the error. For project where you've access you'll be able to add/remove/list tags.

@rhtyd I checked in Chrome browser as well, changed project to other than Default View and tried to access projects and couldn't see the tags in the Primate UI. Able to see tags for the same project in Old UI, with same user in the same project view.


SUPERAntiSpyware.SUPERAntiSpywareFreeEdition version <IP_ADDRESS>6

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

I think you should remove the word Setup from PackageIdentifer

Update to remove the word setup per @KaranKad


Refactor method CSV

Not that we should clean-code it to 15 lines, but it's 400 lines long, lots of decions in there, we should factor out common code and do a multi on $in, at least. Otherwise it's going to be almost impossible to fix stuff like #21
This might include also totally eliminate method csv, which only checks, and deletes, an arg, and does some stuff with meta which I don't really understand. Lots of is copy, too, which are really unnecessary.
That arg, also, should probably get out of the *%args pile and get a definition on its own.

There are several reasons for  not refactoring:

Easy to port from perl5 Text::CSV_XS
Keep the code unchanged so the speedometer will be of value: if you change the code to be more effective or faster while refactoring, you might gain speed and get different numbers. (I know, not good enough a reason to not refactor)
I do not have any problems with bigger code chunks (at all). I rather have a 400 line block of code that I understnd than 400 different files with the code scattered all around just because someone likes smaller code chunks. This is why I do not like Java, where it is common practice

I heard from @lizmat that there are plans to try to optimize next and continue where possible (them not being exceptions than). The code as is would be a wonderful demonstration of how that speedup works out.
Note that CSV parsing is a state-machine, and with all the options I support, getting "common code" out is harder than you think.
If there are things you don't understand, ask! I might be completely wrong too :)

Well, the thing with smaller code chunks is that they're easier to test and
debug. I don't think a small jump in code speed will be a big deal, if we
gain usability and evolvability.

At the moment I disagree: Text::CSV_XS and Text::CSV are written for performance. Losing performance is a big deal. Usability is on the other side of the API. Evolvability is something else, and I seriously doubt if there are may new ideas floating around in adding new features to Text::CSV, but please prove me wrong.

El jue., 2 ene. 2020 a las 7:56, H.Merijn Brand<EMAIL_ADDRESS>escribió:

At the moment I disagree: Text::CSV_XS and Text::CSV are written for
performance. Losing performance is a big deal. Usability is on the
other side of the API. Evolvability is something else, and I seriously
doubt if there are may new ideas floating around in adding new features to
Text::CSV, but please prove me wrong.

Well, there's one thing that as far as I can see, is not in the original
Text::CSV which is using the "file" argument as a synonym for either input
or output. But that's not the main point; refactoring would imply simply
keeping the current API, which is well tested and thus there would be no
big problem to deal with it. WRT to performance, adding tests would check
that, but in principle, divying up a big method into many tiny would allow
the JIT to optimize the call graph; converting "ifs" and "given" into multi
would probably make it faster, not slower.
Anyway, it's not something I'm going to get into immediately, except for
the many files part, which is easy, in general.

Feel free to create a branch en see if there is noticeable speed-loss.
I know it will be hard, but please try to keep my style.

Well, Slang::Tuxic makes a pretty good job to keep it. :-)


fix tests

Describe the bug
The admin-resave tests are failing with a weird error. As far as I can tell everything actually works, and these tests also fail on the django-file-resubmit codebase.
To Reproduce
Steps to reproduce the behavior:

run tests using pytest
see that two fail with an error

Expected behavior
all tests pass
Additional context
I think it may be something to do with django not being installed in requirements.txt, and it looks a bit like a migrations error.

System details (please complete the following information):
- OS: [e.g. MacOS]
- Browser [e.g. chrome, safari]
- Django Version [e.g. 3.2.2]
- bw-file-resubmit Version [e.g. 0.6.0]

The error in both cases is django.db.utils.IntegrityError: The row in table 'django_admin_log' with primary key '1' has an invalid foreign key: django_admin_log.content_type_id contains a value '6' that does not have a corresponding value in django_content_type.id.
@mouse-reeve any idea here? It's either a bug in AdminResubmitMixin or, more likely, a bug in the tests. My web searching skills aren't coming up with any answers I can understand.

Okay this is unhinged, but I did get the test to pass. As far as I can tell, the django admin panel creates log entries that note every action taken from the admin panel. This part I don't know, but my guess is that the internal Django code completes some part of that in a signal listener or similar that isn't executed during the tests. So when the test tries to run a command via the admin panel, django tries to log it, and then is unable to create a content type foreign key, and fails. I looked at the django codebase and figure out where they are creating those entries, and was able to mock that function:
from unittest.mock import patch

...
def test_image_resubmit_save_admin(self):
...
        with patch("django.contrib.admin.models.LogEntryManager.log_action"):
            saved_obj = testadmin.add_view(resubmit_req)  # <=== BUG here

And the test now passes

Well shoot I pushed it directly to main instead of making a PR, undermining how much of a total genius I was giving myself credit for being, but this should be fixed by https://github.com/bookwyrm-social/bw-file-resubmit/commit/d7f6fd6089a9c79387af6281ddd13af1f11f7ad2

I'm impressed!


Exercise 6 level 3

Did anyone encounter this?
Use of multiple joins detected
Grading terminated
IN the main method i first created a List CompletableFuture of BusRoutes, then convert each of those to List CompletableFuture of String
        List<CompletableFuture<String>> cfstring = brlist.stream()
            .map(br -> br.thenCompose(route -> route.description()))
            // description() returns CompletableFuture<String>
            .collect(
                () -> new ArrayList<>(), // Supplier: creates a new ArrayList
                (list, element) -> list.add(element),
                (list1, list2) -> list1.addAll(list2));

        cfstring.forEach(cf -> System.out.println(cf.join()));

Is there any way to solve this issue?
Thanks guys

Did you use .join() anywhere else?

Nope, i used .join() only at the cfstring.forEach(cf -> System.out.println(cf.join())) in the Main.java;

That's odd... Try submitting again.

Still have the same issue hmmm

or maybe is because i used that in BusRoute; opps
    public CompletableFuture<String> description() {
        CompletableFuture<String> result = CompletableFuture
            .completedFuture("Search for: " + this.stop + " <-> " + name + ":\n" +
            "From " +  this.stop + "\n");

        for (BusService service: services.keySet()) {
            CompletableFuture<List<BusStop>> stops = services.get(service);
            result = result.thenCombine(stops.thenApply(x -> describeService(service, x)
                .join()),(r1, r2) -> r1 + r2);
        }
        return result;
    }

@Bryanngu03 Yes, you did. You used two joins()
What I propose is for you to pass the values around in CompletableFutures instead.

Alright Thank you!! will work on it


[qt5] Fix linux dynamic build

Describe the pull request

What does your PR fix? Fixes #14879

Which triplets are supported/not supported? x64-linux-dynamic

Basically this PR does three things:

Allow to correctly find and link to psql client
Allow to correctly link module that have qt5-base as dependency, regarding ICU and zstd sub-dependencies
Allow to correctly run Qt tools (rcc, qkgen, ...) and use qt5 libraries at build time.

Setting LD_LIBRARY_PATH may be somewhat dangerous, but I cannot find a better way to do that, without changing too much things. If someone have a better idea, feel free to propose !

cc @Neumann-A for review this PR,

@Neumann-A Do you have any other concerns about this?

Thanks for your help!


How to trigger event?

How can you trigger an event? I'm trying to process the queue like so:
...
methods: {
  uploadFiles() {
    this.$emit('processQueue')
  }
}
...

Gday @smakman
Unfortnantly there were some changes in how events were handled between parent-child components in Vue1 & 2.
In Vue 2 perhaps the simplest way is to do something like
        var arrayOfComponents= this.$children.filter(function(item){
          return item.id === "myVueDropzone";
        });
        arrayOfComponents[0].processQueue()

Im not sure this is 100% the best way, Im still getting my head around how the parent child communication works in Vue2 but something like this should work (although I've had to update the npm package for this component so you'll need to grab that too).


suggestion

my suggestion: If an account has 2FA Could it auto set "sentry" to true?
If yes thanks ^^

And if you can add account lists Like name156:passwort that it auto add to the json ^^

Hey, thanks for your suggestion.
The first suggestion is controversial as I've explicitly made it opt-in only. Many people assume accounts don't have SteamGuard enabled and then freak out when they get a SteamGuard popup. The sentry filter was designed to combat this and to let people explicitly know that the account has SteamGuard, and if intended so, to manually enable it using the SteamGuard checkbox (which is the sentry equivalent for the accounts.json).
The second feature has already been implemented with the Import button and was pushed to the Titan repo 11 days ago with commit d22a9aa:

wtf? i dont have the import button

As said previously, it was introduced with version 1.6.1-d22a9aa. If you're below that you won't have that feature.


Fix Triple Classloader & Add backward of ServiceMetadata

What is the purpose of the change
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #8800 (22ae35f) into 3.0 (04a9837) will decrease coverage by 0.24%.
The diff coverage is 88.88%.

@@             Coverage Diff              @@
##                3.0    #8800      +/-   ##
============================================
- Coverage     63.90%   63.66%   -0.25%
+ Complexity      314      312       -2
============================================
  Files          1158     1158
  Lines         48824    48830       +6
  Branches       7335     7314      -21
============================================
- Hits          31203    31088     -115
- Misses        14225    14327     +102
- Partials       3396     3415      +19

Impacted Files
Coverage Δ

...a/org/apache/dubbo/common/BaseServiceMetadata.java
94.73% <66.66%> (-1.56%)
:arrow_down:

.../java/org/apache/dubbo/rpc/model/ServiceModel.java
58.49% <100.00%> (+1.62%)
:arrow_up:

...e/dubbo/rpc/protocol/tri/AbstractClientStream.java
64.93% <100.00%> (ø)

...e/dubbo/rpc/protocol/tri/AbstractServerStream.java
54.54% <100.00%> (ø)

...he/dubbo/rpc/protocol/tri/TripleClientHandler.java
62.71% <100.00%> (ø)

...ng/transport/dispatcher/all/AllChannelHandler.java
62.06% <0.00%> (-27.59%)
:arrow_down:

...ntext/event/AwaitingNonWebApplicationListener.java
60.56% <0.00%> (-22.54%)
:arrow_down:

...va/org/apache/dubbo/registry/RegistryNotifier.java
84.61% <0.00%> (-15.39%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
46.15% <0.00%> (-15.39%)
:arrow_down:

...ng/transport/dispatcher/WrappedChannelHandler.java
47.82% <0.00%> (-15.22%)
:arrow_down:

... and 40 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 04a9837...22ae35f. Read the comment docs.


compiling merkle-zkapp example

src/examples/zkapps/merkle-tree/merkle-zkapp.ts example does not compile with  "o1js": "1.3.1"
Here is a template with the merkle-zkapp.ts code.
https://github.com/Pfed-prog/Mina-Template
yarn compile
"compile": "rm -rf build && tsc",
output

the error doesn't seem to have anything to do with the example itself.
maybe you're trying to compile o1js with a version of TS it's not compatible with?
I'd try to upgrade TS.
@Pfed-prog As an aside, I didn't see a package.json in your project, you're git-ignoring all .json files, that seems error-prone to me.

the error doesn't seem to have anything to do with the example itself. maybe your TS version is not compatible with o1js? I'd try to upgrade TS.
@Pfed-prog As an aside, I didn't see a package.json in your project, you're git-ignoring all .json files, that seems error-prone to me.

Yes, excuse me, added dependabot as well. Package json and tsconfig is back.


Fix token send

fixed a major issue in "cli tx create" with lack of binary marshaler for TokenSend which caused the transaction to fail to send
cleaned up some human readable output on tx get

This PR is OBE by https://github.com/AccumulateNetwork/accumulate/pull/358, but leaving it for the moment.


Styling of project section is not fixed

Description
The styling of the project section is not proper. There is a large margin between the search input and the boxes. Also the box styling is not fixed.
Can i work on this issue under GSSOC '23
Screenshots

Additional information
No response
Do you want to work on this issue?

[X] I want to work on this issue.

Issue solved already!


Blog not accepting follow requests on the fediverse (similar to #741 maybe)

Quick summary
My blog isn't accepting follow requests via Mastodon. I just get the "Cancel Follow" button when viewing the blog profile. I'm sorry I don't have much information available because debug doesn't really show anything within Wordpress. tech.minnix.dev is the site and site health is fine. The only plugins I'm using is ActivityPub and wp_debug. I thought it might be a similar issue to #741 but I don't have an @ in my user as my profile url is https://tech.minnix.dev/index.php/author/minnix/
Steps to reproduce
Follow<EMAIL_ADDRESS>on Mastodon
What you expected to happen
Follow request accepted
What actually happened
My follow request is never accepted and "Cancel Follow" is shown instead on the blog's profile
Impact
One
Available workarounds?
No but the platform is still usable
Logs or notes
More info about my install can be found at #748

@minnixtx see: https://github.com/Automattic/wordpress-activitypub/issues/591#issuecomment-2201329297

@minnixtx see: #591 (comment)

Brilliant. It worked. I have no recollection of changing post URLs to include index.php but after changing the format to just include the post title without index.php the problem is solved. Thanks.


CloudQuery Swetrix Plugin

First version of the CloudQuery Swetrix plugin :)
I added tables for log, performance, and live_visitors.

thanks a lot for the contribution!


Fix HillasReconstructor in case of too few telescopes

@mackaiver , @MaxNoe and me faced an issue where the HillasReconstructor would fail even though there were two telescopes left after cleaning. It turned out that you could encounter situations where one of the hillas ellipses had a width of np.NaN because there were only a few pixels remaining which are all aligned.
This would render the weights useless and leave the h_max estimation with a singular matrix.
We decided that the HillasReconstructor should check for valid telescopes (that is telescopes with a defined width of the hillas ellipse) and that we would not even try to reconstruct other events (which should be very few if any).
Is there any reason against this approach?

Hi.
Checking for valid telescopes is indeed a good approach. Crucial parameters can fail for many reasons.
I also remember suggesting in some discussion about Hillas parameters that the width should be equal to 0 and not nan in case of aligned pixels.

I think u refer to #772, right?

Just a question: what happens in case of we have 3 telescopes triggered and one of them has a NaN width? is h_max well reconstructed in this case?
I would also add a comment above those lines saying something like "This is done in case the width is NaN and h_max cannot be reconstructed"...or something like this...so that in the future we forget why we put it there.

Just a question: what happens in case of we have 3 telescopes triggered and one of them has a NaN width? is h_max well reconstructed in this case?
I would also add a comment above those lines saying something like "This is done in case the width is NaN and h_max cannot be reconstructed"...or something like this...so that in the future we forget why we put it there.

Im not sure actually. If we only go with the valid telescopes as @MaxNoe suggested above we would obviously avoid that (potential) problem

Im not sure actually. If we only go with the valid telescopes as @MaxNoe suggested above we would obviously avoid that (potential) problem

I agree we should treat those images in a certain way (and we can discuss about this).
I'm just wondering that happens to those passing this condition even though the width in one on them might be NaN.
In any case I would approve this PR: if you could also have a look at what happens to the reconstruction if we use those images by setting the width to a certain small value (which of course should make sense) instead of NaN, it would be great!

Im not sure actually. If we only go with the valid telescopes as @MaxNoe suggested above we would obviously avoid that (potential) problem

I agree we should treat those images in a certain way (and we can discuss about this).
I'm just wondering that happens to those passing this condition even though the width in one on them might be NaN.
In any case I would approve this PR: if you could also have a look at what happens to the reconstruction if we use those images by setting the width to a certain small value (which of course should make sense) instead of NaN, it would be great!

I will try to find some time for this :)

Reiterating my comments from above, we should avoid putting any "cuts" in the code, other than absolute failure cases (e.g. NaN or Inf preventing a sensible value).  The user should explicitly control all cuts before the hillas code is executed (e.g they might replace the telescope dict with a subset after rejecting telescopes for any reason)

And we must make sure any ignored telescopes are recorded somehow, so we don't get the case of events that are marked as 3 tel in the output that only really used 2 telescopes (which will throw off any benchmarks we do)

Reiterating my comments from above, we should avoid putting any "cuts" in the code, other than absolute failure cases (e.g. NaN or Inf preventing a sensible value). The user should explicitly control all cuts before the hillas code is executed (e.g they might replace the telescope dict with a subset after rejecting telescopes for any reason
)

That would mean to fail loudly, if any of the telescopes contain unusable data.
I like that a lot! This makes it much easier, to design systems, that keep track where and why telescope data was discarded.
So this means, the Reconstructor should fail early and load, if any of its input data is invalid.

@kpfrang
Did you actually succeed with other weighting methods for the planes?

So this means, the Reconstructor should fail early and load, if any of its input data is invalid.

Yes, I think that's cleaner. I worry about adding any "hidden" cuts inside classes like Reconstructors, since it will clearly lead to some unexpected behavior later when people forget they are there (e.g. expecting the telescope multiplicity to be what the reconstructor used, when sometimes it is not).

So this should fail as soon as there any nans in the hillas_dict. Makes sense to me. 👍

I would like to solve this PR asap since I just run into this same problem today.
I had 28 telescopes triggered in a huge event and with just one of them having a width = 0 the reconstruction was giving nan. How to solve this:

discard all telescopes with width = 0 (should be done in the cleaning and not hard-coded then);
if width = 0 (which is unlikely with more than 3 pixels remaining...), use @dneise suggestion (https://github.com/cta-observatory/ctapipe/issues/772#issuecomment-410658085) to use a minimum value for width from the pixel geometry;
discard all telescopes with less than 5 (or configurable number of) pixels remaining after cleaning

We leave this selection to the user (replace width or apply some cleaning) and decide that in the HillasReconstructor we keep only those telescopes not breaking the reconstruction? Of course if the reconstructor drops a telescope, this should be reported to the user (with explanations).
Since my problem is with width = 0 and not width = NaN, I would add the 0-case to the exclusion of a telescope from the reconstruction because asking for isnan doesn't solve my problems.

@kpfrang
Did you actually succeed with other weighting methods for the planes?

What I did was investigating what we gain using weights from lookup tables for the distance of closest approach between the semi-major axis of the image and the true direction projected in the camera.
Besides improving the overall reconstruction, it also helped to save those images. For this investigation I always used width = 0 for such images (back then this was not always consistent). The LUTs were able to deal with 0 as one of the parameters was the ratio width / length. If width = NaN however,  the LUTs obviously would also fail to come up with a weight for those images.
I did not dig too deep into this, but I didn't find a problem in the reconstruction when I kept those images.

What about using those weights to try to fix the reconstruction for just 2 LSTs? Would it solve the issue that @jjlk showed in #967?

Hi all,
regarding this (still open) discussion, now that the protopipe code is out, you could give a look to event_preparer.py.
I couldn't yet elaborate on what Julien left me, but I believe that from line #133 of that file there is code very similar to what you suggest - perhaps it can be possible to get inspired from it.


Live Share notebook serializer not being called when opening a notebook file on guest

VS Code Version: 1.74.1
OS Version: Windows 11

Steps to Reproduce:

Open a folder with .ipynb file in VS code and open the notebook file in editor
Start live share session and join the session in another VS code instance
On the guest, see the error "Co-editing is not supported for notebooks opened with non-shared views."
(If the notebook file does not automatically open on guest, select some text in the notebook file on the host)

The error shows up as the notebook serializer that Live Share registered as guest is not being selected and it breaks coediting in notebook.
How can force Live Share serializer to be selected during a live share session?
Adding @lyup and @mattbierner .

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.74.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Verified that it occurs on latest VS Code version as well 1.74.2

Adding @bamurtaugh for visibility.

cc @mjbvz @rebornix - these are Matt and Peng's GitHub aliases they use in this repo 😄.

@nandiniYeltiwar I can't reliable reproduce this
Here's a successful case where the the LiveShare serializer being invoked on the guest. Here the guest is an OSS build of VS Code connected to a host that's on the VS Code insiders build. This is with LiveShare 1.0.5797:

However syncing edits doesn't work but I also see a bunch of errors in the developer console from the  LiveShare code:
d.setDecorations is not a function
	at vscode-file://vscode-app/Users/matb/.vscode-oss-dev/extensions/ms-vsliveshare.vsliveshare-1.0.5797/extension.js:394:504293
	at Array.forEach (<anonymous>)
	at RulerDecorator._renderCore (vscode-file://vscode-app/Users/matb/.vscode-oss-dev/extensions/ms-vsliveshare.vsliveshare-1.0.5797/extension.js:394:504278)
	at RulerDecorator.render (vscode-file://vscode-app/Users/matb/.vscode-oss-dev/extensions/ms-vsliveshare.vsliveshare-1.0.5797/extension.js:394:502260)
	at ClientDecoratorManager.updateDecorators (vscode-file://vscode-app/Users/matb/.vscode-oss-dev/extensions/ms-vsliveshare.vsliveshare-1.0.5797/extension.js:394:506405)
	at CoEditing.updateDecorators (vscode-file://vscode-app/Users/matb/.vscode-oss-dev/extensions/ms-vsliveshare.vsliveshare-1.0.5797/extension.js:394:460702)
	at CoEditing.<anonymous> (vscode-file://vscode-app/Users/matb/.vscode-oss-dev/extensions/ms-vsliveshare.vsliveshare-1.0.5797/extension.js:394:459122)
	at Generator.next (<anonymous>)
	at fulfilled (vscode-file://vscode-app/Users/matb/.vscode-oss-dev/extensions/ms-vsliveshare.vsliveshare-1.0.5797/extension.js:394:413224)

mainThreadExtensionService.ts:80 TypeError: Cannot read properties of null (reading 'toLowerCase')
	at CoEditing.createSharedFileClient (vscode-file://vscode-app/Users/matb/.vscode-oss-dev/extensions/ms-vsliveshare.vsliveshare-1.0.5797/extension.js:394:454641)
	at GuestCellManager.createFileClient (vscode-file://vscode-app/Users/matb/.vscode-oss-dev/extensions/ms-vsliveshare.vsliveshare-1.0.5797/extension.js:394:1037449)
	at vscode-file://vscode-app/Users/matb/.vscode-oss-dev/extensions/ms-vsliveshare.vsliveshare-1.0.5797/extension.js:394:1037327
	at Array.forEach (<anonymous>)
	at new GuestCellManager (vscode-file://vscode-app/Users/matb/.vscode-oss-dev/extensions/ms-vsliveshare.vsliveshare-1.0.5797/extension.js:394:1037310)
	at GuestNotebooksService.onDidOpenNotebookDocument (vscode-file://vscode-app/Users/matb/.vscode-oss-dev/extensions/ms-vsliveshare.vsliveshare-1.0.5797/extension.js:394:1044642)
	at vscode-file://vscode-app/Users/matb/.vscode-oss-dev/extensions/ms-vsliveshare.vsliveshare-1.0.5797/extension.js:394:1041593
	at Listener.invoke (event.ts:692:17)
	at PrivateEventDeliveryQueue.deliver (event.ts:899:22)
	at Emitter.fire (event.ts:860:24)
	at ExtHostNotebookController.$acceptDocumentAndEditorsDelta (vscode-file://vscode-app/Users/matb/projects/vscode/out/vs/workbench/api/common/extHostNotebook.js:261:53)
	at RPCProtocol._doInvokeHandler (rpcProtocol.ts:455:17)
	at RPCProtocol._invokeHandler (rpcProtocol.ts:440:32)
	at RPCProtocol._receiveRequest (rpcProtocol.ts:370:19)
	at RPCProtocol._receiveOneMessage (rpcProtocol.ts:305:10)

@nandiniYeltiwar Are these error expected? Would they explain why syncing does work as expected or do you still think it's something to do with the wrong serializer being used ?

Here's the exact steps I followed when I do see this issue:

Using VS Code insiders with LiveShare 1.0.5797. Start a new collaboration session
On the host, open an ipynb file
From another VS Code insiders instance with the same LiveShare version (or OSS), join the session
❌  At this point the workspace is untrusted and I see Co-editing is not supported for notebooks opened with non-shared views.
On the host, I then close the notebook and reopen it.
✅  The notebook now shows in the guest too
However any notebook edits on the host produce the LiveShare errors I mentioned above. The guest does not see these changes

Still looking into what triggers the error on first open. If I disconnect the guest and re-join, I often don't see this error (but the notebook also does not open automatically)

Looks like my proposed fix against LiveShare didn't work :/
To better investigate this, I've create a minimal example extension:
https://github.com/microsoft/vscode-extension-samples/tree/dev/mjbvz/test-liveshare-serializer/notebook-serializer-sample
Using this, I could confirm a few things:

LiveShare activates on onFileSystem:vsls. I'm emulating this using onFileSystem:file. If the the serializer is registered during this activation event in my sample, our custom serializer seems to be used whenever you open a notebook

The above does not work if you reload the window open with the notebook editor open. This seems to be because the editor input is restored from a backup. I fixed this by adding additional activation events:
"onNotebook:liveshare-jupyter-notebook",
"onNotebookSerializer:liveshare-jupyter-notebook"

It is not clear to me if this case impacts live share since AFAIk live share editors aren't restored from any backup when you connect to a sharing session.

@nandiniYeltiwar Can you please build on my example extension to create a minimal example of how  live share works with notebooks and that also demonstrates the bug in action. My understanding of the live share code is very limited and I'm not setup to build live share locally. This should help us identify if there's something going wrong on the VS Code side or in the live share code

@mattbierner Its going to be a lot of work to replicate Live Share's co-editing, share and join in order to create a test scenario. We can setup debugging sessions to debug both Live Share and VS code together to narrow down scenarios.
Also, you mentioned you were able to verify that during the repro,  dataToNotebook uses VSCode's normal ipynb extension instead of LiveShare and later when host closed the notebook and reopened it, dataToNotebook used Live Share's serializer. How did the switch in serializer happened?

@nandiniYeltiwar You don't need to rebuild all of liveshare, just a minimal example to help investigate the issue
Try modifying the example I liked to so that it mirrors how lliveshare registers its serializer. Don't worry about actually implementing the serializer, or co-editing, or anything like that
If the sample no longer at that point, then we know the issue is on the VS Code side. However if the sample still works, then we know the issue is likely something on the liveshare side instead. In both cases, having the sample will make this investigation easier

@mjbvz Here is my repo with few changes to serializer registration: https://github.com/nandiniYeltiwar/vscode-extension-samples/tree/dev/nandiniy/test-liveshare-serializer/notebook-serializer-sample.
While debugging the instance, I run the command "Create JSON notebook" which throws an error of unknown notebook type. Is this expected?

Thanks @nandiniYeltiwar. Can you explain a little more how live share works here? Specifically:

Does Liveshare also have a custom notebook type registered for *.ipynb files?
Is this custom live share notebook type also listed in the package.json contributions? The current sample does not do this
Do you use openNotebookDocument to open notebooks on the guest? If you do, do you pass in the live share notebook type when calling it?

Does Liveshare also have a custom notebook type registered for *.ipynb files?

Yes we do. With a prefix for Live Share.
Is this custom live share notebook type also listed in the package.json contributions? The current sample does not do this
we do not have notebook type listed in contributions in package.json
Do you use openNotebookDocument to open notebooks on the guest? If you do, do you pass in the live share notebook type when calling it?
We do use openNoteBookDocument but we pass on vscode.Uri and not the notebook type and content.

How does VS code finds the notebook type when calling openNotebookDocument with notebook Uri?


Upgraded edge-core version to 0.15.0

Do not allow RPi users to enable new FOTA library as we are not creating the new update scripts and not using osTree to manage the updates in 2.2 release.

Closing this.. #14 covers it.

Closing this.. #14 covers it.


Make file not compiling with WinAVR 20100110

Just changed a couple things in the make file. USE_LED set to 1, CS pin changed, all typical. but when doing 'make' in command line it gets to the .text part and comes up with an error 1.
here is the output
rm -rf *.o avr_boot.elf *.eps *.bak *.a *.bin rm -rf pff/src/*.o uart/*.o rm -rf *.lst *.map rm -rf avr_boot.hex avr-gcc -gdwarf-2 -Wall -Os -mcall-prologues -ffunction-sections -fdata-sections  -mmcu=atmega1284p  -std=c99 -DBOOT_ADR=0x1F000  -DF_CPU=16000000   -DUSE_LED=1  -DUSE_UART=0  -DCS_PIN=4  -DVARIANT_1284P=0    -c -o main.o main.c avr-gcc -gdwarf-2 -Wall -Os -mcall-prologues -ffunction-sections -fdata-sections  -mmcu=atmega1284p  -std=c99 -DBOOT_ADR=0x1F000  -DF_CPU=16000000   -DUSE_LED=1  -DUSE_UART=0  -DCS_PIN=4  -DVARIANT_1284P=0    -c -o pff/src/pff.o pff/src/pff. c avr-gcc -gdwarf-2 -Wall -Os -mcall-prologues -ffunction-sections -fdata-sections  -mmcu=atmega1284p  -std=c99 -DBOOT_ADR=0x1F000  -DF_CPU=16000000   -DUSE_LED=1  -DUSE_UART=0  -DCS_PIN=4  -DVARIANT_1284P=0    -c -o diskio.o diskio.c avr-gcc -c -mmcu=atmega1284p  -I. -x assembler-with-cpp -Wa,-adhlns=asmfunc.lst, -gstabs -DBOOT_ADR=0x1F000  -DF_CPU=16000000   -DUSE_LED=1  -DUSE_UART=0  -DCS_P IN=4  -DVARIANT_1284P=0  asmfunc.S -o asmfunc.o avr-gcc -gdwarf-2 -Wall -Os -mcall-prologues -ffunction-sections -fdata-sections  -mmcu=atmega1284p  -std=c99 -DBOOT_ADR=0x1F000  -DF_CPU=16000000   -DUSE_LED=1  -DUSE_UART=0  -DCS_PIN=4  -DVARIANT_1284P=0  -Wl,-Map,avr_boot.map -Wl,--gc-sec tions -Wl,--section-start,.text=0x1F000  -o avr_boot.elf main.o pff/src/pff.o di skio.o asmfunc.o c:/winavr-20100110/bin/../lib/gcc/avr/4.3.3/../../../../avr/bin/ld.exe: address 0x2013c of avr_boot.elf section .text is not within region text c:/winavr-20100110/bin/../lib/gcc/avr/4.3.3/../../../../avr/bin/ld.exe: address 0x2013c of avr_boot.elf section .text is not within region text make: *** [avr_boot.elf] Error 1
Any ideas why?

is the make file not up to par with current make file template standards?

Well I wouldn't consider 2010 to be current. I believe that error indicates that the compile size is too large for the bootloader section. I get the same results trying to build with WinAVR but if I use the tools included with the Arduino IDE installation and then only use WinAVR for the tools no longer included with Arduino such as make.exe then it builds fine with the same makefile settings you're using(although I was getting larger compile sizes than zevero). Try this(works for me with Arduino IDE 1.6.5 - 1.6.7 and should probably work with other versions):
path C:\Program Files (x86)\arduino-1.6.7\hardware\tools\avr\bin;C:\winavr-20100110\utils\bin
make

You might need to edit the path to match your Arduino IDE install location.

its the most current on Sourceforge... but I am new to this side of things. I wonder why there is a size difference compared to how zevero compiles on linux. it really shouldn't be different,
I'll try your method.

Though these are relating to older versions of the toolchain, I believe this answers all our issues and why Linux code is smaller then winavr code. I haven't tried the workaround posted in this thread yet but i feel it will help.
http://www.avrfreaks.net/forum/winavr-20070122-code-size-larger-20060421

Closing issue, I downloaded Ubuntu and created a virtual machine for development use and was able to compile a 4040 byte .hex bootloader file directly on my removable drive. seems there is major issues with using WinAVR and the current source codes. lots of extra binary is being added for some reason, probably related to the post i linked to above. Don't know if anyone wants to tackle a workaround for it so windows users can continue to use the Winavr toolchain rather then going through the hassle of setting up a linux virtual machine.

Strange, the size of mine is 4014. Did you use the latest version of avr_boot and  these settings in the makefile:
MCU_TARGET    = atmega1284p # Target device to be used (32K or larger)
BOOT_ADR      = 0x1F000 # Boot loader start address [byte] NOT [word] as in http://eleccelerator.com/fusecalc/fusecalc.php?chip=atmega1284p
F_CPU         = 16000000  # CPU clock frequency [Hz] NOT critical: it just should be higher than the actual Hz
CS_PIN        = 4 # Arduino pin connected to SD CS. Supported values: 4, 8, 10, 53.
VARIANT_1284P = 0 # ATmega1284P variant: 0=avr_developers/standard, 1=bobuino, 2=sleepingbeauty
USE_LED       = 1 # Debug with two (defined in asmfunc.S)
USE_UART      = 0 # Debug on Serial. 0 ... deactivate or divider of http://wormfood.net/avrbaudcalc.php for baud rate!

Due to the pinout of my project I modified the port mapping so the CS pin is pin 21 or PC5 and the LED pins are 1 and 3 PB1 PB3. but other then that everything is the same.

I just happend to compile avr_boot for my project. Since you seem to be interested I put the compiled binary sizes into the readme. https://github.com/zevero/avr_boot
Note, that it has increased slightly since I added more UART debug info and some code to disable the watchdog reset.

Thanks! Here's mine using the latest version of avr_boot:
3654/3704
3964/4014
3974/4034
20 bytes less on all but the last one which was 18 bytes less.
I tried the configuration listed in my last comment except with the boot section size increased to 4096 words using only WinAVR and it compiled to 4426 bytes so the cause of the original issue was the compile size being larger than the bootloader section size when building with WinAVR. Still I don't consider this a major obstacle for Windows users as they can always use the tools included with the Arduino IDE and the precompiled bootloader files in the avr_boot Boards package already cover all the most common configurations.

still curious as to why my compile size was so different. I agree that the existing boards package covers the most common configs.


Minimize the number of dup'ed options in put_or_update

This PR minimizes the number of .dup calls during .put_or_update, thus minimizing allocations.
@agrare @kbrock  Please review.

Ooh, both methods modify that hash.
I wonder if there is a potential problem here.
Think we should modify the callers and remove any possible dup calls from put_or_update.
Since this is called from put_or_update we have a lot to gain here.

yeah I noticed that the default_get_options is already returning a new hash, so we are passing that hash along.  Ideally we shouldn't modify it in the blocks, but the ones that do aren't doing anything they hadn't done previously.

I like the tap too... @Ladas does it make sense for this PR, or should I do it in a separate one?


Use new oblt-cli actions

The e2e.yml workflow is also failing on main at https://github.com/elastic/elastic-otel-dotnet/actions/runs/9347040825/job/25723160639.
But the oblt-cli related steps are working as expected


Jumping at vertical mode

Conditions: carousel is used at vertical mode and top of carousel block is out of screen.
Bug: when you push next button - page jump to top after slide animation.
Reason:
if (!_.options.autoplay) {     var $currentSlide = $(_.$slides.get(_.currentSlide));     $currentSlide.attr('tabindex', 0).focus(); }
at Slick.prototype.postSlide

what is version of carousel?

1.7.1.
Installed from bower 05.09.2017

One more thing - autoplay: false

I'm seeing this as well. Didn't happen on 1.6, now is happening since updating to 1.7.1.

Adding scrollTo fixes it for me.
from this (1.7.1);
var $currentSlide = $(_.$slides.get(_.currentSlide));
$currentSlide.attr('tabindex', 0).focus();

to this:
var $currentSlide = $(_.$slides.get(_.currentSlide));
var x = window.scrollX, y = window.scrollY;
$currentSlide.attr('tabindex', 0).focus();
window.scrollTo(x, y);

Should be fixed in new release

@leggomuhgreggo Thanks for the quick fix here. Since "focusOnChange" setting was "reluctantly" added, I'm wondering why not leave the focus in, and use the window.scrollTo method I posted above? Granted, JS is not my strength, so there very well may be a big downside, but that potentially could solve both issues at once.

Considered a scroll override but it would break the point of the focus scroll jump, which is accessibility -- granted we're also doing by disabling by default, but the scroll override option adds entropy and get's complicated with multiple sliders on page.

That makes sense. It's sad though, that we now have to compromise either accessibility or a jumpy slider.

Carousel a11y isn't so well defined, particularly as regards this issue, that I'd worry too much about it. That said you can always turn focusOnChange to true and factor for it however you'd like!


Update ci.yml

Issue #, if available:
Description of changes:

Doesn't seem related, but it looks like a legit test failure in CI. Do you know what's up?

Doesn't seem related, but it looks like a legit test failure in CI. Do you know what's up?

Yes. #215 should fix it.


Remove preprinter, add parenthesizer callback to emit

This reverts the "preprinter" transform from #42676 that was primarily used to ensure correct parenthesization using the node factory and amends the emitter to support providing a parenthesizer rule callback when emitting certain nodes.
Related #43486

@typescript-bot perf test

@typescript-bot perf test

@rbuckton can you point out what code is new, as opposed to a reversion?

In emitter.ts, most of the changes are a reversion. I left in some of the changes in comment/sourcemap emit as it improves the number of cases where we can use our binary expression trampoline to avoid exhausting the call stack.
The only real addition is the ability to pass a parenthesizerRule to emit/emitExpression, which accomplishes the same thing I was trying to fix when I added the preprinter transform, but without the extra full-walk of the tree.
Anything in nodeFactory.ts, parenthesizerRules.ts, and types.ts is new and was added to support passing a parenthesizerRule in emitter.ts.

This one wasn't as simple as just rolling back the change, as the work to create a reusable binary expression trampoline is something we want to keep so that we're consistent across the binder, checker, and emitter. As a result, we also kept the changes to comment and source map emit so that we could reuse the logic inside the binary expression trampoline.

While not perfect (as there are some other changes in emitter.ts unrelated to this), you can get a gist of what changed and was reverted by doing the following on the commandline:
git difftool d3b8d5e9c423d2565e9c5122326fbf4a2a2e5d6a^..substitutionParenthesizer -- src/compiler/emitter.ts

I'll actually push up a change that reorders some of the functions so that they line up with where they were prior to $43676 to make the command-line diff easier to read through.

I've pushed up a change that reorders some of the functions so that they line up with where they were prior to #43676 to make the command-line diff easier to read through.

I don't think this should have broken anything, but just to be on the safe side...
@typescript-bot run dt
@typescript-bot test this
@typescript-bot user test this

RWC tests failed, but its unclear why. I'm running them locally.
User tests were fine except for fp-ts, which for some reason ran out of heap memory. I will have to investigate that one to see what's causing the crash.

RWC failures are mostly unrelated to this change, the few that are are changes in indentation that were likely present before the preprinter transform was added (similar to what I mentioned here), so this is just going back to existing behavior.

The fp-ts user tests didn't crash locally. @weswigham did you mention you were you looking into an OOM?

@sandersn did.a bit ago, iirc?

I cannot repro the OOM locally.
@typescript-bot user test this

Ok. It didn't crash that time. Must have been a glitch in the matrix.

Summary of DT failures:

There's a crash that doesn't list the project that is crashing, however this is also occurring in nightly, so I don't think its related to this change: https://typescript.visualstudio.com/TypeScript/_build/results?buildId=101141&view=logs&j=ae5f67bc-b508-52d0-18c7-3e0886a35c88&t=344fa42e-5be7-595c-913e-e7acf0f0490f&l=13595
mithril is crashing due to running out of stack space in checker, which doesn't seem to be related to this change as far as I can tell. It occurs in the nightly as well: https://typescript.visualstudio.com/TypeScript/_build/results?buildId=101141&view=logs&j=abaf456e-5a9c-50a3-94a8-5c090880e34b&t=94425fb2-771d-59ba-1fed-934966b6530f&l=13594
electron-notifications, electron-notify, and electron-json-storage are having issues with traceDeprecation in ../node/process.d.ts, but this occurs in the nightly as well, so is unrelated to this change:

electron-notifications - https://typescript.visualstudio.com/TypeScript/_build/results?buildId=101141&view=logs&j=71179031-6417-5a2f-3d87-af6fce2011e4&t=5ac81f15-0a74-5a9b-b155-06ef07cd84f6&l=13596
electron-json-storage - https://typescript.visualstudio.com/TypeScript/_build/results?buildId=101141&view=logs&j=ae9e61d0-c116-562e-ef72-0c532f74ef92&t=ccd97d0d-fa78-59da-ae5f-9c54639b4c00&l=13600
electron-notify - https://typescript.visualstudio.com/TypeScript/_build/results?buildId=101141&view=logs&j=ae9e61d0-c116-562e-ef72-0c532f74ef92&t=ccd97d0d-fa78-59da-ae5f-9c54639b4c00&l=13634

cytoscape is crashing due to running out of stack space in checker, which is also occurring in the nightly and is unrelated: https://typescript.visualstudio.com/TypeScript/_build/results?buildId=101141&view=logs&j=ae9e61d0-c116-562e-ef72-0c532f74ef92&t=ccd97d0d-fa78-59da-ae5f-9c54639b4c00&l=13588

None of the DT failures seem to be related to this change, but warrant further investigation outside of this PR.

The other crash has the same origin; the electron-* are known failures that shouldn't show up in the final output. They should, I hope, be gone after the additional grep that @weswigham and I stuck onto the end of the diff.


A method for real-time acquisition of circular radius

Hey @JamesLMilner , I hope there can be exposed attributes or methods for obtaining real-time radius of circles.
During the drawing process, getsnapshot and turf cannot be calculated, resulting in an error message.
draw.on('change', (e: string, type: string) => {
 if (e?.length && drawType == 'circle' && !['delete', 'create'].includes(type)) {
    getCircleDiameter(e[0])
  }
});

This is the radius method I currently use to calculate and draw circles.

Seems like a reasonable request 👍🏻  I've implemented it in the latest release


Fix SwaggerUiControllerFactory

This PR fixes a problem reported in issue #25 where the factor stopped instantiating the controller due to a wrong variable name. I've also added a unit test to detect problems with the factory.

@weierophinney Could this please be committed ...

How long we have to wait for this little change?

+1 waiting for merge PR

Thanks, @weckx; issuing the 1.2.1 release now with the fix.


Update package.json to support the latest node engine (20.x.x)

node engine version is updated to support "20.X.X".

@DudiKaplan - attention to this please

Will be perfect if this PR merge


Doc: Two additional storage how-tos

Add how-to guides for launching instances in a specific pool and resizing storage.

Documentation preview available at: https://linuxcontainers.org/lxd/docs/pr.10673/

Testsuite passed


Printing call no. with and without prefix in one go

Hi, I have created a template that includes different prefixes.  I was hoping to use it to print call numbers with and without a prefix.  However, it seems that those without a prefix will have an extra line inserted before the class no., making the first line of the text drop lower than normal.  Is there a way to remove the extra line when there is no prefix?
I suppose I can create separate templates, one for with prefix and one for without, but it would be much more efficient if we can just close our eyes, scan all the barcodes, and print everything in one go.

Thanks in advance for your advice.
PS: Using Parting routine 5, Verdana 12
Katie

@KatieLai, could you provide the details of the template you are using? Thanks.

Hi @mgobat
Here are the details of my tempate "Print Book with Prefix."

Here is my layout

Btw, may I know what "left padding" means?
Thanks again for your help.
Katie

@KatieLai, thank you for the template details. I will take a look.
Left padding refers to an indentation in the label before the text starts. Here's an image of where/how the settings apply:

@KatieLai, unfortunately suppressing the blank line when there is no prefix to print cannot be done with the way the SpineOMatic Cloud App is designed.  We could change this to enhancement request, but unless there are more users that need this functionality, it is unlikely to be added.


Show orders created by provider in Dashboard

On the dashboard chart for "orders created", break it up by lab provider with same colors as API Errors

I though about that, but thats a different resource (Orders vs Events). This is querying the Orders, not the Order Created Events. IMO that would be more appropriate for a Events chart.


chore: bump golang.org/x versions

The new Go "deps.dev" site is flagging up a few vulns here. Although our
versions mostly seemed like they were new enough to have the fixes for
each of them, updating them to @latest seems a reasonable action to see
if that clears any.
https://deps.dev/go/github.com%2Fshopify%2Fsarama/v1.29.0

Will keep an eye on https://deps.dev/go/github.com%2Fshopify%2Fsarama/v1.29.1-0.20210617163330-77748c50f2b2 to see if this clears them or not


Add default AzureFile Storage class to Azure File Csi Driver and deploy app by default

We have identified a missing default storage class for AzureFilehere while it is present for for AzureDisks here.

Potentially as this has proven to work for most customers, we could strive to add all default storage classes that we have also present in Vintage: https://github.com/giantswarm/azure-operator/blob/8a49ffc9e4545c423b2de34d592116229b171f36/service/controller/templates/ignition/default_storage_class.go

Also noticed that the azure-file app is not deployed by default - we should add it to default apps for CAPZ and push the app to proper catalog if needed.

@T-Kukawka I think we should add it to https://github.com/giantswarm/cluster-azure/blob/main/helm/cluster-azure/templates/helmreleases/csi.yaml file. Am I wrong?

yes - seems about right 👍  better place than default apps

PRs are merged. cluster-azure:v0.0.31 has azurefile-csi-driver-app  and the default storage classes. Closing this issue.


LLIL_CALL_STACK_ADJUST bug

After executing call, sp cannot be adjusted automatically

Hi @Chensne , is the issue resolved?
Usually this happens because our analysis does not figure out the stack adjustment of sub_19a5e. As a workaround, you can set the stack adjustment of it using the "Edit Function Properties" dialog: https://docs.binary.ninja/guide/index.html#edit-function-properties-dialog
Also, I am curious on what is causing our auto-analysis to be unable to figure out the stack adjustment. Is it possible to shrae the binary with us so that we can look into it?


OneBlink v1.5 & CivicPlus v1.6

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)
If this is your first time submitting to GitHub and you need some help, please sign up for this session.

[X] I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
[X] I attest that the connector works and I verified by deploying and testing all the operations.
[X] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[X] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
[X] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[X] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

[ ] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
[ ] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
[ ] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
[ ] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

@microsoft-github-policy-service agree company="OneBlink"

Hello @jdawg093 thank you so submitting the updates for your connectors. I would highly recommend separating the connectors and have them in two separate pull request. this will make it easier to submit to ISV Studio using the commit ID.
Please let me know if you have any questions.


WL-4542 Switch to VARCHAR rather than INTs for enum.

This makes the oauth code use VARCHARs rather than INTs for it’s enums as it makes the database more readable and helps to prevent problems when enums are changed.
This is also needed as we currently have this setup from our 10.x OAuth deployment and migrating to INTs seems like a backwards step.

Not very readable


Dependency badging

A concept seem to be mssing: dependancies which are themselves "badged", would not need to be checked for vulnerabilities. This would render the badging process contagious.

On September 7, 2015 3:29:40 PM EDT, enosgit<EMAIL_ADDRESS>wrote:

A concept seem to be mssing: dependancies that themselves are "badged"
do not need to be checked for vulnerabilities. This would render the
badging process contagious.

Reply to this email directly or view it on GitHub:
https://github.com/linuxfoundation/cii-best-practices-badge/issues/16

The idea of checking dependencies is already proposed in the "silver" list.  I was concerned about making it part of the basic list, because some projects have huge transitive dependencies that make that hard to handle or meet.
--- David A.Wheeler

I am not suggesting to move it to the basic list, but only that dependencies which have already archieved a badge may not need to be checked for vulnerabilities (although the fact that the badge is self-issued may pose limitations).

On September 7, 2015 11:37:57 PM EDT, enosgit<EMAIL_ADDRESS>wrote:

I am not suggesting to move it to the basic list, but only that
dependencies which have already archieved a badge may not need to be
checked for vulnerabilities (although the fact that the badge is
self-issued may pose limitations).

Reply to this email directly or view it on GitHub:
https://github.com/linuxfoundation/cii-best-practices-badge/issues/16#issuecomment-138421462

Hmm.  Tools like dependency check from owasp do not separate things that way. Also, as you note, the fact that the badges are self-reported means that checking by each project might be the better way to go.
--- David A.Wheeler

Alright, I only wanted to raise the issue. It's a pity though because it would have contributed to spreading the badge.

I think we should re-examine this in the future.  I think once the badge becomes more common, and the tools improve, this might be easier to do.