New version "^3.0" for "psr/cache"

Is your feature request related to a problem? Please describe.
My project is using Symfony which requires "symfony/cache-contracts v3.0.0", which requires "psr/cache ^3.0",
but "google/apiclient" requires "google/auth", which requires "psr/cache ^1.0|^2.0"
So, when I run "composer require google/apiclient", it failed:
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - google/apiclient[v2.12.0, ..., v2.12.1] require google/auth ^1.10 -> satisfiable by google/auth[v1.10.0, ..., v1.18.0].
    - google/auth[v1.16.0, ..., v1.18.0] require psr/cache ^1.0|^2.0 -> satisfiable by psr/cache[1.0.0, 1.0.1, 2.0.0].
    - google/auth[v1.10.0, ..., v1.15.2] require psr/cache ^1.0 -> satisfiable by psr/cache[1.0.0, 1.0.1].
    - You can only install one version of a package, so only one of these can be installed: psr/cache[1.0.0, 1.0.1, 2.0.0, 3.0.0].
    - symfony/cache-contracts v3.0.0 requires psr/cache ^3.0 -> satisfiable by psr/cache[3.0.0].
    - symfony/cache v6.0.2 requires symfony/cache-contracts ^1.1.7|^2|^3 -> satisfiable by symfony/cache-contracts[v3.0.0].
    - doctrine/doctrine-bundle 2.5.4 requires symfony/cache ^4.3.3|^5.0|^6.0 -> satisfiable by symfony/cache[v6.0.2].
    - doctrine/doctrine-bundle is locked to version 2.5.4 and an update of this package was not requested.
    - Root composer.json requires google/apiclient ^2.12 -> satisfiable by google/apiclient[v2.12.0, v2.12.1].

You can also try re-running composer require with an explicit version constraint, e.g. "composer require google/apiclient:*" to figure out if any version is installable, or "composer require google/apiclient:^2.1" if you know which you need.

Describe the solution you'd like
Maybe could you please update google/auth so it's compatible with psr/cache v3.0?
Describe alternatives you've considered
Currently, I have to use google/apiclient v1.1.9
Thanks!

Upvote

Upvote. In the meantime, unless v3 of symfony/cache-contracts is strictly required, you can downgrade both  symfony/cache-contracts and psr/cache to ^2. (symfony/cache v6.0.2 is compatible with symfony/cache-contracts v2)

Support for PSR cache 3.0 has been added in google/auth v1.12.0, and is immediately compatible by this library.


Remove all animations

Can we remove all animations, positioning, showing, ....?

At that pint wouldn't you jsut use a <div/>? ;)

Can you give me an example, because I do not understand what styled div has to do with animations on show, reposition,...?

Take a look at the show.effect, hide.effect and position.effect


Avoid reserved names in C++ code: "__Consuming"

Double-underscored names are reserved for the C++ "implementation" (language and standard library). Even though __Consuming isn't likely to be part of the C++ standard any time soon, we should follow the rules.
Note that the API digester will continue to use the string "__Consuming" for now, even though the underscores aren't really significant, to avoid invalidating existing dumps.
No functionality change.

@swift-ci Please smoke test


Switchover does not happen when killing the master pod

Describe the bug
A clear and concise description of what the bug is.
Environments

Version: moco:0.10.9
OS: Ubuntu 20.04.3 LTS

To Reproduce
Steps to reproduce the behavior:

Kill the master pod
Master role does not switch to an available replica, instead waits for the killed master pod to be up and available again

Expected behavior
Operator should switch the master role to a replica pod
Additional context
Switchover works fine when the master pod is deleted instead of killed

@slavonicsniper
Could you give us how to reproduce the problem using kubectl?

@slavonicsniper
Thank you for the report!
I found that the failover does not work in the following two cases. And I will fix the 1st case.
1. When immediately after a failover or a switchover.
When a failover occurs, the moco-controller selects the most advanced replica based on the replica's Retrieved_Gtid_Set.
However, immediately after a failover or a switchover occurs, the Retrieved_Gtid_Set is blank.
Therefore, if the subsequent failover occurs in this case, the moco-controller can not select a replica to promote.
And the failover will fail.
2. When MySQLCluster is empty.
In this case, the moco-controller judges the cluster status as Lost.
This decision is unavoidable due to the clustering specifications.
https://github.com/cybozu-go/moco/blob/v0.10.9/docs/clustering.md#mysqlcluster

@slavonicsniper Could you give us how to reproduce the problem using kubectl?

In k9s killing the master pod (ctrl+k).

We have fixed the first case in https://github.com/cybozu-go/moco/issues/370#issuecomment-1055089091


[vscode-graphql-syntax] Ruby GRAPHQL heredoc breaks syntax higlighting in the file

Current Behavior
A few weeks ago, the vscode-graphql-syntax package added Ruby support (#3490), but I think something is not quite right.
This is what the example file packages/vscode-graphql-syntax/tests/__fixtures__/test.rb looks like in my VS Code, running the latest extension v1.3.1:

As you can see, while the GraphQL is highlighted, it breaks the highlighting of following Ruby code.
Looking at the tests, I noticed how the snapshots for Ruby and e.g. Python are very different.
Ruby (actual GraphQL lines don't have an annotation on the right):
https://github.com/graphql/graphiql/blob/25c3bfd8c4e5e74625b756cbbba54fc3add42533/packages/vscode-graphql-syntax/tests/__snapshots__/ruby-grammar.spec.ts.snap#L7-L13
Python (actual GraphQL lines are annotated):
https://github.com/graphql/graphiql/blob/25c3bfd8c4e5e74625b756cbbba54fc3add42533/packages/vscode-graphql-syntax/tests/__snapshots__/python-grammar.spec.ts.snap#L9-L14
It looks like the Ruby grammar recognizes the start of the Heredocs also as the end of the Heredoc, maybe confusing itself in the process? I don't understand a lot about the grammars, and fiddling around with the Regexes I wasn't able to produce a better result.
Expected Behavior
I'd expect the closing GRAPHQL at the end of the Heredoc to end the code block and reactivate the Ruby syntax highlighting.

I was able to fix this locally by removing the ruby syntax addition entirely (edit package.json and remove the grammar file). The grammar from the "Ruby LSP" extension hands things off to the graphql syntax highlighter correctly, and matches for both the GRAPHQL and GQL heredoc identifiers. Alternatively, just switching to GQL identifiers might do the trick, as "Ruby LSP" will still hand things off this extension without triggering its problematic grammar—which is only triggered by GRAPHQL.

GQL doesn't seem to highlight correctly either

if someone wants to fix it, it is just a textmate grammar, so it's a set of regular expressions. should i just remove it for now? is no highlighting better than the current bugs?

As @krishantaylor said, it’d still get highlighted because Ruby LSP hands it off correctly. (At least for me, you probably need to have the Ruby LSP extension.) It would definitely be better than breaking following Ruby code for the rest of the file.

I'd rather see it removed. Ruby LSP is the current recommended extension for ruby anyway.

removal it is!

here is the proposal to remove ruby and ruby markdown block support!
https://github.com/graphql/graphiql/pull/3592

Thank you for fixing this! I didn't think to close this issue, but it has been working great for me since v1.3.6 was released. Thank you! 🧙♂


Support for Special Elements with complex geometry

Some elements with complex geometry will be difficult to achieve with "pure" CSS, yet are really iconic in the LCARS/okudagram style. For instance, the classic circular X/Y control found on many consoles including the helm.
I have found that although less well widely known, the SVG support in browsers is really pretty good these days. This may be a nice way to meet this need, and it can be done in a very modular/optional way.

Totally right. SVG is the path to go here. The only thing is tht people
want to have nice event options so one can link it it to whateverJS.
I guess it would be nice to have some iconic demo SVGs included, together
with interactive demo.
Am Mo., 18. Nov. 2019 um 23:09 Uhr schrieb Justin Warwick <
<EMAIL_ADDRESS>
Some elements with complex geometry will be difficult to achieve with
"pure" CSS, yet are really iconic in the LCARS/okudagram style. For
instance, the classic circular X/Y control found on many consoles including
the helm.
I have found that although less well widely known, the SVG support in
browsers is really pretty good these days. This may be a nice way to meet
this need, and it can be done in a very modular/optional way.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/joernweissenborn/lcars/issues/26?email_source=notifications&email_token=AARG7QILENGY6I4ZMUAEHADQUMHAFA5CNFSM4JO22A32YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H2FQBVQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARG7QOKVFIYUHSF3IAMGJDQUMHAFANCNFSM4JO22A3Q
.


bootstrap 0.11?

I forked a copy of this code base for bootstrap 0.11. Seems to work fine. Would you mind lowering the requirement?

Done


uPickle hangs compiler when no Writer for nested type

You can see a repro at http://scastie.org/20858
import upickle.default._
import java.util.Date

case class Client(first: Option[String],
                  last: Option[String],
                  home: Option[String],
                  cell: Option[String],
                  email: Option[String],
                  address: Option[String],
                  area: Option[String],
                  city: Option[String],
                  state: Option[String],
                  zip: Option[String],
                  created: Option[Date],
                  modified: Option[Date])

implicitly[Writer[Client]]

Providing a Writer[Date] fixes it.

As an example, this causes ammonite-repl to hang when you try to evaluate certain expressions, with Java sitting at max CPU indefinitely.

Bug bankruptcy


[Feature Request]Will gpt-crawler support puppeteer ?

Hi there,
I try to setup this project on Fedora 38, and it failed because of  playwright only support ubuntu and debian.
https://github.com/microsoft/playwright/issues/27890
It will be great if gpt-crawler can  also support  puppeteer, so it can run on more os distribution.

@yujinqiu Crawler is crawlee, it also support for puppeteer, please see it: https://crawlee.dev/api/puppeteer-crawler
You should fork to your repo and update it
If have time, please goto my GPT store with 15k GPTs: https://gptcombo.com/

@yujinqiu I also tried to set it up, and this is a workaround solution.
instead of installing the package using this command npx playwright install, try the following command:
sudo dnf install atk at-spi2-atk cups-libs libdrm at-spi2-core libX11 libXcomposite libXdamage libXext libXfixes libXrandr libgbm libxcb libxkbcommon pango cairo alsa-lib

I use the 1.42.1 for the playwright and fedora server as well, after executing the above command, the library works fine now. I hope it helps.


add support for the updateSecretDesc restful API

this restful API will be exposed to public as:
POST <ehsm_srv_address>/ehsm?Action=UpdateSecretDesc
which is used to update the description of secret.
test: passed the unittest
Signed-off-by: yidingluo1<EMAIL_ADDRESS>

seems updating the description will not impact versionId, right?   All versions share the same description.

yes

seems updating the description will not impact versionId, right? All versions share the same description.

yes


How do I create a CMakeList.txt file for installing BerkelyDB code on windows platform?

CMakeLists_db.txt
When asking a question please also include where you looked for an answer (so we can update the documentation if needed).
Hi All,
Currently I'm trying to integrate the Berkley DB code with our source by migrating from sqlite. We are making use of CMake for our Build and we make use of CMakeList.txt for this. I know that for installing the Linux we make use of the below command:
cd build_unix/
../dist/configure --enable-sql-compat --disable-shared --with-pic --prefix=$INST_DIR
make install
But I'm stuck with windows . I'm attaching the CMakeList.txt file which I have created. Please provide some headsup on how to proceed with this.

Any heads-up?

Maybe you should ask this question on Slack.

Ok


Change Request: More prescriptive telemetry client library name guidance for General Guidelines

The Basics

Which design guideline is affected?
Client Library Usage Telemetry and in particular the line

<client_lib> ::= client library name (all lowercase), e.g. "blobstorage", "keyvault"

Which target languages are affected?
All languages

Describe the change:
We should be more prescriptive with our client library name guidance so our user agent strings are consistent across languages.

Reasoning
We've had n developers write the client library name for blobs in n different ways.  We should add additional guidance so everyone ends up with the same client_lib and user agent format.
Some possible options to help drive discussion:

The name in the Portal (Storage account > Blobs)
The name in the official documentation, dropping Azure if present (Blob Storage via conceptual docs or Blob Service via REST API)
The name on the marketing page (Blob Storage)
The name of the package (varies by language)
The name of the folder in the repo (tied to the package, which varies by language)
A fixed list of names in the guidelines, like our .NET namespace groups

Please also see #356 for a related discussion about consistent naming across our repos.

Discussed over two board meetings and agree this is a requirement for all languages.  The general guidelines have been updated in PR #412 to accomodate these changes.


I can't retrieve data updates

I am using your codebase but I don't understand why this doesn't work for me, even in consol log the new data not appears.
And can you please explain the settings.CHANNEL_FEED_HOST in trigger.py stand for?
I've been explore this but I can't found any explanation for this.
Thank you in advance.
Django 2.2.7
Channels 2.4.0

I'm done, it was my fault.
But hey, thank you!


Possible way to apply gradients using tf.identity()?

Environment info
Operating System: Ubuntu 14.04
Installed version of CUDA and cuDNN: 7.5 and R4
If installed from binary pip package, provide:

Which pip package you installed.
The output from python -c "import tensorflow; print(tensorflow.version)".

If installed from sources, provide the commit hash: 79174afa30046ecdc437b531812f2cb41a32695e
Steps to reproduce
import tensorflow as tf

a = tf.constant(1.)
b = tf.Variable(2.)
c = a * b
grad_symbolic = tf.gradients(c, tf.trainable_variables())
grad_vars = [tf.Variable(tf.zeros_like(_)) for _ in tf.trainable_variables()]
grad_zero_ops = [_.assign(tf.zeros_like(_)) for _ in grad_vars]
grad_accum_ops = [grad_vars[i].assign_add(grad_symbolic[i])
                  for i in xrange(len(grad_vars))]
opt = tf.train.GradientDescentOptimizer(1.)
train_op = opt.apply_gradients(zip(
    [tf.identity(_) for _ in grad_vars], tf.trainable_variables()))
sess = tf.Session()
sess.run(tf.initialize_all_variables()) # This will cause error.
# This will run successfully.
# for _ in tf.all_variables():
#     sess.run(tf.initialize_variables([_]))

What have you tried?

workaround
But in my real project code, the program stucks into the variable initialization for too many minutes if I initialize variables one by one.

Logs or other output that would be helpful
(If logs are large, please upload as attachment).
Traceback (most recent call last):
  File "test_identity_gradient_apply.py", line 26, in <module>
    sess.run(tf.initialize_all_variables()) # This will cause error.
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 333, in run
    run_metadata_ptr)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 573, in _run
    feed_dict_string, options, run_metadata)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 648, in _do_run
    target_list, options, run_metadata)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 668, in _do_call
    raise type(e)(node_def, op, message)
