Error in UNIT test

»	Test.shvarov.csvgenpy.Testcsv	failed
ERROR #5001: Process $zu(115,1) settings changed from 1 to 2 +
ERROR #5001: Process $zu(115,5) settings changed from 0 to 1
Explanation:
%UnitTest.Manager.cls(Cleanup+58): if State("zu115",i)'=$zu(115,i) {
%UnitTest.Manager.cls(Cleanup+59): Set rc=$$$ERROR($$$GeneralError,"Process $zu(115,"i") settings changed from "State("zu115",i)" to "_$zu(115,i))
from $SYSTEM.SQL.Util.GetOption)  on ZU(115,...):
if option="AUTOCOMMIT" { return $zu(115,1) }
if option="SELECTMODE" { return $zu(115,5) }
%Unit.Test.Manager dislikes change of AUTOCOMMIT and SELCTMODE in your Test Class.
I think this is pure NONSENSE and should be ignored

It looks like it is a bug in embedded python.
Yes, all the rest works fine
On Mon, 15 May 2023 at 18:14, rcemper @.***> wrote:

» Test.shvarov.csvgenpy.Testcsv failed
ERROR #5001: Process $zu(115,1) settings changed from 1 to 2 +
ERROR #5001: Process $zu(115,5) settings changed from 0 to 1
Explanation:
%UnitTest.Manager.cls(Cleanup+58): if State("zu115",i)'=$zu(115,i) {
%UnitTest.Manager.cls(Cleanup+59): Set
rc=$$$ERROR($$$GeneralError,"Process $zu(115,"i") settings changed from
"State("zu115",i)" to "_$zu(115,i))
from $SYSTEM.SQL.Util.GetOption) on ZU(115,...):
if option="AUTOCOMMIT" { return $zu(115,1) }
if option="SELECTMODE" { return $zu(115,5) }
%Unit.Test.Manager dislikes change of AUTOCOMMIT and SELCTMODE in your
Test Class.
I think this is pure NONSENSE and should be ignored
—
Reply to this email directly, view it on GitHub
https://github.com/evshvarov/csvgen-python/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAVHEPYWT5ZQGH4SJP6SCMDXGI24FANCNFSM6AAAAAAYCIMBZI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Bad test case in TestComplexDateTimes

File : TestComplexDateTimes.py - Function : testDate3ConfusedHourAndYear
        self.assertExpectedResult(
            self.cal.parse('December 30th 23:02', start),
            (datetime.datetime(self.yr
                               if (self.mth < 12 and
                                   self.dy < 30 and
                                   self.hr < 23 and
                                   self.mn < 2)
                               else self.yr + 1,
                               12, 30, 23, 2, 0).timetuple(), 3))

The check for self.yr + 1 doesn't seem right. It always fails if self.mn > 2, irrespective of the current date.
PS:- There are a couple more similar bad tests in the same function.

Hmm I think it's because some flag control the auto-complicated year if the
date is larger/smaller than current date. So this is a small trick to get
over of the side effect of it.
codereverser<EMAIL_ADDRESS>周四19:08写道：

File : TestComplexDateTimes.py - Function : testDate3ConfusedHourAndYear
    self.assertExpectedResult(
        self.cal.parse('December 30th 23:02', start),
        (datetime.datetime(self.yr
                           if (self.mth < 12 and
                               self.dy < 30 and
                               self.hr < 23 and
                               self.mn < 2)
                           else self.yr + 1,
                           12, 30, 23, 2, 0).timetuple(), 3))

The check for self.yr + 1 doesn't seem right. It always fails if self.mn

2, irrespective of the current date.
PS:- There are a couple more similar bad tests in the same function.

—
Reply to this email directly or view it on GitHub
https://github.com/bear/parsedatetime/issues/141.

I was curious about that myself the other night. Did the switch to contexts or my merge for Python v3 break something?

I don't think so. The check to compare two dates is not correct. i.e.
(self.mth < 12 and
self.dy < 30 and
self.hr < 23 and
self.mn < 2)

always fails if say, self.dy = 31  or self.mn = 10 regardless of other values (where technically it should fail only during Dec 30 23:03 - 23:59).
I think it should've been something like
datetime.datetime(self.yr, self.mth, self.dy, self.hr, self.mn) <= datetime.datetime(self.yr, 12, 30, 23, 2)

please do create a pull request with what you feel it should be so we can fix this

Well I get what you are saying for...  Also be fixed in #142.

Thanks!


Impact of bluetooth visibility towards functionality

Android allows to set the visibility of the device. As a standart setting, it is set to invisible and I generally only set it to visible, when first connecting to another device.
Does this setting have any impact on the functionality of the app or can the phone still be contacted by other devices through the app?

As far as I know, the device does not have to be set to visible/discoverable. In addition, the device does not pair but only uses the bluetooth beacon funktion.
Correct me if I'm wrong.
I'm not 100% sure

I assume the same, but this should explicitly be stated in the documentation/FAQ to avoid misunderstandings.

This setting should not impact the functionality of the app, since the app uses Google's API, which is in turn bases on Bluetooth LE (Low Energy). LE and classic Bluetooth are different technologies, so the visibility for classic BT shouldn't matter.

This was answered a very long time ago, so I think we can close this.

Corona-Warn-App Open Source Team


Enable key-rotation

Allow validators to generate a key tofnd key, back-it up, declare as the new "active key", and slowly rotate out the old key (i.e. it'll still be used for old sign sessions, but no longer for new keygens/signs.

We don't want to impose off-chain statefulness on the caller (vald), nor do we want tofnd to maintain any state other than mnemonics.  A concrete plan as per discussion with @milapsheth:

key presence check and sign now also includes a pubkey k in addition to a key id id.  key presence iterates through all mnemonics m, generates the key k' from (m,id), compares with k.  return true if we find a mnemonic that generates k else return false.  sign does similar, but also signs a given message if k is found.
keygen always uses the current "active" mnemonic

If you don't like the inefficiency of iterating keygen over all mnemonics then we introduce statefulness.  Either caller (vald) or tofnd must maintain state about which mnemonics were used to generate which keys.
Mnemonic management

User adds a new mnemonic via similar "import" mechanism (ie. launch tofnd in mnemonic mode).  "import" with activate flag imports the mnemonic (if it doesn't already exist) and sets it to active (if it isn't already).
Delete an existing mnemonic: "import" with delete flag: if the "imported" mnemonic exists and is inactive then delete it, otherwise throw an error
"export" now dumps the whole list of mnemonics, first in the list is active.  (Separate files for each mnemonic?  One mnemonic per line in one file?)

Based on discussion with @ggutoski and @cgorenflo, the proposed design involving axelard/vald/tofnd:

Validators can generate a new mnemonic to perform a "tofnd key rotation" and will be used for future key ids (i.e core key rotations).
tofnd will have a list of mnemonics it can import/store.
tofnd now receives (key_id, pubkey) when signing. From the pubkey, it can determine the mnemonic that should be used for signing.
On vald startup, it queries the node to retrieve a mapping of key ids to pub keys for a given validator. Any key_id not in this mapping will default to the "latest" pubkey of the validator. This way if any key rotations in core are performed, new key ids will always correspond to the latest mnemonic.
axelard exposes the above query.

Note, this design works for multisig. In the threshold case, during signing only the secret key share is needed. The mnemonic is not used at all anyways. During on chain recovery of key shares for threshold schemes, recovery can be performed in a similar way by indexing against a provided pubkey/hash.


Clarification on equality of "Principal": "" vs "Principal" : { "AWS" : "" }

On this page:
https://github.com/awsdocs/iam-user-guide/blob/master/doc_source/reference_policies_elements_principal.md
the following assertion is made:

The following are equivalent:
"Principal": "*"
"Principal" : { "AWS" : "*" }

but isn't "AWS": "*" a subset of "*"? I.e., the Principal can take the form of:

<principal_block> = ("Principal" | "NotPrincipal") : ("*" | <principal_map>)
<principal_map> = { <principal_map_entry>, <principal_map_entry>, ... }
<principal_map_entry> = ("AWS" | "Federated" | "Service") :
    [<principal_id_string>, <principal_id_string>, ...]

The assertion made implies that "AWS": "*" is equivalent to "Federated": "*" or "Service": "*" or "CanonicalUser": "*", which is not true.

I believe that you're correct and they're not equivalent. Here's what I think happens:
"Principal": "" makes the resource publicly available.
"Principal" : { "AWS" : "" } makes the resource available to anyone with an AWS account.
If that's true, then what this is saying is that they are functionally equivalent because if you try to access something and can't, then you create an AWS account and you'll have access.
However, the statement is too vague. I'll check with my engineers and see how we can be more specific.

Another reference to this Principal clarification:
https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-resource-policies-create-attach.html
"If the Principal in the policy is set to "*", other authorization types can be used alongside the resource policy. If the Principal is set to "AWS", authorization will fail for all resources not secured with AWS_IAM authorization, including unsecured resources."

@x.509
start-assessment-run
--assessment-template-arn
[--assessment-run-name ]
[--cli-input-json <%~[§}{"*.@;_"]>]
[--generate-cli-skeleton ]

We have updated the page to provide clarification. Thank you for your feedback!


chore: add MIT license

I just copied the license from our tsconfig repo.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Bug: State header and footer links don't open in new tabs

Also, the "Official website of..." link just relaunches the website. Can we remove this link?

@wrendo can you remind me of the final decision regarding wether these links should open in new tabs or not?

What's the status on this one?


Fix include from ParsedownTest

I wasn't able to run all the tests from ParsedownExtra because of it.

@hkdobrev do you have any thoughts on this?

@erusev I don't have anything else to add other than the comment above. Seems legit.
@greut Could you elaborate more on what problem you have experienced when running parsedown-extra tests? Probably something has changed as it wasn't a problem before?

PHPUnit 5.6.2 by Sebastian Bergmann and contributors.

...........................................................E      60 / 60 (100%)

Time: 53 ms, Memory: 6.00MB

There was 1 error:

1) ParsedownExtraTest::testLateStaticBinding
include(test/TestParsedown.php): failed to open stream: No such file or directory

/srv/http/pouille2/vendor/erusev/parsedown/test/ParsedownTest.php:142
/srv/http/pouille2/vendor/erusev/parsedown/test/ParsedownTest.php:142

ERRORS!
Tests: 60, Assertions: 59, Errors: 1.

The problem occurs when I'm running the parsedown-extra tests from the parsedown-extra directory in the case where parsedown is the parent (sibling).
https://github.com/erusev/parsedown-extra/blob/master/test/bootstrap.php#L3-L5
erusev/parsedown
erusev/parsedown-extra

Thanks!


Clippy

Best viewed commit wise

is there already an issue about upstreaming that & lint to the compiler?

probably no (searched for "needless_borrow" and "label:A-lint borrow" )


XCode error for clang++ --version

