[Feature Request] Keyring-rs to store secret

Premise
TermSCP uses an AES 256 byte key to encrypt secrets/passwords in bookmarks.
At the moment the AES key is stored in one of the following paths, based on the user's operating system:

Linux: /home/alice/.config/termscp/.ssh/
MacOS: /Users/Alice/Library/Application Support/termscp/.ssh/
Windows: C:\Users\Alice\AppData\Roaming\termscp\.ssh\

This method is quite safe, since anyway, keys are located in a path which is accessible only by the current user.
The Keyring solution
The optimal solution to store the secret would probably be to use keyring-rs which allows the user to store the termscp secret in the operating system vault.
The solution is actually quite simple, since just in a few lines of code, this crates provides a way to do so:
extern crate keyring;
extern crate whoami; // whoami is already in termscp, so only keyring must be added

use keyring::Keyring;

let service: String = String::from("termscp");
let secret: String = generate_key(); // Generates a 256 Bytes random key
let username: String = whoami::username();
let storage: Keyring = Keyring::new(service.as_str(), username.as_str());
// Save password into the storage
if let Err(err) = storage.set_password(secret.as_str()) {
    // Handle error...
}
// ...
// Retrieve password from the storage to decrypt
let secret: String = match storage.get_password() {
    Ok(s) => s,
    Err(e) => { /* Handle error */ },
};

Unfortunately, if on one side this makes safer to handle secrets, at the same time adds a lot of issues.
The BSD compatibility break
Keyring-rs just doesn't support BSD, which would break the compatibility with it. In my opinion is not a big deal, since really, who uses termscp on BSD?
The D-BUS dilemma
On Linux keyring-rs uses D-BUS and requires a service which provides org.freedesktop.secrets. And there are three issues with that.

Some DE doesn't provide any org.freedesktop.secrets service. As a Manjaro/KDE user, I wasn't able to find any service running which provides it, making me unable to use it. I haven't checked how many DE actually supports it, GNOME supports it for sure.
the D-BUS low-level dependency: unfortunately, building keyring-rs on Linux, requires to have the libdbus installed, which is totally MEH. There is no problem if you use a real GNU/Linux operating systems, but what about for example WSL? My WSL doesn't have libdbus installed, since it is not supported, and I haven't any intention to install it. In addition personally, I'm not a huge fan of forcing users to install C libraries to make an application to work. Personally when I see a crate which requires a particular C library to be installed, I give up installing it, not because it's complicated, but just because it's annoying.
The application name is bounded torust-keyring. I'm not 100% sure this means the only service you can use is actually rust-keyring, but if it so, for me it's totally a big no no.

Implementation
After the analysis of the issues introduced by the crate, I haven't given up in implementing this feature, indeed I've actually decided I will implement it in 0.3.1/0.3.2.
The implementation consists in adding a new trait Keystorage which provides these methods:

get_secret() -> &str
set_secret(secret: &str) -> Result
supported() -> bool (static)

and I will implement two providers: KeyringStorage which uses keyring-rs and FileStorage which uses the current implementation.
The keyring-rs crate will be available on Windows and MacOS only, while on Linux, at least until libdbus will be required, I won't be supported. I know it's a pity, considering that probably a big slice of the audience of termscp are Linux/WSL users, but this would introduce many compatibility issues and would remove the coverage for many users (wsl users in particular).

the D-BUS low-level dependency: unfortunately, building keyring-rs on Linux, requires to have the libdbus installed, which is totally MEH. There is no problem if you use a real GNU/Linux operating systems, but what about for example WSL? My WSL doesn't have libdbus installed, since it is not supported, and I haven't any intention to install it. In addition personally, I'm not a huge fan of forcing users to install C libraries to make an application to work. Personally when I see a crate which requires a particular C library to be installed, I give up installing it, not because it's complicated, but just because it's annoying.

Why couldn't it be an optional dependency configured at build-time with a feature flag?

I've already though about this possibility, but I've decided not to opt for it.
The reason is quite simple: most of the termscp users don't install it through cargo install, but through packages (deb, rpm...).
I don't know the exact percentage, but I guess that people which installs termscp via cargo is below 25%, which makes that in the most optimistic case the 15% of my users installs termscp via cargo and are linux users.
How many of them will enable the keyring feature in the build? Considering that not all the linux distros support the service used by the d-bus, it's really not worth it to implement the keyring for linux.
In addition we must consider there's no security vulnerability atm in practice. The key is stored in a file which is accessible only by the current user, as happens for example for the ssh keys and nobody has ever complained for it. In addition to this, you're completely free to choose whether to store or not the passwords and I've adivesed the community not to store passwords for production servers (and I really hope that they opt to use rsa-key-based authentication for them).

Considering that not all the linux distros support the service used by the d-bus, it's really not worth it to implement the keyring for linux.

This is a bit unfair. All of the major distributions (Debian, Ubuntu, Fedora, CentOS, RHEL, Arch, etc) use systemd, and systemd has a hard dependency on dbus. Gentoo users are used to compiling things themselves, so adding/removing compile-time flags is no big deal there. That's the majority of users covered, and I know for Arch at least, maintainers absolutely would enable the keyring feature at build-time.
Dismissing the addition of an optional feature because there exists at least one distribution that wouldn't use that feature is a disappointing attitude.

For what it's worth, KeepassXC also provides org.freedesktop.secrets:
https://archlinux.org/todo/gnome-keyring-dependency-replacement-with-orgfreedesktopsecrets/

I'll make some tests with it when I have some spare time using keyring-rs to see if it works fine.
Once I'll be come back with a definitive analysis in implementing keyring storage for linux I will eventually re-open this issue to link a PR for termscp 0.6.0 (I guess, there's still a lot to do for 0.5.0).
Thanks

Issue closed, for updates and linux implementation, please refer to issue #48


changed download url and model names

The  https://storage.googleapis.com/gpt-2 bucket no longer exists.
Because of this all files downloaded from this URL only contain:
"NoSuchBucketThe specified bucket does not exist. "
I changed the URL to https://openaipublic.blob.core.windows.net/gpt-2/models/ and adjusted the model names for the 2 smaller models.

This is great, thank you so much!


Include Bourbon and Neat

Can you please include Bourbon and Neat here? Compass is dead and not being developed on anymore.

No, but you can easily do so yourself.


feat: enable Go generics for jsii Go CDK code

Current situation
In Go, strings are not nullable by default like they are in TypeScript, C# etc.
There's also no pointer literal - you can't do something like &("string value") to create a pointer to a string literal, it's required to create a variable instead.
While there's discussion on having something built into the language in https://github.com/golang/go/issues/45624 it hasn't concluded with a built-in as part of the language, or a standard library function.
The Go JSII library has worked around this by using the approach of creating functions that turn literals and variables into a pointer. Since Go < 1.18 didn't support generics, there's one for each supported JSII type. This means that you have to think about the type of any variables and use the right conversion function, while you're writing code.
stringPtr := jsii.String("literal value")
float64Ptr := jsii.Number(123.45)

Proposal
In Go 1.18, generics were added. These type parameters can be used to provide a single function that convert literals and variables into a pointer.
func Ptr[T any](v T) *T {
	return &v
}

We can further restrict the allowed types of T by using a constraint.
type Type interface {
	bool | string | float64 | time.Time
}

func Ptr[T Type](v T) *T {
	return &v
}

If we adopt the name V instead of Ptr to save a further two characters (I'd still be happy with Ptr, Val etc. as a name), the previous example can be rewritten as:
stringPtr := jsii.V("literal value")
float64Ptr := jsii.V(123.45)
boolPtr := jsii.V(true)

This means that only one function is used to convert multiple types, and the function name can be a few characters shorter.
For the V function, integer literals can not be converted to float64, since the output would be a pointer to the input type, not to the allowed float64 type. Developers would be prompted that integer types are not in the set of allowed types (string, float64, bool, time.Time).
However, the Number function can be updated in place to use generics to accept any numeric type, which simplifies code that uses integer values from:
intPtrOK := jsii.Number(float64(123))
var x uint32
intPtrOK = jsii.Number(float64(x))

intPtrOK := jsii.Number(123) // Would automatically be converted to `float64`
var x uint32
intPtrOK = jsii.Number(x)

Impact
Since Go 1.18 is already required by the CDK, the use of generics is possible.
For backwards compatibility with existing code, the existing functions would be maintained, so no code would break.
Before
// DynamoDB.
slotMachineTable := awsdynamodb.NewTable(stack, jsii.String("slotMachineTable"), &awsdynamodb.TableProps{
	TableName:    jsii.String("slotMachine"),
	PartitionKey: &awsdynamodb.Attribute{Name: jsii.String("_pk"), Type: awsdynamodb.AttributeType_STRING},
	SortKey:      &awsdynamodb.Attribute{Name: jsii.String("_sk"), Type: awsdynamodb.AttributeType_STRING},
	BillingMode:  awsdynamodb.BillingMode_PAY_PER_REQUEST,
	Stream:       awsdynamodb.StreamViewType_NEW_IMAGE,
})

// Create an event bus.
eventBus := awsevents.NewEventBus(stack, jsii.String("slotMachineEventBus"), &awsevents.EventBusProps{
	EventBusName: jsii.String("slotMachineEventBus"),
})

// Process streams.
streamHandler := awslambdago.NewGoFunction(stack, jsii.String("streamHandler"), &awslambdago.GoFunctionProps{
	Runtime:      awslambda.Runtime_PROVIDED_AL2(),
	Architecture: awslambda.Architecture_ARM_64(),
	Entry:        jsii.String("../api/streamhandler/"),
	Environment: &map[string]*string{
		"EVENT_BUS_NAME":    eventBus.EventBusName(),
		"EVENT_SOURCE_NAME": jsii.String("slot-machine"),
	},
	Timeout:      awscdk.Duration_Minutes(jsii.Number(15)),
	LogRetention: awslogs.RetentionDays_ONE_YEAR,
})
slotMachineTable.GrantReadData(streamHandler)
eventBus.GrantPutEventsTo(streamHandler)

After
// DynamoDB.
slotMachineTable := awsdynamodb.NewTable(stack, jsii.V("slotMachineTable"), &awsdynamodb.TableProps{
	TableName:    jsii.V("slotMachine"),
	PartitionKey: &awsdynamodb.Attribute{Name: jsii.V("_pk"), Type: awsdynamodb.AttributeType_STRING},
	SortKey:      &awsdynamodb.Attribute{Name: jsii.V("_sk"), Type: awsdynamodb.AttributeType_STRING},
	BillingMode:  awsdynamodb.BillingMode_PAY_PER_REQUEST,
	Stream:       awsdynamodb.StreamViewType_NEW_IMAGE,
})

// Create an event bus.
eventBus := awsevents.NewEventBus(stack, jsii.V("slotMachineEventBus"), &awsevents.EventBusProps{
	EventBusName: jsii.V("slotMachineEventBus"),
})

// Process streams.
streamHandler := awslambdago.NewGoFunction(stack, jsii.V("streamHandler"), &awslambdago.GoFunctionProps{
	Runtime:      awslambda.Runtime_PROVIDED_AL2(),
	Architecture: awslambda.Architecture_ARM_64(),
	Entry:        jsii.V("../api/streamhandler/"),
	Environment: &map[string]*string{
		"EVENT_BUS_NAME":    eventBus.EventBusName(),
		"EVENT_SOURCE_NAME": jsii.V("slot-machine"),
	},
	Timeout:      awscdk.Duration_Minutes(jsii.V(15.0)),
	LogRetention: awslogs.RetentionDays_ONE_YEAR,
})
slotMachineTable.GrantReadData(streamHandler)
eventBus.GrantPutEventsTo(streamHandler)

Considerations
The name V is the shortest, but doesn't describe what it does.
The Go team might, at some point, introduce a change to automatically convert literals into pointers, in which case the jsii.V and jsii.String function calls would be redundant and could be stripped out of a codebase. However, this change doesn't make that potential outcome any worse.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I was definitely thinking about doing this and the major holdout was essentially go1.17... but now that go1.20 is out that's not a problem anymore. You beat me to it (I was busy on other stuff), so thanks for that...
I might not have time to review the PR today however, but I'll absolutely be having a stab at it next week.


Transparent plot for 2^x

Transparent plot for 2^x
{ fn: '2^x'},

I tried defining a color but not luck. Looks like a bug or there's another alternative?

http://codepen.io/amejiarosario/pen/QKXyQE?editors=1010

thanks for the report!

Thanks for the report!

Should be fixed in v1.17.3 (note that the pow function for intervals is defined only when the exponent is a single real number, not an interval, for this specific function you should use the builtIn sampler instead) e.g.
functionPlot({
  target: '#demo',
  data: [
    { fn: '2^x', sampler: 'builtIn', graphType: 'polyline' }
  ]
});

cool, I just test it out from the dist folder and it works :)

