Refiling sections on the same file gives unexpected results

Describe the bug
When refiling a section to another in the same file that is below the result is not the expected
Steps to reproduce
In the file test.org with the contents:
* Heading 1
** Subheading 1
** Subheading 2
* Heading 2
**** SubSubheading 2.1

Place the cursor over Subheading 1 and try to refile to test.org:SubSubheading 2.1
Expected behavior
The section is well refined, so the result file is:
* Heading 1
** Subheading 2
* Heading 2
**** SubSubheading 2.1
***** Subheading 1

Right now the output is:
* Heading 1
***** Subheading 1
** Subheading 2
* Heading 2
**** SubSubheading 2.1

Emacs functionality
I guess it works as expected
Minimal init.lua
vim.g.mapleader = ' '

vim.cmd([[set runtimepath=$VIMRUNTIME]])
vim.cmd([[set packpath=/tmp/nvim/site]])

local package_root = '/tmp/nvim/site/pack'
local install_path = package_root .. '/packer/start/packer.nvim'

local function load_plugins()
  require('packer').startup({
    {
      'wbthomason/packer.nvim',
      { 'nvim-treesitter/nvim-treesitter' },
      { 'kristijanhusak/orgmode.nvim', branch = 'master' },
    },
    config = {
      package_root = package_root,
      compile_path = install_path .. '/plugin/packer_compiled.lua',
    },
  })
end

_G.load_config = function()
  require('orgmode').setup_ts_grammar()
  require('nvim-treesitter.configs').setup({
    highlight = {
      enable = true,
      additional_vim_regex_highlighting = { 'org' },
    },
  })

  vim.cmd([[packadd nvim-treesitter]])
  vim.cmd([[runtime plugin/nvim-treesitter.lua]])
  vim.cmd([[TSUpdateSync org]])

  -- Close packer after install
  if vim.bo.filetype == 'packer' then
    vim.api.nvim_win_close(0, true)
  end

  require('orgmode').setup({
    org_agenda_files = {
      './*'
    }
  }
  )

  -- Reload current file if it's org file to reload tree-sitter
  if vim.bo.filetype == 'org' then
    vim.cmd([[edit!]])
  end
end

if vim.fn.isdirectory(install_path) == 0 then
  vim.fn.system({ 'git', 'clone', 'https://github.com/wbthomason/packer.nvim', install_path })
  load_plugins()
  require('packer').sync()
  vim.cmd([[autocmd User PackerCompileDone ++once lua load_config()]])
else
  load_plugins()
  load_config()
end

Screenshots and recordings
No response
OS / Distro
Debian
Neovim version/commit
0.9.1
Additional context
If instead you place the cursor over SubSubheading 2.1 and try to refile to test.org:Subheading 1 the issue is similar. The expected output is:
* Heading 1
** Subheading 1
*** SubSubheading 2.1
** Subheading 2
* Heading 2

And right now it returns:
* Heading 1
** Subheading 1
** Subheading 2
* Heading 2
*** SubSubheading 2.1

Yes, the Refiling feature has some unexpected bugs. I'm currently working on understanding the code, because I want to fix this. My current understanding is, that the correct nesting/promotion of the subheading is done, but the "move" part of the refiling is somehow skipped.
I also observed, that when I refile a subheading into a file without a target headline, the contend is moved, but the subheading is not promoted to the topmost-one, which I would actually expect. Otherwise, if I do a lot of refiling of subheadings with different indent levels into one file, I get a completly messed-up structure instead of a flat list.
@kristijanhusak: This behavior is actually encoded in a unit test, so I would like to ask you, if this behaviour is intentional. If so, I would like to make it optional over a configuration variable, because for my daily use it is actually quite annoying.

that the correct nesting/promotion of the subheading is done, but the "move" part of the refiling is somehow skipped.

Moving in the same file is done here https://github.com/nvim-orgmode/orgmode/blob/master/lua/orgmode/capture/init.lua#L352. It works differently because there's no need to open same file remotely to move things around.

I also observed, that when I refile a subheading into a file without a target headline, the contend is moved, but the subheading is not promoted to the topmost-one, which I would actually expect

If I'm not mistaken, that's how Emacs orgmode works, but it's been a while. If you can double check how it behaves there that would be great.

@kristijanhusak: Yeah, I actually found this function and was already pretty sure, that the bug is right there. I'm still investigating, how the surrounding code actually works to implement my convenience wish, but for now here is the fix for the particular problem: #637

@lyz-code can you check if the issue is fixed now?

I also observed, that when I refile a subheading into a file without a target headline, the contend is moved, but the subheading is not promoted to the topmost-one, which I would actually expect

If I'm not mistaken, that's how Emacs orgmode works, but it's been a while. If you can double check how it behaves there that would be great.

I actually exhumed and repaired my 2years old emacs config to try this out and I realized the following:

Refiling target files are defined separately from the agenda files, although it's common to just define the agenda files
you cannot refile to a plain file, only to headings which are crawled from the files defined in org-refile-targets
org-refile-targets takes also a deepness level, which defines, which headings are actually considered as refile target

Here is an example:
(setq org-refile-targets '((org-agenda-files :maxlevel . 3))

For simplicity I would keep the possibility to directly refile to files, which actually has also value. But if no Heading is given, we should promote the headline to the first level, because it allows for a mutch cleaner and deterministic workflow.
@kristijanhusak If you agree, I will implement this and open a PR. Otherwise it probably ends up in a personal customization on my fork. 😉

If you agree, I will implement this and open a PR. Otherwise it probably ends up in a personal customization on my fork.

Yeah, go for it. Thanks for investigating!

If you agree, I will implement this and open a PR. Otherwise it probably ends up in a personal customization on my fork.

Yeah, go for it. Thanks for investigating!

Done: #641

If you agree, I will implement this and open a PR. Otherwise it probably ends up in a personal customization on my fork.

Yeah, go for it. Thanks for investigating!

I ran the tests on my local machine against the current nightly:

Everything is green here. Is it possible, to rerun the failed tests in Github actions? It seems, that I don't have the permissions for that.

@seflue I just re-run last github action https://github.com/nvim-orgmode/orgmode/actions/runs/7372025475?pr=642 and it failed on the same thing. We'll see once we merge some of these other PRs if the issue persists.

Sorry for the late response I've been away on holidays ^^.
The fix works perfect for me, thank you so much @seflue <3!!
May we close the issue? or wait for the CI thing to be fixed?

Since it's fixed, I'm closing this. Thanks for reporting!


[FMS] Automatic recharging

User story

As a SD
I want / need to make automatic recharging possible in the fms
So that the fms checks battery status of agvs the send order for recharging to the robots dependent on priority

Acceptance criteria

Check battery status and send order for charging under threshold
give shortest path to next charging station
Order abortion if battery level is too low for next order
set agv to offline

Definition of done (DoD)

Linter & Checker were performed and passed
Code Review has been completed
Code was merged in sprint release candidate
Updates are written in issue comments
Feature builds and tests successfully
Acceptance by product owner
User Story & Acceptance Criteria fulfilled

DoD general criteria

Feature has been fully implemented
Feature has been merged into the mainline
All acceptance criteria were met
Product owner approved features
All tests are passing
Developers agreed to release

Implemented automatic recharging on fleet management side. As demonstrated in video on Slack.


Write tests for asttools

asttools gets tested via the framework implementations, but having explicit tests for the functions we support would be nice, too.

I would love to do it

I am sorry @tcdent. I can't finish this contributing.

can i pick this up?


[SPARK-2309][MLlib] Generalize the binary logistic regression into multinomial logistic regression

Currently, there is no multi-class classifier in mllib. Logistic regression can be extended to multinomial classifier straightforwardly.
The following formula will be implemented.
http://www.slideshare.net/dbtsai/2014-0620-mlor-36132297/25
Note: When multi-classes mode, there will be multiple intercepts, so we don't use the single intercept in GeneralizedLinearModel, and have all the intercepts into weights. It makes some inconsistency. For example, in the binary mode, the intercept can not be specified by users, but since in the multinomial mode, the intercepts are combined into weights, users can specify them.
@mengxr Should we just deprecate the intercept, and have everything in weights? It makes sense in term of optimization point of view, and also make the interface cleaner. Thanks.

@dbtsai
Just back from vacation too:)
I used my old implementation of the matrix form of back propagation and made sure that it properly uses stride of matrices in breeze. Also, I optimized roll of parameters into vector combined with in-place update of cumulative sum.

@dbtsai BTW., have you thought about batch processing of input vectors, i.e. stack N vectors into matrix and perform optimization with this matrix instead of vector? With native BLAS enabled this might improve the performance.

@dbtsai I did batching for artificial neural networks and the performance improved ~5x https://github.com/apache/spark/pull/1290#issuecomment-70313952


