mycroft-cli-client associeted errors

I've been having trouble ending the Make but i bypassed it and finished it, it was giving a error when it was runninh the post-image script, then i loaded the image and it runned perfectly until i tried to start mycorft-cli-client it gave the error of unsuported locale
mycroft@MycroftOS:~ $ mycroft-cli-client
Traceback (most recent call last):
 File "/bin/mycroft-cli-client", line 11, in <module>
   load_entry_point('mycroft-core==19.8.4', 'console_scripts', 'mycroft-cli-client')()
 File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 489, in load_entry_point     return get_distribution(dist).load_entry_point(group, name)
 File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 2852, in load_entry_point     return ep.load()
 File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 2443, in load     return self.resolve()
 File "/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 2449, in resolve     module = __import__(self.module_name, fromlist=['__name__'], level=0)
 File "/usr/lib/python3.8/site-packages/mycroft/client/text/__main__.py", line 21, in <module>     from .text_client import (
 File "/usr/lib/python3.8/site-packages/mycroft/client/text/text_client.py", line 39, in <module>     locale.setlocale(locale.LC_ALL, "")  # Set LC_ALL to user default
 File "/usr/lib/python3.8/locale.py", line 608, in setlocale     return _setlocale(category, locale)
locale.Error: unsupported locale setting
I fixed it by exporting the variable LC_ALL to a locale and it started normaly, but i'm getting a unhandled expression inside the client. This was all after i registered the device at home.mycroft.ai.
Thank you for your time.

This was already bypassed, not solved, but the issue is after i register the device its fine and works the only problem is the volume skill and audio output, it can seem to find the audio output correctly and i dont hear the answer, but if i write it i get the answer correctly. I can see the microphone volume change in the client and it receives the wake word and query, but when i use mycroft-audio-test i dont hear a thing.

Right, back on my feet...
First things first. LC_ALL should be set by the buildsystem to "en_US.UTF-8"
https://github.com/j1nx/MycroftOS/blob/develop/buildroot-external/configs/rpi3_defconfig#L22
What did you do exactly? Than I can double check on this side and if needed script the same.
Secondly about the possible Python errors when you start "mycroft-cli-client" a bit to soon after the first boot. That is a known thing. Starting the Mycroft A.I. software stack for the first time means it is downloading all default skills and such. During that it also downloads and installs a lot of additional needed Python packages. If you would give it a bit more time, the mycroft-cli-client starts as wanted without errors.
Anyhow: Last but not least. The sound output. Funny, that sounds excactly like the topic here;
https://community.mycroft.ai/t/mycroft-with-respeaker-2-mic/7635
I am looking into it and also requested that user to give the alpha4 image a good, to see if we can hunt down that bug...

Great news, those problems with the make probably my fault, sorry about that, because i made an image yesterday and the only proble was on speechrecognition but thats a known bug, and the audio problem was solved by copying a configuration.json file to a correct location, which i suspect was due to the failed make, sorry i dont know the details because my group collegue did that fix, but if you want i can try.

Perfect! Will await your feedback about the LOCALE. With a bit of luck, that has resolved itself as well.

The locale is no longer a problem. The problems that now we have is sporadic reboots with no associated trigger.
We have also a question, is it possible to remove the startup and shutdown Mycroft images?

ATM I also witnessed strange things with the last Buildroot 2019.11.x upgrade. Working on a downgraded version as we speak. Untill Python 3.8 is more stable, I stick with the 2019.08.3 stable release of Buildroot.
You will most likely see the commits come in in the development branch later today or tomorrow.
To answer your question about the splash screens. Sure, you can turn off the service via menuconfig. Just run this command before you run the make command, after the "make clean " and "make rpi3-config" command;
make -C buildroot BR2_EXTERNAL=../buildroot-external menuconfig
Than in the ncurses menu go to the bottom section, "External packages" -> "Mycroft A.I. Personal Assistant" and deselect the Mycroft Splash package. Exit back out of this menu and then you can run the build again; "make rpi3"

Fixed by 4061037d0bb69b9c23f4b154674b22482c813ddf


Remove unused HostID

If I see it correctly, we don't need to send host.id any more because it is unset (always "0").
reporter/config.go
31:     // HostID is the host ID to be sent to the collection agent.
32:     HostID uint64

reporter/otlp_reporter.go
137:    // hostID is the unique identifier of the host.
138:    hostID string
333:            hostID:                  strconv.FormatUint(cfg.HostID, 10),
471:    addAttr(semconv.HostIDKey, r.hostID)

Closing in favor of #178


[bug] Off by one error on HTML report generation

🐞 Bug report
Description
When I select lines 3:0-3:44 for example, it shows up in the CSV as 3:0-3:44 but the report generates it as if I selected the whole 2:0 line. I have also seen where multi-line selections shift up one line when generating the code snippet.
Reproduction
Create a file that contains multiple lines, select a line with text above it (I selected the whole line of text if that helps), and then produce an HTML report with code snippets enabled.
Error message

none

🌍 Your Environment
Running extension version 1.19.2

Also just rolled back to 1.19.1 and can confirm that it works fine there :) so I'm able to keep working off that for now.

please check out version 1.19.3 which will fix this issue. This was caused a a side effect of #56

Thank you for promptly addressing this! I can confirm 1.19.3 fixes the issue.


isGlob and globToRegExp do not support windows paths

Describe the bug
Steps to Reproduce
import * as path from 'jsr<EMAIL_ADDRESS>
let globpath = 'D:\\a\\forager\\test\\resources\\*.jpg'
path.isGlob(globpath)
// false
path.globToRegExp(globpath)
// /^D:aforagertestresources\*\.jpg\/*$/

Expected behavior
I would expect to see globpath above return true for a filepath that contains * even on windows. I would also expect that globToRegExp would create a valid path delineated regex. See how these functions behave with unix paths below:
import * as path from 'jsr<EMAIL_ADDRESS>
let globpath = '/forager/test/resources/*.jpg'
path.isGlob(globpath)
// true
path.globToRegExp(globpath)
// /^\/+forager\/+test\/+resources\/+[^/]*\.jpg\/*$/

My best guess is that this is because globs are mainly used in unix systems. I am building a cross-platform app though that needs some kind of glob support for windows paths. For now I can fork these methods to be more cross-platform, but I think this is probably a good improvement to these utilities.
Environment

OS: ubuntu-latest & windows-latest on github ci
deno version: 1.44.1
std version: 1.0.0

I tried the case of isGlob with a windows path and the bug happened, so it's real.

@std/path functions change how they process paths based on the current machine's platform. You can change this behavior by instead importing from @std/path/<platform> for a specific platform. I.e., the following code give the following results.
import * as path from "@std/path/windows";

const globpath = "D:\\a\\forager\\test\\resources\\*.jpg";
console.log(path.isGlob(globpath));
// false;
console.log(path.globToRegExp(globpath));
// /^D:(?:\\|\/)+a(?:\\|\/)+forager(?:\\|\/)+test(?:\\|\/)+resources(?:\\|\/)+[^\\/]*\.jpg(?:\\|\/)*$/

Either way, from a glance, the first call is still incorrect, but the second call seems closer to the expected result. It looks like isGlob() might need some work...

I'm not sure this is a bug or not.
It looks like the current isGlob seems assuming windows path separator is given as four backslashes:
\\\\

(I guess this is probably because \ is considered as escape sequence in glob.)
This behavior seems aligned with is-glob npm package.
import * as path from 'jsr<EMAIL_ADDRESS>import isGlob from "npm:is-glob";

let globpath0 = 'D:\\a\\forager\\test\\resources\\*.jpg'
let globpath1= 'D:\\\\a\\\\forager\\\\test\\\\resources\\\\*.jpg'

console.log(path.isGlob(globpath0))
console.log(isGlob(globpath0));

console.log(path.isGlob(globpath1))
console.log(isGlob(globpath1));

this prints:
false
false
true
true

Oh! That makes sense.

@std/path functions change how they process paths based on the current machine's platform. You can change this behavior by instead importing from @std/path/ for a specific platform. I.e., the following code give the following results.

hmm so @iuioiua if my paths are real windows paths, will a unix path regex actually work for me? I assume parsing a glob with path.globToRegExp from the unix platform will produce a regex that works with unix paths, not windows paths


Asynchronous image loading via the "imageLoadFunction" option is broken for image layers

The ImageWMS, ImageArcGISRest, ImageMapGuide and ImageStatic source classes have the imageLoadFunction constructor option which is supposed to facilitate alternative ways of loading image data. The documenation for the LoadFunction API doc states:
Providing a custom imageLoadFunction can be useful to load images with post requests or - in general - through XHR requests, where the src of the image element would be set to a data URI when the content is loaded.
However, the current implementation (v8.1.0) of the image sources makes it impossible to asynchronously load the image data. Please see the code below:
https://github.com/openlayers/openlayers/blob/f68dbccc35151351070771beca36570fcb193965/src/ol/source/ImageWMS.js#L215-L219
The imageLoadFunction_ is expected to be a synchronous function and the decode function is called right after it, which will of course fail to decode image data that is not yet loaded.
I have a use case where I need to load image data asynchronously and my only option at this moment is to override the ImageWMS class and fix the getImageInternal method implementation.
My suggestion to fix this is the following:

Change the signature of the LoadFunction to: function(image: Image, src: string): Promise<void> | void. This doesn't break compatibility with any current implementations.
Change the load function passed to createLoader to something similar to the following:

load: (image, src) => {
  this.image.setImage(image);

  const retVal = this.imageLoadFunction_(this.image, src);
  if (retVal instanceof Promise) {
    return retVal.then(() => decode(image));
  }

  return decode(image);
}

This issue is a duplicate of #15097 and has been fixed already with #15103.

@ahocevar Would you please care to explain how exactly #15103 solves my problem? The fix in that PR will not work for my use case since image.complete will be false and image.width will be 0. I'm loading the image data as a blob via an AJAX request and and a URL to the blob object will be assigned to image.src only after the load is completed. For this use case the code will still throw an error.

@igorbremec Here is an example to test: https://codesandbox.io/s/wms-image-forked-gqtzz3?file=/main.js. If you set the version of ol to 8.1.0, it won't work, if you set it back to the latest dev version, it will work. The load function I added there just waits for 3 seconds before setting the src, to simulate your async use case:
imageLoadFunction(image, src) {
        setTimeout(() => {
          image.getImage().src = src;
        }, 3000);
      },

@igorbremec Here is an example to test: https://codesandbox.io/s/wms-image-forked-gqtzz3?file=/main.js. If you set the version of ol to 8.1.0, it won't work, if you set it back to the latest dev version, it will work. The load function I added there just waits for 3 seconds before setting the src, to simulate your async use case:
      imageLoadFunction(image, src) {
        setTimeout(() => {
          image.getImage().src = src;
        }, 3000);
      },

