Integration with other cosmos/tendermint chains

Hey there!
Excellent job on cosmos scan I think it looks gorgeous!
I would love to adapt it to other tender mint blockchains, and I'm wondering if there was an easy way to do so?
Obviously I need to change the node API URL, and the genesis file location, but I guess also the Bech32 prefixes?
I Believe I would have to do that in my own cosmos-sdk repo right?
Anything else I would be missing?
Thanks!

Hi, thanks! I think you need to separate api and db too, I think besides
this there will be many nuances. You can clone this repository and try to
push the PR or copy it to your repository. Good luck!
пт, 9 окт. 2020 г. в 01:06, vincentgeneste<EMAIL_ADDRESS>
Hey there!
Excellent job on cosmos scan I think it looks gorgeous!
I would love to adapt it to other tender mint blockchains, and I'm
wondering if there was an easy way to do so?
Obviously I need to change the node API URL, and the genesis file
location, but I guess also the Bech32 prefixes?
I Believe I would have to do that in my own cosmos-sdk repo right?
Anything else I would be missing?
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/everstake/cosmoscan-api/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4RALPCPAXHW4EM4OTHETLSJYZVNANCNFSM4SJKEJXA
.


haktrails usage page outputs json directly

haktrails usage page outputs json directly.. something like gron could help..
@hakluke if you don't have time, I can do it & create a PR..
Thank You :)

Hey! I'm not really concerned about this as there are only a couple of values: allowed_monthly_usage and current_monthly_usage, but I guess we could parse it for a more human readable output.

yeaa..


MPDS_KEY cannot be always read from env

Kind of heisenbug... so far the sequence of actions robustly leading to the availability of the key to the AiiDA daemon is not well documented.

All the variables are read by the daemon at the start time. So just make sure the variable is there at the time of daemon start,


Fix the viewModel -> ViewModel warning

This fixes a warning from can-component about assigning a DefineMap to the viewModel instead of ViewModel (capital V).
Warnings shown when running the tests before this change:

After this change:

Fixes https://github.com/donejs/done-component/issues/58

lgtm


Allow font customization

The author has rejected multiple PRs that allow similar types of customization, so I won't bother opening one...

Has this been opened before or after checking UIAppearance?

Before, will try out appearance first before merging/using this one.

We cannot distinguish between the number keys and the done button, but that's probably a worthy tradeoff for a 0 diff from the original repo. Will close this one.

Will restore this – UIAppearance works in the simulator, but not on device. I assume this is because the inputView runs as an extension and hence in a separate process.


initialize only connected channel on device connection

After discovered that VSP300 failed to initialize in case of one channel unplugged, as I explain in this issue I fixed this case : now the VSP can be connected even some channels are unplugged.

Wonderful! Thank you for the update.


Replace fill-opacity= to fill-opacity: in reaction.out

Reference Issue

Fixes: #3423
What does this implement/fix? Explain your changes.
All tests pass except testPgSQL.
All sub-tests in testPgSQL pass except reaction due to the difference between
expected/reaction.out and results/reaction.out:

fill-opacity=1 on expected/reaction.out
fill-opacity:1 on results/reaction.out

These files are located at:

Code/PgSQL/rdkit/expected/reaction.out
Code/PgSQL/rdkit/results/reaction.out

This fix changes fill-opacity=1 to fill-opacity:1 in expected/reaction.out.
Any other comments?

Thanks @daverona!

Pleasure


Add theme Venture

Thanks for your theme submission, Will. Your theme is already live on www.themes.gohugo.io.


Docs for GPU based indexing

Description
We need to expose package version, parameters that users can tune (along with the impact of tuning) to customers.
example: https://github.com/lancedb/lancedb/issues/767 - user ran out of memory from indexing. The doc should provide guidance on asking user to check pyarrow version, multiprocessing start method and instructions on how to tune the shuffler parameter
Link
No response

I think this page addressed this https://lancedb.github.io/lancedb/ann_indexes/ ?
Please reopen if there's something else needed


Reliance on Site Read Write All for File Add