Summary:
Although this issue may not deal directly with CmdStan, it is a required step in the installation of CmdStan. When testing if Command Line Tools for XCode were properly installed, an error was thrown even though I followed the instructions on the Cmd Installation guide.
Description:
The command clang++ --version throws the error:
dyld: Library not loaded: @rpath/libLLVM-10.dylib
Referenced from: /Users/jamesonblount/opt/anaconda3/bin/clang++
Reason: image not found
zsh: abort      clang++ --version
Reproducible Steps:
On Mac Terminal, the command "clang++ --version" produces this error.
Current Output:
dyld: Library not loaded: @rpath/libLLVM-10.dylib
Referenced from: /Users/jamesonblount/opt/anaconda3/bin/clang++
Reason: image not found
zsh: abort      clang++ --version
Expected Output:
Current version of clang++
Additional Information:
Provide any additional information here.
Current Version:
v2.27.0

Hey @jb621-star, sorry no one responded on this one. Did you manage to fix the issue on your own?


flutter: move build-support/flutter to flutter directory

Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

What's the reasoning behind?

Yeah and if we do this, will rust and other languages/frameworks be moved out of build-support?

What's the reasoning behind?

Mucho texto:
RFC 140 promotes self-contained package directories and strongly discourages files scattered along the filesystem.
Indeed it explicitly prohibits a by-name package to refer to file paths outside its own directory.
Things like ../../../../pkgs/. . . are not allowed in this new framework.
(By the way, weren't you never trapped by counting how many superdirectories you should navigate in order to reach such files?)
Further, with the advent of both RFCs 140 and 146, the classification-based package hierarchy is deprecated and should be phased out.
Further, and more to the point here, no other files in the whole Nixpkgs call ../../../build-support/flutter except pkgs/development/compilers/flutter/default.nix This is just a one-line diff.

Yeah and if we do this, will rust and other languages/frameworks be moved out of build-support?

Well, why not?
Supposing this is doable, why not?
It is way cleaner and easier to reason about an ecosystem/framework knowing that all its relevant files are concentrated in a single directory tree rather than scattered among a wild, obsolete directory hierarchy.
Further, there are some precedents for this approach (yeah, all mine, it is a bit biased I know):

https://github.com/NixOS/nixpkgs/pull/123859

Especially https://github.com/NixOS/nixpkgs/pull/123859/commits/70a5cbc2987b61e2c964c3390cffcedf394de1ad

https://github.com/NixOS/nixpkgs/pull/160336
https://github.com/NixOS/rfcs/pull/140 :)
https://github.com/NixOS/nixpkgs/pull/315949
https://github.com/NixOS/nixpkgs/pull/316764
https://github.com/NixOS/nixpkgs/pull/327960

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1950


chore: more advanced plugin configuration

Which problem is this PR solving?

#616

Short description of the changes
NodeTracer configs can now be configured in the following ways:
Default configuration and plugins
const tracer = new NodeTracer()

Configure a plugin with options
In this scenario, the http plugin will receive the httpPluginOption configuration.
new NodeTracer({
  plugins: {
    http: {
      enabled: true,
      path: "",
      options: {
        httpPluginOption: "value",
      }
    }
  }
});

Configure shared plugin options
In this scenario, the http plugin will receive the httpPluginOption configuration, the https plugin will receive the httpsPluginOption configuration, and both will receive the sharedPluginOption configuration.
new NodeTracer({
  plugins: {
    http: {
      enabled: true,
      path: "",
      options: {
        httpPluginOption: "value",
      }
    },
    https: {
      enabled: true,
      path: "",
      options: {
        httpsPluginOption: "value",
      }
    }
  },
  sharedPluginOptions: {
    sharedPluginOption: "value",
  }
});

Disable a plugin and leave all others enabled
new NodeTracer({
  http: { enabled: false }
});

You no longer need to explicitly give the whole configuration object
new NodeTracer({
  http: {
    // no need for `enabled` or `path` if the defaults are used
    options: { configOption: 1 }
  },
})

Codecov Report

Merging #628 into master will increase coverage by 1.66%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #628      +/-   ##
==========================================
+ Coverage   92.31%   93.97%   +1.66%
==========================================
  Files         177       48     -129
  Lines        8728     3602    -5126
  Branches      758      380     -378
==========================================
- Hits         8057     3385    -4672
+ Misses        671      217     -454

Impacted Files
Coverage Δ

...kages/opentelemetry-plugin-dns/test/utils/utils.ts
33.33% <0%> (-26.67%)
:arrow_down:

.../opentelemetry-plugin-dns/test/utils/assertSpan.ts
100% <0%> (ø)
:arrow_up:

...try-plugin-dns/test/functionals/dns-enable.test.ts
100% <0%> (ø)
:arrow_up:

.../opentelemetry-core/test/metrics/NoopMeter.test.ts

...emetry-metrics/src/export/ConsoleMetricExporter.ts

...lemetry-tracing/src/export/InMemorySpanExporter.ts

...entelemetry-exporter-jaeger/test/transform.test.ts

...entelemetry-core/test/common/ConsoleLogger.test.ts

...telemetry-plugin-document-load/src/documentLoad.ts

...try-core/test/trace/fixtures/test-package/index.js

... and 129 more

This is a great start. What are the valid use-cases of sharedPluginOptions? Currrently, looks like enhancedDatabaseReporting (database specific) and ignoreUrls (http/https specific) options are part of sharedPluginOptions.

This is a great start. What are the valid use-cases of sharedPluginOptions? Currrently, looks like enhancedDatabaseReporting (database specific) and ignoreUrls (http/https specific) options are part of sharedPluginOptions.

Right now the plugin options are the same regardless of if they're shared or if they're set on a single plugin, and only a couple exist. I was going to go through all plugins today and look at which configurations they use and create a set of options interfaces in types that generalizes them like DatabasePluginOptions which would have things like enhanced db reporting and RPCPluginOptions which would have things like ignore urls. This prevents the types interfaces from relying on plugins and instead plugins would just use the configuration interfaces exported from types.

@mayurkale22 one use case of shared configurations might be to set enhanced db reporting true for all db modules (mysql, pg, pg-pool, redis).
new NodeTracer({
  sharedPluginOptions: {
    enhancedDatabaseReporting: true,
  }
});

You may also want to set it true in general, but then disable for a single module which is also possible.
new NodeTracer({
  plugins: {
    redis: {
      options: {
        enhancedDatabaseReporting: false,
      },
    },
  },
  sharedPluginOptions: {
    enhancedDatabaseReporting: true,
  },
});

I see, let's discuss this in tomorrow's SIG meeting.

should we have some rules about naming params to avoid some problems with namespacing later? For example
enhancedDatabaseReporting maybe it should be db.enhancedReporting etc.
'ignoreUrls->http.ignoreUrls`
or maybe if param can be shared among all plugins it should start always with some prefix for example sharedEnhancedDatabaseReporting or shared.EnhancedDatabaseReporting.
Basically we will have more and more plugins and in theory it may happen that the same param can means different thing for different plugins. To avoid such situation I would strongly encourage to add something to the name so we can safely indicate that param can be shared.
Another thing is that the shared params should be immutable so the plugins won't be able to overwrite it (Object.freeze)

@obecny good point. maybe we're overcomplicating it. instead maybe we should just have a single configuration object shared to all plugins?
new NodeTracer({
  options: {
    http: {
      ignoreUrls: ["localhost"],
    },
    db: {
      enhancedDatabaseReporting: true,
    }
  },
});

Then the whole options object is frozen with Object.freeze and sent to all plugins. So the dns plugin can look into the http options and see which urls are ignored. All db related plugins like mysql and pg can look into the db options object and so on.

@obecny good point. maybe we're overcomplicating it. instead maybe we should just have a single configuration object shared to all plugins?
new NodeTracer({
  options: {
    http: {
      ignoreUrls: ["localhost"],
    },
    db: {
      enhancedDatabaseReporting: true,
    }
  },
});

Then the whole options object is frozen with Object.freeze and sent to all plugins. So the dns plugin can look into the http options and see which urls are ignored. All db related plugins like mysql and pg can look into the db options object and so on.

This look cleaner for me and I think you won't be able to pollute the the config with param that can break some other plugins.

So the dns plugin can look into the http options and see which urls are ignored. All db related plugins like mysql and pg can look into the db options object and so on.

This looks cleaner for me and I think you won't be able to pollute the the config with param that can break some other plugins.

Unfortunately, ignoring some urls doesn't mean you want to ignore dns lookup as well...
Besides, dns would require to access to the exporter config not http plugin. As discussed in the SIG, developer will make manual configuration.
This looks cleaner for me too and passing the whole config can have some benefits (http/https/http2).

This looks cleaner for me too and passing the whole config can have some benefits (http/https/http2).

Fully agree. It simplifies the implementation too. I'll update the PR today.

@obecny @OlivierAlbertini take a look. It is drastically simpler now. The shared options object and the plugin-specific options are the same "shape" now. They have a few "sections" like dns and http which can be used by whatever plugins deem appropriate.
new NodeTracer({
  options: {
    http: {
      ignoreIncomingPaths: ["/healthcheck"],
    },
    database: {
      enhancedDatabaseReporting: true,
    },
    dns: {
      ignoreHostnames: ["localhost"]
    }
  },
});

We could ensure that it is not null/undefined when we pass the options during the call at the enable method ? WDYT ?

good idea


Support OSM Overpass API urls for URL imports

As an example, this query to the Overpass API returns a response with:
Content-Type:application/osm3s+xml
but we're not taking into account this source/format here. The osm and osm2 url translators only seem to accept the OSM API directly.

Hey @rafatower could you evaluate how easy would be to do this?

My guesstimate from my ignorance: 2 days or so if it is just adjusting params and testing. 1+ week if there's a need to implement another (sub)format. Osm3 points to a new format for the content-type, but I might be wrong.
@Kartones what do you think?

no idea of this OSM3 format... ignorance++ my only experience with OSM format was fixing the url-based downloading, so without checking what the overpass API provides, how we import OSM etc I can't help much :/

I originally raised this issue in a stackoverflow comment... The query example is not ideal, as it queries for a JSON-based format. If you remove [out:json] or replace it by [out:xml], this will be the well known OSM XML format.

Given that you already have support for GeoJSON, could you consider using something like this: http://tyrasd.github.io/osmtogeojson/ ?

The format is one we support, and if you save the overpass output to a .osm file it uploads fine, but this prevents use with a sync table
An example URL is https://overpass-api.de/api/interpreter?data=%2F*%0AThis%20has%20been%20generated%20by%20the%20overpass-turbo%20wizard.%0AThe%20original%20search%20was%3A%0A%E2%80%9Chighway%3D*%20and%20type%3Away%E2%80%9D%0A*%2F%0A%5Bout%3Axml%5D%5Btimeout%3A25%5D%3B%0A%2F%2F%20gather%20results%0A%28%0A%20%20%2F%2F%20query%20part%20for%3A%20%E2%80%9Chighway%3D*%E2%80%9D%0A%20%20way%5B%22highway%22%5D%2841.65620060264075%2C-4.723037481307983%2C41.657322834579915%2C-4.720258712768555%29%3B%0A%29%3B%0A%2F%2F%20print%20results%0Aout%20body%3B%0A%3E%3B%0Aout%20skel%20qt%3B

Since uploading manually the file is working fine because we support OSM XML file format, this looks like just setting the content type check for Content-Type:application/osm3s+xml as @mmd-osm pointed.

Hey @rafatower any chance you can revisit this? :smile:

@jsanz I did a quick test adding the new content type and it's working with URLs like this one, which return XML. The URL I put one year ago in the issue description is returning JSON, so it won't work. I don't remember how I got it for JSON specifically, but now the Overpass Turbo API gives me always XML in the "get data directly from API" option, so 👌.

I don't remember how I got it for JSON specifically

If you put in [out:json] is your query, you will get JSON, otherwise XML will be default.

Thanks @mmd-osm! :)