Added Mutual Information to available correlations (Issue #10)

I have added a function to calculate mutual information between columns of a DataFrame, and modified the discover function to enable its use.

Hi @PeteBleackley, many thanks for your interest. I'm at PyConUK this weekend, I did reply from my phone but it doesn't seem to have been posted here.
You've used the classification MI function, I suspect we also need to include the regression equivalent: http://scikit-learn.org/stable/modules/generated/sklearn.feature_selection.mutual_info_regression.html#sklearn.feature_selection.mutual_info_regression
What dataset did you test this on? I'm wondering what it means to use only the classification version? What's your experience with MI (I have none!)?

I've generally used MI on discrete data in the past, but I find information theory based algorithms interesting in general. I'll have to comment out line 22 to test - unfortunately, Ubuntu won't let me upgrade Python above 3.5, which is a bit daft. However, I'll have a go on Monday.
According to the scikit-learn docs, we should use mutual_info_classif if the target column in discrete and mutual_info_regression if it's continuous. What would be the best way to test for that? Using the dtype of the column is the most obvious way, but probably not the most reliable.

I've started doing some testing on the Boston dataset, and it looks like we need to use sklearn.utils.multiclass.type_of_target to determine whether to use mutual_info_classif or mutual_info_regression


[SPARK-42112][SQL][SS] Add null check before ContinuousWriteRDD#compute function close dataWriter

What changes were proposed in this pull request?
This pr aims to add null check before ContinuousWriteRDD#compute function close dataWriter to avoid NPE.
Why are the changes needed?
Run the following commands:
mvn clean test -pl sql/core -Dtest=none -DwildcardSuites=org.apache.spark.sql.streaming.continuous.ContinuousSuite -am

All test passed, but there is a NPE in the test log:
- repeatedly restart
...

16:07:39.891 ERROR org.apache.spark.sql.execution.streaming.continuous.ContinuousWriteRDD: Writer for partition 1 is aborting.
16:07:39.891 ERROR org.apache.spark.sql.execution.streaming.continuous.ContinuousWriteRDD: Writer for partition 1 aborted.
16:07:39.892 WARN org.apache.spark.util.Utils: Suppressing exception in finally: null
java.lang.NullPointerException
	at org.apache.spark.sql.execution.streaming.continuous.ContinuousWriteRDD.$anonfun$compute$7(ContinuousWriteRDD.scala:91)
	at org.apache.spark.util.Utils$.tryWithSafeFinallyAndFailureCallbacks(Utils.scala:1558)
	at org.apache.spark.sql.execution.streaming.continuous.ContinuousWriteRDD.compute(ContinuousWriteRDD.scala:91)
	at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:364)
	at org.apache.spark.rdd.RDD.iterator(RDD.scala:328)
	at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:92)
	at org.apache.spark.TaskContext.runTaskWithListeners(TaskContext.scala:161)
	at org.apache.spark.scheduler.Task.run(Task.scala:139)
	at org.apache.spark.executor.Executor$TaskRunner.$anonfun$run$3(Executor.scala:554)
	at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1502)
	at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:557)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:750)

The test did not fail because Utils.tryWithSafeFinallyAndFailureCallbacks function suppressed Exception in finally block, but we should avoid this NPE being thrown.
Does this PR introduce any user-facing change?
No
How was this patch tested?

Pass GitHub Actions
Run the following command manually, and there is no NPE-related log in the test log after this pr.

mvn clean test -pl sql/core -Dtest=none -DwildcardSuites=org.apache.spark.sql.streaming.continuous.ContinuousSuite -am

cc @HeartSaVioR

also ping @dongjoon-hyun @HyukjinKwon

Thanks @dongjoon-hyun

Late +1, thanks for the work!


Column 'id' in where clause is ambiguous by action

Pokud udělám query s joinama více tabulek, které mají položku primární klíč id.
Pri následném volání akce (edit, delete, itemDetail.) se vyhodí chyba SQLSTATE[23000]: Integrity constraint violation: 1052 Column 'id' in where clause is ambiguous

Thanks for your feedback, i will fix that. Can you please write your issue in english? Thanks a lot!

Can you try to set different primary key? (DataGrid::setPrimaryKey('user.id'))

Yea i try this: $grid->setPrimaryKey('products.id');
but it throw error Cannot read an undeclared column 'products'.

Hmm, i won't do probably anything with that. A have two reasons:
1, Your query should be written solid (try specifying the columns (user.*, order.id AS order_id, etc)) and easy to understand
2, The latest Nette\Database won't let me use duplicate columns. User notice Found duplicate columns in database result set: 'id' (from user, order) is thrown.


Fixed Branch Universal Object & Update UITestBed

I fixed the Branch Universal Object so it always returning the new format.
Also, I confirmed that it is returning a format in parity with the Android object.
I updated the unit tests and the UITestBed app for testing.

Result of Integration 1
Duration: 12 minutes and 13 seconds
Result: All 223 tests passed, but please fix 2 warnings.
Test Coverage: 63%

Bump.


Volume Command

Pull request

[x] I have read and agreed to the code of conduct.
[x] I have read and complied with the contributing guidelines.
[x] What I'm implementing was assigned to me or was not being worked on and is a somewhat requested feature. For reference see our GitHub projects.
[x] I have tested all of my changes.

Feature
Music - Volume Setting

You need to use the method that specifys the flag to restrict this to Patreon guilds


chore: Anvil Preliminary Cypress tests

Pull Request Template
Use this template to quickly create a well written pull request. Delete all quotes before creating the pull request.

Description
In this PR we are enabling adding tests to Anvill Layout.
Adding preliminary tests to test

DnD
Suggested widgets
App Navigation
Widget Name Canvas

PR fixes following issue(s)
Fixes #28530