I noticed that to use File Add that it MUST run this GET command first: https://graph.microsoft.com/v1.0/sites/contoso.sharepoint.com:/?$select=id
That would mean that you must grant Sites.Read.All, Sites.ReadWrite.All presumably (https://docs.microsoft.com/en-us/graph/api/site-get?view=graph-rest-1.0&tabs=http)
The use case involves using the Sites.Selected permission, which would make having to grant Sites.ReadWrite.All is not a possibility here. Do we have any resource or is that a requirement?

Closing due to inactivity


Implement PermissionChange

Continued from #4275. Creating a new PR to not lose the work that @kishikawakatsumi did in case we want to revert to that approach.

This is now ready for review /cc @kishikawakatsumi @mrackwitz @bigfish24.

The original intention behind the RLMSyncPermissionBaseObject was to have a common ancestor for the different classes in the management-Realm and share properties between those. This would be good to re-add once we want to implement them in the Cocoa SDK. But from your commits, it seems as that's only a temporary workaround.

I didn't feel the complexity that having this base class was justified by the advantages of sharing a few properties between them.
Given that jazzy doesn't handle inherited docs very well, these properties would need to be overridden and redeclared in their subclasses anyway, not actually saving any code duplication, but rather causing more of it.
In my commit messages, the "temporary hack" I was referring to was the hardcoded RLMSyncPermissionChange/SyncPermissionChange class to PermissionChange table mapping that was hardcoded in the object store, which I've since generalized in the ability to map model classes to custom table names.

I didn't feel the complexity that having this base class was justified by the advantages of sharing a few properties between them.
Given that jazzy doesn't handle inherited docs very well, these properties would need to be overridden and redeclared in their subclasses anyway, not actually saving any code duplication, but rather causing more of it.

Given these complexities, I didn't had in mind anymore, I'd agree with this assessment. The only minor drawback now is that there is no common base type anymore for objects which could be potentially handled in the same way by user-side logic. This could be mitigated though by implementing a protocol defining the common properties, if this is any better than a parent class.

The only minor drawback now is that there is no common base type anymore for objects which could be potentially handled in the same way by user-side logic.

What do you mean by this? The APIs from Realm Objective-C and Realm Swift aren't design to interoperate in any way, and doing so is unsupported. We state this explicitly in our docs:

If you’re looking to use Realm from Objective‑C, or from mixed Objective‑C & Swift apps please see Realm Objective‑C instead. The Realm Objective‑C and Realm Swift APIs are not interoperable and using them together is not supported.

I meant once there is not only PermissionChange, but also PermissionOffer and PermissionRequest.

I meant once there is not only PermissionChange, but also PermissionOffer and PermissionRequest.

I see your point, I'm not sure I agree at the moment, but I'm ok with reconsidering this once we have these additional models in the future.

I've reworked the implementation again to not require any changes to the object store, reporting a custom object name to the object store rather than storing a separate "table name" member in realm::ObjectSchema.
@tgoyne could you please take a look?

Can't set status; build failed.

Looks good to me! Thanks.


hero mdnook include does not work in tables and prints different strings

Situation

[ ] hero mdbook include function does not work in tables
[ ] hero mdbook include changes the output

Example
Include in table

code: we check to include a file into a table and into a standard paragraph

| **Description**           | **Value**     |
| ------------------------- | ------------- |
| TFT Market Price       | !!wiki.include page:'manual:tft_value.md' USD |
| TFT Market Cap | !!wiki.include page:'manual:tft_marketcap.md'  USD |

!!wiki.include page:'manual:tft_value.md' USD

!!wiki.include page:'manual:tft_marketcap.md'

converted to this

## TFT Marketcap and Market Price

The TFT market price and marketcap are as follows:

| **Description** | **Value** |
| :-- | :-- |
| TFT Market Price | !!wiki.include page:'manual:tft_value.md' USD |
| TFT Market Cap | !!wiki.include page:'manual:tft_marketcap.md'  USD |

0. 026

20280000
The market cap is equal to the product of the TFT market price and the circulating supply.

output

Include changes output

include changes the output, the following in a file

0.026

becomes this (add a space)

0. 026

example files content in info_tfgrid

examples files after conversion (hero/var/mdbuild/manual/src/manual

@despiegk @MarioBassem
This issue is a priority, IMO.

i tried to trace this, here is what i found:

the output change issue is indeed a bug, a small fix is possible
the include in a table problem so simple, here is why:

the markdown parser has top level elements: list, table, action, html, codeblock, and paragraph
lists and tables are actually parsed as paragraphs
a paragraph could be parsed to a combination of these elements: def, comment, link, or text
this means that a table cannot contain an action element (an include is an action element)

that being said, i believe some refactoring in the parser should be done to allow having nested element properly.
@despiegk what do you think?

"the output change issue is indeed a bug, a small fix is possible"
Fixing the output would be nice then, if it's a small fix.
@MarioBassem So I could simply set a definition or text instead of a whole page and it would work?
I only want a number really (e.g. 0.022 as the TFT price). So including the page is not necessary.
What would be the include here? Something like this?
!!wiki.include text:'manual:tft_value.md'
Perharps it's easier to set the numbers as def?
Thanks!

its quite a serious amount of work to make this feature work, will think how to do it best

Ok good. For now I put static content instead in the manual.


Make sure that response variables get cleared in the demo app

See TODO comments in demo_app.c

Resolved with issue #83.

Resolved with issue #83.


fix: change deprecated constants for HA 2024.1

Went through the codebase to fix the deprecated constant warning from HA 2024.1.0b2.
Had these in my log:
2023-12-31 13:12:33.939 WARNING (MainThread) [homeassistant.const] TIME_MINUTES was used from kia_uvo, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTime.MINUTES instead, please create a bug report at https://github.com/fuatakgun/kia_uvo/issues
2023-12-31 13:12:33.946 WARNING (MainThread) [homeassistant.const] TIME_DAYS was used from kia_uvo, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTime.DAYS instead, please create a bug report at https://github.com/fuatakgun/kia_uvo/issues
2023-12-31 13:12:33.953 WARNING (MainThread) [homeassistant.const] ENERGY_WATT_HOUR was used from kia_uvo, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfEnergy.WATT_HOUR instead, please create a bug report at https://github.com/fuatakgun/kia_uvo/issues
2023-12-31 13:12:33.960 WARNING (MainThread) [homeassistant.const] ENERGY_KILO_WATT_HOUR was used from kia_uvo, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfEnergy.KILO_WATT_HOUR instead, please create a bug report at https://github.com/fuatakgun/kia_uvo/issues
2023-12-31 13:12:33.969 WARNING (MainThread) [homeassistant.components.device_tracker] SOURCE_TYPE_GPS was used from kia_uvo, this is a deprecated constant which will be removed in HA Core 2025.1. Use SourceType.GPS instead, please create a bug report at https://github.com/fuatakgun/kia_uvo/issues
2023-12-31 13:12:33.976 WARNING (MainThread) [homeassistant.components.device_tracker] SOURCE_TYPE_GPS was used from kia_uvo, this is a deprecated constant which will be removed in HA Core 2025.1. Use SourceType.GPS instead, please create a bug report at https://github.com/fuatakgun/kia_uvo/issues

but found a few more - likely because the climate isn't supported on my vehicle.
tested locally, works fine. Climate wasn't tested yet (as my vehicle doesn't support that). Fixes #785

Awesome thank you for doing this!

Do you know by any chance the minimum version required for these new constants? If so we should update our minimum version as well.  Each time these happen we get a few issues from people running old HA versions.

Found it 2023.1


Environment Variables Problems in Terminal

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.92.2
OS Version: Windows_NT x64 10.0.22631
PowerShell Version: 7.4.4

Steps to Reproduce:

Start a VSCode session
Add some path which have executable program under it to the Path of Enviroment Variables
Then start the terminal and try to run these files

If you try to restart the terminal session to fix this, it won't work. Even when you use the command "Reload Window" it doesn't work. However, this can be fixed when you close all running VSCode sessions and then open them, or when you update an extension and require a restart. But when I open a lot of VSCode sessions I need to close them all, which is very cumbersome.
You can also add a new command that can restart VSCode just like the "restart" when updating an extension.
For this, I just opened a new issue there: #226511

Thank you for reporting this issue. We understand that it can be cumbersome to restart all VS Code sessions to apply changes to environment variables.
The reason why restarting the terminal session or using the "Reload Window" command does not work is that environment variables are inherited from the parent process. When you start a new terminal session or reload the window, the environment variables are not reloaded from the system but are inherited from the VS Code process that was initially started. This means that any changes to the environment variables made after VS Code was started will not be reflected in the terminal sessions.
To apply changes to environment variables, the entire VS Code process needs to be restarted.


[HOLD for payment 2022-01-27] [HOLD for payment 2022-01-25] Food & Drink  emojis and currently they are categorized in Animals & Nature - reported by @thesahindia

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open app
Navigate to any chat
Click on Emoji picker
Scroll to food emojis

Expected Result:
Food & Drink  emojis should have its own category
Actual Result:
Food & Drink  emojis and currently they are categorized in Animals & Nature
Workaround:
Unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: 1.1.26-0
Reproducible in staging?: Y
Reproducible in production?: Y
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: @thesahindia
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1641235742418900
View all open jobs on GitHub

Triggered auto assignment to @stitesExpensify (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Proposal
We need to add this before line 3618 -
    {
        code: CONST.EMOJI_SPACER,
    },
    {
        code: CONST.EMOJI_SPACER,
    },
    {
        code: CONST.EMOJI_SPACER,
    },
    {
        code: CONST.EMOJI_SPACER,
    },
    {
        code: CONST.EMOJI_SPACER,
    },
    {
        code: 'Food & Drink',
        header: true,
    },
    {
        code: CONST.EMOJI_SPACER,
    },
    {
        code: CONST.EMOJI_SPACER,
    },
    {
        code: CONST.EMOJI_SPACER,
    },
    {
        code: CONST.EMOJI_SPACER,
    },
    {
        code: CONST.EMOJI_SPACER,
    },
    {
        code: CONST.EMOJI_SPACER,
    },
    {
        code: CONST.EMOJI_SPACER,
    },

https://github.com/Expensify/App/blob/667570caf12bfa2e083072a07dcc0af3959fb3b0/assets/emojis.js#L3618-L3623
and we need to add this before line 4368
    {
        code: CONST.EMOJI_SPACER,
    },
    {
        code: CONST.EMOJI_SPACER,
    },
    {
        code: CONST.EMOJI_SPACER,
    },

https://github.com/Expensify/App/blob/667570caf12bfa2e083072a07dcc0af3959fb3b0/assets/emojis.js#L4368-L4385

Proposal
Just need to add Food & Drinks header just before grape fruit emoji. We also need to add 5 EMOJI_SPACER before the header and 7 EMOJI_SPACER after the header for adjusting the spaces.
But honestly what I would recommend is instead of manually adjusting such spaces we should remove all EMOJI_SPACER from emojis.js and dynamically add them. I had already added getDynamicSpacing while working on frequently used emojis. Can reuse the logic.
function addSpacesToEmojis(emojis) {
    const updatedEmojis = [];
    emojis.forEach((emoji, i) => {
        if(emoji.header) {
            updatedEmojis = updateEmojis.concat(getDynamicSpacing(updatedEmojis.length), [emoji], getDynamicSpacing(1));
        } else {
            updatedEmojis.push(emoji);
        }
    });
    return updatedEmojis;
}

@mananjadhav, I think your proposal is almost the same as mine except it's missing one crucial thing.
And I think changing the current way of adding EMOJI_SPACER could be a suggestion but it's not related to the issue itself.

except it's missing one crucial thing.

What's that?

could be a suggestion but it's not related to the issue itself

Indeed, but creating issues for a dev function doesn't make sense. Hence, generally, I've pushed such enhancements as a part of any feature development. For instance, we removed hardcoded emoji header indices when we worked on frequently used emojis.

except it's missing one crucial thing.

What's that?

and we need to add this before line 4368
    {
        code: CONST.EMOJI_SPACER,
    },
    {
        code: CONST.EMOJI_SPACER,
    },
    {
        code: CONST.EMOJI_SPACER,
    },

could be a suggestion but it's not related to the issue itself

Indeed, but creating issues for a dev function doesn't make sense. Hence, generally, I've pushed such enhancements as a part of any feature development. For instance, we removed hardcoded emoji header indices when we worked on frequently used emojis.

Yes, and I just think that you could've just shared the suggestion instead of duplicating already existing proposal.

instead of duplicating an already existing proposal.

Don't worry I won't be anyway taking up/getting the job if the proposal is duplicated 😃

@thesahindia  I've updated the proposal to only my recommendation. Hope this helps.

Thank you for noticing this and creating the issue @thesahindia.
@mananjadhav do you know if this was a regression? I thought everything was categorized correctly at one point..
Regardless, I agree that dynamic spacing is a good improvement so that every time we add/remove emojis we don't need to manually change the amount of spaces in the whole file.

Triggered auto assignment to @dylanexpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

do you know if this was a regression?

I checked the history and couldn't find Food & Drinks as the header. I also checked our original data source https://github.com/amurani/unicode-emoji-list/, it is missing there as well, guessing hence we've missed it here.

Posted!
Internal: https://www.upwork.com/ab/applicants/1480481665394843648/job-details
External: https://www.upwork.com/jobs/~01bacbeab1b11e4bfa

Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat (Exported)

Current assignee @stitesExpensify is eligible for the Exported assigner, not assigning anyone new.

Hmm... Tough call. I would differently recommend dynamic spacing and it's a nice clean-up.
But I see that @mananjadhav you didn't specify adding a new category Food & Drink in the emoji file. But that is understood :nerd_face:.
Based on the weightage, Manan has proposed a nice improvement to the code for a long-term basis and it saves space. I like @mananjadhav proposal.  @thesahindia you have proposed a working solution but Manan's proposed improvement has added advantage.
cc: @stitesExpensify
:ribbon: :eyes: :ribbon:  C+ reviewed

I agree with @parasharrajat. @mananjadhav you can go ahead and apply to the job!

@parasharrajat @stitesExpensify  PR raised.

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.1.30-3 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/7125
https://github.com/Expensify/App/pull/7255

If no regressions arise, payment will be issued on 2022-01-25. :confetti_ball:

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.1.31-1 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/7255

If no regressions arise, payment will be issued on 2022-01-27. :confetti_ball:

@thesahindia offer sent for reporting the issue! Please apply and I'll pay you out ASAP!

Done @dylanexpensify

@dylanexpensify I have applied as C+. Thanks.

Everyone paid out, contracts ended, and job closed!


[BUG] MidiSrv.exe crashes

Describe the bug
When running midi.exe on the USB MIDI 1.0 device which is working with the Windows in-box USB MIDI driver (USBAUDIO.sys), MidiSrv crashes suddenly.
I have attached several event log files.
EventLogFiles.zip
To Reproduce

Set the Roland UM-ONE mk2 to class-compliant mode.
Attach the device to PC.
Open the Device Manager and make sure the device is working with the Windows in-box USB MIDI driver (USBAUDIO.sys).
Open midi.exe in two windows.
From one, monitor UM-ONE.
From the other, run following command with attached file:
'midi endpoint send-message-file TestAllMTs.txt'

After completing to end messages, MidiSrv crashes.
Expected behavior
MidiSrv never crashes.
Installer Name or Version
Windows.MIDI.Services.Developer.Preview.4.x<IP_ADDRESS>22.2031.exe
Desktop (please complete the following information):

OS: Windows 11 23H2 build 26040.1000

Device information, if this is with an external MIDI device:

Roland UM-ONE mk2

Classic MIDI 1.0 class driver (USBAUDIO.sys)

Application Information

midi.exe console app.

Please retest with next driver version that had pull request https://github.com/microsoft/MIDI/pull/301

Please retest with next driver version that had pull request #301

This is with our older class driver, so not MIDI 2.0 driver

I have confirmed that this issue is resolved with the latest version of the driver (<IP_ADDRESS>4) and dp6.

I have confirmed that the issue has been solved.

Service: Windows.MIDI.Services.In-Box.Service.-.Developer.Preview.<IP_ADDRESS>94.2233-x64.exe
Driver: [interim preview build] 240713-USBMidi2-x86-TESTSIGNED.zip (DriverVer = 07/13/2024,<IP_ADDRESS>4)
OS: Windows 11 24H2 (OS Build 26100.1150)

It seems I haven't attached TestAllMTs.txt to verify this issue. Sorry.

The issue was resolved.


We would love the option to disable outlining

Imagine We have a number parameters at the top that we need to one off comment out, but the collapse is always in the way.
There is not enough space between the code outlining and the text so we are CONSTANTLY accidentally collapsing when trying to click in first line of the query.
I find myself disabling code outlining on EVERY single new query window.
Please make a global disable of Code outlining.
Thank you.

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

ID: 24d3ba88-bb53-d484-ee90-d3d531befe5d
Version Independent ID: 5382dd32-b21d-2e3a-2c6b-ed2cb7c18863
Content: Code Outlining - SQL Server
Content Source: docs/ssms/scripting/code-outlining.md
Product: sql
Technology: scripting
GitHub Login: @markingmyname
Microsoft Alias: maghan

@dimmthewitted -- thank you for your feedback; please add it here:

SQL Server Feedback

I am closing this issue now.  You are welcome to @ mention me for any followup.
We hope to hear from you again.


[nbgl] PIC some addr

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

Comparison is base (8030947) 59.47% compared to head (b15b740) 59.47%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #474   +/-   ##
=======================================
  Coverage   59.47%   59.47%
=======================================
  Files          12       12
  Lines        1683     1683
=======================================
  Hits         1001     1001
  Misses        682      682

Flag
Coverage Δ

unittests
59.47% <ø> (ø)

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

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


Error: File already exists

Hi! Thanks a lot for creating this plugin first of all. 🙇
When I clip something when there's no target note created, it creates a new daily/weekly note and adds the clip there. However, if I clip some other thing again, it fails with the following error:
plugin:obsidian-clipper:341
Failed to create file: 'Periodic notes/Weekly notes/2023Q2W20.md' Error: File already exists.
    at t.<anonymous> (app.js:1:966983)
    at app.js:1:235927
    at Object.next (app.js:1:236032)
    at a (app.js:1:234750)

I think it may be related with some plugins I'm using, such as Templater, Periodic notes and Calendar, but it'd be nice if the clipper plugin doesn't attempt to create a new note when it exists already.

Looks like it's happening somewhere in here:
async function createWeeklyNote2(date) {
      const { vault } = window.app;
      const { template, format: format2, folder } = getWeeklyNoteSettings();
      const [templateContents, IFoldInfo] = await getTemplateInfo(template);
      const filename = date.format(format2);
      const normalizedPath = await getNotePath(folder, filename);
      try {
        const createdFile = await vault.create(normalizedPath, templateContents.replace(/{{\s*(date|time)\s*(([+-]\d+)([yqmwdhs]))?\s*(:.+?)?}}/gi, (_, _timeOrDate, calc, timeDelta, unit, momentFormat) => {
          const now2 = window.moment();
          const currentDate = date.clone().set({
            hour: now2.get("hour"),
            minute: now2.get("minute"),
            second: now2.get("second")
          });
          if (calc) {
            currentDate.add(parseInt(timeDelta, 10), unit);
          }
          if (momentFormat) {
            return currentDate.format(momentFormat.substring(1).trim());
          }
          return currentDate.format(format2);
        }).replace(/{{\s*title\s*}}/gi, filename).replace(/{{\s*time\s*}}/gi, window.moment().format("HH:mm")).replace(/{{\s*(sunday|monday|tuesday|wednesday|thursday|friday|saturday)\s*:(.*?)}}/gi, (_, dayOfWeek, momentFormat) => {
          const day = getDayOfWeekNumericalValue(dayOfWeek);
          return date.weekday(day).format(momentFormat.trim());
        }));
        window.app.foldManager.save(createdFile, IFoldInfo);
        return createdFile;
      } catch (err) {
        console.error(`Failed to create file: '${normalizedPath}'`, err);
        new obsidian.Notice("Unable to create new file.");
      }

We could avoid calling vault.create() if the note exists at normalizedPath.

I haven't been able to reproduce this yet, though I did find other issues unrelated to this.
Can you share what Operating System you are on. Can you also share what version of Obsidian you are using?
Thanks!

Hey, thanks for a reply. Here's the information:

OS: macOS 13.3.1 (Ventura)
Obsidian: 1.2.8

I was able to reproduce this now.
Clipper uses the periodic-notes plugin for weekly notes. Clipper would fail and show a Notice that this plugin is required when trying to use the weekly note.
Oddly, I can only recreate this if I use a Note Title Format like yours :).

gggg[Q]Q[W]w (like yours fails if note exists)
default in periodic notes works
gggg[W]w works as well.

This is an issue in the periodic-notes-interface code. For some reason it is trying to recreate a date from file names and the Q2 part of the filename being a weekly file is breaking it.
Not sure why the code doesn't just take the date, the format, generate the path and see if that exists.
I don't think I will be able to fix this one on my end currently.

The periodic-notes-interface library is causing the problem. It was designed/extracted from the calendar plugin so has an odd interface. I am going to play around to see if I can support this a different way.


Mac m1 - Add instructions to install python 3.7

The following PR implements the following changes in the README:

In MAcOS instructions, add a step to install xcode command line utils (sometimes necessary for git/homebrew)
Add instructions on how to install python3.7 on MacOS with a M1 chip though ibrew

Comments are appreciated!

This assumes Rosetta2 is installed, should I add an instruction step with this?

perfection...


includes/footer: make contribute button link to blob not edit.

This reduces the amount of spam we see, based on other sites.

_includes/footer.html


How do public parts access data, such as navigation

How do public parts access data, such as navigation
nav is public
layout ->index  (have nav)
layout ->post  (have nav)

I'm sorry, but I don't understand the question. Could you describe it in more details? Quicktemplate functions are translated to usual Go functions, so you can pass arbitrary arguments to them with any data.


YOLO-V5 - Support

Does opendatacam support to YOLOV5 ? Is there any way to implement ? If there is , how can I implement ? Is it like others Yolo's mentioned in the documentations ?

Actually ,  I was wondering  that  if  I want to change the model intstead of yolov4 or yolov3 , can I  do it in the future ?

I hope I understand your question correctly. If you want to use different models/weights (e.g. training your own model) that is already possible. See here: https://github.com/opendatacam/opendatacam/blob/master/documentation/CONFIG.md#use-custom-neural-network-weights
P.S. As this feels more like a support question, instead of discussing development opportunities for ODC I will convert this into a GitHub Discussion. But please keep asking. And if I'm wrong and you really want to make changes to the ODC code please open a new issue.


Enable auto-correct with Detekt in pre-commit.sh

This PR adds auto-correct with Detekt in pre-commit.sh.
When a commit is done and Detekt found issues on the committed files, it will try to correct them automatically, if possible.

Personally I didn't enable that on purpose when I first added the pre-commit scripts.
IMHO formatting the files should be done intentionally, invoking something, not under the hood, since it's something that changes the code so you may want to be sure to review that afterwards.
Said that, I'm fine even enabling this in the pre-commit script but I wanted to clarify why I didn't in the first place.

@fondesa
I see; thanks for the explanation! I found it useful on my project, while I was doing some refactors using the IDE tools, and, since the IDEA code-style doesn't cover as much as Detekt does, some Detekt issues were introduced: enabling auto-correct on pre-commit, allowed me to avoid running Detekt on the whole project.
On the other side, I share your thoughts.
Let's wait for other inputs/data, then.
Should we open a discussion?

I agree with @fondesa, I remember that I did the same discussion in past with other colleagues, and we concluded that is better to throw a failure in pre-commit without any auto-correction, in this way the developer should have more control over his/her staged files.
IMHO auto-correct is definitely useful, but pre-commit I think isn't the right place for it.

Aight, let's close this then, it seems more reasonable that one can run it manually on its side ✌


Graph connector Agent

After installing and configuring the Graph connector agent as per the below link
https://docs.microsoft.com/en-us/microsoftsearch/on-prem-agent
I am unable to register  at the end  the Error message is "Something went wrong .Please click on the register again to retry."
Screen shot attached

I am using 'Client secrets'  in Authentication.
Error from log
2021-05-12 21:40:45,038 [1] ERROR - {ErrorCode=ConfigAppRegistrationFailure, ErrorMessage=Registration failed}
System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
at System.Net.Security.SslStream.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, ExceptionDispatchInfo exception)
at System.Net.Security.SslStream.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.PartialFrameCallback(AsyncProtocolRequest asyncRequest)
Any ideas!

Hello @Jiannko, please send an email with these details to<EMAIL_ADDRESS>referencing this issue and also include the tenant ID where this is happening.

Hello @Jiannko, please send an email with these details to<EMAIL_ADDRESS>referencing this issue and also include the tenant ID where this is happening.

Details sent .

The  error i mentioned has gone after the APIs were granted Admin consent . But I fail when adding the connector
'Graph connector agent associated with the connection is not reachable.'
The agent application is running . Its configured with a Search Admin.
And the secret hasnt expired.
Any other areas which i should be checking!


Include string.h for strchr and strcmp.

This fixes a continuous build
(https://travis-ci.org/github/google/perf_data_converter/jobs/714589290)
running on Ubuntu 16.04 using gcc-4.8.
TESTED=Fresh install and system configuration following https://github.com/google/perf_data_converter/blob/master/.travis.yml

Thanks!


added a TOC to the README

as the README already is super long this would bring some help for first time users.
generated with http://tableofcontents.herokuapp.com/

The ToC looks broken for me:

But besides that, frankly I think listing all the features in the ToC just to link to the screenshots bloats the README more than it simplifies it.

I simplified the TOC so the main points are mentioned.
do you like it like that?


refactor: update error package and api

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

448 of 539 (83.12%)  changed or added relevant lines in 30 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-3.0%) to 83.535%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

core/receiver/service.go
13
14
92.86%

core/receiver/slack_service.go
6
7
85.71%

core/namespace/errors.go
3
5
60.0%

core/namespace/service.go
25
27
92.59%

core/provider/errors.go
3
5
60.0%

core/receiver/errors.go
3
5
60.0%

core/subscription/errors.go
3
5
60.0%

core/template/errors.go
3
5
60.0%

internal/store/postgres/template.go
9
12
75.0%

internal/store/postgres/rule.go
11
15
73.33%

Files with Coverage Reduction
New Missed Lines
%

internal/store/postgres/template.go
1
87.76%

Totals

Change from base Build<PHONE_NUMBER>:
-3.0%

Covered Lines:
1933

Relevant Lines:
2314

💛  - Coveralls


TOC is broken

Issue 171 in the original repository claims it was fixed in CSS without a solution provided.

Another example:   http://localhost:1313/post/2019-12-13-guy-de-maupassant/


[SW-119] CI/CD Process With Github Action

Github Action CI/CD Process
Complete

JDK Setting
Maven Package Caching ( Add for faster packaging. )
Project Build ( Currently, exclude the Test process. )
Docker Buildx Setting ( For Multi Platform building using Docker function. )
Docker Login
Docker build & push ( Using GithubActionCache(gha). To avoid redundant packaging of the layer. )
SSH Connect & Deploy ( Now, connected with Bastion VM. Backend Project port uses 8085. )

To Do

Connect to Private IP using port forwarding of Nginx Proxy Manager.
Change Tags when new image builds. ( Currently, all the tags are latest. )
Environment Setting for "application.yml" file.

수고하였습니다.


tcptunnelchecker shows some failures for tobaru

I have developed a special tool that checks corner cases of TCP forwarding regarding TCP resets/hangups while being backpressured.
It shows discrepancy between connecting back through tobaru and, for example, through socat.
$ cat config.json
{
  // Listen on all interfaces, on port 8080.
  "bindAddress": "<IP_ADDRESS>:1234",
  "target": {
    // Forward to <IP_ADDRESS> port 80.
    "address": "<IP_ADDRESS>:1235",
    // Allow connections from all addresses. 'all' is a special alias for <IP_ADDRESS>/0.
    "allowlist": "all"
  }
}

$ tobaru ./config.json
Listening (TCP): <IP_ADDRESS>:1234
[2022-03-16T08:31:00Z ERROR tobaru::tcp] <IP_ADDRESS>:33892 finished with error: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" }
[2022-03-16T08:31:01Z ERROR tobaru::tcp] <IP_ADDRESS>:33896 finished with error: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" }
[2022-03-16T08:31:01Z ERROR tobaru::tcp] <IP_ADDRESS>:33908 finished with error: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" }
[2022-03-16T08:31:02Z ERROR tobaru::tcp] <IP_ADDRESS>:33952 finished with error: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" }
[2022-03-16T08:31:03Z ERROR tobaru::tcp] <IP_ADDRESS>:33956 finished with error: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" }
[2022-03-16T08:31:03Z ERROR tobaru::tcp] <IP_ADDRESS>:33960 finished with error: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" }

$ ./tcptunnelchecker <IP_ADDRESS>:1235 <IP_ADDRESS>:1234
[ OK ] Trivial test 1
[ OK ] Trivial test 2
[ OK ] Clogged close test passed: outDrainCheck_inClose
[ OK ] Clogged close test passed: outDrainCheck_inDrainClose
[ OK ] Clogged close test passed: outClogCheck_inClose
[ OK ] Clogged close test passed: outClogDrainCheck_inClose
[ OK ] Clogged close test passed: outShutDrainCheck_inClose
[ OK ] Clogged close test passed: outShutDrainCheck_inDrainClose
[ OK ] Clogged close test passed: outClogCheck_inClogClose
[ OK ] Clogged close test passed: outDrainCheck_inShutClose
[ OK ] Clogged close test passed: outDrainCheck_inShutDrainClose
Broken pipe (os error 32)
Broken pipe (os error 32)
[ OK ] Clogged close test passed: outShutDrainCheck_inShutClose
[ OK ] Clogged close test passed: outShutDrainCheck_inShutDrainClose
[ OK ] Clogged close test passed: outClose_inDrainCheck
[ OK ] Clogged close test passed: outDrainClose_inDrainCheck
[ OK ] Clogged close test passed: outShutClose_inDrainCheck
[ OK ] Clogged close test passed: outShutDrainClose_inDrainCheck
[ OK ] Clogged close test passed: outClose_inClogCheck
[ OK ] Clogged close test passed: outClose_inClogDrainCheck
[ OK ] Clogged close test passed: outClogClose_inClogCheck
Broken pipe (os error 32)
Broken pipe (os error 32)
[ OK ] Clogged close test passed: outClose_inShutDrainCheck
[ OK ] Clogged close test passed: outDrainClose_inShutDrainCheck
[ OK ] Clogged close test passed: outShutClose_inShutDrainCheck
[ OK ] Clogged close test passed: outShutDrainClose_inShutDrainCheck

In comparison, the tool does not show errors for socat-based forwarder:
$ socat tcp-listen:1234,fork,reuseaddr tcp-connect:<IP_ADDRESS>:1235
2022/03/16 11:31:53 socat[21951] E write(5, 0x55b7cf2c7000, 8192): Connection reset by peer
2022/03/16 11:31:53 socat[21954] E write(5, 0x55b7cf2c7000, 8192): Connection reset by peer
2022/03/16 11:31:54 socat[21963] E write(5, 0x55b7cf2c7000, 8192): Connection reset by peer
2022/03/16 11:31:54 socat[21973] E write(5, 0x55b7cf2c7000, 8192): Broken pipe
2022/03/16 11:31:54 socat[21976] E write(5, 0x55b7cf2c7000, 8192): Broken pipe
2022/03/16 11:31:55 socat[22000] E write(6, 0x55b7cf2c7000, 8192): Broken pipe
2022/03/16 11:31:56 socat[22002] E write(6, 0x55b7cf2c7000, 8192): Broken pipe
2022/03/16 11:31:56 socat[22006] E write(6, 0x55b7cf2c7000, 8192): Connection reset by peer
2022/03/16 11:31:56 socat[22010] E write(6, 0x55b7cf2c7000, 8192): Broken pipe
2022/03/16 11:31:57 socat[22012] E write(6, 0x55b7cf2c7000, 8192): Broken pipe

$ tcptunnelchecker <IP_ADDRESS>:1235 <IP_ADDRESS>:1234
[ OK ] Trivial test 1
[ OK ] Trivial test 2
[ OK ] Clogged close test passed: outDrainCheck_inClose
[ OK ] Clogged close test passed: outDrainCheck_inDrainClose
[ OK ] Clogged close test passed: outClogCheck_inClose
[ OK ] Clogged close test passed: outClogDrainCheck_inClose
[ OK ] Clogged close test passed: outShutDrainCheck_inClose
[ OK ] Clogged close test passed: outShutDrainCheck_inDrainClose
[ OK ] Clogged close test passed: outClogCheck_inClogClose
[ OK ] Clogged close test passed: outDrainCheck_inShutClose
[ OK ] Clogged close test passed: outDrainCheck_inShutDrainClose
[ OK ] Clogged close test passed: outClogCheck_inShutClose
[ OK ] Clogged close test passed: outClogDrainCheck_inShutClose
[ OK ] Clogged close test passed: outShutDrainCheck_inShutClose
[ OK ] Clogged close test passed: outShutDrainCheck_inShutDrainClose
[ OK ] Clogged close test passed: outClose_inDrainCheck
[ OK ] Clogged close test passed: outDrainClose_inDrainCheck
[ OK ] Clogged close test passed: outShutClose_inDrainCheck
[ OK ] Clogged close test passed: outShutDrainClose_inDrainCheck
[ OK ] Clogged close test passed: outClose_inClogCheck
[ OK ] Clogged close test passed: outClose_inClogDrainCheck
[ OK ] Clogged close test passed: outClogClose_inClogCheck
[ OK ] Clogged close test passed: outShutClose_inClogCheck
[ OK ] Clogged close test passed: outShutClose_inClogDrainCheck
[ OK ] Clogged close test passed: outClose_inShutDrainCheck
[ OK ] Clogged close test passed: outDrainClose_inShutDrainCheck
[ OK ] Clogged close test passed: outShutClose_inShutDrainCheck
[ OK ] Clogged close test passed: outShutDrainClose_inShutDrainCheck

Loopback test tcptunnelchecker <IP_ADDRESS>:1234 <IP_ADDRESS>:1234 also shows results similar to socat ones.

very cool, thanks for creating the issue. will take a look.

Note that fixing it portably may be problematic due to missing support of waiting for hangups without also waiting for read- or write-readiness. See https://github.com/tokio-rs/tokio/issues/3467 or https://github.com/tokio-rs/mio/issues/1476.


MM-21707: enable backstage link for only bots

Summary
Show the link to the backstage (aka Integrations) even if only bot accounts are enabled. Previously, if all of slash commands, webhooks and oAuth were disabled, but bot account creation was enabled, this entry would still be suppressed.
Note that the permissions gate on this feature remains slightly inaccurate: if a subset of the backstage features are enabled, but the user in question has non-intersecting permissions (i.e.  MANAGE_SLASH_COMMANDS but only OAUTH enabled), they'll see the link but end up at a blank page. This pull request does not change that behaviour.
Ticket Link
Fixes: https://mattermost.atlassian.net/browse/MM-21707

/update-branch

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-4883.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

Test server destroyed


Grammarly fixes

Linefeeds by writer in readme.md create havoc in docs -site side. When possible use VS Code Word Wrap when writing markdown to avoid manual linefeeds.

The length rule is not a markdown rule, just a markdown linter rule.
The docs rendering is only breaking if there are extra spaces, and the only way to get that is to manually add linefeeds.
Markdown is not code, it is content to applying old code styling rules on it really does not make sense. Markdown will in all cases (except looking at raw data in a text editor) be shown in whatever width layout so applying a some limit in the source file really does not help.
Need to get these fixes in and let's look at the #257 separately.

Will refactor this PR by applying this Notion proposal.


fix fuzz_calculate_present_value

fuzz_calculate_present_value is failing on main. It fails intermittently on CI and consistently if you bump up FAST_FUZZ_RUNS to 100k
Example failure:
running 1 test
test lp::tests::fuzz_calculate_present_value ... FAILED

failures:

---- lp::tests::fuzz_calculate_present_value stdout ----
thread 'lp::tests::fuzz_calculate_present_value' panicked at crates/hyperdrive-math/src/lp.rs:299:79:
called `Result::unwrap()` on an `Err` value: calculate_max_buy_bonds_out_safe: y = 140766449.986666938237369971 < 140781651.077315479405295767 = optimal_y

Location:
    crates/hyperdrive-math/src/yield_space.rs:266:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    lp::tests::fuzz_calculate_present_value

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 42 filtered out; finished in 13.52s

this might already be fixed, I'm going to run some tests on this to see if it still flakes.

This isn't flaking anymore, fixed in #11 .


Pre release 1.0

Fixed package versions
Removed taming-transformer deps by adding the corresponding missing files for LPIPS loss
Cleaned with isort and black #52

The LPIPS vendoring isn't necessary if #50 is merged.

The LPIPS vendoring isn't necessary if #50 is merged.
Yes but we decided internally to not merge #50 for the future release
This LPIPS refactoring would have been necessary at some point in any case


can I haz push access?

@cjermain so I can sync a branch with some drivers

You should be good now. Does that work?

Yeps :)