Small nitpick: correct wording would be "Overpass API". There's no such thing as "Ovepass Turbo API". overpass turbo is the name of the web frontend, consuming data from Overpass API.

I just renamed the PR, thank you very much again!

Awesome Carla, thanks!!
On Mon, Sep 26, 2016 at 12:21 PM, Carla<EMAIL_ADDRESS>wrote:

I just renamed the PR, thank you very much again!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CartoDB/cartodb/issues/5042#issuecomment-249533309,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALfaJS0cj-2a-N0HP10EcCAArT_FICIks5qt5y2gaJpZM4Fsmgl
.

--
Jorge Sanz
Solutions Engineer
CARTO - Predict through location


module.exports assignment in a JavaScript file cannot be imported with ES6 syntax

See commented out failing test in this pull request.
I've spent a while in the debugger on this, and the root cause appears to be how the export= SymbolObject is constructed in the source file's symbol.exports property in a JavaScript module source file versus a TypeScript module source file. This causes resolveESModuleSymbol to return undefined.
Being it applies only to this specific construct (i.e. assignments to exports. work with es6 imports, or importing with var <id> = require(...) syntax works), its not a total blocker. But would be good to fix ASAP, especially as the error is rather unattractive.

If you do do this, please consider stripping the () and new() members from the import binding to be compliant with ES6 (option 2 in #6809)

Verified this is working in the current bits in 'master'.


GeneratePolymorphicSchemas uses oneOf but not allOf

Hi, i'm testing the new "GeneratePolymorphicSchemas" feature in swashbuckle 5.0.0 rc.
The OpenApi v3 generator creates a oneOf list of all derived classes for the base class. But i would like to have a allOf list in the derived class which includes the reference to the base class. I hope this makes sense.
Is this a feature that is not supported? Or do i have to create my own filter to support this scenario?

Yes it does make sense but no it’s not currently supported. It would be possible to implement but does introduce a little more complexity. Can you explain your use case and why this is important just to help me prioritize this enhancement?

Thank you for your prompt reply, very much appreciated! Here is our use case in simplified form.
This are our types:
// the base class for all derived classes
class EntityBase {
    public string Urn { get; set; }
}

// a container for Entity updates
class EntityUpdate {
    public string EntityType { get; set;}
    public EntityBase Entity { get; set;}
}

// more than 20 types that are derived from EntityBase
class Event : EntityBase {}
class Competitor : EntityBase {}
class Competition : EntityBase {}

Our Web API has this method - we get a List of EntityUpdate objects, where each EntityUpdate contains instances of types that are derived from EntityBase (e.g. Event, Competitor, Competition, etc.)
public List<EntityUpdate> GetEntityUpdates(long version) {
   // ....
}

We use Swashbuckle to create OpenApi 3.0 contracts and use the swagger-codegen tool to generate TypeScript files for Angular (https://github.com/swagger-api/swagger-codegen). This is probably a very common use case.
From an API standpoint you could argue that it would be easy to flatten all types. It would work fine without the polymorphic schemas too. But there is a lot of TypeScript code that would benefit from the information that those types are derived from a common base class. The derived classes are not just used for the API, but also in the program logic. Sure you could use DTOs for the APIs and create other (derived) types for the program logic, but we are talking about 20+ types with lots of properites.
class Event extends EntityBase {}
class Competitor extends EntityBase {}
class Comppetitor extends EntityBase {}

I found many people asking for the same feature in the previous versions of Swashbuckle. Some fixed it with a custom filter, but since Swashbuckle 5.0.0 supports polymorphic schemas, it would be awesome to get this out of the box. Thank you very much for your great work!

I wish all issue's were submitted in this tone - makes it all worth while so thankyou!
I can see how this feature would be useful for client generation tools. I'll take a look and see if I can sneak it into the upcoming 5.0 release.

After looking into this a little deeper, it's a little more complex than I thought and so I won't be in a position to include it with the 5.0.0 milestone

Thank you for taking a look at it, and for adding this feature to the backlog.

I'm also voting for this feature as at the moment I have 10 derived classes I need to handle :(

I'm also voting for this feature as at the moment we have 10 derived classes that should be handled.

Unfortunately i had to switch to NSwag because Swashbuckle does not support this feature.

also a vote for this issue form my side, same problem here :-)

I'm keen to get this added but it's complicated and is holding up the 5.0.0 release, which is super important for ASP.NET Core 3.0 support. So, I'm going to tackle it as a fast follow in v5.1.0.

Support for oneOf, allOf and discriminator added by #1468


Fix for Email - Hostname is not validated correctly #359

Fixes https://github.com/go-playground/validator/issues/359
"Email - Hostname is not validated correctly #359"
While Hostnames could potentially contain underscores, Domains should per RFC not contain underscores.
Tests

Extended validator_test.go to include a test for a domain with underscores to expectedly return an error. Tests were successful after the change.

Change Details:

Removed Underscores from two occurences in Alternations in the Regex.

@go-playground/admins

awesome @jadhub! thanks will merge asap!


fix(README): Adding command documentation

:tada: This PR is included in version 1.0.1 :tada:
Your semantic-release bot :package::rocket:


Closes #2 & #3

Changes:
-Added the sentence input to encrypt and decrypt functions by using fgets().
Closes #2 , #3

Hi, I would like to know where i should share the screenshots of my code. THank you.

file_decrypt.c
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include "header.h"
void file_decryption(char key[])
{
//open the cipher text file
FILE *f1 = fopen("cipher.txt", "r");
//codition to check for error in opening the file
if (f1 == NULL)
    printf("error in opening the file");

else
{
    char ch;
    int keyLen = strlen(key), i, j;

    //to find the length of the message in the file
    int ciphertext_len = 0;
    for (int i = 0; (ch = fgetc(f1)) != EOF; i++)
    {
        if (((ch >= 'A') && (ch <= 'Z')) || ch == 32)
            ciphertext_len++;
    }
    //printf("cipher text length: %d\n", ciphertext_len);

    char *newKey = (char*)malloc((ciphertext_len+1)*sizeof(char));
    char *decryptedMessage = (char*)malloc((ciphertext_len+1)*sizeof(char));

    //generating new key
    for (i = 0, j = 0; i < ciphertext_len; ++i, ++j)
    {
        if (j == keyLen)
            j = 0;

        newKey[i] = key[j];
    }
    newKey[i] = '\0';
    printf("\nNew Generated Key: %s\n", newKey);

    rewind(f1);
    FILE *f2 = fopen("filedecrypt.txt", "w");
    ch = '0';
    for(i = 0; i < ciphertext_len && (ch = fgetc(f1)) != EOF; i++)
    {
        if(ch != 32) {decryptedMessage[i] = (((ch - newKey[i]) + 26) % 26) + 'A';}
        else {decryptedMessage[i] = ch;}
        fputc(decryptedMessage[i], f2);
    }
    decryptedMessage[i] = '\0';
    printf("\nActual Message: %s", decryptedMessage);
    fclose(f2);

}
fclose(f1);

}

I have shared the code here. Kindly review it. Thank you.

I have shared the code here. Kindly review it. Thank you.

hey I'm sorry for the confusion. but we need screenshots of the output.

Great work there!


video.js:18568 VIDEOJS: ERROR: Unable to find plugin: vastClient

I tried to install the toturial file but it failed.
video.js:18568 VIDEOJS: ERROR: Unable to find plugin: vastClient

@truongphitam Did you solve this issue?


a11y review of page layout

Provide feedback on what elements/roles should be used for constructing the layout of PF4 page designs.
As part of this, determine if redundant roles are necessary for HTML5 elements.

Information about implicit role mappings is included at the end of this article, along with links to related studies that were done:
https://a11yproject.com/posts/aria-landmark-roles/
These are old, so it would be good to test ourselves if redundant roles are still needed.

Just came across this recommendation to never set redundant roles: https://www.w3.org/TR/html5/dom.html#do-not-set

The Udacity course on a11y also mentions that landmarks would be the only exception to the rule (of not being redundant) for browser support: https://classroom.udacity.com/courses/ud891/lessons/8311490720/concepts/83024007410923

Closing this issue. Specific updates to the Page component landmark regions were captured in https://github.com/patternfly/patternfly-next/issues/1185


Introduce the--no-shopifyignore flag

Open a new PR that partially incorporates these changes: https://github.com/Shopify/shopify-cli/pull/2551.
However, introduce the --no-shopifyignore flag.

still relevant


check-ttf: Updated Vertical Metrics checks

Hello,
I've updated the vertical metric checks so they match Khaled's proposed scheme. Both Kalapi's and Khaled's should work.
I've divided the test into three seperate tests:

WinAscent & WinDescent == yMax, yMin
OS/2 TypoAsc, TypoDesc == hhea TypoAsc, TypoDesc
Linegaps == 0 (just a warning for this because Kalapi doesn't use 0 linegaps)

If you're happy with this, we need to implement another check. Both schemes call for 'Use typo metrics' to be set.
Cheers,
Marc

ok, this looks good!


Custom fields in issue tracker

Took a look through the bugtracker but noticed this doesn't exist yet:
custom fields in the issue tracker. A lot of issue trackers, like Jira, Phabricator, RedMine allow custom fields. custom fields are very useful to record stuff that doesn't belong in the description. For example a selection of the custom fields we use current:

Customer involved in this request
Origin of the report (forum link)
Waiting: When an issue is depending on something from the customer, or some other event, keep track of what this issue is blocked on.
Docs status: combobox on if this issue needs documentation, if it's already documented or if it's in progress.

Obviously I'm not suggesting adding fields like this to Gitea itself, what I instead suggest is allowing the project to define custom fields of a few types (like Text, Memo, Url, Combobox) and reading/filling through the web interface or api.

it's critical!expecting!

Is there a workaround to work with issues via API and structured content?
e.g.:

defining content as { key = value } in the body or title?
finding issues by searching in a key for a value?
editing the value of a key via api without parsing the body manually?


FCC Weather API randomly returning Japan weather

Challenge Name

https://www.freecodecamp.org/learn/coding-interview-prep/take-home-projects/show-the-local-weather
Issue Description
Many campers have been reporting issues with their weather projects via the forum Help category.  At first, I assumed it was just incorrect code being used, but then I noticed the issue my own weather project and countless others over the past week.  It appears the glitch API is randomly returning the weather data for Japan.  If I open any camper's project using fetch, jQuery $.ajax, $.getJSOn or other method to obtain the weather data from valid lat and lon values, 75% of the time, the response returned is for Japan weather.  You can even see the issue showing up in the weather demo at https://codepen.io/freeCodeCamp/full/bELRjV
Browser Information

Browser Name, Version: Chrome 64.0.3282.186 (Official Build) (64-bit)
Operating System: Windows 8.1
Mobile, Desktop, or Tablet:  Desktop

Your Code
N/A
Screenshot

I think I've identified the issue! It's simply reading from the cache, which contains the Japanese data.
The cache is only used if there are more than sixty requests in its queue (line 50) That means that sometimes it'll return correct results; but sometimes it'll return these, unexpected, results.
How can this be fixed? We have two options...

Remove the cache
Make the cache functional, and actually use the latitude and longitude data when deciding whether to use the cache.

Okay, I think I fixed the issue. I couldn't test it, though, because I lacked an API key -- and there is, of course, the risk of a DOS given that we never resort to caching.
So, improvements could be made. Should we, perhaps, reject requests where otherwise we'd be sending the Japanese data? This is up to y'all. My fix it temporary and I'll try to work on making it better tomorrow.
I don't think I can make a pull request to the glitch.me API (unless, of course, there's a repository on GitHub which I missed); so someone with write permission will need to merge my changes after testing them with a working API key.

Right, I'm afk at this time; but I realised that the rate limiting is required. I'll fix my code soon so that requests are denied if too many API calls have been made.

Okay, I now think I've created a solution in the short-term. I'm not sure what we want to do about scary data collection though -- the coordinates tend to be quite precise (should we round them for caching purpurses?). We should definitely mark things if they're from the cache, to make it clear it's not 100% accurate.
Anyway, for now, whenever the code tries to access the cache, it'll instead send an error message.
 function getBestCachedData(lon, lat){
+ /*
   var fs = require('fs');
   var obj = JSON.parse(fs.readFileSync('./data/cache.json', 'utf8'));
+ */
-  return obj;
+  return {
+     "error": "This API is overloaded with requests at the moment. Please try again in a few seconds and see if you get a response"
+  }
  }

Hi @joker314 I agree to your solution of rejecting with an error. Can you please make a PR? Thanks a lot for taking the time to investigate this.

@QuincyLarson could you guide who has access to this https://fcc-weather-api.glitch.me/ ? I can be delegated if you are the owner.

@raisedadead I'd love to, but I've looked around and I'm not sure if glitch.me actually supports pull requests -- unless you also have a copy on GitHub or I'm missing something?

@joker314 yup you are correct, we will update the project from your remix. Please ignore my previous comment.
I am waiting on Quincy on confirmation of the access to that project. Thanks a lot for your help with this.

@raisedadead - So how long will this temporary fix be in place?  What would the ultimate solution for this look like?  Is this just a rate-limit issue?  If so, it is just going to get worse the more campers work on the weather project.  Can the rate-limit be increased?

So how long will this temporary fix be in place?
This will not be temporary, with the error it will be known that the issue is due to the rate limits.
This was a wrapper created on top of OpenWeatherMaps API, which was not supporting https I think, and hence conflicted with codepen.
If so, it is just going to get worse as more campers create weather projects. Can the rate-limit be increased?
Yes, you can opt for a paid version by integrating the API directly instead of the glitch wrapper in the challenge.
See https://openweathermap.org/price

@raisedadead It looks like the original code intended for there to be a cache. If this is the case, and if we can smooth out the details as to exactly what we want this to look like to respect privacy, then hopefully we can workaround the rate limiting?

Upon second thought, perhaps it's best to give valid data back instead of an error message. Let's instead change the cache to generate random weather conditions, and set the location to "API busy, try again later for real results"?

As someone who just completed this project and had the issue of receiving Japanese weather data or (most of the time) no data I would like to say that receiving any data is more useful than no data. At least with the Japanese data I could see if my code worked regardless of it showing accurate weather.

Well in theory, we could send random data. But we don t want to get complaints on the data being incorrect.. which I am pretty sure will be a case.
Anyways if it helps lets have the random data.
@QuincyLarson can you please guide with the above request?

I think we should send fake data, but make it clear it's fake. Have the location name be "API Busy, Fake Data", and the weather, coordinates, etc. be randomised in the response. This way, people know why the results aren't accurate; and yet everything will still work for developers.
Thoughts?

If you send fake data, I believe that would defeat the whole purpose of providing the current weather data for a specific location.  I like @joker314's idea about figuring out how we want to create the cache and implement it.

BTW, i think the image url of the icon is not returned as described in https://fcc-weather-api.glitch.me/.
It said Images links are included in the JSON under weather[0].icon, which is not.
I noticed that the demo solution wrote css to draw the icon.

Thanks fot letting us know about this potential issue, but the example request amd response do include the desired field. What particular request did you make that didn't have this field?

@joker314  Thx for replying.
https://fcc-weather-api.glitch.me/api/current?lon=39.988&lat=116.3000
{"coord":{"lon":139,"lat":35},"weather":[{"id":803,"main":"Clouds","description":"broken clouds"}],"base":"stations","main":{"temp":28.23,"pressure":1011,"humidity":74,"temp_min":26,"temp_max":31},"visibility":10000,"wind":{"speed":3.6,"deg":230},"clouds":{"all":75},"dt":1499396400,"sys":{"type":1,"id":7616,"message":0.0043,"country":"JP","sunrise":1499369792,"sunset":1499421666},"id":1851632,"name":"Shuzenji","cod":200}

I didn't notice that the example was working fine, so I guess this might due to the location or the special weather?

@Em-Ant It looks like this is an issue with the app running on Glitch. Could you take a look at the cache and see whether this is something we can clear?

I did some quick tests, I believe this is fixed. If anyone is still having problems, feel free to reopen this issue.

@moT01 What kind of tests did you do?  The issue is that there is a rate limit per the free FCC account used to make calls to the OpenWeather API.  Once those rate limits are reached the Glitch proxy returns the Japan coordinates.  The only reason it is not seen as an issue right now, is that this project is now optional in the curriculum, so there are not as many hits to it as there used to be.  As soon as you hit the Glitch 60 times in a minute, the following JSON is returned:
{
  "coord": {
    "lon": 139,
    "lat": 35
  },
  "weather": [
    {
      "id": 803,
      "main": "Clouds",
      "description": "broken clouds"
    }
  ],
  "base": "stations",
  "main": {
    "temp": 28.23,
    "pressure": 1011,
    "humidity": 74,
    "temp_min": 26,
    "temp_max": 31
  },
  "visibility": 10000,
  "wind": {
    "speed": 3.6,
    "deg": 230
  },
  "clouds": {
    "all": 75
  },
  "dt":<PHONE_NUMBER>,
  "sys": {
    "type": 1,
    "id": 7616,
    "message": 0.0043,
    "country": "JP",
    "sunrise":<PHONE_NUMBER>,
    "sunset":<PHONE_NUMBER>
  },
  "id": 1851632,
  "name": "Shuzenji",
  "cod": 200
}

Can you reopen this issue, because it is still on my to-do list of projects to fix?

Ahh, yea - I just made a couple quick calls to the api and was able to get correct weather. I suppose I should probably inquire a little more before closing issues.

I started working on a fix right at the start of Hacktoberfest and then got involved heavily with the QA process.  The rest is history.  I need to revisit this again, because now I have a much better understanding of Node and Express to be able to get a working solution going.

I'll have a look tonight.
Il dom 3 giu 2018, 18:52 Quincy Larson<EMAIL_ADDRESS>ha
scritto:

@Em-Ant https://github.com/Em-Ant It looks like this is an issue with
the app running on Glitch. Could you take a look at the cache and see
whether this is something we can clear?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/issues/16869#issuecomment-394175270,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMWwVv-YXwuqm3yg_86GURyMSPE1Xlbsks5t5BQ_gaJpZM4Sl2JA
.

There is a static cache that has only one entry (the location in Japan).
We could fix it removing the rate limiter (I don't know if it's a good idea, since we have only one api key there), or return a rate limit error in case we exceed the requests quota.
Anyway this api project on glitch is owned by @MiloATH , and we cannot edit it without 'forking' it, i.e. creating a new app with a new url.
I have send a join request using the camperbot account to Milo.

You missed the third option; to fix the cache so that data is actually stored there - or to send random data if the rate limiter is hit.
I fear exceeding the rate limit is not a good idea as the API key could be revoked in such a circumstance, and we might not get results from the API in any case.

@joker314 I was moving in the direction of your third option already.

I've passed on an invite to the glitch project.

The endpoint could be significantly better. I think we should build a separate repo with CI and deploy to something more mature like Heroku (free version). This would allow us to more easily work on the project.

We are not deploying to heroku any more. We will be using Glitch for now. Meaning if there is alternative project we are happy to deploy it under freeCodeCamp's account on Glitch and replace the existing challenge in the Curriculum

@raisedadead @RandellDawson
Hi! Any updates on this?
It would be awesome to see some diagrams with the architecture and the data flow (and eventually the associated filenames)

@Hash2C You can remix the existing Glitch project (shown below) to see and fix the project.
https://glitch.com/edit/#!/fcc-weather-api?path=server.js:1:0

Thanks @RandellDawson, I've been working on it, I hope I can finish a first draft until Thursday

@Hash2C Take your time to get it right.  This bug has been here quite some time.

Thanks @RandellDawson, I'll do my best.
I probably gonna need to know a little bit more about the current constraints.
I read above that we have a limit of 60 hits per minute, which seems to be the free tier in OpenWeather pricing. Is there a way to increase this limit? Like creating other subscriptions to OW? Are there other free "sources of truth" that we could be using along OW?

Is there a way to increase this limit? Like creating other subscriptions to OW?

They may also have limits on ip address (not sure), so creating other subscriptions would not help.

Are there other free "sources of truth" that we could be using along with OW?

No sure.

Edit2: It seems OW "Weather API data update" is " < 2 hours" as seen in this table

I am currently developing my own weather project using OpenWeather's free version and I have contemplated just checking if the request is less than 10 minutes from the last request, then show the last returned data for the same lat/lon.

I created this repo so it get's easier to test locally.
https://github.com/Hash2C/fccWeatherApiDraft
I believe the 3 main use cases (for now) are already covered

If coordinates are invalid/inexistent , send an error
else, convert the coords to a convenient format and then we try to hit the cache

If the requested coordinates are cached

If the timestamp is within the acceptable delta: send cached data
else: set mocking data as cached data (in case later OpenWeather api call fails)

else: set mocking data as something we decide (in case later OpenWeather api call fails).

We try to call OpenWeather api.

If we get the right data, send it, store in cache

Else, send the mocking data

This flow is hugely open to discussion of course!
There is still a lot of work to do, validations, async stuff, edge cases (tests), etc. but we will gradually get there. I commented the server.js file a lot (don't get scary), I will gradually filter most of that information and ask you for help here so we can discuss each issue.

Just an idea: could we eventually have a data service, that tries to minimize the number of "available requests to the OpenWeather API (or others) that don't get made"? This service would feed, let's say, a MongoDB database - that would be our cache (we could use Memcached but that is probably too much, we don't need that extra speed)
Other ideia: Are there any past usage statistics of this service? If not, maybe we could start creating one, maybe that could be usefull, to try to optimize an eventually possible but very suboptimal solution

(for some reason I totally missed your message!)

They may also have limits on ip address (not sure), so creating other subscriptions would not help.

Good point. Is it worth testing?

Are there other free "sources of truth" that we could be using along with OW?

No sure.

If we are allowed to do this, it may greatly increase the probability of achieving a successful solution.

I am currently developing my own weather project using OpenWeather's free version and I have contemplated just checking if the request is less than 10 minutes from the last request, then show the last returned data for the same lat/lon.

Yes, using cached data right? I brought that < 2h question because I asked previously about the acceptable delay, I started coding assuming we can manage to send data at most 1 h old, just to get it started.

I think we can also update the instructions of the challenge to let the developer know we will send back a special response if a limit is reached, so they can let an app user know the data may not be up-to-date. We would still want to return the same data back we currently are (so as no to break any old projects using the FCC API). We would just be adding an extra property to the response. What do you think?

I totally agree with this idea of giving the relevant info to the developers, it is very much the line I was considering to be the strongest

Are there standard tools for Testing and to make Requests in FCC projects?
For Requests I'm using (just because I decided to give it a try, instead of Axios)
www.npmjs.com/package/request
For testing I don't have much experience but I was thinking about Mocha.
But please let me know which tools better integrate with FCC

One thing I'm surely going to need some help to understand is this Security Issues github is warning me about

The simplest solution is just to run npm audit fix and then commit the updated package.json and package-lock.json.  The new packages should not have any breaking changes from the previous, vulnerable ones.  However, that assumes the package authors have not accidentally introduced a breaking change, so it's worth manually checking your app after the fixes have been applied.

I have been playing with the OpenWeather api (actually I should have done this from the beginning).
Did we know this? https://openweathermap.org/faq#error401
The relevant part

For FOSS developers: we welcome free and open source software and are willing to help you. If you want to use OWM data in your free software application please register an API key and file a ticket describing your application and API key registered. OWM will review your request lift access limits for your key if used in open source application.

Hello guys, I have been more constrained than expected.
On my free time, I have been studying the OpenWeather api. Unfortunately it is not well documented.
I think I came up with a feasible strategy, using the bbox option, but I'm still testing.
I came up with this idea of creating a document with all the info I came across, the tests I'm doing.

@Hash2C Take your time to get it right. This bug has been here quite some time.

@RandellDawson
You knew what you were saying :heavy_check_mark:

@Hash2C How is your solution coming along?

Closing this issue as the number of users working on this project in general has significantly dropped as it is no longer a required project for a certification.  This has lead to fewer instances where the rate limit for the API is reached.


upgrade langchain for python-privategpt example

Thank you so much for contributing! We're in the process of revamping our examples.


Add SoundCloud support

[ ] User able to search information about track,also bot must provide some information about track to the user messenger
SoundCloud API

@MichaelYusko I'll work on this

@nik849 Cool! thanks 👍

@MichaelYusko, what sort of functionality are you looking for?

@nik849 I think we can start with the search endpoint bot will be return some information about track/singer to a user messenger, what do you think?
for example: bot.send_soundcloud_message(singer='Kings of Leon') and bot will be return some information about Kings of Leon, and the same for tracks and etc.

@MichaelYusko ok great, I've added in already functions to get track information from a url, i'll add this in too and make a PR when done

@nik849 Sure, please do it when you have a free time;)
notice: bot must communicate via messenger


