Conflicting namespace warning

Describe the bug
Apparently some components are detected twice from the same source: a lot of warnings are printed while building.
Is seems that the conflicting namespace is the same, for better understanding the last warning is this and apparently has no sense.
Maybe related to #3900
Conflicting namespaces:
<EMAIL_ADDRESS>re-exports "CollapseAllVisibility" from both
<EMAIL_ADDRESS>and
<EMAIL_ADDRESS>(will be ignored)

The reproduction consist in a react-ts project, with a replaced button from @fluentui/react package.
The issue appear with:

plain npm
yarn
yarn berry with pnp

Reproduction
https://stackblitz.com/edit/vitejs-vite-dcmhvg?file=src/App.tsx
System Info
System:
    OS: macOS 12.1
    CPU: (8) arm64 Apple M1
    Memory: 87.11 MB / 8.00 GB
    Shell: 3.3.1 - /opt/homebrew/bin/fish
  Binaries:
    Node: 17.2.0 - /opt/homebrew/bin/node
    Yarn: 1.22.15 - /opt/homebrew/bin/yarn
    npm: 8.3.0 - /opt/homebrew/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 96.0.4664.110
    Safari: 15.2
  npmPackages:
    @vitejs/plugin-react: ^1.0.7 => 1.1.3
    vite: ^2.7.2 => 2.7.10

Used Package Manager
npm
Logs
❯ npm run build -- --debug

><EMAIL_ADDRESS>build
> tsc && vite build "--debug"

  vite:config bundled config file loaded in 71.41ms +0ms
  vite:config using resolved config: {
  vite:config   plugins: [
  vite:config     'alias',
  vite:config     'vite:react-babel',
  vite:config     'vite:react-refresh',
  vite:config     'vite:react-jsx',
  vite:config     'vite:modulepreload-polyfill',
  vite:config     'vite:resolve',
  vite:config     'vite:html-inline-script-proxy',
  vite:config     'vite:css',
  vite:config     'vite:esbuild',
  vite:config     'vite:json',
  vite:config     'vite:wasm',
  vite:config     'vite:worker',
  vite:config     'vite:asset',
  vite:config     'vite:define',
  vite:config     'vite:css-post',
  vite:config     'vite:watch-package-data',
  vite:config     'vite:build-html',
  vite:config     'commonjs',
  vite:config     'vite:data-uri',
  vite:config     'rollup-plugin-dynamic-import-variables',
  vite:config     'vite:asset-import-meta-url',
  vite:config     'vite:build-import-analysis',
  vite:config     'vite:esbuild-transpile',
  vite:config     'vite:reporter',
  vite:config     'vite:load-fallback'
  vite:config   ],
  vite:config   build: {
  vite:config     target: [ 'es2019', 'edge88', 'firefox78', 'chrome87', 'safari13.1' ],
  vite:config     polyfillModulePreload: true,
  vite:config     outDir: '/Users/cbartoli/workspace/bin/vite-warning-issue/vite-warning-issue/dist',
  vite:config     assetsDir: 'assets',
  vite:config     assetsInlineLimit: 4096,
  vite:config     cssCodeSplit: true,
  vite:config     cssTarget: [ 'es2019', 'edge88', 'firefox78', 'chrome87', 'safari13.1' ],
  vite:config     sourcemap: false,
  vite:config     rollupOptions: {
  vite:config       input: '/Users/cbartoli/workspace/bin/vite-warning-issue/vite-warning-issue/index.html'
  vite:config     },
  vite:config     minify: 'esbuild',
  vite:config     terserOptions: {},
  vite:config     write: true,
  vite:config     emptyOutDir: null,
  vite:config     manifest: false,
  vite:config     lib: false,
  vite:config     ssr: false,
  vite:config     ssrManifest: false,
  vite:config     reportCompressedSize: true,
  vite:config     chunkSizeWarningLimit: 500,
  vite:config     watch: null,
  vite:config     commonjsOptions: { include: [Array], extensions: [Array] },
  vite:config     dynamicImportVarsOptions: { warnOnError: true, exclude: [Array] }
  vite:config   },
  vite:config   resolve: { dedupe: [ 'react', 'react-dom' ], alias: [ [Object], [Object] ] },
  vite:config   optimizeDeps: {
  vite:config     include: [ 'react/jsx-dev-runtime' ],
  vite:config     esbuildOptions: { keepNames: undefined, preserveSymlinks: undefined }
  vite:config   },
  vite:config   configFile: '/Users/cbartoli/workspace/bin/vite-warning-issue/vite-warning-issue/vite.config.ts',
  vite:config   configFileDependencies: [ 'vite.config.ts' ],
  vite:config   inlineConfig: {
  vite:config     root: undefined,
  vite:config     base: undefined,
  vite:config     mode: undefined,
  vite:config     configFile: undefined,
  vite:config     logLevel: undefined,
  vite:config     clearScreen: undefined,
  vite:config     build: {}
  vite:config   },
  vite:config   root: '/Users/cbartoli/workspace/bin/vite-warning-issue/vite-warning-issue',
  vite:config   base: '/',
  vite:config   publicDir: '/Users/cbartoli/workspace/bin/vite-warning-issue/vite-warning-issue/public',
  vite:config   cacheDir: '/Users/cbartoli/workspace/bin/vite-warning-issue/vite-warning-issue/node_modules/.vite',
  vite:config   command: 'build',
  vite:config   mode: 'production',
  vite:config   isProduction: true,
  vite:config   server: {
  vite:config     preTransformRequests: true,
  vite:config     fs: { strict: true, allow: [Array], deny: [Array] }
  vite:config   },
  vite:config   preview: {
  vite:config     port: undefined,
  vite:config     strictPort: undefined,
  vite:config     host: undefined,
  vite:config     https: undefined,
  vite:config     open: undefined,
  vite:config     proxy: undefined,
  vite:config     cors: undefined
  vite:config   },
  vite:config   env: { BASE_URL: '/', MODE: 'production', DEV: false, PROD: true },
  vite:config   assetsInclude: [Function: assetsInclude],
  vite:config   logger: {
  vite:config     hasWarned: false,
  vite:config     info: [Function: info],
  vite:config     warn: [Function: warn],
  vite:config     warnOnce: [Function: warnOnce],
  vite:config     error: [Function: error],
  vite:config     clearScreen: [Function: clearScreen],
  vite:config     hasErrorLogged: [Function: hasErrorLogged]
  vite:config   },
  vite:config   packageCache: Map(0) { set: [Function (anonymous)] },
  vite:config   createResolver: [Function: createResolver]
  vite:config } +3ms
