golang.org/x/tools/go/packages: cannot import bufio in Go 1.18

What version of Go are you using (go version)?

$ go version
go version go1.18beta1 linux/amd64

Does this issue reproduce with the latest release?
Yes (v1.18beta1)
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/bobg/.cache/go-build"
GOENV="/home/bobg/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/bobg/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/bobg/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/bobg/sdk/go1.18beta1"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/bobg/sdk/go1.18beta1/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.18beta1"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/bobg/go/src/github.com/bobg/modver/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2427960209=/tmp/go-build -gno-record-gcc-switches"

What did you do?
I was beginning to update github.com/bobg/modver for Go 1.18.
I was on my go1.18 branch at commit https://github.com/bobg/modver/commit/561c808eebbd436d00bb9306490e6e5d7235b8fa
I ran go1.18beta1 test -run TestMajor/major/hashsplit .
What did you expect to see?
I expected the test to pass, as it does under Go 1.17.
What did you see instead?
internal error: package "bufio" without types was imported from "hashsplit"

Note, this happens at https://github.com/bobg/modver/blob/561c808eebbd436d00bb9306490e6e5d7235b8fa/compare.go#L188, during the call to packages.Load, which fatals out rather than returning an error.

did you try updating x/tools?

I have now. That fixed it - thanks (he said, embarrassed).


Fix test/Concurrency/objc_async_protocol_irgen.swift for 32-bit

This test was introduced without 32-bit testing.

@swift-ci smoke test

@swift-ci test

@swift-ci test

The test was introduced here and only smoke tested https://github.com/apple/swift/pull/36822

Good

On Apr 9, 2021, at 3:27 PM, Andrew Trick @.***> wrote:
The test was introduced here and only smoke tested #36822 https://github.com/apple/swift/pull/36822
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/apple/swift/pull/36840#issuecomment-816475275, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACQN6LKICRNJJ4FCV2LG53LTH2T47ANCNFSM42UNFBXA.

@swift-ci test macOS

Build failed
Swift Test Linux Platform
Git Sha - 45f74a18192def49ebd4bcd2559418e5c99a3757

The 162 lldb failures are unrelated to this PR.


Add false positive files from the past week

This PR contains most, if not all, of the false positive files from the past week. Some are large and share their match strings with other binaries, so I can remove those if necessary (all of the Vitess files, essentially).

The Vitess files are:

demo
docgen
mysqlctl
mysqlctld
rulesctl
topo2topo
vtaclcheck
vtadmin
vtbackup
vtbench
vtcombo

If you keep the non-obvious vitesse files, please put them in a "vitesse" folder so we know where they are from.

Is it really useful to have so many vitesse files? Are they triggering different alerts?

Double-checked and nope, they all triggered the same critical rule. I'll leave two samples which are relatively small.


bumpversion re-orderers setup.cfg

Assumptions/Environment

bumpversion config is stored in setup.cfg
verified issue on RHEL, Centos + Python 2.7.11, 3.4
relevant config from setup.cfg here

When bumpversion is executed it re-orders the entirety of setup.cfg.  IMHO order is important.

Related issue: https://github.com/peritus/bumpversion/issues/75

It also adds whitespace to the end of some lines, and strip comments. This is fairly nasty behaviour.


Session description is set to empty string by default

Describe the issue
NWBFile.session_description is a required dataset in the NWB schema. Going through the tutorial, this field is not set by default. During conversion, the session_description is set to "" (empty string). The NWB inspector does not complain about the session description not being provided. This results in Neurosift showing "Loading..." when reading a file converted by NWB GUIDE: https://github.com/flatironinstitute/neurosift/issues/178

Should the inspector recommend against setting the value to the empty string? I think yes. Just like the other "description" fields.
Should this field be recommended to provide in GUIDE (colored yellow in the form)? I think yes.
Should this field be required to provide in GUIDE (colored red in the form)? I'm not sure. I lean toward yes because it is required in the schema, and empty string is not informative. Alternatively, we decide that this field should not be required in the NWB schema.

How does NeuroConv set session_description?
@CodyCBakerPhD @bendichter
Steps to Reproduce
Convert a file using GUIDE, look at value of session_description
Operating System
Mac OS with Mac M1
GUIDE Version
1.0.1
Code of Conduct
Yes
Did you confirm this issue was not already reported?
Yes

Yes I would agree having an empty string is not good behavior. If I recall correctly, it might be difficult to make this optional in PyNWB without breaking backwards compatibility for ordered args to the NWBFile init. We switched everything to kwargs long ago and I'd be ok with breaking that at this point but that's the catch in making this optional.
For the GUIDE, I'd say let's make it required, matching the schema. Then let's consider making it optional in the schema separately.

How does NeuroConv set session_description?

NeuroConv is the source of the current behavior, which makes it optional at a high level but because it's required to create a file, sets it to a default of an empty string (preferable to "no description" as happens automatically in a bunch of other places in NWB)
If the goal is to eventually make it optional to create a file, then it would be more work to make it temporarily required in GUIDE only to eventually undo that
Right now the momentum is still tilted in the direction of treating it as optional, so why not just take the next step and relax it at the schema level?


Add a list of recently used gists

While the process of uploading data through gists is quite smooth, it can be a pain to need to re-enter gist id again and again. This might come up if you are switching between gists frequently or accidentally close the page. To address this, I propose maintaining a list of recently used gists in localstorage and populating either a dropdown or straight list just below the "load dataset stored in gist" section of the data selection tab.
Thanks for making such a great project, it's very fun.

Hi
Having a personal history of recently used gist-ids is a great idea. thx
If you just want to open/share a specific gist you could use a link like https://dbis-uibk.github.io/relax/?data=gist:2cfb981fbc5676182d64.
But it's planned to make this process smother in the future.
More information about the links could be found at https://dbis-uibk.github.io/relax/help.htm#tutorial-maintainer-share-dataset


EF7 core not supported MYSQL DB

Please provide solution for this.

@sachinverma2 there are no plans by our team (the EF Core team) to create a MySQL provider. However, if community-members or MySQL themselves create one, we happily add a link in our documentation to this provider.
Closing as there isn't any action to take on the docs repo until MySQL becomes available.

Just also adding that we have been actively working with several provider writers to help them support EF Core. Some of those efforts are open source and public, others are not.


Feature: can.fixture should accept filter function as a first argument

For some tricky cases it would be great to allow filter function as a first argument for can.fixture(). It will give user more control on fixtures.

This functionality is supported in https://github.com/canjs/can-connect, so we can move the discussion there.


PIV Results page feedback

Testing feedback suggestions:
[x] - Distinct background colors for result sections
[x] - Hide toggles/widgets for sections that aren't currently displayed
[ ] - Add lightbulbs (with links to respective curricular modules) to result sections
[x] - Make sure the 'save image' popup is accurate and current regarding the saved images location on phone.

#125 adds collapsible sections and color-coded sections to the results page

Waiting on light bulb content, closing this and adding that to the excel sheet of desired features. Will open a new issue when content is prepared


[#708] test: do not assume hostname of hdfs mini-cluster

What changes were proposed in this pull request?
Do not assume hostname in hdfs URL.
Also, let exception be thrown in ShuffleHdfsStorageUtilsTest to print verbose message.
Why are the changes needed?
Fix #708
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Tested manually

Codecov Report

Merging #709 (0fae8f6) into master (4068593) will increase coverage by 2.16%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #709      +/-   ##
============================================
+ Coverage     60.52%   62.69%   +2.16%
  Complexity     1847     1847
============================================
  Files           228      214      -14
  Lines         12744    10780    -1964
  Branches       1067     1067
============================================
- Hits           7713     6758     -955
+ Misses         4623     3674     -949
+ Partials        408      348      -60

see 14 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Stoped developement?

Is this repo out of dev? or you will keep updating?

This post was on in yr 2014. It's now 2016, so I guess this project is dead unfortunately

But it still works!

Might have security issues

Only phpFreeChat version 1 is listed here:
https://www.cvedetails.com/vendor/8401/Phpfreechat.html
Are there any known security issues with version 2?

This post was on in yr 2014. It's now 2016 (almost 2017 in 2months' time), so I guess this project is dead unfortunately

No brother, its 2023 ;)


Description refers to Convert-NAVServerUser

Description section was copied from Convert-NAVServerUser and does not describe this function.
Examples 3 & 4 do not match the functionality. Switches -ProfileID and -ExportPath do not exist in current version

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

ID: 0358e7c6-3bb8-0f2b-d9f9-2273223f5b37
Version Independent ID: e1ab5649-84a4-49d8-e981-3eecb84bb777
Content: Convert-NAVCustomization (Microsoft.Dynamics.Nav.Management)
Content Source: businesscentral-ps/Microsoft.Dynamics.Nav.Management/Convert-NAVCustomization.md

Thanks for the feedback! The issues have been fixed, and an update will be published soon.


hop-node: TransferRootsDb: Add sub db to track transfer root items by bondedAt timestamp. #341

Adds sub db to index by bondedAt timestamp

LGTM 👍


Problems after applying animation to Fab

Hi
I am applying an animation to the Fab to hide/show it when a list is scrolled. I apply the animation as so:
fab.startAnimation(anim)
The Fab animates correctly however when you tap the Fab after it has been animated the Fab does not transition into the material sheet correctly. Instead the Fab button grows in size and is drawn above the material sheet. Tapping it several more times makes it grow even larger until the app crashes with this exception:
OpenGLRenderer: Error: Ambient Vertex Buffer overflow!!! used 480, total 320
Is there a way to reinitialise the Fab after an animation has been applied to it?
Thanks in advance.

Can you include the animation code?
You won't need to reset the FAB if you're animating its translationX and translationY values.
Take a look at the sample code for how to animate scaling and translating the FAB. https://github.com/gowong/material-sheet-fab/blob/master/sample/src/main/java/com/gordonwong/materialsheetfab/sample/Fab.java#L98

The animation was a simple translate animation like this:
<translate         android:duration="300"         android:fromYDelta="0"         android:toYDelta="100%p" />
I have since implemented the sample code you linked to and it works great.
Thanks for an excellent library and great support.

Oops I spoke to soon! After implementing the sample code and calling animatedFab.show() and animatedFab.hide() a few times I have a similar issue.
The Fab will sometimes appear twice the size after calling show and tapping it will cause an incorrect animation into the sheet. Tapping it again causes this exception: OpenGLRenderer: Error: Ambient Vertex Buffer overflow!!! used 480, total 320
I am using the exact same code listed here: https://github.com/gowong/material-sheet-fab/blob/master/sample/src/main/java/com/gordonwong/materialsheetfab/sample/Fab.java#L98
I'm using a Nexus 6 running Android 6.0.1. Have you experienced this before?
Thanks

