Add support for ignored records.

This seems to work well enough, but I want to mull it over a bit before I'm ready to :shipit:. Partially to think over the specifics, but probably more to figure out if the octodns key thing makes sense and would be able to support some of the other "special" stuff that will eventually need to be added (specifically per-provider info.)
www:
  octodns:
    ignored: true
  type: A
  value: <IP_ADDRESS>

/cc https://github.com/github/octodns/issues/49
/cc @dolvany

Decided I like this pattern, octodns key for stuff that's directing octoDNS to do something. There's a few other places it'll likely get used (configurable health check urls probably being next.)

@ross, thanks for the feature add! I am curious how this feature interacts with multiple records. Given the below example, how would I go about ignoring the A record, but not the TXT record? How would I ignore both?
www:
- ttl: 30
  type: A
  values:
  - <IP_ADDRESS>
  - <IP_ADDRESS>
- ttl: 30
  type: TXT
  value: v=spf1 -all

@ross, thanks for the feature add! I am curious how this feature interacts with multiple records. Given the below example, how would I go about ignoring the A record, but not the TXT record? How would I ignore both?

In that www is an array. Each item is a record, octodns would be a key in one or more of those.
www:
- ttl: 30
  type: A
  values:
  - <IP_ADDRESS>
  - <IP_ADDRESS>
- octodns:
    ignored: true
  ttl: 30
  type: TXT
  value: v=spf1 -all

@ross, hmm, I thought I tried that permutation, but I guess not. I took the ignored directive for a test drive just now and it works as advertised. Thanks!


org: candidates

orgs to review
### Developer tools
- [ ] fig
- [ ] opensauced
- [ ] https://github.com/beansource/awesome-orgs/issues/45

### Networking clients
- [ ] HTTPie
- [ ] Postman Labs
- [ ] Hoppscotch

### AI
- [ ] openai
- [ ] https://github.com/jina-ai

### Analytics
- [ ] https://github.com/beansource/awesome-orgs/issues/22

### Learning
- [ ] https://github.com/total-typescript
- [ ] https://github.com/freeCodeCamp
- [ ] https://github.com/30-seconds

### Security
- [ ] https://github.com/SocketDev

### Community
- [ ] https://github.com/thechangelog

### GraphQL
- [ ] https://github.com/apollographql
- [ ] https://github.com/graphql
- [ ] https://github.com/hasura

### Companies
- [ ] https://github.com/calcom

### Uncategorized
- [ ] https://github.com/vapor

https://github.com/SocketDev
https://github.com/thechangelog
https://github.com/vapor

https://github.com/upstash

https://github.com/essentialkaos

https://github.com/mdx-js

they even have their own awesome mdx


NeoDash unable to load Dashboard from Neo4j Node

I am attempting to load a saved dashboard from Neo4j into the NeoDash platform. However, I am encountering an error message that states, “Unable to load dashboard. A dashboard with the provided name could not be found.” I have verified that all configurations are correctly set. I am currently using NeoDash version 2.4.2 and Neo4j version 4.4.30 Community Edition. Here is my current configuration:
{
  // Single Sign-On (SSO) settings
  "ssoEnabled": false,
  "ssoProviders": [],
  "ssoDiscoveryUrl": "",

  // Standalone mode settings
  "standalone": true,
  "standaloneProtocol": "neo4j",
  "standaloneHost": "localhost",
  "standalonePort": "7687",
  "standaloneDatabase": "neo4j",
  "standaloneDashboardName": "DashboardName (Node label)",
  "standaloneDashboardDatabase": "neo4j",
  "standaloneDashboardURL": "",

  // Additional standalone mode settings
  "standaloneAllowLoad": true,
  "standaloneLoadFromOtherDatabases": true,
  "standaloneMultiDatabase": true,
  "standaloneDatabaseList": "neo4j",

  // Logging settings
  "loggingMode": "0",
  "loggingDatabase": "logs",

  // Custom header for the application
  "customHeader": "Custom Header"
}

Solved Issue
I’m delighted to share that I’ve resolved an issue that was initially a misunderstanding on my part. I was under the impression that the dashboard name referred to the label, when in fact, it refers to the ‘Name’ provided in the ‘Dashboard Title’ section. In an attempt to rectify the issue, I even changed the label of the node, which, in hindsight, was not the correct approach.
The solution lies in setting the ‘d.title’ of the Dashboard node in the ‘config.json’. Here’s the part of the code where the dashboard is loaded:
MATCH (d:_Neodash_Dashboard) WHERE d.title = $name RETURN d.content as dashboard ORDER by d.date DESC LIMIT 1
I hope this solution can assist others who might encounter the same problem. Happy coding!


Object of class Symfony\Component\HttpFoundation\ServerBag could not be converted to string

Bug report
What I did:
I have a table called servers. It contains two columns server_ip and server_name. I can create them in the create view, but i'm not able to edit or delete it. If I try one of those I receive the error mentioned above.
What I expected to happen:
Show the edit form or delete the entry
What happened:
It throws an ErrorExecption
ErrorException (E_RECOVERABLE_ERROR)
Object of class Symfony\Component\HttpFoundation\ServerBag could not be converted to string

What I've already tried to fix it:
Tried to rename the table.
Tried a custom route in web.php where the deletion worked
public function delete(Server $server)
    {
        $server->delete();
    }

Backpack, Laravel, PHP, DB version:
Backpack: Latest,
Laravel: Latest,
PHP: 7.1.3
MySQL: 5.7.17

Edit:
It seems that this line is causing the issue
$this->crud->setEntityNameStrings('server', 'servers');

changing the singular term to anything other solves the issue

Had the same issue, renaming the entity solved it.

Thank you for reporting this @sheriffmarley & @lucasdcrk . I can confirm the issue is happening - it was because at some point (in getCurrentEntryId() I discovered) the server name was conflicting with an already existing variable on the request.
I've corrected this on master, and we should be able to use conflicting names too, including server. It'll be available with a composer update later today, as 3.6.6, after I bundle it with a few more non-breaking changes and tag it.
Thanks again. Cheers!


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Test function link sends one to the wrong page

Under "Test functions" link under "Debug and test" tab links to the wrong page -- it's linking to Supported languages in Azure Functions

Since the link takes me to the wrong page, I can't leave this feedback for that page. So I leave it here.

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

ID: c91c3121-aea2-9a38-c44c-45cc5bbc9248
Version Independent ID: c3c5199d-cff8-f313-dfc6-41499941e505
Content: Debug PowerShell Azure Functions locally
Content Source: articles/azure-functions/functions-debug-powershell-local.md
Service: azure-functions
GitHub Login: @TylerLeonhardt
Microsoft Alias: tyleonha

The following users don't have valid GitHub IDs, or are not collaborators on this repo: ggailey


An unknown server-side error occurred while processing the command. (UnknownError:13)

I am trying to run my test using codeceptjs run Testname --steps . I have started chrome driver before executing test. I am expecting my chrome browser to start and execute the sequence of test steps. But it fails with An unknown server-side error occurred while processing the command. (UnknownError:13).
I receive an error with a message-- An unknown server-side error occurred while processing the command. (UnknownError:13) and is pointing out to me at ..\Roaming\npm\node_modules\codeceptjs\lib\helper\WebDriverIO.js:407:20. The same test was executing fine in May, 2017

