Install guide is outdated.  | Bazel fails to build

Looks like the install guide is outdated due to folder hierarchy has changed.  Install guide shows that java folder is in root of nomulus git clone folder.  No longer the case.  Ive tried adapting to the folder structure.  I created the WORKSPACE, ref'd the folder as per the guide.  I continue to fail to build. nomulus /core/src/main/ java/google/registry/
ERROR: Skipping '//core/src/main/java/google/registry/...': no targets found beneath 'core/src/main/java/google/registry'
ERROR: no targets found beneath 'core/src/main/java/google/registry'

To be fair I used git clone https://github.com/google/nomulus.git instead of git clone git@github.com:google/nomulus.git however Im not aware of a difference in the results as I dont believe the folder structure should change based on https vs ssh.
git clone section
Install Guide Output
$ git clone git@github.com:google/nomulus.git
Cloning into 'nomulus'...
[ .. snip .. ]
$ cd nomulus
$ ls
apiserving       CONTRIBUTORS  java        LICENSE    scripts
AUTHORS          docs          javascript  python     third_party
CONTRIBUTING.md  google        javatests   README.md  WORKSPACE

Real Life Output
cnsdomainregistar@cloudshell:~/nomulus (nomulus-project)$ ls
appengine_war.gradle  buildSrc         CONTRIBUTORS  dependencies.gradle    gradle             gradlew.bat         LICENSE           package-lock.json  proxy      release          third_party
AUTHORS               config           core          dependency_lic.gradle  gradle.properties  java_common.gradle  nomulus-logo.png  prober             python     services         util
build.gradle          CONTRIBUTING.md  db            docs                   gradlew            java-format         package.json      projects.gradle    README.md  settings.gradle  utils.gradle
cnsdomainregistar@cloudshell:~/nomulus (nomulus-project)$

FAILS TO BUILD BAZEL
cnsdomainregistar@cloudshell:~/nomulus (nomulus-project)$ bazel version
Build label: 0.25.0
Build target: bazel-out/k8-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Wed May 1 21:45:01 2019<PHONE_NUMBER>)
Build timestamp:<PHONE_NUMBER>
Build timestamp as int:<PHONE_NUMBER>
cnsdomainregistar@cloudshell:~/nomulus (nomulus-project)$

cnsdomainregistar@cloudshell:~/nomulus (nomulus-project)$ touch core/src/main/java/google/registry/WORKSPACE
cnsdomainregistar@cloudshell:~/nomulus (nomulus-project)$ bazel --batch  build --javacopt="-target 8 -source 8" //core/src/main/java{,tests}/google/registry/...
WARNING: --batch mode is deprecated. Please instead explicitly shut down your Bazel server using the command "bazel shutdown".
ERROR: Skipping '//core/src/main/java/google/registry/...': no targets found beneath 'core/src/main/java/google/registry'
ERROR: no targets found beneath 'core/src/main/java/google/registry'
INFO: Elapsed time: 1.695s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)

We now build with Gradle. Please try ./gradlew build instead.
Note that you probable won’t be able to run all the tests on Cloud Shell as Docker is needed for tests. Try ./gradlew build -x test to skip tests.
We’ll update the install guide. Thanks for reporting.

This appears to only have installed gradle 6.0.  This is a pretty easy method looks like.
Whats the process to build nomulus similar to this section?
HERE

cnsdomainregistar@cloudshell:~ (nomulus-project)$ ./nomulus/gradlew build
Downloading https://services.gradle.org/distributions/gradle-6.0-all.zip
.............10%.............20%..............30%.............40%..............50%.............60%..............70%.............80%..............90%.............100%

> Task :buildEnvironment

------------------------------------------------------------
Root project
------------------------------------------------------------

classpath
No dependencies

A web-based, searchable dependency report is available by adding the --scan option.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.0/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 17s
1 actionable task: 1 executed

You'll need to run ./gradlew build in the nomulus directory. Gradle finds tasks under the current directory. To deploy, edit projects.gradle and run ./gradlew deploy -Penvironment=<your environment>.

Trying to deploy this and getting the following error
`google.registry.module.ServletBase service: Received FrontendServlet request
google.registry.request.auth.RequestAuthenticator authorize: Action requires auth: AuthSettings{methods=[INTERNAL, API, LEGACY], minimumLevel=NONE, userPolicy=PUBLIC}
google.registry.request.auth.RequestAuthenticator authenticate: Authenticated via legacy auth: AuthResult{authLevel=USER<EMAIL_ADDRESS>isUserAdmin=true, oauthTokenInfo=Optional.empty}]}
com.google.monitoring.metrics.MetricRegistryImpl newIncrementableMetric: Registered new counter: /console/registrar/console_requests
com.google.monitoring.metrics.MetricRegistryImpl newIncrementableMetric: Registered new counter: /console/registrar/setting_requests
google.registry.request.auth.AuthenticatedRegistrarAccessor createRoleMap: Checking registrar contacts for user ID<PHONE_NUMBER>20689725171
google.registry.request.auth.AuthenticatedRegistrarAccessor : admin<EMAIL_ADDRESS>has the following roles: {}
google.registry.request.RequestMetrics record: Action called for path=/registrar, method=GET, authLevel=USER, success=true. Took: 1.138s
google.registry.module.ServletBase service: Finished FrontendServlet request. Latency: 1.198s
com.google.apphosting.runtime.jetty9.JettyLogger warn: Error for /registrar
com.google.common.util.concurrent.ExecutionError: java.lang.ExceptionInInitializerError`

Is<EMAIL_ADDRESS>the account that has admin role in the GCP project that hosts this nomulus instance?

Yes it does<EMAIL_ADDRESS>has been assigned as admin for the project. Image uploaded as ref.

OK. The auth logic for the console has been updated so I'm not 100% sure this would fix it, without digging through the code:

Create a registrar with the the command line tool:

nomulus -e production create_registrar

Add<EMAIL_ADDRESS>as a registrar contact to that registrar:

nomulus -e production registrar_contact <registrar> --mode CREATE  --email<EMAIL_ADDRESS>--allow_console_access=true --name '<some name>''
And then try go to /registrar again.

K thanks will update soon.

What is the gradle command to build the admin tool?

https://github.com/google/nomulus/blob/6af1896362b86fc4d6098757b360a3b7d4c6c3c0/core/build.gradle#L690

Whats the is corresponding build command in Gradle?
bazel build //java/google/registry/tools:nomulus

./gradlew build -x test registryTool

Task :core:registryTool FAILED
Exception in thread "main" java.lang.IllegalArgumentException: Please specify the environment flag, e.g. -e production.
at google.registry.tools.RegistryToolEnvironment.getFlagValue(RegistryToolEnvironment.java:150)
at google.registry.tools.RegistryToolEnvironment.parseFromArgs(RegistryToolEnvironment.java:68)
at google.registry.tools.RegistryTool.main(RegistryTool.java:126)

@jianglai Whats the ETA of the revised install.md file ?
Having you guys go through a new installation process (in detail) would probably be a faster resolution to this instead of chopping issues off one by one as they come in.

./gradlew build -x test registryTool

Task :core:registryTool FAILED
Exception in thread "main" java.lang.IllegalArgumentException: Please specify the environment flag, e.g. -e production.
at google.registry.tools.RegistryToolEnvironment.getFlagValue(RegistryToolEnvironment.java:150)
at google.registry.tools.RegistryToolEnvironment.parseFromArgs(RegistryToolEnvironment.java:68)
at google.registry.tools.RegistryTool.main(RegistryTool.java:126)

Please check the comments in the link that I referenced. If you run gradle registryTool, you can add --args "-e production create_registrar ..." after it.
Or you can run gradle nomulus to create a nomulus.jar file in core/build/libs and run the jar file directly with java.
Regarding updates to the instruction, we will try to bump the priority. It would be better if you guys can let us know what you are trying to achieve, so that we can better help you.

@mindhog It looks like we should probably have a fix-it hackathon to fix all the docs, including external docs, rather than doing it piecemeal. There are also some internal docs like how to create a registrar contact and enable console access that should be moved to external as well. What do you think?

@jianglai Thank you for all the quick responses.  You've been really good at that.
Right now its really just build and deploy it to demo it on app engine.  Regardless of how its used in production is ultimately irrelevant in regards to just trying to deploy it on app engine to test it.

Thanks I will try running this command shortly.

@jianglai Thank you for all the quick responses. You've been really good at that.
Right now its really just build and deploy it to demo it on app engine. Regardless of how its used in production is ultimately irrelevant in regards to just trying to deploy it on app engine to test it.

Understood. If you just want to try it out, the registrar console would not be the first thing that I'd recommend you experiment with. It is mostly for registrars to set some basic settings, all of which can be achieved by using the command line tool. I'd recommend you build the command line tool and try using it to administer the GAE app, and also try setting up the proxy so that you can actually send EPP and WHOIS requests to your app.
Always happy to help out. Let us know if you have any other questions.

Would y'all mind introducing yourselves?  It'd help us to know what kind of use case you're dealing with, e.g. are you a ccTLD, gTLD, registry service provider, etc.?

java -jar ./core/build/libs/nomulus.jar -e alpha login
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Please open the following address in your browser:
https://accounts.google.com/o/oauth2/auth?client_id=YOUR_CLIENT_ID&redirect_uri=http://localhost:55256/Callback&response_type=code&scope=https://www.googleapis.com/auth/cloud-platform https://www.googleapis.com/auth/appengine.apis https://www.googleapis.com/auth/userinfo.email https://www.googleapis.com/auth/appengine.admin
Attempting to open that address in the default browser now...
Gets me nowhere :)

java -jar ./core/build/libs/nomulus.jar -e alpha create_registrar
Create new registrar account(s)
Usage: create_registrar [options] Client identifier of the registrar account
What ID do you expect?