I have found the problem.
If you fling the ListView and quickly tap the Fab whilst the list is still scrolling this is when the error occurs. The Fab grows twice the size and is drawn above the sheet. Then when you attempt to hide the sheet you get the 'Ambient Vertex Buffer overflow!!!' exception.
Any ideas what causes this?

A solution I've found is to wrap the call to fab.show() with a condition that checks that it cannot be called more than once whilst the show animation is playing. That seems to have fixed it!

Glad you got it working!
Yes, I imagine issues similar to what you described will happen when multiple animations are repeatedly playing on the FAB. It's up to the app to implement logic to enforce only one playing animation since there's no way for the library to know about outside animations on the FAB.


Tweetinvi Authentication

Trying to follow the code examples, I am having an issue with Auth.SetUserCredentials in .NET.
The error is: The type or namespace 'SetUserCredentials' could not be found.......
Tweet.publishtweet resolves fine.
What am I missing?
// Set up your credentials (https://apps.twitter.com)
Auth.SetUserCredentials("CONSUMER_KEY", "CONSUMER_SECRET", "ACCESS_TOKEN", "ACCESS_TOKEN_SECRET");
// Publish the Tweet "Hello World" on your Timeline
Tweet.PublishTweet("Hello World!");

It looks like a namespace issue. Have your tried Tweetinvi.Auth.SetUserCredentials?

Just tried, that gave me the same results.
The error is: The type or namespace 'SetUserCredentials' could not be found.......

Please provide the entire file on gist.
Also let me know which version of Tweetinvi you are using!

I am currently running TweetinviAPI v<IP_ADDRESS>
Auth.ApplicationCredentials =  new Tweetinvi.Auth.SetUserCredentials("CONSUMER_KEY", "CONSUMER_SECRET", "ACCESS_TOKEN", "ACCESS_TOKEN_SECRET");
I found that the new keyword caused the issue. Sorry to bother you.


It doesn't complete synchronization and prompt 'We can't replicate more lower value'

Hi master. I built up my own sync server by using self-hosted livesync latest version in my home server(Redhat RHEL9). And I am using Obsidian in my Macbook. I clicked the 'Replicate' button, after a few seconds it runs and alway prompt 'We can't replicate more lower value.' at the end of the synchronization. And then there is a sync failure logo.
Usually the error message is as follows：
Retry with lower batch size:6/6
TypeError:Failed to fetch ......
We can't replicate more lower value.
I tested it and rebuild all repeatedly, and it  doesn't work. My vault is not big, with less than 100 ordinary records. The entire vault is only 21mb.
May I ask if there is any problem with my configuration? It doesn't look like there's any MD notes particularly large or a file that's stuck in the sync process. I tested two similar vaults with the same results. Would you please give me some advice? Thanks
Abstract
The synchronization failed and showed 'We can't replicate more lower value' after connecting.
Expected behaviour

Synchronization ends with the message Replication completed
Everything synchronised

Actually happened

Synchronization has been cancelled with the message :  'Retry with lower batch size:6/5'  ...and We can't replicate more lower value
No files synchronised

Reproducing procedure

Configure LiveSync as in the attached material.
Click the replication button on the ribbon.
Synchronising has begun.
About two or three seconds later, we got the error 'Retry with lower batch size:6/5'  and We can't replicate more lower value.
Replication has been stopped. No files synchronised.

Report materials
If the information is not available, do not hesitate to report it as it is. You can also of course omit it if you think this is indeed unnecessary. If it is necessary, I will ask you.
Report from the LiveSync
For more information, please refer to Making the report.

Report from hatch
----remote config----
cors:
  credentials: "true"
  headers: accept, authorization, content-type, origin, referer
  max_age: "3600"
  methods: GET,PUT,POST,HEAD,DELETE
  origins: app://obsidian.md,capacitor://localhost,http://localhost
chttpd:
  bind_address: any
  enable_cors: "true"
  max_http_request_size: "4294967296"
  port: "5984"
  require_valid_user: "true"
admins: 𝑅𝐸𝐷𝐴𝐶𝑇𝐸𝐷
vendor:
  name: The Apache Software Foundation
feature_flags:
  partitioned||*: "true"
chttpd_auth:
  authentication_redirect: /_utils/session.html
  hash_algorithms: sha256, sha
  require_valid_user: "true"
indexers:
  couch_mrview: "true"
prometheus:
  additional_port: "false"
  bind_address: <IP_ADDRESS>
  port: "17986"
httpd:
  WWW-Authenticate: Basic realm="couchdb"
  bind_address: <IP_ADDRESS>
  enable_cors: "true"
  port: "5986"
smoosh:
  state_dir: ./data
couch_httpd_auth:
  authentication_db: 𝑅𝐸𝐷𝐴𝐶𝑇𝐸𝐷
  secret: 𝑅𝐸𝐷𝐴𝐶𝑇𝐸𝐷
  authentication_redirect: 𝑅𝐸𝐷𝐴𝐶𝑇𝐸𝐷
couchdb_engines:
  couch: couch_bt_engine
couchdb:
  database_dir: ./data
  max_document_size: "50000000"
  single_node: "true"
  uuid: 𝑅𝐸𝐷𝐴𝐶𝑇𝐸𝐷
  view_index_dir: ./data
---- Plug-in config ---
version:0.21.3
couchDB_URI: self-hosted
couchDB_USER: 𝑅𝐸𝐷𝐴𝐶𝑇𝐸𝐷
couchDB_PASSWORD: 𝑅𝐸𝐷𝐴𝐶𝑇𝐸𝐷
couchDB_DBNAME: 𝑅𝐸𝐷𝐴𝐶𝑇𝐸𝐷
liveSync: false
syncOnSave: true
syncOnStart: false
savingDelay: 200
lessInformationInLog: false
gcDelay: 0
versionUpFlash: ""
minimumChunkSize: 20
longLineThreshold: 250
showVerboseLog: true
suspendFileWatching: false
trashInsteadDelete: true
periodicReplication: false
periodicReplicationInterval: 180
syncOnFileOpen: false
encrypt: true
passphrase: 𝑅𝐸𝐷𝐴𝐶𝑇𝐸𝐷
usePathObfuscation: false
doNotDeleteFolder: true
resolveConflictsByNewerFile: false
batchSave: true
deviceAndVaultName: ""
usePluginSettings: false
showOwnPlugins: false
showStatusOnEditor: true
usePluginSync: false
autoSweepPlugins: false
autoSweepPluginsPeriodic: false
notifyPluginOrSettingUpdated: true
checkIntegrityOnSave: false
batch_size: 50
batches_limit: 10
useHistory: true
disableRequestURI: true
skipOlderFilesOnSync: true
checkConflictOnlyOnOpen: false
syncInternalFiles: false
syncInternalFilesBeforeReplication: false
syncInternalFilesIgnorePatterns: /node_modules/, /.git/, /obsidian-livesync/
syncInternalFilesInterval: 120
additionalSuffixOfDatabaseName: general
ignoreVersionCheck: false
lastReadUpdates: 21
deleteMetadataOfDeletedFiles: false
syncIgnoreRegEx: ""
syncOnlyRegEx: ""
customChunkSize: 100
readChunksOnline: true
watchInternalFileChanges: true
automaticallyDeleteMetadataOfDeletedFiles: 0
disableMarkdownAutoMerge: true
writeDocumentsIfConflicted: false
useDynamicIterationCount: false
syncAfterMerge: false
configPassphraseStore: ""
encryptedPassphrase: 𝑅𝐸𝐷𝐴𝐶𝑇𝐸𝐷
encryptedCouchDBConnection: 𝑅𝐸𝐷𝐴𝐶𝑇𝐸𝐷
permitEmptyPassphrase: false
useIndexedDBAdapter: true
useTimeouts: false
writeLogToTheFile: false
doNotPaceReplication: false
hashCacheMaxCount: 200
hashCacheMaxAmount: 50
concurrencyOfReadChunksOnline: 50
minimumIntervalOfReadChunksOnline: 333
hashAlg: xxhash64
suspendParseReplicationResult: false
doNotSuspendOnFetching: false
useIgnoreFiles: false
ignoreFiles: .gitignore
syncOnEditorSave: true
pluginSyncExtendedSetting: {}
useV1: false
<!-- paste here -->

Obsidian debug info

Debug info
2023/12/7 23:09:51->OneShot Sync begin... (sync)
2023/12/7 23:09:51->Looking for the point last synchronized point.
2023/12/7 23:09:51->Replication paused
2023/12/7 23:09:52->Replication activated
2023/12/7 23:09:53->HTTP:POST (4587675) to:/_bulk_docs -> failed
2023/12/7 23:09:53->TypeError:Failed to fetch
2023/12/7 23:09:53->Replication error
2023/12/7 23:09:53->Error:Failed to fetch
2023/12/7 23:09:53->Replication stopped.
2023/12/7 23:09:53->Retry with lower batch size:27/7
2023/12/7 23:09:53->OneShot Sync begin... (sync)
2023/12/7 23:09:53->Looking for the point last synchronized point.
2023/12/7 23:09:53->Replication activated
2023/12/7 23:09:53->HTTP:POST (3690582) to:/_bulk_docs -> failed
2023/12/7 23:09:53->TypeError:Failed to fetch
2023/12/7 23:09:53->Replication error
2023/12/7 23:09:53->Error:Failed to fetch
2023/12/7 23:09:53->Replication stopped.
2023/12/7 23:09:53->Retry with lower batch size:16/6
2023/12/7 23:09:53->OneShot Sync begin... (sync)
2023/12/7 23:09:53->Looking for the point last synchronized point.
2023/12/7 23:09:53->Replication paused
2023/12/7 23:09:53->Replication activated
2023/12/7 23:09:54->HTTP:POST (1890485) to:/_bulk_docs -> failed
2023/12/7 23:09:54->TypeError:Failed to fetch
2023/12/7 23:09:54->Replication error
2023/12/7 23:09:54->Error:Failed to fetch
2023/12/7 23:09:54->Replication stopped.
2023/12/7 23:09:54->Retry with lower batch size:10/5
2023/12/7 23:09:54->OneShot Sync begin... (sync)
2023/12/7 23:09:54->Looking for the point last synchronized point.
2023/12/7 23:09:54->Replication activated
2023/12/7 23:09:54->HTTP:POST (916374) to:/_bulk_docs -> failed
2023/12/7 23:09:54->TypeError:Failed to fetch
2023/12/7 23:09:54->Replication error
2023/12/7 23:09:54->Error:Failed to fetch
2023/12/7 23:09:54->Replication stopped.
2023/12/7 23:09:54->Retry with lower batch size:7/5
2023/12/7 23:09:54->OneShot Sync begin... (sync)
2023/12/7 23:09:54->Looking for the point last synchronized point.
2023/12/7 23:09:54->Replication paused
2023/12/7 23:09:54->Replication activated
2023/12/7 23:09:54->HTTP:POST (545715) to:/_bulk_docs -> failed
2023/12/7 23:09:54->TypeError:Failed to fetch
2023/12/7 23:09:54->Replication error
2023/12/7 23:09:54->Error:Failed to fetch
2023/12/7 23:09:54->Replication stopped.
2023/12/7 23:09:54->Retry with lower batch size:6/5
2023/12/7 23:09:54->OneShot Sync begin... (sync)
2023/12/7 23:09:54->Looking for the point last synchronized point.
2023/12/7 23:09:54->Replication paused
2023/12/7 23:09:54->Replication activated
2023/12/7 23:09:54->HTTP:POST (365951) to:/_bulk_docs -> failed
2023/12/7 23:09:54->TypeError:Failed to fetch
2023/12/7 23:09:54->Replication error
2023/12/7 23:09:54->Error:Failed to fetch
2023/12/7 23:09:54->Replication stopped.
2023/12/7 23:09:54->We can't replicate more lower value.
```

```