[1] Starting recording promises
Emitted | suite.before ([object Object])
[1] Queued | hook WebDriverIO._beforeSuite()
[1] Queued | hook JsforceHelper._beforeSuite()
Test Accordion
[2] Starting recording promises
Emitted | test.before
[2] Queued | hook WebDriverIO._before()
[2] Queued | hook JsforceHelper._before()
Emitted | step.before (I resize window "maximize")
[2] Queued | resizeWindow: "maximize"
Emitted | step.after (I resize window "maximize")
[2] Queued | return step result
Emitted | step.before (I am on page "https://test.salesforce.com")
[2] Queued | amOnPage: "https://test.salesforce.com"
Emitted | step.after (I am on page "https://test.salesforce.com")
[2] Queued | return step result
[2] Queued | throw error TypeError: I.login is not a function
[2] Error | Error: An unknown server-side error occurred while processing the command. (UnknownError:13)
Emitted | test.failed ([object Object])
[2] Queued | hook WebDriverIO._failed()
[2] Queued | hook JsforceHelper._failed()
× "before each" hook: Before for "Test Accordion" in 20149ms
[2] Error | Error: An unknown server-side error occurred while processing the command. (UnknownError:13)
Error: An unknown server-side error occurred while processing the command. (UnknownError:13)
[2] Stopping recording promises
Emitted | test.after
[2] Queued | hook WebDriverIO._after()
[2] Queued | hook JsforceHelper._after()
[3] Starting recording promises
Emitted | suite.after ([object Object])
[3] Queued | hook WebDriverIO._afterSuite()
[3] Queued | hook JsforceHelper._afterSuite()
-- FAILURES:

TestName test "before each" hook: Before for "Test Accordion":
An unknown server-side error occurred while processing the command. (UnknownError:13)
rror: An unknown server-side error occurred while processing the command. (UnknownError:13)
at timeouts("script", 1000) - ..\AppData\Roaming\npm\node_modules\codeceptjs\lib\helper\We
bDriverIO.js:407:20

I see an error throw error TypeError: I.login is not a function in the logs. Are your actor helpers registered properly?

Also Why do you try to resize window in Before step? Why You can't set this option in codecept config?
BTW, try to run your test with current master version. Maybe there is promises chain issue that we fix already.

I have resolved the above issue, by killing my process id with port 4444. Then started my chrome browser/ started selenium- standalone server. The Actual error is not "I.login" my test was failing even before the Login test step.
Thanks for the suggestion of Resize window @APshenkin .
Closing the thread as the issue is fixed.


Update/Add Visual C++ Build Tools 2015

Tool name
Visual C++ Build Tools 2015
Tool license
https://visualstudio.microsoft.com/vs/older-downloads/
Add or update?

[X] Add
[ ] Update

Desired version
Latest
Approximate size
No response
Brief description of tool
Compiler and libraries to build C++
URL for tool's homepage
https://visualstudio.microsoft.com/vs/older-downloads/
Provide a basic test case to validate the tool's functionality.
Build a Visual Studio 2015 solution

Virtual environments affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11
[ ] Windows Server 2016
[X] Windows Server 2019
[X] Windows Server 2022

Can this tool be installed during the build?
It's several gigabytes large

Tool installation time in runtime
Long
Are you willing to submit a PR?
No response

Hello @andrew-gresyk ,
We wouldn't like to pre-install Build Tools 2015 to Windows Server 2019 and 2022 images because this component is pretty old and can cause compatibility problems with already pre-installed builds-tools and Visual Studio. Please consider installation in runtime.


Explained Variance

In several ordination (or dimensionality reduction) methods, explained variance is needed to be calculated and reported.
TreeSE object stores reduced dimensionality data, along with the data related to the ordination method itself (e.g. eigen values for PCoA or PCA).
Could a method/function for calculating the explained variance for k dimensions be handy among the miaViz package?

This is a good point, there is already some discussion in OMA beta diversity section current lines 213-221.

Sometimes a similar measure is shown for MDS/PCoA. The interpretation
is generally different, however, and hence we do not recommend using
it. PCA is a special case of PCoA with Euclidean distances.  With
non-Euclidean dissimilarities PCoA uses a trick where the pointwise
dissimilarities are first cast into similarities a Euclidean space
(with some information loss i.e. stress) and then projected to the
maximal variance axes. In this case, the maximal variance axes do not
directly reflect the correspondence of the projected distances and
original distances, as they do for PCA.

The explained variance is generally used only for PCA and other eigenvalue-based ordination methods (most notably, MDS aka PCoA) as far as I have seen. For PCoA, the interpretation is indeed somewhat different from PCA, and measuring the stress (information loss) instead might be more appropriate; although stress concerns the whole ordination rather than specific axes.
On the other hand, many researchers still use PCoA explained variances and may not be even aware of the differences. We have at least shown in OMA how to calculate this for PCoA, and described the interpretation problem.
Because this is widely used, it could make sense to provide it but I am not sure if we want to support the use of this option as a best practice that is easily and readily available through a function, rather than through an explicit programming example. We can discuss this here.
If this is provided as a function, then it could go to miaViz and probably good to calculate for all axes at one go. Such function should return the stress as well, and this can be combined with the Shepard plot (see OMA).

Since this usually given with axis caption, it can be added very easily later on. As Leo has mentioned the mathematical basis for this is sketchy at best and therefore I would avoid any functionality claiming anything different.
I would close this issue. OK?

Ok to me.


transfer-datasets.sh still references deleted variables.sh file

Following step 3 of batch ml GKE tutorial:
sh scripts/transfer-datasets.sh
scripts/transfer-datasets.sh: line 16: scripts/variables.sh: No such file or directory

#510 deleted the "obsolete" script however transfer-datasets.sh still sources from it. No clear workaround as deleting the source command from the script errors out as well.

@natea123 can you please have a look and address the feedback comments in #679?


Ensure to delete environment gracefully

What this PR does / why we need it:
To get environment deletion done gracefully, this PR adds two changes to:

check if no Piped has permission to the given environment.
delete all applications that belong to the given env.

Which issue(s) this PR fixes:
Fixes https://github.com/pipe-cd/pipe/issues/2017
Does this PR introduce a user-facing change?:

NONE

Fixed them.

/hold

/hold cancel

Fixed to use contains operator to fetch Pipeds where the EnvIds field contains the given env-id.
Once got merged, I will work on the remaining things:

Add a Firestore composite index for array-config
Support the contains operator for MySQL

/lgtm

Fixed


Add racket_langserver.

This adds in a basic configuration for the Racket langauage server.
https://github.com/jeapostrophe/racket-langserver

I'm assuming you've seen? https://github.com/neovim/nvim-lspconfig/pull/386/files
Reviewing with notes

I'm assuming you've seen? https://github.com/neovim/nvim-lspconfig/pull/386/files
Reviewing with notes

HOW DID I MISS THIS! ugh, sorry for the noise!

HOW DID I MISS THIS! ugh, sorry for the noise!

I'll give the previous author 3 days to respond, and then will merge this after you address the relevant comments.
My general rule-of-thumb is that if I use the language, it goes in immediately (since I can test it), if not, then I typically wait for at least two people to test the PR (which it seems like you two have done).

I'll give the previous author 3 days to respond, and then will merge this after you address the relevant comments.
My general rule-of-thumb is that if I use the language, it goes in immediately (since I can test it), if not, then I typically wait for at least two people to test the PR (which it seems like you two have done).

I have just one concern about this, and that is: perhaps we should restrict the default file extensions?
Here's one resource to look at https://docs.racket-lang.org/drracket/drracket-files.html, along with .scrbl (for the scribble library)

I have just one concern about this, and that is: perhaps we should restrict the default file extensions?
Here's one resource to look at https://docs.racket-lang.org/drracket/drracket-files.html, along with .scrbl (for the scribble library)

I have just one concern about this, and that is: perhaps we should restrict the default file extensions?
Here's one resource to look at docs.racket-lang.org/drracket/drracket-files.html, along with .scrbl (for the scribble library)

So my main reason for the scheme is that with vanilla neovim, if you open a .rkt file, the ft type will be scheme. So I think it's important to keep that as is.

