TxValidationInvalidWitness: split

The TxValidationInvalidWitness case of TxValidationError is insufficiently specific for debugging purposes, so we split it in two parts:

Wrong signature
Key not corresponding to address

bors r+

@dnadales, when running locally, I saw the following test suite errors:
  Test.Cardano.Chain.Epoch.File
    prop_deserializeEpochs:                         FAIL
        ✗ prop_deserializeEpochs failed after 1 test.

             ┏━━ test/Test/Cardano/Chain/Epoch/File.hs ━━━
          26 ┃ prop_deserializeEpochs :: Property
          27 ┃ prop_deserializeEpochs = H.withTests 1 $ H.property $ do
          28 ┃   menv <- liftIO $ lookupEnv "CARDANO_MAINNET_MIRROR"
          29 ┃   H.assert $ isJust menv
             ┃   ^^^^^^^^^^^^^^^^^^^^^^
          30 ┃
          31 ┃   files <- take 10 <$> liftIO mainnetEpochFiles
          32 ┃   H.assert $ not (null files)
          33 ┃   -- TODO: the property cannot take any parameters (if we want discoverPrefix
          34 ┃   -- to work). Now the question is whether it is OK to use an hardcoded value
          35 ┃   -- for the number of slots per epoch, and if so in which module should we
          36 ┃   -- store this constant?
          37 ┃   let stream = parseEpochFilesWithBoundary mainnetEpochSlots files
          38 ┃   result <- (liftIO . runResourceT . runExceptT . S.run) (S.maps discard stream)
          39 ┃   result === Right ()
          40 ┃  where
          41 ┃   discard :: Of a m -> ExceptT ParseError ResIO m
          42 ┃   discard (_ :> rest) = pure rest

          This failure can be reproduced by running:
          > recheck (Size 0) (Seed<PHONE_NUMBER>820430233<PHONE_NUMBER>072082227) prop_deserializeEpochs

      Use '--hedgehog-replay "Size 0 Seed<PHONE_NUMBER>820430233<PHONE_NUMBER>072082227"' to reproduce.

  Test.Cardano.Chain.Block.Validation
    prop_signingHistoryUpdatesPreserveInvariants:   OK (0.88s)
        ✓ prop_signingHistoryUpdatesPreserveInvariants passed 100 tests.
    ts_prop_mainnetEpochsValid:                     FAIL
        ✗ ts_prop_mainnetEpochsValid failed after 1 test.

              ┏━━ test/Test/Cardano/Chain/Block/Validation.hs ━━━
           76 ┃ ts_prop_mainnetEpochsValid :: ShouldAssertNF -> TSProperty
           77 ┃ ts_prop_mainnetEpochsValid shouldAssertNF scenario = withTests 1 . property $ do
           78 ┃   menv <- liftIO $ lookupEnv "CARDANO_MAINNET_MIRROR"
           79 ┃   assert $ isJust menv
              ┃   ^^^^^^^^^^^^^^^^^^^^
           80 ┃
           81 ┃   -- Get the 'Genesis.Config' from the mainnet genesis JSON
           82 ┃   config <- readMainetCfg
           83 ┃
           84 ┃   -- Construct the initial 'ChainValidationState'
           85 ┃   let cvs = either (panic . show) identity $ initialChainValidationState config
           86 ┃
           87 ┃   let
           88 ┃     takeFiles :: [FilePath] -> [FilePath]
           89 ┃     takeFiles = case scenario of
           90 ┃       ContinuousIntegration -> identity
           91 ┃       Development           -> take 15
           92 ┃       QualityAssurance      -> identity
           93 ┃
           94 ┃   -- Get a list of epoch files to perform validation on
           95 ┃   files <- takeFiles <$> liftIO mainnetEpochFiles
           96 ┃
           97 ┃   let stream = parseEpochFilesWithBoundary (configEpochSlots config) files
           98 ┃
           99 ┃   annotate ("Did you build with `ghc -fhpc` or `stack --coverage`?\n"
          100 ┃     <> "If so, please be aware that hpc will introduce thunks around "
          101 ┃     <> "expressions for its program coverage measurement purposes and "
          102 ┃     <> "this assertion can fail as a result.\n"
          103 ┃     <> "Otherwise, for some reason, the `ChainValidationState` is not in "
          104 ┃     <> "normal form.")
          105 ┃
          106 ┃   result <- (liftIO . runResourceT . runExceptT)
          107 ┃     (foldChainValidationState shouldAssertNF config cvs stream)
          108 ┃
          109 ┃   void $ evalEither result

          This failure can be reproduced by running:
          > recheck (Size 0) (Seed<PHONE_NUMBER>8461969793<PHONE_NUMBER>851444775) ts_prop_mainnetEpochsValid

      Use '--hedgehog-replay "Size 0 Seed<PHONE_NUMBER>8461969793<PHONE_NUMBER>851444775"' to reproduce.

Damian pointed the error is due to CARDANO_MAINNET_MIRROR missing in my environment.


Error on export as gist

When I try "Export as gist", I get error: "There was a problem creating the gist:" and I cannot export my bins to gist.
See the screenshot:

Ditto

It would appear the GitHub Rest API was changed earlier this year.
From https://docs.github.com/en/rest/guides/basics-of-authentication#accepting-user-authorization :

Deprecation Notice: GitHub will discontinue authentication to the API using query parameters. Authenticating to the API should be done with HTTP basic authentication. Using query parameters to authenticate to the API will no longer work on May 5, 2021. For more information, including scheduled brownouts, see the blog post.

I had the same problem. I cant dowload it either!

If the fact that it contains a script is why I cant really use any alternantives

Try to test the html code first then the other
On Wed, Aug 10, 2022, 11:44 PM SurveyMan-AdMe @.***>
wrote:

If the fact that it contains a script is why I cant really use any
alternantives
—
Reply to this email directly, view it on GitHub
https://github.com/jsbin/jsbin/issues/3476#issuecomment-1211358494, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AZBY6AST5GJCWKDYQROMDFDVYQWD5ANCNFSM5GQDY7BQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

The html works perfectly fine i realized i just needed to save it first

lol
e
e
e
e
e
e


Signature error on polkadot js

This error occurs when finalization is lagging (but no more than for 512 blocks, after this threshold we have another error). It is worth noticing that  extrinsic submition works when performed through python substrate interface in this scenario, only extrinsic generated via Polkadot JS fail with the signature error. It could be connected to the fact that Polkadot JS receives a lot of data that it allegedly uses to construct an extrinsic via subscription on storage keys, while python substrate interface fetches this data directly.

polkadot-js/apps uses finalized block for mortality. However mortality uses lossy encoding (see struct Era), which becomes incorrect if finalized block is too far from best block.


Lazy loading routes don't work in generated build

Describe the bug
Routes stop working in generated bundle when I use dynamically imported (async) route components (in dev all works fine):
export const routes =   [
     { path: "/", component: "Home" },
     { path: "/about", component: "About" }
  ].map(({ path, component, meta }) => ({
     path,
     component: () => import(`./views/${component}.vue`)
   }))

Reproduction
Reproduction Repo: https://github.com/husayt/vite-tailwind-starter
Reproduction step
yarn build
yarn servestatic

When i go to localhost:8080 I get this error in the console:
index.d91b05ae.js:1 GET http://localhost:8080/_assets/views/Home.vue net::ERR_ABORTED 404 (Not Found)

Same with /about. So routes don't work, although they work fine with yarn dev
System Info

required vite version: 0.20.2
required Operating System: Windows 10
required Node version: 14.3
Optional:

npm/yarn version yarn 1.22.4

Detailed description
Routes work fine in the  original project from this repo where pages imported statically.
import Home from './views/Home.vue'
import About from './views/About.vue'
import NotFound from './views/NotFound.vue'

/** @type {import('vue-router').RouterOptions['routes']} */
export let routes = [
  { path: '/', component: Home, meta: { title: 'Home' } },
  { path: '/about', component: About, meta: { title: 'About' } },
  { path: '/:path(.*)', component: NotFound },
]

But once I change routes to dynamic import, they stop working in generated bundle (dev still works fine)
const list = [
  { path: "/", component: "Home", meta: { title: "Home" } },
  { path: "/about", component: "About" },
  { path: "/:path(.*)", component: "NotFound" },
]

/** @type {import('vue-router').RouterOptions['routes']} */
export const routes = list.map(({ path, component, meta }) => ({
  path,
  component: () => import(`./views/${component}.vue`),
  meta: meta || { title: component },
}))

This currently seems to be a limitation of ESBuild.

I see, but this is such an important case it will be good to have some kind of workaround. Technically routes are known, so build tool can process them and add tree shakable dynamically loaded chunks.

Full dynamic import path imports are currently untouched during build, because Rollup doesn't provide default handling for it.

@yyx990803 Is there an alternative syntax to use, until there is esbuild support

@husayt In 0.20.3 vite use rollup-plugin-dynamic-import-variables, so it should works.

Actually indeed it does. Thanks @yyx990803


Logging

Hi,
Are you going to implement embedded logging to your framework?
Thanks.

No. Please use Python's logging module.


Consider showing LoaderExceptions when caught exception is ReflectionTypeLoadException

Based on discussion at https://github.com/aspnet/Mvc/issues/4892#issuecomment-227580313. It would be nice to type load exceptions so that it's easier to figure out what went wrong rather than see a generic message that tells you to read LoaderExceptions

cc @Eilon \  @rynowak \ @halter73 \ @davidfowl

Are there other exception types that would benefit from a similar treatment? AggregateExceptions for instance?

Also @ajaybhargavb who's assigned this work :)

If you wanted to be super generic you could think about some reflection based logging. Maybe JSON serialization. I haven't tried it out to see how it would look for ReflectionTypeLoadExceptions and AggregateExceptions, but it might be worth looking into.

Not sure I follow @halter73 - is this essentially serializing the exception to the log?

Since this issue is filed in the diagnostics repo, I thought it would be about how to display exceptions in the error pages, not how it's logged. But yes, I'm essentially suggesting serializing the exception if it can be done in a way that's not too verbose/distracting. Maybe it can be put in a collapsible section like the result of Exception.ToString() is today.
I still think that MVC should catch ReflectionTypeLoadExceptions when it accesses Assembly.DefinedTypes and log it specially with LoaderExceptions like I suggest in https://github.com/aspnet/Mvc/issues/4892#issuecomment-227553247.

@ajaybhargavb this is part of what we discussed earlier. Would be nice to special case some exception types and show more detailed information about them.


Runtime Error

just requests.post()
.py file is ok, but I packaged .py file to .exe file with pyinstaller in win7 32bits, and then when I ran the .exe file in a win7 64bits matchine, It was like this.

This does not like it could possibly be our problem. Do you see this if you replace the requests import with an import of any other third party library?

# -*- coding: UTF-8 -*-

'''
Last modified time: 2015-04-24 17:16:47
Edit time: 2015-04-24 17:17:16
File name: text.py
Edit by caimaoy
'''

import requests