Plug-in log
We can see the log by tapping the Document box icon. If you noticed something suspicious, please let me know.
Note: Please enable Verbose Log. For detail, refer to Logging, please.

Plug-in log
```
general-general:2023/12/7 23:14:24->Cache initialized 200 / 50000000
general-general:2023/12/7 23:14:34->OneShot Sync begin... (sync)
general-general:2023/12/7 23:14:34->Looking for the point last synchronized point.
general-general:2023/12/7 23:14:34->Replication paused
general-general:2023/12/7 23:14:34->Replication activated
general-general:2023/12/7 23:14:35->HTTP:POST (4587675) to:/_bulk_docs -> failed
general-general:2023/12/7 23:14:35->TypeError:Failed to fetch
general-general:2023/12/7 23:14:35->Replication error
general-general:2023/12/7 23:14:35->Error:Failed to fetch
general-general:2023/12/7 23:14:35->Replication stopped.
general-general:2023/12/7 23:14:35->Retry with lower batch size:27/7
general-general:2023/12/7 23:14:35->OneShot Sync begin... (sync)
general-general:2023/12/7 23:14:35->Looking for the point last synchronized point.
general-general:2023/12/7 23:14:35->Replication paused
general-general:2023/12/7 23:14:35->Replication activated
general-general:2023/12/7 23:14:36->HTTP:POST (3690582) to:/_bulk_docs -> failed
general-general:2023/12/7 23:14:36->TypeError:Failed to fetch
general-general:2023/12/7 23:14:36->Replication error
general-general:2023/12/7 23:14:36->Error:Failed to fetch
general-general:2023/12/7 23:14:36->Replication stopped.
general-general:2023/12/7 23:14:36->Retry with lower batch size:16/6
general-general:2023/12/7 23:14:36->OneShot Sync begin... (sync)
general-general:2023/12/7 23:14:36->Looking for the point last synchronized point.
general-general:2023/12/7 23:14:36->Replication paused
general-general:2023/12/7 23:14:36->Replication activated
general-general:2023/12/7 23:14:37->HTTP:POST (1890485) to:/_bulk_docs -> failed
general-general:2023/12/7 23:14:37->TypeError:Failed to fetch
general-general:2023/12/7 23:14:37->Replication error
general-general:2023/12/7 23:14:37->Error:Failed to fetch
general-general:2023/12/7 23:14:37->Replication stopped.
general-general:2023/12/7 23:14:37->Retry with lower batch size:10/5
general-general:2023/12/7 23:14:37->OneShot Sync begin... (sync)
general-general:2023/12/7 23:14:37->Looking for the point last synchronized point.
general-general:2023/12/7 23:14:37->Replication paused
general-general:2023/12/7 23:14:37->Replication activated
general-general:2023/12/7 23:14:37->HTTP:POST (916374) to:/_bulk_docs -> failed
general-general:2023/12/7 23:14:37->TypeError:Failed to fetch
general-general:2023/12/7 23:14:37->Replication error
general-general:2023/12/7 23:14:37->Error:Failed to fetch
general-general:2023/12/7 23:14:37->Replication stopped.
general-general:2023/12/7 23:14:37->Retry with lower batch size:7/5
general-general:2023/12/7 23:14:37->OneShot Sync begin... (sync)
general-general:2023/12/7 23:14:37->Looking for the point last synchronized point.
general-general:2023/12/7 23:14:37->Replication paused
general-general:2023/12/7 23:14:38->Replication activated
general-general:2023/12/7 23:14:38->HTTP:POST (545715) to:/_bulk_docs -> failed
general-general:2023/12/7 23:14:38->TypeError:Failed to fetch
general-general:2023/12/7 23:14:38->Replication error
general-general:2023/12/7 23:14:38->Error:Failed to fetch
general-general:2023/12/7 23:14:38->Replication stopped.
general-general:2023/12/7 23:14:38->Retry with lower batch size:6/5
general-general:2023/12/7 23:14:38->OneShot Sync begin... (sync)
general-general:2023/12/7 23:14:38->Looking for the point last synchronized point.
general-general:2023/12/7 23:14:38->Replication paused
general-general:2023/12/7 23:14:38->Replication activated
general-general:2023/12/7 23:14:38->HTTP:POST (365951) to:/_bulk_docs -> failed
general-general:2023/12/7 23:14:38->TypeError:Failed to fetch
general-general:2023/12/7 23:14:38->Replication error
general-general:2023/12/7 23:14:38->Error:Failed to fetch
general-general:2023/12/7 23:14:38->Replication stopped.
general-general:2023/12/7 23:14:38->We can't replicate more lower value.
<!-- paste here -->

Network log
Network logs displayed in DevTools will possibly help with connection-related issues. To capture that, please refer to DevTools.
Screenshots
If applicable, please add screenshots to help explain your problem.

Other information, insights and intuition.
Please provide any additional context or information about the problem.

Check Database configuration screenshot.

Already solved. The analysis and solution process is as follows:

View livesync plugin logs, found:
general-general:2023/12/9 17:17:29->OneShot Sync begin... (sync)
general-general:2023/12/9 17:17:29->Looking for the point last synchronized point.
general-general:2023/12/9 17:17:29->Replication paused
general-general:2023/12/9 17:17:29->Replication activated
general-general:2023/12/9 17:17:29->HTTP:POST (539834) to:/_bulk_docs -> failed
general-general:2023/12/9 17:17:29->TypeError:Failed to fetch
general-general:2023/12/9 17:17:29->Replication error
general-general:2023/12/9 17:17:29->Error:Failed to fetch
general-general:2023/12/9 17:17:29->Replication stopped.
general-general:2023/12/9 17:17:29->Retry with lower batch size:6/6
general-general:2023/12/9 17:17:29->OneShot Sync begin... (sync)
general-general:2023/12/9 17:17:29->Looking for the point last synchronized point.
general-general:2023/12/9 17:17:29->Replication paused
general-general:2023/12/9 17:17:29->Replication activated
general-general:2023/12/9 17:17:29->HTTP:POST (361070) to:/_bulk_docs -> failed
general-general:2023/12/9 17:17:29->TypeError:Failed to fetch
general-general:2023/12/9 17:17:29->Replication error
general-general:2023/12/9 17:17:29->Error:Failed to fetch
general-general:2023/12/9 17:17:29->Replication stopped.
general-general:2023/12/9 17:17:29->We can't replicate more lower value.

2.It showed that POST activity failed and the /_bulk_docs command failed to execute.
3.Since I used nginx as https reverse proxy, checked /var/log/nginx/couchdb.error.log , found:
2023/12/09 17:08:35 [error] 1316258#1316258: *5645 client intended to send too large body: 4586211 bytes, client: <IP_ADDRESS>, server: obsidian.xxx.com , request: "POST /obsidian-general/_bulk_docs HTTP/1.1", host: "obsidian.xxx.com:5984"
‘client intended to send too large body’ appears in the nginx error log. It means that the uploaded file size exceeds the server-side limit size. So modified /etc/nginx/nginx.conf:
http {
...
# set the maximum upload to 50MB
client_max_body_size 50M;
...
}
systemctl restart nginx
4.The same error still occurs during livesync synchronization. Check /var/log/couchdb.error.log and the error changes to:
2023/12/09 17:53:41 [crit] 1639708#1639708: *1 open() "/var/lib/nginx/tmp/client_body/0000000001" failed (13: Permission denied), client: <IP_ADDRESS>, server: obsidian.xxx.com, request: "POST /obsidian-general/_bulk_docs HTTP/1.1", host: "obsidian.xxx.com:5984".
5.Check the user attributes and permissions of /var/lib/nginx/tmp/client_body
[root@syncserver tmp]# ll
drwx------. 2 web root 6 10月  6 11:46 client_body
drwx------. 2 web root 6 10月  6 11:46 fastcgi
drwx------. 2 web root 6 10月  6 11:46 proxy
drwx------. 2 web root 6 10月  6 11:46 scgi
drwx------. 2 web root 6 10月  6 11:46 uwsgi
Determine the identity of the current running user of nginx and find that it is web.
[root@syncserver nginx]# ps aux |grep nginx
root     1661857  0.0  0.0  10492  1272 ?        Ss   21:14   0:00 nginx: master process /usr/sbin/nginx
web    1661858  0.0  0.0  13764  5284 ?        S    21:14   0:00 nginx: worker process
web    1661859  0.0  0.0  13764  5284 ?        S    21:14   0:00 nginx: worker process
root     1661870  0.0  0.0 221680  2464 pts/1    S+   21:14   0:00 grep --color=auto nginx
Because the Request is large, Nginx needs to write the cache in /var/lib/nginx/tmp/client_body/, but encounters an inconsistency between the nginx running user and the directory owner, resulting in insufficient Permission denied permissions.
Modify /etc/nginx/nginx.conf
Change 'user web;' to ' user nginx;'
chown -R nginx:nginx  /var/lib/nginx
6.It works after restarting nginx service!


ref methods for function components

Next-gen React is looking great, and class components are now rarely necessary.. but components that offer ref instance methods are still stuck with classes. Here's an example class which I believe is currently impossible to convert to a function component:
class MyInput extends React.Component {
  // how would 'focus' be defined if MyInput was a function?
  focus = () => {
    doSideEffect()
    this.textInput.focus()
  }
  render() {
    return (
      <TextInput
        ref={ti => { this.textInput = ti; }}
        {...this.props}
      />
    );
  }
}

Note: I know refs+methods aren't ideal for most use-cases, but they are a reality that prevents us from leaving behind classes in our codebase.
So, I wrote the above issue and then realized that forwardRef could be used for this:
const MyInput = forwardRef((props, ref) => {
  const innerInput = useRef(null);
  function focus() {
    doSideEffect();
    innerInput.current && innerInput.current.focus();
  }
  ref.current = { focus };
  return <Input {...props} ref={innerInput} />;
});

see runnable example
At first glance, this seems to work. Is this sane? Should this be documented? Optimized? Discouraged?

This is exactly solved by the example at https://reactjs.org/docs/hooks-reference.html#useref - or am I missing something here?
function TextInputWithFocusButton() {
  const inputEl = useRef(null);
  const onButtonClick = () => {
    // `current` points to the mounted text input element
    inputEl.current.focus();
  };
  return (
    <>
      <input ref={inputEl} type="text" />
      <button onClick={onButtonClick}>Focus the input</button>
    </>
  );
}

@ericvicenti Yes, there is an api for that.
https://reactjs.org/docs/hooks-reference.html#useimperativehandle

Ah, can't believe I missed this handy useImperativeHandle hook!


Update attribute editor when clearing crop window

When the attribute editor is showing the attributes of a frame, clearing the crop window with the toolbar button should also clear the crop window in the attribute editor.

Not always. I guess you should have added: "Only when a relevant entity (beauty, render pass, I don't remember the name) is selected".

Updated the description, I think it's pretty accurate now.

I'll take this one to fix, if you don't mind

I've found another related bug, I guess. If the "Crop window" attribute will be updated through "Project" > "Output" > "beauty" > right click > "Edit" dedicated dialog window while "beauty" attribute editor is active it will also take no effect to field into attribute editor.

Hello, @dictoon! I've achieved some results on that task, however I am not quite sure that this solution is the one you've been expecting, since there are a lot of other ways to reach the goal.
For example, we can

directly connect signals in MainWindow
emit signal in ClearRenderRegionAction
connect signal directly to QLineEdit clear() slot on its creation
pass the call down through hierarchy without signals
etc.

All the points are having some pros and cons, so if you'll have some recommendations please let me know and I'll improve the proposed solution. Here is a PR.

Done.


Feature/cubified/wish granting template

Administrative Info
[#25]
Make sure your branch name conforms to: <feature/staging/hotfix/...>/[username]/[3-4 word description separated by dashes]. Otherwise, please rename your branch and create a new PR.
Changes
What changes did you make?

Added templating for the Wish Granting page, including:

Integration with side nav for changing between steps
Functional upload, edit, and delete file/category buttons and modals
Local persistent filesystem using localStorage
More extensible FileEntry.js component, exporting more lower-level components in case they need to be used anywhere else in the project

Testing
How did you confirm your changes worked?

Manual testing and verification against the Figma

Confirmation of Change
Upload a screenshot, if possible. Otherwise, please provide instructions on how to see the change.

[Demo GIF]

This isn't urgent, but I want to look more into seeing if I can merge similar modals into a single one -- I will say each of the five modals are just different enough in look/functionality to make this harder than it seems.


Add note about rendering back in the browser

I was confused by Preact appending to the container, and it took a while to find the answer in https://github.com/developit/preact-render-to-string/issues/11. I propose adding a note about it in the readme.

Note that this behaviour is no more in Preact X. There we share the same behaviour add react and don't have a third argument.

Is Preact X the official name of a future Preact version? In that case it could be elaborated in this PR somehow. Would you suggest phrasing it e.g. "Note about Preact versions 9 and lower: unlike React, Preact does not overwrite pre-rendered DOM unless instructed to. Specify the third argument for render to match behaviour.".

Preact X (=10.0.0) is our next major version that is currently in alpha and should be released soon. It includes a few (mostly internal) breaking changes and we were originally aiming to do a v9 release which would just include some vnode changes. But it looks like that won't happen anymore. The release announcement has more information about Preact X :+1:


V0.1.33 rebase release 3.11

/test service-catalog

closing this PR, skipping this upstream version and will resubmit with newer merge.


Find Region From Bucket

This dynamically determines the AWS region instead of requiring it as an input.
Tested by running locally and ensuring the correct region is selected.

Sweet, if this works, it's WAY cleaner :)

LGTM


Provider produced inconsistent result after apply

Your environment
Terraform Provider Version: 2.0.0
CLI Version: 2.28.0
OS: macOS 14.5
Terraform Version: OpenTofu v1.7.1
What happened?
Was working fine, suddenly getting errors on apply today (even though resources haven't changed). Deleted resources in state and in the vault and attempted to recreate.
What did you expect to happen?
Update went as planned.
 Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement

OpenTofu will perform the following actions:

  # onepassword_item.server["au.masked.net"] is tainted, so it must be replaced
-/+ resource "onepassword_item" "server" {
      ~ id = "masked" -> (known after apply)
      ~ uuid = "masked" -> (known after apply)
        # (5 unchanged attributes hidden)

      ~ section {
          ~ id = "masked" -> (known after apply)

          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
        }
    }

  # onepassword_item.server["gen8.au.masked.net"] is tainted, so it must be replaced
-/+ resource "onepassword_item" "server" {
      ~ id = "masked" -> (known after apply)
      ~ uuid = "masked" -> (known after apply)
        # (5 unchanged attributes hidden)

      ~ section {
          ~ id = "masked" -> (known after apply)

          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
        }
    }

  # onepassword_item.server["masked-truenas.kr.masked.net"] is tainted, so it must be replaced
-/+ resource "onepassword_item" "server" {
      ~ id = "masked" -> (known after apply)
      ~ uuid = "masked" -> (known after apply)
        # (5 unchanged attributes hidden)

      ~ section {
          ~ id = "masked" -> (known after apply)

          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
        }
    }

  # onepassword_item.server["masked-ubuntu.kr.masked.net"] is tainted, so it must be replaced
-/+ resource "onepassword_item" "server" {
      ~ id = "masked" -> (known after apply)
      ~ uuid = "masked" -> (known after apply)
        # (5 unchanged attributes hidden)

      ~ section {
          ~ id = "masked" -> (known after apply)

          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
        }
    }

  # onepassword_item.server["masked.kr.masked.net"] is tainted, so it must be replaced
-/+ resource "onepassword_item" "server" {
      ~ id = "masked" -> (known after apply)
      ~ uuid = "masked" -> (known after apply)
        # (5 unchanged attributes hidden)

      ~ section {
          ~ id = "masked" -> (known after apply)

          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
        }
    }

  # onepassword_item.server["kr.masked.net"] is tainted, so it must be replaced
-/+ resource "onepassword_item" "server" {
      ~ id = "masked" -> (known after apply)
      ~ uuid = "masked" -> (known after apply)
        # (5 unchanged attributes hidden)

      ~ section {
          ~ id = "masked" -> (known after apply)

          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
        }
    }

  # onepassword_item.server["mini-ubuntu.au.masked.net"] is tainted, so it must be replaced
-/+ resource "onepassword_item" "server" {
      ~ id = "masked" -> (known after apply)
      ~ uuid = "masked" -> (known after apply)
        # (5 unchanged attributes hidden)

      ~ section {
          ~ id = "masked" -> (known after apply)

          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
        }
    }

  # onepassword_item.server["mini.au.masked.net"] is tainted, so it must be replaced
-/+ resource "onepassword_item" "server" {
      ~ id = "masked" -> (known after apply)
      ~ uuid = "masked" -> (known after apply)
        # (5 unchanged attributes hidden)

      ~ section {
          ~ id = "masked" -> (known after apply)

          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
        }
    }

  # onepassword_item.server["oracle.au.masked.net"] is tainted, so it must be replaced
-/+ resource "onepassword_item" "server" {
      ~ id = "masked" -> (known after apply)
      ~ uuid = "masked" -> (known after apply)
        # (5 unchanged attributes hidden)

      ~ section {
          ~ id = "masked" -> (known after apply)

          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
          ~ field {
              ~ id = "masked" -> (known after apply)
                # (3 unchanged attributes hidden)
            }
        }
    }

Plan: 9 to add, 0 to change, 9 to destroy.

Do you want to perform these actions?
  OpenTofu will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

onepassword_item.server["kr.masked.net"]: Destroying... [id=masked]
onepassword_item.server["kr.masked.net"]: Destruction complete after 2s
onepassword_item.server["masked.kr.masked.net"]: Destroying... [id=masked]
onepassword_item.server["masked.kr.masked.net"]: Destruction complete after 2s
onepassword_item.server["au.masked.net"]: Destroying... [id=masked]
onepassword_item.server["au.masked.net"]: Destruction complete after 2s
onepassword_item.server["mini-ubuntu.au.masked.net"]: Destroying... [id=masked]
onepassword_item.server["mini-ubuntu.au.masked.net"]: Destruction complete after 2s
onepassword_item.server["oracle.au.masked.net"]: Destroying... [id=masked]
onepassword_item.server["oracle.au.masked.net"]: Destruction complete after 2s
onepassword_item.server["masked-truenas.kr.masked.net"]: Destroying... [id=masked]
onepassword_item.server["masked-truenas.kr.masked.net"]: Destruction complete after 2s
onepassword_item.server["masked-ubuntu.kr.masked.net"]: Destroying... [id=masked]
onepassword_item.server["masked-ubuntu.kr.masked.net"]: Destruction complete after 2s
onepassword_item.server["gen8.au.masked.net"]: Destroying... [id=masked]
onepassword_item.server["gen8.au.masked.net"]: Destruction complete after 2s
onepassword_item.server["mini.au.masked.net"]: Destroying... [id=masked]
onepassword_item.server["mini.au.masked.net"]: Destruction complete after 2s
onepassword_item.server["masked-ubuntu.kr.masked.net"]: Creating...
onepassword_item.server["gen8.au.masked.net"]: Creating...
onepassword_item.server["mini.au.masked.net"]: Creating...
onepassword_item.server["kr.masked.net"]: Creating...
onepassword_item.server["masked.kr.masked.net"]: Creating...
onepassword_item.server["au.masked.net"]: Creating...
onepassword_item.server["masked-truenas.kr.masked.net"]: Creating...
onepassword_item.server["mini-ubuntu.au.masked.net"]: Creating...
onepassword_item.server["oracle.au.masked.net"]: Creating...
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to onepassword_item.server["mini-ubuntu.au.masked.net"], provider "provider[\"registry.opentofu.org/1password/onepassword\"]" produced an unexpected new
│ value: .section[0].label: was cty.StringVal(""), but now null.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to onepassword_item.server["mini.au.masked.net"], provider "provider[\"registry.opentofu.org/1password/onepassword\"]" produced an unexpected new value:
│ .section[0].label: was cty.StringVal(""), but now null.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to onepassword_item.server["oracle.au.masked.net"], provider "provider[\"registry.opentofu.org/1password/onepassword\"]" produced an unexpected new value:
│ .section[0].label: was cty.StringVal(""), but now null.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to onepassword_item.server["gen8.au.masked.net"], provider "provider[\"registry.opentofu.org/1password/onepassword\"]" produced an unexpected new value:
│ .section[0].label: was cty.StringVal(""), but now null.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to onepassword_item.server["au.masked.net"], provider "provider[\"registry.opentofu.org/1password/onepassword\"]" produced an unexpected new value:
│ .section[0].label: was cty.StringVal(""), but now null.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to onepassword_item.server["masked.kr.masked.net"], provider "provider[\"registry.opentofu.org/1password/onepassword\"]" produced an unexpected new value:
│ .section[0].label: was cty.StringVal(""), but now null.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to onepassword_item.server["masked-ubuntu.kr.masked.net"], provider "provider[\"registry.opentofu.org/1password/onepassword\"]" produced an unexpected new
│ value: .section[0].label: was cty.StringVal(""), but now null.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to onepassword_item.server["kr.masked.net"], provider "provider[\"registry.opentofu.org/1password/onepassword\"]" produced an unexpected new value:
│ .section[0].label: was cty.StringVal(""), but now null.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to onepassword_item.server["masked-truenas.kr.masked.net"], provider "provider[\"registry.opentofu.org/1password/onepassword\"]" produced an unexpected new
│ value: .section[0].label: was cty.StringVal(""), but now null.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Seems to be an issue since version 2.0.0 which was released just a few hours ago...

This seems to be because my label for the section was empty, worked before and would like to keep using this behavior.
  section {
    label = ""

    ...
  }

This seems to be because my label for the section was empty, worked before and would like to keep using this behavior.
  section {
    label = ""

    ...
  }

I'm setting a value both for the label within the section and the field but also experiencing the same problem.
Terraform v1.7.5
provider registry.terraform.io/1password/onepassword 2.0.0
OS: Linux

Further experimentation surfaced that the provider is not able to deal with empty values. I'll create a separate ticket for that.

@pro4tlzz can you share a hint how you were using sections incorrectly? I'm also running into this issue, the item gets created just fine with all sections labeled, and I still get the "inconsistent values for sensitive attribute" errors...

Changed from something like
  section {
    label = "REDACTED"

    field {
      label   = "Instructions"
      purpose = "NOTES"
      type    = "STRING"
      value   = <<EOT
REDACTED
EOT
    }
  }
}

to
 title      = "REDACTED"
  category   = "login"
  url        = "REDACTED"
  username   = "REDACTED"
  password   = "REDACTED"
  note_value = <<EOT
REDACTED
EOT

Basically don't use section or field as objects, just set all these properties in the root context of the resource

Just chiming in here that I had this same problem.
Since the types of documents that can be created are so limited, I use "login" and create sections.  To avoid confusion, I used to est the username to "".
Setting the username to something aside from an empty string fixed the issue.
  username = "none"```