@maurizzzio: It seems that this is still not fixed. I have the same issue after checking out the copy from master in dist, and I still see the issue on the demo on the website.

@belph I just tried the following on the jsbin embed on the website and is working
functionPlot({
  target: '#demo',
  data: [
    { fn: '2^x', sampler: 'builtIn', graphType: 'polyline' }
  ]
})

@belph you can see a working version on my codepen: http://codepen.io/amejiarosario/pen/QKXyQE
This are the libs I used:

Ah, my mistake! I overlooked the additional properties in @maurizzzio's comment. After adding the graphType:'polyline' property, everything renders as expected.


Support subject modes

Add support for changing mode: READWRITE, READONLY, IMPORT. Docs
Add support for specifying the id and version when creating a schema subject version. Docs

I'm fighting with a failure I just can't get to the bottom of, and wanted to ask for help. Test shouldRegisterSchemaForNewResource in SchemaRegistrySubjectControllerTest is failing because the client never makes the request to register the schema subject version.
I have narrowed the cause of the failure to the change here. What's happening is that the Executor is finishing its try-with-resources block and the client is being closed, but this happens before the call to registerSubjectVersion is finished. The change to CreateSchemaSubjectChangeHandler is necessary because the mode needs to be updated before a new version is registered.
Hopefully I'm missing something simple, but I've banged my head on this for several hours now with no luck.


[libmorton] update to 0.2.12

[X] Changes comply with the maintainer guide
[X] SHA512s are updated for each updated download
[ ] ~The "supports" clause reflects platforms that may be fixed by this new version~
[ ] ~Any fixed CI baseline entries are removed from that file.~
[ ] ~Any patches that are no longer applied are deleted from the port's directory.~
[X] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[X] Only one version is added to each modified port's versions file.

The usage test passed on x64-windows (header files found):
libmorton provides CMake targets:

  # this is heuristically generated, and may not be correct
  find_package(libmorton CONFIG REQUIRED)
  target_link_libraries(main PRIVATE libmorton::libmorton)


hard to add this plugin using lazy.nvim with the container option setting.

I need to use the docker container to serve my custom model and it works when using ollama docker images. BUT, when come to using it in this  plugin, it is difficult to set up the container value in lazy.nvim package manager. Can you provide more code snips to using different config setting ups? Thanks for your time and effort on time good project.

It should be just as simple as this and it helps the beginner to start：
{
    "David-Kunz/gen.nvim",
    config = function()
      require('gen').container = 'ollama_gpu'
      -- require('gen').model = 'zephyr'
    end,
  },

Hi @wishuuu ,
Could you help this user? Shouldn't it be enough to set the container property? I must admit, I haven't tested it yet.

Hi @meicale !
Here is code snippet from my lazy config:
return {     "David-Kunz/gen.nvim",     config = function()         vim.keymap.set('v', '<leader>gn', ':Gen<CR>')         vim.keymap.set('n', '<leader>gn', ':Gen<CR>')         require('gen').model = 'codellama'         require('gen').container = 'ollama'     end }
Honestly it's hard to tell what may be wrong with your config. Can you check if docker exec ollama_gpu ollama run zephyr TEST returns any error in your case? Also are you using Linux or Windows?

There is now a traditional setup function. Does that resolve this issue?

Hi @meicale ,
The docker option was removed since we switched to HTTP-based communication.
You should be able to specify the init function to start your docker container and use port forwarding to communicate with it.
Best regards,
David


Responsive?

Is the Chart Responsive?
I tried setting the width & height of the canvas element as well as it's div container to smaller sizes as resolutions decrease. It works fine in Chrome, but if I open it up on my iPhone the size doesn't change.
Any suggestions?

+1 for responsive? im lost

+1 for responsive

+1 for responsive ... or percentage size.

:+1:

+1

I'm using this as workaround. Not an elegant solution maybe, but it works for me:
var $chart = $('.amount-chart'),
    size = parseFloat( $chart.outerWidth() ),
    clearSet;

$chart.easyPieChart({
    size: size,
    animate: 2000
});

$(window).on('resize', function(){

   size = parseFloat( el.outerWidth() );

   $chart.css({
      height: size
   });

   clearTimeout(clearSet);
   clearSet = setTimeout(function(){
      $chart.removeData('easyPieChart').find('canvas').remove();
      $chart.easyPieChart({
         size: size,
         animate: 1
      });
   }, 100);
 });

Here a jsfiddle example with setTimeout lines commented: https://jsfiddle.net/70vy5smy/2/


Dockerfile for Python and Pypy

Dockerfiles for Python.
Includes Dockerfile with Python3 and Pypy.
There is no Pypy image with alpine, so it's not used.

I approve

Please do so in the review, the. we get the satisfying green check mark that you approved


drivers: mbox: add IVSHMEM based mbox driver

Since the IPM drivers are moving towards deprecation the existing inter VM shared memory IPM driver needs to be converted into a Mailbox kind driver, this PR makes this conversion based on the existing IPM driver.

Merging this driver would enable to using IPC subsystems on top of the IVSHMEM.

Hi folks, any updates here?

@carlocaione  sorry bothering you again, can you review it, or point who can I tag to review this one?
Thank you!

@nashif who else should I relay this PR? It has been opened for a while.
Thank you.

@tbursztyka could you point someone that may review this as well?

@uLipe I am changing the milestone to 4.1 as the 4.0 release is now in testing phase and is only accepting bug fixes and documentation updates


Java attribute of type object is incorrectly mapped to an OpenApi property of type object

Related: https://github.com/OpenAPITools/openapi-generator/issues/16110
Description
A Java attribute of type object can be any instance of an object, e.g. String, Boolean, Long and so on. However, the resulting OpenApi specification assigns this attribute to an object of type object, which must be a JSON object, that is a map.
Example
The following java class can be used as a minimal example:
public class Pet{
	private Long id;

	@Schema(description = "A string, a number or a boolean", anyOf = { String.class, Number.class, Boolean.class })
	private Object name;
}

This generates the following openapi.yaml:
...
    properties:
      name:
        type: object
        description: "A string, a number or a boolean"
        anyOf:
        - type: string
        - type: integer
          format: int64
        - type: number
          format: double
        - type: boolean
...

whereas the following would be correct:
...
    properties:
      name:
        description: "A string, a number or a boolean"
        anyOf:
        - type: string
        - type: integer
          format: int64
        - type: number
          format: double
        - type: boolean
...

Related:

https://github.com/swagger-api/swagger-core/issues/4014
https://github.com/swagger-api/swagger-core/issues/3834


Stats Page

Do the Stats Page
https://sites.google.com/codeustudents.com/summer-2019/week-2-guided-projects/stats-page

Issue: #16
PR: #51


I got error while installing SQLi query tampering :)

while installing SQLi query tampering I faced this error

so any chance to solve this

Thank you for your report. It would be helpful if you could send the whole error message.
Which version of Burp do you use?


leaflet-1.3.1  On the longitude and latitude problems caused by CRS

How to reproduce

Leaflet version I'm using: 1.3.1

Browser (with version) I'm using: chrome

OS/Platform (with version) I'm using: windows 10
const map = L.map('emap', {
crs: L.CRS.EPSG4326,
center: [
31.90059,
120.584663
]
});

and
const map = L.map('emap', {
center: [
31.90059,
120.584663
]
});
After setting the CRS, the center point and the latitude and longitude are different. Because of the data reasons, the latitude and longitude obtained by the CRS:EPSG4326 are consistent with the default values. What is the solution?