if __name__ == '__main__':
    print 'aaa'
    requests.post(r'http://<IP_ADDRESS>:5000/upload', data={'test':'test'})

this is my code ...

Do you see this if you replace the requests import with an import of any other third party library?

Closing for inactivity.


[OSSM-8136] Refactor TestOpenShiftMonitoring test to not use standalone Kiali CR + fix flakiness

Refactored TestOpenShiftMonitoring test to not use standalon kiali CR but patch the existing one (managed by maistra operator) instead. (the way how the customer should use it)
Added waiting for Prometheus target to be ready before requesting the mesh app.

Passed on all SMCP versions: https://master-jenkins-csb-servicemesh.apps.ocp-c1.prod.psi.redhat.com/job/maistra/job/maistra-test-tool/2768/

not use standalon kiali CR but patch the existing one (managed by maistra operator) instead. (the way how the customer should use it)

You are not correct saying that customers should not use custom Kiali CR. SMCP intentionally allows to "attach" custom Kiali CR to SMCP. I see 2 reasons to keep custom Kiali as is:

We documented this approach.
OSSM 3 does not support Kiali out of the box and attaching custom Kiali is the way to integrate with OSSM 3, and users migrating to that version have to follow this approach.

@jewertow  yeah, you are right, the mention is here https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html-single/service_mesh/index#ossm-smcp-kiali_kiali-config-ref

Updated description and the code


Add Elixir toolkit theme to CoDex

@bebatut / @paulzierep - could you please review? 😄
Completed:

Add ETT elements
Configure and deploy test site https://supernord.github.io/galaxy_codex/ (thanks for your help @bedroesb)
Create data table for CoDex and format
Updates to ETT (thanks @paulzierep and @bedroesb) https://github.com/ELIXIR-Belgium/elixir-toolkit-theme/pull/292
Add python script for merging availability across Galaxy instances and creating .yml files for ETT

Still to do:

[ ] Update column names (based on changes during the hackathon)
[ ] Update contributors list (CONTRIBUTORS.yml)
[ ] Create custom folder for deployment of website, which is separate to /docs
[ ] Merge columns and improve usability
[ ] Add tutorial and workflow tables
[ ] Add the ability to create community-specific tables that are subsets of the main CoDex

Thanks @paulzierep
@mthang found a solution to the DateTime issue
The number at the end is the value associated with each availability key in the metadata - suggestions for how to present this in the table? another column?

@paulzierep - do you think the date / time issue is being caused by the date being a string value?
e.g. in the tools.yml file the value is '2024-11-11'

I think: SearchBuilder Requires DateTime when used with dates means that the JS needs a DateTime package which is not there in the Elixir Toolkit, I asked @bedroesb to add it to the toolkit feature: https://github.com/ELIXIR-Belgium/elixir-toolkit-theme/pull/292
Hope that solves it.

@supernord can you rebuild the website and check if the library works now, see: https://github.com/ELIXIR-Belgium/elixir-toolkit-theme/pull/292

Tried it out locally. It should work now. I would suggets to add toc: false to the fronmatter of the md:
---
title: Tools
description: An interactive list of Galaxy tools created by the Galaxy CoDex.
datatable: true
sidebar: false
toc: false
---

This will prevent the table from jumping around after load.
I would also docs/_site in the .gitignore file to make it easier for local deployments.

thanks @bedroesb - that fixed the issue 😄

@bebatut good catch I will make a release soon, so you can use that as version.

I cannot comment much on the jekyll stuff, but from your deployment it looks very nice ! So OK to merge for me. Maybe we could add tool users to the tool table, and I was wondering why trainings are missing. Still it could be merged and improved from there imo. Thanks !

The files and configs needed to include training are there. The remaining issue is that the tutorials.yml file doesn't have the right structure. i.e. it shouldn't have a named index value for each entry in the file.


Weirdness with u2f login

If your account has 2-step verification enabled with u2f (https://support.google.com/accounts/answer/6103523?hl=en), the Play Music Desktop Player ends up taking you to the Chrome web store to install the gnubbyd extension (https://chrome.google.com/webstore/detail/gnubbyd/beknehfpfkghjoafdifaflglpjkojoco/related?utm_source=chrome-app-launcher-info-dialog).

I noticed that too.  It was really confusing.  I ended up just using a Google Authenticator code to get in.

Can confirm this issue exists on OS X  10.11.3 with a YubiKey Neo with the same behaviour as described by @lengau.

I have a U2F key aswell, unfortunately I can't bring support for the keys into the app ( I don't think ) so for now it's just going to have to be an extra click to use Google Authenticator codes.
Sorry guys :)

If anyone has any work around ideas I'm open but don't see how this can be fixed without injecting JS onto the logon page which I really don't want to do

I use 2FA, and I've tried setting up an "app password" but for some reason it doesn't work.  https://security.google.com/settings/security/apppasswords?hl=en  it's painful because I don't actually know my google password (I use last pass) so I've gotta do a lot of stuffing around to login and use the app.


Connect to pm2 in no-daemon-mode

connects to pm2 in no-daemon-mode
overrides console methods to use parent logger
freezes console methods so that pm2 can't override them

Those last two bullets are more of a temporary fix. A better, more permanent solution would be refactoring pm2 to allow for custom loggers instead of using console directly, perhaps by forking the pm2 repo or using patch-package.
Tested with a handful of prod apps, everything seems to be working as expected.

I did some more testing too and overall this seems great!
One issue I found is that we loose a few of the daemon benefits like single-instance apps:

Running launchpad via code (launchpad.startup()) won't make it listen to shutdown signals by default. Because of that, apps aren't terminated on shutdown and subsequent launchpad runs will spawn new app instances.
Running launchpad in a Windows 11 terminal host (instead of directly via cmd.exe and closing the host (or hitting CTRL+C if launching through a .bat file via explorer) also doesn't close the child processes (also see #77 )

The first one was an easy fix: I added a shutdownOnExit option that now automatically listens for onExit within the LaunchpadCore constructor. That can be set to false to disable this behavior. The packages/launchpad/index.js, which is what npx launchpad actually runs, had that as an explicit step, but since we're not running PM2 as a daemon anymore I removed that.
Not quite sure what to do about (2) yet... We may have to look into our own type of daemon options that can register if the main process has terminated. So maybe npx launchpad launches a daemon, that in turn runs LaunchpadCore.startup() (instead of this being directly run via npx launchpad).

I would say let's merge this change in as it resolve other issues and streamlines the whole stack. I'll create a new ticket for (2).


Allow NSData to be written without memory copy

HttpResponseBodyWriter can write UInt8 arrays but not NSData, requiring a conversion between the two. This conversion involves an expensive memory copy from NSData to UInt8 that can be avoided by adding a new method that allows NSData to be written to HttpResponseBodyWriter.
I also updated the podspec file to version 3. Please let me know that should be in a separate pull request.

👍

Just pushed the undo of the podspec. Let me know if you need anything else.

Good PR. Merged.


Help with "large gap" detection

Could you please help me understand why the player detects a "large gap" between the 2nd and the 3rd segments in the following sample?
Player: https://shaka-player-demo.appspot.com (v.2.5.3 debug on Firefox and Chrome Iron)
Asset: https://demo.yospace.com/vincent/dash/3956/manifest.mpd (scrub to far left when the asset starts to play from the beginning)

Ignoring large gap at<PHONE_NUMBER>96 size 1.0903039999539033
gap_jumping_controller.js:235:6

Sounds like there could be a gap at the end of the 2nd segment (ie. t=5340657870920) because the gap is detected at "534072.936696" which is within the 2nd segment "boundaries".
Could you please confirm that?
Many thanks.

What this means is that there is a gap of size 1.090 seconds at time ~534,072.937 seconds in the buffer.  The buffer in question is an intersection of the buffered audio and video streams, and the timestamps are after any period or presentation time offsets are applied and the segments are demuxed by MediaSource.
This gap detection isn't based on the manifest at all, but rather on the demuxed/buffered media at the MediaSource level.  It could be that your manifest is somewhat inaccurate.  This is common at period boundaries, and I noticed that segment 2 is the end of period 1 and segment 3 is the start of period 2.
You can use tools like thumb.co.il to parse the mp4 files and see the timestamps in them if you'd like to investigate the timestamps in your content.
Shaka Player, by default, assumes that a sufficiently large gap is a mistake in the content encoding, and that it would be better to make sure the developer notices by stopping and issuing a warning.  A smaller gap is jumped automatically, as this can be caused by a rounding error.
I think in this case, it's likely true that this is a mistake in your content encoding/packaging.  So I strongly recommend you look into fixing your packager/encoder or filing a bug against the vendor of your packager/encoder.
You can control Shaka Player's behavior, though, if you want.  You can change the threshold of what's considered a "small" gap with player.configure('streaming.smallGapLimit', limitSizeInSeconds).  The default is 0.5 seconds.  You can also ask the player to skip all gaps, regardless of size, with player.configure('streaming.jumpLargeGaps', true).  You could also ask the player to jump individual large gaps by listening for the largegap event from the player and calling event.preventDefault().
Does this help?

Yes this helps.
I will check all these segments and see whether segments before/after the Period boundary are correct or not.

I need to leave this ticket open though because I want to be sure that the player is not seeing a fake data gap and stalling for no reason.

Sounds good.  @shaka-bot will ping the issue in a few days to see if you still need help, and will then close it a few days later if you don't reply.  If that happens, though, it will give you instructions on how to reopen the ticket.

I will close this ticket now since we found genuine data gap in some segments.
Many thanks for your help.

We're always happy to help!


ENH: Allow more than 3 chars for root_symbols

This should allow more than 3 characters for root_symbol.
I have no idea why _encode_continuous_future_sid was written in such an obfuscated way and if I am missing something important there.
Anyway, I have re-written test_continuous_futures.py to test for a root_symbol with 6 characters and all the tests are passing.
This should close #91

Of course you did :)


Update wireshark to 2.2.2

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Installation will failed with known issue: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13152

The last few upstream releases have been a month or so apart and given that the problem is fixed upstream, I'd just wait for the next release. @victorpopkov or @vitorgalvao - what do you guys say?

I’m fine with waiting.


Add support for network interface user friendly name

If CONFIG_NET_INTERFACE_NAME is enabled (default is y), then the system will automatically set a user friendly name to the network interface like eth0, wlan0 etc. Application can change the interface name if needed.
This is useful so that applications do not need to try to use the device name for figuring out the desired network interface.

Increased the max name length to 15 chars.


Fix manage preview

Context
Preview broken in manage-ui. Doesn't supply a value a view depends on a viewbag.
Changes proposed in this pull request
Make the view more resilient to missing data. Bump nuget version.

 preview broken in prod


HDDS-4444. Remove KeyManagerImpl#refreshPipeline because it is the same as refresh().

What changes were proposed in this pull request?
Remove KeyManagerImpl#refreshPipeline() and replace with KeyManagerImpl#refresh().
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4444
How was this patch tested?
Unit test passed.