Issue with frameProcessor - TypeError: Cannot read property 'scanOCR' of undefined

I'm trying to use this frame processor, everything works fine, it scans the text, but, when i try to use the text, reanimated asks me to run the code on runOnJS, when i simply type.
import { runOnJS } from "react-native-reanimated";
The app crashes with this error.
TypeError: Cannot read property 'scanOCR' of undefined
This is the import order on the component:
import 'react-native-reanimated';
import { runOnJS } from "react-native-reanimated";
import { scanOCR } from "vision-camera-ocr";

Package Json
"react": "17.0.2",
"react-native": "0.65.1",
"vision-camera-ocr": "^1.0.0",
"react-native-vision-camera": "^2.12.0",
"react-native-reanimated": "^2.3.0-beta.2",

Hey @josumonk, can you try out the example project and let me know if it works for you? The code there might be helpful in determining if the bug is in the library or your project. https://github.com/aarongrider/vision-camera-ocr/blob/main/example/src/App.tsx
Also, make sure you have applied the babel config correctly:
[
      'react-native-reanimated/plugin',
      {
        globals: ['__scanOCR'],
      },
    ],

I tried the example, and everything works great. I tried copying all package versions over my app too, still failing.
But, it worked when i moved around the animation import import 'react-native-reanimated';
Looks like the entry file changes a little bit when using react-native-navigation.
Thanks for the support.