Thank you. I took a deeper look at the code and realized that the load() function in ol/Image.js ends up being called. However, it still didn't work when i updateded just the Image.js so I must be missing some other changes. I'll give a try again when the next OL version is released.

@igorbremec If you're using npm, you can npm install ol@dev to get the latest.

I can confirm it works on the latest dev version. Thanks again 👍


DOC: update contributing.md to meet these guidlines

https://mozillascience.github.io/working-open-workshop/contributing/

and also
https://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1007296


No matching package named os_info

I encountered the error as follows,
$ cargo build
    Updating registry `https://github.com/rust-lang/crates.io-index`
error: no matching package named `os_info` found (required by `rcc`)
location searched: registry https://github.com/rust-lang/crates.io-index
version required: ^0.1.0

rcc is my project.
os_type is not published on crates.io yet?

Thank you for trying to use os_info. :smile: You are right: this library hasn't been published on crates.io. I want to polish some more rough edges (#23) before this. Currently it is probably better to use the original crate (os_type).
I'm going to use this issue as a reminder for myself to finish the remaining work as soon as possible. :sweat_smile:

Great. I look forward to your update.
I have tried and read os_type before your os_info, and I have noticed that os_type does not work on Windows. Additionally, I like your tactics for detecting an environment.

Finally: https://crates.io/crates/os_info
(Normal) Windows support is still in progress, though.
Feel free to reopen the issue, if something is wrong. :smile:


in-parallel hypothesis testing for Decision Making

by patham9:
"I guess we need something new, some form of parallel hypothesis testing.
if only the used hypothesis is challenged, it can't fully make use of the feedback
when the used hypothesis gets downvoted by failed anticipation, it just switched to the next invalid hypothesis that was not yet downvoted!
The only way to make it succeed is to implement parallel hypothesis testing of k hypothesis, 1 is a too extreme case that isn't effective enough.
Also ANSNA will need it:
Assumption of failure should target all the hypotheses in the postcondition table that had the precondition fullfilled, meaning also the operation  that was chosen as the best one according to one of the entries in the table."
Explanation: When the system chooses an operation because of a memorized implication, and performs the decision, in case of the failed anticipation, also the other implications in the precondition table that had their precondition mostly fulfilled should receive the negative feedback.
Also: In v3.0.0 the policy was to try the specific variable-free implications first, and only if they can't lead to a decision of desire value above threshold, the general ones will be considered too. As an update, once parallel hypothesis testing is implemented, the general hypotheses should directly compete with the variable-free, this shouldn't be an issue then anymore.

This has been implemented already in v3.0.1_dev2 and was brought to perfection.


How to get session data from any HTML template?

I have set the session, but whenever I try to get the session from my handlers, it returns nil. But if I go to the browser > Storage > Cookies, it's there

Are you saving between retrieval from the store? If not you'll get a fresh Session each time. Ex.
package main

import (
	"fmt"
	"github.com/gofiber/fiber/v2"
	"github.com/gofiber/fiber/v2/middleware/session"
)

var SessionStore = session.New()

func main() {
	app := fiber.New()

	app.Get("/", func(c *fiber.Ctx) error {
		sess1, _ := SessionStore.Get(c)
		sess1.Set("ducks", "quack")
		fmt.Println("ducks 1", sess1.Get("ducks"))

		sess2, _ := SessionStore.Get(c)
		fmt.Println("ducks 2:", sess2.Get("ducks"))

		sess2.Set("ducks", "attempt 2")
		if err := sess2.Save(); err != nil {
			return err
		}

		sess3, _ := SessionStore.Get(c)
		fmt.Println("ducks 3:", sess3.Get("ducks"))
		return nil
	})

	app.Listen(":3000")
}

Yields:
ducks 1 quack
ducks 2: <nil>
ducks 3: attempt 2

Basically at ducks 2 you retrieve it without saving first and get a new object. Other option is to get the session once and store it in locals.

@cyantarek could you paste your code snippet, so we can help you.
What do you see if you run the following code?
package main

import (
	"fmt"
	"log"

	"github.com/gofiber/fiber/v2"
	"github.com/gofiber/fiber/v2/middleware/session"
)

var sessionStore = session.New()

func main() {
	app := fiber.New()

	app.Get("/", func(c *fiber.Ctx) error {
		sess, _ := sessionStore.Get(c)

		if sess.Fresh() {
			sess.Set("name", "john")
		}

		name := sess.Get("name")

		_ = sess.Save()

		fmt.Fprintf(c, "Welcome %s", name)

		return nil
	})

	log.Fatal(app.Listen(":3000"))
}


Add transport.tcp logger to the OOTB log4j config.xml file

…to add logger "transport.tcp" since it is often useful for auditing or support purposes. Altered distribution\src\main\assembly\filter.properties to change "KAAZING Gateway" to "Kaazing Gateway" in line with marketing directives.
This change will make it easier for people to use the identity logging feature This was pointed out to me by @michaelcretzman in an email discussion: he was not able to get the (very useful) tcp host and port  part of the identity logging feature working because there was no entry for logger "transport.tcp" in his log4j-config.xml file. Adding it OOTB will make things easier for customers.
I also made a slight wording change in another file since marketing have abandoned the earlier directive we had to use the spelling KAAZING.

Looks great to me! Thanks Chris!


How to configure Envoy to pass the absolute URL to the upstream service?

 For example, when  “GET https://www.google.com” is sent to Squid, it returns with 200 OK.
When Envoy is set up in front of Squid, the absolute URL gets parsed before sending to the upstream server. For example, the URL 'https://www.google.com' is sent as '/' and not as 'https://www.google.com'.
Any recommendations on how to set up Envoy in front of the Squid caching proxy which accepts the absolute URL?
Test Setup
Client --> Envoy --> Squid -->  Internet
Request to squid directly
Client ==> Squid
GET https://www.google.com HTTP/1.1
Client <== Squid
HTTP/1.1 200 OK
Request via Envoy when "http_protocol_options.allow_absolute_url: false"
Client ==> Envoy
GET https://www.google.com HTTP/1.1
Client <== Envoy
HTTP/1.1 400 Bad Request
Request via Envoy when "http_protocol_options.allow_absolute_url: true"
Client ==> Envoy
GET https://www.google.com HTTP/1.1
Envoy ==> Squid
GET / HTTP/1.1
host: www.google.com
x-forwarded-for: <IP_ADDRESS>
x-forwarded-proto: http
x-envoy-internal: true
x-request-id: aba6cc5e-5fe8-4613-8828-cede14874660
x-envoy-expected-rq-timeout-ms: 30000
content-length: 0
Envoy <== Squid
HTTP/1.1 400 Bad Request
X-Squid-Error: ERR_INVALID_URL 0
Client <== Envoy
HTTP/1.1 400 Bad Request
x-squid-error: ERR_INVALID_URL 0

@alyssawilk Do you know if we allow configuring this behavior?

Yeah, I don't think Envoy supports forwarding absolute URLs, and if we did there'd probably be some extra work to not forward it as GET http://www.google.com/ because of the way it is represented internally.