Hi @flirmnave,  thanks for working on this.
The key point backed in HDDS-3658 is new API "refresh" is added in the KeyManager interface which is called from other modules.   It's good to remove the duplicate functions and keep the code clean.

Thanks @bharatviswa504 @ChenSammi for comment and review.
Based on @ChenSammi comment,
KeyManagerImpl#refresh() is a API which called from other modules,
so I remove KeyManagerImpl#refreshPipeline() and keep KeyManagerImpl#refresh() instead.

@flirmnave Then we can rename in the KeyManager to refreshPipeline, right?

LGTM
@bharatviswa504 let's get this merged before HDDS-4537 / PR-1660?

Sure. I am fine with keeping refresh method.

Thanks @bharatviswa504 @ChenSammi @jojochuang for review and comment.


Cleanup unused logic in chromedp_test

After the commit the logic about checking allocTempDir for leaking became useless. This PR removes it.

I don't understand why it's useless. It finds issues like #1105.

Or, I see. Sorry about creating the wrong PR.


Operation not permitted error on import

I'm attempting to import photos from /mnt/media/Pictures\ to\ Import/steph with the following command:
$ python3 elodie.py import --destination=/mnt/media/Pictures "/mnt/media/Pictures to Import/steph"

which results in this stack trace:
Traceback (most recent call last):
  File "elodie.py", line 378, in <module>
    main()
  File "/home/jfritz/.local/lib/python3.8/site-packages/click/core.py", line 716, in __call__
    return self.main(*args, **kwargs)
  File "/home/jfritz/.local/lib/python3.8/site-packages/click/core.py", line 696, in main
    rv = self.invoke(ctx)
  File "/home/jfritz/.local/lib/python3.8/site-packages/click/core.py", line 1060, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/jfritz/.local/lib/python3.8/site-packages/click/core.py", line 889, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/jfritz/.local/lib/python3.8/site-packages/click/core.py", line 534, in invoke
    return callback(*args, **kwargs)
  File "elodie.py", line 140, in _import
    dest_path = import_file(current_file, destination, album_from_folder,
  File "elodie.py", line 67, in import_file
    dest_path = FILESYSTEM.process_file(_file, destination,
  File "/home/jfritz/elodie/elodie/filesystem.py", line 591, in process_file
    os.utime(_file, (stat_info_original.st_atime, stat_info_original.st_mtime))
PermissionError: [Errno 1] Operation not permitted

This looks like a permissions issue. I am running as jfritz:
$ whoami
jfritz

and both /mnt/media/Pictures and /mnt/media/Pictures\ to\ Import/steph are owned by root, but they should allow reads and writes from any user:
$ ls -la /mnt/
total 8
drwxrwxrwx  4 root root 4096 Jun 19 16:49 .
drwxr-xr-x 20 root root 4096 Jun  1 00:07 ..
drwxrwxrwx  2 root root    0 Jul  2 16:29 media

$ ls -la /mnt/media/
total 1028
drwxrwxrwx 2 root root    0 Jun 30 16:56  .
drwxrwxrwx 4 root root 4096 Jun 19 16:49  ..
drwxrwxrwx 2 root root    0 Jul  9 17:50  Pictures
drwxrwxrwx 2 root root    0 Mar 28 23:33 'Pictures to Import'

$ ls -la /mnt/media/Pictures\ to\ Import/
total 1024
drwxrwxrwx 2 root root     0 Mar 28 23:33 .
drwxrwxrwx 2 root root     0 Jun 30 16:56 ..
drwxrwxrwx 2 root root     0 Jul  9 18:05 steph

$ ls -la /mnt/media/Pictures\ to\ Import/steph/
-rwxrwxrwx 1 root root  2682980 Jun  3 15:18 '2021-06-03 11.18.17.jpg'
-rwxrwxrwx 1 root root  6785417 Jun  3 18:54 '2021-06-03 14.54.41.jpg'
-rwxrwxrwx 1 root root  8373582 Jun  3 18:54 '2021-06-03 14.54.48.jpg'

FWIW, I don't see the error if I use sudo to run Elodie's import command as root, so this does appear to be an ownership issue. These files actually live on an NFS that is mounted by this server, hence the root ownership.
This Stack Overflow issue seems to suggest that Elodie is attempting to set the modification time of one of the files that is being imported, and one of the comments on that question suggests trying to change the date with a touch command:
$ touch --date='2021-07-09' /mnt/media/Pictures\ to\ Import/steph/2021-06-03 14.54.41.jpg
touch: setting times of '/mnt/media/Pictures to Import/steph/2021-06-03': Operation not permitted

Is there some way to configure Elodie such that this behaviour is bypassed? Or some other way to set up my permissions to avoid this issue altogether?
FWIW, I'm running Python 3.8.10 and the latest Elodie commit hash is #3364931.

I created a new group called mnt and added my users to it. Then, I changed the mount options on the NFS drive so that it is mounted by the user root and the group mnt. This should now mean that any user in the mnt group has full permissions inside of mnt, and yet I'm still getting the operation not permitted error reported above.

Thanks for the details.
Can you try to comment out the following lines and see if it works?

https://github.com/jmathai/elodie/blob/master/elodie/filesystem.py#L577
https://github.com/jmathai/elodie/blob/master/elodie/filesystem.py#L591
https://github.com/jmathai/elodie/blob/33649319a48222761d821760c064e93e4db65c45/elodie/filesystem.py#L628
https://github.com/jmathai/elodie/blob/33649319a48222761d821760c064e93e4db65c45/elodie/filesystem.py#L633

Thanks for the suggestions @jmathai, but I was able to get around the problem by using the noperm cifs option when mounting the share. It might be worth adding a section to your docs explaining that Elodie needs the ability to change file metadata, so that people who are operating in environments with weird permissions can diagnose that issue if they run into this problem while using the script.


Update data model location

This pulls in the new version of the data model with dependsOn Component added, and fixes the path to the actual test data model in the schematic config file.

Oh no, made the PR in the wrong repo! This was meant for my fork. My bad. Ignore!


[#6761] Cleanup

Codecov Report

Merging #6936 into master will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #6936      +/-   ##
==========================================
- Coverage   39.32%   39.32%   -0.01%
==========================================
  Files        3221     3222       +1
  Lines       95044    95062      +18
  Branches    11893    11893
==========================================
+ Hits        37378    37382       +4
- Misses      54676    54691      +15
+ Partials     2990     2989       -1

Impacted Files
Coverage Δ

...inpoint/web/controller/ScatterChartController.java
0.00% <0.00%> (ø)

...navercorp/pinpoint/web/controller/ScatterView.java
0.00% <0.00%> (ø)

.../pinpoint/web/service/ScatterChartServiceImpl.java
0.00% <ø> (ø)

...point/rpc/client/DefaultPinpointClientHandler.java
70.77% <0.00%> (-1.30%)
:arrow_down:

...orp/pinpoint/rpc/server/DefaultPinpointServer.java
79.22% <0.00%> (-0.71%)
:arrow_down:

...rp/pinpoint/rpc/server/PinpointServerAcceptor.java
84.10% <0.00%> (+0.66%)
:arrow_up:

...cluster/zookeeper/ZookeeperClusterDataManager.java
54.83% <0.00%> (+1.93%)
:arrow_up:

...navercorp/pinpoint/rpc/common/SocketStateCode.java
82.92% <0.00%> (+2.43%)
:arrow_up:

...vercorp/pinpoint/rpc/packet/ClientClosePacket.java
66.66% <0.00%> (+11.11%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1e9dbf8...a25318b. Read the comment docs.


Revert "nixos/dhcpd: switch to DynamicUser"

Reverts NixOS/nixpkgs#139873 (for now)

I checked locally, but let's get more confirmation:
@ofBorg test systemd-networkd-ipv6-prefix-delegation


v6.2.0 [PANIC] [sorter.go:306] ["resolved ts regression"]

What did you do?

Test case:cc_tikv_scale_sync

Workload: 60k table

Steps:   scale-out tikv to 7
scale-in cdc from 6 to 4
scale-in tikv from 7 to 4

What did you expect to see?
No response
What did you see instead?
Test case log:
[2022/08/02 06:15:46.743 +00:00] [INFO] [step.go:30] ["scaleTiDBCluster, target=tikv, replica=7, timeout=0s"]
[2022/08/02 06:29:36.901 +00:00] [INFO] [tidb_cluster.go:103] ["scale tidb cluster success"] [option="scaleTiDBCluster, target=tikv, replica=7, timeout=0s"] [elapsed=13m50.158236255
s]
[2022/08/02 06:29:36.901 +00:00] [INFO] [step.go:30] ["scaleTiDBCluster, target=ticdc, replica=4, timeout=0s"]
[2022/08/02 06:32:12.041 +00:00] [INFO] [tidb_cluster.go:103] ["scale tidb cluster success"] [option="scaleTiDBCluster, target=ticdc, replica=4, timeout=0s"] [elapsed=2m35.139213438
s]
[2022/08/02 06:32:12.041 +00:00] [INFO] [step.go:30] ["scaleTiDBCluster, target=tikv, replica=4, timeout=0s"]
upstream-ticdc-2 panic log:
[2022/08/02 06:31:40.185 +00:00] [PANIC] [sorter.go:306] ["resolved ts regression"] [tableID=61568] [resolvedTs=435007491944480771] [oldResolvedTs=435007493255200775] [stack="github.com/pingcap/tiflow/cdc/processor/pipeline.(*sorterNode).handleRawEvent\n\tgithub.com/pingc
upstream-ticdc-1 panic log:
[2022/08/02 07:29:41.982 +00:00] [PANIC] [sorter.go:306] ["resolved ts regression"] [tableID=61501] [resolvedTs=435008405739143171] [oldResolvedTs=435008406263431170] [stack="github.com/pingcap/tiflow/cdc/processor/pipeline.(*sorterNode).handleRawEvent\n\tgithub.com/pingc
[2022/08/02 07:29:44.078 +00:00] [INFO] [helper.go:49] ["init log"] [file=/var/lib/ticdc/log/ticdc.log] [level=info]
[2022/08/02 07:29:44.078 +00:00] [INFO] [version.go:47] ["Welcome to Change Data Capture (CDC)"] [release-version=v6.2.0] [git-hash=bd21a6ea5ce58b86fe139eddca8dc4436320ca60] [git-branch=heads/refs/tags/v6.2.0] [utc-build-time="2022-08-01 09:09:06"] [go-version="go version
[2022/08/02 07:29:44.078 +00:00] [INFO] [server.go:90] ["creating CDC server"]
Versions of the cluster
Upstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):
(paste TiDB cluster version here)

Upstream TiKV version (execute tikv-server --version):
(paste TiKV version here)

TiCDC version (execute cdc version):
(paste TiCDC version here)
Release Version: v6.2.0
Git Commit Hash: bd21a6ea5ce58b86fe139eddca8dc4436320ca60
Git Branch: heads/refs/tags/v6.2.0
UTC Build Time: 2022-08-01 09:09:06
Go Version: go version go1.18.2 linux/amd64
Failpoint Build: false

/label affects-6.2

If feature batch resolved ts is enabled, Region resolved timestmap can regress. It's expected. And it's allowed by Frontier. So I guess just remove the panic is fine enough.

/assign @sdojjy

Since this issue would not casue correctness problem on data consistence and it's hard to reproduce, so I'm going to adjust it to a severity/moderate issue.

reopen this issue if happen again


How to enable port SSL port 465

Really a great project.
By following README instructions I could able to up the server.
Everything works really fine, I tested IMAP(S), POP3(S) and Mail Submission as well.
But I have an requirement where I wanted to test an email client with legacy SMTPS protocol instead of using the STARTTLS command", i.e. with port 465. So is it possible to enable SMTP over 465 without STARTTLS command.

This will be fixed in the next release. You'll have to open that port manually in docker-compose.production.yml (commented for now)


Float issue with py-ubjson file

Hi,
I am trying to import in Matlab a ubj file generated with py-ubjson.
Everything works fine, except for float?
Any idea why?
in python:
import ubjson
d = {'string': 'test', 'int': 123456,'pi':3.1415}
ubjson.dump(d,open('test.ubj','w'))
in Matlab:
s = loadubjson('test.ubj'')
s =
int: 123456
pi: 1.0965e+227
string: [116 101 115 116]

I looked into this, it looks like py-ubjson saved the floating point (double in this case) in the Big-endian format, even the host machine is a little-endian machine.
The UBJSON specs Draft-12 is not exactly clear on the byte orders for floats.


25 JUL 2024 - Emerging Technologies Meeting Agenda

Date
20240725 - 10am EST / 3PM BST
Untracked attendees

Fullname, Affiliation, (optional) GitHub username
...

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[ ] Convene & roll call (5mins)
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
[ ] Welcome & Announcements

[ ] Updates on current projects
[ ] Updates on Blogs
[ ] Notices about upcoming events/deadlines

[ ] Deep Dive - Neural Interfacing

[ ] Presentation on latest Primer
[ ] Interview with external SME or industry insight

[ ] Any other Admin

[ ] Changes to program
[ ] Proposals for new Primer topics
[ ] Prioritisation changes for existing publication schedule

[ ] Call to action

[ ] POC Program
[ ] Primers
[ ] Brain Trust membership

[ ] AOB
[ ] Thanks & Close Out

Zoom Details

https://zoom.us/j/98538837792?pwd=ZHg3QVVnaCtOT0tEZSs5c0hrZTg1dz09
Meeting ID: 985 3883 7792
Passcode: 152455

Join by Phone

Find your local number: https://zoom.us/u/adl5rhui4P

Patrick Downing | GitHub 👋

Carly Richmond | Elastic

Alvin Shih / Morgan Stanley

Chaitali Ladikkar / Wellington Management

Aaman Rebello | Morgan Stanley

Peter Smulovics / Morgan Stanley

00:06:24 - 00:06:29
Keith J. O'Donnell: Opens the meeting, welcomes participants, and invites late joiners.
00:06:30 - 00:06:42
Keith J. O'Donnell: Begins with standard meeting notices, reminding attendees of necessary protocols and guidelines.
00:06:46 - 00:07:28
Keith J. O'Donnell: Reminds participants of Linux Foundation's antitrust policy, provides guidelines for project leads, and notes that FINOS meetings may be recorded for internal purposes.
00:08:00 - 00:08:14
Keith J. O'Donnell: Announces the focus topic of the meeting, which is "neural technology," and asks attendees to register their attendance via a link or QR code.
00:09:03 - 00:09:18
Keith J. O'Donnell: Introduces the agenda, including standard announcements, events, a special guest presentation on neural technology, and an open discussion.
00:09:30 - 00:10:18
Keith J. O'Donnell: Announces upcoming events, including the OSF New York in September and a movie night in Boston, focusing on gender gaps in tech.
00:10:19 - 00:10:46
Keith J. O'Donnell: Mentions the Grace Hopper Celebration happening in October, featuring a panel on AI readiness.
00:11:02 - 00:11:28
Keith J. O'Donnell: Introduces the focus topic on neural technology and explains the technology readiness scale, which ranges from early prototypes to fully mature technology.
00:11:28 - 00:13:18
Keith J. O'Donnell: Describes five key areas of neural technology: neurofeedback, brain-computer interfaces, neuroprosthetics, transcranial magnetic stimulation, and MRI. He explains the current state of each technology, highlighting its applications and readiness.
00:13:18 - 00:16:15
Keith J. O'Donnell: Discusses the relevance of neural technology in finance and fintech, introducing three main trends: cognitive augmentation, trader performance optimization, and decision-making tools. Mentions David Eagleman's research on creating new senses for humans and how neurofeedback can optimize trader performance.
00:16:18 - 00:20:07
Keith J. O'Donnell: Introduces Barry Downing from the BearBridge group, detailing Barry's experience in neuroscience, leadership, and neurofeedback training. Barry is invited to introduce himself.
00:20:08 - 00:21:38
Barry Downing: Provides a background on the evolution of neurofeedback, noting how it has transitioned from expensive clinic-only equipment to more accessible remote devices.
00:21:39 - 00:24:00
Barry Downing: Explains how neurofeedback sessions work. In Keith's case, the goal was to improve sleep quality by reducing his overactive brain state and increasing slower brain waves during rest.
00:24:00 - 00:27:00
Keith J. O'Donnell: Describes his experience using the neurofeedback tool, explaining how it gives feedback through pleasant or unpleasant sounds, which helps train the brain to enter the desired state more effectively.
00:27:00 - 00:29:20
Barry Downing: Highlights the improvement Keith has made over multiple sessions, emphasizing that his brain is learning to stay in a relaxed state for longer periods, which positively impacts sleep quality.
00:29:21 - 00:33:00
Keith J. O'Donnell: Shares his results over multiple sessions, indicating that his ability to get into the desired state has improved with practice, and elaborates on how the neurofeedback data helps identify sleep quality and cognitive behavior.
00:33:08 - 00:38:00
Barry Downing: Discusses the impact of neurofeedback for other types of individuals, from executives to athletes. The technology can address issues like sleep deprivation, stress, anxiety, and cognitive performance enhancement.
00:38:00 - 00:42:00
Keith J. O'Donnell and Barry Downing: Discuss the potential for using neurofeedback in finance, such as a cognitive plug-in to help traders better understand their behavior and avoid cognitive biases. Keith and Barry explore how neurofeedback might eventually be part of a toolset to assist in decision-making in trading.
00:42:00 - 00:44:00
Barry Downing: Explains how the technology can help traders avoid repeating the same cognitive mistakes by providing real-time feedback on their mental state during decision-making.
00:44:00 - 00:46:30
Keith J. O'Donnell: Wraps up Barry's presentation, and opens the floor for questions from the audience.
00:46:31 - 00:48:30
Aaman Rebello: Asks about the susceptibility of neurofeedback devices to external electromagnetic waves and the possibility of hacking. Barry Downing and Keith respond, indicating that signals from such devices are low-frequency, making them less susceptible to interference, though Bluetooth security is still a concern.
00:48:31 - 00:51:00
Keith J. O'Donnell: Invites more questions, thanks Barry for the presentation, and outlines next steps, including uploading a recording of the session and encouraging collaboration through the GitHub repository for Zenith.
00:51:01 - 00:53:04
Keith J. O'Donnell: Reminds participants of upcoming Brain Trust sessions and invites them to future Zenith public sessions to share and collaborate on emerging technologies in finance. Ends the meeting with closing remarks and thanks.


Relative file: URIs on CLI from PicoCLI don't work as expected

This works:
./enola rosetta --in="file:$PWD/test/picasso.yaml?context=file:test/picasso-context.jsonld" --out="fd:1?mediaType=text/turtle"

This currently does not work:
./enola rosetta --in="file:test/picasso.yaml?context=file:test/picasso-context.jsonld" --out="fd:1?mediaType=text/turtle"

The reason for this is that, as illustrated in the URIsTest#testCreate() (new, to be merged as part of #796), URI.create("file:test/picasso.yaml") creates an URI with just one single "scheme specific part" (SSP)... NOT with a query etc.
This is because file:test/picasso.yaml is not valid! I hacked also sorts of workarounds to make it; but's it's time to redo this:
Instead of file:test/picasso.yaml, just a relative --in=test/picasso.yaml must work! The way to do this is by having an URIs.create() helper which uses a TLC to look up the current BaseURI key. And on the CLI, that is the current working directory! Ergo it can be resolved relatively.
This is also the opportunity to make Context be more strongly typed, with a Context.Key.
Then use https://picocli.info/#_custom_type_converters. (no need)

This will be fixed (WIP) as part of #804.


Link without svg path

Hi, I'm creating a link between 2 nodes and seems to be created correctly but as I can see the svg path it isn't generated

Any idea what I'm doing wrong?
this is my code (It's based on DatabaseDesigner project)
    foreach (var clink in columnsLink)
    {
        var parent = ...
        var child = ...

        var nodeParent = (Table)Diagram.Nodes.First(s => ((Table)s).Name == parent.Label);
        var nodeChild = (Table)Diagram.Nodes.First(s => ((Table)s).Name == child.Label);
        var childColumn = nodeChild.Columns.First(s => s.Name == clink.Label);
        var link = new LinkModel(nodeChild.GetPort(childColumn), nodeParent.GetPort(PortAlignment.Left));
        Diagram.Links.Add(link);
    }

Hello, please show me your code for the node widget.
A link wont output anything if it can't get the positions it needs (e.g. ports not rendering, sizes not fetched)

Ok, that hint was enough, I defined PortAligment.Right to "key" column, but I'm rendering it at the left.
Thanks!!


Investigate issue with not showing notifications (for paulieparker)

No content

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @zach in #feedback.

Has this been fixed with 0.1.16 rc8?
Possible fixes to notifications not showing (setImportant is now set to true)


Update to use lowercase logrus import

Currently it is not easy to build tarmak on a case insensitive file system (such as OSX) due to it still using the old Sirupsen import path for logrus.
The official advice from the logrus repo is the all projects should always use the lower-case variant:
Seeing weird case-sensitive problems? It's in the past been possible to import Logrus as both upper- and lower-case. Due to the Go package environment, this caused issues in the community and we needed a standard. Some environments experienced problems with the upper-case variant, so the lower-case was decided. Everything using logrus will need to use the lower-case: github.com/sirupsen/logrus. Any package that isn't, should be changed.

In order to do this, we'll need to also bump the versions of some of our dependencies that were vendored whilst they still referenced the caps-variant of logrus.
All of our effected projects have been updated to use the lower-case variant, so we don't need to submit any upstream PRs. The following is a list of the dependencies that we need to update:

docker/docker (renamed to moby/moby, but github redirect will save us rewriting all imports)
docker/go-connections
opencontainers/runc
jetstack/vault-unsealer - https://github.com/jetstack/vault-unsealer/pull/11
jetstack/vault-helper - https://github.com/jetstack/vault-helper/pull/4

Once the two PRs on the jetstack projects above are merged, I will be able to put a PR into tarmak so we can get a test run performed against these new versions of dependencies.
/cc @simonswine @dippynark

Ok I have started and merged with vault-unsealer. Now I have some issues with building the pipeline, but I should be able to sort that soonish

👍 let me know once you've tagged a new release of vault-unsealer & vault-helper and I can create a similar PR here

Both should be tagged now, happy to take a look myself. I rather have the docker package renamed to be honest. Always causes confusion, as godoc for docker no longer works...


Explain principle of additive model

Explain what a additive model is and example and connection to boosting (either in intro oder gradient boosting concept chunk).

BB: we should have a chunk (7 slides or so) on GAM but in the regression chapter. this will be a good foundation for what's to come later in boosting etc. Check slides by Andi Groll (TU Dortmund) for that.


OAS20 spec

Super WIP, still experimenting and trying out things.
ERC-20/CW-20 like spec for contracts-sdk with an example implementation
TODO:

[x] do we want so support Allowances and/or any additional token metadata (e.g. see CW-20 for examples), or anything else?

probably not needed for now, can add it later in a non-breaking way (as optional extensions)

[x] cleanup the example code, currently it was more of a playground
[ ] add some more tests

We should probably include the specs contracts tests in the CI test flow and coverage.

Added


sysbuild: Fix including same sysbuild.cmake file multiple times

Fixes an issue with applications that have a sysbuild.cmake file that builds the same application many times by only including each unique sysbuild.cmake file once

Not sure about this. There may come a case where a sysbuild.cmake is expected to run some logic / update some variables for each copy of the image, in which case it should be allowed to run multiple times.
What this does help with is the more common case, where an image creates a copy of itself via its sysbuild.cmake, so it must only run once to prevent infinite recursion. But that could also be handled by adding include_guard(GLOBAL) on top of the file, while retaining the flexibility to treat other applications differently.

include_guard fixed the issue, thanks


Handle pure add/remove

Right now Diff detection only handles vault diffs that have some changes, but it does not handle a completely new file (pure add) or a removal (pure delete). This fixes to handle those cases, while still handling the base case.

@gwatts lmk what u think - would be great to release a new version once this lgtu

Thanks @nitay - I've merged your changes and pushed a new release to the chrome store which should show up soon.

awesome thanks @gwatts!


Update to CocoaPods 1.6.0

Signed-off-by: Fridtjof Mund<EMAIL_ADDRESS>

Looks like this got fixed by ef2fd8179412a512b50d67622a7127f37ec58ea2

Good, I'll close this then


Make a hotkey to copy the error of a currently selected line with a hotkey in VS Code

For example as in the image below, I want to press a hotkey and the error (expected value, found builtin type str not a value in this case) will be copied to my clipboard.

Related on Stack Overflow: How can I copy the problem message of a currently selected line with a hotkey in VS Code?

I'd adjust this proposal to be for the problem under the caret (aka "cursor"), since there can be multiple problems in a line.
Is it possible for there to be multiple overlapping problems? If that's the case, we'd need to work out what to do when that happens.

I would like for all problems that are related to the line on which the caret (cursor) is currently placed be put into clipboard when hotkey is pressed. If there is more than one error, put those errors into clipboard too.
Thank you.

This is especially useful as you can use it to take the error instantly and pipe it to a language model for it to explain it to you.
Implementing this without having vscode provide this feature is very difficult now. Hope it's added.

Copy problem message and throw to chatgpt is what I do daily. Please add this.

Two side notes:

This can be easily implemented as an extension
GitHub Copilot Chat provides code actions "Fix using Copilot" and "Explain using Copilot" that already will send the diagnostic to the LLM and even fix it for you :-)

This can be easily implemented as an extension

can you point out the vscode api that gets you this info? ♥

You can use vscode.languages.getDiagnostics(uri) (link) to get diagnostics for a particular URI.
Here's a Copilot-Chat-generated more complete step-by-step instruction (take with grain of salt but I think this is very helpful if you haven't created extensions before):
Creating a VS Code extension to copy the diagnostic message spanning your selection involves several steps. Here's a step-by-step guide:

Set up your extension project

Install Node.js and npm
Install Yeoman and VS Code Extension Generator with npm install -g yo generator-code
Run yo code to generate a new extension project
Choose TypeScript as the language
Open the generated project in VS Code

Define your command in package.json

In the contributes.commands section, add a new command. Give it a unique id and a title.

"contributes": {
  "commands": [
    {
      "command": "extension.copyDiagnosticMessage",
      "title": "Copy Diagnostic Message"
    }
  ]
}

Implement your command in extension.ts

Import the necessary modules from vscode
In the activate function, register your command using vscode.commands.registerCommand
In the command callback, get the current editor and selection
Use vscode.languages.getDiagnostics to get the diagnostics for the current file
Filter the diagnostics to those that overlap with the selection
Copy the messages of the overlapping diagnostics to the clipboard using vscode.env.clipboard.writeText

import * as vscode from 'vscode';

export function activate(context: vscode.ExtensionContext) {
  let disposable = vscode.commands.registerCommand('extension.copyDiagnosticMessage', async () => {
    const editor = vscode.window.activeTextEditor;
    if (editor) {
      const selection = editor.selection;
      const diagnostics = vscode.languages.getDiagnostics(editor.document.uri);
      const overlappingDiagnostics = diagnostics.filter(diagnostic => diagnostic.range.intersection(selection));
      const messages = overlappingDiagnostics.map(diagnostic => diagnostic.message).join('\n');
      await vscode.env.clipboard.writeText(messages);
      vscode.window.showInformationMessage('Diagnostic messages copied to clipboard.');
    }
  });

  context.subscriptions.push(disposable);
}

Test your extension

Press F5 to run your extension in a new Extension Development Host window
Open a file with diagnostics and select some text
Run your command from the Command Palette (F1, then type "Copy Diagnostic Message" and press Enter)

Remember to replace "extension.copyDiagnosticMessage" with the actual command ID you used in your package.json.

I use vscode extention Problems: Copy
setting :
"problems-copy.useSimpleTemplate": true,
"problems-copy.simpleTemplate": "${severity}, "${message}", ${source}(${code})",
I hit ctrl +shift+c to copy all the prolbem and paste to chatGPT. I do not even need to say "fix this". GPT would just pick it up.

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


F2C: optional case-sensitivity for variables/symbols

convert_to_lower_case() if not variable/symbol .case_sensitive=True
Imported for things like:
... = threadIdx.x
cudaMalloc(...)

There seems some test failures after the latest rebase - hold off on merging until this is fixed.


fixed typos in help-token

fixed typos
improved syntax

[ ] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[ ] Ensure that the pull request title represents the desired changelog entry
[ ] Please describe what you did
[ ] Link to relevant issues in GitHub or Jira
[ ] Link to relevant pull requests, esp. upstream and downstream changes
[ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

@igalg - asking for review and merge.


How to Create a service principal just for PowerShell?

I want to create a service principal to login to Azure and do things.
I can logon using my Windows LIve ID, but that can't be automated. The solution is to create an SP, but this does not help me? What is 'demoapp' if all I want to do is use PowerShell for example to create a storage account.

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

ID: 11cb61ed-1f1b-22ee-11a3-775bc9001538
Version Independent ID: 84b2cbcb-1f11-9a6d-23fd-5c8d76453fa8
Content: Create an Azure service principal with Azure PowerShell
Content Source: docs-conceptual/azurermps-6.6.0/create-azure-service-principal-azureps.md
Product: powershell
GitHub Login: @sptramer
Microsoft Alias: sttramer

The identifier demoapp is a placeholder. Service Principals do not need to be tied to an application, but can be. If you look at the full documentation for New-AzureRMADServicePrincipal you will see that the -ApplicationId parameter can be omitted.
In fact to create a generic service principal of the sort which may be best for scripting, including one with a randomized password generated for you, you can simply run the first example in the cmdlet documentation. https://docs.microsoft.com/en-us/powershell/module/azurerm.resources/new-azurermadserviceprincipal?view=azurermps-6.6.0#examples


Reduce binary size

Is your feature request related to a problem? Please describe.
We are using very diskspace constrained devices, but would like to add thin-edge to them.
When mosquitto is already installed and only the tedge-binaries are missing there are ~3MB left.
Describe the solution you'd like
I read here that rust binaries can be minimized.
Some of the steps are already done in thin-edge and adding strip is not a big deal.
Interessting are the steps Optimize libstd with build-std and Removing libstd with #![no_std], but i don't know rust so well that i could do it myself.

Optimizing libstd with build-std is indeed an idea to explore.
I did a quick experiment. The size is reduced by 15%
$ cargo build --release
$ ls -lh target/release/tedge*
-rwxrwxrwx 2 didier didier 3.6M Sep 23 14:55 target/release/tedge
-rwxrwxrwx 2 didier didier 4.3M Sep 23 14:55 target/release/tedge_agent
-rwxrwxrwx 2 didier didier 4.7M Sep 23 14:55 target/release/tedge_mapper

$  cargo +nightly build -Z build-std=std,panic_abort --target  x86_64-unknown-linux-gnu --release
$ ls -lh target/x86_64-unknown-linux-gnu/release/tedge*
-rwxrwxrwx 2 didier didier 3.0M Sep 23 15:08 target/x86_64-unknown-linux-gnu/release/tedge
-rwxrwxrwx 2 didier didier 3.6M Sep 23 15:09 target/x86_64-unknown-linux-gnu/release/tedge_agent
-rwxrwxrwx 2 didier didier 3.9M Sep 23 15:09 target/x86_64-unknown-linux-gnu/release/tedge_mapper

Removing libstd with #![no_std] is a complete different story that would imply a lot of code updates. I don't even think this is doable at this stage of the project.
That said this issue needs to be addressed.

Reducing the number of executables is likely the most promising approach.
Reducing the number of dependencies must be explored too.

@toewsar  thin-edge.io now uses a multi-call binary approach. This reduces the overall binary size from ~40MB to ~8MB (uncompressed).

Additional packers such as upx can be used to further decrease the binary sizes if further reduction is required (and the performance tradeoffs are ok).


Implemented the Data Service for Exercise class.

Database access for the Exercise class. Missing equal (==) method implementation.

@nicanorgarcia can you rebase this branch onto the current develop to resolve the conflicts? And have a look at my comments. In particular the one about getExercises. All the other stuff is kind of optional

@nicanorgarcia Any updates on this one?

I will delete this branch, had to many conflicts, started a new one


Science sensor system causes glitches in sim

Hi @mabelzhang,
I've been testing the  empty_world env with the science sensor system in the loop and it seems like the queries are causing significant slowdowns. As a result the vehicle appears to be glitching along the navigated track.
https://user-images.githubusercontent.com/7927479/158451273-389a4c50-e13a-4581-8a2d-d25c64254a0c.mp4
The temperature values produced for temperature seem to be correct.
To reproduce run the lrauv-application with the following inputs:
./bin/LRAUV -x "run Science/profile_station.xml"
Thanks

Hey Ben, I was able to reproduce this on main.
However, when I switch to my trilinear interpolation branch in #127, the lag disappears. So, I recommend getting my PR merged so we have all the improvements.
That seems the easiest solution.
I also noticed main is still printing a lot of garbage from my old (3 months now) interpolation code, which has been refactored into its own class in #127 and has cleaner printouts now. Definitely a better experience.

Quick test to switch to barycentric interpolation in #127 by this line in ScienceSensorsSystem.cc:
  this->dataPtr->interpolation.SetMethod(BARYCENTRIC);

Still no lag.
So I'm guess the lag might come from infrastructure.
That of course says nothing about whether interpolation is correct, which we should check separately. But seems like things are better with the new code, not worse.

I added a few IGN_PROFILE lines. See timelines produced below.
You were right about the kNN search being the bottleneck. FindTrilinearInterpolators() takes 800 ms.
In comparison, publishing point clouds take 30 ms.

resolved in #191


Question: removal of "if exists"

I saw that if exists was removed in https://github.com/alimanfoo/petl/commit/62f35c542119bc32e782681a15381972072e043e#diff-57ad97c12e2a16f74c54d7bb4d8e332cL252 - any reason why? Now that when I try to use create=True and drop=True with todb and the target table does not exist, it will raise exception.

NVM i saw this https://github.com/alimanfoo/petl/issues/317 - but this is maybe some kind of annoying know that I have to use different params depending on whether the table previously existed, with an intention to drop whatsoever.

Hi Jiayu, thanks for the message. As you saw in #317 it is not
straightforward to support "IF EXISTS" in a way that is portable across all
major databases. I realise it is annoying that you have to use different
params depending on whether or not the table exists. If you have a proposal
I'd be happy to consider it.
On Tuesday, May 17, 2016, Jiayu Liu<EMAIL_ADDRESS>wrote:

NVM i saw this #317 https://github.com/alimanfoo/petl/issues/317 - but
this is maybe some kind of annoying know that I have to use different
params depending on whether the table previously existed, with an intention
to drop whatsoever.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/alimanfoo/petl/issues/376#issuecomment-219633804

--
Alistair Miles
Head of Epidemiological Informatics
Centre for Genomics and Global Health http://cggh.org
The Wellcome Trust Centre for Human Genetics
Roosevelt Drive
Oxford
OX3 7BN
United Kingdom
Email<EMAIL_ADDRESS><EMAIL_ADDRESS>Web: http://purl.org/net/aliman
Twitter: https://twitter.com/alimanfoo
Tel: +44 (0)1865 287721


V1.2.0

https://github.com/sharkusmanch/playnite-pcgamingwiki-metadata-provider/issues/49
https://github.com/sharkusmanch/playnite-pcgamingwiki-metadata-provider/issues/48


stderr path is not consistent with "trial ls" output information

same issue, there is a extra ".nni"  in my case

Fixed in master branch.


Two viewers next to each other

Hello.
I need to create an app that will have two viewers next to each other in the same page. The idea is to compare two microscopy images, and when you drag/move one or zoom, the other one should also be moved/zoomed.
I started by looking for the events that viewer is publishing, and I see that there are dicommicroscopyviewer_move_started and dicommicroscopyviewer_move_ended events, but they are never fired.
Do you have any ideas how this can be done?

Addressed by https://github.com/ImagingDataCommons/dicom-microscopy-viewer/pull/155


Typescript breakpoints no longer work since 1.25

VSCode Version: 1.25 & 1.26 Insiders. 1.24.1 is working properly.
OS Version: Fedora 28 & Mac OS High Sierra (same symptoms)

Steps to Reproduce:

Start our Node.js server app via launch.json or attach to a process started from the terminal.
Try to set a breakpoint in the server .ts files.

Does this issue occur when all extensions are disabled?:
Yes, it's occurring with a vanilla Insiders Edition, too.
Our Typescript directory structure is the following:

src/... - Typescript source files
build/... - Built Javascript files
build/src/... - Source maps

E.g. src/app.ts is the main source file, build/app.js is the Javascript, build/src/app.js.map is the source map.
The Javascript files point to the source maps at their end with a relative path e.g.
//# sourceMappingURL=../src/server/app.js.map`.

The source maps are built with gulp and they point to the exact absolute source path at their end e.g.
"sourceRoot": "/home/gombosg/myApp/src"`

outFiles is properly set in launch.json, but simply attaching to a running process worked, too.
This used to work perfectly, breakpoints always worked, but they appear as 'unverified' (greyed and hollow) since 1.25.  Downgrading back to 1.24.1 helped though.
Let me know if you need some special logs.

Well, it may not be connected to VSCode itself (but e.g. a Node debug adapter component) but something that has been working so far did break on a certain VSCode version update.

I made a simple test case which works in 1.24 but doesn't work in 1.25.
tsTest.zip
Instructions:

Run build.sh
Set a breakpoint in build/hello.ts
Run with F5, it's already configured.
For me it stopped at the breakpoint in 1.24, didn't stop in 1.25.

@gombosg does your test case work in the latest Insiders?

@weinand Nope. 1.25 and 1.26 Insiders seem to be affected.

Apparently with the mapRoot and sourceRoot tsconfig options, tsc writes out absolute local paths for sourceMappingURL and sourceRoot. I think this is wrong, they should be file URIs and are usually relative paths. I just "fixed" this last month so that / urls can be resolved from the root of a webserver. Since tsc is doing this, I'll have to support this format too.

In my defense, Chrome devtools doesn't handle windows-style local paths which is what TS outputs on Windows, so I will file a bug on Typescript. It does on MacOS though.

I filed Microsoft/TypeScript#25587

@roblourens Thanks a lot! Also, tsc can be configured from gulp etc. and absolute paths can be set anytime. I actually set absolutes source map paths in the gulp config file because it didn't work other way, it was trial and error. ☺

FYI as a quick fix I set the source map URLs in Gulp to relative by setting a relative sourceRoot in the appropriate sourcemaps.write command. This works with 1.25 properly. (But unlike the example I attached before, it's not a native tsconfig.json solution.)

I am also having the same issue. I was working on two typescript projects with different code-bases that have been working with breakpoints for at least the past year and both of them stopped working with the update.  :(
I am not using gulp and don't plan to implement it for this issue.  Any idea when this might be fixed so I can plan accordingly?

It appears that if I remove mapRoot from my tsconfig.json the breakpoints are properly handled and I can now debug again! :)
Here are my configs in case others experience issues to aid in possible troubleshooting.
Before
{
  "extends": "../tsconfig.json",
  "compilerOptions": {
    "declaration": false,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "lib": [
      "es7",
      "dom"
    ],
    "mapRoot": "../dist/server",
    "module": "commonjs",
    "moduleResolution": "node",
    "outDir": "../dist/server",
    "sourceMap": true,
    "strictNullChecks": false,
    "noUnusedLocals": false,
    "target": "es6",
    "typeRoots": [
      "../node_modules/@types",
      "./types"
    ]
  }
}

After
{
  "extends": "../tsconfig.json",
  "compilerOptions": {
    "declaration": false,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "lib": [
      "es7",
      "dom"
    ],
    "module": "commonjs",
    "moduleResolution": "node",
    "outDir": "../dist/server",
    "sourceMap": true,
    "strictNullChecks": false,
    "noUnusedLocals": false,
    "target": "es6",
    "typeRoots": [
      "../node_modules/@types",
      "./types"
    ]
  }
}

This will be fixed in TS' end in TS 3.0, but I'm trying to get a fix out on our end in Insiders.

I think the issue I was experiencing was actually from issue #53785 and might be unrelated from what was reported in this ticket.

@paustint Since you said it's related to mapRoot, this is probably the right issue.

Please try this workaround for mac/linux. Add this to your launch config:
"pathMapping": {
    "/": "/"
}

You will get an warning that the property is "not allowed", ignore it.

@gombosg Life saver! changed path to relative in gulp and I have my breakpoints again. Thank you!

Also having this problem - adding pathMapping has no effect for me (having this problem on mac). I'm not using gulp, though. Latest insiders doesn't work either. I'm running Jest tests using ts-jest.

Never mind my comment above. This is actually a Jest problem for me. Unfortunately both vscode and Jest seem to have problems related to debugging in recent release. For me, the latest release of vscode works with jest@22 + ts-jest but not jest@23.
https://github.com/facebook/jest/issues/6683

There will be a fix in tomorrow's insiders build, please try it out.

I wasn't able to break with:
tsconfig.json:
{
    "include": [
        "src/**/*"
    ],
    "compilerOptions": {
        "sourceMap": true,
        "sourceRoot": "src/",
        "outDir": "build/",
        "mapRoot": "build/"
    }
}

but was after removing the mapRoot and sourceRoot entries.

3.0.1

Yeah with those options you get //# sourceMappingURL=../src/build/foo.js.map which is nonsense

Verified for<EMAIL_ADDRESS>


Could not open test file

Hi,
if I double click on a unit test in AxoCover I will get the following error message in a message box:
Could not open file: .
Although it opens the file but not jumping to it actually.
What can I do about it?
BR,
Hendrik

Hmm, maybe there is a problem with reaching the specific line in the file. This is likely a bug. It could also be that the source file has been modified since test build - note AxoCover will NOT rebuild your tests when you run them, you need to do it manually.

Hmm it is completely rebuilt before each test run. Can I do anything else?
BR,
Hendrik Freund
Software Engineer (8SIN)
Rohde & Schwarz INRADIOS GmbH Nossener Brücke 12, 01187 Dresden, Germany
Phone: +49 (0)351 340907-70
Fax: +49 (0)351 340907-99
Web: http://www.inradios.com/
INRADIOS GmbH; Geschäftsführer (Managing Directors): Dr. Steffen Bittner, Dr. Marco Krondorf; Sitz (Registered Office): Dresden; WEEE-Reg.-Nr. (WEEE Register No.): DE 81158062; USt-IdNr. (VAT Identification No.): DE 815159074; HRB (Commercial Register No.): 28693; Amtsgericht (Registration Court): Dresden
This email and any attachments are intended only for the person to which this email is addressed and may contain confidential and/or privileged information. If you received this email in error, please do not disclose the contents to anyone, but notify the sender by return email and delete this email (and any attachments) from your system.
From: Péter Major<EMAIL_ADDRESS>Sent: Wednesday, February 7, 2018 10:36 AM
To: axodox/AxoCover<EMAIL_ADDRESS>Cc: Freund Hendrik 8SIN<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: [Newsletter] Re: [axodox/AxoCover] Could not open test file (#146)
Hmm, maybe there is a problem with reaching the specific line in the file. This is likely a bug. It could also be that the source file has been modified since test build - note AxoCover will NOT rebuild your tests when you run them, you need to do it manually.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/axodox/AxoCover/issues/146#issuecomment-363710814, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AiVmPTzh-whcpTShqrOuLAF7DWsrk8Giks5tSW6IgaJpZM4R0Npt.
Content provided within this e-mail including any attachments, is for the use of the intended recipients and may contain Rohde & Schwarz company restricted information. Any unauthorized use, disclosure, or distribution of this communication in whole or in part is strictly prohibited. If you are not the intended recipient, please notify the sender by reply email or by telephone and delete the communication in its entirety.

I will review the affected part of the code and add some logging sometime this week. With that we should be able to get a better look at the problem. If you can share a sample project which reproduces the issue that would be very useful.

I attached a sample project where the issue happens on my side.
Hendrik Freund
Software Engineer (8SIN)
Rohde & Schwarz INRADIOS GmbH Nossener Brücke 12, 01187 Dresden, Germany
Phone: +49 (0)351 340907-70
Fax: +49 (0)351 340907-99
Web: http://www.inradios.com/
INRADIOS GmbH; Geschäftsführer (Managing Directors): Dr. Steffen Bittner, Dr. Marco Krondorf; Sitz (Registered Office): Dresden; WEEE-Reg.-Nr. (WEEE Register No.): DE 81158062; USt-IdNr. (VAT Identification No.): DE 815159074; HRB (Commercial Register No.): 28693; Amtsgericht (Registration Court): Dresden
This email and any attachments are intended only for the person to which this email is addressed and may contain confidential and/or privileged information. If you received this email in error, please do not disclose the contents to anyone, but notify the sender by return email and delete this email (and any attachments) from your system.
From: Péter Major<EMAIL_ADDRESS>Sent: Wednesday, February 7, 2018 11:23 AM
To: axodox/AxoCover<EMAIL_ADDRESS>Cc: Freund Hendrik 8SIN<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: [Newsletter] Re: [axodox/AxoCover] Could not open test file (#146)
I will review the affected part of the code and add some logging sometime this week. With that we should be able to get a better look at the problem. If you can share a sample project which reproduces the issue that would be very useful.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/axodox/AxoCover/issues/146#issuecomment-363723719, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AiVmPUqdpQTQ_mwYOV41FwfiiOo3mwyWks5tSXmagaJpZM4R0Npt.
Content provided within this e-mail including any attachments, is for the use of the intended recipients and may contain Rohde & Schwarz company restricted information. Any unauthorized use, disclosure, or distribution of this communication in whole or in part is strictly prohibited. If you are not the intended recipient, please notify the sender by reply email or by telephone and delete the communication in its entirety.

Hmm... It seems GitHub is not supporting these kind of email attachments. You could either drag and drop it on the Web based UI, or send it to AxoCover [at] outlook [dot] com.

WpfApp1.zip

Thank you, I will get back to you after I have checked the issue, likely later this week.

I tried to reproduce the issue, but for me it seems to work (I am using latest VS2017 + latest AxoCover).
If you have 20min I would suggest you to try to debug issue locally. For this you can fetch the code from GitHub, then build it (you will need vs2015+ and Visual Studio SDK installed). The issue will be around the call to method NavigateToMethod in class EditorContext.

Put a guide here on how to build: https://github.com/axodox/AxoCover/wiki/How-to-build-AxoCover%3F
I will also create one about how the code is laid out.

I too suffer this issue with all my diverse projects.  Double clicking opens the file, but stays at the top.  The error dialog shows the correct file name.  This issue applies to both Tests tab and Reports tab navigation.
However, the Test tab Debug button works fine.  Here is a project with the issue:
https://github.com/kaosborn/SimpleApps
Strange you can't reproduce.  My configuration is current and simple:
Visual Studio 2017 Community 15.6.4
AxoCover <IP_ADDRESS>
Windows 10 Pro build 1709
And thanks for AxoCover!  You are definitely on the right track.

@kaosborn I tested AxoCover with your SimpleApps repo, I have the exact same software versions as you list and it works for me. Could it be some compatibility problem with another extension?
Here is how to debug (no need to build or install anything!):

Go to the releases and download the vsix and corresponding source code.
Install the VSIX. + Unpack the source.
The vsix has all the PDB in it, when you run tests the path of installation is printed out with some test DLL paths, e.g. >> Loading assembly from C:\Users\Axodox\AppData\Local\Microsoft\VisualStudio\15.0_46f4e761\Extensions\honzmv02.jc5 \ MSTestAdapter\Microsoft.VisualStudio.TestPlatform.MSTest.TestAdapter.dll...
Add  the above folder to your symbol's path.
Open AxoCover.sln and then navigate to D:\dev\AxoTools\AxoCover\ViewModels\TestExplorerViewModel.cs and add a breakpoint to private void NavigateToTestItem(TestItemViewModel testItem) - this is the method used to navigate to test code.
Open other VS with your problematic project.
Attach the AxoCover VS to this.
Reproduce problem.
Check what is going wrong.

Well I gave it a go with release 1.1.336 but any breakpoints show the warning
The breakpoint will not currently be hit. No Symbols have been loaded for this document.
And indeed the set breakpoint is not hit.  I assume this is because building the project failed. (Or maybe I set up the symbols directory wrong?)
The first build error is:
...\easyhook.h(45): fatal error C1083: Cannot open include file: 'winternl.h': No such file or directory
Bummer. As far as other extensions go, not much out of the usual except perhaps Sandcastle Help File Builder. An expired Visual Studio 2017 Enterprise is present if that matters.

You don't need to build it, however you need to load the symbols from the extension's directory. You can do this by opening the Modules window from Debug / Windows, selecting the AxoCover DLLs and right click Load symbols.
If you still want to build it, please refer to this.

Ah, Debug>Windows>Modules then Load Symbols. That did the trick. A couple items of note:

The extension gets automatically updated which desynchronizes the source. Disabling automatic updates of extensions in Tools>Options solved this.
I'm still using release-1.1.336 because it is not clear what release maps to the new v<IP_ADDRESS>.

So now I can drill down into the codebase. In method NavigateToCodeElement, line is calculated as 0.
I've tried inspecting codeElement but VS won't let me because it is native code.  Strange, I've enabled Native Code Debugging in Project>Properties but still can't inspect native code.
So now I'm stuck.  Any advice?

CodeElement is a Visual Studio COM component. I used to debug these by capturing their properties in variables (watches and immediate window seem to not work with them). But their source is closed and native, so we cannot really look inside.
I can add some code to clamp line argument of NavigateToFile between 1 to number of lines in file. That would not solve the issue, but would at least open / switch to the file without showing an error.
Other notes:

I have added more information about debugging here: https://github.com/axodox/AxoCover/wiki/Debugging-issues
Please refer to releases for mapping (see the version number in the #Uri part).

I looked at the code, and at first glance the issue could be:

VS somehow fails to calculate the line number.
The code element is not the right one, so the issue is coming from earlier calculations.

https://github.com/EWSoftware/SHFB/issues/594


reorder readme to appeal to new users

1: usage ... user can see how this is used / if it solves their problems
2: installation ... users see how to install
3: upgrading

Tweaked things, let me know what you think :)


feat: Edit polish

Error when editing log dialog and saving it as a new train dialog
add tips on icons when you are editing a train dialog
Can't save with dummy last round, need to clean
Make edit icons look better
the bot response is added below the existing bot response / not above as expected.
Switch sub-bubble text to always be "user" and "bot:"
Text in webchat control for the source: would be good to say “User” & “Bot”
Sometimes the source is: “Bot at Invalid date”
Refactor webchat rendering
Better way to show that next step bot response when on bottom of page

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update shaderwriter package

The issue encountered here comes from the use of GCC 9.
Is there a way to force GCC 10 ?


feat: add inclusive param for iter until

Added inclusive boolean parameter for later ..= and ..<

Pull Request Test Coverage Report for Build 2643
Details

0 of 12 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 79.31%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

builtin/iter.mbt
0
12
0.0%

Totals

Change from base Build 2642:
0.1%

Covered Lines:
3381

Relevant Lines:
4263

💛  - Coveralls


fix for CqlInsert.SetTimestamp

CqlInsert.SetTimestamp inserts timestamp in milliseconds. According to specs it should be in microseconds. The fix makes timestamp calculation for inserts same as update and delete statements already have

Thanks for the fix!


build error or source error or my setup problem or as expected?

I took delivery of https://github.com/googlei18n/noto-source/tree/master/src/NotoSansBalinese
and built a font from source using
./build src/NotoSansBalinese/NotoSansBalinese-MM.plist
command and obtained the following ttf
NotoSansBalinese-Regular.ttf.zip
I ran it through noto_lint.py and the following errors appeared (fragment of the list):
E <bounds/glyph/ymax> Real yMax for glyph 267 (g178) is 2162, which is higher than the font's sTypoAscent (1069), resulting in clipping.
E <bounds/glyph/ymin> Real yMin for glyph 267 (g178) is -1118, which is lower than the font's sTypoDescent (-726), resulting in clipping.
E <bounds/glyph/ymax> Real yMax for glyph 268 (g179) is 1118, which is higher than the font's sTypoAscent (1069), resulting in clipping.
E <bounds/glyph/ymin> Real yMin for glyph 268 (g179) is -1118, which is lower than the font's sTypoDescent (-726), resulting in clipping.
E <bounds/glyph/ymax> Real yMax for glyph 269 (g180) is 2162, which is higher than the font's sTypoAscent (1069), resulting in clipping.
E <bounds/glyph/ymin> Real yMin for glyph 269 (g180) is -1118, which is lower than the font's sTypoDescent (-726), resulting in clipping.
E <bounds/glyph/ymax> Real yMax for glyph 270 (g181) is 1570, which is higher than the font's sTypoAscent (1069), resulting in clipping.
E <bounds/glyph/ymax> Real yMax for glyph 272 (zerowidthjoiner) is 1667, which is higher than the font's sTypoAscent (1069), resulting in clipping.
E <bounds/glyph/ymax> Real yMax for glyph 273 (zerowidthnonjoiner) is 1667, which is higher than the font's sTypoAscent (1069), resulting in clipping.
E <bounds/font/ymax> Real yMax 2162, but it should be less than or equal to the value of Ascent in 'hhea' table, which is 1069.
E <bounds/font/ymin> Real yMin is -1486, but it should be greater than or equal to the value of Descent in 'hhea' table, which is -726.
I looked at the ttf using glyphs and glyphs starting with g129 look outsized when compared to the uni* glyphs.

Is it build error or source error or my setup problem or as expected?

it was my build setup problem

Phew! :sweat_smile:


Walking speed seems too slow

When wandering around it feels like I'm crawling a bit - the running speed +10% feels about "natural" for the environment

OMG, yes. Holding sprint button for every move so far was a hussle.


Split utils

Fixes #129

Codecov Report

Merging #162 (9d47460) into develop (aa3dd02) will increase coverage by 0.58%.
The diff coverage is 63.41%.

:exclamation: Current head 9d47460 differs from pull request most recent head 9d831b2.


new pydf

Codecov Report

Merging #354 (0bf9d99) into master (34f8b6b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #354   +/-   ##
=======================================
  Coverage   92.57%   92.57%
=======================================
  Files          23       23
  Lines        1280     1280
  Branches      140      140
=======================================
  Hits         1185     1185
  Misses         68       68
  Partials       27       27

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 34f8b6b...0bf9d99. Read the comment docs.


Review of all visibility attributes

Closing in favour of https://github.com/iotaledger/iota-sdk/issues/65


threaded a timout through fabric

I think you can drop the custom timeout type. So within an application we only care about the deadline. So you should be able to pass around time.Time as the deadline. Might make sense to encapsulate this in a Context, but that also might just obscure the thing we care about.
When passing the the timeout between apps, you'll need to translate the deadline into a timeout. So at the point that you send a message to another component, you figure out how much time is left till the deadline and send that as the timeout to other component.
Does that make sense? If not, we can talk it through

I think you can drop the custom timeout type. So within an application we only care about the deadline. So you should be able to pass around time.Time as the deadline. Might make sense to encapsulate this in a Context, but that also might just obscure the thing we care about.
When passing the the timeout between apps, you'll need to translate the deadline into a timeout. So at the point that you send a message to another component, you figure out how much time is left till the deadline and send that as the timeout to other component.
Does that make sense? If not, we can talk it through

Yep! All makes sense to me. Used a custom type here to be a bit more explicit, but if thats not necessary then all good!

I had a few minor nits, but overall made sense, I think

One last thought. Can we check for a 0 deadline in the router and, if it's zero, either use the default timeout or don't set a timeout (based on whether the xgress impl dial has a configurable timeout)?
So if we have a deadline, use the minimum of the deadline and the xgress impl timeout.
If we don't have a deadline, revert to the default xgress impl timeout behavior


maybe not compatible

When I copy in mobile qq(Chinese communicate software), the copy can't success. but 'success' event can trigger. Then I try to open "https://clipboardjs.com/" in my mobile qq, the "copy button" makes no effect, but the "copy button" with icon can work. It makes me confused vary much.Why?

Please provide a JSFiddle that reproduces this problem, otherwise it's impossible for me to debug. Thanks!


Update flyway-core to 10.21.0

About this PR
📦 Updates org.flywaydb:flyway-core from 9.22.3 to 10.21.0 ⚠
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.flywaydb", artifactId = "flyway-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.flywaydb", artifactId = "flyway-core" }
}]

labels: library-update, early-semver-major, semver-spec-major, commit-count:1

Superseded by #336.

Superseded by #337.


What tool do you use to visualize the nice bike scene in the readme ?

Basically what is the recommended way to visualize RGBD?

Thanks!
I wonder if would you be able to share the script you used to visualize the demo scenes? You must have really good config for such nice visualization.

Sorry for the delayed response, here is a Google Colab with code to create a point cloud from the middlebury predictions: https://colab.research.google.com/drive/1G8WJCQt9y55qxQH6QV6PpPvWEbd393g2?usp=sharing


Page parts/tabs cannot be made visible dynamically

I have some code that enables different parts of a page dynamically, Like the example in the docs
https://docs.microsoft.com/en-us/dynamics-nav/Visible-Property but with page parts too.
This is in the Windows client on 11.0.20783 and 12.0.21229.
If the user does no customisation it appears to still work, but if the user brings the "shipping tab" onto the page when the "payments tab" is not visible it will not become visible again. If the user resets the page when the tab should be being displayed it returns.
If the condition isn't a simple boolean flag (eg it's an Option comparison) the tab(s) cannot be brought back onto the page.
This code is working fine in NAV2017.

Does it work if instead of customization using the new web client Personalization feature?
In general, since this is NAV 2018 issue/question you should contact Support through regular channels.

Umm, my understanding is ...
If you remove the "shipping tab" with a profile the web client personalisation feature is disabled.
You can't add fast tabs or fact boxes with the web client personalisation (even if you previously "hid" the fact box).
The web client "designer" isn't "personal".
So what exactly do you mean?
Nb, is the "regular channel" still "pay to file a bug report then beg for the money to be returned" style?

My apologies, I just noticed this is related to the windows client and not to the new Personalization/Designer features in the web client. In that case it is even more out of scope for this forum:
https://github.com/Microsoft/AL/wiki/Frequently-Asked-Questions#i-found-an-issue-on-nav-2018-what-do-i-do
https://github.com/Microsoft/AL/wiki/Frequently-Asked-Questions#i-found-an-issue-not-related-to-al-development-what-do-i-do
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/

Sigh,  None of those links say that.

The bug is in V12.0.21229. as well as 2018.
The code is in a V2 extension using vscode and AL.
The only mention of the windows client on that page is in the comments BY ME where I indirectly reference this issue.
It is not, currently, a customer facing issue and when it becomes so I have a kludgy (and really ugly looking) workaround.
Your FAQ/Wiki explicitly references "On-Premise" issues as in scope. (Twice)

Note: I'm actually following your first FAQ reference because I'm raising the bug with you as it replicates on 12.0.21229 and only when (if? → kludgy workaround) it becomes a customer issue would I request that you incur the additional cost of making a 2018 update.
So do you want to fix this V12, vscode, On-premise, AL bug in 'main' ?

Hi @rdebath,
Apologies for a late reply on this issue.
I have tested this now on the latest versions of AL extension and Windows client, and could not reproduce it.
Could you please double check if my steps match your initial description?
Created an AL extension like this:
pageextension 50109 MyExtension109 extends "Customer Card"
{
    layout
    {
        modify(Payments)
        {
            Visible = NOT "Allow Line Disc.";
        }
    }
}

Then, testing in Windows client:

I've just re-confirmed the bug on V11cu8 and 12.3.23730.
However, like yourself I cannot reproduce the bug on V13 (13.0.24266)
So I expect it's on Vnext of BC (but it cannot confirm as bcinsider.azurecr.io/bcsandbox:gb is currently broken) and this issue can be closed.

Thanks for the confirmation.


Subworkflow in progress but the workflow is completed

Hi!
I have a workflow that I splitted in few sub workflows, and one of them sometimes is work perfectly but many times it keep in progress indefinitely, as you can see in the screenshot attached.
Let me know any other information that can be useful.
UPDATE: After start to deploy all workflows everytime and not only the one updated this behaviour seems to stopped.
Regards
Snippet sub_workflow task
{             "name": "Simulator",             "taskReferenceName": "sm_rs",             "type": "SUB_WORKFLOW",             "subWorkflowParam": {               "name": "sm_rs"             },             "inputParameters": {               "connectionTimeOut": "${workflow.input.connectionTimeOut}",               "readTimeOut": "${workflow.input.readTimeOut}",               "headers": "${workflow.input.headers}",               "url": "${workflow.input.url}",             }           }
Subworkflow status

Workflow status (used as subflow)

Main workflow

@btafarelo Could you please let us know the result of manually forcing the evaluation of the parent workflow? This could be done by invoking this API manually using cURL or swagger -


For each row we have the stake address, then the list of rewards for that address from the database (ie DbLovelace) and then the rewards from the ledger.

Interestingly if I take out the special handling for the Shelley epoch then there is no validation failure.
This means its a regression in ledger-specs .


Refactor module sync control

Description
Changes proposed in this pull request:

Refactor ModuleTemplate synchronization logic according to the #542
Adjust the test cases

Related issue(s)
See also: #542

/hold

Manual tests performed:
========================================
Testing single module sync (no beta/internal)
========================================

1) Create kyma and moduletemplate without 'sync' labels
   - should sync
   * OK

2) Create kyma and moduletemplate with empty 'sync' labels
   - should sync
   * OK

3) Create kyma with 'sync=false' and moduletemplate with 'sync=true' labels
   - should not sync
   * OK

4) Create kyma with 'sync=true' and moduletemplate with 'sync=false' labels
   - should not sync
   * OK

5) Create kyma with 'sync=true' and moduletemplate with 'sync=true' labels
   - should sync
   * OK

========================================
Testing Beta/Internal feature
========================================

1) Create standard ModuleTemplate(sync enabled) and a beta one(sync enabled)
   Enable sync on Kyma object
   - only standard module should sync
   * OK

2) Like 1) but in addition enable internal on the Kyma
   - only standard module should sync
   * OK

3) Like 1) but in addition enable beta on the Kyma
   - both modules should sync
   * OK

4) Create standard ModuleTemplate(sync enabled) and an internal one(sync enabled)
   Enable sync on Kyma object
   - only standard module should sync
   * OK

5) Like 4) but in addition enable beta on the Kyma
   - only standard module should sync
   * OK

6) Like 4) but in addition enable internal on the Kyma
   - both modules should sync
   * OK

the change is included in https://github.com/kyma-project/lifecycle-manager/pull/553


Update README.md

TinyUrl byte limits added

Updated in https://github.com/alcor/itty-bitty/wiki. Thanks!


Mirror'd vertices trip up the exporter

I think vertices which are in the middle of the mirroring cause the exporter to get tripped up. Investigate further.

This seems to have been fixed at some point, but UV's are not exported correctly, so we're not finished yet!

Fixed


WoW

[Enter feedback here]

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

ID: f35b206b-87eb-cca0-8854-d1fcd6d8732f
Version Independent ID: 11c11e7b-5c02-ee1a-e17d-f5cb4cafbab8
Content: What is Model Builder and how does it work? - ML.NET
Content Source: docs/machine-learning/automate-training-with-model-builder.md
Product: dotnet-ml
GitHub Login: @luisquintanilla
Microsoft Alias: luquinta

@bornwish2 Hello. You didn't leave a message on your issue. I'm assuming you meant to give praise (considering the title is WOW) if not, please feel free to reopen and comment.


walkthrough: walkthrough meadow generates old dependencies for regions and population

One-liner
When running walkthrough meadow the options Load countries regions in the script and Load population in the script need to be updated
Environment

python -V: Python 3.11.1
Operating system: macOS Ventura 13.3.1
Working with local, staging or live: None (or local)

Context & details

When selecting these two options at the bottom of walkthrough meadow I add countries regions and population as dependencies, but

We can't call data://garden/reference via paths.load_dependency("reference"), because we get this error:

etl.helpers.NoMatchingStepsAmongDependencies: No steps found among dependencies of current ETL step, that match the given specifications.

Population needs to be updated to data://garden/demography/2023-03-31/population instead of data://garden/owid/latest/key_indicators

When fixed, it should also be nice to have these options in walkthrough garden

A few comments on this issue:

I think adding regions and population is something that should happen in the garden step, not meadow. Meadow is supposed to be for the minimum amount of preparation of the original data, so we don't need countries-regions or population for that.
The error when loading reference is a small bug in PathFinder, simply because the reference dataset has an unusual URI. But given that we want to move away from countries_regions and start using regions soon, I don't think it's worth fixing.

Thanks @pabloarosado. I agree with both points: in fact, I wanted to include this data on a garden step (currently unavailable). And regarding countries_regions, probably we should do nothing yet, but it's important to highlight it's broken for the most common use case.

Issued a PR for this https://github.com/owid/etl/pull/1004