I have just one concern about this, and that is: perhaps we should restrict the default file extensions?
Here's one resource to look at docs.racket-lang.org/drracket/drracket-files.html, along with .scrbl (for the scribble library)

So my main reason for the scheme is that with vanilla neovim, if you open a .rkt file, the ft type will be scheme. So I think it's important to keep that as is.

Alright, I think this should be good to go 👍🏼

Alright, I think this should be good to go 👍🏼

Squash your commits :)

Squash your commits :)

Also remove the default_config from docs, you don't need that anymore, it's auto generated

Also remove the default_config from docs, you don't need that anymore, it's auto generated

So now the README needs to be updated, and that's all?

So now the README needs to be updated, and that's all?

WDYM? https://github.com/neovim/nvim-lspconfig/commit/8b28c06d2490e1b582c0abc3a7f421c341f6ae7b

WDYM? https://github.com/neovim/nvim-lspconfig/commit/8b28c06d2490e1b582c0abc3a7f421c341f6ae7b

nevermind. The last time I saw the project, the info for individual LSPs was in the readme. Sorry for the noise.

nevermind. The last time I saw the project, the info for individual LSPs was in the readme. Sorry for the noise.


LevelDB Configurations Change

Since we're currently tuning parameters, if you find a good parameter setting, note it down in this ticket with a small log (for example sync size).

Found a decent configuration, average import time 2 seconds for the 465 txs blocks:
<db>
    <path>database</path>
    <vendor>leveldb</vendor>
    <enable_heap_cache>false</enable_heap_cache>
    <max_heap_cache_size>1024</max_heap_cache_size>
    <enable_db_cache>true</enable_db_cache>
    <enable_db_compression>false</enable_db_compression>
    <max_fd_alloc_size>128</max_fd_alloc_size>
    <block_size>16mB</block_size>
    <write_buffer_size>64mB</write_buffer_size>
    <cache_size>256mB</cache_size>
</db>

I've got about 2x boost.
Before:
18-03-27 17:40:52.801 INFO  SYNC [sync-ib]: <import-status: node = 222625, number = 460415, txs = 467, result = IMPORTED_BEST, time elapsed = 4732 ms>
18-03-27 17:40:55.242 ERROR SYNC [p2p-worker-8]: <assemble-and-validate-blocks node=222625>
18-03-27 17:40:57.288 INFO  SYNC [sync-ib]: <import-status: node = 222625, number = 460416, txs = 467, result = IMPORTED_BEST, time elapsed = 4487 ms>

After:
18-03-27 17:56:22.646 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460635, txs = 284, result = IMPORTED_BEST, time elapsed = 2491 ms>
18-03-27 17:56:25.518 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460636, txs = 467, result = IMPORTED_BEST, time elapsed = 2871 ms>
18-03-27 17:56:28.349 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460637, txs = 467, result = IMPORTED_BEST, time elapsed = 2831 ms>