Hi, and thanks for taking the time to open a bug report in Leaflet.
Please provide a more effective bug report, and in particular all the information requested in the issue template (provided when you create a new issue), so that we can effectively investigate and hopefully resolve it.
Sharing a live reproduction example (e.g. using https://leafletjs.com/edit) that automatically shows the bug with comments can highly increase the possibility of successful investigation.
You can also add annotated screenshots, sketches, animated captures, etc.

I will re-open once enough information has been provided.


some randomness ?

i'm thinking about 2 kind of randomness :

An arrow type who have 50% chance to transmit input signal, 50% chance to deny it.
An arrow type who convert signal to any random color (in colorLogic mode)
An arrow type who convert signal to a random color from 2, or 3 specific colors (in colorLogic mode)

done in #20 (the random color mode pick random color from allowed color to go out from target node)


Add topic "guzzle"

Please confirm this pull request meets the following requirements:

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/main/CONTRIBUTING.md.
[x] I am not the sole author or employee of a company who created the topic or collection I'm changing.

Which change are you proposing?

[ ] Suggesting edits to an existing topic or collection
[x] Curating a new topic or collection
[ ] Something that does not neatly fit into the binary options above

Editing an existing topic or collection
I'm suggesting these edits to an existing topic or collection:

[ ] Image (and my file is *.png, square, dimensions 288x288, size <= 75 kB)
[ ] Content (and my changes are in index.md)

Please replace this line with an explanation of why you think these changes should be made.

Curating a new topic or collection

[x] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
[ ] My folder contains a *.png image (if applicable) and index.md
[x] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/main/docs

Guzzle is one of the widely used implementations of PSR-7 as an alternative to CURL

Something that does not neatly fit into the binary options above

[x] My suggested edits are not about an existing topic or collection, or at least not a single one
[ ] My suggested edits are not about curating a new topic or collection, or at least not a single one
[x] My suggested edits conform to the Style Guide and API docs: https://github.com/github/explore/tree/main/docs

Please replace this line with an explanation of your proposed changes.

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

You're welcome as always!


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter ai-toolbox for common errors and appropiate suggestions to keep this adapter up to date.
This check is based on the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.ai-toolbox
  -
ERRORS:

[ ] :heavy_exclamation_mark: [E029] Node.js 18 is required as minimum, node.js 18 is recommended. Please adapt "{'engines' : { 'node' >= '16' } }" at package.json.
[ ] :heavy_exclamation_mark: [E145] Missing mandatory translation into de of some "common.news" in io-package.json.
[ ] :heavy_exclamation_mark: [E250] Not found on npm. Please publish
[ ] :heavy_exclamation_mark: [E606] Current adapter version 0.0.2 not found in README.md
[ ] :heavy_exclamation_mark: [E802] No topics found in the repository. Please go to "https://github.com/ToGe3688/ioBroker.ai-toolbox", press the settings button beside the about title and add some topics.

WARNINGS:

[ ] :eyes: [W154] Missing suggested translation into ru,pt,nl,fr,it,es,pl,uk,zh-cn of some "common.news" in io-package.json.
[ ] :eyes: [W401] Cannot find "ai-toolbox" in latest repository
[ ] :eyes: [W522] Why did you decide not to use i18n support?
[ ] :eyes: [W606] Could not retrieve timestamp of LATEST revision at npm.

:thumbsup: No suggestions found
Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
or
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Sat, 07 Dec 2024 16:50:37 GMT based on commit 4b5328ffd1b36ac0b564a96a0df552a97c700d49
ioBroker.repochecker 3.2.2

@iobroker-bot recheck


Dynamic language binding

I needed this functionality in an app I am working on, so I thought I would contribute the change if you want it.
I have added support to dynamically bind a language parameter. This involves reloading the reCaptcha script from google, so there is no longer a need to include the reCaptcha script tag. I also updated the documentation accordingly. Let me know if this is too big of a change.

I see language is defined on the directive, what happens if you have multiple directives with different languages on the same page at the same time?
It also appears that the recaptcha script will be injected each time a new directive is created which seems wasteful and possibly even problematic for any time more than one recaptcha is loaded (as the recaptcha script assumes checks some globals and overrides others which would have been set by previous, possibly still active recaptcha widgets.

Good point about the language attribute. I will change that to something like recaptcha-language.
The script has to be injected every time because of how Google handles languages for reCaptcha. I agree it's not ideal. I have tested it pretty extensively and haven't noticed any issues.

I may be wrong, but my initial impression here, is that it requires too much complexity for a feature that IMO not many people need. Actually, I wonder why would you need to change the language dynamically?
Regarding the PR itself, i see two issues with it:

It's lacking tests
Is modifying the release files instead of the source files.

@mtrias

The project doesn't contain test currently, at least not in the master branch.
If you scroll down further, you can see that the source files were modified. The release files were only modified due to the grunt build process.

The reason I need to change the language on the fly is because the app I am building will be used on a kiosk computer, so the app has to be able to let the user choose their language. The OS or browser language cannot be used as a basis.

Thanks for the clarification @geo242
Maybe you have an outdated master? I'm pretty sure there are tests in the project.

@mtrias that may be. I will update and add tests

I'd suggest moving setting the language from the directive to the provider/service as the language is probably of the site and not the individual directives.
Also, maybe using the language of the webpage by default (not the OS or browser language, but the lang attribute on the html tag) if it is there (just to help others even if the kiosk doesn't use it (really, it should, as the lang should be set to the language that is displayed on the page).

@TheSharpieOne good points. I will make those adjustments.

Hi,
This is great, i was working on a solution for this as well & was about 90% there, but now I'm investigating this.
The first time I load a page it sets the captcha to the correct language based on the model value that this new language attribute is tied to. However, the first time I change the language, I get the error 'ReCAPTCHA has already been rendered in this element' & the captcha is not rendered. For every subsequent language change the captcha is rendered, but it is rendered with the value of the language that preceded it. So for instance, after that initial error, i change the language from Arabic to German. Now the language of the site has changed to German but the captcha is rendered as Arabic. No errors are thrown. Now i change from German to Spanish. The language model is now Spanish, but the captcha renders in German, the previous model language.
In brief, the first model change causes an error, & every model change after that brings up a captcha with a language corresponding to the previous model value.

I solved it by adding delete $window.grecaptcha; to the function loadScript(url) . Like so:
function loadScript(url) {
delete $window.grecaptcha;
// remainder of function
}

It seems that when return recaptcha = $window.grecaptcha; is returned the $window.grecaptcha object is still the object created with the previous script. Deleting the object before calling the script allows return recaptcha = $window.grecaptcha; to use the $window.grecaptcha from the new script, not the previous one.
I added the change to the unminified release script from my fork of  geo242's fork: https://github.com/rhclayto/angular-recaptcha/blob/language-binding/release/angular-recaptcha.js

Hey guys, good job. But how can I use this now?

are you guys planning to merge this ?

@xarv There are some points that need to be addressed before merging this. I'm referring to this comment, and this other comment. Also, the PR has conflicts that need to be resolved.

Anything new here? Still looking for a working solution

This PR needs more work in order to be merged. If you want to use the feature you can always use the PR's author fork.

superseded by #170

This is obsolete and should be closed.


Removed robotDescriptionServer.xml

Removed device robotDescriptionServer

Please, merge master into devel

Done in https://github.com/robotology/robots-configuration/commit/923749b09bedee00493de0b80bf4dc5d30e4aab2


initial fastlane structures

Fastlane starter kit; be welcome using my Fastlane Cheat Sheet to build on this, and my full_description.txt formatting hints for a well formatted and good looking description should you need to update/change it. Please use the former to add some screenshots – you know, first impression and a picture telling more than 1.000 words and all that :wink:
Why I'm sending this PR? Well, you'll need it for #24 :smiley:

thanks for this! :100:

Gladly done! Adjusted the config here to check and fetch it together with future releases. So whenever you update description etc, my updater will pull it along. Should you add screenshots one day please let me know so I enable them as well.


fix lint for if block

fix "if block ends with a return statement" issue by go lint
Signed-off-by: Lan Luo<EMAIL_ADDRESS>

@antoninbas I think we can enable lint check in go.yml, looks like we only run make golangci which doesn't run lint check, and I just run "make lint", it seems there are quite a lot other warning like exported type GroupMember should have comment or be unexported, not sure if we can skip this kind of warning in .golangci-golint.yml or fix them all, any suggestion?

Codecov Report

Merging #2532 (eabe8a3) into main (028393d) will increase coverage by 0.16%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #2532      +/-   ##
==========================================
+ Coverage   59.78%   59.95%   +0.16%
==========================================
  Files         284      281       -3
  Lines       22265    22203      -62
==========================================
- Hits        13312    13311       -1
+ Misses       7535     7476      -59
+ Partials     1418     1416       -2

Flag
Coverage Δ

kind-e2e-tests
47.10% <0.00%> (+0.22%)
:arrow_up:

unit-tests
42.22% <0.00%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/agent/util/net_linux.go
34.00% <0.00%> (+0.33%)
:arrow_up:

pkg/ovs/ovsctl/appctl.go
29.68% <0.00%> (+1.32%)
:arrow_up:

...g/controller/networkpolicy/store/appliedtogroup.go
86.36% <0.00%> (-3.04%)
:arrow_down:

pkg/controller/grouping/controller.go
67.24% <0.00%> (-1.73%)
:arrow_down:

pkg/apiserver/apiserver.go
87.50% <0.00%> (-0.50%)
:arrow_down:

pkg/agent/memberlist/cluster.go
72.33% <0.00%> (-0.49%)
:arrow_down:

pkg/agent/route/route_linux.go
44.68% <0.00%> (-0.27%)
:arrow_down:

pkg/apiserver/certificate/cacert_controller.go
56.95% <0.00%> (ø)

pkg/legacyapis/controlplane/install/install.go
100.00% <0.00%> (ø)

...egacyclient/clientset/versioned/scheme/register.go
100.00% <0.00%> (ø)

... and 10 more

@antoninbas , it turns out there are quite a lot "if block" issue after disable 'max-per-linter' and run "make lint", I refined all of them here, and will submit a new PR to add go lint check to go.yml and other lint fix.

@antoninbas @lzhecheng Could you help to take a look for this PR? I have another commit to fix other warnings and enable make lint in go.yml workflow but would like to wait this to merge, so I can rebase it and submit the PR. thanks.

@antoninbas , thanks for the comments, I actually push another commit to enable golint with standalone job, and I also add some exclude rules to skip some warnings https://github.com/antrea-io/antrea/commit/79aa76641b83115cf6afb3ac37217fec848d8a33, I think if this PR to fix "if block" warning is OK and merged, I can submit another PR to address CI part. If we want to replace golint with revive, I think we create an issue to track it.

@luolanzone let's not merge something that pulls in a deprecated tool... I'm not sure why we don't start with revive from the get go, after doing some research on the consequences of running it as a PR merge blocker.

@antoninbas sure, I can take a look at revive first to see if it's good to be a PR merge blocker.

Hi @antoninbas  I submitted a new commit to replace golint with revive here https://github.com/antrea-io/antrea/commit/b9cac2004a750b759efa6f32c6156dbd819b4a7b, and I just enable a few rules here https://github.com/antrea-io/antrea/blob/b9cac2004a750b759efa6f32c6156dbd819b4a7b/.golangci.yml#L12-L21 considering we will add it as a CI blocker.

/test-all


[in_app_purchase] Updating in_app_purchase_platform_interface dependency

Ran into an issue using in_app_purchase where it somehow used a version of in_app_purchase_platform_interface previous to 1.3.0. This is an issue because from<EMAIL_ADDRESS>and beyond it implements PurchaseStatus.canceled (according to the docs/changelog).
This PR updates the dependency of in_app_purchase_platform_interface to ^1.3.0 so this should not happen.

Ran into an issue using [...] This is an issue because [...]

What was the issue exactly? This package doesn't directly reference PurchaseStatus.canceled, so I'm not clear on what the bug this would solve is. Please provide a specific error message or description for the problem you are trying to solve.
(If it's just that you wanted the latest version of in_app_purchase_platform_interface, the solution is for you to update your packages, not to change the minimum versions.)

Absent an answer to the question above, closing. Please feel free to re-open if you can provide more context about the goal of this change.


Add sym/cmp for pushbuttons

Open by default:

Closed by default:

Open questions:

Should the invisible grab area be put there or not?

Improve names, e.g. "Momentary switch, open" -> "Push Button Momentary NO" and "Momentary switch, closed" -> "Push Button Momentary NC"

Title Case
I think the symbol you have drawn is only used for push buttons, not for any kind of switches
Starting the names with "Push Button" makes them easier to find in sorted lists
"NO" and "NC" (normally open/closed) are terms commonly used for switches/pushbuttons

Grab area is reasonable, but needs some changes:

Doesn't cover the "button" of the normally-open symbol -> increase height
Should not overlap with pins -> decrease width
Must be filled, otherwise only the area of its lines can be grabbed
As the lines aren't required to grab, better change line width to zero

Maybe place {{VALUE}} at the bottom of the symbol?
Set component default value to "{{PARTNUMBER or DEVICE}}"

Improve names, e.g. "Momentary switch, open" -> "Push Button Momentary NO" and "Momentary switch, closed" -> "Push Button Momentary NC"

A momentary switch is not necessarily a push button. A push button is a momentary switch though.

Starting the names with "Push Button" makes them easier to find in sorted lists

The push button devices would start with "Push Button".

I think the symbol you have drawn is only used for push buttons, not for any kind of switches

According to Wikipedia it seems to be the IEEE symbol for momentary switches :slightly_smiling_face:

"NO" and "NC" (normally open/closed) are terms commonly used for switches/pushbuttons

Ah, good point! I updated the names (including title casing)

Grab area is reasonable, but needs some changes:
Maybe place {{VALUE}} at the bottom of the symbol?

Done:

Set component default value to "{{PARTNUMBER or DEVICE}}"

Done.

According to Wikipedia it seems to be the IEEE symbol for momentary switches

But in the IEEE standard this symbol is called "Pushbutton":

For other momentary switches, I guess these symbols at the right apply:

There are many different kinds of switches (pushbutton/rotary/slider/dipswitch/etc., most of them available as momentary and locked variant). All of them have different symbols (see for example here). I wonder if we should create separate components for all these types, or only a few "generic" switch components. I think at this time I would go with separate components...

You're right :slightly_smiling_face: I'll adjust the naming and will try to fix the name on Wikipedia too.

Done. I used the name "Pushbutton" instead of "Push Button" according to IEEE315-1975.

Perfect :) Looks good now :+1:


authlib already installed, but No module named 'authlib'

I running helm use this template
and enabled oauth follwing config:

enable_oauth: |
from flask_appbuilder.security.manager import (AUTH_DB, AUTH_OAUTH)
AUTH_TYPE = AUTH_OAUTH
OAUTH_PROVIDERS = [
{
"name": "google",
"whitelist": [ os.getenv("OAUTH_WHITELIST_REGEX", "") ],
"icon": "fa-google",
"token_key": "access_token",
"remote_app": {
"client_id": os.environ.get("GOOGLE_KEY"),
"client_secret": os.environ.get("GOOGLE_SECRET"),
"api_base_url": "https://www.googleapis.com/oauth2/v2/",
"client_kwargs": {"scope": "email profile"},
"request_token_url": None,
"access_token_url": "https://accounts.google.com/o/oauth2/token",
"authorize_url": "https://accounts.google.com/o/oauth2/auth",
"authorize_params": {"hd": os.getenv("OAUTH_HOME_DOMAIN", "")}
}
}
]

I also preinstall authlib package to superset image
ex. Dockerfile

FROM apache/superset:latest
RUN pip install --no-cache-dir authlib
.But when I run helm to deploy, it still have error:
.... Failed to create app Traceback (most recent call last):   File "/app/superset/app.py", line 37, in create_app     app_initializer.init_app()   File "/app/superset/initialization/__init__.py", line 473, in init_app     self.init_app_in_ctx()   File "/app/superset/initialization/__init__.py", line 418, in init_app_in_ctx     self.configure_fab()   File "/app/superset/initialization/__init__.py", line 517, in configure_fab     appbuilder.init_app(self.superset_app, db.session)   File "/usr/local/lib/python3.8/site-packages/flask_appbuilder/base.py", line 211, in init_app     self.sm = self.security_manager_class(self)   File "/usr/local/lib/python3.8/site-packages/flask_appbuilder/security/sqla/manager.py", line 62, in __init__     super(SecurityManager, self).__init__(appbuilder)   File "/usr/local/lib/python3.8/site-packages/flask_appbuilder/security/manager.py", line 263, in __init__     from authlib.integrations.flask_client import OAuth ModuleNotFoundError: No module named 'authlib'
So anyone have solution to fix that, I try downgrade authlib to 0.15.x version but still have the same error

I solved the same error by adding authlib==1.2.0 it to the boostrapScript section of my-values.yaml (around L43):
Was:
bootstrapScript: |
  #!/bin/bash
  rm -rf /var/lib/apt/lists/* && \
  pip install \
    psycopg2-binary==2.9.1 \
    redis==3.5.3 && \
 .
.
.

After:
bootstrapScript: |
  #!/bin/bash
  rm -rf /var/lib/apt/lists/* && \
  pip install \
    psycopg2-binary==2.9.1 \
    authlib==1.2.0 \
    redis==3.5.3 && \
.
.
.

Similar to @stevehenderson, I solved this by adding to supersetWorker.command. From:
command:
  - "/bin/sh"
  - "-c"
  - ". {{ .Values.configMountPath }}/superset_bootstrap.sh; celery --app=superset.tasks.celery_app:app worker"

to:
command:
  - "/bin/sh"
  - "-c"
  - ". {{ .Values.configMountPath }}/superset_bootstrap.sh; pip install authlib==1.2.0; celery --app=superset.tasks.celery_app:app worker"

This is because appending to the bootstrapScript didn't seem to run because this step, somehow.

I fixed this in mine by just adding authlib==1.2.0 to docker/requirements-local.txt

Got the same issue when using 3.0.1 as my base image, with authlib and apache-superset[databricks] installed as extra layer for my deployment.
I tried to docker run the image and execute pip list within the container to ensure required libraries were installed correctly.
But have the issue of "No module named authlib" and Databricks connection did not show up when adding new connections after deployed to my local Kubernetes cluster (i was using kind) with my customized image. And worked as charm after add these libraries under bootstrapScript as @stevehenderson suggested.
Still trying to understand why these libraries does not work, and require to be installed with bootstrap when the image already have them installed.

I refer to the Dockerfile where building dev layer from lean layer. And come out with a new custom Dockerfile, where switch user to root before COPY and RUN pip install, then switch back to the user superset. Now authlib and apache-superset[databricks] are both been installed correctly without additional pip install under bootstrapScript.
Following is my latest Dockerfile:
FROM apache/superset:3.0.1

USER root
COPY ./requirements.txt .
RUN pip install --no-cache-dir -r ./requirements.txt
USER superset

Note: I had tried different ways to copy requirements.txt before added switching user, and none of them install extra libraries successfully.
# Rename the file when copy, in case any constraint with the file name "requirements.txt"
COPY ./requirements.txt ./rename.txt
# Change owner when copy the file into image
COPY --chown=superset:superset ./requirements.txt .
# Copy file into requirements directory, instead of under root directory
COPY ./requirements.txt requirements/requirements_custom.txt
# Combine both approaches above
COPY --chown=superset:superset ./requirements.txt requirements/requirements_custom.txt

@alephpt @MartinKChen this issue is about the helm/k8s deployment process, not docker

Closing this one out, as it seems it's gone quiet/stale, and because there seem to be plenty of folks that reached a solution on the thread. If people are still experiencing this in currently supported versions of Superset (3.1/4.0) just say the word and we can revisit/reopen.

The workaround is still required with the current version, while it should work out of the box with the stock Docker image.

having the same issue currently on local machine, macos;
after commenting out the authlib, pypdf is having same issue, so I assume something is related to the OS or python [and therefore many other libs might be not seen];
tried reinstalling both, using Authlib instead of authlib, restarting local machine, nothing helped;
installed macos update recently, not sure if might be related;

Hi @rusackas , this manual step is still needed on 4.0.1.


Update quickstart.rst

Nice wording
About
This pull request is about bad wording.
Checklist

[x] I've ran pre-commit to format and lint the change(s) made.
[x] I've checked to make sure the change(s) work on 3.8.6 and higher.
[ ] This fixes/solves an Issue.

(If existent):

[x] I've made this pull request for/as: (check all that apply)

[x] Documentation
[ ] Breaking change
[ ] New feature/enhancement
[ ] Bugfix

Hey!
Thank you for taking your time to make a pull request. Unfortunately, you've come to violate our contribution requirements by breaking the Discord Code of Conduct, which we require for newcomers and all alike contributors. Your toxic behavior goes against our values additionally with bringing positivity in this library aimed for the OSS ecosystem at Discord, as seen in #554 and #553 . As a result, we kindly ask that you reflect on these actions when you make pull requests for other Discord python libraries and open-sourced projects on GitHub.


server url scoped to single paths

Sometimes, you want to override the server URL just for a single path. We don’t support this yet, so let’s add support for it. :)

oh neat! is this part of the OpenAPI Specification?

Yes, it is. :) Path items can have “an alternative server array to service all operations in this path.”
https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#path-item-object


Problems using redux-form

I'm having problems adding redux-form(redux-form": "6.7.0") as a reducer. Tried it on react-boilerplate which the boilerplate is forked from and it works fine.
after adding
+import { reducer as form } from 'redux-form/immutable';
return combineReducers({
export default function createReducer(asyncReducers: Redux.ReducersMapObject = {}): Redux.Reducer<any> {
  const reducers = {
    route: routeReducer,
    global: globalReducer,
    language: languageProviderReducer,
    + form
    ...asyncReducers,
  };

  return combineReducers(reducers);
}

to reducers.ts
The error I'm getting

I've tried removing the react-hot-loader and different versions of redux-immutable

Your snippet has some syntax issues
+import

+ form

return combineReducers({ export default

If you have an example repo I could take a look at that

My bad, it was supposed to look like a git diff.
Added an example repo https://github.com/affemaen/react-typescript-boilerplate
It combines the form reducer.

Did you still need assistance with this? I should have time this weekend to look it over

Managed a workaround by setting and alias for immutable so that redux-form uses the correct import of immutable.
Seems to be issues with not using the latest version of react-hot-loader. Have to export the form as a prop for a workaround. I don't have access to the code at the moment but I'll post an example later if more people are having problems.


adding currentContext to Routemaster

current context was added to Routemaster and RoutemasterDeletate so we have access to the current context,
an example code of how to use it was added to 'add a new wishlist' button in book store example

Does this PR is gonna be merged? the navigator key is gonna be helpful to everyone 😄

Hi @Crdzbird, sorry, haven't had time to look at it yet; have been very busy. Will get to it as soon as possible. Thanks for the PR.


Container console rendering issues

The container console has weird black lines between each terminal line:

I'm using Portainer 1.14.3 and Google Chrome (Firefox is the same) that is running on Ubuntu 17.04 (this also happens on Windows Server 2016).

Hey @rgl
I notice this myself when using Windows containers. I cannot reproduce this on Linux containers. Can you confirm this?

I just tried on my rgl/docker-swarm-cluster-ubuntu-vagrant and it has the same problem (I used a bash the script to show colors):

@rgl got a container that I could re-use to do some tests?

@deviantony sorry, what container do you mean/want?

Oh don't worry, I was able to reproduce this using the one liner:
for x in {0..8}; do for i in {30..37}; do for a in {40..47}; do echo -ne "\e[$x;$i;$a""m\\\e[$x;$i;$a""m\e[0;37;40m "; done; echo; done; done; echo ""


resolve security dependencies. (#4497)

Pull request opened by the merge tool on behalf of #4497

Merged in 267c1c1d6e9269985946e043b4f605f5281e6744


Write test for v0.2.2.

Ensure that the state behavior protects the implementing element from mixing-in the state behavior multiple times.  Polymer should deal with this in the future.
See #4 and https://github.com/Polymer/polymer/issues/1894

CC @kevmannn @WilliamSWoodruff this would be a great way to dig into writing tests for Polymer.  A challenging one, I'd say.  If you're interested, I can better explain the fix made in #4.  Totally no pressure!!

I definitely would like to get into writing tests sometime, dunno when I'll be able to give it a shot but I'll keep it in mind

Same. Something that I need to get into. I'll try and remember to check it out this weekend.


Drop in replacement via babel alias possible?

I wonder if instead of rewriting all our imports it would also be possible to do define a babel alias instead like "prereact" does for "react".
Has anybody tried this? @nandorojo

certainly possible. I won't make it a recommendation since they don't export all the same things though. a better suggestion would be to have your own file, like hooks/use-get which re-exports useSWR with your own hook name. I find that it's best to wrap library code into your own centralized file so you can always change the function from one place.

I just tried it, it almost works it just chokes on swr/infinite which is not exported by your lib.
We already have a customised swr hook indeed, I will probably hook it into there.


Fix qemu version in ci

Fixed qemu version in CI code, so that travis check can pass.
Signed-off-by: Hariharan T.S<EMAIL_ADDRESS>

The code was referring to older qemu version ie 5.0 which is been removed. Hence added new version 6.0 to the code.
https://github.com/legoater/qemu/tree/powernv-6.0


Minor error in README.MD?

Hi
Thanks for this - just installed it on my UDMP running UniFi OS 3.2.7. Not fully tested but looking go so far.
I have spotted one small issue - README.MD has an error in 'FIRST RUN' section:
cp /data/udapi-server/raddb/certs/server.pem ./raddb-server.pem
cp /data/udapi-server/raddb/certs/server-key.pem ./raddb-server-key.pem

I believe /data/udapi-server should be /data/udapi-config ?
The code (ubios-cert.env)  does refer to /data/udapi-config though.
# Path to RADIUS server certificate
UBIOS_RADIUS_CERT_PATH='/data/udapi-config/raddb/certs'

Thanks
Pete

Thanks Pete, yes, you're absolutely right! will change that.
Regards Alex

@alxwolf sorry to necro this issue..but I am not so sure that 3.2.7 is so happy with custom certificates.
While I don't use this script specifically (I have a internal CA that I use to generate certificates for my intranet), I do at the very least replace /data/unifi-core/config/unifi-core.crt along with /data/unifi-core/config/unifi-core.key. Upon restarting unifi-core with systemctl restart unifi-core, the OS overwrites my custom certificates, effectively undoing my work.
My setup has been working for months and I never had to mess with keystore or the RADIUS config (raddb). I am trying to reach out to anyone who might know more.

Oh, thanks for bringing this up. Then this will require some more investigation than anticipated...


Improve a bit the performances of CoverageData.arcs()

When there is no context id, there is no need
to use a distinct query, since there is already
a distinct constrain in the declaration on the table
involving fromno, tono, fileid and contextid, with
contextid being a constant in our case.
This simplifies the query, and improve a bit the performances:
sqlite> .explain
sqlite> explain select distinct fromno, tono from arc where file_id = 6;
addr  opcode         p1    p2    p3    p4             p5  comment
----  -------------  ----  ----  ----  -------------  --  -------------
0     Init           0     14    0                    00  Start at 14
1     OpenEphemeral  1     0     0     k(2,B,B)       08  nColumn=0
2     OpenRead       2     12    0     k(5,,,,,)      02  root=12 iDb=0; sqlite_autoindex_arc_1
3     Integer        6     1     0                    00  r[1]=6
4     SeekGE         2     13    1     1              00  key=r[1]
5       IdxGT          2     13    1     1              00  key=r[1]
6       Column         2     2     2                    00  r[2]=arc.fromno
7       Column         2     3     3                    00  r[3]=arc.tono
8       Found          1     12    2     2              00  key=r[2..3]
9       MakeRecord     2     2     4                    00  r[4]=mkrec(r[2..3])
10      IdxInsert      1     4     2     2              10  key=r[4]
11      ResultRow      2     2     0                    00  output=r[2..3]
12    Next           2     5     0                    00
13    Halt           0     0     0                    00
14    Transaction    0     0     7     0              01  usesStmtJournal=0
15    Goto           0     1     0                    00
sqlite> explain select  fromno, tono from arc where file_id = 6;
addr  opcode         p1    p2    p3    p4             p5  comment
----  -------------  ----  ----  ----  -------------  --  -------------
0     Init           0     10    0                    00  Start at 10
1     OpenRead       1     12    0     k(5,,,,,)      02  root=12 iDb=0; sqlite_autoindex_arc_1
2     Integer        6     1     0                    00  r[1]=6
3     SeekGE         1     9     1     1              00  key=r[1]
4       IdxGT          1     9     1     1              00  key=r[1]
5       Column         1     2     2                    00  r[2]=arc.fromno
6       Column         1     3     3                    00  r[3]=arc.tono
7       ResultRow      2     2     0                    00  output=r[2..3]
8     Next           1     4     0                    00
9     Halt           0     0     0                    00
10    Transaction    0     0     7     0              01  usesStmtJournal=0
11    Goto           0     1     0                    00
sqlite>

Thanks! But there's one test failure to deal with:
=================================== FAILURES ===================================
___________________ CoverageDataTest.test_no_duplicate_arcs ____________________
[gw1] linux -- Python 3.7.1 /home/travis/build/nedbat/coveragepy/.tox/py37/bin/python
self = <tests.test_data.CoverageDataTest testMethod=test_no_duplicate_arcs>
    def test_no_duplicate_arcs(self):
        covdata = CoverageData()
        covdata.set_context("context1")
        covdata.add_arcs(ARCS_3)
        covdata.set_context("context2")
        covdata.add_arcs(ARCS_3)
>       self.assertEqual(covdata.arcs('x.py'), X_PY_ARCS_3)
E       AssertionError: Lists differ: [(-1, 1), (1, 2), (2, 3), (3, -1), (-1, 1), (1, 2), (2, 3), (3, -1)] != [(-1, 1), (1, 2), (2, 3), (3, -1)]
E
E       First list contains 4 additional elements.
E       First extra element 4:
E       (-1, 1)
E
E       - [(-1, 1), (1, 2), (2, 3), (3, -1), (-1, 1), (1, 2), (2, 3), (3, -1)]
E       + [(-1, 1), (1, 2), (2, 3), (3, -1)]
tests/test_data.py:229: AssertionError

tox is taking ages to run on my laptop :/
Did I misread the code? I had the impression that contextid was a constant :/

Codecov Report

Merging #910 into master will decrease coverage by 8.54%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #910      +/-   ##
==========================================
- Coverage   94.09%   85.54%   -8.55%
==========================================
  Files          86       86
  Lines       12047    12027      -20
  Branches     1204     1203       -1
==========================================
- Hits        11336    10289    -1047
- Misses        576     1584    +1008
- Partials      135      154      +19

Impacted Files
Coverage Δ

coverage/sqldata.py
92.2% <100%> (-0.42%)
:arrow_down:

tests/plugin2.py
0% <0%> (-62.97%)
:arrow_down:

tests/test_plugins.py
50.25% <0%> (-48.97%)
:arrow_down:

tests/test_api.py
61.55% <0%> (-37.52%)
:arrow_down:

tests/test_context.py
64.73% <0%> (-35.27%)
:arrow_down:

tests/test_oddball.py
67.4% <0%> (-32.6%)
:arrow_down:

tests/test_debug.py
69.72% <0%> (-28.45%)
:arrow_down:

tests/test_xml.py
73% <0%> (-27%)
:arrow_down:

tests/test_coverage.py
73.72% <0%> (-25.92%)
:arrow_down:

tests/test_html.py
73.72% <0%> (-25.9%)
:arrow_down:

... and 21 more

Continue to review full report at Codecov.

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

I don't know how you are profiling these changes to see if they are improvements, but I think letting SQLite do the work will be better than doing it in Python.

Yeah, it doesn't make a bug difference :/


Cannot connect to device

I just finished installing adb system wide on Windows 10 and can run adb version and it populates. I can also connect the device (Fire TV Edition) to adb and initiate commands. Homebridge is seeing the Fire TV but says it cant connect and therefore not showing up in Homekit. The popup even came up on the tv and I pressed accept.

See attached photos. Thanks!

Just making sure. If you type adb devices in your command prompt, does it show list of devices that are currently connected?
What’s the result if you type this command: adb -s your-ip-address shell “dumpsys power | grep mHoldingDisplay | cut -d = -f 2“, that command will check if your device screen is on or off, so it should return true or false.

Adb devices does show my device. I did also want to say that if I connect my device manually using cmd before starting homebridge that the plugin when booting seems to disconnect the adb device if that makes sense!

It seems that your ADB work properly. I think I knew the problem, I modified the script a little bit and update the plugins, please try and see the result.

Working great now.  Thanks so much for this plugin!


I did what you tell us in README.md, but still have this error

/usr/local/include/boost/core/noncopyable.hpp(42): error: defaulted default constructor cannot be constexpr because the corresponding implicitly declared default constructor would not be constexpr
1 error detected in the compilation of "/tmp/tmpxft_00002420_00000000-6_nms_kernel.cu.cpp1.ii".
concurrent.futures.process._RemoteTraceback:
"""
Traceback (most recent call last):
File "/home/lab1028/jason/pytorch_pointpillars-master/second.pytorch/second/core/non_max_suppression/nms_cpu.py", line 10, in
from second.core.non_max_suppression.nms import (
ModuleNotFoundError: No module named 'second.core.non_max_suppression.nms'
During handling of the above exception, another exception occurred:
You did really good work!!!!!! I hope if you have met this before and I'm very grateful to you!!!!!

/usr/local/include/boost/core/noncopyable.hpp(42): error: defaulted default constructor cannot be constexpr because the corresponding implicitly declared default constructor would not be constexpr
1 error detected in the compilation of "/tmp/tmpxft_00002420_00000000-6_nms_kernel.cu.cpp1.ii".
concurrent.futures.process._RemoteTraceback:
"""
Traceback (most recent call last):
File "/home/lab1028/jason/pytorch_pointpillars-master/second.pytorch/second/core/non_max_suppression/nms_cpu.py", line 10, in
from second.core.non_max_suppression.nms import (
ModuleNotFoundError: No module named 'second.core.non_max_suppression.nms'
During handling of the above exception, another exception occurred:
You did really good work!!!!!! I hope if you have met this before and I'm very grateful to you!!!!!

/home/lab1028/anaconda3/envs/pointpillars/lib/python3.7/site-packages/dask/config.py:168: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
data = yaml.load(f.read()) or {}
nvcc -std=c++11 -c -o ../cc/nms/nms_kernel.cu.o ../cc/nms/nms_kernel.cu.cc -I/usr/local/cuda/include -x cu -Xcompiler -fPIC -arch=sm_61 --expt-relaxed-constexpr
/usr/local/include/boost/core/noncopyable.hpp(42): error: defaulted default constructor cannot be constexpr because the corresponding implicitly declared default constructor would not be constexpr
1 error detected in the compilation of "/tmp/tmpxft_000030cb_00000000-6_nms_kernel.cu.cpp1.ii".
concurrent.futures.process._RemoteTraceback:
"""
Traceback (most recent call last):
File "/home/lab1028/jason/pytorch_pointpillars-master/second.pytorch/second/core/non_max_suppression/nms_cpu.py", line 13, in
from second.core.non_max_suppression.nms import (
ModuleNotFoundError: No module named 'second.core.non_max_suppression.nms'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/lab1028/anaconda3/envs/pointpillars/lib/python3.7/concurrent/futures/process.py", line 232, in _process_worker
r = call_item.fn(*call_item.args, **call_item.kwargs)
File "/home/lab1028/anaconda3/envs/pointpillars/lib/python3.7/concurrent/futures/process.py", line 191, in _process_chunk
return [fn(*args) for args in chunk]
File "/home/lab1028/anaconda3/envs/pointpillars/lib/python3.7/concurrent/futures/process.py", line 191, in
return [fn(*args) for args in chunk]
File "/home/lab1028/jason/pytorch_pointpillars-master/second.pytorch/second/utils/buildtools/command.py", line 255, in compile_func
raise RuntimeError("compile failed with retcode", ret.returncode)
RuntimeError: ('compile failed with retcode', 1)
"""
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "train.py", line 16, in
from second.builder import target_assigner_builder, voxel_builder
File "/home/lab1028/jason/pytorch_pointpillars-master/second.pytorch/second/builder/target_assigner_builder.py", line 3, in
from second.core.target_assigner import TargetAssigner
File "/home/lab1028/jason/pytorch_pointpillars-master/second.pytorch/second/core/target_assigner.py", line 1, in
from second.core import box_np_ops
File "/home/lab1028/jason/pytorch_pointpillars-master/second.pytorch/second/core/box_np_ops.py", line 7, in
from second.core.non_max_suppression.nms_gpu import rotate_iou_gpu_eval
File "/home/lab1028/jason/pytorch_pointpillars-master/second.pytorch/second/core/non_max_suppression/init.py", line 1, in
from second.core.non_max_suppression.nms_cpu import nms_jit, soft_nms_jit
File "/home/lab1028/jason/pytorch_pointpillars-master/second.pytorch/second/core/non_max_suppression/nms_cpu.py", line 21, in
cuda=True)
File "/home/lab1028/jason/pytorch_pointpillars-master/second.pytorch/second/utils/buildtools/pybind11_build.py", line 113, in load_pb11
cmds, cwd, num_workers=num_workers, compiler=compiler)
File "/home/lab1028/jason/pytorch_pointpillars-master/second.pytorch/second/utils/buildtools/command.py", line 277, in compile_libraries
if any([r.returncode != 0 for r in rets]):
File "/home/lab1028/jason/pytorch_pointpillars-master/second.pytorch/second/utils/buildtools/command.py", line 277, in
if any([r.returncode != 0 for r in rets]):
File "/home/lab1028/anaconda3/envs/pointpillars/lib/python3.7/concurrent/futures/process.py", line 476, in _chain_from_iterable_of_lists
for element in iterable:
File "/home/lab1028/anaconda3/envs/pointpillars/lib/python3.7/concurrent/futures/_base.py", line 586, in result_iterator
yield fs.pop().result()
File "/home/lab1028/anaconda3/envs/pointpillars/lib/python3.7/concurrent/futures/_base.py", line 425, in result
return self.__get_result()
File "/home/lab1028/anaconda3/envs/pointpillars/lib/python3.7/concurrent/futures/_base.py", line 384, in __get_result
raise self._exception
RuntimeError: ('compile failed with retcode', 1)

I have solved the problem by

I have solved the problem by  change the  /second.pytorch/second/core/cc/nms/nms_kernel.cu.cc    //#include <boost/geometry.hpp>   Thanks very much for your code

I have solved the problem by change the /second.pytorch/second/core/cc/nms/nms_kernel.cu.cc //#include <boost/geometry.hpp> Thanks very much for your code

could u tell me how to solve this problem?  i dont know how to deal with the nms_kernel.cu.cc

修饰掉//#include <boost/geometry.hpp>
On 03/11/2020 17:37, Donghui Ma wrote:
I have solved the problem by change the /second.pytorch/second/core/cc/nms/nms_kernel.cu.cc //#include <boost/geometry.hpp> Thanks very much for your code
could u tell me how to solve this problem? i dont know how to deal with the nms_kernel.cu.cc
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.

修饰掉//#include <boost/geometry.hpp> On 03/11/2020 17:37, Donghui Ma wrote: I have solved the problem by change the /second.pytorch/second/core/cc/nms/nms_kernel.cu.cc //#include <boost/geometry.hpp> Thanks very much for your code could u tell me how to solve this problem? i dont know how to deal with the nms_kernel.cu.cc — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.

/tmp/tmpxft_00002ff3_00000000-5_nms_kernel.cu.cudafe1.stub.c: In function ‘void __device_stub__Z10nms_kernelIfLi64EEviT_PKS0_Py(int, float, const float*, long long unsigned int*)’:
/tmp/tmpxft_00002ff3_00000000-5_nms_kernel.cu.cudafe1.stub.c:11:148: error: ‘__args_arr’ was not declared in this scope
ernelIfLi64EEviT_PKS0_Py(const int __par0, const float __par1, const float *__par2, unsigned long long *__par3){__cudaSetupArgSimple(__par0, 0UL);__cudaSetupArgSimple(__par1, 4UL);__cudaSetupArgSimple(__par2, 8UL);__cudaSetupArgSimple(__par3, 16UL);__cudaLaunch(((char *)((void ( *)(const int, const float, const float *, unsigned long long *))nms_kernel<float, (int)64> )));}
^
/tmp/tmpxft_00002ff3_00000000-5_nms_kernel.cu.cudafe1.stub.c:11:148: error: ‘__args_idx’ was not declared in this scope
ernelIfLi64EEviT_PKS0_Py(const int __par0, const float __par1, const float *__par2, unsigned long long *__par3){__cudaSetupArgSimple(__par0, 0UL);__cudaSetupArgSimple(__par1, 4UL);__cudaSetupArgSimple(__par2, 8UL);__cudaSetupArgSimple(__par3, 16UL);__cudaLaunch(((char *)((void ( *)(const int, const float, const float , unsigned long long ))nms_kernel<float, (int)64> )));}
^
/tmp/tmpxft_00002ff3_00000000-5_nms_kernel.cu.cudafe1.stub.c: In function ‘void __device_stub__Z10nms_kernelIdLi64EEviT_PKS0_Py(int, double, const double, long long unsigned int)’:
/tmp/tmpxft_00002ff3_00000000-5_nms_kernel.cu.cudafe1.stub.c:13:150: error: ‘__args_arr’ was not declared in this scope
nelIdLi64EEviT_PKS0_Py(const int __par0, const double __par1, const double *__par2, unsigned long long *__par3){__cudaSetupArgSimple(__par0, 0UL);__cudaSetupArgSimple(__par1, 8UL);__cudaSetupArgSimple(__par2, 16UL);__cudaSetupArgSimple(__par3, 24UL);__cudaLaunch(((char *)((void ( *)(const int, const double, const double *, unsigned long long *))nms_kernel<double, (int)64> )));}
^
/tmp/tmpxft_00002ff3_00000000-5_nms_kernel.cu.cudafe1.stub.c:13:150: error: ‘__args_idx’ was not declared in this scope
nelIdLi64EEviT_PKS0_Py(const int __par0, const double __par1, const double *__par2, unsigned long long *__par3){__cudaSetupArgSimple(__par0, 0UL);__cudaSetupArgSimple(__par1, 8UL);__cudaSetupArgSimple(__par2, 16UL);__cudaSetupArgSimple(__par3, 24UL);__cudaLaunch(((char *)((void ( *)(const int, const double, const double *, unsigned long long *))nms_kernel<double, (int)64> )));}
^
concurrent.futures.process._RemoteTraceback:
"""
Traceback (most recent call last):
File "/home/mdh/lidar_SLAM_Algorithm/nutonomy_pointpillars/second/core/non_max_suppression/nms_cpu.py", line 10, in
from second.core.non_max_suppression.nms import (
ImportError: libcudart.so.9.0: cannot open shared object file: No such file or directory
出现了新的错误。。。。

修饰掉//#include <boost/geometry.hpp> On 03/11/2020 17:37, Donghui Ma wrote: I have solved the problem by change the /second.pytorch/second/core/cc/nms/nms_kernel.cu.cc //#include <boost/geometry.hpp> Thanks very much for your code could u tell me how to solve this problem? i dont know how to deal with the nms_kernel.cu.cc — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.

thank u! I have solved this problem.


Updated jsdoc to conform to the jsdoc optional parameters

Current jsdoc was not valid and IDEs reported the function lock.acquire to require 4 parameters instead of 2 + 2 optionals.

+1

Hi @JonathanPicques , @Philipp91.
Because the author does not respond, the folks at npmjs.org have transferred ownership of async-lock to me. The new repo is at https://www.github.com/rogierschouten.
I have incorporated this PR and will do a release soon (which will likely get a major version increase, so you will have to actively upgrade). You can consider this PR as merged.


Add copy button to the code blocks in docs

Update the mkdocs.yml to add a copy button to the code blocks in the documentation.
Ref: https://squidfunk.github.io/mkdocs-material/reference/code-blocks/#code-copy-button

Can I work on this?


Allow spin add to add variables to the manifest

Syntax:
// spin-template.toml
[add_component]
[add_component.snippets]
variables = "variables.txt"

// snippets/variables.txt
secret = { required = true }
url = { default = "{{ service-url }}" }

Questions:

Should the variables be merged into component.txt?  Splitting them makes it easier to implement because we don't need to analyse which bits of the snippet need to be merged and which appended - we can instead use the snippet key to infer the semantics.
Should variables.txt include the [variables] header?  It is not needed for the implementation but component.txt has it so maybe for consistency?
If the manifest being added to already has a variable with the same name as one given in the snippet, the one from the snippet takes precedence.  Do we just need to document this, or do we need to ask the user if we are about to change an existing value?  (The danger being that the user may not know how to decide.)

Should the variables be merged into component.txt? Splitting them makes it easier to implement because we don't need to analyse which bits of the snippet need to be merged and which appended - we can instead use the snippet key to infer the semantics.

+1 to keeping them separate files. Separate files seems more flexible especially when you consider overlapping sets of variables declarations shared across components.

Should variables.txt include the [variables] header? It is not needed for the implementation but component.txt has it so maybe for consistency?

As much as I love consistency, it would seem like adding the variables header would require some extra processing complexity to merge the contents of each snippet section into a singular variables section (which isn't the absolute worst)? I think I would lean towards omitting the variables header from the snippet unless it is really compelling to others.

If the manifest being added to already has a variable with the same name as one given in the snippet, the one from the snippet takes precedence. Do we just need to document this, or do we need to ask the user if we are about to change an existing value? (The danger being that the user may not know how to decide.)

I would vote to document plus a warning that a previously defined variable is going to be overwritten.  I think the more concerning question is how does a developer reconcile these conflict?

If accepting the overwriting then a component previously wired up to that variable may misbehave.
If not, then is one simply forced to not use the target of add_component (which obviously is the worst experience).

Apologies if i'm missing something obvious or this isn't the place to raise this question!

Okay I'm going to merge this and we can iterate on conflict behaviour


Can't connect to HTTPS sites on 10.10.3 (Yosemite)

Hi. I'm not sure what the underlying issue is, and what is causing it, but it seems like changes in 10.10.3 have affected browser integration tools like Poltergeist, PhantomJS(?), and Qt.
In my project, I have an RSpec test that checks that Google Translate is translating the page. This test passes on OS X 10.10.2 and on Linux (Travis and Vagrant running Ubuntu 14.04), but upgrading to OS X 10.10.3 causes the test to fail, with no other changes.
I inspected the network traffic in one of the specs by adding this line:
puts page.driver.network_traffic.map { |t| [t.response_parts.last.status, t.response_parts.last.url] }

I noticed that all of the calls made during the tests are over HTTP, except for two calls over HTTPS to https://translate.googleapis.com/translate_static/css/translateelement.css and https://translate.googleapis.com/translate_static/js/element/main.js. All of the HTTP calls have a status associated with them, either 200 or 304. However, both of the HTTPS calls have no status at all. Here is an excerpt from the output:
304
http://www.lvh.me:62028/assets/util/geolocation/geolocate-action.js
200
http://translate.google.com/translate_a/element.js?cb=GoogleTranslate.googleTranslateElementInit
200
http://fonts.gstatic.com/s/quattrocentosans/v8/efd6FGWWGX5Z3ztwLBrG9c2kigAIKUS7C8wDj9A45hI.ttf
200
http://fonts.gstatic.com/s/quattrocentosans/v8/tXSgPxDl7Lk8Zr_5qX8FIWAK5Gcw6LbjBo2-NRTaHPD3rGVtsTkPsbDajuO5ueQw.ttf
200
http://www.lvh.me:62028/assets/fontawesome-webfont.ttf?v=4.3.0

https://translate.googleapis.com/translate_static/css/translateelement.css

https://translate.googleapis.com/translate_static/js/element/main.js

On the capybara-webkit repo, someone mentioned that using protocol agnostic URLs fixed the issue for them. Unfortunately, those HTTPS calls are not instantiated directly from my app, so I can't change them.
Any ideas what might be going on here and how to fix it? Is this a PhantomJS issue?

To prove that this is an HTTPS issue, I changed my protocol agnostic font urls from //fonts.googleapis.com/css?family=Libre+Baskerville:400,700 to https://fonts.googleapis.com/css?family=Libre+Baskerville:400,700, and when I run the test again, the network requests to the HTTPS fonts URLs now have a status of nil whereas before, they were returning 200.

Here are some PhantomJS issues that might possibly be related: https://github.com/ariya/phantomjs/issues/12790
https://github.com/ariya/phantomjs/issues/12746
Is there any way to check for SSL handshake errors in Poltergeist?

I just noticed the phantom_js options! Adding phantomjs_options: ['--ignore-ssl-errors=yes'] fixed the issue. Feel free to close this if that is the expected thing to do in this case.

@monfresh I also recall getting caught out on that about a year ago; that is indeed the 'trick'.  This issue should be closed.


manpage, and a make install target, and a makefile

are these things planned? they'll make packaging it for debian much easier:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858622

Hi, there's already a makefile, can you submit a PR to add an install target to it ?
There's no manpage planned either...


Migrate to Github Actions

We should migrate pAPRika to GHA for CI and retire Travis CI. @mattwthompson can we get your help with this?

Thank you @mattwthompson for getting this done.


source.tag versus source.branch fields in rockspecs?

I'm trying to install a rock using the following rockspec:
package = 'tapered'
version = '1.0-1'
source = {
    url = 'git+https://bitbucket.org/telemachus/tapered.git',
    tag = '1.0-1'
}
description = {
    homepage = 'https://bitbucket.org/telemachus/tapered',
    summary = 'Very minimal tap testing for Lua.',
    detailed = [[
	Very minimal tap testing for Lua. Arguably too minimal.
    ]],
    license = 'BSD 3-Clause',
    maintainer = 'Peter Aronoff<EMAIL_ADDRESS>}
dependencies = {
    'lua >= 5.1'
}
build = {
    type = 'builtin',
    modules = { tapered = 'src/tapered.lua' },
    copy_directories = { 'doc' }
}

My problem is that adding the source.tag field causes luarock to issue this command:
git clone -- --branch=1.0-1 https://bitbucket.org/telemachus/tapered.git tapered

That in turn leads git to fail, complaining "Too many arguments." (Full output of the attempted install with --verbose gisted here.)
My question is: Why does source.tag work this way? I would expect that outcome for source.branch instead. For git, to checkout a tag, you first need to cd into the target directory and then run git checkout <tag>.

--branch accepts tags since git 1.7.10, the issue is that --branch option is inserted after --, not before, hence git thinks it's another argument.

@mpeterv I didn't realize that change in git. Thanks for clarifying.
Still, I wonder what luarocks should do. Maybe it's safer to cd since that behavior works for any version of git?

Yes. It seems that the git+http protocol is the culprit here. Could you try with  url = 'https://bitbucket.org/telemachus/tapered.git'

@ignacio That didn't seem to work for me. It led luarocks to use wget as I recall. I can try again though.

@ignacio Unfortunately if I remove 'git+', then luarocks tries to use curl and things go badly:
$ brewdo do luarocks install --verbose tapered-1.0-1.rockspec
Using tapered-1.0-1.rockspec... switching to 'build' mode

os.execute: 	'curl' -k -f -L --user-agent 'LuaRocks/2.2.2 macosx-x86_64 via curl' --connect-timeout 30 'https://bitbucket.org/telemachus/tapered.git' 2> /dev/null 1> '/private/tmp/luarocks_luarocks-source-tapered-1.0-1-5801/tapered.git'
Results: 3
  1 (boolean): true
  2 (string): exit
  3 (number): 0

Error: Directory tapered not found inside archive tapered.git

@telemachus luarocks checks git version, e.g. on my machine it uses separate checkout command because I have git 1.7.9.
I think the easiest fix is to change 4 to 3 in table.insert(command, 4, "--branch=" .. tag_or_branch) in luarocks.fetch.git module

@mpeterv And that's what I get for not checking the source code! Thanks again.

@telemachus Ok, I'll look into it.
@mpeterv I think that it is not that easy. The number of arguments seems to change whether you're using git:// or git+http(s):// protocols. I also look into that.

@ignacio http or https protocols can't be used for cloning because curl or wget will simply return some html from the project page, so that error is not an issue.

@mpeterv is that a BitBucket thing, right?

@mpeterv I wondered about this as well. If the url ends in .git, I was surprised that curl or wget was chosen for download instead of git.
@ignacio What do you mean by "that" being a Bitbucket thing? Not sure I follow.

@ignacio maybe you mean using 'git' protocol, not 'https'?

Sorry for the delay.
Yes, @mpeterv that's what I wanted to say.
@telemachus The original trouble you had (on Twitter) was related to using url = "https://blabla.git", right?  I wonder if we can (safely) issue a warning when http(s) points to a .git repository.

@ignacio I think so, but I'm not sure. I had a lot of trouble, and I kept trying different values for source.url and other fields to fix things. I was trying following this guide, but it doesn't mention the 'git+http{s}' options. (I found those later when googling.)
I'm not really sure whether I was confused or if the documentation is confusing—or both! I'll read over it again when I can and maybe submit some ideas for clarifications there. In any case, thanks both of you for your help.

Makes sense. Since you use Bitbucket, do you know if the same applies to Mercurial repos?

@ignacio I must be one of the few, but although I use Bitbucket, I never use Mercurial. So I'm not sure. Sorry.

I was trying following this guide, but it doesn't mention the 'git+http{s}' options. (I found those later when googling.)

That's because those options are recent additions that don't work on older LuaRocks versions (git+http doesn't work before 2.2.0, git+https doesn't work before 2.2.2). This is one of the few cases (the only case?) where Hisham let incompatible changes slip through ...

@siffiejoe Fair enough. I suppose for earlier versions of LuaRocks then, the easiest thing on Bitbucket is to upload a tar.gz file (which is what I did initially). Unlike GitHub, Bitbucket doesn't provide git:// as a protocol; only ssh:// and https:// are available.

This is one of the few cases (the only case?) where Hisham let incompatible changes slip through ...

Yes, I made an exception for fetch protocols because these fail with a nice error message saying that "git+https is an unsupported protocol". Consider this a point where LuaRocks 2 is "extensible". The other point is build types, where you can come up with any build.type="foo" as long as a module luarocks.build.foo exists (and it can even be fetched via a dependency).

So if I followed correctly the problem was that --branch was inserted in the wrong place. Did #410 fix it? Can we close this one?

Yes, 410 fixed it. Didn't close this one because I thought about adding what @telemachus suggested here: https://github.com/keplerproject/luarocks/issues/409#issuecomment-120524244
What do you think?

I'd skip that for now. It would break the mapping between protocol:// and luarocks.fetch.protocol module...

Oh, right. Closing then.


Error on 4.3.0 RC wallet on win 7x32

I'm getting this error on wallet 4.3.0 version rc

Did you do any special action on the wallet before this started happening? Like adding or removing something from the config file (Navtech servers, proposals, etc.)?

No special action on wallet.just installed on top of 4.2.1 wallet.I attach debug file if it help you.I see that conf file has only a word in it:''undefined''.
debug.log


1.10 new updates

Tardy PR to merge master to 1.10 branch

Need to make a cleaner PR than this one. Learning experiences ftw.


Is inline javascript supported by this package

Would it be possible to add to the package whether javascript outside of a js file is supported?
Like the javascript between 2 script tags?

Could you please explain? Not sure to understand.

Came here looking for this too. I needed something to remove console.log statements from within script tags inside .html files, not .js files.
This doesn't seem to quite work and it ended out stripping out too much, It turned this:
      if(mraid.getState() === 'loading') {
        console.log('mraid.getState is loading, setting up ready event listener')

        mraid.addEventListener("ready", () => tryLaunching({ launchGame: true }));
      } else if (mraid.getState() === 'default') {
        console.log('mraid.getState is default, attempting to launch playable')

        tryLaunching({ launchGame: true });
      }

Into this and actually removed everything in the if/else blocks:
      if(mraid.getState() === 'loading') {
        0;
      } else if (mraid.getState() === 'default') {
        0;
      }

I also had to at least add replaceWith='0;' as an option, or it created problematic stuff like this:
      } else

      startApp();
      launched = true;

...if you had a dangling else:
      } else
        console.log('Skipping MRAID orientation properties before launch attempt');


Adding docs for Output Label Options

Can you also add a note about which versions of aryn-sdk and sycamore you need for this feature? For aryn-sdk, you need 0.1.10. No version of sycamore on pypi currently support the feature (Henry is still working on releasing it).

Can you also add a note about which versions of aryn-sdk and sycamore you need for this feature? For aryn-sdk, you need 0.1.10. No version of sycamore on pypi currently supports the feature (Henry is still working on releasing it).

A version of sycamore with this feature has now been released. It's 0.1.28.


Add exercise for header

Explain header.
Get via headerhash,
extend analogy of boxes and labels and barcodes

[x] write text
[x] add playground item to do a simulation
[x] add exercise in zome

Simplified Header chapter and exercises


List recurent task with queries

Expected Behavior
When I use the task filters, the tasks must be show if they meet the due date conditions, although they are tagged with recurrence.
Current Behavior
When use filters to list tasks in a time window, the recurrent tasks are not show.
Steps to Reproduce
I have the following task:
Description: meeting @joe
Recurrence: every month on Thursday
Due: 2022-09-06
Also, I have a note with the following filters:
not done
due after yesterday
due before in four weeks

To date, this task is not shown. Trying different experiments, the following code shows the task:
is recurring
due after yesterday

but not when it's modified to:
is recurring
due after yesterday
due before in four weeks

I think that my original setting:
not done
due after yesterday
due before in four weeks

must show the recurrent tasks also. Am I wrong with my configuration?
Context (Environment)

Obsidian version: 0.14.6
Tasks version: 1.5.1
[ ] I have tried it with all other plugins disabled and the error still occurs

I can reproduce the behaviour and it is as intended.
Here is the task I created, to match your description:
- [ ] meeting with @joe 🔁 every month on Thursday 📅 2022-09-06

With this tasks block, I get 0 tasks, as you say:
```tasks
not done
due after yesterday
due before in four weeks
```

When I comment out due before in four weeks, the task is found.
This is because the due date of your task is 6th September 2022, which is more than 4 weeks away.
The dates are YYYY-MM-DD. Is it possible you meant to type 2022-06-09?
If this doesn't solve your problem, please paste in your actual task and query.


Network and refactoring

This PR contains:

Order creation
Dio implementation
CRUD calls config without TLS/SSL

GJ merging


Create Book “2024-02-08/index-1”

Automatically generated by Netlify CMS

👷 Deploy Preview for comforting-lamington-e443cb processing.

Name
Link

🔨 Latest commit
96f03bb7f5a37ad1739f68aaa2403361aa0c3458

🔍 Latest deploy log
https://app.netlify.com/sites/comforting-lamington-e443cb/deploys/65c583d5f186720008f2b3ca


[triplets] New triplets <arch>-linux-clang

Add a new triplet for Linux and Clang compiler.
Environment

OS: Linux
Compiler: Clang

https://github.com/microsoft/vcpkg/issues/36351#issue-2098881163

It would be really nice to have support for clang on Linux triplet. Especially since it already supported for macos

+1 for this.  I also would like to be able to use clang as an alternative to gcc on Linux.

My variation on this:

Toolchain file: linux-clang.cmake
# Copied and adapted from:
# https://github.com/microsoft/vcpkg/blob/7adc2e4d49e8d0efc07a369079faa6bc3dbb90f3/scripts/toolchains/linux.cmake
#
# The original seems to be written only for GCC.    Worked great!  The other target branches are untested.  I confirmed it's indeed using / picking up all the different LLVM tools: clang, lld linker, llvm-ar librarian and other binary tools, etc.
Note use of CMAKE_LINKER_TYPE which requires recent CMake release 3.29.
Not sure what would be desired upstream... the toolchain file is basically the same as the vcpkg Linux one, but with some minor tweaks as noted in the comments above.  Feels like the behavior could be controlled in the same Linux toolchain file but via some new VCPKG variables?  Windows has a variety of variables to control version of Visual C++ compiler chosen.  Linux does not seem to offer anything similar.  (Looking at https://learn.microsoft.com/en-us/vcpkg/users/triplets ).  I imagine it could take the form of some triplet variables where the user can specify the compiler / linker they want to use?


⚠ Bofrost.at has degraded performance

In cc0bff9, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1188 ms

Resolved: Bofrost.at performance has improved in 94242f3 after 32 minutes.


iPad issue: Background images did not changed.

Background images did not changed when admin changed backgrounds (i'm guest).
////////CONTRIBOARD TESTING, 24.7.2015////////
Contriboard (SUT) versions:
Client version v1.2.100
API version v0.4.38
IMG version v0.1.10
Testing environment:
Heli (1 kpl iPad iOS 8.3 (12F69) Flowdock -> Apple web-view)
////////CONTRIBOARD TESTING, 24.7.2015////////

Need to check if throttling the user-activity ping frequency to something like 30 seconds or more has any effect on some of the real time updates missing...

Cannot reproduce, might be related to general API slowness with high loads.

OK Closed now