Sync style.css with the latest version of the 'coverage' package

The upstream version of the style.css file packaged with coverage can be found here:
https://github.com/nedbat/coveragepy/blob/7.4.3/coverage/htmlfiles/style.css

@microsoft-github-policy-service agree

Superseded by #94


Changes to scaladoc comments in Client

Hi,
This is a draft PR to see if there is appetite for improvement to the scaladoc comments in the org.http4s.client.Client trait.
I've done a few changes to some of the scaladoc comments in this draft, and want a feel on whether this is the right direction of travel, any early feedback or thoughts about whether doc improvements are better done elsewhere.
The changes were based on the behaviour of DefaultClient
Motivation
As a user of org.http4s.client.Client it's not clear what the behaviour of some methods are without looking at the implementation.
E.g. for expectOption:

Does this return a Some on successful response code class and a None for all other responses?
Or is it the actual behaviour of Some for successful response code classes, None for Not Found or Gone, and errors indicated for all other responses
Does it follow redirects on 3xx response?

Suggestion
Expanding/adding scaladoc comments in some places, at risk of being a bit verbose

Thanks for taking this on! Personally I'm 👍 to the direction of travel here, organizing by status code seems very good.
It would be ideal to target these changes to the series/0.23 branch so that they can find their way into a stable release sooner :)