I have seen similar  2x  results:
18-03-27 13:11:42.111 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460429, txs = 467, result = EXIST, time elapsed = 1 ms> 18-03-27 13:11:44.242 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460445, txs = 465, result = IMPORTED_BEST, time elapsed = 1274 ms> 18-03-27 13:11:45.370 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460446, txs = 467, result = IMPORTED_BEST, time elapsed = 1128 ms> 18-03-27 13:11:48.082 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460449, txs = 467, result = IMPORTED_BEST, time elapsed = 1277 ms> 18-03-27 13:11:49.456 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460450, txs = 427, result = IMPORTED_BEST, time elapsed = 1373 ms> 18-03-27 13:11:52.222 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460453, txs = 467, result = IMPORTED_BEST, time elapsed = 1163 ms> 18-03-27 13:11:53.191 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460454, txs = 425, result = IMPORTED_BEST, time elapsed = 969 ms> 18-03-27 13:11:54.802 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460456, txs = 467, result = IMPORTED_BEST, time elapsed = 1086 ms> 18-03-27 13:12:07.158 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460464, txs = 467, result = IMPORTED_BEST, time elapsed = 820 ms> 18-03-27 13:12:12.491 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460465, txs = 440, result = IMPORTED_BEST, time elapsed = 1627 ms> 18-03-27 13:12:15.727 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460471, txs = 467, result = IMPORTED_BEST, time elapsed = 937 ms> 18-03-27 13:12:27.178 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460479, txs = 450, result = IMPORTED_BEST, time elapsed = 874 ms> 18-03-27 13:12:29.801 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460480, txs = 467, result = IMPORTED_BEST, time elapsed = 820 ms> 18-03-27 13:12:30.738 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460481, txs = 467, result = IMPORTED_BEST, time elapsed = 937 ms> 18-03-27 13:12:31.486 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460482, txs = 438, result = IMPORTED_BEST, time elapsed = 748 ms> 18-03-27 13:12:33.855 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460487, txs = 402, result = IMPORTED_BEST, time elapsed = 665 ms> 18-03-27 13:12:35.907 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460490, txs = 467, result = IMPORTED_BEST, time elapsed = 681 ms> 18-03-27 13:12:36.719 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460491, txs = 467, result = IMPORTED_BEST, time elapsed = 812 ms> 18-03-27 13:12:40.026 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460498, txs = 411, result = IMPORTED_BEST, time elapsed = 744 ms> 18-03-27 13:12:41.281 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460500, txs = 467, result = IMPORTED_BEST, time elapsed = 824 ms> 18-03-27 13:12:42.223 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460501, txs = 467, result = IMPORTED_BEST, time elapsed = 942 ms> 18-03-27 13:12:44.277 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460506, txs = 409, result = IMPORTED_BEST, time elapsed = 615 ms> 18-03-27 13:12:45.381 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460508, txs = 467, result = IMPORTED_BEST, time elapsed = 764 ms> 18-03-27 13:12:46.380 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460509, txs = 467, result = IMPORTED_BEST, time elapsed = 999 ms> 18-03-27 13:12:47.740 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460511, txs = 467, result = IMPORTED_BEST, time elapsed = 775 ms> 18-03-27 13:12:48.562 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460512, txs = 467, result = IMPORTED_BEST, time elapsed = 821 ms> 18-03-27 13:12:49.433 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460513, txs = 467, result = IMPORTED_BEST, time elapsed = 871 ms> 18-03-27 13:12:51.783 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460516, txs = 433, result = IMPORTED_BEST, time elapsed = 895 ms> 18-03-27 13:12:53.153 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460518, txs = 467, result = IMPORTED_BEST, time elapsed = 913 ms> 18-03-27 13:12:56.178 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460521, txs = 467, result = IMPORTED_BEST, time elapsed = 1355 ms> 18-03-27 13:12:57.162 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460522, txs = 467, result = IMPORTED_BEST, time elapsed = 984 ms> 18-03-27 13:12:58.291 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460524, txs = 467, result = IMPORTED_BEST, time elapsed = 763 ms> 18-03-27 13:12:59.164 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460525, txs = 467, result = IMPORTED_BEST, time elapsed = 873 ms> 18-03-27 13:13:00.576 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460528, txs = 467, result = IMPORTED_BEST, time elapsed = 599 ms> 18-03-27 13:13:02.483 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460530, txs = 467, result = IMPORTED_BEST, time elapsed = 886 ms> 18-03-27 13:13:03.780 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460531, txs = 467, result = IMPORTED_BEST, time elapsed = 1297 ms> 18-03-27 13:13:04.594 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460532, txs = 438, result = IMPORTED_BEST, time elapsed = 814 ms> 18-03-27 13:13:06.615 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460536, txs = 467, result = IMPORTED_BEST, time elapsed = 707 ms> 18-03-27 13:13:07.463 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460537, txs = 446, result = IMPORTED_BEST, time elapsed = 847 ms> 18-03-27 13:13:08.430 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460538, txs = 467, result = IMPORTED_BEST, time elapsed = 967 ms> 18-03-27 13:13:10.248 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460540, txs = 467, result = IMPORTED_BEST, time elapsed = 840 ms> 18-03-27 13:13:11.224 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460541, txs = 451, result = IMPORTED_BEST, time elapsed = 955 ms> 18-03-27 13:13:15.053 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460549, txs = 467, result = IMPORTED_BEST, time elapsed = 867 ms> 18-03-27 13:13:15.897 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460550, txs = 467, result = IMPORTED_BEST, time elapsed = 844 ms> 18-03-27 13:13:23.608 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460555, txs = 467, result = IMPORTED_BEST, time elapsed = 987 ms> 18-03-27 13:13:24.876 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460557, txs = 467, result = IMPORTED_BEST, time elapsed = 708 ms> 18-03-27 13:13:26.136 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460558, txs = 409, result = IMPORTED_BEST, time elapsed = 824 ms> 18-03-27 13:13:27.989 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460562, txs = 466, result = IMPORTED_BEST, time elapsed = 837 ms> 18-03-27 13:13:29.931 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460566, txs = 423, result = IMPORTED_BEST, time elapsed = 723 ms> 18-03-27 13:13:50.752 INFO  SYNC [sync-ib]: <import-status: node = d9242b, number = 460570, txs = 467, result = IMPORTED_BEST, time elapsed = 1627 ms> 18-03-27 13:13:53.181 INFO  SYNC [sync-ib]: <import-status: node = d9242b, number = 460572, txs = 467, result = IMPORTED_BEST, time elapsed = 1377 ms> 18-03-27 13:14:03.456 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460578, txs = 434, result = IMPORTED_BEST, time elapsed = 1232 ms> 18-03-27 13:14:04.742 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460579, txs = 467, result = IMPORTED_BEST, time elapsed = 1285 ms> 18-03-27 13:14:05.933 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460580, txs = 467, result = IMPORTED_BEST, time elapsed = 1190 ms> 18-03-27 13:14:22.211 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460584, txs = 467, result = IMPORTED_BEST, time elapsed = 1226 ms> 18-03-27 13:14:23.529 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460585, txs = 435, result = IMPORTED_BEST, time elapsed = 1317 ms> 18-03-27 13:14:33.476 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460590, txs = 467, result = IMPORTED_BEST, time elapsed = 1463 ms> 18-03-27 13:14:34.672 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460591, txs = 467, result = IMPORTED_BEST, time elapsed = 1196 ms> 18-03-27 13:14:36.141 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460592, txs = 467, result = IMPORTED_BEST, time elapsed = 1469 ms> 18-03-27 13:14:37.486 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460593, txs = 467, result = IMPORTED_BEST, time elapsed = 1345 ms> 18-03-27 13:14:39.014 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460594, txs = 467, result = IMPORTED_BEST, time elapsed = 1528 ms> 18-03-27 13:14:40.444 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460595, txs = 467, result = IMPORTED_BEST, time elapsed = 1429 ms> 18-03-27 13:14:41.567 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460596, txs = 467, result = IMPORTED_BEST, time elapsed = 1122 ms> 18-03-27 13:14:43.108 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460598, txs = 467, result = IMPORTED_BEST, time elapsed = 721 ms> 18-03-27 13:14:44.013 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460599, txs = 467, result = IMPORTED_BEST, time elapsed = 905 ms> 18-03-27 13:14:44.891 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460600, txs = 467, result = IMPORTED_BEST, time elapsed = 877 ms> 18-03-27 13:14:45.766 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460601, txs = 467, result = IMPORTED_BEST, time elapsed = 875 ms> 18-03-27 13:14:46.413 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460602, txs = 467, result = IMPORTED_BEST, time elapsed = 647 ms> 18-03-27 13:14:47.260 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460603, txs = 467, result = IMPORTED_BEST, time elapsed = 847 ms> 18-03-27 13:14:48.320 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460604, txs = 444, result = IMPORTED_BEST, time elapsed = 1060 ms> 18-03-27 13:14:57.619 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460607, txs = 450, result = IMPORTED_BEST, time elapsed = 1060 ms> 18-03-27 13:14:58.665 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460608, txs = 467, result = IMPORTED_BEST, time elapsed = 1046 ms> 18-03-27 13:15:07.648 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460614, txs = 437, result = IMPORTED_BEST, time elapsed = 1285 ms> 18-03-27 13:15:11.419 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460621, txs = 467, result = IMPORTED_BEST, time elapsed = 846 ms> 18-03-27 13:15:12.134 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460622, txs = 467, result = IMPORTED_BEST, time elapsed = 714 ms> 18-03-27 13:15:13.005 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460623, txs = 467, result = IMPORTED_BEST, time elapsed = 870 ms> 18-03-27 13:15:13.849 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460624, txs = 467, result = IMPORTED_BEST, time elapsed = 844 ms> 18-03-27 13:15:21.153 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460634, txs = 467, result = IMPORTED_BEST, time elapsed = 1134 ms> 18-03-27 13:15:22.617 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460636, txs = 467, result = IMPORTED_BEST, time elapsed = 953 ms> 18-03-27 13:15:23.333 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460637, txs = 467, result = IMPORTED_BEST, time elapsed = 716 ms> 18-03-27 13:15:24.056 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460638, txs = 467, result = IMPORTED_BEST, time elapsed = 723 ms> 18-03-27 13:15:24.678 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460639, txs = 467, result = IMPORTED_BEST, time elapsed = 621 ms> 18-03-27 13:15:31.241 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460653, txs = 467, result = IMPORTED_BEST, time elapsed = 900 ms> 18-03-27 13:15:32.125 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460654, txs = 467, result = IMPORTED_BEST, time elapsed = 883 ms> 18-03-27 13:15:34.843 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460658, txs = 413, result = IMPORTED_BEST, time elapsed = 887 ms> 18-03-27 13:15:36.122 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460660, txs = 467, result = IMPORTED_BEST, time elapsed = 644 ms> 18-03-27 13:15:38.373 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460663, txs = 460, result = IMPORTED_BEST, time elapsed = 740 ms> 18-03-27 13:15:39.547 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460665, txs = 467, result = IMPORTED_BEST, time elapsed = 916 ms> 18-03-27 13:15:44.528 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460668, txs = 467, result = IMPORTED_BEST, time elapsed = 918 ms> 18-03-27 13:15:47.081 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460674, txs = 467, result = IMPORTED_BEST, time elapsed = 784 ms> 18-03-27 13:15:48.578 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460675, txs = 419, result = IMPORTED_BEST, time elapsed = 937 ms> 18-03-27 13:15:50.622 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460679, txs = 467, result = IMPORTED_BEST, time elapsed = 948 ms> 18-03-27 13:15:52.268 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460680, txs = 467, result = IMPORTED_BEST, time elapsed = 759 ms> 18-03-27 13:15:52.949 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460681, txs = 467, result = IMPORTED_BEST, time elapsed = 681 ms> 18-03-27 13:15:56.601 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460684, txs = 467, result = IMPORTED_BEST, time elapsed = 1091 ms> 18-03-27 13:15:58.904 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460687, txs = 467, result = IMPORTED_BEST, time elapsed = 1121 ms> 18-03-27 13:16:00.101 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460688, txs = 467, result = IMPORTED_BEST, time elapsed = 1197 ms> 18-03-27 13:16:02.192 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460691, txs = 444, result = IMPORTED_BEST, time elapsed = 912 ms> 18-03-27 13:16:03.027 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460692, txs = 409, result = IMPORTED_BEST, time elapsed = 835 ms> 18-03-27 13:16:04.092 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460693, txs = 467, result = IMPORTED_BEST, time elapsed = 1065 ms> 18-03-27 13:16:07.610 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460696, txs = 467, result = IMPORTED_BEST, time elapsed = 1897 ms> 18-03-27 13:16:11.228 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460703, txs = 405, result = IMPORTED_BEST, time elapsed = 1307 ms> 18-03-27 13:16:12.172 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460704, txs = 467, result = IMPORTED_BEST, time elapsed = 944 ms> 18-03-27 13:16:14.721 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460706, txs = 467, result = IMPORTED_BEST, time elapsed = 1605 ms> 18-03-27 13:16:16.345 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460707, txs = 467, result = IMPORTED_BEST, time elapsed = 1623 ms> 18-03-27 13:16:17.381 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460708, txs = 467, result = IMPORTED_BEST, time elapsed = 1036 ms> 18-03-27 13:16:20.253 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460712, txs = 467, result = IMPORTED_BEST, time elapsed = 1182 ms> 18-03-27 13:16:21.254 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460713, txs = 467, result = IMPORTED_BEST, time elapsed = 1001 ms> 18-03-27 13:16:23.707 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460717, txs = 467, result = IMPORTED_BEST, time elapsed = 662 ms> 18-03-27 13:16:24.347 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460718, txs = 467, result = IMPORTED_BEST, time elapsed = 640 ms> 18-03-27 13:16:25.696 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460720, txs = 467, result = IMPORTED_BEST, time elapsed = 734 ms> 18-03-27 13:16:26.324 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460721, txs = 431, result = IMPORTED_BEST, time elapsed = 628 ms> 18-03-27 13:16:29.924 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460724, txs = 467, result = IMPORTED_BEST, time elapsed = 1173 ms> 18-03-27 13:16:32.167 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460725, txs = 467, result = IMPORTED_BEST, time elapsed = 2242 ms> 18-03-27 13:16:34.466 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460726, txs = 467, result = IMPORTED_BEST, time elapsed = 1422 ms> 18-03-27 13:16:35.378 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460727, txs = 467, result = IMPORTED_BEST, time elapsed = 912 ms> 18-03-27 13:16:37.732 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460729, txs = 467, result = IMPORTED_BEST, time elapsed = 1514 ms> 18-03-27 13:16:39.273 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460730, txs = 467, result = IMPORTED_BEST, time elapsed = 1541 ms> 18-03-27 13:16:40.603 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460731, txs = 467, result = IMPORTED_BEST, time elapsed = 1330 ms> 18-03-27 13:16:49.480 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460741, txs = 467, result = IMPORTED_BEST, time elapsed = 1059 ms> 18-03-27 13:16:50.423 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460742, txs = 407, result = IMPORTED_BEST, time elapsed = 943 ms> 18-03-27 13:16:52.944 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460744, txs = 467, result = IMPORTED_BEST, time elapsed = 821 ms> 18-03-27 13:16:53.990 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460745, txs = 467, result = IMPORTED_BEST, time elapsed = 1046 ms> 18-03-27 13:16:55.310 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460746, txs = 467, result = IMPORTED_BEST, time elapsed = 1320 ms> 18-03-27 13:16:56.346 INFO  SYNC [sync-ib]: <import-status: node = f9ea8c, number = 460747, txs = 467, result = IMPORTED_BEST, time elapsed = 1035 ms>