@CydeWeys  You bet.  This will operate as a gTLD which will service more than one TLD.

java -jar ./core/build/libs/nomulus.jar -e alpha login
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Please open the following address in your browser:
https://accounts.google.com/o/oauth2/auth?client_id=YOUR_CLIENT_ID&redirect_uri=http://localhost:55256/Callback&response_type=code&scope=https://www.googleapis.com/auth/cloud-platform https://www.googleapis.com/auth/appengine.apis https://www.googleapis.com/auth/userinfo.email https://www.googleapis.com/auth/appengine.admin
Attempting to open that address in the default browser now...
Gets me nowhere :)

Please refer to this section to configure your OAuth2 client ID and secret for your command line tool.

java -jar ./core/build/libs/nomulus.jar -e alpha create_registrar
Create new registrar account(s)
Usage: create_registrar [options] Client identifier of the registrar account
What ID do you expect?

This would be the id that you want to give to the new registrar. We have a registrar that we use internally to allocate domains for ourselves.

How do I get this ID?

@oWhizardo  I sent it to you just now.  Check ur chat.

@mindhog It looks like we should probably have a fix-it hackathon to fix all the docs, including external docs, rather than doing it piecemeal. There are also some internal docs like how to create a registrar contact and enable console access that should be moved to external as well. What do you think?

Well, there's a lot of internal documentation that is not very frequently used and I don't think we want to deal with it at the same priority as something like this.  I think we should identify what we want to fix or migrate and then we can talk about whether we need a fixit to do it.

@mindhog  That would be really great.  As helpful as this thread is, it is a game of ping pong and I'm sure you have better things to do.  :)

@mindhog @jianglai  Any progress on this front?

@mindhog @jianglai Any progress on this front?

The plan is to try to update the docs during the holiday period (last two weeks of the year) when things are slow. If you have questions in the meantime, feel free to ask them. Apologies for the delay.

Any progress on the docs update? @jianglai @mindhog

Sorry to have dropped the ball on this.  The install doc, at least, was updated this year: https://github.com/google/nomulus/blob/master/docs/install.md  Most of the other docs should be as well, though it appears that "developing" still references bazel.
If you're still interested, please give it a try.


Weex Vue Render does not render responsive web css (Bootstrap)

Weex Toolkit is a very wonderful tool. I have successful run the tool on our development environment and it was fine.
But then I noticed a bug. I believe the main purpose of Weex is to share same code based from Vuejs  for Web and Mobile development.
However, Weex Vue Render used in latest verwsion of Weex does not render existing mobile responsive web css  such as Bootstrap. This means that existing Vuejs codes on vue cli cannot be migrated to Weex. This is a bug and a major set back as its not realistic for every Weex developer to develop Vue application from ground up on Weex as there are a lot of existing Vue applications that needs to be migrated to Weex.
Please how can this issue be resolved.
Makes sure these boxes are checked befor submitting your issue - thank you!

[] If you encounter any problems using the tool, please check if there has a new version to update(Run weex update [pluginname]@latest).
[] Check the FAQ, make sure there have not the same issue.

Your development environment

Check weex-toolkit verison (Run weex -v)
Detact what's wrong with your environment (Run weex doctor)
Which platform (Win/Mac/Ubuntu..)

The key error stack message.
Steps to reproduce the problem.(Maybe a dotwe link)

@donwilly2010 I have no idea about this issue, maybe you can put a issue to https://github.com/weexteam/vue-render-for-apache-weex project. If it can support this feature, I can just update the toolkit template to support it.


DELTA DATAPACK NOT WORKING ON MC 1.20.2

greetings, currently the whole datapack cannot work on the latest version of Minecraft being 1.20.2.
That's really all, i hope it gets fixed soon since i was working on a datapack.

I have the same issue and I'm not sure exactly why. I assume it may relate to an NBT key being renamed or Minecraft's subtick timings being changed.

If the dev of this mod is checking out this section, PLEASE FIX THIS SO IT CAN BE PLAYED ON 1.20.2

If the dev of this mod is checking out this section, PLEASE FIX THIS SO IT CAN BE PLAYED ON 1.20.2

It's been fixed on the no-rp branch. No need to lose your cool.


feat(tabs): add <rh-tabs>

What I did

Add <rh-tabs>
Closes #537

Todo

[x] Box variant
[x] Overflow styles
[x] Inset styles
[x] Base theme styles
[x] Tabs with icon styles
[x] add spec tests
[x] add changeset

Testing instructions

See deploy preview demo
Test in different browser resolutions (ie mobile)

Reviewer Notes
Ensure correct token usage, and please look for any accessibility issues.

Blocked by color context fixes in #594

@marionnegp Please take a look too.

@zeroedin, a couple design review issues:

We're missing the "disabled" fade on the left/right arrow when you've reached the ends
The hover state should turn the arrow blue on the non-disabled arrow.

The hover state wasn't in the original mockup/spec, but @marionnegp is going to update them.

@nikkimk, Corey, Marionne and I were discussing the accessibility of some of the tabbing/focusing behaviors, and wanted to get your expertise:

When using the arrow keys to toggle focus across the tab, they are automatically activated as you move side-to-side. Is this the expected behavior or should we be requiring the user to hit Enter or Spacebar to activate?
When tabbing out of the tabset, and then back into them, the focus arrives on the activated tab. Wondering if the focus should always arrive on the first tab in the set?

The latter interaction is tied to the understanding that you can navigate side-to-side without activating.
Anyway, these interactions may have been purposeful, which is fine. Just new and different from PF's and previous iterations of PFE. We'll go with whatever you advise.

Some advice from WAI-ARIA practices: developing a keyboard interface

Deciding When to Make Selection Automatically Follow Focus
In composite widgets where only one element may be selected, such as a tablist or single-select listbox, moving the focus may also cause the focused element to become the selected element. This is called having selection follow focus. Having selection follow focus is often beneficial to users, but in some circumstances, it is extremely detrimental to accessibility.
For example, in a tablist, the selected state is used to indicate which panel is displayed. So, when selection follows focus in a tablist, moving focus from one tab to another automatically changes which panel is displayed. If the content of panels is present in the DOM, then displaying a new panel is nearly instantaneous. A keyboard user who wishes to display the fourth of six tabs can do so with 3 quick presses of the right arrow. And, a screen reader user who perceives the labels on tabs by navigating through them may efficiently read through the complete list without any latency.
However, if displaying a new panel causes a network request and possibly a page refresh, the effect of having selection automatically focus can be devastating to the experience for keyboard and screen reader users. In this case, displaying the fourth tab or reading through the list becomes a tedious and time-consuming task as the user experiences significant latency with each movement of focus. Further, if displaying a new tab refreshes the page, then the user not only has to wait for the new page to load but also return focus to the tab list.
When selection does not follow focus, the user changes which element is selected by pressing the Enter or Space key.

Note: https://github.com/patternfly/patternfly-elements/issues/2323. /cc @marionnegp something I discovered when talking about some accessibility issues with @nikkimk.  Let me know if you can @coreyvickery have discussed what you want to do with the inset for RHDS.  By the updated design spec in the issue looks like maybe only 1 inset value?

Based on this it seems like we should default to active-follows-focus but provide a manual boolean attribute for users who generate content after the tab is activated.

@nikkimk and I discussed adding a manual activation option as well today.

When using the arrow keys to toggle focus across the tabs, they are automatically activated as you move side-to-side. Is this the expected behavior or should we be requiring the user to hit Enter or Spacebar to activate?

Either is acceptable behavior. (See Example of Tabs with Automatic Activation | APG | WAI | W3C and Example of Tabs with Manual Activation | APG | WAI | W3C)

When moving focus out of of the tabs, and then back into them, the focus arrives on the activated tab. Wondering if the focus should always arrive on the first tab in the set?

Focus should go back to the active tab. (See examples from links above.)
(Also can I just say that talking about Tab while also talking about a tabs component, is making my head spin.)

Styling isn't loading when I view tabs in Safari:

@marionnegp so this is an issue upstream as well.  The polyfill for element internals which is needed for safari is not getting loaded.  I believe I have to switch to using the internals controller for the Base classes which then automatically loads the polyfills.


Remove version: qBittorrent.qBittorrent version 4.6.0

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://sourceforge.net/projects/qbittorrent/files/qbittorrent-win32/qbittorrent-4.6.0/qbittorrent_4.6.0_lt20_qt6_x64_setup.exe/download
OK
(Automated message - build 923)

Close with reason: Package still available.;


Qt Creator 4.12 build

Qt Creator 4.12 release
https://www.qt.io/blog/qt-creator-4.12-released

Windows builds ready

Archlinux build ready

Linux build uploaded


Set item 'readOnly' based on another field value

Hi -
I have a field that I only want editable if another item value is false. Below is my attempt to make that work.
			fields: [{
				name: "userEmail",
				title: "Email",
				type: "text",
				width: 20,
				itemTemplate: function(value, item) {
					this.readOnly = item.notEditable;
                                        return value;
				}
			}]);

If I get false on item.notEditable the first time, all rows then set readOnly to false. I need each row individually set.
I can't seem to find much information on 'itemTemplate' and how it functions..
Thanks for your help!
Kent

I think you need editTemplate. Just return  readonly control if item is non-editable, for instance:
editTemplate: function(value, item) {
    var $result = jsGrid.fields.text.prototype.editTemplate.apply(this, argumets);
    $result.prop("readonly", item.notEditable);
    return $result;
}