In my case I had  both section and field as dynamic objects:
  dynamic "section" {
    for_each = each.value
    content {
      label = "Cluster: ${section.value.name} / ${section.value.provider} / ${section.value.region}"
      field {
        label = "Opsgenie API Integration Key"
        type = "CONCEALED"
        value = try(opsgenie_api_integration.prometheus[section.value.cluster_key].api_key, "-")
      }
      field {
        label = "Cronitor Monitor ID"
        type = "CONCEALED"
        value = try(cronitor_heartbeat_monitor.monitors[section.value.cluster_key].id, "-")
      }
      field {
        label = "Teleport Token"
        type = "CONCEALED"
        value = try(teleport_provision_token.tokens[section.value.cluster_key].metadata.name, "-")
      }
    }
  }

Note the try() for field[].values must have a non-empty value, otherwise it fails with:
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to onepassword_item.keys["customer-name"], provider "provider[\"registry.terraform.io/1password/onepassword\"]" produced an unexpected new value: .section[4].field[1].value: inconsistent values for sensitive
│ attribute.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.


Unable to send any logs to splunk enterprise 8.1.9 using OTEL

Describe the issue you're reporting
We are currently migrating from splunk connect for kubernetes to Splunk OpenTelemetry Collector for Kubernetes using helm and after installing OTEL we don't see any logs in splunk dashboard.  below is the OTEL yaml . can you please let us know wat we are doing wrong
exporters:
  splunk_hec/platform_logs:
    disable_compression: true
    endpoint: <REDACTED>
    idle_conn_timeout: 10s
    index: <REDACTED>
    max_connections: 200
    profiling_data_enabled: false
    retry_on_failure:
      enabled: true
      initial_interval: 5s
      max_elapsed_time: 300s
      max_interval: 30s
    sending_queue:
      enabled: true
      num_consumers: 10
      queue_size: 5000
    source: kubernetes
    splunk_app_name: splunk-otel-collector
    splunk_app_version: 0.81.0
    timeout: 10s
    tls:
      insecure_skip_verify: false
    token: ${SPLUNK_PLATFORM_HEC_TOKEN}