PacReq: Microsoft Edge Beta and Dev.

 Web browser created and developed by Microsoft.
URL:  https://www.microsoftedgeinsider.com/en-us/download?platform=linux-deb
Building Guide:  Closed-source.

Partially fixed with #254

@RDKRACZ as a side note, make separate issues for each request you make. It's easier for us to manage and process your requests then.

Fixed completely by #254 and #255


docs(components): fixing up story book stories

Description
Some minor fixes to import the covalent componets docs experience
What's included?

Fixed broken links on homepage
Imports on some stories that import other componts
Set autodocs option and using 'Overview' as default docs name for component

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

v7.4.3
GitHub release

Your semantic-release bot :package::rocket:


feat: displaying transaction fee

Displaying a simple transaction fee after transaction execution
This PR closes #320

PR seems to be complete, however, there's strange bug related to tracing from "send" module. It prints "Sending transaction ..." twice
https://github.com/near/near-cli-rs/blob/8904db755435ee8c6ccb5bebf47fa55f88ada018/src/transaction_signature_options/send/mod.rs#L13


Verify localized content has updated useSwaggerUI fix

[ ] webapi-help-pages-using-swagger (multiple translations):

https://github.com/dotnet/AspNetCore.Docs.ja-jp/blob/1f5a72104e002c33aa4355a80901a9852852b219/aspnetcore/tutorials/web-api-help-pages-using-swagger/samples/3.0/TodoApi.Swashbuckle/readme.md?plain=1#L53
https://github.com/dotnet/AspNetCore.Docs.zh-cn/blob/e542687dc961d9d1d49e5236b73f55cdff4cf7c3/aspnetcore/tutorials/web-api-help-pages-using-swagger/samples/3.0/TodoApi.Swashbuckle/readme.md?plain=1#L53

Replacing permlinks to tree/live/ links, currently none of these have been updated.
[ ] https://github.com/dotnet/AspNetCore.Docs.ja-jp/tree/live/aspnetcore/tutorials/web-api-help-pages-using-swagger/samples/3.0/TodoApi.Swashbuckle/readme.md?plain=1#L53
[ ] https://github.com/dotnet/AspNetCore.Docs.zh-cn/tree/live/aspnetcore/tutorials/web-api-help-pages-using-swagger/samples/3.0/TodoApi.Swashbuckle/readme.md?plain=1#L53

Associated WorkItem - 248784

Completed


Excuse me, I meet with this problem

when I run the bash ： bash eval_AMRbart_amrparsing.sh /path/to/fine-tuned/AMRBART/ gpu_id，I meet with this problem:
Global seed set to 42
Traceback (most recent call last):
File "/home/jsj201-4/mount1/jym/AMR-Parser/AMRBART-main/fine-tune/run_amrparsing.py", line 157, in
main(args)
File "/home/jsj201-4/mount1/jym/AMR-Parser/AMRBART-main/fine-tune/run_amrparsing.py", line 91, in main
raw_graph=False,
File "/home/jsj201-4/mount1/jym/AMR-Parser/AMRBART-main/spring/spring_amr/tokenization_bart.py", line 44, in from_pretrained
inst = super().from_pretrained(pretrained_model_path, *args, **kwargs)
File "/home/jsj201-4/.conda/envs/kinyum/lib/python3.6/site-packages/transformers/tokenization_utils_base.py", line 1708, in from_pretrained
raise EnvironmentError(msg)
OSError: Can't load tokenizer for '../../../data/pretrained-model/bart-large'. Make sure that:

'../../../data/pretrained-model/bart-large' is a correct model identifier listed on 'https://huggingface.co/models'

or '../../../data/pretrained-model/bart-large' is the correct path to a directory containing relevant tokenizer files

so what should I do?

Hi,
You can replace "../../../data/pretrained-model/bart-large" with "facebook/bart-large" if your device has access to the Internet， otherwise replace it with the directory of the pre-trained model (it can be downloaded here).


Remove deprecated and purely documentational argument providing_args in Django integrations

In Django 3.1 the purely documentational feature of sending in providing_args when creating a Signal was deprecated:
https://docs.djangoproject.com/en/3.1/releases/3.1/#id2

The purely documentational providing_args argument for Signal is deprecated. If you rely on this argument as documentation, you can move the text to a code comment or docstring.

This removes the argument so that we don't get deprecation warnings.
The feature has been purely documentational since 1.8 so this shouldn't break anybody's code.
What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes

[x] No

[x] You consent that the copyright of your pull request source code belongs to Authlib's author.

Thanks


Artifacts are not editable using ManagementConsole