The same problem on a new project, how can I solve it?

Please try :
react-native start --reset-cache
then
react-native run-android


Individual Finding Exception Feature Request

Description
Instead of skipping entire files it would be nice if there was a way to skip individual findings based on an exception. This could be done either by passing in command line arguments or having a file such as a .exceptions file containing a list of libraries to ignore.
Expected Behavior
Pass individual packages and or vulnerabilities with them based on a commandline argument.
Actual Behavior
Right now the exception process ignores all of the packages in the sbom if you specify it. There are cases where only a single package in the file needs to have an exception.

Hello, thank you for the feature request.
We understand your workflows would be improved by being able to exclude individual findings.
We will add your feature request to our backlog.
I cannot offer an ETA as to when this work would begin; however, this is a topic that we discuss regularly.
We also welcome contributions if anyone from the community wishes to help.


Add WYG! Watch Your Gforces!

spec_version: v1.27
identifier: WatchyourGforces
$kref: '#/ckan/spacedock/3515'
$vref: '#/ckan/ksp-avc'
release_status: stable
resources:
  spacedock: https://spacedock.info/mod/3515/WYG!%20-%20Watch%20Your%20G-forces!
  homepage: >-
    https://forum.kerbalspaceprogram.com/topic/221046-wyg-watch-your-g-forces-ksp-112/
  repository: https://github.com/kurgut/WYG-WatchYourG-Forces-
  x_screenshot: https://imgur.com/bSTzQU3