In case anyone bumps into this, I managed to work around the issue with Lua and make Envoy forward to squid for both "CONNECT" and non-CONNECT using absolute URLs (in my case that's for non-TLS traffic)
`static_resources:
listeners:

name: listener_0
address:
socket_address:
protocol: TCP
address: <IP_ADDRESS>
port_value: 10000
filter_chains:

filters:

name: envoy.filters.network.http_connection_manager
typed_config:
"@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
stat_prefix: ingress_http
route_config:
virtual_hosts:
- name: passthrough_outboundproxy
domains:
- "*"
routes:
- match:
connect_matcher:
{}
route:
cluster: outbound_proxy
typed_per_filter_config:
envoy.filters.http.lua:
"@type": type.googleapis.com/envoy.extensions.filters.http.lua.v3.LuaPerRoute
disabled: true
- match:
prefix: "http://"
route:
cluster: outbound_proxy
http_filters:

name: envoy.filters.http.lua
typed_config:
"@type": type.googleapis.com/envoy.extensions.filters.http.lua.v3.Lua
inline_code: |
function envoy_on_request(request_handle)
request_handle:headers():replace(":path", "http://"..request_handle:headers():get(":authority")..request_handle:headers():get(":path"))
end
name: envoy.filters.http.router
http_protocol_options:
allow_absolute_url: true
http2_protocol_options:
allow_connect: true
upgrade_configs:
upgrade_type: CONNECT

clusters:

name: outbound_proxy
type: LOGICAL_DNS
connect_timeout: 5s
typed_extension_protocol_options:
envoy.extensions.upstreams.http.v3.HttpProtocolOptions:
"@type": type.googleapis.com/envoy.extensions.upstreams.http.v3.HttpProtocolOptions
explicit_http_config:
http_protocol_options: {}
load_assignment:
cluster_name: outbound_proxy
endpoints:

lb_endpoints:

endpoint:
address:
socket_address:
address:
port_value: 8080
`


[SPARK-32080][SQL] Simplify ArrowColumnVector ListArray accessor

What changes were proposed in this pull request?

This change simplifies the ArrowColumnVector ListArray accessor to use provided Arrow APIs available in v0.15.0 to calculate element indices.
Why are the changes needed?

This simplifies the code by avoiding manual calculations on the Arrow offset buffer and makes use of more stable APIs.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Existing tests

This also avoid having to deal with an API change in the ArrowBuf class for Arrow 1.0.0 and will allow Arrow-Spark integration tests to run again in preparation for the 1.0.0 release, see https://github.com/apache/arrow/pull/6316.

Test build #124451 has started for PR 28915 at commit 59dd8ea.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/29069/
Test PASSed.

Test build #124451 has finished for PR 28915 at commit 59dd8ea.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/124451/
Test FAILed.

retest this please

Test build #124470 has started for PR 28915 at commit 59dd8ea.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/29089/
Test PASSed.

Test build #124470 has finished for PR 28915 at commit 59dd8ea.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merged to master and branch-3.0.

Thanks @HyukjinKwon and @viirya !


Update resource-limits.md

@v-zlrade : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Abandoning as one of the PMs on SQL MI side already completed PR with the same change


Add scraper to find every Albertsons pharmacy

This is a follow-on to #676 and is a bit speculative at the moment. We’re seeing an increasing number of locations with no store number, but we can scrape a list of [deeply] detailed info for every Albertsons pharmacy (would you like to know if a store has fresh guacamole? Now you can find out!).
This is sort of a proof-of-concept; I’m thinking we’d only run this very rarely and manually for now and commit the resulting data files (but slimmed down; these are HUGE) so we can do lookups either on addresses or latitude/longitude. It takes a while and a lot of resources to do this scrape, and the parts we care about should chaange exceedingly rarely.

Well, I’ve now opened a whole new can of worms:

The data I scraped here has a field named c_oldStoreID which is often different from c_parentEntityID and c_associatedPharmacyStoreID. I’m guessing these might be store numbers a sub-brand used before they got bought by Albertsons.
Sometimes the Albertsons appointment data uses the old store number from above instead of a current/new one.

So this is now repairable in a lot of cases, but will be a real serious mess. If we want to do this cleanly, we should probably:

Update the Albertsons loader to use external ID systems like albertsons_old_xxx or something similar instead of albertsons_xxx.
Add a migration to Update all the existing external ID records in the database in a similar way.
When we land this stuff, switch the scraper external ID systems back to albertsons_xxx

Less work, but also less nice, would simply be using different external IDs when we land this, e.g. albertsons_v2_xxx instead of albertsons_xxx.

OTOH, matching with this data finds stores for two places that are currently getting classified as community clinics because they have no store name in the appointment data. 🙃

This is also finding a handful of situations where the address in the appointment data is just wrong, e.g:

Appointments: Acme 3970 - 631 Mantua Ave, West Deptford, NJ, 08096 (This is a real address, but is a house 6.98 km away from the store in question.)
Store data: ACME #3970 - 631 Mantua Pike, Woodbury, NJ 08096

Rebased and added some terrifying in-progress/experimental code, but just wanted to make sure it was saved. This seems to get a pretty good match in all cases, finds more correct store numbers or addresses when the appointment data may be wrong (at least according to way too many spot checks), and successfully finds brand info when it is entirely missing and/or totally unmatchable in the appointment data.

Quick update: I’ve been a bit busy with offboarding tasks related to leaving USDR, but expect to get back to this over the weekend or next week.

I also tested this against the CDC API and it looks like they universally use the “new” store numbers. (Bad news is that means we are probably already mixing things up for locations that had different old & new numbers.)

In terms of different old vs. new store numbers:

There are 715 stores where old and new numbers are different.
None are in Alaska
58 are in New Jersey. These cover two brands:

ACME Markets: 41
Kings Food Markets: 17

Over all stores, most of the brands have some flavor of this problem:

Albertsons: 257
Shaw's: 127
ACME Markets: 96
Jewel-Osco: 76
United Supermarkets: 48
Albertsons Market: 23
Star Market: 20
Kings Food Markets: 19
Market Street: 19
Safeway: 15
Balducci's: 8
Amigos: 4
Lucky: 1
Tom Thumb: 1
Randalls - CLOSED: 1

Feeling pretty good about how this works now. (Obviously I need to clean out all the crazy logging code, make it use the new data, and fix tests, though.)
Here’s a listing of all the locations that will wind up with different store numbers after matching: https://gist.github.com/Mr0grog/119c526c73b5c7e122640e99dae94d4f
There are two locations that will need special handling:
Method: fuzzy  / Score: 0.2  / Factors: [ 'geo' ]
Appointments: Vons #1738                               /  729 North H St, Lompoc, CA 93436  /  VONS #1738  - 729 North H St, Lompoc, CA, 93436
Match:        Albertsons Pharmacy #3171                /  1500 N H St, Lompoc, CA 93436
              (c_oldStoreID: 3171)

This Vons is not listed on the Vons website, but appears to maybe be real? If we only take scores > 0.2 (which seems plenty reasonable) that’ll solve this.
Method: fuzzy  / Score: 0.55  / Factors: [ 'brand', 'number', 'geo' ]
Appointments: United Supermarkets #573                 /  101 N. Washington, Seymour, TX 76380  /  United 0573 - 101 N. Washington, Seymour, TX, 76380
Match:        United Supermarkets Pharmacy #146        /  202 N Main St, Seymour, TX 76380
              (c_oldStoreID: 573)

Google Maps suggests these really are two different locations, even though the pharmacy in question (101 N. Washington in Seymour, TX, as opposed to the one we're matching to) is not listed on United Supermarkets’s (or any Albertsons sub-brand’s) website. Street view shows a small pharmacy-only outlet at this address.
I think the best solution for this (and maybe something we should do for the Vons just in case) is to list them in the corrections.js module with some extra key like doNotMatchKnownStores: true or something that tells the rest of the code not to try and look up that store. These are both just weird cases where Albertsons lists nothing about them publicly, but that appear to potentially be real stores. The matching code is doing a great job finding other stores of the same brand less than a 1km away that would normally seem like the correct listing.

GOOD NEWS! I was worried about the changing store numbers causing collisions, but it looks like there are somehow no instances of this in practice!
Full details on how I did this and every change and collision are in this gist: https://gist.github.com/Mr0grog/0f832b801bdf52896d30f8656c54de98
But here’s the quick summary:

147 locations are getting a different (Store Brand, Store Number) combination.
34 of these collide with an existing location listing in UNIVAF’s database.
12 of these are potentially concerning because they are changing the store number (as opposed to adding a number to a listing we simply weren't able to detect one in before) or they are changing the brand from another store brand, e.g. Pavilions → Safeway (as opposed to from a “community clinic” to a store).
0 of the collisions appear to represent a different place -- they all have the same address as the corrected appointment listing we want to write.

So it looks like we don’t actually have to worry about this before merging.
On the other hand we should come back after merging and delete the old external IDs for every one of the 147 changed locations that are changing the store number (as opposed to adding a number to a listing we simply weren't able to detect one in before) or are changing the brand from another store brand, e.g. Pavilions → Safeway (as opposed to from community_clinic).
🎉

Assuming this passes tests, it should be good to go. @astonm thank you so much for taking a look earlier, and feel free to review the last few changes I made (mostly on your feedback). I’m planning to merge in the late afternoon/early evening.

Cool, changes all look good to me! 🚢

Update: all the follow-on stuff is done now. There was one correction I had to add (a badly geocoded location was causing a place to match to the wrong saved store data), 9 weird entries that had collided (I think they may have been colliding even before this change), and then all the old external IDs to remove.
In the case of old external ID removals, they are all still available (in case we discover we did something bad) in meta.former_external_ids. For example, in https://getmyvax.org/api/edge/locations/be2c9f41-0594-40cf-97ba-51c052cc6746
{
  id: "be2c9f41-0594-40cf-97ba-51c052cc6746",
  provider: "albertsons_united",
  location_type: "PHARMACY",
  name: "United 0533 United",
  address_lines: ["3400 River Road"],
  city: "Amarillo",
  state: "TX",
  postal_code: "79107",
  county: null,
  position: {
    longitude: -101.8322757,
    latitude: 35.2481958,
  },
  info_phone: null,
  info_url: null,
  booking_phone: null,
  booking_url: "https://www.albertsons.com/pharmacy/covid-19.html",
  description: null,
  requires_waitlist: false,
  meta: {
    time_zone: "America/Chicago",
    vaccinespotter: {
      brand: "united",
      brand_id: 18,
      provider: "albertsons",
    },
    former_external_ids: [
      ["albertsons_store_number", "united:0533"],
      ["albertsons_store_number", "united:533"],
      ["united", "0533"],
      ["united", "533"],
    ],
  },
  created_at: "2021-05-24T17:23:48.240Z",
  updated_at: "2021-05-24T17:23:48.240Z",
  external_ids: [
    ["albertsons", "1600104192608"],
    ["albertsons_store_number", "united:133"],
    ["albertsons_united", "1600104192608"],
    ["united", "133"],
    ["vaccinespotter", "1046423"],
  ],
  availability: {
    sources: ["univaf-albertsons"],
    valid_at: "2022-06-10T22:16:19.000Z",
    checked_at: "2022-06-10T22:27:07.716Z",
    available: "NO",
    changed_at: "2021-11-28T20:38:28.000Z",
  },
}


native_pdf_renderer render image with black BG

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

@eliaweiss can you attach file?

If I attach the document I will open it again


API incompatibility with meteor/http default timeout

Hi,
I am not sure if the library is still maintained. We used this to migrate to latest meteor in our projects without changing much syntax for http calls except the http timeout setting.
With the Abort Controller implementation in this library, the default timeout is set to 90s.
But, the original meteor/http library does not have a default timeout at all.
Refer - https://docs.meteor.com/api/http.html#HTTP-call

timeout Number
Maximum time in milliseconds to wait for the request before failing. There is no timeout by default.

Please update this in the docs regd. preserving original API functionality, or remove the default timeout setting.
Thanks!

Hi @sree-qlp this package is still maintained. I could think of using -1 to indicate no timeout and use this as a default value, leaving the option to still pass a timeout, if desired. Would you help me with reviewing the PR?

Hey @jankapunkt thank you for the response. Absolutely! happy to help :)

@sree-qlp please review #7 thank you!

published as 2.3.0


Port setup invoked before operator setup and port teardown after operator teardown

This is the lifecycle
port.setup()
operator.setup()
operator.teardown()
port.teardown()

why?

port is a component inside an operator and instantiated before the operator so  preferably should be setup before it as well. Only when the child components are setup we should setup the encompassing component  because it  may depend on its child components setup.

Instantiation of the ports starts after the instantiation of operator
already begins. The lifecycle of the port begins after the lifycycle of
operator and it ends before that of operator.
On Fri, Jul 24, 2015 at 1:13 PM, Chandni Singh<EMAIL_ADDRESS>wrote:

port is a component inside an operator and instantiated before the
operator so preferably should be setup before it as well. Only when the
child components are setup we should setup the encompassing component
because it may depend on its child components setup.
—
Reply to this email directly or view it on GitHub
https://github.com/DataTorrent/Apex/pull/82#issuecomment-124704184.


Adds compatibility for Apollo 3

compatibility for Apollo 3
minor update of dependencies
added node version for Volta

Thank you for the PR!
What changes were essential for make it compatible with Apollo server 3? Is it still compatible with Apollo server 2.x?
Also, I prefer not to include anything else other than the purpose of this PR such as adding node version for volta. (Having one topic per PR is preferable)

I’ll reduce the scope of the changes. I understand.

I have taken out Volta Node version from package.json.
At the moment I don't have any Apollo 2 project ready to test compatibility.


added spot_price value for node_pools

This is the third missing piece from the other 2 pr I did (https://github.com/sighupio/furyctl/pull/43 and https://github.com/sighupio/fury-kubernetes-aws/pull/51), that allows covering all the spots behind the spot-instance capability feature.
Feedbacks are welcome! 🙏

I suggest to think about the interface of the new "spot" feature.
Would it makes sense something like:
node_pools = [
{
min_size = 1
max_size = 2
...
spot = {
  enable = true # Require in EKS, GKE, AKS
  price = 0.11231223 # Require only in EKS
}
}
]

I know in azure and gke they don't need the price but it required to configure the right attribute. This way, we can maintain the same interface across cloud (aks,gke,eks) installers.
What do you think?

Is price mandatory? Usually you use the AWS default, see https://github.com/sighupio/fury-kubernetes-aws/blob/master/modules/aws-kubernetes/kube-worker-spot.tf (there is no price here).
If you set the price, and aws increases the price, your instances will no more start up

@angelbarrera92 ... I really don't get it... the only entry point in fury for piloting the setup is the yaml, so, why make a "common interface" also in Terraform that is the implementation? It makes no sense because in the implementation you only leave the real needed parameter.... No need to maintain parameters that the implementation doesn't need

@nutellinoit, we are using in our module the babenko eks official module: https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/docs/spot-instances.md#using-launch-configuration .
Our implementation follows that launch configuration setup, so the only way to do that is to pass the spot_price, as the documentation says

@angelbarrera92 ... I really don't get it... the only entry point in fury for piloting the setup is the yaml, so, why make a "common interface" also in Terraform that is the implementation? It makes no sense because in the implementation you only leave the real needed parameter.... No need to maintain parameters that the implementation doesn't need

Because this was the main design decision we made with the cloud installers.

@nutellinoit, we are using in our module the babenko eks official module: https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/docs/spot-instances.md#using-launch-configuration .
Our implementation follows that launch configuration setup, so the only way to do that is to pass the spot_price, as the documentation says

Understood. What happens when the spot instances costs more than the price set?

Because this was the main design decision we made with the cloud installers.
Ah ok

@nutellinoit :

The spot_price is set to the on-demand price so that the spot instances will run as long as they are the cheaper.

As far as I understood, (and this is what I know regarding the spot instances), you'll be notified with a notification/event and that the instance will be shut down.
This is the nature of the spot instance. But for this reason, I made the deployment of the aws-node-termination-handler: https://github.com/sighupio/fury-kubernetes-aws/pull/51

mmmm this is not how the babenko terraform module works afaik: https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/docs/spot-instances.md#using-launch-configuration as you can see here @lnovara, the discriminant parameter is to set a value in the parameter spot_price otherwise it will be considered as a normal instance. So going back to the furyctl implementation: when you need to inject the spot instance parameter: https://github.com/sighupio/furyctl/pull/43/files#diff-9dfba49c7818625d480d2ebe3e00b2ef393faa4fbb30aa3bd9f55ef53416cb39R39 there is a struct that need to filled up in both its parameters (bool and price) when you're on EKS, while for GKE you only need the boolean.


Missing Information in Project Places (metric)

Hello, I was reviewing our metrics on Project Places (https://github.com/chaoss/wg-diversity-inclusion/blob/master/goal_project_places.md) and I think we should include the following additional aspects in the document:
What do you think? Perhaps we can discuss this in our next call?

Sample Objectives:

(Information Amount) Documentation provides information so that people gather as much information as they want, and no more than they want
(Learning by Doing) Documentation encourages hands-on learning, but doesn’t require it
(Learning by Process) Documentation provides not only details of every step, but also how these steps fit together in the process

Sample Strategies:

Use the GenderMag Heuristics to evaluate the document’s gender-inclusivity. (http://gendermag.org/downloadables/GM-Heuristics-2018-0704.pdf )

Sample Metrics:

Gender-inclusivity:
TODO: what result will indicate good diversity and inclusion?
“Score” on the GenderMag Heuristics (count of how many supported out of 5)
“Score” on the “Sample Objective” list (count of how many supported out of the length of the list)

Thank you @dicortazar for helping me with this issue.

Thanks Anita.

@asarma with some reorg of the repo, I am not sure if this is happened, or is still relevant.  Can you please update?  Thanks

http://gendermag.org/downloadables/GM-Heuristics-2018-0704.pdf < does not exist anymore :(

https://gendermag.org/Old_GM_Site/downloadables/GM-Heuristics-2018-0704.pdf < new link

Closing until we revisit this metric.


Migrate to MOI 0.10

Quite a few breaking changes in MOI recently: https://github.com/jump-dev/MathOptInterface.jl/releases/tag/v0.10.0. One breaking change is already planned for CP 0.5 (https://github.com/dourouc05/ConstraintProgrammingExtensions.jl/milestone/7), hence I'm targeting 0.6 to ease updating solvers.

Solved in great part with the last few commits (ending at c8206a75f2e53a3bd92f677aa0efcfd275d086ea). The tests should still be migrated away from MOI.DeprecatedTests. There may be a few tests that no more pass, though.

A lot of failing tests have been fixed (up to 7ed65b8).

The tests are now migrated; time to tag 0.6.


Sharing conda environment with host

Is it possible to share the host conda environments with the containers, and have them execute under a given environment?

Personally, I think although it is doable, sharing the host conda environments with the containers might affect the local environment. It is not very safe.
I am also not an expert in docker, if you find some better way to execute the generated code, welcome to submit a pull request! Thanks!


Cannot start remote ac

I have another error in my MG4 integration
2023-10-27 06:20:37,585 A/C will be switched on
2023-10-27 06:20:37,585 Error while processing MQTT message: temperature_idx must be between 0 and 14
Traceback (most recent call last):
  File "/usr/src/app/mqtt_publisher.py", line 70, in __on_message
    self.__on_message_real(client, userdata, msg)
  File "/usr/src/app/mqtt_publisher.py", line 91, in __on_message_real
    self.on_mqtt_command_received(vin, msg)
  File "/usr/src/app/./mqtt_gateway.py", line 316, in __on_mqtt_command_received
    vehicle_handler.handle_mqtt_command(msg)
  File "/usr/src/app/./mqtt_gateway.py", line 181, in handle_mqtt_command
    self.saic_api.start_ac(self.vin_info, temperature_idx=self.vehicle_state.get_ac_temperature_idx())
  File "/usr/local/lib/python3.10/site-packages/saic_ismart_client/saic_api.py", line 277, in start_ac
    return self.control_climate(vin_info, fan_speed=2, ac_on=None, temperature_idx=temperature_idx)
  File "/usr/local/lib/python3.10/site-packages/saic_ismart_client/saic_api.py", line 324, in control_climate
    raise Exception('temperature_idx must be between 0 and 14')
Exception: temperature_idx must be between 0 and 14

@tosate I think it's best to remove the saic_api.py check, on an MG4 the idx can go up to 19 (33C or MAX as shown in the app)

Fixed in 0.5.x, feel free to re-open if it still stands


Deprecate the model_size property on the LightningModule

🚀 Feature
We are auditing the Lightning components and APIs to assess opportunities for improvements:

https://docs.google.com/document/d/1xHU7-iQSpp9KJTjI3As2EM0mfNHHr37WZYpDpwLkivA/edit#
https://github.com/PyTorchLightning/pytorch-lightning/issues/7740#issuecomment-876780318

One item that came up on the LightningModule API was the ambiguity of the model_size property: https://github.com/PyTorchLightning/pytorch-lightning/blob/1ad1a89c09e6e8857f4fe680e23644a5013011d0/pytorch_lightning/core/lightning.py#L2073-L2084
The value this property provides is ambiguous, and its implementation of dumping the module to a file to check the size is suboptimal. To reflect this, we'd like to deprecate the property off the core API. If this is still needed, this could be a utility function which accepts an nn.Module and returns the size.
@awaelchli @Borda

Hryt @ananthsub,
I think it is a good remark and it won t scale well with larger model.
Mind doing the depreciation ?
Best,
T.C

Hi @ananthsub
This was a contribution by the community. I vote for deprecation in favor of a utility function :)

I noticed the sub-optimal implementation of model_size and came up with two (maybe better) options:
@property
def model_size(self):
    # Uses a BytesIO buffer instead of writing to disk (this will cost RAM so may not be desirable)
    # See https://stackoverflow.com/questions/26827055/python-how-to-get-bytesio-allocated-memory-length/26827410
    with io.BytesIO() as f:
        torch.save(self.state_dict(), f)
        f.seek(0, io.SEEK_END)
        size_mb = f.tell() / 1e6
    return size_mb

@property
def model_size(self):
    # This is a naive way to get the size of the tensors in the `state_dict()` per discussion here https://discuss.pytorch.org/t/how-to-know-the-memory-allocated-for-a-tensor-on-gpu/28537
    # Better way to do it https://github.com/Stonesjtu/pytorch_memlab/blob/master/pytorch_memlab/mem_reporter.py#L17
    size_mb = 0
    for k, v in self.state_dict().items():
        size_mb += v.element_size() * v.nelement()
    size_mb /= 1e6
    return size_mb

I would be happy to do this in a utility function!

I would be happy to do this in a utility function!

Thanks @calebrob6 ! #8495 will deprecate this off the core LightningModule API. A separate function under https://github.com/PyTorchLightning/pytorch-lightning/tree/master/pytorch_lightning/utilities for a model size that accepts an nn.Module could be useful in parallel. If you have a chance, feel free to contribute this 😄

This was a contribution by the community. I vote for deprecation in favor of a utility function :)

Not really, this was added by @Borda in https://github.com/PyTorchLightning/pytorch-lightning/pull/5706
as we already have a model_size "utility" in:
https://github.com/PyTorchLightning/pytorch-lightning/blob/4c79b3a5b343866217784c66d122819c59a92c1d/pytorch_lightning/core/memory.py#L261-L264
So the deprecation of the property in the LightningModule should also address its replacement.

I added a simple utility function + tests in https://github.com/PyTorchLightning/pytorch-lightning/pull/8500 before I saw the above. @carmocca are you saying that the model size functionality should belong in the ModelSummary class?

are you saying that the model size functionality should belong in the ModelSummary class?

Yes, as it is already supposed to compute model_size


Update grid layout for larger screens in App.css

This pull request includes a change to the src/App.css file to adjust the layout of the .Pictures class for screens with a minimum width of 1440px.

src/App.css: Modified the .Pictures class to use a 4-column grid layout instead of 3 columns and adjusted the left margin to be automatic instead of a fixed 200px.

Before

After

Thank you Villa


Added in decodeBody, check if is object. Created method to mark messa…

…ge as read.
Is the pull request based off the lastest version?
Yes
What features have you added?
On php-imap-client/ImapClient/IncomingMessage.php, method decodeBody, added "is_object" check to not generate notices.
On php-imap-client/ImapClient/ImapClient.php, created a new method "setSeenMessage" and user it on getUnreadMessages.
What bugs did you fix?
It isn't flagging the message as read.

Yes
Optional things below
[] Added your name to the credits
Luiz Fernando da Silva

Looks good. Thanks!


Update signing capability to sign GitHub Releases

Current Behavior -
Release binaries/artifacts must be pushed to an OCI compatible registry beforehand and thereafter notation can sign it.
Proposed Improvement -
Investigate in enhancing Notation signing capability to sign releases/binaries/artifacts published on GitHub Releases. In general release artifacts/binaries would be published in GitHub Releases, therefore supporting this capability can promote adoption better.

I believe this is similar to https://github.com/notaryproject/notation/issues/741


Socialauth

General Checkups

[*] Have you checked that there aren't other open pull requests for the same issue/update/change?
[ ] If your code includes new features and not just bug fixes/copy editing: Did you include new tests?

Description
Activate django-allauth's social login feature
Related Issue
#863

TODO still:
Better handling of existing email.  Will probably include a login link that includes the page where you add social accounts as the ?next= parameter
Tests

@jhdulaney sorry, going ahead with review requires having app information for all three providers, and registering them as SocialApp objects in the admin interface. I can do that, but...

It would be very helpful to have some client secrets/IDs to use to register these? (kbfs works for me) or, if not that, some pointer on where to go to register for all three?

Related to that, did you set up any sort of generic "Open Humans" developer account with any/all of these providers? (I want to check if there's some team-level account information we should store in 1password.)

@jhdulaney sorry, going ahead with review requires having app information for all three providers, and registering them as SocialApp objects in the admin interface. I can do that, but...
1. It would be very helpful to have some client secrets/IDs to use to register these? (kbfs works for me) or, if not that, some pointer on where to go to register for all three?

2. Related to that, did you set up any sort of generic "Open Humans" developer account with any/all of these providers? (I want to check if there's some team-level account information we should store in 1password.)

I can setup some Open Humans dev accounts.

Some questions...

Facebook is asking me to re-enter my password, despite already being logged in to FB. I didn't expect this. Can this be avoided?

When FB returned me to the signup and I had an existing email -- why offer signup if we can already see the email is taken?

The Twitter connection doesn't ask for email address. Is that not an available option?

The Twitter connection also asks for permissions I don't think it needs - it's able to post tweets and update my profile. Is asking for these unavoidable?

And notes for myself -- some pages I might look at to make my own style/html code suggestions (i.e. don't worry about addressing these):

/account/login/
login modal
/account/login/?socialsignup=true&next=/account/social/connections/

Some questions...
1. Facebook is asking me to re-enter my password, despite already being logged in to FB. I didn't expect this. Can this be avoided?

I have not encountered this, so I am unsure as to the conditions that trigger it.  I will investigate.

2. When FB returned me to the signup and I had an existing email -- why offer signup if we can already see the email is taken?

Yeah, that's probably a better way to do things.

3. The Twitter connection doesn't ask for email address. Is that not an available option?

I am somewhat unsure about this.  I have read that Twitter does not provide email addresses, but I have also read that they do (both in Twitter's own docs).  I'm going to have to investigate this a bit.

4. The Twitter connection also asks for permissions I don't think it needs - it's able to post tweets and update my profile. Is asking for these unavoidable?

The allauth docs don't mention any way to control what Twitter asks for, though allauth does provide a mechanism for that with Google and Facebook.

And notes for myself -- some pages I might look at to make my own style/html code suggestions (i.e. don't worry about addressing these):
* /account/login/

* login modal

* /account/login/?socialsignup=true&next=/account/social/connections/

For the bit where right now we are taken to the signup form instead of a login form, allauth has not yet implemented this.  I will work with upstream to get this done.

Let's add comments to the HTML or other code that link to where assets come from

Re @gedankenstuecke's note "when a user is trying to login via their username but only having used social login before it will throw a generic error message as there is no valid password" → I'm in favor of ignoring this edge case and letting the user reset the password. This should work, and my recollection is that this is how many/most sites end up handling the scenario.

Mh... The error message reads Error: The username and/or password you specified are not correct.. Do we feel that this prompts people to request a password reset? I feel the message is so vague that I might just doubt I put in the right username?

Merged


problem with gradients in Opera (again)

Hi!
I'm getting error in Opera (but not on all sites)
Console is throwing out:
Error thrown at line 68, column 2 in <anonymous function: link>(link) in ../prefixfree.js:
    link.setAttribute('data-inprogress', '');
called from line 125, column 2 in <anonymous function>() in ../prefixfree.js:
    $('link[rel="stylesheet"]').forEach(StyleFix.link);

I guess this is not happening any more, right?

It was apparently the bug in my CSS hitting the Opera 12 (linux version). Can't re-produce this now ;-/


Bitcoin Cash support?

It probably already works, but is untested.  Give it a try.

It looks like it doesn't. SIGHASH_FORKID needs to be implemented.

I want to take a stab at this in my free time, mostly just to make all these "news" sites claiming that atomic swaps require segwit to look dumb :)
So far I have forked the tool and am creating (invalid) signatures with SIGHASH_FORKID set.  The signatures are invalid since this sighash flag completely changes the sighash algorithm and sigs no longer validate.  Next step is to implement the correct FORKID sighash algorithm.

Thanks!

@jrick I can help test if you need. I have a bitcoin ABC node.

This should be a fairly simple fix. Might even want to add a --cash option to btcatomicswap. That should please the Bitcoin Cash supporters. 😄

Do you need help?


TFT doesn't come back after VDC failure

with testnet network
first scenario:
when i pay from TF connect app and got transferred successful
got this after waiting:

and 15 TFT has been deducted
second scenario:
i tried again and payment worked fine but got this error

and 15 TFT has been deducted

Errors were fixed successfully after stellar node fix


obj-tables commandline help text

Hi Jonathan,
three minor points regarding the help text of the obj-tables commandline  tool:
o specify order of commandline arguments
o mention the supported image file formats (or file extensions) for viz-schema
o explain the option --write-schema
Thank you!

Argument order
The program does describe the order of the arguments. For example,
obj-tables init-schema --help

Displays
usage: obj-tables init-schema [-h] in_file out_file

Initialize a Python schema from a declarative description of the schema in a table (Excel, CSV, TSV)

positional arguments:
  in_file     Path to the declarative description of the schema (.csv, .tsv,
              .xlsx)
  out_file    Path to save Python schema (.py)

Image formats
obj-tables viz-schema --help describes the supported image formats. GraphViz supports much more than this. If needed, we can expose those other formats.
usage: obj-tables viz-schema [-h] schema_file img_file

Generate a UML diagram for a schema

positional arguments:
  schema_file  Path to the schema (.py) or a declarative description of the
               schema (.csv, .tsv, .xlsx)
  img_file     Path to save a UML diagram of the schema (.pdf, .png, .svg)

--write-schema option
I clarified the help string for this. This instructs ObjTables to save a pretty-printed copy of the schema within the outputted document. I thought this could be useful for sharing documents which use custom schemas with other people. In that case, this option makes it easy to bundle the schema with the document. (We likely won't use this for wc-lang or wc-kb because those schemas are defined in Git repositories.)


Policy CSP/DeviceInstallation: add missing path folder DeviceInstallation

Proposed change:

Add the omitted folder name to the LocURI path in the SyncML sample for DeviceInstallation/PreventInstallationOfDevicesNotDescribedByOtherPolicySettings

All the other SyncML samples contain the correct path, except for this one.
Even the section title for this sample states that the key sorts under "DeviceInstallation",
as well as the DeviceInstallation policies list (link list) on top of the page.
The policy path format is also documented in the page https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-configuration-service-provider .
Resolves #2988
ToDo/Unsolved cases:
I have not searched for other occurrences of this omission error, but I have asked the OP in issue #2988 if he knows of/has found this error on any other pages.

@Justinha - would you be able to merge the content for this PR based on issue #2988? OR do you happen to know who is the new article owner that we can reach out to check and merge the PR content?
Thank you.


[UNDERTOW-2241][UNDERTOW-2247][UNDERTOW-2248] Handle write timeout properly so no chunk errors occur

Jiras:
https://issues.redhat.com/browse/UNDERTOW-2241
https://issues.redhat.com/browse/UNDERTOW-2247
https://issues.redhat.com/browse/UNDERTOW-2248
2.2.x backport PR: #1450

This failed Windows CI. I'll have to do an investigation of the reason for the failure.

Everything indicates the failure in the fix UNDERTOW-2247 is not fully correct. The failure in Windows is a race condition and it requires further work. I'll get back to this after my PTO, on May.

I'm closing for now. Will reopen when I get back to it.

Something odd happened wiht this PR that, even after 10 minutes of having pushed my branch, the PR was not updated, but I could see the branch was updated by following the link from the PR page to the branch.
I ended up having to close it and create a new one, unfortunately :-(

The new PR is #1489

I had to recreate a new PR for the same reason :-(
New PR is #1490


The definition of cco:Organism is too narrow

The present definition is "An Object that is an Animal or Plant." This rules out bacteria, fungi, and hence is at odds with scientific standards.

OBI definition: "A material entity that is an individual living system, such as animal, plant, bacteria or virus, that is capable of replicating or reproducing, growth and maintenance in the right environment. An organism may be unicellular or made up, like humans, of many billions of cells divided into specialized tissues and organs."
This is the most reused class by other ontologies within Bioportal. The definition doesn't quite follow best practices. Notably it doesn't restrict organisms to being objects. I am ok with that.
We can redefine along these lines: "A material entity that is an individual living system, capable of replicating or reproducing, growth and maintenance in the right environment.
Examples: Animal, Plant, Bacteria, Virus.
Elucidation:  An organism may be unicellular or made up, like humans, of many billions of cells divided into specialized tissues and organs.
source: http://purl.obolibrary.org/obo/OBI_0100026
Maybe add an equivalency axiom to the OBI IRI.
Interesting to note that there is comment on the OBI term that says it's a placeholder. Dated 2009 :/

I've objected to the OBI definition in print because the second sentence suggests viruses are cellular, which is false.
The proposed definition takes a stand on viruses being alive, which is a contentious issue we should be neutral on; also the elucidation suggests viruses are cellular.

@johnbeve would removing 'virus' form the list of examples address your concern?
Or do we want a def for 'organism' to include viruses?

@mark-jensen I'm in favor of removing 'virus' from the scope; there are other agents viruses can be grouped with, e.g. viroids, satellites, prions, etc. and in general I think 'organism' is associated with 'living' or 'metabolizing' entities. VIDO provides such a classification.
I  think we should avoid saying 'living' in the definition too, since including it in the definition and not having virus as a subclass would also suggest we're taking a stand. Better, I think, to remain neutral over what counts as 'living' since there are thorny issues around its use scientists need to work out.

We should also avoid "such as [example 1], [example 2]" locutions in definitions.

The OBI definition is marked as placeholder because it was thought it should be in some other domain ontology.
@johnbeve the second sentence should be understood  as a comment rather than definitional.
Having a definition of organism that deviates from OBI's, by excluding viruses is a bad idea, IMO. They are subject matter experts, not us.

@jonathanvajda I think the problem may be broader than that. Consider the definition of Act of Mass Media Communication:
An Act of Communication intended to reach a large audience using a medium such as
the internet, television, radio, newspaper, and magazine.

The object of "such as" refers to the medium, not the act. You wouldn't want to end the definition with "medium". How would you rewrite it? I can think of two approaches:

Add to CCO a class denoting a medium capable of handling acts of mass media communications, and rewrite the definition to use the name of that class.
End the definition with "audience", and put the rest in an elucidation annotation.

Your thoughts?
Most of the definitions that use "such as" are structured this way.

@swartik I am currently working on a proposal to remove the artifact use from the communication hierarchy. There is an act of communication and separately an act of artifact use. The way it's modeled right now, President Nixon's famous "I am not a crook" is either an act of communication by mass media or an act of denial. Under certain circumstances, maybe this is permissible (for an instance to be rdf:type two different communication classes) in some cases, but ultimately should be changed.


Application insights makes process restart every 60 seconds with maximum call stack size exceeded error.

RangeError: Maximum call stack size exceeded
at AppInsightsAsyncCorrelatedErrorWrapper.orig.prepareStackTrace (src\appName\node_modules\applicationinsights\out\AutoCollection\CorrelationContextManager.js:168:28)
at NativeError.prepareStackTrace (src\appName\node_modules\zone.js\dist\zone-node.js:900:30)
at AppInsightsAsyncCorrelatedErrorWrapper.orig.prepareStackTrace (src\appName\node_modules\applicationinsights\out\AutoCollection\CorrelationContextManager.js:168:28)
at NativeError.prepareStackTrace (src\appName\node_modules\zone.js\dist\zone-node.js:900:30)
at AppInsightsAsyncCorrelatedErrorWrapper.orig.prepareStackTrace (src\appName\node_modules\applicationinsights\out\AutoCollection\CorrelationContextManager.js:168:28)
at NativeError.prepareStackTrace (src\appName\node_modules\zone.js\dist\zone-node.js:900:30)
at AppInsightsAsyncCorrelatedErrorWrapper.orig.prepareStackTrace (src\appName\node_modules\applicationinsights\out\AutoCollection\CorrelationContextManager.js:168:28)
at NativeError.prepareStackTrace (src\appName\node_modules\zone.js\dist\zone-node.js:900:30)
at AppInsightsAsyncCorrelatedErrorWrapper.orig.prepareStackTrace (src\appName\node_modules\applicationinsights\out\AutoCollection\CorrelationContextManager.js:168:28)
at NativeError.prepareStackTrace (src\appName\node_modules\zone.js\dist\zone-node.js:900:30)
at AppInsightsAsyncCorrelatedErrorWrapper.orig.prepareStackTrace (src\appName\node_modules\applicationinsights\out\AutoCollection\CorrelationContextManager.js:168:28)
at NativeError.prepareStackTrace (src\appName\node_modules\zone.js\dist\zone-node.js:900:30)
This happens after a Duplicate key error gets thrown repeatedly which should be ignored in my application. Process restarts because of the above error but does not do it when app insights is not configured.
Please suggest a solution.

https://github.com/OsvaldoRosado any comments?

As a quick mitigation, you may be able to stop this error by using setAutoDependencyCorrelation(false) to disable automatic dependency correlation when configuring the SDK.
It looks like there's a problem with the error wrapper that is causing an infinite loop. Are you able to condense this into a small repro code? That would significantly help in root causing this issue

function checkForUpdates (Db1, Db2, queue){
return Promise.join(
Db1.getItems(),
Db2.getItems(),
(Db1Items, Db2Items)=>{
  let requestItems = Db2Items.filter(sourceItem=>{
    let targetItem = _.find(Db1Items, {Id: sourceItem.ItemId});
    // Update if item does not exist in database 1
    if(!targetItem ) return true;
    // or if have older version than in Datawarehouse(DB2) tables
    return (sourceItem.Serial > targetItem .Serial);
  });

  return Promise.map(requestItems , sourceItem=>{
    let itemId= sourceItem.ItemId;
    return queue.add(itemId)
      .then(added=>{
        log.info(`Item ${itemId} was queued for importing`);
      })
      .catch(err=>{

// This is the catch block that is throwing the duplicate key error because the items that are added may //already be in the queue and hence being caught here repeatedly. Before I added //insights.trackException, this wasn't a problem but now after a certain number of catches, it crashes with //the error I posted above and restarts the process.
log.error(err);
insights.trackException(err);
});
});
});
}
function main(config) {
log.info(Connecting to databases....);
const start = + new Date;
return Promise.all([
DB1.connect(config.Database1),
DB2.connect(config.Database2),
queue.connect(config.QueueDB),
]).spread((Db1, Db2, queue)=>{
const done = + new Date;
const duration = (done - start);
insights.trackDependency('DB1, DB2', 'connections to DBs', duration, true, 'SQL');
function doit () {
insights.setOperationId();
const startCheckUpdate = + new Date;
log.info(Checking updated items in Datawarehouse...Start time =${startCheckUpdate});
checkForUpdates(Db1, Db2, queue)
.catch(error => {
log.error(Error was thrown at ${new Date} while checking for updates. error -> ${JSON.stringify(error)});
insights.trackException(error);
insights.trackTrace(JSON.stringify(error),'major');
})
.finally(()=>{
const doneCheckUpdate = + new Date;
const durationCheckUpdate = (doneCheckUpdate - startCheckUpdate);
log.info(Done checking for updates = End time = ${doneCheckUpdate}, finished in ${durationCheckUpdate} milliseconds);
insights.trackDependency('DB1, DB2', 'CHECK FOR UPDATES', durationCheckUpdate, true, 'SQL');
log.info(Updates are being checked at an interval of ${INTERVAL} seconds);
});
}
setInterval(doit, INTERVAL);
});
}
if (require.main === module){
let config = require('./config');
main(config).catch(err=>{
log.error(err);
process.exit(1);
});
}

Looks like its possible for prepareStackTrace on the error object to end in an infinite loop if its called multiple times. The wrapper never cleans up its overwrite of prepareStackTrace and thus begins to wrap itself infinitely. (See https://github.com/Microsoft/ApplicationInsights-node.js/blob/develop/AutoCollection/CorrelationContextManager.ts#L220 which always assumes the stackTrace method it's about to call is not itself)
Out of curiousity, do you stop having this problem if you remove log.error(err) before trackException ?

@diprochatterjee, would it be possible to get information about the stack frames in the beginning of the stack, so that we know what was the original call to .stack that triggered the chain of prepareStackTrace calls? Perhaps you could either provide a repro snippet that we could turn into a unit test, or try debugging on your side and put a breakpoint inside AppInsightsAsyncCorrelatedErrorWrapper to see what triggered the call chain.

I have already provided a snippet of the code that was the cause/zone where the error is coming from. I will try debugging with breakpoints and provide the information to you soon.

Thanks @diprochatterjee. In your snippet, do you happen to know which call is causing the start of prepareStackTrace() chain? There are quite a few ones that can potentially call .stack internally. Also if you could reduce your snippet to a runnable one that would be great. Thanks so much for helping us here.

Moving out of 0.22 release as we don't have a repro right now.

I got such error on v1.0.4 :(

@dmytro-lymarenko Can you provide a code sample that reproduces the problem? Is your call stack the same as the one quoted in the issue description?

I got problems when i initiated (appInsights.setup(..)....) to early, now I'm initiating when my express app has booted, seems to work atm.

I have the issue intermittently, and only at startup. The application crashes with this error. Restarting it will usually solve the problem for some time, which makes it impossible to reproduce in a smaller project.
It seems to fail even without initializing first when the library is imported.
I'm using 1.0.7.
There might be another root cause external to AI but I can't really tell...
Might I suggest, since we know it happens in a few different cases, to count recursive errors and after 10 iterations, log an error saying the log was dropped and let the error bubble up? I guess we won't be able to easily reproduce the root cause(s) but at least when it happens it won't bring everything down with it!
What do you think? Should this be reopened?


Add spinner module

resolve #79

Memo

Set remove logic on whole pages
Add class opacity-0 to the elements that will be hidden during the first rendering.


DAG for Monitoring Single SQS Queue for all Groups

Fixes #183
Part of refactoring to use a single SQS queue for all groups in Sinopia instead of each institution having it's own queue.

Trying to address the -0.2% drop in coverage seems pointless.


Change isNaN and isFinite

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/isNaN
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/isNaN
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/isFinite
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/isFinite

Please note that Number.isNaN() !=  isNaN()`, which is clearly documented in the linked MDN articles, hence that this could very easily introduce bugs in some cases.
Furthermore, generally speaking this format just feels overly/unnecessarily verbose.


Can conditional helper login used in content_cache

I have some helpers that with condition
e.g. link_signinout
which create a link to sign out if user signed in, and a link to sign in if user signed out.
if user_signin?
   ...
else
  ...
end

The {{cms:helper:link_signinout}} is used in my page.
I found that Comfy put the contents into database via content_cache
Can I ask if my conditional helper got snapshoted cached or it will rendered dynamically?
Thanks

content_cache will be holding <%= link_signout %> so it will be dynamic


ci: fix docs-sphinx test

The docs-sphinx CI test seems to time out due to troubles with figuring out the proper dependencies:

We may need to provide some version hints and/or check the resolver technique so that the RTFD build is not trying out so many versions...

Was this fixed with the new schema-salad release or is it a different problem? @audrium @tiborsimko

Yep, this was fixed with the new schema-salad release. Doubled checked the latest CI run, it had the latest schema-salad 8.2.20210914115719 version and ran without any problems. Closing


encoding/csv: documentation of UseCRLF is incomplete

According to the documentation of the UseCRLF flag here:
https://github.com/golang/go/blob/946e2543f878929752da9d16575dd5e96ac78532/src/encoding/csv/writer.go#L23
it only influences the line terminator. When looking at the code one can see that setting that flag to true also impacts the output of the cell content: \r is removed and \n replaced by \r\n.
This behavior should also be reflected in the documentation!

csv doesn't escape newlines in cell contents, so if there's a newline in a cell it is also the end of an output line.
"hello", "foo\nbar", "world"
as csv would be
hello,"foo
bar",world

You're right. What I meant when writing \r and \n was the characters 13 and 10.
So to be clear: If UseCRLF is true a string of chars 0x41 0x0d 0x42 will become 0x22 0x41 0x42 0x22. So a quoted string where the 0x0d is removed (see here: https://github.com/golang/go/blob/8b471db71b95e9250f751f494a6a5359cb50d5cd/src/encoding/csv/writer.go#L89)
On the other hand  0x41 0x0a 0x42 becomes 0x22 0x41 0x0d 0x0a 0x42 0x22 (see here: https://github.com/golang/go/blob/8b471db71b95e9250f751f494a6a5359cb50d5cd/src/encoding/csv/writer.go#L97)
I think this is important to know, so the documentation should tell you about that behavior.

I understood that part, I'm saying that because it's not escaped in csv, an output line != single record and it changes all output line endings, not just end of record endings.
But feel free to send a PR/CL with what you think would make it clearer


Add support for multiple databases

Add a variable to the config file that specifies the database system for the PDO connection.

Please check the pull request. And check if any changes are to be made. I could figure out just adding one variable for storing the type of database the user is going to use.


[backport v1.14] Bluetooth: SMP: fix for bt fixed passkey BT_PASSKEY_INVALID

When BT_PASSKEY_INVALID was set, it never updated the fixed
passkey which made its use ineffective.
Signed-off-by: Faisal Saleem<EMAIL_ADDRESS>Backport from pull request: https://github.com/zephyrproject-rtos/zephyr/pull/32198

Can you rebase now that the doc building is fixed.

Hi @Vudentz


Reorganize code structure

In particular:
src/chart -> scr/codebook
src/chart/renderRow/makeChart -> src/charts

Renaming the chart types:

Bar Chart -> Horizontal Bars
Level Plot -> Vertical Bars
Histogram -> HistogramBoxPlot
Dot Plot - No change

Note to self: Need to update the summaryData.chartType for the new names.

Also going to take the chart.init() call out of the createChart() functions to more closely mirror the standard renderer pattern.

On second thought - going to leave chart.init() as is for now. Our implementation of grouped charts is non-standard here, so the standard pattern isn't trivial. Might be worth considering whether this is all doable with webcharts.multiply()  but not for v1.0.0

Test Notes: confirmed in code review. No test needed.


chore: bdd-spring-1574594354 to 0.0.1

chore: Promote bdd-spring-1574594354 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


flutter_test needs to be updated to support the latest analyzer.

Steps to Reproduce

Open Terminal & type flutter create sample_project
type cd sample_project
type flutter packages get
type code pubspec.yaml

VSC should open the pubspec.yaml file.

add the dependencies for JSON Serializable
Return to Terminal & type flutter packages upgrade
the command will fail with the following message:

Because every version of flutter_test from sdk depends on analyzer 0.31.2-alpha.2 and json_serializable >=0.5.3 depends on analyzer ^0.32.0, flutter_test from sdk is incompatible with json_serializable >=0.5.3.
So, because jam2018 depends on both json_serializable ^0.5.4 and flutter_test any from sdk, version solving failed.
pub get failed (1)
Corresponding issue report at JSON Serializable repo
Logs

[sample_project]$ flutter packages upgrade --verbose
[  +30 ms] [/Users/wooldridgetm/Development/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +39 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/beta
[        ] [/Users/wooldridgetm/Development/flutter/] git rev-parse --abbrev-ref HEAD
[  +12 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] beta
[        ] [/Users/wooldridgetm/Development/flutter/] git ls-remote --get-url origin
[   +9 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[        ] [/Users/wooldridgetm/Development/flutter/] git log -n 1 --pretty=format:%H
[  +19 ms] Exit code 0 from: git log -n 1 --pretty=format:%H
[        ] c7ea3ca377e909469c68f2ab878a5bc53d3cf66b
[        ] [/Users/wooldridgetm/Development/flutter/] git log -n 1 --pretty=format:%ar
[  +14 ms] Exit code 0 from: git log -n 1 --pretty=format:%ar
[        ] 3 weeks ago
[        ] [/Users/wooldridgetm/Development/flutter/] git describe --match v*.*.* --first-parent --long --tags
[  +27 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[        ] v0.5.1-0-gc7ea3ca
[ +134 ms] Running "flutter packages upgrade" in sample_project...
[   +4 ms] [/Users/wooldridgetm/Development/flutterStudio/sample_project/] /Users/wooldridgetm/Development/flutter/bin/cache/dart-sdk/bin/pub --verbosity=warning --verbose upgrade --no-precompile
[+5084 ms] Because every version of flutter_test from sdk depends on analyzer 0.31.2-alpha.2 and json_serializable >=0.5.3 depends on analyzer ^0.32.0, flutter_test from sdk is incompatible with json_serializable >=0.5.3.
[        ] So, because sample_project depends on both json_serializable ^0.5.4 and flutter_test any from sdk, version solving failed.
[  +37 ms] "flutter upgrade" took 5,205ms.
pub upgrade failed (1)

#0      throwToolExit (package:flutter_tools/src/base/common.dart:28)
#1      pub (package:flutter_tools/src/dart/pub.dart:168)
<asynchronous suspension>
#2      pubGet (package:flutter_tools/src/dart/pub.dart:104)
<asynchronous suspension>
#3      PackagesGetCommand._runPubGet (package:flutter_tools/src/commands/packages.dart:60)
<asynchronous suspension>
#4      PackagesGetCommand.runCommand (package:flutter_tools/src/commands/packages.dart:83)
<asynchronous suspension>
#5      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:344)
<asynchronous suspension>
#6      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:279)
<asynchronous suspension>
#7      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142)
<asynchronous suspension>
#8      _rootRun (dart:async/zone.dart:1126)
#9      _CustomZone.run (dart:async/zone.dart:1023)
#10     runZoned (dart:async/zone.dart:1501)
#11     AppContext.run (package:flutter_tools/src/base/context.dart:141)
<asynchronous suspension>
#12     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:270)
#13     CommandRunner.runCommand (package:args/command_runner.dart:194)
<asynchronous suspension>
#14     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:309)
<asynchronous suspension>
#15     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142)
<asynchronous suspension>
#16     _rootRun (dart:async/zone.dart:1126)
#17     _CustomZone.run (dart:async/zone.dart:1023)
#18     runZoned (dart:async/zone.dart:1501)
#19     AppContext.run (package:flutter_tools/src/base/context.dart:141)
<asynchronous suspension>
#20     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:265)
<asynchronous suspension>
#21     CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:109)
#22     new Future.sync (dart:async/future.dart:222)
#23     CommandRunner.run (package:args/command_runner.dart:109)
#24     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:174)
#25     run.<anonymous closure> (package:flutter_tools/runner.dart:59)
<asynchronous suspension>
#26     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142)
<asynchronous suspension>
#27     _rootRun (dart:async/zone.dart:1126)
#28     _CustomZone.run (dart:async/zone.dart:1023)
#29     runZoned (dart:async/zone.dart:1501)
#30     AppContext.run (package:flutter_tools/src/base/context.dart:141)
<asynchronous suspension>
#31     runInContext (package:flutter_tools/src/context_runner.dart:43)
<asynchronous suspension>
#32     run (package:flutter_tools/runner.dart:50)
#33     main (package:flutter_tools/executable.dart:49)
<asynchronous suspension>
#34     main (file:///Users/wooldridgetm/Development/flutter/packages/flutter_tools/bin/flutter_tools.dart:8)
#35     _startIsolate.<anonymous closure> (dart:isolate-patch/dart:isolate/isolate_patch.dart:277)
#36     _RawReceivePortImpl._handleMessage (dart:isolate-patch/dart:isolate/isolate_patch.dart:165)

[sample_project]$ flutter doctor -v
[✓] Flutter (Channel beta, v0.5.1, on Mac OS X 10.13.5 17F77, locale en-US)
    • Flutter version 0.5.1 at /Users/wooldridgetm/Development/flutter
    • Framework revision c7ea3ca377 (3 weeks ago), 2018-05-29 21:07:33 +0200
    • Engine revision 1ed25ca7b7
    • Dart version 2.0.0-dev.58.0.flutter-f981f09760

[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at /Users/wooldridgetm/Library/Android/sdk
    • Android NDK at /Users/wooldridgetm/Library/Android/sdk/ndk-bundle
    • Platform android-27, build-tools 27.0.3
    • ANDROID_HOME = /Users/wooldridgetm/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.4.1, Build version 9F2000
    • ios-deploy 1.9.2
    • CocoaPods version 1.5.2

[✓] Android Studio
    • Android Studio at /Applications/Android Studio 3.2 Preview.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b04)

[✓] Android Studio (version 2.3)
    • Android Studio at /Applications/Android Studio 2.3.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[✓] Android Studio (version 3.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 25.0.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)

[✓] IntelliJ IDEA Ultimate Edition (version 2018.1.4)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 24.2.2
    • Dart plugin version 181.4892.1

[✓] VS Code (version 1.24.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 2.13.2

[✓] Connected devices (1 available)
    • iPhone X • DB37E26D-A616-4EC2-B891-BA37E261586A • ios • iOS 11.4 (simulator)

• No issues found!

Any workaround yet?

just a workaround for me:
remove flutter_test, and use build_runner: "^0.8.10" for now.
and wait for flutter_test to be updated to support the latest analyzer.

dev_dependencies:
  # flutter_test:   # <-- remove this for now.
  #   sdk: flutter

  build_runner: "^0.8.10"  # <-- use this for now.
  json_serializable: "^0.5.8"

You could also try to add
dependency_overrides:
  analyzer: ^0.31.2-alpha.2

Same problem!
[app] flutter packages get
Running "flutter packages get" in app...
Because every version of flutter_driver from sdk depends on analyzer 0.31.2-alpha.2 and json_serializable >=0.5.3 depends on analyzer ^0.32.0, flutter_driver from sdk is incompatible with json_serializable >=0.5.3.
So, because tangbole depends on both json_serializable ^0.5.8 and flutter_driver any from sdk, version solving failed.
pub get failed (1)
exit code 1

@jaggerwang  have you got any solution for this because i am facing the same issue.

@deepakrana0011 the workaround proposed by @zoechi worked for me.

Just remove the test dependencies

@zoechi solution works.
commenting out test dependencies causes lots of dart errors in test\widget_test.dart
these dependency versions:
dev_dependencies:
  flutter_test:
    sdk: flutter
  build_runner: ^1.0.0
  json_serializable: ^1.5.0

causes this error:
Because every version of flutter_test from sdk depends on analyzer 0.33.0-alpha.0 and json_serializable 1.5.0 depends on analyzer ^0.32.2, flutter_test from sdk is incompatible with json_serializable 1.5.0.
And because no versions of json_serializable match >1.5.0 <2.0.0, flutter_test from sdk is incompatible with json_serializable ^1.5.0.
So, because mystrengths depends on both json_serializable ^1.5.0 and flutter_test any from sdk, version solving failed.

workaround was to add version number flutter_test demands:
dependency_overrides:
  analyzer: ^0.33.0-alpha.0

(Note: this warning just popped up for me in the last few days. This issue post solved it finally so I could run again.
It's easy to not have dependency issues in a 20y old platform where hardly any breaking changes are made ever.
I agree that some dependencies could be updated more quickly after dependencies introduced breaking changes, but the main problem is that Flutter is new and moving fast.
That allows you to use modern tech but has some disadvantages like that not all project can keep up with the pace.
What I think helps most is to create issues if dependencies need updates to notify maintainers.
Even better are pull requests ;-)

still have this error with: flutter upgrade
Flutter is already up to date on channel stable
Flutter 2.2.3 • channel stable • https://github.com/flutter/flutter.git
Framework • revision f4abaa0735 (7 weeks ago) • 2021-07-01 12:46:11 -0700
Engine • revision 241c87ad80
Tools • Dart 2.13.4
and here is the error:
Because every version of flutter_test from sdk depends on meta 1.3.0 and json_annotation >=4.1.0 depends on meta ^1.4.0, flutter_test from sdk is incompatible with json_annotation >=4.1.0.
So, because flutter_g_tms depends on both json_annotation ^4.1.0 and flutter_test any from sdk, version solving failed.
pub get failed (1; So, because flutter_g_tms depends on both json_annotation ^4.1.0 and flutter_test any from sdk, version solving failed.)


Implement tunnel RPCs

Need for vxlan
Plugged into Bridge
Create/Get/Delete/Update functions first implementation
Few todos and gaps inside still...
Signed-off-by: Boris Glimcher<EMAIL_ADDRESS>

example of object creation:
	testTunnel = pb.Tunnel{
		Spec: &pb.TunnelSpec{
			LocalIp: &pc.IPAddress{
				Af:     pc.IpAf_IP_AF_INET,
				V4OrV6: &pc.IPAddress_V4Addr{V4Addr: 336860161},
			},
			Encap: &pc.Encap{
				Type: pc.EncapType_ENCAP_TYPE_VXLAN,
				Value: &pc.EncapVal{
					Val: &pc.EncapVal_Vnid{Vnid: 100},
				},
			},
		},
	}

bridge needs to be attached to a VRF

bridge is attached already to VRF, which is VPC object... what is missing ?

Are we talking here about implementing L3VPNs symmetric IRB or L2VPNs ?


SAK-29518 updated Japanese translations

Japanese translation update from Hosei University. Encoding validated, files checked to make sure that only localized Japanese properties files are included, and Sakai started and each tool verified to not crash (and displays Japanese characters).

+1
Is there a different author (from Hosei University) you would like to set on the commit?

I was contacted by Yuji Tokiwa, though I'm not sure who else should share the credit (see also JIRA ticket).

Here is his github account https://github.com/tokiwa
You can change the author with:
git commit --amend --author "Yuji Tokiwa<EMAIL_ADDRESS>

Given license agreements, I think I should remain the author, with credit given in the JIRA - but thanks - I didn't know you could do that in github :-)

This pull request re-created folders that don't have anything in them. We now have osp folders again.


Support both single images and array/collection of images in the image plugin

Motivation
Given this resource: https://staging.nexus.ocp.bbp.epfl.ch/bbp_test/studio_data_11/resources/https%3A%2F%2Fbbp.epfl.ch%2Fneurosciencegraph%2Fdata%2F0ad06861-0c70-4e96-bf57-6ee488d204a1?rev=3
The image viewer plugin does not display.
I tried changing the property from distribution to image to no avail.
Acceptance Criteria

When a user provides one or more images in the resource payload, either under the schema:image property or the schema:distribution property (only for Files with a mediaType starting with image), the plugins should render.

It could also be an ID that point to a File or DataDownload object.

The behavior should be the same as described here: https://github.com/BlueBrain/nexus/issues/1696
If the image(s) cannot load, please provide an appropriate error message:

Is the file not accessible from the storage?
Is there a property missing?
Is the file not actually an image?
...

Add a download button next to the "add to data cart" button for each images in list view
Add a download all button at the top (that will use the archive to zip all images)

Examples:

schma:image is used with Traces (even though we exclude the image plugin for Traces, we can use a Trace resource to test)
https://staging.nexus.ocp.bbp.epfl.ch/bbp_test/studio_data_11/resources/https%3A%2F%2Fbbp.epfl.ch%2Fneurosciencegraph%2Fdata%2F0ad06861-0c70-4e96-bf57-6ee488d204a1?rev=3 (should also work with revision 4)

@adulbrich  As per the manifest, image viewer will work only of 1) The type is File and 2) it has a field with _mediaType which has value starting with "image". In the example we have here, the type is "Data Download" and the there no " _mediaType " property, but only encoding format.

Let's support both single images and arrays and id in both:
{
  "image": {}
},
{
  "distribution": {
    "@type": "File",
    "_mediaType": [
      "image/*"
    ]
  }
}

Adjusting the mapping solved the issue. If an array is used for the 'image' property then it must be added to mapping like so
"mapping": [     {       "image": {}     },     {       "image": []     },     {       "distribution": {         "@type": "File",         "_mediaType": [           "image/*"         ]       }     },     {       "distribution": {         "@type": "DataDownload",         "encodingFormat": [           "image/*"         ]       }     }   ],

@alex4200 this ticket is for accepting [] or {} under the image. For the image plugin to work please consult dhanesh's comments above. We also intentionally disable the 'preview' button for images within the "Preview" plugin. Reach out to me on slack if you have any other questions


Copy edit schema guide

This issue lists a number of things that should be taken care of when copy editing the schema guide before release:

[ ] Fix typos :roll_eyes:
[ ] Optimize names
E.g., for "transitive credit" (and perhaps "credit redirection"), also impacts https://github.com/citation-file-format/cffinit/issues/10
[ ] Mark definitions. keys as not to be used
E.g., look at visual cues (🔴 emoji?), or alternative text (replacing definitions and its subkeys should not be used directly in CITATION.cff files.), or marking the keys up differently (italic monotype?), or adding the key to use in brackets: definitions.version (version)?
[ ] Unify wording
E.g., are keys keys or fields?
[ ] Check if examples are in the right place
[ ] Use Usage examples if there is more than one?
[ ] Reformat key descriptions?
E.g., as >  quotes? See below
[ ] Check what parts in the other edit of the schema guide may be useful to have in the schema guide (e.g., the reference to the changelog?)
[ ] Add links, e.g., to YAML specs

Note: part of this work should probably be done in "pair copy editing" :hot_face:
Example section #
This is an example section describing a key, I quite like the highlighting, it's similar to that suggested in #220.
Perhaps required:'s value should only be bold when it's true?
Note: no Usage example: heading, this is indicated by putting the examples in the quote as well.

cff-version

type: string
required: true

The version of CFF used for providing the citation metadata.
cff-version: "1.2.0"

FWIW both the emojis and the quoted descriptions are a little too much markup for my taste

For markup, what about this?

authors

type: array of definitions.person and/or definitions.entity objects.
required: true
description: The authors of a software or dataset.
usage:authors:
  - given-names: Stephan
    family-names: Druskat

authors:
  - name: "The Research Software project"

authors:
  - given-names: Stephan
    family-names: Druskat
  - name: "The Research Software project"

I like it, let's do it like this!

All done :)


Caused by: com.fasterxml.jackson.core.JsonParseException: Unrecognized token

When I use hudi-0.7.0 and add clustering  to my program,  the same problem happened at the process time.But  before I add clustering,no problem.

Originally posted by @root18039532923 in https://github.com/apache/hudi/issues/1723#issuecomment-787778487

my param is following :

@satishkotha : Can you take a look at this ?

ok,I think data is right.I will share commit file  in a little while.

Thanks for your reply.Today I use this configuration,data has been written successfully.The configuration is the following:

However I find  a new problem,that I set 3 or more partitions,but only 2 partitions is clustering. The problem is the following:

Thanks for your reply.Today I use this configuration,data has been written successfully.The configuration is the following:

However I find a new problem,that I set 3 or more partitions,but only 2 partitions is clustering. The problem is the following:

The up-to-date  commit file is the following:

The content of<PHONE_NUMBER>1336.replacecommit.requested is the following :

@root18039532923 I opened a patch for this https://github.com/apache/hudi/pull/2622.
The problem is only with archival, so I believe clustering and data is all good.  Anyway, if you could try this patch and confirm issue is gone completely, that would be awesome.

Ok,today I will have a try.Thank you.

@root18039532923 Did you get a chance to try this patch? We can merge patch after your testing looks good.

I need the jar of the patch which you opened to test,but I am using inner-net. @satishkotha

After you merge the patch ,I have a try.because I have no the jar of  the patch.

@root18039532923 yes, You may find this page useful to build from source

@root18039532923 : once you respond, can you please remove "awaiting-user-response" label for the issue. If possible add "awaiting-community-help" label.

@root18039532923 Are you able to try out hudi-0.7.0 to see if your issue is resolved ? Please let us know so we can close this ticket

Closing this ticket since the patch is now landed and can be picked up from master if needed.

@root18039532923 were you able to solve this problem using the patch? I built hudi from the source using branch release-0.7.0, but the problem keeps happening in my env.


cannot play

It seems that I can open the server, but I cannot do anything on it.
The following errors often occur in the console:

When I try to create invite or click robots button, It shows this error:

My system is wsl2, I had tried several times to restore initial ubuntu system and then following setup docs step by step, I don't know
which step went wrong.
In addition, when executing "./b data-snapshot run" , this error always occurs the first time, but the second execution can pass, and then start the server. why wouldn't the second execution terminated? Does this error affect?

https://i.imgur.com/HanBmZz.png
I also have "Tray not found" error.
WSL2 here too.


No ability to pass constructor arguments

Currently, there is no way to pass constructor arguments in the deploy function.
This stops the ability to deploy contracts that require args in their constructors.
Could this please be added?

Yes! This is in the works already thanks for raising it.
On Sat, 13 Nov 2021 at 00:06 ponderingdemocritus @.***>
wrote:

Currently, there is no way to pass constructor arguments in the deploy
function.
This stops the ability to deploy contracts that require args in their
constructors.
Could this please be added?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/OpenZeppelin/nile/issues/30, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAM77FYH75UWKJ5JWOIFM3LULXI4BANCNFSM5H6DT75A
.

amazing! looking forward to it

Released in 0.2.1