if no issue exists, please create an issue and ask the maintainers about this first

Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Chore (housekeeping or task changes that don't impact user perception)
This change requires a documentation update

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test


Lucky Train Implementation

Per game rules:

If Doctor Lucky moves into a room with a
player, that player takes the next turn. (Turns
will proceed to the left from that player.)
This means that you can sometimes take
several turns in a row by walking ahead of
Doctor Lucky. This is known as “riding the
Lucky Train,” and it’s a good way to move a
long way without using up Move cards.

The turn-based gameplay will need to be modified to allow for a conditional check of a lucky train effect.

Commit: https://github.com/arevi/Kill-Doctor-Lucky-Web-Port/commit/04524365e921eb747367f559bf91eb6e17cfe54c
Should be addressed, has been tested for local play will require online play test to ensure accuracy.

Online play test passed, the behavior is as expected.


Created static icon

#948  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @CatChen and the rest of your teammates on  Graphite


Optimized margin for mobile devices

⚠⚠⚠ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma
Tick the checkbox if you understand [x]:

[x] I have read and understand the pull request rules.

Description
This PR changes distribution of margin in status page.
On mobile devices the buttons stick to each other. Giving 50% of margin to elements from the div will fix the issue
Type of change

User interface (UI)

Checklist

[x] My code follows the style guidelines of this project
[x] I ran ESLint and other linters for modified files
[x] I have performed a self-review of my own code and tested it
[x] I have commented my code, particularly in hard-to-understand areas (including JSDoc for methods)
[x] My changes generates no new warnings
[x] My code needed automated testing. I have added them (this is optional task)

Screenshots

Before
After

The two buttons being stacked on that side seems a bit off center to me.
I think if we remove the icons on mobile this might be a better call. What do you think?

I will partly solve the problem, but it still be present on some devices. Also it will break style of the page.

Could you explain further?
Uptime Kuma uses a lot of icons in its user interface. While there are no longer any icons on status pages, I think in general it will look out of place.

Shorten the text is a good option


[Bug] lines series doesn't work with dataMin or dataMax

Version
5.4.1
Link to Minimal Reproduction
https://codepen.io/cyric/pen/OJNpLxJ
Steps to Reproduce

Create a lines series using 'dataMin', 'dataMax' or the default values
Observe the axes not respecting the data on load or after zoom

Current Behavior
A specific min or max must be defined otherwise the axis doesn't auto scale
Expected Behavior
The data to be visible, especially after scroll zoom. Similar to scatter
Environment
- OS: Debian
- Browser: Firefox 115.4.0esr
- Framework: Vue@3

Any additional comments?
Reopening of issue 13177

yes, lines do not work with axis dataMin or dataMax, but it's easy to extract those values from the data - Demo.

I ended up doing something similar. Calculating the minimum for the lines series, then using a function for the yAxis min to compare that to the rest of the data.


NFAuthenticationKey_Windows.zip Not Available from OneDrive Folder

Netflix add-on version
1.22.1
Operative systems used
Android
Kodi version used
Kodi 20 (Nexus)
Description of the bug
The NFAuthenticationKey_Windows.zip is not in the OneDrive folder linked in the Wiki
I think OneDrive deleted your file

Steps to reproduce the behavior
No response
Debug log - mandatory
paste.kodi.tv
Possible fix
No response
Additional context
No response
Screenshots
No response

links updated


Support restoring an account without restarting havenod

Test updates for haveno-dex/haveno#310.
Updated 'Can manage an account` test so that delete and restore account does not restart the havenod process.
I had issues with this line in the test so I ran it with that line commented out before any changes were made. It was throwing RpcError: wallet and network is not yet initialized Error: wallet and network is not yet initialized.

ping @duriancrepe

I am here

Rebased and superseded by https://github.com/haveno-dex/haveno-ts/pull/174


contradicting docs on $relatedQuery

In the documentation of $relatedQuery(), it suggests that

By default, any fetched or inserted items are also stored to the owner model’s property

Whereas it is actually defaults to false as indicated in relatedInsertQueryMutates

The default is false.

Is the suggested way to insert properties to db and model also now to do it manually?

The docs need updating. Thanks for bringing this up. Since objection 2.0, model instances are no longer mutated and the relatedInsertQueryMutates method will be removed in 3.0. So yeah, you need to assign/push the item to the model's relation manually.


Recommended pattern for calling e.preventDefault()

I had/have this problem where when I submit a form like, this
<form onSubmit={{validateAll(this.onSubmit)}}>
  <input type="submit" value="Submit" />
</form>

The validation errors would flash and then the page would "redirect" from /submit to /submit?, clearing the state. Once on /submit?, the form validation works as you would expect, and does not submit until the form is valid. I don't really understand why but I don't think this is related to revalidation.
One thing I did notice is that none of the examples use form - they use a div and a custom button.onClick handler. Just curious about what the suggested pattern for calling e.preventDefault() is. I personally prefer to use a form as I find it to be a bit more semmantically correct.

At the moment, I just do this.
  <form
    onSubmit={e => {
      e.preventDefault()
      validateAll(onSubmit)
    }}
  >

Seems OK.

Yes, make sense. As soon as I have a recipe for handling async validations, I'll think about what a good approach could be.

👍

Are you based in Vienna by the way?
I just flew in to Vienna this evening for React Vienna tomorrow  (we'll be filming it for the proect I run, pusher.com/sessions)!

Yes, very cool!

Think this is solved :)

So this is still in user land right now.
Except for debounce which takes care of calling preventDefault.

Yeah, and we want it to stay in userland, ye? It makes a lot of sense

Excellent!


Calender wont update on new month, stuck on last day

for the last 2 months now the calender will not start a new month, but stay on the last day.
any idea why it would do this?

Same here

Same. Any known fixes?

Same here, any fix?
Thx


[BUG] GlobalHotkey is typed into auto-focused input on render

Describe the bug
I mapped a Global key (e.g. 's') that renders a search component that autofocuses on the input. When I hit the letter 's', the component mounts and the 's' is typed into the input. This happens even if I manually set the input value to '' in componentDidMount.
How are you using react hotkeys components? (HotKeys, GlobalHotKeys, IgnoreKeys etc)
I'm using GlobalHotKeys.
Expected behavior
The component should render the component and the search input should come into focus, but nothing should be typed.
Platform (please complete the following information):

Version of react-hotkeys: 2.0
Browser [e.g. chrome]

Solved with adding event.preventDefault()


PS4 save edit?

I would assume the save file's structure is the same. Is it possible to deal and drop the save data, rather than designating the game path?

MCDSaveEdit depends on the official game data in order to show actual images from the game and to help fill out the save file with valid values (which it pulls from the game's localized resources in some cases). So without the game content it can really only modify the emeralds, levels, and item powers. Try using DungeonTools with your save files. If that doesn't work, then the PS4 files are in a format that we don't know how to parse yet.


validation: autodetect, store and continuously validate Data Availability mode.

The Data Availability mode (Ethereum vs non Ethereum) and provider (Celestia, etc) are important pieces of information to attach to each chain in the registry.
We are not able to infer the DA mode from rollup.json -- there are some environment variables for op-node and op-batcher which have useful information, but will not be able to reliably scrape these, either. We have a config field PlasmaConifg but it is not clear if this is actually the whole story with alt DA.
The remaining options are to:

ask and trust the chain contributor to declare the information
go on chain to detect and verify it.

We will go with the second option.
Definition of done:

add-chain tooling uses an L1 RPC client to scrape the latest batcher transaction* for the chain being added. It decodes that and infers if the chain is using alt DA (i.e. the DA mode boolean)

~IF the chain is using alt DA, we require them to have set an "ALT_DA_PROVIDER_BYTE`~

a new field is added to the superchain.ChainConfig type to record the boolean from the previous step, ~as well as the identifier byte if the DA mode is not ethereum. For now, the identifier byte can be stored in a field SelfCertifiedDAProviderByte to emphasise that it is not yet validated on chain.~
a validation check is added, which again scrapes the latest batcher transaction*, decodes the DA mode, and

for all chains checks it is consistent with the declared value now stored in the chain config
for standard chains (and standard candidate chains), ensures the DA mode is Ethereum

~This list of bytes is represented in the superchain-registry https://github.com/ethereum-optimism/specs/discussions/135 as an enum~

*Scraping latest batcher transaction
This is likely a useful reusable module for many validation checks, as well as the add-chain tooling. The idea is to do a binary search on the batcher signing account's nonce. This is a very quick way of finding the latest batcher transaction. The initial lookback window could be just the sequencing window.

EDIT: cutting some things from scope, these will be dealt with in a follow up ticket

@sebastianst as a first step, should we just check whether the BatchSubmitter address for a chain has sent a tx in the last SequencerWindow l1 blocks?
As an improvement to that check, how can we ensure the BatchSubmitter's tx actually posted l2 tx data and wasn't an unrelated tx coming from that address? How does the batch_inbox_address in the chain's config come into play?

Yes, although we should already check that the batcher sends it's txs to the batcher inbox address.
To confirm that a batcher tx really contains valid data for that chain, you would need to have a synced node for that chain and import the batches. But then you'd effectively already run a node 😅 Given that this is just a one-off check at an arbitrary point in time, not sure if we'd get any more meaningful guarantees from this.
Checking for the sequence window is a good default, because a live chain would post with at most this duration between batcher txs.


Downloaded XMLs after color changes are not updated until webpage refresh

Describe the bug
When exporting a theme after a previous download and color change, the downloaded XMLs are identical to the previous download. Webpage refresh fixes this issue.
To Reproduce

In Chrome browser - go to 'The Material Theme Builder' (Custom tab)
Click on 'Export' -> 'Android Views (XML)'
Change the colors.
Click on 'Export' -> 'Android Views (XML)'
The downloaded colors.xml is identical to the previous download before the color change (refreshing the page fixes this issue).

Expected behavior
The downloaded XMLs should be set to the new chosen colors.

Has been fixed in the most recent build


Extend Anchor Tag Helper to support multiple values for a given route data parameter

Feature Request: Extend Anchor Tag Helper's asp-route-{value} and asp-all-route-data properties to (properly) render parameters with multiple values.
Currently, ASP.Net Core MVC translates multiple values for a single query string parameter into an array. However, reversing the process—translating an array into a query string containing multiple values for  single argument—doesn't seem to be supported by Anchor Tag Helper.
Example:
If http://localhost:5000/SomeController/SomeAction?id=A&id=B is executed against the following action method:
public IActionResult SomeAction(string[] id) { /* ... */ }

Function argument id will be set to the equivalent of new[] { "A", "B" }.
However, try using Anchor Tag Helper to create the above link by using an id parameter set to new[] { "A", "B" }:
<a<EMAIL_ADDRESS>
In the link that's output, the query string's id parameter is the equivalent of doing .ToString() on the array then escaping it:
?id=System.String%5B%5D

The request is to change this behavior so that the query string is output as:
?id=A&id=B

and to make the equivalent change to asp-all-route-data so that it supports similar functionality.

Thanks for contacting us, @bgribaudo.
@dougbu, what can we do here?

First off, a workaround / recommendation: Don't use the short form for the query string, instead use

Is it required to use the short form for your scenario?

what can we do here?

Main thing we could do is introduce a new AnchorTagHelper property of type IDictionary<string, object> or RouteValueDictionary. (The first could support similar {prefix}-* attributes to what we have today with asp-route-{key}. The second might require a bit less code.) Later decisions would be mostly low level e.g. about choosing the prefix and deciding how to handle conflicts like asp-all-route-data="dictionary1" asp-all-some-new-prefix="dictionary2".

Unfortunately, there's a lot pushing back against making other changes in the near term e.g.

We can't change the type of the RouteValues property (IDictionary<string, string>) without introducing a breaking change
The IUrlHelper methods eventually called don't support currently passing a literal query string in, making  (already ugly) more difficult

Clearing labels and assignment. @mkArtakMSFT, @danroth27 please decide if this (probably small) enhancement is needed and when.

Also, we can't generate a A HTML tag with @Html.ActionLink with mutiple value because RouteValueDictionary doesn't support several same value (it is a dictionnary).
A other issue:
When a html select with multiple value and submit a form with get method, we obtain:
http://www.domain.com?id=1&id=2
When use method Microsoft.AspNetCore.WebUtilities.QueryHelpers.ParseQuery, id value is 1,2.
If you use http://www.domain.com/?id=1,2, model fill id with wrong value.

@zokiad

RouteValueDictionary doesn't support several same value

The key doesn't need to be repeated because RouteValueDictionary supports e.g. rvd["key"] = new[] { "value1", "value2" }

http://www.domain.com?id=1&id=2

The Values in the dictionary ParseQuery returns are StringValues. In this case, id is the equivalent of new[] { "1", "2" }. Just happens to ToString() as "1,2".

use http://www.domain.com/?id=1,2, model fill id with wrong value.

Use either ?id=1&id=2 or ?id[0]=1&id[1]=2

Oh yes!
Thus a workaround is to use @Html.ActionLink with RouteValueDictionnary.
But it is more clear the anchor taghelper. Perhaps, asp-all-route-data should accept RouteValueDictionnary?
Thank for our help.

I case anyone didnt read the response over in details, this works:
C#
Dictionary<string, string> routeData = new Dictionary<string, string>
{
    { "id[0]", "32" },
    { "id[1]", "1123" },
};

HTML
SomeLink

currently using [0] it would generate something like that:
Dictionary<string, string> routeData = new Dictionary<string, string>
{
    { "id[0]", "32" },
    { "id[1]", "1123" },
};

Uri generated: `/?id[0]=32&id[1]=1123 which is wrong. I want to have ?id=32&id=1123

custom model binders won't.

@schmitch we're straying from the original issue into something new. In particular, it's unclear why you're using a custom model binder that sounds less functional than the built-in ones.
We're very likely to lose track of your bug/feedback/question unless you:

Open a new issue
Explain very clearly what you need help with
If you think you have found a bug, include detailed repro steps so that we can investigate the problem


Integrate Bazel

Follow this awesome series: https://medium.com/wix-engineering/migrating-to-bazel-from-maven-or-gradle-part-5-how-to-avoid-jar-dependency-hell-with-bazel-57d60d0bc9f1

Already implemented.


Minor fixes to Eclipse setup notes after the update to JDK 8.

There is a chance that the following sentence should be updated:
"Compiler Compliance Level" to "1.5"

The usage of 1.6 (which you have changed) is not an oversight, nor is the 1.5 compiler compliance level. At the moment we promise Java 1.5 compatibility. However, we also use some (or maybe just one...) 1.6 API-s if they are available. Because the API differences between 1.5 and 1.6 are minor, the least painful is using 1.6 and then the build will still catch if you link to a non-1.5 API. So that's why it's like it is.

Thank you Daniel for the explanation.
I was actually confused by the following sentence from the same README file:
"You need JDK 8(!), Apache Ant and Ivy to be installed."

Java 8 is because of the build tools. Some build tools needs Java 7 I believe, so you need one more JDK over 5 and 6, and then why not Java 8, rather than 7. Docgen actually requires 8 for a while.

Thank you Daniel.
So, if I am getting it right, the dependency on JDK 8 (or 7) is only for the creation of the jar, not for its usage. And the Eclipse setup steps are about setting up how the jar is built, not about the JDK used in the build process (here I am guessing since I am not an Eclipse user).
If this is the case I will close/discard this branch.

The Java version chosen in Eclipse is a compromise made because you can't specify different Java version for different java files inside the same project. The jar is built by Ant, and has nothing to do with Eclipse (or ant other IDE). Anyway, yes, this can be closed as I see no problems.


Folder based project support

Being able to just open a folder and work with the files within it as a Node project would be really useful. This would help sharing amongst different tools (by not requiring a VS specific project file) and be similar to capabilities in other editors.

Now that Visual Studio 2015, this should perhaps be possible to add since ASP.NET 5 project supports a folder-based structure where files are not saved in the project files.

Still needs a lot of work, but the first stage of this work is done and will light up in Dev15.


Update the deduplication architecture document to reference samples

This document needs the following updates: http://www.medplum.com/docs/fhir-datastore/patient-deduplication

Links and references to bots and examples
Write up on human in the loop (#2679)
For clarity, should assume the Medplum is the target system

@reshmakh  I think this is a duplicate of #2679 . I'll close that one, as this is more detailed

Closing in favor of 2679


Reaction avatars not enabled for hidden items

Room for slight improvement: If an issue has a lot of comments, GitHub will snip some of them in the middle and fetch those on demand, as can be seen in sindresorhus/eslint-plugin-unicorn#169.

If those are expanded, their according reactions will not have avatars.

on-new-comments.ts should take care of that, but I suppose it stopped working.

@issuehunt has funded $40.00 to this issue.

Submit pull request via IssueHunt to receive this reward.
Want to contribute? Chip in to this issue via IssueHunt.
Checkout the IssueHunt Issue Explorer to see more funded issues.
Need help from developers? Add your repository on IssueHunt to raise funds.

@sindresorhus has rewarded $36.00 to @loilo. See it on IssueHunt

:moneybag: Total deposit: $40.00
:tada: Repository reward(0%): $0.00
:wrench: Service fee(10%): $4.00


Annotations of one category should be on the same height if possible

Originally reported by: Rüdiger Rolf (Bitbucket: rrolf, GitHub: rrolf)

at least when increasing the height like in #31 described the labels of one category should be close to each other and on the same height if possible within a track.

Bitbucket: https://bitbucket.org/opencast-community/annotation-tool/issue/32

Not needed after collapse feature was implemented

This would be more or less trivial with the new timeline. I'm reopening this to see whether there is still interest in this feature.
/cc @ebbertd @dagraf


Add more descriptive error messages

Is your feature request related to a problem? Please describe.
As of 4.2.1 there is decent error logging coverage, but it lacks somewhat in what details are reported about errors that occur.
A bit more context when errors occur => easier debugging and better bug reports.

Fixed by #116


pyserial should be a dependency.

We are already installing so much stuff, one more thing won't hurt, and this will prevent anyone from installing the package serial instead of pyserial.

6 months ago I would've said no. But yeah, sure. Why not.
On Wed, Dec 27, 2017 at 7:01 AM, Tom Swirly<EMAIL_ADDRESS>wrote:

Assigned #553 https://github.com/ManiacalLabs/BiblioPixel/issues/553 to
@adammhaile https://github.com/adammhaile.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/issues/553#event-1402444333,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6lGRo14N9QkCim-toRxhppeuL48uks5tEjG1gaJpZM4RNcGV
.


Implement Interactive rule

This PR adds a rule that can be used to test interactive (I/O) applications, that for example make use of a Scanner.
Demo
Echo.java
public class Echo {
    public static void main(String[] args) {
        final Scanner scanner = new Scanner(System.in);
        System.out.println(scanner.nextLine());
    }
}

EchoTest.java
public class EchoTest {
	@Rule
	public final Interactive interactive = Interactive.forClass(Echo.class);

        @Test
	public void testEcho() throws Throwable {
		// Feed a random string into the input.
		this.interactive.feedLine("a random string");

		// Get the output of the program.
		final String output = this.interactive.callMain().output();

		// Evaluate the output.
		Assert.assertEquals("a random string", output);
	}
}

@ninewise I have added an example.


Add string view support

I've noticed polars in particular has started to export Arrow C data with the "vu" format string for string views, but I don't see any support for those in nanoarrow. Is this something that can be added easily? I think the same API we have in place for strings can be used for string views as well?
@bkietz probably knows more

Sounds good. Will take a look if I get some free time


[Event Request] Mark Report 1086 "Job Calculate WIP" as protected

Sadly I cannot really modify the report as the global variables are not marked as protected. Simple request: please add a "protected". :-)

Was fixed in version 22.


collect cyclonus data across a variety of clusters and CNIs

Procedure:

spin up cluster with a CNI
run cyclonus job

check out https://github.com/mattfenwick/cyclonus/tree/master/jobs -- notice the different arguments for each CNI, this is because of their differences in support for some features

capture:

cyclonus invocation
cyclonus job logs
all cluster info (version, ip version, etc.)
all CNI info (config, version, etc.)

IPV4 Progress table:

Cluster
CNI
Version
Linux
Windows

KinD
Calico
v3.18.0
✅
❌

KinD
Antrea
v0.12.0
✅
❌

KinD
Antrea
v0.12.2
❌
❌

KinD
Cilium
v1.9.4
✅
❌

KinD
Cilium
v1.9.5
❌
❌

KinD
ovn-kubernetes
???
❌
❌

GKE
Calico
v3.18.0
❌
❌

GKE
Antrea
v0.12.2
❌
❌

GKE
Cilium
v1.9.5
❌
❌

GKE
ovn-kubernetes
???
❌
❌

EKS
Calico
v3,18.0
❌
❌

EKS
Antrea
v0.12.2
❌
❌

EKS
Cilium
v1.9.5
❌
❌

EKS
ovn-kubernetes
???
❌
❌

IPV6 is not yet supported by Cyclonus

@mattfenwick looking to provide logs via KinD. I have bunch of machines here.

Antrea v0.12.2 with additional files about the env and triggering.
kind-output-antrea-v0.12.2.tar.gz

Cilium v1.9.5 data
v1.9.5-cilium-output.tar.gz

weavenet-output-Mar14-2021.tar.gz

More results from @dougsland and @rikatz:
gke-calico1.log.gz
gke-cilium.log.gz
output-weavenet-Mar-13-2021.tar.gz

ovn-kubernetes from @dougsland :
output-ovn-kubernetes.tar.gz

ovn-kubernetes https://github.com/mattfenwick/cyclonus/runs/2130448921?check_suite_focus=true

🎉 Moved to https://github.com/K8sbykeshed/cyclonus-artifacts 🎉


Reapplied dcolish's Python3 patch to the current code base

Hi,
I was looking for a Python3 version of redis-py and found https://github.com/andymccurdy/redis-py/pull/122 by dcolish. Since it wasn't merged to the current code base, I manually merged it myself. For me, it runs all test cases both on Python and Python3 (except one about ZADD, but that fails on master too).
I hope this can be helpful.
Greetings,
Julian

bump

Your bump hasn't fallen upon deaf ears... just busy ones. I apologize for the lack of response.

FYI, I checked out the network graph and found this...
https://github.com/froystig/redis-py
All tests pass and it indeed works with python 3 (tested in Blender 2.62 -- python 3.2.1)


Chore add -Wconversion and remove some unused code

Proposed changes
add -Wconversion and remove some unused code
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

@BiteTheDDDDt
Hi, when I compiled the BE using command ./build.sh --be, there's an error:
doris/be/src/util/mem_info.cpp:517:38:
error: implicit conversion turns floating-point number into integer: 'double' to 'int64_t' (aka 'long long') [-Werror,-Wfloat-conversion]
    _s_soft_mem_limit = _s_mem_limit * config::soft_mem_limit_frac;
                      ~ ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.

And I noticed that the related code has been changed here. Could you please give me some hints? Thanks a lot!


Subtitles not working from Plex Media

Unless I've configured it wrong, I'm unable to view subtitles from my shows when I configured the schedule and the channel to prefer English subtitles. Linked below is my settings I've put for my schedules and channel:

On plex, i can select the subtitles so they are there, I just don't know how to select it so that Ersatz shows subtitles by default for this channel

This issue should be re-tested, as there have been numerous improvements in the latest dev builds for subtitle extraction.

Hi, I just started playing today with ETV, and I'm also finding it hard to display subtitles. Any new development or things I should be aware of regarding this issue?


Fix org label open count, including close count issue

Fixed using organization tags to see open issues in the tag list including closed issues count

does it also affect v1.17.0 ?

does it also affect v1.17.0 ?

yes, v1.16 also have this problem

can you backport it to release branches for v1.17 and v1.16 ?

can you backport it to release branches for v1.17 and v1.16 ?

done #20364 #20365


fix: capitalization of termux-setup-storage

Before fixing:

Fixed:

(Via build)

@2096779623 how did you made termux background like that?

oh, right! thanks for noticing

Looks like you are packaging mangal for termux, thank you! I'll merge it into the main soon (I hope). Need to finish some other stuff before it

@2096779623 how did you made termux background like that?

Just a ssh client on windows.


new interaction file to load

PMID:25795664 has some genetic interactions that have scores associated, and therefore fit BioGRID's "negative|positive genetic" evidence types. Because those (rightly) aren't available in Canto, I've put them in a file in BioGRID's format, and stuck it in a new subdirectory in pombe-embl/external:
pombe-embl/external_data/interactions/PMID_25795664_scored_interactions.tsv
I don't think there's any great rush, but it would be nice to get it loaded somewhere along the line. I'm working on Canto session approval for the paper, and I can follow up later to alert them whenever we add these annotations (i.e. approving the rest doesn't have to wait).

might be good to chat about this...on the list for this week.
how many annotations?

% wc external_data/interactions/PMID_25795664_scored_interactions.tsv
  79    1106    9785 external_data/interactions/PMID_25795664_scored_interactions.tsv

Kim should be able to load this.
Removing the "discuss" lable.
Kim let  us know if any questions.

try loading this...

I tried loading the new file and it didn't work out.
The current loader only supports the BioGRID download format:
https://wiki.thebiogrid.org/doku.php/biogrid_tab_version_2.0
We'll need a new loader to support the BioGRID upload format.

Drat. In the meantime, I can amend the existing file. Watch this space ...

OK, I've added external_data/interactions/PMID_25795664_scored_interactions.tab2.txt ... hope it loads. I put "-" in a lot of the columns they say are for various IDs. Let me know if I should change anything.

did this work?

I've just added a header line and now it works.  I've added it to the nightly load and it should be visible on Friday morning.

Is this a duplicate of the ticket you closed earlier today?

It looks like the load didn't work.  There are 80 interactions in the file but a lot less than 80 interactions here:
https://www.pombase.org/reference/PMID:25795664
I'll have a look at it.

It looks like the load didn't work. There are 80 interactions in the file but a lot less than 80 interactions here:
https://www.pombase.org/reference/PMID:25795664

Yep, it looks like the pub page only shows the annotations done in Canto. Again, shout if I can/should do anything with the file. (Unassigning myself in the meantime, tho.)

I think this is fixed, possibly in time for tonight's load.  The file has PubMed IDs with a "PMID:" prefix rather than just a number.  The loader now copes with that.

Fixed!  There are now lots of interaction:
https://www.pombase.org/reference/PMID:25795664


Update nodes.py

Not sure why this works t5 strength and a clip_l seems to greatly improve movement with new CogVideoXFun workflow.

Here is an example workflow and video with the dual clip text encode node. In this example I have to increase the clip_l strength to 4 and t5 to 1.15 and decrease negatives to 0.5 to get the gorilla to move. With default cogvideo text encode I just get static image. I'm still trying to get him to take a drink and spin in a circle...
https://github.com/user-attachments/assets/7b39eef0-8ee4-4b2a-b22c-415a76f45576
cog_video_dual_clip_gorilla.json

Oh yeah that's a good idea, thanks!

Just an update since this seems to produce errors on CogVideoX official img2vid workflow, I got a triple clip version of this working for CogVideoXfun with clip_g, clip_l, and t5. It also works for flux image generation and makes a pretty big difference.
it's some refactored code from comfyui sd3 triple clip loader and other code  Will post soon CogVideoX version here.  If you want to test ahead of time my discord name is 311_code.


Store workspace into path

Description

Issues Resolved

Screenshot

Testing the changes

Check List

[ ] All tests pass

[ ] yarn test:jest
[ ] yarn test:jest_integration

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] Update CHANGELOG.md
[ ] Commits are signed per the DCO using --signoff

Codecov Report
Attention: 13 lines in your changes are missing coverage. Please review.

Comparison is base (1e980fa) 66.78% compared to head (6b7cfb1) 66.63%.

:exclamation: Current head 6b7cfb1 differs from pull request most recent head b803de8. Consider uploading reports for the commit b803de8 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main       #6      +/-   ##
==========================================
- Coverage   66.78%   66.63%   -0.15%
==========================================
  Files        3284     3286       +2
  Lines       63092    63143      +51
  Branches    10048    10057       +9
==========================================
- Hits        42134    42078      -56
- Misses      18486    18588     +102
- Partials     2472     2477       +5

Flag
Coverage Δ

Linux_1
?

Linux_2
?

Linux_3
?

Linux_4
?

Windows_1
35.26% <25.92%> (-0.02%)
:arrow_down:

Windows_2
55.07% <77.58%> (-0.14%)
:arrow_down:

Windows_3
43.66% <25.92%> (-0.19%)
:arrow_down:

Windows_4
35.35% <31.48%> (-0.02%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

...lication/capabilities/capabilities_service.mock.ts
100.00% <ø> (ø)

src/core/public/core_system.test.mocks.ts
100.00% <100.00%> (ø)

src/core/public/core_system.ts
91.95% <100.00%> (+0.38%)
:arrow_up:

src/core/public/http/http_service.ts
30.76% <ø> (-53.85%)
:arrow_down:

src/core/public/mocks.ts
59.09% <ø> (ø)

src/core/public/plugins/plugin_context.ts
44.44% <ø> (ø)

...c/core/public/workspace/workspaces_service.mock.ts
100.00% <100.00%> (ø)

...e/server/capabilities/capabilities_service.mock.ts
75.00% <ø> (ø)

...c/core/server/capabilities/capabilities_service.ts
100.00% <ø> (ø)

src/core/public/http/base_path.ts
72.00% <92.30%> (-16.24%)
:arrow_down:

... and 3 more

... and 11 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


chore: Updated for mono_repo 6.0.0

Updated project mono_pkg.yaml configs for latest mono_repo 6.0.0

Need to re-run mono_repo generate

@subfuzion – want me to land this?

That would be great thanks. I had a power failure and can't boot my machine
right now.
On Thu, Dec 16, 2021 at 11:44 AM Kevin Moore @.***>
wrote:

@subfuzion https://github.com/subfuzion – want me to land this?
—
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/functions-framework-dart/pull/305#issuecomment-996130645,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABG76WL5QDSKOMWCEXN2G3URI6THANCNFSM5KG7MPGA
.
You are receiving this because you were mentioned.Message ID:
@.***
com>

--
Tony Pujals
Senior Developer Advocate
Google Cloud | Anthos
GitHub: @subfuzion
Twitter: @tonypujals


fix(reporter): allow prefix overrides on win32

Similar to #57, which seems to have been abandoned, though implemented quite differently.
In addition to adding tests for the functionality I wanted to add, I've also:

Made the npm scripts run cross-platform (they were failing on Windows; this has been checked on Linux)
Remove the win32-specific branch of color testing as the color package does the right thing now (and this test was failing on win32 before I removed that block)
Add a coverage-report npm script to generate the html coverage report as required (which is how I found code to cover)
Add coverage for final error reporting, just to bring coverage up a bit, since I've seen warnings in other PRs about coverage dropping and I thought it might be a nice thing to do (:

Coverage increased (+14.1%) to 84.444% when pulling 26247abc04e646d361e53dfdc10a8ed09e4424b5 on fluffynuts:master into 404cb09db962452627e693587c1637d9db1c00aa on mlex:master.

Apologies for the last few trailing commits: it appears as if mocha-runner, with a current Node (7.x) on win32, pulls in mocha; but not with a lower version of Node (4.8.0) on Linux, causing Travis to fail on the coverage script.
I've added an explicit dependency on mocha which makes Travis happy.

This PR has been open nearly a month now and I still can't read output on a client's TFS server. I'm forking on NPM too, despite really, really not wanting to. Please shout if this PR is ever accepted and pushed to npmjs.com.
I'm a little dismayed that no attention was given to this PR. Not only did I fix a long-standing issue (though I'm not the first to provide a patch for the behavior), I added coverage on other areas of code which weren't covered in the past because I saw historical discussions about the desire of the project to maintain decent coverage. It feels a little like the effort was wasted, to be honest.

@fluffynuts It looks like your PR is good to go. Sorry, I've not really paid attention to this repo as I don't use the reporter day to day anymore.
Please don't be discouraged. If you want to help increase coverage I would suggest a separate PR but I'm okay with merging this in if I pull it down and everything works as expected.

As a note, there are still some tests failing on the Windows 10 machine (this is what I'm developing on locally). I had this problem with the last PR I had and a case needs to be explicitly declared for the tests failing only on Windows 10.
Here is the output:
$ npm test

><EMAIL_ADDRESS>test C:\Users\tjmp68\Projects\karma-spec-reporter
> mocha-runner --reporter spec test/**/*.spec.js

 ▸  [14:09:58] Config: C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\configs\mocha.json

  SpecReporter
    when initializing
      and on a windows machine
        √ SpecReporter should have icons defined appropriately
        √ SpecReporter should allow overriding success icon only
        √ SpecReporter should allow overriding failure icon only
        √ SpecReporter should allow overriding skipped icon only
        √ SpecReporter should allow overriding all icons
      and colors are not defined
        √ SpecReporter should be defined appropriately
        √ should set USE_COLORS to false by default
      and colors are defined
        √ SpecReporter should be defined appropriately
        √ should set USE_COLORS to true
        1) should set the BaseReporter function's colors
      and there are configurations set for the spec reporter
        and suppressFailed is truthy
          √ should return nothing for specSkipped
        and suppressSkipped is truthy
          √ should return nothing for specSkipped
        and suppressPassed is truthy
          √ should return nothing for specSuccess
        and suppressErrorSummary is truthy
          √ should set the suppressErrorSummary flag to true
        and showSpecTiming is truthy
          √ should set the showSpecTiming flag to true
    functionality
      onRunComplete
        with no browsers
          √ should reset failures and currentSuite arrays
          √ should call writeCommonMsg
          √ should call write
        with browsers
          and there are no failures
            √ should call to write all of the successful specs
            √ should reset failures and currentSuite arrays
            √ should call writeCommonMsg
          and there are failures
            and suppressErrorSummary is true
              √ should call to write all of the failed and successful specs
              √ should reset failures and currentSuite arrays
              √ should call writeCommonMsg
              √ should not call to log the final errors
            and suppressErrorSummary is false
              √ should call to write all of the failed and successful specs
              √ should reset failures and currentSuite arrays
              √ should call writeCommonMsg
              √ should call to log the final errors
      logFinalErrors
        2) should write a single failure out
        3) should truncate messages exceding maxLogLines in length
        4) should write out multiple failures
      onSpecFailure
        with FAIL_FAST option
          √ should throw an error

  29 passing (56ms)
  4 failing

  1) SpecReporter when initializing and colors are defined should set the BaseReporter function's colors:

      AssertionError: expected '%s %s FAILED\n' to equal '\u001b[31m%s %s FAILED\u001b[39m\n'
      + expected - actual

      -%s %s FAILED
      +%s %s FAILED

      at Context.<anonymous> (C:\Users\tjmp68\Projects\karma-spec-reporter\test\index.spec.js:179:45)
      at callFn (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runnable.js:326:21)
      at Test.Runnable.run (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runnable.js:319:7)
      at Runner.runTest (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:422:10)
      at C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:528:12
      at next (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:342:14)
      at C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:352:7
      at next (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:284:14)
      at C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:315:7
      at done (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runnable.js:287:5)

  2) SpecReporter functionality logFinalErrors should write a single failure out:

      AssertionError: expected [ Array(5) ] to deeply equal [ Array(5) ]
      + expected - actual

       [
         "\n\n"
      -  "1) should do stuff\n"
      -  "     A B\n"
      -  "     The Error!"
      +  "\u001b[31m1) should do stuff\n\u001b[39m"
      +  "\u001b[31m     A B\n\u001b[39m"
      +  "     \u001b[90mThe Error!\u001b[39m"
         "\n"
       ]

      at Context.<anonymous> (C:\Users\tjmp68\Projects\karma-spec-reporter\test\index.spec.js:433:32)
      at callFn (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runnable.js:326:21)
      at Test.Runnable.run (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runnable.js:319:7)
      at Runner.runTest (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:422:10)
      at C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:528:12
      at next (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:342:14)
      at C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:352:7
      at next (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:284:14)
      at C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:315:7
      at done (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runnable.js:287:5)

  3) SpecReporter functionality logFinalErrors should truncate messages exceding maxLogLines in length:

      AssertionError: expected [ Array(5) ] to deeply equal [ Array(5) ]
      + expected - actual

       [
         "\n\n"
      -  "1) should do stuff\n"
      -  "     A B\n"
      -  "     The Error!"
      +  "\u001b[31m1) should do stuff\n\u001b[39m"
      +  "\u001b[31m     A B\n\u001b[39m"
      +  "     \u001b[90mThe Error!\u001b[39m"
         "\n"
       ]

      at Context.<anonymous> (C:\Users\tjmp68\Projects\karma-spec-reporter\test\index.spec.js:457:32)
      at callFn (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runnable.js:326:21)
      at Test.Runnable.run (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runnable.js:319:7)
      at Runner.runTest (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:422:10)
      at C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:528:12
      at next (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:342:14)
      at C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:352:7
      at next (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:284:14)
      at C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:315:7
      at done (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runnable.js:287:5)

  4) SpecReporter functionality logFinalErrors should write out multiple failures:

      AssertionError: expected [ Array(9) ] to deeply equal [ Array(9) ]
      + expected - actual

       [
         "\n\n"
      -  "1) should do stuff\n"
      -  "     A B\n"
      -  "     The Error!"
      +  "\u001b[31m1) should do stuff\n\u001b[39m"
      +  "\u001b[31m     A B\n\u001b[39m"
      +  "     \u001b[90mThe Error!\u001b[39m"
         "\n"
      -  "2) should do more stuff\n"
      -  "     C D\n"
      -  "     Another error!"
      +  "\u001b[31m2) should do more stuff\n\u001b[39m"
      +  "\u001b[31m     C D\n\u001b[39m"
      +  "     \u001b[90mAnother error!\u001b[39m"
         "\n"
       ]

      at Context.<anonymous> (C:\Users\tjmp68\Projects\karma-spec-reporter\test\index.spec.js:488:32)
      at callFn (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runnable.js:326:21)
      at Test.Runnable.run (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runnable.js:319:7)
      at Runner.runTest (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:422:10)
      at C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:528:12
      at next (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:342:14)
      at C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:352:7
      at next (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:284:14)
      at C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runner.js:315:7
      at done (C:\Users\tjmp68\Projects\karma-spec-reporter\node_modules\mocha-runner\node_modules\mocha\lib\runnable.js:287:5)

 ✘  [14:09:58] undefined
npm ERR! Test failed.  See above for more details.

This is strange -- I spent a reasonable amount of time ensuring that the tests worked across windows and linux (hence the changes to the script block in package.json). Also, re-running the tests on my win10 laptop (both from my fork and from a fresh clone of this repository), everything passes.
There must be something different between our machines?
I have been running this with node 7.7.3 (via nvm). What version of node are you using? Perhaps there's a difference in how they output colors, since the failures are only due to color escape codes which would look natural on a *nix term (and are obviously interpreted by something lower down).
I'm currently downloading 7.8.0 (latest stable) and will then try the last stable (6.10.1)

(btw, thanks for accepting the PR -- if there is an issue caused by something like expecting too high a node version, I'll sort it out)

It is strange. I had no idea what was happening, but it seemed to take place after the upgrade of the colors dependency PR #59 . I didn't really have time to look into it, but can make an issue for it if need be.
I think you might be on to something, as I am running node 6.10.0. I don't have nvm installed on my machine yet, but can definitely find a way if you need help!
Thanks for your patience 😄 If it makes you feel better I just cleared out a few PRs a month ago that were sitting for half a year lol
I'll make sure to pay more attention if someone has put in the work for a PR, my apologies again for the delay!

Googling around a bit, it looks like this is taken care of by libuv, which node is using to deal with ansi color escape sequences on Windows, where the console has traditionally not dealt with those sequences. I happen to know that traditional win32 color console output is tedious, having done it enough from c and c#.
We get to see the sequences in tests before they are handed off to the system lower down, where they are available. It's reasonable to assume that the workaround may have previously been dealt with higher up in an older version of colors.
The question you have to consider is what minimum version of node you'd like to be supported for running tests (as this obviously doesn't affect runtime). On *nix, it won't matter, and conceivably, sometime in the future, cmd.exe may support these codes since Microsoft is punting the embedded Linux idea.
It's really up to your preference: either adding the information about test running to the README.md to avoid confusion by anyone else down the line, or if we can figure out the exact version at which the switch happens, creating conditional tests based on node version and platform being win32.
Your call.


Is there support for Charmaps or other Text formatting?

I can mark a block as .text in the sym file but the ROM I'm looking at isn't using standard ASCII so I'd need a Character Map or some other option to offset and make the text readable.
Is there a way to do that? Am I going about this the wrong way?

That seems like a good idea, the question is how mgbdis should be made aware of the charmap. Perhaps using a table file, and specifying the table file to use in the .text label somehow?


Make sure we can scale to lots of runtimes

We should make sure we can scale to lots of runtimes by creating a test case which registers lots of runtimes (can be simple runtimes) and does some benchmarks.
A lighter test with multiple runtimes should also be added as an E2E test to ensure that everything works correctly with multiple runtimes.

There is an overhead for runtimes (even ones that don't submit any commitments) as certain actions need to happen on each epoch transition (committee election, inserting epoch transition blocks).

In #2529 RuntimeID is now passed dynamically to the worker and is not compiled in the binary anymore. To test this, new e2e test multiple-runtimes which loads arbitrary number of runtimes using the same runtime binary was added.
Additionally, a number of race conditions and hangs have been fixed in #2650 and #2669. We were able to repeatedly run multiple-runtimes with 32 runtimes using a single worker on a machine with 16 GiB of memory. Enabling SGX required a little more than 2x the amount of memory.
More detailed benchmarks will be done in #2536. Closing.


Virtcontainers store

Description and goals
This is a rewrite of the resource_storage and its filesystem_resource_storage backend, with the following goals:

Provide a neutral store API for virtcontainers. The API and the physical backend should be decoupled.
Provide a filesystem backend implementation and make it the default one for virtcontainers.
Provide a separate store package for the core virtcontainers code to consume. Since several components are depending on a store API, this will break these dependencies and allow us to move #1059 further away.

Shortcomings
There are a lot of places in the virtcontainers code where we assume that our store backend will be a local filesystem one. This is practically just right but ideally we should not make any of those assumptions. This PR does not completely remove those assumptions, but the store package top level API is neutral enough so that we could eventually remove them from the core virtcontainers code.

All, I will address the pending comments and fix the CI early next week. I have prepared an additional PR on top of that one to show how we could start moving large pieces of code into their own packages.
See for example the hypervisor package creation at #1208

Basic CI passes, let's retest.

/retest

I just fixed a network NS leak caused by a typo in the Store conversion patch.

/retest

@sboeuf @WeiZhang555 @bergwolf @jodh-intel The CI passes now.

LGTM
Let's retest it again before it can be merged.
/retest

@WeiZhang555 The fc and ARM CI are broken, as expected :-/


The LinkedBlockingQueue should not have a length. (currently 10)

The LinkedBlockingQueue should not have a length.
If a message received has more then 10 messages being send back it
renders the socket useless.  Since the bufferQueue.put() method keeps
waiting forever for the queue to shrink.

In the current situation reaching the buffers limit may cause a deadlock situation which is probably why you came up with this change.
Thanks for calling attention on that!
On the other hand this fix is not a long term solution because it makes it kind of easy to reach OutOfMemory states.
Just image a situation where you constantly send messages and the underlaying socket is not able to transport the data in time.
A better way would be to not increase the limit of the LinkedBlockingQueue to much but actively schedule the data transfer if the buffer is full. That would keep the buffer from constantly growing and would eliminate deadlock possibility.
If possible IO operations would be processed asynchronous but if not the IO operations would be performed by the thread calling the send.
@TooTallNate
We could also solve the problem AND gain performance by making the handling of all the SelectionKeys asynchronous which should not be such a huge thing.


pull request for e2e test at 01/13/2017 02:15:12

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


[Question]: Hanging at parsing files

Describe your problem
I installed locally ragflow but it get stucked at 0.7% or 6.7%

I am using:

ollama (llama3.2 and nomic-embed-text).

RAGFLOW_IMAGE=infiniflow/ragflow:v0.9.0
or dev
or dev-slim
or latest

MEM_LIMIT: I let it be 12GB (my computer has 15 GB in total) (in .env file)

vm.max_map_count=262144

default es options or I added - "ES_JAVA_OPTS=-Xms2g -Xmx2g" in docker-compose-base.yml

I also checked that in htop, there was running task_executor.py processes.
I do not know why I can not parse file ? I also saw many issues in github and https://ragflow.io/docs/dev/faq#43-why-does-my-document-parsing-stall-at-under-one-percent , but none were successful.  I restarted again and again, uploaded the most simplest .txt file (one line), or tried installing by watching tutorial videos but it not worked !
Someone please helps me. It took me really long time. :(

The ragflow image 0.9.0 is very old. Please try infiniflow/ragflow:v0.12.0.
Hovering on the text Parsing ...% will show the progress details such as parsing errors.
And check the log files such as <ragflow_root>/docker/ragflow-logs/api/ERROR.log.

Hi @yuzhichang . it is still stucked !

I pulled v0.12.0 as you said. Here is the ERROR.log file:

Please help me ! thanks

Same issue here,

Process Duration:
59.62 s
Progress Msg:
Task has been received.
Page(1~13): OCR is running...
Page(1~13): OCR finished
Page(1~13): Layout analysis finished.
Page(1~13): Table analysis finished.
Page(1~13): Text merging finished
Page(1~13): Finished slicing files(8). Start to embedding the content.
Page(1~13): Finished embedding(1.13)! Start to build index!

Hi @yuzhichang . it is still stucked !
I pulled v0.12.0 as you said. Here is the ERROR.log file:
Please help me ! thanks

Appearantly this is a problem happening with elastic search. i couldnt solve this yet but it seems to be realted to elastic search domain resolve or elastic search port. can you share your service_conf and docker ps for the related containers to check ports?

Check all log files under <ragflow_root>/docker/ragflow-logs.

Hello, I also have the same problem where document parsing stuck at the building index phrase.

Also, the docker terminal of ragflow-server keeps showing this message:

Looking forward for a fix

I'm here with the same issue. Is there any update?


[Feature request] Markdown support

Firstly, thanks for this awesome extension.
I have the following suggestion:
Part 1
Marker description can render markdown parsed by built-in markdown-it instance from vscode. To capture the built-in parser instance,  your extension can masquerade as markdown extension, but instead of injecting a plugin it just saves the provided parser instance to a variable for later use.
Part 2
The second part might be a bit controversial and "ugly" from architectural standpoint, but it provides a great benefit (IMHO) which would be (comparably) difficult to achieve otherwise.
Instead of storing descriptions inside json file, they are stored externally as .md files. For example: each marker has a unique id, and an .md file with the name matching its id will contain corresponding description.
Why? Because vscode has a built-in setting for updating links in .md files when target file is moved or renamed: markdown.updateLinksOnFileMove.enabled. If you don't feel like re-implementing it, existing code can be leveraged by putting descriptions into .md files so vscode will take care of it.
This is how VSCode finds links in markdown files: link.
Single markdown file
Alternatively, all descriptions can be stored within a single markdown file:
# 1569753 Averdale (city)
population: 420
[details](/some/file.md)

## Districts

### Port
...

### Market
...

### Slums
...

# 1578552 Welwood forest

![image](/images/forest.png)

[details](/some/folder/welwood.md)

In these examples 1569753 and 1578552 are marker ids (followed by names). Note that I used h1 headings to define anchors: this is not ideal (such text could be contained within marker description as valid markdown) but from the top of my head I don't see a good solution that is guaranteed to never clash with valid markdown.

Brainstorming format for markdown file:
<leaflet-marker id="1569753" name="Averdale (city)">

population: 420
[details](/some/file.md)

# Districts

## Port
...

## Market
...

## Slums
...

</leaflet-marker>
<leaflet-marker id="1578552" name="Welwood forest">

![image](/images/forest.png)
[details](/some/folder/welwood.md)

</leaflet-marker>

Markdown supports using html tags. All built-in html elements use one word definition, so name leaflet-marker should be safe and future-proof. If the element leaflet-marker is not defined, the preview will just ignore it. But it can still be parsed easily with regex.

JSON inside markdown
To keep everything in one file, JSON map definition can be stored inside a code block at the very beginning of markdown file.
It would make sense to use frontmatter, but I'm not sure built-in parser supports it without plugins.

It seems vscode does include frontmatter plugin for markdown-it:

https://github.com/microsoft/vscode/blob/167cae71b1b7aba73accb6596158f989f92d2ce1/extensions/markdown-basics/syntaxes/markdown.tmLanguage.json#L12
https://github.com/markdown-it/markdown-it?tab=readme-ov-file

Either way, this file is not meant to be edited manually so it's not super important IMHO. What matters is that built-in link updater will work with it.

I'll look into how to implement these suggestions.
The parsing shouldn't be too difficult, I had been working on unreleased integration with Dendron that can be adapted for that.
Regarding Part 2: Thank you for the information, that is very useful for future consideration.
It's something I wanted to implement, just didn't get around to yet. I think, I'll prefer having descriptions as separate files and use either links or ids to reference them.

Separate files was my first thought, but I see one potential problem with it: polluting the file picker (Ctrl + P) and slowdown from things like updating links that have to go through all files in the workspace. To what extent it actually is a problem (if at all), I don't know.

I've stumbled upon a problem when trying to capture MarkdownIt instance by masquerading as a markdown extension: the initialization of markdown extensions happens when you first open a markdown file, not when the extension is activated.
As a workaround, I made the extension check if MarkdownIt instance is already captured. If it is not, produce an error with a button that forces MarkdownIt instance capture:
if (md == null) {
  const option = await vscode.window.showErrorMessage(
    `Error: MarkdownIt instance was not captured`,
    'Force capture'
  );
  switch (option) {
    case 'Force capture':
      await vscode.workspace
        .openTextDocument({
          content: `This is a dummy markdown document opened to force MardownIt initialization. This allows ${extensionNamePretty} to capture the MarkdownIt instance.`,
          language: 'markdown',
        })
        .then(async (doc) => {
          await vscode.window.showTextDocument(doc, {
            preview: false,
            viewColumn: vscode.ViewColumn.One,
          });
          await vscode.commands.executeCommand(
            'workbench.action.revertAndCloseActiveEditor'
          );
        });

      await new Promise<void>((resolve) => {
        mdCaptureCallback = resolve;
        setTimeout(resolve, 3000);
      });

      if (md == null) {
        await vscode.window.showErrorMessage(
          'MarkdownIt instance capture failed'
        );
        return;
      }
      await vscode.window.showInformationMessage(
        'MarkdownIt instance captured'
      );

      return;
    default:
      return;
  }
}

export function activate(context: vscode.ExtensionContext) {
	// init commands...

	return {
		extendMarkdownIt(markdownIt: any) {
			md = markdownIt;
			if (mdCaptureCallback) {
				mdCaptureCallback();
			}
			return markdownIt;
		},
	};
}

However, a better solution might be to use command markdown.api.render like mentioned here:

https://github.com/microsoft/vscode/issues/80338
https://github.com/microsoft/vscode/issues/75612

I'll look into it after the next update for marker icons is out, probably within the next two weeks.

Tried the command, this seems to work just fine:
const result = await vscode.commands.executeCommand<string>(
  'markdown.api.render',
  '# Test render'
);

Note: if tokens are needed (md.parse instead of md.render), command will not help.


Deployment

Deployment
User story
As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information.
Acceptance Criter
GIVEN a Prework Study Guide website,
WHEN I visit the website using the URL,
THEN I can access my website from any browser

Deployed url link https://amethystlyre.github.io/prework-study-guide/


Updated example

Updated one of the service unavailable examples to include the word 'to'.

You can preview this change here:
Built with commit 5d03df059baa97967971b3829d0a098797a67003
https://deploy-preview-568--govuk-design-system-preview.netlify.com


FVTT V9 - Canvas fails to load

Hello, and thank you for your hard work on this module.
I'm in the process of migrating to v9, and I run quite a few modules. I've found that the canvas never loads. I get errors from other modules, like the following:
monks-active-tiles.js:2810 Uncaught TypeError: Cannot read properties of null (reading 'tiles')
[Detected 1 package: monks-active-tiles]
    at HTMLBodyElement.<anonymous> (monks-active-tiles.js:2810)

But if I disable the module throwing an error, a new error from a new module appears. Deactivating share-media is the only way to get back up and running again.
Another example once Active Tiles are turned off:
Uncaught TypeError: Cannot read properties of undefined (reading 'textures')
[Detected 1 package: perfect-vision]
    at MonoFilter.apply (mono.js:143)
    at e.pop (core.min.js:8)
    at e.renderAdvanced (display.min.js:8)
    at e.render (display.min.js:8)
    at e.render (display.min.js:8)
    at e.render (display.min.js:8)
    at r.render (core.min.js:8)
    at t.render (app.min.js:8)
    at t.emit (ticker.min.js:8)
    at e.update (ticker.min.js:8)
    at _tick (ticker.min.js:8)

I run too many modules to try every combination, so I can't be sure exactly what's going on. What else can I share to help with this bug?

@AurelTristen Thx for the report!
It should be fixed. Give it an update and report back if you encounter others issues.


Wathout module stand-by

Hi,
in Watchout moule the stand-by command work only with CUT, normaly the transition beetwin stand-by e mormal use is DISSOLVE transition ( 1 second ).
Is possible to have the task list command?
with the command "getAuxTimelines 2"  followed by the command $0d  ( carriage return )
Thanks
Paolo

Solved in 2f1517e6


Android crash using Ionic image picker plugin

App crashes when trying to select an image using the image picker plugin. Theres no popup for permission to access the camera so the app crashes automatically. In ios my app is on the app store and theres no problem, the plugin works fine but on android the app crashes. Please help me solve this problem.

@riaz61 one solution would be to handle permissions on your own using a plugin like https://github.com/dpa99c/cordova-diagnostic-plugin.
This is of course until the issue is resolved.

@riaz61 try this out: https://github.com/mirulumam/cordova-imagePicker Forked from @wymsee's imagepicker plugin
tested on Android N 7.1

I forked the original plugin. Use this: https://github.com/abelabbesnabi/cordova-plugin-image-picker
It fixes the problem.

This worked thanks. If you want to test this out before changing or attempting anything, go to your app info or settings on your android device. Then you can enable the permission, it should be there. If its not, the app never tried to use that permission.

excellent i have used https://github.com/Findiglay/cordova-imagePicker and it solved the issue even if i deny the permission request for selecting from library and use camera to capture image

@abelabbesnabi it worked for me. Thanks man.

On Thu, Mar 29, 2018 at 6:24 AM, Yash Vekaria<EMAIL_ADDRESS>wrote:

@abelabbesnabi https://github.com/abelabbesnabi it worked for me.
Thanks man.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/wymsee/cordova-imagePicker/issues/212#issuecomment-377233749,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFlx8tVZXvbLMcCJTbHsBbjnQf8SVKcEks5tjOCBgaJpZM4L6fkF
.

@abelabbesnabi in the ionic new version it's not working

@abelabbesnabi Good solution, but it's not returning base64 code, even with outputType=1 option.

@abelabbesnabi Can you provide a solution working with base64, please?

I'm getting a 404 for 'https://github.com/Findiglay/cordova-imagePicker' when trying to run ionic state reset --plugins seems the repo has been deleted?

I found the other solution;
Ionic:
ionic (Ionic CLI)  : 4.3.1
Ionic Framework    : ionic-angular 3.9.2
@ionic/app-scripts : 3.2.0
1.cordova plugin add cordova-android-support-gradle-release
2.rm -rf platforms/android
3.ionic cordova platform add android
4.ionic cordova build android
Test OK on android  6.0.1 and 8.0.0

@kuangren1984 it worked! Thank you so much!

@kuangren1984 This works perfectly fine :+1: Thanks a lot :)

@thevirajshelke1984 can you please provide the code..

cordova plugin add cordova-android-support-gradle-release
ioinc cordova platform rm android
ionic cordova platform add android
ionic cordova build android

Just follow this steps given by @kuangren1984 :-) They work fine. The app crashes due to different versions of a package needed by some other package in your project. cordova-android-support-gradle-release this package helps us solve the issue.
If you need more insights @faris-dude lemme know :)

Thanks chaps that sorted me out, was pulling my hair out with this one!

@kuangren1984  thanks a lot dude

@kuangren1984 Thanks a lot :)

@kuangren1984  : our saviour !
<EMAIL_ADDRESS>