Description
Hi Team,
In EI 6.6.0 Update level 144 we cannot edit below Artifacts that deployed from a car file through the console.
-MessageProcessors.
-MessageStores.
-Templates.
-Sequences.
-Endpoints.
-Local entries.
Steps to Reproduce
Deploy a car file that includes above Artifacts and try to edit the above Artifacts through the console.
Affected Component
MI
Version
EI 6.6.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
EI 6.6.0

This issue has already been fixed in the master branch.


[Issue] Adding react & react-native types on root devDependencies causing expo throw RNCSafeAreaProvider error

Current Behavior
adding this to root package.json on newly created tamagui monorepo causing error on expo
  "devDependencies": {
    "@types/react": "^18.0.17",
    "@types/react-native": "^0.69.5"
  },

Expected Behavior

Expo app runs normally without error

Tamagui Version
latest / 1.35.8

Reproduction
- `npm create tamagui`
- select monorepo (next-expo-solito)
- choose no when asked install dependencies
- add this to root package.json
`
  "devDependencies": {
    "@types/react": "^18.0.17",
    "@types/react-native": "^0.69.5"
  },
`
- run `yarn install`
- run `yarn native --clear`

System Info
System:
    OS: macOS 13.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 204.23 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.19.0 - ~/.nvm/versions/node/v16.19.0/bin/node
    Yarn: 3.5.0 - /opt/homebrew/bin/yarn
    npm: 8.19.3 - ~/.nvm/versions/node/v16.19.0/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 114.0.5735.133
    Firefox: 108.0.1
    Safari: 16.2
  npmPackages:
    @babel/runtime: ^7.18.9 => 7.21.0
    @manypkg/cli: ^0.19.1 => 0.19.2
    @react-native-community/eslint-config: 2.0.0 => 2.0.0
    @typescript-eslint/eslint-plugin: ^5.37.0 => 5.60.0
    @typescript-eslint/parser: ^5.37.0 => 5.60.0
    check-dependency-version-consistency: ^3.0.3 => 3.0.3
    eslint: ^8.21.0 => 8.39.0
    node-gyp: ^9.3.1 => 9.3.1
    prettier: ^2.7.1 => 2.8.8
    turbo: ^1.10.3 => 1.10.3
    typescript: ^5.1.3 => 5.1.3

If you take a look the dev-dependencies are already installed in your package.json under packages/app

If you take a look the dev-dependencies are already installed in your package.json under packages/app

Yea, I know I report this because initially, it caused an error on my ongoing project when I tried to migrate my old monorepo structure to this version hence, I pinpointed the issue and finally found this


Docs: fix open space planner profiling readme

@unacao why delete the profiling_email.png without deleting the md part includes this png?

@unacao why delete the profiling_email.png without deleting the md part includes this png?

I didn't delete it, it is replaced


Multiple "old kanjis"

Currently, an old kanji is assigned to a new kanji. However, there are cases where several old kanji are assigned to one new kanji.
E.g.

邊 邉 → 辺
辨 辯 瓣 → 弁

Not in Joyo-kanjis but also:

鬪 鬭 → 闘

Thus, we should re-consider the Kanji struct.
// Kanji is a struct that represents a Joyo Kanji.
type Kanji struct {
	// Yomi is the reading info of the Kanji.
	Yomi Yomi `json:"yomi,omitempty"`
	// ShinJitai is the Joyo Kanji in new kanji form.
	ShinJitai KanjiChar `json:"joyo_kanji,omitempty"`
	// KyuJitai is the old kanji form which is mapped to the shinjitai.
	KyuJitai KanjiChar `json:"kyu_jitai,omitempty"`
	// IsKyuJitai is true if the map key is a KyuJitai.
	IsKyuJitai bool `json:"-"`
}

Since multiple kyu-jitai (old form kanji) to a single shin-jitai (new form of kanji) are not much, we decided to create a special map.
https://github.com/KEINOS/go-joyokanjis/blob/5325387626baa45050708ba3ad59c1a668258d87/kanjis/kanji/non_joyo_old2new_map.go#L5-L25
NonJoyoOld2NewMap is a key-value map for old-kanji to new-kanji that are not in Joyo Kanjis.
Test case for this issue
https://github.com/KEINOS/go-joyokanjis/blob/5325387626baa45050708ba3ad59c1a668258d87/kanjis/issues_test.go#L9-L27


Typescript with amd (requirejs) import(include/load) custom jquery plugin into mudule