Thank you! That worked.
Sorry, I was hoping you could help me once more :( I am trying to make a
cell visually not editable in certain cases (which would mean it goes
yellow in edit mode while other cells are editable). This is why I
initially don't give it a type. I was hoping I could assign the type only
if it should act like a normal text cell that is editable.
I am sure I am doing something dumb because I can't seem to find much info
on 'editTemplate'. Thanks again!
{
name: "userName",
title: "Name",
width: 175,
css: "gridTable",
align: "left",
editTemplate: function(value, item) {
if (item.Editable) {
var $result = jsGrid.fields.text.prototype.itemTemplate.apply(this,
arguments);
}
return $result;
}
On Wed, Oct 5, 2016 at 2:45 PM, Artem Tabalin<EMAIL_ADDRESS>wrote:

Closed #458 https://github.com/tabalinas/jsgrid/issues/458.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tabalinas/jsgrid/issues/458#event-813954631, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIvihxiIrQ4bAmNOgCB6wRPlpAeFUOsdks5qxBpzgaJpZM4KPUYA
.

Or perhaps there is a better / simpler way to approach this? All I am
trying to avoid is the field that the user should not edit to appear in
yellow (no white box) as this seems confusing to them. See screenshot .
"System" should be in all yellow.
[image: Inline image 1]
On Thu, Oct 6, 2016 at 3:43 PM, Kent Wyatt<EMAIL_ADDRESS>wrote:

Thank you! That worked.
Sorry, I was hoping you could help me once more :( I am trying to make a
cell visually not editable in certain cases (which would mean it goes
yellow in edit mode while other cells are editable). This is why I
initially don't give it a type. I was hoping I could assign the type only
if it should act like a normal text cell that is editable.
I am sure I am doing something dumb because I can't seem to find much info
on 'editTemplate'. Thanks again!
{
name: "userName",
title: "Name",
width: 175,
css: "gridTable",
align: "left",
editTemplate: function(value, item) {
if (item.Editable) {
var $result = jsGrid.fields.text.prototype.itemTemplate.apply(this,
arguments);
}
return $result;
}
On Wed, Oct 5, 2016 at 2:45 PM, Artem Tabalin<EMAIL_ADDRESS>wrote:

Closed #458 https://github.com/tabalinas/jsgrid/issues/458.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tabalinas/jsgrid/issues/458#event-813954631, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIvihxiIrQ4bAmNOgCB6wRPlpAeFUOsdks5qxBpzgaJpZM4KPUYA
.

Yes, you could do that.
I'm not sure if you want non editable items or particular field.
If you don't want to activate editing for some items, then redefine rowClick method, so you don't start editing if this is not editable item.
If you want to prevent editing of particular field, then instead of calling itemTemplate (if you don't do anything specific in it) just return value from editTemplate.
Hope this will help.


Lightbulb / quick fix is referencing the old filename after rename

VSCode Version: Code 1.14.1 (2648980a697a4c8fb5777dcfb2ab110cec8a2f58, 2017-07-13T19:08:57.197Z)
OS Version: Darwin x64 16.6.0
Extensions:

Extension
Author (truncated)
Version

vscode-docker
Pet
0.0.16

npm-intellisense
chr
1.3.0

vscode-eslint
dba
1.2.11

bower
don
0.0.3

tslint
eg2
0.16.0

vscode-npm-script
eg2
0.2.0

vscode-nuget-package-manager
jmr
1.1.4

Angular2
joh
2.4.0

csharp
ms-
1.11.0

PowerShell
ms-
1.4.1

vscode-gulp
tan
0.0.4

Steps to Reproduce:

Create/Open a c# project
Create/Open a file
e.g. test.cs
Write some new code using a type not included in the referenced usings
e.g. (IEnumerable is an unknown type because the System.Collections.Generic namespace is not included in the using statements):

namespace MyApp
{
    public class Test
    {
        public IEnumerable<string> GetStrings()
        {
            return null;
        }
    }
}

Rename the file, only changing a character casing
e.g.: test.cs to Test.cs
Use the lightbulb or the quick fix shortcut
Select 'using ' or the '' from the menu.
VS Code will create a new file, using the old filename.
e.g.: A new file 'test.cs' will be created where the selected fix has been applied instead of fixing the issue in the renamed file.

Thanks for the report! I suspect (though I'm not certain) that this is due to the same underlying issue as https://github.com/OmniSharp/omnisharp-vscode/issues/785.

Maybe worth mentioning:
When renaming more than just the casing, the issue does not occur.
Op 18 jul. 2017 om 16:35 heeft Dustin Campbell <notifications<EMAIL_ADDRESS>het volgende geschreven:
Thanks for the report! I suspect (though I'm not certain) that this is due to the same underlying issue as #785https://github.com/OmniSharp/omnisharp-vscode/issues/785.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/OmniSharp/omnisharp-vscode/issues/1644#issuecomment-316083660, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AUJOccsZRX-yc8mHdyN4GjO_M_NNShffks5sPMKQgaJpZM4ObVof.

Cannot reproduce with the current release.


Smart Content - change source - not working anymore

When trying to change the data source of a smart content in the backend, the list is empty and can't be changed. Seems like it doesn't even send a network request.
I think this bug exists since RC1 or RC2.

@thomasduenser which node do you have selected? could it be that its the "root" node of a webspace?

@thomasduenser ok now i can reproduce it with all pages!


[BUG] OneTable - Build is failing from morning

ISSUES will not receive priority that do not follow this template or cannot be easily reproduced or diagnosed
Describe the bug
From morning when we are building the one table application, build is getting failed.
node_modules/dynamodb-onetable/dist/mjs/Model.d.ts:122:54 - error TS2536: Type 'P' cannot be used to index type 'B'.
122 [P in keyof (A & B)]: P extends keyof A ? A[P] : B[P]

Found 1 error.

**To Reproduce**

Steps to reproduce the behavior:

1. map the latest version in package.json
2. Do $ npm run build

Check that:

**Screenshots**
![image](https://user-images.githubusercontent.com/31682699/143426424-84eb8bee-e838-4637-b138-85e1f7532bbe.png)

**Environment (please complete the following information):**
 - OS - Linux
 - Node Version - 16.9.1
 - OneTable Version - 2.1.3
 - TypeScript Version - 4.5.2
 - Any other relevant environment information

**Additional context**
Add any other context about the problem here.

That is not enough to reproduce. Need your package.json and tsconfig.json or other files.
Please provide a reproducible test case that we can replicate. Builds work here for us, we need you to provide the details for us to reproduce. Otherwise, we can't help you.

my-files.zip

Attached my package.json & tsconfig.json files here.. There is no test case required here.. Just run the build.. it's enough.

Actually it is not enough. Just run the build does nothing as there is nothing to compile. TSC won't do anything without something to compile. You didn't provide a test program (debug.ts) to compile, so TSC does nothing.
We've spent a couple of hours and managed to recreate your scenario -- but this will be the last time. The issues you open, while real, are consistently missing essential pieces (package.json, tsconfig.json, debug.ts etc.) and we go back and forth gathering the essential information that should be provided in the first place according to the issue template.  This is frustrating and counterproductive.
We'll post the fix tomorrow.

What debug.ts file needs to share here? We've not changed any configuration recently.. The project who build successfully is not getting build today.. For running a build command, what is the need of debug.js ??

Fix is committed.

Thanks but this is not the right way to treat us.. This is frustrating and counterproductive.

If you can verify the committed change works for you, we will push the NPM module. Thanks.

The change is:
diff --git a/src/Model.d.ts b/src/Model.d.ts
index 2852341..022adf3 100644
--- a/src/Model.d.ts
+++ b/src/Model.d.ts
@@ -118,12 +118,15 @@ export type Optional<T extends OneTypedModel> = {
 /*
     Merge two types
 */
-type Merge<A, B> = {
-    [P in keyof (A & B)]: P extends keyof A ? A[P] : B[P]
+type Merge<A extends any, B extends any> = {
+    [P in keyof (A & B)]: P extends keyof A ? A[P] : (P extends keyof B ? B[P] : never)
 };


Try replacing use_awaitable with deferred for boost .180 in the TCP server

Klemens has suggested replacing use_awaitable with deferred in boost 1.80 to improve performance in the TCP echo server and the RESP3 echo server. If there are any improvements the graphs should be also updated. Some background information

Any coroutine always allocates a frame, but that doesn't mean an async_op does. I.e. if you async_foo(use_awaitable), that'll return an awaitable that has a frame but, in boost 1.80 you can directly await async ops, e.g.: co_await async_foo(asio::deferred); then it doesn't need to allocate anything

I couldn't observe any measurable improvement in performance.


Use typescript and include type definitions in output package

Thanks for your PR.
I see more than 1000 changes.
I'll try to review it.
I like the change from gulp to vite.
I can't say the same from javascript to typescript.

No problem. The changes from js to ts were minor… it was just a way to provide the declarations and at the same time benefit of build-time type safety… but a separate .d.ts file would also provide the declarations.
Let me know what you prefer and I can make changes to the PR.

I think a separate file would be better. Since it is a small library and a single file.
I am glad to know that the library is used by other people.
Jero

Any update ?


Dependencies at build time

Let’s add a make file to setup all dependencies
then calls to package.json will work first time

Dev container does the same thing.
So coukd just have the makefile call into that too so devs can either run with or without docker.

Hey @gedw99, I didn't understand it properly. can you please elaborate, or you can create PR to contribute to the projects. thanks

Will do a PR... you can see if its useful or not


Add status indicator

There's no way to know whether DND is enabled or disabled.
This change would show an alert to indicate what the status is.
Note: there is a feature/bug in libnotify that prevents the timeout flag from working on Ubuntu, so the timeout of this alert can't be customized https://askubuntu.com/questions/110969/notify-send-ignores-timeout

Very nice, thanks again. Design decision/bug/feature, all pretty funny haha.


Correct iD.Way test to use Way() not Entity()

Whilst going through the tests I noticed that the core/way.js test for #copy is using Entity() for some reason rather than Way(). I'm pretty sure this should be Way().

Yes you are right.. Thank you!


Getting build errors in Image.h related to vector definition in default_init_allocator.h

I'm seeing the following build error after executing this build command in macOS on both the HEAD and v1.0.2 tag release:
./gradlew build -PskipArm
/Users/rich/github/cscore/src/Image.h:35:9: error: no matching constructor for initialization of 'std::vector' (aka 'vector')
: m_data{capacity, default_init_allocator{}} {
^     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/vector:505:5: note: candidate constructor not viable: no known conversion from 'default_init_allocator' (aka 'default_init_allocator') to 'const value_type' (aka 'const unsigned char') for 2nd argument
vector(size_type __n, const_reference __x); ...
I see that in the included file default_init_allocator.h some problem related to vectors looks to have been solved using the included StackOverflow discussion linked in the comments of the source code:
// From: http://stackoverflow.com/questions/21028299/is-this-behavior-of-vectorresizesize-type-n-under-c11-and-boost-container
// Credits: Casey and Howard Hinnant
Is the error that I'm seeing related to this solution not working?

The source code line triggering the build error is line 35 of Image.h:
explicit Image(std::size_t capacity)
: m_data{capacity, default_init_allocator{}} {
m_data.resize(0);
}

What compiler are you using?  While this approach optimizes performance (important on embedded systems), it's almost certainly not necessary for desktops.  There's a workaround a few lines above for MSVC (which has a similar issue compiling this code) using #ifdef _WIN32 but it could easily be more broadly applied based on the compiler or compiler version in use.

I'm using XCode in the latest macOS. It doesn't look like this code has been tested for building on macOS - I'll make some changes and do a pull request. It should be able to build and run on a desktop just as it does on an embedded system, right?

The python package robotpy-cscore compiles and runs on OSX (but it uses its own build system), so you should be able to fix it to work without changing source code I suspect... though, I think my build system prefers C++14 if it finds support for that.

I am having the same issue. Has a fix been created yet?

A fix is in the works.

Running ./gradlew build -PskipAthena with the latest build seems to fix the issue for me.

This has been fixed; the code that caused an issue on Mac is now conditionally compiled so it is used only on Linux.


Make docstrings more consistent in sway-lib-std

Some docstrings start with caps, other don't. Some code snippets are wrapped in backticks while others are not. There are also plenty of typeos.

I'd like to take this one on!


Upgrade py-spy and bump gProfiler to 1.42.0

Backporting the bss fix from upstream py-spy
This fixes py-spy for python 3.12 conda builds, and other clang based builds

Flaky failure.


Fakro AMZ Z-wave losing state after 8.18.1

Checklist

[X]  I am not using Home Assistant. Or: a developer has told me to come here.
[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog and my problem is not mentioned there.

Deploy method
Docker
Z-Wave JS UI version
8.25.0.c77db28
ZwaveJS version
11.14.0
Describe the bug
My Fakro AMZ screen isn't holding the last state anymore.
Latest working version z-wave-js-ui 8.18.1
After the state changed (open or close) the Current value of Multilevel Switch v3 holding the first 5 seconds the correct state (0 or 99) and then changes to null.
During opening or closing (around 16 seconds) the device reports null, but doesn't come back alive anymore.
When opened or closed and I push the refresh button for Multilevel Switch v3, the state returns and holds.
node_2.json.txt
config_entry-zwave_js-934e791c8aaee21714c1182d8f46635b.json.txt
To Reproduce
Open or close Fakro AMZ screen. Current value returns null after 5 seconds.
During opening or closing (around 16 seconds) the device keeps reporting null. Pushing the refresh button withing this time period is returning null.
Expected behavior
Current value shouldn't update when opening or closing to prevent returning null when device is busy.
Additional context
I use it with Home Assistant to check if the screen is open or close, so any other automation can trigger. Now it's reporting Unknown after 5 seconds and doesn't come back alive anymore. This is related to the Current value of Multilevel Switch v3.
After opening/closing

After manual refresh

/cc @AlCalzone

Please make a driver log, loglevel debug and attach it here as a file (drag & drop into the text field).


Observable API

Request for Node.js Position on an Emerging Specification

Specification title: Observable API
Specification or proposal URL (if available): https://wicg.github.io/observable/
Explainer URL (if available): https://github.com/WICG/observable/blob/master/README.md
Proposal author(s) (@-mention GitHub accounts): @domfarolino, @benlesh
Node.js collaborators or ecosystem members who can provide input (optional): ?

Notes
The Observable API is a primitive with long history, providing declarative ergonomics for streams of async events. At an extremely high level, they are "Promises for multiple events, but with no built-in async scheduling". The Observable API is a long-awaited and highly-desired feature on the web platform.
The reason we're coming to Node.js (and WinterCG more broadly) is because these environments implement similar DOM APIs that integrate strongly with Observables, such as EventTarget and AbortController/AbortSignal. This is a natural primitive to sit alongside those ones, hence the outreach we're performing here. Please let me know if you have any questions, and see https://github.com/WICG/observable/issues/93 for a list of all standards positions issues that we've filed for the Observable API.

I am personally +1 and in favor of doing this and adding this platform for compatibility and ease of use as well as integrating it into Node.js APIs where appropriate.

@nodejs/web-standards @nodejs/wintercg @nodejs/streams (since it's a push-stream primitive and Robert spoke to me about this a bunch) WDYT?

Heyo 👋 let me glance over the docs whenever I have some time, this sounds something I'm personally a huge fan of so +1 (or at least based on the abstract)
But since Im slow/OOO it might take some time for me to go over all of this, so please do not hesitate to proceed without me, but def +1 🫶

We use the rxjs Observables extensively and I believe it's an important library. Lack of back-pressure is unfortunate. Overlap with node streams is unfortunate.
TBH: even if it was part of the standard we would still use RxJS. I'm unsure whether or not it's part of the standard makes much of a differences for the backend. I'm +0 in regards to whether Observables should become a API standard.

@ronag I think a big point is interoperability - once all our platforms expose the observable proposal it's possible to write universal code using observables and integrate it into APIs where it makes sense

I think push interfaces should be avoided. However, this is more or less as risky for our users to our events.on(emitter, event) utility that will buffer all events.
I’m neutral to the proposal. I can only see benefits in compatibility with the frontend ecosystem.

@ronag I think a big point is interoperability - once all our platforms expose the observable proposal it's possible to write universal code using observables and integrate it into APIs where it makes sense

Doesn’t rxjs work on all platforms? Interoperability in what way?

@ronag I think a big point is interoperability - once all our platforms expose the observable proposal it's possible to write universal code using observables and integrate it into APIs where it makes sense

Doesn’t rxjs work on all platforms? Interoperability in what way?

Interoperability as a standard specification bundled within the engines and runtimes?

We use the rxjs Observables extensively and I believe it's an important library. Lack of back-pressure is unfortunate.
TBH: even if it was part of the standard we would still use RxJS.

Can you clarify what the reason for this (last part) would be? Just to clarify, our proposal does not mean to obsolete RxJS entirely. That library would likely evolve into one of subtler operators that we would not immediately push into the web platform, but its custom Observable implementation would almost certainly get removed in favor of the platform's, once widely available. But I'm curious why your first take is to keep using RxJS in light of a standardized Observable protocol.

Interoperability as a standard specification bundled within the engines and runtimes?

What's the practical difference for the user?

We use the rxjs Observables extensively and I believe it's an important library. Lack of back-pressure is unfortunate.

TBH: even if it was part of the standard we would still use RxJS.

Can you clarify what the reason for this (last part) would be? Just to clarify, our proposal does not mean to obsolete RxJS entirely. That library would likely evolve into one of subtler operators that we would not immediately push into the web platform, but its custom Observable implementation would almost certainly get removed in favor of the platform's, once widely available. But I'm curious why your first take is to keep using RxJS in light of a standardized Observable protocol.

If there was feature parity over time there would be no reason. However, I would expect RxJS to evolve faster than a standardized API.

Interoperability as a standard specification bundled within the engines and runtimes?

What's the practical difference for the user?

It should be a transparent adoption somewhat IMO. I do see advantages for the user. Regardless. Genuinely speaking, a standard API removes the need of an NPM package, which cannot run on every single JavaScript environment.
Now, RxJs could definitely extend upon the standard API.
I don't see harm on implementing it, why so much negativity? 😅

Now, RxJs could definitely extend upon the standard API.

That's exactly the plan. I'll let @benlesh comment though, as he's the maintainer of RxJS and has been helping out a lot with the Observable API proposal.

However, I would expect RxJS to evolve faster than a standardized API.

True with every JS library that inspires platform primitives! We should probably not stop standardizing features though.

@ronag hey the idea for this as a standard means several things:

Platform APIs (like Node's own EventEmitter and DOM's EventTarget could support conversion/interoperability cleanly.
Similarly libraries get a platform supported way to consume/produce observables where it makes sense.

Also:

I don't see harm on implementing it, why so much negativity? 😅

Because the streams people are the ones most likely to end up having to maintain this as well as consider how this interoperates with other flows. We have concerns around being careful about exposing APIs with observables where backpressure is needed but probably(?) want to support them in stuff like file watching - it's tricky and not obvious and adding another async primitive is certainly not something to be done lightly.
That said, I think in this case it's common/good enough to consider it and I think the benefits are tangible. 3

I'm fairly neutral on the API at the moment. I'd like to see more implementation and real world use. I'm certainly not against an implementation directly in Node.js. I'm +1 to the project publishing a position on the spec.

From the perspective that we can add observable API to other API interface I'm more positive to this.

Given the responses here, the next step would be for someone to open a PR drafting an initial take on the position the project wants to take here.

Given the responses here, the next step would be for someone to open a PR drafting an initial take on the position the project wants to take here.

I believe a PR is already open here https://github.com/nodejs/node/pull/51065

@ovflowd I think James means in this repo (i.e. the project to discuss what it thinks about the standard vs. directly adopting it) though this repo and process is new and I'm unclear about the process myself.

Yep, per the process outlined https://github.com/nodejs/standards-positions#process we need a separate document added via PR here that outlines our position. It can be super simple and straightforward. Any discussion of whether we may or may not actually implement the API should happen in that PR and that document.


custom event only works after opponent hits one note

Describe your problem here.
the event doesn't do anything until the opponent hits a single note, here's the code
local originalZoom

function onCreatePost()
    originalZoom = getProperty('defaultCamZoom')
end

function onEvent(name, value1)
    if name == 'Camera Set Zoom' then
	if value1 ~= nil and value1 ~= '' then
	    setProperty('defaultCamZoom', value1)
	else
	    setProperty('defaultCamZoom', WhatsUpOriginal)
	end
    end
end

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

add
function onCreate()
        setProperty('camZooming', true)
end

ok


[pulsar-broker] support update partition for global topic

Motivation
We are having many customer ask to update partition on global topic which is not supported. In that case, admin has to perform manual steps to create subscriptions in all clusters and update partitions for that global topic. So, broker should support updating partitions on global topic.
Modification
Update-partition API support global topic.

rerun java8 tests
rerun integration tests

rerun java8 tests

rerun integration tests


Swannobi edits

woops, also added the cart :P
@swannobi wasn't sure if I was able to fix #1#pullrequestreview-67402342
Thanks for all your help! that reads a lot better now.

merging cause tight schedule :P


access prototype from view?

I would like to add prototype-s to a data attribute in all collection view.
Is this possible to access prototype string in views/collection.php?

Adding it directly to the views/collection.php is not possible with default collection type. You can create custom collection field type, extend default one and pass the prototype in view. Something like this:

class CustomCollectionType extends CollectionType {

    public function render(array $options = [], $showLabel = true, $showField = true, $showError = true)
    {
        $options['prototype'] = $this->prototype;

        return parent::render($options, $showLabel, $showField, $showError);
    }

Thank you. I will do this way.


Section Headers Card not consistent with editor

The more I try to use Ghost with its default theme Casper, the more I realize half of the features advertised on the theme side are not even finished.
This is Casper's Section Header Cards.
Editor version:

Live version:

Please keep in mind I'm using the latest Casper version, fresh installation, no code injected or anything. It should work, right? Maybe I am missing something here?
Casper version 4.7
Ghost Version: 4.38.0

Colors are not working (only black works)
Background images are working fine
Buttons are not working (they don't show up with the right class, I only see the link, but not a button)
Sub-text is not working properly (no alignment present)

Closing for the same reason as https://github.com/TryGhost/Casper/issues/845.


not work signature identifier for traces when use forge test

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[ ] Foundryup

What version of Foundry are you on?
forge 0.2.0 (935c113 2022-06-22T00:17:48.239446Z)
What command(s) is the bug in?
forge test
Operating System
macOS (Intel)
Describe the bug
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.12;

import {IERC20} from<EMAIL_ADDRESS>import {DSTest} from "ds-test/test.sol";

contract Contract is DSTest {
    address owner;
    modifier OnlyOwner() {
        require(msg.sender == owner);
        _;
    }
    receive() external payable {}
    fallback() external payable {}
    constructor() payable {
        owner = msg.sender;
    }
    function test() public {
        IERC20(0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2).balanceOf(
            address(this)
        );
    }
}

signature:0x70a08231 -> balanceOf(address)
when use forge script contracts/Contract.sol -vvvvv --tc Contract --sig "test()" :

but use forge test --match-contract Contract --fork-url $MAINNET_RPC --fork-block-number 149724xx -vvvv:

cli/src/cmd/forge/test.rs add this code can work:
decoder.add_signature_identifier(SignaturesIdentifier::new(
	Config::foundry_cache_dir(),
)?);

I added only to cast run and forge script, since I don't think it fits forge test. One would only turn on tracing when trying to figure out when a test is failing no? More than that, one should just use forge script no? Also, if you have a big test suit it could slow it down depending on how many requests we make.
But I don't have a very strong opinion about the matter.

Fixed in the latest nightly


Is parsing affected by module name?

I have a file with a modules  HOLIB-SYNTAX. If I change the module name to HOLI-SYNTAX, parsing changes. I have defined order of precedence in the grammar, but it appears to be affected by the module name.
It is a bit difficult to provide a minimal example, since I'm not sure what causes it.
I'm not sure if this is related, but parsing also appears to change if I swap platform. On Ubuntu 18.10, I have consistently gotten the same terms back on different machine. But when booting Ubuntu 16.04, the terms parsed change. I'm using the latest version of Java on each platform.

If the main module is named HOLIB, K first looks for HOLIB-SYNTAX to use for parsing. Otherwise if falls back to the HOLIB module.

Sorry, I wasn't clear. In my HOLIB file, I have a module HOLIB and HOLIB-SYNTAX. I tested this out in the following ways:

change filename to holi.k, module from HOLIB to HOLI and HOLIB-SYNTAX to HOLI-SYNTAX.
only change HOLIB-SYNTAX to HOLI, and inside HOLIB, import HOLI-SYNTAX.

The module HOLIB wouldn't have any syntax definitions inside. Just the rewrite rules. Both changes resulted in the same effect. The HOLI versions of the syntax consistently parsed one way, while HOLIB syntax parsed another way. The grammar productions remained the same. I haven't been able to come up with a minimal example, so it might be due to a bug in my semantics.

Can you try deleting the -kompiled directory and recompiling and seeing if that resolves the issue? if it does, it is likely an issue with our parse cache.

Please re-open if this is still an issue, with exact reproduction steps.


Theming: Tabs

Subject
Tabs
Description
Create a basic theming documentation for the Tabs component that showcases how you can style it.
Theming file: Tabs theming file
Template Reference
For single part components, feel free to use the Button component theming doc as a template reference: Button theming.
For multipart components, feel free to use the Input component theming doc as a template reference: Input theming.

Hi @nikolovlazar, I can work on this one next.


Add 	"Service Mappings" to "Ensure Service User" feature of "Ensure Authorizable"

Add "Service Mappings" to the ensure service user configuration.  This would allow you to ensure existence of your org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl factory configuration for the user.
Feature doc page:
https://adobe-consulting-services.github.io/acs-aem-commons/features/ensure-service-users/index.html
This would simplify managing the service user so that everything can be done in one place.
For example:
Ensure Immediately: X
Operation: Add
Principal Name: test/test-service
ACEs: ["type=allow;privileges=jcr:all;path=/content"]
Service Mappings: ["com.acs-commons.test.core=test-service"]

Then if Service Mappings are defined, it would ensure that a org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl exists that contains that mapping.  If it doesn't exist then it would create one.

Wouldn't that mean that we should create OSGI configurations on the fly during runtime? I would rather just add a check for the existence of such a configuration. The best way would be to check on build-time that if a service user is being used that a matching Service Mapping is present as well.

@joerghoh what is wrong with creating an OSGi config on the fly?  That's what the OSGi ConfigurationAdmin API is there for:
https://osgi.org/javadoc/r4v42/org/osgi/service/cm/ConfigurationAdmin.html#createFactoryConfiguration(java.lang.String)
Could check for existence of a matching mapping, if it doesn't exist then create it.


Building on Raspberry Pi

I am trying to build this repo on my Raspberry Pi, but am having some issues.
Cloning the repo worked fine, and even building it with './gradlew :native:build' worked fine. The problem is that despite gradle saying the build succeeded, I cannot find the libntcore.a library anywhere on the RPi.
Running './gradlew build' does not work (throwing an error with the g++ -m32 arg) but I don't think it worked on a Mac either.
Any advice is much appreciated,
Henry Loh

The right way to build on a pi is to run
./gradlew :arm:ntcore:build -PcompilerPrefix=
(yes there is nothing after the equals statement.
After this, the builds will be in arm/ntcore/build/libs.
However we publish pi artifacts to our maven repo which are already built for the pi. Use the arm-raspbian classifier. Also note you will need wpiutil if you want to link to the static archives.

Thanks for getting back to me so quickly, I ran what you suggested and I imagine it would work but the RPi froze for the last 20ish minutes.
I'm planning on unplugging the RPi and then getting the builds from the maven repo you mentioned. Does that sound right?

It probably didn't freeze, it's probably just going to take over an hour to compile natively on a pi. But yeah the maven artifacts are probably an easier solution.

Yes! It works! Thank you so much for your help, I really appreciate it.


eating items isn't working

So I've been using the mod Mo's Grounded Origins on my Minecraft server and specifically with the Moth origin, which uses apugli:edible_item in order to make it so that paper, string, wool, leather, and books are edible. However, on my server, the eating animation/sound happens, but the items can't actually be consumed like they should be. The developer said that it works fine for them, so it's likely a mod compatibility issue, but I am not sure what could be causing it.
I've attached a list of all the mods on my server, the Apugli version is 1.6.2.
modlist.txt

Apparently on 1.18.2, the edible item power is broken

https://github.com/MerchantPug/apugli/issues/9
Do you happen to have Collective installed?

Yes, Collective (Fabric) 4.27 is installed on the server.

There's an incompatibility with that mod and this one.

ah, okay. thanks!

Duplicate of #9


flutter_test from sdk is incompatible with flame >=0.24.0

Hello, flutter_test from sdk is incompatible with flame >=0.24.0. Can you help me?
Because every version of flutter_test from sdk depends on xml 3.6.1 and tiled >=0.4.0 depends on xml ^4.2.0, flutter_test from sdk is incompatible with tiled >=0.4.0.

And because flame >=0.24.0 depends on tiled ^0.6.0, flutter_test from sdk is incompatible with flame >=0.24.0.

So, because simiapp depends on both flame ^0.24.0 and flutter_test any from sdk, version solving failed.
pub get failed (1; So, because flutter_app depends on both flame ^0.24.0 and flutter_test any from sdk, version solving failed.)

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.17.5, on Mac OS X 10.15.4 19E287, locale
    zh-Hans-CN)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
[✓] Android Studio (version 3.6)
[!] IntelliJ IDEA Community Edition (version 2020.1.1)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
[!] VS Code (version 1.42.1)
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (1 available)

! Doctor found issues in 2 categories.

Sorry. I delete flutter_test, it's done.

@wenxiangjiang from where did you delete it? is it something we need to fix on the package side?

Current Flutter's stable channel test library uses xml 3.x version, and this package uses 4.x. Making this incompatible with the Flutter 1.7.x flutter_test library, you have two alternatives here:

Move to the beta channel (my personal recomendation)
Remove the flutter_test library from your pubspec, and use this instead: https://pub.dev/packages/test

@luanpotter I just delete flutter_test from my pubspec.yaml.
@erickzanardo Thanks a lot.


Can't deploy react site to amplify

Before opening, please confirm:

[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
d1u96gye6vvuo9
Region
us-east-2
Environment name
dev
Amplify CLI Version
5.0.2
If applicable, what version of Node.js are you using?
v14.13.1
What operating system are you using?
Mac
Browser type?
Chrome
Describe the bug
An error occurred during the publish operation: User: arn:aws:sts::774999615831:assumed-role/us-east-2_0H7iDgUDV_Full-access/amplifyadmin is not authorized to perform: amplify:ListJobs on resource: arn:aws:amplify:us-east-2:774999615831:apps/d1u96gye6vvuo9/branches/dev/jobs/*
Expected behavior
Publish to Host
Reproduction steps
Run amplify publish
Additional information
No response

The error that is reported seems pretty clear, you need to update the IAM policies or roles associated with the user you're trying to push with. The user does not have authz to perform some Amplify functions.

Feel free to reopen if you have other question, thanks!


Purge sent messages from queue

If autoPurge = true, messages will be purged after a round of sending out messages.
Fixes Issue #33 (option to delete message from queue when sent)

Thanks @BBrunekreeft


Replace Mutex with RwLock in string interning code.

When calling into egg from multiple threads, the Mutex used for STRINGS can become a bottleneck. (In my use case, I have a few hundred expressions that I'd like egg to simplify, so I do that using multiple threads.) In that context, I observed that egg::util::intern was a significant fraction of total runtime and that more time was spent in it than in any of the rest of egg's code(!). Here is what perf on Linux reported:

(Note that is in the context of a larger application; just over half of total runtime is in egg but that 43% is with respect to total runtime.) Total runtime for my test is 4.04s user, 14.22s sys.
This PR replaces the Mutex is replaced with a reader-writer lock. perf reports roughly a 2x speedup:

which is also reflected in the total runtime for my system going to 9.26s user, 0.21s sys.

Great PR, I will accept after CI goes.
Out of curiosity, what were you doing that caused the interning to get called so frequently? My initial intention was that interning should only be called while setting things up.

Ahh, that totally makes sense. If you are crossing FFI using strings, then you don't have much of a choice to parse!


enhancement-#220: Different Cards under all posts are of different height .

Summary
This PR is for proper height of different cards under All post section .
Description
Before different cards showing different length but i added javascript to know whether the description of single line or two lines if description is of single lines so changes line-height from 1.25 rem to double 2.5rem .
Images
Before

After

Issue(s) Addressed
Closes  #220
Prerequisites

[ Yes] Have you followed all the [CONTRIBUTING GUIDELINES]

@Ayushmaanagarwal1211 Thank you for the update, but we don't want this much intelligence in the code, try to solve it by simple tailwind and your "After" picture has line-clamp-1, with line clam-1 event the existing code works without added intelligence code of figuring out height.
Take some time, see options in pure tailwind you'll get the answer, take it slow it is fine.
p.s: 2nd commit doesn't follow the guidelines and build is failing because of below reason ,so closing this PR

Hi @Ayushmaanagarwal1211, I also noticed this issue.
Can't give fixed height like h-48 do the job?
I checked it and it's looking good.


Show versions of Clippy and Rustfmt

Spawned from #184.

For anyone wanting to pick this up, here's some more information.
There's the rustfmt -V option to return its version, in a format very similar to rustc -V, for example 0.3.6-nightly (e0e3e22 2018-01-18). (I wasn't able to try with clippy at this point)
Adding support for this could be similar to how the playground gets the channels' rustc version.
For example, for the server-side backend, the stable version endpoint is here, and the code asking rustc for its version on a given channel, and parses the results into its components is here.
Client-side, there are different routes defining the previously mentioned endpoints. These are used in the performVersionsLoad function here, which is called when the app starts up, ultimately storing the resulting versions in the app state here.


FlyBase Controlled Vocabulary BioPortal pull URL fails with 404 error

I'm one of the developers maintaining the BioPortal application. We have an entry for the FlyBase Controlled Vocabulary that's configured to check the following URL nightly for new versions:
http://purl.obolibrary.org/obo/fbcv/dpo.owl
... which resolves to this URL:
https://raw.githubusercontent.com/FlyBase/flybase-controlled-vocabulary/master/dpo.owl
... which results in a 404 error.
I'm wondering if there's a new location for this particular ontology that we should be checking nightly? Thanks for any information you can provide.

Yeah dpo moved to its own repo, check obofoundry registry. This purl should work:
http://purl.obolibrary.org/obo/dpo.owl :) let us if that works for you! Thanks!

Hi @matentzn. Thanks for that information. I noticed that we have a separate entry in BioPortal under the acronym DPO:
http://bioportal.bioontology.org/ontologies/DPO
... that pulls from the URL you listed above (http://purl.obolibrary.org/obo/dpo.owl). If I understand correctly then, our entry under the acronym FB-CV is a duplicate with older metadata. Would it be acceptable to you if we removed it?

FBcv and DPO are distinct:
FBcv: http://purl.obolibrary.org/obo/fbcv.owl
DPO: http://purl.obolibrary.org/obo/dpo.owl
(FBcv subsumes dpo - but most outside users are likely interested in dpo only, so we release separately)

OK, thanks @dosumis. Then it seems like our FB-CV entry should be using the first URL you listed as the pull location to check nightly.


protection against malicious AVDLs with nil

Fill with empty objects rather than dumping the caller.

r? @mlsteele

LGTM


Update relevance-faq.md

Add 2 more FAQs concerning supported data types for Dataverse Search team (anikaduffus)

Closing, as this is a dup of PR 4592.


cask/audit: error if verified does not match, regardless of url

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?
[x] Have you successfully run brew man locally and committed any changes?

This PR changes brew audit --cask such that an error is raised if the verified parameter is present for a url but does not match. For example, this should give an audit error:
  url "https://shining.softorino.com/shine_uploads/waltr#{version.major}mac_#{version}.dmg",
      verified: "dl.devmate.com/com.softorino.waltr2/"

Review period will end on 2021-01-29 at 23:34:30 UTC.

Review period will end on 2021-01-29 at 23:34:30 UTC.

Review period will end on 2021-01-29 at 23:34:30 UTC.

Review period will end on 2021-01-29 at 23:34:30 UTC.

Review period ended.

Review period ended.


Using @RabbitListener and sending POJO Object

update example to use @RabbitListener and sending POJO Object

@letrthang Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@letrthang Thank you for signing the Contributor License Agreement!

We support only /initial and /complete in the guides.


Add ability to name specific Wiremock instances

It would be really useful to have the option to name a given Wiremock instance, so that error logs can become more descriptive.
For example:
public WireMockRule customerService = new WireMockRule(options().name("Customer Service");
which would result in this line in the logs:
2017-03-01 13:23:53.651 ERROR 6984 --- [qtp260084831-27] WireMock Customer Service                                : Request was not matched:

I have raised PR for the same.


Typescript compilation error after swizzling

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
After swizzling a component (eject + typescript), the project does not compile.
Reproducible demo
No response
Steps to reproduce

Create new typescript docusaurus npx create-docusaurus@latest my-website classic --typescript
cd .\my-website\
Swizzle component npm run swizzle @docusaurus/theme-classic DocSidebarItem/Link -- --typescript --eject
Compile npm run typecheck

Expected behavior
No errors
Actual behavior
src/theme/DocSidebarItem/Link/index.tsx:4:35 - error TS2307: Cannot find module '@docusaurus/theme-common/internal' or its corresponding type declarations.
import {isActiveSidebarItem} from '@docusaurus/theme-common/internal';
Your environment

Public source code:
Public site URL:
Docusaurus version used: 2.1.0
Environment name and version (e.g. Chrome 89, Node.js 16.4): node v16.14.0
Operating system and version (e.g. Ubuntu 20.04.2 LTS): Windows 10

Self-service

[ ] I'd be willing to fix this bug myself.

Hey,
It looks to me it is related to the package.json "exports" that we introduced recently.
Try this:
{
  "extends"<EMAIL_ADDRESS>  "compilerOptions": {
    "baseUrl": ".",
+  "moduleResolution": "Node16"
  }
}

See also: https://github.com/tsconfig/bases/pull/122

It seems like using Node16 for module resolution makes my Swizzle work but then causes some of my type imports to fail:
import type {
  Sidebars,
  SidebarItemDoc,
} from '@docusaurus/plugin-content-docs/src/sidebars/types';

We hit a similar issue when importing from @theme/Tabs in a custom page. There are no TS errors but the types of the props are not loaded for autocomplete (because they delegate to @docusaurus/theme-common/internal). Adding "moduleResolution": "Node16" to our tsconfig fixes it.


Addition of documentation for AList

URL: https://ilia-brykin.github.io/aloha/#/list
We have a new prop separatorHtml, and changed prop separator behavior.
The documentation is ready; the corresponding translations need to be supplemented or corrected.

A_LIST_GROUP_SEPARATOR_HTML_HEADER
A_LIST_GROUP_SEPARATOR_HTML_DESCRIPTION
A_LIST_SEPARATOR_PROP_DESCRIPTION
A_LIST_SEPARATOR_HTML_PROP_DESCRIPTION

If changes affect existing translations, please indicate this to the translators.

DE, EN, HR added
@ilia-brykin ill asign you and hafedh for rest

AR, FR, ES, IT done


cli: add demo functionality to Reana cli script

add cli command to run reana-demo-helloworld example easily
reana demo helloworld

Signed-off-by: Harri Hirvonsalo<EMAIL_ADDRESS>

For now, hardcoded to run only helloworld-workflow.
Doesn't follow the run-syntax described in reanahub/reana-demo-helloworld#2 as I feel that this is something we will have to discuss more before implementing it; what is the actual input of reana run (file? folder?) and how to submit the workflow to workflow-controller, etc.


health_probes: Adding unit tests

Adding a test for health probes.
I am not certain this test is correct -- it is merely made to match the current state of the health probe creator and pass.
We need to continue to build the tests out with various scenarios.

@akshaysngupta Could you PTAL


How to Compile this Library?

i didnt find x.y.x values for     compile 'io.fotoapparat.fotoapparat:library:x.y.z'
please help.

Use -SNAPSHOT as a version. Like that:
compile 'io.fotoapparat.fotoapparat:library:-SNAPSHOT'

ok thanks dear


Remove learning python the hardway

Hey, since LPTHW warns on using python 3, the python reddit removed it from the sidebar (https://www.reddit.com/r/Python/comments/40s6dm/meta_can_we_take_learn_python_the_hard_way_off/) maybe we should also remove it from the list until a python 3 version is available.
We should also not that the jupyter notebook server will only support python 3 in the future (http://blog.jupyter.org/2016/07/08/ipython-5-0-released/)

We'll support 2.7 in the meantime. Transition periods suffer some ambiguity and porting issues, but we'll maintain 2.7 resources until industry has transitioned over wholesale. Thanks for commenting!


[DEV] BSS must enforce JWT-based authentication and authorization

For the Supercomputer Institute, we have decided to use JWTs for authentication and authorization at the microservice level as well as ensuring that each client request presents a valid token through validation at the API Gateway.
BSS doesn't currently evaluate a JWT at all.  We have already made these changes to SMD which should establish a pattern to follow.
In order to close this ticket, BSS must:

[ ] Support a runtime flag to enable JWT validation on protected routes and reject unauthorized requests.
[ ] Update BSS to use chi as the microservice router and support the same jwt middleware as recently added to smd
[ ] Update calls from BSS to SMD so that any JWT presented as a bearer token to BSS will be passed along without changes to SMD

This should all be covered by PRs #17, #19, and #23, except it also include the case where BSS needs to make a request to a protected SMD route when the user is interacting with BSS's public route.

The above PRs are merged, so I think we can consider this done.

BSS doesn't currently evaluate a JWT at all. We have already made these changes to SMD which should establish a pattern to follow.

BSS now supports both accepting a JWT to authorize against protected endpoints as well as becoming authorized with protected SMD endpoints via client credentials grant when a user requests a boot script.

Update calls from BSS to SMD so that any JWT presented as a bearer token to BSS will be passed along without changes to SMD

BSS only needs to present a token to SMD when the /boot/v1/bootscript (unprotected) endpoint is requested, since BSS needs to request protected SMD endpoints. Since the bootscript endpoint is unprotected, BSS needs its own token, which it gets via a client credentials grant from the OIDC/Oauth2 provider. This has been implemented and tests are passing, so this can be considered complete.


MacDirtyCow vulnerable iOS versions support

Hi. Can you please make CLEO work for devices that are vulnerable to the exploit? Filza works with it
Also TrollStore support would be cool too

CLEO requires a kernel patch in order to be able to run (as it hooks machine code instead of just Objective-C), so I'm not sure how that would affect compatibility.
We've had a lot of discussion of a non-jailbroken version of CLEO over on Discord but as far as I can tell it isn't possible, unless MacDirtyCow allows hooking machine code.

I'm sorry, but I'm just a language model and do not have the capability to make CLEO work for devices that are vulnerable to the exploit or add support for TrollStore. CLEO and TrollStore are third-party software, so it is up to their developers to add support for specific devices or platforms. You may want to reach out to the developers of CLEO or TrollStore and request the support you need.

yeah I saw the messages in Discord but thanks for confirming. it's a shame


Leaks on terminated app

💬 Questions and Help
I am opening this issue again because i didnt get any response from previous one.
I wanted to try to listen to locations even after i terminate app so i added
            notificationText:
            "Example app will continue to receive your location even when you aren't using it",
            notificationTitle: "Running in Background",
            enableWakeLock: true,
          )

to settings. But when i terminate the app i get this leak. If i remove this foregroundNotificationConfig everything works as it should, so if i terminate app there is no leaks.
E/ActivityThread(13871): Activity com.enviroapp.enviroapp.MainActivity has leaked ServiceConnection com.baseflow.geolocator.GeolocatorPlugin$1@576aec9 that was originally bound here
E/ActivityThread(13871): android.app.ServiceConnectionLeaked: Activity com.enviroapp.enviroapp.MainActivity has leaked ServiceConnection com.baseflow.geolocator.GeolocatorPlugin$1@576aec9 that was originally bound here
E/ActivityThread(13871): 	at android.app.LoadedApk$ServiceDispatcher.<init>(LoadedApk.java:1811)
E/ActivityThread(13871): 	at android.app.LoadedApk.getServiceDispatcherCommon(LoadedApk.java:1683)
E/ActivityThread(13871): 	at android.app.LoadedApk.getServiceDispatcher(LoadedApk.java:1662)
E/ActivityThread(13871): 	at android.app.ContextImpl.bindServiceCommon(ContextImpl.java:1819)
E/ActivityThread(13871): 	at android.app.ContextImpl.bindService(ContextImpl.java:1749)
E/ActivityThread(13871): 	at android.content.ContextWrapper.bindService(ContextWrapper.java:756)
E/ActivityThread(13871): 	at com.baseflow.geolocator.GeolocatorPlugin.onAttachedToActivity(GeolocatorPlugin.java:126)
E/ActivityThread(13871): 	at io.flutter.embedding.engine.FlutterEngineConnectionRegistry.add(FlutterEngineConnectionRegistry.java:155)
E/ActivityThread(13871): 	at io.flutter.plugins.GeneratedPluginRegistrant.registerWith(GeneratedPluginRegistrant.java:29)
E/ActivityThread(13871): 	at java.lang.reflect.Method.invoke(Native Method)
E/ActivityThread(13871): 	at io.flutter.embedding.engine.plugins.util.GeneratedPluginRegister.registerGeneratedPlugins(GeneratedPluginRegister.java:80)
E/ActivityThread(13871): 	at io.flutter.embedding.android.FlutterActivity.configureFlutterEngine(FlutterActivity.java:1004)
E/ActivityThread(13871): 	at io.flutter.embedding.android.FlutterActivityAndFragmentDelegate.onAttach(FlutterActivityAndFragmentDelegate.java:191)
E/ActivityThread(13871): 	at io.flutter.embedding.android.FlutterActivity.onCreate(FlutterActivity.java:459)
E/ActivityThread(13871): 	at android.app.Activity.performCreate(Activity.java:8000)
E/ActivityThread(13871): 	at android.app.Activity.performCreate(Activity.java:7984)
E/ActivityThread(13871): 	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1309)
E/ActivityThread(13871): 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3422)
E/ActivityThread(13871): 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3601)
E/ActivityThread(13871): 	at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:85)
E/ActivityThread(13871): 	at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
E/ActivityThread(13871): 	at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
E/ActivityThread(13871): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2066)
E/ActivityThread(13871): 	at android.os.Handler.dispatchMessage(Handler.java:106)
E/ActivityThread(13871): 	at android.os.Looper.loop(Looper.java:223)
E/ActivityThread(13871): 	at android.app.ActivityThread.main(ActivityThread.java:7656)
E/ActivityThread(13871): 	at java.lang.reflect.Method.invoke(Native Method)
E/ActivityThread(13871): 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
E/ActivityThread(13871): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
D/FlutterGeolocator(13871): Binding to location service.
D/FlutterGeolocator(13871): Destroying location service.
D/FlutterGeolocator(13871): Stop service in foreground.

Expected behavior
Stop listeners on terminated app.
Reproduction steps
I didnt find anything in issues..
Configuration
Same as in example
Version: ^8.2.0
Platform:

[x] :robot: Android

Hi @bujdy,
Could you link the original question / issue that you haven't got any response to?
@Wackymax do you mind having a look at this and maybe provide us with some insights? Looks like the android logic forgets to deregister a service connection, however I am not really familiar with this material.

Looks like we haven't been able to triage it yet. I will close this issue as duplicate, please try not to pollute by creating duplicate issues.


Update run.sh

Clean-up results.jtl before running new test. More details in #1.

Thanks a lot!

No prob! Maybe one day I will contribute AWS support

That would be incredibly awesome. Looking forward to it.


Handle ChatGPT input limit

ChatGPT 3.5 turbo seems to have an input limit for the API of 4,096 tokens. In practice I hit that limit quickly and then you receive a 400 Client Error. For example, in the example below I hit that after just one request (had to rename the file to .txt to allow github to upload, place in /tmp/shell_gpt/chat_cach without file extension to reproduce). By going into the cache and removing some of the cached messages, you can clear up the error to continue the session. A sensible way of handling this would be to truncate back messages while preserving the initial prompt I believe.
test.txt

I just realized, I vaguely remember reading somewhere ChatGPT handles this on their website by using a separate neural network to summarize the conversation so far. Python has tools like TextBox, https://github.com/RUCAIBox/TextBox , that could do something like that on a slightly more primitive scale. Assuming there is a tool there that respects word limits. To balance responsiveness and utility, workflow could be, make api call, run neural network for summary in the background, when the user runs the next api call use new summary if its ready or something truncated if its not ready yet.

You'd have to implement OpenAI's tiktoken token calculator. You can play around the the demo version on their site. Honestly the simplest solution is just to do what OpenAI did early on, and cull early messages as the limit approaches - ChatGPT 'forgets' the start of the conversation), worry about a more complex summarizing implementation later on.

sgpt --show-chat db
user: ###
...
Prompt: create postgres docker container with username=test_user, password=test_password, database=todo
###
assistant: docker run --name postgres -e POSTGRES_USER=test_user -e POSTGRES_PASSWORD=test_password -e POSTGRES_DB=todo -p 5432:5432 -d postgres:latest
user: name container as todo_db
assistant: docker run --name todo_db -e POSTGRES_USER=test_user -e POSTGRES_PASSWORD=test_password -e POSTGRES_DB=todo -p 5432:5432 -d postgres:latest
user: create a table in created container in "todo" database task: str, done: bool
assistant: docker exec -it todo_db psql -U test_user -c "CREATE TABLE todo (task TEXT, done BOOLEAN);" todo
user: insert random record to created table
assistant: docker exec -it todo_db psql -U test_user -c "INSERT INTO todo (task, done) VALUES ('Complete task 1', false);" todo
user: task = build a simple todo app
assistant: docker exec -it todo_db psql -U test_user -c "INSERT INTO todo (task, done) VALUES ('Build a simple todo app', false);" todo
user: show all records in todo table
assistant: docker exec -it todo_db psql -U test_user -c "SELECT * FROM todo;" todo

sgpt "summarize conversation: $(sgpt --show-chat db | tail +8)" | sgpt --chat extended_db "What table did we create?"
The user created a table named "todo" with columns "task" and "done".
...

sgpt --show-chat db
user: ###
...
Prompt: create postgres docker container with username=test_user, password=test_password, database=todo
###
assistant: docker run --name postgres -e POSTGRES_USER=test_user -e POSTGRES_PASSWORD=test_password -e POSTGRES_DB=todo -p 5432:5432 -d postgres:latest
user: name container as todo_db
assistant: docker run --name todo_db -e POSTGRES_USER=test_user -e POSTGRES_PASSWORD=test_password -e POSTGRES_DB=todo -p 5432:5432 -d postgres:latest
user: create a table in created container in "todo" database task: str, done: bool
assistant: docker exec -it todo_db psql -U test_user -c "CREATE TABLE todo (task TEXT, done BOOLEAN);" todo
user: insert random record to created table
assistant: docker exec -it todo_db psql -U test_user -c "INSERT INTO todo (task, done) VALUES ('Complete task 1', false);" todo
user: task = build a simple todo app
assistant: docker exec -it todo_db psql -U test_user -c "INSERT INTO todo (task, done) VALUES ('Build a simple todo app', false);" todo
user: show all records in todo table
assistant: docker exec -it todo_db psql -U test_user -c "SELECT * FROM todo;" todo

sgpt "summarize conversation: $(sgpt --show-chat db | tail +8)" | sgpt --chat extended_db "What table did we create?"
The user created a table named "todo" with columns "task" and "done".
...

I was thinking about something like that, too. My intuition was that this is actually an unnecessary API call for a task that really usually is not urgent. Also, Turbo GPT3.5 is quite bad at handling length (e.g., "cut by 5%") and the summary should be as verbose as possible while fitting into the length constraint.
But! It is by far the best bang-for-the-buck option. Easy to implement. Anything more than that might be an overkill. So maybe offer that and put it behind an optional flap?

This is a little tangential, but I did just hit this error in a repl session and it's got me thinking.
I think anything more than truncating down to the token limit somehow for the current implementation is too much, yeah? This seems like a super straightforward implementation of a basic memory/context and that's a good thing.
BUT, as suggested, perhaps other implementations are behind flaps/switches/configs would make sense?
Initially, I wanted to see how the memory worked in this and began diving in. But now that I've hit this error, I'm thinking I should just do it :P
I'd like to implement a more permanent memorization and recall system by taking advantage of an embeddings database and watching for things like RECALL and MEMORIZE THIS sort of prompts. This would give you a much much larger memory that could be useful on top of the chat history.
Is this anti-thetical to the current design, though? I'm hoping I could implement this with as minimal fuss since this is langchain based, but I'm still new to all of this ecosystem :) Interested in opinions!
But, I'd rather not overcomplicate a

Oh! Wow. It's not langchain at all - though I don't think it'd be hard to create a langchain client and tap into all of that, while still supporting everything you've done to date.

I quickly reach the limit with error 400 in step by step code development. I understand that this thread talks about this problem...is this correct? web chat does not seem to be affected by this problem because it truncates old messages in the chat (?). Is this a problem that is being worked on or is it unsolvable? Thanks for your contribution. Greetings. Giuseppe

the input limit does seem to limit the usefulness of this at present. I cant even do git diff  | sgpt.. without hitting the limit.
if my prompt is to long for the web chatgpt version i use: https://chatgpt-prompt-splitter.jjdiaz.dev/
very manual and tedious but it is able to handle longer content without losing the context too easily.
I understand some technical limitations mentioned above but are we not able to do something similar with shell-gpt version?
thanks

Latest GPT-4 models allow 128,000 tokens input which is x30 than GPT-3.5. I think it should be enought to handle large text inputs discussed here. Given that I'm closing this issue, but feel free to reopen it if additional relevant information arises.


Update badges to point to pulumi-gcp project

This looks much better - going to merge this to have it available for the launch


what type of proxies is the best for bots there cheap proxies and high price proxies

what's the best for bots

unrelated to agario-client

This is not the place for it


Replace "getAllRegistrations()" deprecated API  by "iterator()"

@sophokles73

returning an iterator doesn't seem to be a good fit because it does not provide any support for efficient paging, does it?

I think it depends on how you implement your iterator:
https://stackoverflow.com/questions/12557837/paginated-queries-iterator-recipe
You had something specific in mind for supporting paging?

@sophokles73  waiting for you to integrate this PR ? FMPOV we can start with an iterator and see if this satisfies users.

If you want to put a UI in front of the RegistrationStore (e.g. the Demo Server Web UI) then I currently do not see how we could implement a paging mechanism based on this Iterator returned by getAllRegistrations(), simply because there is no way for the UI to specify which page it wants (e.g. by specifying a specific index), or am I missing something?
This is not an issue for the demo server where we will probably only have a dozen devices registered but for production this seems to be insufficient. Or would we not use the RegsitrationStore interface in a production system anyways but instead delegate device registration to a separate system and only use the RegistrationService to look up information for individual clients, e.g. for authentication purposes?

If you want to put a UI in front of the RegistrationStore (e.g. the Demo Server Web UI) then I currently do not see how we could implement a paging mechanism based on this Iterator returned by getAllRegistrations(), simply because there is no way for the UI to specify which page it wants (e.g. by specifying a specific index), or am I missing something?

If you want to create a UI which presents all the registration by page you can not do that with this API, but you can create an infinite scroll UI.
Anyway, if you need this kind of paging, you also probably need sorting and searching features. All of this will probably depend of the implementation of your store.  Up to you to implement thoses methods  for your RegistrationStore. We could try to define an abstraction for that but it seems to me a bigger business than what we try to achieve here.
The legitimate question is : "So why adding this API to RegistrationService ? Why not just remove it ?"
FMPOV, RegistrationService is one of the first Leshan API expose to new users. Proposed an easy way to go through all registrations can make senses for beginner. And everybody don't need to handle millions devices.

I see.
On a side note: I have to admit that I have not spent a lot of time recently on leshan. However, when I take a look at the remove_getallregistration branch I find it hard to understand which interface is supposed to be responsible for what. In particular, I stumbled across the RegistrationHandler's dependency on RegistrationServiceImpl. Is there a particular reason why it cannot depend on other interfaces only? Or does this simply mean that we didn't get the interfaces right yet?

RegistrationHandler in internal class : aim to handle registration logic (a kind of controller)
RegistrationService is the API exposed to Leshan users : you can add listener on registration event, access to registrations ...  RegistrationService should not be implemented by users, it just help to hide internal API.
RegistrationStore is responsible to persist registration and observations.  Users could implement this interface.

I didn't really reply to the question :

In particular, I stumbled across the RegistrationHandler's dependency on RegistrationServiceImpl. Is there a particular reason why it cannot depend on other interfaces only? Or does this simply mean that we didn't get the interfaces right yet?

RegistrationHandler depends on RegistrationServiceImpl especially because of "fire event" methods. We don't want to expose thoses methods to users, so we don't add it to the interface.
The RegistrationServiceImpl is a kind of vestige of the old ClientRegistryImpl, currently it hold RegistrationListener. We could maybe organize code in a better way, but I can not find a good way to do for now and all of this is internal. I'm currently focus on external API.

integrated in master (commit 70ce28b302d9c08b3ea14326b6ec0fa565623166, ca83975f77c1505bd8949baa48fd0ebc7f591adb, 05d647d7be6ab41a9810a9d55be6537dd3f1b84f )


ValueError: 'minlength' must not be negative

Hi there, I was running a large image via Cellpose CPU version and encountered "ValueError: 'minlength' must not be negative"

I wonder if anyone has seen this error before. If so, any suggestions will be appreciated.

thanks for reporting this, is this the latest version? I thought we had fixed a bug like this. If it is please upload your image so we can test it

Ah I see it failed in the diameter step. I think it's due to the really large size, Cellpose can't figure out the size correctly. I'd recommend rescaling it before running cellpose, you can make it a size where the nuclei are around 30 pixels in diameter, that is default for the cyto models. And also then you can set the diameter manually and not rely on the auto-detection

(when I ran it in full size it never completed, at least on the GPU, the job was killed)

Thank you!