tags:
  - physics
  - config
  - crewed
depends:
  - name: ModuleManager
recommends:
  - name: DeadlyReentry
supports:
  - name: RealSolarSystem
x_via: Generated by Metadata Webtool

Sorry, could you change the recommended mod "Deadly Reentry" to suggests instead ?
Users tend to install things they didn't really want by pressing the next button when installing, I'd thus prefer this being in the suggest section, thank you : )

In the future, either click the "add to ckan" checkbox on spacedock OR use the metadata web tool, not both.  Adding from spacedock is a little preferable.
added the crewed tag in https://github.com/KSP-CKAN/NetKAN/commit/683f770b9d7860df7adccebf87210f8d1077e5b3

@JonnyOThan
Hi, thanks for your message, I wasn't sure the Spacedock method had worked, thus why I did it here, but noted for the future.
I'm ok with all points, about RSS + tags, thanks for clearing up this.

Oh actually I think you can use the metadata tool to submit updates, but it's also pretty easy to use github's web tool (just click the edit button on your .netkan file) to make pull requests to change your mod's metadata.


Removed all warnings, and fixed bugs hidden among them.

Warnings should be taken seriously, since bugs will hide among them.

Thanks for all the bug smashing and code cleaning you've done here.
I've tested the code and everything seems to be in order.
As a side note, some of these errors are present in the dependencies that we didn't include as submodules. If you feel like it, you could also open pull requests with these changes on those dependencies. I think the dependency authors might also appreciate this.


how to transfer tokens using this SDK i.e. spl-token transfer?

not an issue but a question or a feature request
is it possible to transfer tokens using this SDK like with the Solana CLI using a terminal?
Terminal Example:
$spl-token transfer --allow-unfunded-recipient --fund-recipient [token address] [amount of tokens] [recipients wallet]

I believe it's not yet fully integrated, but haven't tested it https://github.com/tighten/solana-php-sdk#transactions

Anymore info on this would be highly appreciated ❤

Seems like it's being worked on https://github.com/tighten/solana-php-sdk/pull/28

@suchpro Were you able to figure this out

I can transfer tokens now, but the amount sent is not encoded properly I believe to the right decimal so it sends a wrong value

@impozzible haven't tested it yet

Figured it out, incase someone else runs into this issue
`public function createTransferInstruction(
PublicKey $source,
PublicKey $destination,
PublicKey $owner,
int $amount
): TransactionInstruction {
$data = [
// uint32
...unpack("C*", pack("C", 3)),
// int64
...unpack("C*", pack("P", $amount)),
];
// dd($data);
$keys =  [
new AccountMeta($source, false, true),
new AccountMeta($destination, false, true),
new AccountMeta($owner,true,true),
];
    return new TransactionInstruction(
        new PublicKey("TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA"),
        $keys,
        $data
    );
}`

'Transfer' instruction is deprecated for now and token developers recommend to use 'TransferChecked' instruction, sample code
`
public function createTransferCheckedInstruction(
string $source,
string $destination,
string $owner,
string $mint,
int    $amount,
int    $decimals
): TransactionInstruction
{
/**
* TokenInstructions :
*   Transfer = 3,
*   TransferChecked = 12,
/
$data = [
// u8
...unpack("C", pack("C", 12)),  // token instruction index
// u64
...unpack("C*", pack("P", $amount)), // amount without decimals
// u8
...unpack("C*", pack("C", $decimals)),   // token decimals
];
$keys = [
new AccountMeta(new PublicKey($source), false, true), // source account address
new AccountMeta(new PublicKey($mint), false, false), // mint token address
new AccountMeta(new PublicKey($destination), false, true), // destination account address, if not exist need call
new AccountMeta(new PublicKey($owner), true, true), // singer address, wallet who will be sing tx
];
    return new TransactionInstruction(
        new PublicKey(SplTokenProgram::SOLANA_TOKEN_PROGRAM_ID),
        $keys,
        $data
    );
}

`

Does anyone have an example of full code on this working? I keep getting a
Transaction simulation failed: Error processing Instruction 0: invalid account data for instruction
error