tensorflow.python.framework.errors.FailedPreconditionError: Attempting to use uninitialized value Variable
	 [[Node: Variable/read = Identity[T=DT_FLOAT, _class=["loc:@Variable"], _device="/job:localhost/replica:0/task:0/cpu:0"](Variable)]]
Caused by op u'Variable/read', defined at:
  File "test_identity_gradient_apply.py", line 15, in <module>
    b = tf.Variable(2.)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/variables.py", line 211, in __init__
    dtype=dtype)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/variables.py", line 319, in _init_from_args
    self._snapshot = array_ops.identity(self._variable, name="read")
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/gen_array_ops.py", line 788, in identity
    result = _op_def_lib.apply_op("Identity", input=input, name=name)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/op_def_library.py", line 704, in apply_op
    op_def=op_def)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/ops.py", line 2249, in create_op
    original_op=self._default_original_op, op_def=op_def)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/ops.py", line 1224, in __init__
    self._traceback = _extract_stack()

The problem is in this line:
grad_vars = [tf.Variable(tf.zeros_like(_)) for _ in tf.trainable_variables()]

If you initialize a variable from (something derived from) another variable, you need to use the Variable.initialized_value() method to tell TensorFlow about the ordering dependency when running the initializers. So your line should look like:
grad_vars = [tf.Variable(tf.zeros_like(v.initialized_value())) for v in tf.trainable_variables()]

Note though that your grad_vars don't really depend on the value of the trainable variables, and the trainable variables all have static shapes, so you could alternatively solve this with the following:
grad_vars = [tf.Variable(tf.zeros(v.get_shape())) for v in tf.trainable_variables()]


feat: stylize_markdown and borders for documentation

The markdown rendered in the documentation floating window is not correct.
This PR implements the documentation floating window using the new vim.lsp.util.open_floating_preview method that has special handling for markdown content. It uses a mix of conceal and custom syntax regions to properly format any markdown, including code block fences.
This brings the rendering in line with Neovim's internal rendering for hover and signature_help.
Additionally, support for borders has been added.
Fixes #373
Fixes #404
Fixes #59
Fixes #270
Fixes #274 (maxwidth is available space for the float)
The new code is much more compact since it can use existing Neovim functionality.
I only removed the file documentation.vim for now, but I guess all the vital vim code related to markdown and floating windows can also be removed, but since I don't fully know the whole code-base I'll leave this to someone else.
Old Style (incorrect)

New Style

With borders enabled:

Thank you for your contribution! I will look into it.

I'm looking into it.

It doesn't work on except the nvim head.
It causes flicker if set prelesect = 'always'

My FloatingWindow module can't render markdown correctly but it re-use existing floating-windo (it will help reducing flicker)

@hrsh7th just pushed a new version.
The floating window code now resides in float.lua.
The floating window is now reused to prevent flickering.

Float.show can also have options, and I added support for borders around the documentation window.
If you're interested in this, I can make a compe option availble that calls Float.show with the configured border

I went ahead and added config for borders too :)
to use borders, you can do somethng like:
require("compe").setup({
  border = "single",
})

require("compe").setup({
  border = "shadow",
})

require("compe").setup({
    border = { "╭", "─", "╮", "│", "╯", "─", "╰", "│" },
})

The flicker has gone. Thank you for quick fix.

I forgot to add in the scrolling of the documentation window. Doing that now.

@hrsh7th scrolling is now also fixed.

It is almost good. We should do some fixes.