v1.2.16

This repository contains GitHub workflows for managing releases automatically.
Please name this issue what you would like the new release to be called. E.x. "v1.0.0"
The following slash commands are available to use in comments on this issue:

Command
Description
Parameters

/release
Creates a new released based on the current state of the master branch
frontend=<version>backend=<version>engagement-status=<version>gitapi=<version>status=<version>config=<version>activity=<version>artifacts=<version>hosting=<version>participants=<version>engagements=<version>dispatcher=<version>agnosticv=<version>anarchy=<version>poolboy=<version>

/promote
Promotes the created release to the next environment
N/A

/cancel
Cancels the current release (and closes this issue)
N/A

/finish
Completes the current release (and closes this issue)
N/A

/release frontend=v1.2.5 backend=v1.4.5 gitapi=v1.3.0 config=v1.2.0 status=v1.1.0 dispatcher=v1.0.15 activity=v0.2.1 artifacts=v0.1.0 participants=v0.1.0 engagements=v0.0.1

/promote

/cancel


when my view window resize, my layout main is not resize, this is my code

$(window).resize(function(){
	z['main'].resize();
});

Please do not submit questions here. Github issues are for bugs only. As for resize, it will size to its container, not window.


P2P example for README?

I've gotten a bit stuck following the current README.

I generated an endpoint ("id") to play with, storing it to a file for reuse
I've instantiated a mesh and am logging it's link URI thing as the documentation does
(I've also found the currently-undocumented telehash.load helper that does the above for me)
Now what?

The documentation says I need a "router to assist" if I want to connect to a hashname.
I remembered that v2 used seeds and whatnot, but I don't see https://github.com/quartzjer/telehash-seeds/ as a dependency and passing that to telehash.load({id:"endpoint.json", links:"seeds.json"}) doesn't work as the links wants a CommonJS module rather than JSON [for starters]. I also see some hints that Telehash might be doing private meshes by default now, and/or that it's using blockname for DHT perhaps instead of seeds — but blockname's documentation makes it sound like it's a way to store backup DNS A records in Bitcoin so I'm a little lost down this path. What is a router, and do I need a Bitcoin wallet/client/??? to use Telehash in this way, but what does backup IPv4 host mappings have to do with Telehash hashnames and/or keys…?
Backing up to this README again, it looks like the other alternative is that I can connect directly, if I have endpoint/id-reminiscent information. Not sure about "paths" here though… I've already logged this URI thing as the first/only thing after instantiating(/starting?) my own mesh, so it seems important, but gets no further mention in the docs here. I guess I need the public keys from the file generated in step 1 above, and maybe the URI for paths? But paths is an {} instead of a [] so I'm not sure how I should pass it based on the docs.

This is as far as I've got today; and I'm guessing as I continue to UTSL in conjunction with the spec, things will gradually become clearer. But, while they were fresh, I wanted to document some things that were confusing to me and have slowed me down trying to play.
At this point, what I think would be helpful is if:

the telehash.org page had a "getting started" link — perhaps I just did the wrong thing by using telehash-js and one of the other implementations is a better place to start? But telehash-js looked fairly recently updated and I've been doing a lot of node.js stuff lately, so it seemed a reasonable place to start

this repo (if it is a good place to start) had a bit more fleshed out documentation, especially going to the point where a connection is made. I just checked and see now there is an examples directory, but the one example it has does a "same-process only" meshA.mesh(meshB) thing — at this point I have only a tentative understanding of what a Telehash mesh is in the abstract, or how its been encapsulated in this JS object I know have.

there were something of a standard Telehash "blinky" or "Hello, World" kick-the-tires tutorial milestone, in common across projects and maybe even featured prominently on the homepage. I really didn't have clear goal (beyond understanding this system better) when setting down to do this; I guess I was hoping to get some sort of tracer bullet "send over here, some evidence of its receipt happens" type communications working. Is there a public "echo server" or "numbers station" somewhere, that I should aiming to access as a first step? Or should I be trying to connect two of my own processes together? Will that work regardless of where in the world each bit of telehash app code is, or does it need to be on the same LAN [the link:// URL contains only a network ip address] or what?

In short, how do I get to a point where I know Telehash is "working", and then what are my options for remixing things from that point?

These are excellent things to have documented as you experience them, thank you!!
I can't answer it all exhaustively here, but at least a few pointers to help move you along:

blockname is still experimental and independent, not used by anything else in telehash (yet)
all meshes are indeed private now, and "seed" is now called "router" and is private to each mesh (so there isn't any public ones)
routers are only required to assist in p2p connectivity across different networks, and any endpoint can provide basic routing for others if enabled
telehash.org is getting updated, and sorely needs it, as does the README and docs here, sorry for the rough edges!

Okay, I got something going:
var th = require('telehash'),
    fs = require('fs');

var ENDPOINT_FILE = process.env.ENDPOINT;

th.load({id:ENDPOINT_FILE}, function (e,mesh) {
  if (e) throw e;
  console.log(mesh.uri());

  if (process.env.LINK) {
    mesh.link(process.env.LINK);
    mesh.stream(function (from, args, accept){
      var chan = accept();
      chan.on('data', function (d) {
        d = d.toString();
        console.log("ECHO:", d);
        chan.write(d.toUpperCase());
      });
    });
  }
  else mesh.accept = function (from) {
    console.log("INCOMING:", from.hashname);
    var link = mesh.link(from),
        chan = link.stream();
    chan.write("Hello?");
    var i = 0;
    setInterval(function () {
      chan.write("Test #"+(++i));
    }, 5e3);
    chan.on('data', function (d) {
      console.log("DATA:", d.toString());
    });
  };
});

Usage isn't particularly elegant, but not too bad either — I'm doing something like this:
## screen 1
ENDPOINT=test1.json node index
# … copy link URI into clipboard

## screen 2
ENDPOINT=test2.json LINK=`pbpaste` node index
# … should now log incoming strings, and those will echo back to screen 1 converted to all-caps

Thanks for your code; it was helpful.

Has anyone figured out how to hook up Telehash v3 with a public DHT?
I'm trying to upgrade a v2 project to v3 but I have no idea where to start with respect to the DHT functionality.

Are test1.json and test2.json like the links.json?

Sort of, but iirc the links.json you are referring to is live connection state (e.g. in case you need to restart your app/server but don't want to renegotiate routing/connections). The test1.json and test2.json are just the keys for each node. They don't actually store link state, just the various generated keypairs themselves.

I ran a modified copy of test_net_udp4.c and was able to get the mesh_add to show up on a remote machine running the router.js program.  I get the message "2wxhqoe up" on the remote end.  Now, I need to figure out why the link_up fails.  I will probably run link_handshake or some other program that has ping support on the remote side.

@natevw - thanks so much for your code - it is the best example I could find so far to help me understand the protocol, a simple README/Getting started page would be great! but for now I guess I am going to have to read the whitepaper :)

@southbite I've actually written up a few page "explainer" overview on Telehash that's mostly waiting for a few (not super essential) diagrams that are still on my list. Don't know if @quartzjer has already published that somewhere or if he'd be comfortable with me publicly posting my draft to a personal gist/blog. (Note also that my draft hasn't been super thoroughly vetted for technical accuracy in every detail, but iirc the initial feedback I got was on track!)

@natevw any news on this paper? It would be great to have some introductory documentation on Telehash, some kind of step-by-step tutorial...

It might make sense to wait until we finish the v4 refactor that Jer keeps talking about. :-)

@quartzjer Ping ping ping .... Still alive?


Connect fix

fixed connect issue by removing cyclic old logic from the previous button
ConnectFix
Description
https://app.clickup.com/t/862kabn0b
Removed old logic trying to keep wallet on refresh (does this anyway)
How has this been tested?
Trying to connect/disconnect on every page : https://feature-connect-fix.doi1f799swne9.amplifyapp.com/swap
Types of changes

[ ] Technical Debt (non-breaking change which removes unused code/assets)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The related ClickUp task has been linked to this PR
[x] The person creating the pull request is listed in "Assignees"
[ ] Change requires updated documentation

Screenshots or Loom Video (optional):

Task linked: CU-8678nrkkh UI: Phantom Connect Error


`split': invalid byte sequence in UTF-8 (ArgumentError)

Hi,
For a project, I'm storing diffs for each commit in forms of difffiles (diff per file) and patches, including the stats for each patch.
My script starts like -
require 'rubygems'
require 'logger'
require 'rugged'
require 'git'

# Include diff, difffile classes
load 'diff.rb'
load 'difffile.rb'
load 'helper.rb'

# Global array to store all the diffs
diffs_array = []

# Initialize both libraries
working_dir = `pwd`.chomp
rubygit_gem_repo = Git.open(working_dir, :log => Logger.new(STDOUT))
rugged_repo = Rugged::Repository.new(working_dir)

# Get all the commits for the project
commit_list = rubygit_gem_repo.log(nil)

# Get the initial empty tree state
empty_tree=`git hash-object -w -t tree /dev/null`
empty_state = rugged_repo.lookup("#{empty_tree.chomp}")

commit_list_array = commit_list.to_a

For 2 commits, I calculate the diff as follows:
  diff_bw_commits = rubygit_gem_repo.diff(prev_sha, next_sha)
  diff = Diff.new(prev_sha, next_sha, diff_bw_commits)
  diff.generate_difffiles_and_stats

In the generate_difffiles_and_stats function, I'm doing the following:
@difffiles = []
    # diff.class => Git::Diff
    # Get the stats for the diff, before extracting individual difffiles
    @stats = @diff.stats
    diff = @diff.to_a

    self.generate_stats
    @num_difffiles = diff.size
    @num_difffiles.times do |i|
      difffile = DiffFile.new( diff[i] )
      @difffiles << difffile
    end

My script runs fine for simple commit histories that I created myself, but when I run it on project JSHint, I'm getting an error:
</CreationDate(D:20120619174250-04'00')/Creator(Adobe Illustrator CS5.1)/ModDat0000000000 65535 f-04'00')/Producer(Adobe PDF library 9.90)/Title(jshint)>>
+0000000016 00000 n
+0000000144 00000 n
+0001070928 00000 n
<</Size 32/Root 1 0 R/Info 31 0 R/ID[<6BDD672972174366B9A561E955D8F759><CE113017%%EOF00efBA27BDB89A4EB25>]>>
\ No newline at end of file
/Users/jatinganhotra/.rvm/gems/ruby-2.1.3@527project/gems/git-1.2.8/lib/git/diff.rb:121:in `split': invalid byte sequence in UTF-8 (ArgumentError)
	from /Users/jatinganhotra/.rvm/gems/ruby-2.1.3@527project/gems/git-1.2.8/lib/git/diff.rb:121:in `process_full_diff'
	from /Users/jatinganhotra/.rvm/gems/ruby-2.1.3@527project/gems/git-1.2.8/lib/git/diff.rb:107:in `process_full'
	from /Users/jatinganhotra/.rvm/gems/ruby-2.1.3@527project/gems/git-1.2.8/lib/git/diff.rb:64:in `each'
	from diff.rb:57:in `to_a'
	from diff.rb:57:in `generate_difffiles_and_stats'
	from script.rb:48:in `block in <main>'
	from script.rb:32:in `each'
	from script.rb:32:in `<main>'

I researched about the error and found that the issue can be fixed by the answer in this StackOverflow answer.
Is it something that I am doing wrong?
Please let me know if you need any more information.
P.S. I know that this gem is not under active development, but it very nicely breaks down a Diff to Difffile to Patch. I can also easily access stats for each commit and stats per file. So, I stick to using it for diff purposes. I looked at the Rugged gem, but couldn't find such functionality. So, I just love this gem for this :)

Over in the lolcommits repo we're having a similar problem (in a slightly different place, when reading the commit logs in the command_lines method)
/Users/henrikhansson/.rvm/rubies/ruby-2.1.2/lib/ruby/gems/2.1.0/gems/git-<IP_ADDRESS>/lib/git/lib.rb:846:in `split': invalid byte sequence in US-ASCII (ArgumentError)
from /Users/henrikhansson/.rvm/rubies/ruby-2.1.2/lib/ruby/gems/2.1.0/gems/git-<IP_ADDRESS>/lib/git/lib.rb:846:in `command_lines'
from /Users/henrikhansson/.rvm/rubies/ruby-2.1.2/lib/ruby/gems/2.1.0/gems/git-<IP_ADDRESS>/lib/git/lib.rb:145:in `full_log_commits'
from /Users/henrikhansson/.rvm/rubies/ruby-2.1.2/lib/ruby/gems/2.1.0/gems/git-<IP_ADDRESS>/lib/git/log.rb:119:in `run_log'
from /Users/henrikhansson/.rvm/rubies/ruby-2.1.2/lib/ruby/gems/2.1.0/gems/git-<IP_ADDRESS>/lib/git/log.rb:112:in `check_log'
from /Users/henrikhansson/.rvm/rubies/ruby-2.1.2/lib/ruby/gems/2.1.0/gems/git-<IP_ADDRESS>/lib/git/log.rb:89:in `first'

I think same approach in PR #190 from @jatinganhotra would probably fix this too..

Yes. The same approach in PR #190 would work. I thought that the PR had been accepted, after I fixed the Ruby 1.8 syntax issue.

I think it's no longer mergable due to conflicts, maybe rebase with upstream master and push again..


OGC Sensor Things compliance

Compliance to OGCSensorThings > =1.0: IoT Device Gateway, Resource Catalogue, IoT Agents, Historicla Datastore, Sensor Platform
[LS-107] created by marco.jahn

Won't do it.


make cache health check aware of all cache backends

First draft of what we see as a gap in functionality in this library. We do still use it heavily for our services.
Here we didn't see a problem with one of the non-default cache backends quickly enough.
I'm happy to change / improve where you deem it necessary.
We do have this code running in production, so there is no time pressure, let's make it right :)

Codecov Report

Merging #267 into master will decrease coverage by 0.04%.
The diff coverage is 90.00%.

@@            Coverage Diff             @@
##           master     #267      +/-   ##
==========================================
- Coverage   72.26%   72.22%   -0.05%
==========================================
  Files          34       34
  Lines         393      396       +3
  Branches       39       39
==========================================
+ Hits          284      286       +2
- Misses        103      104       +1
  Partials        6        6

Impacted Files
Coverage Δ

health_check/cache/backends.py
80.95% <85.71%> (+0.95%)
:arrow_up:

health_check/cache/apps.py
100.00% <100.00%> (ø)

health_check/contrib/celery/tasks.py
66.66% <0.00%> (-8.34%)
:arrow_down:

health_check/mixins.py
96.77% <0.00%> (-0.20%)
:arrow_down:

health_check/views.py
95.83% <0.00%> (-0.17%)
:arrow_down:

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 c7d25c2...14fbeb2. Read the comment docs.

@codingjoe thanks!
added both of your suggestions

thanks @codingjoe :)
Then we'll wait for the next release so we can remove the workaround

Released in 3.14.0 🎉
Auto-releases on PyPi are currently broken, but you get special treatment. I released it manually ;)