Figured it out, incase someone else runs into this issue
public function createTransferInstruction(
        PublicKey $source,
        PublicKey $destination,
        PublicKey $owner,
        int $amount
    ): TransactionInstruction {
        $data = [
            // uint32
            ...unpack("C*", pack("C", 3)),
            // int64
            ...unpack("C*", pack("P", $amount)),
        ];
        // dd($data);
        $keys =  [
            new AccountMeta($source, false, true),
            new AccountMeta($destination, false, true),
            new AccountMeta($owner,true,true),
        ];

        return new TransactionInstruction(
            new PublicKey("TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA"),
            $keys,
            $data
        );
    }```

Can you post your full code for sending a token please?


Added Python example

I've written a basic Python module and loaded it to PyPi (https://pypi.python.org/pypi/socketlabs/0.1.1), and implemented some sample code here showing how to use it. Hope it helps.

Thank you.


Fix parsing of due dates with time

Now it works for both due dates without time (2016-12-16) and due dates with time (2016-12-01T12:00:00)
Fixes https://github.com/Hoffelhas/autodoist/issues/24
Edit: Added some more functionality to take timezones into account

Im have -nf set to 3 days. And still having trouble with next action label getting applied with tasks that are due in the future

Im have -nf set to 3 days. And still having trouble with next action label getting applied with tasks that are due in the future

Is that with my new proposed code?

Yes I was still having issue unfortunately. I can try and re-create to give more info

@erauner12 I think your issue is something different than what this PR fixes: https://github.com/Hoffelhas/autodoist/issues/24
This is about start dates not the due dates too far in the future.
The docs talk about parameter -hf while you say -nf. Did you make a typo or is that the problem perhaps?

Thanks for writing a fix for this. Can't be merged in the latest dev version, but has been included manually.


How do we get compute? Hardware or money to rent (cloud).

We have access to a TPU pod of "v3-32".

We might have access to a 16 x A100 with 40 GB box.


Merge master branch to prTesting1_201901020839 branch

OPS Build status updates of commit c17f4ac:
:clock10: Preparing: average preparing time is 42 sec(s)

OPS Build status updates of commit c17f4ac:
:clock10: Incremental building: average incremental building time is 14 sec(s)

OPS Build status updates of commit c17f4ac:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

split/updateTestCon1.md
:white_check_mark:Succeeded

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


About swagger built-in resource reference CDN problem

The current swagger built-in resources are referenced from the jsdelivr site
Due to domestic network problems, the docs page cannot be opened.
当前/docs页面资源使用了jsdelivr站点提供的CDN服务，而该站点由于被墙导致页面无法正常显示

Is the issue still exist? I can reach these files on my side (Shanghai) without the VPN.
A simple workaround for this would be using the related configuration variables to set a custom CDN provider.

This problem does not exist for the time being, but after many days of observation and the feedback from other users, the problem will occur from time to time


Build the project with Java 11

Currently the project is building with Java 16 which makes kinda impossible of using it on a IntelliJ plugin
https://github.com/ButterCam/compose-jetbrains-theme/blob/main/build.gradle.kts#L39

https://github.com/ButterCam/compose-jetbrains-theme/pull/11


[FEATURE REQUEST]: Add Cold Content ATI and Meltrate State Grids

CRREL's snow scripts used to generate these (default value) additional state grids, which the SNODAS model does not compute.   These state grids are needed to initialize HMS snow models.

Reference for old grid processing script: https://github.com/CRREL/snowmelt

Zero grids were originally provided when previous versions of Hydrologic Modeling System (HEC-HMS) needed initial state grids, even if they are grids full of zeros. Newer versions of the modeling software can "Set Default Values" if grids are not provided. Zero grids will not be produced, stored, and served from Cumulus for the purpose of model initialization.


python310Packages.aio-georss-client: 0.10 -> 0.11, python310Packages.aio-georss-gdacs: 0.7 -> 0.8

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 212830 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.gdacs
python310Packages.aio-georss-client
python310Packages.aio-georss-gdacs
python311Packages.aio-georss-client
python311Packages.aio-georss-gdacs


"Cannot read property 'toLowerCase' of undefined" when LLDB missing

I got the following exception using LLDB when I started debugging:
Cannot read property 'toLowerCase' of undefined

DebugService.updateStateAndEmit (debugService.ts:473)
DebugService.focusStackFrameAndEvaluate (debugService.ts:493)
(anonymous function) (debugService.ts:759)
notifySuccess (winjs.base.raw.js:1170)
enter (winjs.base.raw.js:901)
_run (winjs.base.raw.js:1068)
_error (winjs.base.raw.js:1041)
(anonymous function) (v8Protocol.ts:56)
_cancelAction (winjs.base.raw.js:1652)
enter (winjs.base.raw.js:805)
_run (winjs.base.raw.js:1068)
cancel (winjs.base.raw.js:964)
_cancelAction (winjs.base.raw.js:1311)
enter (winjs.base.raw.js:805)
_run (winjs.base.raw.js:1068)
cancel (winjs.base.raw.js:964)
(anonymous function) (rawDebugSession.ts:296)
(anonymous function) (rawDebugSession.ts:296)

The exception message is displayed in the UI on a bar appearing at the top.
VS Code version: tag 1.11.1, revision d9484d12b38879b7f4cdd1150efeb2fd2c1fbf39
NativeDebug version: 0.17.0
launch.json
    {
      "name": "LLDB Test",
      "type": "lldb-mi",
      "request": "launch",
      "target": "./target/debug/…",
      "cwd": "${workspaceRoot}",
      "preLaunchTask": "build-test",
      "env": {
        "RUST_BACKTRACE": "1"
      }
    }

The preLaunchTask succeeds.
If submitting a bug please make sure
The problem could be solved by installing LLDB. It would have saved time if a more helpful message would have been displayed. Maybe the extension could check the presence of LLDB or GDB at the start of the debugging session?

Duplicate of #102


Word wrap configuration option changes

yazi --debug output
N/A

Please describe the problem you're trying to solve
The recently merged https://github.com/sxyazi/yazi/pull/1159 adds word wrapping to the preview, but the option is poorly named and designed. The two values for the option are "yes" and "no", two strings, instead of a boolean. Additionally, everywhere I can find the word "wrap" mentioned in the pull request except for in the naming of the option, "wrap" is preceded by "word wrap".
Would you be willing to contribute this feature?

[X] Yes, I'll give it a shot

Describe the solution you'd like
To clarify the option, it should be called word_wrap instead of wrap and accept a boolean instead of yes/no strings.
Additional context
No response
Validations

[X] I have searched the existing issues
[X] The latest nightly build of Yazi doesn't already have this feature

The two values for the option are "yes" and "no", two strings, instead of a boolean

This is a deliberate decision. Using a string instead of a boolean is to allow for the addition of other wrapping behaviors in the future. As I mentioned in that PR, it's still unstable and will be adjusted accordingly as ratatui implements these features.
For example, CJK (Chinese, Japanese, Korean) languages require different line wrapping (See https://github.com/ratatui/ratatui/issues/1199), which can't be represented with just a boolean:
wrap = "cjk"

Additionally, everywhere I can find the word "wrap" mentioned in the pull request except for in the naming of the option, "wrap" is preceded by "word wrap"

This is also a deliberate decision, allowing us to add options like wrap_trim or even wrap_indent in the future without making the name too long (like word_wrap_trim or word_wrap_indent), which is both ugly and doesn't fit Yazi's naming aesthetics. As you can see, all options in yazi.toml (or even theme.toml, keymap.toml) are made up of a maximum of two words.

Note that the things I mentioned above (except for wrap_trim) haven't been implemented in ratatui yet. I'm just reserving these options now so that we can expand in the future without causing any breaking changes.


'nlohmann/json.hpp' file not found error even after applying the patch from pull #672

I applied this patch, from the pull #672, to enable json build for extensions
diff --git a/scripts/cmake/depends/json.cmake b/scripts/cmake/depends/json.cmake
index 5f0dcb29..19f1577d 100644
--- a/scripts/cmake/depends/json.cmake
+++ b/scripts/cmake/depends/json.cmake
@@ -16,20 +16,27 @@
 # License along with this library; if not, write to the Free Software
 # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA

-if(ENABLE_BUILD_USERSPACE OR ENABLE_BUILD_TEST)
+if(ENABLE_BUILD_VMM OR ENABLE_BUILD_USERSPACE OR ENABLE_BUILD_TEST)
     message(STATUS "Including dependency: json")
-
     download_dependency(
         json
         URL         ${JSON_URL}
         URL_MD5     ${JSON_URL_MD5}
     )
+
 endif()

 list(APPEND JSON_CONFIGURE_FLAGS
     -DJSON_BuildTests=OFF
 )

+if(ENABLE_BUILD_VMM)
+    add_dependency(
+        json vmm
+        CMAKE_ARGS ${JSON_CONFIGURE_FLAGS}
+    )
+endif()
+
 if(ENABLE_BUILD_USERSPACE)
     add_dependency(
         json userspace

For the first time, after applying the patch, the json build works.
Next time, I created a new a build directory and used the same commands, as the previous one,
cmake ../hypervisor -DDEFAULT_VMM=example_vmm -DEXTENSION=../libvmi_extensions
sudo make

this time, the json didn't build!! and I am getting file not found error.
Why didn't the json build, when I am building from a new directory?

I still get this error. So I copied the json.cpp into libvmi_extensions directory and included it using,
include "json.hpp"

Now I am able to do json serialization without using bfjson.h.
Would I run into any problem if I use json.hppthis way?

No, that should work, but I will also take a look at this to see if
something is wrong
On Mon, May 21, 2018 at 8:32 AM, Manohar Reddy<EMAIL_ADDRESS>wrote:

I still get this error. So I copied the json.cpp into libvmi_extensions
directory and included it using,
include "json.hpp"
Now I am able to do json serialization without using bfjson.h.
Would I run into any problem if I use json.hppthis way?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Bareflank/hypervisor/issues/674#issuecomment-390671714,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFqD45J-Z7RhZCGFpfnF13MdreR9RaCPks5t0s_lgaJpZM4UGAdj
.

This is working. something is wrong from my side.


[spi_device] V1 Signoff

Description
Ensure V1 signoff criteria are fulfilled after focus area changes have landed.

Note that this will need updates to the test plan, since generic mode has been deleted.

Some M2 DD items (e.g. removal of Generic Mode, Removing the filter CSR, Potential Logic Optimizations) should not have a significant impact in terms of expected DV effort, so I'm going to reduce this effort slightly. @johngt

Commits since Earlgrey-ES tapeout
git log Earlgrey-M2.5.2-RC0..HEAD --oneline hw/ip/spi_device/ hw/dv/sv/spi_agent/

599ab38d27 [spi_device] Update block diagram for TPM / generic mode
2d1e029c82 [spi_device] Add read pipeline diagram
1d2e3fe49a [spi_device] Remove data transfer diagram
094cb9f0f2 [spi_device] TPM port name change: rst_n -> rst_ni
2f0b93372a [spi_device] Fix up TPM synchronization between domains
4ed1a8f639 [spi_device] Add synchronous clear to spid_fifo2sram_adapter
9b5f4e05da [spi_device] Clean up TPM address check
cbda9eaf09 [spi_device] Fix up TPM command handling
0d14dd693f [docs] Fix repetitions of the definite article
39cfb3ee40 [spi_device] Remove all timing mode CSRs
4c3debe8c3 [spi_device] Document the high-speed read pipeline
7f855dc3cb [spi_device] Add pipelined reads for flash / passthrough
f28b713409 [spi_device] Remove generic mode mentions
56c127c24b [spi_device] Write mode and status bits alongside command
d914f7532d [spi_device] Enable continuously polled status registers
aff3fbd111 [reggen] Add unused we field statement for hwext
81cfbe0cfd [spi_device] Harmonize address mode syncs to byte beats
40a6acefc1 [spi_device] Relax stringent CSB pulse width requirements
61a237e197 [util/reggen] reverse order of substruct generation
f83506bbdb [spi_device] Add params for DPRAM offsets
f554d45fc8 [spi_device] Add support for 1r1w RAMs and parity init
fc8484601e [reggen,hw] Create index parameter for registers windows
726cd46d0a [spi_device] Remove generic mode
de31bdf1c2 [reggen] Remove the devmode input
963a5006cc [doc] Minor tweak to md sanitisation code
f91b5b47a4 [spi_device] Add 'features' list to spi_device.hjson
1b16ca2122 [reggen] Add mubi support SWAccess that sets/clears a reg
59f8142826 [doc] Moved badges over to using hosted images
e85f47cbfb [doc] spi_device registers and interfaces now use CMDGEN
7688e714e8 [reggen] Add initial support for version and cip_id hjson fields
fbd888eea8 Revert "[reggen] Add CIP_IDs and bump all major versions"
0ba10b3cd3 [reggen] Add CIP_IDs and bump all major versions
93783054f3 [regtool] Correct register QE assignment
Issues closed since the Earlgrey-ES tapeout
DD (& DV)

#21538
#21207
#20754
#20654
#18687
#16411
#16339
#15785
#15721
#15543
#15452
#14045
#13996
#12747
#11740
#11718
#10058

Not planned DD (& DV)

#21159
#18357
#14665
#14051
#13437
#10038
#9823
#1212

DV

#15457

Doc

#15463
#1827

Currently open issues
DD (& DV)

#21700
#21160
#18353
#18354
#15517
#14831
#12439
#12054
#10037
#10009

DV

#21111
#20964 -> PR opened for this (#21712)
#20193
#19081
#19080
#18352

Coverage report from xx/xx/xxxx
Summary

@rswarbrick / @hcallahan-lowrisc Can you review and let me know if the sign-off looks good?
Spi-device DV sign-off is definitely over V1 standards. Is it possible to sign it off at V2/V2S instead?
The screenshot above showing 52.78% progress for V2 is a bit misleading since quite a few of V2 tests on that list are part of the generic mode which is being removed from the testplan in #21579

We've just had a V1 review meeting (@a-will, @antmarzam, @hcallahan-lowrisc, @rswarbrick). Notes here.
We're happy that all V1 checklist items are addressed, although we spotted a couple of minor action items that we'll try to handle immediately.

#21862
#21863
#21864

These action items don't themselves gate V1 signoff, so we're happy to mark the block as V1 at this point.

We're technically supposed to leave this open until the specific commit that changes the state is merged, but... I rolled back spi_device to V1, not V0, so there won't be such a commit. :joy:

Oops! I'll claim that I'd carefully thought about this... :-)


Wrong frame references, playSegments() vs. goToAndStop()

Thanks for the beautiful work! I love lottie, but there seems to be something wrong with frame references.
I got a character animation in AE containing different moves and scenes. Now playing a loop with playSegments() and afterwards playing some single frames with goToAndStop(), the frame references get shifted.
Lets say the AE original has a walk loop from frame 5 to 10 and some single frame character states between 15 an 20. After playing the loop using playSegments([5,10], true), I can't play one of the frames between 15 and 20 using goToAndStop() with their original frame numbers. The first frame has obviously been shifted to 5 now and the original frames numbered 15 to 20 are now frames 10 to 15.
This is somehow confusing. If playSegments() is cropping the frame numbers, how can I reset that? And if it is cropping frames, why only the beginning and not the end?
This is what happens:
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
goToAndStop(15) shows frame 15
playSegments([5,10], true)
1 2 3 4 [5 6 7 8 9 10] 11 12 13 14 15 16 17 18 19 20
goToAndStop(15, true) shows frame 20!
goToAndStop(0, true) shows frame 5!
for goToAndStop() original frame 5 is now frame 0!
playSegments([0,5], true)
[0 1 2 3 4 5] 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
goToAndStop(15) shows frame 15!
for goToAndStop()  frame 15 is now frame 15 again!
Even more confusing, shifted frame references seem to only affect goToAndStop() but not playSegments().

Sorry, accidentially posted in wrong project.


How to run a func only once at a server shutdown？

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[x] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
@app.on_event()

Description
When use '@app.on_event()' on a multiple-worker server, I find that this handler will be called many times.
I wonder if there is any thing be called only once at a server shutdown?
Operating System
Windows
Operating System Details
Windows 11
FastAPI Version
0.70.0
Python Version
3.9
Additional Context
No response

I bet, in this situation you should use some external locking mechanism or consider usage shutdown hooks of your web-server process manager. Like
def on_exit(server):
    pass

in Gunicorn

@insomnes is right, this is not a fastAPI question.
The answer is going to depend how you run fastAPI
import time
import uvicorn
async def app(scope, receive, send):
    pass
if __name__ == "__main__":
    uvicorn.run("toto:app", host="<IP_ADDRESS>", port=5000, log_level="info", workers=2)
    time.sleep(2)
    print("LAST STEP")

INFO:     Uvicorn running on http://<IP_ADDRESS>:5000 (Press CTRL+C to quit)
INFO:     Started parent process [1566165]
INFO:     Started server process [1566169]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Started server process [1566168]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Shutting down
INFO:     Shutting down
INFO:     Waiting for application shutdown.
INFO:     Application shutdown complete.
INFO:     Finished server process [1566169]
INFO:     Finished server process [1566168]
INFO:     Stopping parent process [1566165]
LAST STEP

Process finished with exit code 0

I think you can close this issue @mattholy , thank you


dayjs init data seems not right

When I init data like this, not like moment.js can make right way to parse the Date String.
console.log(dayjs('2018-01'))

output:
Fri Dec 01 2017 00:00:00 GMT+0800 (CST

But I can solve by pass the Date, and init with new Date(string).
console.log(dayjs(new Date('2018-01')))

output:
Mon Jan 01 2018 08:00:00 GMT+0800 (CST)

希望你能看得懂...

It's a bug. However, maybe dayjs('2018-01-01') would be better?
'2018-01' could either be '2018-01-01' or '2018-01-31'

:tada: This issue has been resolved in version 1.6.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Serialization refactor step 2

Implemented null-value deserialization for Vec<u8> using Visitor.
This is part 2 of the serialization improvement efforts described in #247 .

[X] Referenced an issue explaining the need for the change
[ ] Updated all relevant documentation in docs
[X] Updated all code comments where relevant
[X] Wrote tests
[X] Updated CHANGES.md

i'm closing this in lieu of #269 . After merging step 1, it was easier to cherry-pick the working commits from this branch into a new one and open a new PR with that.


Support max width/height for thumbnails

Support setting a maximum width and height in the thumbnail template
tag. The extra arguments max_width and max_height are introduced for
this. Contrary to the existing width and height arguments, these
won't force the thumbnail to a given size, but will only shrink it if
the image is larger than the specified limits.
I did this as a quick fix for myself because I needed this functionality, but I
figured someone else might find this useful to have as well. :)

Thanks for this - I think it's a good idea, but I'm not sure about the implementation.
For example why is it possible to specify both width and max_width at the same time? Would it make more sense to just have width and height args, and an extra bool arg that determines whether the sizes are either forced to shrink/grow the image, or only shrink (as the intention with max_width and max_height)?

Will also need relevant documentation updated: https://github.com/stephenmcd/mezzanine/blob/master/docs/utilities.rst#thumbnail

Thanks for the feedback. I've pushed something I think resembles the implementation you described, together with the updated documentation. See if you find that to be closer to what you'd like. :)

Looks good! I might change the arg name, "no_grow=False" is kind of a double-negative, but leave that to me.
Thanks a lot!


Some RTD documentation not rendered due to libsndfile being missing

Our documentation is being generated, but much of the API is missing. When looking at the raw logs from the RTD builds, it appears that our version of soundfile installed through pip checks for the underlying C library, and if it is not present, it raises an exception. We need to install that library.

This issue was being masked by me having two versions of soundfile installed through pip locally. We can address this issue pretty easily by using this: https://docs.readthedocs.io/en/stable/config-file/v2.html#build-apt-packages

That fixed the issue. This one is all set.


cmd/compile: teach prove.go that {strings|bytes}.Index* return value in the range [-1 .. len(s))

The issue
Currently prove.go doesn't know that functions like strings.Index* always return value in the range [-1 .. len(s)) where s - input string / byte slice. So it emits unnecessary bounds checks in the following code:
func nextSpace(s string) string {
        n := strings.IndexByte(s, ' ')
        if n >= 0 {
                // unnecessary bounds check is generated here
                return s[n:]
        }
        return ""
}

go tip compiler generates the following assembly code for nextSpace:
TEXT nextSpace(SB)
func nextSpace(s string) string {
  0x50f040              64488b0c25f8ffffff      MOVQ FS:0xfffffff8, CX
  0x50f049              483b6110                CMPQ 0x10(CX), SP
  0x50f04d              0f8684000000            JBE 0x50f0d7
  0x50f053              4883ec28                SUBQ $0x28, SP
  0x50f057              48896c2420              MOVQ BP, 0x20(SP)
  0x50f05c              488d6c2420              LEAQ 0x20(SP), BP
        n := strings.IndexByte(s, ' ')
  0x50f061              488b442430              MOVQ 0x30(SP), AX
  0x50f066              48890424                MOVQ AX, 0(SP)
  0x50f06a              488b4c2438              MOVQ 0x38(SP), CX
  0x50f06f              48894c2408              MOVQ CX, 0x8(SP)
  0x50f074              c644241020              MOVB $0x20, 0x10(SP)
  0x50f079              e8d235efff              CALL strings.IndexByte(SB)
  0x50f07e              488b442418              MOVQ 0x18(SP), AX
        if n < 0 {
  0x50f083              4885c0                  TESTQ AX, AX
  0x50f086              7c36                    JL 0x50f0be
        return s[n:]
  0x50f088              488b4c2438              MOVQ 0x38(SP), CX

        ; The compiler may prove 0 <= n < len(s) on this line,
        ; so the following 2 lines plus runtime.panicslice on 0x50f0d0
        ; may be eliminated.
  0x50f08d              4839c8                  CMPQ CX, AX
  0x50f090              773e                    JA 0x50f0d0

  0x50f092              4829c1                  SUBQ AX, CX

        ; Additionally, the following 4 lines assume &s[0] + (len(s) - n) may exceed
        ; max word value. This is impossible, since &s[0] + len(s) doesn't exceed
        ; max word value.
        ; The compiler has enough info to disprove this in order to eliminate these lines.
  0x50f095              4889ca                  MOVQ CX, DX
  0x50f098              48f7d9                  NEGQ CX
  0x50f09b              48c1f93f                SARQ $0x3f, CX
  0x50f09f              4821c8                  ANDQ CX, AX

  0x50f0a2              488b4c2430              MOVQ 0x30(SP), CX
  0x50f0a7              4801c8                  ADDQ CX, AX
  0x50f0aa<PHONE_NUMBER>              MOVQ AX, 0x40(SP)
  0x50f0af<PHONE_NUMBER>              MOVQ DX, 0x48(SP)
  0x50f0b4              488b6c2420              MOVQ 0x20(SP), BP
  0x50f0b9              4883c428                ADDQ $0x28, SP
  0x50f0bd              c3                      RET
                return ""
  0x50f0be              0f57c0                  XORPS X0, X0
  0x50f0c1              0f11442440              MOVUPS X0, 0x40(SP)
  0x50f0c6              488b6c2420              MOVQ 0x20(SP), BP
  0x50f0cb              4883c428                ADDQ $0x28, SP
  0x50f0cf              c3                      RET
        return s[n:]
  0x50f0d0              e82b9df1ff              CALL runtime.panicslice(SB)
  0x50f0d5              0f0b                    UD2
func nextSpace(s string) string {
  0x50f0d7              e8347df4ff              CALL runtime.morestack_noctxt(SB)
  0x50f0dc              e95fffffff              JMP nextSpace(SB)

The solution

Teach the compiler that {strings|bytes}.Index* return value in the range [-1 .. len(s))
Teach the compiler that &s[0] + len(s) - n doesn't exceed max word value if 0 <= n < len(s)

This should improve performance of various parsers for text-based messages (json, xml, html, http, etc.)

cc'ing @aclements and @rasky , since they recently worked on prove.go improvements.

I don't know how much we want to teach the compiler about specific std functions. It'd be nice if there were some way to infer this instead, although I don't see how. Note that if someone was playing around with these functions in the standard library and added -2 as a special signal value, any calling code might be mis-compiled.

I don't know how much we want to teach the compiler about specific std functions. It'd be nice if there were some way to infer this instead, although I don't see how.

Probably, we could annotate return values from functions written in assembly. Such annotations may contain valid ranges for the returned function values. These annotations must be restricted only to assembly-written functions, since in theory the compiler may infer return value ranges for ordinary Go functions using the code from prove pass.

Note that if someone was playing around with these functions in the standard library and added -2 as a special signal value, any calling code might be mis-compiled.

This will violate strings.IndexByte contract, which explicitly states it returns values in the range [-1 ... len(s) )

Punting to 1.13, too late for anything major in 1.12.


Use with Unslider

How can i use this with unslider or any other slider ?
simple code like this doesn't work well with it.
  var myLazyLoad = new LazyLoad({
    elements_selector: ".lazyload",
    data_src: "original"
  });

Please detail what your case is and what are you trying to do

Sorry, it seems to work now, maybe my cache was not refreshed :smile:


Imsha Rehman leaks

Describe the bug
Steps to reproduce

Expected behaviour
Code example

Error log
Configuration
Environment

Client version:
Language version:
OS:

ClickHouse server

ClickHouse Server version:
ClickHouse Server non-default settings, if any:
CREATE TABLE statements for tables involved:
Sample data for all these tables, use clickhouse-obfuscator if necessary

bnbn

bvbv


week1_embeddings homework: Remaining TODO in the notebook

It can be shown (see original paper) that a self-consistent linear mapping between semantic spaces should be orthogonal. TODO simplify phrases

fixed


remove unnecessary iOS cordova hook logic

This change is

PR is added to the queue for testing as 1. task. (d961875)

Test (Success) 90009723 build is completed (d961875)
See https://github.com/ThaliTester/TestResults/tree/90009723d961875_remove_unnecessary_iOS_cordova_hook_logic_larryonoff/ for the logs

PR is added to the queue for testing as 2. task. (439aaa5)

Test 90009723d961875(d961875) has failed
See https://github.com/ThaliTester/TestResults/tree/90009723d961875_remove_unnecessary_iOS_cordova_hook_logic_larryonoff/ for the fail logs

Test (Success) 90009723 build is completed (439aaa5)
See https://github.com/ThaliTester/TestResults/tree/90009723439aaa5_remove_unnecessary_iOS_cordova_hook_logic_larryonoff/ for the logs

Test<PHONE_NUMBER>9aaa5(439aaa5) has failed
See https://github.com/ThaliTester/TestResults/tree/90009723439aaa5_remove_unnecessary_iOS_cordova_hook_logic_larryonoff/ for the fail logs

Reviewed 1 of 1 files at r1, 1 of 1 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from Reviewable


REST autocomplete very slow when having a large number of indexes/aliases

Hello,
I am noticing a case where the autocomplete section of the REST page (where the index / url is entered) it is very slow when accessing a cluster with hundreds of indexes (and even more aliases). It can take several minutes to load and makes the page hard to use.
It would be nice if this were faster, or even disabling autocomplete if the number of results is too large. Thanks!

I have also thousand of indices, and is the interface is not responding anymore. it consumes all the cpu usage where I installed the cerberus.

This happens also for our setup. We have 2k+ indices and 10k+ aliases (each index has in average 5 aliases) and after updating from 0.8.5 to 0.9.2, REST interface is freezing, when we try write something in path input.

@pp88888 @cantipop @orinciog Which browser/version are you using? Did you notice this effect from one version to another? I assume you have no issues with other parts of the app? Also, I imagine there is not a problem fetching the data?(when first opening the REST screen, there is  call made to /rest to fetch this info)

@lmenezes I have tested with 2 browsers:
Firefox 84.0.1
Chrome Version 87.0.4280.88 (Official Build) (x86_64)
both in OSX  10.15.7. I see the same behavior, the autocomplete become unresponsive. Other parts of the app are fine. I reviewed in network tools and I see the JSON response being served pretty quickly. (it is has 6K+ indices on it).

@lmenezes I have tested with 2 browsers:
Firefox 84.0.1
Chrome Version 87.0.4280.88 (Official Build) (x86_64)
both in OSX  10.15.7. I see the same behavior, the autocomplete become unresponsive. Other parts of the app are fine. I reviewed in network tools and I see the JSON response being served pretty quickly. (it is has 6K+ indices on it).

@lmenezes
I'm using two browsers: Firefox 84.0 and Chrome Version 87.0.4280.88 (Official Build) (64-bit) on Ubuntu 18.04.
Both are having same behavior in rest app.
/rest route is served in 600ms with 600KB received.
All other parts are ok, for example the biggest timing route is /overview with 4.4MB received in 6 seconds.

@lmenezes
I'm using two browsers: Firefox 84.0 and Chrome Version 87.0.4280.88 (Official Build) (64-bit) on Ubuntu 18.04.
Both are having same behavior in rest app.
/rest route is served in 600ms with 600KB received.
All other parts are ok, for example the biggest timing route is /overview with 4.4MB received in 6 seconds.

Did you try v0.9.3? We added a fix for #467. Basically if you have many closed indices the performance gets worse.

Did you try v0.9.3? We added a fix for #467. Basically if you have many closed indices the performance gets worse.

@moliware Sure, I will test 0.9.3, but I don't have closed indices. All 2K+ indices are open.

@moliware Sure, I will test 0.9.3, but I don't have closed indices. All 2K+ indices are open.

Hello @moliware I'm running 0.9.4 and still experience this -- fwiw are indices are open as well.

I noticed that the issue is not the REST call, but in the JS responding to the JSON payload. @moliware


Update SWIFT_VERSION in project file

@swift-ci please test OS X

Awesome, thanks @parkera! Hoping to see this pass.


Failed to import - preact in Deno 2

With the upcoming Deno 2 release we have dropped the window global. It was present in Deno 1.x, but won't be anymore in Deno 2. The transpilation code in esm.sh currently assumes that Deno === window, which breaks:
/* esm.sh - esbuild<EMAIL_ADDRESS>denonext production */
// ...snip

// This is a wrong check. The original code has `typeof window !== "undefined"`
typeof Deno<"u"&&window.__PREACT_DEVTOOLS__&& //...

Failing module

GitHub: https://github.com/preactjs/preact
npm: https://npmjs.com/package/preact

import * as devtools from<EMAIL_ADDRESS>console.log(devtools)

Error message
After running deno run I got this:
error: Uncaught (in promise) ReferenceError: window is not defined
    at https://esm.sh/stable/preact@10.15.1/denonext/devtools.js:2:159

Additional info

esm.sh version:
Deno version: 2.0.0-rc.0+2533d68

This is also relevant to Deno 1, as web workers also have no window

i found some early code that replaces typeof window to typeof Deno: https://github.com/esm-dev/esm.sh/blob/v126/server/build.go#L1009-L1015
However the code has been removed since v127, but the build output is cached. and the latest build<EMAIL_ADDRESS>is correct
i'm going the purge the module manually from cache.

@marvinhagemeister i just purged the outdated modules, can you please check again? thanks

Can confirm that this is resolved after running Deno with the --reload flag. Thanks for the quick help 👍

I apologize for the interruption here
I encountered the same problem after upgrading to deno 2
> import * as ot from "https://esm.sh/openapi-typescript"
Uncaught ReferenceError: window is not defined
    at https://esm.sh/v135/node_inspector.js:1:203

@zuisong i just fixed the builtin node ployfills which are using the `window` object, please retry with `--reload` flag


XSS flaw bugfix

GET parameter values must be sanitized before they appear in the resulting HTML.
https://wagtail.chrisdev.com/blog-index/?tag=<script>alert(1)</script>

Thanks @asteinhauser! Minus 100 points to the un-named developer who stuck the totally inappropriate |safe filter in there... :-)


Improve test coverage for Query Execution and document feature gaps.

DiceDB includes a SQL parser and query executor to support Dice-flavoured SQL (DSQL) queries on top of in-memory key-value data. This is a critical component and needs to be extremely stable and well-tested.
The tests for this component can be found under:

tests/qwatch_test.go - end-to-end test for QWATCH command, which tests query execution and message delivery.
internal/querywatcher/dsql_test.go - DSQL parser test which validates SQL query parsing.
internal/querywatcher/executor_test.go - executor unit tests which test for correct query results in the executor.

Requirements for this issue

Find feature gaps and report them under this issue, we will create new issues out of them if they are valid.
Improve test coverage with more query patterns.

Check if certain query patterns are not being validated, think combinations of different features (WHERE + ORDER BY, ORDER BY + LIMIT, etc.)
Add tests for such patterns

Try to break the QWATCH feature, and report findings.

Hi @JyotinderSingh can you assign me this?

Hi @JyotinderSingh can you assign me this?

Please feel free to begin working on this issue and report findings here. This issue can be taken up by multiple people at the same time so I won't be assigning it to anyone in particular (to avoid confusion)

Hi @JyotinderSingh, somehow the links above for tests don't seem to work.
Are these tests really present in the master branch?

Hi @JyotinderSingh, somehow the links above for tests don't seem to work.
Are these tests really present in the master branch?

They have been moved under the integration_tests directory

I see, thanks!

I think there's a discrepancy in the documentation about the syntax for DSQL.
In the documentation here: qwatch-doc, this is specified:

SELECT $key, $value  FROM 'key_pattern'
WHERE condition
ORDER BY field [ASC | DESC] LIMIT n

while the tests here: qwatch_test uses the 'like' keyword:

SELECT $key, $value WHERE $key like 'match:10?:*' ORDER BY $value desc LIMIT 3

@vaibspider yes, we recently changed it. Now we do not need FROM clause. Can you raise a PR in docs repository? it would be a great help.

Sure, will do that!

Closing the issue as PR is already merged.


Registery Remapping Failed

I installed the version the server uses of origin mod and it doesnt work. I even double checked the version the server uses and I use and still doesn't work. Please fix this. Thank You,

Make sure that you have Mob Origins installed in your client


baseURL get duplicated for the url of og:image

Even after this attempted fix: 5c08cfa7202ff2b938471c3db0d0748ee6eea71b
https://stackblitz.com/edit/nuxt-starter-cusggt

Only occurs when nuxt pages is enabled (with vue-router), if you do
mv pages/index.vue app.vue
rm -r pages

then the baseURL won't duplicate.

Can you check the reproduction? It doesn't seem right to what you're showing me

I forgot to save this stackblitz after .env created
NUXT_APP_BASE_URL=/base

It only occurs when using<EMAIL_ADDRESS>https://stackblitz.com/edit/nuxt-starter-pvaeyd (manually add .env is required), seems https://github.com/nuxt-modules/og-image/pull/231 fix this

Also on<EMAIL_ADDRESS>

Thank you @n0099, this looks like it was an issue with something upstream appending the baseURL to the host (nitro or nuxt).
The URL resolving is handled by the Nuxt Site Config module which I've pushed up a fix for in and is used in the latest RC 56 of this module.


Renamed WishListItem Model to Gifts and changed all code tied to the now Gifts Model

Approved with the group.


Add extra Icons

While tumblr doesn't allow share numbers I'd like to add the icon for tumblr and whatsapp, can this be achieved within this?

Why don’t you just read the docs?
https://github.com/sapegin/social-likes#adding-your-own-button

Hi yes sorry, I did follow what you've written. But my icons aren't showing up. So here's what I did.
added to social-likes.js
tumblr: {
popupUrl: 'http://www.tumblr.com/share/link?url={url}&description={title}',
popupWidth: 650,
popupHeight: 500
},
Added this to the flat css
.social-likes__button_tumblr{background: #34465D;}
.social-likes__icon_tumblr{background: url(http://quotepixels.com/img/tumblr.png) no-repeat 2px 3px;}
Then added the html

But here's what I get.

Would appreciate any pointers. Excellent plugin btw!

Could you post it somewhere like jsfiddle.net?

Thanks for the reply, I've put it up on codepen. With bg colour and and chars as fallback but you can take a look.
http://codepen.io/anon/pen/RNyBrV

You’re trying to add image icons to a skin that uses web font. In your case you need to add width and height to .social-likes__icon_tumblr.
(Though it’s very bad idea to mix vector and bitmap icons.)

Thanks for that, is this a font that you've created? How can I add other vectors to it?

Of course.


Fallback conflict-resolution method uses the wrong term

When the conflict optimization is not used (conflict_opt is None) the replication stream decrements its match_index. After doing so, it should also fetch the corresponding match_term from the storage layer.
Failing to do this will result in sending an incorrect prev_log_term in future AppendEntries requests, which will then be rejected, causing the replication to become stuck.

@Diggsey as always, thanks for the report. The version of the code I have been writing over on #59 does account for this issue (by going directly to its log once it receives a conflict_opt report, and using the term of the entry found in the log).
I'll marked this issue for closure once #59 lands. That work?

Yep - I haven't been keeping up with #59 so I don't know what things have already been fixed there. Feel free to close as you see fit.


Automate calendar module

The Calendar module should be connected to Google APIs and update itself along with all other dashboard data.

This is blocked pending elevated privileges on the COS Google organization.

Closing due to #14.