extensions:
  file_storage:
    directory: /var/addon/splunk/otel_pos
  health_check: null
  k8s_observer:
    auth_type: serviceAccount
    node: ${K8S_NODE_NAME}
  memory_ballast:
    size_mib: ${SPLUNK_BALLAST_SIZE_MIB}
  zpages: null
processors:
  batch: null
  filter/logs:
    logs:
      exclude:
        match_type: strict
        resource_attributes:
        - key: splunk.com/exclude
          value: "true"
  k8sattributes:
    extract:
      annotations:
      - from: pod
        key: splunk.com/sourcetype
      - from: namespace
        key: splunk.com/exclude
        tag_name: splunk.com/exclude
      - from: pod
        key: splunk.com/exclude
        tag_name: splunk.com/exclude
      - from: namespace
        key: splunk.com/index
        tag_name: com.splunk.index
      - from: pod
        key: splunk.com/index
        tag_name: com.splunk.index
      labels:
      - key: app
      metadata:
      - k8s.namespace.name
      - k8s.node.name
      - k8s.pod.name
      - k8s.pod.uid
      - container.id
      - container.image.name
      - container.image.tag
    filter:
      node_from_env_var: K8S_NODE_NAME
    pod_association:
    - sources:
      - from: resource_attribute
        name: k8s.pod.uid
    - sources:
      - from: resource_attribute
        name: k8s.pod.ip
    - sources:
      - from: resource_attribute
        name: ip
    - sources:
      - from: connection
    - sources:
      - from: resource_attribute
        name: host.name
  memory_limiter:
    check_interval: 2s
    limit_mib: ${SPLUNK_MEMORY_LIMIT_MIB}
  resource:
    attributes:
    - action: insert
      key: k8s.node.name
      value: ${K8S_NODE_NAME}
    - action: upsert
      key: k8s.cluster.name
      value: contain-eks-lab
  resource/add_agent_k8s:
    attributes:
    - action: insert
      key: k8s.pod.name
      value: ${K8S_POD_NAME}
    - action: insert
      key: k8s.pod.uid
      value: ${K8S_POD_UID}
    - action: insert
      key: k8s.namespace.name
      value: ${K8S_NAMESPACE}
  resource/logs:
    attributes:
    - action: upsert
      from_attribute: k8s.pod.annotations.splunk.com/sourcetype
      key: com.splunk.sourcetype
    - action: delete
      key: k8s.pod.annotations.splunk.com/sourcetype
    - action: delete
      key: splunk.com/exclude
  resourcedetection:
    detectors:
    - env
    - eks
    - system
    override: true
    timeout: 10s