How do you make the compiled typescript file include a jquery plugin amd module in the final compiled js file in the defines list of the module requiring the plugin eg currently output is  define(["require", "exports", "jquery"]... instead of
define(["require", "exports", "jquery" ,"myplugin"],.... which will allow the plugin to work.
I have the following greenify.js a Jquery plugin
   define(["jquery"], function($){
      $.fn.greenify = function() {
      this.css( "color", "green" );
     return this;
    };
 });

greenify.d.ts
interface JQuery
{
   greenify():JQuery;
}

app.ts
import * as $ from "jquery";

var hide = true;
$("button").click(function(){
if(hide){
  $("p").greenify();
  hide = false;
 }else{
   $("p").css( "color", "black" );
   hide = true;
  }
 });

With the usual typescript config ,typings config and jquery d.ts files.this compiles to app.js which does not include greenify in the ["require", "exports", "jquery"] list
  define(["require", "exports", "jquery"], function (require, exports, $) {
  "use strict";
  var hide = true;
   $("button").click(function () {
   if (hide) {
       $("p").greenify();
       hide = false;
   }
   else {
       $("p").css("color", "black");
       hide = true;
   }
    });
 });

Now using requirejs the greenify module will not be loaded.How can one make the compiled file include the greenify module to avoid the TypeError: $(...).greenify is not a function

greenify.d.ts
interface JQuery
{
   greenify():JQuery;
}
declare module "greenify" { }

app.ts
import * as $ from "jquery";
import "greenify";

var hide = true;
$("button").click(function(){
if(hide){
  $("p").greenify();
  hide = false;
 }else{
   $("p").css( "color", "black" );
   hide = true;
  }
 });

@aluanhaddad  out of the (way too many) versions of import statements, I've never seen this one before:
import "mod_name" .  However, I think the key for me to get this working, is I have learned the hard way  , typescript wants everything to be a module, even though all I ever wanted to do is mandate requireJS style syntax to download a (js only , no .ts equivalent) dependency . Thanks

More documentation about modules can be found at http://www.typescriptlang.org/docs/handbook/modules.html

I got a problem about import "mod_name" operation.
If not import the plugin, but access plugin related interface, tsc will not raise any errors. It is really strange and not good.
Reproducing
pre-install
mkdir test
cd test
npm install @types/jquery@2 @types/bootstrap@3  # bootstrap is a jquery plugin

create a file: test.ts
import * as $ from "jquery";
// import "bootstrap";

$(`[data-toggle="tooltip"]`).tooltip(); // `.tooltip()` defined in bootstrap.

run
tsc test.ts  # no error

rm -r node_modules/@types/bootstrap/  # remove plugins from filesystem...
tsc test.ts  #print:  test.ts(4,30): error TS2339: Property 'tooltip' does not exist on type 'JQuery'.

Both tsc 2.0.3 and 2.1.0-dev.20161005 has the same behavior. (System is ubuntu 16.04 and nodejs == v4.2.6)
Is it a bug or I miss something?


unhandled 'which' stderror prompt during vagrant build

There is a unhandled stderror in build.sh which will be prompt during vagrant build.

Vagrant\oxar\build.sh
Line 124: if [ "$(which ratom)" == "" ]; then

vagrant prompting after bash debug enable:

==> default: * Installing ratom *
==> default: ++ which ratom
==> default: which: no ratom in (/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)
==> default: + '[' '' == '' ']'
==> default: + cd /tmp/vagrant-deploy

it should be fixed as below.
- if [ "$(which ratom)" == "" ]; then
+ if [ "$(which ratom 2> /dev/null)" == "" ]; then

Testing after update:

==> default: * Installing ratom *
==> default: ++ which ratom
==> default: + '[' '' == '' ']'
==> default: + cd /tmp/vagrant-deploy

Same issue in

Vagrant\oxar\scripts\packages.sh
Line 105:   #13: Bower support (since node.js will be installed by default)
Line 106:   echo; echo * Installing Bower *; echo
Line 107:   if [ "$(which bower)" == "" ]; then
Line 108:     npm install -g bower


Cluster settings can enter an invalid state

Reproduction
Steps:

Enable PA on a node
Enable RCA/Logging on a node
Enable RCA/Logging on the cluster

Result:
cluster state
{
    "currentPerformanceAnalyzerClusterState": 2,
    "shardsPerCollection": 0
}

node state
{
    "performanceAnalyzerEnabled": false,
    "rcaEnabled": true,
    "loggingEnabled": false,
    "shardsPerCollection": 0
}

Another possibly undesireable state:
Steps:

Enable PA on a node
Enable RCA/Logging on the cluster

Result:
cluster state
{
    "currentPerformanceAnalyzerClusterState": 2,
    "shardsPerCollection": 0
}

node state
{
    "performanceAnalyzerEnabled": false,
    "rcaEnabled": false,
    "loggingEnabled": false,
    "shardsPerCollection": 0
}

RCA/Logging cluster settings is guarded by the node state, not the cluster state.  So, a the cluster state can be made invalid (rca/logging with no pa -- case 2 from above). An invalid cluster state can create an invalid node state (cluster rca/logging with no pa turns off node pa but does not change node rca/logging -- case 1 from above).
Ideally, we would prevent the initiation of an invalid cluster state (case 2) and reset the node rca/logging state if an invalid cluster state is attempted (case 1).


Integrate editor

I have some trouble runing it on local and Heroku deployment failing (https://busy5-pr-573.herokuapp.com/). Can you try to reset your node_module and see if you got same issue than me? Here is what i get:

You probably forgot to run yarn install.
I fixed the issue on heroku. Had to switch to memory history on non-browser environments.

I still need to test it fully but for now i have some small inputs:

Seem like we lost bold text on username and on feed post title, probably because of antd update.
Before: https://user-images.githubusercontent.com/16245250/28360615-34e162f0-6ca0-11e7-9c90-a8e95a228d1b.png
After: https://user-images.githubusercontent.com/16245250/28360631-3f2bf0f4-6ca0-11e7-815e-dbfed0625994.png
Can we have bold back?
For topics, we dont need autocomplete, it feel more confusing than a real help actually.
We can remove the "*" (required) on Title and Topics and "Write your story" label.

On localhost when i try to post i will get an error from the blockchain but nothing will appear on the interface. The error look like this:

This come from the field json_metadata. I can see in error detail that it's a json object while it should be a stringified object. If i stringify the jsonMetadata var it's working fine.

Forget my last review, i had not updated node_module folder properly. It's now working fine in local.

Some suggestions:

Can we have a sidebar right? We would add later some guideline to help post author.
Can we have the button submit with the label "Post", with fixed width and aligned in right?
In the same level of the button can we have "Mardown support" indication? Similar to GitHub

markdown preview quote ( >) and code (``) does not work

i suggest we also had (like steemit) the Rewards option (3):

100% Power up
50%/50
Declined

seems like it has some line break issue when type Enter once, it will not line break in many cases

Reward option require changes on SC2 SDK we can work on this later.

Looks like antd disables default styles of lists so I added styles for inline and multiline code, quotes and lists.
In markdown to add new paragraph you have to add one empty line between text, like this:

Really great work! Latest changes in the style then i think we good:

Add loading icon inside button when submit is processing
Change Create new post button label to Post


Email templates migration

Features

Added Template model and created pivot tables for Templates

[Delivers #120757529]

@EvanBarbour3

@wnowicki :)

@wnowicki

waiting for checks


Introduce rapids_cuda_patch_toolkit

Allows rapids-cmake patch CUDAToolkit to fix missing cublas and cusolver dependencies.
https://gitlab.kitware.com/cmake/cmake/-/merge_requests/7633

@trxcllnt This should fix the issues you have seen with static linking in cugraph / cuml / raft

@gpucibot merge


Why grow a Garden

The idea here is that we have a document we can share with communities who may be interested in growing a Garden (perhaps housed in the Wiki?).
It’s true there are lots of great resources lying around: the forum is full of gems, Luke has published wonderful posts introducing both Celeste and Gardens,  and the Commons Stack has a pretty good post on conviction voting, but we don't seem to have a simple, self-contained overview of what these building blocks (Covenant/Gardens agreements, Celeste, Conviction voting) enable when used in combination, and how they improve on the status quo.
We should endeavour to explain as simply as possible:

how a Garden agreement + Conviction voting + Celeste allow for more nuanced and complex governance, which in turn enables true DAOs (and why that matters)

how a Garden agreement + Celeste ensure community values are upheld over the long-term (for example, by giving small holders the power to keep whales in check)

how Conviction voting gives small holders the agency to contribute. And how it solves the problems associated with: governance attacks, low participation, and the overall inability to effectively prioritise and decide when there are many potential options all competing for consideration at once.

Who is the audience?
#1 If the audience is outside of the crypto space...
I would go high level and stay high level... no need to talk about CV at all... it is just the way.
The big theme is
Economic models can work where business models don't... If your choice is collect donations or asking for volunteers... well you are pretty screwed... good luck begging for people to sacrifice.
If you can have business model and sell something... well starting an economy isn't as much of an improvement... You can probably seek investment for your company and create a revenue + ownership shares model. Ownership shares are effectively an economic model...
You can't issue shares very easily if you are just a community creating shared value.
You can create an economy tho... this is 10x better than all possible alternatives.

I'd be very surprised if the first gardens were started by people outside of the crypto space.
I think the target audience at this stage is more teams in crypto that are thinking about governance and how best to move forward with either creating a DAO or upgrading their existing governance structure.
With respect to the latter, I've been talking with Julien from  Unlock Protocol, for example (hardly someone new to this space).
I think we have to do our best to challenge the following assumption (image attached below) which has come up a lot since I posted my essay on the importance of community before product/market fit), so I'm afraid we're going to have to dig deep into the weeds a little bit.
In particular, we need to make it clear how Conviction voting ∪ Celeste ∪ Covenant ∪ Common Pool can result in more effective governance, and show people inside this space how a radically better world is possible.

Sorry i wanted to add the second section as well... I was writing it in other calls... so it was slow

No worries!
I think comparing and contrasting with other options is a great idea.

Rather than just docs, I'm now seeing this more as a series of blog posts.
Perhaps we can have two streams here. One on effective governance (where we explain the possibilities afforded by Conviction voting ∪ Celeste ∪ a Covenant ∪ a Common Pool)
And a second on comparing and contrasting with the options available, Compound, DAOStack, etc.

Integrated in articles


need developer instructions for how to point correctly at dev builds of matrix-ios-sdk and matrix-ios-kit

i did this.


Legend in AMSS Plots

If you look at the compare-lectures.quantecon.org/jl/amss.html plots at the bottom, you'll see that (a) the legends are in the way of the actual data, (b) that both legends for the 2nd plot say "Complete Market," and that (c) the colors (blue/black) are reversed compared to the original in lectures.quantecon.org/jl/amss.html
Could you work on fixing this?

When you're done with this and think it looks better, feel free to push it directly to master since we want it in before tonight's rebuild.


Update deploy_app.sh

I changed our marketing slogan. Y'all like it?

Yeah that's pretty raw brother


SDK is forcing orientation to portrait mode - missing support for landscape

On larger devices the app forces view to portrait mode. This makes it difficult to use on tables, which are fix mounted in landscape.

You can change screen orientation settings in your manifest file. Just override library manifest in your project. Add this code to app manifest file and will be ok:
You must do this for all sumUp activity.

`

true
`

`

true
`

`

true

`

just set
   <bool name="isTablet">true</bool>

just set  <bool name="isTablet">true</bool>

Hi, could you please elaborate ? Where should I set this attribute ?

make file in res/values with name bools.xml and put in there


forbidExtraProps seems to have no effect

All the other prop types checks we use both from airbnb and elsewhere seem to work as expected, but forbidExtraProps has no effect no matter where we try it or what we pass it.
We're using<EMAIL_ADDRESS>with<EMAIL_ADDRESS>Any thoughts? Is it broken? Surely we can't be the only ones?
We do not use Use of airbnb-js-shims, but after reviewing the shims, all functions are already supported in our environment without shimming.

See my comment in https://github.com/airbnb/prop-types-exact/issues/13; it should continue to work fine afaik, but we only test up to react 16 right now until enzyme supports react 17+.

It does work! User error, as is often the case. Apologies, and thanks for your time @ljharb.


Force "localhost" as a default registry

Extend util.ResolveName() to prepend "localhost" to the list of registries, and teach util.FindImage(), util.ExpandNames(), and util.AddImageNames() to use util.ResolveName().

@mtrmac @runcom We have decided to use localhost/ to represent locally created images. We know this potentially conflicts with users setting up a registry at localhost, But the user has an easy work around if this causes an issue.  IE I can not tell the difference between locally created images and images I pulled from localhost, by setting up the registry with a different name like localhost.com or something and adding an entry to the /etc/hosts file.
This is much better then what we have now in that we can't tell the difference between images created at locally and those pulled from docker.io.  It also eliminates the need for a breaking change to containers/image.
@baude @mheon These changes will also need to be made to podman once we have it working in buildah.
Note: Nalin has also found lots of issues where we were not looking through the registries for certain image interactions.

BTW I believe this is the last patch we need to get in so we can declare Buildah 1.0  :1st_place_medal:

@giuseppe @umohnani8 @TomSweeneyRedHat @mtrmac @baude @runcom PTAL

Note that when we're given an image name that doesn't include a registry component, we'll attempt to pull from a registry running on localhost first, before consulting registries listed in the configuration.  If the configuration doesn't exist, then, we'll just fail to pull an image.

We'll need to document the registry on the localhost if it doesn't work like the multituedd of Docker examples.  There are a number of examples for running a Docker registry on the web, will Buildah no longer talk to those registries without adjustments?  @ipbabble also  wrote a blog on how to set up a local and we'll need to make sure that holds or add an addendum to that blog.

Travis isn't happy @nalind

There are several fixes in this patch suite to make sure that buildah uses the registries.conf properly.  So yes this change will not effect what is going on now, unless you don't have a properly populated registries.conf.  But I have a feeling our previous code was pulling from docker.io even if docker.io was not listed in the registry.conf.  Which would be a big bug.

@TomSweeneyRedHat This should work just fine with a localhost registry.  The only change would be if I do
ctr=buildah from scratch
buildah commit $ctr foobar

I will end up with localhost/foobar as my image name.
If I had the same named package in a localhost registry and did a
buildah from foobar

Then the original localhost/foobar would be replaced by the one pulled down.
This should not effect pushing, since you need to specify a path to push to.

LGTM

@rh-atomic-bot r+
I agree I think we need to sprinkle information in all of the functions that do pull or push.

This really confused me a lot as I didn't understand why my container build scripts weren't picking up changes, turned out of course they were running the docker.io/ version - looks like this change landed in the Silverblue release stream recently.
Eh, yeah I guess it's better than doing docker.io anyways.

Sorry about that, tough to change the existing databases.


[Global] Docker Images

[x] Provide documentation for how to run the database.
[x] Update image for the runner to expose ports.
[ ] Remove bootstrap.

Change of plans: move PostgreSQL out of the current image and provide instructions on how to "bundle" it (i.e. join the two containers through a network).

Docker infrastructure present and working as of 43636dffe1c7143ed21862afe309bf34c15736cd.

Finished as of d9510c183cd37f98243775757baadb774fc0a1ac.


client_0 (maybe others) mistype

Private Sub Auto_Open()
Call sync_with_serv
End Sub
Should be
Private Sub Auto_Open()
Call sync_with_server
End Sub

Oh whoops, you're right. Fixing...

Should be fixed now.
Cheers


Initial implementation of FlipFlop in Ruby

Aside from a class to hold the internal game state and some convenience methods to deal with shuffling the 1-based offset math from the original game with the 0-based indexing of ruby arrays, this is a fairly faithful (and thus not particularly idiomatic) translation of the original.

Thank you! 🙌


Failure to Connect

Preflight Checklist

[x] I have installed the latest version of Storage Explorer.
[x] I have checked existing resources, including the troubleshooting guide and the release notes.
[x] I have searched for similar issues.

Storage Explorer Version
1.35.0
Regression From
1.35.0
Architecture
i86
Storage Explorer Build Number
20240810.1
Platform
All
OS Version
Edition	Windows 11 Pro Version	23H2 Installed on	2/24/2023 OS build	22631.4317 Experience	Windows Feature Experience Pack 1000.22700.1041.0
Bug Description
Unable to retrieve child resources
ProducerError:{
"name": "Electron Net Error",
"message": "net::ERR_CONNECTION_REFUSED",
"stack": "Error: net::ERR_CONNECTION_REFUSED\n    at SimpleURLLoaderWrapper. (node:electron/js2c/browser_init:2:114352)\n    at SimpleURLLoaderWrapper.emit (node:events:519:28)",
"cause": {}
}
Steps to Reproduce
Attempt to attach to existing Azure Storage Account
Actual Experience
Unable to access Storage Account with Azure Storage Explorer
Expected Experience
No response
Additional Context
No response

@johnh1974 Can you provide more details about your steps?

How are you trying to attach to the account (sign in, key, SAS)? If sign in or SAS, can you verify you have the needed permissions to connect?
Are you working behind a proxy at all? What are your proxy settings set to? Do you require any custom certificates?
Are there other storage accounts you are able to connect to?
Version 1.35.0 does not support i86 machines (see 1.29.0 release notes). Can you verify that your machine is indeed i86 or x64? Is this what appear in the About dialog? If so, I would suggest you install the latest version of Storage Explorer for Windows x64/ARM64 (depending on your architecture) and try again.


Update real-time-marketing-analytics.md

added Email insights

@alfergus please merge this once Dec release reaches NAM


Can react-slick support mobile device?

I test it in chrome emulator, it does not work.(can not swipe)

I tested it on my iPhone 6+ and it worked fine (with the exception of the fade demo at the bottom, that works slightly wonky).

yes


Allow for js eval

Test plan

Changelog

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#5229  👈
#5024 : 1 other dependent PR (#5025 )
#4999
#5003
#4992
#4993
#5120
#5228
main

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

Join @RXminuS and the rest of your teammates on  Graphite


[deck] key-bindings for getting in and out of solo mode

We should have key-bindings and cmd-k nodes to toggle between solo and deck layout.

Duplicate of #6777


Add git ignore items to filter some modules' log files from source code

should filter log files from modules :
${EDGEX_GO_HOME}/cmd/export-client/logs/xxx.log
${EDGEX_GO_HOME}/cmd/export-distro/logs/xxx.log

I want claim it.

closing this issue, thanks @tsconn23


Create Cybersecurity-Dataset.csv

Collection of all sites to extract datasets for cybersecurity

This will be a good resource @Abhitika