config.border should be config.documentation.border.
we needs config.documentation.winhighlight too.
The position calculation should be improved (the current implementation does not care about less space of right area.

How would you like 3 to work?
Shall I add a config.documentation.max_width and config.documentation.min_width?
If less than min_width, we hide the popup.

Shall I add a config.documentation.max_width and config.documentation.min_width?
LGTM!

How would you like 3 to work?
The current implementation checks left-side space if the right-side space does not enough then it locates the documentation window to the left side (if it is possible).

ok, gotcha, will make the changes!

@hrsh7th all changes have been added. These are the documentation defaults:
 {
    border = "none",
    winhighlight = "CompeDocumentation",
    max_width = 120,
    min_width = 40,
    max_height = math.floor(vim.o.lines * 0.3),
    min_height = 1,
  }

config.documentation can be true, 1 or a partial table. The config is then merged with the defaults.

I've tested it and few fixes applied in my local machine.
diff --git a/lua/compe/config.lua b/lua/compe/config.lua
index 0bc131a..54af820 100644
--- a/lua/compe/config.lua
+++ b/lua/compe/config.lua
@@ -73,8 +73,8 @@ Config._normalize = function(config)
   config.autocomplete = Boolean.get(config.autocomplete, true)

   local documentation_defaults = {
-    border = "none",
-    winhighlight = "CompeDocumentation",
+    border = { '', '' ,'', ' ', '', '', '', ' ' },
+    winhighlight = "NormalFloat:CompeDocumentation,FloatBorder:CompeDocumentationBorder",
     max_width = 120,
     min_width = 40,
     max_height = math.floor(vim.o.lines * 0.3),
diff --git a/lua/compe/float.lua b/lua/compe/float.lua
index c9197b4..d87786d 100644
--- a/lua/compe/float.lua
+++ b/lua/compe/float.lua
@@ -54,11 +54,7 @@ function M.get_options(contents, opts)
       height = config.documentation.min_height
     end

-    local col = right and right_col or (pum.col - width - 1)
-    if not right and opts.border and opts.border ~= "none" then
-      col = col - 1
-    end
-
+    local col = right and right_col - 1 or (pum.col - width - 1)
     return {
       relative = "editor",
       style = "minimal",
@@ -110,8 +106,12 @@ function M.show(contents, opts)
   end

   local buf = vim.api.nvim_create_buf(false, true)
+  vim.api.nvim_buf_set_option(buf, "buftype", "nofile")
+  vim.api.nvim_buf_set_option(buf, "bufhidden", "wipe")

   -- applies the syntax and sets the lines to the buffer
+  opts.width = float_options.width
+  opts.height = float_options.height
   contents = vim.lsp.util.stylize_markdown(buf, contents, opts)

   -- reuse existing window, or create a new one
@@ -125,7 +125,7 @@ function M.show(contents, opts)
   -- conceal
   vim.api.nvim_win_set_option(M.win, "conceallevel", 2)
   vim.api.nvim_win_set_option(M.win, "concealcursor", "n")
-  vim.api.nvim_win_set_option(M.win, "winhighlight", "NormalFloat:" .. config.documentation.winhighlight)
+  vim.api.nvim_win_set_option(M.win, "winhighlight", config.documentation.winhighlight)

   -- disable folding
   vim.api.nvim_win_set_option(M.win, "foldenable", false)
@@ -134,9 +134,6 @@ function M.show(contents, opts)
   vim.api.nvim_win_set_option(M.win, "wrap", true)
   vim.api.nvim_win_set_option(M.win, "scrolloff", 0)

-  vim.api.nvim_buf_set_option(buf, "modifiable", false)
-  vim.api.nvim_buf_set_option(buf, "bufhidden", "wipe")
-
   return buf, M.win
 end

diff --git a/plugin/compe.vim b/plugin/compe.vim
index cb4a3a7..f3e8b60 100644
--- a/plugin/compe.vim
+++ b/plugin/compe.vim
@@ -41,7 +41,11 @@ function! s:on_text_changed() abort
 endfunction

 if !hlexists('CompeDocumentation')
-  highlight def link CompeDocumentation NormalFloat
+  highlight link CompeDocumentation NormalFloat
+endif
+
+if !hlexists('CompeDocumentationBorder')
+  highlight link CompeDocumentationBorder CompeDocumentation
 endif

 "

What do you think about it?

Looks good to me!
The buftype=nofile, is not needed, since we create a scratch buffer. (see :h nvim_create_buf  and :h scratch-buffer)

I'm trying to use as daily driver

@hrsh7th sounds good. Doing the same here. Haven't seen any issues yet so far :)

vital-vs (current)
denols

vscode-css-language-server

intelephense

neovim built-in (new)
denols: const obj = { should be highlighted.

vscode-css-language-server: html entities should be concealed.

intelephense: var\dump_ should be var_dump.

neovim built-in markdown seems to not care about g:markdown_fenced_languages.
I don't know how to tell ts=typescript to neovim.
neovim built-in markdown seems to not support concealing HTML entities
It can be checked by vscode-langservers-extracted (vscode-css-language-server).
my implementation is the following.
    syntax match vital_vs_vim_syntax_markdown_entities_lt /</ containedin=ALL conceal cchar=<
    syntax match vital_vs_vim_syntax_markdown_entities_gt />/ containedin=ALL conceal cchar=>
    syntax match vital_vs_vim_syntax_markdown_entities_amp /&/ containedin=ALL conceal cchar=&
    syntax match vital_vs_vim_syntax_markdown_entities_quot /"/ containedin=ALL conceal cchar="
    syntax match vital_vs_vim_syntax_markdown_entities_nbsp / / containedin=ALL conceal cchar=

neovim built-in markdown seems to not support complex escape characters handling.
Hmm.. but neovim's implementation looks correct... I can't understand what is wrong.

But I think we should use neovim's built-in markdown renderer on nvim-compe.

About ts: that's a known issue. I have two PRs open to fix this upstream. But I'll see if I can get a smaller PR that just uses g:markdown_fenced_languages in earlier. (that's the issue for denols right?)
We actually render markdown upstream using a syntax file called lsp_markdown. Would be good to get those conceal rules about entities in there. I can make a PR for that.
I'm not sure what's happening with the intelliphense one. I can check. That's what you mean with the complex handling?
Also, your English is just fine, no worries. I'm also not a native English speaker ;)

Update: just updated one of my PRs to only use markdown_fenced_languages

I can't reproduce the issue you see with css. This is what I get:

It looks like the __foo\\_bar__ escaping is not supported by the runtime markdown syntax file.

My implementation is the following.
https://github.com/hrsh7th/vim-vital-vs/blob/master/autoload/vital/__vital__/VS/Vim/Syntax/Markdown.vim#L11
I tried to improve neovim's built-in lsp_mardown.vim.
It's a bit hacky but anyway it works.
" Add this codes.
syn clear markdownEscape
syntax region markdownEscape matchgroup=markdownEscape start=/\\\ze[\\\x60*{}\[\]()#+\-,.!_>~|"$%&'\/:;<=?@^ ]/ end=/./ containedin=ALL keepend oneline concealends

" Following original code should be commented.
" syntax region mkdEscape matchgroup=mkdEscape start=/\\\ze[\\\x60*{}\[\]()#+\-,.!_>~|"$%&'\/:;<=?@^ ]/ end=/.\zs/ keepend contains=mkdEscapeCh oneline concealends
" syntax match mkdEscapeCh /./ contained

It will solve html entiries problem.
syntax match mkdNbsp / / conceal cchar=
syntax match mkdLt /</  conceal cchar=<
syntax match mkdGt />/  conceal cchar=>
syntax match mkdAmp /&/  conceal cchar=&
syntax match mkdQuot /"/  conceal cchar="

@hrsh7th i don't see those html entries as you can see in the screenshot above, so the concealing seems to be correct already. Any idea why you see the entities on your end?

Hm...but lsp_markdown.vim have no html entiries syntax except  ...
Could you provide the echo synIDattr(synID(line("."), col("."), 1), "name") results?

My output also seems different. Maybe we're using a different LSP server version for css?

I'm using lsp server is installed by npm i -g vscode-langservers-extracted.

ok, cool. I'll make a PR upstream to fix this

I created a PR with the syntax changes upstream: https://github.com/neovim/neovim/pull/14907

The syntax changes to lsp_markdown have been merged to master in the meantime 🚀

The markdown fences PR is also merged! 🎉

It is still interpreting stars in code as Markdown formatting, breaking the correct display of code documentation:

The breakpoint function documentation should be displayed like this for python:
breakpoint(*args: Any, **kws: Any) -> None

breakpoint(*args, **kws)

Call sys.breakpointhook(*args, **kws).  sys.breakpointhook() must accept
whatever arguments are passed.

By default, this drops you into the pdb debugger.

@baco ok, I'll check. I suspect that the language server is not returning proper markdown code blocks. Will see if I can repro and what the issue is.
You should see the same behavior when doing hover though. So this would be an upstream Neovim issue. Feel free to post an issue there for further followup

As suspected, pyls doesn't return a MarkupContent, but a string instead. I'll make a PR upstream to render these strings as plaintext instead of markdown

@baco I just pushed a fix to this PR where we assume the syntax is the filetype when a string is used as documentation instead of a MarkupContent.
fyi: PyRight does properly return the correct data

I've pulled your changes, much better now!

There is still something weird with the word wrapping/folding, but I assume that is also for how the documentation is fetched and is not part of this Markdown formatting.

fyi: PyRight does properly return the correct data

I guess... but it seemed somehow pointless at the time to drop CoC in favor of Native-LSP to avoid loading Node runtimes I don't use, and fall into PyRight. Hence my decision on going for PyLS which is native Python, the same language I am already programming into. But I'll keep your advice in mind.

For the wrapping, it will use your existing wrapping settings, so you can change those to word wrapping etc.

Could you apply this patch?
diff --git a/lua/compe/config.lua b/lua/compe/config.lua
index 0bc131a..84f0444 100644
--- a/lua/compe/config.lua
+++ b/lua/compe/config.lua
@@ -73,10 +73,10 @@ Config._normalize = function(config)
   config.autocomplete = Boolean.get(config.autocomplete, true)

   local documentation_defaults = {
-    border = "none",
-    winhighlight = "CompeDocumentation",
+    border = { '', '' ,'', ' ', '', '', '', ' ' },
+    winhighlight = "NormalFloat:CompeDocumentation,FloatBorder:CompeDocumentationBorder",
     max_width = 120,
-    min_width = 40,
+    min_width = 60,
     max_height = math.floor(vim.o.lines * 0.3),
     min_height = 1,
   }
diff --git a/lua/compe/float.lua b/lua/compe/float.lua
index c9197b4..e6dd2b6 100644
--- a/lua/compe/float.lua
+++ b/lua/compe/float.lua
@@ -16,17 +16,11 @@ function M.get_options(contents, opts)
   local pum = vim.fn.pum_getpos()
   if pum and not vim.tbl_isempty(pum) then
     -- check space on the right
-    local right_col = pum.col + pum.width + (pum.scrollbar and 1 or 0)
-    if opts.border and opts.border ~= "none" then
-      right_col = right_col + 1
-    end
-    local right_space = vim.o.columns - right_col
+    local right_col = pum.col + pum.width + (pum.scrollbar and 1 or 0) + 1
+    local right_space = vim.o.columns - right_col - 1

     -- check space on the left
     local left_space = pum.col - 1
-    if opts.border and opts.border ~= "none" then
-      left_space = left_space - 1
-    end

     local max_width = config.documentation.max_width
     local max_height = config.documentation.max_height
@@ -54,11 +48,7 @@ function M.get_options(contents, opts)
       height = config.documentation.min_height
     end

-    local col = right and right_col or (pum.col - width - 1)
-    if not right and opts.border and opts.border ~= "none" then
-      col = col - 1
-    end
-
+    local col = right and right_col - 1 or (pum.col - width - 3)
     return {
       relative = "editor",
       style = "minimal",
@@ -96,9 +86,13 @@ function M.show(contents, opts)
   opts.border = config.documentation.border

   contents = contents or {}
-  if type(contents) == "string" then
-    contents = vim.split(contents, "\n", true)
+  if type(contents) == "table" then
+    contents = table.concat(contents, "\n")
   end
+  if contents == '' then
+    return M.close()
+  end
+  contents = vim.split(contents, "\n", true)
   -- Clean up input: trim empty lines from the end, pad
   contents = vim.lsp.util._trim(contents, opts)

@@ -110,8 +104,11 @@ function M.show(contents, opts)
   end

   local buf = vim.api.nvim_create_buf(false, true)
+  vim.api.nvim_buf_set_option(buf, "bufhidden", "wipe")

   -- applies the syntax and sets the lines to the buffer
+  opts.width = float_options.width or opts.width
+  opts.height = float_options.height or opts.height
   contents = vim.lsp.util.stylize_markdown(buf, contents, opts)

   -- reuse existing window, or create a new one
@@ -125,7 +122,7 @@ function M.show(contents, opts)
   -- conceal
   vim.api.nvim_win_set_option(M.win, "conceallevel", 2)
   vim.api.nvim_win_set_option(M.win, "concealcursor", "n")
-  vim.api.nvim_win_set_option(M.win, "winhighlight", "NormalFloat:" .. config.documentation.winhighlight)
+  vim.api.nvim_win_set_option(M.win, "winhighlight", config.documentation.winhighlight)

   -- disable folding
   vim.api.nvim_win_set_option(M.win, "foldenable", false)
@@ -134,9 +131,6 @@ function M.show(contents, opts)
   vim.api.nvim_win_set_option(M.win, "wrap", true)
   vim.api.nvim_win_set_option(M.win, "scrolloff", 0)

-  vim.api.nvim_buf_set_option(buf, "modifiable", false)
-  vim.api.nvim_buf_set_option(buf, "bufhidden", "wipe")
-
   return buf, M.win
 end

diff --git a/plugin/compe.vim b/plugin/compe.vim
index cb4a3a7..f3e8b60 100644
--- a/plugin/compe.vim
+++ b/plugin/compe.vim
@@ -41,7 +41,11 @@ function! s:on_text_changed() abort
 endfunction

 if !hlexists('CompeDocumentation')
-  highlight def link CompeDocumentation NormalFloat
+  highlight link CompeDocumentation NormalFloat
+endif
+
+if !hlexists('CompeDocumentationBorder')
+  highlight link CompeDocumentationBorder CompeDocumentation
 endif

 "

@hrsh7th done!
Would be great if we could have this merged by Friday, in time for Neovim 0.5 :)

@folke Thank you for your contribution. It's great progress!
I will merge after little more testing.

@hrsh7th awesome, thank you!
I'll keep an eye on potential issues with the new doc float, but feel free to @ mention me as well.
Thanks again for this great plugin.

I was so looking forward for this, great job @folke
I just got this error
Error executing vim.schedule lua callback: compe/float.lua:125: E474: Inva
lid argument

Any ideas?
my conifg

edit["hrsh7th/nvim-compe"] = {
  requires = {
    "andersevenrud/compe-tmux",
  },
  config = function()
    require("compe").setup {
      enabled = true,
      autocomplete = true,
      debug = false,
      min_length = 1,
      preselect = "always",
      throttle_time = 120,
      source_timeout = 5,
      incomplete_delay = 200,
      max_abbr_width = 100,
      max_kind_width = 100,
      max_menu_width = 50,
      documentation = {
        border = "none", -- the border option is the same as `|help nvim_open_win|`
        winhighlight = "NormalFloat", -- highlight group used for the documentation window
        max_width = 120,
        min_width = 40,
        max_height = math.floor(vim.o.lines * 0.3),
        min_height = 1,
      },
      source = {
        buffer = true,
        calc = true,
        tmux = true,
        orgmode = true,
        -- conjure = true,
        nvim_lsp = true,
        tabnine = false, -- to much suggestions, I need to lower it's priority.
        nvim_lua = { filetypes = { "lua.luapad" } },
        path = true,
        spell = false,
        treesitter = false,
        vsnip = true,
      },
    }
    require "internal.map" {
      ["i|<space>"] = "v:lua._insert_space()",
      ["i|<CR>"] = "v:lua._compe_confirm()",
      ["i|<C-j>"] = "pumvisible() ? '<C-n>' : '<c-j>'",
      ["i|<C-k>"] = "pumvisible() ? '<C-p>' : '<c-k>'",
      ["i|<C-space>"] = "pumvisible() ? '<C-n>' : '<C-space>'",
    }
  end,
}

@tami5 my fault, I hadn't updated the docs with the correct info.
You should use "NormalFloat:CompeDocumentation,FloatBorder:CompeDocumentationBorder" as winhighlight, or just remove it so it uses the defaults.
@hrsh7th I made a PR #437 to fix the docs

Nice, it work great now, thanks

@folke  preview is looking so great now .Thank.


[BEAM-9529] Remove datastore.v1, googledatastore

Removed googledatastore and proto-google-cloud-datastore-v1 packages.
Removed v1/datastoreio.py and other v1/ sources that aren't also used by
v1new. The rest were migrated into v1new/.
Migrated inherited test cases from v1 into v1new test classes.
Updated datastore_wordcount IT to use v1new. Now also runs on Python 3.
Added some type hints to v1new/types.py for IDE (PyCharm) ease-of-use.
Updated Datastore snippet to use v1new, now works for Py3.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---

---
---

Java

Python

---

---
---

XLang
---
---
---

---
---

Pre-Commit Tests Status (on master branch)

---
Java
Python
Go
Website

Non-portable

Portable
---

---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

run python 3.7 postcommit

R: @chamikaramj

Note to review: there is very little change to connector code. Most of the changes involve tests, example code, and snippets.

LGTM. Thanks.

Run Python2_PVR_Flink PreCommit


Context.tf out of date?

Found a bug? Maybe our Slack Community can help.

Describe the Bug
Seems like the context.tf is out of date compared to others with respect to null-label? The current null-label is pointing to a version that doesn't work with tf 0.14.0
Expected Behavior
I would expect null-label to be updated to the latest version especially since there seems to be an auto-update process.

Closed by #33


Expose fuser scale (GatedSelfAttentionDense scale)

This seems to affect the strength of InstanceDiffusion's attention, I find that higher values, while easily breaking the image, also force lot of movement. This may be useful when using image inputs and other strong conditioning like IPAdapter.

1.0:
https://github.com/logtd/ComfyUI-InstanceDiffusion/assets/40791699/d21daf84-522f-4e49-b28d-b279d23e036c
1.5:
https://github.com/logtd/ComfyUI-InstanceDiffusion/assets/40791699/0cbb3713-5bab-4dcd-8c7b-b8a6fd4c3f41


Offline use

"Nice app for a great website, but doesn't work offline. Was looking for something to use in Japan, where I don't have data and often am not on WiFi since Google Translate sucks."
"I don't really see a reason to use the app. Maybe if it offered offline search or something."
"I would like to see an option to download the dictionary for offline use."

@Reline can I use Realm DB to help out with the Offline use ?

👍  Sure thing, Realm is my ORM of choice so feel free to push up some work on a branch and I can help out.

How were you planning on approaching this, by the way?

Since jisho uses JMDict Tatoeba etc. which have data dumps. I guess using them can come handy. Still working on how to implement search.

Maybe we can keep a separate option for offline support. When the user clicks on it, then we can download the data dumps in background

Yeah, the search is the most difficult to tackle because we would have to imitate the same results as the Jisho API.
I agree, there should be an option to download for offline mode instead of forcibly downloading it all immediately.
I want to integrate an option to save favorites as well #19 so I'll start up the realm integration on a new branch and once that's done we can start writing for these features on separate branches.

yes. Makes sense. Meanwhile I can take up some other issues.

I've taken the liberty of starting to set up models to parse the JMDict XML files and their kanji lookup files. I'll convert the dictionary models into the API models, then just insert them into the realm DB and either place that on my server or serve the app to the store with the DB preinstalled. Search queries should just do word, reading, and glossary lookups.

Taking this into a different direction, I've noticed Realm is hard to manage in other projects so I'll be building a SQLite database outside the Android environment then downloading from a server at runtime. Probably using SQLBrite/SQLDelight for interfacing.

Finally got english definitions and parts of speech showing after #48 was merged, needs some performance improvements however.
Last but not least is proper okurigana support, currently the readings are not aligned with the kanji.


langchain packages compatibility of pydantic

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
need a small help from you regarding the version compatibility of packages on my machine . I am having below version of packages installed and facing below error while trying to execute. Can you help me please resolve this issue. Would really appreciate your help.
packages :
pydantic (2.7.3)
langchain ( 0.2.3)
langchain-community (0.2.4)
langchain-core (0.2.5)
langsmith(0.1.76)
Exception:
File "/opt/python3.12/lib/python3.12/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 600, in run_script
exec(code, module.dict)
File "/home/hayek/ops_assistant/SOP_Validator.py", line 3, in
from langchain.chat_models import AzureChatOpenAI
File "/opt/python3.12/lib/python3.12/site-packages/langchain/chat_models/init.py", line 24, in
from langchain.chat_models.base import init_chat_model
File "/opt/python3.12/lib/python3.12/site-packages/langchain/chat_models/base.py", line 5, in
from langchain_core.language_models.chat_models import (
File "/opt/python3.12/lib/python3.12/site-packages/langchain_core/language_models/init.py", line 25, in
from langchain_core.language_models.base import (
File "/opt/python3.12/lib/python3.12/site-packages/langchain_core/language_models/base.py", line 75, in
class BaseLanguageModel(
File "/opt/python3.12/lib/python3.12/site-packages/pydantic/v1/main.py", line 286, in new
cls.try_update_forward_refs()
File "/opt/python3.12/lib/python3.12/site-packages/pydantic/v1/main.py", line 807, in try_update_forward_refs
update_model_forward_refs(cls, cls.fields.values(), cls.config.json_encoders, localns, (NameError,))
File "/opt/python3.12/lib/python3.12/site-packages/pydantic/v1/typing.py", line 554, in update_model_forward_refs
update_field_forward_refs(f, globalns=globalns, localns=localns)
File "/opt/python3.12/lib/python3.12/site-packages/pydantic/v1/typing.py", line 520, in update_field_forward_refs
field.type = evaluate_forwardref(field.type_, globalns, localns or None)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/python3.12/lib/python3.12/site-packages/pydantic/v1/typing.py", line 66, in evaluate_forwardref
return cast(Any, type_)._evaluate(globalns, localns, set())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Example Code
No response
Python, Pydantic & OS Version
[hayek@illin3691 ~]$ python3 -c "import pydantic.version; print(pydantic.version.version_info())"
             pydantic version: 2.7.3
        pydantic-core version: 2.18.4
          pydantic-core build: profile=release pgo=true
                 install path: /opt/python3.12/lib/python3.12/site-packages/pydantic
               python version: 3.12.4 (main, Jun  8 2024, 01:32:03) [GCC 8.5.0 20210514 (Red Hat 8.5.0-16)]
                     platform: Linux-4.18.0-425.3.1.el8.x86_64-x86_64-with-glibc2.28
             related packages: typing_extensions-4.12.2
                       commit: unknown

You haven't actually include the error here, but looking at the path, this is probably a duplicate of #9607 and #9607


Make tests automated

For now, I guess we have to run each of them manually? We should either copy the docker setup from OpenAI Gym or the nose setup from Pylearn2.

Work in progress: see #80


getReferencesAtLocation: fix handling of destructoring imports

Fixes #45423.

GitHub is refusing to show tests/cases/fourslash/findAllReferencesJsRequireDestructuring.ts - can you post it as text (it's allegedly 13 lines)?

@RyanCavanaugh, there was no change to findAllReferencesJsRequireDestructuring.ts -- I worked on it on the way to the real test and my Emacs adds the required-by-convention newline at the end of the file (so it was a whitespace change which GH doesn't handle well).  I reverted that line so it's gone from the pr now.

ping @armanio123 @andrewbranch


'urandom' module always produces the same sequences

This is Specific to the Pimoroni Version of RPi Micropython Firmware
I have three RPI Picos and they always produce the same sequence of numbers when I call random.random() with the Pimoroni version of firmware (v0.0.5):
>>> import random
>>> random.random()
0.7111824

>>> random.random()
0.4089468

>>> random.random()
0.09752237

>>> random.random()
0.8465231

The same happens with any of the other 'random' functions, they always produce a replicable sequence.
The standard RPi Micropython port firmware (1.14) from the Official Website does not present this issue, if I install that on all three devices every I always get different numbers.

What you see is typical for a pseudorandom generator.
I think you simply have to seed it yourself with some random value.
Typically with an noisy ADC converter value or with time evolved since start or last keypress or something, that will be not the same each time.

I've rebased our MicroPython fork on upstream so the next release should - hopefully - fix this.

See: https://github.com/pimoroni/pimoroni-pico/releases/tag/v0.0.6


Dataset Failed

Hello, could you please help me with that issue? I don't understand what's wrong. Thanks a lot.

I noticed a couple of closed issues for this. Is it still a problem?

Yes, unfortunately, it is. I thought I would postpone it and try to solve it later. But I would be very grateful for the help.
I'm probably using your tool wrong. Can mass spectrometry data be used as input data? If so, can you guide me on how to transform the input data? Thanks.

I don't think mass spectrometry data would work. It is designed to perform and visualize the results of metabolic task analysis of gene expression data. E.g. the first column of the input data should be an Entrez gene id.


IWW Issue #41, March 9th 🙀 2021

This pull request is for gathering links for the March 9th issue of the Immersive Web Weekly newsletter for the W3C Immersive Web Community Group.
If you have a link to a news article, event, artwork, or project that is directly related to the immersive web then we welcome your help!
To submit a link comment below using this template:
title: Example title of link
url: https://example.com/
author: Alice Smith
content: A short description of what is at the link and why it's related to the immersive web

Please keep in mind that comments here and all submitted links are public!
We keep each issue pretty short so we won't immediately use every submission but we keep track of them all and they may appear in a later issue.
Deadline
IWW goes out each Tuesday morning around 10am Pacific time.
Trevor will edit each issue on the Monday before publication so submissions after that will roll over for use in future issues.
If you need editorial support then email @TrevorFSmith<EMAIL_ADDRESS>

title: OGC GeoPose Draft Is Public
url: https://github.com/opengeospatial/GeoPose/


In My Experience Microsoft Edge Refuses to Install on Windows Server 2019

In My Experience Microsoft Edge Refuses to Install on Windows Server 2019.  I've tried twice.  The standard Microsoft muddle of web pages allowed me to download Microsoft Edge which eventually complained that the PC was running an OS older than Windows 7.   The plan at Microsoft was to eliminate the familiar end user interface part of Windows Server entirely for security reasons.  But there are many paying customers who would complain.  So there is a desktop version on offer which I am using.  Obviously a person who desires to run a browser will require an end user interface quite like the one in Windows 10.  The preferred end user interface (preferred by Microsoft) has a minimal end user interface that allows you to configure Windows Server 2019 using PowerShell.  PowerShell doesn't run a web browser.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 86847b80-8f8e-9493-86ff-5dfd6412b48f
Version Independent ID: 2ce02bc3-24a1-8c9f-c787-34ab90e9f31d
Content: Microsoft Edge Supported Operating Systems
Content Source: edgeenterprise/microsoft-edge-supported-operating-systems.md
Product: microsoft-edge
GitHub Login: @srugh
Microsoft Alias: srugh

@5U8cVs Hi! Microsoft Edge is supported on Windows Server 2019.
Here are a couple of options you can try to download:

Visit https://www.microsoft.com/en-us/edge and on the page select "Windows Server 2019" from the dropdown box

Visit https://www.microsoft.com/en-us/edge/features and scroll down the page to "Browse across devices", in that section you can click on "Using Windows Server? Get Microsoft Edge here."

Let us know if you are still having issues and if you have further questions regarding Microsoft Edge apart from documentation issues please reach out on the Microsoft Edge Tech Community Forum or for Enterprise specific questions please visit the Enterprise section of the Tech Community. Thanks!

Closing due to no response.


v3.3: compiler-sfc fails to resolve source when using path mapping

Vue version
3.3.0-beta.1
Link to minimal reproduction
https://stackblitz.com/edit/node-hrwual?file=repro/src/components/HelloWorld.vue
Steps to reproduce
Consider a component that uses an interface imported with path mapping (as the setup of a project generated with create-vue allows to do):
<script setup lang="ts">
import { User } from '@/User';
defineProps<{
  msg: string;
  user?: User;
}>();
</script>

What is expected?
The compiler should find the file, as if it was imported with:
import { User } from '../User';

What is actually happening?
When bumping from v3.2.47 to v3.3.0-beta.1, the compiler throws (with pnpm dev or pnpm build):
[@vue/compiler-sfc] Failed to resolve import source "@/User".

/home/projects/node-hrwual/repro/src/components/HelloWorld.vue
3  |  defineProps<{
4  |    msg: string;
5  |    user?: User;
   |           ^^^^
6  |  }>();
7  |  </script>
16:04:34 [vite] Internal server error: [@vue/compiler-sfc] Failed to resolve import source "@/User".

System Info
System:
    OS: macOS 13.3.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 4.89 GB / 64.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 16.17.0 - ~/.volta/tools/image/node/16.17.0/bin/node
    Yarn: 1.22.17 - ~/.volta/tools/image/yarn/1.22.17/bin/yarn
    npm: 8.19.3 - ~/.volta/tools/image/npm/8.19.3/bin/npm
  Browsers:
    Chrome: 112.0.5615.137
    Firefox: 111.0.1
    Safari: 16.4
  npmPackages:
    vue: 3.3.0-beta.1 => 3.3.0-beta.1

Any additional comments?
No response

It seems that it does not work because you're using project references. If you add paths in your tsconfig.json it will work:
{
  "compilerOptions": {
    "paths": {
      "@/*": ["./src/*"]
    }
  },
  "files": [],
  "references": [
    {
      "path": "./tsconfig.node.json"
    },
    {
      "path": "./tsconfig.app.json"
    },
    {
      "path": "./tsconfig.vitest.json"
    }
  ]
}

FYI this specific case should fallback to skipping runtime check without an error with latest main branch after 2d9f6f92 - that said project references are indeed not supported at the moment.

I get this error (only during build) when importing a type with relative path eg:
'../types/myfile' ❌

when I use project root import, it resolves without errors
'@/types/myfile' ✅

I should note that this error arises when I import a file to use in defineProps<MyType>() since we can do that now which is awesome 🙂
I fixed it with alias import, but I think it should be fixed for relative imports too

I get this error (only during build) when importing a type with relative path eg:
'../types/myfile' ❌

when I use project root import, it resolves without errors
'@/types/myfile' ✅

I should note that this error arises when I import a file to use in defineProps<MyType>() since we can do that now which is awesome 🙂
I fixed it with alias import, but I think it should be fixed for relative imports too

@gVguy I am having the same issue, also only in an actual build and also only when importing a type to use in defineProps. Interestingly it only occurs on windows build agents, MacOS and linux are fine

Interestingly it only occurs on windows build agents, MacOS

Can't confirm this, for me it occured on MacOS

Interestingly it only occurs on windows build agents, MacOS有趣的是，它只发生在 Windows 构建代理、MacOS 上

Can't confirm this, for me it occured on MacOS无法确认这一点，对我来说它发生在 MacOS 上

I encountered the same issue. When I try to reproduce it on Stackblitz, it behaves normally. This is my reproduction. But in my local environment, compiler-sfc cannot resolve imported Prop types.

The code in my local environment is exactly the same as in Stackblitz. I'm using

Mac Mini M2, macOS 13.5
node v18.15.0
pnpm v8.6.6
The dependency versions are consistent with Stackblitz.

I get this error (only during build) when importing a type with relative path eg:
'../types/myfile' ❌

when I use project root import, it resolves without errors
'@/types/myfile' ✅

I should note that this error arises when I import a file to use in defineProps<MyType>() since we can do that now which is awesome 🙂
I fixed it with alias import, but I think it should be fixed for relative imports too
Thank you.  That helps me a lot

@gVguy Thank you, That helps me a lot.


Refactor template extension and add unit tests

AB#198614

Codecov Report

Merging #666 into master will increase coverage by 4.51%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #666      +/-   ##
==========================================
+ Coverage   19.50%   24.01%   +4.51%
==========================================
  Files          14        6       -8
  Lines         933      204     -729
  Branches      158       26     -132
==========================================
- Hits          182       49     -133
+ Misses        740      155     -585
+ Partials       11        0      -11

Impacted Files
Coverage Δ

docs-article-templates/src/helper/cleanup.ts
26.66% <100.00%> (ø)

docs-preview/src/seo/seoHelpers.ts

docs-preview/src/markdown-extensions/row.ts

docs-preview/src/markdown-extensions/includes.ts

...ocs-preview/src/markdown-extensions/codesnippet.ts

docs-preview/src/seo/docFxHelpers.ts

docs-preview/src/seo/seoPreview.ts

docs-preview/src/markdown-extensions/column.ts

docs-preview/src/markdown-extensions/image.ts

docs-preview/src/markdown-extensions/div.ts

... and 11 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 bd61318...5d1015f. Read the comment docs.


how to connect iphone app to TV

I have you iOS app on iPhone 6 and 5s and TV app on Simulator .
Can we connect on simulator ?.can you please tell me how to do so  ?or whats the solution to test the connection ?

Damn, you're fast! Sadly I didn't manage to run the iOS app & tvOS app at the same time. So I'm currently waiting to get my USB-C cable to run the app on the actual device.
All the networking code is untested...


libxml2 and libxslt: build against python3 by default

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

cc @NixOS/darwin-maintainers. Should we use Python 3 for the bootstrapping Python or is that orthogonal to this issue?

After this change, I get this error:
$ nix-shell -p shared-mime-info -I nixpkgs=.
...
Traceback (most recent call last):
  File "/nix/store/b2cms2q9bmrhp1as93m8vbkjq9r6zn5y-itstool-2.0.2/bin/itstool", line 1545, in <module>
    out = file(opts.output, 'w')
NameError: name 'file' is not defined
make[2]: *** [Makefile:1179: freedesktop.org.xml] Error 1
make[2]: Leaving directory '/build/shared-mime-info-1.13.1'
make[1]: *** [Makefile:731: all-recursive] Error 1
make[1]: Leaving directory '/build/shared-mime-info-1.13.1'
make: *** [Makefile:455: all] Error 2
builder for '/nix/store/40rwsy7q9hbiqhgi5ck5kibmirmywv8k-shared-mime-info-1.13.1.drv' failed with exit code 2
error: build of '/nix/store/40rwsy7q9hbiqhgi5ck5kibmirmywv8k-shared-mime-info-1.13.1.drv' failed

I notice this error when I try to run any NixOS test, such as nix-build nixos/tests/login.nix.
Reverting 8d926467be6438fd88b19b38389ad1fdfc472f4d or makes the error go away, as does dropping itstool back to python2 as in #72335.
itstool says it does not support Python 3 until version 2.0.3, but bumping its version isn't straightforward because itstool/default.nix says 2.0.3+ breaks the build of gnome3.gnome-desktop.

@chkno itstool isn't even used in gnome-desktop anymore, it's likely this issue has been resolved already and we can update itstool, or maybe there's a patch needed in libxml2.

Yeah, distro's have this patch from fedora

https://git.archlinux.org/svntogit/packages.git/tree/trunk/itstool-2.0.5-fix-crash-wrong-encoding.patch?h=packages/itstool

to fix the crash. Maybe it has been committed in a newer version.

@worldofpeace unfortunately gnome-desktop was not the only affected package, the cause is not fixed https://bugzilla.gnome.org/show_bug.cgi?id=789714

@jtojnar https://src.fedoraproject.org/rpms/libxml2/blob/master/f/libxml2-2.9.8-python3-unicode-errors.patch?

Yes, that seems to have come from https://bugzilla.opensuse.org/show_bug.cgi?id=1065270. It is definitely better but as https://bugzilla.gnome.org/show_bug.cgi?id=789714#c4 says, it is just a hack for broken libxml2. I wonder why is this not considered a critical security vulnerability.

Yes, that seems to have come from https://bugzilla.opensuse.org/show_bug.cgi?id=1065270. It is definitely better but as https://bugzilla.gnome.org/show_bug.cgi?id=789714#c4 says, it is just a hack for broken libxml2. I wonder why is this not considered a critical security vulnerability.

It seems upstream doesn't find it concerning

https://gitlab.gnome.org/GNOME/libxml2/issues/12


java.net.ConnectException: Connection timed out: connect

Hello,
I'm trying to use your tool but get a "java.net.ConnectException", can you give me any advice?
thanks

I'm closing this, as the information provided is not sufficient to debug / understand the problem.


Preformance enhancement for security checking (#6697)

Description
This PR makes the change suggested in #6697.  Essentially the formating of the asset and connection bean for calls to the security connector now occur after the metadata-security module has deterined there is a security connector to call rather than on every request.  It will make no difference to a server running the security connector.  Those servers not running the security connector will run faster.  The other benefit is that the bean formatting code has moved from the generic handler to the metadata security module which is better modularization.
During the testing I spotted that the generic handlers were checking that the qualified name is unique twice during the create call.  This is an expensive check to make since it requires a qury to the cohort so removing the second check will improve performance on the create.
Fixing this bug meant the parameters that pass the unique parameter on the create bean call were no longer needed and so this method no longer has these parameters and all of the callers have been updated.
Other bugs I discovered were that the ValidValuesImplementation relationship, which should be multi-link was using the uni-link creation method which means  that the second mapping relationship for a code table will fail.  This will impact the GHC issue https://github.com/odpi/egeria-samples-api/issues/8 which will require this fix to run.
Finally I updated the type archive for release 3.12
Related Issue(s)
#6697
Testing
FVT and the open metadata labs
Release Notes & Documentation
Just internal
Additional notes

Final commit adds a new type called RootSchemaType.  This is inserted in the SchemaType inheritance hierarchy for the schema types that connect the schema to the asset/port etc.  See models 53xx for its use.


Run ATTACH command?

Hi,
Is there a way to use the sqlite ATTACH command to join two separate databases?
https://stackoverflow.com/questions/6824717/sqlite-how-do-you-join-tables-from-different-databases
Thanks.

Sorry have no idea if the open source version can do this as it uses the native implementation of sqlite on the phone and I have never have tried.   Download the demo, add a second db and try...  :grinning:
However, I am pretty sure the encrypted commercial version can; as the SQLite driver for the encryption has pretty much every single feature turned on...


[PL] Translation of mix lesson

In scope of issue #202

@kdebowski, @Koziolek is trying to keep you busy 😝

Now few days of rest :) We have long bank holidays ;)

@Koziolek, I added only one note.


change the default AMI from CoreOS to Amazon Linux 2 LTS

Background
to make sure the OS is more compatible with other components such as

AWS VPC CNI
AWS ALB Ingress

And eliminate potential complexity of maintainence in the future.
TODO

[x] make sure the latest AMI in cn-north-1 and cn-northwest-1 is compatible with the latest stable kops
[x] make sure latest AWS VPC CNI (1.3) is compatible
[ ] https://github.com/kubernetes/kops/issues/6341 need to be identified and fixed
[x] CoreDNS as the replacement of kube-dns
[ ] make sure AWS ALB Ingress is compatible
[x] update env.config and set Amazon Linux 2 LTS as the default AMI

why not use kope.io/k8s-1.11-debian-stretch-amd64-hvm-ebs-2018-08-17 ?

@Cplo  Kops supports many different linux distributions
https://github.com/kubernetes/kops/blob/master/docs/images.md
To make sure it works best in AWS and eliminate potential compatibility issues and complexity, we plan to stick to Amazon Linux 2 instead, given Amazon EKS is using it's optimized AMI based on Amazon Linux 2 as well. However, we were still having some issue here, so we prefer to stick to CoreOS given it's still the proven working image for Kops in Beijing and Ningxia.
You still can change the AMI to any variant linux images kops supports. Just pass AMI into the Makefile and it will use the AMI ID you specified.


rust-analyzer: 2020-04-20 -> 2020-06-01 and fix build of vscode extension

Motivation for this change
Bump version.
Also fix build of vscode extension (fix #89286).
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Can we get this merged? This extension has been broken for a week now.


object-literal-sort-keys is nearly (but not quite) alphabetic

Bug (Suggestion?) Report

TSLint version: 4.2.0
TypeScript version: 2.0.7
Running TSLint via: CLI

TypeScript code being linted
const expected = {
  "Chiefs": "#3996D9",
  "CLG": "#008FEA",
  "CLG Red": "#DC0031",
  "Cloud9": "#1D9DD8",
  "compLexity": "#870000",
  "Conquest": "#D08685",
  "CPH Wolves": "#FCBA2F",
  "Crowns": "#E3DB9A",
  "CSGL": "#DB8328",
  "CyberZen": "#BC3728",
}

with tslint.json configuration:
{
  "extends": "tslint:recommended",
  "rules": {
    "no-console": false
  }
}

Actual behavior
The following ordering is asserted by the rule:
const actual = {
  "CLG": "#008FEA",
  "CLG Red": "#DC0031",
  "CPH Wolves": "#FCBA2F",
  "CSGL": "#DB8328",
  "Chiefs": "#3996D9",
  "Cloud9": "#1D9DD8",
  "Conquest": "#D08685",
  "Crowns": "#E3DB9A",
  "CyberZen": "#BC3728",
  "compLexity": "#870000",
}

Expected behavior
For context I have an object literal that I am using as a data store where the keys are CSGO team names. The code above is a sample but the real object is about 100 entries. Storing data in literals like this is not a great idea admittedly but the implication is that the keys can contain pretty much any character (for example capital letters) anywhere in the string.
The actual code sample is the order specified by TSLint. It looks like the rule compares strings by just doing > and JavaScript sorts capitals first IIRC which is what is giving the "almost" alphabetical result.
Another simpler example would be:
// What the rule wants
const actualAgain = {
  array: [],
  objList: [{}, {}],
  object: {},
}

// Alphabetical
const expectedAgain = {
  array: [],
  object: {},
  objList: [{}, {}],
}

The result is kind of logical but unexpected. If I were going through the code above and sorting my literals I would do it alphabetically and the fact that the rule told me otherwise would be confusing, it almost reduces you to trial and error unless you understand the comparison logic being used.
So my question is

Should it ideally be sorting alphabetically? (I am thinking .toUpperCase() on both before comparison)
If not by default should it be an option?

Also thinking now about the iffy sample I've given, would it be good to subject object literal keys to the same kind of checks performed on identifiers? That is probably a different issue though.

Yeah, I don't think it should consider case when sorting

Should be pretty easy to change the behavior to be case-insensitive. Change this line to:
const key = keyNode.text.toLowerCase();

... but this would unfortunately be a breaking change. Best thing would be to add this as a "ignore-case" rule option and change the default in v5.0


HTMLInfowindow creation seems to "unlink" marker object reference from map marker

I'm submitting a ...  (check one with "x")
[ ] question
[ X] any problem or bug report
[ ] feature request
If you choose 'problem or bug report', please select OS:  (check one with "x")
[X ] Android
[X ] iOS
cordova information:  (run $> cordova plugin list)
insert the output from the command here

If you use @ionic-native/google-maps, please tell the package.json (only @ionic-native/core and @ionic-native/google-maps are fine mostly)
"@ionic-native/core": "4.4.2",     "@ionic-native/geolocation": "^4.4.2",     "@ionic-native/google-maps": "4.4.2",
For my app's behaviour, when clicking a marker i was saving the marker's reference to a global variable, to, when clicking the map, another marker, some buttons i have over the map, the infowindow would close and the marker would change it's icon.
This worked 100% fine with the default infoWindow.
After setting up a custom  HTML htmlInfoWindow,  the object i save as reference, when "de-selected", displays the correct icon name ( the changed one), after the change, but the map is not updating.
the png files:
ics.png -> selected icon
ic.png -> unselected icon
the code that adds the infowindow:
        let html: string =
          '
'+
          '
Farmacia ' + marker.get("debugId") + '
'+
          '
'+
          '
Lorem ipsum
667733
 De dilluns a divendres
'+
          ''+
          '
';
        htmlInfoWindow.setContent(html);
        htmlInfoWindow.open(marker);
        this.lastMarker = marker;

the code that clears it:
clearLast(){
    if (this.lastMarker != undefined) {
      this.lastMarker.hideInfoWindow();
      var image = {
        url: "assets/img/ic.png",
        size: {
          width: 22,
          height: 32
        }
      }
      this.lastMarker.setIcon(image);
    }else{
      console.log("marker is undefined");
    }
  }

when printing this.lastmarker on next marker's  click,  it prints ic.png (unselected), but still displays as selected.

when i comment the htmlInfoWindow.open() lines, it works fine:

I think it might have to do with the fact of adding a HTMLInfoView, maybe it's modifying the marker or something in behind the code. i have no clue.

You should not control show/hide the htmlInfoWindow() by yourself. The plugin does that automatically.
If you do, you get the problem.
The recommended way is to create only ONE htmlInfoWindow and recycling it.

show me an example please. is this the reason the marker breaks?

Please try like this:

class MapPage {
   htmInfoWindow: HtmlInfoWindow =  new HtmlInfoWindow();

   locations: any[] = [
       {
          position: {lat: ..., lng: ...},
          myHtml: "location1"
       },
       {
          position: {lat: ..., lng: ...},
          myHtml: "location2"
       },
       ....
       {
          position: {lat: ..., lng: ...},
          myHtml: "locationN"
       },
   ];

   loadMap() {
     this.map = GoogleMaps.create(...);
     this.map.one(GoogleMapsEvent.MAP_READY).then(() => {

        let mvcArray:BaseArrayClass<any> = new BaseArrayClass<any>(locations);
        mvcArray.mapAsync((location: any, next: (marker:Marker)  =>void) => {
           this.map.addMarker(location).then(next);
        }).then((markers: Marker[]) => {
           markers.forEach((marker: Marker) => {
              marker.on(GoogleMapsEvent.MARKER_CLICK).subscribe(this.onMarkerClick);
           });
        });

    });
    onMarkerClick (params: any[]) {
      let marker:Marker = <Marker> params.pop();
      this.htmlInfoWindow.setConent(marker.get("myHtml"));
      this.htmlInfoWindow.open(marker);
    }
}

The responsiveness of this method is slower ( HTMLInfoWindows take a lot to show), still shows issues when changing selected marker, and most importantly, breaks after some clicks on markers:
Uncaught TypeError: Cannot read property 'getMap' of undefined     at HTMLInfoWindow.calculate (HtmlInfoWindow.js:157)     at HTMLInfoWindow.trigger (BaseClass.js:62)     at HTMLInfoWindow.set (BaseClass.js:34)     at Marker.<anonymous> (BaseClass.js:44)     at Marker.trigger (BaseClass.js:62)     at Marker.set (BaseClass.js:34)     at Marker.setIcon (Marker.js:229)     at callInstance (vendor.js:85916)     at Marker.<anonymous> (vendor.js:85992)     at Marker.value [as setIcon] (vendor.js:146681)

If you have some problems, you should share your project files. I will check it.
Otherwise, please debug by yourself.
At least, you should read JavaScript code, and all code is open source.

I am unable to share with you a  in-production project.
I have debugged my code and it works perfectly fine with your library's native InfoWindow
It's when i try to set up a HTML infowindow that the marker's reference on the map is lost, and the HTML infowindow stops working.
I literally copied your code over mine just to make sure i wasn't doing anything wrong, but nay, it kept behaving incorrectly.
Steps to reproduce (again):
create a map.
create a marketCusterer.
add markers to the marketCluster ( either directly ( as a map of Markers ) or async ( one by one).
on  MARKER_CLICK, save to a global variable a reference to the clicked marker, and change the marker icon to anything else.
on MAP_CLICK (just to make a quick text), change the referenced marker's icon to the original icon.
IF using native infowindow ( title + snippet), the icon will change without issues.
IF using your HTMLInfowindow code ( html string, global infowindow reference recycled), the icon won't change and the last marker clicked reference will no longer apparently be linked the shown marker on the map, not changing the icon or behaving that it should. And clicking too many icons at once pretty fast, will break the HTMLInfoWindow code as shown above.

Sorry, I'm so busy. Until you create a demo project that reproduce your issue , or share your project files with private git repo, I don't help this.

Everyone who use this plugin in produce app, and want to help by me, they does either create a demo or share the project files on a private repo.
Some people still denies both, they search alternative library.
I'm not public service, something like that.
So you need to consider how save my time.
Time is money
This is common idiom in world wide.
If you want to receive my support by free, you should contribute to save my time.

I will try to create a blank project just with a map and some markers for you to see what's going on.
In the event where this fix gives you too much work (weird JS glitches, impossible to fix native stuff), could you help me on modifying your native OBJ-C code to replicate a custom infowindow adapter and layout file i have set up? it adds the option to setup up to two bottom buttons on a infowindow.
I'll post you the code and layout so you can reuse it and publish it if you want to when it's done, it's a very common feature in apps that use maps, a button that opens the details window and a button that opens the phone's goopge maps with a set up route.
i know how to do it in swift 3, but i have  0 clue on how obj-c works (i'm a late adopter of ios).

@wf9a5m75   here you have a sample project.
https://mega.nz/#!cbxxABBI!HvIodyWl3AAMq_k1pT_ITp9s7go3y5eINkGgYX62wxc
commnet the next lines :
this.htmInfoWindow.setContent(html);
this.htmInfoWindow.open(marker);

and set a title and snippet to see the different behaviours.

Thank you for your understanding. I don't need to include the nodejs folder and platform folders.
However, I appreciate you put your code to GitHub, instead of one zip file.
Because I can see what's updated when you change the code later, we can refer the code, I can update the code if you give me a permit, ... etc
Archive file is not able to do something like that.
Please use Github.

Ok, i will when i get home, (2-3hrs). in the meanwhile, you can check the behaviour. thanks.

Thanks, When I arrive to my work desk, I will check it.(I just waked up 10 minutes ago)

ping

I don't need the Welcome pdf

Sorry, it was my 3AM when you posted.
repo created
https://github.com/tryadelion/DemoMaps

Thank you for sharing the demo project, but what is the problem?

I recommend you use the multiple_map branch if you have problems with v2.1.1

if you approach the map more, there's 3 markers. by the code, when a marker is clicked, it should change it's icon to a selected color. when clicking outside the marker, the marker should go back to the normal color ( grey ). currently with this version, when using native InfowView, the markers change colors correctly, but, when using the HTMLinfoview, they don't, the referenced marker ( lastMarker global )  doesn't change the icon.

the multiple_map branch way of implenting itself has not been quite ionic friendly in the past, giving me a lot of troubles installing it. Has the process changed in any way? installation didn't work in any possible way for us and we had to switch to web JS maps for a recent project.
This one i'm using seems quite stable and hasn't given any installation, update or upgrade issue so far.

Also your marker seems to behave much nicely than mine, mine on map pan glitches over the screen  "teleporting" itself to multiple locations back and forth until it finds the marker.

The multiple_maps is development version. It means the edge version, sometimes good than master, sometimes bad than master.
It is depends on the timing (my development)
Currently good than master.
I fixed and improved many things, that's why I recommended.

I will check your repo again tomorrow.

ok! thanks.

ping

US is in holidays.

Ok, ok. had no idea. sorry!

Tentatively, I fixed the HtmlInfoWindow.js code on the airplain. Should be fine (I tested).
Please try the multiple_maps branch. (I'm going to bed from now)

@wf9a5m75  althought needs more testing, i can almost consider both HTMLinfowview flickering and marker "losing reference" when HTML infoview is enabled fixed! i would suggest PR-ing to the main repo so more people can have a fluentlier first hands on experience with the library.

Did you test the multiple_maps branch or no?

Yes, this is what i'm saying. althought i've found a quite breaking issue, even when adding your META tags, a button inside the HTMLInfoview is not getting any click call, the map  or the marker take the click event instead. i copied your example code from : https://github.com/mapsplugin/cordova-plugin-googlemaps-doc/blob/master/v2.0.0/class/HtmlInfoWindow/newHtmlInfoWindow/README.md

Use the multiple_maps branch code. It's solved problem in the multiple_maps branch code.

Yes, im using that. the marker icon issue is solved, the htmlinfoview glitch is solved,  but i can't access any element on "click" inside the htmlinfoview, the MAP_CLICK takes over any action.

Did you try cordova.fireDocumentEvent('plugin_touch', {}); when you open the HtmlInfoWindow?

And additionally, button of ionic does not work is not this pluing's fault.
That's ionic problem. You need to complie your html through the ionic dynamically

Even you use the normal button, and it doesn't work, please make another issue, and close the threads that are already solved.
PR is welcome with test project.

Normal button, or a div with a onclick="alert'HI')".or even a  DOM injected eventListener doesn't work.
the map canvas takes any incoming click call and puts it through the  GoogleMapsEvent.MAP_CLICK, i debugged it, this is what happens when i click anywhere on the infowindow.

Will update the demo project


Config Screen issue

AE2WTLib 10.1.1-beta.4
Applied Energistics 2 10.1.0-beta.2
Cloth Config API 6.2.57
Fabric API 0.46.4

looks like that got messed up when porting to architectury aswell.
I didn't even now / is a leagal character in a translation key.
will be fixed in the next release.


Improve Crypto file portability: allow for MasterPass credentials to be exported/imported

Implement export/import MasterPass credentials functionality so that formerly encrypted data using a masterpass can be decrypted with the same masterpass (after reset) and allow for installation to be restored. This will greatly improve the Crypto file portability across different machines running Crypter.

Resolved with https://github.com/HR/Crypter/commit/983f1054db6d2bba98e0b163f6ad03b847639db3


eslint-plugin-ava

Will a PR for inclusion of esling-plugin-ava be welcomed?

@Flet @feross I know everyone is busy. I'm just asking whether pull-requests and issues that are not in feross/standard are being looked at by someone. Should I get more eyes on this by creating an issue in feross/standard?

It doesn't make sense for that eslint plugin or any other one to be in this package. This package doesn't define any rules.


Added "Perfecto Mobile, Inc." to line 3

Saw that the license referenced "Quantum" but not our legal entity, Perfecto Mobile, Inc.

Already merged.


Regression: null keys in package.yaml break parsing

Empty keys in package.yaml used to be fine, now they cause the parser to fail. Trivial example:
license:
# Error while parsing $.license - expected String, encountered Null

This applies to nested keys as well.
Not sure when this happened, i just discovered it when my heroku buildpack pulled in stack-1.7.1.

I'm closing this as wontfix.  That said, I'm still interested in dissenting opinions.  If there is a good case for restoring the old behavior then it is easy to convince me.

@tejon thank you for bringing this to my attention and sorry for the friction this might have caused.


fix: Dasherize conversion event types path

[x] I have run pre-commit to check linting
[x] I have added information to docs/ if required so people know about the feature!
[x] I have filled in the "Changes" section below?
[x] I have filled in the "How did you test this code" section below?
[x] I have used a Conventional Commit title for this Pull Request

Changes
Fixes https://github.com/Flagsmith/flagsmith-split-testing/issues/7
I accidentally used underscores when I first wrote this code. This is a simple fix.
How did you test this code?
N/A

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 95.86%. Comparing base (90e10cf) to head (c35c0f2).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3516   +/-   ##
=======================================
  Coverage   95.86%   95.86%
=======================================
  Files        1097     1097
  Lines       34140    34140
=======================================
  Hits        32727    32727
  Misses       1413     1413

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


Change sublayer renderer

The sample feels incomplete without the ability to reset the renderer back to the original. Can you add that?
Everything else looks good.

@dg0yal I have made the changes. Please take another look.

Looks good. Please resolve conflict and merge


INSTALL FAILS in Windows

source .venv/bin/activate
fails in Windows :   file or command not found
and WSL
-bash: .venv/bin/activate: No such file or directory

only 3 months after raising the issue a workaround was offered on DC
https://community.intersystems.com/post/running-flask-applications-iris#comment-272086
The issue is neither closed nor the error in README corrected


Fix render of empty elements in Structured Log Details

Description
There was a problem described in #2967 where an empty inner exception was being rendered.
This code is more generic and only non-empty values will be rendered.
This is the before:

This is now the final result (tested only for RabbitMQ):

Fixes partially #2967
Checklist

Is this feature complete?

[X] Yes. Ready to ship.
[ ] No. Follow-up changes expected.

Are you including unit tests for the changes and scenario tests if relevant?

[ ] Yes
[X] No

Did you add public API?

[ ] Yes

If yes, did you have an API Review for it?

[ ] Yes
[ ] No

Did you add <remarks /> and <code /> elements on your triple slash comments?

[ ] Yes
[ ] No

[X] No

Does the change make any security assumptions or guarantees?

[ ] Yes

If yes, have you done a threat model and had a security review?

[ ] Yes
[ ] No

[X] No

Does the change require an update in our Aspire docs?

[ ] Yes

Is this introducing a breaking change?

[ ] Yes

Link to aspire-docs issue (please use this breaking-change template):

[ ] No

Link to aspire-docs issue (please use this doc-idea template):

[X] No

Microsoft Reviewers: Open in CodeFlow

I don't think this is the right place to fix this. It could be valid to have empty tags on structured logs.
The right place to fix is not add an empty exception.innerexception tag inside RabbitMQ library when it's not neccessary.

I don't think this is the right place to fix this. It could be valid to have empty tags on structured logs.
The right place to fix is not add an empty exception.innerexception tag inside RabbitMQ library when it's not neccessary.

That was my second guess :)
I'll close this and fix it there.
Thanks!


Change readme.md readme with Atlassian Cloud auth instructions

Working with Atlassian Cloud, We must replace password by an API token, it's not clear on readme.me.
I can submit a PR if you agree, but basically is something like:

Authentication
Are you using Atlassian Cloud? use your API token instead of your account password, you can generate one following these steps:

access https://id.atlassian.com/manage-profile/security/api-tokens
click on "Create API token" button and save it in a safe place
(See more details about APIs auth on official page

Here's the official doc.
https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/

@rafaelleonardocruz the requested change makes a lot of sense, so yes please, your PR is welcome 🙏


Use of undeclared identifiers

@ahmad71666  hi I suppose this is an issue related to the latest xCode version.
Please try this beta version instead. The issue should gone
https://github.com/tr3v3r/react-native-esc-pos-printer/pull/139


nottinygc memory leak with fastcache

Description
I am developing a WASM plugin for Istio ingress gateway. In the WASM Plugin, the fastcache is used for caching and the total cache size is limit to 32MB for preventing the OOM, however, the memory usage still keeps increasing
How to reproduce
dependecy:

tinygo v0.28.1
nottinygc v0.4.0
proxy-wasm-go-sdk v0.22.0
istion v1.18.0

The code of plugin to describe the issuse :
proxy-wasm-memory-leak

I`ve modify the source code of fastcache to make it  can be compiled with tinygo

The Test script:
func TestMemoryLeak(t *testing.T) {
// Ingress Host and port :<IP_ADDRESS>:31505
	req, err := http.NewRequest("GET", "http://<IP_ADDRESS>:31505", nil)
	if err != nil {
		panic(err)
	}
	for i := 0; i < 10000000; i++ {
		_, err := http.DefaultClient.Do(req)
		if err != nil {
			continue
		}
	}
	fmt.Println("done")
}

what I’ve inspect is that is memory is keep increasing and never release

Thanks @LoremipsumSharp - I have been able to reproduce with a simple snippet using wazero without proxy-wasm-go-sdk or Envoy. Will try to debug this but it may take some time

Hi @LoremipsumSharp - very sorry it took so long to get some time to debug this. I tried running a fastcache loop without nottinygc using the default TinyGo GC and had the same memory leak behavior. So I believe this may not be an issue with nottinygc but just with TinyGo + fastcache interaction itself. Note that TinyGo has had memory leak issues with map keys before (one is https://github.com/tinygo-org/tinygo/pull/3483) and latest version may still have some.
Anyways, because wasm plugins are single threaded, fastcache is very much overkill. If you can, you may consider using just a normal Go map, there is no need for any locking or atomics.
I am going to go ahead and close this but please feel free to reopen if you think the issue is actually nottinygc-specific!


Make encryption optional for update

As suggested in Issue #36, this adds a way to optionally disable encryption when updating an item

Anything wrong with this approach?

Looks great!


Unified state and writable structure

We can change {:send, data, state} | {:nosend, state} with {state, writable}. If writeable is a binary or io_list it can be written to the socket. When :erlang.iolist_size(writeable) is equal to 0 then it is equivalent to no send.
Therefore both handle_packet/2 and handle_message/2 can both return the same writeable and state structure.
This is the first step towards eliminating all side effects and side causes and using a statemachine and comm library.
In the final case every callback has the following signature
callback(args) :: {{mod, config}, writeable, [other sends]}

Ace.HTTP responses from callbacks should look as close as possible to what the domain expects, response, chunked_response etc.
Ace.HTTP.Response.serialize(response) :: writeable
Ace.HTTP.Response.serialize(chunked_response) :: {:more, writeable}
# just call next
Ace.HTTP.Response.next_state(response) :: maybe(app)
Ace.HTTP.Response.to_outtray(chunked_response) :: {app, [conn:, writable, pid: "m1"]

see latest developments in raxx with streaming instead


Remove accidental mismatch of "PAMAP"

https://www.openstreetmap.org/way/166528135 would no longer be flagged by this change, although it's still incompatible data.
Adding more tests in https://github.com/openstreetmap/iD/blob/develop/test/spec/validations/incompatible_source.js might be good.

I don’t know anything about Europe so I can’t help here. As far as I can see it’s a regression introduced by a patch to warn about proprietary Chinese data.


Direct import of tar files into virtual directories

See original issue on GitLab
In GitLab by [Gitlab user @jmacarthur] on Jul 27, 2018, 11:27
Background
This is an issue filed for a proposed MR !445 which currently extracts tar files to a temporary directory before importing that temporary directory. This is inefficient.
Task description

[ ] Implement direct tar file import into virtual directories

Acceptance Criteria
Direct import of tar files with functional equivalence to existing code.

In GitLab by [Gitlab user @jmacarthur] on Jul 27, 2018, 11:27
mentioned in merge request !445

In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 13:44
marked this issue as related to #540

In GitLab by [Gitlab user @tristanvb] on Aug 2, 2018, 13:45
Do we need separate issues here for zip and deb plugins ?

In GitLab by [Gitlab user @jennis] on Aug 22, 2018, 13:00
[Gitlab user @jmacarthur] as well as being inefficient, I've faced another, more serious issue.

Issue #601.

In GitLab by [Gitlab user @jennis] on Aug 22, 2018, 13:01
marked this issue as related to #601

The only case I can imagine where this can be useful is in tar source's stage() method.
In this case, we should just implement this in tar source's stage() method, but not add any core functionality for importing tarballs which is useless outside of tar source.


Ensure downlevel-dts is 4.7-ready

This means we need to support https://github.com/sandersn/downlevel-dts/issues/73

Done in sandersn/downlevel-dts#74 -- thanks @Andarist !


Convert.ToDouble fails on non-english locale

It should be Convert.ToDouble(xxx, CultureInfo.InvariantCulture);

@Dentorol thanks for the report.


Add support for appsecret_proof

With this change, you are able to create graph API on apps that have App Secret Only enabled. Basically, that's a feature that only allows requests that send the appsecret (good for servers).
You can read about it here: https://developers.facebook.com/docs/graph-api/securing-requests#appsecret_proof
This implementation works, and the documentation should just say:

GraphAPI(access_token=None, appsecret=None, timeout=None, version=None)

appsecret: The App Secret key of the app using the Graph. This is usable for apps that only allow requests from server. Read more: https://developers.facebook.com/docs/facebook-login/security#appsecret

This looks good, but I have a couple of suggestions.
For better backwards compatibility, I think it would be best if the appsecret parameter was located at the end of the function (after version).
There are a couple of PEP8 issues that the automated tests found:

facebook/init.py:85:80: E501 line too long (86 > 79 characters)
facebook/init.py:93:80: E501 line too long (98 > 79 characters)
facebook/init.py:98:1: W293 blank line contains whitespace
facebook/init.py:252:1: W293 blank line contains whitespace

Let me know if you don't have time to fix these and/or update the documentation, and I should be able to take care of them soon.

I had a very tight deadline for an app that uses this SDK, so that's the change I am using.
I could fix it on Saturday or so, I don't have Git at the moment. I will write tests too.

Closing due to lack of response.
I think this is further along than #196, but still needs the changes I mentioned.


added xattr flag when creating soci index

DO NOT MERGE: Testing still needs to be added, but please feel free to review what is present
Why
The listxattr and getxattr fuse operations are quite costly, but the vast majority of files do not have any extended attributes.  Given this we can disable xattrs in the fuse file system.
What
This PR does two main things:

Adds an option to build a soci index that knows at the layer level whether xattrs are present
Adds the ability to read this new field in the soci index and disable xattrs in the fuse file system if xattrs are not present in that layer.

BUILDING THE INDEX
This PR adds a new xattr-optimization flag to the create command (cmd/soci/commands/create.go).  This allows the user to opt into a new flow which checks if any files in a given layer have an xattr.  If none of the files have an xattr a new annotation is added to the soci index ocispec.  (soci/soci_index.go)
This new feature is turned off by default.
DISABLING XATTRS IN FUSE
When the layer is resolved it checks the ocispec for the new annotation (fs/layer/layer.go).  If not found it defaults to the original behavior.  This new information is exposed via a new function on the layer interface .  If the annotation indicates there are no xattrs present the fuse.MountOptions are updated to DisableXAttrs (fs/fs.go)
Testing
Still To Come
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Question I'm not sure how to answer: How does this interact with overlayfs xattrs?

Taking a step back and considering https://github.com/awslabs/soci-snapshotter/issues/971, I think the real issue we have is that checking opaqueness is expensive. Each check goes through bbolt to see if a file exists. Since the lower layers are immutable, I think we could probably just push opaqueness up into the in-memory nodes.
I'm going to run some quick hard-coded benchmarks (normal, disableXattrs hard coded to true, isOpaque hard coded to false) to see how that compares.

Nope, looks like I was wrong:

Disabling xattrs entirely really is much more performant than moving opaqueness into memory.

Follow-up PR #1021 has been merged. Thanks to @sbuckfelder for the initial research and design here.


Fix unresolved import

Fixes unresolved import introduced in #91, which occurs outside unix.

That was fast :) - thanks!


Whitelist some set of elements to be used via VDOM, incl. paper-*

incl. determining the subset of events we want to support.
requires research on whether just a subset of what gets sent in an event is enough or whether more work is needed (e.g. is the value of interest in an input field already a parameter to the event handler, so we can just subset the parameters to sanitize?)

Fwiw, shell isolates a list of these here:
https://github.com/PolymerLabs/arcs/blob/master/shell_0_6_0/configuration/whitelisted.js
Today event data is restricted to round-tripped private data the particle has installed on a node (the key) and a single value property provided by the target element.
Ensuring proper value property is a requirement for being a privileged (whitelisted) component.

Can we define what constitutes completion on this issue?

Sheriff says this ticket is elderly and should be in bed, not the saloon.


Refactor tests that are testing error codes from marathon to be unit tests with a mocked client.

No activity in a while. Closing.


Attempt to login with server URL succeeds but upload task fails

The login prompt asks for a collection URL, but you can still login if you specify - perhaps accidentally - the server URL instead.
Then when you attempt to upload a task, you get a terrible error message: Cannot read property 'value' of null
For details see: https://github.com/Microsoft/tfs-cli/issues/46 and https://github.com/Microsoft/vso-agent-tasks/issues/593#issuecomment-148762632

Login now asks for a "service URL", and various commands will try to hit the right host.


Upgrade Python for SPEC0 compliance

Currently, we support 3.10-3.12, this needs to be updated for 3.11-3.13 in CI and in pyproject.toml.

Complete in 9a1a8ce7856cf85cc5e11d03b1796ae36938e08c.


Add show log and test results view / action

TODO for showing logs replaced by a "real" implementation incl. a test results view
Project migrated to Gradle and the more modern Gradle JetBrains plugin (thus deleted loads of code depending on the existing Maven implementation, which is not necessary any more)

BTW: This pull request starts to use a jenkins-client library, so to not duplicate the logic of "knowing" Jenkin's API on client side. I am pretty sure there is much more functionality in this plugin that can be migrated to the library, making more code obsolete.

Hi @klassm ,
Sorry for the late feedback. I have been a long while away from plugin development. Thanks a lot for your Gradle migration for the project. I will solve the minor conflicts and merge your PR.
Regards.

@klassm With this change the compability for pther IDEA products (like Webstorm) will be broken because an additional dependency to Java PSI is needed.
Was that change indented?
As Ic see this was needed for the Feature "show Test Results".
MAybe we can an open action to open it in Browser.
What do you think?


closes #9275

Fixes Issue
Closes #9275
Changes proposed

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots
After fix:

Note to reviewers

I am closing this pull request as discussed here https://github.com/EddieHubCommunity/BioDrop/issues/9275#issuecomment-1746298819

ok