vite v2.7.10 building for production...
transforming (617<EMAIL_ADDRESS>namespaces<EMAIL_ADDRESS>re-exports "MAX_COLOR_SATURATION" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "MAX_COLOR_HUE" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "MAX_COLOR_VALUE" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "MAX_COLOR_RGB" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "MAX_COLOR_RGBA" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "MAX_COLOR_ALPHA" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "MIN_HEX_LENGTH" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "MAX_HEX_LENGTH" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "MIN_RGBA_LENGTH" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "MAX_RGBA_LENGTH" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "HEX_REGEX" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "RGBA_REGEX" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "cssColor" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "rgb2hex" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "clamp" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "hsl2rgb" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "hsl2hsv" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "hsv2rgb" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "hsv2hex" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "rgb2hsv" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "hsv2hsl" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "getColorFromString" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "getFullColorString" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "updateRGB" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "correctRGB" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "correctHSV" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
transforming (1005<EMAIL_ADDRESS>namespaces<EMAIL_ADDRESS>re-exports "AnimationDirection" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
Conflicting namespaces<EMAIL_ADDRESS>re-exports "CollapseAllVisibility" from both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(will be ignored)
✓ 1068 modules transformed.
dist/assets/favicon.17e50649.svg   1.49 KiB
dist/assets/logo.ecc203fb.svg      2.61 KiB
dist/index.html                    0.52 KiB
dist/assets/index.0799e405.js      1.59 KiB / gzip: 0.82 KiB
dist/assets/index.cd9c0392.css     0.75 KiB / gzip: 0.48 KiB
dist/assets/vendor.1aca95a0.js     301.92 KiB / gzip: 93.46 KiB

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

See this also with the graphql-ws package
Conflicting namespaces: "../common/temp/node_modules/.pnpm/graphql-ws<EMAIL_ADDRESS>re-exports "MessageType" from both
"../common/temp/node_modules/.pnpm/graphql-ws<EMAIL_ADDRESS>and
"../common/temp/node_modules/.pnpm/graphql-ws<EMAIL_ADDRESS>(will be ignored)


Add in exponential backoff of API calls.

This adds in exponential back off for API calls (except for the curl call). Let me know if this approach makes sense. I also tried to make this as specific to the currently problem as opposed to making it easy to reuse in any use case. It would be easy to update if that is needed, but I like to keep things as simple as possible until they need to become more complex, let me know if you disagree on that.
I have run through specific scripts that were failing often in addition to running the demo pipeline and both seem to be handling failures better. For the esmfold API sometimes there are quite a few failures before the request succeeds so looking into moving away from the API would be good to both speed up that part as well as make it more reliable, but this does help quite a bit from my test runs.

Ok updated the PR with your feedback @mezarque, thanks for the review and detailed explanations it was really helpful. I'll merge in as soon as my last demo run finishes and looks good.


Add support for choice in group entries

As per move_instantaneous_reward = [ 0 / 1, { * stake_credential => coin } ]

Addressed in #16


Document missing character behavior when drawing text with fonts

Note that there's a proposal about changing this behavior (which I think is better), but I don't know how difficult it is to implement.
See #40405.

Thanks!

Cherry-picked for 3.2.3.


add test function can filter more stream

Signed-off-by: yk3372<EMAIL_ADDRESS>

Interesting idea. But I think this is something very specific. If you really need this I'd advise you to just copy the event_bus.dart file and use that in your code.


Incorrect 'missing' count

A report i generate from a csv gives some columns has having large numbers of missing values and a very small number of zeroes. In fact, in generating this data i use fillna(0) to get rid of the missing data, so i suspect there is an issue with it interpreting 0 as missing data. I tried using fillna(0.0) instead, no bueno.
Is there some heuristic at play here to determine if/when 0's are actually missing?
Thanks!
Z

Hi @Zylatis,
I've made a test that tries to reproduce the scenario you have described. With the basic setup below, the code works as expected, muy bueno. I'm curious in what way this synthetic dataset differs from your setup. Can you try to identify the key differences between both setups?
"""
Test for issue 213:
https://github.com/pandas-profiling/pandas-profiling/issues/213
"""
import pandas as pd
import pandas_profiling
import numpy as np

def test_issue213():
    b = np.ones((1000000))
    b[10:-10] = np.nan
    df = pd.DataFrame(b, columns=['vals'])

    df.profile_report().to_file('test_missing.html')

    df.fillna(0, inplace=True)

    df.profile_report().to_file('test_filled.html')

Hi @sbrugman, Is the above bug like "pandas profiling treats 0 as missing values".  If so please let me know.

Hi @sbrugman, Is the above bug like "pandas profiling treats 0 as missing values". If so please let me know.

I am not sure what you are referring to. If you mean if the issue is related to [#215], then this is not the case, as the formatting issue does not affect these extreme ratios.

So I must apologise, when i re-run it now i no longer get this issue. Sorry for wasting time. The only thing i can think of is i ran it on the wrong file and didn't realise it. At first I thought it might be because i was running from a few folders away and that might be a bug but that seems fine too.
Thanks for speedy responses!


instance.pp fails to remove scripts directory

I have a wrapper that wraps this elasticsearch puppet module. My module then calls the classes, functions of this module. Facing an issue where I am calling elasticsearch::instance, getting the following error
Elasticsearch::Instance[centos-64-x64]/File[/etc/elasticsearch/centos-64-x64/scripts]: Not removing directory; use 'force' to override
Error: Could not remove existing file

looking at the code and looking up what that error means and documentation around the type involved, I think we should be adding the attribute force => true to it to get around the issue.
What do you guys think?
Thanks!

It sounds like your wrapper may be creating the scripts directory for some reason outside the scope of this module. elasticsearch::instance then sees the directory already there and doesn't remove it.
I'd prefer to avoid adding force to the file { ensure => link } resource in elasticsearch::instance since there's the potential for data loss here if someone is storing scripts in the directory for some reason and puppet decides to do a rm -rf on the directory without showing a warning like this.
Since you're already using a wrapper around the module, would prefacing the manual call to elasticsearch::instance with a file resource work for you? Something like
file { "${elasticsearch::configdir}/centos-64-x64/scripts" :
  ensure => absent,
  force => true,
} -> elasticsearch::instance { 'centos-64-x64' :
  ...
}

Maybe?
If that doesn't work I'm open to something like a PR that exposes a force parameter on the elasticsearch::instance type if you'd prefer that.

I'd prefer to avoid adding force to the file { ensure => link } resource in elasticsearch::instance since there's the potential for data loss here if someone is storing scripts in the directory for some reason and puppet decides to do a rm -rf on the directory without showing a warning like this

This makes sense, actually. I'm going to try to find the root cause for this and try your suggestion of prefacing the call with force => true
Thanks!

Ok, I've tried some ways around with no success. Here is the order of execution for my module
Install ES -> Install plugins from RPM(it is directly a package install, so just extract the rpm and put it in plugins directory of elasticsearch) -> Configure instance(by calling instance.pp) which triggers the service restart.
Prefacing the call with file resource with force => true gives me error like, "Hey you have already defined the same file resource on instance.pp 284, the code I was referring about."

How about using a resource collector on that specific resource to add the force => true?
Something like...
File <| title == '/etc/elasticsearch/centos-64-x64/scripts' |> {
	force => true
}

I haven't tested that though so it's syntax might be wrong. But something along those lines.

In fact, a resource reference would probably work too. See https://docs.puppet.com/puppet/latest/reference/lang_resources_advanced.html#amending-attributes-with-a-resource-reference


Update documentation

Proposed changes
This PR updates documentation.
Types of changes
What types of changes does your code introduce to the project: Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] Update only documentation, not any source code.

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.

[X] I have read the CONTRIBUTING doc
[ ] I have signed the CLA
[X] I have updated the change log (CHANGELOG.md)
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
N/A

Codecov Report

Merging #157 (b4808c3) into v0.11.0-next (bcadf63) will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           v0.11.0-next      #157   +/-   ##
==============================================
  Coverage        100.00%   100.00%
==============================================
  Files                 2         2
  Lines              1650      1650
==============================================
  Hits               1650      1650

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 bcadf63...b4808c3. Read the comment docs.


A problem of calculating jacobian in inference

Hi, thanks for the excellent work.
When I tried to validate or test the trained model, an error occurred:
[*************************************]
diff_operators.py", line 74, in jacobian
jac[:, :, i, :] = grad(y_flat, x, torch.ones_like(y_flat), retain_graph=True, create_graph=False)[0]
return Variable._execution_engine.run_backward(
RuntimeError: element 0 of tensors does not require grad and does not have a grad_fn

More detailed information:
return self.model.validation_step(*args, **kwargs)
model_outputs = self.model(inputs, gen_cano_mesh=False, eval=True)
model_outputs = self.idhr_network(inputs)
calls /im2mesh/metaavatar_render/renderer/implicit_differentiable_renderer.py", line 89, in forward
= self.ray_tracer(sdf_network,
/im2mesh/metaavatar_render/renderer/ray_tracing.py", line 110, in forward
self.sphere_tracing(batch_size,
/im2mesh/metaavatar_render/renderer/ray_tracing.py", line 247, in sphere_tracing
search_iso_surface_depth(cam_locs,
/im2mesh/utils/root_finding_utils.py", line 424, in search_iso_surface_depth
J_lbs = forward_skinning_jac(valid_x_hat_0, loc, sc_factor, coord_min, coord_max, center, skinning_model, vol_feat, bone_transforms, mask=None)
File "/mnt/lustre/thu/project/human/nb/codelib/arah/im2mesh/utils/root_finding_utils.py", line 216, in forward_skinning_jac
jac, status = diff_operators.jacobian(pi_bar,
Any suggestions?

Solved. Because of this:
https://github.com/Lightning-AI/lightning/issues/13948


New version: EdrawSoft.EdrawMind version <IP_ADDRESS>3 (11.1.8)

Created by 🥟 Dumplings in workflow run #6480.

Log
Updated: 11.1.6 → 11.1.8
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

https://github.com/microsoft/winget-pkgs/issues/142854


wireguard MTU cannot exceed 1420

https://github.com/openwrt/luci/blob/b8ff46c6d6f403b5881f812d91611b6b5b2167ed/protocols/luci-proto-wireguard/htdocs/luci-static/resources/protocol/wireguard.js#L77-L79
ethernet_mtu = 1500
sizeof_ip4_hdr = 20
sizeof_udp_hdr = 8
wireguard_overhead = 32
ip4_wireguard_mtu = ethernet_mtu - sizeof_ip4_hdr - sizeof_udp_hdr - wireguard_overhead = 1440

Per my understanding, a MTU of 1440 should be acceptable.

I have tested MTU 1440 with ping -s 1398 (inetutils-ping). IPv4 header + payload inside wireguard tunnel = 1426 bytes.

I have tested MTU 1440 in my setup. This MTU value maximize link utilization.

1440 should be fine for ipv4 only traffic.
I think it's also worth noting that mtu of wireguard interfaces should be multiples of 16 as the protocol will pad payload up to for crypto operation.  This is especially the case if endpoint mtus do not match and both set their wg mtu values to the extremes (subtract out 60 without rounding down).

I think it's also worth noting that mtu of wireguard interfaces should be multiples of 16 as the protocol will pad payload up to for crypto operation. This is especially the case if endpoint mtus do not match and both set their wg mtu values to the extremes (subtract out 60 without rounding down).

@yousong I found your message at https://lists.zx2c4.com/pipermail/wireguard/2019-July/004289.html.

Although Wireguard protocol doc  states

encapsulated_packet = encapsulated_packet || zero padding in order to make the length a multiple of 16

The implementation does take care of MTU
static unsigned int calculate_skb_padding(struct sk_buff *skb)
{
	unsigned int padded_size, last_unit = skb->len;
	...
	padded_size = min(PACKET_CB(skb)->mtu,
			  ALIGN(last_unit, MESSAGE_PADDING_MULTIPLE));
	return padded_size - last_unit;
}

I set up a peer-to-peer test environment, wireguard over IPv6 over Ethernet is capable of transmitting MTU=1420 (1500-40-8-32) without fragmentation, even though 1420 is not a multiple of 16.

Fixed with commit https://github.com/openwrt/luci/commit/ddd04a719f3adf4c59d6ab153de0c26eb9495a93


BUG: pjit results in incorrect/incompatible shapes with distributed setup

Description
Note: I can only reproduce this when I'm using more than 1 machine (namely, the v3-256 cloud TPU VM I'm getting to play with)
I was trying to implement ZeRO-3 (along the lines hinted in https://github.com/google-research/t5x/blob/main/docs/usage/partitioning.md#data-parallel-with-parameter-gather) , when I ran into a bug/limitation in pjit.
When using pjit, if I try to elementwise-multiply two arrays together that have "conflicting" PartitionSpecs I get a shape error that I don't get when not using pjit. (They conflict in that one is sharded along the first axis and the other along the second using the same axis of the mesh)
import jax
import jax.numpy as jnp
from jax.experimental.pjit import pjit
from jax.interpreters.pxla import Mesh, PartitionSpec
import numpy as np

devices = jax.devices()
mesh = Mesh(np.array(devices).reshape((-1, 4)), ["data", "model"])

with mesh:
    spec = PartitionSpec("data")
    array = jnp.zeros(512, dtype=jnp.bfloat16)

    def foo(weight, data):
        return weight.reshape(1, -1) * data

    # ok
    out1 = foo(array, jnp.zeros((256, 512)))
    print(out1.shape)

    # error
    pjit_foo_novmap = pjit(foo, in_axis_resources=(spec, PartitionSpec("data", None)), out_axis_resources=PartitionSpec("data", None))
    out = pjit_foo_novmap(array, jnp.zeros((256, 512)))

The error is TypeError: mul got incompatible shapes for broadcasting: (1, 16384), (8192, 512).
Using with_sharding_constraint to force weight to be replicated doesn't fix it. i.e. I still get the same error if I do:
 def foo(weight, data):
        return with_sharding_constraint(weight, PartitionSpec(None)).reshape(1, -1) * data

16384 is 32 * 512 and 8192 is 32 * 256, and 32 is the number of worker VMs
What jax/jaxlib version are you using?
jax 0.3.16 (main from a week ago or so)/ jaxlib 0.3.14
Which accelerator(s) are you using?
TPU (must be more than one VM)
Additional System Info
Cloud TPU VM v3-256, Python 3.10.5,

It seems to work for me locally with 4 devices:
In [2]: import jax
   ...: import jax.numpy as jnp
   ...: from jax.experimental.pjit import pjit
   ...: from jax.interpreters.pxla import Mesh, PartitionSpec
   ...: import numpy as np
   ...:
   ...: devices = jax.devices()
   ...: mesh = Mesh(np.array(devices).reshape((-1, 4)), ["data", "model"])
   ...:
   ...: with mesh:
   ...:     spec = PartitionSpec("data")
   ...:     array = jnp.zeros(512, dtype=jnp.bfloat16)
   ...:
   ...:     def foo(weight, data):
   ...:         return weight.reshape(1, -1) * data
   ...:
   ...:     # ok
   ...:     out1 = foo(array, jnp.zeros((256, 512)))
   ...:     print(out1.shape)
   ...:
   ...:     # error
   ...:     pjit_foo_novmap = pjit(foo, in_axis_resources=(spec, PartitionSpec("data", None)), out_axis_resources=PartitionSpec("data", None))
   ...:     out = pjit_foo_novmap(array, jnp.zeros((256, 512)))
   ...:     print(out.shape)
   ...:
(256, 512)
(256, 512)

In [6]: jaxlib.__version__
Out[6]: '0.3.15'

In [7]: jax.__version__
Out[7]: '0.3.16'

It has to be more than one node, not just multiple devices
On Mon, Aug 22, 2022, 7:50 AM Yash Katariya @.***>
wrote:

It seems to work for me locally with 4 devices:
In [2]: import jax
...: import jax.numpy as jnp
...: from jax.experimental.pjit import pjit
...: from jax.interpreters.pxla import Mesh, PartitionSpec
...: import numpy as np
...:
...: devices = jax.devices()
...: mesh = Mesh(np.array(devices).reshape((-1, 4)), ["data", "model"])
...:
...: with mesh:
...:     spec = PartitionSpec("data")
...:     array = jnp.zeros(512, dtype=jnp.bfloat16)
...:
...:     def foo(weight, data):
...:         return weight.reshape(1, -1) * data
...:
...:     # ok
...:     out1 = foo(array, jnp.zeros((256, 512)))
...:     print(out1.shape)
...:
...:     # error
...:     pjit_foo_novmap = pjit(foo, in_axis_resources=(spec, PartitionSpec("data", None)), out_axis_resources=PartitionSpec("data", None))
...:     out = pjit_foo_novmap(array, jnp.zeros((256, 512)))
...:     print(out.shape)
...:
(256, 512)
(256, 512)
In [6]: jaxlib.version
Out[6]: '0.3.15'
In [7]: jax.version
Out[7]: '0.3.16'
—
Reply to this email directly, view it on GitHub
https://github.com/google/jax/issues/12024#issuecomment-1222469811, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAACLIOQ2TL6ZFS6RU76DF3V2OHTBANCNFSM57CJMPWQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Got it! I'll try to reproduce on 4 processes and see if I can hit this error. If I still don't hit that then I can try on 256 devices.

I am hitting this on 4 processes too.

I think the problem is that arr and the data value is host-local and pjit internally converts it to a global value which is where the mismatch is coming from.
Since you are using pjit (without GDA) on multiple processes, you need to pass host-local shaped inputs to pjit. Can you try doing that and see if it works?

ah, right ok. Switching to pjit initialization of the arrays fixed it. Thank you!
I've been bitten by this before with xmap but didn't realize I was doing it again!
I keep assuming that if I pass in arrays created identically on different nodes they get treated as though they were equal/replicated, and not concatenated.
I seem to have missed the note in the pjit docs!
Sorry about that.

Gotcha. That sounds great!


Publish html version of users guide and leverage github pages

Is your feature request related to a problem? Please describe.
The current deploy of the documentation is a pdf that while useful, could be better implemented as a webpage which doxygen already generates.
Describe the solution you'd like
Leverage github pages to host a "live" version of the users guide.
Describe alternatives you've considered
figure out how to get doxygen to generate markdown instead of html and use Jekyll or another static site generator
Requester Info
Gerardo E. Cruz-Ortiz, NASA-GSFC

Just a note that my experience in using the HTML was dreadful.  You can't search, it's 100's (or 1000's) of random files... I hated that version and would prefer to not even make it to begin with.  The PDF in my experience is WAY more useful... with an index, etc.

Just a note that my experience in using the HTML was dreadful. You can't search, it's 100's (or 1000's) of random files... I hated that version and would prefer to not even make it to begin with. The PDF in my experience is WAY more useful... with an index, etc.

Maybe have both? That's sad that the html is bad. I was hoping it would be like https://pmarsceill.github.io/just-the-docs/

Feel free if you find it useful.  I didn't, it's terrible.  The PDF looks way better.

Can we close this, with the PDF's being sufficient?

I don't think they are. What's the harm in leaving it open?

No harm, just wanted to make sure it was still an active enhancement request.


feat: make it easier to get started

This is a really cool project. I had some challenges getting it running and made a could of changes:

add config.example.com
update readme with quickstart
fix spelling of address and rename to hostname
warn about webhook not configured and prevent error logs

The most controversial would be changing adress to hostname instead of correcting address. The main concern here is that the all the parts make the address and as documented in the URL parser Hostname is either the domain or IP address part of the URL. Additionally, the example config does not set it so the app isn't bound to a specific domain which will make it easier in some deployment scenarios.

Heya, amazing to hear someone else has use for this project.
Thanks for the contributions


Work around hubot-help's kinks

hubot-help simply replaces any occurrence of 'hubot' with either bot's alias or name. This results in rather strange looking lines like ! ! branch on {{hosts}} - Show the currently deployed ! branch. By very least, it breaks an immersion and makes our bot looks worse than it is.

With hubot deployed inside docker containers, this pack as a whole makes very little sense, but still, this seems like a problem worth fixing.

LGTM

Yeah, that's what I was going to ask: isn't this pack going to be deprecated anyway?

May be at some point in time when we ensure there's no more standalone hubot deployments left in a wild. On the other hand, we may want to rewrite it to work with docker... if there's actually enough value it it.

:+1:
Make the experience consistent. We can re-eval long-term.

We merged a fix into hubot-help instead, closing.


ordeby can not work

DB::connection('mongodb')->collection('baike_recommend') ->orderBy('update_time','desc')->toSql();
BaiKeRecommend::orderBy('update_time','desc')->toSql();
explans sql
select * from "baike_recommend" order by ""；
but order by cant not works,please give a solution，tank you。

@BlueAmbition You can do BaiKeRecommend::latest()

@HassanIbrahim If i want order by other filed?

@BlueAmbition BaiKeRecommend::orderBy('db_field', 'desc')->get();

i confirm it's not working in any ways

latest/orderby doesnt matter


RFP - CorsixTH

Checklist

[X] The package I am requesting does not already exist on https://chocolatey.org/packages;
[X] There is no open issue for this package;
[X] The issue title starts 'RFP - ';
[X] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL : https://github.com/CorsixTH/CorsixTH
Direct download URL for the software / installer : https://github.com/CorsixTH/CorsixTH/releases
Software summary / short description: A reimplementation of the 1997 Bullfrog business sim Theme Hospital. As well as faithfully recreating the original, CorsixTH adds support for modern operating systems (Windows, macOS, Linux and BSD), high resolutions and much more.

Status: In progress

corsixth.install is under review : https://chocolatey.org/packages/corsixth.install
corsixth.portable and corsixth (meta/virtual package) coming soon.

Status: Published

https://chocolatey.org/packages/corsixth
https://chocolatey.org/packages/corsixth.install
https://chocolatey.org/packages/corsixth.portable

Can be closed.


TypeError: RedisProtocol.delete received 'str'

I got below error when using RedisSessionInterface, this pr only fixes for async_redis library, not try for others, such as hiredis, etc., you can find a better way to fix this kind of error:
TypeError: RedisProtocol.delete received 'str', expected (<class 'list'>, <class 'generator'>)

And, async_redis.delete accepts a list as parameter.
http://asyncio-redis.readthedocs.io/en/latest/pages/reference.html#asyncio_redis.RedisProtocol.delete

duplicate


Add screenshots

Add screenshots in README.md file.
Screenshots are already there in the repo, you just have to include them in the README file by keeping the heading Screenshots.
Name of files :-

ss1.png
ss2.png

I would love to work on this issue as a part of Cross Woc. Kindly Assign me

I would love to work on this issue as a part of Cross Woc. Kindly Assign me

Bro, I have already assigned you two issues already. I think we should give chance to anyone else. If no one asks for assigning this, I will assign it to you? Is it ok for you?

I would love to work on this issue as a part of Cross Woc. Kindly Assign me

Bro, I have already assigned you two issues already. I think we should give chance to anyone else. If no one asks for assigning this, I will assign it to you? Is it ok for you?

Ok Bro

I would like to work on this Issue as a part of CWOC.
Kindly assign me this issue.
                THANK YOU

NK YOU

Yeah, sure. Are 2-3 days fine for completing it?

Yes

Thank you @tharunc
PR > #23


initialise with zeros, not empty

fixes https://github.com/pymatting/pymatting/issues/75

Thank you!

No problem! Any chance of a bug fix release for this?

Sure! Perhaps this evening.


Single (notion) Page that lists all our design docs

Thanks @wdbaruni ! notion://www.notion.so/pl-strflt/Design-Docs-b25744a00a01437bb4b963cb20d5fde6


simplified outputs by concatenating label-hipp/dentate

This is just an idea, and I'd like to hear feedback @akhanf @royhaast @myousif9 @Bradley-Karat
I was thinking it might be nice to concatenate label-hipp and dentate output files (they would still have no topological connectivity, but it may help simplify future work).
Basically, we'd keep work/ as is, but concatenate where appropriate when moving to hippunfold/. In cases where we don't have dentate data, we'd simply concatenate the appropriate number of NaNs (eg. for inner/outer.surf.gii, or for thickness.shape.gii).
Pros:

make it easier to do things like sample separate images (fMRI, T1/T2w, DWI, etc) using a singe call to wb_command -volume-to-surface-mapping
help simplify the plotting functions and examples i'm working on in https://github.com/jordandekraker/hippunfold_toolbox.
reduce the clutter in hippunfold/sub-{subject}/surf a bit
when loaded into a viewer, you don't need to specify as many files. Most programs will simply not render NaNs which i think is the desired behaviour here

Cons:

restructures output files, so we'd need another (minor?) release
doesn't drive home the fact that DG is anatomically topologically distinct as hard (though it would still be distinct)
less control (eg. if you want to use only one of the two hipp or dentate, you'd have to remove or mask out the other)

Thoughts?

I do see that there could be some value to having a surface file with the multiple hipp components combined (maybe also L+R?). However I am not sure combining their geometries in the same gifti is the best approach, since it limits what can be done with them as you suggest.
The enhancements to the CIFTI format that we discussed at a high-level with David and Matt to do in the near future could resolve the issues you bring up. E.g. right now, using CIFTI is the solution to putting L+R cortex surfaces together. The new additions to the CIFTI format (to add hipp and dg) would then allow cortex+hipp+dg (optionally even L+R) to be combined in the same CIFTI file, and then wb_command cifti_* operations would work on the combined surfaces (and would be a single file for easier viewing etc)..
Since that is on the horizon, I don't think it makes sense to diverge from that significantly (since the cifti solution would not involve concatenating geometry directly in giftis)..
That said, as a short-term workaround if you want to try it out, you could add some rules to concatenate the surfaces in the way you suggest, and also a target rule to generate them all. This would add the functionality, but would not be run by default. In general I think this is a good way to add anything more experimental.


add web3.career

The website rating from is from Similar Web, since Alexa rank is not available anymore.

Is this jobs? This page is for freelance

Hey @andychase
It has variety of different job types including freelancing. Here are some example:

Okay.. well I think it looks mostly jobs focused, check out this page for possibly a good place: https://github.com/lukasz-madon/awesome-remote-job#job-boards


Make sync explicit

@ewandennis
I'm switching out the .Wait() call here with a setting to go to Sync mode.
I'm doing this because there are areas, where for reasons I don't want to think about, the .Wait() call will hang.  Like a MVC action.  I've fielded multiple questions on this, which is why I stopped suggesting people use Wait() or "figure it out."  This mode will perform the "wait" in a way that will not cause a hang in a MVC action.

@ewandennis  I also stuck out a response variable, just to show people that the call does, indeed, return a response.  And if the email could not be sent, the reason will be in that response.
Thank you for putting in the work to make these examples, though.  I've noticed fewer people coming to me with questions, so... that's good!


enh: handle C crash signal

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

Comparison is base (4487329) 70.72% compared to head (d931cc4) 70.75%.

Additional details and impacted files
@@            Coverage Diff             @@
##              3.1     #257      +/-   ##
==========================================
+ Coverage   70.72%   70.75%   +0.03%
==========================================
  Files          78       78
  Lines        8187     8187
==========================================
+ Hits         5790     5793       +3
+ Misses       1829     1827       -2
+ Partials      568      567       -1

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


Add docs on how to set up whole turms system (include Security,VPS,DNS,DB,Turms etc) in cloud by clicking

Prerequisites: #765

Done. https://github.com/turms-im/turms/commit/1a59ce45a0e6f89555fb34af63f84bf6be955def


Redirect page not refreshing

Description
If you are on the redirect page and try to enter another forbidden page, the page is not reloaded and the timer gets stuck
To Reproduce
Steps to reproduce the behavior:

Login
Navigate to page you do not have access to
Directly try to access another page you do not have access to
See error

Expected behavior
The redirect page should refresh.
Desktop (please complete the following information):

OS: Windows
Browser Firefox
Version v0.4.3

This bug can not occur any more. With the introduction of the navigation bar in v0.5.0 and the re-login modal, it is prevented, that a user can navigate from the redirect page directly to another page, he has no permission for. If he tried this via the URL, the redirect page component will be refreshed anyways.


Missing telemetry on some flow commands

While working on PR's #4579 and #4580 I noticed that some commands were missing telemetry options. These should be added / resolved by this PR.

Great catch! We'll try to review it ASAP!


[FEAT] Ability to specify an additional parameter for tsswitch --event-udp

Is your feature request related to a problem?
Ability to specify an additional parameter for tsswitch --event-udp
Proposed solution:
like this:
tsswitch --event-udp address:port[:"message"]
or
tsswitch --event-udp address:port "message"
or
tsswitch --event-message "message" --event-udp address:port
in the latter version, the message can be used for --event-command too
Alternatives:
Additional information:
This is to work around the problem https://github.com/tsduck/tsduck/issues/895
Because in the case of --event-udp it doesn't spawn zombies

Ability to specify an additional parameter for tsswitch --event-udp

Could be done but the UDP message essentially contains a technical description of the event in JSON format.

tsswitch --event-message "message" --event-udp address:port
in the latter version, the message can be used for --event-command too

The --event-command options specifies a command. If you need to pass a fixed message to that command, it shall be part of the specified command.

This is to work around the problem #895
Because in the case of --event-udp it doesn't spawn zombies

As indicated in #895, this problem has already been fixed. You use an outdated version.

Ability to specify an additional parameter for tsswitch --event-udp

Could be done but the UDP message essentially contains a technical description of the event in JSON format.
Let's say we have a description like this:
{  "command": "tsswitch",  "event": "newinput",  "new-input": 1,  "origin": "tsduck",  "previous-input": 0,  "timestamp": "2021/03/13 19:33:47.688" }
If we have some kind of monitoring system on the port indicated by --event-udp, how will it understand from this message which channel we are talking about?
By this description, you can identify where the alert came from:
{  "message": "channel_disney",  "command": "tsswitch",  "event": "newinput",  "new-input": 1,  "origin": "tsduck",  "previous-input": 0,  "timestamp": "2021/03/13 19:33:47.688" }

tsswitch --event-message "message" --event-udp address:port
in the latter version, the message can be used for --event-command too

The --event-command options specifies a command. If you need to pass a fixed message to that command, it shall be part of the specified command.

Actually, I did just that, but if you add the --event-message option, you can also add this message to the beginning of the service message.
But this is just a suggestion for convenience.

I have added a parameter named --event-user-data which does this, passed in event command and UDP JSON structure. Please RTFM for the details. You have to rebuild from the latest state of the repo or, if you use Ubuntu 20 as indicated in #895, you may wait until tomorrow and get the latest nightly builds here (version 3.29-2631 or higher).

Automatically closed after 305 days without update and "close pending" label set.


⚠ Bofrost.de has degraded performance

In ab616da, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1092 ms

Resolved: Bofrost.de performance has improved in 77fa874 after 6 minutes.


Adds description table for webhook payload object of workflow_dispatch webhook event

Why:
Closes #14641

What's being changed:

This article
I have added a description table for workflow_dispatch event's payload object.
Check off the following:

[X] I have reviewed my changes in staging.
[X] For content changes, I have completed the self-review checklist.

@thispsj
Thanks so much for opening a PR! I'll get this triaged for review :zap:

@skedwards88 can you enable auto merge ?


Add filter to remove unwanted fields from logs

SDA enriches logs with metadata fields to Docker Swarm and kubernetes logs such as swarm_node, swarm_task_id, swarm_service, Kubernetes namespace, pod name, UUID  etc.
It should be possible to remove unwanted fields from log output to save storage:
-e REMOVE_LOG_FIELDS: logSource, swarm_node, swarm_task_id, image_name, container_name
An alternative would be dedicated switches to enable/disable log enrichment:
- e ENABLE_SWARM_ENRICHEMENT=true, -e ENABLE_K8S_ENRICHMENT

The feature is ready in sematext/sematext-agent-docker:1.31.53 image.
We will release 1.31.53 as latest image today.
Sematext Docker Agent uses logsene-js environment variable LOGSENE_REMOVE_FIELDS.
e.g.
docker run -v /var/run/docker.sock:/var/run/docker.sock \
-e LOGSENE_TOKEN=YOUR_LOGS_TOKEN \
-e LOGSENE_REMOVE_FIELDS="host,ip,logSource,container_host_name,creditCardNumber, password"
sematext/sematext-agent-docker:dev"

Logs shipped to Sematext Cloud should not contain the fields listed in LOGSENE_REMOVE_FIELDS.
Beside the reduced log volume it is a good feature to remove sensitive data fields from logs :)


getkin version has renamed openapi3.Swagger to openapi3.T

On install, there is an error:

PS D:\APOD\apod-backend-api> go get github.com/iasthc/hsuan-fuzz/pkg/rest-api
go: downloading github.com/iasthc/hsuan-fuzz v1.0.2
go: downloading github.com/valyala/fastjson v1.6.3
go: downloading github.com/getkin/kin-openapi v0.68.0
go: downloading github.com/ghodss/yaml v1.0.0
github.com/iasthc/hsuan-fuzz/pkg/rest-api
\go1.18beta2\pkg\mod\github.com\iasthc\hsuan-fuzz@v1.0.2\pkg\rest-api\hsuanfuzz.go:94:15: undefined: openapi3.Swagger
\go1.18beta2\pkg\mod\github.com\iasthc\hsuan-fuzz@v1.0.2\pkg\rest-api\hsuanfuzz.go:94:15: undefined: openapi3.Swagger

This indicates that the version of getkin is not fixed as a prerequisite, and this package has not kept up with its upstream changes.
https://github.com/getkin/kin-openapi#v0610

Renamed openapi3.Swagger to openapi3.T.

@twocs Thanks for the feedback. I am unable to use my laptop for some personal reasons recently. It will be fixed asap.


Update vehicle_controller.cc

Speed should be corrected by steer.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add OsString from/to bytes helper functions

Related issue: https://github.com/rust-lang/miri/issues/989
r? @RalfJung

:umbrella: The latest upstream changes (presumably #1004) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably #1005) made this pull request unmergeable. Please resolve the merge conflicts.

@RalfJung I have no idea why getcwd broke. Apparently I didn't write enough bytes:
error[E0080]: Miri evaluation error: attempted to read undefined bytes
   --> /home/christian/.rustup/toolchains/miri/lib/rustlib/src/rust/src/libstd/ffi/c_str.rs:974:19
    |
974 |         let len = sys::strlen(ptr);
    |                   ^^^^^^^^^^^^^^^^ Miri evaluation error: attempted to read undefined bytes
    |

However the logic for writing is almost the same. The only difference is the new transformation from OsStr to &[u8] and the fact that I'm not pushing the null terminator before writing but writing it after writing the bytes. I suppose something is wrong with any of those but I'm not sure why

@christianpoveda please don't delete comments, rather mark then as resolved when you resolved them. I got a notification about getcwd breakage and that seems like useful information to keep in the history, even if you managed to fix it later.

@christianpoveda please don't delete comments, rather mark then as resolved when you resolved them. I got a notification about getcwd breakage and that seems like useful information to keep in the history, even if you managed to fix it later.

Just for the future us (and other minds doomed to suffer the same fate as us :P): The problem was that I was trying to write using Allocation:write_bytes and it was failing to write all the bytes causing an invalid memory access in other places. I changed to Allocation::get_bytes_mut and everything is working nice and dandy now.

:umbrella: The latest upstream changes (presumably #991) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably #1014) made this pull request unmergeable. Please resolve the merge conflicts.

Just add a FIXME for now.

Ok then we are good to go

Thanks for the endurance, this is great. :)
@bors r+

:pushpin: Commit de12cbcb32a53a06e1f73e7d9cdfa11e41d79ded has been approved by RalfJung

:hourglass: Testing commit de12cbcb32a53a06e1f73e7d9cdfa11e41d79ded with merge a05f2aa3ab6caddd2fde2a823bcee63a16b6dd6c...

OK now I can start with the other stuff :)

:sunny: Test successful - checks-travis, status-appveyor
Approved by: RalfJung
Pushing a05f2aa3ab6caddd2fde2a823bcee63a16b6dd6c to master...


Unable to import package

Hello, I am trying to follow the tutorial to set this up, however, I keep getting the "Error adding package: git@github.com:fsstudio-team/ZeroSimROSUnity.git"

I am running on Ubuntu 20.04. I tried a couple of versions of Unity 2020.3.18f1 and 2020.3.35f1 to see if that helped. Not sure if this is something that has happened to others and if there's any solution. Thanks.

Tryusing https instead of ssh: https://github.com/fsstudio-team/ZeroSimROSUnity.git
If https works, it is probably because you do not have ssh authentication setup for GitHub.

Hi, thanks for your reply.
The https also did not work:

I have tried to import other packages, and I don't have any issues.

@vbelkina  My apologies, it seems to have been an issue on our end.  Please try again.

It worked! Thank you for your help.

Hi, thanks for your reply!
The https also didn't work.
On Fri, Jun 10, 2022, 17:43 Micah Pearlman @.***> wrote:

Tryusing https instead of ssh:
https://github.com/fsstudio-team/ZeroSimROSUnity.git
If https works, it is probably because you do not have ssh authentication
setup for GitHub.
—
Reply to this email directly, view it on GitHub
https://github.com/fsstudio-team/ZeroSimROSUnity/issues/28#issuecomment-1152757962,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARHEIFGPQS2EBDLIZWEZSWDVOOZJRANCNFSM5YOY655A
.
You are receiving this because you authored the thread.Message ID:
@.***>


Resolved cases and broken links

Fixed cases for "Kubernetes" and "Minikube". Also substituted broken Minikube links for updated versions.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Check if device is connected

Hello,
please, is it possible to implement function to check whether bluetooth device is connected?
For example:
isConnected(deviceId: string) =>  Promise <boolean>
Thank you very much!

I think you can use the method getconnectedDevices like this:
const isConnected = await BleClient.getConnectedDevices([SOME_UUID_TO_FILTER_OR_GET_ALL])

I think you can use the method getconnectedDevices like this:
const isConnected = await BleClient.getConnectedDevices([SOME_UUID_TO_FILTER_OR_GET_ALL])

Thats exactly what I need. Thank you very much! I did not realise I can do it this way :)

You are welcome, Can you please close the issue?


Improve url sanitization by unescaping html entities.

This pull request:

Unescapes HTML from the input url before filtering the protocols to prevent XSS via HTML hex/decimal references using commons-text
Adds tests for potential XSS scenarios
Rearranged some code

Note that this was not necessary because rendering &#x6A&#x61 with HtmlRenderer would result in &#x6A&#x61 (& escaped), so no XSS there.


Not getting channels from an STB

Hello, I have been trying to connect to the STB servers but to no avail. First one gives me an error of "First certificate not found", the second server gives no errors but still no channels show up.
Thank you

I'm getting the same thing except it says "The media could not be loaded, either because the server or network failed or because the format is not supported."


Add Sonar App Labels to Postgresql With Post Processing in the Applier

When the feature is available. This will group the db with the app in the web console.
label
- app = sonar

Fixed


action page (nav) - glitches when I scroll to the top on mobile

if you scroll down so that the nav follows you along the page on mobile, and then scroll up quickly the nav glitches for a second and freezes at the top of the page with a blank white space open where it originally started:

This has been fixed by using position: sticky and the fixed-sticky polyfill.


Add PaperParcel

https://github.com/grandstaish/paperparcel
Boilerplate reduction library written specifically for working with Kotlin data classes on Android.

Thank you!


Error running freshly created ignite app on the web (error:0308010C:digital envelope routines::unsupported)

Describe the bug
Hi, I'm unable to run my freshly created ignite app on the web. I get the following terminal output for yarn:expo start followed by pressing w to run the app on the web:

node:internal/crypto/hash:71
this[kHandle] = new _Hash(algorithm, xofLen);
^

Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:71:19)
at Object.createHash (node:crypto:133:10)
at module.exports (/home/paul/Repos/testApp/node_modules/webpack/lib/util/createHash.js:135:53)
at NormalModule._initBuildHash (/home/paul/Repos/testApp/node_modules/webpack/lib/NormalModule.js:417:16)
at handleParseError (/home/paul/Repos/testApp/node_modules/webpack/lib/NormalModule.js:471:10)
at /home/paul/Repos/testApp/node_modules/webpack/lib/NormalModule.js:503:5
at /home/paul/Repos/testApp/node_modules/webpack/lib/NormalModule.js:358:12
at /home/paul/Repos/testApp/node_modules/loader-runner/lib/LoaderRunner.js:373:3
at iterateNormalLoaders (/home/paul/Repos/testApp/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
at Array. (/home/paul/Repos/testApp/node_modules/loader-runner/lib/LoaderRunner.js:205:4)
at Storage.finished (/home/paul/Repos/testApp/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:55:16)
at /home/paul/Repos/testApp/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:91:9
at /home/paul/Repos/testApp/node_modules/graceful-fs/graceful-fs.js:123:16
at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read_file_context:68:3) {
opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
library: 'digital envelope routines',
reason: 'unsupported',
code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v18.15.0
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Additional information:
I run into the same error when using npm. npm/yarn audit fix (--force) doesn't help.
The suggested solutions in this stackoverflow post (downgrading Node or enabling legacy OpenSSL provider) both seem to cause security issues.
Thanks in advance and all the best,
Paul
Ignite version
8.6.0
Additional info
Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y)
System
platform           linux
arch               x64
cpu                4 cores      Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
directory          testApp      /home/paul/Repos/testApp
JavaScript (and globally-installed packages)
node                     18.15.0                                   /home/paul/.nvm/versions/node/v18.15.0/bin/node
npm                      9.5.0                                     /home/paul/.nvm/versions/node/v18.15.0/bin/npm
corepack               0.15.3
npm                    9.5.0
tslint                 6.1.3
typescript-formatter   7.2.2
typescript             4.9.5
yarn                     1.22.19                                   /usr/bin/yarn
neovim                 4.10.1
tree-sitter-cli        0.20.7
pnpm                     8.1.0                                     /usr/bin/pnpm

expo                     47.0.13                                   managed
Ignite
ignite-cli         8.6.0        /home/paul/.npm/_npx/e31027f3785124a8/node_modules/.bin/ignite
ignite src         build        /home/paul/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build
Android
java               19.0.2       /usr/bin/java
android home       -            /opt/android-sdk
Tools
git                git version 2.39.2   /usr/bin/git

This can be resolved immediately by using Node 16. However, this is not a great long term path as Node 16 reaches EoL.
The issue is upstream in webpack, checkout some of the solutions in this issue on the Webpack repo: https://github.com/webpack/webpack/issues/14532

Node 18 should be fine (I'm on 18.11.0), I've heard of this error before but don't know why it doesn't always show up.
Does this unblock you at all?
export NODE_OPTIONS=--openssl-legacy-provider
yarn expo:start

Does this unblock you at all?
export NODE_OPTIONS=--openssl-legacy-provider
yarn expo:start

Yes, that's what I'm doing for now.

Having the same issue with node v18

@P451M do you want to see if this goes away with the latest that's awaiting review? https://github.com/infinitered/ignite/pull/2377

@P451M do you want to see if this goes away with the latest that's awaiting review? #2377

I was able to get web working with this PR

@P451M try this out using npx<EMAIL_ADDRESS>new


Show Upgradeable as "Managed" when catalog.cattle.io/hidden is true

This resolves an issue with Rancher displaying an upgrade option for Traefik managed by K3s in existing versions.
New versions of K3s (tested with v1.21.7-rc1-k3s1) will provide a value for fleet.cattle.io/bundle-id, causing Upgradeable to display Managed for kube-system traefik.
My concern about this solution is that making use of catalog.cattle.io/hidden might be a little overly aggressive in marking other installed apps as Managed, even when they are not. Perhaps, a better approach would be to check that the namespace is kube-system or something that we know is managed before attempting to hide the upgrade button.
#4442

@rak-phillip @brandond @cbron It looks like k3s added [ab]using the bundle-id annotation to the k3s charts, so why do we need to add looking at hidden?  I don't love forever abusing both of these to have a new meaning of "it's not really fleet but we want it to be treated as not-upgradable" vs adding a new descriptive annotation to explicitly disable upgrade.
There are other ways to handle the existing installs, like applying a new annotation to the apps you're worried about during the upgrade, or just ignoring the problem of existing ones and fixing it going forward.

@rak-phillip What did we decide with this? Do we still plan to merge this one, or is it no longer needed?

@nwmac We had discussed not merging this one, as relying on the hidden and bundle-id annotations are not the right approach for fixing this one. As I understand, we would need to come up with the right combo of annotations to solve the problem in the absence of a new annotation.
This problem is fixed by the backend team for newer versions of k3s, but I think there's still the issue of existing installs.. I think we were leaning toward ignoring the problem of existing installs, but it would be best to explicitly state that decision here.

@nwmac I think I'll just close this one, as the solution proposed here isn't the right one.. we can have another go at it if needed.


PowerToys Setup Failed

Microsoft PowerToys version
0.65.0-x64
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
Installer
Steps to reproduce
Tried to install PowerToys and got the following message:

My system configuration is:

The error logfile is here:
powertoys-bootstrapper-msi-0.65.0_20221211170732.log
✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

Looks like .net 7 installation failed.
https://download.visualstudio.microsoft.com/download/pr/5b2fbe00-507e-450e-8b52-43ab052aadf2/79d54c3a19ce3fce314f2367cf4e3b21/windowsdesktop-runtime-7.0.0-win-x64.exe
Can you please try installing it manually and then trying to install PowerToys again?
/needinfo

Thanks. Tried to install .net 7 and got the following message:

Log file is here:
Microsoft_Windows_Desktop_Runtime_-7.0.0(x64)_20221213171503.log

Based on that error, you're on an x86 OS it looks like, PowerToys only compiles to x64 and ARM64 processor architecture.

fyi, your processor does support x64, just looks like your OS is x86.  https://ark.intel.com/content/www/us/en/ark/products/52952/intel-core-i5-480m-processor-3m-cache-2-66-ghz.html

here is the other statement that confirms you are on an x86 OS.


zh: Update doc for aurora migration

What is changed, added or deleted? (Required)

improve aurora migration guide
Which DM version(s) do your changes apply to? (Required)

[x] master (the latest development version, including v3.0 changes)
[x] v2.0 (TiDB DM 2.0 versions)
[ ] v1.0 (TiDB DM 1.0 versions)

What is the related PR or file link(s)?

This PR is translated from:
Other reference link(s): internal GDoc

Do your changes match any of the following descriptions?

[ ] Delete files
[ ] Change aliases
[ ] Have version specific changes
[ ] Might cause conflicts after cherry-picked

may add guide to use ignore-checking-items if we can't assure we list all Aurora privileges

@handlerww PTAL?

DNM, need update

done. PTAL @TomShawn

LGTM

LGTM

@lance6716 It is not recommended to add internal Google Docs links in PR because only PingCAP members can access these links.


selenium.common.exception.WebDriverException: Message: invalid argument: can't kill an exited process

When I run the docker file, I receive this message:
selenium.common.exception.WebDriverException: Message: invalid argument: can't kill an exited process
Any idea to fix it?
Thanks.

When exactly does this Happen?

Hi! same here...
Running in DOCKER MODE
==> Skipping jitters since specified in config.json
==> Opening Webdriver
Traceback (most recent call last):
  File "eagle-eye.py", line 261, in <module>
    main(skipFB=args.skipfb, skipY=args.skipyandex, FBUrls=[], jsonRep=jsonRepFile, dockerMode=aDocker, dockerName=aName)
  File "eagle-eye.py", line 100, in main
    f.grabData()
  File "/EagleEye/grabber/facebook.py", line 16, in grabData
    driver = cfg.getWebDriver()
  File "/EagleEye/utils/config.py", line 43, in getWebDriver
    return webdriver.Firefox(profile)
  File "/usr/local/lib/python3.6/dist-packages/selenium/webdriver/firefox/webdriver.py", line 174, in __init__
    keep_alive=True)
  File "/usr/local/lib/python3.6/dist-packages/selenium/webdriver/remote/webdriver.py", line 157, in __init__
    self.start_session(capabilities, browser_profile)
  File "/usr/local/lib/python3.6/dist-packages/selenium/webdriver/remote/webdriver.py", line 252, in start_session
    response = self.execute(Command.NEW_SESSION, parameters)
  File "/usr/local/lib/python3.6/dist-packages/selenium/webdriver/remote/webdriver.py", line 321, in execute
    self.error_handler.check_response(response)
  File "/usr/local/lib/python3.6/dist-packages/selenium/webdriver/remote/errorhandler.py", line 242, in check_response
    raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.WebDriverException: Message: invalid argument: can't kill an exited process

I had also changed the GeckoDriver version from dockerfile but the error remains.

Are you using the Linux Subsystem in Windows? If so this isn't tested. PLease try using a Linux distro.

I use macOS

I'm using a Linux distro on Heroku. I'm using the following buildpacks:
http://github.com/buitron/geckodriver-buildpack
http://github.com/buitron/firefox-buildpack
I'm struggling with the same error.
I read on stackoverflow, that this error implies that the GeckoDriver was unable to initiate/spawn a new WebBrowsing Session i.e. Firefox Browser session. Not really sure why though.
I wanted to post a new issue, but I though it could be a possible duplicate, hence posting here.
Any thoughts?!

Hey @ronnielivingsince1994 ,
thank you for linking the other issue.
I have not tested this setup on Heroku and as far as i know the webdriver still needs a x-server to run.
So when using the dockerfile you need to run the docker container using the following arguments:
sudo docker run -t --net=host --env="DISPLAY" \
                           --volume="$HOME/.Xauthority:/root/.Xauthority:rw"  \

You need to set the DISPLAY env varibale for Xorg and mount your local .Xauthority so that the docker container can access the hosts x-server.
So your docker host still needs a xorg server and desktop environment to run the container.
Maybe you can install a desktop environment on heroku and a vnc-server and try it that way?
Hope i could help :)

I will add the x-server requirement to the README as i am in the process of redoing the formatting of the README.

Hi, I have the same problem, but in Ubuntu. Can you help me?

Have you used the docker container or how did you install? Try increasing the timeout in the config

I've the same error on Ubuntu with Docker. I checked several times docker arguments. All seems correct.

Try increasing the timeout in the config file (and run without docker once).

I have the same issue on Ubuntu 18.04. Both Docker and install directly.
Finally, I found that cause by the privilege, try to not run with "root".

I didnt run with root at any time. This might cause issues regarding the firefox profile i think.

Yes, it could be.


[SPARK-41799][CONNECT][PYTHON][TESTS] Combine plan-related tests into single file

What changes were proposed in this pull request?
Combine plan-related tests into single file
Why are the changes needed?
1, test_connect_column_expressions, test_connect_plan_only, test_connect_select_ops almost did the same thing: generate and then validate a plan;
2, the three tests are pretty small, and normally finished in 1 sec.
Starting test(python3.9): pyspark.sql.tests.connect.test_connect_column_expressions (temp output: /__w/spark/spark/python/target/8d15e343-028e-44de-b998-6a7e7cc98047/python3.9__pyspark.sql.tests.connect.test_connect_column_expressions__fkvdhn26.log)
Finished test(python3.9): pyspark.sql.tests.connect.test_connect_column_expressions (0s)
Starting test(python3.9): pyspark.sql.tests.connect.test_connect_function (temp output: /__w/spark/spark/python/target/b35958dc-4dd3-4420-8f44-cb6f66d568dc/python3.9__pyspark.sql.tests.connect.test_connect_function__te14hoiz.log)
Finished test(python3.9): pyspark.sql.tests.connect.test_connect_function (80s)
Starting test(python3.9): pyspark.sql.tests.connect.test_connect_plan_only (temp output: /__w/spark/spark/python/target/3225a48d-5b4c-4cbe-803d-680c9408e3a8/python3.9__pyspark.sql.tests.connect.test_connect_plan_only__4bjohyey.log)
Finished test(python3.9): pyspark.sql.tests.connect.test_connect_plan_only (0s)
Starting test(python3.9): pyspark.sql.tests.connect.test_connect_select_ops (temp output: /__w/spark/spark/python/target/fe6a37ff-9aa8-41d5-8204-44a86423381f/python3.9__pyspark.sql.tests.connect.test_connect_select_ops__cicvg0w7.log)
Finished test(python3.9): pyspark.sql.tests.connect.test_connect_select_ops (0s)

Does this PR introduce any user-facing change?
no, test-only
How was this patch tested?
CI

thank you @Yikun , merged into master


How to generate this setup.py for a namespace subpackage?

[x] I have searched the issues of this repo and believe that this is not a duplicate.
[x] I have searched the documentation and believe that my question is not covered.

Question

Hi!
I'm moving all my projects to Poetry and have issues with some of them. Namely, it's packages that are subpackages to a bigger project.
Here is one example: https://github.com/foliant-docs/foliantcontrib.bump. It's an extension for https://github.com/foliant-docs/foliant.
It means that during installation, the file foliant/cli/bump.py should be placed in foliant/cli folder in Foliant installation. To accomplish this, I'm using namespace package in setup.py.
I haven't found a way to achieve the same thing with Poetry. Tried using packages in pyproject.toml, but that gives me a package name cli, not foliant.cli.

I think this sounds related: https://github.com/sdispater/poetry/issues/167

Your pyproject.toml link leads to a 404. How did you use packages?
I've been able to use namespace packages in Poetry just fine, but my use case is slightly different. I don't have projects that share innermost (leaf) packages, so I'm not sure if this will work for you.
I have two projects, foo-project and bar-project:
foo-project
├── pyproject.toml
└── root_namespace
    └── nested_namespace
        └── subpackage_a
        │   └── __init__.py
        └── subpackage_b
            └── __init__.py

bar-project
├── pyproject.toml
└── root_namespace
    └── nested_namespace
        └── subpackage_c
            └── __init__.py

This is how I use packages in each pyproject.toml:
[tool.poetry]
...
packages = [{ include = "root_namespace" }]
...

This picks up root_namespace and the subpackages in the generated setup.py.
foo-project/setup.py:
packages = \
['root_namespace',
 'root_namespace.nested_namespace.subpackage_a',
 'root_namespace.nested_namespace.subpackage_b']

bar-project/setup.py:
packages = \
['root_namespace',
 'root_namespace.nested_namespace.subpackage_c']

Installing both places the files in the correct directories.

Sorry, I've updated the link.
Thanks for the code sample, I'll try to do something similar and report the result.

[{ include="foliant.cli" }]might be what you want. I think the from field is for specifying the parent directory of your package tree (e.g. src if the foliant directory is in src)

@RaptDept [{ include="foliant.cli" }] doesn't work because Poetry tries to look for foliant.cli folder, which is not there:
[ValueError]
C:\Users\moigagoo\Projects\foliantcontrib.bump\foliant.cli does not contain any element

[{ include="foliant" }] only adds foliant as a package. But if I put an empty __init__.py file in foliant/cli, both foliant and foliant.cli are detected. Even though I'd rather have only foliant.cli added to packages in setup.py and not add and empty __init__.py, it seems to work. Thanks!

It turns out, putting init.py is not a solution. It overwrites the init.py that's already there in the parent package during installation, which breaks stuff.

See my solution here: https://github.com/sdispater/poetry/issue_comments#issuecomment-411573655

@dfee it's 404 unfortunately.

@moigagoo Updated the link, glad you'd already found it.

@moigagoo I'm not understanding how your project doesn't follow the PEP420 guidelines. Is it because you don't have and __init__.py https://github.com/foliant-docs/foliantcontrib.bump/tree/develop/foliant/cli


Upload Malware

https://attack.mitre.org/techniques/T1608/001

This is out of scope for capa. Per the MITRE page:

Much of this activity will take place outside the visibility of the target organization, making detection of this behavior difficult.


Add a JSON proxy wrapper for proto-incapable indexers. [phab:D1443]

Created by fromberger at 2017-03-22 22:52:35:
Some languages have difficulty handling protocol buffers, or at least find it
much easier to work in JSON. To permit a driver to work with such languages,
this change adds a "proxy" library that converts the interaction into a simple
JSON protocol conducted over pipes.
This hasn't yet been integrated into the existing driver tool, but I'd like to
do that as a separate step. The typical mode of operation where we run the
indexer as a subprocess and pass work to it will continue to work in this new
regime, only the communication channel changes.

fromberger wrote at 2017-03-23 04:34:12:

Clarify the handling of errors writing output.

evmar commented inline (context lost during migration) at 2017-03-23 17:43:06:
I'm not clear on why you abandon in the other branch but don't abandon here.
Also, delete extra whitespace line.  :D

evmar commented inline (context lost during migration) at 2017-03-23 17:43:06:
The protocol used by VSCode has an explicit content-length "header" before each message.  It's from some "jsonrpc2" protocol, there are implementations in various languages.  Go's stdlib even has a jsonrpc protocol (that is apparently jsonrpc1 or something, there's a bug about updating it but I think they realize it was a mistake to include anything here).
The reason I mention all this is due to framing.  I think it's not easy on the JS side to say "parse a single JSON object from this stream and stop".  The JS JSON-parsing API expects a complete string, which means you need some sort of frame boundary.
It might be sufficient to just say the boundary is newlines though.  Maybe just call it out in this doc.  IIRC the Go JSON library inserts newlines after its encodes and skips whitespace in its decodes so you already implement this protocol.  So I think this overlong comment has made convince myself this will work and you should just say something about how requests must be sent as a single line terminated in \n.

evmar wrote at 2017-03-23 17:43:06:
I guess we'll need some other glue in the analyzer runner to use this?

evmar accepted this revision at 2017-03-23 17:43:06

zarko commented inline (context lost during migration) at 2017-03-23 17:51:09:
nit: trailing } missing

zarko commented inline (context lost during migration) at 2017-03-23 17:51:09:
In this state, the indexer should abandon the current analysis as soon as possible and start a new one.

zarko accepted this revision at 2017-03-23 17:51:09

fromberger commented inline (context lost during migration) at 2017-03-23 18:19:01:
I actually thought about making this JSON-RPC explicitly, and that's certainly an option if you prefer.
I'd also be happy to add a specific framing if you think that matters, though if explicit newlines are sufficient I'd be OK with documenting that too.

fromberger commented inline (context lost during migration) at 2017-03-23 18:19:01:
It's stronger than that: The indexer will get errors if it does anything else.

fromberger wrote at 2017-03-23 18:19:04:

Fix documentation typo.
Give up on both error branches of a failed 'output' request.

fromberger commented inline (context lost during migration) at 2017-03-23 18:22:26:
It doesn't look like [[ http://www.jsonrpc.org/specification | JSON-RPC 2.0 ]] has any explicit framing requirements; that might be a VSCode extension. I'm not worried about arbitrary clients, though; as long as a well-behaved indexer can buffer and read messages sensibly.

evmar commented inline (context lost during migration) at 2017-03-23 18:33:34:
I think jsonrpc2 is probably overkill, and I've convinced myself that the \n is sufficient, so I think I'd be happy with just documenting that a \n trailer is required on requests.

fromberger wrote at 2017-03-23 18:56:32:

Clarify the message framing rules.

fromberger commented inline (context lost during migration) at 2017-03-23 18:56:50:
Ok, sounds good. I updated the comments, PTAL.

fromberger wrote at 2017-03-23 19:02:58:

Fix another documentation typo.

evmar wrote at 2017-03-23 20:07:22:
LGTM++

fromberger closed via commit 21d5a40356e91a46534c1fa47f0fac3e7ba857d1 at 2017-03-23 20:44:58


Can delete row from table?

I want delete row from table.
Found a function that deletes the specified column of the column family, but did not find a function to delete the row from table.
Is there any way? please tell me.

Sorry, self solved.
I did not notice that we could change the value to nil.
delRequest, err := hrpc.NewDelStr(context.Background(), "table", rowKey, nil)


get_events on pending block is always empty

Describe the bug
When using get_events with to_block = Some(BlockId::Tag(BlockTag::Pending)), the event page is always empty.
Expected behavior
We should return the events of the pending block's transactions.
Screenshots

Additional context
The request enters here: https://github.com/dojoengine/dojo/blob/6b6219faf0a53b781b7fd83dabefc8e8f90b5995/crates/katana/rpc/rpc/src/starknet.rs#L453.
Then processed by the sequencer here:
https://github.com/dojoengine/dojo/blob/6b6219faf0a53b781b7fd83dabefc8e8f90b5995/crates/katana/core/src/sequencer.rs#L299
Also, in the new JSON RPC spec, the block number can be None for the events of the pending block.

How do we handle pagination in that case? iirc the cursor schema is up to us, so we would need to include a txn index in it. not sure how we handle this today

How do we handle pagination in that case? iirc the cursor schema is up to us, so we would need to include a txn index in it. not sure how we handle this today

I'm not sure how it works but I think it just uses the pending block number (latest block number + 1) alongside the event index?
Here's how it looks with the sepolia node.

How do we handle pagination in that case? iirc the cursor schema is up to us, so we would need to include a txn index in it. not sure how we handle this today

I'm not sure how it works but I think it just uses the pending block number (latest block number + 1) alongside the txn index + event index? Here's how it looks with the sepolia node.
As you can see, the events in the EventsPage have a None block_hash and block_number but the cursor still includes the block number.

Ok cool then I think supporting this should be pretty straight forward

To add on this, this seems to be the issue: https://github.com/dojoengine/dojo/blob/main/crates/katana/storage/provider/src/traits/block.rs#L40
The returned BlockId for the Pending block tag is none, which fallbacks to the latest block number here
https://github.com/dojoengine/dojo/blob/main/crates/katana/storage/provider/src/traits/block.rs#L32
What would be the implications of simply returning the latest_block_number + 1?

This is not a Katana bug, it's because the from_block must point to the pending, and the to_block must be None.

@Larkooo this may be interesting to check if with all the reworks + this change, this may stabilize more the Torii behavior?


v-if & event handler

Version
2.6.0-beta.1
Reproduction link
https://codepen.io/frlinw/pen/OreZMz
Steps to reproduce
Click on "Click me"
What is expected?
demo with v2.5.22 show the expected behavior: https://codepen.io/frlinw/pen/XoLYMR
the "Dropdown" component should not be able to handle a click event which is supposed to create it
What is actually happening?
the Dropdown is automatically closed because it handles the click event

Sorry for resurrecting this again, but there definitely is a case for such things:

You prevent a value change in DOM from event
You do some validation logic
You change the :checked or any other event driven DOM change

$nextTick, as said before no longer releases the DOM, thus if you do the change in the next microtask, DOM change will still be prevented
This is a case to provide the functionality of a previous implementation of a $nextTick, or at least be transparent about whether you run the microtask before of after the event finishes propagation
@yyx990803
I think the biggest showstopper case for that is how you handle media events https://developer.mozilla.org/en-US/docs/Web/Guide/Events/Media_events
That's a hornet's nest in terms of browser incompatibility and you some times need to do things like listen for stop event and then relaunch the audio as soon as the stop event finishes propagation to prevent the playback from interruption, or you need to prevent the seek event, and change the playback position, or prevent video muting/unmuting conditionally, without few millisecond 'pop.'
For cases like that, people have no alternative to something like that now, but the issue with few millisecond delay is still there.
event.preventDefault()
await new Promise(resolve => setTimeout(resolve,1))
this.checkIfYouActuallyNeedToStopPlaybackOnTheNextBrowserTick()

If such option will be introduced, just warn people in big red letters that safari has issues with it beforehand.


Support the sending of an Invitation via a Basic Message

Is your feature request related to a problem? Please describe.
Sort of...the problem is that sending a basic message doesn't seem to work for long messages.
Describe the solution you'd like
To support the demo we are planning at the Vancouver Indy Bootcamp, we'd like to be able to send an invitation via the Basic Message protocol.  We'll send you the details of the bootcamp we're preparing (as soon as it is ready).  In one of the steps, a user on an instance of the StreetCred agent generates an invitation and sends it to a connected agent via the Basic Message interface.  On the StreetCred agent, the message is not sent and is a bit of a mess on the screen.
Please try this scenario and ensure the message gets sent and the screen looks OK.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Here is an example of what is displayed when sending an invitation as a basic message.  The message was not actually sent, but does display (badly) on the screen.

@tmarkovski have we resolved this one?

Yup. Can be closed.


Add missing hypens in abbreviation name

@DenisBalan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@BrianBlanchard
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"

Not all of these resource types support hyphens.  Each suggestion needs to be validated.  For instance, "Microsoft.ContainerRegistry/registries" only supports alphanumeric characters and should not have a hyphen.

These changes are now reflected in the live article. I'll close this PR now. Thanks.


pull request for e2e test at 01/09/2017 04:45:12

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


Images src appends extra paths after couple transition cycles

Hi this issue has freaking me out a little bit because I'm at my wits end in terms of solving this problem.
What happens is, on some slower connections or throttled connections sometimes my images dont load whatsoever and get the wrong src PATH or URL, like in the title, there are some extra directories being added.
Correct url
http://graz.io/images/logotypes/case-logotypes.png
Same image but incorrect url
http://graz.io/case/thepoetryhour/images/logotypes/case-logotypes.png
I have the following url http://graz.io where you can experience the problem
If you cycle through couple of transitions I get a 404 error on the images on the homepage (work)
Any pointers? Thank you

Okay, this has been solved. I was using a static site generator (Middleman) and the frontmatter image reference was missing a forward slash. Dumb mistake. The confusion was because the images loaded on page load anyway. Not after traversing the site. Hope this helps anyone else
from
image: images/logotypes/case-logotypes.png
to
image: '/images/logotypes/case-logotypes.png'


c8d/push: Push lazy blobs with distribution source labels

This makes it possible to push multi-platform images if some contents are missing from the local content store, but can be fetched from a source repository.
The trick here is wrapping the ContentStore to return a fake content.Info with a containerd.io/distribution.source. label which specifies the source registry and repository for the blob. It's then used by the repository to cross-repo mount the blobs.
Caveats:

Doesn't work with other registries than the one which provided the missing blob.
Works only as long as we have a source manifest (it's deleted by buildx purge -a or restarting the daemon)

Test:
printf 'FROM alpine\nCMD ["echo", "hello"]' | docker buildx build . \
    -t docker.io/repo/test:latest --platform linux/amd64,linux/arm64
docker push docker.io/repo/test:latest

Test result with a fresh repo
root # docker buildx imagetools inspect docker.io/pawelgronowski465/pushworks:220824 # Repo doesn't exist1
ERROR: docker.io/pawelgronowski465/pushnotworks:220824: not found
root # cat Dockerfile
FROM alpine
CMD ["echo", "test"]
root # docker build . -t pawelgronowski465/pushworks:220824 --platform linux/arm64,linux/amd64,linux/386
[+] Building 4.4s (9/9) FINISHED
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 70B                                                                                0.0s
 => [linux/arm64 internal] load metadata for docker.io/library/alpine:latest                                                              3.9s
 => [linux/amd64 internal] load metadata for docker.io/library/alpine:latest                                                              3.9s
 => [linux/386 internal] load metadata for docker.io/library/alpine:latest                                                                3.9s
 => [linux/amd64 1/1] FROM docker.io/library/alpine@sha256:bc41182d7ef5ffc53a40b044e725193bc10142a1243f395ee852a8d9730fc2ad               0.0s
 => => resolve docker.io/library/alpine@sha256:bc41182d7ef5ffc53a40b044e725193bc10142a1243f395ee852a8d9730fc2ad                           0.0s
 => [linux/386 1/1] FROM docker.io/library/alpine@sha256:bc41182d7ef5ffc53a40b044e725193bc10142a1243f395ee852a8d9730fc2ad                 0.0s
 => => resolve docker.io/library/alpine@sha256:bc41182d7ef5ffc53a40b044e725193bc10142a1243f395ee852a8d9730fc2ad                           0.0s
 => [linux/arm64 1/1] FROM docker.io/library/alpine@sha256:bc41182d7ef5ffc53a40b044e725193bc10142a1243f395ee852a8d9730fc2ad               0.4s
 => => resolve docker.io/library/alpine@sha256:bc41182d7ef5ffc53a40b044e725193bc10142a1243f395ee852a8d9730fc2ad                           0.0s
 => => sha256:9b18e9b68314027565b90ff6189d65942c0f7986da80df008b8431276885218e 0B / 2.71MB                                                0.4s
 => exporting to image                                                                                0.4s
 => => exporting layers                                                                                0.0s
 => => exporting manifest sha256:1e3431ac147d5ab9aad7408f9e9cf77191b909b8d5eeee4c3074d29e012a7fcf                                         0.0s
 => => exporting config sha256:03a88cfd93db02177bb2b47b7fc73504ebf75b7cc3eb4432edc01caae5535098                                           0.0s
 => => exporting manifest sha256:89aebd05109a4dba92ff76ea73b52ded8286b2c5a30467c9810eb3c6b92db91a                                         0.0s
 => => exporting config sha256:9faa6ecf5f1b46d07c961b9a490a16391a9b1f7fb30cea316dbe10992595207a                                           0.0s
 => => exporting manifest sha256:c8ed6a8c58f8e50c90be744426398f3b2fcbea51d45f0e27a266b1a69cf99d5c                                         0.0s
 => => exporting config sha256:9cff1119afd2277751867756a94fe0f20495b47374cc84d8fe7096006cdf272e                                           0.0s
 => => exporting manifest list sha256:610e37756255c286b3e3706d3239e339f4b378487c4aafe03c0941cae65ff462                                    0.0s
 => => naming to docker.io/pawelgronowski465/pushworks:220824                                                                             0.0s
 => => unpacking to docker.io/pawelgronowski465/pushworks:220824                                                                          0.4s
root # docker push docker.io/pawelgronowski465/pushworks:220824
03a88cfd93db: Pushed
9b18e9b68314: Pushed
89aebd05109a: Pushed
c8ed6a8c58f8: Pushed
610e37756255: Pushed
9cff1119afd2: Pushed
6c0d3b419d84: Pushed
213ec9aee27d: Pushed
1e3431ac147d: Pushed
9faa6ecf5f1b: Pushed
root # docker buildx imagetools inspect docker.io/pawelgronowski465/pushworks:220824
Name:      docker.io/pawelgronowski465/pushworks:220824
MediaType: application/vnd.docker.distribution.manifest.list.v2+json
Digest:    sha256:610e37756255c286b3e3706d3239e339f4b378487c4aafe03c0941cae65ff462

Manifests:
  Name:      docker.io/pawelgronowski465/pushworks:220824@sha256:1e3431ac147d5ab9aad7408f9e9cf77191b909b8d5eeee4c3074d29e012a7fcf
  MediaType: application/vnd.docker.distribution.manifest.v2+json
  Platform:  linux/arm64

  Name:      docker.io/pawelgronowski465/pushworks:220824@sha256:89aebd05109a4dba92ff76ea73b52ded8286b2c5a30467c9810eb3c6b92db91a
  MediaType: application/vnd.docker.distribution.manifest.v2+json
  Platform:  linux/amd64

  Name:      docker.io/pawelgronowski465/pushworks:220824@sha256:c8ed6a8c58f8e50c90be744426398f3b2fcbea51d45f0e27a266b1a69cf99d5c
  MediaType: application/vnd.docker.distribution.manifest.v2+json
  Platform:  linux/386

Undrafting this as it allows the build+push case to work.
Will work on the pull+tag+push case separately.

Added some comments and cleaned up the source label handling a bit.
Will squash the commits later when merging.

When upstreaming:

depends on / needs to go after https://github.com/moby/moby/pull/43819
but, we may want to squash all fixes related to "common" progress (push/pull) code into a single commit

combine with one or more of;

https://github.com/rumpl/moby/pull/15
https://github.com/rumpl/moby/pull/16
https://github.com/rumpl/moby/pull/73
https://github.com/rumpl/moby/pull/74
progress fix-up from https://github.com/rumpl/moby/pull/80


Add in-context examples

All current examples are of the usage/api-explanation type. It would be nice to also have examples with more context, even if we use toy-examples.

Hey can you give me a bit more information about this

Library functionality should be explained in the context of (simple) examples resembling problems users may find in real data analysis problems.


Added /healthcheck endpoint for integrations with envoy

Set healthcheck for envoy to integrate and check service health. Easier for us to add endpoint vs. switching envoys reference.
https://github.com/lyft/incubator-superset/pull/2
@mistercrunch

For reference, we would have kept that in our fork but figured that with the growing popularity of Envoy (https://github.com/envoyproxy/envoy) and Envoy using healthcheck/ as a default, others might benefit from this endpoint shipping with Superset.

Coverage decreased (-0.006%) to 71.439% when pulling 0e4a7a601da6949f4e973b9debb4db99943bd5c7 on hughhhh:healthcheck into cbcc00c9290faf4d98c562df2a0f802d63669c77 on apache:master.

Coverage decreased (-0.006%) to 71.439% when pulling 0e4a7a601da6949f4e973b9debb4db99943bd5c7 on hughhhh:healthcheck into cbcc00c9290faf4d98c562df2a0f802d63669c77 on apache:master.

Coverage increased (+0.008%) to 71.453% when pulling d20d484b0ec4e60e757834c123ab84ddad1cd565 on hughhhh:healthcheck into cbcc00c9290faf4d98c562df2a0f802d63669c77 on apache:master.

Coverage increased (+0.008%) to 71.453% when pulling d20d484b0ec4e60e757834c123ab84ddad1cd565 on hughhhh:healthcheck into cbcc00c9290faf4d98c562df2a0f802d63669c77 on apache:master.


Fix python path dependencies with file

This should fix https://github.com/dependabot/dependabot-core/issues/1977
This PR updates the regex in Dependabot::Python::FileFetcher.parse_path_setup_paths to ignore if there is a file: at the beginning of the requirement path.

Is this fix already released?


Test NOIR Across Multiple Repositories for Analyzing

It seems like a good approach to conduct tests on multiple open-source repositories to ensure that NOIR functions correctly across different repositories.
This will help us identify potential compatibility issues, edge cases, and performance bottlenecks when scanning diverse codebases.

Move to https://github.com/ksg97031/endpoints/issues/1


ansible 2.10 support

There doesn't seem to be an existing issue referencing ansible 2.10 issues yet, so here goes :)
ansible 2.10.0b1.post0
  config file = /export/home/orion-admin/ansible-boulder/ansible.cfg
  configured module search path = [u'/export/home/orion-admin/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /export/home/orion-admin/ansible/lib/ansible
  executable location = /export/home/orion-admin/ansible/bin/ansible
  python version = 2.7.5 (default, Apr  1 2020, 10:09:19) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)]
Using /export/home/orion-admin/ansible-boulder/ansible.cfg as config file
Parsed /export/home/orion-admin/ansible-boulder/inventory/boulder.cobbler.yml inventory source with cobbler plugin
Skipping due to inventory source not ending in "cobbler.yaml" nor "cobbler.yml"
cobbler declined parsing /export/home/orion-admin/ansible-boulder/inventory/hosts as it did not pass its verify_file() method
Parsed /export/home/orion-admin/ansible-boulder/inventory/hosts inventory source with ini plugin
Parsed /export/home/orion-admin/ansible-boulder/inventory/monterey.cobbler.yml inventory source with cobbler plugin
Parsed /export/home/orion-admin/ansible-boulder/inventory/seattle.cobbler.yml inventory source with cobbler plugin
[top  4317] 10:19:00.884328 D ansible_mitogen.affinity: CPU mask for Ansible top-level process: 0x000002
[top  4317] 10:19:00.884631 D ansible_mitogen.process: inherited open file limits: soft=1024 hard=4096
[top  4317] 10:19:00.884730 D ansible_mitogen.process: raised soft open file limit from 1024 to 4096
[mux  4327] 10:19:00.887142 D ansible_mitogen.affinity: CPU mask for MuxProcess 0: 0x000001
[mux  4327] 10:19:00.902435 D mitogen.service: Pool(a110, size=32, th='MainThread'): initialized
[mux  4327] 10:19:00.902749 D ansible_mitogen.process: Service pool configured: size=32
META: ran handlers
[task 4361] 10:19:00.934268 D ansible_mitogen.affinity: CPU mask for WorkerProcess: 0x000004
The full traceback is:
Traceback (most recent call last):
  File "/export/home/orion-admin/ansible/lib/ansible/executor/task_executor.py", line 155, in run
    res = self._execute()
  File "/export/home/orion-admin/ansible/lib/ansible/executor/task_executor.py", line 610, in _execute
    self._handler = self._get_action_handler(connection=self._connection, templar=templar)
  File "/export/home/orion-admin/ansible/lib/ansible/executor/task_executor.py", line 1063, in _get_action_handler
    collection_list=collections
  File "/export/home/orion-admin/ansible-boulder/mitogen/ansible_mitogen/strategy.py", line 144, in wrap_action_loader__get
    return adorned_klass(*args, **kwargs)
  File "/export/home/orion-admin/ansible-boulder/mitogen/ansible_mitogen/mixins.py", line 118, in __init__
    super(ActionModuleMixin, self).__init__(task, connection, *args, **kwargs)
TypeError: __init__() got an unexpected keyword argument 'collection_list'
barry.cora.nwra.com | FAILED! => {
    "msg": "Unexpected failure during module execution.",
    "stdout": ""
}
[mux  4327] 10:19:00.980813 D mitogen: Waker(fd=6/8): disconnecting

Thanks for the ticket! :)
I was sorta doing this in this PR here: https://github.com/dw/mitogen/pull/715  (the error you reported I started to fix in that branch),
until I got distracted by sudden failing tests here: https://github.com/dw/mitogen/pull/723
I like a dedicated ticket for 2.10 support though since there will probably be other things other than collections that need to change for 2.10.

Ran into the first issue:
https://github.com/dw/mitogen/pull/715/commits/1bd4b8afcdcff636bed8f6a703769b0ad86ba791

@opoplawski please give https://github.com/dw/mitogen/pull/715 a try and let me know if it fixes your issue 😄 It should work with ansible 2.10 installed from github via pip install<EMAIL_ADDRESS>since ansible==2.10 isn't out yet.

❦  2 septembre 2020 19:05 -07, Steven Robertson:

@opoplawski please give https://github.com/dw/mitogen/pull/715 a try
and let me know if it fixes your issue 😄 It should work with ansible
2.10 installed from github via pip install<EMAIL_ADDRESS>since
ansible==2.10 isn't out yet.

or pip install ansible-core==2.10.0 (which should be exactly the same
as the tag).

I tried it, and ansible-core doesn't exist 🤔 https://pypi.org/project/ansible-base/ does, but that won't come with collections. Eventually ansible==2.10 will release with some collections inside it, see https://github.com/ansible-community/ansible-build-data/blob/main/2.10/ansible.in

❦  3 septembre 2020 21:25 -07, Steven Robertson:

I tried it, and ansible-core doesn't exist 🤔
https://pypi.org/project/ansible-base/ does, but that won't come with
collections. Eventually ansible==2.10 will release with some
collections inside it, see
https://github.com/ansible-community/ansible-build-data/blob/main/2.10/ansible.in

Oh, yes, sorry! It was ansible-base.

How is the status for the the 2.10 version? Is there any ETA for a new release?

How is the status for the the 2.10 support? Is there any ETA for a new release?

Same question here.

I'd suggest subscribing to the pull request linked above to keep updated. 😃

How is the status for the the 2.10 support? Is there any ETA for a new release?

Hello! what's the status for the 2.10+ support? I see mitogen is still under active development but no news on this front :(
Thanks in advance 🙏

How is the status for the the 2.10 support? Is there any ETA for a new release?

Hello! what's the status for the 2.10+ support? I see mitogen is still under active development but no news on this front :( Thanks in advance 🙏

" closed this as completed" means it's been implemented and I can confirm this. I think a better question to ask at this point is support for newer versions than that, since Red Hat has been quite busy reworking a lot of things in Ansible.