receivers:
  filelog:
    encoding: utf-8
    exclude:
    - /var/log/pods/splunk_splunk-app-splunk-otel-collector*_*/otel-collector/*.log
    fingerprint_size: 1kb
    force_flush_period: "0"
    include:
    - /var/log/pods/*/*/*.log
    include_file_name: false
    include_file_path: true
    max_concurrent_files: 1024
    max_log_size: 1MiB
    operators:
    - id: parser-containerd
      regex: ^(?P<time>[^ ^Z]+Z) (?P<stream>stdout|stderr) (?P<logtag>[^ ]*) ?(?P<log>.*)$
      timestamp:
        layout: '%Y-%m-%dT%H:%M:%S.%LZ'
        parse_from: attributes.time
      type: regex_parser
    - combine_field: attributes.log
      combine_with: ""
      id: containerd-recombine
      is_last_entry: attributes.logtag == 'F'
      max_log_size: 1048576
      output: handle_empty_log
      source_identifier: attributes["log.file.path"]
      type: recombine
    - field: attributes.log
      id: handle_empty_log
      if: attributes.log == nil
      type: add
      value: ""
    - parse_from: attributes["log.file.path"]
      regex: ^\/var\/log\/pods\/(?P<namespace>[^_]+)_(?P<pod_name>[^_]+)_(?P<uid>[^\/]+)\/(?P<container_name>[^\._]+)\/(?P<restart_count>\d+)\.log$
      type: regex_parser
    - from: attributes.uid
      to: resource["k8s.pod.uid"]
      type: move
    - from: attributes.restart_count
      to: resource["k8s.container.restart_count"]
      type: move
    - from: attributes.container_name
      to: resource["k8s.container.name"]
      type: move
    - from: attributes.namespace
      to: resource["k8s.namespace.name"]
      type: move
    - from: attributes.pod_name
      to: resource["k8s.pod.name"]
      type: move
    - field: resource["com.splunk.sourcetype"]
      type: add
      value: EXPR("kube:container:"+resource["k8s.container.name"])
    - from: attributes.stream
      to: attributes["log.iostream"]
      type: move
    - from: attributes["log.file.path"]
      to: resource["com.splunk.source"]
      type: move
    - from: attributes.log
      id: clean-up-log-record
      to: body
      type: move
    poll_interval: 200ms
    retry_on_failure:
      enabled: true
    start_at: beginning
    storage: file_storage
  fluentforward:
    endpoint: <IP_ADDRESS>:8006
  otlp:
    protocols:
      grpc:
        endpoint: <IP_ADDRESS>:4317
      http:
        endpoint: <IP_ADDRESS>:4318
  prometheus/agent:
    config:
      scrape_configs:
      - job_name: otel-agent
        scrape_interval: 10s
        static_configs:
        - targets:
          - ${K8S_POD_IP}:8889
service:
  extensions:
  - file_storage
  - health_check
  - k8s_observer
  - memory_ballast
  - zpages
  pipelines:
    logs:
      exporters:
      - splunk_hec/platform_logs
      processors:
      - memory_limiter
      - k8sattributes
      - filter/logs
      - batch
      - resourcedetection
      - resource
      - resource/logs
      receivers:
      - filelog
      - fluentforward
      - otlp
  telemetry:
    logs:
      level: debug
    metrics:
      address: <IP_ADDRESS>:8889

Hey, what are the agent's logs? Do you see any errors?

Closing as inactive. @bala151187 please open a support case to receive further guidance. Thanks!


brandimage

i am using opendistro_security plugin version <IP_ADDRESS> with kibana version 7.9.1. i want to change the login image. The image that has the test "Open Distro for Elasticsearch" and it is above the text "Please login to kibana".
I can see that in the file server/index.js we have this section where the brandimage is enabled but i can't find the place that define which image to use:
ui: config_schema_1.schema.object({
    basicauth: config_schema_1.schema.object({
        // the login config here is the same as old config `opendistro_security.basicauth.login`
        // Since we are now rendering login page to browser app, so move these config to browser side.
        login: config_schema_1.schema.object({
            title: config_schema_1.schema.string({ defaultValue: 'Please login to Kibana' }),
            subtitle: config_schema_1.schema.string({
                defaultValue: 'If you have forgotten your username or password, please ask your system administrator',
            }),
            showbrandimage: config_schema_1.schema.boolean({ defaultValue: true }),
            brandimage: config_schema_1.schema.string({ defaultValue: '' }),
            buttonstyle: config_schema_1.schema.string({ defaultValue: '' }),
        }),
    }),
}),

Can someone help please?

You want to add the variable opendistro_security.ui.basicauth.login.brandimage in kibana.yml . https://discuss.opendistrocommunity.dev/t/customizing-the-kibana-login-page/3697
Note the variable name changed in some version by adding the ui. .

You want to add the variable opendistro_security.ui.basicauth.login.brandimage in kibana.yml . https://discuss.opendistrocommunity.dev/t/customizing-the-kibana-login-page/3697
Note the variable name changed in some version by adding the ui. .

I don't have any file with the name kibana.yml

I don't have any file with the name kibana.yml

@samehif It is in the config folder of kibana.

@samehif It is in the config folder of kibana.

thanks a lot. one last question. where do i save my new image and how do i reference it in the opendistro_security.basicauth.login.brandimage: "your-image-url"

thanks a lot. one last question. where do i save my new image and how do i reference it in the opendistro_security.basicauth.login.brandimage: "your-image-url"

We are doing some "spring cleaning in the fall", and to make sure we focus our energies on the right issues and we get a better picture of the state of the repo, we are closing all issues that we are carrying over from the ODFE era (ODFE is no longer supported/maintained, see post here).
If you believe this issue should still be considered for current versions of OpenSearch, apologies! Please let us know by re-opening it.
Thanks!


Check Aircraft Availability

Check if the aircraft is available for flight (State : Parked / On Ground)
If not throw new exception AircraftNotAvailable

If the aircraft state is not PARKED (On Ground) result will be like this when a pilot tries to start a new flight with it.


Add support for low-pri scale sets

This PR enables support for low-pri node pools in AKS and includes vendoring in the 2019-06-01 SDK.
Creating as draft PR as we haven't decided whether to take this feature to public preview yet..

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/seanmck/azure-cli-extensions.git@akslowpri#subdirectory=src/$EXT&egg=$EXT"

@seanmck what's your plan for this pr? can it be closed or should we plan to merge it?

@zikalino , I have talked with @seanmck, please close this PR. I have created a new one.

what's the relationship to az aks?


Supporting meta-data (schema)

As an app deployer and container administrator I want to be able to discover expected configuration options of a deployment (application). Such a discovery should allow me to read configuration keys, expected type (boolean, String), configured default value, and description.

Configuration metadata consists of two parts:

a way to declare what properties/configurable objects are required by the application (such as a source annotation)
a way to transfer this information to runtime (such as a file META-INF/config/config-metadata.json in each jar file that uses configuratino)

The specification should define both of these, not necessarily the way we get from the first information to the second

(see here on how spring does)

namespace: if the file is inside in the app jar, it is scoped to the enclosed app. If the file is under a server location, there should be a way to specify which application scope it means for.


Add Algorithmia Image

Status
Ready/In Progress/In Hold (Reason for hold)
Related Issues
related: link to the issue
Description
This PR introduces an image file that includes the Algorithmia python library

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

I've contacted algorithmia to see if they could add a license for algorithmia-api-client

@luongthomas thanks for your contribution.
Please take a look at the note regarding the CLA: https://github.com/demisto/dockerfiles/pull/1339#issuecomment-586524128 . You must sign the CLA in-order for us to merge the contribution.
The algorithmia license looks ok. I will push an update to add this to our known licenses, once the CLA is signed.

@luongthomas thanks for your contribution.
Please take a look at the note regarding the CLA: #1339 (comment) . You must sign the CLA in-order for us to merge the contribution.
The algorithmia license looks ok. I will push an update to add this to our known licenses, once the CLA is signed.

I've signed the license agreement 👍

Docker Image Ready - Production
Docker automatic build at CircleCI has deployed your docker image: demisto/algorithmia:<IP_ADDRESS>16
It is available now on docker hub at: https://hub.docker.com/r/demisto/algorithmia/tags
Get started by pulling the image:
docker pull demisto/algorithmia:<IP_ADDRESS>16

Docker Metadata

Image Size: 40.44 MB

Image ID: sha256:6449388564169211cc3721e2091e55fbc759bcc452128a8f2852d1900a6557b2

Created: 2020-02-15T01:03:01.708561234Z

Arch: linux/amd64

Command: ["python3"]

Environment:

PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
LANG=C.UTF-8
GPG_KEY=E3FF2839C048B25C084DEBE9B26995E310250568
PYTHON_VERSION=3.8.1
PYTHON_PIP_VERSION=20.0.2
PYTHON_GET_PIP_URL=https://github.com/pypa/get-pip/raw/42ad3426cb1ef05863521d7988d5f7fec0c99560/get-pip.py
PYTHON_GET_PIP_SHA256=da288fc002d0bb2b90f6fbabc91048c1fa18d567ad067ee713c6e331d3a32b45

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:16403a1d68db7f0ffb0ab595e8a614189f69dfb6
org.opencontainers.image.version:<IP_ADDRESS>16


Cache component query results

python src/bikey_wagon/main.py  87.93s user 24.01s system 52% cpu 3:34.41 total with caching
python src/bikey_wagon/main.py  79.57s user 23.47s system 44% cpu 3:52.02 total without
No tangible difference.
<Prefix>: <Title>
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Checklist
Please read and execute the following:

[ ] My code follows the coding guidelines of this project
[ ] My PR title is following the contribution guidelines
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation (if applicable)
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works (if applicable)
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I ran Black to format my code

Code of Conduct
By submitting this issue, you agree to follow our Code of Conduct:

[ ] I agree to follow this project's Code of Conduct

Have you ran it with `./tools/profile.sh py pyinstrument '?
Looks like most time is spent in the python part (not sql part). We can cache that too.

Thanks for the link! I’ll give it another swing with the profiler when I
get the chance
On Fri, Aug 16, 2024 at 23:58 IoannisP-ITENG @.***>
wrote:

Have you ran it with `./tools/profile.sh py pyinstrument '?
Looks like most time is spent in the python part (not sql part). We can
cache that too.
—
Reply to this email directly, view it on GitHub
https://github.com/atopile/faebryk/pull/15#issuecomment-2294712800, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABALRKXHHXNGU67QJ5BOWWDZR3YAXAVCNFSM6AAAAABMVCLF6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUG4YTEOBQGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Superseded by CachePicker


Implement support for chunked models

Implement model chunking for set_model() and get_model()
Add support for AI.CONFIG to set model chunking size
Update unit tests to verify chunking support
Remove an extraneous debug print statement

Resolves #186

Codecov Report

Merging #237 (3772da7) into develop (ee21858) will increase coverage by 13.86%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##           develop     #237       +/-   ##
============================================
+ Coverage    82.39%   96.25%   +13.86%
============================================
  Files           51        5       -46
  Lines         2800      401     -2399
============================================
- Hits          2307      386     -1921
+ Misses         493       15      -478

Impacted Files
Coverage Δ

src/python/module/smartredis/client.py
95.84% <100.00%> (+0.06%)
:arrow_up:

include/client.h

include/command.h

include/command.tcc

include/commandreply.h

include/redisserver.h

src/cpp/client.cpp

src/cpp/redis.cpp

src/cpp/redisserver.cpp

src/cpp/dbnode.cpp

... and 37 more

This issue is currently blocked by https://github.com/RedisAI/RedisAI/issues/908


Cross Domain Storage

Question
I've used Hive in a couple of production native apps and absolutely love it. Looking to use it in a web project but I have a requirement to store access tokens for multiple domains in one place, eg. dev.com and auth.dev.com and app.dev.com etc all need access to the same storage. Is this possible with Hive?
I know in Javascript this is complicated as cross-domain access to localstorage isn't allowed. One solution is to use an iFrame, which is what cross-storage does. But I'm not sure what the limitations of Hive are and how one would achieve this?

What about using cookies?

@TomasWeg I guess that's an option, but not really a correct use case for cookies. Storing access tokens for a web app is a job for localstorage or something similar. So I guess a better general question would be: is it possible for two different Flutter apps to access the same Hivedb?

No Hive doesn't supports using same database on multiple domains.  Because, hive uses IndexedDB for storing data on web. And IndexedDB limits access scope to only current origin.


Fix mobile web logout bug

Problem
https://artsyproduct.atlassian.net/browse/FX-1927
User-facing issue
Clicking "Logout" from the navbar on old mobile web views (i.e. not Reaction) produces no result and the user is not able to log out. Users can still logout on desktop and mobile web views using Reaction.
Issue root
The handler for the auth:logout event lives in global_client_setup.tsx and is set up by invoking globalClientSetup. Desktop views and Reaction views both use this client setup but old mobile web views do not. When the user attempts to logout, the mediator triggers the auth:logout event but the corresponding listener doesn't exist. The result is that the user cannot logout.
Solution

Add new logoutEventHandler method  that listens for the auth:logout event to common mobile layout code for old mobile web routes.
Add desktop FlashMessage component to common old mobile web layout. This error handling UI is currently used on Reaction pages on mobile web.

FlashMessage UI on mobile web:

@williardx just had a tiny comment, but feel free to address (or not) and merge when ready.


Review sequence of steps for Module 4 Activity 1

In Activity 1 for Module 4 at https://github.com/microsoft/sqlworkshops/blob/master/AzureSQLLabs/Lab-DatabaseDiscoveryAndAssessmentForMigratingToAzure.md#Activity-1
You list out these steps
For assessment tools, select Azure Migrate: Database Assessment, then select Add tool.
For migration tools, select Azure Migrate: Database Migration, and then select Add tool. Azure Migrate is now set up for you to use. In the next activity, you'll use some of the tools you added to assess and migrate Tailspin Toys to Azure.
Please review those screens. I think I had to hit Next instead of Add Tool and then when I was done I had to select Add Tool.

Good catch. Confirmed and updated in my branch


Possible to have cropped image.

Is it possible to return cropped image? For example, if I have image 640x480, I wanted to return center (or specified area) of ie 300x300.
Note: When I specify only maxWidth as option, the gallery hang.

Hi @ryc16,
For your case you could use nativescript-imagecropper that provides such a functionality.
Hope this helps.

Provide maxWidth, maxHeight from this interface https://github.com/NativeScript/nativescript-imagepicker/blob/master/nativescript-imagepicker/index.d.ts#L4 to the getImage here: https://github.com/NativeScript/nativescript-imagepicker/blob/master/nativescript-imagepicker/index.d.ts#L43 and then crop the image using the image cropper.


Learn about jgit

https://www.eclipse.org/jgit/

https://github.com/centic9/jgit-cookbook/blob/master/README.md

https://www.eclipsecon.org/2013/sites/eclipsecon.org.2013/files/Scaling Up JGit - EclipseCon 2013.pdf

https://stackoverflow.com/questions/1911109/how-do-i-clone-a-specific-git-branch

https://www.diva-portal.org/smash/get/diva2:638844/FULLTEXT01.pdf

https://wiki.eclipse.org/JGit/User_Guide

https://doc.nuxeo.com/blog/jgit-example/

https://bluef.github.io/gitgraph.js/

https://github.com/eclipse/jgit/blob/master/org.eclipse.jgit.test/tst/org/eclipse/jgit/transport/RemoteConfigTest.java

https://golb.hplar.ch/2019/08/git-with-jgit.html

Acquired basic level of Jgit


KAFKA-15480: Add RemoteStorageInterruptedException plugin controlled…

Exception allows the plugin to notify Kafka an API operation in progress was interrupted as a result of task cancellation, which can happen under changes such as leadership migration or topic deletion. In addition exposes log for better visibility during debugging.

Any changes to plugin API/contract (including throwing new exceptions) requires a KIP since those API are considered public facing (and plugin providers use them). Please add a KIP to the description once you have created one.


Internationalization

Hi all!
There are a strong demand to have an English version of YAPI.
So I do some internationalization via 'react-intl-universal' and Deepl. Besides, I also add a language switcher in Header.

Hope you can enjoy it.

@hellosean1025 Hi, will you approve this PR, or add official i18n support in future? Thanks!


New feature: add option to open logcat

The goal of this issue is to add option to launch logcat for each device separately.
Logcat should launch with -v color flag. This feature should also take into account user's preferred terminal (iTerm, Terminal.app etc.)
This was currently achievable through custom commands but native support would increase the use of this feature

@okwasniewski  Shall I work on this

@gokul1099 Sure! Go ahead

@okwasniewski  users preferred terminal means, whether the terminal the user set as default terminal or we have to ask the user to select the terminal they prefer to open the logcat

I would keep an option in Preferences which dropdown for iTerm.app, Terminal.app and others but I think we can implement it in the next iteration. So firstly let's implement this feature as a whole (keeping in mind that in the future we will change the terminal we are launching). What do you think?

Yes, We can incorporate an option in the preferences to allow users to select their default terminal. But for now, we can include a functionality that checks the user's preference. If a preferred terminal is set, the application will open that terminal; otherwise, it will default to the system's default terminal. As we introduce the ability to select the preferred terminal in the future, this functionality will seamlessly align with the new option and adapt accordingly.

@okwasniewski  hey I need help on this. When I try to open the terminal and run the adb script for opening the logcat the terminal is opened but the adb command is not getting executed and terminal remain empty. I used shellout to with open command
try shellOut(to: "open -a (preferedTermial) --args bash -c(logcatCommand)")
I also tried using Process to execute this command even in that case terminal open up, but the add command is not getting executed.  Do you have any idea on this ??

I think the easiest way to achieve this is with AppleScript:
osascript -e 'tell app "Terminal"
    do script "adb logcat -v color"
end tell'

Im not sure however how this would work for iTerm

I think the easiest way to achieve this is with AppleScript:
osascript -e 'tell app "Terminal"
    do script "adb logcat -v color"
end tell'

Im not sure however how this would work for iTerm

This is working for Terminal in case of iTerm the script should be like
tell application "Terminal"
set newWindow to (create window with default profile)
tell current session of newWindow
write text "adb -s emulator-5554 logcat -v color"
end tell
end tell
It is like different script for different terminal.

Looks like NSWorkspace is commonly used to open terminal in a certain directory. Just by switching iTerm to Terminal we can achieve terminal opened in different directories. NSWorkspace.shared.openFile(filePath, withApplication: "iTerm")
However its not that simple to execute commands. Looks like apple script is the recommended way of doing so. What you could do is create a protocol something like a Terminal which would have open() method for each terminal: iTerm, Terminal, Hyper etc. that would run those apple scripts and that way we would have a clean architecture with a way of expanding to new ones.

@okwasniewski  I have made one pull request please check


only one id

if only has one id for some class, then raise error
print(cls_id, nID)
self.emb_scale_dict[cls_id] = math.sqrt(2) * math.log(nID - 1)

Even i had the same problem. I modified the part of the code like this:
        for cls_id, nID in self.nID_dict.items():
            nID = max(nID, 2)                             # Added Line
            self.emb_scale_dict[cls_id] = math.sqrt(2) * math.log(nID - 1)

But i am not sure if it is the right way.
@CaptainEven  can you please comment on this.
ThankYou

I see this was opened quite some time ago ;) but I stumbled on the same issue and I'm curious if such assumption of a fixed minimum can in some negative way affect the pipeline.


Error when using fromString

Trying to take operators like < and return something like { op: "<" }:
syntax foo = function(ctx) {
  const op = ctx.next().value;
  const x = #`dummy`.get(0);
  return #`{ op: ${x.fromString(op.val())} }`;
}

foo +=;

The above fails with Error: [assertion error]: all tokens must have line info.
Just doing #{ op: null } works as well as #${x.fromString(op.val())} } so it's a weird combination of the two.

This works:
syntax foo = function(ctx) {
  let op = ctx.next().value;
  op = #`${op.fromString(op.val())}`;
  return #`{ op: ${op} }`;
}

foo +=;

For some reason I can't inline the op.fromString expression. This happens even with string literals:
syntax foo = function(ctx) {
  let dummy = #`dummy`.get(0);
  return #`x ${dummy.fromString("hi")}`;
}

// Error!
foo;

The above code fails, but if you remove the x from the template it works.

There's an assumption on https://github.com/sweet-js/sweet.js/blob/aee31d07bafd6c582ec68875886e1dd4ab7d7b60/src/template-processor.js#L55 that if to is a Syntax object that it also has slice data.
@jlongster your working examples fail that check and the call to setLineNumber is never made.
I think a check for slice should do it.

I spoke too soon. There is a Term::setLineNumber as well.

I think a check for slice should do it.

That does fix it, but I don't know if it introduces any regressions. Should it check to.slice or from.slice? Seem like it should check from as you are cloning onto to so it seems like that shouldn't have location info in the first place.

It does introduce a regression. I'm trying to track down the cause as we speak.

 All of the tests still pass.

Seem like it should check from as you are cloning onto to so it seems like that shouldn't have location info in the first place.

to will have location info if it was a pre-existing Syntax object. It's when one is created w/ .from* that there's a lack of info.
It should probably check both to and from, but the assertion that throws the error is pretty clear about tokens having to have location info. But that obviously doesn't make sense in this case.
@disnet?

Actually, I think what we need to do is make the from* methods copy slice to the new syntax object. It was just an oversight that they weren't already; much better to have the invariant that all syntax objects flowing through the expander have line info.

@disnet should this be added in the Syntax constuctor?
https://github.com/sweet-js/sweet.js/blob/278e5db0e14c00dec0aac8273a21e720bc7ef6de/src/syntax.js#L172

@gabejohnson Syntax.from.
Or more accurately, the various Types.create functions that call new Syntax with a brand new token. Maybe we should have a token constructor?

@disnet a token constructor is fine. It would cut down on some code. What's the signature?
Also, why wouldn't we copy over slice from the token of oldstx in the Syntax constructor?

Token(type, value, slice) maybe?
We wouldn't want to copy slice by default in the Syntax constructor because sometimes the slice in the provided token is fine.

I made a partial fix for this since it was holding up the build of 2.2.0. I think a real fix involves refactoring how we handle Terms, Syntax, and Tokens, which I'm playing around with now.

@disnet Do we want to make a Token spec similar to the new Term spec?

Incidentally I think this is fixed
syntax foo = function(ctx) {
  const op = ctx.next().value;
  const x = #`dummy`.get(0);
  return #`{ op: ${x.fromString(op.value.val())} }`;
}

foo +=;
// ;
// {
//   op: "+=";
// }
// ;

Do we want to make a Token spec similar to the new Term spec?

Hold off for now. The spec macro is in need of cleaning.


Feature Request - Ability to remove arrows stuck inside player models

Mergu referred me to this place to request a feature with which arrows stuck in players could be removed.
Normally, if a player drinks an invis potion, any arrows stuck inside the player model do not turn invisible along with the player.
So, rather than masking them, I was hoping that they can be removed, such as with - remove, or perhaps a new function.
After some digging, I came across a Spigot thread that had the following to say.
https://www.spigotmc.org/threads/removing-arrows.72723/
((CraftPlayer)player).getHandle().getDataWatcher().set(new DataWatcherObject<>(10, DataWatcherRegistry.b),0);
I personally do not know what these functions do, but apparently Mergu did have some idea -- and adviced to make a feature request, so that this can be given a thought, or examination, or ... perhaps a ponder.
Thanks!

Magic number seems to be 9 instead of 10 in 1.8, will require testing in each version but seems useful and interesting.

I doubt the event comment is relevant/helpful here.
Unless you can use on player damaged by arrow: - remove <context.damager> and it removes the arrow

That was more to reference the major CPU load it might cause.
I do not know if that is accurate, but since someone thought of it, I thought to mention it.
As for events. <context.damager>is the entity firing the bow, so lets not do that. Instead, <context.projectile> is the arrow in flight, which can be removed if the arrow rebounds, like, from a Citizens2 NPC, but once it gets stuck inside of a player, it no longer is that entity that <context.projectile> covers.
If you need more testing done, let me know, and I'll try to provide the results.


Error: Invalid schema object - webpack

Hi everyone, when I compile my application with webpack get an error on console.
The problem is on this file workbox-build > build > options > partials > generate.js
in this lines of code:
.when('navigationPreload', {     is: true,     then: joi.required()   }),
if remove this not have error in console.
Library Affected:
workbox-build
Browser & Platform:
all browsers
Console Error
Error: Invalid schema object     at new module.exports (mypath/node_modules/@hapi/hoek/lib/error.js:23:19)     at Object.module.exports [as assert] (mypath/node_modules/@hapi/hoek/lib/assert.js:20:11)     at internals.Array.concat (mypath/node_modules/@hapi/joi/lib/types/any/index.js:143:14)     at internals.Array.when (mypath/node_modules/@hapi/joi/lib/types/any/index.js:436:60)     at Object.<anonymous> (mypath/node_modules/workbox-build/build/options/partials/generate.js:62:45)     at Module._compile (internal/modules/cjs/loader.js:688:30)     at Object.Module._extensions..js (internal/modules/cjs/loader.js:699:10)     at Module.load (internal/modules/cjs/loader.js:598:32)     at tryModuleLoad (internal/modules/cjs/loader.js:537:12)     at Function.Module._load (internal/modules/cjs/loader.js:529:3)     at Module.require (internal/modules/cjs/loader.js:636:17)     at require (internal/modules/cjs/helpers.js:20:18)     at Object.<anonymous> (mypath/node_modules/workbox-build/build/options/schema/webpack-generate-sw.js:16:25)     at Module._compile (internal/modules/cjs/loader.js:688:30)     at Object.Module._extensions..js (internal/modules/cjs/loader.js:699:10)     at Module.load (internal/modules/cjs/loader.js:598:32)     at tryModuleLoad (internal/modules/cjs/loader.js:537:12)     at Function.Module._load (internal/modules/cjs/loader.js:529:3)     at Module.require (internal/modules/cjs/loader.js:636:17)     at require (internal/modules/cjs/helpers.js:20:18)     at Object.<anonymous> (mypath/node_modules/workbox-webpack-plugin/build/generate-sw.js:20:33)     at Module._compile (internal/modules/cjs/loader.js:688:30)

Could you provide your full GenerateSW() configuration, along with the version of workbox-webpack-plugin and webpack that you're using?
I just gave it a quick try, and the relevant parameter validation does appear to be working as expected.
This line is meant to check that when navigationPreload is set, runtimeCaching also needs to be set:
https://github.com/GoogleChrome/workbox/blob/26958c6ce3fa3bb394117e2aead51c92b08d6a4a/packages/workbox-build/src/options/partials/generate.js#L78-L81

Hi @jeffposnick,
this is my GenerateSW configuration (the last on plugins list in webpack configuration)
new GenerateSW({
          swDest: 'sw.js',
          clientsClaim: true,
          skipWaiting: true,
          navigationPreload: false,
          offlineGoogleAnalytics: true,
        }),

and the version of modules:
"workbox-webpack-plugin": "^5.1.2"
"webpack": "^4.25.1"
Thanks

I'm not able to reproduce this.
I started from scratch with the following webpack.config.js:
const path = require('path');
const {GenerateSW} = require('workbox-webpack-plugin');

module.exports = {
  entry: path.join(__dirname, 'src', 'app.js'),
  mode: 'development',
  output: {
    path: path.join(__dirname, 'build'),
  },
  plugins: [
    new GenerateSW({
      swDest: 'sw.js',
      clientsClaim: true,
      skipWaiting: true,
      navigationPreload: false,
      offlineGoogleAnalytics: true,
    }),
  ],
};

src/app.js is something really basic, like console.log('hello').
I'm able to successfully run the webpack build and a service worker file is generated.
Can you start fresh—remove your node_modules and reinstall everything, or do this in a new directory—and see if you can reproduce the issue still?

Hello @jeffposnick!
Ok after many attempts with a fresh installation, the problem seems the package "webpack-merge", but it's very strange because if I change order of import, GenerateSW don't show errors.
from (show error)
const merge = require('webpack-merge');
const { GenerateSW } = require('workbox-webpack-plugin');

to (work correctly)
const { GenerateSW } = require('workbox-webpack-plugin');
const merge = require('webpack-merge');

Okay, thanks for debugging this further.
I don't know that there's anything actionable that we can do on the Workbox side of things to prevent this behavior—it sounds more like webpack-merge is doing something that messes with the underlying joi validation library dependency.
I'm going to close this for now unless there's something that comes up which we could be doing differently.


Save flash for app settings & project configuration

During the work on PR #295 we've noticed that we need a message after the saving acutally happend so the user gets a feedback.
We'd like to change the behaviour at ProjectConfiguationModal too. As there it will autohide the dialog and this is the feedback that saving happend. We'd like to keep the modal open and show the flash message as well.
Describe the solution you'd like
Add a small text saved close to the save button that will auto hide after 2 seconds. Styling could be similar to the style from the info text on ProjectConfiguration modal if save button is blocked.
I think it's OK to add a saved flag on app-status.reducer and then the component that will display the flash can connect to this do display the message for two seconds and clear afterwards the saved flag with an action.
Additional context
This requires the app-settings feature from PR #295. You could start working if you're using app-settings branch as base for your work.

I'll give it a shot!

I thought the auto-close was fine. I was thinking of adding the save flash after the auto-close at the bottom of the current screen that auto-hides after 2 seconds or so.
I also wonder if it's necessary for the app to prompt the user for confirmation when changing the project name.
I think adding a close/cancel button is definitely helpful. It could be put next to "save project" button and maybe prompt user for "discard changes" confirmation if there are any changes already made to the project configurations.

Yes, sound good. I like the idea of having toast messages that will auto-hide. For now it's OK to auto-close dialogs on save & show a message about saving afterwards.
We could add the other behaviour later. If it's really needed.
I think React-Redux-Toastr Repo & demo would be good.
There are probably other libs but that was the first I've found. Maybe you c
I think the prompt after project name change is needed as it's asking if it's OK to rename the project folder as well. Some users just want to rename the name inside package.json and not the project folder on disk.
The prompt with a warning of unsaved changes would be also great. Can this also be triggered with the backdrop dismiss?

I played a bit with the toast messages because I wanted to check how this is working.
You can find my code here. Just not sure how to do the styling - using css with important feels a bit hacky.

Thanks for the code! I'll play around with it and see if I can tweak the styling a bit.


Update all installed packages

It would be great to have a way to easily update all installed packages. This can more or less already be done by doing something like
jpm list-installed | xargs -I _ sudo jpm install _

However, this only works to update dependencies which are themselves listed in pkgs.janet (those in the official package listing), but not for those packages that are only possible to install directly via git (for example: jpm install https://github.com/sogaiu/jandent).
Should be pretty easy to implement, just go through the files in the .manifest dir and call install for each of them. Although I might not be considering some potential issues

Added the 'update-installed` command to address this. Note that there is still some question about semantics here, especially when installing some packages from the "latest master", vs a specific tag. JPM only tracks that specific git commit installed, not what the user requested to be installed. So this may update packages that a user requested to be a specific tag. Still, I think for version pinned dependencies one should use a lockfile.

That's great! and yes, I agree with the fact that pinned dependencies should use a lockfile. Also, I imagine globally installed packages would normally be binaries, so one normally wants to keep those up to date :)
Tagging the commit here just in case anyone is interested c886d61d170194c8e6a605658a17a078b6ab546a
Closing this issue


Writing to extended XYZ format

New functionality to write to the extended XYZ format

Example python API usage:
from pymlff import MLAB

# load an ML_AB file
ab = MLAB.from_file("ML_AB")

# write to an .xyz file
ab.write_extxyz("ML_AB.xyz")

Example cli usage:
mlff write-extyxz ML_AB ML_AB.xyz

Can be useful for other programs which read in configurations in the XYZ format such as Nequip/Allegro
Can be read into ase:

Example:
from ase.io import read

atoms = read(ML_AB.xyz)

Thanks @AntObi!


Upgrade to Rails 7.1 (resolve conflicts)

What
Closes #13 and #141

https://github.com/ffi/ffi/issues/1107
This causes type checking failing...

It's better to ignore ffi gem on type checking temporarily.
# in rbs_collection.yaml
gems:
  - name: ffi
    ignore: true

GO!!!!!!!!!!!!!!!!!!!


firefox xeditable input & buttons missing

If I use xeditable within a table 'td' tag then it works in chromium but not in firefox (version 38)
        {{version.from_date}}

If I put it within a span, it works fine.

          {{version.from_date}}

I'm experiencing the same behaviour, How can we investigate more on the problem?

If you use an  tag as the root of the editable text it started working fine in Firefox. Couldn't figure out how to get the  going with it.

Today I've run into the same issue with Firefox. Chrome and Safari work fine on  tags.
The work-around of moving the editable-* attributes to a  withing the  appears to work. Thanks for the suggestion, @map7 .
(All versions current as of 25 Jan 2017.)

The reason a td doesn't work is because the code tries to hide the text when the input field is shown.  Since the td contains both the text and the input field, the td ends up being hidden which then messes things up.
The documentation does state that editable-elements should be placed inside table cells.
This is working as intended and can be closed.

@eugef please close