[BUG] Using plugin overrides buildOptions

Bug Report Quick Checklist

[x] I am on the latest version of Snowpack & all plugins.
[x] I use package manager npm
[x] I run Snowpack on OS Linux
[x] I run Snowpack on Node.js v12+

Describe the bug
While using plugin: '@snowpack/plugin-webpack' and build option clean set to false, files in out directory still get cleared.
To Reproduce

Set buildOptions clean: false, and use plugin '@snowpack/plugin-webpack'.
Write a file to your build out directory.
Now build with snowpack: snowpack build --watch

The file written before snowpack build gets removed. As I am using --watch flag, this behaviour doesn't reproduce in subsequent writes.
Expected behavior
Build out directory files be preserved as clean: false option is set.

@jalovatt I like your approach, rather than having both tools (webpack and snowpack build) build to the same output folder, however,  the method you proposed above config.output.path = path.resolve(__dirname, 'dist') does not contain the index.html entry point? do you have a solution that just leverages @snowpack/plugin-webpack?

@jalovatt I like your approach, rather than having both tools (webpack and snowpack build) build to the same output folder, however, the method you proposed above config.output.path = path.resolve(__dirname, 'dist') does not contain the index.html entry point? do you have a solution that just leverages @snowpack/plugin-webpack?

Sorry, I forgot that I was using a local branch when I suggested that. For anyone else reading this, there is a PR to have the plugin respect the user's config.output.path: #3255


Error: trackBy must be a function, but received undefined

Hi, i getting this error when upgrading to lastest version 3.1.0 , 2.8.2 works fine for me

Thank you

Hi,
Looks like it fails with angular 2.4.1:
https://plnkr.co/edit/crXt0CkBsQmg1Hx6cRiC?p=preview
But with lastest Angular2 (i.e. 2.4.9 as of today), it works:
https://plnkr.co/edit/mZTQ9xnikhMwoOvkfiLl?p=preview
(with dependencies: lodash 4.6.1, mobx 3.1.0 or 3.1.3, ng2-mobx 1.2.9)
Hope this helps.

Fixed in 3.2.1 - please upgrade


Specify modelClass attribute in rest ActiveController like Yii::createObject() style

What steps will reproduce the problem?
I cant specify model in rest ActiveController by attribute modelClass like this
        'some-controller' => [
            'class' => 'yii\rest\ActiveController',
            'modelClass' =>  [
                'class' => 'humhub\modules\fooddelivery\models\OrderFood',
                'some-model-attribute' => 'value',
        ],

Whether such a possibility in the future?
Additional info

Q
A

Yii version
2.0.8

PHP version
PHP 7.0.8-0ubuntu<IP_ADDRESS>

Operating system
Ubuntu

No, this will not be supported as modelClass is used not only for model creation but for the ActiveQuery creation too.


Remove unused report recipes

These two reports seems to be unused for ages.
@miq-bot add_label reporting, technical debt

@miq-bot add_label technical debt

@isimluk
these are reports really unused but we can recycle it  ♻ and move to product/report/chargeback folder .
changes what we will be needed:

change in yamls db: Chargeback to ChargebackVm
review columns with current columns
also create report/s for ChargebackContainer - there are new recently

so then we will have some predefined report also for chargebacks.
@gtanzillo are you ok with this ?

I am ready to commit to recycle. Though, I would love to see smallish write-up about use-case of the Chargeback reports. That would help me focus on what might be valuable for users (as opposed to getting-the-broken-code-repaired mindset). Also the writing could help us to prioritize that work well.
I would need your help guys with such write-up. I still don't have comprehensive understanding of what might be all the use-cases & value of the feature XYZ... I try to tip toe lightly. :mans_shoe: I mean in general... until I see a code that is undocumented, unreachable, and broken (try to generate these reports in console), then I cannot resist to remove it. :smiling_imp:


HCC RUNTIME ERROR in hipCaffe

Issue summary
./build/test/test_all.testbin
Backtrace:
0x00007f04870cd32e:	Kalmar::CLAMP::DetermineAndGetProgram(Kalmar::KalmarQueue*, unsigned long*, void**) + 0x59e
0x00007f04870cd690:	Kalmar::KalmarBootstrap::KalmarBootstrap() + 0x120
0x00007f04870cd549:	__hcc_shared_library_init + 0x29
0x00007f048a2766ba:	_dl_rtld_di_serinfo + 0x706a
0x00007f048a2767cb:	_dl_rtld_di_serinfo + 0x717b
0x00007f048a266c6a:	+ 0x717b
HCC RUNTIME ERROR: Fail to find compatible kernel at file:mcwamp.cpp line:346
Operating system: Ubuntu 16.04

@MAXHAOZHANG  This information is not enough for us to understand what is going wrong,
When you report an issue we need the version of the driver your running which version of HCC.

Duplicate issue:  https://github.com/ROCmSoftwarePlatform/hipCaffe/issues/39

The GPU in my server does not support ROCm -v1.7 -- From AMD
AMD Firepro W9100
Thank you!


Error parsing lftp job status (Previous Error parsing lftp job status #55)

I have docker 0.8.6 and hitting the same error.
Restarting resolves the app for a random period of time (could be minutes, could be hours)

Log Dump:
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/app/python/common/job.py", line 44, in run
self.execute()
File "/app/python/controller/controller_job.py", line 29, in execute
self.__controller.process()
File "/app/python/controller/controller.py", line 202, in process
self.__update_model()
File "/app/python/controller/controller.py", line 295, in __update_model
lftp_statuses = self.__lftp.status()
File "/app/python/lftp/lftp.py", line 322, in status
statuses = self.__job_status_parser.parse(out)
File "/app/python/lftp/job_status_parser.py", line 94, in parse
raise LftpJobStatusParserError("Error parsing lftp job status")
lftp.job_status_parser.LftpJobStatusParserError: Error parsing lftp job status
2022-06-04 12:59:42,020 - ERROR - seedsync (MainProcess/MainThread) - Caught exception
Traceback (most recent call last):
File "/app/python/lftp/job_status_parser.py", line 89, in parse
statuses += self.__parse_queue(lines)
File "/app/python/lftp/job_status_parser.py", line 482, in __parse_queue
raise ValueError("Unrecognized line '{}'".format(lines[0]))
ValueError: Unrecognized line '/downloads/AudioBook/1984 (George Orwell) - Audio Book/Audio Books - George Orwell - 1984 - 6 of 14.mp3.lftp 7813120-11719680 34.4 KiB/s'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/app/python/seedsync.py", line 164, in run
controller_job.propagate_exception()
File "/app/python/common/job.py", line 77, in propagate_exception
raise exc_info[1].with_traceback(exc_info[2])
File "/app/python/common/job.py", line 44, in run
self.execute()
File "/app/python/controller/controller_job.py", line 29, in execute
self.__controller.process()
File "/app/python/controller/controller.py", line 202, in process
self.__update_model()
File "/app/python/controller/controller.py", line 295, in __update_model
lftp_statuses = self.__lftp.status()
File "/app/python/lftp/lftp.py", line 322, in status
statuses = self.__job_status_parser.parse(out)
File "/app/python/lftp/job_status_parser.py", line 94, in parse
raise LftpJobStatusParserError("Error parsing lftp job status")
lftp.job_status_parser.LftpJobStatusParserError: Error parsing lftp job status
2022-06-04 12:59:45,037 - ERROR - seedsync.Controller.Lftp (MainProcess/ControllerJob) - Lftp timeout exception
Traceback (most recent call last):
File "/app/python/lftp/lftp.py", line 128, in __run_command
self.__process.expect(self.__expect_pattern, timeout=self.__timeout)
File "/usr/local/lib/python3.8/site-packages/pexpect/spawnbase.py", line 343, in expect
return self.expect_list(compiled_pattern_list,
File "/usr/local/lib/python3.8/site-packages/pexpect/spawnbase.py", line 372, in expect_list
return exp.expect_loop(timeout)
File "/usr/local/lib/python3.8/site-packages/pexpect/expect.py", line 181, in expect_loop
return self.timeout(e)
File "/usr/local/lib/python3.8/site-packages/pexpect/expect.py", line 144, in timeout
raise exc
pexpect.exceptions.TIMEOUT: Timeout exceeded.
<pexpect.pty_spawn.spawn object at 0x14b62a98ca90>
command: /usr/bin/lftp
args: ['/usr/bin/lftp', '-p', '22', '-u', ‘XXX,XXX’, 'sftp://XXX’]
buffer (last 100 chars): b'll) - Audio Book/Audio Books - George Orwell - 1984 - 6 of 14.mp3.lftp 7813120-11719680 34.4 KiB/s\r\n'
before (last 100 chars): b'll) - Audio Book/Audio Books - George Orwell - 1984 - 6 of 14.mp3.lftp 7813120-11719680 34.4 KiB/s\r\n'
after: <class 'pexpect.exceptions.TIMEOUT'>
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 714
child_fd: 68
closed: False
timeout: 30
delimiter: <class 'pexpect.exceptions.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
0: re.compile(b'lftp XXX@XXXX:.>’)
2022-06-04 12:59:48,092 - ERROR - seedsync.Controller.Lftp (MainProcess/ControllerJob) - Lftp timeout exception
Traceback (most recent call last):
File "/app/python/lftp/lftp.py", line 128, in __run_command
self.__process.expect(self.__expect_pattern, timeout=self.__timeout)
File "/usr/local/lib/python3.8/site-packages/pexpect/spawnbase.py", line 343, in expect
return self.expect_list(compiled_pattern_list,
File "/usr/local/lib/python3.8/site-packages/pexpect/spawnbase.py", line 372, in expect_list
return exp.expect_loop(timeout)
File "/usr/local/lib/python3.8/site-packages/pexpect/expect.py", line 181, in expect_loop
return self.timeout(e)
File "/usr/local/lib/python3.8/site-packages/pexpect/expect.py", line 144, in timeout
raise exc
pexpect.exceptions.TIMEOUT: Timeout exceeded.
<pexpect.pty_spawn.spawn object at 0x14b62a98ca90>
command: /usr/bin/lftp
args: ['/usr/bin/lftp', '-p', '22', '-u', ‘XXX,XXX’, 'sftp://XXX’]
buffer (last 100 chars): b'll) - Audio Book/Audio Books - George Orwell - 1984 - 6 of 14.mp3.lftp 7813120-11719680 34.4 KiB/s\r\n'
before (last 100 chars): b'll) - Audio Book/Audio Books - George Orwell - 1984 - 6 of 14.mp3.lftp 7813120-11719680 34.4 KiB/s\r\n'
after: <class 'pexpect.exceptions.TIMEOUT'>
match: None
match_index: None
exitstatus: None
flag_eof: False
pid: 714
child_fd: 68
closed: False
timeout: 30
delimiter: <class 'pexpect.exceptions.EOF'>
logfile: None
logfile_read: None
logfile_send: None
maxread: 2000
ignorecase: False
searchwindowsize: None
delaybeforesend: 0.05
delayafterclose: 0.1
delayafterterminate: 0.1
searcher: searcher_re:
0: re.compile(b'lftp XXXX@XXXX:.>’)
Exception in thread ControllerJob:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/pexpect/pty_spawn.py", line 23, in _wrap_ptyprocess_err
yield
File "/usr/local/lib/python3.8/site-packages/pexpect/pty_spawn.py", line 328, in close
self.ptyproc.close(force=force)
File "/usr/local/lib/python3.8/site-packages/ptyprocess/ptyprocess.py", line 400, in close
raise PtyProcessError('Could not terminate the child.')
ptyprocess.util.PtyProcessError: Could not terminate the child.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "/app/python/common/job.py", line 56, in run
self.cleanup()
File "/app/python/controller/controller_job.py", line 34, in cleanup
self.__controller.exit()
File "/app/python/controller/controller.py", line 207, in exit
self.__lftp.exit()
File "/app/python/lftp/lftp.py", line 404, in exit
self.__process.close(force=True)
File "/usr/local/lib/python3.8/site-packages/pexpect/pty_spawn.py", line 328, in close
self.ptyproc.close(force=force)
File "/usr/local/lib/python3.8/contextlib.py", line 131, in exit
self.gen.throw(type, value, traceback)
File "/usr/local/lib/python3.8/site-packages/pexpect/pty_spawn.py", line 25, in _wrap_ptyprocess_err
raise ExceptionPexpect(*e.args)
pexpect.exceptions.ExceptionPexpect: Could not terminate the child.


Allow doc comments on function arguments and return types

Would continue on #324 to let the below work.
type State s a =
    /// The state
    s
    /// State returns the new state and a value
    -> { state : s , value : a }

Haskell also allows the equivalent of:
type State s a =
    s                            //< The State
    -> { state : s , value : a } //< State returns the new state and a value


Medoid compositing method always running out of memory?

I'm interested in this approach but whenever I try it it always runs out of memory (even though other compositing methods work fine with the same settings)

If the image computation is running over the user memory limit on download, you can reduce the max_tile_size parameter.  I suggest trying max_tile_size=8 (MB).  The command line docs are here and the API docs here.

Hi Dugal, 8 is what I have it set to after experimenting for a value that stops throwing those memory errors 99% of the time, I think something more is going on here. Does this method work for you?

Hello, I have seen a "user memory limit exceeded" error when downloading a large Sentinel-2 medoid composite.  When I decreased max_tile_size, it downloaded ok.
Earth engine has a size limit (32 MB) on download requests.  geedim calculates the download tile sizes so that this is not exceeded.   Earth engine also has a limit on user memory for image computations.  This limit can still be exceeded when downloading computed images (e.g. medoid composites) with geedim.  Unfortunately there is no way for geedim to know the memory requirements of a computation in advance.  So it is up to the user to adjust max_tile_size if they run into memory issues.
Alternatively, exporting is not subject to the user memory limit, so a user could export their computed image to an asset, and then download the asset image with geedim.
If you think there is something else going wrong, please provide code to recreate the problem case.

I will try with even smaller tile sizes when I get a chance (next week)

See the related documentation section in the latest release.

Well, for me it doesn't work even if I reduce max_tile_size to 0.1

Here is the GeoJSON I've used.
{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "properties": {},
      "geometry": {
        "coordinates": [
          [
            [
              -0.3689373648039975,
              5.785841065493003
            ],
            [
              -0.3689373648039975,
              5.364440103464588
            ],
            [
              0.05576223573189054,
              5.364440103464588
            ],
            [
              0.05576223573189054,
              5.785841065493003
            ],
            [
              -0.3689373648039975,
              5.785841065493003
            ]
          ]
        ],
        "type": "Polygon"
      }
    }
  ]
}

Btw, if it helps, the error seems to happen before it starts downloading

OK.  Can you tell me the value of collection?

'COPERNICUS/S2_SR_HARMONIZED'

The latest v1.7.0 release contains some improvements and an example related to this.


TypeError: Cannot read property 'startLineNumber' of null

I was just reloading the window and I guess moved my mouse:
TypeError: Cannot read property 'startLineNumber' of null
    at ModesContentHoverWidget._renderMessages (modesContentHover.js:205)
    at ModesContentHoverWidget._withResult (modesContentHover.js:158)
    at HoverOperation._completeCallback (modesContentHover.js:97)
    at HoverOperation._onComplete (hoverOperation.js:82)
    at HoverOperation._triggerSyncComputation (hoverOperation.js:59)
    at RunOnceScheduler.runner (hoverOperation.js:20)
    at RunOnceScheduler.onTimeout (async.js:423)

Also already fixed in master


Apple Podcast: AAC encoding

Also, the audio file in your feed isn’t optimized, which prevents users from streaming it on Apple Podcasts.
You can optimize the audio file by converting it in iTunes to an AAC encoding. Next, remove the non-working file from your feed and replace it with the newly encoded audio file.
Once you have made all of the corrections, please click Publish in Apple Podcast Connect to submit your podcast.
If you need further assistance after completing the steps above, please let me know. I’m happy to help. My schedule is Monday through Friday, 9 a.m. to 6 p.m. central standard time. Should an update be received while I’m out of the office, one of my colleagues will follow up with you on my behalf.
For your reference, your case number is<PHONE_NUMBER>67.
Kind regards,
Crystal
Apple Inc.

Feature dropped.
Went straight mp3.
Podcast is up and serving: https://podcasts.apple.com/us/podcast/theologicus/id1680606952


Remove feature

Describe the need of your request
Add an action to remove an entire feature
Proposed solution
Create an action to remove an entire feature.
Find out what assets are mapped to the given feature then delete all those assets.
The action should be added as a button on the feature model view
Alternatives you've considered
No response
Additional context
No response

@RimanHoubbi https://bitbucket.org/easelab/hans-text/pull-requests/27


Remove warnings

Thanks for releasing this library! These two patches fix a couple of warnings, the descriptions give the rationale for the safety of the changes.

A further note on the value of j: The loop where j is used as an assignment index is:
			for (j = outisz; j--; )

So j can become negative after the implicit check for 0 in the j-- expression has occurred. At this point the loop has exited however, and we don't read j again.
I would suggest re-writing this loop as:
for (j = outisz; j !=0; j--)

For readability.

ACK


[BUG] Close renderer in ieeg locate GUI

Fixes https://github.com/mne-tools/mne-python/issues/10225.
Sorry @BarryLiu97  I wrote the PR without thinking this might have been a good one for you, next time.

haha, never mind. It's good enough that my advice helps.

Feel free to merge assuming it comes back green.
@BarryLiu97 does it fix your problem?

Yes, indeed!

@GuillaumeFavelier, I was trying to copy what you had in the coreg GUI but I was getting cleanup errors. You wouldn't happen to know how to do this best, would you?

That's odd. It works for me locally with your branch.

@alexrockhill feel free to merge if you and @BarryLiu97 are happy, or feel free to move and use safe_event and/or reorder based on what @GuillaumeFavelier suggests

Ok I'll merge if @GuillaumeFavelier doesn't have anything suggestions to change

Thanks @alexrockhill @BarryLiu97 @GuillaumeFavelier !


3 Gang Switch only showing as one switch

Hi there. I recently got a 3 gang Sonoff  touch switch and it is only showing as one switch and will not control anything once configured with Homebridge/homekit

Moved to open issue of same nature


Autocompletion for .svg and .png files doesnt work

Hello.
Autocompletion for .svg and .png files doesn't work.
E.g
import { ReactComponent as Logo } from "../assets/<spot>"
If I trigger cmp autocompletion in  with lsp source I cannot see any images, only inner dirs if such exist.

Have you tried passing cmp's capabilities table to the server? See my comment in #34.

I believe the fix described in #34 should fix this, but feel free to open another issue if not.


circt: 1.99.1 -> 1.99.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for circt is: Circuit IR compilers and tools
meta.homepage for circt is: https://circt.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.99.2 with grep in /nix/store/ghwzsf5mpyhiv48bn21glfixj4cmf40x-circt-1.99.2
found 1.99.2 in filename of file in /nix/store/ghwzsf5mpyhiv48bn21glfixj4cmf40x-circt-1.99.2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

circt

Instructions to test this update (click to expand)

Either download from the cache:
nix-store -r /nix/store/ghwzsf5mpyhiv48bn21glfixj4cmf40x-circt-1.99.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A circt https://github.com/r-ryantm/nixpkgs/archive/047637626d416ae4abaa397764203a8215babd11.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/047637626d416ae4abaa397764203a8215babd11#circt

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ghwzsf5mpyhiv48bn21glfixj4cmf40x-circt-1.99.2
ls -la /nix/store/ghwzsf5mpyhiv48bn21glfixj4cmf40x-circt-1.99.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 3 packages built:

circt
circt.dev
circt.lib

Maintainer pings
cc @SharzyL @pineapplehunter @sequencer for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge


Add the --config-only flag on flutter build macos

Use case
Not sure if there's already an issue open for this, I couldn't find it, but I believe the --config-only flag should be added on flutter build macos just like flutter build ios. To be used in conjunction with fastlane on CI/CD for example.

Proposal
Add the --config-only flag on flutter build macos, same as  flutter build ios

Closing this as duplicate of https://github.com/flutter/flutter/issues/84018


Respect $CARGO_HOME

Minimal code: -
Platform: MacOS
Version: uv 0.3.1 (be17d132a 2024-08-21)

uv does not respect $CARGO_HOME, used to change the location of the the default $HOME/.cargo folder.
For example, I use the fish shell, and uv creates a file $XDG_CONFIG_HOME/fish/conf.d/uv.env.fish with the following content:

source "$HOME/.cargo/env.fish"

Changing this to
set -q CARGO_HOME; or set CARGO_HOME "$HOME/.cargo"

source "$CARGO_HOME/env.fish"

fixes this.
For bash/zsh it's even simpler:
source "${CARGO_HOME:-"$HOME/.cargo"}/env"

Context: My $CARGO_HOME is set to "$XDG_DATA_HOME/cargo" to respect the XDG base directory spec.

Hello there from cargo-dist, the project that generates this installer.
We should be respecting CARGO_HOME on install, but we actually replicate the behaviour of rustup here: we assume that anyone who is setting CARGO_HOME was doing so on a temporary basis for the duration of the install, and then resolve its value so that things will keep working even if it becomes unset.
See the equivalent issue in rustup: https://github.com/rust-lang/rustup/issues/3020

Thank you for your explanation. I'm not vey familiar with the rust ecosystem, so this explanation certainly helps!
When I read the linked issue thread, it seems that my best way to resolve the issue is to reinstall Rust and friends, and setting the cargo home env variable during rust installation.


Fix bug where form is submitted when user clicked on Back button on form last page

This PR includes

Fix bug where form is submitted when user clicked on Back button on form last page.
Remove unnecessary code.

@adibzter Do test it out first, thanks.

My bad. Yep the feature is already there, and this was just a bug fix where when user on last page and they click back button on the form, its still treated as submit form, not going back to previous page.

🚀


Azure AD Authentication and long requests headers

I experienced an issue on my asp.net core site hosted on Azure App Service when accessed behind an NGinx Proxy.
I got a 502 Bad Gateway error when trying to authenticate using Azure AD. After a few days of research I opened a ticket on the AspNet Core project (https://github.com/aspnet/AspNetCore/issues/14725) and in the end the issue was that the request headers were > 4Kb and NGINX was rejecting those requests (NGINX Default Config).
I saw there is a section regarding this: https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/linux-nginx?view=aspnetcore-3.0#long-request-header-fields but I thought maybe it would be good to mention that this limit can easily be reached when using Azure AD Authentication. In fact I don't embed a lot of claims in the token and I do not include the security groups (which can increase the size of the cookie by a lot), so I guess this is some pretty standard setup.
In my case a note about 502 Bad Gateway errors being related to authentication cookies in Azure AD could have saved me at least a week of debugging.

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

ID: dcdd2c35-bf2b-2673-d150-303a8aaa54d2
Version Independent ID: 815fe034-c9fc-aee3-a8b5-f2e860b30302
Content: Host ASP.NET Core on Linux with Nginx
Content Source: aspnetcore/host-and-deploy/linux-nginx.md
Product: aspnet-core
Technology: aspnetcore-hostdeploy
GitHub Login: @guardrex
Microsoft Alias: riande

Thanks @MaximeMarck ... That's a great idea.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1984 ms

Resolved: Bofrost.at performance has improved in 851fb4e after 9 minutes.